5069-AENTR Compact 5000 EtherNet/IP Adapter 5069AENTRNew In Box
PRODUCT DETAILS
5069-AENTR — Compact 5000 Dual-Port EtherNet/IP Adapter Module
The 5069-AENTR is a dual-port EtherNet/IP adapter for the Compact 5000 I/O platform, connecting a remote bank of 5069-series I/O modules to the network and presenting them to the controller as a remote I/O node. Two onboard Ethernet ports support Device Level Ring (DLR) topology, letting the node act as a ring participant without requiring an external switch at its physical location — useful for distributed Compact 5000 nodes spread across a machine or production line.
Specifications
| Parameter | Value |
|---|---|
| Part Number | 5069-AENTR |
| Platform | Compact 5000 (5069) |
| Network Protocol | EtherNet/IP (CIP) |
| Ethernet Ports | 2 × RJ-45, 10/100 Mbps |
| Topology Support | Linear, Star, Device Level Ring (DLR) |
| I/O Messaging | Class 1 cyclic, Class 3 / UCMM explicit |
| IP Address Assignment | BOOTP, DHCP, or static |
| Local I/O Bus | 5069 DIN-rail expansion bus |
| Operating Temperature | 0°C to 60°C |
| Standards | EtherNet/IP conformance tested, UL 508, CE |
Why the Second Port Matters
A single-port adapter requires a switch at every node location if the system needs ring redundancy or simple daisy-chaining without extra switch hardware. The 5069-AENTR's two ports let the node sit directly in a DLR ring — cable in one port, cable out the other, continuing to the next device in the chain. If a cable segment between two nodes fails, the ring supervisor reroutes traffic through the opposite direction automatically, keeping the rest of the nodes online while the fault is located and repaired.
For machines with several distributed Compact 5000 I/O nodes — along a conveyor line, across a multi-station assembly cell — this collapses what would otherwise be individual home-run cables to a central switch into one continuous cable path, cutting both cable length and the number of switch ports needed.
Node Setup and Network Configuration
- Set a static IP address before connecting to the production network — default BOOTP assignment can shift after a power cycle on networks without a permanent BOOTP server mapping.
- Add the adapter to the controller's I/O tree in the engineering software, then add each physically installed 5069 I/O module in the correct slot order — a mismatch between configured and physical module types causes a fault on that slot.
- For DLR participation, a ring supervisor (the controller's own EtherNet/IP module, if capable, or a managed switch at the ring head) must be configured separately — the adapter itself participates as a ring node but doesn't manage the ring.
- Document the node's IP address and physical location together — distributed I/O nodes without clear documentation are harder to troubleshoot when a network issue arises on an unfamiliar machine.
FAQ
Q: Can both ports be connected to different network segments simultaneously?
No. Both ports share one IP address and function as a two-port switch within the module — they're on the same network segment, not bridging two separate ones.
Q: Is this adapter required for every 5069 I/O bank, or only for remote installations?
An adapter is required at the head of any 5069 I/O bank that connects over EtherNet/IP, whether local to the controller or in a remote location. A bank physically attached to a 5069-series controller directly may not need a separate adapter, depending on the controller's own connectivity.
Q: How many 5069 I/O modules can one 5069-AENTR node support?
The supported module count per node depends on backplane current budget and the platform's per-node limits — verify against the Compact 5000 system specifications for the specific module mix being installed.
Q: What happens to the node's I/O if the EtherNet/IP connection drops?
The adapter applies the configured connection-loss behavior to each I/O module — typically outputs de-energize and inputs hold their last known state until the connection is restored, with specific behavior configurable per module in the engineering software.