Difference between revisions of "S15: Smart Sparta Parking System"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Hardware Interface)
(= Hardware Interface)
Line 209: Line 209:
 
The function of each module is explained in the hardware implementation part.
 
The function of each module is explained in the hardware implementation part.
  
== Hardware Interface =
+
===== Hardware Interface =====
 
In this section, you can describe how your hardware communicates, such as which BUSes used.  You can discuss your driver implementation here, such that the '''Software Design''' section is isolated to talk about high level workings rather than inner working of your project.
 
In this section, you can describe how your hardware communicates, such as which BUSes used.  You can discuss your driver implementation here, such that the '''Software Design''' section is isolated to talk about high level workings rather than inner working of your project.
  

Revision as of 03:44, 23 May 2015

Abstract

A smart parking system which aid people to find a parking slot at a parking garage with ease. The system will display the available parking slots in real time and will direct the driver to a specified location hence reducing the touble to find one. This employs a bluetooth communication with control center and consumer via an android application.

Objectives & Introduction

This project aims to simplify the parking process in large parking lots. Currently, when a car enters a parking lot, the information provided at the entrance is the total empty spots available. No information regarding where the spots are is provided. If the parking lot is a large one and the spots left are very few, the users face a difficult time finding an empty spot.

What we are doing here is that we tell the user a spot number, based on his car size, where he can park his car. We also have provided the user with an android based mobile application which has a map of the parking lot hence making it easier for the user to find the exact location.

Team Members & Responsibilities

  • Bhargava Leepeng Chandra
    • Android application, Model/Prototype Design
  • Gautam Saily
    • Motor, Nordic Wireless, Model/Prototype Design
  • Niveda Das
    • IR Sensors, Nordic Wireless
  • Rishabh Holenarasipur Sreedhara
    • Display, LDRs, Integration
  • Sujith Durgad
    • Bluetooth, Control Centre

Project Schedule

Week No. Start Date Planned End Date Task Status Actual End Date
1 03/30/2015 04/06/2015
* Design the Project Layout
* Order necessary Hardware
* Task allocation
* GIT version control system setup and integration
  • Completed
Servo motors, IR sensors, LDRs, Bluetooth orders placed. Model basic layout sorted. Git project setup and integrated to eclipse.
04/06/2015
2 04/06/2015 04/13/2015
* Start Model Implementation to position hardware
* Design Android Application UI Layout
* LCD base code testing
* Research Nordic wireless
  • Completed
Model initiated, Android UI defined, Able to test LCD
04/13/2015
3 04/13/2015 04/20/2015
* Bring up parking layout and motors on to Model
* Basic bluetooth code testing
* Basic Nordic wireless design
  • Completed
CAD design for Model completed. The hardware model follows the CAD model to the possible extent. Nordic wireless: Able to send and receive messages between two SJOne boards. Bluetooth in progress
04/21/2015
4 04/20/2015 04/27/2015
* Establish Communication between Nodes using Nordic wireless
* Complete hardware model with Motors, IR sensnors and LDRs installed
* Implement IR sensors, LDRs and Motor (individual operation)
* Update Wiki page
  • Ongoing
--/--/----
5 04/27/2015 05/04/2015
* LCD dispaly Layout for information display with refresh
* Implement Nordic wireless on all three boards
* Verify mutli node communication
* Android App basic initialization and interface with bluetooth
* Update Wiki page
  • Scheduled
--/--/----
6 05/04/2015 05/11/2015
* Integration testing with modular approach
* Fixing issues
* Update Wiki page
  • Scheduled
--/--/----
7 05/11/2015 05/18/2015
* Integration testing of complete system
* Check if all systems are operational
* Test working of system integration
* Fixing issues
* Update Wiki page
  • Scheduled
--/--/----
8 05/18/2015 05/25/2015
* Final testing
* Complete Wiki page project report
* Final demo
  • Scheduled
--/--/----

Parts List & Cost

Index Part Description Part Number Vendor Qty. Price/unit Total Price
1 SJOne Board: ARM Cortex-M3 based LPC1758 Platform -NA- SCE SJSU 3 $80.00 $240.00
2 Bluetooth Bee B005GI4HFA Amazon.com 1 $23.00 $23.00
3 LDRs GM5539 Amazon.com 20 $0.224 $4.88
4 Servo Motor LS-0003 Fry's Electronics 2 $9.99 $21.73
4 IR Sensors
5 MSC Components
6

Design & Implementation

This section consists of the hardware/software design and implementation of our parking system model.

CAD Model for SSPS

Hardware Design

The project model is divided into two parking levels. Both levels have different controllers. The lower level has the master controller and the upper level has the slave controllers. The modules controlled by the master are LCD Display, LED’s, LDR’s, IR Sensors, Servo Motors, Bluetooth Transceiver and Nordic Mesh Network. The modules controlled by slave controller are LDR’s and Nordic Mesh Network.

The function of each module is explained in the hardware implementation part.

Hardware Interface

In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high level workings rather than inner working of your project.

Software Design

Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.

Implementation

This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.

Testing & Technical Challenges

Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.

Include sub-sections that list out a problem and solution, such as:

My Issue #1

Discuss the issue and resolution.

Conclusion

Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?

Project Video

Upload a video of your project and post the link here.

Project Source Code

References

Acknowledgement

Any acknowledgement that you may wish to provide can be included here.

References Used

List any references used in project.

Appendix

You can list the references you used.