IMDHMIControls LibraryShop main store

Troubleshooting

PLC-5 not visible in RSLinx after processor replacement

PLC programming Published 9 min read

Short answer

A replacement PLC-5 stays invisible in RSLinx because the 1785-ENET sidecar answers the network on its own while the processor waits for an application that configures the Ethernet channel 3A. Leave the non-isolated serial port disconnected until the cable is checked, bring the processor up over serial DF1 or DH+, download the saved program, and the Ethernet path returns.

On this page
  1. Why can RSLinx see the 1785-ENET but not the new PLC-5 processor?
  2. What do the red PROC and battery lights tell you?
  3. Is the PLC-5 serial port safe to connect straight to a laptop?
  4. How do you build a working serial DF1 path in RSLinx?
  5. Why do the DH+ lights flash green with no processor visible?
  6. How does channel 3A bring the Ethernet sidecar back?
  7. What is the recovery sequence, and how long does the download take?
  8. Questions asked

A PLC-5 processor swap that leaves RSLinx showing the 1785-ENET but not the processor is not a network fault: the sidecar answers on its own interface, and the processor stays invisible until an application that configures Ethernet channel 3A is running in it. Work in this order — read the PROC and battery indicators, respect the non-isolated serial port before touching it, bring up a serial DF1 path, use DH+ as the alternate, download the saved program with that channel set, and only then re-verify Ethernet.

Why can RSLinx see the 1785-ENET but not the new PLC-5 processor? #

Because the 1785-ENET sidecar talks to the network through its own interface, so it answers RSLinx and flash tools on its own, while the PLC-5 behind it stays unreachable until a downloaded application configures channel 3A — a visible module entry proves the module, never the processor.

Separate a reachable module from a reachable processor. The 1785-ENET holds its own network identity and answers browsing and flash-tool traffic no matter what the processor is doing; processor programming traffic passes only once the application in the processor carries the channel configuration that tells the interface how to serve the PLC-5 behind it. That is why a flash tool scanning the Ethernet segment reports the 1785-ENET and stays silent about the processor, and why healthy traffic lights at remote RIO drops say nothing about which application the replacement is running.

A visible bridge module with an invisible controller behind it is a pattern, not a PLC-5 quirk — the same shape appears when reaching a CompactLogix through a ControlNet bridge in RSLinx, where the bridge answers while the controller needs its own working path.

Copying the old processor's switch positions fails as a fix: the switches carry the physical and network identity, while the application and its channel configuration live in memory. Treat Ethernet as the last path to verify, not the first.

What do the red PROC and battery lights tell you? #

A red PROC indicator means the processor sits in a faulted state, and a red battery indicator means the memory battery is low, disconnected or missing — neither light by itself proves a dead processor, and both together usually mean a faulted or empty application.

Read the two lights as separate faults. PROC red is the processor's fault state, cleared by fixing the cause; after a swap the most common causes are an absent or invalid application, a chassis power problem, or a bad backplane connection. Battery red is a retention warning: with a low or disconnected battery, the RAM-resident application survives only while chassis power stays on, and it disappears the moment power is removed. That makes locating the saved program file the highest-value step on this job, before any download is attempted.

Both the removed processor and the replacement showed red PROC and red battery. Before declaring two defective processors, record the catalog identification and switch positions of both units, keep the removed processor documented until recovery is complete, and read the actual application state through the serial path once it works — the lights start the diagnosis, they never finish it.

Is the PLC-5 serial port safe to connect straight to a laptop? #

Treat it as no: channel 0 is a non-isolated RS-232 port, so a voltage difference between the laptop's supply ground and the panel ground drives current directly through the cable, and a burnt smell from the computer means stop, disconnect, and inspect before anything reconnects.

Because the port is not isolated, laptop and controller share a common reference the moment the cable goes in, and incorrect wiring, a damaged interface, or two devices fed from different supplies turns that connection into a current path. After a smell or any heat:

  • Leave the suspect cable and adapter out of both devices until they have been inspected.
  • Check the laptop port, the converter, both cable connectors and the processor connector for heat damage or bent pins.
  • Confirm the connector used is the channel 0 serial port; a DB-25 shell by itself proves nothing about function or pin assignment.
  • Verify continuity on transmit, receive and signal common against the processor's serial wiring documentation, and land any handshake lines where that documentation puts them.
  • Make the first connection with the laptop running on its battery, through a USB-to-serial converter with optical isolation — the isolation breaks the ground-difference path that produced the smell.

