Difference between revisions of "S20: Nimble"
(→Parts List & Cost) |
(→Parts List & Cost) |
||
Line 220: | Line 220: | ||
| $ 6.00 '''per unit including shipping fee''' | | $ 6.00 '''per unit including shipping fee''' | ||
|- | |- | ||
− | |} | + | ! scope="row"| 3 |
+ | | GPS | ||
+ | | Amazon [] | ||
+ | | 1 | ||
+ | | $ .00 '''per unit including shipping fee''' | ||
+ | |- | ||
+ | ! scope="row"| 4 | ||
+ | | Compass | ||
+ | | Amazon [] | ||
+ | | 1 | ||
+ | | $ .00 '''per unit including shipping fee''' | ||
+ | |- | ||
+ | | | ||
+ | |||
+ | } | ||
<HR> | <HR> |
Revision as of 03:41, 11 March 2020
Contents
Project Title
<Nimble>
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>
- Tanmay Chandavarkar <Master, Sensors>
- Yuming Cheng < Master, GPS, Motor >
- Ellis Makwana <Master, Sensors>
- Naeem Mannan <Master, Mobile Application, To be determined>
- Francesco Vescio <To be determined>
- Lawrence Wan <Master, GPS, Motor, Sensors>
- 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
Team Deliverables Schedule
WEEK |
START DATE |
END DATE |
TASK DETAILS |
STATUS |
---|---|---|---|---|
1 | Feb 2020 | 4 March 2020 |
|
Completed Completed Completed Completed |
2 | 05 March 2020 | 12 March 2020 |
|
In Progress Completed In Progress In Progress |
3 | 13 March 2020 | 19 March 2020 |
|
In Progress Not Started Yet Completed In Progress In Progress In Progress In Progress |
4 | 20 March 2020 | 26 March 2020 |
|
In Progress Not Started Yet Not Started Yet Not Started Yet Not Started Yet Not Started Yet |
5 | 27 March 2019 | 09 April 2019 |
|
Not Started Yet Not Started Yet Not Started Yet Not Started Yet Not Started Yet Not Started Yet Not Started Yet Not Started Yet Not Started Yet Not Started Yet Not Started Yet Not Started Yet Not Started Yet Not Started Yet Not Started Yet Not Started Yet Not Started Yet |
6 | 10 April 2020 | 16 April 2020 |
|
|
7 | 17 April 2020 | 23 April 2020 |
|
|
8 | 24 April 2020 | 30 April 2020 |
|
|
9 | 1 May 2020 | 7 May 2020 |
|
|
10 | 8 May 2020 | 21 May 2020 |
|
|
11 | 22 May 2020 |
|
|
Parts List & Cost
Item# | Part Desciption | Vendor | Qty | Cost |
---|---|---|---|---|
1 | RC Car | Traxxas - Amazon [2] | 1 | $168.84 |
2 | CAN Transceivers MCP2551-I/P | Robotshop [3] | 6 | $ 6.00 per unit including shipping fee |
3 | GPS | Amazon [] | 1 | $ .00 per unit including shipping fee |
4 | Compass | Amazon [] | 1 | $ .00 per unit including shipping fee |
}
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 DesignSoftware 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 DesignSoftware 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 DesignSoftware 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 DesignSoftware 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 DesignSoftware 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 DesignSoftware 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 VideoProject Source CodeAdvise for Future Students<Bullet points and discussion> AcknowledgementReferences |