Issue with 2 byte codes in IR5.10 and RM 1.03

gfb107 · Post by **gfb107** » Tue Aug 17, 2004 3:05 pm

The point is that the 6131 stores keymoves differently than almost all other remotes, and IR hasn't been enhanced to handle this. So IR doesn't know how to display the keymoves, and it doesn't know how to create them. So, you just can't use IR to deal with the keymoves.

Now, why are you so averse to installing the extender? The process is very simple, and you can always undo it if you aren't happy with it.

Post by **The Robman** » Tue Aug 17, 2004 3:07 pm

mikea128 wrote:I was just about to play around some more when I saw this post - it is in fact a URC-6131! I didn't realize it didn't do 2-byte keymoves? I could have sworn i had some in there already, but maybe i'm just crazy? The older IR showed the keymoves correctly at least...

hmmm so, is there a work around?

Option 1 is to use the extender.

Option 2 is to create additional device upgrades that contain all the functions that you need and then do keymoves from them

For example, let's say that you've created an upgrade for your DVD player, but there are still a few functions missing and you want to program them to the 3 PIP buttons. You would create a second upgrade that just contains the three additional functions (mapped to any button, it doesn't matter). Next you would assign that upgrade to a device button in IR and load it into the remote. Then on the remote itself, keymove those three functions from the buttons that you programmed them to, to the 3 PIP buttons and download using IR. You will now see 3 new keymoves that perform the 3 functions in question. You are now free to de-assign that upgrade from the device button and continue with your customization.

Don't be concerned with how the keymoves look in IR. The hex code that gets stored for these keymoves is the hex version of the keycode of the button from where they came (ie, the button that you programmed them to in the 2nd upgrade that you created).

This work around is the only way you can use some special protocols, like the device multiplexor, in an unextended URC-6131.

mikea128 · Post by **mikea128** » Tue Aug 17, 2004 9:15 pm

ok i think i follow...seems like i could just do a keymove on the remote and be ok, except that i want them on phantom keys. but if i could do a keymove on the remote and simply change the key that it's mapped too, IR screws it up and it no longer works...hmmmm?

Post by **The Robman** » Tue Aug 17, 2004 11:02 pm

No, IR won't screw it up. You can absolutely program keymoves to regular buttons using the remote itself, then use IR to convert them to phantom buttons.

mr_d_p_gumby · Post by **mr_d_p_gumby** » Wed Aug 18, 2004 1:53 am

The Robman wrote:You would create a second upgrade that just contains the three additional functions (mapped to any button, it doesn't matter).

If you are concerned with trying to keep these "keymove upgrades" to a minimum size, be aware that if you map a function to a digit button, the upgrade will have to define bytes for all ten digit buttons. Similarly, if you map it to a volume button, you'll get three bytes for vol+/-/mute. Channel+/- go together too. Other than that, you can map to any button and only use one byte per mapping.