It doesn't look great to me. I'd expect a checksum on the end of the
sentence consisting of a * and two hex digits 0-9/A-F. I'm
disappointed the Sure isn't generating the checksum, as is
computationally trivial and serial transmission is far from inherently
error-free. Earlier NMEA specification versions require the checksum
only for $GPRMC, but the latest NMEA version mandates checksum on all
sentences.
Perhaps there's some way to enable checksum generation via a
programming sentence from the PC.
Cheers,
Dave Hart
Folks,
I have two Sure GPS devices, both running with the default configuration,
and I see checksums on both:
____________________________________________
C:\>ntpq "-c clockvar &2" alta
associd=9890 status=00f2 15 events, clk_bad_format,
device="NMEA GPS Clock",
timecode="$GPGGA,124113.000,5554.4213,N,00312.0716,W,2,8,1.32,185.4,M,49.6,M,000
0,0000*47",
poll=24068, noreply=7627, badformat=2690527, baddata=0, stratum=0,
refid=GPS, flags=0
C:\>ntpq "-c clockvar &2" feenix
associd=55229 status=00f2 15 events, clk_bad_format,
device="NMEA GPS Clock",
timecode="$GPGGA,124157.000,5554.4163,N,00312.0708,W,1,8,1.01,185.2,M,49.6,M,,*4
9",
poll=27448, noreply=6175, badformat=2840824, baddata=0, stratum=0,
refid=GPS, flags=0
____________________________________________
Cheers,
David
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
