TomTom One 140 can't find satellites

The One 140 updated immediately when I got it, to 9.541. The One is still at 8.010 and the One 3rd ed. is 8.016 and neither have been offered any other application updates from TomTom Home.
 
Nope - the 8.010 and 8.016 versions aren't going to cut it. The formatting of the date/time by the satellites would cause what amounts to an overflow condition, and current time is CRITICAL to knowing where the satellites are and getting a position lock.

I don't remember (it's been 6+ years) whether the original ONE and ONE 3rd were provided WNRO updates or not. Many models, but not all, were updated, some even after the 'event' occurred in April 2019, and some built later already had the code issues sorted before it happened. I have no record of 9.xxx code for either model.
 
Well ... that explains all the issues I've had with satellite connectivity on those units. Is there a way to force a firmware update that isn't offered? Or will that just cause more problems than it solves.
 
Well ... that explains all the issues I've had with satellite connectivity on those units. Is there a way to force a firmware update that isn't offered? Or will that just cause more problems than it solves.
There are literally dozens and dozens of different firmware builds for the older devices, and they're not cross-compatible. Each build takes into account the specific hardware and features of a given model. If there isn't a build to solve the WRNO problem for a particular old TT model, then nothing can be done about that.
 
Yes, that makes sense. Thanks for all your help.
 
Is it safe to say that the applications that are compatible with/solve the WNRO issue are all 9.XXX or later?
 
Normally, unless I'm mistaken, version 9.541 should be compatible with your device.

What you need to do is make a complete backup of your GPS.
Then delete the navcore from both your GPS and your computer.
Then introduce your GPS to TomTom Home.
 
Is it safe to say that the applications that are compatible with/solve the WNRO issue are all 9.XXX or later?
No, it is not safe to assume that.

For example, 7.834 = Toyota TNS400, Eclipse AVN2210p and 2227p

8.843 was a fix for several of the standalone units.

9.501 solved it for the Rider 2013 model.

All of the various 9.541 builds did seem to cover most of the rest of the models receiving updates, however. Understand that there were many different builds of the 9.541 code. They varied based upon the target device, and hence, are NOT interchangeable.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Staff online

Members online

Latest resources

Forum statistics

Threads
30,046
Messages
205,406
Members
69,607
Latest member
MikeTMechanic

Latest Threads

Back
Top