|
|
3 anni fa | |
|---|---|---|
| .. | ||
| keymaps | c6f1b594a2 Remove legacy keycodes, part 2 (#18660) | 3 anni fa |
| templates | 9632360caa Use a macro to compute the size of arrays at compile time (#18044) | 4 anni fa |
| config.h | 154d35ac14 Remove `UNUSED_PINS` (#17931) | 4 anni fa |
| info.json | 3da6575e24 Move keyboard USB IDs and strings to data driven: M (#17859) | 4 anni fa |
| mxss.c | 2728603fe6 Move tmk_core/common/<plat> (#13918) | 4 anni fa |
| mxss.h | 645c5fabf2 Add VIA support to MxSS, plus minor tweaks (#7809) | 6 anni fa |
| mxss_frontled.c | 9632360caa Use a macro to compute the size of arrays at compile time (#18044) | 4 anni fa |
| mxss_frontled.h | 645c5fabf2 Add VIA support to MxSS, plus minor tweaks (#7809) | 6 anni fa |
| readme.md | 645c5fabf2 Add VIA support to MxSS, plus minor tweaks (#7809) | 6 anni fa |
| rgblight.c | fa141a5a8f Migrate STM32_EEPROM_ENABLE to use EEPROM_DRIVER (#14433) | 5 anni fa |
| rules.mk | a8d440e4e0 Tidy up NKRO_ENABLE rules (#15382) | 4 anni fa |
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.
