Battery check

[xairbusdriver]

Just unplugged the AC adaptor again. Checked good voltage, ~39 mA. Plugged back into Console. Ran through the Set up procedure, even though every thing was still as previously set.

Tools->Status:
Station Comms: Poor - Check Installation (84.01%). However, it started increasing and is now up to 84.45%. 
Comms Error: 23 and steady
Watchdog: OK
Good Data: 86xx and increasing
Sensor Errors: 1311 and steady

Tools->Hardware Options:
Transmitter Battery Status: all good after cycling through their tests
Console Voltage: 4.72 [removed link to the now castly photobucket.com site]

Console display: No longer showing "low battery voltage"

Resembles the DC-10s I used to fly. We called them "Electric Jets". Sometimes resetting circuit breakers wasn't enough. Sometimes it required shutting down all three jet motors, the APU, disconnecting ground power, and disconnecting the batteries. That was sometimes the only way to get things back in sequence! Basically, forcing all relays to relax and reboot the airplane! Only on the ground, of course. Also similar to the brain transplant I'm on the waiting list for!

Just after posting the above text:
Station Comms: Average - Check Installation (85.06%) and increasing
Good Data: 8906 and increasing
Sensor Errors: 1311 and steady

[dfw_pilot]

Todays ECAM/EICAS driven airplanes are even worse. ACARS and CPDLC circuit breakers have to be reset weekly on our 747's that came off the assembly line just months prior.

[xairbusdriver]

Woke up today to see the return of low console batteries both on the Console and the Hardware Options panel (1.72v!).

I bought a bunch of 1' "extension" cords (just a foot of cable between the male/female plugs) last month to help with handling 'wall warts and normally spaced multiple outlet boxes/panels. The Davis AC adapter is one of those slightly too big 'warts'. Added one of the 1' cords so there was no 'elbowing' by other plugs.

Console made the required beeping complaining about being unplugged for a few seconds. But the display is back to pre-set current date/time/etc., flashing "X", no 'low battery' message. Hardware Options now showing 4.72V. Had a few bad Comms, but holding at 2590. Good Comms 27319 and increasing. Valid data showing at web site.

Bad/lose AC outlet? We'll see. If things become unstable after 4pm here, I should still have at least an hour to contact Davis before everyone leaves for the weekend!

[Bull Winkus]

Just unplugged the AC adaptor again. Checked good voltage, ~39 mA. Plugged back into Console. Ran through the Set up procedure, even though every thing was still as previously set.

~~~

Voltage? Why are you reporting milliamp if you were checking voltage? If you are checking mA across the powered plug end, you are measuring current going through your tester. Are you doing this to determine if the adaptor is putting out? ? Color me confused?

[xairbusdriver]

Didn't record the actual voltage but well over 4.5. It was difficult enough just holding the leads against the paper clip (required to touch the deeply recessed center contact) and the slippery sleeve of the plug. The mA does, at least show some current available. I'd have to unplug the adapter (again!) to see its rated amperage (you are welcomed to check the Davis site for that info, BTW). Sorry for the confusion, I'm no electrician but I did help connect some Christmas lights on the porch last year!

Since you asked...
Looking at the Hardware Options window again and seeing a reported Console voltage now at 1.73V and the Console also reporting "Low Batteries". I'm going to contact Davis as soon as I post this.

[Bull Winkus]

Be sure and check the polarity of each individual battery in the console. You can also check that all batteries have about the same voltage. One weak one can spoil the party.

Sounds like you've got a mystery on your hands. Good luck!

 

[xairbusdriver]

Just finished talking with "Bruce" at Davis. Ran through some 'hidden' trouble-shooting steps (using the TEMP and HUM buttons). Bottom line is hat the Console simply is not seeing the batteries at all; zero voltage. But he also claims the center contact on the Console end of the plug is "flush" with the end of the plug. Mine is a full 1mm down, inside the end of the plug. That's why I had to use an unfolded paper clip to reach the center tap, the lead on my meter is ~3/32" diameter. It only touches the center contact when inserted a full 7/32" into the end.[removed link to the now castly photobucket.com site]
No center contact showing inside the black plastic tip.
[removed link to the now castly photobucket.com site]
There's something down there, but the flash is off center enough that it still doesn't show the center  contact.
Anyone willing to look at their plug (Console end) and report the center contact position?

