ErgoDox VS crkbd

https://www.ergodox.io/, been around forever now.

Closest split PCB based design with a Kinesis Advantage thumb cluster, I know of, is the Ergodox Would need tenting to emulate the keywells. Lovingly design and print a case with tenting legs for it? 🤔

Should be in here somewhere: https://github.com/Ergodox-io/ErgoDox

> Is ZSA's build known to have latency issues compared to QMK?

ZSA is using a patched QMK - they even let you download the exact source for each firmware build they make for you. At the time when I switched to vanilla QMK (that was already some years ago), ZSA were veeery far behind master; running the latest QMK release fixed a couple of issues for me (like hotplugging the halves), so I guess there could be other improvements? No idea really.

> Would a faster microprocessor help

In the MCU world, latency and clock speed can have a very linear relationship - until they suddenly don't. The microcontroller's job is very simple really: scan the key matrix at a certain frequency, perform key debouncing, compare the current state with the previous, and craft a USB HID packet with key press/release events.

So having twice the clock speed could theoretically let you scan twice as often, so it might let you cut the latency in half. Except we have those pesky physics getting in our way! For simplicity let's assume we don't have split halves (where there's an extra serial connection slowing things down); I'm no EE so I only grasp these concepts at the surface level, but signals take time to propagate, and long traces on the PCB (and cables too) have a tiny bit of their own capacitance. (Capacitors are like really fast, really tiny batteries - but they still take a tiny amount of time to charge and discharge, which does all sorts of interesting things to high-frequency signals.)

On top of that, the electrical connection that the pieces of metal are making inside the switch, are never perfect at the exact instant the switch is supposed to (de)register: a couple electrons might start jumping over the air even before contact is made, and the physical connection is subject to normal wear, amplifying the "edge case" effect over its lifetime - which all together means we have to actually spend a certain amount of time "looking" at the state of the switch, to let it settle and make sure we got it right.

We end up spending so much time letting physics do its job that in a trivial firmware, the MCU is actually spending a significant amount of time... just sleeping. Which means we were later able to cram all sorts of madness like individual RGB lightning or status displays, and never decreased the poll rate.

Where would these 40ms come from then? Well I wouldn't get near the problem without an oscilloscope, and unfortunately I don't have one.

> I'm just starting to get into custom keyboards.

Then I recommend studying the original ErgoDox firmware & build instructions! It's extremely straightforward compared to a beast like QMK, which actually uses a whole RTOS.

https://www.ergodox.io/; https://github.com/benblazak/ergodox-firmware

Hi! Does anyone here have some experience playing age on an ergodox? I usually move the right part out of the way so that I can have more space for the mouse (it is actually great for things like FPS because the mouse hand is in a very natural position), but the default hotkeys force me to move my left hand across both sides, making it hard to actually hit the key without looking. I've been only using control groups 1-5 due to this, which is less than optimal.

The closest open source keyboard you'll get next to the Moonlander is probably the ErgoDox that it's heavily inspired from.

Looks at the order here : https://github.com/foostan/crkbd/issues/96

I followed this guide for the build (https://github.com/foostan/crkbd/blob/main/corne-classic/doc/buildguide_en.md)

Not sure which information you mean, but here goes. Nice!Nano v2 Pinout (shows Arduino pin mapping). Nice!View Getting Started (explains how to remap the CS pin for a non-native shield like Corne). The overlay file where "cs-gpios" is set for the nice_view_adapter in ZMK. If you look at the Corne Schematic, you'll see as shown in the labels in this image that the bottom two pins (B2, B4, B5, B6) don't appear to be used for a column, row, or the OLED header. But the only way to really verify is to pull the KiCAD file for your Corne version and check yourself. I think D0 ("Data") should work. It appears to go to an optional I2C connection.

Want to say the corne board drawings etc are available at https://github.com/foostan/crkbd as well, if you fancy learning kicad you might be able to tweak them yourself ... though that is definitely the deep end of things...

https://youtu.be/-E7KRnVCjq8 https://youtu.be/4bB9A1YYyII https://github.com/foostan/crkbd/blob/main/corne-cherry/doc/v3/buildguide_en.md

For the layout, I took inspiration from the CRKBD and the Boardsource's Microdox.

This is the numbered LED series from the Corne Classic Build Guide (https://github.com/foostan/crkbd/blob/main/corne-classic/doc/buildguide_en.md)

I would need hex file from here https://github.com/foostan/crkbd/blob/main/doc/firmware_en.md and then i need to run flash command . Il read through it one more time, it seems that i use same hex file for both sides.