URC 6131 (walmart) shows wrong device codes

[ellobob13]

This is about as basic as you can get. But I got my eeprom and JP1 connector and soldered them in (and resoldered,,,). After a while I got the eeprom reset to flash 4 times repeatedly and after re-soldering my JP1 connector I got IR to upload from the device.

It is recognized as PVR0PVR0 although IT says I have more eemprom than the the rdf says.

I set all my device keys then uploaded to remote then went to test - nothing worked. I downloaded to my computer and those codes were indeed set.

I use SET to program these codes and all works fine but IR seems to read device codes incorrectly. I reprogrammed the TV code to a different TV but IR still sees the original code (the one I set through IR).

Please help.
Richard

[ellobob13]

This now seems to be working as expected. I just added to key moves via long setup 994 and the download is working.

Sorry to bother
Richard

[johnsfine]

1) If you don't do a 981 reset after adding the eeprom, the remote may still think it doesn't have an eeprom and store info elsewhere. That should be the only way it is possible to change setup code selection on the remote and see the old values in IR.

But it sounds like at some point the remote figured out it had an eeprom, or the KeyMoves wouldn't download either.

2) If you have an RDF file for the wrong eeprom size it may also be wrong about fixed data and checksum, which would cause problems on future uploads.

3) Your symptoms partially fit the symptoms you would get if there were a problem in the reset signal in the JP1 cable or JP1 connector. If that were totally broken, the remote would see KeyMoves and upgrades loaded by IR.EXE but not setup code and misc. (VPT etc.) changes.

If you think reset is broken and can't fix it, you can make uploads work by: After each upload remove a battery, press a key, then replace the battery.

[ellobob13]

Well I am back to having problems.

All went well I even added an upgrade file I had downloaded and it worked. Some keys were missing so I added them and uploaded that to the remote. Now the upgrade does not work at all. it is though the device code had changed.

I just pulled out a battery and pressed a button. Now the remote is working.

Which pin on the JP1 connector is the reset. How can I debug it?

Thanks
Richard

[ellobob13]

I have done some more reading and have more information.

After the download the red LED on my remote does blink twice.

I can use the remote while the JP1 cable is plugged in.

If I unplug the cable I do not see the led blink.

This it all seems OK BUT the device codes do not get set correctly unless I do it manually or pull a battery out.

Doe anyone have a suggestion?

Thanks
Richard

[johnsfine]

After the download the red LED on my remote does blink twice.

So the JP1 RESET signal is perfect end to end. We can stop considering that as a possible cause of problems.

This it all seems OK BUT the device codes do not get set correctly unless I do it manually or pull a battery out.

Does pulling a battery out actually help anything? I can't understand how. That only should help if there were a problem in RESET, which there isn't.

Reprogramming a setup code manually on the remote itself, would help if there is something wrong with the RDF file (the specified checksum range is a good, but not only, possbility).

A long-shot theory for why pulling the battery might help would be there is some sort of load (partial short) on the SDA or SCL signals so that when the remote resets while connected to the PC, it decides it has no EEPROM.

You should be able to test for that by trying to use some KeyMove or Upgrade stored in EEPROM while the remote is still connected. Then hopefully some hardware expert might guess what should be checked to track down the hardware problem.


Hopefully another expert who knows more about 6131's can jump in here and figure this out.