WH1081 / Cumulus Data Error

[gbee]

Cumulus 1.9.2 & WH1081

I started to get error in the status box and a constant 8°C, now my weather was stable but not this stable, eventually I see that the readings are not being recorded from the WS.

The Error was showing old value and new value and just constantly reloaded these. I eventually deleted Cumulus and started again.

My problem is that my CB Dxing causes spikes, I removed them from Cumulus and everything was fine. But then I noticed no rain, and found the known culprit, a full memory buffer on the WS. Easy Weather cleared the mem and wrote a new log file.

Therafter, Cumulus was giving me the error message of old values and new values. How could I have stopped this an kept my records?

[steve]

I'm not sure exactly what it is that you're asking. It sounds like you're talking about "spike removal"? If that's the case, then either you've set an unrealistic value, or your weather station is continually sending bad data (due to the radio interference, presumably). If you zip up the diags folder and attach it, I'll take a look.

But then I noticed no rain, and found the known culprit, a full memory buffer on the WS. Easy Weather cleared the mem and wrote a new log file.

It's not normally necessary to clear the memory buffer, it just starts again at the beginning when it's "full".

[gbee]

.

It's not normally necessary to clear the memory buffer, it just starts again at the beginning when it's "full".[/quote]

I've actually deleted everything, I had been expecting the error to overwrite and stop, it just seemed to loop.

With the WH1081 it is a known problem that if the memory buffer is full physically on the Console, rain data will not be sent to the software ~ no matter what software it is. Yes, the data overwrites itself so for record purposes you only get one months supply of data [or less with 10 minute updates].

The CB only causes spikes, data is accurate between them.

As best that I can explain my little problem is that the Easy Weather wrote a new log, and Cumulus read this log and it was different from what it had itself, but instead of offering an overwrite it just looped the error data and Cumulus's display was not updating from the console.

[steve]

With the WH1081 it is a known problem that if the memory buffer is full physically on the Console, rain data will not be sent to the software ~ no matter what software it is.

There are a lot of Fine Offset users in this forum, and I don't remember anyone else mentioning this. Mine doesn't do it.

As best that I can explain my little problem is that the Easy Weather wrote a new log, and Cumulus read this log and it was different from what it had itself, but instead of offering an overwrite it just looped the error data and Cumulus's display was not updating from the console.

I'm even more confused now. If you're getting spike removal messages, then you're connecting to the station directly (as recommended) and not using the Easyweather log file in Cumulus at all. I can't really say any more without the diags files.

[gbee]

Thanks, anyway.

I've run Cumulus for six months, every month I shut it down, load Easy Weather, download the log to a it's date and clear the memory. Shut Easy Weather Load Cumulus and run away happily.

During the Christmas I changed the highs and lows in Cumulus, fine. End of January I did my routine and Cumulus status showed error, old value new value don't match and it stopped working, just looping the error data constantly.

Thanks for the reply, as I anticipate this occurring again, I thought I might mention it.

[Lloyd]

With the WH1081 it is a known problem that if the memory buffer is full physically on the Console, rain data will not be sent to the software ~ no matter what software it is. Yes, the data overwrites itself so for record purposes you only get one months supply of data [or less with 10 minute updates].

Not heard of this before. I'm on one minute updates (using wview), so my buffer fills in just under 3 days. No problems with rain records.

Lloyd