Servo axes expose network shortcuts quickly. Integrating a Kinetix 5500 (2198-xxxx-ERS3) onto a subnet that already carries ControlLogix I/O, safety adapters, PanelView traffic, and VFDs raises a practical question: is a managed Stratix mandatory, and which topology keeps CIP Sync inside budget? The answer hinges on Requested Packet Interval, IEEE 1588 V2 time sync, and jitter—not on whether the drive “pings.”

CIP Motion is intolerant of unmanaged residence-time jitter even when unicast connections look healthy in Studio 5000.

CIP Motion / CIP Sync requirements

If any switch in the path fails to act as a transparent clock (or at least bound PTP residence time), the drive rejects synchronization and the fault looks like a servo problem.

Switch feature checklist

• IEEE 1588 V2 transparent clock with tight residence-time specs
• Hardware QoS with strict priority for time-critical DSCP (EtherNet/IP and PTP markings)
• IGMPv2/v3 snooping when multicast remains in use
• ODVA / Rockwell-validated CIP behavior where possible (Stratix 5700/5400/5410 families)

Unmanaged switches forward PTP frames without correcting residence time; multi-hop jitter can reach hundreds of microseconds—outside a 1 ms motion budget. Third-party managed switches can work if PTP TC and QoS are configured correctly, but you own the risk and lose native Stratix diagnostics in the I/O tree.

Low-axis topology: direct DLR from EN2TR

For one or two axes, a proven pattern is physical segregation rather than buying a motion switch on day one:

EN2TR Port 1 -> plant switch (HMI, I/O, VFD)
EN2TR Port 2 -> Kinetix 5500 Port 1 (2-node DLR)
Drive: Network Topology = DLR, node (not supervisor)
Axis Update Period = 1 ms (match RPI)

Unicast CIP Motion on that two-node segment removes IGMP pressure from the motion path. Cable length must still respect copper limits; ring circumference is the sum of both segments when you later expand the DLR chain.

HMI broadcast domains are the quiet enemy of 1 ms motion streams on shared subnets.

HMI segregation options

Update Period versus RPI

On a Kinetix 5500 axis, Update Period (Motion properties) and RPI (Connection properties) are related but not identical knobs. Set both to 1 ms for ERS3 firmware that supports it, and keep them matched. A mismatch is a frequent root cause of “Connection Not Established” during commissioning. PTP announce rates on the ENxT should remain at the Rockwell-recommended values unless a validated architecture document says otherwise.

As axis count grows past roughly eight to ten drives on shared unmanaged fabric, cumulative jitter usually forces a Stratix-class upgrade even if unicast connections looked acceptable with one or two axes. Plan that inflection during the first retrofit rather than after the third unexplained sync fault.

Commissioning checks

1. Confirm grandmaster is the intended ENxT; read PTP state on Stratix if present
2. Match Update Period and RPI; mismatches yield connection faults
3. Verify NS/connection lists against switch counters when they disagree
4. Storm-test HMI navigation while axes run—watch for sync faults
5. Document topology drawings; “temporary” office switches become permanent debt
6. Capture a baseline of axis following error before and after HMI stress

Motion and Logix hardware sparing should follow the same PLC/PAC rules applied to discrete controllers so a failed EN2TR does not strand a production cell.