Unified-Daughterboard VS mechware

and concerning sending keystroke to host i opted to use the unified-daughter board from the open source project hence there is no presence of the usb connector or fuse.

It is Unified Daughterboard, which has been used in many keyboards. I don't want to make my main keyboard act as a hub because I want all other modules to work without the need for the main one. The hub is just a simple PCB that will take all outputs from all modules and combine them into 1 output to the daughter board. If there is no problem for the daughterboard to take multiple inputs, I guess my concept will work.

I'll be replacing the board above with the one shown here: GitHub - ai03-2725/Unified-Daughterboard: Unified daughterboards for custom keyboard designers and users

A lot if not most boards I’ve seen use the unified daughterboard, or a size variation thereof. These are relatively easy to acquire or order custom, the schematics are online: https://github.com/ai03-2725/Unified-Daughterboard

Sure, how do I check that? Also, if this is helpful, I believe this the schematic of the daughterboard: https://github.com/ai03-2725/Unified-Daughterboard.

Hi, I'm using this USB 2.0 daughterboard for a mechanical keyboard: https://github.com/ai03-2725/Unified-Daughterboard. The USB-C to USB-C wire I'm connecting to it only seems to work in one orientation — is it meant to be reversible? I was wondering if it's an implementation issue or a limitation of the 2.0 spec.

As I've been looking (and failing) to find a unified daughterboard C3 in the EU/USA I'm willing to organize a small GB asap if enough people are interested.

There is a universal open source daughterboard that most boards use: https://github.com/ai03-2725/Unified-Daughterboard

These daughterboards are based on the latest spec, seen here: https://github.com/ai03-2725/Unified-Daughterboard and notably include ESD protection, unlike previous revisions. Great for replacing a current daughterboard if you are worried about electro static discharge, and for future boards to have some lying around.

I do it for my keyboard firmware project, it's designed to compile up for Arduino (well, not their IDE, but VS with PlatformIO but it's much of a muchness) https://github.com/dairequinlan/mechware

code here https://github.com/dairequinlan/mechware/blob/main/src/input/MatrixInput.cpp That's dual use code, few #define chunks there for Ardiuno (Teensy) and Pico, but basically (using the more common Arduino syntax) ...

Plan is to add the BLE functionality as another pluggable module to my own firmware https://github.com/dairequinlan/mechware

Indeed. It makes for a neat µC for a keyboard, all that GPIO :-D OP are you planning a complete build ? This might be useful it's a complete pluggable and configurable firmware for PICO based keyboards. Dual compiles to Teensy/Arduino so there are a bunch of conditional blocks but it's fairly straightforward otherwise.

it's not an actual pro micro though, right ? It's a RP2040 board like the Pi Pico. I didn't know that that was even supported by QMK yet (if that's what you're trying to use). Coincidentally I just started using as a daily driver a custom split board I put together, which has a Pi PICO in either half, talking I2C to one another. Completely custom firmware though, source is here: https://github.com/dairequinlan/mechware/tree/pico