Cumulus Support

Suddenly at dec. 1 my uploads stopped being sent. The station has been working flawlessly since mid july and the receiving module shows it is receving the data. I updated to Cumulus v1.9.2 when it was available.

I have unplugged the receiving unit data logger and then tried a different USB port in case that was it. To no avail.

I believe the setup is correct since it has been sending data for that length of time.

Am wondering if I should be downloading to a specific spot on my drive. Have UPS backup and have had no issues there. Have stopped program, powered down computer (windows XP) and re-booted, then re-started cumulus with no solution.

Errrors are listed below after the USB connection was reattached.

Using Ambient WS 2080 with lithium batteries installed. Thanks in advance, BOB.

FROM ERROR:

12/2/2011 7:35:40 AM : The station is not initialised
12/2/2011 7:35:46 AM : FTP Connect Error, Error code = 11004
12/2/2011 7:35:46 AM : FTP Connect Error, Error code = 11004
12/2/2011 7:35:46 AM : FTP Connect Error, Error code = 11004
12/2/2011 7:35:46 AM : FTP Connect Timeout

UPDATE:
Looking back I had this happen once before and then I loaded the v1.9.2 update figuring it was the flaw in the software....that resolved the problem then.

Also you can look at the previous two days graphs on the website listed below and see that the data was also flatlining
copy and paste
http://www.wunderground.com/weatherstat ... =IONNIAGA5

It looks like you have two unrelated problems. The first is that the 'fixed block' of memory in your station does not contain the expected values:

12/2/2011 7:35:40 AM : The station is not initialised

The diags file will give more information. You can over-ride the checks that Cumulus does on your memory, and that might get you going (or you might just get corrupt data being read) by stopping Cumulus and editing Cumulus.ini. In the [Station] section, add a line

EWdisablecheckinit=1

