Power Mouse
Design Team 05
Amy Hicks, Computer Engineer, Archivist Joel Howard, Computer Engineering, So=ware Manager Cody Johnson, Electrical Engineer, Hardware Manager Tara McCarthy, Electrical Engineer, Project Leader Dr. Bahrami, Dr. Ida 12/2/2011 Need and Objective Statement
Need
In the United States each year, consumers use more than 3 billion
disposable batteries. Wireless computer mice are a contributor to the
problem. There must be a mouse that functions using energy it
harvested itself rather than using disposable batteries.
Objective
Our design will attempt to remove the external energy source from a
wireless computer mouse, replacing it with internal devices such as
piezoelectric and electromagnetic generators. The mouse will need to
generate enough power for its own current operation and store power for
quick use later.
2 Design Specification Requirements
1.
Power harvested of 1mW or greater should be captured.
2.
The user should be able to move the mouse with less than 1 Newton of force.
3.
Components of the mouse must funcPon in temperatures of 0°C to 80°C.
4.
Mouse must be completely contained in a single housing.
5.
Cost of the product including parts and labor should not exceed $600.
3 Design Specification Requirements
6. Each power harvesPng technique should have its own power regulaPon system. 7. Must work for at least 8 hours of average use on a full charge. 8. Power harvesPng is done both passive and acPvely 9. AutomaPc alert of criPcal and full power levels. Shows the user the current ba[ery power when 10. requested. 4 Hardware Theory of Operation
•  Use power harvesting devices:
–  Solar panels
–  Dynamo
–  Piezoelectric plates
To generate power to charge a wireless mouse battery
5 Hardware Theory of Operation
Hardware level 2 block diagram
6 Hardware Theory of Operation
Hardware level 2 block diagram
7 Hardware level 2 block diagram
8 Software
9 Software Theory of Operation
10 Software Theory of Operation
•  Software will perform the following tasks:
11 Software Theory of Operation
•  Software will perform the following tasks:
–  Periodically sample the current into and out of the
battery and integrate over time to track state of
charge;
12 Software Theory of Operation
•  Software will perform the following tasks:
–  Periodically sample the current into and out of the
battery and integrate over time to track state of
charge;
–  Periodically sample the voltage across the battery to
determine when battery is ‘full’ and reset state of
charge;
13 Software Theory of Operation
•  Software will perform the following tasks:
–  Periodically sample the current into and out of the
battery and integrate over time to track state of
charge;
–  Periodically sample the voltage across the battery to
determine when battery is ‘full’ and reset state of
charge;
–  Calculate percentage of charge remaining;
14 Software Theory of Operation
•  Software will perform the following tasks:
–  Periodically sample the current into and out of the
battery and integrate over time to track state of
charge;
–  Periodically sample the voltage across the battery to
determine when battery is ‘full’ and reset state of
charge;
–  Calculate percentage of charge remaining;
–  Control 4 green and 1 red LEDs to display this
information to user.
15 Software Theory of Operation
•  Software will run on a PIC24F16KA102
16 Software Theory of Operation
•  Software will run on a PIC24F16KA102
–  ‘Extreme Low Power’ device – down to 275uA
active mode current
17 Software Theory of Operation
•  Software will run on a PIC24F16KA102
–  ‘Extreme Low Power’ device – down to 275uA
active mode current
–  10 bit ADC, up to 9 channel, 500ksps
conversion rate
18 Software Theory of Operation
•  Software will run on a PIC24F16KA102
–  ‘Extreme Low Power’ device – down to 275uA
active mode current
–  10 bit ADC, up to 9 channel, 500ksps
conversion rate
–  500kHz Low-Power FRC Oscillator
19 Software: Level 1 Block Diagram
20 Software: Level 1 Block Diagram
21 Software: Level 2 Block Diagram
22 Software: Level 2 Block Diagram
23 Software: Level 2 Block Diagram
24 Software: Level 2 Block Diagram
25 Software: Pseudocode: Constants
26 Software: Pseudocode: Globals
27 Software: Pseudocode: Globals
28 Software: Pseudocode: Globals
29 Software: Pseudocode: Main Loop
30 Software: Pseudocode: Main Loop
31 Software: Pseudocode: Main Loop
32 Software: Pseudocode: Main Loop
33 Software: Pseudocode: Main Loop
34 Software: Pseudocode: Main Loop
35 Software: Pseudocode: Main Loop
36 Software: Pseudocode: Main Loop
37 Software: Pseudocode: Timer ISR
38 Software: Pseudocode: Timer ISR
39 Software: Pseudocode: Button ISR
40 Questions?
41