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

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎SCHEDULE)
(→‎SCHEDULE)
Line 195: Line 195:
 
* Game should be running with LED matrix display involvement<br/>
 
* Game should be running with LED matrix display involvement<br/>
 
'''Zach'''
 
'''Zach'''
−
* PCB should be assembled<br/>
+
* PCB assembled and tested. Problems identified and solutions proposed.<br/>
 
|
 
|
 
<br/>
 
<br/>
Line 211: Line 211:
 
! scope="row"| 12/3/19
 
! scope="row"| 12/3/19
 
|  
 
|  
−
* Testing and Validation: does the game run without crashing/errors?<br/>
+
* Complete game testing and validation<br/>
 +
* Critical bugs (software AND hardware) identified and a clear path towards closure has been identified<br/>
 
|
 
|
 +
* <span style="color:red">Incomplete</span> <br />
 
* <span style="color:red">Incomplete</span> <br />
 
* <span style="color:red">Incomplete</span> <br />
  
Line 218: Line 220:
 
! scope="row"| 9
 
! scope="row"| 9
 
! scope="row"| 12/10/19
 
! scope="row"| 12/10/19
−
|
 
−
* Reserve time for debugging issues<br/>
 
−
* Identify and fix critical bugs (hardware and software)<br/>
 
−
* Finish any optimizations and visualization features<br/>
 
 
|
 
|
−
* <span style="color:red">Incomplete</span> <br />
+
* Continuation of previous week activities (bug fixes, etc)
 +
* Implement any potential optimizations and/or expansions
 +
|
 
* <span style="color:red">Incomplete</span> <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 05:36, 9 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
  • Establish baseline software architecture design and guidelines going forward
  • Complete
  • Complete
4 11/5/19

Kelvin

  • Verify functionality of LED matrix and gather resources for further understanding


  • Complete
5 11/12/19

Kelvin

  • Find out feasibility of creating an LED matrix driver in C

Polin

  • Have APIs ready for joystick and buttons

Ryan

  • Have basic user interface for the game displayed through serial port

Zach

  • First controller PCB design complete
  • Specify any remaining hardware components and coordinate purchase


  • Incomplete


  • Incomplete


  • Incomplete


  • Incomplete
  • Incomplete
6 11/19/19

Kelvin

  • Complete baseline API for LED matrix

Polin

  • Determine feasibility of MP3 decoding and integration into system

Ryan

  • Complete first pass at basic tower defense level with straight pathway

Zach

  • Controller PCB sent out for fabrication


  • Incomplete


  • Incomplete


  • Incomplete


  • Incomplete
7 11/26/19

Kelvin

  • LED matrix driver should be reviewed and complete

Polin

  • Work with Zach to identify remaining hardware components and, if applicable, MP3 decoder requirements

Ryan

  • Work with Kelvin to integrate his API into the game
  • Game should be running with LED matrix display involvement

Zach

  • PCB assembled and tested. Problems identified and solutions proposed.


  • Incomplete


  • Incomplete


  • Incomplete
  • Incomplete


  • Incomplete
8 12/3/19
  • Complete game testing and validation
  • Critical bugs (software AND hardware) identified and a clear path towards closure has been identified
  • Incomplete
  • Incomplete
9 12/10/19
  • Continuation of previous week activities (bug fixes, etc)
  • Implement any potential optimizations and/or expansions
  • 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=56270"