kEY Moves in IR

[JohnParks]

I am trying to incorporate this function into my urc-6131 via a key move in ir. L1 works, but L2 doesn't.

Learned1 via urc-8811 form OEM
Protocol: NEC1
Device: 210
Sub-Device: 108
OBC: 140
HexCmd: CE
EFC: 060

Learned2 via urc-8811 from urc-6131
Protocol: NEC1
Device: 210
Sub-Device: 109
OBC: 140
HexCmd: CE
EFC: 060

Obviously this has something to do with the Sub-Device differences. I am using setup code 0315 which does not contain the above EFC: 060.

[gfb107]

What device type is setup code 0315? The reason I ask is that setup code TV/0315 is NOT the same as setup code VCR/0315.

I took a quick peek in devices.xls, and the only setup code I could find that uses NEC1, device 210 sub-device 109 is Audio/0135

[JohnParks]

Thank Grea for your help. Sorry, I should have stated Audio for the setup 0135. I am using a Onkyo TX-SR501. I am using two other simular function as key moves in IR and they work fine. These two have EFC's of 53, and 58, which are present in setup 0135.

[gfb107]

I found Onkyo_HT-SR510_Receiver.txt, which seems to use a mix of sub-device 108 and 109. I'm fairly certain Audio/0135 only uses 108.

I think you'll just have to use that device upgrade.

[JohnParks]

I'm just not understanding the relationship of protocol, Device, Sub-Device, OBC, HexCmd, and EFC with the fixed and varible part of the transmitted signal. If Device/Sub-Device is the fixed part then why would the OEM want to change it instead of just adding new EFC's? Also, other then base 10/16, OBC, HexCmd, and EFC seem in some cases to be used interchangeably, but not in others with protocol being the determining factor. These subtleties are eluding me. Having to do an upgrade just for one function just doesn't make sense.

I do not expect a detailed explanation to the above, but some pointers to some .doc's would be greatly appreciated. I have read about everything on this site and yahoo which in many cases only adds to the confusion.

[johnsfine]

I'm just not understanding the relationship of protocol, Device, Sub-Device, OBC, HexCmd, and EFC with the fixed and varible part of the transmitted signal. If Device/Sub-Device is the fixed part then why would the OEM want to change it instead of just adding new EFC's?

Sometimes the OEM does that because they view something like a tuner and an amp as two seperate devices even when they sell a product containing both. Using different subdevices may simplify their task of modularizing their designs.

More often we have no clue why the OEM complicates their job of encoding and decoding IR signals by mixing subdevice numbers when using other OBCs would be simpler.

Also, other then base 10/16, OBC, HexCmd, and EFC seem in some cases to be used interchangeably, but not in others with protocol being the determining factor. These subtleties are eluding me.

The OBC is the number actually encoded in the IR signal as a command. But that is only based on our reverse engineering of the IR signal. We needed to guess what part of the signal was command vs. other things and how that part encodes a number. Usually there are enough clues that we can be confident our reverse engineering has reach the set of numbers that the original device designer started with, but not always.

The HexCmd is the non-fixed part of the data that a UEI protocol module uses to decide what to send. Usually that has one of a few simple relationships to the OBC. But that depends on how someone at UEI reverse engineered the signal.

The EFC is a crude encription of the HexCmd.

They are used "interchangeably" in the sense that they normally carry the same information (but in different forms). If you know which protocol module is being used, you know how to translate between OBC and HexCmd. For any one byte HexCmd there is a fixed rule for how to translate to and from EFC.

[NatasCub]

Considering I've just gone through and catalogued the protocol, device, and sub-device for the remote that came with my Onkyo TX-SR500, I'm curious what L2 maps to on your original remote? Based on the codes I've gathered, your L1 maps to the DVD input select button on your remote, however L2 does not seem to map to anything my remote generated, nor does it seem to match up to any of the additional codes I've gathered from other Onkyo models.