Troubleshooting

Many people will encounter one or more situations where they cannot communicate with the instrument.  In 90% of the cases, this is not a problem with the electronics but with the configuration or some other piece of hardware.  Here are a few tips:  " />'>

a) Spend a few minutes checking all the dumb things - make sure that the serial port is connected to the PC (make sure it is the right port!, that the power connectors are all properly seated, that the underwater connector is properly mated, etc.

b) Check the troubleshooting section of the manual.  Among other things, it explains how to test the computer serial port.

c) The most common culprit is the power supply.  Measure the voltage output but don't stop there - some times the power supply is not working properly and cannot supply the necessary current.  In general, it is a great idea to measure the current with an amp-meter or with a lab supply.  If the current is zero, the power does not reach the electronics and the failure could be in the cable or maybe the internal connector is not properly attached.

d) Be aware of the hardbreak/softbreak issue.  Nortek changed from one type of "wake-up!" signal to another in 2001/2002 (exact time varies with the instrument) and you may have to toggle the break setting in the Communication / Serial port menu to change from one type of break to another.  Use the terminal emulator window to check for the desired effect; the response from the instrument may be garbled if the baud rate is wrong but something will always show up on the screen if you send a break and the electronics is online.

I have two Vectors laying on my benchtop.  One I can communicate with  " />'> , one I can't " />'> .  Same computer, software, comms cable, power supply.
I've used the default BREAK that is initiated from the COMMUNICATION/Terminal Emulator dialog in Vector v1.25 software, with no response from the 'mute' Vector.
Are there any other steps I can take to restore comms?
Thanks,
-Chris

Dear Chris

The first thing I normally check in a case like this is if the units draws any current.  If you put an amp meter in series with the power supply line (or if you have a DC power supply that shows you the current) you can see if the unit is "dead" or not.

If it is "dead", it is time to open it up and take a look inside.

Best regards, Atle Lohrmann

Atle,

Thank you for the reply.  Directly upon applying 12VDC through the comms cable, with a multimeter (10A fused scale, dial set to 10A) wired in series to my Vector, it reads 0.03A (max precision.)  This is about what I see from my power supply (varies from 0.02-0.04).

I don't know about 'death', but is rigor mortis setting in?  Kidding aside, I still cannot communicate with the ADV.  What did you mean by 'opening it up.'  I have already opened the battery/comms side of the case to verify no water leakage, wire-loom intact, etc.  Are you suggesting opening the probe-side of the housing?

Thanks,
-Chris

Dear Chris,

These are typical current drains

Command mode 8-12mA
Power down 1-2mA
Wait mode 2-4mA
Measurement mode 50-150mA

Your reading is something in between. Which power level was the Vector deployed with last time?
Please open the teminal emulator and check if it comes any characters at all. Turn det power on and off and see it anything displays then.

Are you running RS232 or RS422?

Best Regards
Jonas Røstad

Dear Jonas,

The last time I attempted to deploy the Vector (when the instrument ceased to communicate) it was running from a 11.7V lithium battery.

I am using RS232 to communicate with the instrument.  I have cycled power (numerous times) while using the terminal emulator.  I get absolutely no character response in the window (despite seeing that the unit is drawing current.)

Again, when Vector v1.25 tries to autoconnect (cycling through all baud configs), it is unable to detect the instrument (baud.)

Thank you for the help,
-Chris

Dear Jonas,
Ooops!  By 'power level' did you mean from the dialog on the Advanced settings tab in Deployment Planning?  If so, I configured it for "HIGH".
Thanks,
-Chris

Dear Chris,

This is starting to sound like a real hardware failure. " />'>
My last suggestion is that you try communicationg with it via RS422 (if you have the harness and cable available). If not - please contact inquiry@nortek.no for an RMA-number for returning the instrument for repair.

Best Regards
Jonas Røstad

Or call Malcolm in Annapolis! " />'>

I have a similar problem to Chris's, just with Aquadopps instead of Vectors.  I have 4 of them.  I can connect with three of them, and they are now deployed.  I haven't been able to communicate with the fourth one.  It sends garbled responses when I try to send it a break.  Is there a way for me to automatically cycle through all of the possible connection speed combinations within AquaPro?  I've tried many but not all of the possible combinations.  If I use a multimeter to find the output currents and voltages, what should I see?  
Thanks,
-Jon

Dear Jon,

When receiving garbled responses you are right when suspecting wrong baudrate.
The software has a baudrate scanner if you choose  Stop data collection in the instrument softwares main menu.
The voltage levels of the RS232 signal should be +/- 6,6V.

Best Regards
Jonas Røstad