this post was submitted on 25 Jun 2023
40 points (100.0% liked)

ErgoMechKeyboards

5836 readers
3 users here now

Ergonomic, split and other weird keyboards

Rules

Keep it ergo

Posts must be of/about keyboards that have a clear delineation between the left and right halves of the keyboard, column stagger, or both. This includes one-handed (one half doesn't exist, what clearer delineation is that!?)

i.e. no regular non-split¹ row-stagger and no non-split¹ ortholinear²

¹ split meaning a separation of the halves, whether fixed in place or entirely separate, both are fine.
² ortholinear meaning keys layed out in a grid

No Spam

No excessive posting/"shilling" for commercial purposes. Vendors are permitted to promote their products/services but keep it to a minimum and use the [vendor] flair. Posts that appear to be marketing without being transparent about it will be removed.

No Buy/Sell/Trade

This subreddit is not a marketplace, please post on r/mechmarket or other relevant marketplace.

Some useful links

founded 1 year ago
MODERATORS
 

Hi folks, I've been working on this keyboard pretty much since January of this year, and I've finally got it to the point that I can call it done! If you'd like to build one, all files are available here.

This is an MX-based keyboard, 36 keys with integrated trackball. The github page has a bunch more details. I also have a choc version in dev using the same style that's based off the Trinidox.

Let me know what you think!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 0 points 1 year ago (1 children)

haha sorry! Decisions are tough...I say build both :-)

I'm not quite sure what you mean by two trackball halves...do you mean a trackball on both the left and right? Totally possible if that's what you mean since each side has a uC...but I think I'm not quite catching your question.

I'll get some pics of hand on home row and hand on trackball. I aim for it to be equivalent to a "row shift", meaning when using the trackball, the fingers rest comfortably on the top row which then become the mouse buttons. This works well if you use HJKL for VIM style arrow keys since it can all be on the same nav layer: home row for arrows, top row for mouse buttons. Take a peek at the Trinidox page I linked to...it has pictures of home row and trackball use and should be very similar to the flow-MX36.

Thanks for your interest! Keep me posted...would love to see another build in the wild!

[–] [email protected] 1 points 1 year ago (1 children)

You were correct, I would like to have one two trackballs, one per halve.
The pics would still be great, but your method of moving the whole hand up one row sounds, without ever having tried a contoured keyboard with integrated trackball, as the best placement solution I have seen so far.

[–] [email protected] 1 points 1 year ago (1 children)

Ok, ya should totally be possible to have 2 trackballs. You made me think I should provide details about the trackball placement philosophy on the github page... I've been neck deep in this design for so long, I've forgotten many of the design features that makes it unique. Touch base of you make one! Would be awesome to see a double trackball version :-)

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

Perfectly understandable. :)
You say that it is possible to use Amoeba-PCBs in the Flow-MX36. Have you wired yours using them? I wonder if there is enough space, especially in the thumb cluster and innermost columns. If I ever stop procrastinating and try to build it, I would like to use Amoeba Kings with it.

[–] [email protected] 0 points 1 year ago (1 children)

I built it using amoeba royales. It's certainly tight. I modeled the amoebas plus components and had a cutter to create the necessary space, so that part was pretty easy. The tightest key is the bottom row on the left most column (for the right side case with trackball). It fits but needs a little jiggling.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

Thank you for the info!