For my next GPSDO board revision, I would like to include one of Tom's PICDiv
devices to give a much better 1PPS out than the Ublox receivers are capable of.
This means that it has to be started (or slewed to be) exactly on time. So I
was wondering if anyone had experimented in controlling
I might have been the one who brought up the problem of the NMEA
message not being right on the UTC send tick. But now I'm thinking
of another problem this might create. It is slightly off topic
because it has to do with location.
Let's say I have a mobile robot (or a self driving car) that
While I was googling for reports of other misbehaving GPS chips, I discovered
the existence of the worlds first leap second enabled wrist watch.
Seiko introduced the Astron models 8X53, 8X82, 7X52 which automatically check
for a leap second on …….
« Seiko Astron enters the leap second data
> Le 20 juil. 2016 à 22:10, Gary E. Miller a écrit :
>
> Yo Martin!
>
> On Wed, 20 Jul 2016 21:37:02 +0200
> Martin Burnicki wrote:
>
>> So when the GPS receiver always just *showed* information on the
>> current UTC data set then this is OK.
To answer about how they get good timing. Many times you run a loop that runs
off a timer at say exact 1000 times per second. Having something like a 1KHz
loop gives very deterministic timing. Lots of ways to do it. One is to run some
RTOS. I had to make all the axis of a machine tool move at
KO4BB.com ran out of disk space.
Apparently the Control Panel indicated I was using 120GB out of 160
available, but it was off by about 40GB...
About 90GB of that are manuals.
A good bit of the extra are duplicate files that resulted from the site
hosting transfer a couple of years ago that
HI
> On Jul 20, 2016, at 7:51 PM, Mark Sims wrote:
>
> I added the ability of Lady Heather to calculate the time offset of the
> timing message from "wall clock" time. It calculates the difference between
> the system clock time to the time that the (end of) the timing
I added the ability of Lady Heather to calculate the time offset of the timing
message from "wall clock" time. It calculates the difference between the
system clock time to the time that the (end of) the timing message arrived.
The result is only as good as your system clock, so the system
Yo Noah!
On Wed, 20 Jul 2016 17:12:14 -0400
Noah wrote:
> First time poster; just subbed. Not a time hobbies the; my team @
> work runs NTP infrastructure. So , that's a brief intro out of the
> way...
Yes, a few of us NTP people here. We are several orders of magnitude
On Wed, Jul 20, 2016 at 09:37:02PM +0200, Martin Burnicki wrote:
> The UTC/leapsecond data sent by the satellites contains the UTC offset
> before and after the leap second event time. This has been 17/17 until
> recently, and is 17/18 now.
>
> The GPS satellites didn't start all at the same time
First time poster; just subbed. Not a time hobbies the; my team @ work runs NTP
infrastructure. So , that's a brief intro out of the way...
Discovered that my commercial GPS appliances opted to *apply* yesterday's
pending leap second, which has made for an interesting day.
--n
>> On Jul 19,
On 7/19/2016 5:09 PM, Pete Lancashire wrote:
> Saw this guy at GoodWill, but they wanted $25 for it so didn't get it.
>
> Model: A11121Z115
>
> http://petelancashire.com/gallery/main.php?g2_itemId=7196
>
> http://petelancashire.com/gallery/main.php?g2_itemId=7200
>
> -pete
>
I got in a Z3812A (aka Lucent KS-24361 REF-0) and installed a Motorola UT+ in
it following the excellent guide by Peter Garde (google is your friend) and
have it working as a standalone GPSDO...basically it now a REF1 unit). The
mod mostly involves moving half a dozen 0 ohm resistors (I
Yes I was looking forward to seeing his "Tria" drop in Oncore replacement but
it looks like he moved on to other projects.
Original message
From: paul swed
Date:07/20/2016 2:08 PM (GMT-05:00)
To: Discussion of precise time and frequency measurement
Jay Grizzard wrote:
> On Tue, Jul 19, 2016 at 11:39:29PM +, Mark Sims wrote:
>> The GPS satellites are now reporting the pending leapsecond...
>>
>> The Z3801A has it messed up... it says the leap will occur on 30 Sep
>> 2016 (73 days). The Z3801A has two different messages that report the
Have not heard from Dan in a while.
I did test various arduinos with his software and it all worked just fine.
The system stability really depended on the quality of the GPS pps used.
Regards
Paul
WB8TSL
On Wed, Jul 20, 2016 at 12:11 PM, Gregory Beat wrote:
> Dan Watson spent
On Tue, Jul 19, 2016 at 11:39:29PM +, Mark Sims wrote:
> The GPS satellites are now reporting the pending leapsecond...
>
> The Z3801A has it messed up... it says the leap will occur on 30 Sep
> 2016 (73 days). The Z3801A has two different messages that report the
> leap day... both are
Dan Watson spent considerable time (2015) on standalone Lucent KS-24361 REF-0
with a "new" GPS board that would be "backward" compatible.
Not sure where he is fir project in 2016 (availability of OSHPark boards).
http://syncchannel.blogspot.com/2015/10/denuo-gps-retrofit-board.html
Sent from iPad
> On Jul 20, 2016, at 12:25 AM, Tom Van Baak wrote:
>
> Hi Gary,
>
>> 2.1 A positive or negative leap-second should be the last second of a UTC
>> month,
>> but first preference should be given to the end of December and June,
>> and second preference to the end of March
My Agilent 53132 power module went bad, does any one have one for sale or
info or schematic.
Thanks Bert Kehren
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow
Gary E. Miller wrote:
> Yo time-nuts@febo.com!
>
> On Tue, 19 Jul 2016 23:18:18 -0700
> Hal Murray , time-nuts@febo.com wrote:
>
>> g...@rellim.com said:
In general there's a common belief that a leap second can only
occur at the end of June or December. This
Magnus,
Magnus Danielson wrote:
> Now, what annoys me is that the IERS message says that the leap second
> is scheduled for January:
>
> 8<---
>
> Paris, 6 July 2016
>
> Bulletin C 52
>
> To
Hi Hal,
I guess you know this but...
> I wasn't considering refclocks to be "core" in that context. Got a better
> word?
> Have you found any similar code that isn't in one of the refclocks?
ntp_loopfilter.c used to have code that restricted the months for
leap seconds. The new core ntpd
On Wed, Jul 20, 2016 at 01:05:59AM -0700, Hal Murray wrote:
> g...@rellim.com said:
> > Yes, I know the problem being solved. Like today, the leap second being
> > broadcast sooner than ntpd expects, so it picks the wrong month.
> Do you know of any ntp servers that have picked the wrong month?
Hal Murray wrote:
> g...@rellim.com said:
>>> I don't think there is anything in the core of ntpd that restricts
>>> leap seconds to Jun/Dec. If there was, it would have filtered out
>>> the above problem.
>> How about this:
>> ntpd/refclock_hpgps.c, line 544:
>
> I wasn't considering refclocks
g...@rellim.com said:
> Yes, I know the problem being solved. Like today, the leap second being
> broadcast sooner than ntpd expects, so it picks the wrong month.
Do you know of any ntp servers that have picked the wrong month?
g...@rellim.com said:
>> I don't think there is anything in the
Hello Michael
> Thinking out loud, I wonder how bad L1-only, post-processed, would be for
> time-nuts use? Especially with a timing-grade antenna (e.g. the common
> Trimble Bullet). Dual frequency is great when your receiver has the potential
> to move, you have to resolve carrier phase
Hi Gary,
> 2.1 A positive or negative leap-second should be the last second of a UTC
> month,
> but first preference should be given to the end of December and June,
> and second preference to the end of March and September.
Sounds correct. The point is to never to hardcode a "preference". You
Yo time-nuts@febo.com!
On Tue, 19 Jul 2016 23:18:18 -0700
Hal Murray , time-nuts@febo.com wrote:
> g...@rellim.com said:
> >> In general there's a common belief that a leap second can only
> >> occur at the end of June or December. This is false. Don't ever
> >> hardcode
Gary,
On 07/20/2016 07:36 AM, Gary E. Miller wrote:
Yo Tom!
IERS is free to schedule a leap second at the end of any month. And
it may be an insert or a delete. Assume nothing more or less in your
code. Code and test and document for positive and negative leap
seconds equally.
Got a
30 matches
Mail list logo