How to Build a Cosmic Critter Pet with Raspberry Pi Pico

What you'll build

In this guide you will bring a Cosmic Critter to life on a Raspberry Pi Pico using an MPU6050 accelerometer, a 0.96-inch OLED display for its animated face, a WS2812B LED ring for nebula-inspired ambient lighting, and a piezo buzzer for chirps. The critter reads tilt from the accelerometer and maps it to one of four moods — HAPPY, SLEEPY, DIZZY, or HYPER — updating the OLED face, LED ring colour, and buzzer tone accordingly. Tilt it hard along one axis and it goes hyper; tip it the other way and it drifts to sleep; rock it sideways and it gets dizzy. Leave it flat and it stays content. A button lets you cycle moods manually.

The Raspberry Pi Pico is a solid beginner platform for this kind of project. The RP2040 chip handles I2C, PWM, and the PIO-driven WS2812B protocol without needing external timers or interrupts. The firmware uses the Arduino-compatible mbed core, so the libraries feel familiar if you have worked with Arduino before. You will learn how to read accelerometer data over I2C, apply threshold logic to derive discrete states, drive a NeoPixel ring with FastLED, and generate tones on a buzzer using analogWrite-style PWM.

When you finish you will have a self-contained interactive toy that runs from any USB power bank. The code is organised into clear sections for mood logic, LED patterns, face rendering, and sound, so extending it — adding new moods, swapping in a light sensor, changing the chirp melody — is a matter of editing one function at a time. For a button-only take on the virtual pet concept, see the ClawdBot Tamagotchi.

What you are building

This guide covers one complete Cosmic Critter unit. The firmware has four jobs:

1. Read acceleration from the MPU6050 over I2C and map the X/Y values to a mood state (HAPPY, SLEEPY, DIZZY, or HYPER).
2. Render a matching face on the SSD1306 OLED and update the WS2812B LED ring colour and animation.
3. Emit a short chirp on the piezo buzzer every 3 seconds when idle.
4. Debounce the mood button and let it cycle through all four moods manually.

This guide does not cover enclosure fabrication, battery management circuits, or multi-unit communication. Those are meaningful extensions but they are not needed to get a working critter.

Upload and calibrate

Flash the firmware via Schematik's one-click upload or copy the .uf2 file to the Pico in BOOTSEL mode. Open Serial Monitor at 115200 baud. On successful boot you should see:

Cosmic Critter ready

If that line does not appear within two seconds of power-on, the MPU6050 initialisation has failed — check GP4/GP5 wiring first.

Pin constants to know. The firmware defines SDA_PIN and SCL_PIN as GP4 and GP5 respectively, but it calls Wire.begin() without arguments. On the RP2040 mbed core, Wire.begin() always uses the variant's fixed I2C pins; a static_assert in the firmware confirms that PIN_WIRE_SDA == 4 and PIN_WIRE_SCL == 5 at compile time. If you try to move I2C to other pins by changing those constants alone, the assert will fail — you would also need to switch to Wire1. For this build, leave them at GP4/GP5.

Other constants. LED_PIN is GP12, BTN_PIN is GP14, BUZZER_PIN is GP15, and NUM_LEDS is 12. FastLED brightness is fixed at 120 out of 255 — enough to see the colours clearly without drawing excessive current. The loop runs on a 50 ms delay.

Tilt thresholds. The firmware reads accelX and accelY in m/s² from the MPU6050 (range set to MPU6050_RANGE_4_G) and applies these rules in order:

• accelX > 5.0 → HYPER
• accelX < -5.0 → SLEEPY
• abs(accelY) > 6.0 → DIZZY
• else → HAPPY

If your critter flips to HYPER while sitting flat on a table, the MPU6050 axes may be rotated relative to the expected orientation — try reseating the board or rotating it 90 degrees. If all four moods feel too sensitive or too sluggish, adjust the 5.0 and 6.0 thresholds directly in the firmware.

Button behaviour. The button on GP14 cycles through HAPPY → SLEEPY → DIZZY → HYPER → HAPPY with a 250 ms debounce window. Press it to override the tilt logic and test each mood's LED pattern and face before you start tilting the device around.

Chirp timing. The buzzer emits a short chirp every 3000 ms when the critter is in an idle state. If you want less frequent chirps, increase that interval; if you want silence entirely, leave the buzzer unconnected.

Troubleshooting

• Serial Monitor shows nothing after power-on. Confirm baud rate is 115200. If still nothing, the firmware is likely stalling at mpu.begin() — check that GP4 and GP5 are correctly connected to the MPU6050 SDA and SCL pins.
• OLED stays blank but MPU6050 works. The SSD1306 and MPU6050 share the I2C bus. If the OLED is blank, it is likely at a different I2C address than 0x3C, or its SDA/SCL leads are swapped. Some SSD1306 breakouts have SDA and SCL in a different order than the MPU6050 — compare the two silkscreens carefully.
• I2C wired to GP2/GP3 instead of GP4/GP5. The mbed core's Wire.begin() is hard-wired to the variant's GP4/GP5 regardless of what SDA_PIN and SCL_PIN constants say. Moving the physical wires to GP2/GP3 will break I2C silently. Keep all I2C peripherals on GP4/GP5.
• LED ring flickers or Pico resets when LEDs first light up. The WS2812B ring draws a surge of current on startup. Fit the 470 µF capacitor across VBUS and GND as close to the ring's power pads as possible. If flicker persists, check that the ring's GND is tied to Pico GND, not floating.
• Mood never changes with tilt. Open Serial Monitor and watch for mood state output. If the state is always HAPPY regardless of tilt, either the MPU6050 is reading near-zero (flat orientation or a wiring fault) or the thresholds are too high for your mount angle. Try tilting the Pico sharply past 45 degrees; if it still stays HAPPY, print accelX and accelY raw values to confirm the sensor is producing real data.
• Button mood cycle does not respond. INPUT_PULLUP means the button should connect GP14 to GND when pressed, not to 3V3. If you wired it to 3V3, the pin will never read LOW and the button will appear dead.

Going further

The four mood states are defined in a single switch block. Adding a fifth mood — say, ANGRY triggered by a sudden sharp tap — means adding one threshold check and one case with its own LED colour, face bitmap, and buzzer pitch. The MPU6050 also exposes a gyroscope; you could use rotation rate instead of (or alongside) tilt to distinguish a slow tip from a sudden shake.

For a wearable version, swap the breadboard for a small perfboard, replace jumper wires with short solid-core wire, and power everything from a 3.7 V LiPo through a Pico LiPo board that handles charging over USB. The firmware requires no changes — the mbed core abstracts the voltage supply — though you will want to lower FastLED.setBrightness from 120 to something lower to extend battery life.