Problems datalogger Oregon WMR200

[lmmeteo]

Hi Steve

Always turn off my PC every day between 7 and 8 pm and light it the next day very early in the morning.

The problem starts when upgrading from version 1.9.2 (1032) to 1.9.3 (1051), next day morning after turning on the PC the data is received from the charging Datalogger incomplete, buggy or lost.
have returned to version 1.9.2 (1032) and has been presented no problem with the data.

attachment the Diags folder.

[steve]

The only thing I changed between 1032 and 1051 for the WMR200 was to make sure that Cumulus didn't try to talk to the station if Windows said it wasn't connected. Your station seems to be sending a lot of stuff that Cumulus doesn't recognise, and with invalid dates. I don't think this is anything to do with build 1051, it works fine for me, and no-one else has so far reported this type of problem.

Note that the clock in your station appears to be some way ahead of the time on your PC, which will cause lost data.

Please install build 1052, and if you continue to have problems, first try resetting the station, and if you still continue to have problems, turn on the debug log by editing cumulus.ini and adding

logging=1

to the [Station] section. Then start Cumulus. Attach the diags folder and debug.log file when the problem has occurred.

[lmmeteo]

Hi Steve,

I did what you indicated: upgrade to v1.9.3 (1052), restart the station panel and editing cumulus.ini and adding logging=1 to the [Station] section.

Cumulus performed better but has stopped and has shown errors in the last 2 days

The debug.log file is very large, the size now 3.86Gb. (before upgrade 27kb)

attachment the Diags folder, screen error and bugreport.txt

Thanks

[steve]

It looks like your station just stops sending data. I can't say any more without seeing the debug.log file. The crash (the bugreport.txt file) is because the debug.log got too big. You will need to delete it each time you start Cumulus.

[lmmeteo]

Hi Steve,

Datalogger worked OK the last 2 days.

I edited cumulus.ini and delete logging=1 to the [Station] section. Also delete data file debug.log

There have been no further failures and data errors.

Thanks,
grateful!!!

[steve]

That's good. Hopefully the latest build fixed the original problem, and the problems you were getting after that were just the debug log getting too big.