Difference between revisions of "F16: Kasper"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Motor I/O Controller)
(→‎Motor I/O Controller)
Line 45: Line 45:
 
|-
 
|-
 
! scope="row"| 1
 
! scope="row"| 1
−
| 09/28/2015
+
| 09/27/2016
−
| 10/04/2015
+
| 10/04/2016
 
| LCD module selection and purchase
 
| LCD module selection and purchase
 
| Completed
 
| Completed
Line 52: Line 52:
 
|-
 
|-
 
! scope="row"| 2
 
! scope="row"| 2
−
| 09/27/2015
+
| 09/27/2016
−
| 10/05/2015
+
| 10/05/2016
 
|
 
|
 
*Studying data sheets(LCD and motor) to get understanding of basic concepts and working of components
 
*Studying data sheets(LCD and motor) to get understanding of basic concepts and working of components
 
*Understanding and proposing driving mechanisms for LCD and motors(DC and servo)
 
*Understanding and proposing driving mechanisms for LCD and motors(DC and servo)
 
| Upcoming Task
 
| Upcoming Task
−
| 10/05/2015
+
| 10/05/2016
 
|-
 
|-
 
! scope="row"| 3
 
! scope="row"| 3
−
| 10/05/2015
+
| 10/05/2016
−
| 10/12/2015
+
| 10/12/2016
 
|  
 
|  
 
*Interfacing motors to SJOne board and developing drivers for the same
 
*Interfacing motors to SJOne board and developing drivers for the same
 
*Interfacing LCD module to SJOne board and developing drivers to display basic texts and symbols
 
*Interfacing LCD module to SJOne board and developing drivers to display basic texts and symbols
 
| Upcoming Task
 
| Upcoming Task
−
| 10/12/2015
+
| 10/12/2016
 
|-
 
|-
 
! scope="row"| 4
 
! scope="row"| 4
−
| 10/12/2015
+
| 10/12/2016
−
| 10/30/2015
+
| 10/30/2016
 
|  
 
|  
 
*Implementation of basic power on RC car run with motors(DC and servo) interfaced to SJOne board  
 
*Implementation of basic power on RC car run with motors(DC and servo) interfaced to SJOne board  
 
*Collaborating with other teams to develop basic obstacle avoidance and testing it
 
*Collaborating with other teams to develop basic obstacle avoidance and testing it
 
| Upcoming Task
 
| Upcoming Task
−
| 11/5/2015
+
| 11/5/2016
 
|-
 
|-
 
! scope="row"| 5
 
! scope="row"| 5
−
| 10/30/2015
+
| 10/30/2016
−
| 11/12/2015
+
| 11/12/2016
 
| Proposals related to speed controls and sensors for the same and integration of LCD module(with data display)
 
| Proposals related to speed controls and sensors for the same and integration of LCD module(with data display)
 
| Upcoming Task
 
| Upcoming Task
−
| 11/12/2015
+
| 11/12/2016
 
|-
 
|-
 
! scope="row"| 6
 
! scope="row"| 6
−
| 11/12/2015
+
| 11/12/2016
−
| 11/25/2015
+
| 11/25/2016
 
| CAN bus communication from motor and I/O controller to other boards
 
| CAN bus communication from motor and I/O controller to other boards
 
| Upcoming Task
 
| Upcoming Task
Line 93: Line 93:
 
|-
 
|-
 
! scope="row"| 7
 
! scope="row"| 7
−
| 11/25/2015
+
| 11/25/2016
−
| 12/15/2015
+
| 12/15/2016
 
| Debugging issues during trial runs and testing out fault cases  
 
| Debugging issues during trial runs and testing out fault cases  
 
| Upcoming Task
 
| Upcoming Task
−
| 12/8/2015
+
| 12/8/2016
 
|  
 
|  
 
|-
 
|-

Revision as of 19:59, 10 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

Motor I/O Controller

Team Members: 

Chethan Palangotu Keshava
Prashant Aithal

