F24: Survival Dodge - Revision history

Proj user10: /* Project Source Code */

2024-12-22T22:16:47Z

‎Project Source Code

Proj user10: /* Design & Implementation */

2024-12-22T22:10:40Z

‎Design & Implementation

Proj user10: /* Software Design */

2024-12-22T22:09:45Z

‎Software Design

Proj user10: /* Implementation */

2024-12-22T21:59:01Z

‎Implementation

Proj user10: /* Team Members & Responsibilities */

2024-12-22T21:43:03Z

‎Team Members & Responsibilities

Proj user10: /* Testing & Technical Challenges */

2024-12-22T21:42:36Z

‎Testing & Technical Challenges

Proj user10: /* Testing & Technical Challenges */

2024-12-22T21:42:00Z

‎Testing & Technical Challenges

Proj user10: /* */

2024-12-22T21:38:25Z

‎

Proj user10: /* References Used */

2024-12-22T21:29:41Z

‎References Used

Proj user10: /* Team Members & Responsibilities = */

2024-12-22T21:28:59Z

‎Team Members & Responsibilities =

@@ Line 422: / Line 422: @@
 === Project Source Code ===
-https://gitlab.com/chandrasekhar2499/sjtwo-c/-/tree/test?ref_type=heads
+https://gitlab.com/sivaprasad6132/240/-/tree/survival_dodge?ref_type=heads
 == References ==

@@ Line 267: / Line 267: @@
 == Design & Implementation ==
 '''LED Matrix Display:'''
@@ Line 365: / Line 367: @@
 |}
 === Software Design ===

@@ Line 369: / Line 369: @@
 === 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 ===

← Older revision		Revision as of 21:59, 22 December 2024
Line 372:		Line 372:

	=== Implementation ===		=== Implementation ===
		+
		+	Game Logic State Machine
		+	The game logic follows a state machine with multiple states. Below is a detailed flow of states.
		+
		+	START_SCREEN: Initially, the game is in the START_SCREEN state. Pressing any button during this state transitions the game to the GAME_START state.
		+
		+	GAME_START: This state activates the gameplay screen where the game officially begins. The player's score starts from zero. The player can move around to avoid obstacles. If the player touches an obstacle, the game moves to the UPDATE_LIVES state. If no button is pressed, it remains in this state until an obstacle is encountered or the timer runs out.
		+
		+	UPDATE_LIVES: In this state, the player’s lives are decremented due to a collision with an obstacle. If the player has remaining lives, the game returns to the GAME_START state to continue playing. If no lives remain, the game transitions to the GAME_OVER state.
		+
		+	GAME_OVER: This state is triggered when the player's lives are depleted or the game timer reaches zero. The gameplay stops, and the game over screen is displayed along with the final score. From here, pressing the start button restarts the game, sending it back to the START_SCREEN state.

	== '''Game Logic''' ==		== '''Game Logic''' ==

← Older revision		Revision as of 21:43, 22 December 2024
Line 34:		Line 34:

	== Team Members & Responsibilities ==		== Team Members & Responsibilities ==
−	* Uday Kumar Reddy Pesala
−
−	* Chandra Sekhar Naidu Gorle
−
−	* Adi Siva Prasad Reddy Korivi
−

	==== Chandra Sekhar====		==== Chandra Sekhar====

@@ Line 402: / Line 402: @@
 == Testing & Technical Challenges ==
-Problem: The LED matrix display was experiencing flickering because the refresh rate was too low, causing visible delays in row/column updates. This resulted in an unstable display where LEDs appeared to blink or stutter instead of showing a smooth image.
+'''Problem:''' The LED matrix display was experiencing flickering because the refresh rate was too low, causing visible delays in row/column updates. This resulted in an unstable display where LEDs appeared to blink or stutter instead of showing a smooth image.
-Solution: We addressed the flickering issue in the display by optimizing the duty cycle through several key strategies. First, we increased the refresh rate to ensure that the rows and columns of the display are updated at a high frequency, specifically above 60 Hz. This rapid updating helps to stabilize the image. Next, we balanced the ON/OFF time of each row and column to maintain consistent brightness across the display. Finally, we implemented precise timing control by fine-tuning the delays and synchronization within the microcontroller code. This adjustment helps avoid any overlap or skipped updates, thereby reducing flicker and enhancing the visual smoothness of the display.
+'''Solution:''' We addressed the flickering issue in the display by optimizing the duty cycle through several key strategies. First, we increased the refresh rate to ensure that the rows and columns of the display are updated at a high frequency, specifically above 60 Hz. This rapid updating helps to stabilize the image. Next, we balanced the ON/OFF time of each row and column to maintain consistent brightness across the display. Finally, we implemented precise timing control by fine-tuning the delays and synchronization within the microcontroller code. This adjustment helps avoid any overlap or skipped updates, thereby reducing flicker and enhancing the visual smoothness of the display.
 == Conclusion ==

@@ Line 407: / Line 407: @@
 === <Bug/issue name> ===
-Discuss the issue and resolution.
 == Conclusion ==

@@ Line 423: / Line 423: @@
 === References Used ===
-List any references used in project.
+* [http://elm-chan.org/fsw/ff/00index_e.html FatFs Filesystem Module]
 === Appendix ===
 You can list the references you used.

@@ Line 33: / Line 33: @@
 * Further explore synchronization and task prioritization of tasks in an RTOS within a more complex application
-== Team Members & Responsibilities ===
+== Team Members & Responsibilities ==
 *  Uday Kumar Reddy Pesala
@@ Line 39: / Line 39: @@
 *  Adi Siva Prasad Reddy Korivi
 ==== Chandra Sekhar====