Difference between revisions of "S21: UTAH"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Team Members & Responsibilities)
Line 335: Line 335:
 
<BR/>
 
<BR/>
  
−
== Design & Implementation ==
+
== Printed Circuit Board  ==
−
The design section can go over your hardware and software design.  Organize this section using sub-sections that go over your design and implementation.
+
<Picture and information, including links to your PCB>
 +
<br>
 +
 
 +
<HR>
 +
<BR/>
 +
== 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>
 +
 
 +
 
 +
<HR>
 +
<BR/>
 +
== Sensor ECU ==
 +
<Picture and link to Gitlab>
  
 
=== Hardware Design ===
 
=== Hardware Design ===
−
Discuss your hardware design here.  Show detailed schematics, and the interface here.
 
  
−
=== Hardware Interface ===
+
=== Software Design ===
−
In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the '''Software Design''' section is isolated to talk about high level workings rather than inner working of your project.
+
<List the code modules that are being called periodically.>
 +
 
 +
=== Technical Challenges ===
 +
 
 +
< List of problems and their detailed resolutions>
 +
 
 +
<HR>
 +
<BR/>
 +
== Motor ECU ==
 +
<Picture and link to Gitlab>
 +
 
 +
=== Hardware Design ===
  
 
=== Software Design ===
 
=== Software Design ===
−
Show your software design.  For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level.  Do not show the details of the code.  For example, do not show exact code, but you may show psuedocode and fragments of code.  Keep in mind that you are showing DESIGN of your software, not the inner workings of it.
+
<List the code modules that are being called periodically.>
  
−
=== Implementation ===
+
=== Technical Challenges ===
−
This section includes implementation, but again, not the details, just the high level.  For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash.  You can include sub-sections for each of your component implementation.
 
  
−
== Testing & Technical Challenges ==
+
< List of problems and their detailed resolutions>
−
Describe the challenges of your project.  What advise would you give yourself or someone else if your project can be started from scratch again?
 
−
Make a smooth transition to testing section and described what it took to test your project.
 
  
−
Include sub-sections that list out a problem and solution, such as:
+
<HR>
 +
<BR/>
 +
== Geographical Controller ==
  
−
=== <Bug/issue name> ===
+
<Picture and link to Gitlab>
−
Discuss the issue and resolution.
 
  
 +
=== Hardware Design ===
 +
 +
=== Software Design ===
 +
<List the code modules that are being called periodically.>
 +
 +
=== Technical Challenges ===
 +
 +
< List of problems and their detailed resolutions>
 +
 +
<HR>
 +
<BR/>
 +
 +
<HR>
 +
<BR/>
 +
== 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>
 +
 +
<HR>
 +
<BR/>
 +
== 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>
 +
 +
<HR>
 +
<BR/>
 +
== 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>
 +
 +
 +
<BR/>
 +
<HR>
 +
<HR>
 +
<BR/>
 
== Conclusion ==
 
== Conclusion ==
−
Conclude your project here.  You can recap your testing and problems.  You should address the "so what" part here to indicate what you ultimately learnt from this project.  How has this project increased your knowledge?
+
<Organized summary of the project>
 +
 
 +
<What did you learn?>
  
 
=== Project Video ===
 
=== Project Video ===
−
Upload a video of your project and post the link here.
 
  
 
=== Project Source Code ===
 
=== Project Source Code ===
−
*  [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link]
 
  
−
== References ==
+
=== Advise for Future Students ===
 +
<Bullet points and discussion>
 +
 
 
=== Acknowledgement ===
 
=== Acknowledgement ===
−
Any acknowledgement that you may wish to provide can be included here.
 
−
 
−
=== References Used ===
 
−
List any references used in project.
 
  
−
=== Appendix ===
+
=== References ===
−
You can list the references you used.
 

Revision as of 17:18, 9 March 2021

UTAH: Unit Tested to Avoid Hazards

Abstract

UTAH abstract

Objectives & Introduction

