Difference between revisions of "S19: Lightfury"
Proj user16 (talk | contribs) (→Schedule) |
Proj user16 (talk | contribs) (→Schedule) |
||
Line 76: | Line 76: | ||
| | | | ||
* Setup Gitlab | * Setup Gitlab | ||
+ | * Order Tranceivers | ||
+ | * Commit and raise merge request by each member to get hold over Gitlab basics | ||
| Completed | | Completed | ||
Line 103: | Line 105: | ||
| | | | ||
* Identify components for the project | * Identify components for the project | ||
+ | * Allocated budget for the project | ||
* Order Components | * Order Components | ||
| Completed | | Completed | ||
Line 114: | Line 117: | ||
* Sensor: Perused the datasheet to get started with development | * Sensor: Perused the datasheet to get started with development | ||
* GPS: Went through the datasheet and circuitry details for GPS module(no.) | * GPS: Went through the datasheet and circuitry details for GPS module(no.) | ||
+ | * Compass & LCD: | ||
+ | * Motor: | ||
+ | * Android : | ||
+ | * BLE: | ||
+ | |||
| Completed | | Completed | ||
Line 124: | Line 132: | ||
* Sensor: Successfully interfaced ultrasonic/Lidar with LPC to get raw data | * Sensor: Successfully interfaced ultrasonic/Lidar with LPC to get raw data | ||
* GPS: Successfully interfaced ultrasonic/Lidar with LPC to get raw data | * GPS: Successfully interfaced ultrasonic/Lidar with LPC to get raw data | ||
+ | * Compass & LCD: | ||
+ | * Motor: | ||
+ | * Android : | ||
+ | * BLE: | ||
| Completed | | Completed | ||
Line 134: | Line 146: | ||
* Sensor: Parsed the raw data to achieve useful data | * Sensor: Parsed the raw data to achieve useful data | ||
* GPS: Parsing of raw data to get meaningful values | * GPS: Parsing of raw data to get meaningful values | ||
+ | * Compass & LCD: | ||
+ | * Motor: | ||
+ | * Android : | ||
+ | * BLE: | ||
| Completed | | Completed | ||
Revision as of 02:32, 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 self-navigates to the provided coordinates. The car uses SJOne boards based on LPC 1758 Microcontrollers. This page is a detailed report of the whole 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>
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
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 |
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 |
3 | Semtec GPS | Microchip [3] | 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>