Difference between revisions of "S19: Lightfury"
Proj user16 (talk | contribs) (→Schedule) |
Proj user16 (talk | contribs) (→Printed Circuit Board) |
||
Line 277: | Line 277: | ||
== Printed Circuit Board == | == Printed Circuit Board == | ||
<Picture and information, including links to your PCB> | <Picture and information, including links to your PCB> | ||
+ | Planned a single PCB to place and route CAN transceivers and eliminate dangling wires. | ||
<br> | <br> | ||
Revision as of 03:37, 14 March 2019
Contents
Project Title
LightFury
Abstract
LightFury is an autonomous electric car project that aims to bring different embedded system paradigms together and consolidate them with industry level sophistication and robustness. This project will feature an RC car which will employ different sensors and motors to navigate the track. Every sensor/motor combined with a dedicated functionality is managed by a controller. Such different controllers will communicate with the master node using the CAN protocol.
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 |
|
In Progress | 03/19/2019 |
5 | 03/19/2019 |
|
Planned | 03/26/2019 |
6 | 03/26/2019 |
|
Planned | 04/02/2019 |
7 | 04/02/2019 |
|
Completed | 04/09/2019 |
8 | 04/09/2019 |
|
Planned | 04/16/2019 |
9 | 04/16/2019 |
|
Planned | 04/23/2019 |
10 | 04/23/2019 |
|
Planned | 04/30/2019 |
10 | 04/23/2019 |
|
Planned | 04/30/2019 |
11 | 04/30/2019 |
|
Planned | 05/07/2019 |
12 | 05/07/2019 |
|
Planned | 05/14/2019 |
12 | 05/14/2019 |
|
Planned | 05/22/2019 |
12 | 05/22/2019 |
|
Planned | 05/22/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>
Planned a single PCB to place and route CAN transceivers and eliminate dangling wires.
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>