![\"\"](\"https:\/\/courses.ideate.cmu.edu\/60-223\/f2021\/work\/wp-content\/uploads\/2021\/11\/ezgif-2-76b36e67cfb1.gif\")
Standard use, first four keys 1-4, 5th key mapped to long message<\/p><\/div>\n
![\"\"](\"https:\/\/courses.ideate.cmu.edu\/60-223\/f2021\/work\/wp-content\/uploads\/2021\/11\/MVIMG_20211102_083823-scaled.jpg\")
A cinematic view with plants!<\/p><\/div>\n
![\"\"](\"https:\/\/courses.ideate.cmu.edu\/60-223\/f2021\/work\/wp-content\/uploads\/2021\/11\/MVIMG_20211102_084231-768x1024.jpg\")
Next to a tape measure for scale<\/p><\/div>\n
![\"\"](\"https:\/\/courses.ideate.cmu.edu\/60-223\/f2021\/work\/wp-content\/uploads\/2021\/11\/MVIMG_20211102_083848-1024x768.jpg\")
A top down view of the layout<\/p><\/div>\n
![\"\"](\"https:\/\/courses.ideate.cmu.edu\/60-223\/f2021\/work\/wp-content\/uploads\/2021\/11\/MVIMG_20211102_085352-scaled-e1635857905387-1024x768.jpg\")
A use case example. On a desktop as shortcut keys.<\/p><\/div>\n
Process Photos:<\/h2>\n![\"\"](\"https:\/\/courses.ideate.cmu.edu\/60-223\/f2021\/work\/wp-content\/uploads\/2021\/11\/MVIMG_20211025_063400-1024x768.jpg\")
early component testing, including a mess of wires, resistors, and eraser shavings<\/p><\/div>\n
![\"\"](\"https:\/\/courses.ideate.cmu.edu\/60-223\/f2021\/work\/wp-content\/uploads\/2021\/11\/MVIMG_20211102_090903_2-853x1024.jpg\")
Initial ideation, input and format brainstorming<\/p><\/div>\n
![\"\"](\"https:\/\/courses.ideate.cmu.edu\/60-223\/f2021\/work\/wp-content\/uploads\/2021\/11\/Copy-of-MVIMG_20211102_090853_2-923x1024.jpg\")
struggling to portion out inputs and understanding requirements<\/p><\/div>\n
Decision Points:<\/h2>\n![\"\"](\"https:\/\/courses.ideate.cmu.edu\/60-223\/f2021\/work\/wp-content\/uploads\/2021\/11\/MVIMG_20211102_084035-1024x768.jpg\")
A clear view of the wiring matrix and efficiently used potentiometer power and ground<\/p><\/div>\n
Wiring Strategy<\/p>\n
A critical consideration when designing a custom keyboard is wiring. This was an unexpected step which affected far more than I thought it could. The Arduino pro micro is an exceptional piece of technology, but is only built to handle so many inputs. This has led enthusiasts the apply creative workarounds and allowed them to achieve exceptional results. The critical option for me was individually wiring each switch or forming them in an array and addressing the problem of ghosting with diodes. Individual wiring would be far more messy and setting up buttons in a matrix was generally the practice in most custom boards. I decided to hand wire a neat matrix and follow the steps someone might use for a much larger keyboard to further immerse myself in the learning process. With careful wire stripping and many soldering attempts, I was able to neatly lay out the matrix for eight switch inputs.<\/p>\n
![\"\"](\"https:\/\/courses.ideate.cmu.edu\/60-223\/f2021\/work\/wp-content\/uploads\/2021\/11\/Capture-1.png\")
notoriously buggy flashing software<\/p><\/div>\n
![\"\"](\"https:\/\/courses.ideate.cmu.edu\/60-223\/f2021\/work\/wp-content\/uploads\/2021\/11\/Capture1.png\")
guide for wiring, showing example of for a ‘plank’ layout<\/p><\/div>\n
<\/p>\n
HID vs Arduino<\/p>\n
When sending signals from the Arduino to the computer there are two ways the computer can read them; as input from an Arduino device that needs to be translated, or as native keyboard inputs from an HID. Following the spirit of a fully native keyboard, I attempted to flash my Arduino pro micro using community developed tools. The process of flashing skips over the step where a computer has to read a device as an Arduino before receiving simulated keyboard inputs and would hopefully lead to a more robust tool. This option included several external programs to feed matrix diagrams into very abstract code. Ultimately, despite investing my efforts into this step in order to make a native keyboard device very specific issues, such as a missing .dll file that affected how my computer’s USB port communication left me with software issues I could not understand well enough to fix. I was forced to keep the traditional Arduino input<\/p>\n
Discussion:<\/h2>\n
The construction of a macro keyboard was an insightful and difficult experience in developing a useful tool tailored for myself. By diving into a expansive hobby I learned from a massive array of disciplines and got to understand, first hand, the potentials and difficulties of building and programming a custom keyboard. Fundamentally, the project can be split into hardware and software.\u00a0<\/span><\/p>\nThe hardware component of the experience was significantly more creative and forgiving. Classmate responses noted \u201c…the physical customization of a keyboard\u2026 shows how creative you can be with something that seems really standard.\u201d I felt this was a perfect interpretation of my ideation stage, which saw me find all the possible inputs I could use without writing new fundamental components, like libraries. Unfortunately, my inexperience led to some hardware choices which, in retrospect, were not ideal. This is exemplified by my choice of a potentiometer instead of a rotary encoder. While the potentiometer worked well for volume control, a hardware item with a physical upper and lower limit was not as easy to apply to common computer programs as would have been a simple increase-decrease input (rotary encoder). This taught me that when designing a versatile tool, the more open ended and simple the inputs, the more use it will be.<\/span><\/p>\nA less functional, but still incredibly important aspect of the project is the design. A big motivation between custom keyboards is personalization. One classmate wrote \u201c<\/span>I like how clean the keypad looks with the acrylic base and it\u2019s really nice how you hand-wired everything.\u201d This comment made me very excited to see other people finding joy in customizing something so mundane. <\/span>Through the project I learned about popular styles and where enthusiasts found beauty in electrical tools like keyboards. Hand-wiring and efficiency were popular themes that I subscribed to. Gridded geometric wiring, clear casing, and colorful keycaps were my adoption of the popular design principles in custom keyboards.<\/span><\/p>\nThe software portion of the project was much more rigid and problematic. Here, roadblocks presented themselves left and right, from out of date tools to nuanced device issues. While there was a breadth of experience available, the lack of a single popular resource meant many uncommon issues remained unsolved. Other project documentation often warned of numerous attempts to get fundamental functionality.<\/span><\/p>\n
early component testing, including a mess of wires, resistors, and eraser shavings<\/p><\/div>\n
Initial ideation, input and format brainstorming<\/p><\/div>\n
struggling to portion out inputs and understanding requirements<\/p><\/div>\n
Decision Points:<\/h2>\nA clear view of the wiring matrix and efficiently used potentiometer power and ground<\/p><\/div>\n
Wiring Strategy<\/p>\n
A critical consideration when designing a custom keyboard is wiring. This was an unexpected step which affected far more than I thought it could. The Arduino pro micro is an exceptional piece of technology, but is only built to handle so many inputs. This has led enthusiasts the apply creative workarounds and allowed them to achieve exceptional results. The critical option for me was individually wiring each switch or forming them in an array and addressing the problem of ghosting with diodes. Individual wiring would be far more messy and setting up buttons in a matrix was generally the practice in most custom boards. I decided to hand wire a neat matrix and follow the steps someone might use for a much larger keyboard to further immerse myself in the learning process. With careful wire stripping and many soldering attempts, I was able to neatly lay out the matrix for eight switch inputs.<\/p>\n
notoriously buggy flashing software<\/p><\/div>\n
guide for wiring, showing example of for a ‘plank’ layout<\/p><\/div>\n
<\/p>\n
HID vs Arduino<\/p>\n
When sending signals from the Arduino to the computer there are two ways the computer can read them; as input from an Arduino device that needs to be translated, or as native keyboard inputs from an HID. Following the spirit of a fully native keyboard, I attempted to flash my Arduino pro micro using community developed tools. The process of flashing skips over the step where a computer has to read a device as an Arduino before receiving simulated keyboard inputs and would hopefully lead to a more robust tool. This option included several external programs to feed matrix diagrams into very abstract code. Ultimately, despite investing my efforts into this step in order to make a native keyboard device very specific issues, such as a missing .dll file that affected how my computer’s USB port communication left me with software issues I could not understand well enough to fix. I was forced to keep the traditional Arduino input<\/p>\n
Discussion:<\/h2>\n
The construction of a macro keyboard was an insightful and difficult experience in developing a useful tool tailored for myself. By diving into a expansive hobby I learned from a massive array of disciplines and got to understand, first hand, the potentials and difficulties of building and programming a custom keyboard. Fundamentally, the project can be split into hardware and software.\u00a0<\/span><\/p>\nThe hardware component of the experience was significantly more creative and forgiving. Classmate responses noted \u201c…the physical customization of a keyboard\u2026 shows how creative you can be with something that seems really standard.\u201d I felt this was a perfect interpretation of my ideation stage, which saw me find all the possible inputs I could use without writing new fundamental components, like libraries. Unfortunately, my inexperience led to some hardware choices which, in retrospect, were not ideal. This is exemplified by my choice of a potentiometer instead of a rotary encoder. While the potentiometer worked well for volume control, a hardware item with a physical upper and lower limit was not as easy to apply to common computer programs as would have been a simple increase-decrease input (rotary encoder). This taught me that when designing a versatile tool, the more open ended and simple the inputs, the more use it will be.<\/span><\/p>\nA less functional, but still incredibly important aspect of the project is the design. A big motivation between custom keyboards is personalization. One classmate wrote \u201c<\/span>I like how clean the keypad looks with the acrylic base and it\u2019s really nice how you hand-wired everything.\u201d This comment made me very excited to see other people finding joy in customizing something so mundane. <\/span>Through the project I learned about popular styles and where enthusiasts found beauty in electrical tools like keyboards. Hand-wiring and efficiency were popular themes that I subscribed to. Gridded geometric wiring, clear casing, and colorful keycaps were my adoption of the popular design principles in custom keyboards.<\/span><\/p>\nThe software portion of the project was much more rigid and problematic. Here, roadblocks presented themselves left and right, from out of date tools to nuanced device issues. While there was a breadth of experience available, the lack of a single popular resource meant many uncommon issues remained unsolved. Other project documentation often warned of numerous attempts to get fundamental functionality.<\/span><\/p>\n
A clear view of the wiring matrix and efficiently used potentiometer power and ground<\/p><\/div>\n
Wiring Strategy<\/p>\n
A critical consideration when designing a custom keyboard is wiring. This was an unexpected step which affected far more than I thought it could. The Arduino pro micro is an exceptional piece of technology, but is only built to handle so many inputs. This has led enthusiasts the apply creative workarounds and allowed them to achieve exceptional results. The critical option for me was individually wiring each switch or forming them in an array and addressing the problem of ghosting with diodes. Individual wiring would be far more messy and setting up buttons in a matrix was generally the practice in most custom boards. I decided to hand wire a neat matrix and follow the steps someone might use for a much larger keyboard to further immerse myself in the learning process. With careful wire stripping and many soldering attempts, I was able to neatly lay out the matrix for eight switch inputs.<\/p>\n
notoriously buggy flashing software<\/p><\/div>\n
guide for wiring, showing example of for a ‘plank’ layout<\/p><\/div>\n
<\/p>\n
HID vs Arduino<\/p>\n
When sending signals from the Arduino to the computer there are two ways the computer can read them; as input from an Arduino device that needs to be translated, or as native keyboard inputs from an HID. Following the spirit of a fully native keyboard, I attempted to flash my Arduino pro micro using community developed tools. The process of flashing skips over the step where a computer has to read a device as an Arduino before receiving simulated keyboard inputs and would hopefully lead to a more robust tool. This option included several external programs to feed matrix diagrams into very abstract code. Ultimately, despite investing my efforts into this step in order to make a native keyboard device very specific issues, such as a missing .dll file that affected how my computer’s USB port communication left me with software issues I could not understand well enough to fix. I was forced to keep the traditional Arduino input<\/p>\n
Discussion:<\/h2>\n
The construction of a macro keyboard was an insightful and difficult experience in developing a useful tool tailored for myself. By diving into a expansive hobby I learned from a massive array of disciplines and got to understand, first hand, the potentials and difficulties of building and programming a custom keyboard. Fundamentally, the project can be split into hardware and software.\u00a0<\/span><\/p>\n The hardware component of the experience was significantly more creative and forgiving. Classmate responses noted \u201c…the physical customization of a keyboard\u2026 shows how creative you can be with something that seems really standard.\u201d I felt this was a perfect interpretation of my ideation stage, which saw me find all the possible inputs I could use without writing new fundamental components, like libraries. Unfortunately, my inexperience led to some hardware choices which, in retrospect, were not ideal. This is exemplified by my choice of a potentiometer instead of a rotary encoder. While the potentiometer worked well for volume control, a hardware item with a physical upper and lower limit was not as easy to apply to common computer programs as would have been a simple increase-decrease input (rotary encoder). This taught me that when designing a versatile tool, the more open ended and simple the inputs, the more use it will be.<\/span><\/p>\n A less functional, but still incredibly important aspect of the project is the design. A big motivation between custom keyboards is personalization. One classmate wrote \u201c<\/span>I like how clean the keypad looks with the acrylic base and it\u2019s really nice how you hand-wired everything.\u201d This comment made me very excited to see other people finding joy in customizing something so mundane. <\/span>Through the project I learned about popular styles and where enthusiasts found beauty in electrical tools like keyboards. Hand-wiring and efficiency were popular themes that I subscribed to. Gridded geometric wiring, clear casing, and colorful keycaps were my adoption of the popular design principles in custom keyboards.<\/span><\/p>\n The software portion of the project was much more rigid and problematic. Here, roadblocks presented themselves left and right, from out of date tools to nuanced device issues. While there was a breadth of experience available, the lack of a single popular resource meant many uncommon issues remained unsolved. Other project documentation often warned of numerous attempts to get fundamental functionality.<\/span><\/p>\n
![\"\"](\"https:\/\/courses.ideate.cmu.edu\/60-223\/f2021\/work\/wp-content\/uploads\/2021\/11\/diagramsvgp2.svg\")
<\/p>\n![\"\"](\"https:\/\/courses.ideate.cmu.edu\/60-223\/f2021\/work\/wp-content\/uploads\/2021\/11\/p2elecd.svg\")
<\/a><\/h2>\n