Motorola ACE3600 RTU Troubleshooting Guide

Motorola ACE3600 RTU Troubleshooting Guide

ACE3600 RTU often plays a triple role of "on-site data acquisition+local logic judgment+remote communication" in SCADA scenarios such as pump stations, sewage treatment, substation monitoring, distribution automation, communication station monitoring, and remote meter reading. During field maintenance, many failures are not caused by single module damage, but by the superposition of multiple factors such as power margin, extended frame configuration, communication link parameters, I/O filtering and hold value settings. When replacing or expanding the ACE3600 RTU, it is recommended to treat it as a small control system for inventory purposes, rather than just replacing one board.

Perform system inventory before replacement and expansion

The ACE3600 RTU adopts a modular structure of rack, power supply, CPU, and I/O modules. The rack can choose 0, 3, 5, 7, or 8 I/O slots. The 0-slot rack is only equipped with power supply and CPU; The 8-slot rack can be wall mounted or installed in a 19 inch cabinet. When replacing a discontinued module on site, the first step should be to record the slot position, order number, I/O type, number of terminal blocks, and on-site wiring method of the original module. The I/O module of ACE3600 supports hot swapping, but hot swapping should only be applied to the module itself and should not be used to disassemble the backplane, expand power cables, or communication cables when they are live.

The second step is to verify the CPU capability. Both CPU 3610 and CPU 3640 use 32-bit processors and real-time multitasking firmware, but I/O expansion must use CPU 3640 with Eth1 Ethernet port. If the original host rack CPU3610 on site is planned to add expansion frames, simply replacing the expansion module will not achieve expansion, and the CPU must be upgraded and the STS site configuration rechecked. There are SI1 and SI2 serial ports as well as PI1 and PI2 plug-in ports on the CPU module. SI1 can be configured as RS232 or RS485, SI2 is RS232, and CPU3640 also comes with a 10/100BaseT Ethernet port. After replacing the CPU, the serial protocol, baud rate, IP address, link ID, and FEP/IP gateway address should be checked to avoid "hardware replacement but communication still disconnected".

The third step is to backup STS configuration and applications. The site configuration, I/O link table, KLV/PDV predefined values, communication ports, and IP conversion table of ACE3600 all rely on STS management. If only the hardware is restored without downloading the configuration after replacing the module, the CPU may not be able to recognize the actual I/O combination, and the expansion module may also restart repeatedly due to inconsistent firmware versions.

I/O expansion failure: first check frame number, LAN, and initialization

The I/O expansion of ACE3600 is based on 100Base-T full duplex Ethernet. A single extension frame can directly connect the Eth1 port of the extension module to the Eth1 port of the main CPU through a cross LAN line; For multi frame systems, an extended LAN switch needs to be installed in the main rack I/O slot. A single switch can connect up to 7 extended frames, and a dual switch can connect up to 13 extended frames, forming a configuration of approximately 110 I/O modules. The extended frame includes an extended power supply, an extended module, and an I/O module. The extended module is installed in the CPU slot of the extended frame and communicates with the main frame through a dedicated LAN.

The common issue of "extension frames not going online" on site can be investigated in the following order: first, check the rotation frame number switch on the extension module, ranging from 1 to 13, where A, B, C, and D represent 10, 11, 12, and 13, respectively; Changing the frame number during operation will not take immediate effect and requires restarting the extended frame. Secondly, check if shielded Cat 5E FTP cables are used for LAN cables. For single frame direct connections, crossover cables should be used, and for multi frame connections, available ports of the extended LAN switch should be connected; The Eth1/M port of the switch is reserved for the main CPU and cannot be connected to ordinary computers, routers, or other non expansion devices, otherwise it may cause communication delays and abnormal expansion systems. Thirdly, observe the status of the MCOM LED and STS hardware testing of the expansion module. The main CPU defaults to waiting for the initialization of extension frames for about 60 seconds. Extension frames that fail to complete the timeout will be ignored until the next main CPU restart. Fourth, check the firewall address list. If the main frame has enabled a firewall and defined an address range, it may block communication from extended frames to the main frame; Either manually add the extended frame IP, or keep the address list empty to allow communication.

After the expansion module is powered on, it will load the expansion firmware image from the main CPU, then load user files, register the actual I/O module, and establish EMI communication. If the communication interruption between the extended frame and the main CPU exceeds the configurable time (about 1 minute by default), the extended module will restart and reinitialize. Therefore, when observing periodic disconnection of expansion frames on site, do not only replace the expansion module, but also check the LAN line shielding grounding, switch ports, main CPU load, and expansion power supply voltage drop.