Drum sequencer concept in PLC Programming - Step-by-Step Execution

Concept Flow - Drum sequencer concept

Start

↓

Initialize Step=0

↓

Check Step < Total Steps?

No→Stop

Yes↓

Trigger Drum Sounds for Current Step

↓

Wait for Step Duration

↓

Increment Step

↩Back to Check Step

The drum sequencer cycles through steps, triggering drum sounds at each step, then waits and moves to the next step until all steps are played.

Execution Sample

PLC Programming

Step := 0;
WHILE Step < 4 DO
  TriggerDrum(Step);
  WAIT(500ms);
  Step := Step + 1;
END_WHILE;

This code plays 4 drum steps, triggering sounds and waiting 500 milliseconds between each.

Execution Table

Iteration	Step	Condition Step<4	Action	Output
1	0	True	TriggerDrum(0), WAIT(500ms), Step=1	Drum sound at step 0
2	1	True	TriggerDrum(1), WAIT(500ms), Step=2	Drum sound at step 1
3	2	True	TriggerDrum(2), WAIT(500ms), Step=3	Drum sound at step 2
4	3	True	TriggerDrum(3), WAIT(500ms), Step=4	Drum sound at step 3
5	4	False	Exit loop	Sequencer stops

💡 Step reaches 4, condition Step<4 is False, loop ends

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	Final
Step	0	1	2	3	4	4

Key Moments - 2 Insights

Why does the sequencer stop after Step reaches 4?

Because the condition Step < 4 becomes False at iteration 5, so the loop exits as shown in execution_table row 5.

What happens if we forget to increment Step inside the loop?

The Step variable stays the same, so the condition Step < 4 is always True, causing an infinite loop. This is why Step increments at each iteration in execution_table rows 1-4.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of Step at iteration 3?

A 3

B 2

C 1

D 4

💡 Hint

Check the Step column in execution_table row 3.

At which iteration does the condition Step < 4 become False?

A Iteration 4

B Iteration 3

C Iteration 5

D Iteration 1

💡 Hint

Look at the Condition Step<4 column in execution_table row 5.

If the WAIT time is increased, how does it affect the execution table output?

A The output drum sounds play slower but Step values stay the same

B Step increments slower and fewer steps run

C Step values increase faster

D The loop exits earlier

💡 Hint

WAIT affects timing, not Step increments, as seen in variable_tracker.

Concept Snapshot

Drum sequencer cycles through steps triggering sounds.
Use a loop with Step variable from 0 to total steps - 1.
Trigger drum sound at each Step.
Wait between steps for timing.
Increment Step each loop until condition fails.
Loop ends when all steps played.

Full Transcript

A drum sequencer in PLC programming uses a loop to play drum sounds step by step. It starts with Step at 0, checks if Step is less than total steps (4 here), triggers the drum sound for that Step, waits for a set time (500ms), then increments Step. This repeats until Step reaches 4, when the loop stops. The execution table shows each iteration's Step value, condition check, actions, and output sounds. The variable tracker shows Step increasing from 0 to 4. Key points include why the loop stops when Step reaches 4 and the importance of incrementing Step to avoid infinite loops. The quiz tests understanding of Step values at iterations, when the loop ends, and effects of changing wait time.

Practice

1. What is the main role of a drum sequencer in PLC programming?

easy

A. To control the speed of a conveyor belt

B. To create repeating timed drum patterns using timers and outputs

C. To measure temperature changes over time

D. To display text messages on a screen

Solution

1. Step 1: Understand the drum sequencer purpose

   A drum sequencer automates drum beats by controlling timing and outputs.

2. Step 2: Match the purpose to options

   Only To create repeating timed drum patterns using timers and outputs describes creating repeating timed drum patterns using timers and outputs.

3. Final Answer:

   To create repeating timed drum patterns using timers and outputs -> Option B

4. Quick Check:

   Drum sequencer = timed drum patterns [OK]

Hint: Drum sequencer = timed drum beats using timers [OK]

Common Mistakes:

• Confusing drum sequencer with conveyor control
• Thinking it measures temperature
• Assuming it displays messages

2. Which of the following is the correct way to start a timer in a PLC drum sequencer program?

easy

A. Timer1(IN, 500ms);

B. Timer1 = Start(500);

