Skip to main content

Allen Bradley Connectivity Guide

Adapter script required — EtherNet/IP will not work without tag mapping

Adding an Allen Bradley (EtherNet/IP) machine in MachineMetrics is only the setup step. You must implement a Transform Adapter Script that maps PLC tags and memory to MachineMetrics data items. Without that mapping, the adapter cannot interpret your tags — the machine may show as added but will not report usable production data, which leads many customers to assume the connection is “broken.”

Tag / address mapping via an adapter script is mandatory before you will see data. See Configuration on this page for setup steps and patterns. Contact MachineMetrics Support if you need more help.

Overview​

What is Allen Bradley EtherNet/IP?​

MachineMetrics connects to Allen Bradley PLCs using the EtherNet/IP (Ethernet Industrial Protocol), a network protocol for industrial automation applications.

Key Characteristics:

  • Based on Common Industrial Protocol (CIP)
  • Uses standard Ethernet (TCP/IP)
  • Default port: 44818
  • Tag-based addressing
  • Real-time data exchange

Important: MachineMetrics' Allen Bradley adapter uses EtherNet/IP and only works with specific Allen Bradley controls: CompactLogix, ControlLogix, and GuardLogix. It does not support MicroLogix or SLC500 PLCs (which have their own dedicated adapters).

Compatible Allen Bradley Controls​

Supported Controls​

CompactLogix:

  • All CompactLogix models (1769, 5069 series)
  • Processor integrated into head (implicit slot 0)
  • No slot parameter needed in configuration
  • Examples: 1769-L30ER, 1769-L33ER, 5069-L310ER

ControlLogix:

  • All ControlLogix models (1756 series)
  • Must specify backplane slot where processor is installed
  • Use slot: parameter in configuration
  • Examples: 1756-L71, 1756-L73, 1756-L85E

GuardLogix:

  • All GuardLogix safety controllers (1756 series)
  • Must specify backplane slot where processor is installed
  • Use slot: parameter in configuration
  • Examples: 1756-L71S, 1756-L73S, 1756-L75

Not Supported with This Adapter​

Allen Bradley MicroLogix:

  • ❌ Not supported with the Allen Bradley (EtherNet/IP) adapter
  • MicroLogix PLCs are not compatible with this connector
  • Alternative: Use Modbus/TCP if available on your MicroLogix model

Allen Bradley SLC500:

  • ❌ Not supported with the Allen Bradley (EtherNet/IP) adapter
  • SLC500 PLCs have their own dedicated Allen Bradley SLC500 adapter
  • See the SLC500 connectivity guide for connecting these PLCs

Other Manufacturers:

  • ❌ Not supported - This adapter is designed exclusively for Allen Bradley CompactLogix, ControlLogix, and GuardLogix controls
  • Other manufacturers' EtherNet/IP implementations (Siemens, Omron, etc.) are not compatible

Prerequisites​

  • Allen Bradley CompactLogix, ControlLogix, or GuardLogix PLC
  • IP address of controller
  • List of tags to monitor (from PLC program or documentation)
  • Backplane slot number (for ControlLogix/GuardLogix)
  • Network access (TCP port 44818)
  • EtherNet/IP scanner tool (for testing, optional)

Physical Connection​

Step 1: Connect Ethernet

  • Plug Ethernet cable into controller's Ethernet port
  • Connect to network switch
  • Ensure Edge device is on same network

Step 2: Verify Network

  • Ping controller IP from Edge or computer
  • Verify port 44818 is not blocked by firewall

Step 3: Test with EtherNet/IP Scanner (Optional)

  • Use Rockwell Automation's RSLinx or similar tool
  • Attempt to browse tags
  • Verify communication before configuring MachineMetrics

Tag Structure​

Tag Path Format​

Allen Bradley PLCs expose data as "tags" with hierarchical paths.

Globally Scoped Tags:

AssemblyIndex
Module10.ModeAuto
Module10.PositionAxis[2]

Locally Scoped Tags (within program):

Program:Station1.FaultNumber
Program:Station1.Values.Reals[0]

Data Types:

  • Booleans, integers, floats, strings
  • Simple types and complex structures
  • Arrays and nested objects

Configuration​

Tip: Use Max — MachineMetrics’ AI assistant — to help generate or refine an EtherNet/IP adapter script for your PLC tags. The examples below are starting points.

Basic Configuration (CompactLogix)​

version: 2
scan-interval: 0.25    # Poll every 250ms (adjust as needed)

tags:
  mode-auto: Module10.ModeAuto
  fault-ind: Module10.FaultInd
  part-count: HMI1.PartCounter

variables:
  execution:
    - source: mode-auto and fault-ind == false
    - state:
        - ACTIVE: this
        - READY: true
  
  parts:
    - source: part-count
    - value-increase
    - count

