Difference between revisions of "F16: Kasper"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Schedule)
(Master Controller Schedule updated)
Line 22: Line 22:
 
**Ankit Gandhi
 
**Ankit Gandhi
 
**Bharat Khanna
 
**Bharat Khanna
−
* [[#Central Controller|''Central Controller'']]
+
* [[#Master Controller|''Master Controller'']]
 
**Aajna Karki
 
**Aajna Karki
−
**Spoorthi Shivakumar
+
**Spoorthi Mysore Shivakumar
 
* [[#Communication Bridge Controller|''Communication Bridge Controller'']]   
 
* [[#Communication Bridge Controller|''Communication Bridge Controller'']]   
 
**Bharat Khanna
 
**Bharat Khanna
Line 253: Line 253:
 
Make a smooth transition to testing section and described what it took to test your project.
 
Make a smooth transition to testing section and described what it took to test your project.
  
−
== Central Controller ==
+
== Master Controller ==
 
=== Team Members & Responsibilities ===
 
=== Team Members & Responsibilities ===
  
 
*''''' Aajna Karki '''''   
 
*''''' Aajna Karki '''''   
−
*''''' Spoorthi Shivakumar '''''
+
*''''' Spoorthi Mysore Shivakumar '''''
  
 
=== Schedule ===
 
=== Schedule ===
 +
{| class="wikitable"
 +
|-
 +
! scope="col"| SI No.
 +
! scope="col"| Start Date
 +
! scope="col"| End Date
 +
! scope="col"| Task
 +
! scope="col"| Status
 +
! scope="col"| Actual Completion Date
 +
|-
 +
! scope="row"| 1
 +
| 09/26/2016
 +
| 10/02/2016
 +
|
 +
* Understand the tasks involved and the overall scope of the Master Controller
 +
| Completed
 +
|
 +
|-
 +
! scope="row"| 2
 +
| 10/03/2016
 +
| 10/11/2016
 +
|
 +
* Finalise on node addresses and message IDs for each of the CAN controllers
 +
| In Progress
 +
|
 +
|-
 +
! scope="row"| 3
 +
| 10/12/2016
 +
| 10/18/2016
 +
|
 +
* Build the car considering the overall hardware design
 +
* Implement a way to stop the car which would help control crashes during initial integration testing
 +
| Upcoming Task
 +
|
 +
|-
 +
! scope="row"| 4
 +
| 10/19/2016
 +
| 10/25/2016
 +
|
 +
* Research on the algorithms to be designed - Obstacle avoidance and Navigation
 +
|Upcoming Task
 +
|
 +
|-
 +
! scope="row"| 5
 +
| 10/26/2016
 +
| 10/31/2016
 +
|
 +
* Integration of the motor and sensor modules
 +
* Establish communication across different CAN controllers interfaced
 +
| Upcoming Task
 +
|
 +
|-
 +
! scope="row"| 6
 +
| 11/01/2016
 +
| 11/08/2016
 +
|
 +
* Acquire periodic data from Sensor and Bluetooth controllers and provide the data to the Motor controller
 +
| Upcoming Task
 +
|
 +
|-
 +
! scope="row"| 7
 +
| 11/9/2016
 +
| 11/17/2016
 +
|
 +
* Implement the Obstacle Avoidance Algorithm based on the sensor data received
 +
* Integrate the Geographical Controller and test the algorithm for functionality
 +
| Upcoming Task
 +
|
 +
|-
 +
! scope="row"| 8
 +
| 11/18/2016
 +
| 11/22/2016
 +
|
 +
* Communicate with the Bluetooth controller to send and receive updates from the Geographical Controller
 +
| Upcoming Task
 +
|
 +
|-
 +
! scope="row"| 9
 +
| 11/23/2016
 +
| 11/30/2016
 +
|
 +
* Implement the Navigation algorithm based on the data received from the Geographical controller
 +
| Upcoming Task
 +
|
 +
|-
 +
! scope="row"| 10
 +
| 12/01/2016
 +
| 12/15/2016
 +
|
 +
* Test extensively and debug issues
 +
| Upcoming Task
 +
|
 +
|-
 +
|}
 +
 +
  
 
=== Design & Implementation ===
 
=== Design & Implementation ===

Revision as of 19:02, 9 October 2016

Project Title

Self Driving Car

Abstract

This project implements a self-driving car.

Objectives & Introduction

Objective of this project is to create a self driving car

Team Members & Responsibilities

We have used five controllers

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

SI No. Start Date End Date Task Status Actual Completion Date
1 09/20/2016 09/27/2016
  • Dividing the project into smaller tasks.
  • Based on the number of tasks allocating each task to a team of two.
 Completed 09/27/2016
2 09/28/2016 10/4/2016 Reading previous reports and plan accordingly for each task.Ordering components based on
  • The power requirement, Preferable if the input voltage is in the range of SJOne output voltage level.
  • Review of the components that give few or no hardware errors.
  • Placement of modules in the car.
 In Progress
3 10/5/2016 10/11/2016 Understanding Hardware design and requirements of each task. In Progress
4 10/12/2016 10/18/2016 Designing project architecture based on the protocol for communication, power requirement and the number of special purpose GPIO on the SjOne board.
  • CAN message ID's, priorities, data size and format proposals for all the possible CAN messages on the bus
 Upcoming Task
5 10/19/2016 10/25/2016 Planning methods of testing individual modules based on communication protocols used. Upcoming Task
6 10/26/2016 11/08/2016 Integrating Sensor modules with SJone board
  • Development of obstacle avoidance algorithm with sensor integration
  • Developing Master for CAN communication
  • Integrating Mobile app with the Controller
 Upcoming Task
7 11/9/2016 11/20/2016 Testing Individual sensor with Master controller using CAN communication Upcoming Task
8 11/21/2016 12/05/2016 Integrating & Testing after connecting all sensors to the controller Upcoming Task

Parts List & Cost

Item# Part Desciption Vendor Qty Cost $
1 RC Car From Preet 1 0
2 SJOne board Preet 5 80
3 GPS Module From Preet 1 40
4 Triple Axis Magnetometer (Compass) Sparkfun 1 15
5 Bluetooth Module Sparkfun 1 24.95

Sensor Controller

Team Members & Responsibilities

  • Shruthi Narayan
  • Rimjhim Ghosh

Schedule

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.

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.

Motor & I/O Controller

Team Members & Responsibilities

  • Chethan Keshava
  • Prashant Aithal

Schedule

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.

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.

Geographical Controller

Team Members & Responsibilities

  • Ankit Gandhi
  • Bharat Khanna

Schedule

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.

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.

Communication Bridge Controller

Team Members & Responsibilities

  • Bharat Khanna
  • Shantanu Vashishtha

Schedule

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.

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.

Master Controller

Team Members & Responsibilities

  • Aajna Karki
  • Spoorthi Mysore Shivakumar

Schedule

SI No. Start Date End Date Task Status Actual Completion Date
1 09/26/2016 10/02/2016
  • Understand the tasks involved and the overall scope of the Master Controller
 Completed
2 10/03/2016 10/11/2016
  • Finalise on node addresses and message IDs for each of the CAN controllers
 In Progress
3 10/12/2016 10/18/2016
  • Build the car considering the overall hardware design
  • Implement a way to stop the car which would help control crashes during initial integration testing
 Upcoming Task
4 10/19/2016 10/25/2016
  • Research on the algorithms to be designed - Obstacle avoidance and Navigation
 Upcoming Task
5 10/26/2016 10/31/2016
  • Integration of the motor and sensor modules
  • Establish communication across different CAN controllers interfaced
 Upcoming Task
6 11/01/2016 11/08/2016
  • Acquire periodic data from Sensor and Bluetooth controllers and provide the data to the Motor controller
 Upcoming Task
7 11/9/2016 11/17/2016
  • Implement the Obstacle Avoidance Algorithm based on the sensor data received
  • Integrate the Geographical Controller and test the algorithm for functionality
 Upcoming Task
8 11/18/2016 11/22/2016
  • Communicate with the Bluetooth controller to send and receive updates from the Geographical Controller
 Upcoming Task
9 11/23/2016 11/30/2016
  • Implement the Navigation algorithm based on the data received from the Geographical controller
 Upcoming Task
10 12/01/2016 12/15/2016
  • Test extensively and debug issues
 Upcoming Task


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.

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.


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=F16:_Kasper&oldid=28275"