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

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎SCHEDULE)
m (→‎SCHEDULE)
Line 140: Line 140:
 
! scope="row"| 10/15/19
 
! scope="row"| 10/15/19
 
|  
 
|  
−
* Share team contact information<br\>
+
* Share team contact information<br>
−
* Create Git Repository<br\>
+
* Create Git Repository<br>
−
* Set up group Slack channel<br\>
+
* Set up group Slack channel<br>
−
* Invite Preet to Slack<br\>
+
* Invite Preet to Slack<br>
−
* Establish Code Guidelines and Standards<br\>
+
* Establish Code Guidelines and Standards<br>
 
|  
 
|  
 
* <span style="color:green">Complete</span> </br>
 
* <span style="color:green">Complete</span> </br>

Revision as of 02:47, 16 October 2019

Logo

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
  • 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
  • Create Git Repository
  • Set up group Slack channel
  • Invite Preet to Slack
  • Establish Code Guidelines and Standards
  • Complete </br>
  • Incomplete </br>
  • Complete </br>
  • Incomplete </br>
  • Complete </br>
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
  • 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

CONCLUSION

This pr


Project Video

Project Source Code

Advice for Future Students

Retrieved from "http://socialledge.com/sjsu/index.php?title=F19:_Tower_Defense_in_Space&oldid=56073"