Re: [time-nuts] GPS leap second pending (TBolt/Heather)
my monitor ( see http://www.romahn.info/tbolt2lcd/ ) also shows leap sec pending. This info is from Thunderbolt. Götz = I see no spurious indications from the NTP servers I happen to be using. I wrote a program to check: http://www.satsignal.eu/software/net.htm#NTPLeapTrace Cheers, David -- SatSignal Software - Quality software written to your requirements Web: http://www.satsignal.eu Email: david-tay...@blueyonder.co.uk ___ 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] GPS leap second pending (TBolt/Heather)
My Ball/EFRATOM MFS-209's MGPS receiver has announced there is a leap second scheduled for 6/30/2015 at midnite. The MGPS's engine is a 6 channel Trimble of some sort. -Chuck Harris Götz Romahn wrote: my monitor ( see http://www.romahn.info/tbolt2lcd/ ) also shows leap sec pending. This info is from Thunderbolt. Götz ___ 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] GPS leap second pending (TBolt/Heather)
my monitor ( see http://www.romahn.info/tbolt2lcd/ ) also shows leap sec pending. This info is from Thunderbolt. Götz Am 23.01.2015 um 04:38 schrieb Didier Juges: Re: Note that this is not a GPS problem, nor a Trimble problem. It's just a problem with user written software. I agree with Mark's comment. His software makes no attempt to interpret or correct the information put out by the Thunderbolt, it simply reports it. My Thunderbolt Monitor does the same thing. I can imagine a different tool with a different objective doing something different with good reason, but that is not what Lady Heather does, by choice rather than by mistake. It's a problem with user's expectations :) On Thu, Jan 22, 2015 at 8:05 PM, Mark Sims hol...@hotmail.com wrote: Nope, it's not an error or a problem. That column of data is showing a decode of the 16 status bits that the Tbolt is providing.The Trimble docs say that bit is a Leap Pending bit, so that is what Heather displays. It would be wrong to try and mask/adjust the report of the receiver's status word. Lady Heather is a monitor and display program for Trimble timing receivers. It shows the values that the receiver is reporting (usually to the precision that the receiver provides... think that micro-degree temperature value is really that accurate? I have a lovely bridge that you might want to purchase) But that's what the receiver is sending, so that's what gets displayed. - Note that this is not a GPS problem, nor a Trimble problem. It's just a problem with user written software. ___ 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. ___ 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] GPS leap second pending (TBolt/Heather)
Agreed that simply showing the status of the leap-pending bit is the logical thing to do, and it's definitely not something I would call a bug. It would be extremely cool, though, if it used the data from packet 0x58 to display a countdown timer. I'd volunteer to make the change, but I have an excellent excuse to avoid doing so, namely that I'm going to be offline for a few days while I move. :) This also means that the test/demo server at ke5fx.dyndns.org:45000 will be down for a while, probably at least a week. If you click on the KE5FX TBolt (Seattle, USA) link and it times out, that'll be why. -- john, KE5FX Miles Design LLC Nope, it's not an error or a problem. That column of data is showing a decode of the 16 status bits that the Tbolt is providing.The Trimble docs say that bit is a Leap Pending bit, so that is what Heather displays. It would be wrong to try and mask/adjust the report of the receiver's status word. Lady Heather is a monitor and display program for Trimble timing receivers. It shows the values that the receiver is reporting (usually to the precision that the receiver provides... think that micro-degree temperature value is really that accurate? I have a lovely bridge that you might want to purchase) But that's what the receiver is sending, so that's what gets displayed. ___ 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] GPS leap second pending (TBolt/Heather)
Nope, it's not an error or a problem. That column of data is showing a decode of the 16 status bits that the Tbolt is providing.The Trimble docs say that bit is a Leap Pending bit, so that is what Heather displays. It would be wrong to try and mask/adjust the report of the receiver's status word. Lady Heather is a monitor and display program for Trimble timing receivers. It shows the values that the receiver is reporting (usually to the precision that the receiver provides... think that micro-degree temperature value is really that accurate? I have a lovely bridge that you might want to purchase) But that's what the receiver is sending, so that's what gets displayed. - Note that this is not a GPS problem, nor a Trimble problem. It's just a problem with user written software. ___ 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] GPS leap second pending (TBolt/Heather)
Re: Note that this is not a GPS problem, nor a Trimble problem. It's just a problem with user written software. I agree with Mark's comment. His software makes no attempt to interpret or correct the information put out by the Thunderbolt, it simply reports it. My Thunderbolt Monitor does the same thing. I can imagine a different tool with a different objective doing something different with good reason, but that is not what Lady Heather does, by choice rather than by mistake. It's a problem with user's expectations :) On Thu, Jan 22, 2015 at 8:05 PM, Mark Sims hol...@hotmail.com wrote: Nope, it's not an error or a problem. That column of data is showing a decode of the 16 status bits that the Tbolt is providing.The Trimble docs say that bit is a Leap Pending bit, so that is what Heather displays. It would be wrong to try and mask/adjust the report of the receiver's status word. Lady Heather is a monitor and display program for Trimble timing receivers. It shows the values that the receiver is reporting (usually to the precision that the receiver provides... think that micro-degree temperature value is really that accurate? I have a lovely bridge that you might want to purchase) But that's what the receiver is sending, so that's what gets displayed. - Note that this is not a GPS problem, nor a Trimble problem. It's just a problem with user written software. ___ 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.
[time-nuts] GPS leap second pending (TBolt/Heather)
I was just sent a nice TBolt / Heather.exe screenshot from alert time-nuts reader Steven Reyer showing LEAP PENDING!. The good news is that, yes, there will be another leap second (in June). The bad news is that, no, there is not a leap second at the end of this month (January) nor at the end of March for that matter. So depending on how you interpret pending, Heather.exe has a bug. This sort of premature or ambiguous leap second reporting has caused problems with users in the past, especially when the leap second is announced more than 3 months ahead. Note that this is not a GPS problem, nor a Trimble problem. It's just a problem with user written software. In this case the user software is Heather. This message is derived from Trimble's 0x8F-AC Supplemental Timing Packet, minor alarm, bit 7. Note that the bit does not necessarily imply there is a leap second at the end of *this* month. All it means is a leap second is pending at the end of *some* month in the future. The user is then suppose to use packet 0x58 UTC Data (Type 5) to decode WN_lsf, DN_lsf, delta_lsf in order to figure out which month it is and report that. Like most GPS timing receivers, the TBolt handles leap seconds correctly when they occur. So no worries. But if you write your own add-on software and dare to report leap seconds ahead of time, you must do the math yourself. Give Mark Sims (author of Heather) first chance to fix it; if he doesn't want to then one of you can be a hero and send him a fix to him. For extra confidence you can use packet 0x8E-A4 to test your code. /tvb ___ 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.
