systemref

Cross-Vendor Fieldbus Bridging — Connecting Siemens Profinet to Allen-Bradley EtherNet/IP

H. Maqsood Jun 19, 2026 3 min read profinet ethernet-ip fieldbus siemens allen-bradley gateway
A hardware gateway presents itself as a native device on each network and maps a shared I/O memory block between them. Correct configuration requires matching byte order, I/O sizes, and scan cycle timing on both sides.

Profinet and EtherNet/IP run on standard Ethernet hardware but are incompatible at the application layer. Profinet uses GSDML device descriptions and DCP name resolution. EtherNet/IP uses EDS files and CIP implicit messaging. A hardware gateway translates between them — it appears as a legitimate Profinet device to the Siemens controller and as a valid EtherNet/IP adapter to the Allen-Bradley controller.

Common gateway hardware: HMS AnyBus X-Gateway, ProSoft PLX51, Moxa MGate EIP-3170.

Network map first

Document the full network map before touching any configuration. Both networks must be on separate subnets with no routing between them — the gateway is the only crossing point.

Siemens S7-1500          192.168.1.10
  └── Profinet subnet:   192.168.1.0/24
      └── Gateway (PN):  192.168.1.50

AB ControlLogix          192.168.2.10
  └── EtherNet/IP subnet:192.168.2.0/24
      └── Gateway (EIP): 192.168.2.50

The gateway has two independent network interfaces. Assign static IPs on both. Do not bridge the subnets — keep them isolated at Layer 3.

Profinet side: TIA Portal

  1. Download the GSDML file from the gateway manufacturer and import it into TIA Portal: Options → Manage general station description files
  2. Drag the gateway from the hardware catalog onto the Profinet network
  3. Assign the Profinet device name — must match the name flashed to the gateway's physical hardware
  4. Configure the I/O modules: set input and output byte counts (e.g., 64 bytes in, 64 bytes out). These define the shared memory block
  5. Compile and download

The device name is resolved via DCP (Discovery and Configuration Protocol), not DNS. If the gateway is not on the same L2 segment as the PLC during commissioning, DCP name assignment will fail — bring them to the same switch.

EtherNet/IP side: Studio 5000

  1. Register the EDS file: Tools → EDS Hardware Installation Tool
  2. Add the gateway as a new module on the EtherNet/IP backplane
  3. Set connection parameters:
  4. Download to the ControlLogix

The RPI (Requested Packet Interval) defines how often the ControlLogix polls the gateway. Setting it faster than the gateway's refresh rate produces no benefit and increases bus load.

I/O mapping table

Define this before configuration. Data at byte offset N on one side must match type and endianness on the other.

Byte offset Profinet tag EtherNet/IP tag Type Note
OUT 0–1 DB100.DBW0 Gw_OUT[0] UINT UINT16 Speed setpoint
OUT 2–3 DB100.DBW2 Gw_OUT[1] UINT UINT16 Torque limit
IN 0–1 DB101.DBW0 Gw_IN[0] UINT UINT16 Actual speed
IN 2 DB101.DBB2 Gw_IN[4] SINT BYTE Status word

Byte order: Profinet follows big-endian (Motorola) byte order. EtherNet/IP on Allen-Bradley follows little-endian (Intel) byte order. Most gateways offer a configurable byte-swap per word. Verify with a non-symmetric test value: write 0x0102 from the Siemens side and confirm what arrives on the Allen-Bradley side before mapping real data.

Commissioning verification

  1. Ping both gateway interfaces from their respective subnets
  2. Confirm Profinet device status is "OK" in TIA Portal diagnostics (not "Error" or "Deactivated")
  3. Confirm EtherNet/IP connection shows "Running" in Studio 5000 Controller Organizer
  4. Write a known constant to a Profinet output tag; verify the value appears correctly in the mapped EtherNet/IP input tag
  5. Repeat in the reverse direction

A connection in "Running" state with all-zero data is not a successful commissioning — it means the connection is established but data may still be mapped or byte-swapped incorrectly.

Related