6fa11bf219
* Separate RGBLight/RGB Matrix keycode handling * Remove `_DISABLE_KEYCODES` handling * Update RGB Matrix keycode docs * Update underglow keycodes for previously migrated boards * Update keycodes for boards with custom handling * Fix typos * Fix bad merge |
||
---|---|---|
.. | ||
keymaps/default | ||
ld | ||
config.h | ||
halconf.h | ||
keyboard.json | ||
matrix.c | ||
mcuconf.h | ||
readme.md | ||
rules.mk | ||
voyager.c | ||
voyager.h |
Voyager
A next-gen split, ergonomic keyboard with an active left side, USB type C, and low profile switches.
- Keyboard Maintainer: drashna, ZSA
- Hardware Supported: Voyager (STM32F303xC)
- Hardware Availability: ZSA Store
Make example for this keyboard (after setting up your build environment):
make zsa/voyager:default
Flashing example for this keyboard:
make zsa/voyager:default:flash
See the build environment setup and the make instructions for more information. Brand new to QMK? Start with our Complete Newbs Guide.
Voyager Customization
Indicator LEDs
There are 4 functions for enabling and disabling the LEDs on the top of the boards. The functions are STATUS_LED_1(bool)
through STATUS_LED_4(bool)
, with the first LED being the top most LED on the left hand, and the fourth LED being the bottom most LED on the right side.
By default, the Indicator LEDs are used to indicate the layer state for the keyboard. If you wish to change this (and indicate caps/num/scroll lock status instead), then define VOYAGER_USER_LEDS
in your config.h
file.
Detecting split / Gaming mode
To make it extra gaming friendly, you can configure what happens when you disconnect the right half. This is especially useful when using gaming unfriendly layers or layouts (e.g. home row mods, dvorak, colemak).
Example for enabling a specific layer while right side is disconnected:
void housekeeping_task_user(void) {
if (!is_transport_connected()) {
// set layer
}
}