PanelView Plus with CompactLogix L32E and SLC 5/04

A mixed-generation HMI project becomes difficult when one PanelView Plus application must exchange data with both a CompactLogix 1769-L32E on EtherNet/IP and an SLC 5/04 that still depends on DH+ or DF1. The first correction is terminology: the L32E is a CompactLogix controller, not a ControlLogix controller. The second is architectural. FactoryTalk View Machine Edition should treat each controller path as a separate, testable communication contract rather than hiding both processors behind one ambiguous shortcut.

A hybrid HMI should expose two explicit controller paths so a technician can isolate an EtherNet/IP fault from a legacy-network fault.

Start with an inventory, not a bridge

Record the exact PanelView Plus catalog number, firmware revision, FactoryTalk View ME version, controller catalog numbers, SLC channel configuration, and every installed communication module. A 1769-L32E has an embedded Ethernet port. An SLC 5/04 provides DH+ on Channel 1 and can use Channel 0 for serial protocols; it does not become an EtherNet/IP controller merely because a gateway is installed. That distinction determines which device owns routing, diagnostics, and recovery.

Also separate design-time and runtime paths. The engineering computer may browse a controller through one interface while the terminal uses another after the runtime file is downloaded. Rockwell’s EtherNet/IP Network Devices User Manual explains that FactoryTalk Linx provides the runtime communication service used by PanelView Plus and FactoryTalk View. A successful laptop browse therefore does not prove that the terminal’s runtime path is correct.

Build the CompactLogix path directly

Give the L32E a documented static address on the control subnet and create a dedicated FactoryTalk Linx device shortcut, such as CLX_L32E. Select the controller in the Design tab, then copy or reproduce the path in the Runtime tab. Verify that the shortcut resolves to the controller itself rather than only to an Ethernet driver. The terminal, controller, and engineering workstation must have compatible IP settings, but they should not share addresses. Check subnet masks and any routed VLAN boundary before blaming the HMI application.

Use controller-scoped tags when practical and maintain a clear ownership prefix in HMI references. An alarm or command named for its source controller is easier to diagnose during migration. For commands, use request, acknowledgement, timeout, and permissive states rather than a momentary HMI write that assumes the network never pauses. The PLC should own the final interlock decision; the PanelView is an operator interface, not a safety controller.

Choose an honest SLC 5/04 access strategy

The SLC path depends on installed hardware and the required data rate. A serial-to-Ethernet interface can expose Channel 0 data, but its connection and throughput limits must be checked against the exact interface manual. A gateway can be useful for a small number of HMI values, yet it should not be treated as equivalent to native EtherNet/IP. Polling too many integer files through a serial bottleneck creates slow displays, stale values, and nuisance communication alarms.

If DH+ must remain, a 1756-DHRIO-based gateway can route between Ethernet and DH+ when it is correctly configured in a ControlLogix chassis. That chassis is the gateway; it does not turn the 1769-L32E into a ControlLogix controller. Confirm DH+ node numbers in octal, channel mode, baud rate, termination, and the complete route. Avoid publishing a universal message path because slot numbers and topology are site-specific. A route copied from another machine can reach the wrong node or fail after a chassis change.

A third-party industrial protocol gateway may also be appropriate, but only after verifying supported services, simultaneous client limits, serial timing, environmental rating, and vendor support. The decision should be based on measured HMI traffic and lifecycle risk, not on whether the device appears in a browse window.

Separate shortcuts preserve controller identity and make runtime diagnostics far more useful.

Commission the shortcuts as independent systems

Create one shortcut for the L32E and another for the SLC path. Never reuse a shortcut name during a migration simply to avoid editing tags. Confirm the Design and Runtime tabs, save the communication configuration, create the runtime file for the intended terminal firmware, and download it with the correct communication settings included.

Test read-only values first. Use a value that changes predictably, a heartbeat generated by each controller, and an HMI timestamp that reveals stale data. Then test command handshakes with the machine in a safe state. Disconnect each network path separately and confirm that the HMI identifies the failed controller without freezing or presenting old values as current. Restore the link and measure recovery time.

Diagnose by layer

If both shortcuts fail, start with terminal addressing, switch port status, VLAN access, and runtime configuration. If only the L32E fails, verify IP reachability, controller mode, embedded-port status, and the shortcut target. If only the SLC fails, divide the path into Ethernet-to-gateway, gateway configuration, serial or DH+ wiring, and SLC channel settings. Error counters and link indicators are more useful than repeatedly downloading the same HMI file.

DH+ work deserves extra discipline. Duplicate node numbers, incorrect baud rates, missing termination, damaged trunk cable, or an improperly configured DHRIO channel can create intermittent symptoms that look like an HMI defect. Capture the known-good node map and physical topology before changing anything. For EtherNet/IP, monitor connection use and packet rate instead of assuming that a lightly loaded office network model applies.

Design the migration exit

A bridge is often a temporary asset, but temporary systems can remain for years. Document power, cables, firmware, configuration backups, spare strategy, and the owner of every shortcut. Keep the SLC data contract stable while new logic is commissioned, then retire legacy paths in controlled stages. Relevant replacement planning belongs with the store’s PLC and PAC systems inventory and its HMI displays lifecycle plan.

The engineering goal is not merely to make tags browse. It is to create a communication design whose failures are visible, bounded, and recoverable. Separate controller identity, explicit runtime paths, measured traffic, and tested loss-of-communication behavior provide that foundation.