User Manual

Table Of Contents

User Manual

Page 37 of 45

6. Troubleshooting and Log Analysis

Common Abnormality Debugging

6.1.1 Abnormal Channel Status

A normal or abnormal channel is used to describe whether the RS485 physical link is working. That is:

(1) When communication timeouts occur for all measurements of a sensor, the channel is set to abnormal;

(2) When a sensor has at least one measured value that gets transmitted (no matter if it is an error code or data

returned by the sensor), the channel status is normal

6.1.2 Error: No sensor found. Is the sensor connected

Debug from the following aspects:

⚫ Make sure the sensor is connected to one of the four ports on Sensor Hub;

⚫ Make sure the wire sequence (positive and negative / RS485 A, B) of the sensor wiring is correct;

⚫ Make sure the sensor Modbus address is consistent with the address set in the Sensor Hub Configuration Tool;

⚫ Make sure that the sensor power supply mode configuration is correct;

⚫ Ensure that the warm-up time, start-up time and response timeout meet the sensor requirements;

⚫ Check that the function codes and registers of the measurements are configured correctly;

6.1.3 Error: [ERROR] rs485 err code: XX XX

For some sensors that require a certain warm-up time, the sensor will return a function error code if it is not

provided enough warm-up time before communicating actively.

When testing the sensor, firstly check the presence of the sensor. To check that you need to wait for the start-

up time instead of waiting for the warm-up time. For example, the sensor startup time is 1s, and the warm-up time

takes 5 minutes. After Sensor Hub powers on the sensor, it only takes 1s to communicate. In this case, you will

receive a function code error. [ERROR] rs485 err code will appear in the window, and when collecting data, it will

wait for the warm-up time before communicating to ensure that the right data can be obtained.