Re: $BASETIME (^T) inaccurate?

I've made some temporary changes to the program to help work on this, namely at program startup it now saves the time of day, UnixUptime, and ^T value. I'll try to observe regularly and see what happens.

Much of the discussion until now has been about how changing the system time could affect this. I assure you, I'm not changing the system time. ntpd could be getting involved, but that would only involve at most, tenths of seconds.

Comment on Re: $BASETIME (^T) inaccurate? Download Code

Replies are listed 'Best First'.
Re^2: $BASETIME (^T) inaccurate? by haukex (Archbishop) on Apr 12, 2023 at 18:04 UTC
I assure you, I'm not changing the system time. ntpd could be getting involved, but that would only involve at most, tenths of seconds. I explained that on a Raspberry Pi, NTP is most definitely involved (if connected to a network), and the time jumps are quite significant. Unless of course you've written your code in a way that it is not started on boot, but waits until the first time the NTP server is queried to start running, but you made no mention of that. You also mention "time of day, UnixUptime, and ^T value" but not the monotonic clock.	[reply]

Replies are listed 'Best First'.

Re^2: $BASETIME (^T) inaccurate?
by haukex (Archbishop) on Apr 12, 2023 at 18:04 UTC

I assure you, I'm not changing the system time. ntpd could be getting involved, but that would only involve at most, tenths of seconds.

I explained that on a Raspberry Pi, NTP is most definitely involved (if connected to a network), and the time jumps are quite significant. Unless of course you've written your code in a way that it is not started on boot, but waits until the first time the NTP server is queried to start running, but you made no mention of that. You also mention "time of day, UnixUptime, and ^T value" but not the monotonic clock.

[reply]