Any thoughts?




Thanks Steve!steve wrote:It's failed to do the end of day rollover, for whatever reason. Maybe it couldn't read the archive data from the station. There are some large gaps in the data so it looks like there were problems with the data download. It looks like the logger interval has become just over 2 hours, Cumulus can't work properly with that setting.
If you zip up the diags folder and attach it, I'll take a look.
You are the King. Not sure how it switched to that. maybe when I was playing around with the settings. I switched it back but I assume yesterdays log is lost? Unless I do it manually?steve wrote:You have the station type set to "Fine Offset with Solar", but looking at the data from the logger, it doesn't look like your station does have solar sensors. This is causing Cumulus to completely misinterpret the data, including the logging interval, hence the lack of rollover.
Hmm, none of the 10 backup files have a day file for February 1, 2012. I guess its because the error happened on that day?steve wrote:Having corrected the setting, you can 'rewind' and force a re-download of the data by stopping Cumulus and copying the files from a backup folder that was created before the problem occurred, into the Cumulus data folder, and then starting Cumulus again.
That entry was never created, so can't exist in any backups.Cambium wrote:Hmm, none of the 10 backup files have a day file for February 1, 2012. I guess its because the error happened on that day?
You copy them all. This restores you to a state some time in the past. You then run Cumulus, and it downloads all of the data from the logger since that point in the past, and brings you up to date by creating all of the required entries in the files. The price you pay is that you give up a certain amount of resolution; any data that you currently have that was logged 'live' (I think you have a 1-minute interval set in Cumulus) will be replaced by data from the logger (I think you have that set to a 5-minute interval). The overall effect is as if Cumulus hadn't been running since the point in the past that you rewind to. Like when you start it up on a morning having had it not running overnight.I guess my last question is: Would the "day file" be the only one you would copy and paste to "re-download"? Or is there something else I can do to get the data from yesterday inputted?
DONE.....PERFECT.steve wrote:That entry was never created, so can't exist in any backups.Cambium wrote:Hmm, none of the 10 backup files have a day file for February 1, 2012. I guess its because the error happened on that day?You copy them all. This restores you to a state some time in the past. You then run Cumulus, and it downloads all of the data from the logger since that point in the past, and brings you up to date by creating all of the required entries in the files. The price you pay is that you give up a certain amount of resolution; any data that you currently have that was logged 'live' (I think you have a 1-minute interval set in Cumulus) will be replaced by data from the logger (I think you have that set to a 5-minute interval). The overall effect is as if Cumulus hadn't been running since the point in the past that you rewind to. Like when you start it up on a morning having had it not running overnight.I guess my last question is: Would the "day file" be the only one you would copy and paste to "re-download"? Or is there something else I can do to get the data from yesterday inputted?