Difference between revisions of "F14: Self Driving Undergrad Team"
From Embedded Systems Learning Academy
Proj user8 (talk | contribs) (→Design & Implementation) |
Proj user8 (talk | contribs) (→Design & Implementation) |
||
| Line 51: | Line 51: | ||
*INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS | *INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS | ||
| − | ==== Sensor Controller Team ==== | + | ==== Sensor Controller Team Hardware Design ==== |
Discuss your hardware design of Sensor Controller | Discuss your hardware design of Sensor Controller | ||
*INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS | *INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS | ||
| − | ==== Motor Controller Team ==== | + | ==== Motor Controller Team Hardware Design ==== |
Discuss your hardware design of Motor Controller | Discuss your hardware design of Motor Controller | ||
*INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS | *INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS | ||
| − | ==== I/O Team ==== | + | ==== I/O Team Hardware Design ==== |
Discuss your hardware design of I/O | Discuss your hardware design of I/O | ||
*INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS | *INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS | ||
| − | ==== Communication Bridge + Android ==== | + | ==== Communication Bridge + Android Hardware Design ==== |
Discuss your hardware design of Communication Bridge and Android | Discuss your hardware design of Communication Bridge and Android | ||
*INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS | *INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS | ||
| − | ==== Geographical Controller Team ==== | + | ==== Geographical Controller Team Hardware Design ==== |
Discuss your hardware design of Geographical Controller | Discuss your hardware design of Geographical Controller | ||
*INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS | *INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS | ||
| − | ==== Master Controller Team ==== | + | ==== Master Controller Team Hardware Design ==== |
Discuss your hardware design of Master Controller | Discuss your hardware design of Master Controller | ||
*INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS | *INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS | ||
| Line 81: | Line 81: | ||
| − | ==== Sensor Controller Team ==== | + | ==== Sensor Controller Team Hardware Interface ==== |
Describe how your hardware communicates. WHAT BUSes were used | Describe how your hardware communicates. WHAT BUSes were used | ||
*SHOW HOW FRAMES ARE SENT | *SHOW HOW FRAMES ARE SENT | ||
| − | ==== Motor Controller Team ==== | + | ==== Motor Controller Team Hardware Interface ==== |
Discuss your hardware design of Motor Controller | Discuss your hardware design of Motor Controller | ||
*SHOW HOW FRAMES ARE SENT | *SHOW HOW FRAMES ARE SENT | ||
| − | ==== I/O Team ==== | + | ==== I/O Team Hardware Interface ==== |
Discuss your hardware design of I/O | Discuss your hardware design of I/O | ||
*SHOW HOW FRAMES ARE SENT | *SHOW HOW FRAMES ARE SENT | ||
| − | ==== Communication Bridge + Android ==== | + | ==== Communication Bridge + Android Hardware Interface ==== |
Discuss your hardware design of Communication Bridge and Android | Discuss your hardware design of Communication Bridge and Android | ||
*SHOW HOW FRAMES ARE SENT | *SHOW HOW FRAMES ARE SENT | ||
| − | ==== Geographical Controller Team ==== | + | ==== Geographical Controller Team Hardware Interface ==== |
Discuss your hardware design of Geographical Controller | Discuss your hardware design of Geographical Controller | ||
*SHOW HOW FRAMES ARE SENT | *SHOW HOW FRAMES ARE SENT | ||
| − | ==== Master Controller Team ==== | + | ==== Master Controller Team Hardware Interface ==== |
Discuss your hardware design of Master Controller | Discuss your hardware design of Master Controller | ||
*SHOW HOW FRAMES ARE SENT | *SHOW HOW FRAMES ARE SENT | ||
| − | === | + | === Hardware Interface === |
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. | 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. | ||
SYSTEM LEVEL SOFTWARE DESIGN GOES HERE | SYSTEM LEVEL SOFTWARE DESIGN GOES HERE | ||
| − | ==== Sensor Controller Team ==== | + | ==== Sensor Controller Team Hardware Interface ==== |
Describe how your hardware communicates. WHAT BUSes were used | Describe how your hardware communicates. WHAT BUSes were used | ||
*SHOW SOFTWARE FLOWCHART DIAGRAM | *SHOW SOFTWARE FLOWCHART DIAGRAM | ||
| − | ==== Motor Controller Team ==== | + | ==== Motor Controller Team Hardware Interface ==== |
Discuss your hardware design of Motor Controller | Discuss your hardware design of Motor Controller | ||
*SHOW SOFTWARE FLOWCHART DIAGRAM | *SHOW SOFTWARE FLOWCHART DIAGRAM | ||
| − | ==== I/O Team ==== | + | ==== I/O Team Hardware Interface ==== |
Discuss your hardware design of I/O | Discuss your hardware design of I/O | ||
*SHOW SOFTWARE FLOWCHART DIAGRAM | *SHOW SOFTWARE FLOWCHART DIAGRAM | ||
| − | ==== Communication Bridge + Android ==== | + | ==== Communication Bridge + Android Hardware Interface ==== |
Discuss your hardware design of Communication Bridge and Android | Discuss your hardware design of Communication Bridge and Android | ||
*SHOW SOFTWARE FLOWCHART DIAGRAM | *SHOW SOFTWARE FLOWCHART DIAGRAM | ||
| − | ==== Geographical Controller Team ==== | + | ==== Geographical Controller Team Hardware Interface ==== |
Discuss your hardware design of Geographical Controller | Discuss your hardware design of Geographical Controller | ||
*SHOW SOFTWARE FLOWCHART DIAGRAM | *SHOW SOFTWARE FLOWCHART DIAGRAM | ||
| − | ==== Master Controller Team ==== | + | ==== Master Controller Team Hardware Interface ==== |
Discuss your hardware design of Master Controller | Discuss your hardware design of Master Controller | ||
*SHOW SOFTWARE FLOWCHART DIAGRAM | *SHOW SOFTWARE FLOWCHART DIAGRAM | ||
| − | === Implementation === | + | === Software 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. | 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. | ||
| + | |||
| + | SYSTEM LEVEL SOFTWARE IMPLEMENTATION GOES HERE | ||
| + | |||
| + | ==== Sensor Controller Team Hardware Interface ==== | ||
| + | Describe steps to communicate hardware | ||
| + | |||
| + | ==== Motor Controller Team Hardware Interface ==== | ||
| + | Describe steps to communicate hardware | ||
| + | |||
| + | ==== I/O Team Hardware Interface ==== | ||
| + | Describe steps to communicate hardware | ||
| + | |||
| + | ==== Communication Bridge + Android Hardware Interface ==== | ||
| + | Describe steps to communicate hardware | ||
| + | |||
| + | ==== Geographical Controller Team Hardware Interface ==== | ||
| + | Describe steps to communicate hardware | ||
| + | |||
| + | ==== Master Controller Team Hardware Interface ==== | ||
| + | Describe steps to communicate hardware | ||
== Testing & Technical Challenges == | == Testing & Technical Challenges == | ||
Revision as of 04:24, 21 September 2014
Contents
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
- Team Member 1
- Driver Development
- Team Member 2
- FreeRTOS Software Design
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 | Task | Actual |
|---|---|---|---|
| 1 | 10/8 | Task list | Completed? Problems Encountered? |
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 System Level Hardware Design
*INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS
Sensor Controller Team Hardware Design
Discuss your hardware design of Sensor Controller
*INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS
Motor Controller Team Hardware Design
Discuss your hardware design of Motor Controller
*INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS
I/O Team Hardware Design
Discuss your hardware design of I/O
*INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS
Communication Bridge + Android Hardware Design
Discuss your hardware design of Communication Bridge and Android
*INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS
Geographical Controller Team Hardware Design
Discuss your hardware design of Geographical Controller
*INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS
Master Controller Team Hardware Design
Discuss your hardware design of Master Controller
*INCLUDE BLOCK DIAGRAM and PIN CONNECTIONS
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.
SYSTEM LEVEL HARDWARE INTERFACE INTERFACE GOES HERE
Sensor Controller Team Hardware Interface
Describe how your hardware communicates. WHAT BUSes were used
*SHOW HOW FRAMES ARE SENT
Motor Controller Team Hardware Interface
Discuss your hardware design of Motor Controller
*SHOW HOW FRAMES ARE SENT
I/O Team Hardware Interface
Discuss your hardware design of I/O
*SHOW HOW FRAMES ARE SENT
Communication Bridge + Android Hardware Interface
Discuss your hardware design of Communication Bridge and Android
*SHOW HOW FRAMES ARE SENT
Geographical Controller Team Hardware Interface
Discuss your hardware design of Geographical Controller
*SHOW HOW FRAMES ARE SENT
Master Controller Team Hardware Interface
Discuss your hardware design of Master Controller
*SHOW HOW FRAMES ARE SENT
Hardware Interface
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.
SYSTEM LEVEL SOFTWARE DESIGN GOES HERE
Sensor Controller Team Hardware Interface
Describe how your hardware communicates. WHAT BUSes were used
*SHOW SOFTWARE FLOWCHART DIAGRAM
Motor Controller Team Hardware Interface
Discuss your hardware design of Motor Controller
*SHOW SOFTWARE FLOWCHART DIAGRAM
I/O Team Hardware Interface
Discuss your hardware design of I/O
*SHOW SOFTWARE FLOWCHART DIAGRAM
Communication Bridge + Android Hardware Interface
Discuss your hardware design of Communication Bridge and Android
*SHOW SOFTWARE FLOWCHART DIAGRAM
Geographical Controller Team Hardware Interface
Discuss your hardware design of Geographical Controller
*SHOW SOFTWARE FLOWCHART DIAGRAM
Master Controller Team Hardware Interface
Discuss your hardware design of Master Controller
*SHOW SOFTWARE FLOWCHART DIAGRAM
Software 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.
SYSTEM LEVEL SOFTWARE IMPLEMENTATION GOES HERE
Sensor Controller Team Hardware Interface
Describe steps to communicate hardware
Motor Controller Team Hardware Interface
Describe steps to communicate hardware
I/O Team Hardware Interface
Describe steps to communicate hardware
Communication Bridge + Android Hardware Interface
Describe steps to communicate hardware
Geographical Controller Team Hardware Interface
Describe steps to communicate hardware
Master Controller Team Hardware Interface
Describe steps to communicate hardware
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.
