Difference between revisions of "F16: Thunderbolt"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Schedule)
(→‎Motor & I/O Controller)
Line 345: Line 345:
 
* '''Virginia Menezes'''
 
* '''Virginia Menezes'''
 
* '''Saurabh Deshmukh'''
 
* '''Saurabh Deshmukh'''
 +
 +
 +
=== Schedule ===
 +
{| class="wikitable"
 +
|-
 +
! scope="col"| Sr No
 +
! scope="col"| Start Date
 +
! scope="col"| End Date
 +
! scope="col"| Task
 +
! scope="col"| Status
 +
! scope="col"| Actual Completed Date
 +
|-
 +
! scope="row"| 1
 +
| 9/19/2016
 +
| 9/24/2016
 +
|
 +
* Understanding the motor and PWM concept.
 +
| Completed
 +
| 9/25/2016
 +
|-
 +
! scope="row"| 2
 +
| 10/4/2016
 +
| 10/5/2016
 +
|
 +
* Testing Servo and DC motor using RC Transmitter and Receiver.
 +
| Completed
 +
| 10/5/2016
 +
|-
 +
! scope="row"| 3
 +
| 10/7/2016         
 +
| 10/10/2016
 +
|
 +
* Testing and interfacing of servo and DC motor with SJOne Board
 +
|In Progress
 +
|-
 +
|-
 +
! scope="row"| 4
 +
| 10/11/2016         
 +
| 10/18/2016
 +
|
 +
* Design of CAN message ID for motor controller.
 +
|-
 +
|-
 +
|-
 +
! scope="row"| 5
 +
| 10/20/2016
 +
| 10/24/2016
 +
|
 +
* Design a power circuit on RC car with motors interfaced to SJOne board.
 +
|-
 +
|-
 +
|-
 +
! scope="row"| 6
 +
| 11/01/2016
 +
| 11/08/2016
 +
|
 +
* Establishing reliable CAN communication for motorswith master controller.
 +
|-
 +
|-
 +
|-
 +
! scope="row"| 7
 +
| 11/15/2016       
 +
| 11/18/2016
 +
|
 +
* Interfacing of sensors with motors and testing obstacle avoidance .
 +
|-
 +
|-
 +
|-
 +
! scope="row"| 8
 +
| 11/18/2016
 +
| 11/22/2016                       
 +
|
 +
* Integrating it with the master controller, testing and debugging
 +
|-
 +
|-
 +
|-
 +
|}
 
=== Design & Implementation ===
 
=== 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.
 
The design section can go over your hardware and software design.  Organize this section using sub-sections that go over your design and implementation.

Revision as of 18:08, 11 October 2016

Project Title

Thunderbolt - a self driving RC car

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.

Schedule

Sr No Start Date End Date Task Status Actual End Date
1 09/14/2016 09/20/2016 Read previous reports and module distribution Completed
2 09/21/2016 09/27/2016 Set up git and wiki page Completed
3 09/28/2016 10/04/2016 Read previous reports and order parts In Progress
4 10/05/2016 10/25/2016 Work on individual modules In Progress
5 10/26/2016 11/01/2016 Interface Motor, Sensor, GPS, Bluetooth module with the Master Controller over CAN bus
6 11/02/2016 12/01/2016 Testing, Modifications and error correction
7 12/02/2016 12/08/2016 Final testing

Team members and Responsibilities

  • Master Controller
    • Abhishek Singh
    • Saurabh Ravindra Deshmukh
    • Neha Biradar
  • Motor Controller
    • Krishank Mehta
    • Virginia Menezes
    • Saurabh Ravindra Deshmukh
  • GPS/Compass Module
    • Samiksha Ambekar
    • Krishank Mehta
    • Neha Biradar
    • Virginia Menezes
  • Sensors
    • Arthur Nguyen
    • Rajeev Sawant
    • Samiksha Ambekar
  • Bluetooth
    • Abhishek Singh
    • Nikhil Namjoshi
  • Android Application
    • Nikhil Namjoshi
    • Saurabh Ravindra Deshmukh

Parts List & Cost

Item# Part Desciption Vendor Qty Cost
1 RC Car given by Preet
2 Bluetooth hc 05 Amazon 1 $3.21
3 Sonar Sensor Maxbotix EZ1 MB 1010
4

Master Controller

Schedule

Sr No Start Date End Date Task Status Actual Completed Date
1 10/11/2016 10/18/2016 Decide/Develop the CAN message ID and node address for all controllers In Progress
2 10/18/2016 10/25/2016 Design the algorithm for navigation and obstacle avoidance
3 10/25/2016 11/01/2016 Integrate the Bluetooth module with the Master controller over CAN bus and communicate to the android app on phone
4 11/01/2016 11/08/2016 Interface the Motor module with the Master controller over CAN bus
5 11/08/2016 11/15/2016 Interface the sensor controllers with the Master controller over CAN bus
6 11/15/2016 11/22/2016 Designing of the kill switch and interfacing the Master controller with GPS module
7 11/15/2016 11/22/2016 Testing the Master module with all controllers interfaced
8 11/15/2016 11/22/2016 Take care of modifications and shortcomings if any
9 11/22/2016 11/29/2016 Final Testing of self driving car

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.

Sensor Controller

Group Members

  • Arthur Nguyen
  • Rajeev Sawant

Schedule

Week# Scheduled Start Date Task Implementation Completion Date Status
1 10/02/2016
  • Choose appropiate components
  • Read through wiki to find out components used in earlier projects.
  • Ordered additional ultrasonic sensors.
 Complete
