Difference between revisions of "S24: Team Zero"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Schedule)
Line 12: Line 12:
 
The project was divided into N modules:
 
The project was divided into N modules:
  
* Bridge and Geographical Controller
+
* Bridge and Geological Controller
 
* Motor Controller
 
* Motor Controller
 
* Sensor Controller
 
* Sensor Controller
* Driver Controller and LCD
+
* Driver and LCD Controller
 
* Web Application
 
* Web Application
  
 
=== Team Members & Responsibilities ===
 
=== Team Members & Responsibilities ===
 +
<Team Picture>
  
 
[[File:team_zero_image.jpeg]]
 
[[File:team_zero_image.jpeg]]
Line 28: Line 29:
 
<One member may participate in more than one ECU>
 
<One member may participate in more than one ECU>
  
* Bridge
+
* Lidar
 
** [https://gitlab.com/Ouriquco]
 
** [https://gitlab.com/Ouriquco]
 
** Link to Gitlab user2
 
** Link to Gitlab user2
Line 44: Line 45:
 
** Link to Gitlab user2
 
** Link to Gitlab user2
  
* Web Application
+
* Android Application
 
** Link to Gitlab user1
 
** Link to Gitlab user1
 
** Link to Gitlab user2
 
** Link to Gitlab user2
Line 72: Line 73:
 
* 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.
 +
* Decide on list of parts to be used.
  
 
| Completed
 
| Completed
Line 78: Line 80:
 
| 03/10/2024
 
| 03/10/2024
 
| 03/16/2024
 
| 03/16/2024
* Complete the essential code for each node assigned to the corresponding team member.
+
|
 +
* Order sensor parts, RC car, and other items from list.
 +
* Complete implementation of controller interfaces using custom values and communicating over CAN Bus with DBC.
 +
 
 
|
 
|
 
|-
 
|-
Line 85: Line 90:
 
| 03/23/2024
 
| 03/23/2024
 
|
 
|
 +
* Receive all parts from list.
 +
* Connect sensors to RC car.
 +
* Integrate sensor values into Sensor controller interface.
 +
 
|
 
|
 
|-
 
|-

Revision as of 18:33, 14 March 2024

Project Title

<Team Name>



Abstract

<2-3 sentence abstract>

Introduction

The project was divided into N modules:

  • Bridge and Geological Controller
  • Motor Controller
  • Sensor Controller
  • Driver and LCD Controller
  • Web Application

Team Members & Responsibilities

<Team Picture>

Team zero image.jpeg

Gitlab Project Link - [1]

<Provide ECU names and members responsible> <One member may participate in more than one ECU>

  • Lidar
    • [2]
    • Link to Gitlab user2
  • Motor
    • [3]
    • Link to Gitlab user2
  • Geographical
    • [4]
    • Link to Gitlab user2
  • Communication Bridge Controller & LCD
    • [5]
    • Link to Gitlab user2
  • Android Application
    • Link to Gitlab user1
    • Link to Gitlab user2
  • Testing Team
    • [6]
    • Link to Gitlab user2


Schedule

Week# Start Date End Date Task Status
1 03/03/2024 03/09/2024
  • Read previous projects, gather information and discuss among the group members.
  • Distribute modules to each team member.
  • Decide on list of parts to be used.
Completed
2 03/10/2024 03/16/2024
  • Order sensor parts, RC car, and other items from list.
  • Complete implementation of controller interfaces using custom values and communicating over CAN Bus with DBC.
3 03/17/2024 03/23/2024
  • Receive all parts from list.
  • Connect sensors to RC car.
  • Integrate sensor values into Sensor controller interface.
4 03/24/2024 03/30/2024
5 03/31/2024 04/06/2024
6 04/07/2024 04/13/2024
7 04/14/2024 04/20/2024
8 04/21/2024 04/27/2024


Parts List & Cost

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