Pro
10 min
CCST 29 — Drive Fault / Alarm Handling
ccstmotiondrivefaultalarm
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
Briefing
A drive faults (DRIVE_FAULT input) — shut down DRIVE_RUN immediately, latch FAULT_ALARM, and wait for FAULT_ACK to clear it before allowing a restart.
Objectives
- DRIVE_RUN drops immediately on DRIVE_FAULT
- FAULT_ALARM latches and only clears on FAULT_ACK
- Motor cannot restart until FAULT_ALARM is cleared
Hints
- FAULT_ALARM latches SET on DRIVE_FAULT, RST on FAULT_ACK
- DRIVE_RUN := DRIVE_CMD AND NOT FAULT_ALARM
I/O Table
Inputs
DRIVE_CMDDrive run command
BOOL · %I0.0
DRIVE_FAULTDrive fault signal
BOOL · %I0.1
FAULT_ACKFault acknowledge
BOOL · %I0.2
Outputs
DRIVE_RUNDrive run output
BOOL · %Q0.0
FAULT_ALARMFault alarm output
BOOL · %Q0.1
Your program will be tested against:
All test cases run automatically when you submit. Assertions are hidden until you pass.
- #1Drive runs on cmd
Drive runs on cmd
- #2Drive drops on fault
Drive drops on fault
- #3Clears on ACK
Clears on ACK
Related scenarios
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