Cumulus Support

Hi All,

I am a new owner of a Davis Vantage Vue. I put up the Davis WeatherLink website as well as the Cumulus. When I went live on the Cumulus, the WeatherLink site has stopped updating at the expected 15min intervals. Prior to deploying Cumulus the Weatherlink worked perfectly. It now updates intermittently with no pattern. At the time of this post it hasn't updated in over 2 hours. The Cumulus site is working perfectly and updating every 15min. I have excellent network speeds so I don't believe that is the issue.

Any idea what the problem might be?


Thank you,
John

You're using a Weatherlink IP logger, yes? These are apparently unable to upload while software is connected to them. You need to set a disconnect period in Cumulus so that Cumulus will disconnect once a minute to allow it to upload - see 'discon period' in the station settings. You'll need to experiment with the value.

steve wrote:You're using a Weatherlink IP logger, yes? These are apparently unable to upload while software is connected to them. You need to set a disconnect period in Cumulus so that Cumulus will disconnect once a minute to allow it to upload - see 'discon period' in the station settings. You'll need to experiment with the value.

Yes, I have the WeatherLink IP Logger. I will try your suggestion. Thank you!

John, the Davis Instruments WeatherLinkIP data logger (adaptor) was primarily designed to capture the data from the console and upload that data to the WeatherLink Network - it was never meant to be use with a weather software - the WeatherLinkIP adaptor does not like to share its time with anything else, thus the problems you are encountering.

Although Steve gaves you a solutions, it is only a 'band aid' solution and the communication problems are still there - maybe not as obvious.

The only option is to choose between the limited possibilities offered by the WeatherLink Network or too use your own software (such as Cumulus) to extend and properly control all the possibilities.

The only solution is to deactivate the upload functions of the WeatherLinkIP data logger...

I have had one such WeatherLinkIP data logger for the past 2 years (replaced twice so far), so I know what I am talking/writing about...

gemini06720 wrote:John, the Davis Instruments WeatherLinkIP data logger (adaptor) was primarily designed to capture the data from the console and upload that data to the WeatherLink Network - it was never meant to be use with a weather software - the WeatherLinkIP adaptor does not like to share its time with anything else, thus the problems you are encountering.

Although Steve gaves you a solutions, it is only a 'band aid' solution and the communication problems are still there - maybe not as obvious.

The only option is to choose between the limited possibilities offered by the WeatherLink Network or too use your own software (such as Cumulus) to extend and properly control all the possibilities.

The only solution is to deactivate the upload functions of the WeatherLinkIP data logger...

I have had one such WeatherLinkIP data logger for the past 2 years (replaced twice so far), so I know what I am talking/writing about...

Thanks for your input Ray. Before your post I took Steve's advice and adjusted the 'discon period' to 60. Now both my WeatherLink and Cumulus sites seem to be updating properly. The WeatherLink updates about every 1min (apparently this frequency is set by Davis and cannot be changed). The Cumulus site updates every 15min. (I can change the Cumulus update frequency)

Maybe I'd see an issue if both sites were updating every minute. I'll need to test that to verify but I'm happy so far.

jgkurz wrote:Before your post I took Steve's advice and adjusted the 'discon period' to 60.

Note that the 'discon period' is the amount of time each minute that Cumulus spends disconnected from the station (as described in the help), so I'm surprised that Cumulus is working very well at all with a discon period of 60 seconds. At worst, this means that Cumulus is only ever connected to the station very briefly once a minute, or at best it is connected for a minute, then disconnected for a minute, and so on. You will this be losing a lot of readings, which will (in particular) seriously affect your wind readings.

I suggest you start with a discon period of 5 seconds or less, and then take it from there.

steve wrote:

jgkurz wrote:Before your post I took Steve's advice and adjusted the 'discon period' to 60.

Note that the 'discon period' is the amount of time each minute that Cumulus spends disconnected from the station (as described in the help), so I'm surprised that Cumulus is working very well at all with a discon period of 60 seconds. At worst, this means that Cumulus is only ever connected to the station very briefly once a minute, or at best it is connected for a minute, then disconnected for a minute, and so on. You will this be losing a lot of readings, which will (in particular) seriously affect your wind readings.

I suggest you start with a discon period of 5 seconds or less, and then take it from there.

I changed to 5 and all is still fine. Just to be clear, does a 5 mean the Cumulus site and/or the WeatherLink site will lose 5sec of data because of the disconnect every minute or so?

jgkurz wrote:Just to be clear, does a 5 mean the Cumulus site and/or the WeatherLink site will lose 5sec of data because of the disconnect every minute or so?

It means that Cumulus will lose one or two readings every minute; so if a high gust, for example, occurred at that time, Cumulus wouldn't see it.