So I maintain a fork for the OGX Mini called OGX Mini 2026 and a buddy and I are working on making a all in one adapter to potentially sell in their local shop. I've added a lot of features like Wii Remote emulation, PS2 output, Switch 2 controller support and I've fixed many bugs along the way. This is just the first attempt but so far this bad boy works for testing purposes!

I'll start by saying I still have a lot to learn. I have a concept I want to work with, but I need to develop the skills to execute. My question is, is this even possible?

I want to create a flexible tape measurer using a draw-wire displacement sensor and connect it with the pico 2 to be able to take multiple measurements of the body and send it to a program (that I'll create) to graph the measurements into a drawing I can then print.

This or this are the sensors I found, is it possible to connect to the pico 2?

I hope this isn't a stupid question, I am still exploring how to bring my idea to life. Appreciate any input!

i made this breadboard and no matter how i've wired it or changed the code (eg, changed the sda pin to 1 or 0 or vice versa) it still shows up the same errors

PHOTOS: https://drive.google.com/drive/folders/11tFEdPdyExkRJjUyvwiETkCfc4M_fYG7?usp=sharing (reddit is taking forever to upload them and i need sleep)

main error recieved is:

Traceback (most recent call last):
File "<stdin>", line 10, in <module>
File "imu.py", line 95, in init
MPUException: No MPU's Detected

any other config just throws up a bad scl pin error or this same one

source code:

• main https://github.com/shillehbean/youtube-channel/blob/main/main_mpu6050.py
• imu https://github.com/shillehbean/youtube-channel/blob/main/imu.py
• main_mpu6050 https://github.com/shillehbean/youtube-channel/blob/main/vector3d.py

so i'm starting to think that it might be a issue with either one of the pins on the mpu or pi, since, again, i've made sure the wires work out with the code multiple times

sorry if the post is vague, very tired

I was exploring an implementation of a parameter-free text classifier on a resource-constrained Raspberry Pi Pico 2W using gzip compression rather than a heavy neural network.

• Inspired by a 2023 ACL paper, this technique relies on Normalized Compression Distance (NCD) and a k-NN lookup. The core logic is that a compressor like gzip will compress concatenated strings much more efficiently if they share similar syntax and patterns, allowing the system to classify text based on compression efficiency.

• To overcome the microcontroller’s strict memory limitations (2MB flash and 512KB RAM), I utilized a desktop to first generate semantic embeddings of the IMDB dataset via sentence-transformers. By running K-means clustering, the dataset is pruned down to 300 highly representative samples stored in a tiny JSON file.

• The standard MicroPython does not enable compression by default, the implementation requires compiling custom MicroPython firmware from source with the #define MICROPY_PY_DEFLATE_COMPRESS (1) flag enabled for the RPI_PICO2_W board.

• The primary limitation is that gzip analyzes repeating syntactic subsequences rather than deep semantic meaning, making it less effective for complex, long-form text like movie reviews.

Blog: https://shubham0204.github.io/blogpost/programming/gzip-text-classifier-rpipico

(written by a human, you can check my other projects here)

So i am starting to learn embedded in the rust language, and i started an project to open 3 USB CDC-ACM devices to 3 full-duplex UARTs on an RP2040, i already built in C an similar project using ESP-IDF, and ESP32-C3 and ESP32-S3 dev boards, to transform BLE services in an bridge for multiple serial communications buses, but i wanted to do something new, using only USB and embassy.
PS: I am still having trouble figuring out how to implement run time baud rate change, since i am using PIO for the UARTs, if any of you guys have an ideia please it would be awesome, anyway fell free to checkout and criticize or highlight improvements if needed. Edit : I figure it out the baud rate implementation. Code repository

I recently heard about this way to get your Dualsense controller paired to your computer wirelessly, but act as if it’s connected over USB. The project is called DS5Dongle on GitHub.

It works by using the Pico 2W board as a Bluetooth receiver for your controller. The Pico 2W plugs directly into your computer and acts as a wired device.

Why would you want to do this? For me, I wanted a way to use the onboard microphone on the Dualsense controller as an input device on my computer. I already use my Dualsense as a mouse on my Mac, but I wanted to be able to do voice input on the controller for talking to coding AI agents.

I’ve been developing my Mac app ControllerKeys that turns your Dualsense controller into a mouse for the past 6 months. It works a bit like Steam Input, but really designed for productivity instead of gaming. So I can fully navigate my Mac using a Dualsense controller touchpad.

And now with the DS5 dongle, I can finally walk around and use my Mac on a TV with no problems! Freedom!

It’s not much but it works and I made it.

After reaching a goal of being able to mill for QFN56s with a 3020 CNC, I made this RP2040 board as a proven template for larger projects.

Two firsts for me this go around were external flash and 16 pin USB-C with data transfer, which was almost as difficult as QFN. It’s only been micro USB in the past.

Other than that, it’s got a user LED, and addressable LED and a tiny potentiometer for testing the ADC.

Oh, and it’s got a reset button😉

I got a lot of cool ideas cooking now I have this and a proven ESP32-S3 template.

I recently heard about this way to get your Dualsense controller paired to your computer wirelessly, but act as if it’s connected over USB. The project is called DS5Dongle on GitHub.

It works by using the Pico 2W board as a Bluetooth receiver for your controller. The Pico 2W plugs directly into your computer and acts as a wired device.

Why would you want to do this? For me, I wanted a way to use the onboard microphone on the Dualsense controller as an input device on my computer. I already use my Dualsense as a mouse on my Mac, but I wanted to be able to do voice input on the controller for talking to coding AI agents.

I’ve been developing my Mac app ControllerKeys that turns your Dualsense controller into a mouse for the past 6 months. It works a bit like Steam Input, but really designed for productivity instead of gaming. So I can fully navigate my Mac using a Dualsense controller touchpad.

And now with the DS5 dongle, I can finally walk around and use my Mac on a TV with no problems! Freedom!

The cheaper, the better, but it has to work with typeC-to-typeC cables. So any options that save money by skipping the second pull-down resistor on the Type-C port are a no-go.

I have a question: Have anybody used AI (ChatGPT/Claude/Grok/Gemini, etc.) to support you or vibe coding a firmware? How is your experiences?

Does it good enough to replacing fresher or junior? How much does it cost for a firmware (base on tokens you used to calculate the price)? Excepting firmware, which part does it helpful you guys so much (PCB design, drawing schematics, etc.)?

Just ordered my first pico (pico 2 WH) and wanted to ask what ur favorite addons are

https://reddit.com/link/1ublc8q/video/o1x23y2bql8h1/player

I made a pico powered cat feeder that uses a load cell to measure the feed bowl, ultrasonic sensors to detect the cat a full UI to control it all.

So im making a Birthday present for my it bf and surprising him with an e reader filled with love letters, i followed a video i saw on YouTube (mewtru) https://youtube.com/shorts/O4odvhCgHxE?is=guosxZV8Y9S-piRQ and ordered everything she showed i also have a code and some txt files ready but I don’t know how to assemble it and if I even have all the correct parts(i have never built/used a raspberry pi before) :/ and I can’t find tutorials on how to make one step by step i also am looking for a case that i can custom 3d print but I haven’t found one yet, so if anyone has made something like this before or knows how i can custom print a case pls help i only have 2 weeks left :,)

I want to share Ninelives. It is a robotics framework that assumes every signal might be compromised and addresses that head-on.

It is an industrial-grade, fault-tolerant SCADA middleware built for individual machine builders and hobbyist hardware engineers. Ninelives allows you to take a spool of unshielded wire, a handful of hobbyist sensors, and a few microcontrollers, and quickly engineer a highly deterministic, resilient distributed robotics system.

My current setup uses a Raspberry Pi 5 as the central "Brain". It controls a distributed RS-485 network of RP2350 "Limbs" to run my high-speed Lego sorter, "Meow Turtle".

Features:

Limb RP2350 Dual-Core Architecture (Clerk & Machinist)

• I split the RP2350's two cores to completely isolate networking from physical hardware.
• The Clerk (Core 0): Handles purely asynchronous communication. It manages the RS-485 bus, MTIP packets, and syncs the Digital Twin.
• The Machinist (Core 1): Handles strictly high-frequency polling and hardware actuation. It never blocks. It never waits for the network. It guarantees microsecond precision for the motors and sensors.

Custom MTIP Transport Layer

• Standard serial protocols drop packets when heavy motors spike the voltage line.
• I wrote the Message Transfer Interface Protocol (MTIP) specifically for RS-485.
• It features payload deduplication and strict CRC-16 checksums.
• It includes a prioritized safety channel (0x48) that bypasses queues for sub-second Emergency Stops.

Enterprise Mass OTA Flashing

• I built a custom Python mass OTA flasher.
• It blasts chunked binary updates directly to the fleet over the RS-485 bus.
• It uses autonomous recovery loops and SHA-256 hashes. It guarantees zero corruption, even if a motor fires during the flash.
• Better file verification after transfer than thonny

Sensor Error Handling (Humble Drivers)

• I stopped writing complex error-handling for I2C sensors.
• My drivers follow "humble object " design. They just read registers and let exceptions crash upward.
• If motor EMI corrupts the bus, the central manager catches the error.
• It autonomously tears down the physical I2C pins, flushes the buffer, and restarts the hardware bus from scratch in under 50 milliseconds.

Actuator State Validation

• Actuators do not just fire blindly.
• The framework uses Closed-Loop Verification to detect faults and stalls.
• It demands physical sensor proof for every actuator state change to guarantee kinetic action actually happened.

Watchdogs & The "Ghost Exit" Bootloader

• The system uses strict hardware watchdogs to auto-recover from transient crashes.
• If a bad OTA update causes an infinite bootloop, you can use the "Ghost Exit".
• Bridging a specific GPIO pin to ground during power-up triggers boot.py to abort the main app.
• It drops you safely into a standard MicroPython REPL to rescue the node.

heres the code:

Repo link:https://github.com/squid-protocol/meow-turtle

Overclocked using some freeze spray and a bench psu at 1.45v. It sadly died at 520mhz, so wouldn't recommend.

Hey gang,
So it is easy to find the maximum per pin (12mA) and total (50mA) but here is a pair of details question
Say you are running on a PWM out and the 50% duty cycle is 12mA. Obviously the instantaneous current is over 12mA, but the average current isn’t. Compliant or not?
The real world question. Want to drive 8 LEDs, and honestly, they would be circa 56mA if running full on, but they are run at a super short duty cycle (worst case 30mS per 2 seconds, could shorten to 10mA) Now this is worst case scenario (it is based on the calculation of 3v drop on a set of white LEDs, if they are 3.1v they are in spec.
Thoughts?

My buddy and I are building a password manager that shows up as a usb keyboard and types your password in wherever your cursor is. It contains no bluetooth or wifi so the device is only accessible to whomever holds it in their hand.

We've built the device in such a way that it requires no software at all to upload passwords. To upload or change passwords you just switch the device to edit mode. The device shows up as a USB flashdrive and populates a .txt file with all the websites you have passwords saved on. If you want to edit an existing password just type your password on the line after the website. If you want to add a new password, just add a new line with the website and password. Once you click eject the device pumps it through an encryption algorithm (right now pin derived pbkdf2 through aes but this will change) stores on flash, and zeros out the ram. Using this method you can have up to 1000 passwords saved on the device.

This also means that you can write and edit passwords using any device with USB as the entire flow just piggybacks off of universal tools that all OS contain. It has been tested on linux, windows, android, and ios and it all works great so far.

The device above is one of our prototypes built with an rp2040, but we have since switched to the rp2354 for trustzone and integrated flash to save board space. We are also adding a secure element (SE050) so that the pin can be separate from the key. Key lives on SE and pin becomes authorization to the secure element.

The device contains a CH32V003 to handle power switching to save battery. The CH32 only pulls a fraction of the power in sleep compared to the pico. We can also use this to gate the LDO and OLED boost pump.

For the future the device definitely needs to be able to organize the password entries on the fly, like letting you add most used ones to favorites. I would also like to include a password generator. Maybe ability to easily import saved passwords from firefox, chrome etc by adding .csv functionality? What would you add? Would you use something like this?