Cumulus Support

steve wrote:

hendrikr wrote:

steve wrote:It must be having problems reading the data from the logger. Or are you saying that it continues to display 'live' data behind the 'downloading data' box?

That's exactly what it does, actual data are being shown behind the message box.

That's strange. Basically, it opens the window, downloads and processes the archive data, then closes the window and goes into 'live' mode. I guess it's possible there's some error path where the window doesn't get closed. The diags file for that run might give some clues.

Please find attached today's debug.log. I started logging this morning. Data stopped updating at 11:53/11:54. When returning home I will first replace the logger hardware and see, what happens and then restart everything.

Unfortunately, as I thought, it hasn't helped:

5411.64594 : 11:53:18 USB device is plugged in
5411.64594 : 11:53:18 request EW data block, written = 9, addr = 006F50
5411.64609 : 11:53:18 EW data line 05 1A 19 CB 00 43 01 00 7F
5411.64625 : 11:53:18 EW data line 06 25 0E 18 00 06 7A 00 00
5411.64625 : 11:53:18 Data: 1A 19 CB 00 43 01 00 7F 25 0E 18 00 06 7A 00 00
5411.64625 : 11:53:18 EW data line 07 FF FF FF FF FF FF FF FF
5411.64641 : 11:53:18 EW data line 08 FF FF FF FF FF FF FF FF
5411.74547 : 11:53:28 USB device is plugged in
5411.74547 : 11:53:28 request EW data block, written = 0, addr = 000000
5411.84547 : 11:53:38 USB device is plugged in
5411.84547 : 11:53:38 request EW data block, written = 0, addr = 000000
5411.94547 : 11:53:48 USB device is plugged in
5411.94547 : 11:53:48 request EW data block, written = 0, addr = 000000
5412.04547 : 11:53:58 USB device is plugged in
5412.04547 : 11:53:58 request EW data block, written = 0, addr = 000000

It just stopped responding - or stopped being able to be spoken to at 11:53:28. There's no indication of any problem before that.

steve wrote:Unfortunately, as I thought, it hasn't helped:

5411.64594 : 11:53:18 USB device is plugged in
...
5412.04547 : 11:53:58 request EW data block, written = 0, addr = 000000

It just stopped responding - or stopped being able to be spoken to at 11:53:28. There's no indication of any problem before that.

I saw that. I installed my second logger, but it didn't show any data. Then I closed Cumulus and on closing an error message box showed up, which immediately disappeared due to Microsoft's tremendously helping "send error report" service, which appeared then. Then I started Cumulus again and it immediately started working, i.e. the "download data" message box came up for a second and disappeared and then data display and logging started working - without having to reboot.
In the meantime I installed Mark Russinovich's Sysinternals Suite (http://technet.microsoft.com/en-us/sysi ... 42062.aspx), maybe this may help finding out, what thread dies when data akquisition stops. I will be out of the house until Sunday, so I will continue with that next week.