F24: Jardinains - Revision history

Proj user1: /* Implementation */

2024-12-19T23:32:20Z

‎Implementation

Proj user1: /* Software Design */

2024-12-19T23:31:54Z

‎Software Design

Proj user1: /* */

2024-12-19T23:31:25Z

‎

Proj user1: /* Team Members & Responsibilities */

2024-12-19T23:30:31Z

‎Team Members & Responsibilities

Proj user1: /* Acknowledgement */

2024-12-19T23:20:32Z

‎Acknowledgement

Proj user1: /* Parts List & Cost */

2024-12-19T23:19:37Z

‎Parts List & Cost

Proj user1: /* Schedule */

2024-12-19T23:13:31Z

‎Schedule

Show changes

Proj user1 at 23:09, 19 December 2024

2024-12-19T23:09:21Z

Proj user1 at 23:07, 19 December 2024

2024-12-19T23:07:56Z

Proj user1: /* Schedule */

2024-11-26T22:38:44Z

‎Schedule

@@ Line 276: / Line 276: @@
 === Implementation ===
-Paddle Movement
+Paddle Movement :
 The paddle movement is driven by accelerometer data wirelessly transmitted from the SJ-Two board to the LPC4088 board. This data is mapped to 63 possible positions for the paddle. Initially, the paddle would instantly move to the position corresponding to the accelerometer input. However, this approach was refined by introducing an algorithm that allows for a smoother transition between positions. The algorithm calculates paddle velocity based on the "current desired position" and the previous position. Parameters of the algorithm were fine-tuned iteratively to achieve a smooth and responsive paddle movement.
 Paddle-Ball Collision Logic
 The ball's position is updated each frame by adding delta_x and delta_y to its current x and y coordinates. If the ball's next y-position crosses the paddle's y-position, a paddle collision check is performed. To do this, the ball's movement is modeled as a slope derived from delta_x and delta_y. Using this slope, along with the ball's current position and one pixel above the paddle's y-position, a point-slope equation (y2−y1)=m(x2−x1)(y_2 - y_1) = m(x_2 - x_1)(y2−y1)=m(x2−x1) is used to calculate the x-position of the ball at the time it reaches that y-coordinate.
 Once the expected collision point is determined, the ball's collision magnitude and its next position's magnitude are calculated. By comparing these magnitudes, a time fraction for the frame is derived to estimate when the ball might have collided with the paddle. Using the paddle's current position and velocity, the paddle's previous position is estimated to determine how far it moved during this time fraction. By multiplying the time fraction by the paddle's x-position change, it is possible to check whether the paddle was underneath the ball at the moment it reached the pixel above the paddle's y-position.

@@ Line 271: / Line 271: @@
 Controller
 The accelerometer on the SJ2 board manages paddle movement by sampling the y-axis magnitude 17 times over a 17-millisecond period and calculating the average. This value is capped at a maximum of 700 within a range of 1000. To make it simpler, the tilt value is divided by 31, producing 32 possible readings, which correspond to 5 bits of data. Each time there is a change in magnitude or a button press, the controller transmits a single byte of data to the console. This byte encapsulates all the necessary information for controlling the on-screen paddle. The first two bits indicate button input, with 0 representing no input and 1 indicating input detection. The third bit specifies the tilt direction, where 0 means left and 1 means right. The remaining five bits represent the accelerometer's magnitude.
 Audio
 Sound effects are added using MP3 Serial Decoder HiLetgo GD3300, source code was written on our own.
 === Implementation ===

@@ Line 293: / Line 293: @@
 Paddle – Collision Logic
 During final integration and testing, one major issue we faced was a bug where the ball failed to detect collisions with the paddle, causing it to pass through instead of bouncing off. To troubleshoot this, we implemented a clever debugging method: changing the ball's colour during each collision check. This allowed us to visually confirm whether the collision logic was being executed. Through this approach, we discovered that the section of code responsible for checking paddle collisions was being skipped, even when the ball's next y-position had crossed the paddle's y-position. This debugging method proved invaluable in identifying and resolving the root cause of the issue.
 == Conclusion ==

@@ Line 29: / Line 29: @@
 === Team Members & Responsibilities ===
 *  Dev Hitesh Malkan
-**
+**   Core gameplay development
 *  Nidhi Sharma
-**
+**   Interface LED matrix with SJ2 board and core gameplay
 *  Sunny Shah
