r/ErgoMechKeyboards • • 21h ago

[buying advice] Sculpted caps eg KLP Lamé on Glove80?

3 Upvotes

Curious if anybody has used sculpted caps like KLP Lamé on a glove80? Really liking the layout so far but could stand to have the num/function rows brought a bit closer to my fingers.

I know mx sculpted boards like the advantage/dactyls work well with SA profile, but I haven't seen anybody use sculpted caps on a Glove80.


r/ErgoMechKeyboards • • 48m ago

[discussion] Participate in my study - and learn more about how typing correlates with stress, focus, and energy!

1 Upvotes

Hi r/ErgoMechKeyboards , Have you ever wondered how you could know if you were stressed, tired, or unfocused to a specific level? Well, TypeSense is an academic study that aims to find a correlation between how you type and how focused, stressed, and energized you are. Participate in my quick and non-invasive study and receive a personalized typing diagnostic at the end that correlates your stress, focus, and energy to various micro features in your typing rhythm.

I'm Lucas, a high school student running a science fair study (GSDSEF) on whether the rhythm of how you type may relate to how focused, stressed or energetic you feel. If the results hold up, it could possibly help researchers understand everyday focus a little better. If all goes to plan, this type of research may lead to helping doctors and scientists predict early-depression signals.

What I need: about 20 adults (or more, but 18+), in the US, with their own personal Windows PCs (not a work or school machine).

What you'd do: run a small app for 3 weeks and answer a quick mood check-in (stress, focus, energy) every 20 minutes or so.

