void_switch VS zmk

As far as I know the "other times this has been tried" all have had individual displays (and controllers) in each key. The difference being that here there is just one panel under the whole board with most of the parts above the display being transparent. This approach should be far less complicated to build, more robust and cheaper.

Honestly, I don't think I need an LCD in my keyboard but I'd quite like to have a go on some mAgLeV hall effect switches! On that note, if you like magnets and/or keebs you might be interested in Void switches[0] -- 3D printable hall effect switches

[0] https://github.com/riskable/void_switch

I made a 3D printed keyboard with 3D printed switches + stabilizers and sent it to Chyrosran22 for review.

Longer story: Chyros suggested about 5 months ago that I make an "ultra bright" RGB LED keyboard that used my 3D printable Void Switch design (https://github.com/riskable/void_switch) so he could do a fun "RGB" video. I designed the PCB, the case, the top plate, switches, stabilizers, rotary encoders, etc from scratch and the keyboard in the video is the result.

The keyboard hardware was actually done within the first 3 months but I needed some extra time to add lighting effects to the firmware to meet the "fancy RGB" requirement :)

It's actually my 2nd normal-size analog keyboard design. The first being my Riskeyboard 70 which used a MAX7219 LED matrix display and regular (non-XL) ws2812b RGB LEDs: https://gfycat.com/firsthanduniformeasteuropeanshepherd

Not shown in his video: The top plates have no electronics in them which means they're completely waterproof and can be washed in a sink with soap & water: https://gfycat.com/unconsciousvigilantkinglet . Also, the incremental rotary encoder and absolute rotary encoder (aka "the selection knob") are analog as well (using a custom design).

The keycaps were 3D printed as well and designed using my Keycap Playground: https://github.com/riskable/keycap_playground

Haha... So I can use my awesome contactless magnetic separation+levitation 3D printable Void Switch design of course:

https://github.com/riskable/void_switch

...and so I can do this:

https://gfycat.com/costlyglaringhyracotherium

..and this:

https://gfycat.com/unconsciousvigilantkinglet

You can clean it in the sink with soap and water because there's no electrical contacts or components in the switches.

... But that's really just scratching the surface of what it can do.

Answering myself: the void switches by riskable can be used as analogic switches. It's an open source project: https://github.com/riskable/void_switch

If you wanted to try to do something DIY you could build something with riskable's void switch and adapt his firmware to do this. Since hall effect sensors are analogue, you program the set and reset point and can set multiple. Although, I do wonder how easy it is to reliably use this feature, but that's the fun in experimentation.

> "Instead of developing, manufacturing and keeping physical buttons in stock for years to come, car manufacturers are keen on integrating more functions into a digital screen which can be updated over time."

That's lame. 3D printing buttons is a very quick and simple solution to that problem. They can even use my lasts-forever, contactless analog hall effect Void Switch design: https://github.com/riskable/void_switch

Keeping buttons--something that's so quick and easy to 3D print--in stock seems like a huge waste of storage space.

Maybe these?

I saw this same question was posted half a year ago and was wondering if anyone knew of any updates. Looks like this development branch of ZMK is stalled.

Not sure which information you mean, but here goes. Nice!Nano v2 Pinout (shows Arduino pin mapping). Nice!View Getting Started (explains how to remap the CS pin for a non-native shield like Corne). The overlay file where "cs-gpios" is set for the nice_view_adapter in ZMK. If you look at the Corne Schematic, you'll see as shown in the labels in this image that the bottom two pins (B2, B4, B5, B6) don't appear to be used for a column, row, or the OLED header. But the only way to really verify is to pull the KiCAD file for your Corne version and check yourself. I think D0 ("Data") should work. It appears to go to an optional I2C connection.

if you built the firmware using the corne shield that might be the issue. the splitkb aurora corne has a different pinout.

Depending on a controller you will be programming features of your keyboard using QMK or ZMK (there are alternatives but these two are the most popular). You can check documentation of these tools regarding display but some nice sum up is in the related article on splitkb: https://docs.splitkb.com/hc/en-us/articles/360010533820-What-can-you-use-an-OLED-display-for-

corne-ish zen, the group buy is long over but there is an extras round coming up. I suggest going on the discord if you're interested in knowing when they'll be available for sale. it is a prebuilt so you can just buy it whole and have it ready to use out of the box and runs on ZMK.

I would be pretty interested in a wireless Ploopy. Especially if it runs ZMK since that is what I currently use for a split keyboard. It would be pretty awesome to link the macros and layers between my keyboard and mouse if the mouse could be a second peripheral "half" of the keyboard. Admittedly, ZMK's mouse support is still kinda beta, but the wireless support is amazing.

The other firmware I wrote for my wireless programable keyboard based on ZMK.

The code to enable the second encoder is outlined in this Pull Request https://github.com/zmkfirmware/zmk/pull/728, but since it's not in the main ZMK codebase, to use this feature you need to roll your own ZMK with this PR included. And luckily there is already a kind person who did this in https://github.com/narze/zmk/pull/2

Try the Kinesis Advantage Pro because you can customize with ZMK. If you have DIY skills and want to customize event further. There's the open source version. Spit keyboards with QMK are good too.

Wired split is not supported by ZMK yet. See https://github.com/zmkfirmware/zmk/issues/1110