2 10/09/2016
  • Sensor Data Sheet Review with team.
  • Follow up on ordered parts
Complete
3 10/16/2016
  • Test the Individual Sensor and Speed.
  • Download software for LCD.
4 10/23/2016
  • To Mount ultrasonic sensor on car and test it.
5 10/30/2016
  • Transfer of sensor data via CAN Bus to Master.
6 11/06/2016
  • Collaborating with other modules for first demo.
  • Fine-tuning algorithms for sensor.
7 11/13/2016
  • Testing the implementation for multiple sensors and debugging the issue.
  • Decide upon additional I/O such as lights.
8 11/20/2016
  • Optimizing the code and testing for stability and report.

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

Group Members

  • Krishank Mehta
  • Virginia Menezes
  • Saurabh Deshmukh


Schedule

Sr No Start Date End Date Task Status Actual Completed Date
1 9/19/2016 9/24/2016
  • Understanding the motor and PWM concept.
 Completed 9/25/2016
2 10/4/2016 10/5/2016
  • Testing Servo and DC motor using RC Transmitter and Receiver.
 Completed 10/5/2016
3 10/7/2016 10/10/2016
  • Testing and interfacing of servo and DC motor with SJOne Board
 In Progress
4 10/11/2016 10/18/2016
  • Design of CAN message ID for motor controller.
5 10/20/2016 10/24/2016
  • Design a power circuit on RC car with motors interfaced to SJOne board.
6 11/01/2016 11/08/2016
  • Establishing reliable CAN communication for motorswith master controller.
7 11/15/2016 11/18/2016
  • Interfacing of sensors with motors and testing obstacle avoidance .
8 11/18/2016 11/22/2016
  • Integrating it with the master controller, testing and debugging

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

Group Members

  • Samiksha Ambekar
  • Neha Biradar

Schedule

Sr No Start Date End Date Task Status Actual Completed Date
1 09/28/2016 10/04/2016 Read previous reports and order GPS , compass module and antenna Completed 10/04/2016
2 10/05/2016 10/16/2016 Interface GPS module and compass module to SJOne board. In Progress
3 10/17/2016 10/25/2016 Parse GPS data and format the data to be transmitted. Test code to get compass reading information.
4 10/26/2016 11/05/2016 Algorithm development of GPS module for distance calculation.
5 11/06/2016 11/14/2016 Calibrating the compass module.Integration of GPS and compass module. Interfacing of GPS and compass module to Android
6 11/15/2016 11/22/2016 Integration with Master through CAN bus and unit testing.
7 11/22/2016 11/29/2016 Complete System Testing.

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.

GPS Module: Readytosky Ublox NEO-M8N

This GPS module uses UART serial communication interface. The refresh rate ranges from 1Hz up to 10Hz with a default baud rate of 9600bps. This module is an updated version to the Ublox NEO-M7N which brings improved accuracy of up to 0.9 meters using its build in antenna.

Specifications:

  • Power Supply:DC Voltage 2.8V~6.0V
  • Power Consumption: 50mA@5V
  • Support for GPS,GLONASS,Galileo,BeiDou,QZSS and SBAS
  • 72 Searching Channel
  • Receiving Sensitivity:Trace -167dBm, Capture-148dBm
  • Positioning Time:Cold Start:avg26s, Warm Start:avg25s, Hot Start:avg3s
  • positioning accuracy:2m At Open Wind
  • Output Frequency:1Hz-10Hz,Default 1Hz
  • Speed accuracy:0.1 m/s (Without Aid)
  • Acceleration accuracy:0.1 m/s (Without Aid)
  • Dynamic Characteristics:Max Height:18000m, Max Speed:515m/s, Max Acceleration:4G
  • UART Interface:UART Port:TXDA and RXDA
  • Support Rate:4800bps to 115200bps,Default 9600dps
  • Working Temperature:-40℃-+85℃
  • Storage Temperature:-40℃-+85℃
  • Diameter:45mm
  • Height:6mm
  • Weight:10g
  • 6pins 1.25mm port


GPS Connector Definition:

  • GND,
  • TX,data output
  • RX,data intput
  • VCC,2.8V-6V

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

Group Members

  • Nikhil Namjoshi
  • Abhishek Singh
  • Saurabh Deshmukh

Schedule

Sr No Start Date End Date Task Status Actual Completed Date
1 9/27/2016 10/4/2016
  • Decide the Bluetooth module and purchase it.
  • Search online and read previous projects wikipedia pages.
 Complete 10/4/2016
2 10/6/2016 10/8/2016
  • Testing of Bluetooth Module with SJ-One Board using available bluetooth app on Android app store
 Complete 10/8/2016
3 9/30/2016 10/2/2016
  • Development of basic android app for one directional bluetooth communication.
 Complete 10/2/2016
4 10/2/2016 10/6/2016
  • Development of basic android app for plotting Google Map route between two points.
 Complete 10/6/2016
5 10/10/2016 10/25/2016
  • Bi-directional communication between SJ-ONE Board and Android App.
 In Progress
6 10/25/2016 11/2/2016
  • Interface android & bluetooth module with CAN
7 11/3/2016 11/8/2016
  • Interfacing with GPS module using CAN bus for receiving current location.
8 11/9/2016 11/23/2016
  • Integration with Master through CAN bus.
9 11/26/2016 12/5/2016
  • Android App GUI enhancements and bug fixes.

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.


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:_Thunderbolt&oldid=28432"