Difference between revisions of "S18: Death Race"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Introduction)
(→‎Schedule)
Line 142: Line 142:
 
|
 
|
 
|-
 
|-
−
! scope="row"| 9
+
! scope="row"| 10
 
| 04/22
 
| 04/22
 
|  
 
|  
Line 148: Line 148:
 
|
 
|
 
|-
 
|-
−
! scope="row"| 9
+
! scope="row"| 11
 
| 04/22
 
| 04/22
 
|  
 
|  

Revision as of 01:23, 18 April 2018

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

Death Race - A car racing game using FreeRTOS

Git Link - [1]
Git Users:

  • hemant.banjara
  • rahuldevaragudde
  • rajvisharia
  • snehashahi
  • supradeepk6

Abstract

Real-time adaptation of computer games can content the users’ abilities, skills and also enhance the players' engagement and immersion. We are planning to design a car racing video game between two players.There will be two tracks for each player and the player can shift between the two tracks. The players will change the track (on RGB LED Matrix Display) by tilting the SJone board.The players will get two kinds of obstacles, squares and circles.They gain points if they catch circles and lose the game if they hit the squares.The obstacles are generated at random and the toughness increases with time.The game UI will have user options like - indication for players connectivity, start and quit game.Individual player score will be displayed on LCD display

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.

Introduction

The project was divided into 4 main modules:

1) Player Module: Two SJOne boards simultaneously sending accelerometer data to the Master Board via Nordic wireless.

2) Wireless: Communication bridge between the player module and the Master module.

3) Master Module:

4) Display Module:

Objectives

1) ...


Team Members & Responsibilities

Schedule

Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.

}

Parts List & Cost

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

Week# Date Task Status
1 03/04
  • To decide the project idea
  • Brainstorming on different project ideas and finalized video game idea
2 03/11
  • To decide the project hardware
  • Decided the project hardware
3 03/18
  • To decide the structure of team, deadline, and deliverables
  • Finalised the structure of team and deadline date
4 03/25
  • To setup the gitlab project
  • Done
5 04/01
  • To implement the Player code logic
  • Test player logic

Implemented,tested and pushed the code to git

6 04/08

To implement Master logic

  • Implemented Master logic using uart
7 04/15
  • To test the master logic with player logic using uart
  • Tested the master logic with 2 player using uart
8 04/22

To implement the master logic with nordic wireles

9 04/22

To the master logic with nordic wireles

10 04/22

To the master logic with nordic wireles

11 04/22

To the master logic with nordic wireles

Item# Part Desciption Vendor Qty Cost
1 SJOne Boards From Preet 3 $240.00
2 64x64 RGB LED Matrix Adafruit 1 $92.00
3 Bonnet Adafruit 1 $
4 $
5 $
6 $
7 $
8 $
9 $
10 $
11 $

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.

Retrieved from "http://socialledge.com/sjsu/index.php?title=S18:_Death_Race&oldid=44375"