The other problem is that Cumulus is unable to connect to your ftp server (it's not getting a response):

12/2/2011 7:35:46 AM : FTP Connect Error, Error code = 11004
12/2/2011 7:35:46 AM : FTP Connect Error, Error code = 11004
12/2/2011 7:35:46 AM : FTP Connect Error, Error code = 11004
12/2/2011 7:35:46 AM : FTP Connect Timeout[/color]

You will need to investigate that yourself.

I noticed there is an update as of dec. 1 for new build 1022....would that update help this?
thanks for your speedy reply...

BOB7376 wrote:I noticed there is an update as of dec. 1 for new build 1022....would that update help this?

No, because it's not a problem with Cumulus.

HAve added line you sugested and the program took time to update the accumulated data stored in the ambient reciever logger....then green light was flashing on the catchup heading.

The red error message read as follows after the green ligh on catchup is out:

12/2/2011 10:16:00 AM : Data input appears to have stopped - check your station and connections
12/2/2011 10:16:30 AM : FTP Connect Error, Error code = 11004
12/2/2011 10:16:30 AM : FTP Connect Error, Error code = 11004
12/2/2011 10:16:30 AM : FTP Connect Error, Error code = 11004
12/2/2011 10:16:30 AM : FTP Connect Timeout
12/2/2011 10:17:00 AM : Data input appears to have stopped - check your station and connections
12/2/2011 10:18:00 AM : Data input appears to have stopped - check your station and connections
12/2/2011 10:19:00 AM : Data input appears to have stopped - check your station and connections
12/2/2011 10:20:00 AM : Data input appears to have stopped - check your station and connections
12/2/2011 10:20:09 AM : FTP Connect Error, Error code = 11004
12/2/2011 10:20:09 AM : FTP Connect Error, Error code = 11004
12/2/2011 10:20:09 AM : FTP Connect Error, Error code = 11004
12/2/2011 10:20:09 AM : FTP Connect Timeout
12/2/2011 10:21:00 AM : Data input appears to have stopped - check your station and connections
12/2/2011 10:22:00 AM : Data input appears to have stopped - check your station and connections
12/2/2011 10:23:01 AM : Data input appears to have stopped - check your station and connections
12/2/2011 10:24:00 AM : Data input appears to have stopped - check your station and connections

The have been no updates to the computer and software, this is why I am so perplexed.

Thanks for your speedy reply though.

It looks like Cumulus isn't getting a response from your station. The diags files may have more information.

2011 12 03 station investigation.

DATA updated (eventually after several interventions).

After that update took quite a while for data to appear on Wunderground.
Since that update time station data has flatlined.

Cumulus logo sits on tray. Right click and select RESTORE shows dialogue box show Error Blinking red.

Right click on cumuls and select web update , dialogue box says FTP PROGRESS “CONNECT TIMEOUT”

Interestingly before right clicking on cumulus the data box that show when you hover over an icon was showing the flatlined data. After selecting update….it is showing current data.

Closed cumulus. Waited, then re-started Cumulus. Dialogue box shows to update to web then closes in just a couple of seconds. Please wait dialoque box shows “DOWNLOADING DATA” and “PLEASE WAIT” but no activity on the gas gauge unlike previous times when data had been stored but no data uploaded e.g. during station maintenance, repositioning of aerometer and sensors, etc.

Closed zone alarm in case those settings had changed(or an update had occurred) and was unable to update web.

Shut down computer and restarted….then started Cumulus downloaded data and cumulus shows current data.

Still unable to update to web however using update web selection.

Have attached the 8 files in diagnostics and two photos of the cumulus screen before and after download data occurred as well as file structure image for cumulus.

Thanks in advance.

You have some sort of issue with your station and/or PC.

The first block of memory read from your station is garbage:

12/3/2011 07:21:56.140 : Request EW data block, addr = 000000
12/3/2011 07:21:56.156 : EWUSB: EW startup data line 01 53 53 53 53 53 53 53 53
12/3/2011 07:21:56.171 : EWUSB: EW startup data line 02 53 53 53 53 53 53 53 53
12/3/2011 07:21:56.171 : EWUSB: EW startup data line 03 05 20 02 3B 11 00 00 00
12/3/2011 07:21:56.187 : EWUSB: EW startup data line 04 85 00 00 F0 0F 00 F0 47
12/3/2011 07:21:56.187 : Request EW data block, addr = 000020
12/3/2011 07:21:56.203 : EWUSB: EW startup data line 05 3C 28 17 14 00 00 00 00
12/3/2011 07:21:56.203 : EWUSB: Read pressure values: rel=1030.0 abs=514.3 offset =515.7

Those bytes of 53 shouldn't be there, and your absolute pressure is off the scale.

Then the station stops responding to requests for data:

12/3/2011 07:23:00.703 : *** Data input appears to have stopped

Then you get errors trying to connect to your ftp server:

12/3/2011 07:23:05.140 : FTPRequestDone ftpConnectAsync Errcode = 11004

The 11004 code means that Cumulus was unable to connect.

By the way, there are some tips here for taking screen shots: http://wiki.sandaysoft.com/a/Screen_capture

Have you tried resetting the station?

what would be the best way to reset...
1. remove the USB connection and then the batteries from the receiving unit?
or
????

BTW thanks for your help on this...cause I'm just getting confused and frustrated....old story when the weather is nice and you've got time..all works well.....
When you got no time to troubleshoot...trouble finds you...lol....

BOB7376 wrote:what would be the best way to reset...
1. remove the USB connection and then the batteries from the receiving unit?

Yes, that's right. Do it with Cumulus stopped. Once it's picked up the signal from the remote sensor again, start Cumulus and see if the station is sending what's expected.

BTW thanks for your help on this...cause I'm just getting confused and frustrated....old story when the weather is nice and you've got time..all works well.....
When you got no time to troubleshoot...trouble finds you...lol....

Fine Offset stations tend to keep you busy!

Well we have ignition!
After much thinking and pondering etc., I remembered that I had a problem in the early fall with the receiving console. At that time, I found a trace of white substance on the back of the console when I had inspected the connections. When I had removed the battery cover I found a bit of corrosion. I cleaned the terminals, replaced the batteries.

So this morning after a full night's sleep to think this out...I referred to my notes and found the previous occurrence. Even though the console was displaying data correctly, I check the battery compartment. Photos are attached with much more corrosion this time. Cleaned and replace so will contact Ambient on monday since the unit has a one year warranty.

Reset the console with all the factors and behold data was sent to computer and cumulus sent it on. "downloading data" followed by cumulus uploading to the net.

So first problem may be cured (at least temporarily). thanks for your help...especially on the screen saver software.
Have included screen shots of my internet screen in case something pops out at you that I am not doing correctly. Have never been able to send data to weatherbug...so this may be a blessing in disguise....

Once again thanks....the station has not been a great deal of work..and it has been interesting for sure....

will attach screen shots and hope the size of the images are better this time..first time poster...

Where exactly are you wanting to upload data to? You've put "Jones Creek Canada" for the name of your ftp server, which is not a valid name, and not supplied any other details, so I assume you don't actually have your own web site? You need to clear that field and untick 'auto update', that will stop the ftp errors.

Your WU and PWS pages appear to be updating OK, so I don't know what it is that you think isn't working?

You are correct (again). I have not set up a website since I wanted to see what time would be involved in this aspect alone.

Have followed you suggestions regarding name removal.

My rainfall numbers show activity...we have clear (now) was cloudy earlier but no rain. It may have been data corruption from previously stored data....not sure and I know that makes no sense.....

Have attached graphs from WU Thanks again Steve..will contribute for sure.

UPDATE:
Have contacted Ambient in Arizona and after some discussion, they have agreed to swap out the console. Apparently, they have never seen this problem before.....I am sending out the console this week and hope to have the new one....up and operating ASAP.

Will update and definitely check the new unit when it arrives periodically to make sure the same thing doesn't happen to the batteries.

Steve, thanks for your assistance this week....much appreciated.

Bob.