PCBs are incredibly cheap to print (<$25 shipped for me to print at https://jlcpcb.com, IIRC), and he shows you how to do some mods to the schematic using KiCad [1].
BV also has some crazier minimal keyboard designs like this 18-key split one with lots of layers: https://www.youtube.com/watch?v=yNOGEtqn85o
[0]: https://www.youtube.com/watch?v=JqpBKuEVinw [1]: https://www.kicad.org/
It's ultimately the same process I used to create my Analog Hall Effect Keyboard that was reviewed by Chyrosran22 recently: https://youtu.be/iv6Rh8UNWlI
https://wiki.ai03.com/books/pcb-design/page/pcb-guide-part-1...
Once you build your first little macropad, and verify that your design is generally correct, you can fork the repo you created and pretty much copy/paste your MCU region, and build a new grid of keys around it. The guide also gave me good tips on what to have assembled, and what to hand-solder, to be able to cut some costs.
The other piece of the puzzle for me is curvature. On a flat keyboard there is more stretching or physically moving but adding in a bit of curvature helps cut down on that.
For a few years now I have been using a hand wired Dactyl-ManuForm [1] and it has been great. At least for writing / programming. I go back to a regular keyboard for gaming purposes.
I 3D printed adapters for my chair arm rests so the keyboards sit at the front of each rest, right where my hands naturally want to be. I can then recline my chair a bit and type for hours without sitting forward/hunched over the desk.
I don't know that I'm a fan of the complete split like this, but I definitely agree with your overarching point.
I've designed my own as well but just went with the traditional key matrix with a diode per switch. Works well enough for the current size.
I made two videos talking about how I design my analog keyboard PCBs and how I'm using analog multiplexers here: https://youtu.be/TfKz_FbZWLQ
They do avoid having a diode per key, in exchange for needing a chip for N keys, where n is the number of of parallel inputs in your parallel to serial shift register.
They can also save IO lines. Obviously with if using chainable shift registers, you can have an unlimited number of keys with just 3 IO lines.
More realistic of course, would be to use several IO lines in parallel. For a 64 key matrix, one could say use 8, 8-bit shift registers, each connected to one input line, plus one output latch line and one output clock line (for a total of 10), vs the 16 lines needed traditional matrix.
8 input lines is nice, because if you pick the I/O lines right, retrieving the values is just a single port read. Making the procedure: latch, (toggle clock twice, read port, write to next location in memory buffer) x8.
There are of course downsides, like shift registers needing more board space than tiny surface mount diodes, but this is not necessarily a deal-killer.
Searching again, looks like zmk added support for the common 595 shift register: https://github.com/zmkfirmware/zmk/pull/1325
Edit: You could avoid using diodes, but diodes increase the number of switches possible via a matrix more than shift registers do by giving you more gpio. I’d imagine one can use both together.
Bucking-Springs
split-keyboard
WHITE backlight under the keys (I can touch type, but after 35+ years I still "gaze unfocused" and take in all the keys)
The tactility is very well defined, and the tactile mechanism (click bar) is IMO better than Cherry-style click jackets, like seen in Cherry Blues.
A split keeb with a white backlight that accepts MX-footprint switches should be simple to find.
Drool over this:
https://youtu.be/oNnW4wED4uU
;-)> This is my gold-tier wish list:
> Bucking-Springs
> split-keyboard
Model M M15: it's split. It's a collector item though.
Similar to the touchpad on the 'Ultimate Hacking Keyboard v2' but standalone without the pogo pins coupling part? [0]
Probably not "small", but it fits between the two halves of my Moonlander quite nicely :)
That thought felt weird in the beginning, but trust me: it works.
I personally just built a keyboard with an integrated trackball however. It’s great!
I'd say if you look at a layout like miryoku https://github.com/manna-harbour/miryoku .. in miryoku, the [] keys are one row up from home row, accessed on a layer. Whereas, putting [] on outer columns, your hand has to move and reach over two rows.
That is, I'd emphasise layering brings more keys to within easy access of the fingers (at the cost of added complexity to use the keyboard, - which not everyone has the taste for).
http://www.keyboard-layout-editor.com/#/gists/8b8dcd36c0abcc... https://gist.github.com/rollcat/8b8dcd36c0abccf430b4160ad899...
For those not familiar, to get down to this low number of keys, some layouts will place modifiers (ctrl, shift, alt, meta) as secondary actions (when the key is held down vs. tapped) on home row keys (asdf, jkl; on QWERTY). The problem is to distinguish a tap from a hold, there's a minimum delay before the key is sent, making it very annoying for fast typists as there may be visible input lag when hitting one of the home row keys.
I forsee a minor surge of full-size split ergos and that's a great thing.
The ones oriented like a mouse wheel, but wide (as opposed to the ones sitting like a volume knob on a mixer) are very natural to use and unobtrusive.
I also use an ortho layout, but find the whole community trying to justify it as better for you ergonomically to be unconvincing. There’s little data that says ortho has any health benefits over staggered. We have data on the position and alignment of the wrist being the biggest factor, and you can achieve this with either style.
> This is the physical layout, so you see QWERTY here. I actually type on Colemak though!
How do you know if someone uses an alternative key layout? They’ll tell you.
I can type near 150wpm, but it is a completely random style that mostly only follows using whatever finger happens to be closest to the next key regardless of which hand it is after leaving every finger wherever it was last used.
In case anyone is interested, there are also people who hand-wire keyboards. This lets you explore funky custom layouts without having to learn the circuit design and manufacturing side. I came across this pretty detailed guide recently. https://www.crackedthecode.co/a-complete-guide-to-building-a...
This kind of article just shows me what I will become in a few years if that first experience indeed succeeds.
IANAL, but if they have a trademark for "NICE" in relation to keyboards, yours may be in violation.
Thank you.
>not cupped
Probably better off going with a Matias then.