I have a Z3816A that’s showing a yellow “ro” next to the date in LH and is 18 seconds ahead of a Motorola 12 channel (and my iPhone). I haven’t had time to look into it as I’m adjusting to “voluntary” retirement and trying to clear out some excess stuff.

Steve

Hi,
I just got a heads up fro TomTom, saying my Go Live 825 bought 2012 « may » have WNRO problems after the April 6 rollover and invited me to update the firmware. I wouldn’t think it would affect the navigation, but it might brick the device. Unfortunately I can’t test it as it went to recycle 3 month ago . This could be an interesting week.
Mike

"Ceux qui sont prêts à abandonner une liberté essentielle pour obtenir une petite et provisoire sécurité, ne méritent ni liberté ni sécurité."
Benjimin Franklin

Potentially everything using the week 10 bits.  Check your manufacturer.  Trimble is all over this.

Sent from my iPhone

I received the same invitation. And they states that the WNRO problem is
an "external" problem.  I did it and now all the maps are signaled as
invalid!

Fortunately I was able to copy my  main map from a backup copy.

Regards,

Ignacio EB4APL

El 04/04/2019 a las 12:29, Mike Cook escribió:

El software de antivirus Avast ha analizado este correo electrónico en busca de virus.
https://www.avast.com/antivirus

Yes Steve, you are correct.

https://www.gps.gov/

Scroll down a bit and you can find a count down to the roll over. And it states the time when it will roll over. Just what you have said.

Jeff Z.

Sent from my iPhone

I checked my Garmin Emap, 1999 vintage IIRC. That is telling me that it is 20/05/2014.

I found this for Trimble which shows a number of devices affected by this which are commonly used bt timenuts.

https://novotech.com/support/eol-notices/trimble-gps-wnro-april-6-2019-event

Have a nice day

"Ceux qui sont prêts à abandonner une liberté essentielle pour obtenir une petite et provisoire sécurité, ne méritent ni liberté ni sécurité."
Benjimin Franklin

Steve Olney wrote:

The explanation is simple, IMO.

When the GPS system was put into operation in 1980 then the GPS time
matched UTC.

However, a number of leap seconds have been inserted into the UTC time
scale since, and each leap second delayed UTC by 1 s.

Yet 18 leap seconds have been inserted, so UTC is 18 s behind GPS time,
or the other way round, GPS time is 18 s ahead of UTC, so the WNRO
occurs 18 s before UTC midnight.

BTW, the effects of the rollover have already begun. For example, the
reference times of the almanac and clock correction parameters in the
the navigation messages received from the satellites refer to a time a
in the near future, so the week number of those time stamps has already
rolled over.

Martin

The OP doesn’t state where he got the  « quote » from, but IMHO it is wrong. As I understand it.
The GPS epoch started at 0h 1st June 1980 and the week number roles at 1024 week intervals at 0h GPS time. When a leap second is added its as if the clock stops for a second so GPS time will be in advance of UTC buy the number of leap seconds added.  18 leap seconds have been added to date, so 0h GPS 07 april 2019 will be crossed at 23:59:42 UTC on April 6 as you indicated.

"Ceux qui sont prêts à abandonner une liberté essentielle pour obtenir une petite et provisoire sécurité, ne méritent ni liberté ni sécurité."
Benjimin Franklin