|
|
5 år sedan | |
|---|---|---|
| .. | ||
| keymaps | fe6d6cf76d Remove empty override functions (#14312) | 5 år sedan |
| templates | 645c5fabf2 Add VIA support to MxSS, plus minor tweaks (#7809) | 6 år sedan |
| config.h | 6f36eb469d Remove unused `IS_COMMAND()` instances and Magic Key definitions (#14610) | 5 år sedan |
| info.json | 4791cfae1a Remove width, height and key_count from info.json (#14274) | 5 år sedan |
| mxss.c | fe6d6cf76d Remove empty override functions (#14312) | 5 år sedan |
| mxss.h | 645c5fabf2 Add VIA support to MxSS, plus minor tweaks (#7809) | 6 år sedan |
| mxss_frontled.c | 0f500eb336 MxSS RGB Handler Touchup (#8105) | 6 år sedan |
| mxss_frontled.h | 645c5fabf2 Add VIA support to MxSS, plus minor tweaks (#7809) | 6 år sedan |
| readme.md | 645c5fabf2 Add VIA support to MxSS, plus minor tweaks (#7809) | 6 år sedan |
| rgblight.c | c38fe49242 Update MXSS custom rgblight and fix compilation error | 5 år sedan |
| rules.mk | 5af1799735 Remove BLUETOOTH_ENABLE from keyboard-level rules.mk (#14379) | 5 år sedan |
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.
