MergenHub Envest Live demo
Home/Protocols/Allen-Bradley Logix
Protocol · Allen-Bradley Logix

Allen-Bradley Logix — EtherNet/IP by tag name

Connect to Rockwell Logix controllers with the tag names in the PLC, without writing an address table. Structures, arrays and program tags are read and written; the tag list comes from the device.

← All protocols & modules
MergenHub — Allen-Bradley LogixConnected
Project
▾Connectivity
▾Logix
▪Line1_PLC
Line1_PLC · 192.168.1.20,1,0
DriverAllen-Bradley ControlLogix Ethernet
ControllerCompactLogix 5380
PathBackplane, slot 0
ConnectionForward Open
Tag sourceDiscovered from device
TagAddressValueQuality
Line_SpeedLine_Speed42.5Good
Motor1_RunMotor[1].Running1Good
Part_CountProgram:Main.PartCount18240Good
Alarm_BitAlarmWord.30Good
RecipeRecipeNameBOX-200Good

The MergenHub interface — tag-name access on a CompactLogix controller: structure member, program tag, DINT bit and STRING.

Logix and EtherNet/IP

ControlLogix, CompactLogix and GuardLogix controllers keep their data in named tags and offer symbolic access through the CIP protocol over EtherNet/IP. MergenHub reaches those tags directly by name.

Where is it used?

Machine and line control in automotive, food, pharma, packaging and water treatment plants. Sites with Rockwell and other PLC brands side by side are brought under one SCADA.

Step by step

First live data in four steps

Connects to ControlLogix, CompactLogix, GuardLogix and Micro800 by tag name over EtherNet/IP (CIP); no extra software such as RSLinx is needed.

  1. 01

    Add a channel

    Choose the Allen-Bradley ControlLogix Ethernet driver with Add Channel. The same driver also serves CompactLogix, GuardLogix and Micro800.

  2. 02

    Add a device

    Add Device and pick the Model; the ID is the IP, backplane and CPU slot: 192.168.1.10,1,0. On CompactLogix the slot is usually 0; on Micro800 enter the IP only.

  3. 03

    Browse or add tags

    Generate Tags from Device lists the controller-scoped tags. By hand: Program:MainProgram.Counter, UDT member Motor.Speed, array Tank[3], DINT bit Status.5. A whole UDT is not read as one tag.

  4. 04

    Watch live, read over OPC UA

    Tick Live data in the toolbar; every tag shows its value, quality (Good / Bad / Uncertain) and timestamp. OPC UA clients read the same tags at opc.tcp://host:48010/MergenHub under Channel › Device › Tag.

Driver capabilities

Feature coverage

The CIP layer is shared with the OMRON NJ/NX driver; the connection type is chosen automatically from what the device supports.

Access

By tag name

Controller-scoped and program-scoped tags (Program:Main.Tag), structure members, array elements and DINT bits.

Data types

Atomic types and STRING

BOOL, SINT, INT, DINT, LINT, REAL, LREAL and STRING (82 characters) are read and written.

Path

Slot and hops

Device ID IP,1,slot; multiple hops and IP hops are supported. Micro800 uses the IP only.

Connection

Automatic fallback

Large Forward Open → small → unconnected messaging (Unconnected Send), falling back to what the device supports.

Discovery

Tag list from the device

Controller-scoped atomic tags are listed from the device; the selected ones are added to the project in one step.

Family

Logix + Micro800

ControlLogix, CompactLogix, GuardLogix and Micro800.

Supported controllers and types
ControlLogixCompactLogixGuardLogixMicro800EtherNet/IP CIPProgram:… tagUDT memberArray elementDINT.bitSTRINGREAL / LREAL
Control safety

Writes are verified from the device response

GuaranteeEvery write is checked against the status code of the CIP response; if the controller rejects it, the write is treated as failed and shown that way on screen.