Difference between revisions of "F17: FoxP2"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Schedule)
Line 55: Line 55:
 
! scope="row"| 1
 
! scope="row"| 1
 
| 10/8/2017
 
| 10/8/2017
 +
Sensors: Research and requirement for the proper front and reverse sensors. IO design.
 
| 10/14/2017
 
| 10/14/2017
 
| Geographical: Order GPS and Compass
 
| Geographical: Order GPS and Compass

Revision as of 09:33, 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

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

  • R Nikfar
    • Team Lead, Electrical Circuits Engineering, PCB design, Sensor testing and implementation.
  • Jason Tran
    • Sensor IO Implementaion, and testing, Master controller.
  • Ahsan Uddin
    • Motor Control, Battery and LCD interface.
  • Yuyu Chen
    • GPS module implementation.
  • Marvin Flores
    • Android Application development and testing.
  • Rabeel Elahi
    • Master Controller Implementation.
  • Sophia Quan
    • Sensors, Motor Control.
  • Michael Jaradah
    • Unit Testing.
  • Taylor Kearns
    • Testing.
  • Bohan Liu
    • Master Controller.

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.

Week# Date End Date Task Status Completion Date
1 10/8/2017

Sensors: Research and requirement for the proper front and reverse sensors. IO design.

10/14/2017 Geographical: Order GPS and Compass

Android: Setup Android Studio; Run test application Motor: PWM proof of concept

On-going

On-going On-going

2 10/15/2017 10/21/2017 Geographical: Interface with micro-controller to receive raw data

Android: Initial App UI running. Solid plan for checkpoint algorithm. Motor: Run the car in straight line in manual mode

3 10/22/2017 10/28/2017 Geographical: Implement algorithm to parse GPS NMEA sentence and calibrate compass

Android: Checkpoint algorithm implemented. Phone to SJSUOne board communication setup. Motor: LED Display initial integration

4 10/29/2017 11/04/2017 Geographical: Integrate GPS and compass together to get heading, bearing, and distance

Android: Checkpoint algorithm tested. Full Communication with SJSUOne board implemented. Motor: Finalize the incoming messages for Motor and setup the core system for motor controls

5 11/05/2017 11/11/2017 Geographical: Interface with other nodes on CAN bus

Android: Other commands such as start and stop implemented and tested. Checkpoint algorithm finalized.

6 11/12/2017 11/18/2017 Geographical:

Android: Testing

7 11/19/2017 11/25/2017 Geographical:

Android: Testing

8 11/26/2017 12/02/2017 Geographical:

Android: Testing

9 12/03/2017 12/09/2017 Geographical:

Android: Testing

10 12/10/2017 12/16/2017
11 12/17/2017 12/20/2017 Demo autonomous car on 12/20

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.