I have an RC 5200 that just keeps beeping. The screen flickers on then back off. I cant load to it. I've tried resetting and nothing. Any and all suggestions are appreciated.

DZL1.

I've seen this happen when the battery has failed. To test try taking the battery out and running it on the docking station.

OK I tried that same thing. I guess I should have been more specific as to why I think this is happening. I was in the middle of a load and didn't notice that the battery was very low. Well the battery died in the middle of the load. Is it possible that the file somehow corrupted the remote? Is there anyway to reload the firmware? Please advise. Thanks.

DZL1.

Ok, easy problem to solve (relatively) read the FAQ here: [Link: remotecentral.com] and/or here: [Link: remotecentral.com].

When the first link says "reflash the firmware several times" it means that you have to catch the remote in the correct timing cycle. It could take a dozen times. Hyperterminal (second link) may be easier.

Good news is the remote is fine.

Thanks for the info. I'm going to try that now. Will keep you posted.

DZL1.

OK I did the hyperterminal method. Did steps 1-4 but nothing shows up on the hyperterminal window. Tried it several times. Any suggestions? Will keep trying. Thanks.

DZL1.

Maybe you set wrong baud rate?

I thought so too, but all settings are exactly like what the tutorial says.

DZL1.

You don't see anything at all with Hyperterminal connected and the remote rebooting?

The one catch is that, if I remember correctly, when you cancel a file update the remote usually shows the logo screen for a second and THEN reboots. The flickering screen and instant reboot I've only seen when the battery has failed. It could be that attempting to write to the memory at such low battery power ended up randomly corrupting something more important to the boot process.

I've never used hyperterminal so maybe I'm not using it right. But to answer your question, nothing shows up on the screen. I hope my remote didnt just become a paper weight.

DZL1.

You've got mail.

For some reason, I got the process written down where you load a ccf into the remote, not flash the firmware. This was a tiny bit finicky, but after I made it the process I use any time I run into this, I heard about the nearly the same process using a firmware update. But everyone noted that the timing has to be exactly right to use the firmware approach. So I've sent you the Word file that I created years ago to remind me how to fix this using a ccf.

Maybe I spoke too soon, but another method you can try involves Tonto. Tonto is 3rd party replacement software for ProntoEdit, and can be downloaded here: [Link: giantlaser.com]. After installation of the software (reboot the computer) run the program, choose your remote type and then select "undead remote" listed under "Remote" on the toolbar. Then, follow the on screen instructions. It usually works first time, every time. Exception would be Daniel's scenario.

"Undead" basically automates the exact Hyperterminal steps from the FAQ, but that may be a good thing. :-)

OK guys I will try and keep you posted.

DZL1.

I figured out how hyperterminal works. I get the 00 02 04 etc. I press esc, after the prompt i type dl ccf, then i transfer but then a box pops up and nothing happens. Then on the status box it will say cancelled and on sending box it will show the ccf i selected. Then after a while the status box will then say connection timed out. then that box closes and a different box pops up saying no response from remote system. Tried it many times with no luck.

DZL1.