Difference between revisions of "F15: TopGun"

From Embedded Systems Learning Academy
Jump to: navigation, search
m (→‎Team Members & Responsibilities)
(→‎Schedule)
Line 45: Line 45:
 
== Schedule ==
 
== Schedule ==
 
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.
 
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.
 +
 +
=Team Schedule=
 +
{| class="wikitable"
 +
|-
 +
! scope="col"| Week#
 +
! scope="col"| Scheduled
 +
Completion Date
 +
! scope="col"| Task
 +
! scope="col"| Concerned Team
 +
! scope="col"| Status
 +
|-
 +
! scope="row"| 1
 +
| 9/20
 +
| Understanding flow of whole project
 +
*Discussion with the team about the individual devices
 +
*Creating teams and assigning tasks to each team
 +
|
 +
| Completed
 +
|-
 +
! scope="row"| 2
 +
| 9/27
 +
|
 +
*Making decision which hardware components should be used and order them
 +
*Going through the datasheets of individual components and have the software ready for testing till the hardware is in hand
 +
*Start learning the Android studio
 +
*Interface RC car motors with LPC
 +
*Interface ADC ultrasonic sensor to the LPC and filter readings
 +
|
 +
*
 +
*
 +
*Team #3
 +
*Team #1
 +
*Team #4
 +
| Completed
 +
|-
 +
! scope="row"| 3
 +
| 10/4
 +
| Testing of individual modules and their components
 +
*Get the ping sensor readings filtered
 +
*Get the GPS readings filtered
 +
*interfacing of bluetooth module to LPC
 +
*Understand the Google Maps API - Performing basic marker placement on maps and performing routing between markers
 +
*Understand the working of the IMU sensors 
 +
*Printing Texts on LCD module
 +
|
 +
*Team #5
 +
*Team #2
 +
*Team #3
 +
*Team #3
 +
*Team #4
 +
*Team #1
 +
| Completed
 +
|-
 +
! scope="row"| 4
 +
| 10/6
 +
| Basic Hardware layout on RC Car
 +
|
 +
* Team #1
 +
| Completed
 +
|-
 +
! scope="row"| 5
 +
| 10/13
 +
| Obstacle avoidance on RC Car 
 +
|
 +
* Team #1
 +
| Completed
 +
|-
 +
! scope="row"| 6
 +
| 10/20
 +
| CAN bus setup between all 5 controllers
 +
*Sending data from Slave controllers to the Master controller
 +
*Soldering the CAN circuit and fixing on the RC car
 +
*Get the IMU(Compass) readings filtered and ready
 +
 +
|
 +
 +
* Team #2
 +
* Team #1
 +
* Team #4
 +
| In progress
 +
|-
 +
! scope="row"| 7
 +
| 10/27
 +
|
 +
*Android App and its interface with LPC - Use android application to get way point data between source and destination, transmit the data to bluetooth module on the car using bluetooth API 
 +
|
 +
*Team 3
 +
| In Progress
 +
|-
 +
! scope="row"| 8
 +
| 11/14
 +
|
 +
* Driving algorithm development
 +
* Getting all the hardware fixed on the RC car
 +
|
 +
* Team #1,#4
 +
* Team #1
 +
| In progress
 +
|-
 +
! scope="row"| 9
 +
| 11/27
 +
| Driving algorithm deployment and testing
 +
|
 +
| Not completed
 +
|-
 +
! scope="row"| 10
 +
| 12/1
 +
| Debugging
 +
|
 +
| Not Completed
 +
|-
 +
|}
 +
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-

Revision as of 07:07, 23 October 2015

Grading Criteria

  • 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.

Project Title

Abstract

This section should be a couple lines to describe what your project does.

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.

Team Members & Responsibilities

Motor & I/0 Controller:

  • Anuj Korat
  • Dhruv Kakadiya

Communication Bridge & Android Controller:

  • Anush Shankar
  • Aditya Devaguptapu

Geographical Controller:

  • Chitrang Talaviya
  • Navjot Singh

