Cumulus stopped - Interesting observation

[steve]

I have a debug txt which shows errors in arithmetic.

It's the timestamp in the debug logger overflowing; it does that if it's left switched on. Do you have it switched on?

[vern7485]

Thanks for the info. I am not aware of switching it on. Please give me a clue as to how to switch it off. I found data logger switch on. Is it in a configuration file I need to edit manually? Thanks a lot for your help and quick response.
Charlie

[steve]

You turn it on (and off again) by selecting 'Debug log' on the Configuration menu (a check mark appears when it's on), but it turns itself off if you restart Cumulus. You can turn it on permanently by setting "Logging=1" in the [Station] section of cumulus.ini - but I assume you haven't done either of those as you would surely have remembered? It's rather odd, though, if you didn't, as that's exactly the error that occurs if it gets left on, and it did crash in the debug log component. The debug log component is a bit strange though, in that its code can get executed even when it's not turned on; it just doesn't write anything to the file. Needs replacing, really.

[vern7485]

Thanks Steve for the response. I turned the debug logging on to get the text I sent you. So, maybe the debug log on caused the overflow. Cumulus was hung in some sort of loop and I turned debug logging on and asked cumulus to exit. I got a crash and exit. The dump may not be useful. I guess I need to know how to safely cause the dump when it is hung? Thanks for the support.

[steve]

You can't cause one of those dumps manually, they are produced automatically when an unhandled exception occurs. If it hangs, all you can do is exit, either by using the menu, if it lets you, or by terminating the process. The diags files may then give a clue as to what the problem was.

[vern7485]

Thanks again Steve, here are two diag files close to the time. It was complaining about not able to write to usb. I looked at the events log for windows nothing was recorded as at that time. Thanks again.

[steve]

Yes, there was some sort of problem with your station and/or USB connection, so Cumulus could no longer communicate with it. Then when you restarted Cumulus, it couldn't find the station.

[vern7485]

Steve
Yes, I agree. My Windows' log shows no problems with the USB2.0. I have a printer on it, a 250GB hard disk which is only active when I look for an archived file, etc. No USB events recorded. So, my guess would be the station, WH1080 I will look for the paperwork on it to see what the warranty is if any. Thanks for your help.
Charlie
OBTW It has been running now for several days, i.e since the 4th.

[steve]

I know of at least two cases where the USB socket in the station has been poorly soldered causing intermittent connections. If you're at all handy in that direction, and don't mind risking the warranty, you could open her up and have a look...

[Gina]

Also, try another USB cable - I had a faulty one.

[vern7485]

Steve,
Well, I believe I have solved issue for me; the usb cable was an extended one which picked up a stray rf signal nearby and jammed the usb for the wh1080. Solution I moved the station closer to the computer. Time will tell but I believe it has been fixed.