MISSION 44 · INTERMEDIATE ARDUINO
Make countdown mission clock. Explore nonblocking countdown and cancel.
5 · Inventor Arcade
Your new skill: Nonblocking countdown and cancel
Revisit the skill you will reuse: electronic dice console
WHAT YOU'LL USE
Reuse the parts between missions; these are not 45 simultaneous installations. Red/yellow/green means those three monochrome colours. RGB is a separate component with three channels.
BEFORE YOU BUILD
Unplug USB before changing connections. Use only the USB supply for this build; never connect 9V to 5V or a signal pin, and never connect to mains. An adult verifies variant, printed pin labels and resistor values before powering. Stop and unplug if a part becomes hot or damaged.
YOUR REWARD
PREDICT BEFORE YOU BEGIN
Before the test: which input will change, and what signal or reading do you expect?
BEFORE YOU BUILD
Parent check: exact part variant, labelled pins and stated values. If a check cannot be confirmed, keep this physical build unpowered and explore the code and prediction instead.
YOUR CHALLENGE
NEW POWER-UP
Nonblocking countdown and cancel
You have explored pseudorandom choice and one event per press. Now try nonblocking countdown and cancel.
Each coloured strip is one connected group. Different numbered rows stay separate. This explains the board; use the mission’s exact connection reference for component positions. Check rail breaks on your supplied board.
Copy the complete code into Arduino IDE or download the sketch. Follow the matching component card before connecting power.
// First Wonder Brain Bots 44 — Countdown Mission Clock
// USB-powered model. Unplug before rewiring. Serial Monitor: 9600 baud.
unsigned long started=0;
int state=0;
int countValue=0;
int durationSeconds=10;
bool latched=false;
const byte buttonPins[]={2};const byte buttonCount=1;
bool rawButton[4]={HIGH,HIGH,HIGH,HIGH},stableButton[4]={HIGH,HIGH,HIGH,HIGH},pressedEvent[4]={false,false,false,false};
unsigned long changedAt[4]={0,0,0,0};
void scanButtons(unsigned long now){for(byte i=0;i<buttonCount;i++){
pressedEvent[i]=false;bool raw=digitalRead(buttonPins[i]);
if(raw!=rawButton[i]){rawButton[i]=raw;changedAt[i]=now;}
if(now-changedAt[i]>=30&&raw!=stableButton[i]){stableButton[i]=raw;pressedEvent[i]=raw==LOW;}
}}
bool press(byte index){return pressedEvent[index];}
void setup(){Serial.begin(9600);pinMode(8,OUTPUT);digitalWrite(8,LOW);pinMode(2,INPUT_PULLUP);Serial.println("Ready. Follow your mission test.");}
void loop(){
unsigned long now=millis();
scanButtons(now);
if(press(0)){state=!state;latched=false;started=now;countValue=-1;Serial.println(state?"START":"CANCEL");}
if(state){long remaining=durationSeconds-(now-started)/1000;
if(remaining!=countValue){countValue=remaining;Serial.println(max(0L,remaining));}
if(remaining<=0){state=0;latched=true;Serial.println("TIME UP");}}
else if(digitalRead(2)==LOW)latched=false;digitalWrite(8,latched);
}
CONNECTION MAP
BUILD PATH
STEP 1 OF 6
You will explore nonblocking countdown and cancel. Gather the kit and home materials below. Unplug USB. Match the part names and printed labels.
A video demonstration will appear here when it is ready. You can follow the written step now.
You will explore nonblocking countdown and cancel. Gather the kit and home materials below. Unplug USB. Match the part names and printed labels.
WHAT'S REALLY HAPPENING?
Nonblocking countdown and cancel. Check your rule against an example where it should respond and one where it should not. The cancel button needs to remain responsive while time passes.
This is a tabletop learning model. Real systems also need reliable power, robust sensors and careful handling of unknown measurements; this kit model is not a safety or security device.
FAIR-TEST CHALLENGE
Change one input or setting at a time; keep the wiring and protection unchanged. Repeat three trials.
WHEN IT DOESN'T WORK YET
Likely cause: Wrong board, port or cable connection
Try this first: Check Arduino Uno selection and supplied data cable. Unplug external wiring before checking upload on built-in LED.
Likely cause: Pin labels, input calibration or variant differs
Try this first: Unplug. Compare every connection with the map. Return to the earlier single-input mission; test one subsystem at a time.
Likely cause: Sensor settling, target, contact or calibration
Try this first: Follow the exact test setup; allow settling, use a flat target or check module pinout unpowered. Never replace unknown with a guessed safe reading.
CLEAN, RESET AND STORE
Disconnect USB, remove wires carefully and store components dry.
NEXT SKILL
Mode selection and input validity