Chapter 12 Troubleshooting 12.2.3 BUS FAULT LED Indicator’s Being ON When a CPU module detects an error, the BUS FAULT LED indicator on the CPU module is ON. The BUS FAULT LED indicator on the CPU module corresponds to the ERROR LED indicator on an I/O module. If an error occurs in an I/O module, the status of the BUS FAULT LED indicator on the CPU module is the same as that of the ERROR LED indicator on the I/O module. If there are errors occurring in the I/O modules, the BUS FAULT LED indicator on the CPU module will be ON.
For example, the BUS FAULT LED indicator on the CPU module will be ON if the ERROR LED indicator on I/O module A is ON and the ERROR LED indicator on I/O module B blinks. If the ERROR LED indicator on I/O module B still blinks after the error occurring in I/O module A is eliminated, the BUS FAULT LED indicator on the CPU module will blink. Please refer to sections 12.4.2~12.4.8 in this manual for more information about the LED indicators. Users can get the remedies for the errors detected by a CPU module from the table below. If the error code which users get is not listed in the table below, users need to check whether the I/O module operates normally.
Please refer to section 12.3 in this manual for more information about the troubleshooting for I/O modules. 12-11 Error Description Remedy code 16#6111 The specified email address does not exist. (SM1112) 1. Check whether the email address is correct. 2. Set the Ethernet parameter for the CPU module in HWCONFIG again. 16#6200 The remote IP address set in the TCP socket function is illegal. (SM1196) 1. Check the program and the related special data registers. 2. Set the Ethernet parameter for the CPU module in HWCONFIG again. 16#6209 The remote IP address set in the UDP socket function is illegal. (SM1196) 1. Check the program and the related special data registers. 2.
Set the Ethernet parameter for the CPU module in HWCONFIG again. 16#6300 Only auxiliary relays, data registers, and link registers can be used in the Ether Link. Check the setting of the Ether Link in NWCONFIG, and download it again. 16#6301 The device used in the Ether Link exceeds the device range. Check whether the device used in the Ether Link is within the device range supported by the CPU module. 16#6302 The length of the data exchanged in the Ether Link exceeds the limit. Check whether the length of the data exchanged in the Ether Link is within the range supported by the CPU module. 16#6305 The node used in the communication command is different from the local node.
Check the setting of the Ether Link in NWCONFIG, and download it again. 16#630A The module ID or the setting of the module is different from the setting in the Ether Link. 1. Check the setting of the parameter in HWCONFIG. 2. Check the setting of the Ether Link in NWCONFIG. 16#630B The setting of the netmask address for the CPU or the module is different from the setting in the Ether Link. 1. Check the setting of the parameter in HWCONFIG. 2. Check the setting of the Ether Link in NWCONFIG. 16#6500 An error occurs when a data exchange function is initialized.
(SM699) Check whether the sum of the number of Modbus TCP data exchange blocks and the number of the Ether link data exchange blocks exceeds the system specifications, and download the setting again.