Difference between revisions of "S19: CANT Bus"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Schedule)
(Updated to reflect Preet's Sp2019 project wiki template)
Line 15: Line 15:
  
 
== Abstract ==
 
== Abstract ==
−
This section should be a couple lines to describe what your project does.
+
<2-3 sentence abstract>
  
−
== Objectives & Introduction ==
+
=== 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 ==
+
The project was divided into N modules:
 +
 
 +
* Sensor ...
 +
* Motor..
 +
* ...
 +
* Android
 +
 
 +
=== Team Members & Responsibilities ===
 
* Kevin Chan
 
* Kevin Chan
 
* Khrysta Finch
 
* Khrysta Finch
Line 28: Line 34:
 
* Vijay Vanapalli
 
* Vijay Vanapalli
 
* Nelson Wong
 
* Nelson Wong
 +
 +
<Team Picture>
 +
 +
Gitlab Project Link - [https://gitlab.com/cant-bus/cant-bus]
 +
<BR/>
 +
 +
<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
 +
 +
<br>
  
 
== Schedule ==
 
== Schedule ==
Line 44: Line 84:
 
|3/4
 
|3/4
 
|3/10
 
|3/10
−
|Strategize approach, determine tasks, assign tasks, draft architecture
+
|
 +
* Strategize approach
 +
* Determine tasks
 +
* Assign tasks
 +
* Draft architecture
 
|In progress
 
|In progress
 
|
 
|
Line 51: Line 95:
 
|3/11
 
|3/11
 
|3/17
 
|3/17
−
|Finalize architecture, order parts, begin electrical schematic and PCB design
+
|
 +
*Finalize architecture
 +
*Order parts
 +
*Begin electrical schematic and PCB design
 
|
 
|
 
|
 
|
Line 58: Line 105:
 
|3/18
 
|3/18
 
|3/24
 
|3/24
−
|Finalize electrical schematic and PCB design. Begin code design per subsystem (must include UT!)
+
|
 +
* Finalize electrical schematic and PCB design
 +
* Begin code design per subsystem (must include UT!)
 
|
 
|
 
|
 
|
Line 65: Line 114:
 
|3/25
 
|3/25
 
|3/31
 
|3/31
−
|Continued code design and editing, App dev, Order PCB
+
|
 +
* Continued code design and editing
 +
* Begin app dev
 +
* Order PCB
 
|
 
|
 
|
 
|
Line 72: Line 124:
 
|4/1
 
|4/1
 
|4/7
 
|4/7
−
|Hardware assembly, code review
+
|
 +
* Hardware assembly
 +
* Code review
 
|
 
|
 
|
 
|
Line 79: Line 133:
 
|4/8
 
|4/8
 
|4/14
 
|4/14
−
|App dev complete, continue HW assembly, begin outdoor testing
+
|
 +
* App dev complete
 +
* Continue HW assembly
 +
* Begin outdoor testing
 
|
 
|
 
|
 
|
Line 86: Line 143:
 
|4/15
 
|4/15
 
|4/21
 
|4/21
−
|Review, Revise, Retest
+
|
 +
* Review, Revise, Retest
 
|
 
|
 
|
 
|
Line 93: Line 151:
 
|4/22
 
|4/22
 
|4/28
 
|4/28
−
|Review, Revise, Retest, Code lock at end of the week
+
|
 +
* Review, Revise, Retest
 +
* Code lock at end of the week
 
|
 
|
 
|
 
|
Line 100: Line 160:
 
|4/29
 
|4/29
 
|5/5
 
|5/5
−
|To be determined
+
|
 +
* To be determined
 
|
 
|
 
|
 
|
Line 107: Line 168:
 
|5/6
 
|5/6
 
|5/12
 
|5/12
−
|To be determined
+
|
 +
* To be determined
 
|
 
|
 
|
 
|
 
|}
 
|}
 +
  
 
== Parts List & Cost ==
 
