Pro
12 min

Fault 07 — Counter Overflow

fault-injectioncounteroverflow
Fault 07 — Counter Overflow scenario preview

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 parts-counting batch system runs the first batch correctly but locks up after that — subsequent BATCH_START commands have no effect. Use the Variables tab to watch the counter state across batches.

Objectives

  • Use the Variables tab to watch C_PARTS.CV and C_PARTS.Q
  • Count a full batch of 10 parts and observe the counter state
  • Identify the missing counter reset logic
  • Add a reset rung and verify subsequent batches work correctly

Hints

  • Open the Variables tab and monitor C_PARTS.CV
  • After 10 parts, watch C_PARTS.Q — does it ever go false again?
  • A CTU needs its R input to go true to reset CV back to 0

I/O Table

Inputs

BATCH_START

Start new batch command

BOOL · %I0.0

PART_SENSOR

Part-detected sensor

BOOL · %I0.1

Outputs

BATCH_DONE

Batch complete output

BOOL · %Q0.0

BATCH_ACTIVE

Batch in progress 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. #1BATCH_DONE fires after 10 parts

    Count 10 parts — BATCH_DONE should go true

  2. #2Second batch can be started after first completes

    After first batch, BATCH_START restarts the counter

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