- What This Cheat Sheet Covers (and What It Doesn't)
- Exam Snapshot: Verified Facts at a Glance
- The Seven Objectives on One Page
- Status Indicators, Inputs and Outputs
- Power Distribution and Processor Faults
- Troubleshooting Discrete I/O Systems
- Multi-Step Sequence Programs: Build and Debug
- Building Your Own Notes Page
- A Domain-Ordered Review Plan
- Quick Answers
- C-208 is Programmable Controller Troubleshooting 1, issued by SACA, with seven competency objectives numbered 208.1 through 208.7.
- Objectives 208.6 and 208.7 cover multi-step sequence programming and troubleshooting; outlines that stop at 208.5 are incomplete.
- The seven objectives are unweighted; no official percentage blueprint exists, so study all seven evenly.
- Silver is a proctored online written test; Gold adds an observed hands-on assessment on approved equipment.
What This Cheat Sheet Covers (and What It Doesn't)
This page condenses what candidates need to remember about Programmable Controller Troubleshooting 1 (C-208), a credential from the Smart Automation Certification Alliance (SACA). It is built around the seven competency objectives in the SACA skill standard for the Certified Industry 4.0 Automation Specialist I core micro-credential. If you want the long-form version of each area, the C-208 exam domains guide goes deeper, and the C-208 study guide lays out a full preparation path.
A cheat sheet is only useful if it is honest about what is known. Several details people ask about, such as the exact number of written questions and the exam timer, were not verifiable from the issuer material, so this page does not state them. Where a rule varies by testing center, that is flagged rather than guessed.
Exam Snapshot: Verified Facts at a Glance
Use this table as the top half of your one-page review. Every entry comes from SACA's published skill standard or from a named testing center's published rules.
| Item | What is verified |
|---|---|
| Credential | Programmable Controller Troubleshooting 1 (C-208), SACA |
| Number of objectives | Seven (208.1 through 208.7) |
| Weighting | Unweighted competency objectives; no published percentage blueprint |
| Silver delivery | Proctored online written test through the SACA portal |
| Gold requirement | Silver plus an observed hands-on assessment on approved equipment |
| Example Silver fee | $139 per test at Central Pennsylvania Institute of Science and Technology (local listing) |
| Example Gold fee | $175 per test at the same institute (local listing) |
| Example Silver threshold | 70% at CNM (center-specific) |
| Written question count and timer | Not verified; check with your testing center |
| Renewal interval | No universal interval asserted |
The fees above are local examples, not national prices. SACA membership benefits can provide certification access for eligible enrolled students and member-company employees, which is separate from training tuition. For a fuller money breakdown, see the C-208 certification cost guide, and for score questions, the C-208 passing score article.
The Seven Objectives on One Page
Memorize this list first. Everything else in the exam hangs off these seven lines.
- 208.1: Use status and diagnostic indicators to troubleshoot a PLC
- 208.2: Troubleshoot PLC inputs and outputs
- 208.3: Troubleshoot PLC power distribution system
- 208.4: Troubleshoot a PLC processor
- 208.5: Troubleshoot a PLC system with discrete I/O
- 208.6: Program and operate a multi-step PLC sequence program
- 208.7: Troubleshoot a multi-step PLC sequence program
Notice the shape of the list. The first five are classic hardware-side diagnosis: indicators, I/O, power, processor, and the combined discrete system. The last two shift to program logic, first writing and running a sequence, then finding faults in one. Candidates who prepare only for the hardware side leave the final two objectives exposed.
Key Takeaway
Because the objectives are unweighted, there is no safe domain to skip. Treat the sequence-program objectives (208.6 and 208.7) with the same seriousness as the hardware objectives, and read the C-208 difficulty guide to see where candidates tend to struggle.
Status Indicators, Inputs and Outputs
Domain 1: Use status and diagnostic indicators to troubleshoot a PLC
Reading the controller before touching anything
The fastest troubleshooting starts with what the controller is already telling you.
- Know the typical meaning of power, run/mode, fault, and communication indicators and what a steady versus flashing state suggests.
- Distinguish a processor fault indication from an I/O module fault indication.
- Use diagnostic information to decide which subsystem to investigate first, rather than swapping parts at random.
- Remember that exact indicator behavior is manufacturer-specific, so read the controller's documentation for the colors and patterns it uses.
Domain 2: Troubleshoot PLC inputs and outputs
Field devices, wiring and module channels
Most real-world faults live at the boundary between the controller and the machine.
- Verify an input three ways: the field device state, the module's channel indicator, and the program's input status.
- Verify an output in reverse: program logic commands it, the channel indicator lights, and the load actually responds.
- Separate a dead field device from a failed module channel by checking voltage at the terminal.
- Recognize sinking versus sourcing arrangements and why mismatched wiring produces an input that never changes state.
The recurring skill here is isolation. A good answer on this kind of question narrows the fault to one segment of the signal path: sensor, wiring, terminal, module, or program.
Power Distribution and Processor Faults
Domain 3: Troubleshoot PLC power distribution system
Following power from source to controller
Many apparent controller faults are really supply problems.
- Trace power from the incoming supply through protective devices to the power supply module and onward to the I/O.
- Know the difference between AC line power to the controller and the DC supply used for field devices and I/O.
- Measure rather than assume: confirm voltage at each stage with a meter, observing safe work practices and lockout procedures.
- Recognize that tripped breakers, blown fuses, loose terminations and a failing power supply produce different symptom patterns.
Domain 4: Troubleshoot a PLC processor
Processor state, memory and communication
When indicators point at the processor, the questions turn to mode and program state.
- Understand run, program and fault conditions and what each implies for outputs.
- Know that a processor fault can come from program errors, memory problems, or hardware, and that the fault code or diagnostic display narrows the cause.
- Recognize when a battery, memory backup, or communication link is the likely culprit.
- Be able to explain the safe sequence for clearing a fault: understand the cause before resetting.
Troubleshooting Discrete I/O Systems
Domain 5: Troubleshoot a PLC system with discrete I/O
This objective pulls the previous four together. Instead of asking about one subsystem, scenarios describe a system symptom, such as a machine that will not start or an output that never energizes, and expect you to pick a logical diagnostic order.
A repeatable diagnostic order
A dependable pattern for system-level symptoms:
- Check the obvious first: power, mode, and any fault indicators.
- Confirm the status of the relevant input and output in the program and at the module.
- Test the field device and its wiring with the meter.
- Only then suspect the module or processor.
- Document what you changed so the fix can be repeated or reversed.
Discrete devices are the on/off kind: pushbuttons, limit switches, proximity sensors, solenoids, motor starters and indicator lamps. Be comfortable with how each presents itself to the controller and what a typical failure of each looks like.
Multi-Step Sequence Programs: Build and Debug
Domain 6: Program and operate a multi-step PLC sequence program
Writing logic that advances step by step
A sequence runs through ordered steps, each starting only when the previous one is complete.
- Define each step by its action, its completion condition, and the transition to the next step.
- Use latching or step-bit techniques so only one step is active at a time.
- Include start, stop and reset conditions so the sequence can be operated and returned to a known state.
- Be able to download, place the controller in run, and observe the sequence operating as intended.
Domain 7: Troubleshoot a multi-step PLC sequence program
Finding why a sequence stalls or misbehaves
Debugging a sequence means working out which step is active and why it will not advance.
- Monitor online to identify the active step and the condition holding it.
- Check whether a required input, timer, or counter condition is never satisfied.
- Look for logic errors such as steps that can activate simultaneously or a missing reset that traps the sequence.
- Distinguish a program fault from a field-device fault by comparing the commanded state with the real-world result.
This pair of objectives is where the Gold hands-on assessment feels most direct, since you are working on approved equipment. If you plan to pursue Gold, the C-208 training overview covers how hands-on preparation typically fits in.
Building Your Own Notes Page
Some testing centers allow a notes sheet. CNM, for example, publishes that candidates may bring up to five pages of prewritten notes and formulas, usable on both sides, which must be surrendered to the proctor, and that a scientific calculator is allowed. That is one center's policy, not a universal C-208 rule, so ask your own center before you prepare anything.
If notes are permitted, spend the space on what you will actually forget under pressure:
- Ohm's law and basic power relationships for voltage-drop and load checks
- A one-line diagnostic order for system-level faults
- Input and output verification chains, written as short arrow sequences
- The seven objective titles, so you can tag each practice question to a domain
- Sink/source wiring reminders and typical indicator meanings for your controller family
Key Takeaway
Do not copy definitions into your notes. Write the decision paths: "input not changing, so check device, then terminal voltage, then channel indicator, then program." Decision paths transfer to unfamiliar scenarios; definitions do not. Checking your eligibility and requirements and local policies before exam day prevents surprises.
A Domain-Ordered Review Plan
One short plan, ordered by how the objectives build on each other rather than by generic study theory. Adjust the pacing to your scheduled test date; see the C-208 exam dates article for scheduling mechanics.
Indicators, inputs and outputs (208.1, 208.2)
- Learn indicator meanings and the three-way input and output verification chains.
- Practice isolating a fault along the signal path.
Power and processor (208.3, 208.4)
- Trace power from source to I/O and practice meter-based checks.
- Review processor modes and fault-clearing logic.
Discrete systems (208.5)
- Run through system-level symptom scenarios using one fixed diagnostic order.
Sequence programs (208.6, 208.7)
- Build and debug a multi-step sequence, then rehearse a mixed practice round with questions tagged by objective.
Finish with timed practice. The C-208 practice tests let you drill mixed questions across all seven objectives so you can see which areas still need attention.
Quick Answers
C-208 is Programmable Controller Troubleshooting 1 from SACA. It spans seven objectives: indicators, inputs and outputs, power distribution, the processor, discrete I/O systems, building a multi-step sequence program, and troubleshooting one. For definitions and background, see What Is C-208?
No percentage weighting is published. The objectives are unweighted competency statements, so plan to cover all seven rather than concentrating on a few.
Silver is a proctored online written test taken through the SACA portal. Gold requires Silver plus an observed hands-on assessment on approved equipment.
There is no verified national price. One institute lists $139 per Silver test and $175 per Gold test, but those are local examples. SACA membership benefits may cover access for eligible students and member-company employees. Confirm with your testing center.
It depends on the center. CNM publishes a 70% Silver threshold, at least seven days between attempts, and up to five attempts per term, while another provider lists retake eligibility after 24 hours. Ask your center which policy applies to you.
No universal renewal interval has been verified, so do not assume one. Confirm validity details with SACA or your testing center. For career context, see the C-208 jobs overview.