Master Controller:

  • Divya Dodda

Sensor Controller:

  • Hemanth Konanur Nagendra
  • Akshay Vijaykumar

Treasurer:

  • Anuj Korat

Schedule

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.

Team Schedule

Week# Scheduled

Completion Date

Task Concerned Team Status
1 9/20 Understanding flow of whole project
  • Discussion with the team about the individual devices
  • Creating teams and assigning tasks to each team
 Completed
2 9/27
  • Making decision which hardware components should be used and order them
  • Going through the datasheets of individual components and have the software ready for testing till the hardware is in hand
  • Start learning the Android studio
  • Interface RC car motors with LPC
  • Interface ADC ultrasonic sensor to the LPC and filter readings
  • Team #3
  • Team #1
  • Team #4
 Completed
3 10/4 Testing of individual modules and their components
  • Get the ping sensor readings filtered
  • Get the GPS readings filtered
  • interfacing of bluetooth module to LPC
  • Understand the Google Maps API - Performing basic marker placement on maps and performing routing between markers
  • Understand the working of the IMU sensors
  • Printing Texts on LCD module
  • Team #5
  • Team #2
  • Team #3
  • Team #3
  • Team #4
  • Team #1
 Completed
4 10/6 Basic Hardware layout on RC Car
  • Team #1
 Completed
5 10/13 Obstacle avoidance on RC Car
  • Team #1
 Completed
6 10/20 CAN bus setup between all 5 controllers
  • Sending data from Slave controllers to the Master controller
  • Soldering the CAN circuit and fixing on the RC car
  • Get the IMU(Compass) readings filtered and ready
  • Team #2
  • Team #1
  • Team #4
 In progress
7 10/27
  • Android App and its interface with LPC - Use android application to get way point data between source and destination, transmit the data to bluetooth module on the car using bluetooth API
  • Team 3
 In Progress
8 11/14
  • Driving algorithm development
  • Getting all the hardware fixed on the RC car
  • Team #1,#4
  • Team #1
 In progress
9 11/27 Driving algorithm deployment and testing Not completed
10 12/1 Debugging Not Completed
Week# Scheduled

Completion Date

Task Concerned Team Status
1 9/20 Understanding flow of whole project
  • Discussion with the team about the individual devices
  • Creating teams and assigning tasks to each team
 Completed
2 9/27
  • Making decision which hardware components should be used and order them
  • Going through the datasheets of individual components and have the software ready for testing till the hardware is in hand
  • Start learning the Android studio
  • Interface RC car motors with LPC
  • Interface ADC ultrasonic sensor to the LPC and filter readings
  • Team #3
  • Team #1
  • Team #4
 Completed
3 10/4 Testing of individual modules and their components
  • Get the ping sensor readings filtered
  • Get the GPS readings filtered
  • interfacing of bluetooth module to LPC
  • Understand the Google Maps API - Performing basic marker placement on maps and performing routing between markers
  • Understand the working of the IMU sensors
  • Printing Texts on LCD module
  • Team #5
  • Team #2
  • Team #3
  • Team #3
  • Team #4
  • Team #1
 Completed
4 10/6 Basic Hardware layout on RC Car
  • Team #1
 Completed
5 10/13 Obstacle avoidance on RC Car
  • Team #1
 Completed
6 10/20 CAN bus setup between all 5 controllers
  • Sending data from Slave controllers to the Master controller
  • Soldering the CAN circuit and fixing on the RC car
  • Get the IMU(Compass) readings filtered and ready
  • Team #2
  • Team #1
  • Team #4
 In progress
7 10/27
  • Android App and its interface with LPC - Use android application to get way point data between source and destination, transmit the data to bluetooth module on the car using bluetooth API
  • Team 3
 In Progress
8 11/14
  • Driving algorithm development
  • Getting all the hardware fixed on the RC car
  • Team #1,#4
  • Team #1
 In progress
