Category: Industry Trends

Specifications

DH+ to EtherNet/IP™

1/ The operating mode acts as a bridge between an EtherNet/IP and a DH+ network.

Programming terminals, and/or processors on an EtherNet/IP network can access legacy processors on a DH+ network

Download to a PLC5 or SLC through RSLinx

Configured through web browser

Supports all DH+ baud rates (57.6. 115.2. and 230.4 K baud).

2/ The operating mode helps the communication between an Ethernet-Based processor with legacy processors on a DH+ network.

Support gathering data without changing existing PLC or SLC hardware

DH+ to Modbus TCP

This operating mode allows Modbus TCP Clients to access the PLC data from stations on a Data Highway Plus Network.

The Modbus TCP server supports up to 128 connections

Modbus Input and Output Registers are mapped to the PLC/SLC files for each station

Modbus TCP Unit/Slave ID data is mapped to the Data Highway Plus Station

The AN-X4-AB-DHRIO Gateway is designed to help customers initiate a phased migration

approach to replacing or upgrading legacy PLC’s, HMI’s, Drives, or Flex I/O adapters.

These solutions can be achieved by selecting the corresponding operating mode during the initial configuration.

The AN-X4-AB-DHRIO has a built-in webserver to view diagnostics, current configuration,

upload configuration files, and set the operating mode. It is also DIN Rail Mountable.

Specifications

DH+ to EtherNet/IP™

1/ The operating mode acts as a bridge between an EtherNet/IP and a DH+ network.

Programming terminals, and/or processors on an EtherNet/IP network can access legacy processors on a DH+ network

Download to a PLC5 or SLC through RSLinx

Configured through web browser

Supports all DH+ baud rates (57.6. 115.2. and 230.4 K baud).

2/ The operating mode helps the communication between an Ethernet-Based processor with legacy processors on a DH+ network.

Support gathering data without changing existing PLC or SLC hardware

Cabling and Termination

Follow Allen-Bradley cabling recommendations for remote I/O. Refer to Approved

Vendor List for DH, DH+, DH-485. and Remote I/O Cables, publication ICCG-2.2.

February 1996.

On the AN-X module, the connections should be line 1. shield, line 2.

Ethernet Configuration

The AN-X2-ABRIO-EIPSCN module connects a controller on remote I/O such as a

PLC-5 to scan I/O modules on Ethernet.

Before you can use the AN-X2-ABRIO-EIPSCN, you must configure its network

properties on Ethernet.

AN-X modules are shipped with the link-local address 169.254.42.84.

Unless you have control of the DHCP server, in most applications you will assign the

AN-X a static IP address. Otherwise the DHCP server may assign a different IP address

each time AN-X powers up, and any software that accesses the AN-X module would have

to be reconfigured.

If you are using multiple AN-X modules, connect and configure one at a time, since

initially they will all be set to the same link-local IP address.

Power

AN-X requires a DC power input of anywhere from 12 to 24 VDC.

Left to right the pins on the power connector are chassis ground, negative voltage and

positive voltage.

The chassis ground should be connected.

Power consumption is 200 mA @ 12VDC or 100mA @ 24VDC.

The part number for the power connector is Phoenix MSTB 2.5/3-ST-5.08

Contact us if you need a suitable wall adapter.

AN-X2 Modes of Operation

There are two AN-X2 modes of operation:

• Maintenance mode. The AN-X2 runs the maintenance firmware at startup. It

performs diagnostics (memory tests, etc), copies any changes from the microSD card.

If there are no errors, it starts the AN-X2 in production mode.

• Production mode. This is the normal runtime mode of operation.

Prevent Electrostatic Discharge

The module is sensitive to electrostatic discharge.

Package Contents

• AN-X2-ABRIO module

• microSD to SD card adapter

• CD containing software and documentation

• rubber feet for desktop use

Using the MicroSD Card

The AN-X2 microSD card stores configuration data and firmware.

