Difference between revisions of "Autonomous RC Car Project Report Template"
Proj user22 (talk | contribs) (→Sensor ECU) |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
<Team Name> | <Team Name> | ||
| + | <HR> | ||
| + | <BR/> | ||
== Abstract == | == Abstract == | ||
<2-3 sentence abstract> | <2-3 sentence abstract> | ||
| Line 47: | Line 49: | ||
** Link to Gitlab user2 | ** Link to Gitlab user2 | ||
| − | < | + | <HR> |
| − | + | <BR/> | |
== Schedule == | == Schedule == | ||
| Line 77: | Line 79: | ||
|} | |} | ||
| + | <HR> | ||
| + | <BR/> | ||
== Parts List & Cost == | == Parts List & Cost == | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 100: | Line 104: | ||
|} | |} | ||
| + | <HR> | ||
| + | <BR/> | ||
== Printed Circuit Board == | == Printed Circuit Board == | ||
<Picture and information, including links to your PCB> | <Picture and information, including links to your PCB> | ||
<br> | <br> | ||
| + | <HR> | ||
| + | <BR/> | ||
== CAN Communication == | == CAN Communication == | ||
<Talk about your message IDs or communication strategy, such as periodic transmission, MIA management etc.> | <Talk about your message IDs or communication strategy, such as periodic transmission, MIA management etc.> | ||
| Line 117: | Line 125: | ||
<HR> | <HR> | ||
<BR/> | <BR/> | ||
| − | |||
== Sensor ECU == | == Sensor ECU == | ||
<Picture and link to Gitlab> | <Picture and link to Gitlab> | ||
| Line 128: | Line 135: | ||
=== Technical Challenges === | === Technical Challenges === | ||
| − | < | + | < List of problems and their detailed resolutions> |
| − | |||
| − | |||
| − | |||
<HR> | <HR> | ||
<BR/> | <BR/> | ||
| − | |||
== Motor ECU == | == Motor ECU == | ||
<Picture and link to Gitlab> | <Picture and link to Gitlab> | ||
| Line 146: | Line 149: | ||
=== Technical Challenges === | === Technical Challenges === | ||
| − | < | + | < List of problems and their detailed resolutions> |
| − | |||
| − | |||
| − | |||
<HR> | <HR> | ||
| Line 164: | Line 164: | ||
=== Technical Challenges === | === Technical Challenges === | ||
| − | < | + | < List of problems and their detailed resolutions> |
| − | |||
| − | |||
| − | |||
<HR> | <HR> | ||
<BR/> | <BR/> | ||
| + | <HR> | ||
| + | <BR/> | ||
== Communication Bridge Controller & LCD == | == Communication Bridge Controller & LCD == | ||
<Picture and link to Gitlab> | <Picture and link to Gitlab> | ||
| Line 182: | Line 181: | ||
=== Technical Challenges === | === Technical Challenges === | ||
| − | < | + | < List of problems and their detailed resolutions> |
| − | |||
| − | |||
| − | |||
<HR> | <HR> | ||
| Line 200: | Line 196: | ||
=== Technical Challenges === | === Technical Challenges === | ||
| − | < | + | < List of problems and their detailed resolutions> |
| − | |||
| − | |||
| − | |||
<HR> | <HR> | ||
| Line 217: | Line 210: | ||
=== Technical Challenges === | === Technical Challenges === | ||
| − | < | + | < List of problems and their detailed resolutions> |
| − | + | ||
| − | |||
| − | |||
| + | <BR/> | ||
| + | <HR> | ||
<HR> | <HR> | ||
<BR/> | <BR/> | ||
Latest revision as of 17:18, 3 March 2020
Contents
Project Title
<Team Name>
Abstract
<2-3 sentence abstract>
Introduction
The project was divided into N modules:
- Sensor ...
- Motor..
- ...
- Android
Team Members & Responsibilities
<Team Picture>
Gitlab Project Link - [1]
<Provide ECU names and members responsible> <One member may participate in more than one ECU>
- Sensor
- Link to Gitlab user1
- Link to Gitlab user2
- Motor
- Link to Gitlab user1
- Link to Gitlab user2
- Geographical
- Link to Gitlab user1
- Link to Gitlab user2
- Communication Bridge Controller & LCD
- Link to Gitlab user1
- Link to Gitlab user2
- Android Application
- Link to Gitlab user1
- Link to Gitlab user2
- Testing Team
- Link to Gitlab user1
- Link to Gitlab user2
Schedule
| Week# | Start Date | End Date | Task | Status |
|---|---|---|---|---|
| 1 | 09/15/2017 | 09/16/2017 |
|
Completed |
| 2 | 09/17/2017 | 10/03/2017 |
Parts List & Cost
| Item# | Part Desciption | Vendor | Qty | Cost |
|---|---|---|---|---|
| 1 | RC Car | Traxxas | 1 | $250.00 |
| 2 | CAN Transceivers MCP2551-I/P | Microchip [2] | 8 | Free Samples |
Printed Circuit Board
<Picture and information, including links to your PCB>
CAN Communication
<Talk about your message IDs or communication strategy, such as periodic transmission, MIA management etc.>
Hardware Design
<Show your CAN bus hardware design>
DBC File
<Gitlab link to your DBC file> <You can optionally use an inline image>
Sensor ECU
<Picture and link to Gitlab>
Hardware Design
Software Design
<List the code modules that are being called periodically.>
Technical Challenges
< List of problems and their detailed resolutions>
Motor ECU
<Picture and link to Gitlab>
Hardware Design
Software Design
<List the code modules that are being called periodically.>
Technical Challenges
< List of problems and their detailed resolutions>
Geographical Controller
<Picture and link to Gitlab>
Hardware Design
Software Design
<List the code modules that are being called periodically.>
Technical Challenges
< List of problems and their detailed resolutions>
Communication Bridge Controller & LCD
<Picture and link to Gitlab>
Hardware Design
Software Design
<List the code modules that are being called periodically.>
Technical Challenges
< List of problems and their detailed resolutions>
Master Module
<Picture and link to Gitlab>
Hardware Design
Software Design
<List the code modules that are being called periodically.>
Technical Challenges
< List of problems and their detailed resolutions>
Mobile Application
<Picture and link to Gitlab>
Hardware Design
Software Design
<List the code modules that are being called periodically.>
Technical Challenges
< List of problems and their detailed resolutions>
Conclusion
<Organized summary of the project>
<What did you learn?>
Project Video
Project Source Code
Advise for Future Students
<Bullet points and discussion>
