The primary motivation behind v2 was to simplify the build process by ditching the XIAO/Shift Register for an integrated STM32 microprocessor. The only parts that need soldered are the hot swap sockets.
Features
- 36 key unibody split
- Choc spaced, column staggered, splayed
- Cirque touchpad support
- Integrated microprocessor
- Built in mounting standoffs
- Preflashed with VIAL
Kits include all required hardware except switches, keycaps and case.
Base Kit - $50
Cirque Kit - $65
Printed Cases are available in every color - as long as the color is purple or black.
Black ABS - $35
Purple ABS - $35
Purple Sparkle PLA - $25
Matte Black PLA - $25
MJF printed ChicagoSteno.
Over the last couple months I've been working on the next version of Bad Wings, the board I've been daily driving for over a year now. Using the stm32f072 onboard and has cirque support (which wasn't working until a couple hours ago - thanks GeorgeN!). I've been using it for two weeks now and I'm happy.
Now that the cirque is working, I need to design a new case.
for sure. I don't know if people are doing it because it's better, or because they're trying to justify having dual trackballs.
I've seen people use one trackball for normal mouse type usage, and the other for scrolling.
I second this. I also prefer ZMK and use it on my wired boards whenever possible.
cross-posted from: https://keeb.lol/post/1338
cross-posted from: https://lemmy.world/post/2498887
Hey all! I've been working on a new standard for interconnecting a main keyboard pcb to modules.
What does this mean? If a keyboard pcb supports the interface via a connector and some basic wiring, it will allow you to use the available open source modules.
I designed an open source keyboard called vulpes minora to prove out the concept, along with 4 modules that you can connect to it. Even before officially announcing it, there are have been 3 keyboards that have adopted it, along with 2 modules developed (Great work by zzeneg , Ariamelon, and Ben!)
Here is a link to see the full list of supported keyboards and modules.
The VIK repository is here, and it highlights how it works, how to implement support for it (for both a keyboard and a module), along with working examples.
https://github.com/sadekbaroudi/vik
If more people adopt it, more people will be incentivized to make modules, and we'll all benefit from it. No more days of "hey, check out this cirque trackpad, let's figure out a way to hack it onto existing boards!". Instead, it will be "Hey, we should design a VIK module that supports this new cool thing!". Then people will be able to just swap in the new thing, write some basic firmware, and fold it into their existing keyboards.
Thinking out loud here, but if it starts to get popular, we could even work with the QMK folk to potentially create some standardized way of supporting modules (from a firmware perspective) in a more streamlined way.
Anyway, questions and feedback very much welcome.
If you'd like to discuss it in more depth, please feel free to join the fingerpunch discord server, and chat me up (sadekbaroudi) in the #vik channel.
https://fingerpunch.xyz/discord
There was a recent article published on kbd.news if anyone wants to look through that as well
much appreciated!
I love all of these ideas!
It wasn't until this build (I've done several xswitch designs now) that I started to really like them. I love the way they feel, but they're too heavy for me to use all day. This build has been my travel board, where I'm only using a keyboard for 30-60 minutes and I love it.
These are the Kailh XSwitch. I haven't tried the new cherry ulp yet.
I haven't personally tried, but I have heard a lot of people say that switching between isn't too bad. It can take a minute or two for the memories to come back though.
I've also heard that using different keymap layouts (ie, QWERTY vs COLEMARK) on different physical layouts. QWERTY for typical rowstag, COLEMARK for ergo.
The customizer service is top notch! I love the set that I got. Good luck everyone!
view more: next ›