Difference between revisions of "S21: Roadster"
Proj user12 (talk | contribs) (→Project Title) |
Proj user12 (talk | contribs) (→Abstract) |
||
| Line 2: | Line 2: | ||
== Abstract == | == Abstract == | ||
| − | + | ''Roadster'' is a self-driving RC car. (TODO) | |
=== Introduction === | === Introduction === | ||
| Line 16: | Line 16: | ||
<Team Picture> | <Team Picture> | ||
| − | Nimit Patel | + | * Nimit Patel |
| − | Sourab Gupta | + | * Sourab Gupta |
| − | Srikar Reddy Narapureddy | + | * Srikar Reddy Narapureddy |
| − | Tejas Pidkalwar | + | * Tejas Pidkalwar |
| − | Tirth Pandya | + | * Tirth Pandya |
| − | + | [https://bitbucket.org/tejasPidkalwar/roadster/src/Main/ Bitbucket Repository] | |
<BR/> | <BR/> | ||
| − | |||
| − | |||
<Provide ECU names and members responsible> | <Provide ECU names and members responsible> | ||
Revision as of 20:08, 16 March 2021
Contents
Roadster
Abstract
Roadster is a self-driving RC car. (TODO)
Introduction
The project was divided into N modules:
- Sensor ...
- Motor..
- ...
- Android
Team Members & Responsibilities
<Team Picture>
- Nimit Patel
- Sourab Gupta
- Srikar Reddy Narapureddy
- Tejas Pidkalwar
- Tirth Pandya
<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
| Week# | Start Date | End Date | Task | Status |
|---|---|---|---|---|
| 1 | 09/15/2017 | 09/16/2017 |
|
Completed |
| 2 | 09/17/2017 | 10/03/2017 |
Parts List & Cost
| Item# | Part Desciption | Vendor | Qty | Cost |
|---|---|---|---|---|
| 1 | RC Car | Traxxas | 1 | $250.00 |
| 2 | CAN Transceivers MCP2551-I/P | Microchip [1] | 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
< 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>
