noroadsleft a345458fa9 MxSS Configurator bugfix: removed an extra key that didn't belong (#3362) | 5 years ago | |
---|---|---|
.. | ||
keymaps/default | Add MxSS keyboard (#3335) | 5 years ago |
templates | Add MxSS keyboard (#3335) | 5 years ago |
config.h | Add MxSS keyboard (#3335) | 5 years ago |
info.json | MxSS Configurator bugfix: removed an extra key that didn't belong (#3362) | 5 years ago |
mxss.c | Fixed issues with MxSS RGB functionality (#3341) | 5 years ago |
mxss.h | MxSS refactor and Configurator bugfix (#3355) | 5 years ago |
mxss_frontled.h | Add MxSS keyboard (#3335) | 5 years ago |
readme.md | Add MxSS keyboard (#3335) | 5 years ago |
rgblight.c | Fixed issues with MxSS RGB functionality (#3341) | 5 years ago |
rules.mk | Add MxSS keyboard (#3335) | 5 years ago |
Keyboard Maintainer: MxBlue
Hardware Supported: Custom PCB, ATMega32u4
Hardware Availability: https://geekhack.org/index.php?topic=94986.0
Make example for this keyboard (after setting up your build environment):
make mxss:default
See build environment setup then the make instructions for more information.
The MxSS PCB has 2 front RGB LEDs which has a separate brightness and mode of operation to the rest of the RGB LEDs. These are controlled through the supplied custom keycodes.
There are 3 modes of operation:
Colors for FLED_INDI mode are hardcoded as hue/saturation values, the caps lock color can be found in mxss_frontled.h, the layer colors are defined in keymap.c (see default/keymap.c for example).
As SAFE_RANGE is used for defining the custom keycodes seen above, please use NEW_SAFE_RANGE as the starting value for any custom keycodes in keymap.c, as per the example.