-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding LEDs #13
Comments
I too would like to know. Seems like it should be easy to add cheap RGB LED strips on the bottom of the PCB for people with Acrylic cases. |
LED strip can be added by connecting GND and +5v on the underside of the ISP headers. Not sure about programmability. source: u/thearctican @ https://www.reddit.com/r/MechanicalKeyboards/comments/f5kbc6/cftkb_mysterium_transparent_grey/ |
It uses an ATMEGA32A-PU. (V2 model) |
There is a similar topic in the discipline issues section. I'm trying to get this sorted but I get an unrecognized USB device error after flashing the firmware. I guess we can't use a pin already taken for rows or columns? Anyway, QMK supports only certain types of LED strips: https://beta.docs.qmk.fm/using-qmk/hardware-features/lighting/feature_rgblight LEDs have to be enabled in rules.mk and configured in config.h by uncommenting LED part:
I bet the problem I got is because A7 is already used as a column pin, I struggle to understand which pins are BX, CX and DX as this naming doesn't match ATMEGA32A pinout schematic. |
the guide mentions D71 pin used for ISO, I wonder if we can use it to control the rgb... |
According to the schematic, only C0 & C0 are not taken but if you assign any of them to the LED's you'll get an unrecognized device. Atm I got fixed blue LED's and I would love to replace them with an RBG led. |
Using Pin 23 - C1 works fine. Controlling the RGB with defined Keys in the Keymap works fine. |
Is it possible to add LEDs or any type of lighting to the board?
The text was updated successfully, but these errors were encountered: