Difference between revisions of "F19: Tower Defense in Space"

Revision as of 01:32, 16 October 2019 (view source) Proj user10 (talk | contribs) m (→‎MASTER CONTROLLER) ← Older edit		Revision as of 01:32, 16 October 2019 (view source) Proj user10 (talk | contribs) m (→‎MOTOR CONTROLLER) Newer edit →
Line 317:		Line 317:
	We used		We used
−
−	== <font color="EE82EE"> MOTOR CONTROLLER </font> ==
−
−
−	=== <font color="EE82EE"> Hardware Design </font> ===
−	The motor board
−	<b> <br>
−	1 pin  <br>
−	1 pin f <br>
−	1 pin  <br>
−	</b> <br>
−
−	The ESC was included with the RC we purchased and it was interfaced with 3 pins:
−	<b> <br>
−	1 pin fo <br>
−	</b> <br>
−
−	Manag <br>
−	<br>
−	Managing wheel spin was a more complicated process. The ESC also requires a PWM signal in order to operate, but is not as simple as the servo's operation. <br>
−	In or
−	<b><br>
−	S
−	</b><br>
−	<br>
−
−
−	===== <font color="EE82EE"> '''''Speed Control Timing Diagrams''''' </font> =====
−
−	[[File:Run DBC Speed timing diagrams.PNG |thumb| 600px|center| Speed Timing Diagrams]]
−
−
−	===== <font color="EE82EE"> '''''Steering Control Timing Diagrams''''' </font> =====
−
−	[[File:Run DBC Steering timing diagrams.PNG |thumb| 600px |center| Steering Timing Diagram]]
−
−
−	===== <font color="EE82EE"> '''''Motor Controller Schematic''''' </font> =====
−
−	[[File:RUN DBC motor sch.png |thumb| center | 800px | Motor Module Schematic]]
−
−	=== <font color="EE82EE"> Software Design </font>  ===
−	<br>
−	<b>Periodic Callback: Init (beginning of program)</b><br>
−	<br>
−	<b>Periodic Callback: 1Hz (every 1sec)</b><br>
−	- Che
−	<br>
−	<b>Periodic Callback: 10Hz (every 100ms)</b><br>
−	- Sen
−
−	=== <font color="EE82EE"> Technical Challenges </font>===
−
−	===== <font color="EE82EE"> '''''SJOne PWM''''' </font>=====
−	W
−
−
−	===== <font color="EE82EE"> '''''Encoder''''' </font>=====
−	The
−	=== <font color="EE82EE"> Bill Of Materials </font> ===
−	{| class="wikitable"
−	! colspan="5" style="background:#EE82EE;" |
−	<span style="color:#FFFFFF"> MOTOR CONTROLLER </span>
−	|-
−	! scope="col" style="text-align: center;" style="background:#C0C0C0;" |
−	<span style="color:#000000"> PART NAME </span>
−	! scope="col" style="text-align: center;" style="background:#C0C0C0;" |
−	<span style="color:#000000"> PART MODEL </span>
−	! scope="col" style="text-align: center;" style="background:#C0C0C0;" |
−	<span style="color:#000000"> QUANTITY </span>
−	! scope="col" style="text-align: center;" style="background:#C0C0C0;" |
−	<span style="color:#000000"> COST PER UNIT (USD) </span>
−	|-
−	|
−	* '''Motor Encoder'''
−	|
−	* [https://www.digikey.com/product-detail/en/nidec-copal-electronics/RE12D-100-201-1/563-2051-ND/6469487, Nidec Copal Optical Rotary Encoder]
−	|
−	* 1
−	|
−	* $63.16
−	|}
−
−	<HR>
−	<BR/>
	== <font color="FF0000"> SENSOR CONTROLLER </font> ==		== <font color="FF0000"> SENSOR CONTROLLER </font> ==

---

Revision as of 01:32, 16 October 2019

ABSTRACT

My abstract goes here.

INTRODUCTION AND OBJECTIVES

RC CAR OBJECTIVES

TEAM OBJECTIVES

CORE MODULES OF TOWER DEFENSE
LED Matrix User Input Game Logic Hardware

PROJECT MANAGEMENT ADMINISTRATION ROLES
Team Lead Finance Manager Git Repository Manager Wiki Report Manager Bill of Materials Manager

TEAM MEMBERS & RESPONSIBILITIES
Team Members	Administrative Roles	Technical Roles
[Ryan Zelek]	Team Lead a role
[Zach Smith]
[Chong Hang Cheong]
[Polin Chen]

SCHEDULE

TEAM MEETING DATES & DELIVERABLES
Week#	Date Assigned	Deliverables	Status
1	10/15/19	Share team contact information<br\> Create Git Repository<br\> Set up group Slack channel<br\> Invite Preet to Slack<br\> Establish Code Guidelines and Standards<br\>	Complete Incomplete Complete Incomplete Complete
2	10/22/19	Identify hardware components (BOM) Begin purchasing major items Finalize game architecture	Incomplete Incomplete Incomplete
3	10/29/19	Solidify individual roles and responsibilities Begin implementing basic code structure	Incomplete Incomplete
4	11/5/19	Interface the software with the hardware	Incomplete
5	11/12/19	First hardware design implementation complete	Incomplete
6	11/19/19	Complete first draft of individual subsystems PCB sent out for fabrication	Incomplete Incomplete
7	11/26/19	Integration of major subsystems	Incomplete
8	12/3/19	Testing and Validation	Incomplete
9	12/10/19	Reserve time for debugging issues Identify and fix critical bugs (hardware and software) Finish any optimizations and visualization features	Incomplete Incomplete Incomplete

BILL OF MATERIALS (GENERAL PARTS)

MICRO-CONTROLLERS
PART NAME	PART MODEL & SOURCE	QUANTITY	COST PER UNIT (USD)
32x64 RGB LED Matrix	[1]	2	$49.95

HARDWARE INTEGRATION PCB

Hardware Design

The hardware integration PCB was designed with two goals:

1. Minimize the footprint of the onboard electronics
2. Minimize the chances of wires disconnecting, during drives

To accomplish these goals,

The board consisted of n layers:

layer name

Technical Challenges

Design

• Balancing priorities between HW design and getting a working prototype

Assembly

• Wireless antenna connector on master board not accounted for in footprint, it may have to be removed to avoid interference with one connector.

Bill Of Materials

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

---

TEST

In order

Hardware Design

During

We used

SENSOR CONTROLLER

Hardware Design

Sen

Sensor Controller Schematic

CAD Design

We g

Placement for the Ultrasonic Sensors

We r

Sensor Value Conversion

In or

Software Design

Flowchart

The f

Timing Diagram

Technical Challenges

Sensor Interference

We saw :

• Higher

• Instead of l

Power Deficiency

At first

Unstable HR-04 Readings

At fi

ADC Supply Voltage

The mid

Slow car response to obstacle due to large queue size (running average)

During

Bill Of Materials

SENSOR CONTROLLER
PART NAME	PART MODEL	QUANTITY	COST PER UNIT (USD)
Infrared Sensor	Infrared Proximity Sensor	1	$13.95
Front-left-right Distance Sensor	MB1010, LV-MaxSonar-EZ1	2	$29.95
Front-middle Distance Sensor	MB1000, LV-MaxSonar-EZ0	1	$29.95

---

CONCLUSION

This pr

Project Video

RUN-D.B.C project video

Project Source Code

RUN-D.B.C project source code

Advice for Future Students

• FORM YOUR TEAM AS EARLY AS POSSIBLE AND START WORKING ON THE PROJECT AS EARLY AS POSSIBLE (WEEK 1 IF POSSIBLE)
• If you are