If the processor's connector or port shows heat damage, treat that serial channel as suspect and use the DH+ route described below for the download.

How do you build a working serial DF1 path in RSLinx? #

Add a serial DF1 driver in RSLinx on a decent USB-to-serial converter, let the driver's auto-configure detect the port settings instead of guessing them, and prove the identical setup on another serial PLC in the plant before you judge the replacement processor.

  1. Build the cable once and label it: a DB-9-to-DB-25 adapter on the processor's channel 0 port, a straight DB-9 cable, and a null modem inline when auto-configure fails without it.
  2. Create the DF1 driver in RSLinx on the COM port the converter created, then run auto-configure; it listens for the rate and framing that channel 0 actually holds, which matters because the original builder may have left custom serial settings in the program.
  3. If auto-configure fails, add or remove the null modem, re-check continuity, and retry — the cable is the usual culprit, not the processor.
  4. Prove the driver, converter and cable end to end on a different serial PLC on site before concluding the replacement is dead.
  5. Only when RSLinx browses to the processor station, open the programming software; it needs the communication path first, and a tree that shows only the 1785-ENET means the path is not finished yet.

Why do the DH+ lights flash green with no processor visible? #

Flashing green DH+ indicators show token rotation on the network, not a browsable processor — the driver must run at the network's baud rate, 57.6 or 115.2 kbit/s on this platform, and the processor's DH+ station address must be unique on the link.

Network participation is real but incomplete: a node can rotate the token while a rate mismatch or an address conflict keeps it out of the RSLinx browse. Read the removed processor's switch bank, because it holds the DH+ rate and station address the network expects, and set the replacement's switches to match — but expect switches alone to deliver only DH+ access, since the application and its Ethernet channel configuration live in memory, not on the switches. If the replacement arrived pre-set, confirm its station address is unique before judging the network, because two nodes at one address push each other off the link. DH+ is a fully legitimate route for the download whenever the serial path stays suspect.

How does channel 3A bring the Ethernet sidecar back? #

The 1785-ENET takes its whole Ethernet identity from the processor's application: channel 3A must be configured as Ethernet in the program before the module passes processor traffic, so the recovery runs over serial DF1 or DH+, downloads the saved application, and only then does the Ethernet path return.

The Ethernet interface documentation is explicit about the order: once the module has its unique IP address, the channel is configured in the processor application so the interface serves the PLC-5 behind it, and until that application runs in the processor, no programming software can open it — including whatever version the site already runs. In the programming software the setting lives under the processor's channel configuration, on the Edit Channel Properties screen, Channel 3A tab, where you select the Ethernet channel type.

  • Open the saved application offline and check that tab's settings against the site's address plan; the original builder addressed every device through software with custom IP addresses, and the replacement must return with the same plan.
  • Correct the channel settings in the file before the download so the processor comes up Ethernet-ready on the first pass.
  • For the exact screens and settings, the walkthrough of configuring Ethernet on a PLC-5/30 with a 1785-ENET sidecar module follows the same path step by step.

ControlFlash reporting only the 1785-ENET is the expected result on a processor without its application, and it diagnoses nothing about processor firmware — hold every reflash until the processor runs the program. If the module still refuses processor traffic after a verified download, check firmware revision compatibility between the sidecar and the processor before touching firmware.

What is the recovery sequence, and how long does the download take? #

Recover in this order: serial DF1 path, read the processor's state, confirm the saved application, download it with the Ethernet channel configured, then re-verify Ethernet — and a slow download is normal, because at a 9,600 bit/s port a 100,000-byte program needs about 104 s of raw transfer before overhead.

The arithmetic, with illustrative inputs: at 9,600 bit/s with 8 data bits, no parity and 1 stop bit, every byte costs 10 bits on the wire, so 9,600 bit/s ÷ 10 bits/byte = 960 bytes per second; a 100,000-byte application then needs 100,000 B ÷ 960 B/s ≈ 104 s, a bit under two minutes of pure transfer, and DF1 framing plus processor response time stretches real downloads to several minutes. The 9,600 bit/s rate and the 100,000-byte size are examples — the actual rate is whatever auto-configure detected on channel 0, and the time scales linearly: double the bytes, double the minutes.

