Establishing reliable RSLinx Classic communications to an SLC 5/04 remains a foundational skill on plants that still run RSLogix 500 logic beside newer ControlLogix cells. The controller’s dual-channel personality is the first gate: Channel 0 can be DF1 or DH-485, while Channel 1 is DH+ only. Choosing the wrong RSLinx driver for the physical port is the most common reason RSWho stays empty even when the processor RUN LED is healthy.

Match media before you open RSLinx. DF1 Full-Duplex on Channel 0 typically uses a 1747-CP3 (or equivalent) serial cable from a PC COM port or USB-serial adapter. DH-485 on Channel 0 needs a 1747-PIC or AIC+ path, not a plain null-modem cable. DH+ on Channel 1 requires a 1784-PCMK, 1784-PKTX, or legacy KTX-class card with the correct trunk tap and terminating resistors. Baud rate on both ends must match exactly, and DH+ node addresses are octal values from 00 through 77.

Verify the processor channel configuration in RSLogix 500

Online or offline, open Channel Configuration for the SLC 5/04 and note which protocol is assigned to Channel 0 and which node or station number is defined. Do not assume factory defaults survived the last OEM download. If Channel 0 is DF1 Full-Duplex at 19200 with no handshaking, your RSLinx DF1 driver must mirror those settings. If Channel 0 is DH-485, the station number and baud must agree with the AIC+ network. Channel 1 DH+ node address must be unique on the trunk; duplicate octal nodes produce intermittent browsing that looks like a driver bug.

Print or screenshot the channel summary before leaving the laptop cart. Many “RSLinx cannot see the PLC” tickets resolve when the electrician discovers Channel 0 was switched to DH-485 months earlier for a panel-view migration while the laptop still loads a DF1 driver profile.

Configure the RSLinx driver

1. Launch RSLinx Classic and open Configure Drivers.
2. For DF1 on Channel 0, add “RS-232 DF1 devices,” select the correct COM port, set Device to SLC-CH0 / 1747-CP3 style, match baud, parity, error checking, and Full-Duplex.
3. For DH-485, add the 1747-PIC/AIC+ driver (or appropriate USB replacement stack), set station number unique from the processor, and match baud.
4. For DH+ on Channel 1, configure the 1784-PCMK/PKTX/KTX driver, set the PC node to an unused octal address, and verify network type and speed (typically 57.6K or 230.4K as installed).
5. Start the driver and confirm it shows Running without port-in-use errors.

Browse with RSWho and validate depth

Open RSWho, expand the new driver, and wait for the SLC 5/04 station to appear with the expected node. Online the controller from RSLogix 500 through that path and perform a small data-table monitor read. If the station appears then drops, revisit cable shield, AIC+ bias, DH+ terminations, and USB-serial latency. Laptop power management that suspends USB COM ports is a frequent cause of DF1 dropouts during long uploads.

Checklist before calling the network “dead”:
1. RSLogix 500 Channel Config protocol = intended media
2. Baud identical on PLC and RSLinx
3. Cable/adapter part number matches protocol
4. DH+ node unique and octal
5. Driver status = Running; RSWho shows station
6. RSLogix 500 goes online without timeout storms

Pitfalls that waste a shift

Do not point a DH+ driver at Channel 0. Do not use a CP3 cable on a DH-485 port and expect auto-negotiation. USB-RS232 adapters that ignore fixed baud under Windows driver power saving will pass a first browse and fail an upload. On DH+, document octal addresses in the cabinet so decimal-thinking technicians do not set node 8 when the dial reads 10 octal. Keep one known-good CP3 and one known-good PCMK profile in the plant RSLinx backup folder.

Once RSWho consistently lists the SLC 5/04, save the RSLinx configuration and export the driver set for the maintenance image. That small discipline keeps offline edits, force tables, and trending tools available on aging PLC & PAC systems without reinventing the serial path every outage.