Cumulus Support

While I was on vacation, my computer malfunctioned for several days, causing no data to be recorded by Cumulus for a period of about 4 days. Is there a way to have the console re-send data to Cumulus, thereby over-writing the days with no data?

Usually when this has happened, when I return from vacation I see that Cumulus had shut down in my absence, and re-starting it triggers a "catch-up" period where everything gets corrected. In this case, when I returned my computer had just been "hanging", and only a re-boot got Cumulus working again. Unfortuntately, this did not correct the missing days.

-Tom

As long as the data is in your logger, you can 'rewind' by copying all of the files from one of the Cumulus backups (taken each day and when you start Cumulus) into the data folder, while Cumulus is stopped. There's a FAQ about correcting invalid data using this method.

I don't see any backups that were recorded during the 5 "dark" days (July 17-21) It appears from the dayfile I opened after I restarted Cumulus yesterday that no data was captured on the missing days? How can I see if the data is still in the logger?

Looked in the "daily" folder?

Yes, in the "daily" folder (backup\daily) there are no files/folders that were written during my data blackout. I was hoping the data was still on the console and I could force a data download from the console.

As Cumulus wasn't doing the daily rollover, for whatever reason, it won't have been doing the daily backups either, but that's not relevant as you want the last daily backup before the problem occurred. You could also use that one from the 14th July startup. Using the backup is what forces the re-download of the data from the logger, from the date and time of the backup.

To determine whether your logger will hold the required data, use your logger interval (the one the station is using rather than Cumulus, although you should have set them the same) and the fact that the logger holds 2560 entries (e.g. a 5 minute interval gives you slightly less than 9 days, which would be adequate if you do it soon). This assumes of course that the station was logging correctly for the required period - if the problem is only at the PC end, that's a reasonable assumption.

That did the trick! Used the July 14 backup, and the logger filled in the rest. Thanks!