Allen Bradley Quest AN-X2-AB-DHRIO Remote I/O Adapter Integration and Troubleshooting



Allen Bradley Quest AN-X2-AB-DHRIO Remote I/O Adapter Integration and Troubleshooting

How to smoothly integrate old RIO racks, discrete I/O, and block transfer data into the ControlLogix platform is a problem that many renovation projects cannot avoid on sites where existing Allen Bradley Remote I/O systems are still running in large quantities. The Quest AN-X2-AB-DHRIO remote I/O adapter is designed as an Ethernet gateway for such scenarios: it connects to the EtherNet/IP network of ControlLogix on one end and the Remote I/O network on the other end, and maps RIO data to the scheduling connection data area of ControlLogix through configuration software. For engineers, what truly determines the success or failure of a project is often not whether it can be connected, but whether the rack mode, terminal resistance, mapping relationship, connection type, and LED diagnosis are handled correctly.

Module positioning and two rack modes

AN-X2-AB-DHRIO, as a Remote I/O adapter, has one RIO channel and can simulate one or more racks. It supports three baud rates of 57.6, 115.2, and 230.4 kbaud, with rack numbers ranging from octal 00 to 76, and supports some rack combinations. It can monitor discrete I/O and block transfer read/write on the same RIO network, as well as update I/O data through ControlLogix scheduling connections. The module communicates with ControlLogix through Ethernet, and RIO data is mapped from the configuration program to scheduling input and output data.

Understanding the two modes of "Active" and "Monitored" is the first step in configuration. The Active rack is simulated by AN-X2-AB-DHRIO, and ControlLogix writes RIO input and block transfer read data to the adapter, and reads RIO output and block transfer write data from the adapter. Monitored rack is a real rack that exists on the network, and ControlLogix only reads its RIO input, output, and block transfer read/write data. All data is mapped to the input area of ControlLogix. If a rack number contains both Active and Monitored partial racks, monitoring data is mapped to CLX input, Active input is mapped to CLX output, and the mapping is effective for the entire rack number. Partial racks cannot be mapped separately.

Hardware, power supply, and microSD maintenance

The front panel of the module provides 10/100 Ethernet ports, 12-24 VDC power terminals, three pin Phoenix RIO network terminals, as well as 100, Link/ACT, SYS, NET and other LEDs. The power terminals from left to right represent the chassis ground, negative voltage, and positive voltage, and the chassis ground should be reliably connected. The power consumption of the module is about 200 mA@12 VDC or 100 mA@24  VDC， The maximum power consumption is about 2.4 W, the operating temperature is 0-50 ° C, and the humidity is 5% -95% non condensing. It is recommended to install ferrite magnetic rings on Ethernet and power cables for CE installation, and corresponding magnetic rings should also be installed on RIO/DH+cables.

The important difference between AN-X2 and the original AN-X is the use of microSD cards to store firmware and configuration data. The card format must be FAT-16 or FAT-32, with no limitations on capacity and speed, but the module must be inserted during operation, and it is strictly prohibited to unplug the card while it is still powered on. If the module cannot be accessed from Ethernet due to IP settings, you can remove the card after power failure, modify the IP, Netmask, DefGtwy, Hostname, and Firmware fields in the config. txt file using a text editor, and then plug them back in with the pins facing up. When inserting the card, it should be pushed straight to avoid the card falling into the shell. The module hardware also includes watchdog and Jabber inhibitor protection: firmware that is not "fed to the dog" on time will enter a safe and fatal fault; If the transmitter conducts for more than 150% of the maximum frame time, it will be forcibly shut down and enter a safe state.

RIO wiring, terminal resistance, and cable length

