With
these NMEA devices the resolution comes from the chipset. As
below, the time is 09h37m52s, the milliseconds value is
always returned as zero. Not all NMEA sentences are returned
by every device, mine doesn’t return the timestamps.
They
are easy to read – just open the COM port and read the text.
$GPGLL,5006.3037,N,00507.6798,W,093752.000,A,A*47
$GPGLL,5006.3035,N,00507.6796,W,093753.000,A,A*4A
$GPGLL,5006.3032,N,00507.6792,W,093754.000,A,A*4E
time_t timeGetTime(); That has millisecond
resolution - if running with mm timer set to 1 ms. Then there
is the precision (100ns) timer with motherboard dependent
actual resolution. I use timeGetTime() most of the time. One
must handle it's roll over, of course. With time64_to work
with on 64 bit builds that's not much of a problem. It is
always a relative time to when the computer boots. But that
offset can be backed out if critical.
{^_^}
On 20220511 00:10:26, Simon Brown wrote:
And,
Testing my device it shows a time
resolution of just one second.
Yes,
Could do that, I have such a device.
Simon Brown
https://www.g4eli.com
https://www.sdr-radio.com
[Edited Message Follows]
Hi Simon. I have
seen in the forecast of version 1.2.7 of the "World Map",
an NTP client, would it be possible to implement the
reading of the clock of a GPS (installed in a serial
port)? It would be appreciated in areas or circumstances
without internet connection .
Thanks for your time. Antonio D. (EA7HGL)
--
--
