Cumulus Support

I've been gone for a while, but just was able to get on Cumulus. My job keeps me out of town and I have Cumulus running while I'm away. Anyways ever since Jan 31 it looks like my high temp is 999 and low is -500. Another thing is that my "yesterday" data is messed up too. Everything else is always 0 except the high and low temp...any ideas??

If you need a screen shot how do I do that?

So I noticed one of my "Today" records came from the future!!! I noticed if after I had shut down and restarted Cumulus to try to fix the "yesterday" data which didn't work. Anyways the daily low temp was recorded at 21:00 which isn't too odd except for the fact it was only 20:28 when I looked. I looked up to see if maybe the clocks got out of sync, but both the Cumulus time and the station time on the console were within 1 sec of each other...although I'm not sure if they were in sync before the restart, so maybe the got out of sync on Jan 31 and that has caused the 999 *F days and rest of my "yesterday" data problem.

You're having 'rollover' problems. For some reason, Cumulus isn't detecting that midnight has occurred and isn't resetting your data for the start of a new day. Please zip up and attach your diags folder.

I might have done things the hard way, but since it was just a few days it wasn't too bad. I went thru the Feb10 log to manually get the things that the dayfile and current "yesterday" file would need and put them in by hand. I was awake at midnite so I opened up Cumulus and saw that the "today" data correctly slide over to the "yesterday" spots. Another thing I noticed for the dayfile was that there were duplicate dates for Jan 31 and Feb 1 then just single entries for Feb 2/3 but the "duplicate dates" and Feb 2/3 had the weird data. I didn't save the old dayfile so not sure I can post that if you need it, unless it was in on of the backup folders.

Heres the zip of the Diag folder.

It looks like you had two problems. First, it seems the station got disconnected (as far as Windows was concerned anyway):

2010-01-31 00:19:03 : 12:19:03 AM EWUSB: HidControl Device Unplug
2010-01-31 00:19:03 : EWUSB: HidControl Device Removal

What's odd is that it does seem to have recovered, so I'm not sure whether that did actually affect your data or not. So possibly not relevant.

What definitely is relevant is this:

2010-02-03 00:00:00 : === Day reset for 2/3/2010
2010-02-03 00:00:00 : Error writing Dayfile: I/O error 32

and again:

2010-02-04 00:00:01 : === Day reset for 2/4/2010 12:00:01 AM
2010-02-04 00:00:01 : Error writing Dayfile: I/O error 32

This is the file sharing violation that some people get which I can't explain. It means that something else (antivirus? who knows) had the dayfile.txt file open and prevented Cumulus writing to it. I have changed the way Cumulus writes dayfile.txt in 1.8.9 to try to avoid this problem.

Incidentally, do you know you know you have 'use data logger' unset?

Not sure if it was ever physically unplugged, although I doubt it since it was plugged in when I got home and its doubtful the wife would've known or cared if it was unplugged and probably wouldn't have plugged it back in on her own

All of the boxes in settings including "use data logger" are un-checked / no check marks however you want to say it.

Is the new version out yet or are you still doing testing on it?

Thanks for your help

Great Cornholio wrote:All of the boxes in settings including "use data logger" are un-checked / no check marks however you want to say it.

Yes, that's what I'm saying: you have 'use data logger' not set, so if you stop Cumulus for any length of time, it won't pick up the missing data when you start it up again.

Is the new version out yet or are you still doing testing on it?

It's available as what I call a 'beta', but once a few people have used a beta for a day or two it tends no have no more bugs than the 'stable' version. You can get it from the downloads page if you want to try it.

Sorry I mis-read it the first time and thought you asked "do you know IF you have" I will go ahead and set it up. I would probably just wait till the bugs are worked out. My job keeps me out of town a lot (was just gone for 2 weeks and only home for 2 days..head back out tomorrow) so being a beta tester probably isn't a good idea.

Great Cornholio wrote:Sorry I mis-read it the first time and thought you asked "do you know IF you have"

It would have helped if I hadn't put too many "you know"s in there!