Cumulus Support

Hi guys,

I'm relatively new to this forum, but have been using Cumulus for a while, anyhow, I've recently just got my station up and running again on a new pc, (Windows XP SP3... it's an old system). I set it up last night and had a hell of a time with getting Cumulus to recognise the Vantage Vue, anyhow, that was resolved albeit I'm not sure how, (Windows updates/different USB cables/USB ports). (This is a brand new system by the way).

Today the system has been running pretty well, until around 1pm, where it disconnected, (not sure why), I then see the disconnect at around 3pm and had a fiddle and got it working, however. Since the disconnect it seems that Cumulus has not downloaded any new data from the data logger. I've checked the trends on my site, and the temperature just before 1pm stays static at around 14c, then when the station was reconnected re-initializes and sees the new data, jumps almost straight to nearly 17c just after 4pm. You can see this here: http://benfleetweather.uk/trends.htm

I'm wondering if this is normal behaviour? Is cumulus not picking this up because the data was not fed to the application in real time? Do catch up's just amend record data and not trends? I'm stabbing in the dark here and not sure what's gone wrong so would like some assistance.

Any help would be of great use to me!

Thanks!

Do you have "Use data logger" ticked in Station Setting?

Paul

Hi there, I do have this ticked

I'm not sure this issue is relevant now due to it only being a problem with trend graphs, which are overwritten every 12 hours

Not sure if this has any bearing and if it would change your issue, but I have my graphs at 48 hours in the Display Settings.

Did Cumulus log any data at restart in the monthly log file from that 3 hour period?

Paul

If you station disconnects for whatever reason while Cumulus is running, you will get gaps in your data - Cumulus requires the real-time data while it is running. Downloading of archive data to catch up only occurs at start up.

PaulMy wrote:Not sure if this has any bearing and if it would change your issue, but I have my graphs at 48 hours in the Display Settings.

Did Cumulus log any data at restart in the monthly log file from that 3 hour period?

Paul

Hi there, thanks for the reply!

Out of curiosity how did you change the amount of hours that your graphs log?

Also, It's been a while since this issue happened, and I've done a lot of messing around with my site, so can't actually remember what was logged back then lol

steve wrote:If you station disconnects for whatever reason while Cumulus is running, you will get gaps in your data - Cumulus requires the real-time data while it is running. Downloading of archive data to catch up only occurs at start up.

Thanks, I didn't know that there would be gaps left in the data, but have had my station, as well as cumulus, the internet and the site running continuously since the error, and have had no further issues, I am also going to match the logging intervals between WeatherLink and Cumulus like I've seen you suggest to other members in the past.

When you say downloading of archive data only occurs at start up, what exactly does this mean, does it upload just the records, and not the graphs and timestamps, as I had a full 3 hour period of flatlined graphs?

I've noticed Cumulus catching up with all the latest data as it downloads data at startup, I'm just wondering what it actually does with it and where the information is then stored, what is uploaded to the website etc.

Thanks

It uses the logger data at start up as a substitute for the live data it gets while it is running. It does exactly the same thing with the logger data as it does with the live data - it processes the data from each logger entry as if it was a 'live' reading.

steve wrote:It uses the logger data at start up as a substitute for the live data it gets while it is running. It does exactly the same thing with the logger data as it does with the live data - it processes the data from each logger entry as if it was a 'live' reading.

Thanks for this.

I think I have just realised what has happened now.

Soon after I posted this thread, I had intermitted connectivity issues between the data logger and my PC, this was due to the data logger not being pushed down fully.

Therefore I believe that during this 3 hour period, the station was not actually reporting any data to the logger, therefore when I reconnected it to Cumulus, any archive data it had downloaded was static or 'blank' due to not receiving any new data from the station.

I think I've hit the nail on the head now, but could someone confirm to me that the problem I've just stated would tie in with a disconnected data logger/station?
Thanks again.

If the logger wasn't fully connected to the console then it's quite possible that the console was unable to log data to the logger.