9 11/27 Driving algorithm deployment and testing Not completed
10 12/1 Debugging Not Completed

Parts List & Cost

Item# Part Desciption Vendor Web link Qty Cost
1 RC Car From Preet http://www.rchobbyexplosion.com/DHK_Hunter_4WD_Short_Course_Truck_with_2_4Ghz_p/dhk8135.htm 1 Free
2 RC Car Battery Amazon http://www.amazon.com/dp/B000HKKZN0/ref=rr_xsim_1_1?ie=UTF8&qid=1443933750&sr=0 1 $24.72
3 Core CPU Supply Amazon http://www.amazon.com/gp/product/B002BHXYSK?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00 1 $12.70
4 CAN Transceiver MCP2551 Microchip http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en010405 15 $20.00
5 Printed Circuit Boards Amazon http://www.amazon.com/Prototyping-Tinned-Universal-Printed-150x200mm/dp/B00N3WTROC/

http://www.amazon.com/Double-Protoboard-Prototype-Printed-Circuit/dp/B00NQ3A50S/

4 $20.13
6 M-F,F-F,M-M Jumper Wires Amazon http://www.amazon.com/Kalevel%C2%AE-120pcs-Multicolored-Female-Breadboard/dp/B00M5WLZDW/ 120 $8.75
7 Servo Motors Amazon http://www.amazon.com/RioRand-TowerPro-micro-Helicopter-Arduino/dp/B00M8RGGFG/ 5 $12.89
8 Ultrasonic Sensors Amazon http://www.amazon.com/gp/product/B00NG8TJ6E?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s02 5 $10.45
9 9 DOF Razor IMU module SparkFun https://www.sparkfun.com/products/10736 1 $74.95
10 FTDI Basic Breakout SparkFun https://www.sparkfun.com/products/9873 1 $14.95
11 LCD Display uLCD-32PTU 4D systems http://www.4dsystems.com.au/product/uLCD_32PTU/ 1 $111.00
12 Bluetooth Module Amazon.com http://www.amazon.com/KEDSUM%C2%AE-Arduino-Wireless-Bluetooth-Transceiver/dp/B0093XAV4U/ 1 $9.99
13 Wire Cutter Amazon http://www.amazon.com/Hakko-CHP-170-Stand-off-Construction-21-Degree/dp/B00FZPDG1K 1 $2.99
14 GPS Sensor Adafruit http://www.adafruit.com/products/746 1 $39.95
15 7-Segment Display From Preet https://www.sparkfun.com/products/retired/9765 1 Free
Total Cost $450

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

Discuss your hardware design here. Show detailed schematics, and the interface here.

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.

CAN Message ID Table

Message ID Task associated with it Data bytes Data values
0x00 Kill switch 1 Data 0/1
0x01 Reset Message 1 Data 0/1
0x02 PowerUp Message Sync 1 Data 0/1
0x03 PowerUp Message Sync Ack 1 Data values(1-5)
0x04 PowerUp Message Ack 1 Data values(1-5)
0x05 Heartbeat Message 1 Data 0/1
0x06 Heartbeat Message Ack 1 Data values(1-5)
0x07 Distance sensor data message 6 Front three sensor, One left, One right and One back (each byte for each sensor)
0x08 Light/Battery sensor data message 2 one for Light and one for Battery status
0x09 Geo data message 8 4 bytes for longitude and 4 bytes for lattitude
0x0A Car pause message 1 Data 0/1
0x0B Car resume message 1 Data 0/1
0x0C Checkpoint message request 1 Data 0/1
0x0D Checkpoint data message 8 Still working with JSON data in Android application
0x0E Driving mode message 1 SLOW / NORMAL / FAST / TURBO
0x0F Speed message from GPS 1 Speed value (in mph)
0x10 Free run car message 1 Data 0/1 -> Just run car with obstacle avoidance
0x11 Error Message 1 Different types of error messages

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.

Retrieved from "http://socialledge.com/sjsu/index.php?title=F15:_TopGun&oldid=18611"