F16: Spartan and Furious

From Embedded Systems Learning Academy
Revision as of 23:45, 8 October 2016 by Proj user10 (talk | contribs) (→‎Schedule)

Jump to: navigation, search

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

Schedule

Week# Date Task Actual Status
1 9/17/2016
  • Purchasing RC car.
  • Purchased RC car.
 Complete
2 9/24/2016
  • Individual module distribution
  • Project report setup
  • Git setup
  • Order components
  • Members identified for modules
  • Wikipage project report template and Git were setup
  • Ordered GPS module and CAN transceivers
 Complete
3 10/01/2016
  • Define scope of each module
  • Determine Git flow
  • Follow up on component procurement
  • Initial flow of each module defined
  • Identified the branches and decided on merge process
  • Ordered additional ultrasonic sensors and LCD
 Complete
4 10/08/2016
  • Create branches in Git
  • Follow up on component procurement
  • Created Master branch on Git
  • All ordered parts received on 10/07
 Complete
5 10/15/2016
6 10/22/2016
7 10/29/2016
8 11/05/2016
  • First demo on 8th!
8 11/12/2016
8 11/19/2016
8 11/26/2016
8 12/03/2016
8 12/10/2016
8 12/17/2016

Parts List & Cost

Give a simple list of the cost of your project broken down by components. Do not write long stories here.

ECUs

Motor Controller

Group Members

Schedule

Week# Date Task Actual Status
1 10/01/2016
  • Determining and analyzing the duty cycle for servomotor and DC motor of the car
  • Tested the car servo and DC motor using Digital Oscilloscope.
  • Observed and noted the duty cycle wave forms.
 Complete
2 10/08/2016
  • Basic testing of Servo and DC motor.
  • Testing speed of car with variable PWM.
  • Implemented test code to interface SJOne board with a servo motor to control the direction and verified the same on the car.
  • Speed testing in progress.
 Complete
3 10/15/2016
  • Developing drivers for both motors.
  • Testing the car with developed drivers.
4 10/22/2016
  • Establishing basic CAN communication.
  • Interfacing with Master Controller with Motor.
5 10/29/2016
  • Fine tuning motor control code.
6 11/05/2016
  • Testing and debugging.
7 11/12/2016
  • Design of Feedback Control mechanism for car.
8 11/19/2016
  • Speed synchronization of car using IR sensor and testing.
9 11/26/2016
  • Testing and integration with all modules.
10 12/03/2016
  • Fine tuning, debugging and integration.

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.

Android and Communication Bridge

Group Members

Schedule

Week# Date Task Actual Status
1 10/01/2016
  • Order components
  • Refer previous projects on Wiki to check for components.
 Complete
2 10/08/2016
  • Follow-up on ordered parts.
  • Components acquired from Preet.
  • Studied the datasheet to understand communication protocol.
 Complete
3 10/15/2016
  • Android app prototype
  • Established Bluetooth communication with Android App
 Complete
4 10/22/2016
  • Interface Bluetooth module with SJ-One board.
5 10/29/2016
  • Transmitting and receiving messages between Android App and SJ-One board.
6 11/05/2016
  • Testing and debugging.
7 11/12/2016
  • Establishing CAN communication with peripheral modules.
8 11/19/2016
  • Enhancing UI of the Android App.
9 11/26/2016
  • Interfacing with GPS module and testing.
10 12/03/2016
  • Final integration, 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

Schedule

Week# Date Task Actual Status
1 10/01/2016
  • Order components
  • Refer previous projects wiki to check for components.
  • Ordered GPS module and Magnetometer
 Complete
2 10/08/2016
  • Follow up on ordered parts
  • Parts received on 3rd Oct.
  • Go through Adafruit GPS datasheet to understand the supported formats
 Complete
3 10/15/2016
  • Parse GPS data and format the data to be transmitted
  • Test code to get compass reading information
4 10/22/2016
  • Interfacing GPS and compass to SJOne board
5 10/29/2016
  • Initial Algorithm development of GPS module for distance calculation
  • Establishing basic CAN communication
6 11/05/2016
  • Collaborating with other modules for first demo
7 11/12/2016
  • Algorithm for distance and heading calculation
  • Coding and Calibration of GPS module
8 11/19/2016
  • Coding and Calibration of GPS module
  • Individual Unit Testing
9 11/26/2016
  • Integration of GPS and compass modules
  • Interfacing GPS with Android, Master and IO controllers
10 12/03/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.

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 and I/O

Group Members

Schedule

Week# Date Task Actual Status
1 10/01/2016
  • Order components
  • Read through wiki to find out components used in earlier projects.
  • Searched if better components were available.
  • Ordered additional ultrasonic sensors and LCD.
 Complete
2 10/08/2016
  • Follow up on ordered parts
  • Parts received on 7th Oct.
  • Started working on sensors.
 Complete
3 10/15/2016
  • Design basic sensor algorithm for obstacle detection.
  • Download software for LCD.
4 10/22/2016
  • Design layout for LCD screen
  • Mount ultrasonic sensor on car and test it.
5 10/29/2016
  • Establishing basic CAN communication.
  • Integrate IR sensor for gauging speed.
6 11/05/2016
  • Collaborating with other modules for first demo.
  • Fine-tuning algorithms for sensor and IR.
7 11/12/2016
  • Develop LCD code for displaying all sensor information and car vitals.
  • Decide upon additional I/O such as lights.
8 11/19/2016
  • Integrate sensor and I/O code.
  • Facilitate Motor module to test with IR sensor.
6 11/26/2016
  • Testing and integration with all modules.
9 12/03/2016
  • Fine tuning and debugging of the whole module.

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

Group Members

Schedule

Week# Date Task Actual Status
1 10/01/2016
  • Implement basic CAN communication CAN between two SJ-One Boards
  • Successfully tested CAN communication between two SJ-One boards.
 Complete
2 10/08/2016
  • Research on the CAN bus, tasks and scheduling.
  • Decision regarding flow of the master controller.
  • Learnt about the working of CAN bus and decided on flow for the master controller.
 Complete
3 10/15/2016
  • Decision making regarding Node address and message ID's for CAN controller.
In Progress
4 10/22/2016
  • Interfacing master controller with Sensor Controller module.
5 10/29/2016
  • Basic interfacing of master controller with GPS and motor module.
6 11/05/2016
  • Testing and debugging.
7 11/12/2016
  • Design of Feedback Control mechanism for car.
8 11/19/2016
  • Speed synchronization of car using IR sensor and testing.
9 11/26/2016
  • Testing and integration with all modules.
10 12/03/2016
  • Fine tuning, debugging and integration.

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:_Spartan_and_Furious&oldid=28255"