Selection guide
Connecting SLC 500 processors to Ignition SCADA
Short answer
For a serial-only SLC 5/03 that already feeds a PanelView, put a DF1-capable serial gateway with Ethernet upstream on the serial line and let Ignition share it in DF1 full-duplex. Swap in a 5/05 when the machine is due processor work anyway, because Ignition then gets a dedicated Ethernet channel. Use RSLinx Classic OPC-DA as a pilot when it is already licensed, and skip the DeviceNet-plus-LabVIEW route.
On this page
- Start with the catalog number, not the family name
- The five paths, decided
- Setting up the DF1 side
- One port, two clients: arithmetic for a 5/03 feeding a PanelView
- The RSLinx Classic OPC-DA pilot
- Modbus map or native driver
- Prove the path before you change hardware
- The decision, controller by controller
- Questions asked
For serial-only SLC 5/03 processors that already feed PanelView HMIs, the lowest-risk path to Ignition is a DF1-capable serial gateway with Ethernet upstream: the processor and its wiring stay as they are, and the serial line is shared in DF1 full-duplex. Swap in a 5/05 when the machine is due processor work anyway, because Ignition then gets a dedicated Ethernet channel while the PanelView keeps the serial port. RSLinx Classic as an OPC-DA server is the zero-new-hardware pilot when it is already licensed. Leave the DeviceNet-scanner-plus-LabVIEW idea out of the SCADA plan: it puts a PC and a second software stack between the data and Ignition. Decide controller by controller from the catalog number, never from the family name.
Start with the catalog number, not the family name #
Read the catalog number off each processor and record its ports and what the PanelView actually uses today. A 5/03 is serial-only: the programmer cable drawing for the 5/03 and 5/04 shows one 9-pin D-shell serial connector, and that port is the whole conversation. A 5/05 is the same chassis and I/O with an Ethernet channel on the processor. Split the MicroLogix units by model as well: the ones with a built-in Ethernet port reach Ignition directly, and the serial-only ones take the same gateway treatment as the 5/03. When a serial-only MicroLogix is already at end of life, spending on a connection path is the wrong money — migrating a MicroLogix 1500 machine to a current PLC works through that choice. The panel survey, not the family name, picks the path.
The five paths, decided #
| Path | What Ignition sees | The serial HMI | Commit to it when |
|---|---|---|---|
| Processor swap to a 5/05 | Ethernet with native SLC addressing | Stays on the serial port | A shutdown window exists anyway, or a third client is coming |
| Ethernet module in the rack | Ethernet through the module | Untouched | A supported module is already on hand and the processor takes it; otherwise the 5/05 swap beats module hunting |
| DF1 serial gateway, Ethernet upstream | EtherNet/IP pass-through or a Modbus TCP map | Shares the serial port in full-duplex | The 5/03 and its wiring must stay untouched |
| RSLinx Classic OPC-DA server | OPC-DA | Untouched | The license already exists and you need a pilot this week |
| DeviceNet scanner to a PC running LabVIEW | Nothing directly; LabVIEW re-publishes | Untouched | Only where a LabVIEW data system already owns that scanner |
One name on the shortlist does not fit the serial side. The Moxa MGate EIP3170 converts between EtherNet/IP and Modbus, and a converter of that class has no DF1 serial side to put on a 5/03's port — keep it for EtherNet/IP-to-Modbus duty elsewhere. The class that fits terminates DF1 on a serial port and presents EtherNet/IP or Modbus TCP upstream, and the Digi One IAP HAZ is that class. Confirm the exact model's conversion and simultaneous pass-through behavior in its documentation before ordering, because that behavior is what keeps the PanelView alive while Ignition polls. If the real destination is a newer platform rather than a 5/05, treat the swap as a stopgap: passing SLC 5/03 data to a CompactLogix over Ethernet shows the bridge pattern that keeps the old processor serving data during the change.
Setting up the DF1 side #
- Mode: DF1 Full Duplex with the Control Line set to No Handshaking — the documented configuration for this driver and port.
- Stations: leave the Source ID at 9 as the documented setup does, and keep each master's source station distinct once two initiators share the line.
- Cable: the 1747-CP3, or any female-to-female null-modem crossover DB9 cable. The 9-pin connector carries RXD on pin 2 and TXD on pin 3 in the programmer cable pinout, and a null-modem crosses them.
- Laptop work: a USB-to-RS232 adapter stands in when the PC has no serial port; in a virtual machine, confirm the COM port mapping reaches the adapter before blaming the PLC.
One port, two clients: arithmetic for a 5/03 feeding a PanelView #
Inputs:
- Serial ports on a 5/03: 1 — the single 9-pin connector in the programmer cable drawing.
- Clients needing that port: 2 — the existing PanelView, plus Ignition through the gateway.
- Mode after the gateway: DF1 Full Duplex, Control Line No Handshaking.
- Ports after a 5/05 swap: 2 — the serial port stays and the processor adds an Ethernet channel.
Rule in words: one serial port carries one physical conversation; a second client either time-shares that conversation or gets its own channel.
Arithmetic:
- With the gateway: 2 clients − 1 port = 1 client sharing. Full-duplex resolves the sharing in time — every Ignition request waits its turn between PanelView requests, and the reverse.
- After a 5/05 swap: 2 ports − 2 clients = 0 shared conversations. Ignition owns the Ethernet channel outright.
Result: the gateway path runs both clients on one port and prices it in turn-taking latency; the swap removes the sharing entirely.
Decision: keep the shared port while Ignition is the only new client and its writes are occasional. Two clients on one port is the limit this arrangement is built for; a third client, or writes fast enough to close a control loop, is the threshold where Ignition moves to its own channel through the 5/05 swap or in-rack Ethernet.
The RSLinx Classic OPC-DA pilot #
When RSLinx Classic is already licensed, it serves the DF1-connected processors as an OPC-DA server and Ignition connects as an OPC client, with no new hardware on the PLC side. Host the server on an industrial mini PC in the cabinet next to the serial links. If that computer is not the Ignition gateway computer, plan for DCOM configuration; remote OPC is the known friction in this arrangement. Before calling it production, connect every controller at once and watch scan rates under real load — the arithmetic in sizing one Ignition gateway for 100,000 OPC UA tags bounds the Ignition side of that test. Decision: use it to prove the data this week, then move machines onto gateways or 5/05 swaps as shutdowns allow.
Modbus map or native driver #
Two shapes exist on the Ignition side. A pass-through keeps native SLC addressing, so tags map one-to-one and the mapping work is minimal. A Modbus TCP conversion means you build the register map inside the gateway and point the Modbus driver at those registers, which earns its keep when several controllers must appear as one consolidated server. For the Ethernet-capable MicroLogix and 5/05 processors, use the native path — how a SCADA client reads a small PLC over EtherNet/IP walks through it for small controllers. In either shape, configure the connection read-only until reads are stable.
Prove the path before you change hardware #
- Back up the PLC project and write down every communication setting before touching anything.
- From the Ignition host, confirm the gateway or controller answers on the network; reachability proves only the network leg.
- Bring up one read-only tag and read the driver diagnostics — a connection that opens while tags fail is an addressing or protocol mismatch, not a hardware fault.
- Repeat with the PanelView running. If one client disturbs the other, the sharing is not working: fix the mode and station settings before buying anything.
- Change one layer at a time; swapping processor, gateway and driver together hides which layer failed and makes rollback guesswork.
- Test writes only against a designated non-critical address with the machine's reaction observed, and leave production writes until the logic that consumes them has been checked.
The decision, controller by controller #
- Untouched 5/03 with a serial PanelView: a DF1 gateway of the Digi One IAP HAZ class, full-duplex, sharing the port.
- Machine with a shutdown window coming or a third client on the horizon: 5/05 swap — Ignition takes Ethernet, the PanelView keeps serial.
- Ethernet-capable MicroLogix: connect directly and spend nothing on gateways.
- Licensed RSLinx Classic on spare hardware: pilot now, plan the exit.
- DeviceNet-plus-LabVIEW: leave it where it already serves; it is not the SCADA path.
Questions asked
Can the PanelView and Ignition really share one serial port?
Yes, when both initiators run DF1 full-duplex with the control line set to no handshaking. The PanelView and the gateway take turns on the line, so each one's polling adds latency to the other. If the PanelView is configured for a different DF1 mode today, bring it to full-duplex before adding the gateway, and give each master its own source station rather than letting both sit at the same ID.
Which Ignition connection should I use with the gateway: Modbus or the native SLC driver?
Follow whatever the gateway exposes upstream. Where it passes the native protocol through, your existing address references carry over with almost no remapping. Where it presents Modbus TCP, you own the register layout on the gateway side and point the Modbus driver at those registers — worth it when several controllers must appear as one consolidated server. Writes travel either way, but start the connection read-only.
Is RSLinx Classic OPC-DA a production answer or just a pilot?
A pilot, and only with a license you already hold. Check that your edition includes OPC serving, and when the server computer is not the Ignition gateway computer, plan for DCOM configuration, because remote OPC is the known friction point. Connect every controller at once and watch scan rates under real load; if responses sag, split controllers across servers or move them onto gateways rather than tuning around the OPC layer.
Do the MicroLogix controllers in the same plant need the same treatment?
No. Split them by catalog number. The MicroLogix controllers with a built-in Ethernet port connect to Ignition directly over the same native path as a 5/05, so gateways there are wasted money. The serial-only ones take the same DF1 gateway treatment as the 5/03, and for units already at end of life, replacement is the better spend.
After swapping to a 5/05, do I still need the gateway?
No. Ignition talks to the processor's Ethernet channel and the PanelView keeps the serial port, so the gateway comes out of the panel. Keep a 1747-CP3 or null-modem cable on the shelf for program uploads, and if the PanelView moves to Ethernet later, the serial port returns to programming duty full time.