Difference between revisions of "S19: Run D.B.C"

Revision as of 23:59, 17 March 2019 (view source) Proj user10 (talk | contribs) ← Older edit		Revision as of 00:00, 18 March 2019 (view source) Proj user10 (talk | contribs) Newer edit →
Line 714:		Line 714:
	<BR/>		<BR/>
−	== <font color="696969"> Hardware Integration Printed Circuit Board (PCB) </font> ==	+	== <font color="696969"> HARDWARE INTEGRATION PRINTED CIRCUIT BOARD (PCB) </font> ==
	<Picture and information, including links to your PCB>		<Picture and information, including links to your PCB>
Line 720:		Line 720:
−	== Sensor Controller ==	+	== SENSOR CONTROLLER ==
	<Picture and link to Gitlab>		<Picture and link to Gitlab>
Line 738:		Line 738:
	<BR/>		<BR/>
−	== Motor ECU ==	+	== MOTOR CONTROLLER ==
	<Picture and link to Gitlab>		<Picture and link to Gitlab>
Line 757:		Line 757:
−	== Master Module ==	+	== MASTER CONTROLLER ==
	<Picture and link to Gitlab>		<Picture and link to Gitlab>

---

Revision as of 00:00, 18 March 2019

Abstract

The RUN-D.B.C project, involves the design and construction of an autonomously navigating RC car. Development of the R.C car's subsystem modules will be divided amongst and performed by seven team members. Each team member will lead or significantly contribute to the development of at least one subsystem.

Objectives & Introduction

RC CAR OBJECTIVES
Successfully detect and avoid obstacles Autonomously navigate to a fixed destination, from a fixed starting location; based on feedback from a GPS Integrate communication between the RC car's master controller and an Android device, using Bluetooth Integrate system hardware communication using a PCB

TEAM OBJECTIVES
Strive to learn as much as possible, in order to develop a professional product Establish and enforce professional software design standards Establish and enforce professional hardware design standards Achieve 100% code coverage, during unit testing Carefully document and track all bugs encountered and patched, during development Clearly communicate the development of all modules of the RC car

CORE MODULES OF RC CAR
Android App Bridge Controller Geographic Controller Master Controller Motor Controller Sensor Controller Hardware Integration PCB Wiring Harness

PROJECT MANAGEMENT ADMINISTRATION ROLES
Team Lead Finance Manager Git Repository Manager Wiki Report Manager Gantt Chart Manager Bill of Materials Manager Project Presentation Manager

TEAM MEMBERS AND RESPONSIBILITIES
Team Members	Administrative Roles	Technical Roles
Tristan French	Team Lead Git Repository Manager Finance Manager	Master Controller (Lead) Hardware Integration PCB Wiring Harness
Ryan Zelek		Testing and Integration (Lead) Master Controller Motor Controller
Samir Mohammed	Wiki Report Manager Gantt Chart Manager Bill of Materials Manager	Android App and Bridge Controller (Lead) Hardware Integration PCB Wiring Harness
Vignesh Kumar Venkateshwar	Project Presentation Manager	Motor Controller (Lead) Android App and Bridge Controller
Bharath Vyas Balasubramanyam		Geographic Controller (Lead) Motor Controller
Nuoya Xie		Sensor Controller (Lead) Geographic Controller
Kelvin Cheong		Sensor Controller Geographic Controller

Schedule

