diff --git a/blog/New-Keyboard!/index.html b/blog/New-Keyboard!/index.html new file mode 100644 index 0000000..8fecc7f --- /dev/null +++ b/blog/New-Keyboard!/index.html @@ -0,0 +1,228 @@ + + + 'New Keyboard!' + + + + +

New Keyboard!

+ tl;dr show me the board +

+ Throughout the past few years I've hopped from keyboard to keyboard + initally as a need for something to type on, but eventually as an obession + with the sound and feel which to this day I cannot shake. +

+

Keyboard #1

+

+ I started on a Razer Cynosa Chroma which as far as I can tell is no longer + for sale. But for the sake of context you should know that it's a 100% + membrane keyboard with per key backlighting. For a starter keyboard it was + fine, but looking back any old office keyboard would've worked and the + $40(?) that I spent on it was not worth it. But who cares, lets go to the + next keyboard! +

+

Keyboard #2

+

+ After being pushed by a friend who was obsessed interested in + keyboards I finally took the plunge and built my first custom keyboard. + This keyboard was a what I thought would be best after using a membrane + for over two years (I had very little clue what I was doing). I ended up + choosing a TKL board called the NINJA87BT which came with gateron milky + yellow switches. This may not sound custom, but then I went and ordered + some very very expensive switches called Helios v2s which are very quiet + and so soft to type on. I also bought some keycaps with legends printed + on the side nothing too expensive, but very nice to look at. Because this + was my first board I had no clue what I was doing and I ended up spending + around $300... +

+

Keyboard #3

+

