How to Connect SLC 500 PLC to PanelView Plus via Ethernet
Scenario: A manufacturing facility uses an Allen-Bradley SLC 5/04 PLC (1747-L542) with DH-485 communication for a traction converter test bench. The existing PanelView 550 (2711-B5A2) monochrome terminal is limited, and the plant needs to add a new PanelView Plus 600 (2711P-T6C20D) color touchscreen and connect to an MES for paperless traceability. The SLC 5/04 lacks an Ethernet port, making direct integration impossible without a costly PLC replacement. This article details a cost-effective solution using an industrial Ethernet protocol converter to bridge DH-485 to EtherNet/IP and Modbus TCP, enabling seamless communication between the legacy PLC, modern HMI, and MES.
System Architecture and Hardware Selection
The core of the upgrade revolves around a protocol converter that acts as a transparent bridge between the SLC 500’s DH-485 network and Ethernet-based devices. The chosen device is an industrial Ethernet communication module (similar to YC8000-AB) that supports dual protocol stacks: EtherNet/IP for Rockwell Automation HMI and Modbus TCP for third-party systems like MES.
| Component | Specification | Role |
|---|---|---|
| PLC | Allen-Bradley SLC 5/04 (1747-L542) with 1747-M13 memory module | Logic control, data acquisition |
| Legacy HMI | PanelView 550 (2711-B5A2), DH-485 | Local backup display |
| New HMI | PanelView Plus 600 (2711P-T6C20D), 10/100 Mbps Ethernet | Primary operator interface |
| Protocol Converter | Industrial Ethernet module, DH-485 to EtherNet/IP & Modbus TCP, 24VDC, DIN rail | Communication bridge |
| Network Switch | Managed industrial switch, e.g., Hirschmann OCTOPUS 8M-EEC | Ethernet connectivity |
| MES Workstation | Industrial PC with FactoryTalk View SE or custom C# application | Data logging, batch management |
Wiring and Network Topology
The DH-485 network originally connected the SLC 5/04, PanelView 550, and a 1747-UIC adapter. The protocol converter is simply wired in parallel to the existing DH-485 trunk line using its dedicated DH-485 terminal block. No changes to the PLC program or existing devices are required. The converter’s station address is set to 3 (unused on the network), and the default baud rate of 19.2 kbps is maintained.
On the Ethernet side, the converter’s RJ45 port connects to the industrial switch. IP addresses are assigned as follows:
- Protocol Converter: 192.168.10.38, subnet 255.255.255.0, gateway 192.168.10.1
- PanelView Plus 600: 192.168.10.40, same subnet
- MES Workstation: 192.168.10.x range, accessing converter via Modbus TCP port 502
The PanelView Plus uses EtherNet/IP driver to communicate with the converter, which maps PLC data to CIP assemblies. The MES system uses standard Modbus TCP to read/write holding registers, with the converter handling protocol translation transparently.
Protocol Converter Configuration
Configuration is performed via a USB-C connection and dedicated software (e.g., YC Configurator). The steps are straightforward:
- Select Template: Choose “SLC DH-485 → EtherNet/IP + Modbus TCP” to load pre-defined settings.
- DH-485 Settings: Set station address to 3, scan length to 32 words, and update rate to 10 ms. This matches the SLC’s data table size for N7:0–N7:31.
- EtherNet/IP Mapping: Create Assembly Instance 101 (Input) and map N7:0–N7:31 to %I101. Optionally, create Assembly Instance 102 for outputs if needed (e.g., N7:10 for start commands).
- Modbus TCP Mapping: Enable “Zero Offset” and map N7:0–N7:31 to Holding Registers 40001–40032 (function code 03). This allows MES to read data with standard Modbus commands.
- Download and Verify: Click “Download” to transfer configuration. The module’s RUN LED should turn solid green, and COMM LED flashes to indicate active data exchange with the SLC.
Tip: Always verify the DH-485 baud rate matches the existing network. Most SLC 5/04 systems use 19.2 kbps, but some older installations may use 9600 bps. Mismatched baud rates will prevent communication.
PanelView Plus 600 HMI Development
Using FactoryTalk View Studio ME, create a new project and add an EtherNet/IP driver pointing to the converter’s IP address (192.168.10.38). Define a shortcut with CIP Instance 101 and length 32 words. This gives access to the SLC’s N7 data as if it were a native EtherNet/IP device.
Typical tag mapping includes:
| HMI Tag | CIP Address | SLC Address | Description |
|---|---|---|---|
| Voltage_Set | %I101:0 | N7:0 | Voltage setpoint (0-1000V) |
| Current_Set | %I101:1 | N7:1 | Current setpoint (0-500A) |
| Temp1 | %I101:2 | N7:2 | Temperature reading (°C) |
| Start_Test | %O101:0/0 | N7:10/0 | Start test command (momentary) |
Design screens with numeric inputs, bar graphs, and trend objects. Download the runtime to the PanelView Plus. Data refresh rates under 200 ms are achievable, meeting real-time monitoring needs.
MES Integration via Modbus TCP
The MES application, developed in C# using the NModbus library, connects to the converter at 192.168.10.38:502. It periodically reads holding registers 40001–40008 to capture voltage, current, temperature, and status. Writing to register 40020 (mapped to N7:20) allows the MES to send a test batch number, which the PLC program stores in a string file (ST10:0) for label printing.
Network analysis with Wireshark shows an average Modbus TCP response time of 8 ms with zero packet loss, well within the 1-second MES sampling cycle. The dual protocol support ensures that both HMI and MES can access the same data concurrently without conflicts.
PLC Program Considerations
Since the protocol converter is transparent to the SLC, no major ladder logic changes are needed. The existing DH-485 messaging remains intact. A simple addition at the end of the routine can set a “test complete” flag (N7:11/0) that is readable by both the PanelView Plus and MES. This minimizes downtime and validation effort.
Important: Ensure the SLC’s DH-485 communication channel is not overloaded. The converter’s scan rate should be set to balance data freshness with network load. A 10 ms update for 32 words is typically safe, but monitor the channel utilization if other devices are present.
Benefits and Lessons Learned
- Cost Savings: Avoided replacing the SLC 5/04 with a CompactLogix system, saving hardware, engineering, and re-certification costs.
- Minimal Downtime: The converter was installed during a short maintenance window without disrupting the existing DH-485 network.
- Dual Protocol Support: Simultaneous EtherNet/IP and Modbus TCP allowed seamless integration of Rockwell HMI and third-party MES.
- Remote Diagnostics: The converter’s web interface enables remote monitoring and firmware updates, simplifying long-term maintenance.
- Scalability: The same approach can be applied to other legacy PLCs with serial interfaces, such as PLC-5 or MicroLogix, using appropriate protocol converters.
This case demonstrates that with the right protocol conversion technology, aging automation assets can be modernized to meet Industry 4.0 demands without large capital expenditures. The key is selecting a reliable, industrial-grade converter that supports the required protocols and offers easy configuration.
Conclusion: Upgrading an SLC 500 system to Ethernet connectivity is not only feasible but also practical. By leveraging a protocol converter, facilities can extend the life of their legacy equipment while gaining modern communication capabilities. This solution is ideal for budget-conscious projects with tight timelines.
