tshort / dactyl-keyboard Goto Github PK

Dear dactyl manuform author,

I hope this message finds you well. My name is Antoni Bezak and I am a 15-year-old technology enthusiast with a particular interest in keyboard design and assembly.

Recently, I successfully built a keyboard based on the Dactyl Manuform design, which I found to be an incredibly rewarding and educational experience. I am writing to you because I am considering taking this project a step further.

Given the positive feedback I've received from those who have seen and used my keyboard, I am contemplating the idea of building more Dactyl Manuform keyboards and selling them. However, I am aware that your design is open-source and I want to respect any conditions or restrictions associated with its use.

Therefore, I would like to formally ask for your permission to use the Dactyl Manuform design in this manner. Would it be acceptable for me to build and sell keyboards based on your design? If so, are there any specific requirements or conditions that I need to adhere to?

I look forward to hearing from you and would like to express my gratitude for your contribution to the open-source community. Your work has not only provided me with a fantastic keyboard but also a valuable learning experience.

Best regards,
Antoni Bezak

The plate files generatable by dactyl.clj (once you add a mirrored left variant) merely consist of the wall outlines, not the full plate. They essentially are a brim of plate around the (inner) perimeter of the keybord. If i got it wrong what they should be, please excuse my issue. On the other hand, it’d be great if it was possible to generate »full« plates, that are usable as-is, for the keyboard. Sadly, my openscad knowledge is not as good, so i didn’t succeed yet in making them »full«. If i succeed, i’ll open an PR — until then, i’d be grateful for any tips that more seasoned users might have ^_^.

Thank & Best,
-Dario

Hi.
i'm trying to build this keyboard (my very first DIY keyboard).

I've wired the promicro in this way: https://github.com/tshort/dactyl-keyboard/blob/master/resources/dactyl_manuform_left_wire_diagram.png

but nothing works, i'm able to flash the promicro, the keyboard is being detected by the operating system, but when pressing any key, nothing happens.

Should I set something particuraully on the firmware configuration ?
Already tried to swap cols and rows in MATRIX_ROW_PINS and MATRIX_COL_PINS, nothing changed

goes here...

I've been making some changes for my own build without any previous experience with clojure. I'd just like to ask how would I succesfully change the 1.5u thumb keys to 1u so that the case also realizes this? I've moved the top keys from thumb-15x-layout to thumb-1x-layout and removed the former altogether from the code. That alone clearly isn't enough and I'm in a point where I now got only the gaps left between the top thumb key holes and the case. I can't seem to figure out how would I go about closing the gaps, so help would be appreciated.

I don't know if you have ever tried Googling dactyl-manuform, but for some reason this repository is very hard to located via Google. It's nowhere to be found in the 3 first pages of the Google results for "dactyl-manuform". This is very unfortunate, since I think your fork of the Dactyl is an amazing piece of work.

I'm not sure how Github does their SEO, but I think if you change the description to something like "Dactyl-ManuForm, a parameterized ergonomic keyboard", I think it might show up in more searches.

Changing the name of the repository is also a step to consider (perhaps dactyl-manuform, or dactyl-manuform-keyboard), but that is a bit more drastic.

Hello, thanks for this awesome project/keyboard.
I'm guessing what are the usual print settings most people use. Do you print it vertical? horizontal? which supports do you use? what infill?

Thanks and regards

Hi, thanks for this project! The design is awesome!

Would it be possible to remove the nubs on the sides of the switch cutouts? Those prevent us from using Kailh switch housings, which have grown in popularity. I'd suggest using a different model for the switch holes like recommended in #23
For the time being, I've used a small, low-velocity rotary tool to remove them which is just inconvenient.

adereth#29

Do you think we can change it for dactyl manuform as well?

I realize the STLs are out of date (i generated some updated cases and plates myself).

However, for those who wish to use the existing STL files to print a keyboard, they can use this pre-built STL file. (Mirror it in your 3d printer slicer to have one of each side). It's 2.4mm thick, with chamfered screw holes.
old-right-5x6-plate.stl.zip

I had one break off. My keyboard is still usable. It's still plugged in on the right side. I'm okay as long as I don't want to reprogram my left side:).

This is a known problem with these cheap knock-off controllers.

I should redesign this to use a separate full-size USB connection and wire that to the Arduino Pro Micro.

Hi Tom. Thank you for the awesome keyboard design.

I forked your repository 498 commits ago, eventually turning it into a CAD application for multiple designs. Although the changes in my fork are large, both in scope and volume, I have preserved upstream compatibility by replicating the Dactyl-ManuForm design in the new application, making it the default build target.

