Difference between revisions of "F19: Tower Defense in Space"
Proj user10 (talk | contribs) m (→INTRODUCTION AND OBJECTIVES) |
Proj user10 (talk | contribs) (→INTRODUCTION AND OBJECTIVES) |
||
Line 39: | Line 39: | ||
* [Ryan Zelek] | * [Ryan Zelek] | ||
| style="text-align: left;" | | | style="text-align: left;" | | ||
− | + | '''Team Lead'''<br /> | |
− | |||
− | |||
| style="text-align: left;" | | | style="text-align: left;" | | ||
− | * <span style="color:#FF8C00"></span> <br /> | + | * <span style="color:#FF8C00"></span>Game Design Lead<br /> |
− | |||
− | |||
|- | |- | ||
Line 52: | Line 48: | ||
* [Zach Smith] | * [Zach Smith] | ||
| style="text-align: left;" | | | style="text-align: left;" | | ||
+ | Git Repo Manager<br /> | ||
| style="text-align: left;" | | | style="text-align: left;" | | ||
− | * <span style="color:#EE82EE"></span> | + | * <span style="color:#EE82EE"></span>Hardware Design Lead<br /> |
− | |||
− | |||
|- | |- | ||
Line 62: | Line 57: | ||
* [Chong Hang Cheong] | * [Chong Hang Cheong] | ||
| style="text-align: left;" | | | style="text-align: left;" | | ||
− | + | Wiki Report Manager<br/> | |
− | |||
| style="text-align: left;" | | | style="text-align: left;" | | ||
− | * <span style="color:#008000"></span> | + | * <span style="color:#008000"></span>LED Matrix API<br /> |
− | |||
− | |||
|- | |- | ||
Line 74: | Line 66: | ||
* [Polin Chen] | * [Polin Chen] | ||
| style="text-align: left;" | | | style="text-align: left;" | | ||
+ | Bill of Materials Manager<br /> | ||
| style="text-align: left;" | | | style="text-align: left;" | | ||
* <span style="color:#008000"></span><br /> | * <span style="color:#008000"></span><br /> | ||
− | |||
− | |||
|} | |} |
Revision as of 02:49, 17 October 2019
Contents
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.
Project Title
Tower Defense ... In Space
ABSTRACT
My abstract goes here.
INTRODUCTION AND OBJECTIVES
TEAM MEMBERS & RESPONSIBILITIES | ||||
---|---|---|---|---|
Team Members |
Administrative Roles |
Technical Roles | ||
|
Team Lead |
| ||
|
Git Repo Manager |
| ||
|
Wiki Report Manager |
| ||
|
Bill of Materials Manager |
|
SCHEDULE
TEAM MEETING DATES & DELIVERABLES | ||||
---|---|---|---|---|
Week# |
Date Assigned |
Deliverables |
Status | |
1 | 10/15/19 |
|
| |
2 | 10/22/19 |
|
| |
3 | 10/29/19 |
|
| |
4 | 11/5/19 |
|
| |
5 | 11/12/19 |
|
| |
6 | 11/19/19 |
|
| |
7 | 11/26/19 |
|
| |
8 | 12/3/19 |
|
| |
9 | 12/10/19 |
|
|
BILL OF MATERIALS (GENERAL PARTS)
MAJOR COMPONENTS | ||||
---|---|---|---|---|
PART NAME |
PART MODEL & SOURCE |
QUANTITY |
COST PER UNIT (USD) | |
|
|
|
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
CONCLUSION
This pr