Basic
20 min

Light Curtain Muting Logic Simulation

safetymutinglight-curtaintimingfault-latch

Ready to build this?

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

Sign up to play this scenario →

Already have an account? Log in

Light Curtain Muting Logic Simulation scenario preview

Briefing

This training simulation demonstrates the observable sequence and timing concepts used by one example of two-sensor light-curtain muting. It is not a safety function or deployable machine-safety program. On real equipment, muting must be configured in a safety-rated controller or device using the manufacturer-approved sensor arrangement, required sequence, timing and maximum mute duration, discrepancy and fault monitoring, guarded reset, and validation derived from the machine risk assessment. Here, LIGHT_CURTAIN_OK, MUTE_A and MUTE_B let you study expected behaviour: A then B within 2 seconds creates the simulated mute window; simultaneous, reversed, or late activation creates a simulated fault.

Objectives

  • MACHINE_ENABLE is on while LIGHT_CURTAIN_OK is true and no fault is latched
  • Beam break (LIGHT_CURTAIN_OK = false) without valid muting → latch SAFETY_FAULT_LATCH
  • Valid mute: MUTE_A then MUTE_B, ≥50 ms apart, within 2 s — MUTE_LAMP asserts during the muted window
  • MUTE_LAMP stays on as long as both mute sensors are active and the sequence was valid
  • Invalid mute (simultaneous, reversed, or timeout) → latch SAFETY_FAULT_LATCH
  • RESET_PB clears SAFETY_FAULT_LATCH only when LIGHT_CURTAIN_OK is true and no mute is active
  • Treat every output as a training signal only; a safety-rated device must control real safety outputs and final elements after risk assessment and validation

Hints

  • Use R_TRIG on MUTE_A to detect its rising edge; latch MUTE_A_BIT
  • Start a TON (2 s) on MUTE_A rising edge — if it expires before MUTE_B asserts, fault
  • Check MUTE_A_BIT AND NOT MUTE_B_PREV on MUTE_B rising edge for reverse-order guard
  • MUTE_VALID := MUTE_A_BIT AND MUTE_B (both asserted, valid sequence)
  • MACHINE_ENABLE := LIGHT_CURTAIN_OK AND /SAFETY_FAULT_LATCH; or bypass OK when MUTE_VALID

I/O Table

Inputs

LIGHT_CURTAIN_OK

Light curtain OK (true = clear, false = blocked)

BOOL · %I0.0

MUTE_A

Mute sensor A (first in sequence)

BOOL · %I0.1

MUTE_B

Mute sensor B (second in sequence, within 2 s)

BOOL · %I0.2

START_PB

Machine start push-button

BOOL · %I0.3

RESET_PB

Fault reset push-button

BOOL · %I0.4

Outputs

MACHINE_ENABLE

Machine run enable output

BOOL · %Q0.0

SAFETY_FAULT_LATCH

Safety fault (latching)

BOOL · %Q0.1

MUTE_LAMP

Mute active indicator lamp

BOOL · %Q0.2

Your program will be tested against:

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

  1. #1Machine enables when curtain OK and started

    With LC clear and START_PB, MACHINE_ENABLE asserts and no fault

  2. #2Beam break without muting latches SAFETY_FAULT_LATCH

    LC blocked with no valid mute → fault latches; releasing LC does not clear

  3. #3Valid mute sequence allows curtain block without fault

    MUTE_A then MUTE_B within 2s, then LC blocked — no fault, MUTE_LAMP on

  4. #4Simultaneous MUTE_A + MUTE_B latches fault

    Both mute sensors asserted at same time is an invalid mute — fault latches

  5. #5MUTE_B before MUTE_A latches fault

    Reversed order is an invalid mute — SAFETY_FAULT_LATCH must latch

Ready to build this?

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

Sign up to play this scenario →

Already have an account? Log in

Runnable simulator field guide

Light-curtain muting sequence scenario: test checklist

Direct answer

The learner can draw the complete state model, test every permitted and rejected sensor order and explain why acknowledgement cannot substitute for hazard clearance.

Written for pLC and safety learners examining state, timers and sensor patterns around a simulated material-transfer muting case.

a guarded motor-control and machine-safety training cell used to prove starter, drive, interlock, stop, feedback and restart behavior while studying muting-state logic, sequence evidence and controlled recovery
System map / 02

NODE 01observable

Scenario setup

Simulated material path, protective field, mute sensors, expected direction, sequence states, transition timeouts, maximum mute, fault state, indication, reset eligibility and restart separation.

NODE 02observable

I/O and state map

Sensor pattern through explicit state and time guards to mute request, protective-field status, machine permission, fault latch, clearance and deliberate recovery.

NODE 03observable

Normal run

Each valid pattern enters and exits the mute once while invalid patterns reach a defined faulted or protected state.

NODE 04observable

Boundary run

Reverse order, overlap, missing sensor, blocked field, excessive duration, simultaneous change, device discrepancy, reset during demand and power return.

NODE 05observable

Injected fault

A model, sensor, state, transition, timer, mute, protective-field, fault, reset or restart mismatch.

NODE 06observable

Target check

The educational result kept separate from a qualified design and validation of the target safety function.

Answer surface / 07

Why model light-curtain muting as states?

Explicit states make sensor order, timing, normal exit, fault paths and reset eligibility inspectable instead of hiding them in overlapping timer bits.

What is the difference between muting and bypass?

Muting is an automatic, monitored and bounded function for a defined condition; an uncontrolled bypass defeats protection and is not equivalent.

Real light curtain muting plc footage

See this exact skill in the working simulator.

Watch the real browser product respond to the task on this page, then try the same practical workflow yourself. No slides, concept mockups, install, or credit card.

Try this in the browser
Light Curtain Muting — PLC Timing, Sequence and Fault Detection