Re: [time-nuts] End of the World, or beginning of a new one?
Michael A. Waldron lists@... writes: Olivier from Heol says that it will revert to 1995 again in a few months, although he was unspecific as to the exact reasons he said they simulated it in their lab. I've decided I'd like to upgrade the GPS in my 2100-rb, but it will probably be a little while before I get the job done. -Mike On 7/2/2015 3:01 PM, Bob Martin wrote: As I look at my Tymserve 2100 sitting in the rack to my left, the date it's displaying is JUL 02 2015. So the week rollover bug was coupled to the leap second? No wine to drink today (it's still early)... Anyone else with a TS2100 that's suddenly acting strange, er, correct for the first time in a while? bob k6rtm ___ time-nuts mailing list -- time-nuts@... To unsubscribe, go to https://www.febo.com/cgi- bin/mailman/listinfo/time-nuts and follow the instructions there. Hello, Yes the Tymserve and other similar DATUM / Symmetricom products which use the Trimble ACE board will fail again in 2016. This is due to the way the GPS epoch is calculated inside the 2100 : the DATUM engineers estimated the future leap second insertions to determine GPS epochs, which was not a so good idea... Our N024 GPS board inserted insteas of the ACE board corrects this bug, as well as offering high GPS sensitivity and fast startup. We offer warranty for the next 20 years. Regards Olivier ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End of the World, or beginning of a new one?
See patent US5923618 and also http://www.leapsecond.com/notes/gpswnro.htm for details. Based on what happened to the TS2100 (with Trimble ACE receiver) it looks like they tried to guess which 1024-week GPS epoch it was based on how high the leap second count was. And although this sounds good in theory, the earth is not cooperating with that plan. Not only are leap seconds unpredictable but the rate of leap seconds is even less predictable. In the 1970's there was an average of one leapsecond a year. In the 1980's and 1990's this dropped to about 1.5 years. And since 2000 it's down to one leap second every 4 years. That is, the earth has been gradually speeding back up, their hardcoded algorithm no longer well matches reality, and so they mispredicted which 1024 epoch GPS is in. I would recommend people use the Heol Design replacement receiver, which doesn't have this problem. /tvb - Original Message - From: Björn b...@lysator.liu.se To: Discussion of precise time and frequency measurement time-nuts@febo.com Sent: Saturday, July 04, 2015 1:30 PM Subject: Re: [time-nuts] End of the World, or beginning of a new one? Yes the Tymserve and other similar DATUM / Symmetricom products which use the Trimble ACE board will fail again in 2016. This is due to the way the GPS epoch is calculated inside the 2100 : the DATUM engineers estimated the future leap second insertions to determine GPS epochs, which was not a so good idea... That was Trimble engineers... anyone with the actual algorithm they used? /Björn ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End of the World, or beginning of a new one?
Yes the Tymserve and other similar DATUM / Symmetricom products which use the Trimble ACE board will fail again in 2016. This is due to the way the GPS epoch is calculated inside the 2100 : the DATUM engineers estimated the future leap second insertions to determine GPS epochs, which was not a so good idea... That was Trimble engineers... anyone with the actual algorithm they used? /Björn ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End of the World, or beginning of a new one?
Olivier from Heol says that it will revert to 1995 again in a few months, although he was unspecific as to the exact reasons he said they simulated it in their lab. I've decided I'd like to upgrade the GPS in my 2100-rb, but it will probably be a little while before I get the job done. -Mike On 7/2/2015 3:01 PM, Bob Martin wrote: As I look at my Tymserve 2100 sitting in the rack to my left, the date it's displaying is JUL 02 2015. So the week rollover bug was coupled to the leap second? No wine to drink today (it's still early)... Anyone else with a TS2100 that's suddenly acting strange, er, correct for the first time in a while? bob k6rtm ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. -- Michael A. Waldron, AE0MW http://www.mikew.org ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
Bob Camp wrote: Well it sounds like there are (so far) no major reports of extreme behavior. There still seem to be *lots* of reports of systems that do not handle things gracefully. I wonder if the data above is specific to a chip set (which it probably is) or to how Glonass handles leap seconds (yikes !!!). As said in my previous email, it was a NVD8C-CSM v3.1 module specifically set to GLONASS-only mode. I'm assuming the problem is specific to GLONASS. The GPS satellites sends their data frames in 6 second intervals aligned with GPS time which is linear, with constant offset to TAI, so the data frames are not affected by a leap second. It's been quite a while that I looked at some GLONASS specs, but if I remember correctly the data frames sent by GLONASS satellites are aligned with UTC. So if a leap second is inserted or deleted there *is* some interruption in the sequence of the data frames. So it's much more difficult for receivers to keep tracking GLONASS satellites than GPS satellites over a leap second, and I'm not specifically surprised that GLONASS receiver at least loose sync when a leap second occurs. Martin ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
Frister wrote: My NTP server did a double 59 on the terminal. for anybody who is interested I captured the event : https://youtu.be/OpNci29CI7E I think you need to be careful if you just watch the time in a loop with a sleep 1. Due to slightly varying sleep intervals the time when the date command is called may interfere with the second boundary of the system time, so you may observe missing or duplicate times anyway. Eventually the following command shows less ambiguous results: while true; do date -u +'%F %T.%N'; sleep 0.25; done E.g.: 2015-07-02 09:46:01.236101917 2015-07-02 09:46:01.490039978 2015-07-02 09:46:01.743952328 2015-07-02 09:46:01.997539363 2015-07-02 09:46:02.251356539 2015-07-02 09:46:02.505238060 2015-07-02 09:46:02.759204117 2015-07-02 09:46:03.013218510 2015-07-02 09:46:03.267194076 2015-07-02 09:46:03.521256275 2015-07-02 09:46:03.775118487 2015-07-02 09:46:04.029012022 2015-07-02 09:46:04.283006237 2015-07-02 09:46:04.537024946 2015-07-02 09:46:04.790874099 Usually you get 4 timestamps per second, but eventually there may be only 3 or so, depending on the accuracy of the sleep intervals. In any case you have the fractions of the second to *see* that there is eventually a second :03.9 where you expected :04.0, or vice versa. Martin ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
Thank you Martin, To be honest, I didn't know that the sleep command could be utilized with a 1 Foolish of me to not have tried it. On 02/07/2015, Martin Burnicki martin.burni...@burnicki.net wrote: Frister wrote: My NTP server did a double 59 on the terminal. for anybody who is interested I captured the event : https://youtu.be/OpNci29CI7E I think you need to be careful if you just watch the time in a loop with a sleep 1. Due to slightly varying sleep intervals the time when the date command is called may interfere with the second boundary of the system time, so you may observe missing or duplicate times anyway. Eventually the following command shows less ambiguous results: while true; do date -u +'%F %T.%N'; sleep 0.25; done E.g.: 2015-07-02 09:46:01.236101917 2015-07-02 09:46:01.490039978 2015-07-02 09:46:01.743952328 2015-07-02 09:46:01.997539363 2015-07-02 09:46:02.251356539 2015-07-02 09:46:02.505238060 2015-07-02 09:46:02.759204117 2015-07-02 09:46:03.013218510 2015-07-02 09:46:03.267194076 2015-07-02 09:46:03.521256275 2015-07-02 09:46:03.775118487 2015-07-02 09:46:04.029012022 2015-07-02 09:46:04.283006237 2015-07-02 09:46:04.537024946 2015-07-02 09:46:04.790874099 Usually you get 4 timestamps per second, but eventually there may be only 3 or so, depending on the accuracy of the sleep intervals. In any case you have the fractions of the second to *see* that there is eventually a second :03.9 where you expected :04.0, or vice versa. Martin ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. -- vbradio.wordpress.com ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
On Thu, Jul 02, 2015 at 04:47:02PM +, Frister wrote: To be honest, I didn't know that the sleep command could be utilized with a 1 Foolish of me to not have tried it. It's an extension, as sleep used to only work with integer numbers of seconds, e.g. http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sleep.html#tag_20_118 however, it's pretty widely supported these days. David. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
Le 1 juil. 2015 à 09:02, Hal Murray hmur...@megapathdsl.net a écrit : michael.c...@sfr.fr said: Lady Heather just went told me 23:59:59 , 00:00:00 and stayed there for 2 secs, No 23:59:60 :-( What sort of device was it looking at? a T-Bolt. Firmware 3.0 GPS 10.2 .Mfg. 2002. Leap status was Leap Pending! I have it on video. -- These are my opinions. I hate spam. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. 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 ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
My NTP server did a double 59 on the terminal. for anybody who is interested I captured the event : https://youtu.be/OpNci29CI7E I did measure an odd behaviour on leapsecond day from time-a.nist.gov NTP server usually it runs about 8 mS behind my local PPS but all the sudden went to +22 mS for most of the the UTC day, see: https://flic.kr/p/vnZGaU a few minutes after 00:00 it returned to the usual offset https://flic.kr/p/vrPsAR 73 Frits W1FVB On 01/07/2015, Martin Burnicki martin.burni...@burnicki.net wrote: Bob Camp schrieb: Hi So are we all still here? Any portion of the group blasted into non-existance by the leap second please speak up :) === Any observations of anomalous behavior yet? From a NVD8C-CSM v3.1 module in Glonass-only mode: $GPZDA,235958.00,30,06,2015,00,00*65 $GPGGA,235959.00,5158.9396,N,00913.5513,E,1,10,00.7,119.5,M,47.2,M,,*53 $GPRMC,235959.00,A,5158.9396,N,00913.5513,E,00.00,144.5,300615,,,A*5F $GPGSV,1,1,04,33,26,210,00,37,29,164,00,39,29,160,00,40,17,127,00*76 $GLGSV,3,1,10,68,36,066,46,69,74,335,41,70,26,270,49,77,17,018,35*61 $GLGSV,3,2,10,78,34,075,43,79,18,125,40,83,06,190,38,84,43,230,42*6F $GLGSV,3,3,10,85,42,304,45,86,07,344,38*68 $GLGSA,A,3,68,69,79,83,85,84,77,78,70,86,,,01.4,00.7,01.2*1C $PORZD,A,002.7*39 $GPZDA,235959.00,30,06,2015,00,00*64 $GPGGA,00.00,5158.9396,N,00913.5513,E,1,10,00.7,119.5,M,47.2,M,,*52 $GPRMC,00.00,A,5158.9396,N,00913.5513,E,00.00,144.5,010715,,,A*5D $GPGSV,1,1,04,33,26,210,00,37,29,164,00,39,29,160,00,40,17,127,00*76 $GLGSV,3,1,10,68,36,066,46,69,74,335,40,70,26,270,49,77,17,018,36*63 $GLGSV,3,2,10,78,34,075,43,79,18,125,41,83,06,190,39,84,43,230,42*6F $GLGSV,3,3,10,85,42,304,46,86,07,344,37*64 $GLGSA,A,3,68,69,79,83,85,84,77,78,70,86,,,01.4,00.7,01.2*1C $PORZD,A,002.7*39 $GLGBS,00.00,2.0,1.8,5.2*51 $GPZDA,00.00,01,07,2015,00,00*66 $GPGGA,01.00,5158.9396,N,00913.5513,E,1,10,00.7,119.5,M,47.2,M,,*53 $GPRMC,01.00,A,5158.9396,N,00913.5513,E,00.00,144.5,010715,,,A*5C $GPGSV,1,1,04,33,26,210,00,37,29,164,00,39,29,160,00,40,17,127,00*76 $GLGSV,3,1,10,68,36,066,44,69,74,335,39,70,26,270,47,77,17,018,34*63 $GLGSV,3,2,10,78,34,075,42,79,18,125,39,83,06,190,37,84,43,230,41*6C $GLGSV,3,3,10,85,42,304,44,86,07,344,36*67 $GLGSA,A,3,68,69,79,83,85,84,77,78,70,86,,,01.4,00.7,01.2*1C $PORZD,A,002.7*39 $GPZDA,01.00,01,07,2015,00,00*67 RestartKÕÎ$GPGGA,00.00,.,N,0.,E,0,,,-18.0,M,18.0,M,,*5E $GPRMC,00.00,V,.,N,0.,E,00.00,000.0N*46 $GPGSV,1,1,00*79 $GLGSV,1,1,00*65 $GPGSA,A,1,,,*1E $PORZD,V,999.9*2B $GPGBS,00.00,,,*6F $ALVER,NVS,CSM23,0207*72 $POTST,ID,0268501855,ANT,1,RFG,0,RFR,0*3E $GPGGA,01.00,.,N,0.,E,0,,,-18.0,M,18.0,M,,*5F $GPRMC,01.00,V,.,N,0.,E,00.00,000.0N*47 $GPGSV,1,1,00*79 $GLGSV,1,1,00*65 $GPGSA,A,1,,,*1E $PORZD,V,999.9*2B $GPZDA,01.0000,00*67 $GPGGA,02.00,.,N,0.,E,0,,,-18.0,M,18.0,M,,*5C $GPRMC,02.00,V,.,N,0.,E,00.00,000.0N*44 The module restarted itself when the leap second occurred. Martin ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. -- vbradio.wordpress.com ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
michael.c...@sfr.fr said: Lady Heather just went told me 23:59:59 , 00:00:00 and stayed there for 2 secs, No 23:59:60 :-( What sort of device was it looking at? -- These are my opinions. I hate spam. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
At home I recorded the following seconds: Tunderbolt GPSDO 58 59 60 00 01 02 Meinberg LANTIME M200 58 59 59 00 01 02 hopf DCF 7001 58 59 60 01 02 03 Conrad DCF Time Terminal 58 59 00 01 02 03 The (old 1999) DCF hopf clock in particular was a strange one. It announced a leap event an hour before. Then it went from second 59, 60 to 01, so it was still a second ahead! After 8 minutes it counted the 01 second two times. From then on it showed the correct time. Local time was 02:00 hours, so i've missed some sleep. This morning at work we've found some 'link errors' in application logs at exactly 23:59:59. NTP clients were out of sync for some time. But no big problems reported yet. Bob Camp schreef op 2015-07-01 03:03: Hi So are we all still here? Any portion of the group blasted into non-existance by the leap second please speak up :) === Any observations of anomalous behavior yet? Bob ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
time-nuts@febo.com said: As expected, on the leap second the display on the 8183 showed 6:59:60 (the 8183-A showed 23:59:60), but the TV400 displayed 7:00:00 at that moment. The TV400 remained one second ahead until it displayed 7:00:03 for a two-second period, then from 7:00:04 forward it was properly synced. My guess is that there is a CPU in the TV400 that is smart enough to filter out noise but not smart enough to know about leap seconds. It considers 23:59:60 to be noise and rejects it. The following data gets rejected because it doesn't match the predicted time. After a few seconds of data that is self-consistent, it switches to the new time. -- These are my opinions. I hate spam. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
Bob Camp schrieb: Hi So are we all still here? Any portion of the group blasted into non-existance by the leap second please speak up :) === Any observations of anomalous behavior yet? From a NVD8C-CSM v3.1 module in Glonass-only mode: $GPZDA,235958.00,30,06,2015,00,00*65 $GPGGA,235959.00,5158.9396,N,00913.5513,E,1,10,00.7,119.5,M,47.2,M,,*53 $GPRMC,235959.00,A,5158.9396,N,00913.5513,E,00.00,144.5,300615,,,A*5F $GPGSV,1,1,04,33,26,210,00,37,29,164,00,39,29,160,00,40,17,127,00*76 $GLGSV,3,1,10,68,36,066,46,69,74,335,41,70,26,270,49,77,17,018,35*61 $GLGSV,3,2,10,78,34,075,43,79,18,125,40,83,06,190,38,84,43,230,42*6F $GLGSV,3,3,10,85,42,304,45,86,07,344,38*68 $GLGSA,A,3,68,69,79,83,85,84,77,78,70,86,,,01.4,00.7,01.2*1C $PORZD,A,002.7*39 $GPZDA,235959.00,30,06,2015,00,00*64 $GPGGA,00.00,5158.9396,N,00913.5513,E,1,10,00.7,119.5,M,47.2,M,,*52 $GPRMC,00.00,A,5158.9396,N,00913.5513,E,00.00,144.5,010715,,,A*5D $GPGSV,1,1,04,33,26,210,00,37,29,164,00,39,29,160,00,40,17,127,00*76 $GLGSV,3,1,10,68,36,066,46,69,74,335,40,70,26,270,49,77,17,018,36*63 $GLGSV,3,2,10,78,34,075,43,79,18,125,41,83,06,190,39,84,43,230,42*6F $GLGSV,3,3,10,85,42,304,46,86,07,344,37*64 $GLGSA,A,3,68,69,79,83,85,84,77,78,70,86,,,01.4,00.7,01.2*1C $PORZD,A,002.7*39 $GLGBS,00.00,2.0,1.8,5.2*51 $GPZDA,00.00,01,07,2015,00,00*66 $GPGGA,01.00,5158.9396,N,00913.5513,E,1,10,00.7,119.5,M,47.2,M,,*53 $GPRMC,01.00,A,5158.9396,N,00913.5513,E,00.00,144.5,010715,,,A*5C $GPGSV,1,1,04,33,26,210,00,37,29,164,00,39,29,160,00,40,17,127,00*76 $GLGSV,3,1,10,68,36,066,44,69,74,335,39,70,26,270,47,77,17,018,34*63 $GLGSV,3,2,10,78,34,075,42,79,18,125,39,83,06,190,37,84,43,230,41*6C $GLGSV,3,3,10,85,42,304,44,86,07,344,36*67 $GLGSA,A,3,68,69,79,83,85,84,77,78,70,86,,,01.4,00.7,01.2*1C $PORZD,A,002.7*39 $GPZDA,01.00,01,07,2015,00,00*67 RestartKÕÎ$GPGGA,00.00,.,N,0.,E,0,,,-18.0,M,18.0,M,,*5E $GPRMC,00.00,V,.,N,0.,E,00.00,000.0N*46 $GPGSV,1,1,00*79 $GLGSV,1,1,00*65 $GPGSA,A,1,,,*1E $PORZD,V,999.9*2B $GPGBS,00.00,,,*6F $ALVER,NVS,CSM23,0207*72 $POTST,ID,0268501855,ANT,1,RFG,0,RFR,0*3E $GPGGA,01.00,.,N,0.,E,0,,,-18.0,M,18.0,M,,*5F $GPRMC,01.00,V,.,N,0.,E,00.00,000.0N*47 $GPGSV,1,1,00*79 $GLGSV,1,1,00*65 $GPGSA,A,1,,,*1E $PORZD,V,999.9*2B $GPZDA,01.0000,00*67 $GPGGA,02.00,.,N,0.,E,0,,,-18.0,M,18.0,M,,*5C $GPRMC,02.00,V,.,N,0.,E,00.00,000.0N*44 The module restarted itself when the leap second occurred. Martin ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
t...@leapsecond.com said: Am I reading this right -- those GPS receivers applied the leap second 16 seconds before they were supposed to, resulting in a double 23:59:44 instead of 23:59:59 and 23:59:60? So not only did they use GPS instead of UTC but the opted for the double second instead of a valid leap second. That's my reading. 57203 86383.752 $GPRMC,235943.000,A,3726.0874,N,12212.2628,W,1.71,186.96,300615,,*1A 57203 86384.750 $GPRMC,235944.000,A,3726.0866,N,12212.2630,W,1.33,180.14,300615,,*1D 57203 86385.752 $GPRMC,235944.000,A,3726.0858,N,12212.2631,W,1.10,178.01,300615,,*13 57203 86386.751 $GPRMC,235945.000,A,3726.0850,N,12212.2632,W,1.18,179.98,300615,,*10 -- These are my opinions. I hate spam. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
Hi Hal, Am I reading this right -- those GPS receivers applied the leap second 16 seconds before they were supposed to, resulting in a double 23:59:44 instead of 23:59:59 and 23:59:60? So not only did they use GPS instead of UTC but the opted for the double second instead of a valid leap second. /tvb - Original Message - From: Hal Murray hmur...@megapathdsl.net To: Discussion of precise time and frequency measurement time-nuts@febo.com Cc: hmur...@megapathdsl.net Sent: Tuesday, June 30, 2015 8:38 PM Subject: Re: [time-nuts] End Of The World Any observations of anomalous behavior yet? From a BU-353: 57203 86380.750 $GPRMC,235940.000,A,3726.0893,N,12212.2627,W,0.52,64.49,300615,,*20 57203 86381.748 $GPRMC,235941.000,A,3726.0889,N,12212.2627,W,0.45,78.54,300615,,*2D 57203 86383.138 $GPRMC,235942.000,A,3726.0883,N,12212.2627,W,0.82,157.71,300615,,*14 57203 86383.752 $GPRMC,235943.000,A,3726.0874,N,12212.2628,W,1.71,186.96,300615,,*1A 57203 86384.750 $GPRMC,235944.000,A,3726.0866,N,12212.2630,W,1.33,180.14,300615,,*1D 57203 86385.752 $GPRMC,235944.000,A,3726.0858,N,12212.2631,W,1.10,178.01,300615,,*13 57203 86386.751 $GPRMC,235945.000,A,3726.0850,N,12212.2632,W,1.18,179.98,300615,,*10 57203 86388.136 $GPRMC,235946.000,A,3726.0842,N,12212.2630,W,1.67,146.83,300615,,*1C 57203 86388.752 $GPRMC,235947.000,A,3726.0836,N,12212.2627,W,1.15,129.24,300615,,*19 From a MR-350P 57203 86382.186 $GPRMC,235941.000,A,3726.0808,N,12212.2649,W,0.27,67.38,300615,,*2C 57203 86382.799 $GPRMC,235942.000,A,3726.0807,N,12212.2652,W,0.37,210.08,300615,,*1A 57203 86383.805 $GPRMC,235943.000,A,3726.0811,N,12212.2647,W,0.48,95.98,300615,,*26 57203 86384.807 $GPRMC,235944.000,A,3726.0812,N,12212.2647,W,0.17,210.63,300615,,*13 57203 86385.806 $GPRMC,235944.000,A,3726.0810,N,12212.2648,W,0.29,145.10,300615,,*14 57203 86387.188 $GPRMC,235945.000,A,3726.0809,N,12212.2647,W,0.39,174.68,300615,,*1E 57203 86387.807 $GPRMC,235946.000,A,3726.0806,N,12212.2647,W,0.54,173.43,300615,,*17 ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
Hi On Jul 1, 2015, at 6:25 AM, Martin Burnicki martin.burni...@burnicki.net wrote: Bob Camp schrieb: Hi So are we all still here? Any portion of the group blasted into non-existance by the leap second please speak up :) === Any observations of anomalous behavior yet? From a NVD8C-CSM v3.1 module in Glonass-only mode: $GPZDA,235958.00,30,06,2015,00,00*65 $GPGGA,235959.00,5158.9396,N,00913.5513,E,1,10,00.7,119.5,M,47.2,M,,*53 $GPRMC,235959.00,A,5158.9396,N,00913.5513,E,00.00,144.5,300615,,,A*5F $GPGSV,1,1,04,33,26,210,00,37,29,164,00,39,29,160,00,40,17,127,00*76 $GLGSV,3,1,10,68,36,066,46,69,74,335,41,70,26,270,49,77,17,018,35*61 $GLGSV,3,2,10,78,34,075,43,79,18,125,40,83,06,190,38,84,43,230,42*6F $GLGSV,3,3,10,85,42,304,45,86,07,344,38*68 $GLGSA,A,3,68,69,79,83,85,84,77,78,70,86,,,01.4,00.7,01.2*1C $PORZD,A,002.7*39 $GPZDA,235959.00,30,06,2015,00,00*64 $GPGGA,00.00,5158.9396,N,00913.5513,E,1,10,00.7,119.5,M,47.2,M,,*52 $GPRMC,00.00,A,5158.9396,N,00913.5513,E,00.00,144.5,010715,,,A*5D $GPGSV,1,1,04,33,26,210,00,37,29,164,00,39,29,160,00,40,17,127,00*76 $GLGSV,3,1,10,68,36,066,46,69,74,335,40,70,26,270,49,77,17,018,36*63 $GLGSV,3,2,10,78,34,075,43,79,18,125,41,83,06,190,39,84,43,230,42*6F $GLGSV,3,3,10,85,42,304,46,86,07,344,37*64 $GLGSA,A,3,68,69,79,83,85,84,77,78,70,86,,,01.4,00.7,01.2*1C $PORZD,A,002.7*39 $GLGBS,00.00,2.0,1.8,5.2*51 $GPZDA,00.00,01,07,2015,00,00*66 $GPGGA,01.00,5158.9396,N,00913.5513,E,1,10,00.7,119.5,M,47.2,M,,*53 $GPRMC,01.00,A,5158.9396,N,00913.5513,E,00.00,144.5,010715,,,A*5C $GPGSV,1,1,04,33,26,210,00,37,29,164,00,39,29,160,00,40,17,127,00*76 $GLGSV,3,1,10,68,36,066,44,69,74,335,39,70,26,270,47,77,17,018,34*63 $GLGSV,3,2,10,78,34,075,42,79,18,125,39,83,06,190,37,84,43,230,41*6C $GLGSV,3,3,10,85,42,304,44,86,07,344,36*67 $GLGSA,A,3,68,69,79,83,85,84,77,78,70,86,,,01.4,00.7,01.2*1C $PORZD,A,002.7*39 $GPZDA,01.00,01,07,2015,00,00*67 RestartKÕÎ$GPGGA,00.00,.,N,0.,E,0,,,-18.0,M,18.0,M,,*5E $GPRMC,00.00,V,.,N,0.,E,00.00,000.0N*46 $GPGSV,1,1,00*79 $GLGSV,1,1,00*65 $GPGSA,A,1,,,*1E $PORZD,V,999.9*2B $GPGBS,00.00,,,*6F $ALVER,NVS,CSM23,0207*72 $POTST,ID,0268501855,ANT,1,RFG,0,RFR,0*3E $GPGGA,01.00,.,N,0.,E,0,,,-18.0,M,18.0,M,,*5F $GPRMC,01.00,V,.,N,0.,E,00.00,000.0N*47 $GPGSV,1,1,00*79 $GLGSV,1,1,00*65 $GPGSA,A,1,,,*1E $PORZD,V,999.9*2B $GPZDA,01.0000,00*67 $GPGGA,02.00,.,N,0.,E,0,,,-18.0,M,18.0,M,,*5C $GPRMC,02.00,V,.,N,0.,E,00.00,000.0N*44 The module restarted itself when the leap second occurred. Martin Well it sounds like there are (so far) no major reports of extreme behavior. There still seem to be *lots* of reports of systems that do not handle things gracefully. I wonder if the data above is specific to a chip set (which it probably is) or to how Glonass handles leap seconds (yikes !!!). Bob ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
As expected, on the leap second the display on the 8183 showed 6:59:60 (the 8183-A showed 23:59:60), but the TV400 displayed 7:00:00 at that moment. The TV400 remained one second ahead until it displayed 7:00:03 for a two- second period, then from 7:00:04 forward it was properly synced. On the 2012 event my HP 55300A did the same thing on the IRIG output. The :03 second was repeated and then normal operation resumed. I did attempt to view the event on a 3.5 Tomtom GPS, without much joy. There's a setup screen that shows all SVs in view as well as the current UTC. When it came time to roll from 23:59:59 to 23:59:60 the time line just went blank for 1 second, then rolled to 00:00:00. Their code must be checking for 'invalid' time. Bummer ... -John ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
I'm happy to report that I did not get blasted away, but I did record what I think is an odd catch-up on a display clock. I have a Spectracom TV400 display clock literally sitting on top of and connected to a Spectracom 8183 (set to Central time zone) via RS-485 and 10' of shielded, twisted-pair wire. Below the 8183 is an 8183-A set to UTC. I grabbed my iPhone and videoed the three a little bit on both sides of the leap second while listening to WWV on 10 MHz with a Kinemetrics/TrueTime WVTR MK V. As expected, on the leap second the display on the 8183 showed 6:59:60 (the 8183-A showed 23:59:60), but the TV400 displayed 7:00:00 at that moment. The TV400 remained one second ahead until it displayed 7:00:03 for a two-second period, then from 7:00:04 forward it was properly synced. I know only enough about electronics to be potentially dangerous, so I have no explanation for this behavior. Perhaps someone knows why this happened and can explain? Thanks much to all for the enjoyment of and knowledge I've gained from reading postings on this list! David Stell Oklahoma City -Original Message- From: time-nuts [mailto:time-nuts-boun...@febo.com] On Behalf Of Bob Camp Sent: Tuesday, June 30, 2015 8:04 PM To: Discussion of precise time and frequency measurement Subject: [time-nuts] End Of The World Hi So are we all still here? Any portion of the group blasted into non-existance by the leap second please speak up :) === Any observations of anomalous behavior yet? Bob ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
On Wed, Jul 1, 2015 at 1:03 AM, Bob Camp kb...@n1k.org wrote: Hi So are we all still here? Any portion of the group blasted into non-existance by the leap second please speak up :) === Any observations of anomalous behavior yet? I was eagerly connecting to various things to watch for problems when everything stopped responding precisely at the end of the leapsecond. Turned out my cell phone-- an old android 2.3 device on the sprint network-- dropped off the network (looked like it was up but couldn't make or receive calls and no data was getting through). I waited 15 minutes to see if it would recover on its own, but it did not during that time. OTOH if it went out for 15 minutes otherwise I might not have thought to much of it-- so no proof that it was due to the leapsecond; very coincidental timing if not. :) ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
I drove past the US Naval Observatory on Massachusetts Avenue in Washington this evening. Their big LED clock by the main entrance was dark and someone appeared to be working on it. The leap second must have broken the USNO clock! Dan Schultz N8FGV ---original message--- Date: Tue, 30 Jun 2015 21:03:30 -0400 From: Bob Camp kb...@n1k.org To: Discussion of precise time and frequency measurement time-nuts@febo.com Subject: [time-nuts] End Of The World Message-ID: 66d6b7a9-aa39-4d5d-8a34-dd5f78488...@n1k.org Content-Type: text/plain; charset=us-ascii Hi So are we all still here? Any portion of the group blasted into non-existance by the leap second please speak up :) === Any observations of anomalous behavior yet? Bob ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
Hi, Some of us have found ourselves in Besancon this week for the EFTS, which is extraordinary but not strange. I found myself explaining Delta and Omega counter responses with hockey-puck ADEV responces on the whiteboard for the lab-session. Cheers, Magnus On 07/01/2015 03:03 AM, Bob Camp wrote: Hi So are we all still here? Any portion of the group blasted into non-existance by the leap second please speak up :) === Any observations of anomalous behavior yet? Bob ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
The Heol card worked in my 2100 and handled the event like a champ. I was surprised that the NIST site only fixed itself about 5 minutes ago though. Apparently Google has been inserting about .2 of a second for the last few updates slowly working up to this which I thought was interesting. HAPPY LEAP EVENT EVERYONE!! Respectfully, Sean Gallagher Malware Analyst 571-340-3475 -- Original Message -- From: Bob Camp kb...@n1k.org To: Discussion of precise time and frequency measurement time-nuts@febo.com Sent: 6/30/2015 9:03:30 PM Subject: [time-nuts] End Of The World Hi So are we all still here? Any portion of the group blasted into non-existance by the leap second please speak up :) === Any observations of anomalous behavior yet? Bob ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] End Of The World
Any observations of anomalous behavior yet? From a BU-353: 57203 86380.750 $GPRMC,235940.000,A,3726.0893,N,12212.2627,W,0.52,64.49,300615 ,,*20 57203 86381.748 $GPRMC,235941.000,A,3726.0889,N,12212.2627,W,0.45,78.54,300615 ,,*2D 57203 86383.138 $GPRMC,235942.000,A,3726.0883,N,12212.2627,W,0.82,157.71,30061 5,,*14 57203 86383.752 $GPRMC,235943.000,A,3726.0874,N,12212.2628,W,1.71,186.96,30061 5,,*1A 57203 86384.750 $GPRMC,235944.000,A,3726.0866,N,12212.2630,W,1.33,180.14,30061 5,,*1D 57203 86385.752 $GPRMC,235944.000,A,3726.0858,N,12212.2631,W,1.10,178.01,30061 5,,*13 57203 86386.751 $GPRMC,235945.000,A,3726.0850,N,12212.2632,W,1.18,179.98,30061 5,,*10 57203 86388.136 $GPRMC,235946.000,A,3726.0842,N,12212.2630,W,1.67,146.83,30061 5,,*1C 57203 86388.752 $GPRMC,235947.000,A,3726.0836,N,12212.2627,W,1.15,129.24,30061 5,,*19 From a MR-350P 57203 86382.186 $GPRMC,235941.000,A,3726.0808,N,12212.2649,W,0.27,67.38,300615 ,,*2C 57203 86382.799 $GPRMC,235942.000,A,3726.0807,N,12212.2652,W,0.37,210.08,30061 5,,*1A 57203 86383.805 $GPRMC,235943.000,A,3726.0811,N,12212.2647,W,0.48,95.98,300615 ,,*26 57203 86384.807 $GPRMC,235944.000,A,3726.0812,N,12212.2647,W,0.17,210.63,30061 5,,*13 57203 86385.806 $GPRMC,235944.000,A,3726.0810,N,12212.2648,W,0.29,145.10,30061 5,,*14 57203 86387.188 $GPRMC,235945.000,A,3726.0809,N,12212.2647,W,0.39,174.68,30061 5,,*1E 57203 86387.807 $GPRMC,235946.000,A,3726.0806,N,12212.2647,W,0.54,173.43,30061 5,,*17 They both use SiRF chips. Above is just the GPRMC lines. Some of them are delayed enough to fall into the next second because every 5th second includes the GPGSV sentences. I'm pretty sure this was reported 3 years ago, I don't remember who found it, but I did remember to look back to find the insertion at midnight TAI rather than UTC. -- Overall, pretty boring. Jun 30 16:59:59 shuksan klogd: Clock: inserting leap second 23:59:60 UTC From a Z3801A: 57203 86397.032 T22015063023595830+1046 57203 86398.032 T22015063023595930+1047 57203 86399.034 T22015063023596030+103F 57203 86399.034 T2201507010030+1025 57204 0.034 T22015070101300102B 57204 1.032 T22015070102300102C 57204 2.032 T22015070103300102D From a Z3811A: 86397.050728 T22015063023595830+0045 86398.050667 T22015063023595930+0046 86399.050712 T22015063023596030+003E 86399.050765 T2201507010030+0024 0.050696 T2201507010132A 1.050750 T2201507010232B 2.050685 T2201507010332C Google's external time servers do their smear dance at 50 ms/hour starting 10 hours before the leap. It's linear rather than a fancy cosine. I'll get a graph together one of these days. -- These are my opinions. I hate spam. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
