F20: Treasure Diver - Revision history

Proj user5: /* LED Matrix */

2021-05-31T00:05:28Z

‎LED Matrix

2021-05-31T00:03:52Z

‎CAD Enclosures Design

2021-05-30T23:51:25Z

‎Schedule

2020-12-18T07:59:30Z

‎Collision Detection

2020-12-18T07:58:30Z

‎Software Design

2020-12-18T07:55:50Z

‎Collision Detection

2020-12-18T07:55:19Z

‎General

2020-12-18T07:47:00Z

‎PCB Design

2020-12-18T07:46:25Z

‎Bluetooth Interface

2020-12-18T07:46:08Z

‎Game Pad Controller

@@ Line 1,362: / Line 1,362: @@
 * '''START EARLY AND FINISH THE LED DRIVER ASAP''' The longer you take to implement the driver, the more time you have to wait before you can do any actual game development. You will really start feeling it towards the last week where you want to add polish to your game but you no longer have time. You do not want to catch yourself saying "Just one more week".
-* For the more artistically gifted amongst you, GIMP and MtPaint (open source) are fantastic resources for planning out levels and designing images. For example you can draw out your image and then using a python script or other image processing software you can get 2d array representation of your image that you can place your code. This is going to be much easier than writing entire screens out by hand it out by hand:
+* For the more artistically gifted amongst you, GIMP and MtPaint (open source) are fantastic resources for planning out levels and designing images. For example you can draw out your image and then using a python script or other image processing software you can get 2d array representation of your image that you can place your code. This is going to be much easier than writing entire screens out by hand:
 {| style="margin-left: auto; margin-right: auto; border: none;"

@@ Line 1,322: / Line 1,322: @@
 * When we received the 3D printed enclosures, some of the holes were smaller than designed. This can happen in FDM printing because plastic is melted and placed layer by layer, which is only accurate to a certain thickness and height. In order to enlarge the holes, a needle file was used to file down the openings until the hole was big enough.
 * Due to the COVID pandemic, we were unable to access the free 3D printing services offered by SJSU and so we had to pay to get our enclosures printed. Our original design was extremely costly and so the enclosures had to be redesigned twice in order to bring the cost down to an affordable amount. All the redesigning we had to do took a lot of time away from the other aspects of our project and the resulting enclosures were not as fancy as we originally planned, but it was all we could afford.
 === PCB Design ===

@@ Line 293: / Line 293: @@
 * Completed
 * Completed
+* Completed
 |-
 |}

@@ Line 782: / Line 782: @@
 [[File:Character-Treasure_Chest_Collision_Detection.png|700px|center|Character-Treasure Chest Collision Detection]]
 [[File:Bullet-Obstacle_&_Bullet-Enemy_Collision_Detection.png|700px|center|Bullet-Obstacle & Bullet-Enemy Collision Detection]]
 === RGB LED Matrix ===

@@ Line 776: / Line 776: @@
 ===== Software Design =====
-<insert flow chart of software design & discuss>
+The software design for each collision detection is described in the below flowcharts. The coding implementation is very lengthy and can be viewed in our GitLab repository.
 [[File:Character-Obstacle_Collision_Detection.png|700px|center|Character-Obstacle Collision Detection]]

← Older revision		Revision as of 07:55, 18 December 2020
Line 1,381:		Line 1,381:

	* Create a function that prints the X and Y values of the accelerometer and/or joystick. It will be useful for debugging and further understanding the device.		* Create a function that prints the X and Y values of the accelerometer and/or joystick. It will be useful for debugging and further understanding the device.
−
−	~~=== General ===~~
−
−	* Advice/tip #1
−	* Advice/tip #2
−	* Advice/tip #n

	== Conclusion ==		== Conclusion ==

@@ Line 1,325: / Line 1,325: @@
 === PCB Design ===
 * Our first design of the matrix controller PCB had incorrect pin spacing for the led matrix pins because we accidentally used the wrong footprint. Unfortunately, we didn't notice this until after we had placed the PCB order and so we had to oder a second matrix controller PCB that had the correct matrix pin spacing. Fortunately, we noticed this before our order shipped and so we were able to add the corrected PCB design to our order without any additional delays.
 === LED Matrix ===

@@ Line 1,340: / Line 1,340: @@
 === Bluetooth Interface ===
 * During testing, we realized that once a bluetooth command was sent, it would repeatedly send instead of just being sent once. For example, when the select button was pressed on the game pad, the select command would continuously send even though the button had been released and was no longer pressed. This is just how the bluetooth device works and so we had to make some modifications in our bluetooth handler code to accommodate this. In order to solve the button press data re-sending issue, we set button press to false immediately after receiving a button press command. In order to solve the joystick/accelerometer data re-sending issue, we defined a default state (CENTERED) which means no character movement, so it didn't matter that the centered command was being sent continuously.
 === Game Pad Controller ===

@@ Line 1,346: / Line 1,346: @@
 === Game Pad Controller ===
-* Originally, thresholds for each direction were checked without comparing to another, and it would cause the character to go in a direction that was not intended or not move. When adding comparisons of magnitudes, the character control greatly improved.
+* Originally, thresholds for each direction were checked without comparing to another, and it would cause the character to go in a direction that was not intended or not move. When adding comparisons of magnitudes, character control greatly improved.
 == Advice for Future Students ==