C-309 logo
Focused certification exam prep
Start practice

C-309 Study Guide 2026: How to Pass on Your First Attempt

TL;DR
  • Programmable Controller Systems 2 (C-309) is issued by the Smart Automation Certification Alliance (SACA) and centers on analog PLC logic, program control...
  • Six preparation objectives map to Domains 1-6; none carries a published weight, so study all six rather than gambling on one.
  • Silver is a proctored online written exam; Gold adds an observed hands-on assessment on SACA-approved equipment.
  • Exact question count, time limit, retail fee and pass mark were not verified, so confirm them with your testing center.

What Programmable Controller Systems 2 (C-309) Actually Covers

Programmable Controller Systems 2 (C-309) is a SACA micro-credential built around the second layer of PLC skill: moving beyond basic discrete ladder logic into analog signals, program flow control, modular code and operator interfaces. If you can already latch a motor circuit and build a timer-based sequence, this is the credential that asks whether you can handle a 4-20 mA level transmitter, restructure a program with subroutines, and give an operator a screen that tells the truth about the machine.

If you are still orienting yourself, our explainer What Is C-309 Certification? covers the basics, and the C-309 exam domains guide goes deeper on each content area. This article is the study plan: how to sequence the six objectives, what to practice by hand, and where candidates lose points.

The six objectives at a glance

DomainFocusSkill type
Domain 1Program and operate a PLC logic program that uses analog instructionsProgramming
Domain 2Troubleshoot a PLC program application that uses analog I/ODiagnostics
Domain 3Program and operate a PLC logic program that uses program control instructionsProgramming
Domain 4Program and operate a PLC logic program that uses subroutine instructionsProgramming
Domain 5Program and operate an HMI project that uses objects to interact with a PLCHMI development
Domain 6Program and operate an HMI project that uses information, diagnostic and alarm messagesHMI development

Notice the verbs: program, operate, troubleshoot. This is an applied credential. Memorizing instruction mnemonics will not carry you; you need to understand what each instruction does to data and to scan behavior.

A Note on Scope and What We Could Not Verify

Honesty matters in exam prep, so here is where our research stands. The six domains above come from credential-coded preparation objectives (309.01 through 309.06) published in provider course documents, including a PLC II course form and an HMI course form from a community college program. These documents reproduce the C-309 preparation standards, but they do not prove which exam version SACA is administering today. We treat the six objectives as a reliable study map, not as a guaranteed exhaustive blueprint.

There is also a documented scope conflict. Some SACA announcements and an occupational database entry describe Ethernet communications in connection with this credential code, which differs from the analog/PLC/HMI scope in the preparation objectives. We have not blended those descriptions together. If your testing center's candidate guide mentions Ethernet topics, take that seriously and add them to your plan; if it matches the six objectives here, you are covered.

Verify before you commit: Ask your testing center or instructor for the current candidate guide before you schedule. A short email now prevents spending weeks on the wrong content. Ethernet communications is the one topic area where sources disagree.

Format, Delivery and Registration Mechanics

What we can say with confidence about delivery:

  • Silver level: a proctored online written exam delivered through the SACA portal at participating centers.
  • Gold level: requires Silver first, then an observed hands-on assessment using SACA-approved equipment.
  • Access routes: SACA education and industry membership benefits can provide certification access for eligible enrolled students and for employees of member companies. These are separate from tuition, equipment charges or local center fees.

What we could not verify: the exact number of written questions, the time limit, the individual retail exam fee, and any universal pass mark, retake policy or renewal rule. Course hours and practical-assessment durations you may see in college catalogs are not a written-exam timer, so do not treat them as one. For the money side, see our C-309 certification cost breakdown; for scoring, read what is known about the passing score; and for scheduling, check testing windows and deadlines.

Prerequisites: what is and is not required

Do not assume a universal admission gate. College courses carry their own prerequisites, and a published degree-pathway example places earlier PLC coursework ahead of this material, but that is a local sequencing choice, not a verified issuer-wide rule. Practically, though, you should arrive fluent in basic ladder logic, I/O addressing and bit-level instructions. Our requirements guide untangles what is mandatory from what is merely sensible.

Analog Instructions and Analog Troubleshooting (Domains 1-2)

Analog work is the conceptual leap of this credential. Discrete logic asks whether something is on or off. Analog logic asks how much, and the PLC has to translate a real-world signal into a number it can compare, scale and act on.

Domain 1: Analog Instructions

You must be able to write a program that reads, converts and uses analog values to make control decisions.

  • Understand how an analog input module converts a current or voltage signal into raw integer counts.
  • Scale raw counts to engineering units (such as degrees, PSI or percent level) using scale or compute instructions.
  • Use comparison instructions with scaled values to set thresholds and trigger outputs.
  • Write values back out through analog output channels, respecting range limits.
  • Know the difference between data types, since integer versus floating-point math changes your results.