+ I started thinking about the future and how I really needed to take care + of the hands that I use every day for programming. Though I wanted to go + fully ergonomic, like where I'm at now, I chose to pace myself and decided + to go with a UHK 60v2. It was expensive, but it promised something + spectacular: a split keyboard without the ortho keywells and qmk + configuration of my current keyboard which would've been very hard to + switch to coming from a normal TKL. Instead of sticking with the cherry + reds it came with I put my Helios in (because they are still the best + switches I've ever felt). While this board was not nearly as custom as my + last I was able to enjoy it much more knowing I was not going to get + carpel tunnel halfway through my life. +

+

+ I ended up using this board for about a year and a half until around mid + July of 2025 when I updated the firmware for the first time since getting + the board and it caused the keyboard to start crashing every once in a + while. I tried to roll back to the version I was using before, but my + configuration wasn't able to migrate back. So I decided it was time to + move on to the keyboard I'd been dreaming of making. +

+

Keyboard #4 (my current one)

+

+ The keyboard I've been typing this post on is a dactyl manuform 4x5, and + It's my first truly hand built keyboard. I 3d printed the case, sanded, + primed, painted (although it did not hide the layer lines very well), and + wired. Wiring was a bit tricky but thanks to the pictures in the + github repo + I was able to do it without too much trouble. +

+ + +

+ After finishing the wiring, which took around 12 hours, I tried to flash + qmk to both halves. At which point realized that the right half had the + rows wired to the arduino pro micro in reverse order. After fixing the + slight hiccup I flashed and viola a working keyboard. I then put on some + black legend-less keycaps, and here is the final(ish) result: +

+ +

+ The ish in final(ish) is because I've yet to add a baseplate which would + add some much needed weight so the halves doesn't slide across my desk, + but for now I'm happy with it. +

+

Build your own

+

+ Incase you're reading this in the hopes of some tips for building your + own here they are: +

+

+

+ When it comes to using my keyboard it's setup for typing as that's what I + do on it it most of the time, however when I play games things get a bit + tricky. For games where I can remap the keys I shift every key over by one + except for the keys on the bottom row, and then I set the sprint key as a. + For the games where I can't remap the keys... I just stop playing them. + If I had more of an interest in gaming I would've gone with the 4x6 as + 6 more keys it offeres could've been really nice. +

+

+ For those curious about the specs: I decided on a rj9 port mainly because + I like the look of them over the TRRS cables everyone seems to be using + nowadays. For the pro micro I went with the cheapest one I could find + with a usb-c port, you can't really go wrong here. As for the actual + layout my qmk config is below incase you really wanna know how I type: +

+ 
+/*
+This is the c configuration file for the keymap
+
+Copyright 2012 Jun Wako 
+Copyright 2015 Jack Humbert
+
+This program is free software: you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation, either version 2 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program.  If not, see .
+*/
+
+#include QMK_KEYBOARD_H
+
+bool process_record_user(uint16_t keycode, keyrecord_t* record) {
+  switch (keycode) {
+    case KC_BSPC: {
+      static uint16_t registered_key = KC_NO;
+      if (record->event.pressed) {  // On key press.
+        const uint8_t mods = get_mods();
+#ifndef NO_ACTION_ONESHOT
+        uint8_t shift_mods = (mods | get_oneshot_mods()) & MOD_MASK_SHIFT;
+#else
+        uint8_t shift_mods = mods & MOD_MASK_SHIFT;
+#endif  // NO_ACTION_ONESHOT
+        if (shift_mods) {  // At least one shift key is held.
+          registered_key = KC_DEL;
+          // If one shift is held, clear it from the mods. But if both
+          // shifts are held, leave as is to send Shift + Del.
+          if (shift_mods != MOD_MASK_SHIFT) {
+#ifndef NO_ACTION_ONESHOT
+            del_oneshot_mods(MOD_MASK_SHIFT);
+#endif  // NO_ACTION_ONESHOT
+            unregister_mods(MOD_MASK_SHIFT);
+          }
+        } else {
+          registered_key = KC_BSPC;
+        }
+
+        register_code(registered_key);
+        set_mods(mods);
+      } else {  // On key release.
+        unregister_code(registered_key);
+      }
+    } return false;
+  }
+  return true;
+}
+
+#define _BASE 0
+#define _RAISE 1
+#define _LOWER 2
+
+#define SFT_ESC  SFT_T(KC_ESC)
+#define CTL_BSPC CTL_T(KC_BSPC)
+#define ALT_SPC  ALT_T(KC_SPC)
+#define SFT_ENT  SFT_T(KC_ENT)
+
+#define KC_ML KC_MS_LEFT
+#define KC_MR KC_MS_RIGHT
+#define KC_MU KC_MS_UP
+#define KC_MD KC_MS_DOWN
+#define KC_MB1 KC_MS_BTN1
+#define KC_MB2 KC_MS_BTN2
+
+#define RAISE MO(_RAISE)
+#define LOWER MO(_LOWER)
+
+const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
+    [_BASE] = LAYOUT(
+        KC_Q,    KC_W,    KC_E,    KC_R,    KC_T,                                         KC_Y,    KC_U,    KC_I,    KC_O,    KC_P,
+        KC_A,    KC_S,    KC_D,    KC_F,    KC_G,                                         KC_H,    KC_J,    KC_K,    KC_L,    KC_SCLN,
+        KC_Z,    KC_X,    KC_C,    KC_V,    KC_B,                                         KC_N,    KC_M,    KC_COMM, KC_DOT,  KC_QUOT,
+                          KC_LBRC, KC_RBRC,                                                        KC_MINS, KC_EQL,
+                                                     KC_LCTL, KC_LSFT, KC_TAB, RSFT_T(KC_ESC),
+                                                     KC_SPC,  KC_LALT,  KC_ENT,  KC_BSPC,
+                                                     LOWER,   KC_LGUI,   KC_RGUI, RAISE
+    ),
+
+    [_RAISE] = LAYOUT(
+        QK_BOOT, KC_MPRV, KC_MSTP, KC_MPLY, KC_MNXT,                                      KC_PGDN, MS_BTN1, MS_BTN2, KC_PGUP, KC_VOLU,
+        _______, MS_LEFT, MS_DOWN, MS_UP,   MS_RGHT,                                      KC_LEFT, KC_DOWN, KC_UP,   KC_RGHT, KC_MUTE,
+        _______, MS_WHLL, MS_WHLD, MS_WHLU, MS_WHLR,                                      KC_BSLS, KC_SLSH, KC_LBRC, KC_RBRC, KC_VOLD,
+                 _______, _______,                                                                          _______,  _______,
+                                   _______, _______,                                      _______, _______,
+                                                     _______, _______,  _______, _______,
+                                                     _______, _______,  _______, _______
+    ),
+
+    [_LOWER] = LAYOUT(
+        KC_EXLM, KC_AT,   KC_HASH, KC_DLR,  KC_PERC,                                      KC_CIRC, KC_AMPR, KC_ASTR, KC_LPRN, KC_RPRN,
+        KC_1,    KC_2,    KC_3,    KC_4,    KC_5,                                         KC_6,    KC_7,    KC_8,    KC_9,    KC_0,
+        KC_F1,   KC_F2,   KC_F3,   KC_F4,   KC_F5,                                        KC_F6,   KC_F7,   KC_F8,   KC_F9,   KC_F10,
+                 KC_F11,  KC_F12,                                                                           KC_GRV,  _______,
+                                   _______, _______,                                      _______, _______,
+                                                     _______, _______,  _______, _______,
+                                                     _______, _______,  _______, _______
+    )
+};
+
+ + diff --git a/blog/New-Keyboard!/pics/final-ish.jpg b/blog/New-Keyboard!/pics/final-ish.jpg new file mode 100644 index 0000000..1d0fded Binary files /dev/null and b/blog/New-Keyboard!/pics/final-ish.jpg differ diff --git a/blog/New-Keyboard!/pics/sanded.jpg b/blog/New-Keyboard!/pics/sanded.jpg new file mode 100644 index 0000000..765b2b5 Binary files /dev/null and b/blog/New-Keyboard!/pics/sanded.jpg differ diff --git a/blog/New-Keyboard!/pics/wiring.jpg b/blog/New-Keyboard!/pics/wiring.jpg new file mode 100644 index 0000000..bd872a1 Binary files /dev/null and b/blog/New-Keyboard!/pics/wiring.jpg differ diff --git a/blog/rss.xml b/blog/rss.xml index b61badb..606d470 100644 --- a/blog/rss.xml +++ b/blog/rss.xml @@ -11,6 +11,228 @@ + + 'New Keyboard!' +https://squi.bid/blog/New-Keyboard!/index.html +https://squi.bid/blog/New-Keyboard!/index.html +Tue, 12 Aug 2025 03:23:38 -0400 + + + 'New Keyboard!' + + + + +