TEAM MEETING DATES AND DELIVERABLES
Week#	Date Assigned	Deliverables	Status	Date Completed
1	2/16/19	Share team contact information Create Git Repository (Tristan) Set up Slack Invite Preet to Slack Establish Code Guidelines and Standards	Complete Complete Complete Complete Complete
2	2/24/19	(1/2 team) Share research of past projects Establish ownership of Administrative and Technical Project Modules Establish weekly team meeting time Establish Team Slack usage Guidelines and Standards Received CAN Transceivers Create a Gantt chart to track project progress (Samir) Create Git directory structure (Tristan) Create a Bill of Materials (Samir) Select and order an RC car (Bharath) Push a file to Git Repository Conduct research of project modules (based on ownership/sub-team) Invite Preet to Gitlab	Complete Complete Complete Complete Complete In Progress Complete Complete Complete Complete Complete Complete
3	3/3/19	(2/2 team) Share research of past projects Explore using Splitwise for managing project finances Explore using Taiga.io for project management (Samir/Tristan) Sub-teams share research and findings with each other and the team Start planning what parts need to be ordered and update BoM Email Preet regarding LCD screen for Bridge Controller Interface with the HC05 Bluetooth module Research frameworks for Android App development Research GPS modules Create a high-level system block diagram and control scheme Develop a high-level plan interfacing with speed controller and servo controller Select a PCB design tool (develop a sample board in KiCAD) Test performance/specs of current Ultrasonic sensors and research others	Complete Complete Not Started Complete In Progress In Progress In Progress In Progress In Progress In Progress In Progress In Progress In Progress
4	3/10/19	Each team create a schedule for sub-system development and send to Samir Set up Cygwin on Windows (and configure) Mac machines for auto-formatting Finalize and purchase LCD screen for Bridge Controller Learn to develop in Android Studio (watch tutorials and begin developing Android App) Purchase Adafruit Ultimate GPS module Selected KiCad as PCB design tool (develop sample PCB to help learn how to use software) Purchase long-range distance sensors and select bump sensors
5	3/17/19
6	3/24/19	Interface with with speed controller and servo controller Finalize high-level system block diagram and control scheme
7	3/31/19	All parts have been ordered LPC 1758 responds to feedback from bump sensor LPC 1758 responds to feedback from Ultrasonic sensors (reports distance of objects in their detection radius) Complete DBC CAN message format LPC 1758 responds to feedback from motor speed sensor (reports RPM of wheels, when a PWM signal is applied) Complete DBC CAN message format
8	4/7/19	Complete sensor module code and push final revision to GitLab
9	4/14/19	All modules have been fully assembled
10	4/21/19
11	4/28/19
12	5/5/19	RC car has been fully assembled and modules have been integrated
13	5/12/19
14	5/22/19	DEMO

Parts List & Cost

MICRO-CONTROLLERS
PART NAME	PART MODEL AND SOURCE	QUANTITY	COST PER UNIT (USD)
Micro-controller	LPC 1758 (Supplied by Preet Kang)	5	$80.00

RC CAR
PART NAME	PART MODEL AND SOURCE	QUANTITY	COST PER UNIT (USD)
RC Car	Traxxas 1/10 Slash 2WD RTR with 2.4GHz Radio	1	$205.99
Lithium-Ion Battery	Traxxas 7600mAh 7.4V 2-Cell 25C LiPo Battery	1	$74.95
Battery Charger	Traxxas 2970 EZ-Peak Plus 4-Amp NiMH/LiPo Fast Charger with iD Auto Battery Identification	1	$47.95

ANDROID APP AND BRIDGE CONTROLLER
PART NAME	PART MODEL	QUANTITY	COST PER UNIT (USD)
Bluetooth Serial Communication Module	LeaningTech HC-05 Module Bluetooth Serial Pass-Through Module Wireless Serial Communication with Button for Arduino (Supplied by Nouya Xie)	1	N/A

GEOGRAPHIC CONTROLLER
PART NAME	PART MODEL	QUANTITY	COST PER UNIT (USD)

MASTER CONTROLLER
PART NAME	PART MODEL	QUANTITY	COST PER UNIT (USD)

MOTOR CONTROLLER
PART NAME	PART MODEL	QUANTITY	COST PER UNIT (USD)

HARDWARE INTEGRATION PCB AND WIRING HARNESS
PART NAME	PART MODEL	QUANTITY	COST PER UNIT (USD)

SENSOR CONTROLLER
PART NAME	PART MODEL	QUANTITY	COST PER UNIT (USD)

ANDROID 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>

Bug Tracking

<Problem Summary> <Problem Resolution>

---

(WIRELESS COMMUNICATION) BRIDGE CONTROLLER AND LCD 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>

Bug Tracking

<Problem Summary> <Problem Resolution>

---

GEOGRAPHIC 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>

Bug Tracking

<Problem Summary> <Problem Resolution>

---

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>

---

HARDWARE INTEGRATION PRINTED CIRCUIT BOARD (PCB)

<Picture and information, including links to your PCB>

SENSOR 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>

Bug Tracking

<Problem Summary> <Problem Resolution>

---

MOTOR 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>

Bug Tracking

<Problem Summary> <Problem Resolution>

---

MASTER 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>

Bug Tracking

<Problem Summary> <Problem Resolution>

---

Conclusion

<Organized summary of the project>

<What did you learn?>

Project Video

Project Source Code

Advice for Future Students

<Bullet points and discussion>

Grading Criteria

• How well is Software & Hardware Design described?
• How well can this report be used to reproduce this project?
• Code Quality
• Overall Report Quality:
  • Software Block Diagrams
  • Hardware Block Diagrams

    Schematic Quality

  • Quality of technical challenges and solutions adopted.