michael bova- project lead kevin alderfer- lead engineer ryan selig- hardware engineer p13015-...

20
Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

Upload: violet-walton

Post on 26-Dec-2015

215 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

Michael Bova- Project LeadKevin Alderfer- Lead Engineer

Ryan Selig- Hardware Engineer

P13015-Navigation Aid for Visually-

Impaired

Page 2: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

eZ430-RF2500

Page 3: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired
Page 4: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

Why choose new design?

Page 5: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

Benefits

Easier integration of transceiver into design

Controllable output power/read range for each tag/node

Lower power consumptionOn-board antennasFuture improvements: Can transmit

more data than just an ID

Page 6: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

New Challenges

Redesigning the PCBUpdating software to utilize eZ430-

RF2500Staying under budgetCreating battery packs

Page 7: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

Software

UML Functional Diagram (for each system below):

Main MSP430ReceiverTransmitter

Page 8: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

Navigation Functional Diagram

Page 9: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

Map Data Structures

Page 10: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

h

Magnetometer Function Diagram

Page 11: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

Access Point

Page 12: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

End Device

Page 13: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

Programmable Output Power

Output Power (dBm)

Read Range (m) Operating Voltage (V)

0 34 3.2

-20 10 2.7

-26 3-4 2.5

-28 1.5-3 2.5

-30 0.5-1 2.5

Page 14: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

Hardware

Existing Design (block diagram)Changes neededProposed new design (block diagram)Proposed schematic/PCB for eZ430-

RF2500 interfaceRange limiting/funneling

Page 15: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

Changes Made / Considered

Removed RFID H10223 connector

Removed LT1930 switching regulatorIncrease in Voltage no longer necessary due to

RFID removal

Consider adding Germanium diode between Li-Ion battery and Access Point for miniscule Voltage decrease (~0.2V)

Page 16: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

Demos

eZ430-RF2500 network with different output powers

Input/Output (Keypad/Motors)

Page 17: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

Task Management If design is done, order PCB by end of Finals week and eZ430s(Fall quarter). Update map file (Week 1) Purchase supplies for battery packs (Week 1) Update transmitting data (from temperatures to IDs) (Week 2) Test PCB from fab (Week 2) Assemble battery packs (Week 3) Replace reader code with eZ430 code (Week 4) Program each individual end device (Week 4) Test communication between nodes and receiver after integration (Week 5) Fix magnetometer code (Week 6) Test/improve path following (Week 7) Test/improve path finding (time permitted) Full system testing (Week 8) Write technical paper (Week 9) Create final product poster board (Week 10) Demo (Week 10)

Page 18: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

Bill of Materials

Item Quantity Cost

eZ430-RF2500t 8 $160

eZ430-RF2500t 2 Borrowed

AAA batteries 20 $7.97

PCB Prototype 3 ($5/in^2)

AAA Battery Holder 10 $15.00 Battery/Spy-Bi-Wire connector 10 ?

Keypad 1 Inhereted

Magnetometer 1 Inhereted

Motors 4 Inhereted

Lithium Ion Battery 1 Inhereted

MSP430 Dev Kit 1 Borrowed

Sleeve 1 Inhereted

Plastic Housing 1 Inhereted

Page 19: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

Major Risks

Not receiving PCB on scheduleFailing to meet customer

demands/deadlines due to reduced team size

Staying under budgetGauging workload incorrectly

Page 20: Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired

Questions? Comments? Concerns?

Thank you for your feedback!