data-items:
  - execution
  - parts

ControlLogix/GuardLogix with Slot Parameter​

For ControlLogix and GuardLogix, specify the processor slot:

version: 2
slot: 3                # Backplane slot where processor is installed
scan-interval: 0.25

tags:
  mode-auto: Module10.ModeAuto
  fault-ind: Module10.FaultInd
  part-count: HMI1.PartCounter

variables:
  execution:
    - source: mode-auto and fault-ind == false
    - state:
        - ACTIVE: this
        - READY: true
  
  parts:
    - source: part-count
    - value-increase
    - count

data-items:
  - execution
  - parts

Note: CompactLogix is always slot 0 (don't need to specify slot parameter).

Advanced Configuration​

version: 2
scan-interval: 0.25

tags:
  recipe-loaded: RecipeLoaded
  mode-auto: Module10.ModeAuto
  fault-ind: Module10.FaultInd
  peak-force: Program:Station1.Values.Reals[0]
  press-force: Program:Station1.Values.Reals[2]
  fault-code: HMI1.StaData.FaultNumber
  fault-msg: HMI1.StaData.FaultDescription

variables:
  execution:
    - state:
        - ACTIVE: mode-auto and fault-ind == 0 and recipe-loaded
        - READY: true
        
  controller-mode:
    - state:
        - AUTOMATIC: mode-auto
        - MANUAL: true

data-items:
  - recipe-loaded
  - controller-mode
  - execution
  - press-force

conditions:
  system:
    - code: gen_fault
      message: Machine is in fault
      value:
        FAULT: fault-ind > 0
    - code: ${fault-code}
      message: ${fault-msg}
      value:
        FAULT: fault-ind > 0

Adding Machine in MachineMetrics​

  1. Go to Assets → Machines → Add Machine
  2. Enter machine details
  3. Select Allen Bradley (or EtherNet/IP) as adapter type
  4. Enter controller IP and port <ip-address>:44818
  5. Enter adapter script configuration
  6. For ControlLogix/GuardLogix: Verify slot: parameter is correct
  7. Test connection and save

Troubleshooting​

Common Errors​

Error Code 0x04 - Path Segment Error:

  • Invalid tag path specified
  • Check tag names in PLC program
  • Verify tag paths match exactly (case-sensitive)
  • Ensure tag exists in controller

Error Code 0x08 - Service Not Supported:

  • ControlLogix/GuardLogix: Connected to wrong slot
  • Verify processor slot number in backplane
  • Check backplane configuration in adapter script

Connection Timeouts:

  • Scan interval too high for controller
  • CompactLogix has short timeout (~128ms)
  • Try reducing scan-interval to 0.1
  • Note: Lower scan interval may increase PLC load (test carefully)

No Data Appearing:

  • Verify tags exist in PLC program
  • Check tag paths are correct (case-sensitive)
  • Review Edge logs for errors
  • Test with simpler configuration first
  • Use RSLinx or similar tool to verify tags are accessible

Wrong Controller Type:

  • Verify you're using the correct adapter
  • MicroLogix: NOT supported with this adapter (use Modbus if available)
  • SLC500: Use the dedicated Allen Bradley SLC500 adapter instead

Additional Resources​

Questions? Contact MachineMetrics Support

Allen Bradley PLC Communication Capabilities​

Compatibility Chart​

The following table shows which Allen Bradley PLC models support EtherNet/IP (used by MachineMetrics) and their communication capabilities.

PlatformModel NumberSeriesBuilt-in EthernetEtherNet/IP SupportModbus TCP SupportNotes
CompactLogix 53805069-L306ERL3✓ (Dual 1Gbps)✓✓ (via ladder logic)Latest generation, dual-IP or DLR mode
5069-L306ERML3✓ (Dual 1Gbps)✓✓ (via ladder logic)With motion support
5069-L310ERL3✓ (Dual 1Gbps)✓✓ (via ladder logic)
5069-L310ER-NSEL3✓ (Dual 1Gbps)✓✓ (via ladder logic)No stored energy
5069-L310ERML3✓ (Dual 1Gbps)✓✓ (via ladder logic)
5069-L320ERL3✓ (Dual 1Gbps)✓✓ (via ladder logic)2MB, 40 nodes
5069-L320ERML3✓ (Dual 1Gbps)✓✓ (via ladder logic)
5069-L330ERL3✓ (Dual 1Gbps)✓✓ (via ladder logic)
5069-L330ERML3✓ (Dual 1Gbps)✓✓ (via ladder logic)
5069-L340ERL3✓ (Dual 1Gbps)✓✓ (via ladder logic)4MB, 90 nodes
5069-L340ERML3✓ (Dual 1Gbps)✓✓ (via ladder logic)
5069-L350ERML3✓ (Dual 1Gbps)✓✓ (via ladder logic)
5069-L380ERML3✓ (Dual 1Gbps)✓✓ (via ladder logic)
5069-L3100ERML3✓ (Dual 1Gbps)✓✓ (via ladder logic)
CompactLogix 53701769-L16ER-BB1BL1✓ (Dual 100Mbps)✓✓ (via ladder logic)No serial port
1769-L18ER-BB1BL1✓ (Dual 100Mbps)✓✓ (via ladder logic)No serial port
1769-L18ERM-BB1BL1✓ (Dual 100Mbps)✓✓ (via ladder logic)With motion, no serial
1769-L24ER-QB1BL2✓ (Dual 100Mbps)✓✓ (via ladder logic)Has RS-232 port
1769-L24ER-QBFC1BL2✓ (Dual 100Mbps)✓✓ (via ladder logic)
1769-L27ERM-QBFC1BL2✓ (Dual 100Mbps)✓✓ (via ladder logic)With motion
1769-L30ERL3✓ (Dual 100Mbps)✓✓ (via ladder logic)
1769-L30ERML3✓ (Dual 100Mbps)✓✓ (via ladder logic)With motion
1769-L33ERL3✓ (Dual 100Mbps)✓✓ (via ladder logic)
1769-L33ERML3✓ (Dual 100Mbps)✓✓ (via ladder logic)With motion
1769-L36ERML3✓ (Dual 100Mbps)✓✓ (via ladder logic)With motion
CompactLogix (older)1769-L31-✗✗✗Requires comm module for Ethernet
1769-L32C-✗✗✗Requires comm module for Ethernet
1769-L32E-✓ (Single 100Mbps)✓✓ (via ladder logic)Single Ethernet port
1769-L35CR-✗✗✗Requires comm module for Ethernet
1769-L35E-✓ (Single 100Mbps)✓✓ (via ladder logic)Single Ethernet port
1769-L20/L30-✗✗✗Requires 1769 comm modules
ControlLogix 55801756-L81E-✓ (Single 1Gbps)✓✓ (via ladder logic)3MB, 100 nodes
1756-L82E-✓ (Single 1Gbps)✓✓ (via ladder logic)5MB, 175 nodes
1756-L83E-✓ (Single 1Gbps)✓✓ (via ladder logic)10MB, 250 nodes
1756-L84E-✓ (Single 1Gbps)✓✓ (via ladder logic)20MB, 250 nodes
1756-L85E-✓ (Single 1Gbps)✓✓ (via ladder logic)40MB, 300 nodes
ControlLogix 55701756-L71-✗Via 1756-EN2x/ENBT✓ (via ladder logic)Requires Ethernet module
1756-L72-✗Via 1756-EN2x/ENBT✓ (via ladder logic)Requires Ethernet module
1756-L73-✗Via 1756-EN2x/ENBT✓ (via ladder logic)Requires Ethernet module
1756-L74-✗Via 1756-EN2x/ENBT✓ (via ladder logic)Requires Ethernet module
1756-L75-✗Via 1756-EN2x/ENBT✓ (via ladder logic)Requires Ethernet module
ControlLogix 55601756-L61-✗Via 1756-EN2x/ENBT✓ (via ladder logic)Requires Ethernet module
1756-L62-✗Via 1756-EN2x/ENBT✓ (via ladder logic)Requires Ethernet module
1756-L63-✗Via 1756-EN2x/ENBT✓ (via ladder logic)Requires Ethernet module
1756-L64-✗Via 1756-EN2x/ENBT✓ (via ladder logic)Requires Ethernet module
1756-L65-✗Via 1756-EN2x/ENBT✓ (via ladder logic)Requires Ethernet module

Common Ethernet Modules for ControlLogix 5570/5560​

  • 1756-ENBT - Single port, 128 EtherNet/IP connections, 64 TCP
  • 1756-EN2T - Single port, 256 EtherNet/IP connections, 128 TCP
  • 1756-EN2TR - Dual port, 256 EtherNet/IP connections, 128 TCP
  • 1756-EN3TR - Latest generation dual port

Key Notes​

  1. Modbus TCP support on all Ethernet-equipped controllers requires ladder logic implementation (not native protocol)
  2. All ControlLogix 5580 (1756-L8xE) have built-in Ethernet ports
  3. ControlLogix 5570/5560 (1756-L6x, L7x) require Ethernet communication modules
  4. CompactLogix 5380 has the fastest Ethernet (1 Gbps dual port)
  5. Letters in model numbers: E = Ethernet, R = Safety-rated, M = Motion, XT = Extreme temperature
  6. This table covers the main production models - there are also safety variants (GuardLogix) with similar communication capabilities