Few plants cut every CPU over in a single outage. Operator stations therefore must present a ControlLogix or CompactLogix L32E on EtherNet/IP while a remaining SLC 5/04 still speaks DH+ or DF1. Collapsing both controllers into one RSLinx topic creates failures that look networked when they are merely organizational. Current PanelView Plus 7 catalogs also dropped native DH+, so the SLC side usually needs a bridge.

Three practical bridges—NET-ENI, DHRIO, or Digi One IAP—cover most hybrid PanelView Plus migrations.

Reference nodes

Option A — 1761-NET-ENI on SLC Channel 0

Wire CH0 DF1 Full Duplex (no handshaking) to the ENI RJ-12 with a 1761-CBL-PM02/HM02 cable. Set baud to 38.4 kbps on L542-class processors (19.2 kbps may be the ceiling on older L541 units). Assign a static IP, set DF1 device type to SLC 5/04, and raise message timeout (~1500 ms) for loaded networks. In RSLinx, the ENI appears as a parent with the SLC as a child when the serial link is healthy.

Connection limit warning: the NET-ENI commonly supports only six concurrent TCP connections. A PanelView Plus, a programming laptop, and a historian topic can exhaust the budget quickly. For multi-client HMIs, prefer Digi One IAP or migrate the SLC onto an Ethernet adapter strategy.

SLC CH0 DF1 checklist
- Mode: DF1 Full Duplex, no handshaking
- Baud matches ENI (38400 typical)
- Cable: 1761-CBL-PM02 / HM02 (TX/RX crossed as required)
- ENI firmware FRN 4.xxx+ for modern View ME / RSLinx stacks

Option B — 1756-DHRIO in the Logix chassis

When DH+ must remain, install a 1756-DHRIO, set Channel A to an unused octal node, and keep topology as trunkline/dropline with proper blue-hose practice—do not mix daisy-chain styles on the same segment. From the L32E, reach the SLC with CIP Data Table Read/Write MSG instructions whose path traverses backplane → DHRIO slot → DH+ node (octal). Example path shape: 1,2,04,1,0 for slot 2 and DH+ node 04. Node mismatches surface as path-segment or extended status errors on the MSG.

Keep PanelView shortcuts separated: one EtherNet/IP path to the L32E, one bridged path to the SLC.

Option C — Digi One IAP

Digi One IAP (or SP) provides DF1-to-EtherNet/IP bridging with a higher practical client count than NET-ENI and better ambient ratings for warm cabinets. Configure serial for RS-232, 38400 8-N-1 matching CH0, register the EDS so RSLinx shows a recognized parent/child pair, and treat a lone IAP icon (no SLC child) as a serial-cable fault indicator.

PanelView Plus communication setup

1. Create distinct device shortcuts—never reuse one shortcut name for both CPUs
2. Point the L32E shortcut at the ENBT/EN2T path used by Studio 5000
3. Point the SLC shortcut at ENI, Digi, or the Logix MSG-backed tags you expose
4. Name HMI tags with controller prefixes so operators and maintainers see ownership
5. Validate each shortcut offline with a forced communication test before cutover

Dual-path HMI topic isolation checks

Confirm unique DH+ node numbers, unique IP addresses, and that the PanelView firmware revision still matches the communication module you planned. Do not share a single RSLinx Enterprise topic across both controllers “to save configuration time.” Document both shortcuts on the panel drawings. When migration funding arrives, retire the dual path; until then, spare HMIs and controllers under the same PLC and PAC inventory rules used for the L32E fleet.