JP1 Remotes

vickyg2003 · Posted: Sun Jan 16, 2011 5:11 pm Post subject:

Well it would seem that there is an error in the 5 digit EFC calculation.

For example
Play

RM says 00044
KM says 65580

to see which was right, I set my Comcast to Aux/1232

I then captured the resulting signals to IR Scope,
Both came out as Sony12 Device 20, OBC 51

The funny thing is, when I plugged either of those numbers (00044, or 65580) into the 5 digit EFC in RM, the result was also Sony 12, Device 20, OBC 51.
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

cauer29 · Joined: 03 Feb 2010 Posts: 236

3FG · Expert Joined: 19 May 2009 Posts: 3367

Vicky,
As cauer29 has said, 44 and 65580 are the same number, because by definition an EFC fits into 16 bits, and the largest number is then 2^16-1=65535. So for uploading with a cable either form is acceptable. If the number is too big, bit 16 is automatically discarded.

But evidently the routines that accept EFC manually consider a leading pair of zeros to indicate that a 3 digit style EFC is being entered. So we should never try to use 00xxx as a true 5 digit EFC. Instead it should be added to 65366. Put another way, if the EFC is going to be used by an executor which takes 1 byte, then the EFC should be expressed as 00xxx.
If the EFC is going to be used by an executor that needs two bytes of hex data, add 65536 if necessary to avoid 2 leading zeros.

Of course it would be nice if RM did that automatically, but as a general thing, RM has been written for JP1 interface users rather than folks trying to manually program their remotes.

vickyg2003 · Posted: Sun Jan 16, 2011 7:02 pm Post subject:

Oh I see the problem, the rest of the information is on the other page.

You guys think I'm complaining because two EFC's send the same code,
I'm complaining because the EFC doesn't send the correct code.

Play is
Sony15 Dev 151, OBC 24

But NEITHER EFC sends this code, they both send
Sony12, Dev20, OBC 51
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

3FG · Expert Joined: 19 May 2009 Posts: 3367

Vicky,
I carefully checked that EFC 65580 should give hex data 59 E9. It should. So I worked through what the 00 27 executor needs to send device 151 OBC 26, and that turned out to be 59 E9. So belatedly, I used a Comcast 1067BX3 (setup code 21232) to send EFC 65580, learned it, and .... it was device 151 OBC 26, both in IR and RMIR.

However, manually assigning EFC 00044 does send Sony 12, device 20, OBC 51. This is, IMO, expected since that's what the 3 digit EFC 044 would provide.

The part that is odd is that entering 65580 into the EFC5 column in RM does put 044 into the EFC3 column, and 25833 into EFC5, and of course the hex data corresponds to 25833 rather than 65580. So I think that's a bug in RM. It is however, unrelated to the Sony 12/15/20 Combo-- the same thing happens with NEC 4 DEV combo.

vickyg2003 · Posted: Mon Jan 17, 2011 8:17 am Post subject:

3FG · Expert Joined: 19 May 2009 Posts: 3367

Vicky,
At least one of us doesn't understand the situation.

Here's what I think:
There is no "65536 limit" on 5 digit EFCs. In fact it is common to manually enter EFCs into the low 70,000 range. It is similar to 3 digit EFCs. Those have only 256 unique values, but the remote will let you enter e.g. 356 and internally convert that to 100.

To put it bluntly, I think the assertion that EFC 65580 (entered manually) sends Sony 12, Device 20, OBC 51 is incorrect. I tried it, and it sends Sony 15, Device 151, OBC 26.

I believe that all the Bravia Synch signals can be sent by UEI remotes, and that these can be entered manually into the remote. I haven't tried entering them as keymoves using EFCs in IR or RMIR.

vickyg2003 · Posted: Mon Jan 17, 2011 3:09 pm Post subject:

vickyg2003 · Posted: Mon Jan 17, 2011 6:35 pm Post subject:

I was able to reach some of my remotes, and can say that 10820 works just fine and can send out these 5 digit efcs.... Don't know what is going on with the Comcast because repeated tests show you can't enter those numbers from the keyboard.
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

vickyg2003 · Posted: Mon Jan 17, 2011 7:39 pm Post subject:

Apparently this is just a problem with 5 digit EFC remotes that have AdvancedCodeFormat= EFC,

The only two remotes that I can think of that have that combination is the URC9960B01 and the Comcast

The other early 5 digit EFC remotes had even more problems.

But this is something to keep in mind for all those people that come asking for codes on the Comcast.
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.