Difference between revisions of "F20: Flappy"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Schedule)
(Schedule)
Line 39: Line 39:
 
| 10/13
 
| 10/13
 
|
 
|
* Flappy project proposal approved by instructor.  
+
* Flappy project proposal approved by the instructor.  
 
|
 
|
 
* <span style="color:green"> Completed </span>
 
* <span style="color:green"> Completed </span>
Line 46: Line 46:
 
| 10/20
 
| 10/20
 
|
 
|
* Order project parts
+
* Order LED Matrix
 
* Create GitLab repository
 
* Create GitLab repository
 
|
 
|
Line 55: Line 55:
 
| 10/27
 
| 10/27
 
|
 
|
* Received and Review All relevant Parts
+
* Received LED Matrix
* Assign Module Integration for 3 members
+
* Order Sound board
* PCB Design Process Start
+
* Overall Game-machine design
 
|
 
|
 
* <span style="color:green"> Completed </span>
 
* <span style="color:green"> Completed </span>
 
* <span style="color:green"> Completed </span>
 
* <span style="color:green"> Completed </span>
* <span style="color:blue"> In Progress </span>
+
* <span style="color:green"> Completed </span>
 
|-
 
|-
 
! scope="row"| 4
 
! scope="row"| 4
 
| 11/3
 
| 11/3
 
|
 
|
* Screen Driver - Display Text/Image
+
* Order Button
* Sound Board ordering
+
* Game-machine Design
 
* Game Logic - Basic High-level Game design
 
* Game Logic - Basic High-level Game design
 
|
 
|
* <span style="color:yellow"> Move to next week </span>
+
* <span style="color:green"> Completed </span>
* <span style="color:blue"> In Progress </span>
+
* <span style="color:green"> Completed </span>
 
* <span style="color:blue"> In Progress </span>
 
* <span style="color:blue"> In Progress </span>
 
|-
 
|-
Line 78: Line 78:
 
|
 
|
 
* Screen Driver - Basic Display
 
* Screen Driver - Basic Display
* Game Logic - All Game Basic Functionality implemented
+
* Game Logic - Bird location
* System Design - Integrate Game - Screen - Sound
+
* Game Logic - Poles location
 
|
 
|
 
* <span style="color:blue"> In Progress </span>
 
* <span style="color:blue"> In Progress </span>
Line 88: Line 88:
 
| 11/17
 
| 11/17
 
|
 
|
* Integrate all game parts
+
* Soundboards Receive
* Rough Draft Report
+
* Button Receive
* Update Wiki Page
+
* Soundboards interface
 +
* Button interface
 +
* PCB design
 +
* Packaging design
 
|
 
|
 
Coming Soon!  
 
Coming Soon!  
Line 97: Line 100:
 
| 11/24
 
| 11/24
 
|
 
|
* Packaging Logistic
+
* Integrate basic parts
* Integrate Big Button
 
 
* Integrate Bonus Game Round
 
* Integrate Bonus Game Round
* Make a one-piece case
+
* Order PCB board
 +
* Game case 3D print
 
|
 
|
Coming Soon!  
+
<span style="color:brown"> Coming Soon! </span>
 
|-
 
|-
 
! scope="row"| 8
 
! scope="row"| 8
Line 111: Line 114:
 
* Final Wiki Page Update
 
* Final Wiki Page Update
 
|
 
|
Coming Soon!  
+
<span style="color:brown"> Coming Soon! </span>
 
|-
 
|-
 
! scope="row"| 9
 
! scope="row"| 9
Line 119: Line 122:
 
* User Testing - Letting Strangers play
 
* User Testing - Letting Strangers play
 
|
 
|
Coming Soon!  
+
<span style="color:brown"> Coming Soon! </span>
 
|-
 
|-
 
! scope="row"| 10
 
! scope="row"| 10
Line 127: Line 130:
 
* Final Project Demo
 
* Final Project Demo
 
|
 
|
Coming Soon!  
+
<span style="color:brown"> Coming Soon! </span>
 
|}
 
|}
  

Revision as of 01:43, 11 November 2020

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

Flappy Wings

Abstract

This section should be a couple lines to describe what your project does.

Objectives & Introduction

Show list of your objectives. This section includes the high level details of your project. You can write about the various sensors or peripherals you used to get your project completed.

Team Members & Responsibilities

  • Huy Nguyen
  • Michael Wang
  • Brian Tran

Schedule

Week Date Task Status
1 10/13
  • Flappy project proposal approved by the instructor.
  • Completed
2 10/20
  • Order LED Matrix
  • Create GitLab repository
  • Completed
  • Completed
3 10/27
  • Received LED Matrix
  • Order Sound board
  • Overall Game-machine design
  • Completed
  • Completed
  • Completed
4 11/3
  • Order Button
  • Game-machine Design
  • Game Logic - Basic High-level Game design
  • Completed
  • Completed
  • In Progress
5 11/10
  • Screen Driver - Basic Display
  • Game Logic - Bird location
  • Game Logic - Poles location
  • In Progress
  • In Progress
  • In Progress
6 11/17
  • Soundboards Receive
  • Button Receive
  • Soundboards interface
  • Button interface
  • PCB design
  • Packaging design

Coming Soon!

7 11/24
  • Integrate basic parts
  • Integrate Bonus Game Round
  • Order PCB board
  • Game case 3D print

Coming Soon!

8 12/1
  • Final Testing
  • Final Report
  • Final Wiki Page Update

Coming Soon!

9 12/8
  • Reliability Testing
  • User Testing - Letting Strangers play

Coming Soon!

10 12/16
  • Complete Wiki Report
  • Final Project Demo

Coming Soon!

Parts List & Cost

Give a simple list of the cost of your project broken down by components. Do not write long stories here.

Design & Implementation

The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.

Hardware Design

Discuss your hardware design here. Show detailed schematics, and the interface here.

Hardware Interface

In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high level workings rather than inner working of your project.

Software Design

Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.

Implementation

This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.

Testing & Technical Challenges

Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.

Include sub-sections that list out a problem and solution, such as:

<Bug/issue name>

Discuss the issue and resolution.

Conclusion

Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?

Project Video

Upload a video of your project and post the link here.

Project Source Code

References

Acknowledgement

Any acknowledgement that you may wish to provide can be included here.

References Used

List any references used in project.

Appendix

You can list the references you used.