> The DCF77 only produces one timestamp each minute, so there really isn't a
> big push for data reduction compared to NMEA's timestamp each second. I'd
> really like to record the timestamp as received since it'll be useful in
> case there's a problem with reception you can easily determine if it
Hal Murray writes:
> strom...@nexgo.de said:
>> Like the NMEA clock: day, time of day, clock ID, timecode (optionally maybe
>> the decoded time and flags from the timecode).
>
> There are two approaches to logging clockstats info.
>
> As background, the assumption is that you don't want to log eve
strom...@nexgo.de said:
> Like the NMEA clock: day, time of day, clock ID, timecode (optionally maybe
> the decoded time and flags from the timecode).
There are two approaches to logging clockstats info.
As background, the assumption is that you don't want to log everything.
You can log stuff
Gary E. Miller writes:
> Each refclock writes a different style clockstats. So tell us what you
> would like logged.
Like the NMEA clock: day, time of day, clock ID, timecode (optionally maybe the
decoded time and flags from the timecode).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron
Yo Achim!
On Sun, 19 Feb 2017 13:18:12 +0100
Achim Gratz wrote:
> It seems that the generic clock driver doesn't log into clockstats.
> The GPS NMEA driver on the other hand does. If there's a flag or
> configuration option to enable that seperately, I've not found it.
> I'm not sure if that wa
It seems that the generic clock driver doesn't log into clockstats. The
GPS NMEA driver on the other hand does. If there's a flag or
configuration option to enable that seperately, I've not found it. I'm
not sure if that was ever working, however I think it should be fixed
anyway.
Regards,
Ac
