JP1 Remotes

gadget00 wrote:Am I right in hoping that I may get different information from the new JP1 learning remote that I bought, if I can get it to connect?

Doesn't seem likely.

gadget00 wrote:Also - what is the "S0" that transmitts after every command? It doesn't happen after every IR command from other remotes - only these particular buttons I'm trying to program.

That is just the way that IR capture system responds to a behavior of the NEC1 protocol that most other protocols don't have.

Lots of other remotes use NEC1. It is very common. But I guess the other remotes you tested do not use NEC1.

Hmmm. Darn.

So - any suggestions? Not quite sure what to do next.

My goal out of this whole project is simply to get the Audio Authority codes on to the Comcast remote (preferably as shifted keys 1-6). Beyond that, it would be nice to connect the new 9910 so I could program it.

Here's the IR file I created:
https://www.hifi-remote.com/forums/dload ... le_id=5216

I'll xpost this link to the other thread I started in JP1 beginners, too.

johnsfine wrote:

gadget00 wrote:Am I right in hoping that I may get different information from the new JP1 learning remote that I bought, if I can get it to connect?

Doesn't seem likely.

gadget00 wrote:Also - what is the "S0" that transmitts after every command? It doesn't happen after every IR command from other remotes - only these particular buttons I'm trying to program.

That is just the way that IR capture system responds to a behavior of the NEC1 protocol that most other protocols don't have.

Lots of other remotes use NEC1. It is very common. But I guess the other remotes you tested do not use NEC1.

Your .IR file is not correct as you don't have any of the Input buttons associated with any keys in your CBL/2047 device upgrade. In your previous .IR file, you had Input 1,2,3 assigned to A,B,C keys. We then mapped CABLE buttons A,B,C to use CBL/2047 A,B,C keys respectively. You also have keymoves mapping CBL/SHIFT-1 to CBL/2047 SHIFT-1. You should be mapping to CBL/2047 A key.

Ah. I feel stupid.

I tried two more things, but it still doesn't work. I changed the RM file so that the Sources 1-6 are shifted buttons 1-6 on the remote. A link to that is below.

Also below are two links to two versions of the IR file. Neither work. Version 1.1 freezes the remote. Version 1.2 doesn't freeze the remote, but when I try hitting the shifted-1 key, it doesn't send out an IR signal at all (confirmed by my computer).

What am I doing wrong?

Again - thanks for all your help.

RM file v1.1:
https://www.hifi-remote.com/forums/dload ... le_id=5220

IR file v1.1:
https://www.hifi-remote.com/forums/dload ... le_id=5218

IR file v1.2:
https://www.hifi-remote.com/forums/dload ... le_id=5219

binky123 wrote:Your .IR file is not correct as you don't have any of the Input buttons associated with any keys in your CBL/2047 device upgrade. In your previous .IR file, you had Input 1,2,3 assigned to A,B,C keys. We then mapped CABLE buttons A,B,C to use CBL/2047 A,B,C keys respectively. You also have keymoves mapping CBL/SHIFT-1 to CBL/2047 SHIFT-1. You should be mapping to CBL/2047 A key.

Update: vickyg2003 was able to load your .IR file and learn the codes and they learn as expected.

For v1.1 .IR file, you also have CBL/2047 assigned to the CABLE button but you should have CABLE assigned to CBL/1376.

Since you are using the SHIFT-Key button to assign functions in the RMDU file, RM generates KeyMoves to support this. This is why your device upgrade has no buttons assigned with functions. You can see this in IR.exe's Device Tabsheet as the right panel shows [NotMapped] for all the buttons.

RM is generating a KeyMove that uses the EFC format option. You can also verify the EFC values within IR.exe match what RM has.

Your v1.2 .IR file doesn't work because it is referencing a button that doesn't exist in the device upgrade.
Since you are not using the device upgrade directly, it doesn't matter which buttons hold your function codes. Your initial .IR file had it on the A,B,C buttons. Then follow the steps on creating a KeyMove to use the A,B,C buttons from the CBL/2047 device upgrade.
So pressing A in CABLE mode means use CBL/2047 keycode A(which is Input1).

Also, if you assign a KeyMove to a SHIFT-<digit>, then to invoke this function, you'll have to press SHIFT SHIFT <digit> on the remote for it to work.

Alright. I think I've got it, then. Thanks!

So - is there a way to create a shifted key and only have to press the "setup" button one time?

binky123 wrote:Update: vickyg2003 was able to load your .IR file and learn the codes and they learn as expected.

For v1.1 .IR file, you also have CBL/2047 assigned to the CABLE button but you should have CABLE assigned to CBL/1376.

Since you are using the SHIFT-Key button to assign functions in the RMDU file, RM generates KeyMoves to support this. This is why your device upgrade has no buttons assigned with functions. You can see this in IR.exe's Device Tabsheet as the right panel shows [NotMapped] for all the buttons.

RM is generating a KeyMove that uses the EFC format option. You can also verify the EFC values within IR.exe match what RM has.

Your v1.2 .IR file doesn't work because it is referencing a button that doesn't exist in the device upgrade.
Since you are not using the device upgrade directly, it doesn't matter which buttons hold your function codes. Your initial .IR file had it on the A,B,C buttons.

Code: Select all

Upgrade Code 0 = 07 FF (CBL/2047) Audio Authority AVAtrix sources for the Comcast-URC-1067 (using A,B,C) (RM v1.82)
5A 00 00 00 00 1D 20 FD 06 5F 9F 1F 
End

Then follow the steps on creating a KeyMove to use the A,B,C buttons from the CBL/2047 device upgrade.
So pressing A in CABLE mode means use CBL/2047 keycode A(which is Input1).

Also, if you assign a KeyMove to a SHIFT-<digit>, then to invoke this function, you'll have to press SHIFT SHIFT <digit> on the remote for it to work.

gadget00 wrote:Alright. I think I've got it, then. Thanks!

So - is there a way to create a shifted key and only have to press the "setup" button one time?

YES! Don't use DIGIT buttons.

A single press of "setup" accesses the shifted function assignments for all buttons ASIDE FROM the DIGITS. Only the digits require TWO presses of "setup" to access a shifted function, because for a SINGLE press of "setup", a subsequent numeric press is expected to be the first in a sequence of an EFC being sent directly (i.e. to send EFC 64, one would press <setup><0><6><4>, so it wouldn't know to execute the shifted <0> function. Hence a second press is required.

(Of course none of that applies if you're using an extender. Single press for shifted buttons all around.)

Wow, that was quick. Thank you all very much!

Capn Trips wrote:

gadget00 wrote:Alright. I think I've got it, then. Thanks!

So - is there a way to create a shifted key and only have to press the "setup" button one time?

YES! Don't use DIGIT buttons.

A single press of "setup" accesses the shifted function assignments for all buttons ASIDE FROM the DIGITS. Only the digits require TWO presses of "setup" to access a shifted function, because for a SINGLE press of "setup", a subsequent numeric press is expected to be the first in a sequence of an EFC being sent directly (i.e. to send EFC 64, one would press <setup><0><6><4>, so it wouldn't know to execute the shifted <0> function. Hence a second press is required.

(Of course none of that applies if you're using an extender. Single press for shifted buttons all around.)