Also tested the C cells, each one read 1.567v (no load). Still, the Console refused to display anything with only the C cells installed.

Have an RAM number. Should be getting a new Console and adapter within 7 - 10 days. Meanwhile, the thing seems to work fine on AC adapter power alone and it doesn't even draw any power from the batteries!

[xairbusdriver]

Be sure and check the polarity of each individual battery in the console.

What? Are you trying to say they should all be positive to negative?! What about the two on each end?! They aren't touching another battery at all!! Actually, I've been very close to an idiot who put the ISS battery in backwards! But I don't let him near anything electrical anymore!

Details, details, DETAILS!!!

Actually, the only reason I buy "Copper Top" batteries is that it's easier to tell if multiple batteries are aligned properly...

BTW, the only Console battery contact one can see easily is the positive one and it looks clean. The negative one has a spring mount and there is some mechanical force pushing them toward the positive end, but I can't actually see if the spring is still connected to that end of the circuit board. I'll let Davis tear the box apart to determine that... or anything else they can.

I will say that Davis had no problem with my having bought the hardware from Rainman. They had my info in their database, so they knew it's still under warranty

[elagache]

Dear X-Air and WeatherCat troubleshooters,

Just finished talking with "Bruce" at Davis. Ran through some 'hidden' trouble-shooting steps (using the TEMP and HUM buttons). Bottom line is hat the Console simply is not seeing the batteries at all; zero voltage.

Wow!  That's an odd sort of failure.  Did Bruce have any explanation for the problem?

Have an RAM number. Should be getting a new Console and adapter within 7 - 10 days. Meanwhile, the thing seems to work fine on AC adapter power alone and it doesn't even draw any power from the batteries!

Glad that Davis has stood behind their products and that you won't have to lose any data to get this problem sorted out!

Cheers, Edouard 

[xairbusdriver]

Press and hold those two buttons time and the Console will display the batteries total voltage on the bottom display line. Press DONE to return to the regularly scheduled display.

Mine would only display "BGN 15 BATTERY ? ?". I have no idea what "BGN" means, of course. Just did this procedure again, but this time the "15" changed to "20". There are several other numbers displayed, two of them seem to be the number of seconds since something happened, they count upwards during this mode. One may be the number of seconds since (AC) power was restored. The other may be just the number of seconds since this mode started. Other numbers have meaning only to Davis and possibly the IRS.

[xairbusdriver]

The Console seems happy enough to just repeat the low battery condition. BTW, the TEMP + HUM procedures is now saying "BGN 17 BATTERY ? ?", still no idea what he number means. Perhaps BGN stands for Batteries Going North? That would seem the opposite of "Going South (or West in the UK)" which seems to be the worst direction! WC seems fine, also. And there have been zero comms error since my last Console trouble-shooting.

[xairbusdriver]

The new Console came today. Managed to get it set up before leaving for a movie. Everything looked fine on the screen.

Not so much from WC. Looked at the shared screen for the mini and saw a no station found dialog. Selected the USB logger didn't help. WC Status showing nothing.

I remembered that during the Console Setup, I never saw the Baud Rate screen. That should be the last screen in the process. Perhaps I didn't completely seat the logger? Unplugged the AC adaptor, removed the batteries, pulled out the logger, reinserted it, firmly inserting it into the Console.

This time, running through the Set Up steps, I did get the baud rate screen, and confirmed that it was 19200. Restarted WC, again.

