I have a set of 9603N iridium boards (fw TA14001) that used to be fine, but lately they are displaying an incorrect date with the NMEA frame $GNZDA. I get a date in April 2006 instead of Nov 2025. I saw that a re-epoch will be rolled out on Jan 14th 2026 but I don’t know if those events can be related… Is anyone meeting a similar issue?
Hi @AriMnqt ,
Forgive me for asking the dumb question… But do you have an antenna attached, and is it getting a clear signal from the Iridium satellites? The 9603N needs a satellite signal in order to set the clock.
I hope this helps,
Paul
Hello Paul
Yes, an antenna is attached, and satellites are detected. We do get perfect $GNGGA data, and the also the time (hh:mm:ss) value within the $GNZDA is correct.
But $GNGGA and $GNZDA are GNSS NMEA messages. Not Iridium AT-MSSTM 32-bit epoch values. Are we talking about the same thing?
Best,
Paul
Are you talking about Artemis Global Tracker? Is the ZOE-M8 GNSS outputting the wrong date?
The AT-MSSTM 32-bit epoch is correct but the answer to the CCLK command did match the 2006 date… It indeed does seem to be a GNSS input default. I am using the RockBLOCK 9603N coupled with an SL871L GNSS from Telit.
Hi @AriMnqt ,
I do not know if this will help you to solve your issue, but please see:
Best wishes,
Paul
@PaulZC thank you, yes we actually have 2 related issues : this re-epoch and a similar situation with our GNSS’s pivot date. We have now updated both firmwares and I will try the command in this thread.