Has anyone else noticed that the clock is off 1 second since the leap second was added? I'm comparing to https://time.is/ Is there a way to correct this or will it require a firmware update?
It would require a firmware update as the GPS time does not implement leap seconds and that is where the Edge is getting its time from. The Edge then converts that time to local time for display.
The time on my Edge 520 looks to be correct.
The GPS unit will automatically display the calculated UTC based time from GPS time received. The GPS unit receives the GPS time adjustment from the GPS satellite and that adjustment is sent out every 12.5 minutes. To be sure that your GPS has received this adjustment the unit needs to have good satellite reception for at least 12.5 minutes for you to be sure it has had the opportunity to receive the information from the satellite.
Sources:
http://gpsinformation.net/main/gpstime.htm http://tycho.usno.navy.mil/leapsec.html http://www.leapsecond.com/java/gpsclock.htm
For me personnally, as long as the GPS can determine my position with reasonable accuracy and put decent time stamp on my ride then I would not worry about it being off by a second or two.
¯\_(ツ)_/¯
When I first read this post, I was astounded that anyone could notice something so obscure. But as it turns out, scott46tw is absolutely correct - the Edge 520 clock is off by one second:
I spoke with Garmin on this. Only a limited number of models are affected by this. It depends on the GPS chip set they are using. The only Edge model that is affected by this is the 520.
