Preventing Auto Shutdown During Large Updates

[Radaway]

this happens during upgrading, especially when there are large updates? For example, when I receive updates for the European buildings and similar data( 7 megs > ), the process can take more than an hour on the hardware like 5100/6100 etc . Simply leaving the unit on the table to update is fine, but after some time, the unit automatically switches off(or goes on blink !, assuming there is no activity. This typically happens after about 15–20 minutes of inactivity (I think).

When you return, you often find that the update hasn't completed correctly, and there are messages that need to be acknowledged. You then have to ''wake'' the system up again, and this cycle repeats itself. This issue mostly occurs with lengthy updates, which, fortunately, do not happen frequently. However, the unit should be *intelligent enough* to recognize that an update is in progress and, as long as the update continues, it should not switch itself off or go into standby mode.

I'm not sure if there's an existing setting to prevent this, but it's definitely something that others may have encountered as well.?

 

[canderson]

I just updated my old 600 this morning.
Took a long while as it was a full N.A. map update.
MOST of the time, it's the PC (especially notebooks) that shut down the USB port when going into a 'power saving' mode that causes the interruption. The power to the computer's USB port gets shut down, and the device connected to it, seeing no power, then goes into some kind of sleep/hibernation of its own (like a TomTom!) Unfortunately, the computer isn't smart enough to realize that lack of 'participation' by the user doesn't mean nothing useful is happening!

Generally, it's necessary to go into the power management settings of the computer to prevent this. Even my desktop has a setting for this, and I keep it disabled! If I don't, the TomTom would eventually lose power from its USB port on my computer.

 

[Radaway]

Great !...I did not know this - one of those --many of windows' quirky def. settings that many a users don't know about.
well now that it's done , lets wait for the next big update <glee>
thanks !

 

[John Daniels]

My 6000 does this during every map update (always more than an hour), despite the laptop being on and active all the time - I just watched the device screen go blank during the update. If the device is on and does not move after 30 minutes it comes up with an inactivity warning which you must acknowledge, but it does show this during an update and simply turns off (or more likely hibernates). During the recent map update it ended up corrupting the map giving me all sorts of problems.

 

[Radaway]

<it ended up corrupting the map giving me all sorts of problems.>
I get it too, stuff like: no maps available etc !! - in the middle of an ongoing update
just make the connection ''awake'' again ( take cable in , cable out , if rqd. from both ends [PC & TT] ...reset the Unit till u hear those ''drum beats'') and TT rolls back and does it again from where it 'stopped'.
at least that's the workard. I go for. ....takes some time( & deep breath) , but those horrid messages then disappear automatically and screen shows that rotating circle again, suggesting : we are on Line.

I'm also curious on Canderson's post above (Thx. Sir!), it makes sense completely & now just waiting for the next on-field test !

patience may be the key here ...@ least what I've learned from the whole Regimen

*PS: what I've noticed , TT is very good in ''rollbacks'' & carrying on frm. that last suspended snapshot. I've wrkd. with many a software in my life & their's, is there right on the top-shelf, regarding this hiccup.