Cumulus Support

Showing a 91.1 °F range for 7/24/13

The log for that day shows this gap in data. Not sure if this is the cause or not. I'm attaching my diags folder.

24/07/13,06:30,70.2,91,67.4,2.0,7.0,156,0.00,0.37,1011.82,4.78,73.8,47,7.0,70.2,70.2,0.0,0,0.000,0.000,75.5,0,0.0,157,0.00
24/07/13,17:10,90.9,51,70.3,2.0,0.0,0,0.00,0.39,1012.74,4.80,78.7,48,0.0,90.9,96.8,0.0,0,0.000,0.000,97.5,596,0.0,345,0.00

Thanks for any help.

When you started Cumulus at 17:09 on the 24th, it asked the station for the logger data needed to catch up from when it closed at 02:08. The station sent the entire contents of the logger. This is because you have Cumulus set to a 1 minute log interval, and the station set to 30 minutes, so you hit the issue with the station described in this FAQ: http://wiki.sandaysoft.com/a/FAQ#Cumulu ... t_start_up

This wasn't directly the cause of the problem. Despite sending the entire contents of the logger, the station didn't send all of the required missing data, hence the gap in your data, and this contributed to the daily range problem.

It appears that it got a minimum temperature value of zero from somewhere. This may have been supplied by the station (I can see a number of invalid entries in the diags files), or possibly caused by the following:

On the previous night, you started Cumulus up just before midnight. Because it took so long to download the entire contents of the logger data, it had passed midnight before it had finished processing the data. I'm not quite sure what the full effect of this would be, but from the daily range value, it's possible that it caused a minimum value of zero to be recorded. It is not recommended to start or stop Cumulus close to midnight. It tries to cope with every eventuality, but given the added complication of the long logger download, it's possible that something went wrong somewhere.

I strongly recommend that you set your logger intervals to be the same in Cumulus and the station. Cumulus copes with getting data that it didn't actually need, but in your case the station is also sending invalid entries and is not sending some entries which are actually required. Do you have a Weatherlink IP, or are you using Virtual VP? The symptoms of sending invalid entries and missing entries fit some of the known issues with Virtual VP and the Davis DLL which Cumulus uses.

Thank you for the response. I am using Weatherlink IP.
What would be your suggestion to remove this highest daily range? I'd like to remove this range and get a more realistic data point.
Thanks again.

Use the built-in editors for monthly and all-time records, on the edit menu. Your previous monthly record for July is logged in the diags file:

New monthly record, month = 7: 2013-07-24 00:00 91.100 "High daily temp range" 2013-07-04 00:00 33.800

So you can change it back to 33.8 on 4th July 2013.

If you look in the alltimelog.txt file in the Cumulus folder, there will be a similar entry for the all-time record which you can use in the all-time editor.

Got my range set back and my intervals matching.
Thanks for your help.

tul9033 wrote:Got my range set back and my intervals matching.
Thanks for your help.

Kind of hard not to notice your username...fellow Tulsan, perhaps?

Indeed!

BigOkie wrote:

tul9033 wrote:Got my range set back and my intervals matching.
Thanks for your help.

Kind of hard not to notice your username...fellow Tulsan, perhaps?