-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TRRS support #4
Comments
I would like to restore the features currently lost between the forks, including TRRS. However, I’m not sure that a circular aperture would suffice. Geometrically, a normal through-hole-mountable TRRS jack, or even a breakout board, is more complicated than the RJ9s I’ve been using. Do you have schematics for a specific design, or a drawing of the kind of mount you have in mind? |
I don't have a particular TRRS socket in mind. Mostly, I find the available TRRS cables nicer to work with than the available RJ-9. For example, it's possible to get sleeved TRRS, but not sleeved RJ-9. |
For lack of a general solution, consider the following: When you get a specific socket, model that and use the model as negative space inside a cuboid. Divide the result into two halves, like a casting mold, and print them. Then you would have an adapter. Ideally, the two halves would fit so neatly around your socket that you could take this separately printed cuboid adapter and your TRRS socket and slide them snugly into the DMOTE case where I put my RJ9. If that works, I would be happy to accept the model of your socket, and of the adapter, as options for the DMOTE. A quick-and-dirty solution, without the CAD work, would be to embed your sockets in something like Kneadatite (or wood, or whatever), which takes both paint and punishment. |
The original dactyl used a TRRS connector instead of RJ-9. It would be nice to have support for choosing either a circular aperture or a rectangular one for the board-to-board connector so that a TRRS jack would still be possible.
The text was updated successfully, but these errors were encountered: