Just to let you know that I received my replacement NS-T receiver and verified
that that problem is fixed.
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow
NAVCEN issued an alert regarding receiver errors in handling the current
pending leap second data like has occurred with the Skytraq receiver.
Several brands/models were affected. I have not seen the original alert,
but here is an article summarizing:
http://www.insidegnss.com/node/4398
Keith
We have received some additional information from Skytraq regarding the
leap second error:
The faulty version firmware indicates leap seconds (17) from now to June
16th (two weeks before June 30th). During June 16th ~ June 30th, leap
second will recover to 16 and change properly to 17 on June
I have verified the Skytraq claim on my stand alone NS-T.
Tue Jan 27 06:52:06 UTC 2015
$GPGGA,065206.000,4847.3506,N,00216.3005,E,1,06,1.3,191.0,M,47.0,M,,*59
Tue Jan 27 06:52:06 UTC 2015 $GPGLL,4847.3506,N,00216.3005,E,065206.000,A,A*52
Tue Jan 27 06:52:06 UTC 2015
I have verified the Skytraq claim on my stand alone NS-T.
Tue Jan 27 06:52:06 UTC 2015 $GPGGA,065206.000,4847.3506
Hi Mike,
Please use more precise timestamps so your results can be believed. In general
it's not adequate to use one second unix time stamps to identify a possible one
second
Skytraq has provided updated firmware that corrects the 1 second offset.
For those who have not already, please contact us off list for return
instructions to have your unit updated.
Thank you for your patience with this issue. According to Skytraq the
error was introduced when code was added
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,
We have confirmed this issue with the Skytraq firmware on the LTE-Lite and
are working with Skytraq to obtain a firmware update. I will post again
when a firmware update is available.
Keith
Keith
On Sun, Jan 25, 2015 at 5:47 PM, Bill Beam wb...@gci.net wrote:
Odd indeed. My LTE-lite is one
Skytraq has also confirmed the issue and is working on a firmware update.
Updating the Skytraq firmware on the LTE-Lite Eval Board requires the unit
be returned to Jackson Labs for reprogramming. We will update the Skytraq
firmware on units at no charge if units are returned to us. Please
Be careful with 'eyeball data'. GPS receiver does not generate NMEA time data
and the leading edge of PPS at the same time.
Programs like Tac32 (totally accurate clock) and Lady Heather increment the
time display at the leading edge of PPS with a
value 1 second greater than the previous NMEA
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
- Original Message -
From: Paul tic-...@bodosom.net
To: Discussion of precise time and frequency measurement time-nuts@febo.com
Sent: Friday, January 23, 2015 8:58 PM
Subject: [time-nuts] LTE Lite time error
I see a one second error in the NMEA string from my LTE Lite.
It lost a second
I see a one second error in the NMEA string from my LTE Lite.
It lost a second between 23:33:34 and 23:33:42 21-Jan-2015 UTC.
I happened to check because a report of a one second error in some NTP pool
servers.
Just a heads up -- I'll be following up with JL directly.
--
Paul
13 matches
Mail list logo
