Steve:steve wrote: While determining the 'station clock' time, it presumably read the data on the 'sensor clock' interval. I suppose I could try to make it avoid doing that, but that then has the potential to miss a 'station clock' change and have to wait for the next one. I don't know if that's what pywws does.
And it seems to me that there's always going to be the chance of hitting the station clock change while determining the sensor clock time, and I don't think there's any way around that.
Also, it looks like your sensor clock is drifting by six seconds a day, and your station clock by four seconds a day, and I don't currently have any code in to cater for that (a drift of more than three seconds):
A few questions for you (clarifications really)
- Station clock is the console, correct?
- Sensor clock is the clock on the sensor array, correct?
- In your opinion (since you have experience with a wide variety of systems) is that drift considered really bad? Should I see if I can return it for a replacement?
- Lastly, on the topic of the clock drift - This station is supposed to have a Radio Controlled Clock (RCC) that I thought set the clock based on a signal from an atomic clock somewhere. Maybe it only does it so often?
Thank you so much for your work and help on this. My postings are only intended to help you improve Cumulus. It is a great piece of software.