Factory Upgraded 6011 Problems

[schwarwp]

I have a 6011 with a factory upgraded/installed JP1 connector and a 1K EEPROM. I am having no luck reprogramming the device using the JP1 cable I built.

The "check interface" works.

It seems like I can write to the EEPROM and then read the data back properly, however when I use CODE 990 my recently uploaded configuration is never recognized.

I get a single blink after uploading a program change but I have never gotten the "double blink" described in other threeads.

Is there a reset sequence to load the EEPROM into the remotes main memory?

Do I have to run and extender or something like that?

Any help would be appreciated.

Paul S,

[johnsfine]

I have a 6011 with a factory upgraded/installed JP1 connector and a 1K EEPROM.

...

I get a single blink after uploading a program change but I have never gotten the "double blink" described in other threeads.

I assume you mean a long blink instead of the double blink. If it were a single short blink I have no idea what that means.

A long blink means the remote's CPU failed to communicate with the eeprom.

No blink at all means the remote's CPU wasn't reset.

Is there a reset sequence to load the EEPROM into the remotes main memory?

If the remote's CPU wasn't reset (which is a moderately common JP1 symptom) then after uploading with IR.EXE you should remove a battery, press a key while the battery is out, then replace the battery. That will reset the CPU.

[schwarwp]

I get one blink a few seconds after writing to the EEPROM. I don't considor the blink to be long, could you define a long blink?

I think I am writing to the EEPROM. I can (try to) define a new device code, write it to the remote. Close IR.exe, re-open IR.exe then read the remote's configuration and the device I've just defined shows up.

When enter the new setup code for the device I've just defined I get the "one long blink" for device not found.

I really think my cable is working properly.

It seems like I am writing to a section of the EEPROM that the remote never looks at.

I have tried taking the batteries out and pressing a button, that does not have an effect.

Do I need to use and Extender to do what I want to do?

[johnsfine]

I get one blink a few seconds after writing to the EEPROM. I don't considor the blink to be long, could you define a long blink?

By "long blink" I meant the same length you got for "device not found".

I really think my cable is working properly.

Yes it is. That much was clear from your earlier post.
The question is why the remote doesn't read the setup data from the eeprom.

It seems like I am writing to a section of the EEPROM that the remote never looks at.

Only the RDFs for 4K and larger eeproms have any choice about where the setup data is located. The RDFs for 1K and 2K eeproms put the setup data in the place where the remote would read it from a 1K or 2K eeprom.

I have tried taking the batteries out and pressing a button, that does not have an effect.

I don't even remember what sort of blink pattern you're supposed to get when you put the batteries back. But tell us anyway what you do get. Maybe someone with a healthy remote will remember or retest.

Do I need to use and Extender to do what I want to do?

You can't use an extender. There is no version of the extender for a 1K eeprom. It wouldn't help this problem anyway.

The next theory I have about the cause is that you're using the wrong RDF file. You need the RDF file for a 601x/801x/881x that has a 1K eeprom. If you used one for a different eeprom size that would explain the symptoms.

Hopefully you have the right RDF in your RDF folder.

Another test to try is to do a 981 reset on the remote (that also has a blink pattern which would tell us something if someone remembers what it's supposed to be). After the 981 reset do a download with IR.EXE. IR at that point should either auto select the right RDF or complain that it isn't there. Examining the resulting eeprom image should make it obvious whether the 981 reset worked (if it didn't then it must be a hardware problem in the connection between the remote's CPU and eeprom).

[schwarwp]

Yes, I do get a long blink after writing to the remote.

I have tried two RDF's one is "881x/801x/601x - 1K version" the other is "881x/801x/601x" the 1K version does not give me any error messages except on the initial download which as "bad checksum at $E000 expected $10 $EF found $EF $10. After Uploading one time I never get any additional error messages. All other 601x RDF's seem to work worse.

When I do a 981 I get two short blinks, twice.

How do I find or make the correct RFD?

[mr_d_p_gumby]

How do I find or make the correct RFD?

After the 981 reset do a download with IR.EXE. IR at that point should either auto select the right RDF or complain that it isn't there.

[johnsfine]

"bad checksum at $E000 expected $10 $EF found $EF $10.

That usually means the length of the checksum area specified by the RDF is off by one. I may be too busy to check for several days. I hope some other expert checks that.

When I do a 981 I get two short blinks, twice.

That means the CPU can read and write the eeprom correctly, so it pretty much rules out and hardware problem in the remote.

[schwarwp]

Are there any documents or tips on how to modify/create rdf files?

[scottf]

This sounds way too familiar... Was there a solution for this?

I have a 8810 and a 6011... the 8810 works great with my jp1 cable, but the 6011 gives me the same (or very similar) error to the above error.

[billt]

I am having this EXACT same problem. Was there ever any resolution to this?

[The Robman]

Every so often, when I am testing some URC-6131 remotes that I have just modified, I get something like this. Some of the time I can fix it be re-soldering either the 6-pin or the EEPROM, but occassionally, I get a remote that just won't communicate with the JP1 cable. Typically though, these remotes will reset using the 981 command. It's generally not worth me spending alot of time on it, so I just throw them on the junk pile.