Show list of your objectives. This section includes the high level details of your project. You can write about the various sensors or peripherals you used to get your project completed.

Team Members & Responsibilities

Akash Vachhani profilepic.jpg

  • Jonathan Beard
    • Android Application Developer
    • Communication Bridge Controller
  • Ameer Ali
    • Master Controller

Jonathan tran self pic.jpeg

  • Jonathan Tran Gitlab
    • Sensors Controller
  • Amritpal Sidhu
    • Motor Controller
  • Shreevats Gadhikar
    • Motor Controller

Schedule

Week# Start Date End Date Task Status
1
  • 02/15/2021
  • 02/21/2021
  • Read previous projects to understand what is expected and have some meaningful knowledge by first meeting. Assign roles.
  • Completed
2
  • 02/22/2021
  • 02/28/2021
  • Acquire parts: Canbus modules, GPS module, Ultrasonic module, Bluetooth module, Car frame, and LCD display
  • Conduct meeting: Discuss GitLab layout and expectation of each assigned role
  • Completed
3
  • 03/01/2021
  • 03/01/2021
  • 03/01/2021
  • 03/01/2021
  • 03/01/2021
  • 03/01/2021
  • 03/07/2021
  • 03/07/2021
  • 03/07/2021
  • 03/07/2021
  • 03/07/2021
  • 03/07/2021
  • Purchased RC car and batteries.
  • Created branch for motor controller driver. Working on motor controller init.
  • Completed
  • In Progress
4
  • 03/08/2021
  • 03/08/2021
  • 03/08/2021
  • 03/08/2021
  • 03/08/2021
  • 03/08/2021
  • 03/14/2021
  • 03/14/2021
  • 03/14/2021
  • 03/14/2021
  • 03/14/2021
  • 03/14/2021
5
  • 03/15/2021
  • 03/15/2021
  • 03/15/2021
  • 03/15/2021
  • 03/15/2021
  • 03/15/2021
  • 03/21/2021
  • 03/21/2021
  • 03/21/2021
  • 03/21/2021
  • 03/21/2021
  • 03/21/2021
6
  • 03/22/2021
  • 03/22/2021
  • 03/22/2021
  • 03/22/2021
  • 03/22/2021
  • 03/22/2021
  • 03/28/2021
  • 03/28/2021
  • 03/28/2021
  • 03/28/2021
  • 03/28/2021
  • 03/28/2021
7
  • 03/29/2021
  • 03/29/2021
  • 03/29/2021
  • 03/29/2021
  • 03/29/2021
  • 03/29/2021
  • 04/04/2021
  • 04/04/2021
  • 04/04/2021
  • 04/04/2021
  • 04/04/2021
  • 04/04/2021
8
  • 04/05/2021
  • 04/05/2021
  • 04/05/2021
  • 04/05/2021
  • 04/05/2021
  • 04/05/2021
  • 04/11/2021
  • 04/11/2021
  • 04/11/2021
  • 04/11/2021
  • 04/11/2021
  • 04/11/2021
9
  • 04/12/2021
  • 04/12/2021
  • 04/12/2021
  • 04/12/2021
  • 04/12/2021
  • 04/12/2021
  • 04/18/2021
  • 04/18/2021
  • 04/18/2021
  • 04/18/2021
  • 04/18/2021
  • 04/18/2021
10
  • 04/26/2021
  • 05/02/2021
11
  • 05/03/2021
  • 05/09/2021
12
  • 05/10/2021
  • 05/16/2021


Parts List & Cost

Item# Part Description Vendor Qty Cost
1 Traxxas 1/10 Scale RC Short Truck Traxxas [1] 1 $239.99 + Tax
2 2S 7.4V 5000mAh LiPo Battery Pack Amazon [2] 2 $40.69 + Tax
3 Bluetooth Adapter Amazon [3] 1? $8.99 + Tax


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

Retrieved from "http://socialledge.com/sjsu/index.php?title=S21:_UTAH&oldid=64033"