Cumulus Support

Hi all,

At the wiki I read: Although I do not want to upload to the APRS network, cumulus.exe still writes every 10 seconds to the wxnow.txt file in the installation directory.

I use version 1.9.1 and the APRS/CWOP settings (not enabled) are empty in the Internet settings dialog.

Is there a parameter to keep cumulus.exe from writing to wxnow.txt.

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).

At the main window at the bottom at the right, you see "Last data read at: 14:29:50" for example.

This changes every ten seconds.

Every time cumulus reads the data (from the weather station?) it reads or writes my harddisk at that exact moment as well.

Maybe it reads the data from a buffered driver file?

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 think you are right!

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:


15:38:00,9569490 cumulus.exe C:\VIX\CUMULUS\wxnow.txt CreateFile
15:38:00,9574139 cumulus.exe C:\VIX\CUMULUS\wxnow.txt WriteFile
15:38:00,9575334 cumulus.exe C:\VIX\CUMULUS\wxnow.txt CloseFile
15:38:00,9582137 cumulus.exe C:\VIX\CUMULUS\debug.log QueryOpen
15:38:00,9584872 cumulus.exe C:\VIX\CUMULUS\debug.log CreateFile
15:38:00,9585316 cumulus.exe C:\VIX\CUMULUS\debug.log QueryStandardInformationFile
15:38:00,9585517 cumulus.exe C:\VIX\CUMULUS\debug.log QueryStandardInformationFile
15:38:00,9585791 cumulus.exe C:\VIX\CUMULUS\debug.log CloseFile
15:39:01,0194055 cumulus.exe C:\VIX\CUMULUS\wxnow.txt CreateFile
15:39:01,0197226 cumulus.exe C:\VIX\CUMULUS\wxnow.txt WriteFile
15:39:01,0198358 cumulus.exe C:\VIX\CUMULUS\wxnow.txt CloseFile
15:39:01,0205115 cumulus.exe C:\VIX\CUMULUS\debug.log QueryOpen
15:39:01,0207864 cumulus.exe C:\VIX\CUMULUS\debug.log CreateFile
15:39:01,0208314 cumulus.exe C:\VIX\CUMULUS\debug.log QueryStandardInformationFile
15:39:01,0208515 cumulus.exe C:\VIX\CUMULUS\debug.log QueryStandardInformationFile
15:39:01,0208778 cumulus.exe C:\VIX\CUMULUS\debug.log CloseFile
15:40:01,0712479 cumulus.exe C:\VIX\CUMULUS\wxnow.txt CreateFile
15:40:01,0715546 cumulus.exe C:\VIX\CUMULUS\wxnow.txt WriteFile
15:40:01,0716549 cumulus.exe C:\VIX\CUMULUS\wxnow.txt CloseFile
15:40:01,0723315 cumulus.exe C:\VIX\CUMULUS\debug.log QueryOpen
15:40:01,0726050 cumulus.exe C:\VIX\CUMULUS\debug.log CreateFile
15:40:01,0726494 cumulus.exe C:\VIX\CUMULUS\debug.log QueryStandardInformationFile
15:40:01,0726698 cumulus.exe C:\VIX\CUMULUS\debug.log QueryStandardInformationFile
15:40:01,0726967 cumulus.exe C:\VIX\CUMULUS\debug.log CloseFile
[/color]

Thanks for the extra option in the ini.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.

Regards,

Victor

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.

Ok, I understand.

Thanks anyway.