Honeywell ControlEdge HC900 Controller Troubleshooting Manual

Restore default configuration: If the module is recognized but all channels have bad values, it may be due to a damaged internal configuration table of the module. Use the 'Upload I/O Config' feature of Designer to read the correct configuration from the controller, then execute 'Factory Defaults' on the module and download it again.

Hot plug precautions:

Hot swapping is only applicable to I/O modules and does not support hot swapping of CPU or scanner modules (S50/S75 Scanner). Replacing the scanner must be powered off.

When replacing non redundant I/O modules in a redundant system, both the primary and backup controllers will sense the removal/insertion of the module, but data will only be restored when the serial number of the new module matches the configuration.

After hot plugging, the output state of the digital output module returns to the safe default value (usually preset in the configuration), and the command must be reissued by the operation station.

3.3 Modbus TCP communication interruption or response timeout

phenomenon

The upper computer (such as SCADA, HMI) cannot read the real-time data of HC900, and the Designer software cannot connect to the controller through Ethernet.

The Link/Activity LED on the Ethernet port of the controller is not lit or only flashing yellow.

Modbus TCP client reports' Connection timeout 'or' Socket error '.

Possible reasons:

IP address conflict or subnet mask/gateway configuration error.

Ethernet switch failure or port blockage (such as broadcast storm).

Controller Modbus/TCP service crash (internal watchdog not reset).

The number of hosts connected simultaneously exceeds the limit (C50/C70/C75 up to 10 concurrent connections, C30 up to 5).

The firewall or network security policy intercepted the Modbus TCP port (default 502).

Exclusion steps:

Physical layer inspection: Use a cable tester to verify the continuity and line sequence of Ethernet cables (recommended to use shielded CAT5e). Observe the corresponding port LED of the switch. If it is constantly on but not flashing, there may be a link negotiation issue. The HC900 Ethernet port supports MDIX auto flip, but if connecting to an old switch, try using a crossover cable.

Verify IP configuration: Connect the controller through the serial port (RS-485) of Designer (USB-RS485 converter is required), Honeywell p/n 50089787-501）。 View the IP address, subnet mask, and default gateway of the Ethernet port in "Controller" ->"Communications". Confirm that it is on the same logical subnet as the upper computer. Note: The two Ethernet ports of C70/C75 must be configured on different subnets and cannot be the same.

Ping test: Use the command line to ping the controller IP from the upper computer. If it doesn't work, check the switch VLAN settings and port security. If it is connected but Modbus TCP is not, use a port scanning tool (such as Nmap) to check if port 502 is open.

Check concurrent connections: On the diagnostic page of Designer, check the "Ethernet Host Connections" counter. If the maximum value is reached, close unused SCADA clients or add upper computer connection pool reuse. The maximum number of connections allowed by Modbus TCP includes Designer connections. It is recommended to disconnect unnecessary Designer sessions during production.

Restart communication stack (without shutdown): Use the function block "System Reset" to reset only Ethernet communication (without restarting the controller). Specifically, add a temporary pulse to trigger the "CfgReset" parameter in the control strategy (caution should be exercised, only resetting the communication submodule). A safer way: Send Modbus commands through the RS-485 port to reset the TCP stack.

Firmware upgrade: If Modbus TCP service freezes frequently, please upgrade to v6.300 or above, which enhances the TCP stack's ability to recover from exceptions.

HART IP communication fault supplement: If using HART IP to communicate with FDM, the default TCP port is 5094. Check if the HART IP server is enabled (check "Enable HART IP Server" in Designer). Simultaneously confirm that there is no conflict with the HART field device address (0-15). When using the Wireless HART adapter, it is necessary to check the signal strength.

3.4 Power redundancy failure or frequent controller restarts

phenomenon

The "Power supply fail" alarm appears in the system log, but there is still voltage input on site.

The controller restarts periodically, and the I/O state briefly disappears before recovering.

The "OK" LED of one module in the redundant power module is turned off.

Possible reasons:

Internal faults within a single power module, such as aging capacitors and blown fuses.

External power supply voltage fluctuation exceeds the allowable range (P01 module: 90~264VAC; P24 module: 21-29VDC).

The redundant power connectors on the rack expansion backplane are loose.

High ambient temperature leads to overheating protection of the power module.

Exclusion steps:

Measure input voltage: Use a multimeter to measure the voltage at the input end of the power module. For P01, ensure the voltage is between 90~264VAC and the frequency is between 47~63Hz; for P24, ensure the voltage is between 21~29VDC and the ripple is less than 5%.