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.
Scan the I²C bus for devices, then ask an MPU-6050 motion sensor who it is. I²C is two wires shared by many chips, each with its own address.
| Pin | Connects to | What it does |
|---|---|---|
SDA | The module's SDA | I²C data, the same pin as A4. |
SCL | The module's SCL | I²C clock, the same pin as A5. |
5V | The module's VCC | Its regulator makes 3.3 V for the chip. |
GND | The module's GND | The shared ground. |
Sensors and actuators this board drives, with the real connections.
VCC to 5V, GND to GND, SDA to SDA, SCL to SCL. It answers at 0x68 (0x69 with AD0 high). The breakout's own pull-up resistors matter here: the R4 has none fitted.
| Part pin | Board pin |
|---|---|
| VCC | 5VWire colour red |
| GND | GNDWire colour black |
| SDA | SDAWire colour blue |
| SCL | SCLWire colour yellow |
Use a breakout with a regulator on it (the common GY-521 has one); the bare chip is 3.3 V only.