Difference between revisions of "S23: X Æ A-13"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Schedule)
(Schedule)
Line 60: Line 60:
 
! scope="col"| End Date
 
! scope="col"| End Date
 
! scope="col"| Task
 
! scope="col"| Task
 +
! scope="col"| Point of Contact
 
! scope="col"| Status
 
! scope="col"| Status
 
|-
 
|-
Line 69: Line 70:
 
* <font color = "green">Create a private git fork for the RC car repository.
 
* <font color = "green">Create a private git fork for the RC car repository.
 
* <font color = "green">Decide and conclude a recurring team meeting schedule
 
* <font color = "green">Decide and conclude a recurring team meeting schedule
|<font color = "green"> Completed
+
| Entire team
 +
|<font color = "green">Completed
 
|-
 
|-
 
! scope="row"| 2
 
! scope="row"| 2

Revision as of 04:02, 30 March 2023

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

Task# Start Date End Date Task Point of Contact Status
1 02/13/2023 02/18/2023
  • Read previous projects, gather information and discuss among the group members.
  • Create a private git fork for the RC car repository.
  • Decide and conclude a recurring team meeting schedule
Entire team Completed
2 02/20/2023 02/22/2023
  • Order CAN transceiver modules
Completed
3 03/03/2023 03/10/2023
  • Research several RC Car for the target application
  • Purchase RC Car
Completed
4 03/10/2023 03/17/2023
  • Create a git flow process. Establish a process for merging into the master code repository.
  • Finalize the sensors and other hardware we need for the project.
  • Finalize the best available hardware based on the data collected.
  • To validate communication between CAN nodes and PCAN data.
Ongoing
5 03/28/2023 04/03/2023
  • Design Geo Controller module
Ongoing
6 04/03/2023 04/10/2023
  • Create a custom DBC file
  • Design the modularity of each nodes
TBD
7 04/03/2023 04/10/2023
  • Decision on the app development platform
  • Decide on Flutter vs Android Studio
  • Learn the fundamentals of Android app development
TBD
8 04/11/2023 04/18/2023
  • Decide WiFi or Bluetooth for primary connectivity
  • Establish a base code platform for the communication module
  • Develop the car data display page for the mobile application.
TBD
9 04/11/2023 04/18/2023
  • Design of compass module
  • Practical validation of the GPS lab parser
  • Engage in compass calibration and integrate data with other CAN modules.
TBD
10 04/11/2023 04/18/2023
  • Decoding the ESC logic of the car
  • Formulating the motor logic
  • Design and test the HMI and LCD module
TBD
11 04/19/2023 04/26/2023
  • Integration testing with obstacle avoidance algorithm
  • Start examining the results of practical trials conducted in the past week's execution and make necessary adjustments to address encountered problems.
  • Verify the accuracy of the Direction Distance Calculation Module through unit testing, ensuring that the module output matches the manual calculation of data.
  • Design and build the PCB for the present prototype
TBD


Parts List & Cost

Item# Part Desciption Vendor Qty Cost
1 RC Car Maverick Quantum MT [2] 1 $180.00
2 RC Car Battery Lithium Polymer Two-Cell 1 $20.0
3 CAN Transceiver Modules SN65HVD230 4 $43.56
4 Microcontroller Development Environment SJTwo Board 5 $250


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