7544 B01 RDF

dsarens · Post by **dsarens** » Mon Aug 22, 2005 1:50 pm

Rob,

I altered the NAME in the GENERAL section in your RDF so that I would be sure which RDF was being used.

I followed your instructions as above and the first two bytes have changed in the raw data.

Step 2 data first 32 bytes;

5E A1 4F 44 34 4C 4F 44 34 30 02 2C 10 51 23 4F
31 F7 00 00 0F 14 00 00 00 00 00 FF FF FF FF FF

Step 4 data first 32 bytes;

87 78 4F 44 34 4C 4F 44 34 30 02 2C 10 51 23 4F
31 F7 00 00 0F 14 00 00 00 0C 03 02 2C F8 00 FF

Step 7 data first 32 bytes;

5E A1 4F 44 34 4C 4F 44 34 30 02 2C 10 51 23 4F
31 F7 00 00 0F 14 00 00 00 0C 03 02 2C F8 00 FF

It appears that when I did the move on the remote it altered the first two bytes of the data (should it do that?), when I did the key move using IR, it reset them back to the state just after a 981.

I did it twice just to be sure!

Duncan

Post by **The Robman** » Mon Aug 22, 2005 1:57 pm

Sorry, that's my fault. I temporarily commented out the checksum area and must have forgot to set it back. In the RDF change [Checksums2] to [Checksums].

This still doesn't explain why you're getting the fixed data message and I'm not though.

dsarens · Post by **dsarens** » Mon Aug 22, 2005 2:23 pm

That's made it work! I've done a keymove and a basic device upgrade and they're both OK. I'll do a full program up of the remote and report back.

I notice you changed the AdvCodeAddr, EepromSize, FixedData and removed the SpecialProtocols. The [Checksums] was set as [Checksums2] in the OD4LOD40 (URC-7541_7544 1K European Version) original file. Did you have to change anything else?

Thanks very much,

Duncan

Post by **The Robman** » Mon Aug 22, 2005 2:41 pm

I didn't deliberately remove the Special protocols section, I must have been using an older version of the RDF.

dsarens · Post by **dsarens** » Mon Aug 22, 2005 4:02 pm

Just created a full device upgrade and it doesn't work properly. Some keys are OK, some in the wrong places and some just don't work.

It was created in RM 1.30. The upgrade is a NEC1, Dev 4, Sub 123 and the upgrade code is;

Upgrade code 0 = 27 cd (SAT/1997) TM5000CI (RM v1.30)
5a 17 36 fe ff 20 df 21
ff 7f af 8f a7 c7 ff 7f 3f bf 07 87 6f 0f fd bd
2f 5f 3d
End

I did an initialize to FF and a 981 reset and then did the upgrade and I have uploaded the IR file.

https://www.hifi-remote.com/forums/dload ... le_id=2092

Duncan

Post by **The Robman** » Mon Aug 22, 2005 4:57 pm

That's not unexpected. My RDF is a "Starter" RDF where all the info comes from the old RDF that I used as a starting point. My primary objective was to get you talking to your remote, which you weren't able to do before. Now you'll have to figure out (1) if the keycodes are correct for the buttons and (2) if the button maps are correct.

Start with the keycodes, create macros on the remote and then download the memory and validate that the correct buttons are displayed in the macro. If you find errors, correct them. Then, once that is complete, create an upgrade and load it, then see where the functions ended up.

dsarens · Post by **dsarens** » Tue Aug 23, 2005 4:36 am

Thanks Rob,

I checked all the keycodes are they're fine.

I made a new upgrade, this time using KM rather than RM, because RM also uses the RDF file and wasn't sure whether this would confuse things further.

First I made a simple upgrade, assigning 1, 2 & 3 to the corresponding buttons on the remote. This worked. I then made a full upgrade and every button works except all the number buttons. I then discovered if I removed any one of the numbers, the upgrade would work fully, except of course the removed number. I also noticed the upgrade code grew in size if a number button is removed.

I can only guess that the protcol has defined code for the number buttons and that my remote is not decoding it correctly, and by removing one number, each button has to be described individually, which my remote can handle. But it's only a guess. For info the Protocol is NEC1, using Dev 4, Sub Dev 123.

Duncan

Post by **The Robman** » Tue Aug 23, 2005 5:41 am

Each remote has a built-in table of number codes that are often used. Your number buttons obviously match a frequently used set. However, the table in your remote is different to the table in the B00 version, which is why KM used the wrong set. When you delete one of the number button codes (or use a different code), you no longer match the built-in codes so KM has to add all the codes for your number buttons to the upgrade.

Open up your RDF and look for the [DigitMaps] section and delete the contents, this will force RM to always generate your number codes.

dsarens · Post by **dsarens** » Tue Aug 23, 2005 7:15 am

Deleted the [DigitMaps] section in the RDF. Using RM the numbers now work, but some other functions are incorrect. When I earlier used KM, all the other functions were fine.

Also I have found that sometimes after doing keymoves, uploading to remote and downloading again causes the keymove/macro data to become corrupted. It isn't consisent though.

Duncan