C. TON Timer1 (IN:=TRUE, PT:=T#500ms);

D. StartTimer Timer1 500ms

Solution

1. Step 1: Identify standard PLC timer syntax

   In PLC programming, TON timers use the format TON TimerName (IN:=condition, PT:=preset time).

2. Step 2: Compare options to standard syntax

   Only TON Timer1 (IN:=TRUE, PT:=T#500ms); matches the correct TON timer syntax with input and preset time.

3. Final Answer:

   TON Timer1 (IN:=TRUE, PT:=T#500ms); -> Option C

4. Quick Check:

   TON timer syntax = TON Timer1 (IN:=TRUE, PT:=T#500ms); [OK]

Hint: Look for TON with IN:= and PT:= parameters [OK]

Common Mistakes:

• Using non-PLC syntax like Start(500)
• Missing IN:= or PT:= keywords
• Incorrect function call style

3. Given this PLC code snippet for a drum sequencer:

TON Timer1 (IN:=Start, PT:=T#250ms);
IF Timer1.Q THEN Output1 := TRUE; ELSE Output1 := FALSE; END_IF;

What will be the state of Output1 after 300ms if Start is TRUE?

medium

A. Output1 will be TRUE

B. Output1 will toggle ON and OFF rapidly

C. Output1 will be FALSE

D. Output1 will remain unchanged

Solution

1. Step 1: Understand timer behavior with Start TRUE

   Timer1 counts 250ms when Start is TRUE, then Q becomes TRUE after 250ms.

2. Step 2: Check Output1 assignment after 300ms

   Since 300ms > 250ms, Timer1.Q is TRUE, so Output1 is set to TRUE.

3. Final Answer:

   Output1 will be TRUE -> Option A

4. Quick Check:

   Timer done (Q=TRUE) after 250ms means Output1=TRUE [OK]

Hint: Timer Q is TRUE after preset time passes [OK]

Common Mistakes:

• Assuming Output1 toggles without reset
• Thinking Output1 stays FALSE after timer done
• Ignoring timer preset time

4. Identify the error in this drum sequencer PLC code snippet:

TON Timer1 (IN:=Start, PT:=T#500ms);
IF Timer1.Q THEN Output1 := TRUE;
ELSE Output1 := TRUE; END_IF;

medium

A. Start input is not declared

B. Timer1 PT value is invalid

C. Missing semicolon after TON statement

D. Output1 is always TRUE regardless of timer

Solution

1. Step 1: Analyze IF-ELSE logic for Output1

   Both IF and ELSE branches set Output1 to TRUE, so Output1 never becomes FALSE.

2. Step 2: Check timer and syntax correctness

   Timer PT value and semicolons are correct; Start input declaration is not shown but not an error here.

3. Final Answer:

   Output1 is always TRUE regardless of timer -> Option D

4. Quick Check:

   Output1 logic error = always TRUE [OK]

Hint: Check IF and ELSE assignments carefully [OK]

Common Mistakes:

• Ignoring ELSE branch value
• Assuming timer PT is wrong
• Confusing missing declarations as error

5. You want to create a 4-step drum sequencer using PLC timers that activates Output1, Output2, Output3, and Output4 in sequence every 500ms. Which approach best achieves this?

hard

A. Use one timer with 500ms preset and a counter from 1 to 4 to activate outputs in order

B. Use four timers all set to 500ms running simultaneously to activate outputs

C. Use one timer with 2000ms preset and activate all outputs at once

D. Use a single output and toggle it every 500ms without sequencing

Solution

1. Step 1: Understand sequencing with timers and counters

   One timer triggers every 500ms; a counter tracks steps 1 to 4 to activate outputs in sequence.

2. Step 2: Evaluate options for correct sequencing

   Use one timer with 500ms preset and a counter from 1 to 4 to activate outputs in order uses timer plus counter for stepwise output activation; others either run timers simultaneously or activate all outputs together, not sequencing.

3. Final Answer:

   Use one timer with 500ms preset and a counter from 1 to 4 to activate outputs in order -> Option A

4. Quick Check:

   Timer + counter = stepwise output sequence [OK]

Hint: Combine timer with counter for step sequencing [OK]

Common Mistakes:

• Using multiple timers without sequencing logic
• Activating all outputs simultaneously
• Not using a counter to track steps