If you're interested, the Aiwa protocol uses 2 bytes of fixed data where the data is stored in LSB format, which means you read the binary from left to right.enliteneer wrote:Not sure how remotemaster corrupted the file, or how the data learned by the remote was so different/incomplete, but changing that bit did the trick!
All the legacy JP1 tools take the two bytes together to convert the data into decimal, so when there's non-zero data in the 2nd byte the tools give a device code greater than 255.
RM takes a different approach, it treats the 2nd byte as a sub-device, thus limiting the size of the main device code to 255 or lower.
This particular device uses a device code of 352, which yields a hex code of "06 80", however when RM opened the KM file, it didn't account for the fact that the device code was greater than 255 and thus didn't correctly calculate the 2nd byte, so you ended up with a hex code of "06 00".
I reported this as a bug yesterday here and Greg, the guy who wrote and maintains RM, posted a fix later in the day. So, if you download the latest version of RM (ie, 1.96) it should handle your upgrade correctly.