JP1 Remotes

Hi,

It seems like FF is longer than 01 when specified for this protocol, but even FF seems like it is still less than one second... Any ideas?

Thanks,

Alan

Yes, you are correct. The 2116 extender only generates a very short pause. If you use KM to generate the pause protocol you will get one that lasts alot longer. All you need to do is use the protocol out of KM to replace the one in the extender via IR and you are good to go.

Nils_Ekberg wrote:Yes, you are correct. The 2116 extender only generates a very short pause. If you use KM to generate the pause protocol you will get one that lasts alot longer. All you need to do is use the protocol out of KM to replace the one in the extender via IR and you are good to go.

Thanks, I'll get the pause protocol from KM then.

I have another question, my Tivo OEM remote can process keystrokes much faster than via the 2116. I tried dropping my keymoves from 90 to about 30 and this didn't seem to affect the speed, so I wonder if the issue has something to do with the custom tivo protocol. Here is a cut from the protocol that has to do with timing, could I begin to cut some of these values down to smaller values to make the protocol work faster, thereby increasing my remote speed for actions like up up up up? Should I halve each one or specific ones to start?

DW 0011Ah ; 0 bit on time - 564 us
DW 00106h ; 0 bit off time - 524 us
DW 0011Ah ; 1 bit on time - 564 us
DW 00331h ; 1 bit off time - 1634 us
DW 0D742h ; Length - 110212 us
DW 011A7h ; Repeat on time - 9038 us
DW 008B7h ; Repeat off time - 4462 us

Thanks,

Alan

Conceptional the 2116 with the extender should be just as fast if not faster than the OEM. You could try to experiment with the timing but my guess is the timing needs to be there for the command length and would not impact the speed of the keystroke. It is worth trying unless someone else has a suggestion.


2 questions:

1) how is the speed of the keystrokes for your other devices

and

2) Have you ever tried version 2 of the extender. There is extra overhead in version 3 that could potentially be causing the problem but I have never tried 3 so I am just shooting in the dark here.

Nils_Ekberg wrote: 1) how is the speed of the keystrokes for your other devices
and
2) Have you ever tried version 2 of the extender. There is extra overhead in version 3 that could potentially be causing the problem but I have never tried 3 so I am just shooting in the dark here.

Pretty slow. In fact if I press a key 5 times in a row, I get 3 of them. Ext3 with an empty configuration is as fast, but as soon as I add 5 keymoves to it, it slows right down.

Ext2 seems to act the same way.

Ext1 for some reason doesn't. Even after loading up a bunch of custom devices it still seems fast.

Any ideas on ext2/3 or should I just use ext1? I really like ext3 if I could figure out the speed issue. Is there anything in its ASM processing loop I could eliminate to make it faster? I could recompile it...

Thanks,

Alan

I have not looked inside the code for a long time but I know I am running ver2 with no problems and have a lot of keymoves and macros.

I will take a look at it (ver 3) and see if anything jumps out.

Nils_Ekberg wrote:I have not looked inside the code for a long time but I know I am running ver2 with no problems and have a lot of keymoves and macros.

I will take a look at it (ver 3) and see if anything jumps out.

After some more testing I found that all 3 extenders (1,2,3) are slower than a non extended remote. Unfortunently I need many of the extender features, so I will have to sacrifice a little speed for a lot more flexibility. I did shorten the custom Tivo protocol delay a bit and that also helped.

Thanks for the help,

Alan