Domain 2: Troubleshooting Analog I/O

This is the diagnostic twin of Domain 1. Given a misbehaving program, you must isolate whether the fault is in the field device, the wiring, the module configuration or the logic.

  • Recognize the signature of a live-zero signal versus a lost one, and why 4-20 mA signaling aids fault detection.
  • Check scaling endpoints when a reading is proportionally wrong but not dead.
  • Distinguish a wrong module range setting from a wiring fault from a logic error.
  • Use online monitoring to watch raw and scaled values side by side.

The most common failure pattern here is scaling arithmetic. Candidates know the formula but mix up raw minimum and maximum against engineering minimum and maximum, or ignore the integer-division trap that flattens a result to zero. Work through at least a dozen scaling problems by hand, checking your answer at the endpoints (minimum should produce minimum, maximum should produce maximum) and at the midpoint.

Endpoint check: After scaling any analog value, test it at 0%, 50% and 100% of the input range. If all three come out right, your slope and offset are almost certainly right. If the midpoint is off, you likely have an offset or integer-math problem.

Program Control and Subroutines (Domains 3-4)

Domains 3 and 4 shift from signal handling to program architecture. This is where you learn that a PLC does not run top to bottom and stop; it scans repeatedly, and you can deliberately steer which parts of the program execute and when.

Domain 3: Program Control Instructions

Program control instructions alter normal scan flow. Candidates need to know what each does, when to use it and what can go wrong.

  • Instructions that jump over sections of logic and the labels they target.
  • Master control-style instructions that enable or disable a block of rungs, and what happens to outputs inside a de-energized zone.
  • Temporary end or similar flow-stopping instructions used during testing.
  • How skipped or disabled logic affects timers, latches and retained states.

Domain 4: Subroutine Instructions

Subroutines let you break a large program into callable, reusable units.

  • Create a subroutine file and call it from the main routine with a jump-to-subroutine instruction.
  • Understand return behavior and how control passes back to the calling rung.
  • Pass parameters, where the platform supports it, versus relying on shared data tables.
  • Recognize good uses: repeated analog scaling, alarm handling, machine-mode logic.

A particularly testable idea: a subroutine that is not called does not execute, so any output last set inside it stays frozen in its last state. Candidates who forget this misdiagnose "stuck" outputs. Practice predicting what a program does on the scan after a jump or a subroutine call is skipped.

Platform note: instruction names differ across PLC brands. Learn the concept first, then map it to the controller you train on. Questions are more likely to test the behavior than a vendor-specific mnemonic, but confirm with your candidate guide.

HMI Objects and Messages (Domains 5-6)

The final two domains move to the operator's side of the machine. An HMI project is only useful if the objects on screen are tied to the right PLC tags and if the messages it displays help people act correctly.

Domain 5: HMI Objects That Interact with a PLC

Build and operate screens whose objects read from and write to controller data.

  • Create the communication link between the HMI project and the PLC and map tags correctly.
  • Use objects such as pushbuttons, indicators, numeric displays, numeric entry and bar-style graphics.
  • Match object behavior to tag data type: bit tags for lights and buttons, numeric tags for setpoints and readouts.
  • Navigate between screens and keep the interface consistent and readable.

Domain 6: Information, Diagnostic and Alarm Messages

Messages are where the HMI earns its keep during a fault.

  • Distinguish information messages (status), diagnostic messages (why something is stopped) and alarm messages (something needs attention now).
  • Trigger messages from PLC bits or analog thresholds.
  • Write messages that name the condition, location and likely action, not just "Fault 12."
  • Understand acknowledgment and how alarm state is displayed and cleared.

Here the analog and HMI halves of the credential meet. A high-level alarm on a tank, for example, starts with a scaled analog value in the PLC (Domain 1), compares it to a limit, sets a bit, and that bit triggers an alarm message on the HMI (Domain 6). If you rehearse that complete chain once, you will see how the six domains connect rather than treating them as isolated topics.

Key Takeaway

Build one small end-to-end project: an analog level input, scaled to engineering units, compared against high and low limits inside a subroutine, with an HMI display and an alarm message. It exercises all six domains at once.

A Domain-Ordered Study Sequence

Because no domain carries a published weight, the safest approach is balanced coverage, ordered by dependency. Analog comes first because the later domains reuse it, and HMI comes last because it displays what the PLC logic produces. Adjust the timeline to your own schedule; this is a six-week pattern.

Week 1

Analog fundamentals (Domain 1)

  • Review how analog modules convert signals to counts.
  • Do scaling problems by hand, checking endpoints and midpoint.
  • Program a simple scaled-input comparison in a simulator.
