Figured I should do a Black Friday sale also. No coupon needed, sale ends December 1st.

$10 off Bad Wings Kits

$5 off Cut Slope Kits

$5 off Cut Slope PCBs

I'm not going to delete any of the posts relating to the past days drama, but they are locked and any future posts about it will be removed.

KiCad keyboard tutorials

I've posted a couple times about Cut Slope, but one last post to announce that I've released the source code today.

I've got a couple of the prototypes left if you're interested in getting one without getting a whole order fabbed.

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

Integrated RP2040 design guide by Sleepdealr

By Sadek Baroudi, from KBD.NEWS 2022 Advent Calendar

By Pete Johanson, from KBD.NEWS 2022 Advent Calendar

Technically not an ergo board, but in it's current setup I'm using it as a one handed gamepad. That makes it ergo, right?

After a year off from gaming, I've been itching to play. While designing some sort of gamepad, I realized I had basically already designed what I was wanting - Chaz.

After tossing ZMK and an adjusted keymap on it, I think it'll work well enough while I think about what I really want in a gamepad. If, for some godawful reason, you want one of these - I've got a few kits up on my site or if you think you want five of this abomination, it's Open Source.

My latest design - Cut Slope.

• integrated RP2040, 16MB flash
• Choc spaced, ortho-ish with dropped and splayed pinkies
• Full color, 240x320 display

I've got a few of the prototypes listed on my shop if anyone is interested in grabbing one: https://shop.hazel.cc/products/cut-slope

Hardware wise, Cut Slope is fully functional. Screen works, just need to figure out what I want to put on it.

Still working on a full case, but printed a quick tray for peace of mind while using it.

Just got my first embedded design in and it works!

Embedded RP2040. ortho-ish layout with dropped and splayed pinkies, thumb fan, GMT-020 display (🤞).

Now to figure out Quantum Painter and build a case.

Nothing super exciting, just a choc spaced QAZ. Using the new set from fkcaps.com to get all the needed sizes.

Open Source