Cumulus Support

Good morning

My Cumulus MX does not appear to download any Archive data when it starts, it runs this instantly.

The log seems to show it has been read but when I view the graphs on the screen there is a flat line.
Weather Underground also has a flat line.

Any ideas?

A logging file is attached.

David HOLMAN

My Cumulus MX does not appear to download any Archive data when it starts, it runs this instantly.

You apparently closed Cumulus down and then started it up again almost immediately. There was one archive entry to download, MX correctly downloaded and processed it:

2016-04-18 08:39:32.989 Loaded archive record for Page=0 Record=0 Timestamp=18/04/2016 08:39:00
2016-04-18 08:39:32.989 Processing archive record for 18/04/2016 08:39:00
2016-04-18 08:39:33.036 Page=0 Record=0 Timestamp=18/04/2016 08:39:00
2016-04-18 08:39:33.036 Writing log entry for 18/04/2016 08:39:00

I can't say why your graphs flat-line, even though Cumulus is actually downloading archive data - a link to your WU page would be useful, so that I can at least see when the flat line started and stopped for the file that you have uploaded.

You apparently closed Cumulus down and then started it up again almost immediately. There was one archive entry to download, MX correctly downloaded and processed it

I too experience a data start at a zero value when I shut down MX and restart within a few minutes. In my case this only manifests with the pressure reading - all other data starts at the current value.

Data is provided by an Oregon 88 console - what can I do to prevent the leading zero pressure value. Lately I have experienced network problems - none associated with MX - but the network problems have caused me to shutdown MX, reboot the computer, and restart MX. This action causes the zero starting value for pressure upon each restart but not any other channels. Any suggestions?

I too experience a data start at a zero value when I shut down MX and restart within a few minutes.

Ignore - just found a bad (zero) pressure data point in the data files. Everything now correct.

This is nothing to do with the problem in this thread, your station doesn't provide archive data for one thing. Likely caused by this listed known issue: "Some timer-based actions (e.g. realtime FTP and realtime SQL update) can happen before first data is read". Logging data is a "timer-based action".