Then run the sequence:

  1. Confirm the saved program file on the workstation is this machine's application, before anything can overwrite the processor.
  2. Build and prove the serial DF1 path from the sections above; fall back to DH+ at the panel's rate and a unique station address if the serial port is suspect.
  3. Browse to the processor in RSLinx and record its fault or state once it appears.
  4. Compare the file's Ethernet channel settings with the site address plan and correct the file offline.
  5. Download, return the processor to Run, and watch the remote RIO drops re-acquire.
  6. Re-check RSLinx over Ethernet: the processor should now appear behind the 1785-ENET, and the flash tool should see it too.

Decisions by case:

  • Serial path works and the download completes: the fault was the missing application and channel configuration, the replacement processor is sound, and the battery gets replaced per the processor's documented procedure before the next power-down.
  • Auto-configure keeps failing after a clean cable, a proven converter and the cross-check on another PLC: treat the processor's serial channel as damaged, run the recovery over DH+, and quarantine that processor at the next outage.
  • Ethernet stays dead after a verified download: re-check the file's channel 3A settings against the address plan first, then the sidecar's firmware revision compatibility — in that order.
  • No serial path, no DH+ path, and the indicators stay red after seating, chassis power and backplane pins are verified: the processor itself is the remaining suspect, and the replacement is a same-catalog processor staged with the program ready before the swap.
  • Battery found dead or disconnected and the panel powered down with no saved file anywhere: no network path recovers that memory, and the application is rebuilt from drawings, device lists and site records, including the Ethernet channel from the address plan.

Questions asked

Can I just change the 1785-ENET's IP address to fix the visibility?

No. The module's address only becomes useful once the processor application configures the Ethernet channel, and in this fault the module is already answering the network, so the address is not the blocker. Keep the site's custom address plan intact, set it inside the saved application's channel configuration, and download the program through serial DF1 or DH+.

The battery light is red but the panel still has power — is the program already gone?

Not yet. While chassis power stays on, the processor keeps its memory even with a dead or missing battery; the application is lost at the moment power is removed without a healthy battery. Read the actual program state through a working serial DF1 or DH+ path instead of assuming, and install the correct replacement battery before the next shutdown.

Should I swap in a third processor?

Not until the diagnosis says so. Two processors faulting the same way points first at conditions they share: chassis power, connector seating, bent backplane pins, the battery connection, or an empty application state on both. Get a serial path, read the fault, download the saved program, and only replace hardware again if the fault follows the processor instead of the slot.

What if no saved program file exists anywhere?

Then no network path recovers anything, because the memory is already gone if power cycled with a dead battery. The application has to be rebuilt from machine drawings, device lists and site records, with the Ethernet channel recreated from the site address plan. That is why finding and verifying the saved file comes before every other step in the sequence.

Why did the laptop only act up when plugged into wall power?

A laptop running on its battery floats free of the building's supply ground, so the voltage difference between it and the panel, which drives current through the non-isolated serial port, largely disappears; on the charger it returns. Treat battery power as a useful test, not a fix — the permanent answer is an isolated USB-to-serial converter and a verified cable.

Keep reading

  • Troubleshooting

    Why HMI values show question marks: PLC comms timeouts

    Yes — a running PLC program can cause intermittent HMI timeouts by consuming nearly all controller execution time, and clean Ethernet counters do not clear it: utilization measures bytes, not the cost of servicing requests. Work controller load first: Task Monitor above 90% on the dropping units against 7–15% on healthy ones, then message pacing, packet-rebuild address forms, read grouping, and power last.

    PLC programming

  • Troubleshooting

    Why Modbus cannot transfer a PLC ladder program over TCP

    No Modbus address reaches ladder memory: the application protocol defines four data tables — coils, discrete inputs, input registers, holding registers — and program storage is not in any of them. Swapping RTU for TCP changes transport, not protocol. On DirectLogic PLCs the program moves only over K-Sequence or DirectNET through the vendor's programming tools; Modbus stays for mapped user data.

    PLC programming

  • Selection guide

    Choosing PLC to SCADA communication over long distances

    For PLC-to-SCADA communication over long distance, choose the transport by reach and connection behavior: fiber Ethernet for a continuous long link (one span rated 2 km), RS-485 where serial fits, extenders or radio on existing pairs, dial-up or leased-line modems on phone service. Direct copper Ethernet fails at 100 m per segment; the SCADA driver or OPC service, not the PLC's ASCII modem commands, carries the protocol.

    Industrial networks