What it records: typing timing only: how long keys are held and the gaps between them. It never records which keys you press or what you type. Yes, it's a background app that watches typing, so I understand the side-eye. That's why the source code is public (https://github.com/ricewas-mis-taken/TypeSense) and the consent form spells out exactly what's collected.

Best of all: At the end of my study, you'll have greatly helped advance research in how typing might show patterns in mood, stress and energy. You'll also receive a fully personalized typing report!

Interested or have questions? Comment, direct message, or email me at help.type_sense@lucastang.dev 

Lucas


r/ErgoMechKeyboards • • 20h ago

[buying advice] Transition to Split KB

2 Upvotes

Hey all,

I'm looking for some advice concerning a transition to split keyboards. I'm currently using a TKL and a razer Tartarus, which is on the fritz. I'm thinking about transitioning to a split keyboard but not sure which is the right start.

I guess I'm a little concerned with the budget, I'm happy to spend £100-120, but want to understand what I'm getting. I've looked at KBS like sofle/lily 58, but neither seem to give the thumbs I'm after. I guess I'm asking is it worth committing to something more ortho with more of an adjustment, or closer to the Tartarus and iterating later, noting I have to learn layers and key binds. Maybe there is something with more thumbs that would work without a massive investment and relearn?


r/ErgoMechKeyboards • • 21h ago

[photo] Ergomeownical keyboard

Post image
86 Upvotes

The RefleXion65 . And Tino.


r/ErgoMechKeyboards • • 5h ago

[design] mikefour, the 3.6mm tall keyboard you cannot build [write-up]

Thumbnail
gallery
231 Upvotes

This is mikefour, because mikethreepointsix sounds weird: it’s 3.6mm tall, measured from the tabletop to the top of the unpressed keycap, and still has a 1.5mm stroke. Amazing, right?! Don’t give me any credit for this fact, because this was made possible by the One Key Module (OKM) from r/Framework, the highly repairable laptop and PC company. Framework developed this switch for users wanting to create their own ‘input covers’. In their Framework 16 laptop, you can take out the entire keyboard easily and replace it with a new one, even a DIY one of your own design. But you will need amazing thin keys, because space is ofc very limited in laptops. The PG1316 or MX ULP are too tall, not only because of the switch height, but because of the way they are mounted to the PCB. That’s where the OKM’s stand out. Read more about this unique switch design below, and why you cannot build one too.

Bottom side mounting

In one of the attached videos, I show how the switch is placed into the PCB from the bottom side. The ready-mounted keycaps protrude through the lattice-shaped PCB to the top side. This is really smart, because this way the PCB connecting the switches doesn’t add any height! I added a picture where you can see the OKM and Cherry MX ULP (which is the same size as PG1316) next to each other separately, and in/on the PCB. It’s really crazy how thin this keyboard is. I needed to use a top-mounted USB-C connector, because if I used a flush one, the cable housing would push up the keyboard.

I used a single 1.6mm PCB, which is the advised total height so the pressed keycap is flush with the top face. For a cleaner-looking top face, you can use a 0.8mm PCB and another 0.8mm layer on top with whatever finish you want: another solid PCB without tracing, or a laser-cut sheet, or a CNC-milled aluminum housing. I was planning the last, but ended up with this simple as can be, single-PCB with integrated controller keyboard.

But why can’t I build one?!

You can read all about it here in Framework's own post. In short: it was announced quite some time ago, but the product was not ready yet. After a compact Developer Program in Q1 2026, Framework decided to not launch the switch. It was too expensive to produce, and the Developer Program showed it was quite finicky to build with, even for expert keyboard builders.

OKM strengths

The OKM is an awesome switch with some unique properties:

  • As mentioned, the height including PCB is crazy low. Nothing I know of comes close.
  • Switch feel is uncompromised. Imo, the best ULP switch out-of-the-box. It feels like a premium laptop keyboard switch, which it probably is. It’s a ‘rubber’ dome under the hood; it feels great. Nice tactile bump and smooth, silent bottom-out.
  • Daisy-chainable: the switch has integrated column and row traces and more. In the lattice PCB, you need only short traces between the modules. At least, that’s the idea. More on that later.
  • Integrated diode and white LED. To make tracing even easier, diodes have been built into the switch for matrixing the switches. A white LED is also integrated for a per-key backlight in this super-thin package.
  • You can laser engrave the keycaps. Doing so removes the top black layer and exposes the transparent inside, making lit-up custom legends possible.

OKM limitations

A strength can also have a downside, which is not always bad but more of a compromise, and can restrict your design:

  • The lattice structure is required to be able to solder the modules on these PCB edges. This means you cannot have the keycaps tight against each other: there will always be space in between.
  • Also, because of this, you cannot have a smaller key spacing than MX-spacing (19.05 x 19.05 mm) with the OKM. It’s sized for that spacing.
  • Keycaps can be removed, but because everything is so slim, the clips below the cap are tiny, so custom profiled (printed) caps will be a challenge.

OKM quirks

These are some interesting things us devs found in the program:

  • The modules have a total of 10 contacts per key for daisy chaining, plus four larger metal tabs close to the corners. These four tabs protrude tiny slots in the PCB lattice and position the keycap nice and centered in its PCB cutout. These tabs, however, only seem to allow a near ortho-linear switch layout. When using different amounts of column- or row-stagger, these tabs quickly collide between neighboring switches. The only way to work around these collisions is to use a greater-than-MX-size spacing, which would be weird. Some splay can help, but you might still run into trouble in other spots where keys are close to each other. The solution we used is just to clip off some tabs. On mikefour, one or more tabs were cut off on about a third of the switches.
  • The modules have integrated LEDs, but no integrated resistors, and the provided information only mentioned connecting the rails named 5V and BL_LOW. It was quite unclear how to hook them up in a daisy-chained way without risk of current hogging. I thought of a hacky way to put a per-LED resistor on the lattice using one of the unused vertical passthrough traces on the module for power, but fellow dev Axel thought of a way of using a dedicated (QMK/ZMK-compatible) LED-matrix I2C controller chip to skip the per-LED resistor, which I copied in the end. But this still required some additional vertical tracing over the narrow lattice PCB structure where the slots for the tabs only allowed one thin trace to pass. So, the intended way to safely hook up the LEDs using the intended daisy-chaining is a bit unclear.
  • Back to the four larger metal tabs. You would say it is a good idea to solder those to the lattice PCB to structurally bond the switch, and not rely on the 10 tiny surface-mounted contacts for a structural bond. Especially since these contacts are on the bottom of the PCB and pressing the switch from the top of the PCB directly loads these connections. But these tabs proved very hard to solder, and might even have had a coating that prevents soldering. Later, Framework mentioned the tabs were only meant for positioning. In the keyboard, it’s probably best to rest the bottoms of the OKMs on a (table) surface, plate, or case below so pressing force is directly transferred there, instead of loading the surface-mounted contacts.
  • The OKMs came packaged as a larger PCB with 9 OKMs in it, with the OKMs still attached to the larger PCB with a few small bridges. The OKMs can be broken out of the larger PCB easily. With the modules still attached, the complete larger PCB has some cool functionality built in to be able to test all 9 OKMs at once using exposed pads on the larger PCB. This means that traces pass through the small bridges that hold the modules in the larger PCB. Breaking out the modules therefore breaks these traces. One of the devs spent days figuring out why his build was malfunctioning, only to finally find out that some tiny piece of exposed copper from this broken-off bridge was causing a short with an exposed pad on his own lattice PCB…

My first PCBA!

On to my personal build. This thing is so thin, so simple, it would look a bit off to just stick a nice!nano or Xiao on there and to try to hide a battery. And for the LEDs, I would preferably need this additional LED matrixing chip to avoid the per-LED resistors. So, I decided it was time for my first PCBA and to integrate the MCU and LED controller directly onto the lattice PCB. So, also my first wired-only keyboard design, which also means I can crank the LEDs all I want. Unlimited powerrr! Check out this crazy QMK LED wave video attached.

I copied Axel Voitier’s Handywork PCB (which you should totally check out on his GitHub, as it’s the only actual working custom Framework 16 laptop input cover I have seen! It’s crazy to see a laptop with custom ergo layout built in!) and modified his open-source design to work with a normal USB-C port instead. I used ChatGPT in Codex (VSCode) to help me with modifying and checking the KiCad schematic, as I found out it can just read/edit/execute functions in KiCad. In the end, I did all the tracing myself (it wasn’t very good at that yet), but Codex helped me a lot with checks going beyond KiCad’s DRC, such as correct component placement. I learned a lot from the process! Building firmware and troubleshooting is also a breeze with Codex. Like with my mikefive split, I don’t think I could have done it without it. I’m a mechanical design engineer, and electronics is def not my profession!

The MCU is a RP2040, and the LED controller is an IS31FL3733. The RP2040 uses an external clock and memory. I needed 3.3 and 5V regulators, and the USB port required a protection chip. Also, I only used 0.3mm drilling for vias to save significant PCB cost, which was quite a tracing challenge with these small chips and my ambition to use a 2-layer PCB. Don’t ask me about EMI/EMC though…

The only ‘mistake’ I made was to rely on the OKM’s internal tracing for grounding some parts of the MCU circuit, which could have easily been fixed by some additional grounding vias. But because DRC just checks everything with OKM’s virtually installed, this ‘issue’ didn’t pop up until I received the PCBs and tried to flash the RPI without modules installed. But in the end, everything worked without issues with the OKMs soldered in. Very happy with how the electrical design went!

320 solder points

32 switches, 10 surface-mounted contacts each. That’s more solder points than your usual keyboard build. They are tiny too. It took quite some time to do. I found out that when using enough flux, they solder quite nicely. A small pointy soldering tip was nice to have for these tiny surface-mounted connection points. I needed to reflow only 2 out of 320 joints after troubleshooting. Finding out which one it was took more time than the rework itself.

Only two thumb keys

I’ve now been typing ergo for about 2.5 years or so. Almost all of it on my own ULP boards. In the end, I always chose to use stock keycaps (with mods below), and those caps are just flat. This makes blind hand/finger positioning a bit trickier. With the single thumbs, I’m always in the right position as long as my thumbs feel the switches. On my mikefive and mikecinq I sometimes found myself accidentally a column outward. Keymap-wise, I took inspiration from other 32-key or lower keymaps: I started putting in combos on the base layer for Enter, Esc, Tab, Cut/Copy/Paste, Caps Word which reduces my need for more than two thumbs. I’m already using this more combo-based setup on my mikecinq for around half a year now, and I am very happy with it.

Messy silkscreen

I chose the messy silkscreen print on purpose to make the slots for the four metal OKM tabs on each switch less noticeable or eye-catching. The component cluster is visible and open, but stands out less because of the busy silkscreen pattern. If you're using the PCB as the visible piece, why not use that silkscreen, right?

A general tip is to use a white PCB with black silkscreen for nicer black and white. On a black PCB with white silkscreen, the white is much less bright, and black PCB’s at JLCPCB are matte instead of glossy.

My new dailies

My wireless mikecinq was my daily. It’s easy to slide into my bag and take it with me. mikefour is wired, so am I going to plug in and out each day and shove bare components in my bag? Fortunately, PCBA requires a minimum of two assembled PCBs. So, for now I have one permanently at work, and one permanently at home. I must say, not having to charge my keyboard once in a while, and on-the-fly keymap edits in Vial feel kind of good :)