The sensor list (can't figure out how I looked at that, now ) shows the Wind Direction and Speed as invalid. However, the winds are about as calm as can be, so I'm not sure it's "invalid" or simply not changing.

WC Core reporting equal Good Data and Sensor Errors (~600 in both after ~20 minutes of running). Station Comms: is, obviously, "Bad (0.00%). However, Comms Errors is only 16 and holding.

I've Restarted both the mini and WC a couple of times. Un/Re-plugged the logger. Changed the USB cable (and port on the mini), searched for several terms (sensors, channels, comm(s), valid/invalid, etc.). Used the "Configure Comms & Exit" options twice (which really seems to simply Quit WC, after hitting command-Q again, since I have that method enabled).

TwoOne questions:
1. What else can I do?
2. Where is that sensor list window and why can't a search of the manual find it? Found a link in the WC Wiki that pointed to the thread where the Dev noted it is in the "Live Data" tool. While I am seeing the Wind sensor data as being "Invalid" I have no idea why it was working before I changed the Console and now doesn't. I suppose it means a trip up to the roof to check the wiring/cups/vane/solar panel/battery. I'll probably wait until the rain stops... next Monday, I think.

I think what this means is that the Console and WC are talking to each other fine. Just not getting any wind data.

At least with the bad Console, I was getting good data/comms! I'm about ready to re-install it and ignore the non-DC power method!

BTW, the TEMP + HUM button combo reports the DC output of the C cells. Mine now reads "BGN 16 BATTERY 4.8V". [removed link to the now castly photobucket.com site]

[xairbusdriver]

Just checking emails and found one from WC reporting that "Comms reset successful." That was probably the last time I rand the "Configure Comms and Exit" function. Not sure what that's supposed to do. AT least once after doing that, I think I got the 'cannot connect' dialog and selected the USB logger, again. I know for sure, the last time I used it, WC just started back normally, without reporting any comms problems. My bad for not keeping better trouble-shooting actions/results.

The new Console was installed ~12:15 and that's why I got two emails from WC:
1. "Comms to station have failed, trying to reset. Results to follow... TimeStamp: 12:20:44"
2. "Station comms reset FAILED. Weather is no longer updating. Please check station and USB/serial connections then reboot WeatherCat. TimeStamp: 12:21:03"

The reconnection message was: "Comms reset successful. TimeStamp: 15:55:03" It was a long, but interesting movie. Events with the Console were not as entertaining!

[elagache]

Dear X-Air and WeatherCat troubleshooters,

The new Console came today. Managed to get it set up before leaving for a movie. Everything looked fine on the screen.

  . . . . Okay, that's your first mistake!  Stay away from all that fantasy stuff and stick to "honest" (honest? ) documentaries! . . . 

If you can find any honest documentaries please let me know - I haven't seen one in such a long time!! 

TwoOne questions:
1. What else can I do?
2. Where is that sensor list window and why can't a search of the manual find it? Found a link in the WC Wiki that pointed to the thread where the Dev noted it is in the "Live Data" tool. While I am seeing the Wind sensor data as being "Invalid" I have no idea why it was working before I changed the Console and now doesn't. I suppose it means a trip up to the roof to check the wiring/cups/vane/solar panel/battery. I'll probably wait until the rain stops... next Monday, I think.

I think what this means is that the Console and WC are talking to each other fine. Just not getting any wind data.

That's extremely odd.  It seems incredibly unlikely that your anemometer would have failed at precisely the moment you installed your new console.  You still have the old console and it was working even for wind data - correct?  Could you swap the old console back to see if still reports no wind data?  If the old console works for wind data, then you have another bad console.  I can't imagine anything else.

Any other advice WeatherCat troubleshooters?

Edouard

P.S. Just had a momentary power outage that whacked the backup drive on my computer.  We'll see if Apple First Aid can revive da' patient.

[xairbusdriver]

I did get another email notice from WC just before the one in my last post. All of them occurred when I disconnected the old Console. Here's the one email that was the frist one to report problems... while I was speedily configuring the new Console:
"Sensor failure at sample time. Failed sensors are: External temperature, Pressure, Precipitation, Wind, External humidity, Internal temperature. Internal humidity.
TimeStamp: 12:20:24"

Could you swap the old console back to see if still reports no wind data?

Sure, don't have any more movies coming up! Maybe I can keep better records of actions/reactions...