RIO terminals are defined as Line 1, Shield, and Line 2, with Line 1 being the closest to the power terminal. When wiring, it is necessary to ensure that Line 1 of AN-X2 corresponds to Line 1 of PLC, and the shielding layer should be treated according to the on-site specifications. The RIO network must have one and only one terminating resistor installed at each physical end. If the network is running at 230.4 kbps, or at 57.6/115.2 kbps and there are no devices such as 1771-AS, 1771-ASB A/B series, 1771-DCM, 1771-AF, 1771-AF1 in the network, use an 82 Ω resistor; If the network includes the aforementioned devices or does not require support for more than 16 physical devices at 57.6/115.2 kbps, use a 150 Ω resistor. The maximum number of physical devices in the network is 32. The cable length is limited by the baud rate: 57.6 kbaud is approximately 10000 feet, 115.2 kbaud is approximately 5000 feet, and 230.4 kbaud is approximately 2500 feet. When connecting Ethernet directly to a computer, use a crossover cable, and when passing through a switch or router, use a standard straight through cable.

Ethernet configuration and link local access

The module is shipped with a link local address of 169.254.42.84. When configuring for the first time, the computer must be on the same subnet as the module and cannot be accessed through the router at that address. After entering the address in the browser, enter the web interface and select Administration/AN-X Configuration to set DHCP or static IP. If DHCP is selected but there is no DHCP server in the network, the module will fall back to 169.254.42.84 and repeatedly flash the red SYS light three times. Most industrial sites recommend assigning static IP addresses to avoid reconfiguring the upper software due to changes in the power on address each time. Static IP must be filled with a valid gateway address, even if there is no actual device on the gateway address. The length of Hostname is 1 to 30 characters, and the firmware must be selected as AN-X2-AB-ADPT for use with remote I/O adapters. After submission, the configuration will be written to the microSD card's config. txt file, which will take effect after restarting.

If the computer cannot access 169.254.42.84, you can run route print at the command prompt to check if there is a 169.254.0.0/16 route; If not, use route add 169.254.0.0 mask 255.255.0.0 and connect the AN-X2 network card IP address to the computer, then ping test. When multiple AN-X2 are powered on simultaneously, the initial address should be the same, and they should be connected and configured one by one. The web interface can also view ControlLogix logs, system logs, archive configurations, firmware updates, and restart modules. The browser may cache old pages, and when data is not refreshed, cache free mode or clear cache can be used.

Configure software, rack and block transfer mapping

The configuration tool AnxAbRioCfgAdpt is used to set baud rates, automatically configure, manually add or delete racks, configure block transfer modules, map I/O, save/download configurations, archive templates, and monitor diagnostics. The baud rate can be selected from 57k, 115k, 230k, or Auto. When adding a rack, you need to select the octal rack number, start/end I/O group, and Active or Monitor mode. Automatic configuration will first detect the baud rate, then listen to network packets to construct the configuration, and update and add universal BT-MODULE based on observed block transmission; It cannot recognize the specific block transmission module type, so manual confirmation of the template is required.

Before mapping, the data direction must be clearly defined: the RIO input of the Active rack is mapped to the CLX output, and the RIO output is mapped to the CLX input; The RIO input and output of the Monitored rack are mapped to the CLX input. Similarly, for block transfer, the BTR data from the Active rack is mapped to the CLX output, and the BTW data is mapped to the CLX input; The BTR and BTW of the Monitored rack are mapped to the CLX input. Mapping is based on the entire rack number and cannot map individual racks. After changing the mapping, the ControlLogix output table should be cleared to prevent accidental writing to the wrong location. The configuration tool supports automatic mapping of unassigned items, manual specification of CLX blocks and offsets, clearing mappings, and exporting RSLogix 5000 aliases. Before exporting aliases, make sure the AN-X2 checkbox is selected; If the RIO or CLX configuration changes, the alias should be re imported. Ghost Mode can be used for upgrading old systems: first monitor the old system data and timing in adapter mode, create a new ControlLogix program to compare and run, confirm that there are no errors, then switch to scanner mode, and use the exported scanner configuration to take over the RIO network.

RSLogix 5000 connection and listen only

