F18: Catch me if you can - Revision history

Proj user2: /* References */

2019-12-18T17:53:31Z

‎References

Proj user2: /* Appendix */

2019-12-18T17:52:37Z

‎Appendix

Proj user11: /* Schedule */

2018-12-21T06:37:48Z

‎Schedule

Proj user11: /* Issues, Challenges and solutions to get past them */

2018-12-20T19:05:37Z

‎Issues, Challenges and solutions to get past them

Proj user11: /* Issues, Challenges and solutions to get past them */

2018-12-20T19:03:56Z

‎Issues, Challenges and solutions to get past them

Proj user11: /* Acknowledgement */

2018-12-20T18:56:02Z

‎Acknowledgement

Proj user11: /* Acknowledgement */

2018-12-20T18:53:14Z

‎Acknowledgement

Proj user11: /* Steps of Testing */

2018-12-20T18:42:41Z

‎Steps of Testing

Proj user11: /* PCB module Testing */

2018-12-20T16:09:12Z

‎PCB module Testing

Proj user11: /* Tasks and Flow Control */

2018-12-20T16:08:36Z

‎Tasks and Flow Control

← Older revision		Revision as of 17:53, 18 December 2019
Line 692:		Line 692:

	[5] [https://learn.sparkfun.com/tutorials/rgb-panel-hookup-guide?_ga=2.65248494.1993636224.1545283057-617364471.1535821258]		[5] [https://learn.sparkfun.com/tutorials/rgb-panel-hookup-guide?_ga=2.65248494.1993636224.1545283057-617364471.1535821258]
		+
		+	=== Appendix ===
		+	You can list the references you used.

← Older revision		Revision as of 17:52, 18 December 2019
Line 692:		Line 692:

	[5] [https://learn.sparkfun.com/tutorials/rgb-panel-hookup-guide?_ga=2.65248494.1993636224.1545283057-617364471.1535821258]		[5] [https://learn.sparkfun.com/tutorials/rgb-panel-hookup-guide?_ga=2.65248494.1993636224.1545283057-617364471.1535821258]
−
−	~~=== Appendix ===~~
−	~~You can list the references you used.~~

@@ Line 147: / Line 147: @@
 * Complete Wiki Report and Final Demo
 |Completed
-| 18/11/2018
+| 12/18/2018
 |}

@@ Line 604: / Line 604: @@
 '''1.  RGB LED Matrix Display driver'''
-Porting Adafruit LED driver, which is AVR microcontroller compatible into LPC was challenging because the library was not compatible with LPC1758 micro-controller. As a result, initially all the LEDs were getting turned on. Plenty of changes were done in the existing Adafruit library after which the driver was working as expected. Some of the changes were - to map the LPC GPIOs to LED matrix pins. This was challenging because choosing the pins also mattered for PCB design, which we were unaware until we started to design PCB. We had to remap the LPC GPIO pins to LED matrix as per PCB wiring convenience again. In addition to the basic API functions available, we had to develop many new APIs which were specific to the game using the bitmap to create various re-usable objects.
+Porting Adafruit LED driver, which is AVR microcontroller compatible into LPC was challenging because the library was not compatible with LPC1758 micro-controller. As a result, initially all the LEDs were getting turned on. Plenty of changes were done in the existing Adafruit library after which the driver was working as expected. Some of the changes were - to map the LPC GPIOs to LED matrix pins. This was challenging because choosing the pins also mattered for PCB design, which we were unaware until we started to design PCB. We had to remap the LPC GPIO pins to LED matrix as per PCB wiring convenience again. In addition to the basic API functions available, we had to develop many new APIs which were specific to the game using the bitmap to create various re-usable objects. So basically we had to migrate the whole library from AVR to LPC1758.
 '''2.  Nordic Wireless'''

@@ Line 604: / Line 604: @@
 '''1.  RGB LED Matrix Display driver'''
-Porting Adafruit LED driver, which is AVR microcontroller compatible into LPC was challenging because the library version was not compatible with the LED display, as a result all the LEDs were turned on. This issue was resolved when we used an older version. Also as we used the existing Adafruit library, we had to map the LPC GPIOs to LED matrix pins.This was challenging because choosing the pins also mattered for PCB design, which we were unaware untill we started to design PCB. We had to remap the LPC GPIO pins to LED matrix as per PCB wiring convenience again.
+Porting Adafruit LED driver, which is AVR microcontroller compatible into LPC was challenging because the library was not compatible with LPC1758 micro-controller. As a result, initially all the LEDs were getting turned on. Plenty of changes were done in the existing Adafruit library after which the driver was working as expected. Some of the changes were - to map the LPC GPIOs to LED matrix pins. This was challenging because choosing the pins also mattered for PCB design, which we were unaware until we started to design PCB. We had to remap the LPC GPIO pins to LED matrix as per PCB wiring convenience again. In addition to the basic API functions available, we had to develop many new APIs which were specific to the game using the bitmap to create various re-usable objects.
 '''2.  Nordic Wireless'''

@@ Line 679: / Line 679: @@
 == References ==
 === Acknowledgement ===
-We would like to thank our Professor Preetpal Kang for all his awesome lectures and explanations of the embedded system topics, they could not have been explained better! Not only did we enjoy working on this project but it also gave us an overall learning experience and precious life lessons. We would also like to thank the ISA members for always being around and ready for helping whenever required.
+We would like to thank our Professor Preetpal Kang for all his awesome lectures and explanations of the embedded system topics, they could not have been explained any better than this! Not only did we enjoy working on this project but it also gave us an overall learning experience and precious life lessons. We would also like to thank the ISA members for always being around and ready for helping whenever required.
 === References Used ===

← Older revision		Revision as of 18:42, 20 December 2018
Line 653:		Line 653:
	3) Once, we had the console module ready, we started integrating the display module and console module. Once we integrated ,we checked for the basket movement while changing the board orientation. Until we had the smooth movement of the basket object on the screen, we continued to finely tune the calibration for accelerometer values.		3) Once, we had the console module ready, we started integrating the display module and console module. Once we integrated ,we checked for the basket movement while changing the board orientation. Until we had the smooth movement of the basket object on the screen, we continued to finely tune the calibration for accelerometer values.

