Pro
10 min

CCST 21 — E-Stop Circuit Basics

ccstsafetyestopfault-latch

Ready to build this?

Sign up free — no credit card required. This scenario requires the Pro plan.

Sign up to play this scenario →

Already have an account? Log in

CCST 21 — E-Stop Circuit Basics scenario preview

Briefing

Implement a standard E-stop circuit: pressing ESTOP_PB immediately drops MOTOR_CONTACTOR and latches ESTOP_FAULT. Only after ESTOP_PB is released AND RESET_PB pressed does the fault clear.

Objectives

  • MOTOR_CONTACTOR drops immediately on ESTOP_PB
  • ESTOP_FAULT latches until reset
  • RESET_PB only clears fault when ESTOP_PB is released

Hints

  • Latch ESTOP_FAULT with SET on ESTOP_PB
  • Clear only when NOT ESTOP_PB AND RESET_PB
  • MOTOR_CONTACTOR := (START_PB OR MOTOR_CONTACTOR) AND NOT STOP_PB AND NOT ESTOP_FAULT

I/O Table

Inputs

START_PB

Start

BOOL · %I0.0

STOP_PB

Stop

BOOL · %I0.1

ESTOP_PB

E-stop (NC, asserted=tripped)

BOOL · %I0.2

RESET_PB

Reset

BOOL · %I0.3

Outputs

MOTOR_CONTACTOR

Motor

BOOL · %Q0.0

ESTOP_FAULT

E-stop fault lamp

BOOL · %Q0.1

Your program will be tested against:

All test cases run automatically when you submit. Assertions are hidden until you pass.

  1. #1Motor drops on E-stop

    Motor drops on E-stop

  2. #2Fault stays after E-stop released

    Fault stays after E-stop released

Ready to build this?

Sign up free — no credit card required. This scenario requires the Pro plan.

Sign up to play this scenario →

Already have an account? Log in

Job-readiness and assessment field guide

CCST practical 021 assessment: readiness checklist

Direct answer

The candidate can verify identity and range, stimulate one approved boundary, trace indication and command paths and document restoration.

Written for controls candidates practicing a point-to-point loop check with safe scope, predicted states and reviewable acceptance evidence.

a controls technician completing a supervised practical assessment on generic PLC, motor-control and instrumentation equipment while studying controls loop-check planning, I/O evidence and documented restoration
System map / 02

NODE 01observable

Role scope

Loop identity, drawing revision, safe state, field device, range and unit, I/O channel, controller tag, display, output effect and acceptance signature.

NODE 02observable

Skills map

Approved stimulus through sensor or contact, wiring, I/O, controller value, HMI indication, optional output command, final response and retained record.

NODE 03observable

Core exercise

Known low, normal and high or open and closed states agree at each declared boundary with correct identity and quality.

NODE 04observable

Stretch case

Wrong tag, crossed pair, reversed range, stale display, forced value, output inhibit, communication loss, restart and incomplete restoration.

NODE 05observable

Troubleshooting

An identity, device, wiring, channel, configuration, tag, display, command, feedback or documentation mismatch.

NODE 06observable

Portfolio evidence

The loop returned to service and signed under current site procedure, drawings and certification objectives.

Answer surface / 07

What is the purpose of a loop check?

It proves the complete installed path and identity from an approved field stimulus through wiring, I/O, controller and display or final response before operation.

What must be restored after a loop check?

Remove simulators and forces, restore wiring and configuration, confirm normal mode and quality, repeat required functional checks and document exceptions.