== Parts List & Cost ==
−
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
+
{| class="wikitable"
 +
|-
 +
! scope="col"| Item#
 +
! scope="col"| Part Desciption
 +
! scope="col"| Vendor
 +
! scope="col"| Qty
 +
! scope="col"| Cost
 +
|-
 +
! scope="row"| 1
 +
| RC Car
 +
| Traxxas
 +
| 1
 +
| $250.00
 +
|-
 +
! scope="row"| 2
 +
| CAN Transceivers MCP2551-I/P
 +
| Microchip [http://www.microchip.com/wwwproducts/en/en010405]
 +
| 8
 +
| Free Samples
 +
|-
 +
|}
  
−
== 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>
 +
 
 +
== CAN Communication ==
 +
<Talk about your message IDs or communication strategy, such as periodic transmission, MIA management etc.>
  
 
=== Hardware Design ===
 
=== Hardware Design ===
−
Discuss your hardware design here.  Show detailed schematics, and the interface here.
+
<Show your CAN bus hardware design>
  
−
=== Hardware Interface ===
+
=== DBC File ===
−
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.
+
<Gitlab link to your DBC file>
 +
<You can optionally use an inline image>
 +
 
 +
 
 +
<HR>
 +
<BR/>
 +
== Sensor 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.>
 +
 
 +
=== Technical Challenges ===
  
−
=== Implementation ===
+
<Bullet or Headings of a module>
−
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.
+
==== Unreliable sonor sensors ====
 +
<Problem Summary>
 +
<Problem Resolution>
  
−
== Testing & Technical Challenges ==
+
<HR>
−
Describe the challenges of your project.  What advise would you give yourself or someone else if your project can be started from scratch again?
+
<BR/>
−
Make a smooth transition to testing section and described what it took to test your project.
+
== Motor ECU ==
 +
<Picture and link to Gitlab>
  
−
Include sub-sections that list out a problem and solution, such as:
+
=== Hardware Design ===
  
−
=== <Bug/issue name> ===
+
=== Software Design ===
−
Discuss the issue and resolution.
+
<List the code modules that are being called periodically.>
  
 +
=== Technical Challenges ===
 +
 +
<Bullet or Headings of a module>
 +
==== Unreliable Servo Motors ====
 +
<Problem Summary>
 +
<Problem Resolution>
 +
 +
<HR>
 +
<BR/>
 +
== Geographical Controller ==
 +
 +
<Picture and link to Gitlab>
 +
 +
=== Hardware Design ===
 +
 +
=== Software Design ===
 +
<List the code modules that are being called periodically.>
 +
 +
=== Technical Challenges ===
 +
 +
<Bullet or Headings of a module>
 +
==== Unreliable GPS lock ====
 +
<Problem Summary>
 +
<Problem Resolution>
 +
 +
<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 ===
 +
 +
<Bullet or Headings of a module>
 +
==== Insane Bug ====
 +
<Problem Summary>
 +
<Problem Resolution>
 +
 +
<HR>
 +
<BR/>
 +
== Master Module ==
 +
 +
<Picture and link to Gitlab>
 +
 +
=== Hardware Design ===
 +
 +
=== Software Design ===
 +
<List the code modules that are being called periodically.>
 +
 +
=== Technical Challenges ===
 +
 +
<Bullet or Headings of a module>
 +
==== Improper Unit Testing ====
 +
<Problem Summary>
 +
<Problem Resolution>
 +
 +
<HR>
 +
<BR/>
 +
== Mobile Application ==
 +
<Picture and link to Gitlab>
 +
 +
=== Hardware Design ===
 +
 +
=== Software Design ===
 +
<List the code modules that are being called periodically.>
 +
 +
=== Technical Challenges ===
 +
 +
<Bullet or Headings of a module>
 +
==== Wifi Link Reliability ====
 +
<Problem Summary>
 +
<Problem Resolution>
 +
 +
<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 00:24, 13 March 2019

Grading Criteria

  • How well is Software & Hardware Design described?
  • How well can this report be used to reproduce this project?
  • Code Quality
  • Overall Report Quality:
    • Software Block Diagrams
    • Hardware Block Diagrams
      Schematic Quality
    • Quality of technical challenges and solutions adopted.

Project Title

[C]ompile [A]nother [N]on-[T]rivial Bus

Abstract

<2-3 sentence abstract>

Introduction

The project was divided into N modules:

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

Team Members & Responsibilities

  • Kevin Chan
  • Khrysta Finch
  • Andrew Javier
  • Aaron Lee
  • Jonathan Rojas
  • Vijay Vanapalli
  • Nelson Wong

<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

Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.

Week# Start Date End Date Task Description Status Completion Date
1 3/4 3/10
  • Strategize approach
  • Determine tasks
  • Assign tasks
  • Draft architecture
 In progress
2 3/11 3/17
  • Finalize architecture
  • Order parts
  • Begin electrical schematic and PCB design
3 3/18 3/24
  • Finalize electrical schematic and PCB design
  • Begin code design per subsystem (must include UT!)
4 3/25 3/31
  • Continued code design and editing
  • Begin app dev
  • Order PCB
5 4/1 4/7
  • Hardware assembly
  • Code review
6 4/8 4/14
  • App dev complete
  • Continue HW assembly
  • Begin outdoor testing
7 4/15 4/21
  • Review, Revise, Retest
8 4/22 4/28
  • Review, Revise, Retest
  • Code lock at end of the week
9 4/29 5/5
  • To be determined
10 5/6 5/12
  • To be determined


Parts List & Cost

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

<Bullet or Headings of a module>

Unreliable sonor sensors

<Problem Summary> <Problem Resolution>


Motor ECU

<Picture and link to Gitlab>

Hardware Design

Software Design

<List the code modules that are being called periodically.>

Technical Challenges

<Bullet or Headings of a module>

Unreliable Servo Motors

<Problem Summary> <Problem Resolution>


Geographical Controller

<Picture and link to Gitlab>

Hardware Design

Software Design

<List the code modules that are being called periodically.>

Technical Challenges

<Bullet or Headings of a module>

Unreliable GPS lock

<Problem Summary> <Problem Resolution>


Communication Bridge Controller & LCD

<Picture and link to Gitlab>

Hardware Design

Software Design

<List the code modules that are being called periodically.>

Technical Challenges

<Bullet or Headings of a module>

Insane Bug

<Problem Summary> <Problem Resolution>


Master Module

<Picture and link to Gitlab>

Hardware Design

Software Design

<List the code modules that are being called periodically.>

Technical Challenges

<Bullet or Headings of a module>

Improper Unit Testing

<Problem Summary> <Problem Resolution>


Mobile Application

<Picture and link to Gitlab>

Hardware Design

Software Design

<List the code modules that are being called periodically.>

Technical Challenges

<Bullet or Headings of a module>

Wifi Link Reliability

<Problem Summary> <Problem Resolution>


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=S19:_CANT_Bus&oldid=51839"