||9 months ago|
|keymaps||[Keyboard] add info.json for dactyl_promicro (#6993)||2 years ago|
|config.h||Remove `DESCRIPTION`, H-J (#11616)||1 year ago|
|dactyl_promicro.c||Remove empty override functions (#14312)||9 months ago|
|dactyl_promicro.h||[Keyboard] add info.json for dactyl_promicro (#6993)||2 years ago|
|info.json||Remove width, height and key_count from info.json (#14274)||9 months ago|
|readme.md||[Keyboard] handwired dactyl with 2 pro micros added (#5113)||3 years ago|
|rules.mk||Remove firmware size impact notes from <keyboard>/rules.mk (#14652)||9 months ago|
See https://github.com/adereth/dactyl-keyboard for the original Version.
This Dactyl uses the Arduino Pro Mirco (2x). Wiring is a 6x6 Matrix like the Dactyl Manuform
make handwired/dactyl_promicro:<keymapname>, for example
How to setup your build enviroment can be found here: Installing Build Tools
Apart from diodes and key switches for the keyboard matrix in each half, you will need:
Alternatively, you can use any sort of cable and socket that has at least 3 wires. If you want to use I2C to communicate between halves, you will need a cable with at least 4 wires and 2x 4.7kΩ pull-up resistors
A speaker can be hooked-up to either side to the
C6) pin and
GND, and turned on via
The 3 wires of the TRS/TRRS cable need to connect GND, VCC, and digital pin 3 (i.e. PD0 on the ATmega32u4) between the two Pro Micros.
Next, wire your key matrix to any of the remaining 17 IO pins of the pro micro
and modify the
The wiring for serial:
The wiring for i2c:
The pull-up resistors may be placed on either half. It is also possible to use 4 resistors and have the pull-ups in both halves, but this is unnecessary in simple use cases.
You can change your configuration between serial and i2c by modifying your
the keymaps in here are for the 4x5 layout of the keyboard only.
To flash your firmware take a look at: Flashing Instructions and Bootloader Information.
If you always plug the usb cable into the right board, add an extra flag to your
Do update the
F_CPU parameter in
8000000 which reflects
the frequency on the 3.3V board.
Also, if the slave board is producing weird characters in certain columns,
update the following line in
matrix.c to the following:
// _delay_us(30); // without this wait read unstable value. _delay_us(300); // without this wait read unstable value.