Thanks for reading if you made it this far! This was all typed on the mikefour. So again, like the mikefive split, it’s kind of an inspirational build. I can, however, share the files on my GitHub. Maybe the MCU/LED controller setup over USB is worth something for someone, and my main source, HandyWork, is also open source.

mikefive split files?

By the way, I didn’t share the mikefive split files as the code and hardware just weren’t good enough. It didn’t live up to my battery life claims, which could be fixed in code, but the hardware needs a revision too for people to build it reliably. This was such an experimental build that I would want to change quite a few things to make it a keyboard I would actually use, and I don’t know if I want to make that investment soon. However, some crazy smart people picked up on the extreme battery life concept and are making something that should work. Keep your eyes open on this sub.

Next?

I have two more projects on the shelf. I still have Cherry MX ULP switches in all tastes here, which should be pretty good with some thin silicone layer on top of the PCB. This might be the only option to ever launch the mikefive commercially. Mechboards uses the Cherry too on their Corne Min, and yes, it’s 60g, but some people just want an ULP ergo board, and there just isn’t much to choose as quality alternative switches.

And I am working on a crazy low-profile Svalboard-like thing. So, yeah, I didn’t post for some time, but the community is still working behind the scenes. Stay tuned…


r/ErgoMechKeyboards • • 15h ago

