Pro
12 min
CCST 16 — Forced I/O and Override Risks
ccstdiagnosticsforceI/Ostuck
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
Understand how I/O forcing works: you will force %I0.0 TRUE to simulate a stuck sensor and observe downstream effect. Then remove the force and verify normal operation.
Objectives
- Identify a sensor that is stuck TRUE in the Variables tab
- Determine the downstream output that is incorrectly energised
- Describe how to safely remove an I/O force
Hints
- Forced I/Os are marked with an F in Allen-Bradley; in this simulator use the Variables tab
- Removing a force on an input allows the real field value to take over
I/O Table
Inputs
LEVEL_SENSORLevel sensor (stuck HIGH)
BOOL · %I0.0
Outputs
FILL_VALVEFill valve output
BOOL · %Q0.0
Your program will be tested against:
All test cases run automatically when you submit. Assertions are hidden until you pass.
- #1Fill valve off when level high
Fill valve off when level high
- #2Fill valve on when level low
Fill valve on when level low
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