|
|
3 tahun lalu | |
|---|---|---|
| .. | ||
| keymaps | c98cb17ce1 Fixup missing include in mxss via keymap (#20475) | 3 tahun lalu |
| templates | a84528f853 Move remaining `LAYOUT`s to data driven (#20422) | 3 tahun lalu |
| config.h | 4ae9bfd17a Move `RGBLIGHT_HUE/SAT/VAL_STEP` to data driven (#21292) | 3 tahun lalu |
| info.json | 4ae9bfd17a Move `RGBLIGHT_HUE/SAT/VAL_STEP` to data driven (#21292) | 3 tahun lalu |
| mxss.c | a84528f853 Move remaining `LAYOUT`s to data driven (#20422) | 3 tahun lalu |
| mxss_frontled.c | 9632360caa Use a macro to compute the size of arrays at compile time (#18044) | 4 tahun lalu |
| mxss_frontled.h | 961f0b7b2d Reallocate SAFE_RANGE (#19909) | 3 tahun lalu |
| readme.md | 961f0b7b2d Reallocate SAFE_RANGE (#19909) | 3 tahun lalu |
| rgblight.c | 54d172830c [Keyboard] Fix mxss rgblight.c compilation issues (#20804) | 3 tahun lalu |
| rules.mk | f9aeea64c1 Migrate `MCU` and `BOOTLOADER` to data-driven (#19529) | 3 tahun lalu |
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).
