Time of Day Missing in "Recent Extremes"

[ShawnInPaso]

Hello,

I'm seeking some help to correct a problem. The time of day shown in the "recent extremes" always shows "at 00:00". Consequently, the "extremes" only contain the value which occurred at midnight (e.g. whatever the low temp was at 00:00 is the low temp for the entire day).

I have searched the forum for an answer and came up empty handed. Then, I updated the Cumulus software to 1.9.4 and the problem still exist?

My station is a Davis VP2. While this hasn't been an issue in the past, I think it has been occurring for a few week intermittently and now stays this way.

Any help or advice would be much appreciated.

Thank you,
Shawn

[steve]

If you zip up the diags folder and attach it, I'll take a look. Please also include the today.ini file. Is it doing it right now?

[ShawnInPaso]

Yes it's doing it now. I will zip up the files and upload them. Thanks very much.

[ShawnInPaso]

Steve -

Guess I'm having a bad day. When I attempt to upload the zipped file using the "choose file" button, the "progress bar" dialog box just hangs endlessly.

Conversely, when I "choose" a filename and submit my reply to the board it shows the upload but then results in an empty message reply?

Shawn

[ShawnInPaso]

While I'm sorting out the upload issue, I took a look at the most recent Diag file(cumulus.009). Below is a snippet from the file.

You can see the error messages after the rain counter data. Those error messages go on and on and on for a very long time?

1/9/2014 20:13:16.628 : Rain last 24 hour: 0.00
1/9/2014 20:13:16.628 : Initial data processing complete
1/9/2014 20:13:16.628 : Drawing initial graphs from data logs
1/9/2014 20:13:16.632 : Finished drawing initial graphs from data logs
1/9/2014 20:14:22.236 : Saving display settings
1/9/2014 20:14:22.236 : Writing cumulus.ini file
1/9/2014 20:15:06.754 : Saving display settings
1/9/2014 20:15:06.754 : Writing cumulus.ini file
1/9/2014 20:30:00.244 : Writing today.ini, LastUpdateTime = 1/9/2014 8:30:00 PM raindaystart = 0.310000002384186 rain counter = 0.330000013113022
1/9/2014 21:00:00.483 : Writing today.ini, LastUpdateTime = 1/9/2014 9:00:00 PM raindaystart = 0.310000002384186 rain counter = 0.330000013113022
1/9/2014 21:30:00.098 : Writing today.ini, LastUpdateTime = 1/9/2014 9:30:00 PM raindaystart = 0.310000002384186 rain counter = 0.330000013113022
1/9/2014 22:00:00.429 : Writing today.ini, LastUpdateTime = 1/9/2014 10:00:00 PM raindaystart = 0.310000002384186 rain counter = 0.330000013113022
1/9/2014 22:30:00.020 : Writing today.ini, LastUpdateTime = 1/9/2014 10:30:00 PM raindaystart = 0.310000002384186 rain counter = 0.330000013113022
1/9/2014 23:00:00.452 : Writing today.ini, LastUpdateTime = 1/9/2014 11:00:00 PM raindaystart = 0.310000002384186 rain counter = 0.330000013113022
1/9/2014 23:06:16.164 : VP2: LoadCurrentVantageData_V, error = -32701
1/9/2014 23:06:16.244 : VP2: LoadCurrentVantageData_V, error = -32701
1/9/2014 23:06:16.324 : VP2: LoadCurrentVantageData_V, error = -32701
1/9/2014 23:06:16.404 : VP2: LoadCurrentVantageData_V, error = -32701
1/9/2014 23:06:16.484 : VP2: LoadCurrentVantageData_V, error = -32701
1/9/2014 23:06:16.564 : VP2: LoadCurrentVantageData_V, error = -32701

[PaulMy]

The 32701 error has been discussed a number of times on the forum and I have experienced it as well. Incorrect Com port setting or trying to run 2 programs at the same time are some causes. Steve may have more comment from his review of the log info but can you shut down Cumulus and try to connect and run Weatherlink as that may identify and eliminate some causes.

Paul

[ShawnInPaso]

That must be it Paul. After I reset everything, the time(s) appeared in the Cumulus display next to the related "extremes". Odd that only those times were affected. No doubt a communication glitch with the com ports, serial to USB and all of that. I have work to do to correct it, but thanks to you (and Steve) for the help.

Shawn

[steve]

Any communication problems that go on for a long time, and particularly if they cross from one day into the next, will affect the operation of the daily highs and lows.

[ShawnInPaso]

Thanks again Steve - I'm sure this was a communication issue now.

Sorry I didn't know to search for the specific error; but now all is good and I know a bit more about solving my own computer issues.