Results 11 to 20 of 641
-
7th April 2019, 02:14 PM #11
My report:
Go 950 with 9.541 not a single problem, time correct
Rider v2 start at at 09:30 local time with 00:30 H with Navcore 9.500, hard reset time set to 09:30 H hard reset time 09:31
TomTom One Third edition Navcore 9.541 no time displayed, while I want to adjust the clock manual, it displayed 18:32 H more or less the local time at Australia
after a hard reset still no time availble on the screen while the setting are correct to display all the times available, now trying to receive any satellite
Rider v2, I've made a route to Hoek van Holland, after receiving signals, distance and the time to get there are correct, start a demo, start time demo at 09:43 arrivel time will be 10:22
TomTom One XL 9.541, start with the information screen with for me a strange sound which is very similar to the next patient at the family doctor, the time is indicated correctly
Calculate the time to Hoek van Holland 42 minutes which is more or less the same as from the Rider v2
The strange sound I think I've made a mistake when copying the files, I'll put back the normal drumroll.
While my Rider v2 is halfway, the route is OK and the time the same, my TomTom One third edition refuse to receive any satellite.
My Rider v2 has completed the ride and arrived at the destination as indicated at the correct time, I do not expect any further problems
While the One XL and the One third version are still searching for a satellite signal, I think that they will respond exactly the same and it all
comes down to the fact that the time must have some time to recover from the shock, just like many owners of the various TomTom'sLast edited by pe1agp; 7th April 2019 at 02:31 PM.
-
The Following 3 Users Say Thank You to pe1agp For This Useful Post:
- [ Click To Expand ]
-
4Wheel (7th April 2019), Momatz (12th April 2019), Nando Rola (7th May 2019)
-
7th April 2019, 02:43 PM #12
To find satellite position is not the problem for my ONE3rd (9.541) and the Go920 (9.702). But keeping the time permanently. After a hard reset, the time is only a few minutes okay, then it is changed back to 00.00.
-
The Following 3 Users Say Thank You to Alfred_ML For This Useful Post:
- [ Click To Expand ]
-
-
7th April 2019, 02:49 PM #13
XXL 9.541.
When syncing, the time was set to GMT instead of BST.
Soft reset followed by re-sync solved problem.Last edited by srwpchelp; 9th April 2019 at 12:54 AM.
-
The Following 2 Users Say Thank You to srwpchelp For This Useful Post:
- [ Click To Expand ]
-
-
7th April 2019, 02:51 PM #14
GO Live 950
9.058 / 1025.9386 no issues (10:52, GMT +2).Last edited by Poteo_Roke; 7th April 2019 at 03:42 PM.
-
The Following 3 Users Say Thank You to Poteo_Roke For This Useful Post:
- [ Click To Expand ]
-
-
7th April 2019, 02:55 PM #15
I'll later this day to start the tests once more Alfred_ML, to be sure all wil be OK for the next journey.
-
The Following 1 Users Say Thank You to pe1agp For This Useful Post:
- [ Click To Expand ]
-
4Wheel (7th April 2019)
-
7th April 2019, 03:45 PM #16
Go 750 Live (serial #W4..) with NC 9.541: no issues
One New/Second Edition (serial #Z3..) with NC 9.541 (_Go files, x50 emu) or NC 9.500 (rider5 emu):
navigation: no issues
travel time: no issues
current time: always 00:00
arrival time: 00:00 + travel time (useless)
There are rumours, that TT will update NC for Rider, Rider 2 and Urban to fix the WNRO-bug.
Rider owners pls register your email at
Pls. let me know, if you get the URL of the original NC from TT
I recommend these NCs:
Last edited by BMWdriver; 7th April 2019 at 10:47 PM. Reason: added important informations
-
The Following 2 Users Say Thank You to BMWdriver For This Useful Post:
- [ Click To Expand ]
-
-
7th April 2019, 03:51 PM #17
550 Live and 940 both with orig/official 9.541 and ONE XL with orig/official 8.010:- no noticeable differences (yet):- all 3 picked up satellite signals within around 1 min as usual, clock holds correct time/route planning shows correct eta, hard reset doesn't put time back to 00.00
SPAM HUNTER/KILLER
Please do not just post "thanks" but use the "thanks" button bottom/right or the reputation star "*" bottom/leftS i m p l e s
-
The Following 3 Users Say Thank You to biggerdave For This Useful Post:
- [ Click To Expand ]
-
4Wheel (7th April 2019), Alfred_ML (8th April 2019), steve98244 (8th April 2019)
-
7th April 2019, 03:53 PM #18
Lucky you! Go920 with 9.702 now OK after setting time "per hand". But ONE3rd with 9.541 is losing the time within a minute after satellite recognition, no matter if synchronization or setting by hand. Switch off/on, time is correct again for less than one minute. What a crap ...
But the little one is only for my american iron, for biker the way is the target! We don't need a time, we have it!Last edited by Alfred_ML; 7th April 2019 at 04:06 PM.
-
The Following 3 Users Say Thank You to Alfred_ML For This Useful Post:
- [ Click To Expand ]
-
-
7th April 2019, 06:33 PM #19
-
The Following 3 Users Say Thank You to scrub For This Useful Post:
- [ Click To Expand ]
-
-
7th April 2019, 06:34 PM #20
All 3 TT GO 700's ((M5) working perfectly on a 3 hour drive ...
OS 9.051 Europe_west 1025_9386 (my preferred version),
OS 9.541 Europe_west 1025_9386 (latest SE offering from here),
OS 7.903 Western_europe 660.1219 (original off the CD !!)
So no problems with the device at all, so far !! Having done the research I'll now be putting all three back to OS 9.051 Europe_west 1025_9386 as IMHO it's the one that works best, for me
There is a 95% chance that I won't be needing one of these anyhow, as I have changed the car to an Audi with a built in system , and it seems it can be kept up-to-date easily ...we wait and see.. Wife and kids will still use the Go 700's so you wont see the back of me ... yet
-
The Following 2 Users Say Thank You to Entwood For This Useful Post:
- [ Click To Expand ]
-
Blowfish/Meta codes for v1135...
; Europe_1135_12484 35 42 1D 38 86 4B 09 7F F9...