Difference between revisions of "S19: Lightfury"
Proj user16 (talk | contribs) (→Abstract) |
Proj user16 (talk | contribs) (→Schedule) |
||
Line 69: | Line 69: | ||
| 02/12/2019 | | 02/12/2019 | ||
| | | | ||
− | * Form Teams | + | * Form Teams and decide group name. Also look up past projects and learn about the autonomous car design. |
| Completed | | Completed | ||
Line 79: | Line 79: | ||
| | | | ||
* Setup Gitlab | * Setup Gitlab | ||
− | * Order | + | * Order CAN Transceivers. Study CAN communication. |
* Commit and raise merge request by each member to get hold over Gitlab basics | * Commit and raise merge request by each member to get hold over Gitlab basics | ||
| Completed | | Completed | ||
Line 88: | Line 88: | ||
| 02/26/2019 | | 02/26/2019 | ||
| | | | ||
− | * Setup Gitlab | + | * Setup Gitlab master branch for Project Light Fury. Create and merge branches for development tracking. |
| Completed | | Completed | ||
Line 98: | Line 98: | ||
* Read previous projects, gather information and discuss among the group members. | * Read previous projects, gather information and discuss among the group members. | ||
* Distribute modules to each team member. | * Distribute modules to each team member. | ||
− | * | + | * Divide the applications in different module for independent development. |
* Identify the baseline application. | * Identify the baseline application. | ||
| Completed | | Completed | ||
Line 107: | Line 107: | ||
| 03/12/2019 | | 03/12/2019 | ||
| | | | ||
− | * Identify components for the project | + | * Identify components required for the project |
* Allocated budget for the project | * Allocated budget for the project | ||
* Order Components | * Order Components |
Revision as of 03:19, 14 March 2019
Contents
Project Title
LightFury
Abstract
LightFury is an autonomous electric car that takes GPS location as a destination from an Android smartphone application and navigates with the help of sensors (sonar, compass) to the provided coordinates. The car uses SJOne boards based on LPC 1758 Microcontrollers. This page is a represents design report for the project.
Introduction
The project was divided into 7 modules:
- Master Controller
- Motor Controller
- Sensor Controller
- GPS Controller
- Android application and Bluetooth Connectivity
- Hardware (PCB designing)
- Testing
Team Members & Responsibilities
<Team Picture>
<Provide ECU names and members responsible> <One member may participate in more than one ECU>
- Sensor
- Ultrasonic
- Compass
- Motor Controller
- Geographical Controller
- Communication Bridge Controller & LCD
- Android Application
- Testing
Schedule
Week# | Start Date | Task | Status | Completion Date |
---|---|---|---|---|
1 | 02/12/2019 |
|
Completed | 02/12/2019 |
2 | 02/19/2019 |
|
Completed | 02/19/2019 |
3 | 02/26/2019 |
|
Completed | 02/26/2019 |
4 | 03/05/2019 |
|
Completed | 03/09/2019 |
5 | 03/12/2019 |
|
Completed | 03/19/2019 |
5 | 03/19/2019 |
|
Completed | 03/26/2019 |
6 | 03/26/2019 |
|
Completed | 04/02/2019 |
7 | 04/02/2019 |
|
Completed | 04/09/2019 |
7 | 04/09/2019 |
|
Completed | 04/16/2019 |
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 |
3 | Semtec GPS | 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>