In RSLogix 5000, first add the 1756-ENBT/A module with Major Rev set to 1, Slot set to 16, Chassis Size set to 17, Rack Connection set to None, IP address consistent with AN-X2, and Electronic Keying set to Disable Keying. Then add a 1756-MODULE universal module for each required connection, select Data-INT for Comm Format, use Slot 0 for data connection, use Slot 15 for diagnostic connection, and set Assembly Instance and Size according to the configuration. RPI can be selected between 1 and 750 ms, and should be set based on RIO scanning time and application requirements; The diagnostic connection does not require high-frequency updates and can be set to around 500 ms.

AN-X2 supports listen only connections, but listen only must rely on an exclusive owner connection, which must be multicast and not unicast. An AN-X2 can support multiple listen only connections, while the original AN-X only supported one input only connection. If using listen only, when adding a generic module, select Input Data INT for Comm Format, and connect RPI to the exclusive owner consistently. The diagnostic counter is mapped to Slot 15 and cannot be mapped to a single counter separately; Its content includes good frames, timeouts, CRC errors, noise errors, abort errors, send frames, protocol errors, rack status tables, current/average/minimum/maximum RIO scan times, scheduled I/O transmit/receive counts, and Ethernet errors. The Active rack will keep the input at 0 until the corresponding connection is established, so during debugging, it should be confirmed that all scheduling connections have been established first.

LED diagnosis and common faults

The green SYS light indicates normal operation; Red 3 indicates DHCP configuration failure; Red 4/5/6 are internal errors, please contact technical support; Yellow 2 indicates that the microSD card is not inserted; Yellow 3 indicates a lack of maintenance firmware on the card; Yellow 4 indicates that the config. txt file is missing or has parsing errors; Yellow 5 indicates that the production firmware file name has not been specified; Yellow 6 indicates a lack of production firmware on the card; Yellow 7 indicates invalid firmware or burning error; Yellow 8 indicates that the daughter board does not match; A single red flash indicates that AN-X has returned an error request to ControlLogix, and the scheduling I/O configuration should be checked; Flash green/off indicates that not all scheduled connections are open; Flashing red/off indicates an error in the configuration file. During startup, SYS and NET will flash alternately as' railloading ': yellow indicates that firmware is being copied from microSD to Flash, and green indicates production mode startup. Fatal errors will be displayed as an 8-bit flashing code, with green indicating 1 and red indicating 0. After recording, contact support.

NET light green indicates receiving good frames; Red indicates that bad frames have been received within the last 250 ms; Flashing indicates that one or more parts of the rack have not been updated; A constant yellow light indicates that no rack has been configured. If the RxBadCRC and RxNoise in the global diagnostic counter increase, the RIO cable and terminal resistance should be checked; RxTout growth indicates no response after sending, including checkpoint number, baud rate, and wiring; PrtclErr indicates protocol message abnormality, check mapping and rack configuration. If the ControlLogix connection is abnormal, you can check the ControlLogix logs on the web interface to locate the cause. Use the web interface Administration/Update AN-X Firmware for firmware updates, select AN-X2-AB-ADPT.qff; During the download and restart period, it is strictly prohibited to turn off the power, and do not download while the application is running, otherwise it may cause the module to fail to start and require factory initialization.

Maintenance and replacement suggestions

For spare parts replacement, the IP, Hostname, firmware version of the original module should be recorded first config.txt、 Rack configuration and mapping files, and backup microSD card contents. AN-X2 requires firmware version 4 or above, and the configuration tool also needs to be 4. x.x or above. After replacement, first confirm that the SYS light is normal and the NET light can receive good frames, and then check all scheduling connections and diagnostic counters in RSLogix 5000. If upgrading from the original AN-X to AN-X2, attention should be paid to the differences in diagnostic labels, listen only connections, and unicast/multicast support, re import aliases, and review mappings. Only by verifying RIO terminals, Ethernet addresses, rack modes, block transfer templates, and CLX connections as a whole can AN-X2-AB-DHRIO stably serve as a bridge between Ethernet and Remote I/O in the renovation of old systems.