Of the following two pictures, one is your original design, and one is its imitation as a product of my fork.

The visible differences are intended as enhancements, or sacrifices without practical impact.

I believe the changes to the application are useful to your users. My fork solves #26 and #19 for free. It probably solves #23 too, and makes it easier to solve problems like #42, because it has a declarative configuration layer in YAML where the size of each key is controlled in isolation from source code. This configuration layer eliminates the need for fragile diff-patching to get different matrix sizes.

The license has not changed.

I therefore propose a merge. With your permission, I’ll send a pull request for the whole thing.

There are reasons why you might not want this. For example:

• There are other active forks.
• My fork does not have the little hooks for wires, which I guess are not heavily used. This is the only feature loss I am aware of.
• My fork has removed your build-guide document (part of the readme), which I would be happy to restore to its former glory as a separate file.

Let’s discuss it. Is there anything you would want before considering a PR? Is it out of the question?

Hello, could you provide another link to the RJ-9 connector, or a picture of what they look like?

The "side-nub" really isn't catching the latch on the key assembly. It's just forcing it out and I have to glue all my keys in. What I see others doing is creating a ridge in the mount where the key assembly can snap into as it's designed. Thoughts?

It seems like there is an error with the files for the 4x5 case hosted on Thingiverse. The holes for the switches are 14mm x 13.3 mm, instead of 14mm x 14mm like they should be. I've re-downloaded the files, and confirmed that the most recent ones have this error.

The files on github seem fine.

I just got my cases from 3D hubs, and couldn't figure out why I couldn't get the switches in. After some headscratching, checking the print settings, and finally checking the files, I found the problem.

I've been making some changes for my own build without any previous experience with clojure.

I'd just like to ask how would I succesfully change the 1.5u thumb keys to 1u so that the case also realizes this? I've moved the top keys from thumb-15x-layout to thumb-1x-layout and removed the former altogether from the code. That alone clearly isn't enough and I'm in a point where I now got only the gaps left between the top thumb key holes and the case. I can't seem to figure out how would I go about closing the gaps, so help would be appreciated.

I now receive this error after the latest commit:

IMPORTING FROM ../src/trackball_socket_body_34mm

IMPORTING FROM ../src/trackball_sensor_mount

IMPORTING FROM ../src/trackball_socket_cutter_34mm

IMPORTING FROM ../src/trackball_sensor_cutter

Traceback (most recent call last):

File "/app/src/generate_configuration.py", line 365, in

run()

File "/app/src/dactyl_manuform.py", line 3625, in run

mod_r = model_side(side="right")

File "/app/src/dactyl_manuform.py", line 3519, in model_side

shape = union([shape, sensor])

File "/app/src/helpers_cadquery.py", line 56, in union

shape = shape.union(item)

File "/opt/conda/lib/python3.9/site-packages/cadquery/cq.py", line 3242, in union

r = r.clean()

File "/opt/conda/lib/python3.9/site-packages/cadquery/occ_impl/shapes.py", line 389, in clean

upgrader.Build()

OCP.Standard.Standard_Failure: Courbes non jointives

When I switch to solid it builds but when generating the stl from the SCAD file, OpenSCAD says that the mesh is not closed.

Clojure noob here. Got lost somewhere along the way, wondering if someone could point me in the right direction?

Get Clojure runtime. check.
Get Leiningen. Check
Get OpenSCAD. Check.
Cloned adereth/dactyl-keyboard repo. Check.
Open things/*Scad file in OpenSCAD. Cool.

Now here is where I am lost:
Have Dactyl.clj open in Sublime3
Changed rows to 6x6
Saved.
in Terminal Cd to src/dactyl-keyboard/dactyl.clj
Lein repl.
load-file "src/dactyl-keyboard/dactyl.clj"
Get this ouput:
#object[clojure.lang.RT$3 0x6106f905 "clojure.lang.RT$3@6106f905"]
"src/dactyl_keyboard/dactyl.clj"

And no changes to things/*scad files or to OpenSCAD render?

I recently printed out a 4x5 right dactyl-manuform from the STL in the repo here, and threw on some spare switches and DSA keycaps to test out the feel. After messing around for a while, I noticed that one of the thumb keycaps hits the case. See images for exact location.

Hi. 3d models, 5x6 in particular, seem to not be manifold and can't be sliced by slic3r
Is it known issue?

https://imgur.com/a/tcvJX

Although it doesn't affect the keyboard usage, the extra inner wall should be removed.
Which lines should I look into?

Is there a 3d printable plate file? Or how do I generate one?