Yes there is certainly an error here: With my timing module I was just eyeballing the output on a windows platform , comparing GUI data. I have just linked the module up to a BeagleBone Black sync’d with NTP and this is the NMEA msg log:
root@bb3:/home/mike/serial-ports# while read GGA; do echo `date` $GGA; done < /dev/ttyO4 Mon Jan 26 21:51:07 UTC 2015 $GPGGA,215106.000,4847.3526,N,00216.3005,E,1,04,2.8,192.8,M,47.0,M,,0000*5C Mon Jan 26 21:51:07 UTC 2015 $GPGLL,4847.3526,N,00216.3005,E,215106.000,A,A*56 Mon Jan 26 21:51:07 UTC 2015 $GPGSA,A,3,25,12,06,31,,,,,,,,,3.0,2.8,1.0*3A Mon Jan 26 21:51:07 UTC 2015 $GPRMC,215106.000,A,4847.3526,N,00216.3005,E,000.0,173.5,260115,,,A*60 Mon Jan 26 21:51:07 UTC 2015 $GPVTG,173.5,T,,M,000.0,N,000.0,K,A*0D Mon Jan 26 21:51:07 UTC 2015 $GPZDA,215106.000,26,01,2015,00,00*54 Mon Jan 26 21:51:07 UTC 2015 $PSTI,00,2,0,4.6,,*30 Mon Jan 26 21:51:08 UTC 2015 $GPGGA,215107.000,4847.3526,N,00216.3005,E,1,04,2.8,192.8,M,47.0,M,,0000*5D Mon Jan 26 21:51:08 UTC 2015 $GPGLL,4847.3526,N,00216.3005,E,215107.000,A,A*57 Mon Jan 26 21:51:08 UTC 2015 $GPGSA,A,3,25,12,06,31,,,,,,,,,3.0,2.8,1.0*3A Mon Jan 26 21:51:08 UTC 2015 $GPGSV,3,1,10,25,73,294,42,12,59,063,44,14,45,264,20,29,41,196,25*7B Mon Jan 26 21:51:08 UTC 2015 $GPGSV,3,2,10,24,34,136,13,02,28,091,21,31,22,306,34,06,19,047,37*74 Mon Jan 26 21:51:08 UTC 2015 $GPGSV,3,3,10,32,03,310,,03,01,347,*7A Mon Jan 26 21:51:08 UTC 2015 $GPRMC,215107.000,A,4847.3526,N,00216.3005,E,000.0,173.5,260115,,,A*61 Mon Jan 26 21:51:08 UTC 2015 $GPVTG,173.5,T,,M,000.0,N,000.0,K,A*0D Mon Jan 26 21:51:08 UTC 2015 $GPZDA,215107.000,26,01,2015,00,00*55 Mon Jan 26 21:51:08 UTC 2015 $PSTI,00,2,0,-3.9,,*15 The time data is all a second late so they appear to have a serious issue. I module I have is the NS-T from NavSpark, so I will get on to them to see if they have a fix. Updates later. "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 > Le 26 janv. 2015 à 02:47, Bill Beam <[email protected]> a écrit : > > Odd indeed. My LTE-lite is one second late, appears to have already added > the pending leap second. > I can compare with four other GPS timeing receivers using time pulse on DCD > line. The NMEA data > reports in error. I am awaiting reply from JL. This is not good for an eBay > sniper.... > > Bill, NL7F > > On Sun, 25 Jan 2015 12:12:55 -0800, Tom Van Baak wrote: > >> Hi Paul, > >> Odd, my LTE-Lite appears spot on. Let's take this off-list and see what's >> going on. > >> If anyone else has been logging SkyTraq NMEA or binary from the LTE-Lite let >> us know. > > > Bill Beam > NL7F > > > > _______________________________________________ > time-nuts mailing list -- [email protected] > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
