Difference between revisions of "F17: Optimus"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Schedule)
(→‎Schedule)
Line 55: Line 55:
 
|-
 
|-
 
! scope="row"| 1
 
! scope="row"| 1
−
| 9/21/2017
+
| 9/23/2017
 
|
 
|
 
* Decide roles for each team member
 
* Decide roles for each team member
Line 68: Line 68:
 
|-
 
|-
 
! scope="row"| 2
 
! scope="row"| 2
−
| 9/26/2016
+
| 9/30/2016
 
|
 
|
 
* Discuss and understand each module functionality  
 
* Discuss and understand each module functionality  
Line 80: Line 80:
 
|-
 
|-
 
! scope="row"| 3
 
! scope="row"| 3
−
| 10/03/2016
+
| 10/07/2016
 
|
 
|
 
* Plan project goals and milestones for each module
 
* Plan project goals and milestones for each module
Line 92: Line 92:
 
|-
 
|-
 
! scope="row"| 4
 
! scope="row"| 4
−
| 10/10/2016
+
| 10/14/2016
 
|
 
|
 
*  
 
*  
Line 106: Line 106:
 
|-
 
|-
 
! scope="row"| 5
 
! scope="row"| 5
−
| 10/15/2016
+
| 10/21/2016
 
|
 
|
 
*
 
*
Line 114: Line 114:
 
|-
 
|-
 
! scope="row"| 6
 
! scope="row"| 6
−
| 10/22/2016
+
| 10/28/2016
 
|
 
|
 
*
 
*
Line 122: Line 122:
 
|-
 
|-
 
! scope="row"| 7
 
! scope="row"| 7
−
| 10/29/2016
+
| 11/04/2016
 
|
 
|
 
*
 
*
Line 130: Line 130:
 
|-
 
|-
 
! scope="row"| 8
 
! scope="row"| 8
−
| 11/05/2016
+
| 11/11/2016
 
|
 
|
 
*Integration of modules for first demo.
 
*Integration of modules for first demo.
Line 137: Line 137:
 
|-
 
|-
 
! scope="row"| 9
 
! scope="row"| 9
−
| 11/12/2016
+
| 11/18/2016
 
|
 
|
 
*
 
*
Line 145: Line 145:
 
|-
 
|-
 
! scope="row"| 10
 
! scope="row"| 10
−
| 11/19/2016
+
| 11/25/2016
 
|
 
|
 
*
 
*
Line 153: Line 153:
 
|-
 
|-
 
! scope="row"| 11
 
! scope="row"| 11
−
| 11/26/2016
+
| 12/1/2016
 
|
 
|
 
*
 
*
Line 161: Line 161:
 
|-
 
|-
 
! scope="row"| 12
 
! scope="row"| 12
−
| 12/03/2016
+
| 12/08/2016
 
|
 
|
 
*
 
*
Line 167: Line 167:
 
*
 
*
 
| Planned
 
| Planned
−
|-
 
−
! scope="row"| 13
 
−
| 12/10/2016
 
−
|
 
−
*
 
−
*
 
−
 
−
|
 
−
*Final testing done.
 
−
| Planned
 
−
|-
 
 
|}
 
|}
  

Revision as of 00:29, 10 October 2017

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

Optimus - Self Navigating R/C Car powered by SJOne(LPC1758) micro controller

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

  • Revathy
    • CAN controller, Integration/System Testing
  • Unnikrishnan
    • CAN controller, Integration/System Testing
  • Kripanand Jha
    • CAN controller, Integration/System Testing
  • Sneha
    • GPS Controller
  • Sushma
    • Sensor Controller
  • Harshitha
    • Sensor Controller
  • Parimal
    • Android App
  • Rajul
    • Motor Controller, Bluetooth/App Interface
  • Suprajith
    • Sensor controller
  • Sarveash
    • Motor Controller

Schedule

Legend:

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

Week# Date Planned Task Actual Status
1 9/23/2017
  • Decide roles for each team member
  • Read FY16 project reports and understand requirements
  • Setup Gitlab project workarea
  • Ordered CAN Tranceivers and get R/C car
  • Team roles are decided and module owners are assigned
  • Gitlab project is set
  • Ordered CAN tranceivers and got R/C Car
 Complete.
2 9/30/2016
  • Discuss and understand each module functionality
  • Setup Wiki Project Report template
  • Create component checklist and order required components for individual modules.
  • Overall project requirements are understood
  • Wiki Project report setup is done
  • Odered components for Geo controller module
 Complete
3 10/07/2016
  • Plan project goals and milestones for each module
  • Decide Project execution strategy
  • Setup Gitlab project code for each contoller
On Track
4 10/14/2016
  • 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
Planned
5 10/21/2016
Planned
6 10/28/2016
Planned.
7 11/04/2016
Planned.
8 11/11/2016
  • Integration of modules for first demo.
 Integration and Testing completed for the first demo. Planned.
9 11/18/2016
Planned.
10 11/25/2016
Planned
11 12/1/2016
Planned
12 12/08/2016
Planned

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:

<Bug/issue name>

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=F17:_Optimus&oldid=39930"