-**
+**   Audio system research and design
 *  Navya
-**
+**   MP3 module driver development
+**   Interfacing the accelerometer
 == Schedule ==

@@ Line 310: / Line 310: @@
 == References ==
 === Acknowledgement ===
-Any acknowledgement that you may wish to provide can be included here.
+We extend our heartfelt gratitude to Professor Preet and the ISA for organizing such an outstanding class and setting high standards. Their guidance and expectations continually motivated us to strive for excellence and surpass our own limits.
 === References Used ===

@@ Line 210: / Line 210: @@
 == Parts List & Cost ==
-Give a simple list of the cost of your project broken down by components.  Do not write long stories here.
+{| class="wikitable"
 == Design & Implementation ==

@@ Line 84: / Line 84: @@
+|
 * <span style="color:green">Completed</span>
-* <span style="color:orange">In progress</span>
+* <span style="color:green">completed</span>
 |-
 ! scope="row"| 4
@@ Line 134: / Line 134: @@
 * Conduct comprehensive testing of code and hardware.
+|
-* <span style="color:red">Not started</span>
+* <span style="color:green">completed</span>
 |-
 ! scope="row"| 7

@@ Line 15: / Line 15: @@
 == Abstract ==
-TODO
+Prepare for endless bouncing, breaking, and gnome-busting excitement! Jardinaiins reinvents classic brick-breaking gameplay with a delightful twist. Dive into vibrant, garden-themed levels filled with challenging obstacles, quirky gnome antics, and thrilling power-ups. Smash through barriers, outsmart mischievous gnomes, and uncover surprises as you progress in this fun and addictive adventure!
 == 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.
+•  Interface the SJ2 board with the Waveshare 64x64 RGB LED Matrix Panel to display dynamic text, colorful images, and animations. The onboard GPIOs of the SJ2 microcontroller will drive the LED panel, and its chainable design will be utilized to facilitate scalability for larger displays.
 === Team Members & Responsibilities ===
@@ Line 98: / Line 105: @@
 * <span style="color:green">Completed</span>
 * <span style="color:green">Completed</span>
-* <span style="color:orange">In progress</span>
+* <span style="color:green">Completed</span>
-* <span style="color:orange">In progress</span>
+* <span style="color:green">Completed</span>
 |-
 ! scope="row"| 5
@@ Line 117: / Line 124: @@
 * <span style="color:green">Completed</span>
 * <span style="color:green">Completed</span>
-* <span style="color:orange">In progress</span>
+* <span style="color:green">Completed</span>
 |-
 ! scope="row"| 6
@@ Line 140: / Line 147: @@
 * Update and complete wiki page with project details.
+|
-* <span style="color:red">Not started</span>
+* <span style="color:green">completed</span>
-* <span style="color:red">Not started</span>
+* <span style="color:green">completed</span>
 |-
 |}
@@ Line 161: / Line 168: @@
 === 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.
+Controller
 === 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.
+Paddle Movement
 == 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?
+Ball-Collision Logic
-Make a smooth transition to testing section and described what it took to test your project.
+The initial ball collision logic relied on pixel values to detect when the ball entered a brick. However, this approach failed to handle cases where the ball entered a brick diagonally, requiring the logic to be completely reworked. In the updated version, the focus shifted to determining whether the ball was crossing into an area containing a brick. This was achieved by dividing the playing field into a grid representing the positions of the bricks.
+The new logic involved an initial check to see if the ball was crossing a boundary near a brick. If the ball crossed only the x-boundary, a collision check was performed to determine if it hit a brick. Similarly, if it crossed only the y-boundary, another collision check was conducted. In cases where the ball crossed both x- and y-boundaries, additional logic was applied to determine which boundary the ball crossed first. This updated method effectively handled diagonal collisions and improved the overall accuracy of the collision detection.
-Include sub-sections that list out a problem and solution, such as:
+This experience highlighted the value of abandoning ineffective solutions and adopting new approaches, as they can lead to better outcomes.
 === <Bug/issue name> ===
@@ Line 176: / Line 197: @@
 == 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?
+We thoroughly enjoyed the process of creating this project and gained a wealth of knowledge along the way. Our driver development skills were sharpened as we wrote drivers for various modules, including the LED matrix and MP3 decoder. Additionally, our understanding of the FreeRTOS API deepened, and we acquired fundamental game and graphics development skills through our work with the LED matrix.
 === Project Video ===