Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired."— Presentation transcript:

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

2 eZ430-RF2500

3

4 Why choose new design?

5 Benefits Easier integration of transceiver into design Controllable output power/read range for each tag/node Lower power consumption On-board antennas Future improvements: Can transmit more data than just an ID

6 New Challenges Redesigning the PCB Updating software to utilize eZ430-RF2500 Staying under budget Creating battery packs

7 Software UML Functional Diagram (for each system below): Main MSP430 Receiver Transmitter

8 Navigation Functional Diagram

9 Map Data Structures

10 h Magnetometer Function Diagram

11 Access Point

12 End Device

13 Programmable Output Power Output Power (dBm)Read Range (m)Operating Voltage (V) 0343.2 -20102.7 -263-42.5 -281.5-32.5 -300.5-12.5

14 Hardware Existing Design (block diagram) Changes needed Proposed new design (block diagram) Proposed schematic/PCB for eZ430-RF2500 interface Range limiting/funneling

15 Changes Made / Considered Removed RFID H10223 connector Removed LT1930 switching regulator Increase 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)

16 Demos eZ430-RF2500 network with different output powers Input/Output (Keypad/Motors)

17 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)

18 Bill of Materials ItemQuantityCost eZ430-RF2500t8$160 eZ430-RF2500t2Borrowed AAA batteries20$7.97 PCB Prototype3($5/in^2) AAA Battery Holder10$15.00 Battery/Spy-Bi-Wire connector10? Keypad1Inhereted Magnetometer1Inhereted Motors4Inhereted Lithium Ion Battery1Inhereted MSP430 Dev Kit1Borrowed Sleeve1Inhereted Plastic Housing1Inhereted

19 Major Risks Not receiving PCB on schedule Failing to meet customer demands/deadlines due to reduced team size Staying under budget Gauging workload incorrectly

20 Questions? Comments? Concerns? Thank you for your feedback!


Download ppt "Michael Bova- Project Lead Kevin Alderfer- Lead Engineer Ryan Selig- Hardware Engineer P13015- Navigation Aid for Visually-Impaired."

Similar presentations


Ads by Google