F22: Bob Burgers - Revision history

243 user1: /* Buttons and Joysticks */

2022-12-16T22:57:34Z

‎Buttons and Joysticks

243 user1: /* Enclosure */

2022-12-16T22:57:27Z

‎Enclosure

243 user1: /* Buttons and Joysticks */

2022-12-16T22:48:47Z

‎Buttons and Joysticks

243 user1: /* Enclosure */

2022-12-16T22:34:07Z

‎Enclosure

243 user1: /* Acknowledgement */

2022-12-15T08:55:12Z

‎Acknowledgement

243 user1: /* Conclusion */

2022-12-15T08:52:18Z

‎Conclusion

243 user1: /* */

2022-12-15T08:40:01Z

‎

243 user1: /* Testing */

2022-12-15T08:33:44Z

‎Testing

243 user1: /* Technical Challenges */

2022-12-15T08:26:22Z

‎Technical Challenges

243 user1: /* GamePlay Implementation */

2022-12-15T08:21:15Z

‎GamePlay Implementation

@@ Line 429: / Line 429: @@
 ===Buttons and Joysticks===
-Mathew Hanna todo
 <div><ul>
 </li>

@@ Line 420: / Line 420: @@
 === Enclosure===
-Mathew Hanna Todo
 <div><ul>

@@ Line 434: / Line 434: @@
 <li style="display: inline-block;vertical-align: top;"> [[File:Joysticks.PNG |thumb|center|250px |  Joysticks]]</li>
 <li style="display: inline-block;vertical-align: top;"> [[File:Buttons.PNG |thumb|center|250px |  Buttons  ]]</li>
 </ul></div>

← Older revision		Revision as of 22:34, 16 December 2022
Line 424:		Line 424:

	<li style="display: inline-block;vertical-align: top;">[[File:Enclosure.PNG \|thumb\|center\|250px \| Metal Enclosure]] </li>		<li style="display: inline-block;vertical-align: top;">[[File:Enclosure.PNG \|thumb\|center\|250px \| Metal Enclosure]] </li>
		+	The enclosure was from anchor electronics, some careful measurements for drilling and cutting made it a good fit for our application, between all the components and the hand wiring it may have been thicker then visually appealing but it made for an easy environment to work in.

	</ul></div>		</ul></div>

@@ Line 596: / Line 596: @@
 == References ==
 === Acknowledgement ===
-We would like to thank Preet for providing and teaching a course that gives a more unique hands on approach to teaching. To be able to learn and perform lab/projects that are more relevant to what currently being used in industry, gives a since of optimism for what we will face in the near future.
+We would like to thank Preet for providing and teaching a course that gives a more unique hands on approach to learning.
 === Appendix ===

@@ Line 586: / Line 586: @@
 == Conclusion ==
-We are quite satisfied with the project. We would had like to add more dynamism to the gameplay but had to deal with unfortunates situations which negated some of the time we had set for improving the gameplay. As simple as the game might seem, making it two player game added longevity to the play time. For some of us, this was our first semester as a master student. It was a pretty tough introduction to embedded systems, but a fun introduction as well. We got to work more with peripherals that we had not used before. Learning about FreeRtos, UART, SPI, and I2C made us feel more prepare for future jobs. Working as a team for this project thought as a lot as well. It thought how important communication is for a project fluidity. Overall, the project provided and tested us on new knowledge, thought us new skills that we believe will be essential for our future career in embedded systems.
+We are quite satisfied with the project. We would had like to add more dynamism to the gameplay but had to deal with unfortunates situations which negated some of the time we had set for improving the gameplay. Nevertheless, by implementing a two player system, we provided the user a more competitive experience. For some of us, this was our first semester as a master student. It was a pretty tough introduction to embedded systems, but a fun introduction as well. We got to work more with peripherals interfaces that we had not used before. Learning about FreeRtos, UART, SPI, and I2C made us feel more prepare for future jobs. Working as a team for this project thought as a lot as well. It thought us how important communication is for a project fluidity. Overall, the project tested us on new knowledge, and thought us new skills that we believe will be essential for our future career in embedded systems.
 === Project Video ===

@@ Line 583: / Line 583: @@
 * The music would stop playing or ending earlier. The mp3 module was set to gpio first and then change to UART. The datasheet did not provide all necessary codes for the correct use of the commands. Research was done to find that an extra command was needed for all commands that require the mp3 module to jump between songs.
 * FPS issues with the ball looking like it was hitting one area but it was delay. The leds lights don't light up as always expected, therefore accommodations were done, where if the ball is around the area and its close enough it will count as a hit or goal.
-* The PCB rows were backwards. The pcb was created to hold the sj2 board, however, the row were backwards and needed to be remade. A second board was made and bought, but it got delayed and lost in Los Angeles, by the time it arrived, we did not want to mess with the system. We did not have enough time to integrate the pcb into the game but were able to logically tested using another sj2 board. Checking if the connections match.
+* The PCB rows were backwards. The pcb was created to hold the sj2 board, however, the row were backwards and needed to be remade. A second board was made and bought, but it got delayed and lost in Los Angeles. By the time it arrived, we did not want to mess with the system. We did not have enough time to integrate the pcb into the game but were able to logically tested using another sj2 board to check if the connections match.
 == Conclusion ==

