Students will
- Select the correct board and port
- Upload a sketch and distinguish compile, upload, and runtime behavior
- Change a timing value and verify the new behavior
Arduino Uno R3
Upload a known sketch, change one timing value, and use visible evidence to prove that the Uno is running the revised program.
Reviewed connection map
Read before uploading
void setup() {
pinMode(LED_BUILTIN, OUTPUT);
}
void loop() {
digitalWrite(LED_BUILTIN, HIGH);
delay(500);
digitalWrite(LED_BUILTIN, LOW);
delay(500);
}Optional engineering record
Choose the prompts that help students explain predictions, evidence, debugging, and transfer. Saving creates a new entry in this browser’s Rudi notebook.
Use these prompts if they help students capture evidence, decisions, or questions. You do not need to complete every prompt or create an entry at every step.
Try a known data-capable USB cable, reconnect the board, and recheck the editor's board and port menus.
Confirm both delay values were edited, save the sketch, and upload the revised version again.
2026 middle school standards
These are evidence-based crosswalk candidates for curriculum review—not a claim of official alignment.
Students use board and editor documentation while selecting, compiling, and uploading a known sketch.
Lesson evidence: Successful documented uploadStudents isolate variables, compare observed behavior with the intended purpose, and document a revision.
Lesson evidence: Before-and-after timing evidenceboard-tour · sketch-foundations
Starting point, not verified curriculum. Review the actual hardware, circuit, code, power requirements, and classroom conditions.
After teaching this lesson