Discrepancy between KM 8.26 and RM 1.04 (RM is wrong)

unclemiltie · Post by **unclemiltie** » Sun Aug 29, 2004 4:13 pm

for a Yamaha HTR-550 upgrade I've done in the past with KM, when I switched over to RM I found that it's not doing the keymoves correctly.

RM is settting them up as double-byte code, and the hex is wrong.

here's the output from KM (correct)

Upgrade Code 0 = 34 98 (Tuner/1176) Yamaha HTR-5500 AV Receiver (KM v8.26)
5A 00 F0 0E F4 73 00 A1 A1 00 EE 6E AE 2E CE 4E
8E 0E F6 A7 27 C7 F7 77 07 9E C6 DE E6 66 35 B5
96 16 E5 65 15
KeyMoves
3D F3 34 98 47«Discrete On» ¦3E F3 34 98 87«Di
screte Off» ¦95 F3 34 98 97«Tuner» ¦96 F3 34 98
D5«D-TV/CBL» ¦97 F3 34 98 7C«DVD» ¦99 F3 34 98
55«V-AUX» ¦9A F3 34 98 0F«VCR» ¦A1 F3 34 98 5E
«Test»
End

Here's the output from RM (not correct)

Upgrade code 0 = 34 98 (Tuner/1176) Yamaha HTR-5500 AV Receiver
5a 00 f0 0e f4 73 00 a1 a1
00 ee 6e ae 2e ce 4e 8e 0e f6 a7 27 c7 f7 77 07
9e c6 de e6 66 35 b5 96 16 e5 65 15
KeyMoves
95 f4 34 98 00 76«Tuner»¦
96 f4 34 98 00 64«D-TV/CBL»¦
97 f4 34 98 00 b1«DVD»¦
99 f4 34 98 00 68«V-AUX»¦
9a f4 34 98 00 3a«VCR»¦
a1 f4 34 98 00 c0«Test»¦
3d f4 34 98 00 f8«Discrete On»¦
3e f4 34 98 00 f6«Discrete Off»
End

I've posted two files, the RM and KM file to the diagnostic area for debugging. They're named

Yamaha HTR-5550-6113.txt
Yamaha HTR-5550-6131.rdmu

for now I've just fixed the keymoves in IR with the right codes and all is fine, but this one got me for a few hours trying to figure what happened.

Mark Pierson · Post by **Mark Pierson** » Sun Aug 29, 2004 5:21 pm

The KM file is setup to use the 6131 Extender while the RM file is using the regular 6131 which uses a new style 2-byte key move even for 1-byte commands. If you change RM to the 6131 extender, the upgrades match.

FYI, posting actual links to files uploaded for diagnosis makes it easier for those offering help to find them.

unclemiltie · Post by **unclemiltie** » Sun Aug 29, 2004 7:38 pm

Thanks mark, but why would those upgrades not work (ie: none of the shifted keys worked on the RM built upgrade) When I went in and edited the keymoves in IR to reflect the right single-byte hex codes, all was well. That's what got me looking back at the KM generated upgrade.

The remote IS an extended remote.

BTW, I was going to post links but after I uploaded the files, I found that they had spaces in them and didn't know how to deal with that in the link. sorry bout that.

pgk · Post by **pgk** » Mon Aug 30, 2004 2:31 am

To recap the RM file is creating keymoves for an Unextended remote, KM is creating them for the Extended remote.

The unextended 6131 remote uses a different format to keymoves than most of the other JP1 remotes, the extender "fixes" this but can not directly use the unextended keymoves. That's why the two are not compatible. As Mark suggests if you change the remote selected in RM to the extended remote it'll create the correct keymoves.

The readme file for the extender mentions this in the "Installation and Activation" section.

johnsfine · Post by **johnsfine** » Mon Aug 30, 2004 5:43 am

pgk wrote:To recap the RM file is creating keymoves for an Unextended remote, KM is creating them for the Extended remote.

I don't know how KM selects extender vs. non extender. Maybe it doesn't even support the 6131's non extender keymoves.

RM lets the user select an RDF file, then the RDF file tells RM how to do various things (KM doesn't use RDF files).

In most models the extender vs. non extender RDF file choice makes a big difference to IR.EXE but little difference to RM. For the 6131, the extender vs. non extender controls the format of keymoves.

Mark Pierson · Post by **Mark Pierson** » Mon Aug 30, 2004 6:30 am

unclemiltie wrote:BTW, I was going to post links but after I uploaded the files, I found that they had spaces in them and didn't know how to deal with that in the link.

Spaces have to be manually editied and replaced with "%20". I.e., "Yamaha HTR-5550-6113.txt" would become "Yamaha%20HTR-5550-6113.txt".