The are no restrictions on the size or speed of the card. The format must be FAT-16 or

FAT-32.

An adapter is provided so you can insert the microSD card in an SD slot in your

computer.

The card must be present while the AN-X2 is running.

WARNING!

Do not remove the card while the AN-X2 is powered on!

If the AN-X2 is inaccessible from Ethernet because of its settings, you can remove the

card and edit the file config.txt. Refer to page 12 for details.

Reinsert the card in the slot at the back of the AN-X2. with the pins facing up.

WARNING!

If you remove the card to edit the configuration file, push the card in

straight or the card might fall inside the case and you will have to

disassemble the AN-X2 to retrieve it .

Hardware Features

The module has:

• two LEDs to indicate the status of the connection to the Ethernet (100 and Link/Act)

• an LED to indicate the module’s internal state and the state of Ethernet

communication (MS or SYS)

• an LED to indicate the state of communications on the Remote I/O network (NS or NET)

• an Ethernet connector

• a power connector

• a 3-pin Phoenix connector to connect to the remote I/O network

A watchdog timer is implemented in the module’s hardware. If the firmware does not

kick the watchdog within the timeout period the watchdog times out and places the

module into a safe fatal failure state.

A jabber inhibit timer is implemented in the module’s hardware. If the network

transmitter is on longer than 150% of the longest network frame time, the transmitter is

forced off and the module is placed into a safe fatal failure state.

On remote I/O the AN-X module supports:

• Baud rates 57.6. 115.2. and 230.4 Kbaud

• Rack numbers 0 to 76 octal

• Block transfers at all allowable locations

On Ethernet, the AN-X supports up to 16 Ethernet/IP connections. Each Ethernet adapter

and the associated discrete I/O requires one connection. Each analog module requires one

connection. In some cases, a discrete module will require a separate connection, for

example, if desired functionality is available only if the module has its own connection.

The AN-X2-ABRIO-EIPSCN module has a web interface for configuring the module, for

monitoring logs and for performing administrative functions. You can communicate with

the module using any standard web browser such as Internet Explorer.

The module firmware can be selected and updated using the web interface. 

Refer to page 41 for details.

The AN-X emulates a ControlLogix scanning I/O over Ethernet.

All configuration data comes from the AN-X, not from remote I/O. Configuration

options correspond to what’s available in a ControlLogix, not to what is available in

remote I/O. No configuration data gets passed from remote I/O to Ethernet. If your

program dynamically changes configuration data, or if it contains logic to configure a

module, the program will have to be modified to remove or disable that logic.

You may need to make some changes to the control application related to addresses, logic

and timing.

Some behaviour that is set by switches on the remote I/O adapter is set in parameters for

Ethernet modules. For example, hold last state is set on a module-by-module basis when

you scan over Ethernet.

In addition, you may need to make changes because Ethernet does not support

complementary I/O, or standard 32 or complementary 32 addressing.

For example, 32 bit discrete Flex I/O modules require a separate Ethernet connection.

You must communicate with them from remote I/O using block transfers, not as discrete data.

AN-X2-ABRIO-EIPSCN Module Overview

The AN-X2-ABRIO-EIPSCN communications module connects a scanner such as a

PLC-5 on an Allen-Bradley remote I/O network to I/O modules on Ethernet/IP.

As parts become obsolete and remote I/O adapters become unavailable, the

AN-X2-ABRIO-EIPSCN is a solution that lets you retain the original controller, I/O

modules and field wiring and replace remote I/O adapters with Ethernet adapters. The

existing remote I/O scanner talks to the AN-X, which maps discrete and analog I/O on

remote I/O to Ethernet data.

In addition, you may need to make changes because Ethernet does not support

complementary I/O, or standard 32 or complementary 32 addressing.

For example, 32 bit discrete Flex I/O modules require a separate Ethernet connection.

You must communicate with them from remote I/O using block transfers, not as discrete data.