1. 5/13/2011 Andrew Hobson Andrew Vitkus Evan Gelfand Sponsor: Dr. DeBartolo PHASE III P11003 Dynamic Keyboard Phase II Dynamic Keyboard Phase III

2.  Overview  Customer Needs and Engineering Specifications  Concept Selection  System Architecture  Mechanical/ Electrical Design Overview  Testing Results  Current State  Successes and Failures  Next Step  What would We Change?  Questions? Agenda

3.  Design and manufacture a PC keyboard that will sense key pressure  Utilize Dynamic Keyboard, Phase I, and Dynamic Keyboard Phase II recommendations  Hand off Dynamic Keyboard, Phase III, so that Phase IV will create software applications Dynamic Keyboard Overview Dynamic Keyboard Phase III

4. Customer Needs and Engineering Specifications Customer Need # Description CN1 Ability to portray expression through learned ability CN2 Integration to PC through standard connections CN3 Ability to differentiate individual key strike events, and associate them to corresponding sensor events in time. CN4Simple keyboard functionality CN5Must be reliable CN6Establish a high level of device precision CN7 Design or consider other keyboard configurations for future teams Engr. Spec. # Specification (description) Unit of Measure Ideal Value ES1Keystroke has tactile FeelBooleanYes ES2 Individual keys will be able to withstand at least 10N of force (2.25lbs) Max force (N)10 ES3Total component costsDollars ($)<1000 ES6Force Response RangeForce (N)2.5 ES9Precision of force sensor% error±5% ES17Keyboard drivers-Original ES20Type of PC InterfaceTypeUSB ES21Paired Character DataBooleanYes Key Customer NeedsKey Engineering Specifications

5. Concept Selection Concept Selection from MSDI

6. System Architecture Overview System Architecture Block Diagram

7. Assembly Overview Modified Bottom Casing Fabricated Wedge Custom PCB with Force Sensors Modified Top Casing 4-40 x 1” Screws Fabricated Band Dynamic Keyboard Exploded View

8.  Chose SpecResearch K-558/U keyboard for aesthetics, cost, and space for electronics  Used standard domes (not foam)  Reversible construction  Used standard size fasteners (4-40 x 1” SHCS) Mechanical Design Overview SpecResearch K-558/U

9. Electrical Design Overview  Single PCB design  USB interface  86 Pressure Sensors (Force Sense Resistor)  Implemented Arduino Nano MCU  2 RGB-LED provide feedback  Sends Key-Pressure paired data  Sampling frequency up to 60 Hz  Keyboard hardware interface API  Integrated with original keyboard hardware Arduino Nano MCU

10.  Mechanical Specifications: weight, dimensions, cable length all exceeded customer specifications  Electrical Specifications: signal delay, sample rate, power required, controller resolution, operating frequency met or exceeded customer specifications Testing Results Overview Custom Made Pressure Testing Fixture

11. Pressure Testing Results Graph of Key Pressure Testing Results

12.  Keyboard is built and operational  Dual functionality  Standard Keyboard  Dynamic Keyboard  LEDs provide visual feedback for users  Outputs Key-Pressure paired data  Functional Keyboard software suite Current State Assembled Dynamic Keyboard Phase III

13. Successes and Failures SolidWorks Top View of Pressure Sensors on PCB SuccessesFailures Able to communicate between SolidWorks and PCB Artist Wedge had to be re- designed Custom PCB/ keyboard matrix alignments Keyboard selection Positive feedback at ImagineRIT F10, F11 buttons do not function Only one “spin” of PCB required Custom PCB and FSRs took up majority of budget Extra FSRs left overMechanical Noise Under budgetDome placement

14.  Normalize sensor values  Further develop controller API  Develop software applications that utilize the key- pressure data.  Applications: text size and color change, shortcuts to programs, enhanced passwords, shorthand writing, autocorrect, gaming, ergonomics Next Step Proposed Text Application

15.  Design smarter sensor matrix PCB configuration  Use brand name keyboard with single dome pad  Enhanced mechanical support  Use a microcontroller with faster ADC  Further develop software  Perform more rigorous testing What Would We Change? Dome Pad

16. Questions?