WMR200 Data retrieve fails sometimes during history download

[docinfo57]

Hi,
I often (once a month) notice that data fails to retrieve during history download.

My weather station information, when I ask "datalogger day rest", is according to the amount of data history in memory.

1) Sometimes CumuluxMX loops and I have to reset the weather station memory for going further, loosing my history data

2) Sometimes, looks like it's taking data, update dayfile the correct way, but not Monthly logs !

3) Sometimes, like In the join debug log, everything was OK since line 1670850, then it starts to ignored history data and finish with a Day reset required (line 1671217), clearing further data in the memory of the station without asking

I observed this behavior since january 2017, when I started to use CumuluxMX in several release versions.

Before, I used to use EasyWeather and I never notice such problems. I switch to CumulusMX for sending weather station informations on APRS.

If you could take a look at the routine wich import history data and secure it, that would be nice. I initially think this could be a timeout error, but the log doesn't show this...
And please, never clearing data in Weather station without asking !

I've noticed that retrieving several days of data (1/mn, 3600/day ) from the weather station is quite long. Perhaps due to reading/deleting for each record individualy.
During this period, which may take several minutes, new datas of the weather station are lost !

Is'nt possible to read all the history data, and at the end, asking for delete, with the possibility of checking the importation in the MonthLog, before confirmation ?
Perhaps through a beta option ?

Thanks and for you work.

Dominique

[mcrossley]

Let us be clear about one thing at the start, Cumulus MX does not at any point "clear" the log data from the WMR200.

You have 1 minute logging enabled.

From the log file, it starts reading the logger at 08:21:20, and the first log entry returned is for 27/08/21 22:14

Each record read takes about 0.29 seconds (the WMR200 uses a pretty inefficient transfer protocol - sending one byte per 9 byte USB message!)

MX reads 12,129 records, which takes it up to 05/09/21 11:19
The WMR can hold up to 27,000 history records I believe, which equates to just over 18 days at 1 minute logging.

The last logger record is read at 09:20:54

CMX then requests the next log record and receives a Temperature packet followed by a Status packet etc. In other words the WMR200 has switched from logger download mode to normal "live" operation.

Further calls to download log data are ignored, so I assume the WMR has no more data.

Questions:

1. You have not run Cumulus MX against your WMR200 since 27/08/21 @ 22:14?

That is an awful long time with one minute logging. I'd recommend that you restrict the CMX downtime to shorter periods.

2. No other program was reading the "live" WMR data between 05/09/21 and yesterday?

[mcrossley]

Also, please read the notes Steve made originally about the WMR200 - viewtopic.php?p=44096

* WMR200 is SLOW reading the logger
* WMR200 cannot provide "live" data, and log data at the same time
* CMX cannot process "live" data whilst it is processing historic data

[docinfo57]

Hi,
Thank's for your clarifying previous messages.

I'm sorry, but the problem persists. Based on the remaining days on the station display, there is data in memory.
Looks like the playback is looping on a date error.

The time and date of the station are correct.

Debug logs in attached file.

Thanks. Dominique

[mcrossley]

The log shows that your station is returning empty logger records. They just contain the history record header and a checksum. All the data is zeros.

Code: Select all

D2 2A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FC 00

[docinfo57]

Hello,

Perhaps a problem within the procedure wich extract informations ?

Otherwise, how can you explain that days memory remaining, pass from 16 to 29 days when I reset memory on the station ?

Tks. Dominique

[mcrossley]

MX just asks for logger data, the console then sends everything it has.
After MX receives 50 invalid messages it gives up and starts reading the live data. That will probably have left unread data in the logger.