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
Discussion and questions about Cumulus weather station software version 1. This section is the main place to get help with Cumulus 1 software developed by Steve Loft that ceased development in November 2014.
The wiki was incorrect (I've amended it). Cumulus always recreates the wxnow.txt file once a minute (not every 10 seconds) and there is no option to disable this. Is it causing you a problem?
steve wrote:The wiki was incorrect (I've amended it). Cumulus always recreates the wxnow.txt file once a minute (not every 10 seconds) and there is no option to disable this. Is it causing you a problem?
Thanks.
My mistake, I thought cumulus was writing to this file every 10 seconds.
It is not causing any problem, except that cumulus.exe is doing (reading and/or writing) something every 10 seconds with my harddisk. It is keeping the disk form falling to sleep, that is all.
Since I am logging only once every hour I was wondering what happens every 10 seconds and then I only found the wxnow.txt file that had a recent timestamp.
Cumulus will write to the disk quite frequently just after it starts, but after a few minutes I can't think of anything that would cause it to write anything at less than one minute intervals (unless you were using realtime uploads etc, of course).
If the reading means that a high or low is exceeded (for today, for example) then a disk write will occur. I can't think of any other reason for a disk write when the data is read.
I've put an ini-file option in the next build to turn off creating wxnow.txt, by the way.
I supose it has something to do with the very bad weather currently here in the Netherlands.
With Procmon from sysinternals I was able to see it was writing a lot (almost every ten seconds) to the today.ini file.
After a while cumulus.exe only wrote to the wxnow.txt once per minute and did something on the debug.log file:
Maybe you can have a look at the debug.log, since I did not have the debug option on and still cumulus.exe is doing something on the debug.log as you can see in the log above.
The debug log is beyond my control, I'm afraid. It's not supposed to do anything with the file when it's turned off, and it would require large-scale changes to Cumulus to use something else.
steve wrote:The debug log is beyond my control, I'm afraid. It's not supposed to do anything with the file when it's turned off, and it would require large-scale changes to Cumulus to use something else.