ErgoDox VS qmk_configurator

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.

Handedness? Not sure what do you mean by that. I'm using the config.qmk.fm website for the key configuration

I'm using https://config.qmk.fm/ to create a firmware for Iris rev.7 including mouse keys, and then use QMK toolbox on MacOs to flash the firmware, but while everything else works in all layers, the mouse keys do not move the cursor at all. Any ideas?

How can I use https://config.qmk.fm/ to map certain specific keys such as € or @, that are not direct or available in the framework ?

"documentation": "\"This file is a QMK Configurator export. You can import this at . It can also be used directly with QMK's source code.\n\nTo setup your QMK environment check out the tutorial: \n\nYou can convert this file to a keymap.c using this command: `qmk json2c {keymap}`\n\nYou can compile this keymap using this command: `qmk compile {keymap}`\"\n",

I didn't want to really start another thread because the question I have is so similar I think. I was somehow able to use config.qmk.fm to map a really generic colemak-dh keymap, I read the qmk noob section so I looked up how to use github/git completely lost, I have the Corne 3x6 I didn't build it I purchased it secondhand so Ive been doing some research on ergonomic mapping Miryoku generally seems to be a solid choice

I'd recommend you jump on QMK configurator, select the Charybdis of desired size, and start making your layers 😉

My keyboard was working fine prior to flashing. I have a solderable dz60 (ATMEGA32U4). I tried to flash it with firmware downloaded from config.qmk.fm (selected dz60 as keyboard). It said successful on qmk toolbox, but my caps lock light is stuck on and no button presses work. The esc + plugin option to reset stopped working, so I had to take the pcb out to press the reset button. Still not working after flashing with default firmware downloaded from config.qmk.fm. I tried flashing it with dz60 via firmware, and it gets recognized in via now, but still not working. After hours of troubleshooting of it not working, I flashed it with dz60rgb_v2 just to see what happens, and then very few of the keys work after a few presses (but they're mismapped), and the caps lock light goes off. I've tried the keyboard on different devices, and on both of them it gets recognized as a keyboard, but the caps lock light is still stuck on and no presses register.

Let's suppose that the issue is the diode orientation. I'm a total QMK newbie -- how could I swap between ROW2COL and COL2ROW at the firmware level? On the QMK Github I see instructions for modifying the appropriate headers. But when I generate my config from config.qmk.fm I only get a single .hex file. Thanks again!

Probably the easiest way to do it by clicking buttons is to use config.qmk.fm.

For non-ez keyboards, a similar tool is the QMK Configurator. See this documentation page or the video tutorial for an overview.