Troubleshooting
Why an SLC 5/03 stays Default/Faulted after a bad download
Short answer
The corrupted download left no valid application in the processor, so Program/Run cycling cannot recover it and RSLogix will not download while RSLinx still reports Default/Faulted. Remove the battery, short VBB to GND and hold it a full three minutes — a 60-second short failed on this processor and a hold of more than two minutes cleared it — then confirm the state change in RSLinx before reloading the project.
On this page
- What the corrupted download left behind
- Read the LEDs against the chapter 10 table first
- Prove the DF1 path, then leave it alone
- Match what you see to the next decision
- Hold the short three minutes, not sixty
- The memory clear, step by step
- Reload the project
- Verify before you hand control back
- Questions asked
An interrupted download left your SLC 5/03 with no valid application, and that is why nothing you have tried has moved it: switching between Program and Run requests an operating mode, but there is no program left to run, and RSLogix will not download onto a processor that cannot identify itself. The fix is the full memory clear — battery out, VBB shorted to GND — held for a full three minutes rather than the 60 seconds you already tried, then verified in RSLinx before you download again. A 60-second short failed on exactly this fault; a hold of more than two minutes cleared it.
What the corrupted download left behind #
A download writes the project into the processor's battery-backed RAM. Interrupt the transfer and you are left with a partial image: the application no longer checks out as valid, so the processor faults and stays defaulted. The serial side of the firmware keeps answering, which is why RSLinx still browses the device and reports it as Default/Faulted. Visibility and download-readiness are separate tests: your DF1 link is proven, the processor state is not.
So stop cycling the mode switch, reinstalling drivers, and retrying the download. None of those writes a valid image, and every retry into a defaulted processor is another chance to interrupt a transfer.
Read the LEDs against the chapter 10 table first #
Before you clear anything, record the complete front-panel indication: every indicator, and whether each is off, steady, or flashing. Match the whole pattern — not just the flashing fault LED — against the table in chapter 10, Troubleshooting, of publication 1747-UM011, the SLC 500 Modular Hardware Style User Manual. The table splits into two branches:
- A pattern consistent with invalid or empty application memory: continue to the memory clear below.
- A pattern the table identifies as a processor hardware fault: stop. Memory clearing cannot repair it, and that branch ends in processor replacement.
Prove the DF1 path, then leave it alone #
Your setup — a 1747-CP3 serial cable on an RS232 DF1 driver in RSLinx — gives you a clean diagnostic boundary:
- Run auto-configuration on the RS232 DF1 driver.
- If it fails, the fault is the port, cable, driver, or computer interface; fix that before touching processor memory. DF1 behavior is not identical across these families, so if you also work PLC-5 processors, read why DF1 reads work on an SLC 500 but not a PLC-5 before blaming the cable.
- If it succeeds and the browse still reads Default/Faulted, the transport is good. Stop swapping cables and drivers; the processor state is the blocker.
Match what you see to the next decision #
| What you observe | What it proves | Decision |
|---|---|---|
| Fault indication began during an interrupted download | Application memory is incomplete | Take the memory-clear branch |
| Auto-configuration succeeds, browse reads Default/Faulted | The serial path reaches the processor | Clear memory; stop changing drivers |
| RSLogix will not identify the processor | The processor cannot present a valid identity | Fix the state before any download retry |
| The complete LED pattern matches a hardware-fault row | Memory is not the problem | Follow the replacement branch |
| The processor drops out of the browse entirely | The link failed, not the memory | Troubleshoot the serial path first |
That last row is the one exception to the state-first rule: if the processor vanishes from RSLinx rather than showing Default/Faulted, spend your time on a PLC-5 that goes missing in RSLinx after processor replacement, not on a reset.
Hold the short three minutes, not sixty #
The commonly quoted interval for the VBB-to-GND short is 60 seconds. On the processor behind this article, 60 seconds did not complete the clear; repeating the same short held for more than two minutes did. Budget the hold from those numbers:
- Observed bounds: failed at 60 s of contact, succeeded at more than 120 s.
- Minimum hold: 60 s + 60 s margin = 120 s.
- Budgeted hold: 180 s — one clean three-minute attempt instead of two uncertain ones.
The battery-only alternative, removing the battery with no short, also empties memory, but it is quoted at over thirty minutes: 1800 s against the 180 s short, ten times as long. VBB is the battery-backed supply to memory, and the short collapses it; the time to fully lose contents is not guaranteed by the nominal figure, which is where the margin comes from. The acceptance test is the processor state in RSLinx, never the clock.
The memory clear, step by step #
- Put the machine in a safe state and isolate chassis power by your plant's procedure before you open anything — a recovered processor may command outputs at power-up.
- Keep whatever verified copy of the project you have; after this clear, the processor holds nothing.
- Remove the processor battery.
- On the back of the processor, find the terminals marked VBB and GND and confirm the labels against 1747-UM011; never short unidentified points.
- Short VBB to GND with a screwdriver tip and hold solid contact for the full three minutes worked out above.
- Remove the short first, then reinstall the battery and restore power.
- Refresh the RSLinx browse. Cleared means the processor no longer reads Default/Faulted. If it still does after a known-good three-minute contact, stop repeating and go back to the chapter 10 table — a pattern that survives a confirmed clear points at hardware, and that decision is replacement.
Reload the project #
With the processor out of the defaulted state, the download that failed before now has somewhere to land:
- Refresh RSLinx and confirm the processor identifies as an SLC 5/03, not Default/Faulted.
- Open the known-good project file in RSLogix — not the transfer that was in progress when the fault began.
- Start the download and keep processor power and the serial connection undisturbed until the transfer completes.
- Answer any processor-type or compatibility prompt from what RSLinx actually reports, never from memory.
- Touch the mode switch only after the download finishes successfully.
Verify before you hand control back #
- RSLinx identifies the processor as a healthy SLC 5/03.
- RSLogix goes online and the program in the processor matches the file you downloaded.
- The complete LED pattern matches the normal-pattern rows of the chapter 10 table.
- The processor accepts Run mode and the fault indication does not return across a power cycle.
- Field devices behave under the machine's normal commissioning test before you release it to operation.
A successful auto-configuration was never the acceptance test. Recovery is complete only when identity, project, mode, and LEDs all agree.
Questions asked
How long should the VBB-to-GND short be held on an SLC 500?
The commonly quoted interval is 60 seconds, but an SLC 5/03 in exactly this Default/Faulted state did not clear at 60 seconds and did clear with the short held for more than two minutes. Plan a full three minutes of solid contact and accept the clear only when RSLinx stops reporting Default/Faulted. Removing the battery without any short also empties memory, but that method is quoted at over thirty minutes.
Why does RSLinx see the processor when RSLogix will not accept a download?
Auto-configuration and the browse only prove that something at the far end of the DF1 link answers; the communication side of the firmware stays alive even when application memory holds no runnable program. RSLogix needs the processor to identify itself as a healthy SLC 5/03 before it will transfer a project, and a defaulted processor with an incomplete application cannot do that. Clear the state and the RSLogix symptom goes with it.
Would a fault routine in the program have prevented this?
A fault routine can be written to unlatch a recoverable major error and request a reset at power-up, and it is worth configuring after you reload the project. It could not have helped here: the routine is part of the application, and after a corrupted download there is no valid application for the processor to run. Program-based handling covers recoverable errors, never a defaulted processor with empty memory.
What if the processor still reads Default/Faulted after a three-minute clear?
Stop repeating resets and downloads. Recheck the complete LED pattern against the chapter 10 table in publication 1747-UM011. A fault pattern that survives a confirmed memory clear points to processor hardware, and that branch of the table ends in replacement, not another reset. Before condemning it, confirm the short made solid contact on both points and the battery was fully out, because a poor contact is the one remaining procedural suspect.