WMR200 memory management

[JacquesD]

Hi,

I had a question from a French user, about a WMR200 station.

Pc hang from june 22 9am to june 23 11pm. He restart his Pc and Cumulus read station memory
(progress bar and counting numbers appears), but most recent readings are missing (from 2pm to 11pm).

I've found WMR200 manual and it said that with this interval (1 min.), station could store 19 days.
But, it say too that when memory is full, data logger stop storing reading (instead of usual deleting
oldest readings).

Then, I think that is why he lost newest readings, but someone had info about Cumulus memory
management on this station?

Thanks,
Jacques

[steve]

Cumulus has no control over the WMR200 logger, and the logger operates in a completely different way to every other weather station. When Cumulus starts up, the station sends it all the entries it has in its logger, and hopefully these are all the entries needed to fill in the gap since Cumulus was last running.

The station doesn't write entries to its logger all of the time, only when PC software isn't connected. This is kind of clever but kind of stupid at the same time. It sounds to me like the station thought that software was connected during that missing period, which is why it didn't log entries. It's unlikely to be an issue with the memory being full; it has a large memory and it deletes old entries when they are sent to the PC.

If I had the zipped up diags folder I might be able to say more, but it's highly unlikely that the missing data can be retrieved, the station probably doesn't have it.

[mimo57]

Hello,
@Jacques thank you for your post.

@ Steve, I can provide the files before and after the blackout.

Edit: Uploaded files in MP

friendships
Yves

PS: It was not the PC (winXP-sp2) which was planted, but CUMULUS (1032)

[steve]

Edit: Uploaded files in MP

I don't know what that is, sorry. Just zip up the diags folder and attach it to a reply in the forum. If you don't know how to do that, instructions are in the post linked to above 'Please click here before posting'.

[mimo57]

Edit: Uploaded files in MP

I don't know what that is, sorry. Just zip up the diags folder and attach it to a reply in the forum. If you don't know how to do that, instructions are in the post linked to above 'Please click here before posting'.

MP=pm= personal message

[steve]

I've received your private message now

Cumulus apparently stopped working after this point:

22/06/2012 09:10:00.144 : Writing today.ini, LastUpdateTime = 22/06/2012 09:10:00 raindaystart = 366,014007568359 rain counter = 366,014007568359

I have no idea why that happened. Has it done this before?

When you restarted it, the station started sending the missing data:

23/06/2012 23:29:39.250 : History data for: 2012-06-22 09:15

It sent the logger data up to this point:

23/06/2012 23:38:53.468 : History data for: 2012-06-23 14:20

Then it started sending logger data with old timestamps (from January 4th):

23/06/2012 23:38:56.187 : History data for: 2012-01-04 00:16
23/06/2012 23:38:56.187 : Timestamp is earlier than latest data, ignoring
23/06/2012 23:38:56.359 : Packet:D2 31 11 00 04 01 0C 0B 00 00 00 2E 00 43 01 0C 12 0F 0C 0B 0B 0C 23 70 02 9A 01 FF DE 63 F8 33 01 00 21 01 1D 5A 00 52 A1 4B 00 5A 3C 00 00 06 09
23/06/2012 23:38:56.359 : History data for: 2012-01-04 00:17
23/06/2012 23:38:56.359 : Timestamp is earlier than latest data, ignoring
23/06/2012 23:38:56.515 : Packet:D2 31 12 00 04 01 0C 0B 00 00 00 2E 00 43 01 0C 12 0F 0C 0B 0B 0C 23 30 02 9A 01 FF DE 63 F8 33 01 00 21 01 1D 5A 00 52 A1 4B 00 59 3C 00 00 C6 08
23/06/2012 23:38:56.515 : History data for: 2012-01-04 00:18
23/06/2012 23:38:56.515 : Timestamp is earlier than latest data, ignoring

The last logger packet it sent was:

23/06/2012 23:44:01.062 : History data for: 2012-01-04 22:04
23/06/2012 23:44:01.062 : Timestamp is earlier than latest data, ignoring

Hence the gap in the data from 14:20 to 23:44.

[mimo57]

strange data from 04 January 2012.
They represent approximately 22 hours of recording. The DATA LOGGER could not be saturated with so little.
So why there is no data 23-06-2012 23-06-2012 11:45 p.m. 2:20 p.m. to?
Station or badly encoded recording in the DATA LOGGER or when transferring the station to Cumulus, the data are incorrect .. ??? ...

[steve]

Did you have the station running on Jan 4th? I think I'd be tempted to force a clear of the station's memory. I don't know how you do that.

[mimo57]

Did you have the station running on Jan 4th? I think I'd be tempted to force a clear of the station's memory. I don't know how you do that.

Yes, I have data for January 2012 (attachment)

I'll do a reset of the data logger would try and stop a cumulus over 24 hours and see what it gives.

I'll keep you informed.

edit:
Another question, do you have an explanation of the error "FTPRequestDone ftpQuitAsync errno = 500" in the files diags?

[mimo57]

Hi everyone,

I just realized a test on the data logger from my station.
After purging, I stopped for 48 hours in a row cumulus.
The data logger has worked very well, he told me tonight at 18h 17days capacity on 19.
So I can already conclude that this was not an overflow of data logger which I deleted ~ registration 9am the other day.

Certainly there were probably old news that dated from 4-01-2012 in memory, but in view of logs, enough to saturate the memory.

While this has happened, I think it will remain a mystery, but I keep an eye on it, you never know if it starts again. ...

Anyway thank you for having me followed.

PS:Another question, do you have an explanation of the error "FTPRequestDone ftpQuitAsync errno = 500" in the files diags?

friendship
Yves

[steve]

PS:Another question, do you have an explanation of the error "FTPRequestDone ftpQuitAsync errno = 500" in the files diags?

It's an error coming back from your ftp server, presumably complaining that it doesn't like the 'quit' command which Cumulus sends. If you're not having any ftp problems you can probably ignore it.

[mimo57]

PS:Another question, do you have an explanation of the error "FTPRequestDone ftpQuitAsync errno = 500" in the files diags?

It's an error coming back from your ftp server, presumably complaining that it doesn't like the 'quit' command which Cumulus sends. If you're not having any ftp problems you can probably ignore it.

Ok, thank you for the answer. What is bizarre is that this message does not appear each time you connect. If the command "Quit" is not recognized by the FTP server, it should be there all the time. Logically.

[steve]

It recognises the command, it probably objects to some of the times Cumulus uses it. I've put them in various places to try to stop the connection locking up, as it seems to for some people occasionally.

[mimo57]

It recognises the command, it probably objects to some of the times Cumulus uses it. I've put them in various places to try to stop the connection locking up, as it seems to for some people occasionally.

OK, thx

Yves