User's Guide ______________________________________________________________________
208 _________________________________________________________________ M211296EN-A
6. Disconnect the power and replace the communication modules.
- Replace one module at a time and try to restart the system to
find out the damaged one.
- Restart the system.
7. The QML logger does not receive commands entered in the AWS
Client software.
- Check the maintenance cable connection and that you have the
correct maintenance cable in use.
- The terminal connection is not open.
- Type open and press ENTER. Note that the command must be
typed exactly correctly before it can be executed and that the
command is not echoed on the screen.
- The port settings on PC and QML logger are not matching
- Use settings 9600bps, 8 data, 1 stop, no parity on PC.
8. Has someone made any software or hardware changes to the station
prior to malfunction? If so, could those changes have an effect on
the operation?
a. When you have loaded a new setup:
- Make sure you have the original setup and the new setup
saved as an .adc file.
- Reload the original setup and verify that the system starts
and runs with the original setup.
b. When you have installed new hardware:
- Disconnect the new hardware.
- Reload the original setup and verify that the system starts
and runs.
- Connect the new hardware.
- Reload the new setup and verify that the system starts and
runs.
9. Sensor(s) are not working properly.
a. Are there one or multiple malfunctioning sensors? Multiple
simultaneous sensor malfunctions in the same QML logger
often indicate a damaged logger.
b. Check the output of the warnings and errors commands for
indication of the probable cause.
- Connect the maintenance cable and start the AWS Client
software. Type commands warnings and errors. For
details, see section Warnings and Errors on page 219.
- Pay also attention to the message related to the excitation
voltages. If the damaged sensor is powered by the logger,
it may cause an overload.
To Next Page
Loading...
