Difference between revisions of "S21: Roadster"

Revision as of 21:17, 16 March 2021 (view source) Proj user12 (talk | contribs) (→‎Schedule) ← Older edit		Revision as of 21:26, 16 March 2021 (view source) Proj user12 (talk | contribs) (→‎Schedule) Newer edit →
Line 71:		Line 71:
	! scope="col"| Status		! scope="col"| Status
	|-		|-
−	! scope="row"| 1	+	! scope="row"| 1
−	03/01 to 03/07	+	03/01 to 03/07
−	(Start of Phase 1)	+	''Start of Phase 1''
	|		|
	* 03/01		* 03/01
		+	* 03/04
	* 03/05		* 03/05
	|		|
	* 03/04		* 03/04
		+	* 03/07
	* 03/07		* 03/07
	|		|
	* Study and discuss previous project reports		* Study and discuss previous project reports
		+	* Brainstorm on the requirements for the project
	* Identify and order/purchase the required components		* Identify and order/purchase the required components
	|		|
	* 03/04		* 03/04
−	* 03/09	+	* 03/07
		+	*<font color = "maroon"> 03/09
	|		|
		+	*<font color = "green"> Completed
	*<font color = "green"> Completed		*<font color = "green"> Completed
	*<font color = "green"> Completed		*<font color = "green"> Completed
Line 186:		Line 191:
	! scope="row"| 5		! scope="row"| 5
	03/29 to 04/04		03/29 to 04/04
−	(End of Phase 1)	+	''End of Phase 1''
	|		|
	* 04/02		* 04/02

---

Revision as of 21:26, 16 March 2021

Roadster

Abstract

Roadster is a self-driving RC car. (TODO)

Introduction

The project was divided into N modules:

• Sensor ...
• Motor..
• ...
• Android

Team Members & Responsibilities

<Team Picture>

• Nimit Patel

• Sourab Gupta

• Srikar Reddy Narapureddy

• Tejas Pidkalwar

• Tirth Pandya

Bitbucket Repository

<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	Actual Completion	Status
1 03/01 to 03/07 Start of Phase 1	03/01 03/04 03/05	03/04 03/07 03/07	Study and discuss previous project reports Brainstorm on the requirements for the project Identify and order/purchase the required components	03/04 03/07 03/09	Completed Completed Completed
2 03/08 to 03/14	03/08 03/08 03/11 03/12	03/08 03/08 03/14 03/14	Create and setup Bitbucket Repository Create and setup Confluence for document collaboration Study the datasheets and manual of acquired components Distribute initial roles among the team members	03/04 03/07 03/15	Completed Completed In Progress Completed
3 03/15 to 03/21	03/15 03/15 03/19 03/18 03/15	03/18 03/18 03/21 03/21 03/27	Interface ultrasonic sensors and test the functionality Interface GPS and Compass and test the functionality Analyse and discuss the hardware placement of the RC Car Create SENSOR and DRIVER nodes to transmit and receive data Identify the Android app requirements and start studying the Android framework		In Progress In Progress N/A N/A In Progress
4 03/22 to 03/28	03/22 03/22 03/25 03/27 03/22	03/25 03/24 03/28 03/31 03/28	Create the GEO node to get coordinates and cardinal directions from GPS and Compass Interface the Bluetooth module to communicate with SJ-two board Create the MOTOR node to drive the RC Car Start designing the DBC file Develop an initial version of the Android app		N/A N/A N/A N/A N/A
5 03/29 to 04/04 End of Phase 1	04/02 03/29 03/29 03/29 03/31 04/03	04/03 04/01 04/01 04/01 04/03 04/04	Finalize the DBC file Design obstacle avoidance and steering logic on the DRIVER node Design motor driving logic on the MOTOR node Integrate sensor data on the SENSOR node Interface the Android app with Bluetooth module on DRIVER node Collective Test 1: Integrate all the completed modules and test on the RC Car		N/A N/A N/A N/A N/A N/A

---

Parts List & Cost

Item#	Part Desciption	Vendor	Qty	Cost
1	RC Car	Traxxas	1	$250.00
2	CAN Transceivers MCP2551-I/P	Microchip [1]	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>

Acknowledgement

=== References ===