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:
Hi Chuck,
Thanks for the comprehensive list. Very nice work. This bug in many versions of
the HP SmartClock-series has shown up before (but not always in the 90's, see
below). What's going is yet another problem with how developers write code for
leap seconds. It's really hard to get right.
Hi guys.
After several experiments I could discover that the bad ADEV from the two
GPSDO DUT are due to GPS lock losses. This is probably because the antenna is
outside the windows but half the sky is hidden. We can see the on the frequency
plot the sharp change of 0.5Hz and the locking. Good
Hi,
Just a stupid question on Timelab.
Why do I have the plot with 1/4 for the time actually used for the measurement
? I can see that the plot is updated every 4 samples but the scale is not
relevant. The sample interval is correctly set (1s)
Cheers
Stephane
-Message d'origine-
De :
Hi
If you go back in the archives and look for the discussions on “Collins hard
limiter” they will lead you to some other areas to consider when trying to
square low frequency sine wave signals. The quick summary is that you need a
series of bandwidth limited limiter stages ahead of what ever
Bob et Stéphane,
The Collins hard limiter is a fancy squarer circuit.
In short, the Collins hard limiter is what I hinted about in my earlier
message. Rather than hitting the hard limiter of the comparator
directly, with the slew-rate issue I gave.
Collins observed that if you provide a
Bob,
I am relatively new to the list and still learning the jargon and
concepts. You wrote: There does appear to be a D in the TBolt loop.
For what ever reason, that’s not a changeable value. The D does scale
with the time constant.
Could you or one of the other members elaborate on the what is
Hi Stéphane,
have you read W. Riley's paper on a DMTD system?
http://www.wriley.com/A%20Small%20DMTD%20System.pdf
Cheers,
Adrian
Stéphane Rey schrieb:
Hi guys.
After several experiments I could discover that the bad ADEV from the two
GPSDO DUT are due to GPS lock losses. This is probably
Hi
A classic control loop in it’s simplest form has only one term. That is often
referred to as a proportional term. When the control signal (or error) changes
by A the output changes by A times that term. Often in shorthand notation this
term is refereed to as a P term.
The next thing that
Cash,
Typically a PLL loop uses a PI loop-filter, making it a PI-control
system with a steered integrator in the form of the oscillator. Many
other control systems prefer to use the PID controller, and Bob found
that there is a D factor in there.
The factors at hand is:
P = Proportinal
I =
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
More info from Charles (stuck in time-nuts @yahoo @aol prison):
/tvb
- Original Message -
From: Charles Zabilski
To: Tom Van Baak
Sent: Saturday, January 24, 2015 1:52 PM
Subject: Re: 2015 Leap Second
Tom:
Thanks for the update. I got around that problem in later
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
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
Hello Nuts,
I have been playing a bit tuning a Thunderbolt with Lady Heather and now
have more questions than answers. The collective time-nut brain would be
appreciated.
1. Using the '' command I can change the damping and time constant in LH.
Are these values immediately transferred to the TB?
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
I'm seeing the same thing with my TS-2100 - it is one second behind WWV
based on the front panel display. My ET-6000 appears to be in sync.
What's interesting though is that I have a little applet on my iPhone
(NetTime) that connects to nist.time.gov and it is also a second behind.
-Bob
Robert Watzlavick kirjoitti:
I'm seeing the same thing with my TS-2100 - it is one second behind WWV
based on the front panel display. My ET-6000 appears to be in sync.
Ok - then this is verified...
So the only way (for me) is to run this with 1PPS from Thunderbolt. Good
thing is that
Hi
On Jan 23, 2015, at 10:58 PM, Skip Withrow skip.with...@gmail.com wrote:
Hello Nuts,
I have been playing a bit tuning a Thunderbolt with Lady Heather and now
have more questions than answers. The collective time-nut brain would be
appreciated.
1. Using the '' command I can change
Hi
Maybe a bit more information, much of it applies to all GPSDO’s :
The TBolt first goes through a process to get the OCXO roughly on frequency and
to get the PPS approximately aligned. That process is not impacted by the time
constant and damping. The OCXO goes a bit crazy during this
20 matches
Mail list logo
