It seems odd that the Garmin receiver got it wrong. The Garmin GPS-20 and
-25, which I think are both older than the 18x, get it correct. The GPS-20
is so old it is a single-channel receiver, the GPS-25 is 12-channel but
still 5 V power.
GPS-20, June 1998:
Hi. I'm pretty new to time nuts. I'm pretty much a novice, but a novice in
training. I subscribed to this group because I had reviewed pertinent
information that was being shared, and I appreciate the acceptance. I'm not
sure I can be of much immediate help to any others, but perhaps
dave.martind...@gmail.com said:
It seems odd that the Garmin receiver got it wrong. The Garmin GPS-20 and
-25, which I think are both older than the 18x, get it correct.
I haven't played with the -20 or -25, but I have -18 (no x) as well as -18x.
It's easy to tell the -18 from the -18x just
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
Hal Murray hmur...@megapathdsl.net wrote:
Internally, Linux (and most other modern OSes) use UTC. The API doesn't
include the TAI offset. There is no way to talk about the extra second.
See adjtimex(2) for a description of the leap second API.
Tony.
--
f.anthony.n.finch d...@dotat.at
Hi all;
I have a Precision Standard Time Model 1020 that I have been playing with for
the last few weeks, BTW I'm looking for a manual for it to scan or copy I will
pay round trip shipping, so here's how it behaved at the leap second.
This is a clock that strips the 100 hz time code to
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
Hi
You don’t *have* to go to the “many days” approach if that’s beyond the
accuracy you require.
You *can* go there if you need to. If you don’t have a GPSDO (or something
similar) it may not
make much sense to go quite that far.
Even with less accurate sources, the same approach still
Hi
On Jul 2, 2015, at 12:19 AM, Mary Crowson crowson@sbcglobal.net wrote:
Hi. I'm pretty new to time nuts. I'm pretty much a novice, but a novice in
training. I subscribed to this group because I had reviewed pertinent
information that was being shared, and I appreciate the
Guys,
We tested the recent firmware updates for the JLT products, and they
correctly output the 23:59:60 time stamp, this firmware even outputs the
correct leapsecond timing if GPS signals are totally lost and the GPSDO is
in GPS-holdover mode during the actual event. We recorded a video of the
Gang,
You will remember a few years ago I had problems with my DATUM
9390-52054 GPS Time Code and Frequency Standards. For those that
were not involved at the time but might be curious about the history
of my grief with these units, I have included one of my epistles for
background purposes
On Wed, June 24, 2015 4:54 pm, Neil Schroeder wrote:
Better late (reply) than never?
Main question: if I want to isolate the quiet and noisy power
supplies, or just supply them differently, can they share a
common return?
All conductors have resistance and inductance. Any current flowing on
On Wed, July 1, 2015 11:19 pm, Mary Crowson wrote:
Finally, for now, does anybody have any recommendations as
to how I could, in an affordable manner, without spending
$350+ on a new GPS antenna combiner, combine the signals
for these four GPS antennas
There is no such thing as a GPS antenna
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
Greetings to all timekeepers,
Using a Trimble Thunderbolt and Lady Heather I created a short video
of the recent leap second event and put it on UTUBE which documents this
event.
I viewed ...58..59..60..00..01..
You can watch it here:
Greetings to all timekeepers,
Using a Trimble Thunderbolt and Lady Heather I created a short video of the
recent leap second event and put it on UTUBE which documents this event.
I viewed ...58..59..60..00..01..
You can watch it here:
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.
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
18 matches
Mail list logo
