I occasionally get the odd missing log entry (main data log - eg. Jun21log.txt). Its only the odd line maybe once a month or fewer. Its just a bit of a pain if I need to line up extracted readings against data from other systems that don't lose data.
It seems to almost always be the 04:10 reading (I log every 10 minutes). I can't find anything else that might cause this other than the entry clocksettinghour=4 setting in the cumulus.ini file. I wonder if the system setting the clock perhaps forwards, perhaps backwards at 04:00 cause a missed data log?
Has anyone else ever noticed anything like this?
Welcome to the Cumulus Support forum.
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Missing log entries and clocksettinghour
Moderator: mcrossley
-
- Posts: 220
- Joined: Mon 03 Jan 2011 4:27 pm
- Weather Station: Davis Vantage Pro2
- Operating System: Win 7
- Location: Willand, mid Devon.
- Contact:
- mcrossley
- Posts: 12763
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Missing log entries and clocksettinghour
Setting the console time seems to be a very expensive operation on the console. It becomes unresponsive for quite a long time. That is why CMX only sets the time if it is more than 30 seconds out.