Strange issues across all readings this morning MX 3018

[ayde_bury]

Ok I'm upgrading to 3019 in the next few minutes, but some weird thing happening during the early morning data today.

4:11am to 5:17am wind speed of 255mph recorded.
Outdoor temperature and humidity flatline from 4:11 to 5:17am.
Rainfall records -0.2mm and then returns to 0mm at the end of the event.
All console generated readings are fine; pressure indoor temp etc.

I would normally think a low ISS battery for this stuck reading, however, the wind is separate form all the other sensors on a secondary ISS.

Home station data can be viewed here: http://www.oinky.net/weather/trends.htm

[steve]

255 is the undocumented 'dash value' for wind, but I thought I was now looking for that everywhere - I'll check. It does look like your console lost contact for that period. Was this from live data or from the logger?

If you get Weatherlink to download the logger data, it should confirm/refute the lost contact theory. And if you attach the MXdiags file, I should be able to see something in there.

[steve]

That rain figure is actually the rate, so apparently -0.2 mm/hr was read - details like that matter

[ayde_bury]

Interestingly Steve, it does look like a loss of connection to both the main ISS and also the the secondary anemometer ISS at exactly the same times within WeatherLink.

This was all live data as I leave CumulusMX running 24/7 on the server.

MXDebug file attached as requested.

[steve]

The current code does check for 255 everywhere, but perhaps not all of those checks were in 3018. I'll add a check for negative rain rate.

[ayde_bury]

Hi Steve,

I've installed 3019 and the problem looks like it persists. The only change that I made to my settings since installing MX was to set the Culumus software to sync my console clock to the PC.

I disabled this earlier in the week and the stage dropouts at around 4:11am stopped and the readings have been good since.

This may well be coincidence so over the weekend I will re-enable this setting to see whether the problem returns.

[ayde_bury]

Hi Steve,

Well the CumulusMX sync Davis Time to Local PC was re-enabled late this afternoon at 18:33. At 18:44 the windspeed jumped to 255mph and rainfall rate to -0.2mm. All other external readings to the console remained stuck until 19:49 when they jumped to their correct rates.

I will turn off the Davis clock sync again, manually edit the data to remove the 255mph spike and leave it like this for the moment.

The complete configuration of the system MX is running with is as follows:

Davis Vantage Pro2 Plus Wireless.
Anemometer Transmitter Kit
Windows 2008 Server R2 with SP1
8GB Ram

[steve]

The current code definitely checks all of the wind values now, and also checks for negative rain rate. Perhaps 3019 didn't have all of those changes. I'll be uploading a new build later this week.

Did you restart after setting the clock sync option? It only sets it at start up and at 0400, so unless you restarted, just changing the setting wouldn't have caused it to set the clock, so it couldn't have been related to the false data from the console.

[ayde_bury]

Hi Steve,

Yes I did restart Cumulus at the point of changing the time sync setting. No problems for just over two days with it turned off again.

I will await the next build and then try again. Thanks for looking into this.