You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the README.org file the hand wiring pics as well as the text state "As you can see in these following pictures, I went for the “row-driven” setup (visible by the direction of the diodes, the black line being towards the key-switches). ". However it is my understanding that the black line as the cathode pointing towards the key would indicate the "Drive Columns" type setup would it not?
I think that the firmware has a simple config setting for either selection however that would need you to re-compile it for "Drive Columns" option. Am I correct or am I just a n00b out of his depth?
The text was updated successfully, but these errors were encountered:
I believe you are right. If the black line on the diode is pointing towards the switch, its "Column" driven. The columns will be high and the rows that will be read as inputs.
If you're using the benblazak/ergodox, you can switch the row/column driven option from the /src/keyboard/ergodox/option.h file.
Sorry, I'm wrong in my previous statement. I've wired the diodes such that the cathode is pointing towards the switch which is on an ergodox pcb board the circular solder pad, therefore its DRIVE_ROWS.
mostley
referenced
this issue
in mostley/blender-dactyl-keyboard
Nov 14, 2021
In the README.org file the hand wiring pics as well as the text state "As you can see in these following pictures, I went for the “row-driven” setup (visible by the direction of the diodes, the black line being towards the key-switches). ". However it is my understanding that the black line as the cathode pointing towards the key would indicate the "Drive Columns" type setup would it not?
I think that the firmware has a simple config setting for either selection however that would need you to re-compile it for "Drive Columns" option. Am I correct or am I just a n00b out of his depth?
The text was updated successfully, but these errors were encountered: