Difference between revisions of "F16: Spartan and Furious"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Schedule)
(→‎Schedule)
Line 126: Line 126:
 
*<font color="clouds"></font>
 
*<font color="clouds"></font>
  
−
*<font color="orange">Design layout for LCD screen</font>
+
*<font color="orange">Test basic working for IR</font>
  
 
*<font color="orange">Mount ultrasonic sensor on car and test it. </font>
 
*<font color="orange">Mount ultrasonic sensor on car and test it. </font>
  
 
|
 
|
−
CAN signals alongwith their priorities identified (DBC file format generated).  
+
*CAN signals along with their priorities identified (DBC file format generated).  
 
*<font color="blue"></font>
 
*<font color="blue"></font>
 
*<font color="green">
 
*<font color="green">

Revision as of 06:12, 23 October 2016

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

Legend Motor Controller , Master Controller , Android Controller, Geo Controller, Sensor and I/O Controller , Team Goal

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 for individual modules
  • 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
  • Determining and analyzing the duty cycle for servomotor and DC motor of the car.
  • Implement basic CAN communication CAN between two SJ-One Boards
  • Initial flow of each module defined
  • Identified the branches and decided on merge process
  • Ordered additional ultrasonic sensors and LCD
  • Tested the car servo and DC motor using Digital Oscilloscope.
  • Observed and noted the duty cycle wave forms .
  • Successfully tested CAN communication between two SJ-One boards.
 Complete
4 10/08/2016
  • Create branches in Git
  • Follow up on component procurement
  • Basic testing of Servo and DC motor.
  • Testing speed of car with variable PWM.
  • Research on the CAN bus, tasks and scheduling.
  • Decision regarding flow of the master controller.
  • Download software for LCD.
  • Created Master branch on Git
  • All ordered parts received on 10/07
  • 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.
  • Learnt about the working of CAN bus and decided on flow for the master controller.
  • Installed 4D System Workshop4 IDE (for LCD).
Complete
5 10/15/2016
  • Developing drivers for both motors.
  • Testing the car with developed drivers.
  • Android app prototype
  • Parse GPS data and format the data to be transmitted
  • Decision making regarding various messages to be sent on CAN bus.
  • Design basic sensor algorithm for range finding.
  • Algorithm developed for both the motors and testing in progress.
  • Basic App Screen layout designed.
  • GPS latitude & longitude coordinates extracted from NMEA format.
  • Identified various messages for different nodes.
  • Designed basic algorithm for range finding.
Complete
6 10/22/2016
  • Define CAN signals for each module.
  • CAN signals identified
  • Interfacing with Master Controller with Motor.
  • Interface Bluetooth module with SJ-One board
  • Test code to get compass reading information
  • Test basic working for IR
  • Mount ultrasonic sensor on car and test it.
  • CAN signals along with their priorities identified (DBC file format generated).
  • Implementing the Magnetometer source code.
7 10/29/2016
  • Designing of CAN hardware.
  • Testing and debugging.
  • Fine tuning motor control code.
  • Transmitting and receiving messages between Android App and SJ-One board.
  • Initial Algorithm development of GPS module for distance calculation
  • Basic interfacing of master controller with motor module.
  • Establishing basic CAN communication.
  • Integrate IR sensor for gauging speed.
8 11/05/2016
  • Integration of modules for first demo.
  • Testing and debugging.
  • Testing and debugging.
  • Collaborating with other modules for first demo
  • Interface with the motor and Sensor module for the first demo.
  • Testing and debugging.
  • Collaborating with other modules for first demo.
  • Fine-tuning algorithms for sensor and IR.
9 11/12/2016
  • Design of Feedback Control mechanism for car.
  • Establishing CAN communication with peripheral modules.
  • Algorithm for distance and heading calculation-H
  • Coding and Calibration of GPS module
  • Interface of master controller with GPS module.
  • Develop kill switch mechanism.
  • Develop LCD code for displaying all sensor information and car vitals.
  • Decide upon additional I/O such as lights.
10 11/19/2016
  • Speed synchronization of car using IR sensor and testing.
  • Enhancing UI of the Android App.
  • Coding and Calibration of GPS module
  • Individual Unit Testing
  • Develop heartbeat mechanism to check health of each of the modules.
  • Integrate master controller with android module.
  • Integrate sensor and I/O code.
  • Facilitate Motor module to test with IR sensor.
11 11/26/2016
  • Testing and debugging for second demo.
  • Interfacing with GPS module and testing.
  • Integration of GPS and compass modules
  • Interfacing GPS with Android, Master and IO controllers
  • Integration of I/O module.
12 12/03/2016
  • Fine tuning, debugging and integration.
  • Final integration, testing and debugging.
  • Complete System Testing
  • Fine tuning, debugging and integration.
13 12/10/2016
  • Final Testing and fine tuning
  • Report preparation

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

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

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

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

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

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=28869"