Welcome to the Cumulus Support forum.

Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025

Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024

Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)

Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki

If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080

Recurring Data Input Error

Discussion specific to Fine Offset and similar rebadged weather stations
Post Reply
User avatar
KJ4KTW
Posts: 12
Joined: Wed 04 Jan 2012 2:17 pm
Weather Station: Davis Vantage Vue (KJ4KTW-13)
Operating System: Windows XP SP3
Location: Ingleside, TX, USA
Contact:

Recurring Data Input Error

Post by KJ4KTW »

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?
User avatar
steve
Cumulus Author
Posts: 26672
Joined: Mon 02 Jun 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: Recurring Data Input Error

Post by steve »

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.
Steve
User avatar
KJ4KTW
Posts: 12
Joined: Wed 04 Jan 2012 2:17 pm
Weather Station: Davis Vantage Vue (KJ4KTW-13)
Operating System: Windows XP SP3
Location: Ingleside, TX, USA
Contact:

Re: Recurring Data Input Error

Post by KJ4KTW »

Here you go! Thanks for the quick reply!
You do not have the required permissions to view the files attached to this post.
User avatar
steve
Cumulus Author
Posts: 26672
Joined: Mon 02 Jun 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: Recurring Data Input Error

Post by steve »

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.
Steve
User avatar
KJ4KTW
Posts: 12
Joined: Wed 04 Jan 2012 2:17 pm
Weather Station: Davis Vantage Vue (KJ4KTW-13)
Operating System: Windows XP SP3
Location: Ingleside, TX, USA
Contact:

Re: Recurring Data Input Error

Post by KJ4KTW »

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.
User avatar
KJ4KTW
Posts: 12
Joined: Wed 04 Jan 2012 2:17 pm
Weather Station: Davis Vantage Vue (KJ4KTW-13)
Operating System: Windows XP SP3
Location: Ingleside, TX, USA
Contact:

Re: Recurring Data Input Error

Post by KJ4KTW »

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. :)
Post Reply