Difference between revisions of "F24: Rival Rush"
Proj user3 (talk | contribs) (→Team Members & Responsibilities) |
Proj user3 (talk | contribs) (→Schedule) |
||
Line 39: | Line 39: | ||
|- | |- | ||
! scope="row"| 1 | ! scope="row"| 1 | ||
− | | | + | | 10/14 |
| | | | ||
− | * To go through previous | + | * To go through previous projects and discuss with the team members. |
* To come up with new ideas for applications specific to FreeRTOS. | * To come up with new ideas for applications specific to FreeRTOS. | ||
| | | | ||
* Had a brainstorming session with the team and decided to do gaming projects using FreeRTOS. | * Had a brainstorming session with the team and decided to do gaming projects using FreeRTOS. | ||
− | |||
* Prepared the abstract for the project proposal. | * Prepared the abstract for the project proposal. | ||
|- | |- | ||
! scope="row"| 2 | ! scope="row"| 2 | ||
− | | | + | | 10/21 |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
| | | | ||
* To decide the structure of the team and divide the project into different modules. | * To decide the structure of the team and divide the project into different modules. | ||
Line 68: | Line 57: | ||
* Assigned roles and responsibilities to each member. | * Assigned roles and responsibilities to each member. | ||
* Created a test plan with tasks, deadlines and deliverables assigned to it. | * Created a test plan with tasks, deadlines and deliverables assigned to it. | ||
+ | |- | ||
+ | ! scope="row"| 3 | ||
+ | | 10/28 | ||
+ | | | ||
+ | * To implement player module logic to send orientation data to the Master module. | ||
+ | * To start designing the Master module which will take inputs from different players, take a decision and sends it to LED Matrix display. | ||
+ | | | ||
+ | * Divided the project into different modules like Master, Player, Wireless, LED Display, PCB, and Testing. | ||
|- | |- | ||
! scope="row"| 4 | ! scope="row"| 4 | ||
− | | | + | | 11/04 |
| | | | ||
− | * To | + | * To understand the high-level APIs for the Wireless nordic node. |
− | * To | + | * To understand the connections, read the datasheet for RGB LED Matrix. |
| | | | ||
− | * | + | * Assigned roles and responsibilities to each member. |
+ | * Created a test plan with tasks, deadlines and deliverables assigned to it and ordered all the components. | ||
|- | |- | ||
! scope="row"| 5 | ! scope="row"| 5 | ||
− | | | + | | 11/11 |
| | | | ||
− | |||
− | |||
− | |||
− | |||
* To install Eagle software for PCB design and get accustomed to the basic functions. | * To install Eagle software for PCB design and get accustomed to the basic functions. | ||
| | | | ||
Line 93: | Line 87: | ||
|- | |- | ||
! scope="row"| 6 | ! scope="row"| 6 | ||
− | | | + | | 11/18 |
| | | | ||
* To test the Player and Master modules. | * To test the Player and Master modules. | ||
Line 104: | Line 98: | ||
|- | |- | ||
! scope="row"| 7 | ! scope="row"| 7 | ||
− | | | + | | 11/25 |
| | | | ||
* Integrate Player and Master modules and make necessary changes as per other module requirements. | * Integrate Player and Master modules and make necessary changes as per other module requirements. | ||
Line 113: | Line 107: | ||
|- | |- | ||
! scope="row"| 8 | ! scope="row"| 8 | ||
− | | | + | | 12/02 |
| | | | ||
* To send and receive data between Player and Master using Wireless protocol. | * To send and receive data between Player and Master using Wireless protocol. | ||
Line 125: | Line 119: | ||
|- | |- | ||
! scope="row"| 9 | ! scope="row"| 9 | ||
− | | | + | | 12/09 |
| | | | ||
* To implement RGB LED Matrix tasks and APIs for the Master module. | * To implement RGB LED Matrix tasks and APIs for the Master module. | ||
Line 139: | Line 133: | ||
|- | |- | ||
! scope="row"| 10 | ! scope="row"| 10 | ||
− | | | + | | 12/16 |
| | | | ||
* To keep moving the display down continuously for the car race track. | * To keep moving the display down continuously for the car race track. |
Revision as of 09:10, 4 November 2024
Contents
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
Rival Rush
Abstract
This is a 2 player game that would be implemented on a 64*64 RGB LED. Each player has to move against the oncoming traffic without being hit by any of the vehicles. The players can move left or right horizontally across the highway by tilting the player consoles (SJ2 boards). The movement across the road by tilting is sensed by an accelerometer. The players will have 3 lives each of which is deducted per hit. The players can also collect coins on the road which add to their score. The number and speed of the approaching traffic will increase over time. The player with a greater score at the end of 60 seconds will win the game. The LED will display the players’ scores, number of lives left and the racing track on either side.
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
- Alshama Mony Sheena
- Harshwardhan Ashish Bhangale
- Gautam Santhanu Thampy
Schedule
Week# | Date | Task | Status |
---|---|---|---|
1 | 10/14 |
|
|
2 | 10/21 |
|
|
3 | 10/28 |
|
|
4 | 11/04 |
|
|
5 | 11/11 |
|
|
6 | 11/18 |
|
|
7 | 11/25 |
|
|
8 | 12/02 |
|
|
9 | 12/09 |
|
|
10 | 12/16 |
|
|
11 | 05/13 |
|
|
12 | 05/20 |
|
|
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.