By Kevin McAleer, 3 Minutes
Page last updated November 20, 2026

You can now see inside a running program. That changes how you build things: fewer guesses, more measurements.
| Instrument | Best for | Feed it with |
|---|---|---|
| Plotter | Values that change over time, side by side | inst.plot(name=value) |
| Multimeter | One voltage, with min, max and average | inst.read_adc(adc) or inst.meter(value) |
| Oscilloscope | PWM frequency and duty, signal shape | inst.read_pwm(pwm) or inst.scope(value) |
| Data Logger | Keeping a record of a whole run | Nothing extra. Press REC |
And the ideas underneath:
SNK. Your program keeps running while it reportsAsk what kind of question you have.
| Your question | Reach for |
|---|---|
| “What is it right now?” | Multimeter |
| “How is it changing?” | Plotter |
| “Is the signal the right shape?” | Oscilloscope |
| “What happened during that run?” | Data Logger or a CSV file |
| “Did it ever dip?” | Multimeter MIN, or the Plotter |
Next time something misbehaves, try this before changing any code:
It feels slower than guessing. It is nearly always faster.
We covered four instruments. The dock has many more, and they all work the same way: open it, click ?, copy the snippet. I²C detect scans for connected chips, Range draws a distance sensor’s readings as a radar, IMU shows a tilt sensor in 3D, and the output panels let you drive a servo or motor by hand.
Quick quiz 1 of 3
Your robot’s battery might be sagging when the motors start. Which reading tells you?
Quick quiz 2 of 3
Which two helpers return a value your program can use?
Quick quiz 3 of 3
What’s the first step of the debugging habit?
You can use the arrows ← → on your keyboard to navigate between lessons.
Comments