Allen-Bradley Ethernet

Connecting to Allen-Bradley Devices

Ignition provides several drivers for Allen-Bradley devices. These drivers connect through the Gateway to devices that support Ethernet communication or devices with Ethernet modules like ENBT or EN2T. The following device drivers are available in the Allen-Bradley Ethernet module:

• CompactLogix (Legacy): Supports legacy firmware versions v20.18 and prior.
• ControlLogix (Legacy): Supports legacy firmware versions v20.18 and prior.
• Logix: Supports ControlLogix and CompactLogix devices with firmware v20.19 and later.
• Micro800: Supports Micro800 models including 820, 850, and 870.
• MicroLogix: Supports MicroLogix models including 1100 and 1400 series.
• PLC5: Supports direct communication with Allen-Bradley PLC5 controllers.
• SLC: Supports the 5/05 series using Ethernet.

note

These drivers only support firmware versions 16 and above. Earlier versions may work, but are not officially supported. For unsupported versions, consider using a third party OPC server.

caution

Direct connections to RSLinx Emulate 5000 are not supported and may result in communication issues.

Verifying Device Connectivity

Device connections can be verified from the Gateway Webpage under Connections > Devices > Connections. Check the Status column to confirm that the device shows Connected.

Allen-Bradley Connection Paths

All Allen-Bradley drivers include a Connection Path setting. This setting is required when you're connecting to a processor through a bridge device or an external Ethernet module, such as an ENBT or EN2T. For example, if you're communicating with a ControlLogix or CompactLogix processor via a ControlLogix Gateway, you'll need to define a connection path.

The connection path tells the driver how to navigate through backplanes, modules, and network links to reach the destination processor. Because hardware configurations vary widely, the path is unique to your setup. However, most connection paths follow a consistent pattern. For detailed examples and templates, refer to the individual driver documentation.

How to Build a Connection Path

Building a connection path involves identifying each segment between Ignition and the processor, then expressing those steps in the expected format. The path is always defined in pairs: an action (such as exiting a port) followed by a destination (such as an IP address or slot).

1. Begin the path with a 1, which tells the driver to move from the current module (such as an Ethernet card) into the chassis backplane, where it can access other modules by slot.

2. Enter the slot number of the module you want to route through.

3. Specify the exit port or channel on that module.

4. Provide the address of the next module in the path—this could be an IP address, ControlNet address, or DH+ station number, depending on the network type.

Repeat this pattern as needed until you reach the processor.

note

Since each step consists of two entries, all valid connection paths must contain an even number of values. If your path ends in an odd number, a step is likely missing.

Module Entry and Exit Codes

Each movement in the path consists of two entries: one for exiting a module and one for entering the next. This means all valid paths contain an even number of entries. If your path ends with an odd number of entries, a step is missing.

By following the path through your networked modules, you can configure communication from Ignition to any accessible Allen-Bradley processor.

Use the following codes based on the module type:

ENET, ENBT, and EN2T:
Exiting:
    1 = Backplane
    2 = Ethernet Port
Entering:
    IP Address

CNB:
Exiting:
    1 = Backplane
    2 = ControlNet Port
Entering:
    ControlNet Address

DHRIO:
Exiting:
    1 = Backplane
    2 = DH+ Channel A
    3 = DH+ Channel B
Entering:
    DH+ Station Number (octal 0–77)