Re: Cumulus hangs shortly after midnight...
Posted: Fri 09 Sep 2011 6:59 pm
The graphs window wasn't really designed to be left open permanently. There's no particular reason that it shouldn't work, but it looks like it does cause some kind of problem. So I would think it may well happen again.
One thing I do notice in the diags files is that you have Cumulus and your station set to a different log intervals (1 minute in Cumulus and 10 minutes in the station). This causes the Davis feature to be activated where the stations sends the entire contents of the logger every time Cumulus starts:
09/09/2011 15:52:44.984 : VP2: DownloadData_V = 2559
09/09/2011 15:52:44.984 : VP2: GetNumberOfArchiveRecords_V = 2559
09/09/2011 15:52:44.984 : VP2: Number of history records = 2559
09/09/2011 15:52:45.000 : Logger entry zero: Y = 2011, M = 8, D = 22, H = 21, M = 10
09/09/2011 15:52:45.000 : VP2: Earliest timestamp 22/08/2011 21:10:00
09/09/2011 15:52:45.000 : VP2: Earliest timestamp is earlier than requested
09/09/2011 15:52:45.000 : VP2: Find first entry after 09/09/2011 15:47:00
09/09/2011 15:52:45.000 : VP2: Checking logger entry 0 Y = 2011, M = 8, D = 22 H = 21, M = 10
09/09/2011 15:52:45.000 : VP2: New earliest timestamp 22/08/2011 21:10:00
09/09/2011 15:52:45.000 : VP2: Checking logger entry 1 Y = 2011, M = 8, D = 22 H = 21, M = 20
You may not consider this to be a problem; Cumulus tries to cope, but it means that the start up takes much longer than it should. You may want to set both to the same interval.
One thing I do notice in the diags files is that you have Cumulus and your station set to a different log intervals (1 minute in Cumulus and 10 minutes in the station). This causes the Davis feature to be activated where the stations sends the entire contents of the logger every time Cumulus starts:
09/09/2011 15:52:44.984 : VP2: DownloadData_V = 2559
09/09/2011 15:52:44.984 : VP2: GetNumberOfArchiveRecords_V = 2559
09/09/2011 15:52:44.984 : VP2: Number of history records = 2559
09/09/2011 15:52:45.000 : Logger entry zero: Y = 2011, M = 8, D = 22, H = 21, M = 10
09/09/2011 15:52:45.000 : VP2: Earliest timestamp 22/08/2011 21:10:00
09/09/2011 15:52:45.000 : VP2: Earliest timestamp is earlier than requested
09/09/2011 15:52:45.000 : VP2: Find first entry after 09/09/2011 15:47:00
09/09/2011 15:52:45.000 : VP2: Checking logger entry 0 Y = 2011, M = 8, D = 22 H = 21, M = 10
09/09/2011 15:52:45.000 : VP2: New earliest timestamp 22/08/2011 21:10:00
09/09/2011 15:52:45.000 : VP2: Checking logger entry 1 Y = 2011, M = 8, D = 22 H = 21, M = 20
You may not consider this to be a problem; Cumulus tries to cope, but it means that the start up takes much longer than it should. You may want to set both to the same interval.