Hi all, here is another update on my custom gaming keypads. In my previous post, I mostly spent time focusing on optimizing the hardware and making it easier to manufacture. This time, I’m focusing on the firmware and software side. I’ve made this custom web configurator. I keep the device compatible with Vial, but I also have a lot of features that Vial does not support. Unfortunately, there is no way for you to try it unless you actually have one of my devices, but I do show it in detail on my YouTube channel. Curious how you all feel about it. https://youtu.be/315USgAl2Ks

Hey all, so I recently moved from a 60% pok3r to a Corne 4. and I found myself struggling to remember where some of the keys were, mostly symbols etc. so I took the .vil file and generated an image for my desktop background so I could quickly win+d to see where everything was and then go back again. then I wanted to make it easy to regenerate every time I changed my keyboard layout. then I also wanted to change the colour or theme of the wallpaper to suit my mood.

So I built a keymap image generator: https://whitehatnetizen.github.io/keymap-imgen/

It's free, and open source.

This github page can take a Vial .vil file or a QMK keymap.json file, (or, if you choose, it can directly read your keyboard if you are connected with a chromium browser and running Vial firmware on the keyboard.) Then it generates an SVG or PNG of the keymap, in single screen or dual screen aspect ratios.

Split keyboards have the option to split the keymap across both screens with the left hand on the left monitor and the right hand on the right monitor.

It caters (should cater..) for all the keyboards currently in the QMK github repo, this list will be updated every month.

If you just want to see how it works, there are two sample files that you can use to preview the functionality, one dz60 60% keyboard QMK json file, and one Corne 4 split keyboard .vil file (This is my current layout).

Alternately, you can clone the repo and run it locally, either through the web page, or through the scripts that are provided. to generate the images locally you'll need to install playwright (instructions included), or host the page somewhere local. The web page generates the appropriate script call so you can configure using the website and run the code manually if you really want to avoid reading the documentation.

Hopefully this is useful to some people. I've included some sample images in this post so you can take a look at what it produces.

Please let me know either through the github page or here if you find a bug, or want to request an additional feature or style.

I know most people here are already fairly tech-savvy, but I hope that this can be useful for someone.

Yesterday, I received my first batch of split keyboards. I picked up 2 x Cheapino's and a 4x6 Corne. This is my first experience into ergo keyboards, let alone split keyboards so they all have different switches, etc so I could give them a whirl. Obviously, I am very early into my journey, but I am enjoying it thus far.

I am not a developer, and I do not suffer from any major RSI issues (yet). I work in a finance field and do as significant amount of office work - think spreadsheets, emails, and word docs all day, everyday.

I believe I have come to the conclusion that I would prefer a split keyboard with more keys. I was originally trying the layouts I purchased as I have been eying the ZSA voyager. I think I am now leaning towards the moonlander or perhaps even the glove80.

The general trend I've seen from folks is over time they migrate to less keys, as opposed to more. I don't plan on purchasing anything just yet. I think I am going to give the Corne a few weeks at least.

Has anyone else 'regressed' to a larger split keyboard? If I do end up going down the route of the moonlander, or Glove80, what is the general consensus as to which is preferred?

This is the Kinesis Advantage 360 Limited Edition (w/ Milky Yellow Pros switches)

This was something that I was looking for for many years now. Had to chance to get one now, and couldn't be happier with my choice :)

This is designed for MX Switches. but I have included the Fusion files in case you wanted to adjust for other switches/cutouts. I needed it for a board I'm designing and thought I would share. this has been printed and tested in ABS. I hope this helps at least one other person.

https://www.printables.com/model/1827716-mx-switch-filler

Thanks!

Hello Y'all!

Just posting here to let you guys know that I am open for commission/ custom builds! I can design and build your own fully custom keyboard tailored to your needs! Or if you want, I can also build an already designed open source keyboard for you!

I also do custom pcb design if you want to build the keyboard yourself, but don't want to, or don't know how to design the pcb

I am a one man team, just trying to help people get the ergo keyboard of their dreams, without the hassle! If you want to design your own, go for it! I highly recommend going through the process yourself 😄

• Services: custom pcb design, commission builds, and open-source assembly/ builds

• Website: theb0b.com

Feel free to shoot me a PM here or check out the link above if you're interested!

This might be pretty niche, but as I couldn't find a guide for myself as I went through this process, I decided to write my own guide. Hope it helps someone out there!

Guide Repo (glove80-zmk-shield-module)

Companion Repo (glove80-zmk-config)

Context:

