Troubleshooting
Connect SCADA to an SLC 5/03 and MicroLogix 1500
Short answer
None of the three listed drivers will work: ControlLogix and CompactLogix are different controller families, and the MicroLogix 1100/1400 connection is Ethernet to models that have an Ethernet port. Your SLC 5/03 and MicroLogix 1500 LRP are serial-only, so connect through an OPC server with a serial DF1 or DH-485 driver, or a protocol-aware gateway. Put both controllers on one DH-485 network and bridge it once.
On this page
None of the three connections will work, and the reason is physical, not a setting. ControlLogix and CompactLogix are different controller families from your SLC and MicroLogix, and the MicroLogix 1100/1400 choice is an Ethernet connection aimed at the family members that carry an Ethernet port. Your SLC 5/03 and MicroLogix 1500 LRP have no such port — both CPUs are serial-only. Pick the architecture instead of the driver: an OPC server running serial SLC-500 and MicroLogix drivers, or a protocol-aware gateway that speaks DF1 or DH-485 downstream. For this pair, the build to commit to is one DH-485 network carrying both controllers, bridged once.
Why the listed drivers cannot reach these CPUs #
Every choice your software offered opens an Ethernet session; that is the whole problem. The MicroLogix 1100 and 1400 appear by name because they are the MicroLogix models with a built-in Ethernet path — the route described in how a SCADA client reads a small PLC over EtherNet/IP. The 1500 predates them and never gained that port.
| Connection offered | Reaches these CPUs | Reason |
|---|---|---|
| ControlLogix | No | Different controller family with a tag-based data model |
| CompactLogix | No | Same Logix family in packaged form, same data model |
| MicroLogix 1100/1400 | No | Ethernet connection; the 1500 LRP has no Ethernet port |
| SLC-500 or MicroLogix device over DF1 or DH-485 | Yes | Serial path served by an OPC server or a gateway |
The data model is the second wall. SLC and MicroLogix programs address data files — N7:0, B3:1, T4:2 — element by element inside a numbered file. Logix processors hold named tags. A Logix driver selection does not convert one into the other; there is nothing in your CPUs for it to address, over any cable.
ControlLogix and CompactLogix are controllers, not connection modes #
Each name is a controller your software could reach if one were installed; neither is a mode for reaching something else. The question 'can we connect using ControlLogix as well as CompactLogix' therefore answers no, in every scenario: those selections belong on machines whose processor actually is a Logix controller, typically reached over an EtherNet/IP network. Your CPUs predate that platform and speak DF1, DH-485 and ASCII out of serial ports. The work is not choosing between those two names; it is building the serial path the CPUs actually have.
What the two CPUs actually give you #
The SLC 5/03 carries two ports. One is a dedicated DH-485 port, native to that network with no protocol selection to make. The other is the serial Channel 0, whose configuration selects DF1, DH-485 or ASCII, as the SLC 500 Modular Hardware Style User Manual (1747-UM011) documents.
The MicroLogix 1500 LRP also carries two ports, both RS-232 serial — the second channel is what the LRP variant adds over the standard processor. Channel 0 selects DF1 (full- or half-duplex), DH-485 or ASCII. Neither channel is Ethernet, and no configuration changes that.
Two ports per CPU is the break that makes this job easy: SCADA takes one channel while the programming terminal or an existing HMI keeps the other, so nobody gets evicted from a port that already works.
Two architectures that close the link #
Route one is a serial OPC server. The server runs SLC-500 and MicroLogix device drivers over a PC serial port, and the SCADA package reads through its OPC client. If your package has an OPC client, build this route first: there is no protocol translation to debug, and one server carries both CPUs. A natural host is an industrial mini PC mounted beside the controllers, close enough that the serial cables stay short.
Route two is a protocol-aware gateway. It terminates the protocol your SCADA package serves on its Ethernet side and originates DF1 or DH-485 frames toward the CPU on its serial side, so the package addresses mapped registers as it would any other device. Take this route when the package cannot act as an OPC client. Either way the requirement is fixed: the box must speak both protocols. A converter that only pipes serial bytes across Ethernet is not a translator and will pass nothing useful.
A third reader needs neither box: another controller can pull the same data files straight off the wire, the approach covered in reading SLC 5/03 data over DH-485 and DF1.
Put both controllers on one DH-485 network #
One network, one bridge — that is the architecture to build for this pair. The SLC 5/03 is native on DH-485 through its dedicated port; set the MicroLogix 1500 Channel 0 to DH-485 and join it with the RS-232-to-RS-485 arrangement its documentation specifies. Give each CPU its own station number, and a single gateway or a single OPC-server driver then serves both. DH-485 is a token-passing protocol over RS-485 signaling, so the wiring is multidrop, not one cable per device.
The PC-side attachment and cabling are the same job described in connecting an SLC 5/03 HMI and PC over DH-485. Other Allen-Bradley serial nodes join the same wire the same way.
How fast the serial link will poll #
An illustrative example with round numbers: take DF1 full-duplex at 19200 bit/s, a typical setting for these channels — the channel status screen in the programming software gives the real value on your CPU. One character on the wire is 1 start bit + 8 data bits + 1 stop bit = 10 bits, so the channel carries 19200 bit/s ÷ 10 bit = 1920 characters per second. A read of 100 integer words returns 200 data bytes; with framing and checksum call it 220 bytes, and 220 bytes is 220 characters on the wire, against a 20-byte request.
- Response: 220 characters ÷ 1920 characters/s ≈ 0.11 s on the wire.
- Request: 20 characters ÷ 1920 characters/s ≈ 0.01 s.
- Round trip ≈ 0.12 s of wire time, before processing and turnaround.
At 9600 bit/s the same exchange takes 960 characters/s and the response alone is about 0.23 s. The decision from those numbers: polling both controllers once per second over the one link leaves the wire idle most of the time, while 100 ms-class updates are not what this hardware delivers — if one screen demands that, poll only the handful of registers behind it.
Commissioning checklist #
- Record what is installed: CPU catalog numbers from the nameplates, which port each cable leaves, and every device already on that channel — programmer, HMI, another controller.
- Read the channel configuration in the programming software and write down protocol, baud rate, parity and stop bits, error checking and station number. Configured values, not assumed defaults.
- Prove serial access before touching SCADA: go online with the programming software. A CPU that will not appear there will not appear to an OPC server either — the same failure seen with a MicroLogix 1000 that vanished from RSLinx after a channel change.
- Choose the architecture from the sections above; for this pair, one DH-485 network with a single bridge.
- Wire the downstream side to the documented pinout and the recorded serial settings, then configure the upstream side — OPC device definitions or the gateway Ethernet setup.
- Bring the link up read-only: read one known value, a timer accumulator or an integer register, and watch it change in step with the programming software during an approved machine state.
- Prove which controller answered before the first write — on a shared DH-485 network, a write aimed at the wrong station number commands a machine you did not choose. Enable writes one tag at a time after that.
Questions asked
What is the actual difference between ControlLogix and CompactLogix?
ControlLogix is the chassis-based family: processor, network modules and I/O are separate modules slotted into one rack, the choice for large I/O counts, integrated motion and redundancy. CompactLogix packages a single processor with its own local I/O for mid-size machines. Both are programmed with the same Logix tools and addressed through named tags. The choice between them is a machine-size decision on new projects; it never enters a driver list for an SLC or a MicroLogix.
Can one gateway or one OPC driver serve both controllers?
Yes. Leave the SLC 5/03 on its DH-485 port, set the MicroLogix 1500 Channel 0 to DH-485, and both CPUs sit on one network behind a single bridge. Give each station its own node number; DH-485 carries up to 32 nodes. That is the entire addressing plan: no second gateway, and one serial driver in the OPC server covers both CPUs.
We already own a Modbus TCP to Modbus RTU gateway. Will it work here?
No. Neither CPU offers Modbus RTU on its serial channels: the SLC 5/03 Channel 0 selects DF1, DH-485 or ASCII, and the MicroLogix 1500 offers the same set on Channel 0. The Modbus-capable MicroLogix models are the 1100 and 1400, which is also why the driver list names them. Keep the Modbus gateway for instruments and drives that actually speak it.
What cable does the SLC 5/03 serial port need for DF1?
A female-to-female null-modem (crossover) serial cable between the CPU and the PC, gateway or converter; a straight-through cable will not pass data between two DTE devices. For the MicroLogix 1500, use the pinout its installation instructions give for the channel you chose.