Cumulus Support

I have updated to the lastest beta and now I receive this message when Cumulus downloads the data from the logger at start up. If I let Cumulus continue downloading the data while the message is on the screen Cumulus downloads the data properly and starts as normal.

But Cumulus does normally freeze when it downloads from the logger and then unfreezes and starts updating when the green bar moves across the usual please wait window.

Also there is nothing in the diags file shows anything abnormal but it seems with the latest beta it thinks it is frozen and it is frozen but Cumulus is downloading the data properly.

Is this something I don't need to worry about? Please find attached screen shots of the bug report.

I think the freeze checking is going to be more trouble that it's worth; I'll take it out again.

Strangely enough I had the same frozen bug report today. Unknown to me the network / internet connection broke at 4am today and I only saw it after returning home this afternoon. An alarm would have alerted me when I came down into the lounge.

I couldn't even display Task Manager which is something of a first. I also 'lost' around 3 hours of data for the first time I can remember - 0730 - 1030. And I'm running an earlier build as you can see from my sig.

I don't understand that; I only enabled the 'freeze checking' in the latest build.

steve wrote:I don't understand that; I only enabled the 'freeze checking' in the latest build.

That is strange but I can assure you I saw the same message as that posted by Matt.

Thanks Steve for your response. I was hoping it was not got to do something with my weather station with the trouble it has caused.

I got the same error with 1048. Took a lot of tries to get it to download the data. Had the same problem with 1047 at the initial startup after upgrading. This time I noticed a type of spike in the running graphs. Many of them showed no data or 0 data for the time I started up Cumulus.

Steve,
I get the same bug report most, but not all the time. If you wait it out for about 90 secs, the station comes up normal. I don't think the "freeze checking" is the problem; but rather, was rightfully highlighting an issue (my setup) that was evident at least back in build 1047. Sometimes, my station (builds 1047 and 1048) comes up in less than 10 seconds and will shut down in 10 seconds. Other times it may take about 90 seconds (bug appears at 70 secs) to come up and 60 seconds to shut down. At present, I'm trying to determine why this happens. Here is what I've noticed on my extended station startup, text in "" below is the station status;
a. 0 - 6 secs -- "Initialising", clock stopped.
b. At 6 secs -- "Downloading Data", downloading data box appearing on the screen, clock updates 6 secs and stops.
c. At 70 secs -- "Downloading Data", bug report window appears, clock has not updated and remains stopped.
d. At 90 secs -- the downloading data and the bug report boxes disappear, clock updates, station defaults appear and all is fine.
I believe the "freeze checking" is a good feature and has identified a sporatic issue with my set up. If we can determine and solve why at times stations go into an extended startup, you might consider reinstating the bug report in future builds. I noticed it was disabled in 1049.

The Cumulus initiative, your support and the community that has formed around it is utterly amazing. Thank you for your leadership.

If you zip up the diags folder and attach it, I may be able to see what it was doing. Note that in some cases, start up with Davis stations can take a long time, if the station decides to send the entire contents of the logger. It will do this quite often if the Cumulus logger interval is not the same as the station logger interval, but it can also do it sometimes even when they are the same.

File attached.
I suspect my station is operating as you indicated, sometimes loading a long file, sometimes not. While testing today, I'm 2 each way already. I'll check the intervals and baud rates. Thanks

You've got Cumulus set to a logging interval of 5 minutes, but the station set to 10 minutes, so on average, on half of the starts you will hit this issue: http://wiki.sandaysoft.com/a/FAQ#Cumulu ... t_start_up

I am also having a problem with cumulus locking up when (I guess) it is downloading data. I think I saw earlier that cumulus is written in Delphi. How about adding some processmessages statements so the cumulus window can still respond to mouse clicks?

I am told by experts that using Application.ProcessMessages() is bad. And while I accept that aesthetically it's not ideal that it stops responding, you're not supposed to fiddle with Cumulus while it's downloading the logger data (that's why the "Please Wait" message appears), so is it really an issue anyway?