ErgoDash VS vial-qmk

I'm looking to build and use the right half of an ErgoDash keyboard as a fully programmable gamepad. I'm currently using an OLKB Peronic and while it's serviceable, I'm driven to find/make something better. So before I dive head first into this, does anyone have any experience with ErgoDash keyboards? If there's some fundamental flaw I'm missing or if there's a better option out there, please let me know.

Could someone please assist me or point me to somewhere I can get assistance with building/diagnosing an Ergodash. https://github.com/omkbd/ErgoDash

I'm building (another) ErgoDash and I'm considering adding only underglow lights (with RGB WS2812B LEDs) and not backlights. However the documentation wrapes them together and I'm not sure whether the additonal components - a MOSFET and a 1k Ohm resistor - are needed for the underglow. Anyone knows? Can there be any harm (i.e. shorting something) in trying without them?

If you want a compact split with plenty of keys, I would recommend the ergodash, which is open sourced and can be bought prebuilt.

ErgoDash (general info https://github.com/omkbd/ErgoDash)

I flashed the firmware in this repo for both sides. Then I connect the keyboard into my computer and start Via. But it keeps searching for devices... BTW, I see some posted that Ergodash is supported in Via but cannot find the firmware in the official document here . Was it removed or something else?

I started with an ErgoDash [1], purchased because my Microsoft/Logitech split keyboards had worn out, and at the time I couldn't find a replacement with normal (not low profile) keys. It has a few additional keys compared to the Iris. I have one at work and another at home, and to make them more similar to the broken keyboards I 3D printed angled bases. I use it for 99% of my typing.

I should probably have tried a Kinesis Advantage 2 first.

I'm partway through printing/assembling a Lagrange keyboard [2] (I'm currently stuck working out how to order the circuit boards), which is similar to the Dactyl. I will add the F1-F12 keys to my print, as they're the only thing I miss -- if a shortcut in my IDE is Ctrl+Shift+F10, it's nice for it to be that, not Ctrl+Shift+Fn+0.

I made [3] to help others see what's available.

[1] https://github.com/omkbd/ErgoDash/

[2] https://github.com/dpapavas/lagrange-keyboard

[3] https://aposymbiont.github.io/split-keyboards/

What about ergodash. Has an additional inner column, and an extra couple of thumbs.

Hello, building an Ergodash, I have some questions concerning flashing the pro micros:

I was warned by a colleague that this was a rabbit hole, then warned by people online, and I'll pass on that warning now.

I tried to help by updating and better-presenting an existing list of ergonomic mechanical keyboards: https://aposymbiont.github.io/split-keyboards/

I'm using an ErgoDash¹ with a 3D-printed tilted stand, but I intend to assemble a Lagrange² "soon".

¹ https://github.com/omkbd/ErgoDash

² https://github.com/dpapavas/lagrange-keyboard

i wish to enable several features on my corne thru vial but could not seem to make those from this link to compile - first error was about keycode then something about dynamic keymap when i had the first fixed/simplified. i'd appreciate if anyone could share their tested vial configuration files that i can use as guide.

This applies to OP as well, if you have any Keyboard @ https://github.com/vial-kb/vial-qmk/tree/vial/keyboards/keychron

You'll probably need to download the files from the GitHub repository for Vial or QMK. Depending on what you prefer and what you need. Then you'll have to learn what you need to change to set up the screens and then to edit the files. Your keyboard maker probably can provide you some files you can use. Then you'll have to compile your own HEX file. And only after that you can re-flash your keyboard and use all those amazing things you integrated into the firmware.

It looks like that's a vial keymap specifically for the rev2? I don't know whether it would make a difference, but you could try to compile from this keymap instead and see if it works?

According to this (https://github.com/vial-kb/vial-qmk/blob/vial/keyboards/bastardkb/charybdis/4x6/v2/splinky/config.h) the Vial firmware for Splinky based Charybdis is written natively using RP2040 pin names.

Think you can also port to VIAL? I am currently using the doio firmware without problems, but guessing your updates will be useful: https://github.com/vial-kb/vial-qmk/tree/vial/keyboards/doio/kb16

I've been using VIA to edit my keyboard layout, but unfortunately the software can't find my keyboard anymore (it just gets stuck on 'Searching for devices'). I think I need to reflash my keyboard. I don't have any .hex files for it with QMK toolbox, and the libra mini doesn't show up in the list of keyboards on the online QMK configurator. I do, however, have access to the files found in vial-qmk/keyboards/libra_mini/keymaps/vial (found here https://github.com/vial-kb/vial-qmk/tree/vial/keyboards/libra_mini). I've been using the vial.json file from there to change the layout up until now. How would I go about getting a .hex file, or better yet, a keymap.JSON file compatible with the online QMK configurator?