Motor & I/O Controller Schedule

SI No. Start Date End Date Task Status Actual Completion Date
1 09/27/2016 10/04/2016 LCD module selection and purchase Completed 10/04/2015
2 09/27/2016 10/05/2016
  • Studying data sheets(LCD and motor) to get understanding of basic concepts and working of components
  • Understanding and proposing driving mechanisms for LCD and motors(DC and servo)
 Upcoming Task 10/05/2016
3 10/05/2016 10/12/2016
  • Interfacing motors to SJOne board and developing drivers for the same
  • Interfacing LCD module to SJOne board and developing drivers to display basic texts and symbols
 Upcoming Task 10/12/2016
4 10/12/2016 10/30/2016
  • Implementation of basic power on RC car run with motors(DC and servo) interfaced to SJOne board
  • Collaborating with other teams to develop basic obstacle avoidance and testing it
 Upcoming Task 11/5/2016
5 10/30/2016 11/12/2016 Proposals related to speed controls and sensors for the same and integration of LCD module(with data display) Upcoming Task 11/12/2016
6 11/12/2016 11/25/2016 CAN bus communication from motor and I/O controller to other boards Upcoming Task 11/15/2015
7 11/25/2016 12/15/2016 Debugging issues during trial runs and testing out fault cases Upcoming Task 12/8/2016

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
6 LCD screen Adafruit 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

Schedule

SI No. Start Date End Date Task Status Actual Completion Date
1 09/28/2016 10/4/2016 GPS and Compass module selection and purchase In Progress
3 10/5/2016 10/11/2016 Pin Identification and connection diagram In Progress
4 10/12/2016 10/18/2016 GPS Firmware Development and individual testing Upcoming Task
5 10/19/2016 10/25/2016 Compass Firmware Development and individual testing Upcoming Task
6 10/26/2016 11/01/2016 Calibrating GPS and Compass Module Upcoming Task
7 11/02/2016 11/08/2016 Communication with Master using CAN Upcoming Task
8 11/09/2016 11/15/2016 Testing and debugging with whole system 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.

Communication Bridge Controller

Team Members & Responsibilities

  • Bharat Khanna
  • Shantanu Vashishtha


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 Study previous project reports and order Bluetooth module and other components based on the following:
  • Power requirement, preferably with input voltage within SJOne board output voltage range.
  • Review of the components that give few or no hardware errors.
  • Decide about placement of modules and components in the car.
 In Progress
3 10/5/2016 10/11/2016
  • Understanding Bluetooth module hardware design, configuring the pins to be used on SJone board for communication with the module.
  • Plan on the design/layout for accomodating all the components on a single board.
 In Progress
4 10/12/2016 10/18/2016
  • Designing project architecture based on the bluetooth protocol, 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
  • Work on Bluetooth firmware development to integrate with SJ one board.
  • Planning methods of testing Bluetooth module.
 Upcoming Task
6 10/26/2016 11/08/2016
  • Develope basic Android application to work with the Bluetooth module.
  • Test the communication between SJ one board and Android application over Bluetooth protocol.
 Upcoming Task
7 11/9/2016 11/20/2016
  • Interface Bluetooth module with CAN.
  • Integration with GPS module. Testing and fine tuning the communcation.
  • Testing the Bluetooth module with Master controller using CAN communication
 Upcoming Task
8 11/21/2016 12/05/2016
  • Work on Android app GUI enhancements like Google Maps, Google Drive etc.
  • Testing and debugging of the complete system.
 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.

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
  • Finalise on the CAN transceiver to be used and place an order for the same
 Completed 10/02/2016
2 10/03/2016 10/11/2016
  • Finalise on the node addresses and message IDs for each of the CAN controllers
 In Progress
3 10/12/2016 10/18/2016
  • Understand the overall hardware design and build the car
  • 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
  • Co-ordinate during the integration of the motor and sensor modules from the Master Controller perspective
  • 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=28316"