Cumulus Support

Hi Steve,
I turn my computer off at night, and then load data the next morning. Whilst loading data (which takes about 10 minutes) it is not possible to move or minimise the Cumulus application which sits in the middle of my 1920x1080 screen - is this a function of my OS (Windows 7), or something that cannot be achieved for technical/programming reasons? Many thanks for an excellent application as ever.

It's probably something I could do if I was clever enough, and it would probably involve rewriting the download code so that it doesn't block the main thread. It would have a side effect of slowing down the initial download. With some station types, you can minimise the window; it depends on the mechanism for downloading the data.

The best I can offer is the 'start minimised' option.

Bit puzzled as to why your computer is taking 10 mins to download and process 1 nights data. I do exactly the same and it takes 15-20 seconds!!

I've just timed my Fine Offset, and Cumulus downloaded and processed 316 entries (about 14 hours worth at 5 minute intervals), in 14 seconds.

13/10/2012 13:45:20.990 : 13:45:20 EWUSB: Get history data

13/10/2012 13:45:34.077 : 13:45:34 EWUSB: End processing history data

The download from a Fine Offset should be quite quick. The download for Oregon WMR200 is slow, but Cumulus has no control over that, and for those you can minimise the window anyway. I'd expect the download for other stations to be pretty quick, for an overnight download. Oh, except perhaps La Crosse stations, where just reading one data item can sometimes take several minutes.

Many thanks Steve, and to others. My PC is a Dell 8300, and rather long in the tooth, I should have explained myself more clearly, the downloads of data (normally about 630 entries) is pretty quick, it's the subsequent processing which is slower due to the processor I suspect. Thanks for your helpful comments

My La Crosse station normally takes around 3 minutes to download about 150 entries at 5 minute intervals for the last 12 hrs or so.

14/10/2012 07:47:16.193 : WS2300: Downloading history data
14/10/2012 07:50:31.221 : WS2300: End processing history data

The downloading is slow with one entry each second or two like this:

14/10/2012 07:47:17.243 : WS2300 History Record: Address: 095F Data: 72 12 57 C0 88 64 F9 90 00 69
14/10/2012 07:47:19.696 : WS2300 History Record: Address: 094C Data: B8 06 67 C0 88 65 F9 00 00 26
14/10/2012 07:47:20.747 : WS2300 History Record: Address: 0939 Data: E8 FE 46 C0 88 66 F9 00 00 8A
14/10/2012 07:47:21.798 : WS2300 History Record: Address: 0926 Data: 17 F7 46 C0 88 66 F9 00 00 8A

But the processing with the green bar moving across on the please wait window is quite quick as shown here:

14/10/2012 07:50:17.516 : WS2300: Processing history data for = 13/10/2012 8:30:00 PM addr = 0C57
14/10/2012 07:50:17.518 : WS2300: History rain total = 0
14/10/2012 07:50:17.552 : Writing today.ini, LastUpdateTime = 13/10/2012 8:30:00 PM raindaystart = 0 rain counter = 0
14/10/2012 07:50:17.553 : WS2300: Processing history data for = 13/10/2012 8:35:00 PM addr = 0C6A
14/10/2012 07:50:17.554 : WS2300: History rain total = 0
14/10/2012 07:50:17.607 : Writing today.ini, LastUpdateTime = 13/10/2012 8:35:00 PM raindaystart = 0 rain counter = 0
14/10/2012 07:50:17.608 : WS2300: Processing history data for = 13/10/2012 8:40:00 PM addr = 0C7D
14/10/2012 07:50:17.608 : WS2300: History rain total = 0
14/10/2012 07:50:17.644 : Writing today.ini, LastUpdateTime = 13/10/2012 8:40:00 PM raindaystart = 0 rain counter = 0

Yes, La Crosse stations don't give up their data easily.

Sometimes I get also get a “cannot read archive data” error. I then have to restart Cumulus to re download the data from the logger by rewinding using the latest backup, even though the data comes out properly the second time.