Gary pointed out:
> Just about every refclock has their own way of doing the timestamp.
The problem is that things like refclock_process_offset() take l_fp as
arguments. We can add wrappers that use timespec, convert to l_fp, then call
the old code or the reverse depending on the order we do t
Yo Hal!
On Wed, 26 Apr 2017 15:43:00 -0700
Hal Murray wrote:
> > So you start with two l_fp, or two timespec(64), or one of each.
> > Then subtract to get an offet as a timespec(64) or a double.
>
> My expectation is that timestamps would never leave the front end.
> The subtracts and pivot
> Let's use timestamp and offset.
Good suggestion. Thanks.
> But I'm OK with doubles for offsets. If the offset is into many years the
> nanosec will take care of themselves later.
Ahh. Good.
> So you start with two l_fp, or two timespec(64), or one of each. Then
> subtract to get an offet
Gary E. Miller via devel writes:
> Thanks, but I'm more interested in the temp/freq logging program.
When it's cleaned up…
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#Kom
Yo Achim!
On Wed, 26 Apr 2017 22:45:22 +0200
Achim Gratz via devel wrote:
> Gary E. Miller via devel writes:
> > Yes, I remember your descriptions, what I'm asking for is code.
> > reuseable code.
>
> Have at it.
Thanks, but I'm more interested in the temp/freq logging program.
RGDS
GARY
--
Gary E. Miller via devel writes:
> Yes, I remember your descriptions, what I'm asking for is code. reuseable
> code.
Have at it. The datafile (joined.txt) has the UTC timestamp, PPS
offset, temperature (sampled each second right after the PPS pulse and
averaged over 5min or 300 samples), NTP tim
Yo Achim!
On Wed, 26 Apr 2017 22:20:17 +0200
Achim Gratz via devel wrote:
> Gary E. Miller via devel writes:
> >> What exactly do you suggest to replace it with?
> >
> > Timespec with time64_t.
>
> Is that POSIX yet?
Nope. There is no generic standardized solution yet. Until an
OS gives
Achim said:
>> USB would be good enough so you don't actually need a second PC.
> Is the driver code actually looking whether it has an actual serial device?
> At least the generic driver should not care and you could just replace the
> device with a FIFO and feed the data in from your simulator.
Yo Hal!
On Wed, 26 Apr 2017 13:12:48 -0700
Hal Murray via devel wrote:
> Achim said:
> <> I think that should be rejected in favor of eliminating l_fp
> except at the
> >> very edge and doing the pivot at the edge.
> > What exactly do you suggest to replace it with?
>
> There are two uses
Gary E. Miller via devel writes:
>> What exactly do you suggest to replace it with?
>
> Timespec with time64_t.
Is that POSIX yet?
> As Linux 64-bit uses now for native time. Then
> the timestamp arithmetic does not lose precision and the first time64_t
> rollover is centuries from now.
I'm not
Achim said:
<> I think that should be rejected in favor of eliminating l_fp except at the
>> very edge and doing the pivot at the edge.
> What exactly do you suggest to replace it with?
There are two uses for l_fp: time and offset.
By pushing it to the edge, we eliminate uses as time.
I would
This blog post will be about GPS receiver firmware pivoting issues and
about GPS system 1024 week era wrapping issues.
There will be another different blog post about about NTP era wrapping and
pivoting
Analysis of the time_t wrapping is getting too far out of our remit, and
other people have alr
Yo Achim!
On Wed, 26 Apr 2017 21:59:32 +0200
Achim Gratz via devel wrote:
> Hal Murray via devel writes:
> > devel@ntpsec.org said:
> >> Work item: Replace
> >> typedef uint64_t l_fp;
> >> with
> >> typedef uint64_t l_fp_time;
> >> typedef int64_t l_fp_offset;
> >
> > I think that sho
Yo Achim!
On Wed, 26 Apr 2017 21:43:03 +0200
Achim Gratz via devel wrote:
> Gary E. Miller via devel writes:
> > Cool. Did you use ntpheat?
>
> No, I've simply extended the Perl script that logs all PPS timestamps
> (this also ensures that all the measurements are aligned with the
> loopsta
Hal Murray via devel writes:
> devel@ntpsec.org said:
>> Work item: Replace
>> typedef uint64_t l_fp;
>> with
>> typedef uint64_t l_fp_time;
>> typedef int64_t l_fp_offset;
>
> I think that should be rejected in favor of eliminating l_fp except at the
> very edge and doing the pivot at the
Yo Hal!
On Wed, 26 Apr 2017 12:43:20 -0700
Hal Murray via devel wrote:
> ntpq needs to be able to show the EPOCH a server is using.
BUILD_EPOCH, UNIX_EPOCH and NTP_EPOCH.
Just more system variable to add to mode 6.
RGDS
GARY
Hal Murray via devel writes:
> fallenpega...@gmail.com said:
>> How hard is it to write a fake NMEA device simulator in Python, and use
>> Linux IPC control magic to have it appear at a fake serial device?
>
> I don't know anything about IPC, but I do know how to connect 2 PCs with a
> crossover
NB typo: It's lfptofloat rather than lfpfloat
(I'm leaving the subject un-fixed to help mail archives)
Gary said:
> It needs to be pivoted earlier. When you put a timestamp l_fp into a double
> you lose too much precision. Only l_fp offsets should be converted to
> doubles.
Looks like Gary is
Gary E. Miller via devel writes:
> Cool. Did you use ntpheat?
No, I've simply extended the Perl script that logs all PPS timestamps
(this also ensures that all the measurements are aligned with the
loopstats).
>> I still have to add an integral
>> term to the control loop in order to make the
Eric S. Raymond writes:
> We can't fix *that*, either. All we can do is add a warning to the man pages
> for NMEA-related drivers that if your GPS is older than 1024 weeks you may be
> cruising for a bruising. I think I'll go do that.
Well, the more I think about it, I'd say we should rip out an
Yo Hal!
On Wed, 26 Apr 2017 00:13:03 -0700
Hal Murray via devel wrote:
> Eric said:
> > Work item: The lfpfloat() function in the Python interface may be
> > dispensible. Convert the hex literal to float and divide by 1<<32
> > to scale to seconds since the NTP epoch.
>
> It also needs to do
Yo Hal!
On Wed, 26 Apr 2017 11:50:56 -0700
Hal Murray wrote:
> Gary said:
> >> and/or
> >> how does the first step get turned into the right size double
> >> without a pivot and/or where does that pivot happen?
> > Unrelated to this issue. That happens in ntpd/ntp_loopfilter.c So a
> > questi
Yo Hal!
On Wed, 26 Apr 2017 00:40:52 -0700
Hal Murray wrote:
> > Manual config
>
> Did you enable this for all senders or only selected domains?
ALL senders, not an option by sender.
> > This ir a consequence of SPF. A lot of devel@ email is bunced as
> > undeliverable. You have seem this
Gary said:
>> and/or
>> how does the first step get turned into the right size double without
>> a pivot and/or where does that pivot happen?
> Unrelated to this issue. That happens in ntpd/ntp_loopfilter.c So a question
> for another thread. Let's not continue to get lost bouncing around.
Tha
Yo Hal!
On Wed, 26 Apr 2017 11:26:42 -0700
Hal Murray via devel wrote:
> Unix/POSIX has the same problem with time_t
> It rolls over into the sign bit in 2038
Only for some. Not an issue with 64 bit Linux.
RGDS
GARY
---
G
Yo Hal!
On Wed, 26 Apr 2017 00:52:27 -0700
Hal Murray wrote:
> > Different code path.
>
> OK, I'm missing something.
Many people are. We jus tnot sure which ones. :-)
> Eric restored the pivot code that we don't like to step_systime()
Yes.
> How does the first step happen without going
Mark Atwood said:
> I'm going to work it into a blog post. Anyone with a good grasp of the GPS
> rollover issues is invited to work on it as well.
It's not just a GPS issue.
Unix/POSIX has the same problem with time_t
It rolls over into the sign bit in 2038
NTP packet format has the same probl
Yo Hal!
On Wed, 26 Apr 2017 03:33:14 -0700
Hal Murray via devel wrote:
> [What packet types do we support?]
>
> man ntp.conf says:
>peer
>NTP peer mode has been removed for security reasons. peer
> is now just an alias for the server keyword. See above.
>
> It's not clear w
Hi!
I just created blog/_drafts/gps-pivot.ad
It's a lightly edited transcript of a conversation about GPS rollover and
pivoting.
I'm going to work it into a blog post. Anyone with a good grasp of the GPS
rollover issues is invited to work on it as well.
Thanks!
..m
--
Mark Atwood
http://abou
Hal Murray :
> [What packet types do we support?]
>
> man ntp.conf says:
>peer
>NTP peer mode has been removed for security reasons. peer is now
>just an alias for the server keyword. See above.
>
> It's not clear what "has been removed" means. Just the server set
[What packet types do we support?]
man ntp.conf says:
peer
NTP peer mode has been removed for security reasons. peer is now
just an alias for the server keyword. See above.
It's not clear what "has been removed" means. Just the server setup command
or support for t
Trevor N. via devel :
> I have a device that will rollover after week 1998 (in 2018) that I
> just tested with a GPS simulator set to 2 years in the future,
> attached to ntpd classic with a +2 year offset in get_ostime (and
> "disable ntp" in conf) and ntpcal_get_build_date() of 2016. The
> 512-w
Hal Murray :
>
> Eric said:
> > Possible work item (me): Change Mode 6 so it no longer ships system status
> > bits in hex, decoding them into a string token list instead, old behavior
> > preserved under ENABLE_CLASSIC_MODE. This is because the PLL* definitions
> > aren't guaranteed to be consist
Hal Murray :
>
> I don't think they are right. I get occasional timeouts/crashes but haven't
> had time to investigate. Possibly the logic is correct and we need to bump
> the retry count.
>
> Has anybody else noticed troubles?
I have never seen this problem.
--
http://www.c
Hal Murray :
>
> devel@ntpsec.org said:
> > Work item: Replace
> > typedef uint64_t l_fp;
> > with
> > typedef uint64_t l_fp_time;
> > typedef int64_t l_fp_offset;
>
> I think that should be rejected in favor of eliminating l_fp except at the
> very edge and doing the pivot at the edge.
I need a day or two without distractions (like this) to finish things.
Mostly, get good backoff on the DNS not working case.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/
I don't think they are right. I get occasional timeouts/crashes but haven't
had time to investigate. Possibly the logic is correct and we need to bump
the retry count.
Has anybody else noticed troubles?
--
These are my opinions. I hate spam.
> Different code path.
OK, I'm missing something.
Eric restored the pivot code that we don't like to step_systime()
How does the first step happen without going through there? and/or how does
the first step get turned into the right size double without a pivot and/or
where does that pivot hap
Thanks.
> Manual config
Did you enable this for all senders or only selected domains?
> This ir a consequence of SPF. A lot of devel@ email is bunced as
> undeliverable. You have seem this weh your email was removed from devel@
> due to too many bounces.
I thought the normal approach was to
Eric said:
> Work item: The lfpfloat() function in the Python interface may be
> dispensible. Convert the hex literal to float and divide by 1<<32 to scale
> to seconds since the NTP epoch.
It also needs to do a pivot and/or have an option not to pivot.
--
These are my opinions. I hate spam
devel@ntpsec.org said:
> Work item: Replace
> typedef uint64_t l_fp;
> with
> typedef uint64_t l_fp_time;
> typedef int64_t l_fp_offset;
I think that should be rejected in favor of eliminating l_fp except at the
very edge and doing the pivot at the edge.
--
These are my opinions. I ha
Yo Hal!
On Tue, 25 Apr 2017 23:29:23 -0700
Hal Murray wrote:
> What's the deal on this? It's new as of yesterday or today.
Yup.
> Is that a manual configuration step or something that mailman does
> automagically?
Manual config
> Please cc devel and/or other lists as appropriate.
Only app
Eric said:
> Possible work item (me): Change Mode 6 so it no longer ships system status
> bits in hex, decoding them into a string token list instead, old behavior
> preserved under ENABLE_CLASSIC_MODE. This is because the PLL* definitions
> aren't guaranteed to be consistent across different syst
43 matches
Mail list logo
