Difference between revisions of "F15: Minion"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Schedule)
(→‎Schedule)
Line 403: Line 403:
 
|
 
|
 
|}
 
|}
 +
 +
''' Sensor Controller Schedule'''
 +
{| class="wikitable"
 +
|-
 +
! scope="col"| Sl. No
 +
! scope="col"| Start Date
 +
! scope="col"| End Date
 +
! scope="col"| Task
 +
! scope="col"| Status
 +
! scope="col"| Actual Completion Date
 +
|-
 +
|-
  
 
== Parts List & Cost ==
 
== Parts List & Cost ==

Revision as of 00:54, 7 October 2015

Grading Criteria

  • How well is Software & Hardware Design described?
  • How well can this report be used to reproduce this project?
  • Code Quality
  • Overall Report Quality:
    • Software Block Diagrams
    • Hardware Block Diagrams
      Schematic Quality
    • Quality of technical challenges and solutions adopted.

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

Sensor Controller:-

Motor & I/0 Controller:-

  • Sudheer Doddapaneni
  • Keerthanaa Alagudurai

Android Controller:-

  • Akshay Kanchar
  • Asmita Deshpande

Geographical Controller:-

Master Controller:-

Tester:-

Treasurer:-

  • Keerthanaa Alagudurai

Hardware:-

  • Sudheer Doddapaneni

Release:-

  • Akshay Kanchar

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.

Common Schedule

Week# Date Task Actual
1 10/8 Task list Completed? Problems Encountered?

Sensor Controller Schedule

Sl. No Start Date End Date Task Status Actual Completion Date
1 9/20/2015 10/5/2015 Research on sensors available and place order
2 10/6/2015 10/12/2015 Develop simple test code for the sensors
3 10/13/2015 10/20/2015 Collaborate with the other sub teams to finish the CAN bus communication and allow the self driving car to drive autonomously
4 10/21/2015 10/30/2015 Interface all sensors to board and calculate distance
5 10/30/2015 11/2/2015 Test for obstacle avoidance
6 11/2/2015 11/5/2015 Work on light sensor
7 12/01/2015 12/17/2015 Final testing and debugging

Motor & I/0 Controller Schedule

Sl. No Start Date End Date Task Status Actual Completion Date
1 9/21/2015 9/25/2015 Order LCD Display Completed 9/25/2015
2 9/28/2015 10/3/2015 Going through the motor concepts and PWM
3 10/4/2015 10/9/2015 Intreface the DC and SERVO Motors with SJONE board
4 10/10/2015 10/13/2015 Establishing basic CAN communication with other modules
5 10/11/2015 10/16/2015 Getting the car to run with the PWM signals from Motor controller
6 10/17/2015 10/23/2015 Research on Speed cotrol method and sensor for the same interface LCD display with LPC1758 via UART
7 10/23/2015 11/4/2015 Establishing reliable CAN communication for IO & Motor with others
8 11/5/2015 11/12/2015 Integrate Speed sensor and send feedback control start,stop buttons and headlight
9 11/13/2015 11/20/2015 Testing substantial self driving capability of the car
10 11/21/2015 11/30/2015 Complete integration, Debugging and Fine tuning
11 12/1/2015 12/5/2015 Final Validation

Geographical Controller Schedule

Sl. No Start Date End Date Task Status Actual Completion Date
1 9/27/2015 10/7/2015 Ordering Parts
2 10/14/2015 10/20/2015 Interfacing of compass(I2C) and GPS (UART) with SJONE board
3 10/20/2015 10/30/2015 Compass calibration
4 10/7/2015 10/30/2015 Algorithm and coding
5 10/25/2015 11/15/2015 Individual unit testing
6 10/30/2015 11/30/2015 Interfacing with other controllers
7 10/30/2015 11/30/2015 Integration Testing

Master Controller Schedule

Sl. No Start Date End Date Task Status Actual Completion Date
1 9/30/2015 10/6/2015 a) Design of Algorithm and Architecture for Master Module.
b) Setup of CAN communication between two controllers.
2 10/7/2015 10/13/2015 a) Development of CAN message system for Android, Sensor and GPS, I/O reception.
b) Decide about periodic function frequencies that’ll be handling different modules.
3 10/14/2015 10/20/2015 a) Development of driving,stopping and obstruction avoidance algorithm for motor.
b) Implementation of LED Display to display number of messages on CAN bus.
4 10/21/2015 10/27/2015 a) Designing of Kill switch with the help of Motor, I/O and Android.
b) Design the system to restore the last known configuration.
c) Implementation to reset modules if the CAN bus reaches BUS off state.
5 10/28/2015 11/3/2015 a) Design of Head Light functionality with the help of Sensor module.
b) Implementation of log files saving to SD card.
6 11/4/2015 11/10/2015 a) Integration of all the modules with Master module and check it after combining everything.
b) Probable implementation of additional features.
7 11/11/2015 11/17/2015 a) Refine the work done earlier.Change areas that need a change.
b) Test the Master module while all the modules are integrated together and list down modifications and additions to be done.
8 11/18/2015 11/24/2015 Testing of system and specially making sure that last week’s shortcomings are taken care of.
9 11/25/2015 12/1/2015 a) Final testing of individual modules.
b) Testing the self-driving capability of the car.
10 12/2/2015 12/8/2015 Final working on the shortcomings in the previous week.
11 12/9/2015 12/15/2015 Final Testing of Car.

Sensor Controller Schedule

Parts List & Cost

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

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.

Include sub-sections that list out a problem and solution, such as:

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.

Sl. No Start Date End Date Task Status Actual Completion Date
Retrieved from "http://socialledge.com/sjsu/index.php?title=F15:_Minion&oldid=18263"