Did I kill my remote?

Bluesman · Post by **Bluesman** » Sat Oct 28, 2006 9:26 am

I tried to update my URC-7780 with a sound file created with IR70beta2. The update failed and I laid the remote aside and checked the settings in IR. As I took the remote again and pressed a key, the background light went on and the power-led started to flash rapidly. No response to key pressings including the magic-key.

Battery removal and reinsertion brought no change. As soon as I put the batteries in the background light goes on and the power-led starts flashing.

I built a JP1 interface, hoping that I could reset the remote this way, but the remote is not recognized.

Any suggestions? Or did I really kill my remote just by sound?

Post by **The Robman** » Sat Oct 28, 2006 1:26 pm

It sounds like you managed to load a bad executor into the remote (ie, probably one designed for a different remote) and this is confusing the remote. Another possibility is that you have set a fixed byte incorrectly, which would also confuse the remote. Either way, this is just bad data which can (in theory) be fixed with good data loaded into the EEPROM.

Without JP1, you would want to find a way to do a 981 MFR RESET.

If you had used JP1 from the start, you would likely have saved a copy of the EEPROM image before you made any changes and you could use this to restore the remote, but of course, that's not the case here.

If your remote is not recognized by JP1, it means that we haven't seen it before and are unlikely to have a clean image for you. Therefore, the best I can suggest is that you re-initialize the memory to add FF's and then see if the remote will let you do a 981 reset. If it does, download and save this memory image so you can use it to restore the remote in the future.

To init the remote, in IR.exe, select Advanced > Initialize to $FF

binky123 · Post by **binky123** » Sat Oct 28, 2006 2:20 pm

The URC-7780 Stealth 12 is a JP1.2 remote.

Post by **The Robman** » Sat Oct 28, 2006 4:07 pm

In that case, it will probably need expert help to get it running again, unless you can get it to let you do a 981 reset.

zaphod7501 · Post by **zaphod7501** » Sat Oct 28, 2006 5:05 pm

Here is an idea based on no specific knowledge of your remote, but:
A lot of consumer electronic devices will go into setup or reset modes by holding one or more buttons down as power is applied. You might try holding down the setup button (magic?) as you install the batteries. You can try miscellaneous buttons and of course make sure that one of the buttons isn't already stuck or jammed down.

Bluesman · Post by **Bluesman** » Sat Nov 04, 2006 8:30 am

Got it working again.

I bought the JP1.2 Interface-Cable from www.diygadget.com (very fast oversea delivery, by the way) and did an Initialization to $FF. Now it works again.

Thx for your suggestions.

czo · Post by **czo** » Thu Nov 23, 2006 4:34 pm

haaaaaaaaaaa, mine is locked too......

I'll build a JP1.2 cable and try to reset it.... Hope it will work...

Did you try other upgrades with your cable? Does it work? Is the urc7780.rdf bad????

Olivier.

Bluesman · Post by **Bluesman** » Fri Nov 24, 2006 10:56 am

czo wrote: haaaaaaaaaaa, mine is locked too......

I'll build a JP1.2 cable and try to reset it.... Hope it will work...

Good luck! Chances are good: I reset mine a few times now, using the cable.

OneForAll-Support told me, that if you update the remote via wav-file, you also have to include all previous updates you made in the soundfile, too. Otherwise the remote will hang up, the way mine did. If that's true, one can do one or two updates only, depending on how large the first update was and then never add additional updates again. I wonder, what people without cable shall do then. Send the remote to OneForAll each time they get a new device that's not in the remotes database?

czo wrote: Did you try other upgrades with your cable? Does it work? Is the urc7780.rdf bad????

I tried, but didn't manage to do an working upgrade so far. Don't know, if the rdf is bad, or if I'm doing something wrong.