A lot of custom-built or ethusiast-level keyboards such as the Planck, Zeal60, Let's Split and many more use an open-source firmware called QMK. This firmware allows you to freely define your keyboard layout and add a lot of functionality (i.e. emitting a different keycode on long and short keypress, dual-function keys, leader keys (think of vi's :)). We could use the Hack Week to add functionality, check the source code for security issues and add support for more keyboards.
If you own a qmk-running mechanical keyboard or plan on doing so feel free to join me :)
This project is part of:
Hack Week 16
Activity
Comments
Be the first to comment!
Similar Projects
Adding individual key RGB to the keychron k17 pro by ldragon
Description
I recently acquired a k17 pro and was disheartened to learn instead of a way to set individual key RGB values we were given a set of preset "animations" and didn't have individual key RGB. The keychron k17 pro in hardware does support individual key RGB addressing as shown in many of the animations it ships with.
However this functionality is not provided to the firmware/via to set individual key RGB back light. Other keychron keyboard with similar issues seem to have this resolved by following a method similar to the one described here this aim is to replicate this one the k17 and attempt to over come the shortcomings of the original(save+load does not work).
Goals
- Port the original RGB to the wls_2025q1 branch of keychrons fork of qmk
- Fix the capslock and numlock state light not changing state after being pressed once.
- Fix the save+load issue that is present in the fork by Sasuchisama
Resources
Creating test suite using LLM on existing codebase of a solar router by fcrozat
Description
Two years ago, I evaluated solar routers as part of hackweek24, I've assembled one and it is running almost smoothly.
However, its code quality is not perfect and the codebase doesn't have any testcase (which is tricky, since it is embedded code and rely on getting external data to react).
Before improving the code itself, a testsuite should be created to ensure code additional don't cause regression.
Goals
Create a testsuite, allowing to test solar router code in a virtual environment. Using LLM to help to create this test suite.
If succesful, try to improve the codebase itself by having it reviewed by LLM.
Resources
Smart lighting with Pico 2 by jmodak
Description
I am trying to create a smart-lighting project with a Raspberry Pi Pico that reacts to a movie's visuals and audio that involves combining two distinct functions: ambient screen lighting(visual response) and sound-reactive lighting(audio response)
Goals
- Visuals: Capturing the screen's colour requires an external device to analyse screen content and send colour data to the MCU via serial communication.
- Audio: A sound sensor module connected directly to the Pico that can detect sound volume.
- Pico 2W: The MCU receives data fro, both inputs and controls an LED strip.
Resources
- Raspberry Pi Pico 2 W
- RGB LED strip
- Sound detecting sensor
- Power supply
- breadboard and wires