Cumulus Support

Steve,

I have a Davis Vantage Vue and am running 1.9.2 build 991. We had a storm move through this evening and had a brief power outage. After I restarted the PC running Cumulus it did a data logger read. My Vue console was showing a wind gust of 45mph but this was not read by Cumulus. The catch up light was not lit as well. I send data to APRS, PWS and Wunderground. I am attaching the debug file. Another thing I found odd was that in the Cumulus ini file it says last logger download was 02/27/2009 6:57:51 am, which was before I even bought the station. And after a Cumulus restart it takes my station about 2 -3 min to start receiving data from the tramsmitter. If there are any other files that would help let me know.

Thanks
Dave

I can't give you the full story, because you've only given me the one file (or was that the first run after the power outage?). But the situation in that file is that Cumulus was started at 20:06, having been closed down at or just after 19:50, so there's a only a small gap to fill. It asks the station for the data since 19:50:

6/20/2011 20:06:37.578 : VP2: Downloading history from 6/20/2011 7:50:00 PM

Your station has a logger interval of 30 minutes, so it doesn't understand a request for data for 19:50, and this activates a 'feature' in the station where it sends the entire contents of its logger to Cumulus:

6/20/2011 20:07:57.484 : VP2: Number of history records = 2559
6/20/2011 20:07:57.500 : Logger entry zero: Y = 2011, M = 4, D = 28, H = 12, M = 30
6/20/2011 20:07:57.500 : VP2: Earliest timestamp 4/28/2011 12:30:00 PM

So Cumulus has to work its way through the data to find what it actually needs:

6/20/2011 20:07:57.500 : VP2: Earliest timestamp is earlier than requested
6/20/2011 20:07:57.500 : VP2: Find first entry after 6/20/2011 7:50:00 PM
6/20/2011 20:07:57.500 : VP2: Checking logger entry 0 Y = 2011, M = 4, D = 28 H = 12, M = 30
6/20/2011 20:07:57.500 : VP2: New earliest timestamp 4/28/2011 12:30:00 PM
6/20/2011 20:07:57.500 : VP2: Checking logger entry 1 Y = 2011, M = 4, D = 28 H = 13, M = 0
6/20/2011 20:07:57.500 : VP2: New earliest timestamp 4/28/2011 1:00:00 PM

There's another 'feature' somewhere in the Davis code where the latest logger entry is never sent to Cumulus, so the latest entry that Cumulus gets isn't 20:00, but 19:30:

6/20/2011 20:07:57.593 : VP2: Checking logger entry 2558 Y = 2011, M = 6, D = 20 H = 19, M = 30
6/20/2011 20:07:57.593 : VP2: New earliest timestamp 6/20/2011 7:30:00 PM
6/20/2011 20:07:57.593 : VP2: No history records to process

Cumulus doesn't need this entry because its own last logger entry is later than that, so it has now finished with the logger download and carries on as normal.

In summary:

The logger download takes a long time because you've got your Cumulus logger and Vue logger set to different intervals, which isn't recommended as it activates the annoying 'feature'. You should really set them to the same value.

In this example the logger data was downloaded, but there wasn't actually any useful logger data to process (allowing for the fact there should have been just the one entry).

That 'last logger download' item in cumulus.ini isn't used.

If you zip up and attach the entire diags folder, I can see if there were any issues prior to this run. If you tell me the timestamp of that 45 mph wind gust I might be able to tell you why it wasn't recorded.

You should install the latest beta; there are a few known bugs in build 991 (unrelated to your query).

Thanks for the input. I have installed the newest beta and set the logger to 30 min. The 45mph wind was 06/20 at 1958. Attached is the Diags folder.

Dave

Skywatcher_ne wrote:The 45mph wind was 06/20 at 1958.

So it would have been in that 20:00 logger entry, which the Davis code didn't send.