JP1 Remotes

Friday, I don't quite know what I'm doing in protocol builder, but it looks like we could turn the repeating off on all keys but the Volume, Channel, FF and Rewind keys.

Update the protocol in IR with this code and see if this improves things.
Make sure you only end up with one 01ff protocol. Edit your existing protocol by pasting everything from the word Upgrade through the word End.



Upgrade protocol 0 = 01 FF (HCS08) PID 01 FF (RM v1.73)
20 15 23 47 11 CD 4E 08 08 01 21 03 45 01 21 01
1A D4 FD 11 A7 08 CB 3F 62 3F 63 6E 03 AA CC FF
5F
End


If this doesn't improve things I'll try my hand at tweaking the leadout time.

to understand it right. my protocol at moment is

Upgrade protocol 0 = 01 FF (HCS08) Manual Settings (RM v1.86)
20 15 23 47 11 CD 4D 08 08 01 21 03 45 01 21 01
1A D4 FD 11 A7 08 CB 3F 62 3F 63 6E 03 AA CC FF
5F
End

and replace it with

Upgrade protocol 0 = 01 FF (HCS08) PID 01 FF (RM v1.73)
20 15 23 47 11 CD 4E 08 08 01 21 03 45 01 21 01
1A D4 FD 11 A7 08 CB 3F 62 3F 63 6E 03 AA CC FF
5F
End

i will try next days and reply

thanks so far

The change of 4D to 4E is the only part that actually makes a difference.

i am sorry for my very late reply, but i had a very bad flu last month.

so, i changed the protocol from 4D to 4E
the effect is, that the comands are send only 1 time. even when i pressing longer, there is none repeat of any function.

That was the desired effect for the regular buttons, but the VOL, CH and FFWD and REW buttons should repeat.

yes they repeat

in few situation this is better for me, but when i scroll in my videolist which is very very large, it is quite boring to push 189 times "down" to reach the last entrys of my list. only to play a movie with the letter "W"
because the tvix does not support page-scroll.

is there any other way?

I hope you are feeling better.

One other solution would be adjusting the lead out time. However, the leadout time on this protocol appears to be near the maximum. If I try upping the leadout time past 13166 it appears to get shorter instead of longer.

Here is an upgrade with the lightly longer leadout time.

Upgrade protocol 0 = 01 FF (HCS08) PID 01 FF (RM v1.73)
20 15 23 47 11 CD 4E 08 08 01 21 03 45 01 21 01
1A FF FD 11 A7 08 CB 3F 62 3F 63 6E 03 AA CC FF
5F
End


If this doesn't work for you, you might want to put the up/down arrows on keys that still do repeat when you change the 4e to 4d .

I have started working on this but ran out of time to complete it yesterday evening. I will pick it up again this evening.

@vickyg

i have tested your last change but there are still no repeats. unfortunately i need the buttons that have repeats for his normal functions. and because of my handycap i even cant reach other buttons than the up/down for scrolling.

maybe therobman find another reason

but there are still no repeats.

That is not what I was expecting at all! I thought the repeats would be too fast again. I'll try to find my WIDGET to see exatly what adjusting the leadout time is doing.

oops! That should have been

Upgrade protocol 0 = 01 FF (HCS08) PID 01 FF (RM v1.73)
20 15 23 47 11 CD 4D 08 08 01 21 03 45 01 21 01
1A FF FD 11 A7 08 CB 3F 62 3F 63 6E 03 AA CC FF
5F
End

I still had repeating turned off. The 4e needs to changed back to the 4d.

It repeats slower than the original upgrade. I can see it even without looking at the graph. But will it be slow enough?

not slow enough

in use, i cant really feel a difference to the original

ps. the scrolling up/down is ok, but when i make changes in dvd-setup. e.g. change resolution, change audio-setup...
and then confirming (left=yes/right=no) i NEVER hit the yes. because right there its to fast.

sorry for my bad english

Just FYI, I think the problem here is that the leadout time is too large, not too small. With a smaller leadout time, the device would know that the remote is repeating and would act appropriately. With the longer leadout time, I think the device thinks the user is deliberately pressing the button really fast.

Earlier you said that

That probably means that the leadout time is too short, so the executor would need to be fixed in PB.

It is a fairly large leadout time even before I started tweaking it.

I think the problem here is that the leadout time is too large, not too small. With a smaller leadout time, the device would know that the remote is repeating and would act appropriately. With the longer leadout time, I think the device thinks the user is deliberately pressing the button really fast.

If the user was pushing the key rapidly wouldn't the whole key repeat? If I'm using my widget correctly the repeat portion isn't the whole sequence.
I totally don't understand the logic here.

How much should we shorten the leadout time?

FRIDAY, I have a lot of trouble with menu's too. If I navigate a menu I never try to scroll through the choices, I always tap the button when navigating menu's giving me one tap at a time.

Perhaps for Menu Naviagation you can set up some Macros that can navigate the menu to do the mundane chores. That's how I got hooked on JP1. I wrote 2 macros that did menu navigation and gave me single taps, because like you I had lots of trouble getting just one press of the keys. Now that I know better, I turn off all repeating because I'm not precise with my pressing either.

I made that last statement as a way of correcting my earlier statement, as I could see that you were following my earlier statement.

When I started working on this last Thursday I noticed that the leadout time was very large and much larger than the time reported in the signals, so my intention is to come up with a more realistic time and then try testing it.

As for the logic, look at it this way. If the leadout time is set to the correct shorter time called for by the protocol, and the device detects that shorter leadout time, it would know that the button is being held and would respond accordingly (ie, it would actually repeat the function at a speed that the user could deal with, and I assume this is how it works when the OEM remote is used).

On the other hand, imagine that the user is really pressing the button quickly, the time between button presses is still going to be long (by protocol standards) no matter how quickly the user is actually pressing the button. So, my assumption is that this is what's happening here, with the long leadout that I mistakenly built into the original protocol, the device thinks that the user is pressing the button repeatedly and very quickly and is responding accordingly.