Difference between revisions of "S13: Garage Parking Aid"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Schedule)
(→‎Project Source Code)
 
(139 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
=== Grading Criteria ===
+
== Garage Parking Aid ==
−
<font color="green">
 
−
*  How well is Software & Hardware Design described?
 
−
*  How well can this report be used to reproduce this project?
 
−
*  Code Quality
 
−
*  Overall Report Quality:
 
−
**  Software Block Diagrams
 
−
**  Hardware Block Diagrams
 
−
**:  Schematic Quality
 
−
**  Quality of technical challenges and solutions adopted.
 
−
</font>
 
  
−
== Project Title ==
+
[[File:CmpE146_S13_T3_exterior.jpg|center|frame|'''Garage Parking Aid''']]
  
 
== Abstract ==
 
== Abstract ==
−
This section should be a couple lines to describe what your project does.
+
 
 +
The purpose of this project is to aid when parking a car. This device will send to an Android phone the distance between the car and an obstacle.
  
 
== Objectives & Introduction ==
 
== Objectives & Introduction ==
−
Show list of your objectives.  This section includes the high level details of your project.  You can write about the various sensors or peripherals you used to get your project completed.
+
 
 +
* Measure distance and display on computer screen
 +
* Send data over bluetooth
 +
* Combine bluetooth and ultrasonic
 +
 
 +
[[File:CmpE146_S13_T3_birdeye.jpg|center|frame|Bird's eye view]]
  
 
=== Team Members & Responsibilities ===
 
=== Team Members & Responsibilities ===
−
*  Team Member 1
+
*  Elizabeth
−
**  Driver Development
+
**  Create UART2 driver
−
*  Team Member 2
+
**  Wire peripherals
−
**  FreeRTOS Software Design
+
**  Send messages with Bluetooth
 +
*  Tian
 +
**  Create Android app
 +
**  Assemble project into a box
 +
**  Configure ultrasonic distance meter
  
 +
== Schedule ==
 
<table class="wikitable">
 
<table class="wikitable">
−
<th>Week Number</th> <th>Goal</th> <th>Actual</th>
+
<th>Week Number</th> <th>Planned Items</th> <th>Actual</th>
  
 
<tr>
 
<tr>
Line 33: Line 34:
 
</center> </td>
 
</center> </td>
 
<td>
 
<td>
−
* Recieve 7 PCBs
+
* Receive Bluetooth board
−
* Assemble 2 PCBs
+
* Receive Ultrasonic board
−
* Test PCB Functionality
+
* Complete Schedule
−
* Order remaining parts (connect port x2, extra parts, LEDs)
+
</td>
 +
 
 +
<td>
 +
* Receive bluetooth board
 +
* Receive ultrasonic board
 +
* complete schedule
  
 
</td>
 
</td>
 +
</tr>
 +
 +
<tr>
 +
<td> <center>
 +
2
 +
</center></td>
 
<td>
 
<td>
−
* Proposal
+
* Transmit a signal with bluetooth
−
* Development of PCB design
+
* Andoid app created
−
* Tested all sensors
+
</td>
−
* Setup RTOS
+
 
 +
<td>
 +
* bluetooth wired
 +
* basic Android app created
 +
 
 
</td>
 
</td>
 
</tr>
 
</tr>
  
 +
<tr>
 +
<td> <center>
 +
3
 +
</center></td>
 +
<td>
 +
* Fix bluetooth bugs
 +
* Ultrasound working properly with board
 +
</td>
  
 +
<td>
 +
* send data over bluetooth
  
−
== Schedule ==
+
</td>
−
<table class="wikitable">
+
</tr>
−
<th>Week Number</th> <th>Planned Items</th> <th>Actual</th>
 
  
 
<tr>
 
<tr>
 
<td> <center>
 
<td> <center>
−
1
+
4
−
</center> </td>
+
</center></td>
 
<td>
 
<td>
−
* Receive Bluetooth board
+
* Connect all components
−
* Receive Ultrasonic board
+
* Test
−
* Complete Schedule
 
 
</td>
 
</td>
  
 
<td>
 
<td>
−
* [Actual]
+
* Project put into casing
−
*
+
 
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 71: Line 95:
 
<tr>
 
<tr>
 
<td> <center>
 
<td> <center>
−
2
+
5
 
</center></td>
 
</center></td>
 
<td>
 
<td>
−
* Start on bluetooth
+
* Working device
 +
* Work on reports
 
</td>
 
</td>
  
 
<td>
 
<td>
−
* [Actual]
+
* Device is working
−
*  
+
* Report is being done.
 +
 
 
</td>
 
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
  
−
== Schedule ==
+
== Parts List & Cost ==
−
Show a simple table or figures that show your scheduled as planned before you started working on the project.  Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals.  The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.
 
  
−
<tr><td>Week 1</td></tr>
+
{| class="wikitable"
−
<tr><td>Week 2</td></tr>
+
|-
 +
! Parts
 +
! Cost
 +
|-
 +
| SJ One Board
 +
| $65
 +
|-
 +
| Bluetooth
 +
| $0
 +
|-
 +
| 2.4 GHz Antenna
 +
| $5
 +
|-
 +
| Ultrasonic transmitter and receiver
 +
| $10
 +
|-
 +
| Blackbox
 +
| $0
 +
|-
 +
| Wire
 +
| $10
 +
|-
 +
| Batteries
 +
| $7
 +
|-
 +
! Total:
 +
! $97
 +
|}
  
−
== Parts List & Cost ==
+
== Design & Implementation ==
−
Give a simple list of the cost of your project broken down by components.  Do not write long stories here.
 
  
−
== Design & Implementation ==
 
−
The design section can go over your hardware and software design.  Organize this section using sub-sections that go over your design and implementation.
 
  
 
=== Hardware Design ===
 
=== Hardware Design ===
−
Discuss your hardware design here. Show detailed schematics, and the interface here.
+
 
 +
The following hardware components are all that we used for this project. The LPC1758 Processor on the SJSU_ONE Development Board, which is powered by the battery pack, controls everything through the board. It activates the ultrasonic module, gets the time reading from it, computes the readings into distance and then transfer the data to bluetooth module, then the bluetooth module will send the received data to the Android Application on a paired bluetooth Android Device through the 2.4Ghz Antenna.
 +
 
 +
[[File:CmpE146_S13_T3_LPC1758.jpg|center|frame|SJSU_ONE Development Board]]
 +
 
 +
[[File:CmpE146_S13_T3_bluetooth2.jpg|center|frame|Bluetooth]]
 +
[[File:CmpE146_S13_T3_Bluetooth_Pin.jpg|center|frame|Bluetooth Pin Assignment]]
 +
 
 +
[[File:CmpE146_S13_T3_ultrasonic2.jpg|center|frame|Ultrasonic]]
 +
[[File:CmpE146_S13_T3_Ultra_Pin.jpg|center|frame|Ultrasonic Pin Assignment]]
 +
 
 +
[[File:CmpE146_S13_T3_antenna.jpg|center|frame|2.4 GHz Antenna]]
 +
 
 +
[[File:CmpE146_S13_T3_BatteryPackSmall.jpg|center|frame|4 x AA Battery Pack]]
  
 
=== 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.
+
 
 +
[[File:CmpE146_S13_T3_interior.jpg|center|frame|Interior Connection]]
 +
 
 +
[[File:CmpE146 S13 T3 wiring2.jpg|center|frame|Schematic]]
 +
 
 +
 
 +
 
 +
Hardware Communication: The development board is connected to the bluetooth chip and ultrasonic receiver/transmitter. The bluetooth receives data through pin RX-1, which is TX on the processor's pin, and transmits the data over bluetooth. The ultrasonic receives a trigger signal through the pin Trigger then sends an ultrasonic pulse. When the Echo pin is read back, it will send a high signal to the board for the time it took the sonic wave to be sent then received. The battery gives 5V power to development board and ultrasonic.
 +
 
 +
The Bluetooth device is connected to UART1 and the ultrasonic device is connected to GPIO. To communicate with the Bluetooth, the processor sends and receives data via UART1 TX/RX Pins which are connected to the RX/TX Pins on the bluetooth. RTS pin is tied to CTS pin, which means bluetooth is always clear to send data is ready to send. To communicate with the ultrasonic, the processor sends and receives data through the board's pins P1.20 and P1.19, which are programmed to be output and input ports that directly connect to the Trig and Echo.
 +
 
 +
Another option to capture the time of the ultrasonic's pulse, is to program the GPIO pins to be PWM and capture. The PWM pin will output a pulse to the ultrasonic and the ultrasonic will send an ultrasonic pulse. When it receives an echo of the pulse, it will send a pulse to the capture pin. When the capture pin receives a change in voltage, it will store the time into a designated register. The capture pin can be programmed to capture on rising or falling edge.
  
 
=== Software Design ===
 
=== 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.
+
 
 +
[[File:CmpE146_S13_T3_software.jpg|center|frame|Software Design]]
 +
 
 +
For Software Design on the board side, we have two tasks dedicated for two components: bluetooth_task and ultrasonic_task. We use queue for data transfer between two tasks.
 +
 
 +
'''Ultrasonic_task'''
 +
 
 +
This task takes a queue handle pointer and stores it to its private local variable. Two pins are initialized: Trigger as output, Echo as input. As the task begins to run, the Trigger Pin is set high for 20us then is cleared. This will activate ultrasonic module to send 8 pulses of sound wave. The board will monitor the Echo Pin and once the Echo Pin goes high it will start the timer. When the pin falls back to low it will stop the timer. The time the echo pin is high it is the time for the soundwave to be send and received. To calculate the distance, use the time measured and multiple by the speed of sound, then divided by two, ( Distance = ((Duration of high level)*(Sonic :340m/s))/2 ) After that, we use xQueueSend function to immediately send this distance value to the queue handler, and end this run. This task is designed to run every 2 sec.
 +
 
 +
[[File:CmpE146_S13_T3_Ultra_Code.jpg|center|frame|ultrasonic_task]]
 +
 
 +
'''Bluetooth_task'''
 +
 
 +
This task also takes a queue handle pointer and stores it to a private local variable. In addition, this task has another private variable that will get the instance of Uart2 Class, which controls ports connected to our bluetooth module. The third variable called distance and will store the distance received from the queue. The board has a mislabel Uart1 and is supposed to be Uart2.
 +
 
 +
[[File:CmpE146_S13_T3_Bluetooth_Local.jpg|center|frame|bluetooth_task local variable]]
 +
 
 +
The task first initializes the bluetooth module, then runs in a loop, checking if anything is on the queue, if yes, it immediately receives it, if it is different from the stored value in distance from previous run, store it to local variable, distance, and output a message string containing the distance to the paired android device.
 +
 
 +
[[File:CmpE146_S13_T3_Bluetooth_Code.jpg|center|frame|bluetooth_task]]
 +
 
 +
'''Main Function'''
 +
 
 +
The main function is really simple, it first creates a queue handle with xQueueCreate, then calls both tasks and pass the address of this handle to them.
 +
 
 +
[[File:CmpE146_S13_T3_Main_Code.jpg|center|frame|main function]]
 +
 
 +
'''Android App'''
 +
 
 +
For the Android App, Our design is really simple: the app is going to check if bluetooth on your Android phone is on, if not, it will prompt the user to turn it on; then it is going to start continuously receiving string that is sent from the board via bluetooth, and then parse the string, check for end of line '/r/n', and then display the string at the center of the screen in TextView field, saying how far is your car is to the wall in cm. We pre-loaded the MAC address of the bluetooth module into the app, so we don't have to manually connect to it everytime. But this requires that the bluetooth module is paired with your phone already, and bluetooth permission is granted to the app.
 +
 
 +
[[File:CmpE146_S13_T3_Request_bt.jpg|center|frame|main function]]
 +
 
 +
[[File:CmpE146_S13_T3_Display_distance.jpg|center|frame|main function]]
  
 
=== Implementation ===
 
=== 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.
+
 
 +
 
 +
[[File:CmpE146_S13_T3_flowchart.jpg|center|frame|Flowchart]]
 +
 
 +
The above flow chart is a clear view of the whole process of our project.
 +
 
 +
'''Get reading from Ultrasonic'''
 +
 
 +
1. Set Trigger Pin<br>
 +
2. Clear Trigger Pin<br>
 +
3. Wait for Echo Pin to go High<br>
 +
4. Measure the time duration that Echo Pin stays High<br>
 +
5. Echo Pin falls back to Low<br>
 +
6. Calculate distance: Distance = ((Duration of high level)*(Sonic :340m/s))/2<br>
 +
<br>
 +
<br>
 +
'''Send data through bluetooth'''
 +
 
 +
1. Receive data from queue and store it to an int temp variable<br>
 +
2. Compare temp with local private variable distance<br>
 +
3. If not equal, update temp to distance and send it through bluetooth<br>
 +
4. If equal, skip this data, and start new run and wait for the next available data from queue<br>
 +
<br>
 +
<br>
 +
 
 +
'''Android App'''
 +
 
 +
1. Add permission to AndroidManifect.xml:<br>
 +
    <uses-permission android:name="android.permission.BLUETOOTH_ADMIN" /><br>
 +
    <uses-permission android:name="android.permission.BLUETOOTH" /><br>
 +
2. Set up GUI, add TextView.<br>
 +
3. Check the state of Bluetooth adapter, if not Enable, request to enable.<br>
 +
4. Get the remote device, which is the bluetooth module, using its MAC address, and create a socket for communication using the SPP UUID: "00001101-0000-1000-8000-00805F9B34FB" and connect. Then disable Discovery Mode<br>
 +
5. Create a Thread for receiving input stream, pass the message string to the string handle, parse the string and display in the TextView.
  
 
== Testing & Technical Challenges ==
 
== 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:
+
One major problem during testing, is whenever we point the ultrasonic module towards an object at a bad angle, where the exposed surface of the object is not sufficient, the ultrasonic reading gets stuck and the Echo Pin will keep staying Low. The solution to this problem is to add a timeout inside Ultrasonic_task to break out of the loop after reaching the timeout limit and check the timer to see if the time measured is greater than 0 and less than the time of maximum distance it could support. If the condition returns false, ignore this value and skip the queue process, and re-activated the trigger.
  
−
=== Wifi Connection Issues ===
+
== Conclusion ==
−
Many wifi connection issues were encountered.  To solve this problem, a dedicated task was created to re-connect to wifi if the connection was ever lost.
 
  
−
== Conclusion ==
+
From this project, we gained a better understanding on how FreeRTOS, Uart, Bluetooth communication works. We also learned how to build a simple Android Application associated with Bluetooth. Our project is pretty simple, but this is my (TIAN) first hardware/software hybrid project, where we had to start from the beginning, design, build and code, and finally test. We were stuck several times throughout the project, but with Preet's help, we came through. However, we did not do a good job managing the time, and in the end we were not able to implement some of of features that we wanted in the first place, such as sound warning at a close distance or radar view of the distance. But It is a good experience, and a reference to both of us in our future projects.  
−
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 ===
 
=== Project Video ===
−
Upload a video of your project and post the link here.
+
Initial Demo:
 +
https://www.youtube.com/watch?v=Neq6_BrYMEc&feature=youtu.be
  
 
=== Project Source Code ===
 
=== Project Source Code ===
−
Send me your zipped source code and I will upload this to SourceForge and link it for you.
+
*  [https://sourceforge.net/projects/sjsus13/files/ Project source code is available at SourceForge]
  
 
== References ==
 
== References ==
 
=== Acknowledgement ===
 
=== Acknowledgement ===
−
Any acknowledgement that you may wish to provide can be included here.
+
* Preet Kang
 +
* Dr. Haluk Ozemek
  
 
=== References Used ===
 
=== References Used ===
−
List any references used in project.
+
 
 +
* https://www.sparkfun.com/products/158
 +
* https://s3-ap-northeast-1.amazonaws.com/sain-amzn/20/20-019-100/HC-SR04.rar
 +
* http://wiring.org.co/learning/tutorials/bluetooth/
 +
* http://www.lynxmotion.com/images/html/build117.htm
  
 
=== Appendix ===
 
=== Appendix ===
−
You can list the references you used.
+
 
 +
* http://www.micropik.com/PDF/HCSR04.pdf
 +
* https://www.sparkfun.com/datasheets/Wireless/Bluetooth/rn-bluetooth-um.pdf
 +
* https://www.sparkfun.com/datasheets/RF/BlueSMiRF-RPSMA-Schematic.pdf
 +
* https://www.sparkfun.com/datasheets/RF/BlueSMiRF_v1.pdf

Latest revision as of 21:21, 23 May 2013

Garage Parking Aid

Garage Parking Aid

Abstract

The purpose of this project is to aid when parking a car. This device will send to an Android phone the distance between the car and an obstacle.

Objectives & Introduction

  • Measure distance and display on computer screen
  • Send data over bluetooth
  • Combine bluetooth and ultrasonic
Bird's eye view

Team Members & Responsibilities

  • Elizabeth
    • Create UART2 driver
    • Wire peripherals
    • Send messages with Bluetooth
  • Tian
    • Create Android app
    • Assemble project into a box
    • Configure ultrasonic distance meter

Schedule

Week Number Planned Items Actual

1

  • Receive Bluetooth board
  • Receive Ultrasonic board
  • Complete Schedule
  • Receive bluetooth board
  • Receive ultrasonic board
  • complete schedule

2

  • Transmit a signal with bluetooth
  • Andoid app created
  • bluetooth wired
  • basic Android app created

3

  • Fix bluetooth bugs
  • Ultrasound working properly with board
  • send data over bluetooth

4

  • Connect all components
  • Test
  • Project put into casing

5

  • Working device
  • Work on reports
  • Device is working
  • Report is being done.

Parts List & Cost

Parts Cost
SJ One Board $65
Bluetooth $0
2.4 GHz Antenna $5
Ultrasonic transmitter and receiver $10
Blackbox $0
Wire $10
Batteries $7
Total: $97

Design & Implementation

Hardware Design

The following hardware components are all that we used for this project. The LPC1758 Processor on the SJSU_ONE Development Board, which is powered by the battery pack, controls everything through the board. It activates the ultrasonic module, gets the time reading from it, computes the readings into distance and then transfer the data to bluetooth module, then the bluetooth module will send the received data to the Android Application on a paired bluetooth Android Device through the 2.4Ghz Antenna.

SJSU_ONE Development Board
Bluetooth
Bluetooth Pin Assignment
Ultrasonic
Ultrasonic Pin Assignment
2.4 GHz Antenna
4 x AA Battery Pack

Hardware Interface

Interior Connection
Schematic


Hardware Communication: The development board is connected to the bluetooth chip and ultrasonic receiver/transmitter. The bluetooth receives data through pin RX-1, which is TX on the processor's pin, and transmits the data over bluetooth. The ultrasonic receives a trigger signal through the pin Trigger then sends an ultrasonic pulse. When the Echo pin is read back, it will send a high signal to the board for the time it took the sonic wave to be sent then received. The battery gives 5V power to development board and ultrasonic.

The Bluetooth device is connected to UART1 and the ultrasonic device is connected to GPIO. To communicate with the Bluetooth, the processor sends and receives data via UART1 TX/RX Pins which are connected to the RX/TX Pins on the bluetooth. RTS pin is tied to CTS pin, which means bluetooth is always clear to send data is ready to send. To communicate with the ultrasonic, the processor sends and receives data through the board's pins P1.20 and P1.19, which are programmed to be output and input ports that directly connect to the Trig and Echo.

Another option to capture the time of the ultrasonic's pulse, is to program the GPIO pins to be PWM and capture. The PWM pin will output a pulse to the ultrasonic and the ultrasonic will send an ultrasonic pulse. When it receives an echo of the pulse, it will send a pulse to the capture pin. When the capture pin receives a change in voltage, it will store the time into a designated register. The capture pin can be programmed to capture on rising or falling edge.

Software Design

Software Design

For Software Design on the board side, we have two tasks dedicated for two components: bluetooth_task and ultrasonic_task. We use queue for data transfer between two tasks.

Ultrasonic_task

This task takes a queue handle pointer and stores it to its private local variable. Two pins are initialized: Trigger as output, Echo as input. As the task begins to run, the Trigger Pin is set high for 20us then is cleared. This will activate ultrasonic module to send 8 pulses of sound wave. The board will monitor the Echo Pin and once the Echo Pin goes high it will start the timer. When the pin falls back to low it will stop the timer. The time the echo pin is high it is the time for the soundwave to be send and received. To calculate the distance, use the time measured and multiple by the speed of sound, then divided by two, ( Distance = ((Duration of high level)*(Sonic :340m/s))/2 ) After that, we use xQueueSend function to immediately send this distance value to the queue handler, and end this run. This task is designed to run every 2 sec.

ultrasonic_task

Bluetooth_task

This task also takes a queue handle pointer and stores it to a private local variable. In addition, this task has another private variable that will get the instance of Uart2 Class, which controls ports connected to our bluetooth module. The third variable called distance and will store the distance received from the queue. The board has a mislabel Uart1 and is supposed to be Uart2.

bluetooth_task local variable

The task first initializes the bluetooth module, then runs in a loop, checking if anything is on the queue, if yes, it immediately receives it, if it is different from the stored value in distance from previous run, store it to local variable, distance, and output a message string containing the distance to the paired android device.

bluetooth_task

Main Function

The main function is really simple, it first creates a queue handle with xQueueCreate, then calls both tasks and pass the address of this handle to them.

main function

Android App

For the Android App, Our design is really simple: the app is going to check if bluetooth on your Android phone is on, if not, it will prompt the user to turn it on; then it is going to start continuously receiving string that is sent from the board via bluetooth, and then parse the string, check for end of line '/r/n', and then display the string at the center of the screen in TextView field, saying how far is your car is to the wall in cm. We pre-loaded the MAC address of the bluetooth module into the app, so we don't have to manually connect to it everytime. But this requires that the bluetooth module is paired with your phone already, and bluetooth permission is granted to the app.

main function
main function

Implementation

Flowchart

The above flow chart is a clear view of the whole process of our project.

Get reading from Ultrasonic

1. Set Trigger Pin
2. Clear Trigger Pin
3. Wait for Echo Pin to go High
4. Measure the time duration that Echo Pin stays High
5. Echo Pin falls back to Low
6. Calculate distance: Distance = ((Duration of high level)*(Sonic :340m/s))/2


Send data through bluetooth

1. Receive data from queue and store it to an int temp variable
2. Compare temp with local private variable distance
3. If not equal, update temp to distance and send it through bluetooth
4. If equal, skip this data, and start new run and wait for the next available data from queue


Android App

1. Add permission to AndroidManifect.xml:

   <uses-permission android:name="android.permission.BLUETOOTH_ADMIN" />

   <uses-permission android:name="android.permission.BLUETOOTH" />

2. Set up GUI, add TextView.
3. Check the state of Bluetooth adapter, if not Enable, request to enable.
4. Get the remote device, which is the bluetooth module, using its MAC address, and create a socket for communication using the SPP UUID: "00001101-0000-1000-8000-00805F9B34FB" and connect. Then disable Discovery Mode
5. Create a Thread for receiving input stream, pass the message string to the string handle, parse the string and display in the TextView.

Testing & Technical Challenges

One major problem during testing, is whenever we point the ultrasonic module towards an object at a bad angle, where the exposed surface of the object is not sufficient, the ultrasonic reading gets stuck and the Echo Pin will keep staying Low. The solution to this problem is to add a timeout inside Ultrasonic_task to break out of the loop after reaching the timeout limit and check the timer to see if the time measured is greater than 0 and less than the time of maximum distance it could support. If the condition returns false, ignore this value and skip the queue process, and re-activated the trigger.

Conclusion

From this project, we gained a better understanding on how FreeRTOS, Uart, Bluetooth communication works. We also learned how to build a simple Android Application associated with Bluetooth. Our project is pretty simple, but this is my (TIAN) first hardware/software hybrid project, where we had to start from the beginning, design, build and code, and finally test. We were stuck several times throughout the project, but with Preet's help, we came through. However, we did not do a good job managing the time, and in the end we were not able to implement some of of features that we wanted in the first place, such as sound warning at a close distance or radar view of the distance. But It is a good experience, and a reference to both of us in our future projects.

Project Video

Initial Demo: https://www.youtube.com/watch?v=Neq6_BrYMEc&feature=youtu.be

Project Source Code

References

Acknowledgement

  • Preet Kang
  • Dr. Haluk Ozemek

References Used

Appendix

Retrieved from "http://socialledge.com/sjsu/index.php?title=S13:_Garage_Parking_Aid&oldid=3901"