1 / 11

Sensor-Aided Smart Vehicle Management System

Residents of a gated community face security problems due to extra actions needed for vehicle access. Learn about a sensor-aided solution that simplifies vehicle entry without compromising security. Follow the journey of Group 18 in developing this innovative system under the guidance of Dr. Daji Qiao and advisors. Explore the challenges faced and solutions implemented to ensure efficient vehicle management.

rransom
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 Midterm 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. Project Plan • Plan and Design Documents (1st Semester) • Implementation (January/February 2010) • 2 group members: TelosB Mote programming • 2 group members: database and web management console development • Testing (March/April 2010) – start March 1! • Non-Vehicle Testing (first 2 weeks) • Vehicle Testing

  5. Project Design

  6. Implementation: Work Sessions • Group Work Sessions every Thursday for 2-3 hours • Review project progress • Demo new working components • Assign new tasks • Troubleshoot code and hardware • Guaranteed, collaborative work time • Bulk of work done individually, outside of scheduled work sessions

  7. Implementation: Component Status • Database/Management Web Console • Complete! Needs aesthetic work. • Database modified as needed. • Control Software/Vehicle Sensor • Able to send and receive data via the mesh sensor through serial device. • Reads and writes MySQL database through MySQL C API. • Still needs to handle unpaired messages and gate relay controller.

  8. Implementation: Component Status • Vehicle Sensor • Sends and receives data from user sensor. • Forwards paired messages to gate sensor. • Power and signal management still in progress. • User Sensor • Functionality complete! • Power and signal management still in progress. • Mesh Node • Half complete: forwards data to gate sensor, but does not receive data from vehicle sensors.

  9. Implementation: Issues Encountered • Power management • Not clearly defined in TinyOS documentation • Signal strength • Control Software/Database Communication • API requires gcc flags not clearly defined • Took some time to figure out • Gate Sensor • Required multithreading, only provided in BaseStation sample code

  10. Rest of Semester • Implementation continues through February • Non-Vehicle/Functionality Testing starts March 1 • In-Vehicle Testing starts March 15 • Poster Design starts during In-Vehicle Testing

  11. Questions ?

More Related