qmk_firmware/keyboards/rgbkb/zen
2021-09-29 23:23:10 -07:00
..
common Clean up includes for glcdfont headers (#7745) 2020-03-01 17:56:50 +11:00
rev1 Remove width, height and key_count from info.json (#14274) 2021-09-12 14:04:56 +10:00
rev2 Merge remote-tracking branch 'upstream/master' into develop 2021-09-12 14:10:26 +10:00
.noci Initial list of keyboards to exclude from CI (#11213) 2020-12-21 15:38:39 +01:00
config.h
post_rules.mk Move non-assignment code to post_rules.mk (#14207) 2021-09-09 21:37:31 -07:00
readme.md
rules.mk Merge remote-tracking branch 'upstream/master' into develop 2021-09-29 23:23:10 -07:00
zen.c
zen.h

Zen Keyboard

A split ergo keyboard with a few goals in mind:

  • Be as thin as possible. Other split KBs (Let's Split, Nyquist, Iris) are 15.2mm thick. The Zen rev2 is only 13.2mm thick including switches and caps when using Kailh Choc low-profile switches, and 22.1mm using standard MX switches and DSA keycaps.
  • Layout designed for gaming. 1.5u pinky keys, ortho alphas, and angled thumb keys. After trying Ortholinear, Atreus62, and Ergodox, this is the best layout for gaming and typing.
  • Per-key RGB lighting. 34 WS2812b LEDs per side make it exceptionally bright
  • Price. Using Arduino Pro Micro, SK6812 LEDs, and PCB FR4 for the case, the cost of each half without switches or caps can be reduced to under $20 when purchased at volume.
  • Options. The Zen rev2 comes with rotary encoder support, SSD1306 OLED pinout, USB-C or TRRS interconnect, and jumpers to enable compatibility with the QMK Proton-C and the Keeb.io Elite-C

Keyboard Maintainer: Legonut Hardware Supported: Zen rev1, Zen rev2 Hardware Availability: RGBKB.net

A build guide and more info for this keyboard can be found here: Zen Build Guide.

Make example for this keyboard (after setting up your build environment):

make rgbkb/zen/rev2:default

To build for a Proton-C:

make rgbkb/zen/rev2:default CTPC=yes

Note: The Proton-C does not have split keyboard, or encoder support. Also OLED driver support is untested. Will update as status changes.

See build environment setup then the make instructions for more information.