Troubleshooting; Writing A Problem Report; Table 38 Troubleshooting Aqt530 - Vaisala AQT530 Configuration Manual

7. Troubleshooting
If the product does not work as it should, check all cables and connectors.
Check the maintenance needs.
If the failure persists, contact Vaisala technical support.
Table 38 Troubleshooting AQT530
Problem
Measurement failure or irrelevant
data values.
No response to any commands.
No response to Modbus query.
7.1 Writing a problem report
When troubleshooting the product, write a problem report including:
• What failed (what worked / did not work)?
• Where did it fail (location and environment)?
• When did it fail (date, immediately / after a while / periodically / randomly)?
• How many failed (only one defect / other same or similar defects / several failures in
one unit)?
• What was done when the failure was noticed?
• What was connected to the product and to which connectors?
Probable cause
The settings are incorrect.
There is a hardware failure.
Wiring is wrong.
Operational power is not
connected.
Baud rate or other serial property
of the device is different from the
host.
RS-485 wiring is wrong.
Chapter 7 – Troubleshooting
Remedy
Contact Vaisala technical support.
Check the wiring.
Check the operating voltage.
Connect the serial cable and check
the serial port settings of the
device with a terminal program.
Do the following:
1. Configure human-readable
ASCII CSV report, see
Configuring ASCII CSV data
sending (page 21).
2. Verify that ASCII CSV report is
sent every 60 s to RS-485 port.
If data is not coming through,
change the wiring of pins 5 and
6. See M12 pinout and wiring
(page 55).
3. Configure original Modbus
mode (Modbus RTU or
Modbus ASCII) back to the
device, see Configuring Modbus
interface (page 20).
53