6131 Key Move Format

[cerulean]

Hi,

I've been programming my 6131. I searched and found that I can't do key moves from within IR because of the way that Key Moves are stored on the 6131. I manually did my key moves using 994 and cloned them to the hidden dev keys. But now I need to "move" a key to my TV enter button to change the aspect ration on my TV. Since I can't use 994 to do this (it's an EFC that's not in the code for my TV), I need to do it in IR.

Is there some corralation between what you see in IR and what the code really is when you program Key Moves from within IR?

Thanks,
Bob

[johnsfine]

1) I'm pretty sure you can do the KeyMove manually on the remote:

TV
Long press of Setup key
9 9 4
Short press of Setup key
EFC number
Target Key (Enter)

2) You can enter that in IR, if you know how. I think I remember how, but I'm not sure:

Use a hex calculator (not IR's EFC calculator) to convert the EFC number from decimal to hex.

Create the KeyMove in IR and select "hex command" rather than "EFF" and enter the hex command 00 XY where XY is the hex value you computed above. The space is required between the 00 and the XY.

[cerulean]

TV
Long press of Setup key
9 9 4
Short press of Setup key
EFC number
Target Key (Enter)

John,

Thank you. I'll give it a try when I get home.

Bob

[The Robman]

You are correct that the format used to save the data has changed (and we are working on a fix for a future version of IR to handle it), but the manual procedure for entering key moves and advanced codes has NOT changed.

Just in case you are interested, the new formats are as follows:

1. Key Moves
Always 5 bytes, where the final byte is the keycode of the button that the function is assigned to in the original setup code or upgrade.

2. Advanced Codes
Always 6 bytes, where the final two bytes are the EFC.

[If the base EFC was used (ie, 0 thru 255) byte5 will be zeroes and byte6 will contain the EFC. If an EFC over 255 was used, the overflow data will be in byte5 and byte6 will contain the base EFC.]

Even though the URC-6131 uses 3 digit EFCs, in the future remotes will use 5 digit EFCs which is why the format now uses two bytes.

[cerulean]

John,

The Key Move worked fine punching in the EFC. Thank you.


Rob,

Thanks for the information on the format. But it's beyond my knowledge level. I'm comfortable using the KM spreadsheet and IR, but have never had to go beyond that level. I look forward to the future release of IR.

/Bob