ini file reverts back (in particular data logger)

[leforthomas]

Hi
I have Cumulus MX v.3.0.0 build 3036 running on a raspberry pi. I have an AERCUS WS3803.
Real time runs ok, but I have problems with the catch up- the pi is disconnected at night, but I want to catch up the data from the station at power on.

I have had this working occasionally (after copying the backup data to the data directory) but not systematically, in fact now not at all.

I think the issue is coming from the ini file. After seeing that the settings were often switched back (in particular the DataLogger option) I stopped using the browser based interface for modifying the settings and edited the file directly.

My ini file currently has UseDataLogger=1, but the diagnostic file says data logging is disabled.

Thanks in advance for any feedback!
Jayne

[steve]

My ini file currently has UseDataLogger=1, but the diagnostic file says data logging is disabled.

That's not the same thing.

If you zip up the MXdiags folder and attach it, I'll take a look.

[richard_newberry]

I get that to saying in Mxdiag txt files that its disabled when you first start CumulusMX.

[Hunter362]

I can confirm, if I uncheck data logging via the console, it does indeed stop logging the transfers.
But upon restart, data logging *will* be checked ON once again.

Crap, my bad.... It is the Debug logging that is enabled, even if you turn it off via the console, it is enabled after a restart.
is the default for it to be ON when restarted?

[water01]

I suggest you send Steve the files he asked for otherwise he is unlikely to be able to help.

[steve]

Debug logging and data logging are OFF by default. If you turn them on or off in the UI, that is for the current session only. To change them permanently you edit Cumulus.ini. For debug logging the item is "Logging" and for data logging the item is "DataLogging". A value of zero is off and a value of 1 is on.

These are DIAGNOSTIC settings, they are nothing to do with the normal operation of Cumulus.

The default for collecting the archive data from the logger at start up is ON. The only way to turn this off in MX is to edit Cumulus.ini and set UseDataLogger=0. This is NOT RECOMMENDED, you would need to have a particular reason for doing this. By default Cumulus will always try to download archive data at startup from stations which support archive data, no action is required to enable this. If it doesn't download archive data at startup, then either the user, MX, or the station has done something in error, and the MX diags files will help to diagnose the problem.

The help for the 'data logging' setting in MX is admittedly not very clear. I'll correct this in the next build.

[Hunter362]

Debug logging and data logging are OFF by default. If you turn them on or off in the UI, that is for the current session only. To change them permanently you edit Cumulus.ini. For debug logging the item is "Logging" and for data logging the item is "DataLogging". A value of zero is off and a value of 1 is on.

These are DIAGNOSTIC settings, they are nothing to do with the normal operation of Cumulus.

I misread the first post as to the logging, I thought he was talking about the logging from all the file transfers. I'm self hosting on the same machine, as MX and have it set for 1 min updates, so the log does grow very fast.
Thanks Steve for your work and patience!

[leforthomas]

Thanks for the feedback, I was indeed confused by the two types of data logging.
I have it working now, the problem having nothing at all do with any data logger. Is seems that rebooting the pi without closing cumulus may have been to blame, I have installed the start/stop scripts and now things seem to be more robust.
Thanks!