−	4) After fine tuning the calibrations, we moved on to test out game algorithms, where the display screen was rigorously tested by playing the game continuously, reversing the console board and trying to see whether display responds. All the stages of game algorithms (the handlers mentioned the software design ) the start screen,end screen, count down screen and display during game was verified .	+	4) After fine tuning the calibrations, we moved on to test out game algorithms, where the display screen was rigorously tested by playing the game continuously, reversing the console board and trying to see whether display responds. All the stages of game algorithms (the handlers mentioned the software design ) the start screen,end screen, count down screen and display during game was verified.
		+
		+	5) The game algorithm i.e. system testing was done where we tested the screen navigation sequence, difficulty levels of the game (it
		+	should not be too easy to win and not too hard to win either). Also every member was asked to play the game for a through testing for robustness of the algorithm. Negative test cases were also tested like pressing the key randomly and likewise.

← Older revision		Revision as of 16:09, 20 December 2018
Line 639:		Line 639:

	Console circuit testing was not possible before we design and received PCBs as we don't have main IC and it is available only in SMD. Ones we solder the whole PCB and gave power PCB got burnt, after rigorous testing and debugging we found that we used SPDT switch which connects battery's positive terminal to ground. We solve this problem in next iteration by not connection one lag of SPDT switch after that it worked fine. We configured our IC to charge 400 mAh battery at the rate of 80mAh (preferred configuration in the datasheet). So It takes approx 5h to charge battery ones it fully discharged. We tested our circuit with two full charging-discharging cycles and everything worked as expected.		Console circuit testing was not possible before we design and received PCBs as we don't have main IC and it is available only in SMD. Ones we solder the whole PCB and gave power PCB got burnt, after rigorous testing and debugging we found that we used SPDT switch which connects battery's positive terminal to ground. We solve this problem in next iteration by not connection one lag of SPDT switch after that it worked fine. We configured our IC to charge 400 mAh battery at the rate of 80mAh (preferred configuration in the datasheet). So It takes approx 5h to charge battery ones it fully discharged. We tested our circuit with two full charging-discharging cycles and everything worked as expected.
−
	<BR/>		<BR/>

@@ Line 557: / Line 557: @@
 <tr>
 <td>
-[[File:Input handler 2019 fall.JPG|300px|thumb|center|'''Display module screen state flow''']]
+[[File:Tasks list 2019 fall.JPG|185px|thumb|center|'''List of Free RTOS Tasks''']]
 </td>
 <td>
-[[File:Display_handler_2019_spring.JPG|300px|thumb|center|'''Display Handler Class''']]
+[[File:Input handler 2019 fall.JPG|300px|thumb|center|'''Input Handler Class''']]
 </td>
 <td>
-[[File:Tasks list 2019 fall.JPG|300px|thumb|center|'''List of Free RTOS Tasks''']]
+</tr>
 </td>
 <td>
-[[File:Logic handler 2019 fall.JPG|300px|thumb|center|'''List of Free RTOS Tasks''']]
+[[File:Logic handler 2019 fall.JPG|315px|thumb|center|'''Game Logic Handler Class''']]
 </td>
 <td>
@@ Line 572: / Line 581: @@
 </table>
 </center>
@@ Line 583: / Line 590: @@
 '''Game_Begin:''' This is a task which divided into Logic Handler, Input Handler and Display Handler. Input Handler read the input,Logic Handler implements various algorithms to generate eggs with random behavior,checks for game Over condition,sliding the basket depending upon the direction received from Input handler,speed of sliding ,Logic to determine the catch or miss of Egg and increment the water level on every miss.Display Handler deals with displaying objects on screen. Each handler class have its manager functions which calls all the private functions of respective handler. From the game Task we call these manager functions of all the handlers.Basic Game theory is to check the input,update the logic and display. we are implementing same thing using handlers for display,logic and input.
 '''Tasks in Console Module :'''