IMDHMIControls LibraryShop main store

Troubleshooting

PLC-5/80E loses scan list on remote I/O after power cycle

PLC programming Published 5 min read

Short answer

Auto-negotiate selected on Ethernet Channel 2 of a Series F Revision A PLC-5 clears the chassis scan list on the remote I/O scanner channels whenever the processor power cycles. Disable auto-negotiate and hard-set 100 Mbps full duplex, or flash Revision A.1 or newer; Auto-Config only rebuilds the list after each event.

On this page
  1. What the symptoms tell you
  2. The two documented corrections
  3. Read the series, revision and Channel 2 selection
  4. Apply the correction
  5. Verify with a controlled power cycle
  6. When this cause is excluded
  7. The decision, by case
  8. Questions asked

Your PLC-5/80E is losing the chassis scan list on Channels 1A and 1B every time the processor itself power cycles, and the cause is documented: auto-negotiate selected on Ethernet Channel 2 of a Series F Revision A processor. The release notes for the enhanced, protected, Ethernet and ControlNet PLC-5 controllers state that with auto-negotiation selected in the Channel 2 Ethernet configuration, power cycling the controller takes the remote I/O configuration with it. Two corrections are documented: disable auto-negotiate and hard-set Channel 2 to 100 Mbps full duplex, or flash the processor to Revision A.1 or newer. Auto-Config only rebuilds the rack list after the fact; it is a recovery action, and it leaves the trigger armed for the next outage.

What the symptoms tell you #

Four observed symptoms together point at the scan-list clearing and away from the usual suspects:

  • The processor returns online with its program intact, so memory retention is working. Battery or EEPROM failure shows up as program loss, not as intact logic with a missing rack list.
  • The 1771-ASB racks report disconnected and the SCADA raises rack fault alarms, which is the scanner running without its rack list, not adapters failing one by one.
  • Program mode plus Auto-Config restores communication, confirming the list was cleared, because rebuilding that list is exactly what Auto-Config does.
  • The fault follows long outages only, because only those drain the UPS far enough to power-cycle the processor. The racks losing and regaining power is not the trigger; the processor restart is.

The two documented corrections #

A Rockwell Automation knowledge base entry and the PLC-5 release notes give this fault two corrections: disable auto-negotiate on Channel 2, or upgrade the processor to Revision A.1 or newer. The scope is exact, and it is worth stating precisely: the behavior belongs to Series F Revision A processors, it requires auto-negotiation selected in the Channel 2 Ethernet configuration, and the loss hits the remote I/O configuration at a power cycle. If your processor reads Series F Revision A and Channel 2 shows auto-negotiate selected, that is the diagnosis — apply the correction rather than diagnosing further.

Read the series, revision and Channel 2 selection #

Go online and read the processor's series and revision from its status and identification information, then open the Channel 2 Ethernet configuration and note whether the Auto Negotiate selection is checked. The revision decides the branch:

  • Series F, Revision A with auto-negotiate selected: apply the correction below before the next outage, because every processor power cycle will repeat the fault.
  • Revision A.1 or newer, or another series: this cause does not apply as stated. Record the Channel 2 settings and run the controlled power-cycle test before spending time elsewhere.
  • Processor does not appear in the communications driver at all: that is a separate visibility fault, and PLC-5 not visible in RSLinx after processor replacement covers it.

Apply the correction #

One safety note first: a mode change or processor power cycle pulls the machine out of its running logic, so work it under operations authorization with the process in a safe state. Then:

  • Save the project and record the processor revision, the Channel 2 settings, and the scanner channel's scan list as found.
  • Put the processor in Program mode as your change procedure requires and open the Channel 2 Ethernet configuration.
  • Clear the Auto Negotiate selection and set the port to 100 Mbps full duplex, the fixed setting used in the resolution reported for this fault; PLC-5/80E Ethernet duplex configuration covers the channel setup in detail.
  • Set the connected switch port to the same fixed speed and duplex. One fixed end against one negotiating end is a duplex mismatch, which trades a configuration fault for link errors.
  • Apply the change, confirm the processor reports the intended Channel 2 setting, and confirm the scan list is present before returning to Run.
  • Run Auto-Config once, only if the rack list still needs rebuilding from the last event.

Verify with a controlled power cycle #

