Recently upgraded to the 9200 from the 5000 but having a few problems.

Been downloading fine but the 9200 had a funny turn and went into the beep cycle. Had a look through these forums and it seems it is a well known 'feature' so I either need to update the firmware or undead it through Tonto.

As I am using Tonto to design the pages, I tried the undead function. After a couple of goes, it went :
2% (Press RESET on remote) - I did nothing and left it as it was already in a rest cycle (as I understand),
15% (Looking for CABERNET) and this is as far as the progress bar gets. I have left it looking for up to 20 minutes but still no joy.

One other point to mention is that when I first got the progress bar going (can't remember how far it got), the battery on my laptop died mid update/undead. Don't know if this would have messed it up even further?

Last point is that I am using a mac with a keyspan serial adapter with Tonto - saw some cabernet threads about hyperterminal etc but I don't have a PC to try this method. A little concerned now as most threads I have read say that the Tonto undead function is pretty succesful but I can only get as far as the 'looking for CABERNET' message.

I know it is a long shot but any experts give me any pointers?

Thanks all

simon

I'm not real sure about exactly what's going on from your description but .....


The beep cycle, aka a constant reboot loop, can happen with any Pronto model. There are only a few possible causes, one of which you mention below.


I'm confused. Why would you undead it if it wasn't in a reboot loop, and why would you not follow the on screen instuctions? I.e. - press reset when you're told to?


Now here's a clue. An interupted (or canceled) download is the main (only??) cause for a reboot loop. This is the reason to use "undead" in Tonto.


I'm not a Mac or laptop user, but you need to follow the instuctions (press reset, have your ccf open in Tonto) when you use "undead"

Since you've been able to communicate with the remote previously, the adapter isn't the problem and undead should solve the reboot loop if you follow the instructions.

Jim L

Thanks for that Bomber Jim.

Just in case it helps anyone else, I left the batteries overnight and I managed to get it working. I guess the only thing which I may have done different was to have my CCF open when using the undead function.

Just in case it was a problem with my CCF, I created a very simple one page CCF from scratch to download and it worked perfectly. I then tried to reload my old CCF and it messed up my remote again!! Had to go through the undead process again and began a new CCF from scratch (just in case). Obviously, I'll be taking a lot of the design elements from the old CCF and hopefully, it won't bring over any of the bugs aswell.

Thanks again

It may behoove you to remove devices/macrogroups one-by-one until to help isolate which one is causing problems.

The other thing you might want to do is to download CCFTools and use the CCFDumper on your CCF as an insight into what's in there.

Lyndel

I thought about that but didn't want to go through the panic of permanently buggering up the device every time I downloaded another CCF!


Does this work on a Mac? I programmed my last remote using Softwindows and Pronto edit - it was a very hit and miss affair getting it all to work. I use Tonto now on the 9200 and it is so much easier to use and I don't have to go near any PC emulators.

Thanks again

You isolate the problem in your CCF by testing on the device, fix the CCF, then... No More Issue.

You may have the same problem down the road if the problem is something that Tonto may be doing to corrupt the file. Ensure that you are using the latest release of Tonto. I'm also curious as to whether the CCF will run in the emulator. Ooops, I forgot you are on a Mac. If you want to ship me a zipped version of your corrupt CCF, I'll test in the emulator and report back. Email is on profile.


No it does not.

Lyndel