7544 B01 RDF

[dsarens]

I've just acquired a 7544 B01, added a JP1 and 2K EEPROM and I am having problems with the RDF. I've tried one from the latest RDF Zip file (OD4LOD40 URC-7541_7544 1K European Version) which I edited to default to a 2K EEPROM but I can't get the remote to work with any device upgrades. It sometimes remembers the setup codes entered in IR.

I know other users have made some progress with a 7544, but I think my remote has a different suffix (B01) and requires a different RDF. Maybe the existing RDF needs altering slightly - I did see a guide on this forum on creating RDFs, but I can't find it now.

I've uploaded the raw data file successfully performing a 981 reset and then programming these codes; TV=0093, VCR=0037, SAT=1111 & DVD=0591.

Any help will be much appreciated.

Thanks,

Duncan

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

[dsarens]

Looking in to this further, it appears that IR will only show internal set-up codes correctly - any devices I've attempted to add are scrambled. I think it might be that the RDF is pointing to the wrong areas of memory because key moves I've done on the remote itself are showing as garbled macro moves in IR. Could it be that some of the following settings in the RDF need altering?

[General]
Name=URC-7541/7544 One For All 4 Digital - 2K European Version
OldRemoteID=22,22
EepromSize=$800
AdvCodeAddr=$01B..$0FF
UpgradeAddr=$100..$7fd
Processor=S3C80
RAMAddr=$FF00

Any thoughts anyone??

[dsarens]

Slight progress. I altered;

AdvCodeAddr=$01B..$0FF to AdvCodeAddr=$019..$0FF

and now IR will correctly read key moves made on the remote, but I can't program moves on IR and upload them to the remote.

Also, I think the protocols section probably needs upgrading because the 7544 supports the Nokia 32 protocol (using setup code SAT 1111) which my 7541 doesn't.

But I'm just fiddling, I really need expert help!

[dsarens]

To any one who is looking at this file, I'm not sure that IR was in raw mode, ie I may have had an experimental RDF in the way. I've downloaded another file, this time I deleted the RDF, initialized the EEPROM to 00, did a 981 reset and then programmed the codes. I'm not sure if this is the correct procedure, if not please let me know and I'll do it again.

Thanks,

Duncan


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

[The Robman]

Typically, you want to initialize to all FFs before doing a 981 reset as the remote uses zero bytes to indicate the end of sections. The reason we added the 00 initialize was for the URC-9960B01 which uses FFs for end of sections.

[dsarens]

Thanks Rob.

I've initialized to FF, done a 981 reset and then entered the codes as you suggested and uploaded the new file.

Duncan

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

[The Robman]

Load the FFs file into the remote, then do one keymove and learn one button and save the new file.

[dsarens]

Loaded FF file to remote and did 1 keymove. Remote does not have a learn function.

Thanks,

Duncan

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

[The Robman]

Can you verify if the remote accepts the 975 learn command. The reason I ask is because the original file that you posted contains some partially deleted learned signals. Even if your remote doesn't have the learning hardware, I need to know if the firmware supports learning (I suspect that it doesnt) as it determines whether I can let the upgrade area use the 2nd half of the E2 memory.

In the meantime, here's my current RDF for it....
https://www.hifi-remote.com/forums/dload ... le_id=2087

[dsarens]

The 7544 doesn't accept the 975 learn command. I tried the RDF you've made, but it won't accept a device upgrade (made with RM using the same RDF) and it also won't work with key moves made in IR. It does show key moves made on the remote itself.

Also, IR says there is a fixed data conflict at address 0015.

Regards,

Duncan

[The Robman]

I adusted the RDF to use the correct fixed data and I don't get an error message when I open your IR files, which leads me to believe that you're not really using my RDF. Can you make sure that you saved it as an *.rdf file and not a *.rdf.txt file.

[dsarens]

Rob,

I've double checked the RDF and I was using yours.

If I make any changes on the remote (setup codes or key moves) it works fine. If you do the same from IR and upload it to the remote, the remote always ignores it.

I did a key move on the remote, which worked, examined the raw data and saw the following six bytes starting at 19h - 0c 03 02 2c f8 00. I then initilazed to FF, 981 reset and then programmed the move using IR, uploaded to the remote and downloaded again and the data was identical, but the keymove didn't work.

The fixed data also shows as 14h at address 15h, as per your RDF, but the message about fixed data still comes up.

Could it be there is some sort of offset in the data between read and write?

Duncan

[underquark]

...which I edited to default to a 2K EEPROM...

There already appears to be a .RDF for a European, 2k EEPROM. Does IT work?

[dsarens]

underquark,

No, I've tried it. My remote has a B01 chipset. I assume the RDF was written for the B00 version.

[The Robman]

Did you close IR after saving my RDF? In order to force IR to use a new RDF you have to either (a) close and restart IR or (b) open a file for a completely different remote and then re-open your file or download from your remote.

Regarding the fixed data, when I open the files that you posted using my RDF I don't get a warning message, so the fact that you do get the message tells me that you cannot be using my RDF.

Once you do start using my RDF, if you still have the same problem with keymoves, try this...

1) Load the remote will FFs and do a 981 reset.
2) Download and save the file.
3) Program a keymove on the remote.
4) Download and save the file.
5) Open the file from #2 above.
6) Type programming the keymove using IR.
7) Save the file.
8) Compare the file from #4 with the file from #7, let us know what the difference is.