Cumulus Support

Hi there, not sure if anyone can advise me. I'm going away for about 10 weeks and I dont want to lose any weather data. My WH1081 memory fills up quicker than that and I wont be able to dowload it to cumulus 1 on my desktop so it will get overwritten. Is there any workaround anyone came across please ?

Cheers

Leave the computer on while you're away?

A fine Offset has 4080 memory locations. Therefore change the saving of data to 25 mins or to be safe 30 mins (10 x 7 x 24 x 60 = 100800 ) / 4080 = 24.71.

To change the data capture time use Steve Loft's old program Set logger interval which is in the Wiki here https://cumuluswiki.org/a/Software#Util ... t_Stations

I was also thinking about adjusting the WH1081 logging interval. But I have a bad feeling that C1 did have some issues when the logging intervals of C1 and WH1081 were not the same. And changing the Cumulus logging interval with existing data was not a good idea, if even possible.

Just leaving the computer on isn’t a very reliable solution either, unless it is configured to login automatically to desktop (no password) and start Cumulus1 automatically from startup shortcut. If it really is WinXP in this case, it will not reboot due windowsupdate, but in 10 weeks many things can happen.

Thanks for the replies but that is exactly my point. I cant leave the computer on. So I guess htere is no way to change the length of time before the WH1081 memory gets full? Looks like i will just have to lose a few weeks of data - first time for 12 years

In saying that I have noted the comment regarding the utility but I dont want to try and use it unless my existing data is secure.

Skyline wrote: ↑Sun 15 Dec 2024 9:28 am ... but I dont want to try and use it unless my existing data is secure.

Your existing data won't go anywhere. You will just get less frequently sampled data whilst you are away. Once Cumulus has caught up after you get back, change the console logging interval back to its previous value.

If you change the interval in CMX, then there is an option to also set the console interval to match. You can use this rather than the set logger utility if you wish.

Note that changing the logging interval should only be done when the Cumulus data is current. The records do not contain a timestamp, so their time is calculated using the currently defined interval.

Thanks Mark appreciated. Is there a maximum I can set the log interval to or is anything within reason ok?

It must be divisor of 60, so using Paul's David's calculation above 30 minutes - which is the maximum

mcrossley wrote: ↑Mon 16 Dec 2024 4:12 pm It must be divisor of 60, so using Paul's calculation above 30 minutes - which is the maximum

Point of order m'lud twas me!!

Dah!