Students will
- Connect to the correct UNO Q from App Lab
- Run an unchanged example and identify visible evidence of success
- Distinguish the board's Linux processor from its real-time microcontroller at a classroom level
Arduino UNO Q 2GB
Connect UNO Q and run an App Lab example
Set up the UNO Q in Arduino App Lab, run a known example, and document the difference between the Linux side and the real-time microcontroller.
MS-PRO-PD-13ProgrammingMS-PRO-TR-19Programming
Evidence of success
- App Lab shows the intended UNO Q as available
- The selected example runs and stops predictably
- A labeled two-part diagram distinguishes the Linux processor and real-time microcontroller
- A setup note records one verified step and one possible failure point
Hardware
- Arduino UNO Q 2GB
- USB-C data cable
- Computer with Arduino App Lab
- Classroom Wi-Fi for initial setup and updates
Prerequisites
- Use a classroom computer and account safely
- Identify a USB-C data cable
- Teacher has completed setup once before class
Before class
- Install and open the current Arduino App Lab release
- Complete one board setup and update cycle before class
- Confirm the classroom network permits the required connection
- Prepare a fallback screenshot or recording in case account or network access is unavailable
Build and test
- 01Connect the UNO Q directly with a known data-capable USB-C cable
- 02Open App Lab and complete the guided board setup, including device name, password, network, and available updates
- 03Open the Examples area and choose a simple built-in example such as Blink LED or UNO Q Pin Toggle
- 04Run the example unchanged and record the visible evidence
- 05Open the app structure and identify what runs as an Arduino sketch and what runs on the Linux side
- 06Stop the app cleanly and record the exact setup step that would help the next group
Optional engineering record
Record evidence from this lesson
Choose the prompts that help students explain predictions, evidence, debugging, and transfer. Saving creates a new entry in this browser’s Rudi notebook.
Record your thinking — optional4 prompts
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.
Nothing is saved until you choose this button.
Troubleshooting
App Lab does not find the board
Confirm the cable carries data, reconnect directly rather than through an unverified hub, and follow the current App Lab connection prompt.
Setup or update stalls
Check network access, board power, and the current App Lab status; use the prepared fallback rather than repeatedly changing settings during class.
2026 middle school standards
Potential CSTA connections
These are evidence-based crosswalk candidates for curriculum review—not a claim of official alignment.
Use reference documentation in program development.
Students use current board and App Lab documentation while setting up and running a known example.
Lesson evidence: Documented setup and successful example runUse systematic strategies to test, refine, and document changes to a computing technology to meet the intended purpose.
Students isolate variables, compare observed behavior with the intended purpose, and document a revision.
Lesson evidence: Setup note and observed run evidenceSupporting concepts
board-tour · component-boards · sketch-foundations
Sources and review
Arduino UNO Q documentationArduino App Lab documentationArduino App Lab examplesStarting point, not verified curriculum. Review the actual hardware, circuit, code, power requirements, and classroom conditions.
After teaching this lesson