Ergodox-firmware Alternatives

ergodox-firmware reviews and mentions

• ErgoDox DIY - But how?
  1 project | /r/ErgoMechKeyboards | 1 May 2023

  I've used github.com/benblazak/ergodox-firmware to customize my firmware, but you're probably better of with qmk, zmk or whatever the cool kids use these days.

• Keyboard Latency
  4 projects | news.ycombinator.com | 1 Dec 2022

  > 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

• What is the simplest .hex file I can use to test my Teensy 2 with?
  2 projects | /r/olkb | 24 Apr 2021

  I'm currently trying to flash a Teensy 2 with the QMK Ergodox build, and I'm running into trouble after flashing the firmware. Everything runs smoothly, and I have had success with the slow blink hex with both the CLI and GUI, but the ergodox firmware doesn't seem to register as a keyboard.

• A note from our sponsor - InfluxDB
  www.influxdata.com | 6 May 2024

  Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →