time-nuts@lists.febo.com

Discussion of precise time and frequency measurement

View all threads

Can Lady Heather set PC time directly from a TrimbleThunderbolt?

MS
Mark Sims
Thu, Aug 3, 2017 8:41 PM

Answer to second question:  For GMT time display set the time zone name to GMT with a time zone offset of 0.  (TZ keyboard command TZ GMT,  command line option /tx=GMT).

First question:  Yes Heather can set your system clock (assuming the program has access privileges to the change the clock.  Check out the TS keyboard command or /ts? command line options.  The clock setting routine is rather rude and crude.  It just jams the system clock with the receiver time on a once per minute/hour/day interval or whenever the receiver and system clocks diverge by more the "x" milliseconds.  The main purpose of the time set feature is for use when you don't have a net connection or NTP available.

The next version of Lady Heather has the ability to echo the receiver data (in either native format or NMEA format) to another serial port / IP address.

And for radio operations Heather has the ability to display the location in Maidenhead format.

Answer to second question: For GMT time display set the time zone name to GMT with a time zone offset of 0. (TZ keyboard command TZ GMT, command line option /tx=GMT). First question: Yes Heather can set your system clock (assuming the program has access privileges to the change the clock. Check out the TS keyboard command or /ts? command line options. The clock setting routine is rather rude and crude. It just jams the system clock with the receiver time on a once per minute/hour/day interval or whenever the receiver and system clocks diverge by more the "x" milliseconds. The main purpose of the time set feature is for use when you don't have a net connection or NTP available. The next version of Lady Heather has the ability to echo the receiver data (in either native format or NMEA format) to another serial port / IP address. And for radio operations Heather has the ability to display the location in Maidenhead format.
CW
Chris Wilson
Fri, Aug 4, 2017 2:39 PM

Hello,

on 04/08/2017 15:36  you wrote:

Answer to second question:  For GMT time display set the time zone
name to GMT with a time zone offset of 0.  (TZ keyboard command TZ
GMT,  command line option /tx=GMT).

First question:  Yes Heather can set your system clock (assuming
the program has access privileges to the change the clock.  Check
out the TS keyboard command or /ts? command line options.  The
clock setting routine is rather rude and crude.  It just jams the
system clock with the receiver time on a once per minute/hour/day
interval or whenever the receiver and system clocks diverge by more
the "x" milliseconds.  The main purpose of the time set feature is
for use when you don't have a net connection or NTP available.

The next version of Lady Heather has the ability to echo the
receiver data (in either native format or NMEA format) to another serial port / IP address.

And for radio operations Heather has the ability to display the location in Maidenhead format.


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.

Thanks  to  everyone  for the replies, so basically would you say that
with  a permanent internet connection I should forget using GPS time to
set  the  PC  clock  and  just use Meinberg or NTP (which is what I am
currently using and seems to work just fine)?

--
Best Regards,
Chris Wilson.

Hello, on 04/08/2017 15:36 you wrote: > Answer to second question: For GMT time display set the time zone > name to GMT with a time zone offset of 0. (TZ keyboard command TZ > GMT, command line option /tx=GMT). > First question: Yes Heather can set your system clock (assuming > the program has access privileges to the change the clock. Check > out the TS keyboard command or /ts? command line options. The > clock setting routine is rather rude and crude. It just jams the > system clock with the receiver time on a once per minute/hour/day > interval or whenever the receiver and system clocks diverge by more > the "x" milliseconds. The main purpose of the time set feature is > for use when you don't have a net connection or NTP available. > The next version of Lady Heather has the ability to echo the > receiver data (in either native format or NMEA format) to another serial port / IP address. > And for radio operations Heather has the ability to display the location in Maidenhead format. > _______________________________________________ > 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. Thanks to everyone for the replies, so basically would you say that with a permanent internet connection I should forget using GPS time to set the PC clock and just use Meinberg or NTP (which is what I am currently using and seems to work just fine)? -- Best Regards, Chris Wilson.
DJ
David J Taylor
Fri, Aug 4, 2017 4:18 PM

Thanks  to  everyone  for the replies, so basically would you say that
with  a permanent internet connection I should forget using GPS time to
set  the  PC  clock  and  just use Meinberg or NTP (which is what I am
currently using and seems to work just fine)?

   Best Regards,
               Chris Wilson.

---============

Chris,

That would be fine, but if you are interested make yourself a stratum-1
server based on, for example, a Raspberry Pi card.  Then if the Internet
/does/ go down, you'll still keep time.

BTW: you refer to "GPS time".  Not my area of expertise, but GPS time and
UTC aren't the same - GPS time doesn't use leap-seconds, for example, so
it's many seconds off from NTP.

Cheers,
David

SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@blueyonder.co.uk
Twitter: @gm8arv

Thanks to everyone for the replies, so basically would you say that with a permanent internet connection I should forget using GPS time to set the PC clock and just use Meinberg or NTP (which is what I am currently using and seems to work just fine)? Best Regards, Chris Wilson. ============================================= Chris, That would be fine, but if you are interested make yourself a stratum-1 server based on, for example, a Raspberry Pi card. Then if the Internet /does/ go down, you'll still keep time. BTW: you refer to "GPS time". Not my area of expertise, but GPS time and UTC aren't the same - GPS time doesn't use leap-seconds, for example, so it's many seconds off from NTP. Cheers, David -- SatSignal Software - Quality software written to your requirements Web: http://www.satsignal.eu Email: david-taylor@blueyonder.co.uk Twitter: @gm8arv
JH
John Hawkinson
Fri, Aug 4, 2017 5:46 PM

David J Taylor via time-nuts time-nuts@febo.com wrote on Fri,  4 Aug 2017
at 17:18:12 +0100 in 90765FA83DAC4C7EAA06F9A781AA5906@Alta:

BTW: you refer to "GPS time".  Not my area of expertise, but GPS
time and UTC aren't the same - GPS time doesn't use leap-seconds,
for example, so it's many seconds off from NTP.

We've been though this before, but I'll say it again.
This is not a very helpful thing to say.

"GPS time" is a very bad phrase to use, because it can mean "UTC derived via GPS," which is what most people mean. This accounts for leap seconds as most people expect. It is what essentially all consumer GPS receivers will display.

But "GPS time" can also mean "GPS system time," the internal time used by the GPS system that does not include leap seconds. It is extremely rare that anybody means this, but it does happen (esp. on time-nus). And many GPS receivers can be convinced to display GPS system time.

So, please don't say "GPS time," because it is ambiguous. But please also don't suggest that when people say "GPS time" they must mean "GPS system time," because they rarely do and it's just an unnecessary bit of confusion.

--jhawk@mit.edu
John Hawkinson

David J Taylor via time-nuts <time-nuts@febo.com> wrote on Fri, 4 Aug 2017 at 17:18:12 +0100 in <90765FA83DAC4C7EAA06F9A781AA5906@Alta>: > BTW: you refer to "GPS time". Not my area of expertise, but GPS > time and UTC aren't the same - GPS time doesn't use leap-seconds, > for example, so it's many seconds off from NTP. We've been though this before, but I'll say it again. This is not a very helpful thing to say. "GPS time" is a very bad phrase to use, because it can mean "UTC derived via GPS," which is what most people mean. This accounts for leap seconds as most people expect. It is what essentially all consumer GPS receivers will display. But "GPS time" can also mean "GPS system time," the internal time used by the GPS system that does not include leap seconds. It is extremely rare that anybody means this, but it does happen (esp. on time-nus). And many GPS receivers can be convinced to display GPS system time. So, please don't say "GPS time," because it is ambiguous. But please also don't suggest that when people say "GPS time" they must mean "GPS system time," because they rarely do and it's just an unnecessary bit of confusion. --jhawk@mit.edu John Hawkinson
CA
Chris Albertson
Fri, Aug 4, 2017 6:28 PM

On Fri, Aug 4, 2017 at 7:39 AM, Chris Wilson chris@chriswilson.tv wrote:

Thanks  to  everyone  for the replies, so basically would you say that
with  a permanent internet connection I should forget using GPS time to
set  the  PC  clock  and  just use Meinberg or NTP (which is what I am
currently using and seems to work just fine)?

You'd be using the same NTP software in either case.  The difference
is it you were to add a GPS reference clock to the current setup.
Even with GPS you's till want to keep the internet based reference
clocks.

Currently your PC clock might be accurate that the few milliseconds
level.  Adding a GPS receiver into the mix will improve accuracy to
the tens of microseconds level.  You'd gain abut two orders of
magnitude over the current setup.

Do you need this?  I can think of uses for a highly accurate clock in
amateur radio.  Perhaps you are measuring propagation delay.  Doing
this 100 times more accurately might be helpful.    On the other hand
maybe you only need log files time stamps to be with a second or so of
correct?    When I got into this may application was pointing
telescopes and measuring the light from variable stars.    Usually you
can start with you application and work backwards to place a
requirement on time accuracy

On the other hand this is a "time nuts" list and some people here just
want the BEST they can get.

I'm not a fan of Meinberg because of the way they market freely
available software.

--

Chris Albertson
Redondo Beach, California

On Fri, Aug 4, 2017 at 7:39 AM, Chris Wilson <chris@chriswilson.tv> wrote: > > Thanks to everyone for the replies, so basically would you say that > with a permanent internet connection I should forget using GPS time to > set the PC clock and just use Meinberg or NTP (which is what I am > currently using and seems to work just fine)? You'd be using the same NTP software in either case. The difference is it you were to add a GPS reference clock to the current setup. Even with GPS you's till want to keep the internet based reference clocks. Currently your PC clock might be accurate that the few milliseconds level. Adding a GPS receiver into the mix will improve accuracy to the tens of microseconds level. You'd gain abut two orders of magnitude over the current setup. Do you need this? I can think of uses for a highly accurate clock in amateur radio. Perhaps you are measuring propagation delay. Doing this 100 times more accurately might be helpful. On the other hand maybe you only need log files time stamps to be with a second or so of correct? When I got into this may application was pointing telescopes and measuring the light from variable stars. Usually you can start with you application and work backwards to place a requirement on time accuracy On the other hand this is a "time nuts" list and some people here just want the BEST they can get. I'm not a fan of Meinberg because of the way they market freely available software. -- Chris Albertson Redondo Beach, California
TS
Tim Shoppa
Fri, Aug 4, 2017 7:44 PM

I'm all for building NTPD from source (as a former refclock developer).

But for those not building from source and wanting to install on Windows,
Meinberg NTPD's self-installing package is very easy and does everything
right.

They distribute this for free. I think they've done a great service. And
having real NTPD is so much superior to the many poor quality commercial
programs out there that a newbie might otherwise install.

Tim N3QE

On Fri, Aug 4, 2017 at 2:28 PM, Chris Albertson albertson.chris@gmail.com
wrote:

On Fri, Aug 4, 2017 at 7:39 AM, Chris Wilson chris@chriswilson.tv wrote:

Thanks  to  everyone  for the replies, so basically would you say that
with  a permanent internet connection I should forget using GPS time to
set  the  PC  clock  and  just use Meinberg or NTP (which is what I am
currently using and seems to work just fine)?

You'd be using the same NTP software in either case.  The difference
is it you were to add a GPS reference clock to the current setup.
Even with GPS you's till want to keep the internet based reference
clocks.

Currently your PC clock might be accurate that the few milliseconds
level.  Adding a GPS receiver into the mix will improve accuracy to
the tens of microseconds level.  You'd gain abut two orders of
magnitude over the current setup.

Do you need this?  I can think of uses for a highly accurate clock in
amateur radio.  Perhaps you are measuring propagation delay.  Doing
this 100 times more accurately might be helpful.    On the other hand
maybe you only need log files time stamps to be with a second or so of
correct?    When I got into this may application was pointing
telescopes and measuring the light from variable stars.    Usually you
can start with you application and work backwards to place a
requirement on time accuracy

On the other hand this is a "time nuts" list and some people here just
want the BEST they can get.

I'm not a fan of Meinberg because of the way they market freely
available software.

--

Chris Albertson
Redondo Beach, California


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.

I'm all for building NTPD from source (as a former refclock developer). But for those not building from source and wanting to install on Windows, Meinberg NTPD's self-installing package is very easy and does everything right. They distribute this for free. I think they've done a great service. And having real NTPD is so much superior to the many poor quality commercial programs out there that a newbie might otherwise install. Tim N3QE On Fri, Aug 4, 2017 at 2:28 PM, Chris Albertson <albertson.chris@gmail.com> wrote: > On Fri, Aug 4, 2017 at 7:39 AM, Chris Wilson <chris@chriswilson.tv> wrote: > > > > > Thanks to everyone for the replies, so basically would you say that > > with a permanent internet connection I should forget using GPS time to > > set the PC clock and just use Meinberg or NTP (which is what I am > > currently using and seems to work just fine)? > > You'd be using the same NTP software in either case. The difference > is it you were to add a GPS reference clock to the current setup. > Even with GPS you's till want to keep the internet based reference > clocks. > > Currently your PC clock might be accurate that the few milliseconds > level. Adding a GPS receiver into the mix will improve accuracy to > the tens of microseconds level. You'd gain abut two orders of > magnitude over the current setup. > > Do you need this? I can think of uses for a highly accurate clock in > amateur radio. Perhaps you are measuring propagation delay. Doing > this 100 times more accurately might be helpful. On the other hand > maybe you only need log files time stamps to be with a second or so of > correct? When I got into this may application was pointing > telescopes and measuring the light from variable stars. Usually you > can start with you application and work backwards to place a > requirement on time accuracy > > On the other hand this is a "time nuts" list and some people here just > want the BEST they can get. > > I'm not a fan of Meinberg because of the way they market freely > available software. > > > -- > > Chris Albertson > Redondo Beach, California > _______________________________________________ > 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. >
CC
Chris Caudle
Fri, Aug 4, 2017 10:15 PM

On Fri, August 4, 2017 9:39 am, Chris Wilson wrote:

Thanks  to  everyone  for the replies, so basically would you say that
with  a permanent internet connection I should forget using GPS time to
set  the  PC  clock  and  just use Meinberg or NTP (which is what I am
currently using and seems to work just fine)?

I think you asked the wrong question, so you got the question to the
answer you asked and not what you wanted to know.

You asked whether Lady Heather can set PC time, the answer is yes but it
is a crude way to set the time.

What you really wanted to know is how to get time from a GPS receiver into
the PC, and the answer to that is that gpsd has a driver that can
communicate with a Thunderbolt (Palisade driver), and gpsd also knows how
to communicate with a Thunderbolt.  So use ntp directly to communicate
with the Thunderbolt.  Lady Heather is an awesome program for doing lots
of things with a Thunderbolt, but disciplining the system clock to follow
the GPS receiver is not really one of those things.

--
Chris Caudle

On Fri, August 4, 2017 9:39 am, Chris Wilson wrote: > Thanks to everyone for the replies, so basically would you say that > with a permanent internet connection I should forget using GPS time to > set the PC clock and just use Meinberg or NTP (which is what I am > currently using and seems to work just fine)? I think you asked the wrong question, so you got the question to the answer you asked and not what you wanted to know. You asked whether Lady Heather can set PC time, the answer is yes but it is a crude way to set the time. What you really wanted to know is how to get time from a GPS receiver into the PC, and the answer to that is that gpsd has a driver that can communicate with a Thunderbolt (Palisade driver), and gpsd also knows how to communicate with a Thunderbolt. So use ntp directly to communicate with the Thunderbolt. Lady Heather is an awesome program for doing lots of things with a Thunderbolt, but disciplining the system clock to follow the GPS receiver is not really one of those things. -- Chris Caudle
MB
Martin Burnicki
Sat, Aug 5, 2017 11:01 AM

Chris,

Chris Albertson wrote:

I'm not a fan of Meinberg because of the way they market freely
available software.

I'm sorry you feel this way.

We at Meinberg have supported the NTP project for many years, by
donations of money and hardware, testing, submitting bug reports and
patches. There've been also enhancements like the initial leap second
handling code in the Windows port of ntpd, workarounds for limitations
in Windows to increase the possible accuracy under Windows, etc.

Quite some years ago there was no easy way to install ntpd under
Windows, so one of my colleagues had the idea to put a GUI setup program
together which makes installation under Windows as simple as possible
even for inexperienced users.

When we started this, we also discussed with the other NTP developers
and agreed that we would and should provide the installer via the
Meinberg download page, where we clearly say that the setup program
provides a precompiled version built from the public source code that is
available at ntp.org.

The installer is also free of charge, and there are no duties implied by
using it.

So once more, I feel sorry that you have such a bad feeling about this,
which has just been introduced to make NTP more popular even for users
who are not time nuts.

If you know how to do it you can still build your own binaries from the
original source code.

Martin

(who is biased since working at Meinberg)

Chris, Chris Albertson wrote: > I'm not a fan of Meinberg because of the way they market freely > available software. I'm sorry you feel this way. We at Meinberg have supported the NTP project for many years, by donations of money and hardware, testing, submitting bug reports and patches. There've been also enhancements like the initial leap second handling code in the Windows port of ntpd, workarounds for limitations in Windows to increase the possible accuracy under Windows, etc. Quite some years ago there was no easy way to install ntpd under Windows, so one of my colleagues had the idea to put a GUI setup program together which makes installation under Windows as simple as possible even for inexperienced users. When we started this, we also discussed with the other NTP developers and agreed that we would and should provide the installer via the Meinberg download page, where we clearly say that the setup program provides a precompiled version built from the public source code that is available at ntp.org. The installer is also free of charge, and there are no duties implied by using it. So once more, I feel sorry that you have such a bad feeling about this, which has just been introduced to make NTP more popular even for users who are not time nuts. If you know how to do it you can still build your own binaries from the original source code. Martin (who is biased since working at Meinberg)
AK
Attila Kinali
Sat, Aug 5, 2017 1:19 PM

On Sat, 5 Aug 2017 13:01:56 +0200
Martin Burnicki martin.burnicki@burnicki.net wrote:

Chris Albertson wrote:

I'm not a fan of Meinberg because of the way they market freely
available software.

I'm sorry you feel this way.

We at Meinberg have supported the NTP project for many years, by
donations of money and hardware, testing, submitting bug reports and
patches. There've been also enhancements like the initial leap second
handling code in the Windows port of ntpd, workarounds for limitations
in Windows to increase the possible accuracy under Windows, etc.

I have to second Martin here. Meinberg made ntp on windows a thing.
Before them, it took a lot of effort to get it working (if you ever
got that far). Also, Meinberg is one of the few companies out there
who finance the development of ntp through the network time foundation.

I also do not see how Meinberg "markets" ntp. If putting it on their
webpage, free of charge with lots of explanation what it is, where
it comes from and how to use it properly is marketing, then yes.
But then time-nuts is marketing Microsemi 5071s and Trimble Thunderbolts.

		Attila Kinali

--
You know, the very powerful and the very stupid have one thing in common.
They don't alters their views to fit the facts, they alter the facts to
fit the views, which can be uncomfortable if you happen to be one of the
facts that needs altering.  -- The Doctor

On Sat, 5 Aug 2017 13:01:56 +0200 Martin Burnicki <martin.burnicki@burnicki.net> wrote: > Chris Albertson wrote: > > I'm not a fan of Meinberg because of the way they market freely > > available software. > > I'm sorry you feel this way. > > We at Meinberg have supported the NTP project for many years, by > donations of money and hardware, testing, submitting bug reports and > patches. There've been also enhancements like the initial leap second > handling code in the Windows port of ntpd, workarounds for limitations > in Windows to increase the possible accuracy under Windows, etc. I have to second Martin here. Meinberg made ntp on windows a thing. Before them, it took a lot of effort to get it working (if you ever got that far). Also, Meinberg is one of the few companies out there who finance the development of ntp through the network time foundation. I also do not see how Meinberg "markets" ntp. If putting it on their webpage, free of charge with lots of explanation what it is, where it comes from and how to use it properly is marketing, then yes. But then time-nuts is marketing Microsemi 5071s and Trimble Thunderbolts. Attila Kinali -- You know, the very powerful and the very stupid have one thing in common. They don't alters their views to fit the facts, they alter the facts to fit the views, which can be uncomfortable if you happen to be one of the facts that needs altering. -- The Doctor