Difference between revisions of "S19: CANT Bus"
Proj user4 (talk | contribs) (→Schedule) |
Proj user4 (talk | contribs) (→Team Members & Responsibilities) |
||
| Line 28: | Line 28: | ||
=== Team Members & Responsibilities === | === Team Members & Responsibilities === | ||
* Kevin Chan | * Kevin Chan | ||
| + | ** Lidar, Tachometer, Power, Wireless communications | ||
* Khrysta Finch | * Khrysta Finch | ||
| + | ** Assistant Team Leader, Chassis, Telemetry, Compass, Driver (PCB/Schematic) | ||
* Andrew Javier | * Andrew Javier | ||
| + | ** Motor, Steering, Compass, Wireless communications (GPS, Lidar, Chasis) | ||
* Aaron Lee | * Aaron Lee | ||
| + | ** GPS, Mobile App (Compass, Telemetry) | ||
* Jonathan Rojas | * Jonathan Rojas | ||
| + | ** GPS, Lidar, Tachometer, Power | ||
* Vijay Vanapalli | * Vijay Vanapalli | ||
| + | ** Motor, Steering, PCB/Schematic (Mobile App) | ||
* Nelson Wong | * Nelson Wong | ||
| + | ** Team Leader, Driver, Telemetry, PCB/Schematic, Chassis, Mobile App | ||
<Team Picture> | <Team Picture> | ||
Revision as of 03:21, 14 March 2019
Contents
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
- Lidar, Tachometer, Power, Wireless communications
- Khrysta Finch
- Assistant Team Leader, Chassis, Telemetry, Compass, Driver (PCB/Schematic)
- Andrew Javier
- Motor, Steering, Compass, Wireless communications (GPS, Lidar, Chasis)
- Aaron Lee
- GPS, Mobile App (Compass, Telemetry)
- Jonathan Rojas
- GPS, Lidar, Tachometer, Power
- Vijay Vanapalli
- Motor, Steering, PCB/Schematic (Mobile App)
- Nelson Wong
- Team Leader, Driver, Telemetry, PCB/Schematic, Chassis, Mobile App
<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 |
|
Complete | |
| 2 | 3/11 | 3/17 |
|
||
| 3 | 3/18 | 3/24 |
|
||
| 4 | 3/25 | 3/31 |
|
||
| 5 | 4/1 | 4/7 |
|
||
| 6 | 4/8 | 4/14 |
|
||
| 7 | 4/15 | 4/21 |
|
||
| 8 | 4/22 | 4/28 |
|
||
| 9 | 4/29 | 5/5 |
|
||
| 10 | 5/6 | 5/12 |
|
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>
