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

mikea128 · Post by **mikea128** » Sat Aug 14, 2004 11:42 am

First, I must say that JP1 has come a long way in the last year or so since I last played with it. RemoteMaster is amazing and just what I had envisioned, but....

1. i can't get IR 5.10 to work with any 2 byte protocols as keymoves or upgrades. If i put in a keymove with 2 bytes (whether i copy paste from RM/KM or manually type it in) it's immediately changed once i hit "OK" and look in the keymoves tab of IR. It changes the hex consistently. If i click on it again to edit and simply hit ok, it changes again. For example $FF $FF changes to $A6 $A6, which then turns into $9D $9D.

2. Whenever I import 2 byte KM files into RM, things also get screwed up. I have yet to find a good pattern to this, but here are two examples. With Denon-receivers.txt from Yahoo, the first byte is either C8 or B8, all of which are changed to F8 in RM. With the Panasonic 53WX52 RPTV.txt file, the bytes are swapped and all FF and DF become FF. Maybe it's the first 4 bits? But why is one swapped and the other not?

I'm not sure what I could be doing wrong, but any help would be greatly appreciated. I get the feeling this can't be a bug because I feel that someone else would have caught it by now, especially the IR one. I could go back to doing it the old KM way with an older version of IR, but this is soooo much easier, especially with the ability to add comments in IR.

Thanks!
Mike

gfb107 · Post by **gfb107** » Sat Aug 14, 2004 3:55 pm

In the future, please post links to the files you refer to, so we can get them without having to search for them.

I'm taking a look now.

gfb107 · Post by **gfb107** » Sat Aug 14, 2004 7:51 pm

Looks like v1.03 broke importing of upgrades that use byte2.

v1.02 seems to work. You can still get that at https://sourceforge.net/project/showfil ... p_id=30560

A warning about the Panansonic upgrade. in v1.02, RM chooses a different variant of the protocol than KM does, so the hex commands have the bytes reversed. If you manually change the protocol to "Panasonic Multi-Device (Hacked)" and put in the correct "Main Device" and "Sub-Device", it'll work.

mikea128 · Post by **mikea128** » Sat Aug 14, 2004 11:38 pm

Thanks for the help. I'll be sure to post links next time. Any idea about the IR issue? I tried 5.09 with no luck. I think 4.xx works, but that doesn't support comments which i'd really like to use.

mikea128 · Post by **mikea128** » Mon Aug 16, 2004 12:23 pm

can anyone at least confirm that they have the same IR issue with 2 byte codes?

e34m5 · Post by **e34m5** » Mon Aug 16, 2004 12:40 pm

I just created a few two byte codes in 5.10 w/o problems. What error are you getting. You did select the Hex radio button..right

johnsfine · Post by **johnsfine** » Mon Aug 16, 2004 12:56 pm

mikea128 wrote:can anyone at least confirm that they have the same IR issue with 2 byte codes?

I tried device upgrades with 2 byte hex going from RM to IR with and without KeyMoves, plus I tried KeyMoves defined directly in IR. I couldn't find any symptom similar to what you describe.

Mark Pierson · Post by **Mark Pierson** » Mon Aug 16, 2004 12:59 pm

I'm not sure if this could cause the problems you describe, but are you using the latest set of RDF's for the 5.x version of IR?

mikea128 · Post by **mikea128** » Mon Aug 16, 2004 2:17 pm

I believe I have the latest RDF's, but I'll double check when I get home. I just downloaded them from Yahoo Groups a couple days ago, so it seems unlikely.

I definitely hit the hex radio button (and when I've forgotten, IR yells at me

). I don't actually get an error message, i just see that the keymove is not saved correctly and it doesn't work on my remote.

I'll play with it more tonight or tomorrow...

Mark Pierson · Post by **Mark Pierson** » Mon Aug 16, 2004 2:27 pm

What remote are you using? Is it a URC-6131 (which doesn't support 2-byte keymoves unless the extender is used, and IR displays erroneous hex codes for them) by any chance?

mikea128 · Post by **mikea128** » Tue Aug 17, 2004 11:10 am

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?

gfb107 · Post by **gfb107** » Tue Aug 17, 2004 11:11 am

The workaround is to install the extender.

mikea128 · Post by **mikea128** » Tue Aug 17, 2004 11:19 am

I knew that was coming and was just about to edit my post...so no other options?

mikea128 · Post by **mikea128** » Tue Aug 17, 2004 2:34 pm

OK, i've dealt with my Denon 2 byte code keymoves by using the built-in Denon code for the keymoves and that's an acceptable solution. I may get to the extender later...it scares me somehow and I don't want to spend too much time messing with this.

Anyway, I'm still having trouble with IR and hex code keymoves. It still doesn't save single byte keymoves if entered as hex for some reason. I just tried it on the 6131 with the built-in code for panasonic tv's (TV_250), entering hex $83 for discrete on gets saved with hex $36. If i enter the EFC (22), it saves as EFC 22 (with incorrect hex shown) but doesn't work when I actually use the remote. Ideas?

*UPDATE* - i just tried entering the above advanced code manually into the remote (ie setup 994 style) and the remote accepts it just fine and it works, but it appears in IR wrong. Note that it is in fact a 2 byte keymove (according to IR, even though I only put in a 3 digit EFC), so it would appear to me that the 6131 does in fact support 2byte keymoves?

johnsfine · Post by **johnsfine** » Tue Aug 17, 2004 2:50 pm

Most models store hex commands in KeyMoves: KeyMoves by EFC are translated to hex command before being stored. KeyMoves from keys defined by setup code have their hex commands looked up before being stored. KeyMoves defined by IR.EXE can be any hex command. They get their protocol and fixed data from the source setup code but don't need any keys defined in the source setup code.

In the 6131, keymoves are stored as either EFC (in hex, but that isn't the same thing as hex command) or keycode: Keymoves defined (on the remote) by EFC are stored that way and the EFC to hex command translation occurs when you use the key. Keymoves defined from other keys store the keycode, so it doesn't matter whether the hex command is one byte or many bytes.

So you can have the KeyMove of a multi-byte hex command, but only when it is the keycode type of keymove and the source setup code actually includes a key for the specific function you want.

I've never played with IR.EXE for the 6131, so I don't know if it gives you any way to define those KeyCode type KeyMoves.