1 / 28

Sensor-Aided Smart Vehicle Management System

Design a system for a gated community ensuring secure vehicle entry using sensors, without extra effort from residents. The system pairs users and vehicles, allowing only authorized access. Requirements include authentication, theft alerts, and gate control for valid pairs. Engineering principles and tradeoffs guide the design. The platform includes TelosB motes, nesC/tinyOS, PHP, and MySQL. Components include gate, mesh, and vehicle sensors, user interface specs, and database design. Testing phases involve component, indoor, and outdoor system testing. Simulation and modeling are key for system validation.

cbreen
Download Presentation

Sensor-Aided Smart Vehicle Management System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Sensor-Aided Smart Vehicle Management System Design Committee Presentation Senior Design – May 2010 – Group 18 Dr. Daji Qiao, Advisor Pasha Kazatsker, Eric Klaus, Eric Mader, Brett Thompson

  2. Problem Statement • Residents of a gated community must act. • Extra actions lead to apathy. • Apathy leads to poor security. • Poor security on vehicles is undesirable!

  3. General Solution • No added effort required. • Sensors provided for identification. • Users are paired with vehicles. • Only authorized pairs are allowed in or out.

  4. Assumptions • Authorized users are in possession of a user sensor whenever attempting to operate a vehicle. • All entrances to the community implement a gate sensor. • Gate sensors shall be powered by a dedicated source, not a battery. • Emergency vehicles shall have the means to enter and exit the community. • Computers used to control the system shall have at least one operational USB port for each gate in the community.

  5. System Limitations • Range of mesh sensors shall be in a maximum range of 60 meters of one another. • Vehicles shall have a location to conceal a vehicle sensor that is within 2 meters of the typical placement of a user sensor. • The user and vehicle sensors shall operate at reasonable levels of battery power consumption.

  6. Requirements • System shall authenticate user and vehicle sensor pairs. • System shall send an alert if a vehicle is being stolen. • System shall command a gate to open for valid user and vehicle sensor pairs.

  7. Engineering Principles • State diagrams • Critical Thinking • Product life cycle • Voltage/Current • Graph Theory • Wireless Communication

  8. Design Tradeoffs • Battery Life vs. reliability/responsiveness • Security vs. accessibility • Security vs. code complexity • Ease of installation vs. elegance • Cost (us) vs. reliability • Cost (clients) vs. reliability

  9. Budget

  10. Schedule/Gantt Chart (Fall)

  11. Schedule/Gantt Chart (Spring)

  12. Platform • TelosB Motes • nesC/tinyOS • PHP • MySQL

  13. Components

  14. System Components

  15. Gate Sensor State Diagram

  16. Mesh Sensor State Diagram

  17. Vehicle Sensor State Diagram

  18. User Interface Specification

  19. User Interface Specification

  20. Database Design

  21. Use Cases

  22. Sequence Diagram: Valid Pairing

  23. Sequence Diagram: Invalid Pairing

  24. Test Plan • PHASE 0: Component Testing • PHASE 1: Indoor System Testing • Using RC Car • Sensors/nodes mounted in test environment • PHASE 2: Outdoor System Testing • Using actual car • Sensors/nodes mounted in test area on campus

  25. Simulation and Modeling

  26. Simulation and Modeling

  27. Simulation and Modeling

  28. Questions

More Related