Cumulus Support

Hi all, I updated to 1.9.2 build 1017 when it became official. Prior version was 1.9.1 build 989 with no issues. Anyway today I noticed that the Davis VPII console showed a 23mph wind gust in the 5PM hour, yet, Cumulus is showing 22 mph as the high gust of the day. Is this a glitch?

thanks much..

Cumulus can only log the data that the station (actually, the Davis DLL) sends it; if it didn't send it a 23 mph speed, it couldn't log it. It's possible because of the way the Davis DLL operates the protocol that an occasional packet might get missed; there's nothing I can do about that, sorry. Cumulus reads the data as fast as the DLL (and your PC) will allow it (one thing you could check is to make sure that you haven't got an entry for 'VP2SleepInterval' in Cumulus.ini, or of you have, it should be zero). Do you have a dedicated PC for your weather station?

Note that the Davis DLL performs unit conversions; perhaps it's simply a conversion/rounding difference. You would expect that with mph no conversion would occur, but who knows how they've coded it?

Thanks for the reply Steve, don't be sorry for something out of your control.....

We're experiencing something similar, however it's only with high gusts. Last night our http://www.weatherlink.com/user/trigono ... s=1&type=0 account logged a wind gust of 55MPH but Cumulus only shows 48MPH. Also, our weatherunderground account which is fed from the ip logger, not cumulus only shows 48MPH. Something to do with weatherlink's rounding perhaps?

We are allowing cumulus to release the connection to our IP data logger so it can update weatherlink.com though... this might be the problem?

Would be interesting to get to the bottom of this - nice to know someone else is having the same sort of niggles!

~CalonDdraig

CalonDdraig wrote:We are allowing cumulus to release the connection to our IP data logger so it can update weatherlink.com though... this might be the problem?

Quite possibly; all the time that Cumulus isn't connected to the station, it's missing data, which might contain the high value. What value have you set for the disconnect period?

It's interesting (perhaps) that the WU peak from the IP logger is the same as the Cumulus value.

You could watch the wind speeds on the console and Cumulus at the same time, and check that Cumulus is managing to keep up with the data...

Hi Steve,

Our discson period is 10 - don't know if that's seconds or what. Is that too high for just allowing the ip logger to 'ping' weatherlink?

Cheers,

~CalonDdraig

CalonDdraig wrote:Our discson period is 10 - don't know if that's seconds or what. Is that too high for just allowing the ip logger to 'ping' weatherlink?

Yes, it's seconds. I don't know how long it takes, and Davis don't give any guidance. They don't even document the fact that software needs to periodically disconnect at all. With the IP logger, Davis appear to be disregarding the fact that third-party software exists.

Cumulus waits a further second beyond the value you give it, so currently you are missing approximately 11/60th of the data updates. I would suggest starting at zero and working up as necessary until the weatherlink.com updates work successfully.