Wrong pace -> wrong sync?

JPCV
JPCV Registered Users Posts: 1
New Traveler
edited January 24 in TomTom Sports
Hey! I bought my Tomtom Spark music a few weeks ago and I have not figured out yet what is causing the slower "instant" pace showed by the watch, while running. At first I thought my physical condition could be lower than usual but after a few runs I think I discovered the cause of the problem. Until now, the watch took about 10 sec. to sync with the gps sat. but in one run it took around 1 minute! In that run I the pace showed by the watch was identical to the pace I thought I was running.
The 10 sec. sync is normal? Or the 1 min. sync is more normal? Is there anything that I can do to make a good sync before running so the pace can also be realistic?
Thanks for your help!

Comments

  • tfarabaugh
    tfarabaugh Posts: 16,932
    Superuser
    For the GPS issue, are you updating the QuickGPS file a minimum of every three days by syncing the watch? This caches the expected satellite locations and makes for quicker attainment. Also do not try to get signal while moving, you are just making it harder on the watch. Best to just sit still with the button pointing skyward (or take it off and place it on a flat surface) until it finds the GPS. Make sure the watch is in an unobstructed area without large buildings, tree cover or reflective surfaces as this will cause a lot of interference. It will also take longer the first time you are in a new location but will speed up thereafter as it caches the location data for that spot. Once you get the Go it is best to give it another minute or two as Go is just the minimum satellites locked on. The longer you wait the more it will grab and the better your signal will be.

    For pace, no watch has true "instant pace". It is all computed in arrears and is a balance between responsiveness and smoothness. A longer lag time gives you smoother data but is slow to react. A short lag time gets faster responsiveness but choppier data. TomTom is slow to react to changes in pace because it applies a long smoothing period to produce smooth, non-choppy data. If you are running at a fairly steady pace you will not notice the lag. However, if you are doing intervals or sprints or changing speed a lot the lag can be become more apparent. This has been a complaint since the first version of the watch was released 3+ years ago and really has not changed much, so I would not expect much to change now.

    I hope this helped answer your question. If so, please mark it as a solution so others can look for it if they have the same question.