JP1 Remotes

Having problem with a URC6011 upgraded at OFA. So I take it is the 1K version. In fact if I try with anything but the 1k RDF IR complains and will not work with the wrong RDF. This is a log of what I did and what happened.

When first connected with JP1 cable and after opening IR, download from remote. Profile saved to file call urc6011.ir and its associated urc6011.txt file.

Both batteries in.

Reset remote with setup-9-8-1. 4 blinks on remote.

From IR- Check interface. Report OK.

From IR - Advanced-Clean upper memory.

From IR - Advanced-Purge memory.

From IR - Download from Remote get error message "Bad checksum at address $000. Expected $C7 $38, but found $38 $C7". Clicked OK

Open saved IR file by file-open. IR window title give name of the file followed by "URC-881x/801x/601x - 1k Version"

Upload to remote. 2 blink on the red dot, lower left hand corner of IR window. 1 long blink on the remote. (something is not communicating right).

The remote will not operated the devices.

Set up the remote using factory default code for TV only. The remote will operate the TV but none of the other device whose codes are described by URC6011.IR uploaded via IR.

Download from the Remote. IR shows the TV with code as described by URC6011.IR and uploaded earlier on but not as setup using the factory default code.

Is this a hardware or softeware problem?
Is it CPU not reading from the EEPROM? How to rectify if so?
Does the error message says anything and if so, how to fix the cause of the error? Will it get the CPU to talk to the EEPROM properly

I have gone through the forum and this problem was reported by at least two others.

Tak,

This sounds very similar to a problem which came up elsewhere (reference below)

In summary the issue is normally that the RDF file is specifying the area used in the eeprom to be slightly different than the remote actually uses.
(Hence when calculating the checksum IR is computing a different value to the remote, similarly when you upload the checksum is incorrect and so the remote doesn't like it)

To resolve this, quoting from this thread (Look at the first post describing the problem and the last couple of posts describing the fix, ignore my posts which were of no use to anyone)

Re-do a 981 reset on the remote, and then try editing the RDF until you can download without the checksum error. Currently, the RDF section controlling this reads Change the $3FF value one address lower each time: $3FE, $3FD, etc. Usually it's only off by a few addresses, so if you don't get success after a dozen tries, then it's not going to fix it. In that case, you'll probably have to post the IR file (with no RDF active) for someone to look at.

It worked after modifying (repairing) the rdf.

So to summarise:
Error message "Bad checksum at address $000. Expected ....., but found ........" cannot be ignored.

To resolve it the rdf has to be modified.
1. Save a copy of 6_806_80(URC-881x_801x_601x 1k). rdf as backup.
2. Edit the rdf with a text editor e.g. Notepad. Change the checksums as:

pgk wrote:editing the RDF until you can download without the checksum error. Currently, the RDF section controlling this reads

Code: Select all

[Checksums] 
^$000:$002..$3FF 

Change the $3FF value one address lower each time: $3FE, $3FD, etc. Usually it's only off by a few addresses, so if you don't get success after a dozen tries, then it's not going to fix it. In that case, you'll probably have to post the IR file (with no RDF active) for someone to look at.

3.Open IR and tell it to get the rdf by file-new-select-the modified(repaired) rdf. This avoids any cached incorrect version.
4. Download from remote.
5. If "Bad checksum" error appears repeat step 2 to 4 until no error message appear.
6. Proceed to do upgrade or device assignment change etc. for upload to remote. Otherwise the upload will be ignored.

Last question particularly for the experts. Should I put the modified rdf in the file area?

It seems the 6_806_80(URC-881x_801x_601x 1k). rdf works for URC881x but is slightly off for URC6011.
Having the more accurate, but 1 byte different, rdf modified (repaired) for URC601x will avoid getting bad checksums.

Tak