@@ Line 567: / Line 567: @@
 ===Testing===
-Since we only had one Led Matrix, we would first test are assigned peripherals using individual Leds or by using printfs. Then we would meet and integrated those components and tested them individually with the Led Matrix.
+Since we only had one Led Matrix, we would first test our assigned peripherals using individual Leds or by using printfs. Then we would meet and integrated those components and tested them individually with the Led Matrix.
-This game required a lot of geometry because of the freedom of movement of the ball. A lot, of testing was done to find all of the angles where the ball will disappear or hit the incorrect angles. The ball sometime was set to stop as soon as it left a playable area to find the correct wholes in the play area.
+This game required a lot of geometry because of the freedom of movement of the ball. A lot of testing was done to find all of the angles where the ball will disappear or hit the incorrect angles. The ball was programmed to stop as soon as it left a playable area. This was done to know where the holes in the walls were located. Once found they were patch.
-The joysticks were manipulated to find the correct speed for playability. Sometimes, we would just change the values and only move the blocks to find the correct speed.
+The joysticks were manipulated to find the correct speed for playability. Sometimes, we would just change test the values and only move the blocks to find the correct speed.
-Similarly, multiple different games tested the correct speed of the ball. If it was too fast it provided a clear resolution of the ball but hard to play. While, if it was too slow, the refresh rate will make the ball translucent. All, we could do is keep playing the game, until we reach a good medium.
+Similarly, playing multiple games tested the correct speed of the ball. If it was too fast it provided a clearer resolution of the ball but made it difficult to play. While, if it was too slow, the refresh rate will make the ball translucent. All, we could do is keep playing the game, until we reach a good medium.
 === <Bug/issue name> ===

@@ Line 562: / Line 562: @@
 ===Technical Challenges===
-Our main challenges hardware wise came from loose connections. If we were to do the project again from scratch, the first priority would be to create and assemble the pcb. Having everything set up would save us a lot of time debugging hardware thinking that some of the matrix issues were software related.
+Our main challenges hardware wise came from loose connections. If we were to do the project again from scratch, the first priority would be to create and assemble the pcb. Having everything set up in one pcb would save us a lot of time with debugging hardware.
 Additionally, some of the movements are rigids, with the values changing at a constant rate instead of slowing increasing or decreasing. We would have like to assigning someone to work on specific delays and modifications to make the movement more dynamic.
 ===Testing===

@@ Line 544: / Line 544: @@
 * The ball will then freely move until it reacts to something. The first pixel of the ball is used to detect where it is at all time. The walls and block have hit boxes that take into account where the ball is.
 * If the ball detects that its in a compromise location, it will ask it self what did it hit. If the balls detects no collision but its out of the play area, it will be return to the center.
-* If it hit a wall, the state machine will use it previous state direction and return it the opposite way. For, example if it can up-right, it will return it up-left.
+* If it hit a wall, the state machine will use its previous state direction and return it the opposite way. For, example if it came up-right, it will return it up-left.
-* If it hit a block, the state machine will use it previous state direction and the position where ball hit the block to return the ball. If the ball hits an edge it will return the ball back where it came from. If the ball hit the opposite edge, the state machine will return the ball, the same it would for if it hit the wall.
+* If it hit a block, the state machine will use its previous state direction and the position where the ball hit the block to return the ball. If the ball hits an edge it will return the ball back where it came from. If the ball hit the opposite edge, the state machine will return the ball, the same it would for if it hit the wall.
 * If it hit the area inside the penalty area, then that will signal a goal. The ball will be place back in the center and it will increment the scoring board. The player goal count will be incremented according to whoever scored.
-* After a goal is score, the score task will check if the maximum numbers of goals was reach. Depending on who reach the maximum number of goals first a celebration song and display will be activated.
+* After a goal is score, the score task will check if the maximum numbers of goals was reach. Depending on who reach the maximum number of goals, first a celebration song will play and then the celebration display will be activated.
 * The Celebration screen will remain and the game will be over, unless the reset button is hit. The reset button will reset all global variables and the game will restart.
@@ Line 554: / Line 554: @@
 <div><ul>
-The game flow resembles the image below. Once the game starts, all states will be working on the gameplay. The only actions that can break the flow are the paused and reset buttons. The paused button will paused, wait, and after pressed again return to the gameplay. The reset, restarts the game flow.
+The game flow resembles the image below. Once the game starts, all states will be working on the gameplay. The only actions that can break the flow are the paused and reset buttons. The paused button will paused, wait, and after pressed again return to the gameplay. The reset restarts the game flow.
 <li style="display: inline-block;vertical-align: top;"> [[File:GamePlay Flow Diagram.PNG |thumb|right|250px |  Overall Game Flow]] </li>