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

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎SCHEDULE)
(→‎SCHEDULE)
Line 165: Line 165:
 
|  
 
|  
 
* Integration of major subsystems<br/>
 
* Integration of major subsystems<br/>
 +
* Game should be running with LED matrix interaction<br/>
 
|
 
|
 +
* <span style="color:red">Incomplete</span> <br />
 
* <span style="color:red">Incomplete</span> <br />
 
* <span style="color:red">Incomplete</span> <br />
  

Revision as of 04:19, 8 November 2019

Logo

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

  • [Ryan Zelek]

Team Lead
  • Game Design Lead
  • [Zach Smith]

Git Repo Manager
  • Hardware Design Lead
  • [Chong Hang Cheong]

Wiki Report Manager
  • LED Matrix API
  • [Polin Chen]

Bill of Materials Manager


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
  • Incomplete
  • Complete
  • Complete
  • Complete
2 10/22/19
  • Identify major hardware components (BOM)
  • Begin purchasing major items
  • Finalize game architecture
  • Have Git Repo Setup
  • Complete
  • Complete
  • Complete
  • Incomplete
3 10/29/19
  • Solidify individual roles and responsibilities
  • Begin implementing basic code structure
  • Complete
  • Incomplete
4 11/5/19
  • Interface the software with the hardware
  • Incomplete
5 11/12/19
  • First hardware design implementation complete
  • Polin: Have APIs ready for joystick and buttons
  • Ryan: Have basic user interface for the game displayed through serial port
  • Kelvin: Find out feasibility of creating an LED matrix driver in C
  • Incomplete
  • Incomplete
  • Incomplete
  • 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
  • Game should be running with LED matrix interaction
  • Incomplete
  • Incomplete
8 12/3/19
  • Testing and Validation: does the game run without crashing/errors?
  • 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)

MAJOR COMPONENTS

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=56238"