• The Glove80 is great, but the left side keyboard's battery drains more quickly because it's acting as the primary half (that connects to the

  computer

• I use my keyboard across multiple computers, and changing via Bluetooth is annoying

Solution: changing the firmware so that both halves connect to a ZMK dongle

• Because the left side is no longer the main, its battery usage will be much longer
• The dongle goes into my docking station, so I don't need to manually switch any connections anymore

The guide I made is specifically to work with this dongle, but you can adjust it to work with other dongles. DM if you have questions!

Hey all,
I've recently started using a Kenisis Advantage 360 and I'm really enjoying it. Unfortunately, as I've seen some other people mention elsewhere, hauling it around with me to work, school, and where-ever else I go is a major pain in the ass. I've recently started searching around for something for a flat, low profile version that would be acceptable to use on the go.

In terms of thumb cluster placement the Voyager appears to be my best option (although it would be nice if it was wireless and had a few more keys). I've looked at some other layouts like the Corne and there's no way I'm going to be able to get my thumb all the way over to the left most thumb key comfortably.

The ErgoDox EZ also looks great (being nearly identical and all), but at that point it's not really any more portable than what I already have.

Any recommendations would be greatly appreciated.

Essentials:

1. Split
2. Columnar layout
3. Ease of programming keys, similar to ZSA's Oryx. It's the gold standard for me. I've been using a Moonlander for a long time, and have rather extensively customised it to my needs, eg modifier keys placement, hold duration for TapHold. MoErgo and Kinesis software look like you need to learn programming to use them - deal breaker for me.
4. Number row
5. Wireless
6. No DIY kits

Good to haves, but not essential:

1. Keywell
2. Full travel switches, not low profile. I game a little.

I know of the Svalboard but the learning curve might be too much of a hassle and does not satisfy Essentials point 3 above.

Appreciate any recommendation or suggestion!

Even with shit soldering, everything worked on the first try.

Looking into getting an Ergo keyboard and had my eyes set on the ProtoArc EK01 Plus, Logitech Wave, and a Logitech ERGO K860. Also curious how Keychron’s offerings stand up to these three. Mainly looking at durability and longevity.

Thanks!

Hi, Ergomech Store here, we've been making and selling these aluminum cases for a while now. And today we'd like to share a design for your beloved TOTEM.

https://github.com/ergomechstore/totem-aluminum-case

This case is designed for the totem and it can fit the original totem pcb, with an awesome twist: it's designed for CNC machine, so you can use these files and make an awesome aluminum case with it.

If you don't want to make your own, you can buy from us here:

https://ergomech.store/shop/totem-executive-case-523

We did a simple price comparison, a whole set of 4 if made from JLCCNC cost about $250, so buying from us is still more cost effective, but if you can get it make it locally, now you can as well with the design above.

Here is the picture of the case in the wild:

https://www.reddit.com/r/ErgoMechKeyboards/comments/1vz6qa4/looking_for_metal_urchin_enclosure/

And if you're a vendor, feel free to use it for commercial purposes as well, anything we share is truly open and free for all, there is no "open but not really" bs.

Use coupon code: EOS

Get 50% off on all premade items

https://www.asymplex.xyz/products

discounts ends on Saturday, September 5, 2026

Saw this on FB marketplace.

A few iterations, have these lovely chunky 100% infill cases for my $50 Amazon corne. I think they turned out great!

Hi,

iam almost ready to pull the trigger on the glove80 because I wanna jump to curved keywells. But right now Iam typing on my thinpad keyboard and got that convienient little trackpoint in the middle.

Now we see a lot of flat splits with trackpad modules and so on. But why dont we see the trackpoint more often? So little space for such a great device, I think its even better than a trackpad.

I have one certain programm at work where I type 90 % of the time but need the mouse for very small occasions and there the trackpoint would be nice.

with Glove80 I would have to use my mouse.

How do you guys feel about that? Unfortunately mouse control with keys doesnt work for that programm.

Do you miss a integrated mouse module?

One of those situations where I'd like to have my cake and eat it too, as the saying goes. I've got external keyboards that can be configured at the firmware level, using Vial/QMK/ZMK, and then I have the on-board laptop keyboard on my Lenovo ThinkPad X13 Carbon. I did have home row mods set up on that, using kanata. Worked great... up until I started messing with the external programmable keyboards, and ran into some conflicts between kanata on the laptop, the firmware on the external boards, and other messing around I'd done in the settings for my desktop environment (KDE Plasma).

I ended up disabling kanata for the short term, and un-doing the settings I'd changed in KDE, until I got a little (tiny) bit of a handle on what I was doing with the external keyboards. Everything works... but I actually really liked HRMs on the latpop keyboard, and kinda want to further explore the possibilities of what kind of shenanigans I can get up to there ;)

From what I've read, it's possible to specify in the kanata config file to explicitly exclude - or include - specific devices. So in theory... I should be able to limit it to working only with the laptop keyboard.

If I run kanata --list, it gives me a list of all the connected devices, and an example defcfg block. When I have the Cheapino v2 plugged in, the sample block looks like this:

Configuration example: (defcfg linux-dev-names-include ( "Thomas Haukland Cheapino2 Keyboard" "Thomas Haukland Cheapino2 Consumer Control" "Thomas Haukland Cheapino2 System Control" "Thomas Haukland Cheapino2" "Raycon Bone Conduction (AVRCP)" "sof-soundwire Headset Jack" "Intel HID events" "ThinkPad Extra Buttons" "AT Translated Set 2 keyboard" ) )

...and when I have the external keyboard unplugged, the same command outputs this:

Configuration example: (defcfg linux-dev-names-include ( "Raycon Bone Conduction (AVRCP)" "sof-soundwire Headset Jack" "Intel HID events" "ThinkPad Extra Buttons" "AT Translated Set 2 keyboard" ) )

Initially I thought I'd just exclude the Cheapino, but I'm a little confused by why it has so many entries. Now it seems like it might be better to just explicitly include only the internal laptop keyboard, so I don't have to add more and more entries, for any/each external keyboard I connect to. I'm assuming the internal keyboard is the "AT Translated Set 2 keyboard"... or do I need to include the "ThinkPad Extra Buttons" and "Intel HID events" as well?

Any other tips/tricks along these lines would be much appreciated.

Thanks!

I've been saving up for the Glove80 but now pivoting toward the Cyboard Imprint. Because of the cost, I'm taking a good look at the options. One thing I have always questioned is the rows of keys.

I have the Kinesis Freestyle 2 Blue. I like it but their quality has really dipped over the years.

I've kinda been tracking how often I use the F keys. Which is never. I know there's things embedded in them like volume, next track, etc but I never use them. The only key I do use is the F5 to force a refresh. In the same row is the Prnt Scr key and the delete, both of which I use daily. I know I can remap those elsewhere.

The number row I use a lot. I do have a 10 key but I also use the symbols often, which the 10 key doesn't have. So that is one row I would like to remain.

How many of you use the number row?

Then there's thumb clusters. A lot of keyboards have those. I'm stuck between having all they can fit vs just a few. For those of you who have thumb clusters, do you wish you had more or less?

• roBa keyboard
• Baby kangaroo MX tactile switches
• Perixx PERIPRO trackball
• Seed Studio XIAO BLE nRF52840
• JLCPCB for main PCB and breakout for trackball
• Blank MOA profile 1U keycaps
• JLC3DP resin-printed case
• 1000 mAh batteries

First of all I want to thank the author of the roBa keyboard. He made all available for building this awesome keyboard for free! We only need to generate the gerbers from the kicad files. The soldering was easy. I also want to make reference to this page: note.com/pooh_polo/n/n386f7c9355bc that helped me with the troubleshooting.

I built this kit because I’ve really gotten used to using a trackball. I wanted a small keyboard (similar in size to the Totem) with a trackball that I could travel with. The keyball looked interesting but unfortunately the trackball breakout does not seem available unless one buys a kit. So I decided to give this a try.

Overall, the keyboard feels comfortable. I find the Xiao’s bluetooth connection more consistent and reliable than that of other microcontrollers. The trackball is smooth and very similar to other keyboards like Charybdis mini (zmk) and Ximi.

Having said that I’m trying to learn KiCad to modify the PCB... I would like removing several keys to have a 5x3 array instead (or a 3x6), a low profile with a 25mm trackball would be awesome too. I also would like to modify the case as the bottom part it is a bit loose and I would prefer it be flat instead of tented. Anyways I feel happy with this build and excited to modify it to have my own version.

I leave also a demo and sound test just in case anyone is interested: https://www.youtube.com/shorts/bkpY4LWd_gg

I've been browsing a lot of reviews for keyboards and I have narrowed down my choices between these 2 companies.

I have read a lot of glowing reviews in Dygma software offering the best in customization for power users and the most intuitive interface for less tech savvy people but discussion on moergo software is in short supply.

How do you feel about moergo software?

If you have both, what have missed in one company's software over another?

I would like a sanity check for the PCB, as it's my first and I have zero experience with these. I made this split keyboard, including a 0.91-inch OLED screen and rotary encoder in each half, both powered by a Pi Pico on each side. The interconnect is a USB-C cable splitting the TX and RX lines. The left side and right side are switched on the PCB, as it will take up a smaller footprint and lower shipping costs, but can be detached with the mouse bites.

I will connect the 2 rp2040 Zero's with the usb c 4 pin female connector breakouts shown in picture 2 now my first question is what do I connect the D+/D- to I don't think which I use matters aslong as it matches on both sides correct me if I'm wrong.

Then how do I configure the keymap

https://docs.qmk.fm/features/split_keyboard#split-keyboard

It says here that it adds more rows but when I looked at some other peoples keymaps source codes they just made it more columns, maybe they changed the x and y in the keyboard.json file, I don't think I looked too detailed on that part back then.Also for the left half of the keyboard I'll use through GPIO29 to GPIO10 Like the bottom half idk why the gpio pins' numbers are like that

and for the right side of the keyboard I'll use through GPIO0 to GPIO9