|
|
5 سال پیش | |
|---|---|---|
| .. | ||
| keymaps | 645c5fabf2 Add VIA support to MxSS, plus minor tweaks (#7809) | 6 سال پیش |
| templates | 645c5fabf2 Add VIA support to MxSS, plus minor tweaks (#7809) | 6 سال پیش |
| config.h | 1e1b469fa2 Remove `DESCRIPTION`, K-M (#11619) | 5 سال پیش |
| info.json | a345458fa9 MxSS Configurator bugfix: removed an extra key that didn't belong (#3362) | 8 سال پیش |
| mxss.c | 645c5fabf2 Add VIA support to MxSS, plus minor tweaks (#7809) | 6 سال پیش |
| mxss.h | 645c5fabf2 Add VIA support to MxSS, plus minor tweaks (#7809) | 6 سال پیش |
| mxss_frontled.c | 0f500eb336 MxSS RGB Handler Touchup (#8105) | 6 سال پیش |
| mxss_frontled.h | 645c5fabf2 Add VIA support to MxSS, plus minor tweaks (#7809) | 6 سال پیش |
| readme.md | 645c5fabf2 Add VIA support to MxSS, plus minor tweaks (#7809) | 6 سال پیش |
| rgblight.c | c38fe49242 Update MXSS custom rgblight and fix compilation error | 5 سال پیش |
| rules.mk | 7161d65070 Remove FAUXCLICKY feature (deprecated) (#11829) | 5 سال پیش |
This PCB supports the VIA configurator, and this is the recommended way to configure the keymap on this keyboard. Building the firmware should only be necessary if you would like to change the colours of the front LEDs in indicator mode.
For more information about the VIA configurator, see here.
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).
# Further Notes
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.
