S22: TBD

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	02/15/2022	02/21/2022	Ordered parts, discussed sensors for prototyping, and reviewed previous projects.	Completed
2	02/22/2022	02/28/2022	Divide the tasks among the team and finalize parts.	Completed
3	03/01/2022	03/07/2022	Initial Draft for common DBC file for sensor readings	Completed
4	03/08/2022	03/14/2022	Get Data from Ultrasonic Sensor	Incomplete
5	03/15/2022	03/21/2022	Get Data from Ultrasonic Sensor	Incomplete
6	03/22/2022	03/28/2022	Get Data from Ultrasonic Sensor	Incomplete
7	03/29/2022	04/04/2022	Get Data from Ultrasonic Sensor	Incomplete
8	04/05/2022	04/11/2022	Get Data from Ultrasonic Sensor	Incomplete
9	04/12/2022	04/18/2022	Get Data from Ultrasonic Sensor	Incomplete
10	04/19/2022	04/25/2022	Get Data from Ultrasonic Sensor	Incomplete
11	04/26/2022	05/02/2022	Get Data from Ultrasonic Sensor	Incomplete
12	05/03/2022	05/09/2022	Get Data from Ultrasonic Sensor	Incomplete
13	05/10/2022	05/16/2022	Get Data from Ultrasonic Sensor	Incomplete
14	05/17/2022	05/25/2022	Get Data from Ultrasonic Sensor	Incomplete

---

Parts List & Cost

Item#	Part Desciption	Vendor	Qty	Cost
1	RC Car	Redcat Racing [2]	1	$139.00
2	CAN Transceivers (SN65HVD230)	Microchip [3]	4	$10.00

---

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>

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>

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>

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>

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>

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>

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?>

Advise for Future Students

<Bullet points and discussion>