Week 2

Analog troubleshooting (Domain 2)

  • Practice isolating faults: field device, wiring, module range or logic.
  • Intentionally break your Week 1 program and diagnose it.
  • Watch raw versus scaled values online.
Week 3

Program control (Domain 3)

  • Write jump and master-control-style logic.
  • Predict output states inside skipped or disabled zones before running the code.
Week 4

Subroutines (Domain 4)

  • Move your analog scaling into a subroutine and call it repeatedly.
  • Test what happens to outputs when the subroutine is not called.
Week 5

HMI objects and messages (Domains 5-6)

  • Tag-link buttons, indicators and numeric displays to your program.
  • Add information, diagnostic and alarm messages tied to PLC bits.
Week 6

Integration and review

  • Run full-length practice questions across all six domains.
  • Revisit your weakest domain and rebuild one project from scratch.

If your schedule is tight, compress by merging Weeks 3 and 4, but protect the analog weeks. For a one-page refresher near test day, see the C-309 cheat sheet, and for a broader view of the overall plan, our main C-309 study guide is the hub for this series.

Building Hands-On Proof Before Test Day

The Silver written exam tests whether you understand the concepts; the Gold assessment tests whether you can do the work on SACA-approved equipment while someone watches. Even if you only plan to sit Silver, hands-on practice is the fastest way to make the written material stick, because analog scaling, scan behavior and tag mapping are far easier to remember once you have watched them misbehave on a real or simulated controller.

What to practice with

  • Simulator or emulator software for your PLC platform, which lets you force analog values and watch results without hardware.
  • HMI development software that can connect to a simulated or physical controller.
  • Training equipment at your college or training center, which is also where Gold assessments typically take place.

Mistakes that cost the most points

  1. Scaling with swapped min/max values, producing a reversed or offset reading.
  2. Forgetting integer math truncation when dividing before multiplying.
  3. Assuming outputs reset when a subroutine or skipped zone stops executing.
  4. Mapping an HMI object to the wrong tag type, such as a numeric display tied to a bit.
  5. Writing alarm messages that describe a symptom but give the operator no next step.
Think like a technician: Many questions are scenario-based. A tank reads full when it is empty, an HMI light never turns on, an output stays on after a routine stops. Train yourself to ask "where in the signal chain could this fail?" before choosing an answer.

To find out how well you retain this material under question pressure, run timed sets on our C-309 practice test site and note which domain your misses cluster in. Then go back to the matching week above and rebuild that project.

Where the Credential Fits in the Job Market

The skills tested here map to roles in manufacturing and process environments: maintenance technicians, controls and automation technicians, PLC programmers and technicians supporting packaging, materials handling, water treatment or discrete assembly lines. Employers in these settings value someone who can read an analog loop, trace a fault and update an operator screen, not just reload a program.

The credential is also commonly encountered through college and training-center programs and through SACA member companies that use it to document skills for their workforce. We do not cite specific salary or pass-rate figures here because we could not verify them; for the discussion of earnings, see the salary guide, for roles, read C-309 jobs, and for an honest weighing of cost against payoff, the ROI analysis is worth a read. If you are wondering about difficulty, how hard the C-309 exam is addresses that directly.

Frequently Asked Questions

Who issues Programmable Controller Systems 2 (C-309)?

The Smart Automation Certification Alliance (SACA). It is delivered as a micro-credential, with a proctored online written Silver level and a Gold level that adds an observed hands-on assessment on SACA-approved equipment.

What topics should I study first?

Start with analog instructions (Domain 1) and analog troubleshooting (Domain 2). Later domains reuse scaled analog values in program control, subroutines and HMI alarms, so weak analog fundamentals create problems throughout the rest of your preparation.

How many questions are on the exam and how long is it?

We could not verify the written question count or time limit, and course hours listed by colleges are not an exam timer. Confirm both with your SACA testing center before you schedule or plan a timed practice session.

Do I need prior coursework before sitting for it?

No universal issuer-wide prerequisite was verified. College courses set their own prerequisites, and a published degree pathway places earlier PLC courses first, but you should still be comfortable with ladder logic and I/O basics beforehand.

Does the exam cover Ethernet communications?

The preparation objectives we reviewed cover analog, program control, subroutines and HMI, not Ethernet. Some SACA announcements and an occupational database entry describe Ethernet for this code, so check your candidate guide and treat Ethernet as a possible add-on topic until confirmed.

With the six domains mapped, a dependency-ordered plan and one integrated project under your belt, you will have prepared the way the credential itself is designed: by doing the work, not just reading about it. Pair that with timed question practice on the main practice test page, and you will know exactly where you stand before exam day.

Ready to pass your C-309 exam?

Put this into practice with free C-309 questions across every exam domain.