Difference between revisions of "S19: Hot Wheels"

Revision as of 23:58, 11 May 2019 (view source) Proj user13 (talk | contribs) (→‎DC Motor) ← Older edit		Revision as of 03:37, 12 May 2019 (view source) Proj user13 (talk | contribs) (→‎Project Title) Newer edit →
Line 1:		Line 1:
	== Project Title ==		== Project Title ==
−	<Team Name>	+	Self-navigating RC car using CAN communication.
	== Abstract ==		== Abstract ==

---

Revision as of 03:37, 12 May 2019

Project Title

Self-navigating RC car using CAN communication.

Abstract

In the HOT WHEELS project, we plan to design and construct an autonomously navigating, electric R.C car which uses CAN bus for internal communication and an android app for selecting car destination. Development of the R.C car's subsystem modules will be divided amongst the eight team members.

Introduction

The project was divided into N modules:

• Sensor ...
• Motor..
• ...
• Android

Team Members & Responsibilities

<Team Picture>

Gitlab Project Link - [1]

<Provide ECU names and members responsible> <One member may participate in more than one ECU>

• Master Control
  • Kailash Chakravarty

• Sensor
  • Rishabh Sheth

• Motor
  • Kriti Hedau
  • Tahir Rawn

• Geographical
  • Harmeen Joshi
  • Nandini Shankar

• Communication Bridge Controller & Android Application
  • Swanand Sapre
  • Aquib Mulani

• Code Review & Commit Approvers
  • Rishabh Sheth
  • Nandini Shankar
  • Kailash Chakravarty

Schedule

Week#	Date	Task	Status	Completion Date
1	02/12/19	Form Teams	Completed	02/12/19
2	02/17/19	Setup a Slack workspace for the team. Setup private channel on Slack workspace	Completed Completed	02/17/19 02/17/19
3	02/26/19	Create a Gitlab project and add all team members as well as Preet Order CAN transcievers All team members get familiar with the Gitlab environment and make their initial commit.	Completed Completed Completed	02/26/19 02/26/19 02/26/19
4	03/05/19	Research previous projects wiki page and gather useful information. Identify and discuss individual modules within the project and finalize roles of each team member. Demo CAN Communication	Completed Completed Completed	03/07/19 03/07/19 03/07/19
5	03/12/19	Each team member review their corresponding module hardware requirements. Study data sheets of sensors used in each module. Pick PCB design platform and begin work on PCB design/schematic.	In-Progress In-Progress Not Started
6	03/19/19	Finish ordering required components. Finalize PCB design/order by end of week. Each team member start work on implementing individually working modules.	Not Started Not Started Not Started
7	03/26/19	Demo a "Hello World" program implementation by each module. Study android app development environment. Start implementing android app.	Not Started Not Started Not Started
8	04/02/19	--- SPRING BREAK ---
9	04/09/19	Demo Android app basic prototype	Not Started
10	04/16/19	Finish implementing individual working modules.	Not Started
11	04/23/19	Work on integrating individual modules into the final testing. Identify test cases for the integrated prototype model. Start integration testing.	Not Started Not Started Not Started
12	04/30/19	Finish integration testing. Finalize Wiki page documentation.	Not Started Not Started
13	05/07/19	--- BUFFER WEEK ---
14	05/14/19	Final Exam Preparation
15	05/22/19	Final Demo

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

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 [3]

VERSION "0.1.0"

BU_: MASTER SENSOR MOTORIO GEO APP

BO_ 220 MOTORIO_CMD: 4 MASTER

SG_ MOTORIO_CMD_Direction : 0|8@1+ (1,0) [0|2] "" MOTORIO

BO_ 210 ULTRA_CMD: 4 SENSOR

SG_ SENSOR_SONARS_FrontDistance : 0|8@1+ (1,0) [2|100] "" MASTER

BO_ 250 DISTANCE: 4 GEO

SG_ DISTANCE_FinalDistance : 0|16@1+ (0.1,0) [0|0] "" MASTER

BO_ 102 BLUETOOTH: 4 APP

SG_ DISTANCE_FinalDistance : 0|16@1+ (0.1,0) [0|0] "" MASTER

CM_ BU_ MASTER "The Master controller of the car";

CM_ BU_ MOTOR "The motor controller of the car";

CM_ BU_ SENSOR "The sensor controller of the car";

CM_ BU_ GEO "The Geo controller of the car";

CM_ BU_ APP "The Bluetooth/App controller of the car";

---

Sensor ECU

<Picture and link to Gitlab>

MOTOR CONTROLLER

Group Members

• Tahir Rawn
  
• Kriti Hedau
  

Design & Implementation

Hardware Design

	SJOne Pin Diagram
Sr.No	Pin Number	Pin Function
1	P0.0	CAN RX
2	P0.1	CAN TX
3	P2.0	Servo motor
4	P2.1	DC motor
5	P2.5	Speed Encoder

• Hardware Specifications

DC Motor

Servo Motor

RPM Sensor

Hardware Interface

Software Design

Technical Challenges

Future Counsel

---

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>

---

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