JP1 Remotes

Yeah, that's probably what it is. They both came from Charter.

Thanks for replying, though.

I have two Scientific Atlanta UJ3EXP cable box remotes and I'm wondering if there's anything I can do with them JP1-wise.

They look very close to the Scientific Atlanta Explorer cable box remotes that have an RDF and limited support, but these do not have JP1 pins, nor a header.

I can't figure out ...

Just to follow up on this, I attempted to solder the larger EEPROM by running wires from the PCB to each pin and it worked beautifully. Thanks for the suggestion.

I'm by no means a soldering expert, but somehow I managed to get it on this one remote.

I'll keep an eye out for that stuff, though. Good tip, thanks.

Nope...never used flux. I'm curious, though. I'll have look into it.

Yeah, that's what it was. Somehow one of the pins on the 6-pin header came loose and was being pushed out when the JP1 cable was inserted. But it's fixed now.

Chalk it up to bad soldering, I guess, because it works great now. Thanks for putting up with me!

I'm not sure anyone's tried to solder the big chip in before, but now we can say it's been done.

I have a newly-acquired URC-6131n(w) remote that I'm trying to add JP1 to.

I soldered in the 6-pin JP1 header, and because I bought the wrong 24LC16 EEPROM (mentioned in a previous thread, where the conclusion was that if I could make it fit, it might work). I ran 5 wires from the PCB (pins 5-8 ...

I'm sure this question can be answered by simply trying it, but I thought I'd ask first:

I just bought a URC-6131nw from Wal-Mart and I was planning to put in an EEPROM and JP1 pins. I mistakenly ordered the part 579-24LC16B-I/P from mouser.com instead of 579-24LC16B-I/SN...the only difference that ...

It's the dumping part that intrigues me...if all you can do is get a dump of the EEPROM, how do you use the interface to get to its operating system?

I'm the incompetent one, since I don't understand the post. But, to answer your questions:

Yes, NEC1 is a device protocol. Something like 0047 is a device code.

If you are going to make your own device upgrade, then you have to make up a device code (it can be anything you want between 0000 and ...

The more I sit and think about extenders, the more it just amazes me, so I want to ask you guys...how did you find out all these ROM calls like LightOn and LightOff that these remotes use? Did you write a special protocol that blinks out the memory contents and you picked it apart or what? I guess ...

johnsfine wrote:Please do.

Done.
Thank you...your extender and all the documentation I've found scattered about are what allowed me to do this.

I just created an extender for a 1K EEPROM in the 6012 family of remotes which is based on the 3.2 extender. It works perfectly fine and in the same exact way as the 3.2 extender, the only difference being that it does not include the ToadTog, DSM, and pause protocols. (These could be added by ...

Just to get it to execute code, I removed all of the extender code and just put a RET at the end of the EEPROM (just before $400). The device and protocol to load it go in the new upgrade area, and the keymove to load it goes in the old keymove area. It couldn't be any simpler...I assemble it ...