> By the way, the code I am writing is not part of a NTP algorithm to adjust a
> system clock for time. It is for a one-time frequency calibration of an
> oscillator. I take a time snapshot at the beginning and at the end of an
> approximately six hour period during which I am counting cycles
On 05/02/2017 00:22, Robert Scott wrote:
[]
By the way, the code I am writing is not part of a NTP algorithm to
adjust a system clock for time. It is for a one-time frequency
calibration of an oscillator. I take a time snapshot at the beginning
and at the end of an approximately six hour
On 2017-02-05 02:14, David Woolley wrote:
> On 05/02/17 00:22, Robert Scott wrote:
>> I hope to achieve a frequency accuracy of 5 PPM. Once that
>> measurement is made, I store it for subsequent use in my app.
> The equipment doesn't have a very long service life and is in a
> temperature
On 05/02/17 00:22, Robert Scott wrote:
I hope to achieve a
frequency accuracy of 5 PPM. Once that measurement is made, I store
it for subsequent use in my app.
The equipment doesn't have a very long service life and is in a
temperature controlled environment, as I think both ageing and
On Sat, 4 Feb 2017 10:09:11 +, David Woolley
wrote:
>On 03/02/17 23:10, Robert Scott wrote:
>> But with other servers, the first
>> response came back good, the second response came back LI=3, the third
>> and fourth responses never came back at all.
On 03/02/17 23:10, Robert Scott wrote:
But with other servers, the first
response came back good, the second response came back LI=3, the third
and fourth responses never came back at all. (recvfrom() has to be
aborted).
Is this possibly a defense mechanism against a DOS attack?
See
On Fri, 03 Feb 2017 03:15:09 GMT, no-one@notreal.invalid (Robert
Scott) wrote:
>I am writing some parsing code for reading Time Server packets. The
>first 32 bits of the returned packet are:
>
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|LI | VN |Mode |Stratum|