Wires for the keyboard were made by stripping the sheathing from one end of a short piece of Cat5e and crimping an RJ45 end to the other. Wire color coding was matched to the wrist mounted version to ensure compatibility. Since microswitches with flat spade terminals were used each of the key wires was given a receptacle capable of attaching to the switch. Ground wires were configured differently since a ground was required on each switch. Splitting flat spade terminals were used on the first switch of each keypad and each subsequent switch had two wires crimped in the receptacle except the last one.
Wire colors were matched to the switches and the keypads were attached to a programmed Arduino Micro to test all the switches. No problems were seen aside from a debounce issue which was fixed in the code. Switches in this model seem to require a longer debounce time compared to the mini tactile switches used previously.
To do:
The rest of the posts for this project have been arranged by date.
First time here?
Completed projects from year 1.
Completed projects from year 2.
Wire colors were matched to the switches and the keypads were attached to a programmed Arduino Micro to test all the switches. No problems were seen aside from a debounce issue which was fixed in the code. Switches in this model seem to require a longer debounce time compared to the mini tactile switches used previously.
Wired and functional keyboard
To do:
- Build base
- Construct or shape
- Drill wiring holes
- Stain
- Finish
- Attach keypads
Wire buttons to RJ45 connectorAttach to controller and test- Write instructions
The rest of the posts for this project have been arranged by date.
First time here?
Completed projects from year 1.
Completed projects from year 2.
Disclaimer for http://24hourengineer.blogspot.com/
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All
information in this blog, or linked by this blog, are not to be taken
as advice or solicitation. Anyone attempting to replicate, in whole or
in part, is responsible for the outcome and procedure. Any loss of
functionality, money, property or similar, is the responsibility of
those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes
the intellectual property of Brian McEvoy. Any information contained
within these messages may be distributed or retained at the discretion
of Brian McEvoy. Any email sent to this address, or any email account
owned by Brian McEvoy, cannot be used to claim property or assets.
Comments
to the blog may be utilized or erased at the discretion of the owner.
No one posting may claim claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
2015-08-16 (Su)
Comments
Post a Comment