PID $005E: Aiwa protocol - RM bug

Post by **The Robman** » Wed Sep 02, 2009 1:47 pm

As found here:
https://www.hifi-remote.com/forums/viewt ... 9469#p79469

If a KM that upgrade uses the Aiwa protocol with a device code > 255 is imported into RM, the 2nd byte of fixed data is not populated correctly.

RM treats the Aiwa fixed data as two device codes, whereas legacy JP1 tools have always treated it as one device code, that can be greater than 255.

I don't know how to code this in protocols.ini, but there should be something there that traps when the user enters a single device code that's greater than 255 and then uses the overflow data to populate the 2nd fixed byte. (ie, divide the number entered by 256, discard the remainder and treat the result as the RM sub-device code).

gfb107 · Post by **gfb107** » Wed Sep 02, 2009 3:02 pm

Looking into this now.

gfb107 · Post by **gfb107** » Wed Sep 02, 2009 8:43 pm

Fixed in RM v1.96

Post by **The Robman** » Wed Sep 02, 2009 9:57 pm

Wow, talk about quick service, thanks Greg.