Difference between revisions of "S24: Team TerraByte"

Revision as of 05:59, 10 March 2024 (view source) 243 user2 (talk | contribs) (→‎Team Members & Responsibilities) ← Older edit		Revision as of 06:03, 10 March 2024 (view source) 243 user2 (talk | contribs) (→‎Schedule) Newer edit →
Line 116:		Line 116:
	* Read previous projects, gather information and discuss among the group members.		* Read previous projects, gather information and discuss among the group members.
	* Distribute modules to each team member.		* Distribute modules to each team member.
−		+	* Order CAN transceiver modules
		+	* Build  db9 connector and connect to Busmaster.
	| <font color = "green">Completed		| <font color = "green">Completed
	|-		|-
Line 123:		Line 124:
	| 03/10/2024		| 03/10/2024
	|		|
−	* Order CAN transceiver modules	+
	| <font color = "red">Incomplete		| <font color = "red">Incomplete

---

Revision as of 06:03, 10 March 2024

Title

TerraByte

---

Abstract

<2-3 sentence abstract>

Introduction

The project was divided into 5 modules:

• Sensor Node
• Motor Node
• Driver Node
• Geo Controller Node
• Android App

Team Members & Responsibilities

<Team Picture>

Gitlab Project Link - C243_TerraByte
Team Members: Dikshant Kotla, Harikrishnan Kokkanthara Jeevan, Minal Upadhye, Susmitha Ganesh, Vamsi Rushi Dhanekula

Team Members	Technical Roles
Dikshant Kotla	Driver Node Owner
Harikrishnan Kokkanthara Jeevan	Motor Node Owner
Minal Upadhye	Sensor Node and Motor Node Co-Owner
Susmitha Ganesh	Geological Node Owner
Vamsi Rushi Dhanekula	Mobile App Owner Bluetooth Communication and LCD Display

• 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	03/04/2024	03/10/2024	Read previous projects, gather information and discuss among the group members. Distribute modules to each team member. Order CAN transceiver modules Build db9 connector and connect to Busmaster.	Completed
2	03/04/2024	03/10/2024		Incomplete
3	03/11/2024	03/17/2024	TBD	Incomplete
4	03/18/2024	03/24/2024	TBD	Incomplete
5	03/25/2024	03/31/2024	TBD	Incomplete
6	04/01/2024	04/07/2024	TBD	Incomplete
7	04/08/2024	04/14/2024	TBD	Incomplete
8	04/15/2024	04/21/2024	TBD	Incomplete
9	04/22/2024	04/28/2024	TBD	Incomplete
10	04/29/2024	05/05/2024	TBD	Incomplete
11	05/06/2024	05/12/2024	TBD	Incomplete
12	05/13/2024	05/19/2024	TBD	Incomplete
13	05/20/2024	05/26/2024	TBD	Incomplete

---

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