Cumulus Support

Good Day, All! I am a new user and I have my station up and running and reporting to weatherunderground and am still awaiting approval from WeatherBug and CWOP.

Last night was the first real trial of my station and software. When I checked on the station this morning, I found several dozen occurrences of "Data input appears to have stopped - check your station and connections" and it occurs every few minutes with no real visible pattern. However, it appears to fix itself after a short time. Is there a setting I'm missing here?

It sounds like you have a faulty connection between your station and PC. If you zip up the diags folder and attach it, I'll see if I can see anything.

Here you go! Thanks for the quick reply!

I can't see anything in there explaining the 'data stopped' warnings, but something strange seems to have been happening which may or may not be related. In the early hours of the morning (between approx 0130 and 0330) Cumulus was stopped and restarted several times without closing down properly - do you know what the cause of that was? It was following this that the 'data stopped' warnings started.

At that time, I had the software set to restart automatically upon apparent input loss. I let the program run unattended for a couple hours and when I came back I saw that the program had been nearly continuously restarting itself. The only thing I figure could be the problem, then is the USB extension cable I'm using. I'll get a different cable and try that on Friday.

OK, so I didn't get a new cable yet BUT I changed some settings on my station. The computer I'm using for the weather station is the same one I use for all my amateur radio stuff. For simplicity, I've had the computer's clock set to GMT time as opposed to -6 which is my local time. I decided for weather reporting purposes that changing my computer's clock to -6 would be a good idea. Once I did that and deleted all the previous data records, the error messages stopped. I've been reporting for about an hour now without a single error message so I think that fixed it. Odd. I'm just glad it's working as designed, however.