Page 1 of 1

Cumulus Data Not Updating

Posted: Thu 12 Nov 2015 11:42 pm
by mmosier1
I have an Ambient Weather WS-2080A that is showing correct data. The station is defined in Cumulus as Fine Offset under Windows10. It had been working fine, but Cumulus is no longer updating. I've reset the WS-2080A by removing batteries, reset the USB, rebooted my PC. Nothing seems to correct the problem.

Any ideas?

Thanks for any help.

Mike

Re: Cumulus Data Not Updating

Posted: Fri 13 Nov 2015 8:38 am
by steve
If you zip up the diags folder and attach it to a reply in this thread, I'll take a look.

Re: Cumulus Data Not Updating

Posted: Tue 24 Nov 2015 3:32 am
by mmosier1
I've attached the diagnostics file. I appreciate any help you can offer.

Mike
cumulus.zip

Re: Cumulus Data Not Updating

Posted: Tue 24 Nov 2015 9:18 am
by steve
It seems to be getting corrupt readings from the station. It keeps saying 'sensor contact lost', but I'm not sure that's actually the case, I think it's just that the garbage data it's getting happens to have the 'contact lost' bit set. The station is apparently using the same memory location all the time (you have the interval set to 30 minutes, so it should have moved on to the next location a few times in the period that the log you've uploaded covers) but the data in that location doesn't seem to be changing anyway.

I would suggest resetting the console, but as you've already tried that, I don't have any other suggestions, other than perhaps trying a different USB port and a different cable (preferably one with ferrite chokes). You definitely did a full reset - removed the batteries and the USB cable at the same time, for a few minutes?

Re: Cumulus Data Not Updating

Posted: Wed 25 Nov 2015 1:26 am
by mmosier1
I just did another reset and now I have bogus data showing. And it's only for a few fields. I also tried holding the up arrow to reset. No luck. I think the unit has totally failed at this point.

Mike

Re: Cumulus Data Not Updating

Posted: Wed 25 Nov 2015 8:53 am
by steve
Resetting can cause bogus data for a few readings on some stations (those which are downloaded from the logger at startup), as the memory doesn't get cleared, just the current pointer gets reset. But if it continues to get bogus data once it's switched to live data, then it does look like some kind of problem with the console. You should check with some other software before buying a new console or station, though.