[photo] Cornison: a Corne Cherry with a full bottom row (dedicated mods, arrows) and a case script that reads the KiCad file

Thumbnail
gallery
39 Upvotes

This is the Cornison, my split based on foostan's Corne Cherry v3. It has a few extra keys in a Levinson-style bottom row, which is where the name comes from (Corne + Levinson).

What's different from a Corne

  • Left half: the 3×6 grid plus 3 thumb keys and dedicated Ctrl, Alt and Cmd.
  • Right half: the 3×6 grid plus 2 thumb keys and 4 arrow keys.
  • 48 keys, hotswap sockets, Pro Micro, OLED, TRRS, and footprints for per-key and underglow RGB.

The case

The case isn't hand-modeled. A Python script (build123d) reads the KiCad PCB and builds the tray case, switch plate, MCU cover, plate spacers and tenting legs from the real footprint positions. If the PCB changes, the case follows. The plate also exports as an FR4 KiCad project, so it can be ordered from JLCPCB alongside the PCB.

The tenting legs screw into inserts in the case floor from below, so the tent comes off without opening the keyboard. They sit at 18°, and there's a tray in the middle for stick-on tire weights. This helps to keep it stable while typing.

Status

v1.1 is built and I'm using it daily. Both halves, the TRRS link, OLEDs, case, FR4 plate, cover and tents all work. RGB isn't tested yet. I don't really use RGB myself.

Printed in Prusament PETG on a Bambu P1S: Galaxy Black for the case, Chalky Blue for the tents and covers.

I used Claude (AI) to write most of the case generator and scripts. The design calls, testing and fixes from real prints are mine, and everything in the photos is built and working.

Links

MIT licensed. Happy to answer questions.


r/ErgoMechKeyboards • • 13h ago

[help] Newb looking for ergo split with trackball and display

3 Upvotes

Hi,
I'm experiencing some pain when I type a lot on my KC200MX. That's why I chose to look for an ergo alternative.

I'd like something as cheap as possible, with a trackball on the thumb cluster and preferably a display on the left half to see the current layout.
My wife uses my computer from time to time and it would drive her crazy having to learn to type on this one without some kind of legend.

I have a 3d-printer and soldering experience, so hand soldering is no problem for me. Also, I don't mind wiring the switches by hand to save some money.

Could you guide me to a diy keyboard that ticks all my requirements?