JP1 Remotes

On my 3680 and my Charter C4000, I can program functions to the shifted number keys but they do not work.

Example: I wanted to put my Aiwa stereo's Disc 1 key at shift-1.

Is that a limitation of these two remotes, the JP1 program or something else?

They do work, but you have to hit the "shift" button twice, otherwise the remote thinks you're manually entering an advanced code (EFC).

I used to create my own manuals for these remotes where I described that feature, like this:
http://www.hifi-remote.com/manuals/rs-l ... 1994#shift

Great. Much appreciated.

Are you saying that you can send an EFC command without assigning it to a key (as in Setup #####)?

SysTech_Larry wrote:Are you saying that you can send an EFC command without assigning it to a key (as in Setup #####)?

yes

Using that info and an upgrade file, I was able to generate all 256 EFCs for NEC & Roku devices.

For other devices, would I add two leading zeros to the three-digit EFC or just copy the five-digit EFC, as given?

The reason that UEI switched from 3-digit EFCs to 5-digits was to allow EFCs to be used for executors that use 2 bytes of variable data. So, if the "other device" uses such an executor, the EFCs will really be 5-digits. For executors like NEC that only use 1 byte, the old 3-digit EFCs simply have 2 leading zeroes added.

Now, if you're using the SETUP+EFC function to test missing EFCs, there is a better way. When I do it, I create testing upgrades that only contain the missing codes, then I load them all up to my remote and just start pressing all of the buttons. When I come across a button that does something, I go back to the spreadsheet that I used to generate the lists and notate what it was, then when the exercise is done, I add all the new codes to my original upgrade file.

Hello Larry,
I've been following your development.

There are two terms we use here, EFC and OBC that are rather confusing, and extremely important to differentiate.

We have protocol executors, and device codes.

The protocol executor is like a little subroutine, that takes some fixed data and some variable data to generate the signal for a various button push. The EFC = the variable data. The desired output will be an OBC. Over time the protocol executors in newer remote will need to have different EFC's fed in to get the desired output.

The RDF (remote definition file) keeps track of which version of the executor each remote has and our tools will create the EFC's


An OBC - original button code is what the remote is sending.

An EFC is a parameter that will get an executor to send the OBCs

So bottom line, if you want to move information from a remote that uses 3 digit EFCs to a remote that uses 5 digit EFCs, work from OBCs and let the JP1 tools compute the EFCs.

Thank you.

The Robman wrote:...
Now, if you're using the SETUP+EFC function to test missing EFCs, there is a better way. When I do it, I create testing upgrades that only contain the missing codes, then I load them all up to my remote and just start pressing all of the buttons. When I come across a button that does something, I go back to the spreadsheet that I used to generate the lists and notate what it was, then when the exercise is done, I add all the new codes to my original upgrade file.

I have done that for general function searches, but SETUP+EFC sounds handy for a one-off test.