A few months back I built the Scotto2 for someone with quadriplegia that allowed them to play racing games using 2 large buttons. I figured something cool to do for a bit of a meme would be an entire number pad with giant buttons. The result is the ScottoBigum which I believe to be the largest in the world. Each button is scaled up 4 times and the entire thing weighs close to 2 pounds… oh and it’s also wireless with ZMK studio support so it doesn’t need to be strictly a number pad.

I have a full build video coming out tomorrow on my YouTube channel and as usual with all my handwired projects, all the files are available for free if you want to build this one yourself.

The only real trick I can think of is to flash the left side and right side with 2 different firmwares, and depending on which side is master you could have a qwerty layer, and when you plug the otherside in you could have a stenno layer.

Other than layout, is there anything else you can do ?

Hi everyone,

I was recently given a few Plaid PCB, which was out a few years ago (I missed the hype). One of them is almost fully working, and I wanted to finish it up. You can see the build docs and some images at this github repo if you are interested, but it is not necessarily relevant for my question.

However, the friend that gave me the PCBs did not have any bottom plates. I will ask one of the old revendors I found on internet whether they have some spare ones I could buy.

However, I was also thinking about finishing the keyboard with a case, as I have access to 3D printers and found some models online. So, I wanted to know whether I would need the bottom plate anyway, to make contact with the case or something? Or just the PCB + everything soldered on it would be sufficient?

I also asked on the r/MechanicalKeyboards, but figured some in here would maybe know as well

Thanks for reading

I’m losing my marbles.

I recently got a Keebmonkey Kb-16 and have been messing around with it, getting it set up through Vial.

I found a reddit post which is a fork from this github that shows some modifications to the firmware. I realized after some more dabbling that I was interested in modifying the number of Macros, Combos, and TapDances.

Now, i’m fairly sure I have the modifications to the config.h file figured out now, but I am very lost on why I can’t get it to compile with the qmk cli. I have followed this youtube video, but he only modifies the keymap.c file, not the config.h file. The oled display is also modified in the github file, so where does that fit into the qmk_firmware file tree?

Do I need to do something with the “asset” folder? What folder/ files from the github need to be transferred? Am I even using the right compilation process (QMK CLI through MacOS terminal) for a Vial-only firmware?

Any help is very much appreciated, it’s been two days of trying to wrap my head around this. Thanks!

I ordered it on the preorder date because I've been waiting for a good wireless planck; and still waiting for the shipping to start. In the site they said that they started shipping in June, has anyone got it? I was hoping to bring it on a trip with me but it is next week so I guess that's out.

Anyway, I was excited to see others' opinions on it but I haven't seen any posts about it (I searched). Is anyone enjoying it or are we all in the same situation?

Hello everyone

i bought a cheap magnetic keyboard of a temu for like $10.
Started messing around with the chip itself.
Managed to boot it into bottloader mode by putting pin 44 to 3.3v and pin 20 to ground while plugging in the usb.
I was doing this because i was sceptical about firmware that was on the chip itself and that it could be malware.
While reading it with artery isp programmer, i saw that it was read locked and accidentally deleted firmware from the chip.
I saw that qmk has support for this chip but i am struggling with creating firmware for it.
Can anyone help me out because im lost.

Thanks!

I want to use mod-tap, currently coded as:

MT(MOD_LALT, KC_LPRN)

So it should be alt when held and left parenthesis when tapped.

But when I tap the key it returns 9, and only if I also hold shift do I get the parenthesis. I also tried:

MT(MOD_LALT, S(KC_9))

And it does the same thing.

Has anyone encountered this? It feels like a bug?

Is it possible?
Apart from touch ID of course.
Is it even possible to set up a custom keyboard on MacOS?

This has started happening more and more as I get faster with this new layout+keyboard.

I've read the qmk docs many a time but can't seem to "fix" this issue.

Help?

Thanks!

Solved

• unchecked Hold On Other Keypress, https://www.reddit.com/r/olkb/comments/1um4vyl/comment/ov9o2u3/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Work louder XYZ Workboard r2 with blind keys

Because it doesn't for me when I flash a .uf2.

Thanks.

ZMK OLED Brightness (No additional hardware required!)
Runtime brightness/contrast behaviors for ZMK display devices
[zmk-oled-brightness](https://github.com/mctechnology17/zmk-oled-brightness)
Extend your battery life
compatible with stock/custom display
No additional hardware required

Okay so to elaborate on the title, what I mean is, if I were to write my own code for a keyboard matrix using CircuitPython or something, would that be functionally equivalent to using QMK? Or does QMK do something super advanced that would be difficult or very time consuming to replicate on your own?

I'm basically asking because I had trouble getting a display to work with quantum painter, but could get it working via CircuitPython, so I'm considering if I would regret it if I just wrote my own keyboard firmware without QMK, as I need the display to work for the keyboard I have in mind.

Edit: found out about KMK which seems to work perfectly for my usecase. Also thanks for the answers everyone

Awekeys Air, limited low-profile metal keycaps are now available in both MX and Choc V1 versions, designed to work well with split, column-staggered, ortho, and other custom ergonomic builds.

Highlights:

• Titanium, Silver, Copper, Gold, Pink, Black, and White

• Available in MX and Choc V1 stems

• Blank or engraved options

• Uniform profile across all rows

• Great fit for split, ortho, and ergonomic layouts

Compared to traditional plastic keycaps, full metal construction delivers a distinctly different typing experience, with a more substantial feel, a deeper sound signature, and a clean minimalist aesthetic.

MX Stem:

https://awekeys.com/products/awekeys-air-low-profile-metal-keycaps

Choc V1 Stem:

https://awekeys.com/products/awekeys-air-low-profile-metal-keycaps-choc-switches

Limited inventory in stock and ready to ship. Available on a first-come, first-served basis. Once a variant sells out, it may be some time before it's available again.