New Keyboard!

+ tl;dr show me the board +

+ Throughout the past few years I've hopped from keyboard to keyboard + initally as a need for something to type on, but eventually as an obession + with the sound and feel which to this day I cannot shake. +

+

Keyboard #1

+

+ I started on a Razer Cynosa Chroma which as far as I can tell is no longer + for sale. But for the sake of context you should know that it's a 100% + membrane keyboard with per key backlighting. For a starter keyboard it was + fine, but looking back any old office keyboard would've worked and the + $40(?) that I spent on it was not worth it. But who cares, lets go to the + next keyboard! +

+

Keyboard #2

+

+ After being pushed by a friend who was obsessed interested in + keyboards I finally took the plunge and built my first custom keyboard. + This keyboard was a what I thought would be best after using a membrane + for over two years (I had very little clue what I was doing). I ended up + choosing a TKL board called the NINJA87BT which came with gateron milky + yellow switches. This may not sound custom, but then I went and ordered + some very very expensive switches called Helios v2s which are very quiet + and so soft to type on. I also bought some keycaps with legends printed + on the side nothing too expensive, but very nice to look at. Because this + was my first board I had no clue what I was doing and I ended up spending + around $300... +

+

Keyboard #3

+

+ I started thinking about the future and how I really needed to take care + of the hands that I use every day for programming. Though I wanted to go + fully ergonomic, like where I'm at now, I chose to pace myself and decided + to go with a UHK 60v2. It was expensive, but it promised something + spectacular: a split keyboard without the ortho keywells and qmk + configuration of my current keyboard which would've been very hard to + switch to coming from a normal TKL. Instead of sticking with the cherry + reds it came with I put my Helios in (because they are still the best + switches I've ever felt). While this board was not nearly as custom as my + last I was able to enjoy it much more knowing I was not going to get + carpel tunnel halfway through my life. +

+

+ I ended up using this board for about a year and a half until around mid + July of 2025 when I updated the firmware for the first time since getting + the board and it caused the keyboard to start crashing every once in a + while. I tried to roll back to the version I was using before, but my + configuration wasn't able to migrate back. So I decided it was time to + move on to the keyboard I'd been dreaming of making. +

+

Keyboard #4 (my current one)

+

+ The keyboard I've been typing this post on is a dactyl manuform 4x5, and + It's my first truly hand built keyboard. I 3d printed the case, sanded, + primed, painted (although it did not hide the layer lines very well), and + wired. Wiring was a bit tricky but thanks to the pictures in the + github repo + I was able to do it without too much trouble. +

+ + +

+ After finishing the wiring, which took around 12 hours, I tried to flash + qmk to both halves. At which point realized that the right half had the + rows wired to the arduino pro micro in reverse order. After fixing the + slight hiccup I flashed and viola a working keyboard. I then put on some + black legend-less keycaps, and here is the final(ish) result: +

+ +

+ The ish in final(ish) is because I've yet to add a baseplate which would + add some much needed weight so the halves doesn't slide across my desk, + but for now I'm happy with it. +

+

Build your own

+

+ Incase you're reading this in the hopes of some tips for building your + own here they are: +

+

+

+ When it comes to using my keyboard it's setup for typing as that's what I + do on it it most of the time, however when I play games things get a bit + tricky. For games where I can remap the keys I shift every key over by one + except for the keys on the bottom row, and then I set the sprint key as a. + For the games where I can't remap the keys... I just stop playing them. + If I had more of an interest in gaming I would've gone with the 4x6 as + 6 more keys it offeres could've been really nice. +

+

+ For those curious about the specs: I decided on a rj9 port mainly because + I like the look of them over the TRRS cables everyone seems to be using + nowadays. For the pro micro I went with the cheapest one I could find + with a usb-c port, you can't really go wrong here. As for the actual + layout my qmk config is below incase you really wanna know how I type: +

+ 
+/*
+This is the c configuration file for the keymap
+Copyright 2012 Jun Wako 
+Copyright 2015 Jack Humbert
+This program is free software: you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation, either version 2 of the License, or
+(at your option) any later version.
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+GNU General Public License for more details.
+You should have received a copy of the GNU General Public License
+along with this program.  If not, see .
+*/
+#include QMK_KEYBOARD_H
+bool process_record_user(uint16_t keycode, keyrecord_t* record) {
+  switch (keycode) {
+    case KC_BSPC: {
+      static uint16_t registered_key = KC_NO;
+      if (record->event.pressed) {  // On key press.
+        const uint8_t mods = get_mods();
+#ifndef NO_ACTION_ONESHOT
+        uint8_t shift_mods = (mods | get_oneshot_mods()) & MOD_MASK_SHIFT;
+#else
+        uint8_t shift_mods = mods & MOD_MASK_SHIFT;
+#endif  // NO_ACTION_ONESHOT
+        if (shift_mods) {  // At least one shift key is held.
+          registered_key = KC_DEL;
+          // If one shift is held, clear it from the mods. But if both
+          // shifts are held, leave as is to send Shift + Del.
+          if (shift_mods != MOD_MASK_SHIFT) {
+#ifndef NO_ACTION_ONESHOT
+            del_oneshot_mods(MOD_MASK_SHIFT);
+#endif  // NO_ACTION_ONESHOT
+            unregister_mods(MOD_MASK_SHIFT);
+          }
+        } else {
+          registered_key = KC_BSPC;
+        }
+        register_code(registered_key);
+        set_mods(mods);
+      } else {  // On key release.
+        unregister_code(registered_key);
+      }
+    } return false;
+  }
+  return true;
+}
+#define _BASE 0
+#define _RAISE 1
+#define _LOWER 2
+#define SFT_ESC  SFT_T(KC_ESC)
+#define CTL_BSPC CTL_T(KC_BSPC)
+#define ALT_SPC  ALT_T(KC_SPC)
+#define SFT_ENT  SFT_T(KC_ENT)
+#define KC_ML KC_MS_LEFT
+#define KC_MR KC_MS_RIGHT
+#define KC_MU KC_MS_UP
+#define KC_MD KC_MS_DOWN
+#define KC_MB1 KC_MS_BTN1
+#define KC_MB2 KC_MS_BTN2
+#define RAISE MO(_RAISE)
+#define LOWER MO(_LOWER)
+const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
+    [_BASE] = LAYOUT(
+        KC_Q,    KC_W,    KC_E,    KC_R,    KC_T,                                         KC_Y,    KC_U,    KC_I,    KC_O,    KC_P,
+        KC_A,    KC_S,    KC_D,    KC_F,    KC_G,                                         KC_H,    KC_J,    KC_K,    KC_L,    KC_SCLN,
+        KC_Z,    KC_X,    KC_C,    KC_V,    KC_B,                                         KC_N,    KC_M,    KC_COMM, KC_DOT,  KC_QUOT,
+                          KC_LBRC, KC_RBRC,                                                        KC_MINS, KC_EQL,
+                                                     KC_LCTL, KC_LSFT, KC_TAB, RSFT_T(KC_ESC),
+                                                     KC_SPC,  KC_LALT,  KC_ENT,  KC_BSPC,
+                                                     LOWER,   KC_LGUI,   KC_RGUI, RAISE
+    ),
+    [_RAISE] = LAYOUT(
+        QK_BOOT, KC_MPRV, KC_MSTP, KC_MPLY, KC_MNXT,                                      KC_PGDN, MS_BTN1, MS_BTN2, KC_PGUP, KC_VOLU,
+        _______, MS_LEFT, MS_DOWN, MS_UP,   MS_RGHT,                                      KC_LEFT, KC_DOWN, KC_UP,   KC_RGHT, KC_MUTE,
+        _______, MS_WHLL, MS_WHLD, MS_WHLU, MS_WHLR,                                      KC_BSLS, KC_SLSH, KC_LBRC, KC_RBRC, KC_VOLD,
+                 _______, _______,                                                                          _______,  _______,
+                                   _______, _______,                                      _______, _______,
+                                                     _______, _______,  _______, _______,
+                                                     _______, _______,  _______, _______
+    ),
+    [_LOWER] = LAYOUT(
+        KC_EXLM, KC_AT,   KC_HASH, KC_DLR,  KC_PERC,                                      KC_CIRC, KC_AMPR, KC_ASTR, KC_LPRN, KC_RPRN,
+        KC_1,    KC_2,    KC_3,    KC_4,    KC_5,                                         KC_6,    KC_7,    KC_8,    KC_9,    KC_0,
+        KC_F1,   KC_F2,   KC_F3,   KC_F4,   KC_F5,                                        KC_F6,   KC_F7,   KC_F8,   KC_F9,   KC_F10,
+                 KC_F11,  KC_F12,                                                                           KC_GRV,  _______,
+                                   _______, _______,                                      _______, _______,
+                                                     _______, _______,  _______, _______,
+                                                     _______, _______,  _______, _______
+    )
+};
+
+ +]]> + + + 'Serializing data in C' https://squi.bid/blog/Serializing-data-in-C/index.html