An illustrative worked example with the arithmetic shown; substitute your own rack count:

  • Before the fix: a PLC-5/80E Series F Revision A, auto-negotiate on Channel 2, 6 racks configured in the scan list. One controlled power cycle leaves the list holding 0 of 6 racks, so 6 − 0 = 6 racks lost, and Auto-Config rebuilds all 6.
  • After the fix: auto-negotiate off, 100 Mbps full duplex at both ends. Three controlled power cycles, and the scan list holds 6 of 6 racks every time: 6 ÷ 6 = 1.00, or 100% retention across 3 restarts.
  • Decision rule: any post-fix cycle that drops the count below the configured rack total fails verification and sends the case to the excluded-cause branch below.

If you took the Revision A.1 upgrade instead, verify the same way: revision readback, one controlled power cycle, scan list populated, racks reconnected without Auto-Config.

When this cause is excluded #

With auto-negotiate already disabled, or a different series and revision in hand, the documented trigger is off the table, so do not expect this correction to change anything. Run the one-cycle test with the scan list recorded before and after:

  • The list clears: the release notes do not cover your case. Capture the series and revision readback, the Channel 2 configuration, and both scan-list states, and open a support case with the vendor against that evidence.
  • The list holds: the processor restart is not the problem. Work the 1771-ASB adapter status, rack power, and the remote I/O cabling, and if outages regularly outlast the UPS hold time, extend that hold time so the processor stops restarting at all.

The decision, by case #

  • Series F Revision A with auto-negotiate on Channel 2: disable auto-negotiate, fix 100 Mbps full duplex at both ends, verify with one controlled power cycle.
  • Firmware change preferred: flash Revision A.1 or newer and verify the same way.
  • Auto-negotiate already off, or another series or revision: this cause excluded; run the one-cycle test, then either a support case with the captured evidence or adapter, power, and cabling diagnostics.

With the correction in place, a drained UPS restarts the processor and the scan list survives it, which turns a night call-out into a log entry.

Questions asked

Does a weak processor battery cause this scan list loss?

No. A failed retention battery shows up as program or data loss after the power cycle, and this processor comes back with its logic intact — only the chassis scan list is gone. The cause is the Channel 2 auto-negotiate condition on Series F Revision A. Keep the battery on its replacement schedule anyway, because the next symptom it causes will be real program loss.

Can auto-negotiate stay enabled if we upgrade to Revision A.1?

Yes. Revision A.1 and newer are documented as correcting the scan-list clearing, so auto-negotiate on Channel 2 may remain selected. After the firmware change, run one controlled power cycle with the scan list recorded before and after, and confirm the 1771-ASB racks reconnect without Auto-Config before you call it fixed.

The scan list still clears with auto-negotiate disabled. What next?

Then the documented trigger is excluded. Capture the series and revision readback, the Channel 2 configuration, and the scan-list state before and after one controlled power cycle, and open a support case with that evidence. Also confirm what the processor loads at power-up: if a memory module restores the project on restart, its stored scan list must match the running one, or every restart quietly reverts it.

Why do short outages raise rack alarms but leave no lasting fault?

Because the processor stays up on the UPS and keeps its scan list. The racks dropping offline raise rack fault alarms while power is absent, but they rejoin automatically when it returns, with no Auto-Config needed. Only an outage long enough to drain the UPS and restart the processor clears the list, and that difference tells you which event you just had.

Keep reading

  • How-to

    Remote I/O commissioning checklist for a modular station

    Commission a modular remote I/O station in this order: match the coupler's protocol and addressing to the controller interface, budget and verify station power, seat modules and connectors against the drawing, then prove cyclic data exchange and every field signal before enabling outputs. A loading web page and lit status LEDs prove the coupler is alive; only a value that changes at the controller proves valid I/O data.

    Controllers and I/O

  • Troubleshooting

    PLC-5 not visible in RSLinx after processor replacement

    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.

    PLC programming

  • How-to

    PLC-5 heartbeat without the PLC-5 sending messages

    Let the ControlLogix do all the sending: it either writes an incrementing heartbeat word to the PLC-5 over Ethernet MSG or pulses a spare output into a spare PLC-5 input, and the PLC-5 resets a watchdog timer only on a genuinely new value or pulse edge — never on message-complete status. Set the preset above two update periods plus measured transfer delay; in the worked example, 1500 ms detects a dead link within 1.5 s.

    PLC programming