Difference between revisions of "S20: Bucephalus"
(→Schedule) |
(→Schedule) |
||
Line 198: | Line 198: | ||
* <font color="black">Draw block diagrams with pin information for each board and begin PCB design based on these diagrams | * <font color="black">Draw block diagrams with pin information for each board and begin PCB design based on these diagrams | ||
* <font color="black">Start implementing a basic Android app without Google maps API and create a separate GitLab repo for app | * <font color="black">Start implementing a basic Android app without Google maps API and create a separate GitLab repo for app | ||
− | * <font color=" | + | * <font color="33BAFF">Geological node is able to transmit a heading message to the driver node |
* <font color="CDCC1C">Bridge sensor node is able to transmit a destination latitude and longitude coordinates message to geological node | * <font color="CDCC1C">Bridge sensor node is able to transmit a destination latitude and longitude coordinates message to geological node | ||
* <font color="CDCC1C">Decide on ultrasonic sensor mounts and order extra if needed | * <font color="CDCC1C">Decide on ultrasonic sensor mounts and order extra if needed | ||
Line 227: | Line 227: | ||
| | | | ||
* <font color="CDCC1C">Finish a basic implementation of filtering ultrasonic sensor's ADC data | * <font color="CDCC1C">Finish a basic implementation of filtering ultrasonic sensor's ADC data | ||
− | * <font color=" | + | * <font color="33BAFF">Geological node is able to compute the destination heading (0-360 degrees) and send to driver node |
* <font color="4CA821">Add PWM functionality to motor board code and test on DC and servo motors | * <font color="4CA821">Add PWM functionality to motor board code and test on DC and servo motors | ||
* <font color="4CA821">Complete a basic implementation of encoder code on motor board | * <font color="4CA821">Complete a basic implementation of encoder code on motor board | ||
Line 233: | Line 233: | ||
* <font color="black">Complete rough draft of schedule and upload to Wiki page | * <font color="black">Complete rough draft of schedule and upload to Wiki page | ||
* <font color="black">Learn how to integrate Google maps API into Android app | * <font color="black">Learn how to integrate Google maps API into Android app | ||
− | * <font color=" | + | * <font color="33BAFF">Geological node is able to parse the GPS NMEA string to extract latitude and longitude coordinates |
* <font color="black">Complete rough draft of DBC file messages and signals | * <font color="black">Complete rough draft of DBC file messages and signals | ||
− | * <font color=" | + | * <font color="33BAFF">Geological node is able to receive a current heading (0-360 degrees) from the compass module |
− | * <font color=" | + | * <font color="33BAFF">Geological node is able to receive an NMEA string from the GPS |
* <font color="CDCC1C">Design a block diagram for optimal ultrasonic sensor placement | * <font color="CDCC1C">Design a block diagram for optimal ultrasonic sensor placement | ||
* <font color="black">Purchase tap plastic acrylic sheet | * <font color="black">Purchase tap plastic acrylic sheet | ||
Line 292: | Line 292: | ||
* <font color="black">Establish and test CAN communication between all boards | * <font color="black">Establish and test CAN communication between all boards | ||
* <font color="black">Display sensor and motor data on Android app | * <font color="black">Display sensor and motor data on Android app | ||
− | * <font color=" | + | * <font color="33BAFF">Finish GPS module integration with geographical controller |
* <font color="black">Design and solder a prototype PCB board in case PCB isn't delivered in time | * <font color="black">Design and solder a prototype PCB board in case PCB isn't delivered in time | ||
* <font color="4CA821">Test existing motor board code on RC car's motors | * <font color="4CA821">Test existing motor board code on RC car's motors | ||
Line 353: | Line 353: | ||
* <font color="4CA821">Fully integrate wheel encoder onto car chassis | * <font color="4CA821">Fully integrate wheel encoder onto car chassis | ||
* <font color="4CA821">Finish basic implementation of PID control and test on car | * <font color="4CA821">Finish basic implementation of PID control and test on car | ||
− | * <font color=" | + | * <font color="33BAFF">GEO controller can compute the heading from Android app's actual destination coordinates, and send to driver board |
* <font color="black">Solder and integrate PCB onto car and test drive to make sure everything is working properly | * <font color="black">Solder and integrate PCB onto car and test drive to make sure everything is working properly | ||
Line 374: | Line 374: | ||
* <font color="black">Test drive from start to destination with obstacles and making U-turns (outdoor) | * <font color="black">Test drive from start to destination with obstacles and making U-turns (outdoor) | ||
* <font color="black">Finalize DBC file | * <font color="black">Finalize DBC file | ||
− | * <font color=" | + | * <font color="33BAFF">Complete basic implementation and unit testing of checkpoint algorithm |
− | * <font color=" | + | * <font color="33BAFF">Test checkpoint algorithm on car (outdoor) |
* <font color="4CA821">Finalize PID control implementation and test on car (outdoor) | * <font color="4CA821">Finalize PID control implementation and test on car (outdoor) | ||
* <font color="black">Complete Android app's basic features (start, stop, connect, google maps, displaying car data) | * <font color="black">Complete Android app's basic features (start, stop, connect, google maps, displaying car data) | ||
Line 406: | Line 406: | ||
* <font color="4CA821">Tweak PID control implementation based on feedback from test drives | * <font color="4CA821">Tweak PID control implementation based on feedback from test drives | ||
* <font color="black">Tweak obstacle avoidance algorithm based on feedback from test drives | * <font color="black">Tweak obstacle avoidance algorithm based on feedback from test drives | ||
− | * <font color=" | + | * <font color="33BAFF">Finalize checkpoint algorithm based on feedback from test drives |
* <font color="black">Finalize Android app's checkpoint selection capability, display car data screen, and UI improvements | * <font color="black">Finalize Android app's checkpoint selection capability, display car data screen, and UI improvements | ||
Revision as of 22:43, 7 May 2020
Contents
ABSTRACT
Bucephalus is a Self Driving RC car using CAN communication based on FreeRTOS(Hard RTOS). The RC car takes real time inputs and covert it into the data that can be processed to monitor and control to meet the desired requirements. In this project, we aim to design and develop a self-driving car that autonomously navigates from the current location to the destination (using Waypoint Algorithm )which is selected through an Android application and at the same time avoiding all the obstacles in the path using Obstacle avoidance algorithm . It also Increases or Decreases speed on Uphill and downhill (using PID Algorithm)as well as applies breaks at required places. The car comprises of 4 control units communicating with each other over the CAN Bus using CAN communication protocol, each having a specific functionality that helps the car to navigate to its destination successfully.
INTRODUCTION
Objectives of the RC Car:-
1) Driver Controller:- Detection and avoidance of the obstacles coming in the path of the RC car by following Obstacle detection avoidance.
2) Geographical Controller:- Getting the GPS coordinates from the Android Application and traveling to that point using Waypoint Algorithm
3) System hardware communication using PCB Design.
4) Bridge and Sensor Controller:- Communication between the Driver Board and Android Mobile Application using wireless bluetooth commmunication.
5) Motor Controller:- Control the Servo Motor for Direction and DC motor for speed. Implementation of PID Algorithm on normal road uphill and down hill to maintain speed
The project is divided into six main modules:
CORE MODULES OF RC CAR | ||||
---|---|---|---|---|
|
Team Members & Responsibilities
<Team Picture>
Bucephalous GitLab - [1]
- Mohit Ingale GitLab LinkedIn
- Driver and LCD Controller
- Hardware Integration (PCB Designing)
- Testing Team / Code Reviewers
- Shreya Patankar GitLab LinkedIn
- Geographical Controller
- Hardware Integration (PCB Designing)
- Testing Team / Code Reviewers
- Wiki Page
- Nicholas Kaiser GitLab LinkedIn
- Bridge and Sensor Controller
- Wiki Page
- Hardware Integration (PCB Designing)
- Hari Haran Kura GitLab LinkedIn
- Motor Controller
- Testing Team / Code Reviewers
- Hardware Integration (PCB Designing)
- Abhinandan Burli GitLab LinkedIn
- Driver and LCD Controller
- Testing Team / Code Reviewers
- Hardware Integration (PCB Designing)
Schedule
Week# | Start Date | End Date | Task | Status |
---|---|---|---|---|
1 | 02/16/2020 | 02/22/2020 |
|
|
2 | 02/23/2020 | 02/29/2020 |
|
|
3 | 03/01/2020 | 03/07/2020 |
|
|
4 | 03/08/2020 | 03/14/2020 |
|
|
5 | 03/15/2020 | 03/21/2020 |
|
|
6 | 03/22/2020 | 03/28/2020 |
|
|
7 | 03/29/2020 | 04/04/2020 |
|
|
8 | 04/05/2020 | 04/11/2020 |
|
|
9 | 04/12/2020 | 04/18/2020 |
|
|
10 | 04/19/2020 | 04/25/2020 |
|
|
11 | 04/26/2020 | 05/02/2020 |
|
|
12 | 05/03/2020 | 05/09/2020 |
|
|
13 | 05/10/2020 | 05/16/2020 |
|
|
14 | 05/17/2020 | 05/23/2020 |
|
|
Parts List & Cost
Item# | Part Desciption | Vendor | Qty | Cost |
---|---|---|---|---|
1 | RC Car Chassis | Traxxas | 1 | $250.00 |
2 | Lithium-Ion Battery | 1 | ||
3 | Battery Charger | 1 | ||
4 | Tap Plastics Acrylic Sheet | 1 | ||
5 | Ultrasonic Sensors | Amazon [2] | 4 | |
6 | GPS Module | 1 | ||
7 | GPS Antenna | 1 | ||
8 | Compass Module | 1 | ||
9 | UART LCD Display | 1 | ||
10 | Bluetooth Module | 1 | ||
11 | CAN Transceivers SN65HVD230DR | 15 | Free Samples | |
12 | Sjtwo Board | Preet | 4 | $50.00 |
13 | 12" Pipe | 1 | ||
14 | Android Mobile Phone | 1 | ||
15 | Sensor Mounts | 4 |
Hardware Integration:- Printed Circuit Board
We Initially started with a very basic design of mounting all the hardware on a cardboard sheet for our first round of Integrated hardware testing.
Challenges:- The wires were an entire mess and the car could not navigate properly due to the wiring issues as all the wires were entangling and few had connectivity issues.
Hence we decided to go for a basic dot matrix Design before finalizing our final PCB Design as a Prototype board for testing if anything goes haywire.
The Prototype Board just before the actual PCB board was created on a dot matrix PCB along with all the hardware components for the Intermediate Integrated testing phase is as follows:
1) To avoid all the above challenges We designed the custom PCB using EasyEDA in which we implemented connections for all the controller modules(SJTwo Board LPC4078) all communicating/sending data via CAN bus. The data is sent by individual sensors to the respective controllers. GPS and Compass are connected to Geographical Controller. RPM sensor, DC and Servo Motors are connected to Motor Controller.
2) Ultrasonic are connected to Bridge and Sensor Controller. LCD is connected to Driver Controller. Bluetooth is connected to Bridge and Sensor Controller. CAN Bus is implemented using CAN Transceivers SN65HVD230 terminated by 120 Ohms; with PCAN for monitoring CAN Debug Messages and Data. Some Components need 5V while some sensors worked on 3.3V power supply. Also it was difficult to use separate USB's to power up all boards.Hence we used CorpCo breadboard power supply 3.3V/5V.
3) PCB was sent to fabrication to JLCPCB China which provided PCB with MOQ of 5 with the lead time of 1 week. We implemented 2 layers of PCB with most of the parts in top layer GPS sensor and Compass sensor. We implemented rectangular header connector for SJTwo boards, RPM sensor, DC & Servo Motor on the bottom layer. There were 2 iterations of this board.
4) Challenges :-We also need to change the header for LCD since it was having different pitch.
DESIGNING:-
AFTER DELIVERY:-
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
Bridge and Sensor 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>
Motor 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>
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>
Driver 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>
Acknowledgement
=== References ===