Decoding learned signals improperly?

[Gerard Pinzone]

I'm using a RadioShack 15-2104 remote for my new Viewsonic N2635w LCD HDTV. I learned all the buttons from the original and then used ir.exe to see the protocol, OBC, EFC, etc. so I can make a new device using KM.

Most of the functions work fine. However, some of them will not work properly. The learned signal from the remote works on the TV as expected, but reproducing the function (using KM and ir.exe) fails.

Here's a screenshot of IR:



It seems like the protocol is recognized (RC5 is pretty darn basic). What's really odd is the OBC vs. EFC/Hex values. KM's calculation yields different OBCs for the EFC/Hex values listed, but not the other way around.

Anyone know what might be going on here?

[Evan_s]

It's best to actually upload the IR file with the learned signals to the files section and link to it.

[Capn Trips]

Have you read the Protocol Help for RC5 in KM?

If so, are you entering device code 0 or 100?

Code: Select all

RC-5 is a quickie combo protocol, allowing you to combine up to 
three RC-5 device codes. You select which device code you wish a 
function to use by entering the OBC in the OBC column of the 
Functions sheet, and then entering a "0", "1", or "2" in the byte2 
column. However, you will only have access to OBC's 0 - 63. In 
order to access OBC's in the range 64 - 127, you will need to add 
100 to the device code entered.

[Gerard Pinzone]

I'm going to try to implementing that, but one of the problem functions has an OBC less than 64.

[johnsfine]

Capn Trips gave you most of the answer, maybe all you need. I'll add a few details anyway:

1) Don't use the EFC numbers from those decodes. Use the OBC numbers. There are other situations in which someone may need the EFC numbers, so IR.exe displays them. But for building an RC5 upgrade, OBC numbers will work much better.

2) Since most of your functions work, I assume most of your OBC numbers are less than 64. So you need to leave the device 0 setting for the first device number on KM's setup sheet. Put 100 as the second device number. Then on each line in the functions sheet that needs an OBC greater than 63, you put 1 in the byte2 column to select that.

I'm going to try to implementing that, but one of the problem functions has an OBC less than 64.

If that is still true after retesting, post some more details. That would be seperate issue. We DO understand why all the OBC numbers above 63 didn't work and what to do to fix that.

[Gerard Pinzone]

I got it to work. When you load the file into KM, the OBC numbers look wrong since OBC (in KM) = OBC (in IR) - 64.

I guess I've never ran into a RC-5 device with OBCs > 63

I will upload the device to the file area in case anyone else needs it.