Loading the figure…
Stopped · Your code isn't running yet. Until you press Run, the board runs the program already on it.
Nothing printed yet. Press Run.
Not checked yet
Run your code to check it. The checks replay a fixed script on a virtual clock, so the same code always gets the same result.
Each fault really happens in the simulation. Trigger one, watch the figure, then read why.
Play the world: press, slide and turn the parts while the code runs.
Change a value here or click a chip in the code.
Turn the Pi into a robot's brain: a ROS 2 node publishes velocity commands on /cmd_vel ten times a second, and a button on GPIO27 stops it for good.
| Pin | Connects to | What it does |
|---|---|---|
GPIO27 | E-stop button, other side to GND | Digital input with pull-up |
GPIO17 | 330 Ω resistor and status LED | Digital output |
GND | Button and LED | Return |
Sensors and actuators this board drives, with the real connections.
Anode (long leg) to GPIO17 on pin 11 through a 330 Ω resistor, cathode to GND on pin 9: about 4 mA from 3.3 V. gpiozero calls it LED(17).
| Part pin | Board pin |
|---|---|
| A | GPIO17Wire colour orange |
| K | GNDWire colour black |
Never connect an LED without its resistor: the pin would try to source far more than 16 mA.
One leg to GPIO27 on pin 13, the other to GND on pin 14. gpiozero's Button turns on the internal pull-up, so no resistor is needed: the pin reads high until you press.
| Part pin | Board pin |
|---|---|
| 1 | GPIO27Wire colour yellow |
| 3 | GNDWire colour black |