Difference between revisions of "S24: Team Gran Turismo"

Revision as of 15:29, 17 May 2024

1 Project Title
2 Abstract
- 2.1 Introduction
- 2.2 Team Members & Responsibilities
3 Schedule
4 Parts List & Cost
5 Printed Circuit Board
6 CAN Communication
- 6.1 Hardware Design
- 6.2 DBC File
7 Sensor ECU
8 Motor ECU
9 Geographical Controller
10 Communication Bridge Controller & LCD
11 Master Module
12 Mobile Application
13 Conclusion

Project Title

Gran Turismo

Abstract

"The Gran Turismo" is an autonomous RC car designed to navigate to a specified destination using GPS coordinates, communicated via a mobile application. The car integrates four microcontrollers (Driver, Sensor/Bridge, Geo, and Motor nodes) which communicate over a Controller Area Network (CAN) bus. It utilizes FreeRTOS to manage periodic tasks for data gathering, processing, and decision-making, ensuring effective obstacle detection and avoidance while maintaining the intended path.

Introduction

The project was divided into 5 modules:

Sensor/Bridge node
Motor node
Geo node
Driver node
Android App

Team Members & Responsibilities

Team Members:

Daniel Zhao Yeung
Suryanto Phienanda
Kaijian Wu
Lianshi Gan

Gitlab Project Link - C243_GT

Team Members	Task Responsibility
Daniel Zhao Yeung	Geo Node
Lianshi Gan	Sensor Node
Suryanto Phienanda	Motor Node
Suryanto Phienanda	Driver Node
Kaijian Wu	Mobile App

Schedule

Week#	Start Date	End Date	Task	Status
1	03/04/2024	03/10/2024	Learn about the Busmaster and dbc. Connect db9 to Busmaster. Assign tasks to each team member.	Completed
2	03/11/2024	03/17/2024	Finish up RC Car Infrastructure. Get all the sensors and parts. Play with sensors and SJ2 boards.	Incomplete
3	03/18/2024	03/24/2024	Start working on dbc and mobile app. Integrate sensors with SJ2 boards. Get Data from different modules(GPS, Sensors). Starting to check on motor.	Incomplete
4	03/25/2024	03/31/2024	Develop LCD module. Start working on driver module. Build libraries for all modules (Bluetooth/WIFI, GPS, Sensor....). Continue work on mobile app.	Incomplete
5	04/01/2024	04/07/2024	PROTOTYPE 1 Build the car with all the modules. Create unit/integration tests. Continue work on mobile app.	Incomplete
6	04/08/2024	04/14/2024	Get the speed measuring sensor. Motors with PID control. Continue work on mobile app.	Incomplete
7	04/15/2024	04/21/2024	PROTOTYPE 2 Integrate bluetooth module Continue with mobile app	Incomplete
8	04/22/2024	04/28/2024	Finalize/Connect mobile app with RC car. Obstacle avoidance.	Incomplete
9	04/29/2024	05/05/2024	PROTOTYPE 3 Prepare for outdoor tests.	Incomplete
10	05/06/2024	05/12/2024	PROTOTYPE 4 Perform outdoors tests and recalibrate.	Incomplete
11	05/13/2024	05/19/2024	Final Demo	Incomplete

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

CAN Communication

Hardware Design

DBC File

Sensor ECU

Hardware Design

Ultrasonic Sensor

Selecting the appropriate distance sensor is crucial for the success of the project. Our team chose the Ultrasonic Sensor URM09 from DFRobots due to its ease of use and cost-effectiveness. The URM09 offers multiple communication protocols, and we opted for the I2C package to simplify the configuration and reading process, allowing us to focus on the overall system integration.

Ultra-Sonic Sensor URM09 (I2C Protocol)
- Supply Voltage: 3.3~5.5V DC
- Operating Current: 20mA
- Operating Temperature Range: -10℃～＋70℃
- Measurement Range: 2cm～500cm (can be set)
- Resolution: 1cm
- Accuracy: 1%
- Frequency: 50Hz Max
- Dimension: 47mm × 22 mm/1.85” × 0.87”

Software Design

Technical Challenges

Configure 4 ADC channels

We load the distance sensor data by ADC channel. There are only 3 channels ready to use on SJ2 board. Need to modify P0_26 as below to unlock ADC:

static void distance__configure_all_adc_pins(void) {
  LPC_IOCON->P0_25 &= ~(3 << 3);
  LPC_IOCON->P0_25 &= ~(1 << 7);

  LPC_IOCON->P0_26 &= ~(3 << 3);
  LPC_IOCON->P0_26 &= ~(1 << 16);
  LPC_IOCON->P0_26 &= ~(1 << 7);

  LPC_IOCON->P1_30 &= ~(3 << 3);
  LPC_IOCON->P1_30 &= ~(1 << 7);

  LPC_IOCON->P1_31 &= ~(3 << 3);
  LPC_IOCON->P1_31 &= ~(1 << 7);
}