S18: Traffic Menace Video Game - Revision history

Proj user11: /* Column Selection */

2018-05-27T11:41:44Z

‎Column Selection

Proj user11: /* Collision */

2018-05-27T11:35:45Z

‎Collision

Proj user11: /* Collision */

2018-05-27T11:35:24Z

‎Collision

Proj user11: /* Restart */

2018-05-27T11:30:07Z

‎Restart

Proj user11: /* Traffic level */

2018-05-27T11:21:35Z

‎Traffic level

Proj user11: /* Lanes */

2018-05-27T11:17:56Z

‎Lanes

Proj user11: /* Game Algorithm */

2018-05-27T11:16:09Z

‎Game Algorithm

Proj user11: /* Game Algorithm */

2018-05-27T11:15:39Z

‎Game Algorithm

Proj user11: /* Driver For LED */

2018-05-27T11:07:52Z

‎Driver For LED

Proj user11: /* Driver For LED */

2018-05-27T10:59:13Z

‎Driver For LED

@@ Line 300: / Line 300: @@
 [[File:CMPE244 S18 Shiftregister.JPG|400px|thumb|center|Shift register SIPO]]
-In summary in order to display something on the LED panels the following steps needs to be performed by the driver
+In order to display something on the LED panels the following steps needs to be performed by the driver
 * Shift the pixel data for row 1 into the top column drivers and the pixel data for row 33 into the bottom column drivers using the R1, G1, B1, R2, G2, and B2 data inputs and the SCLK shift clock signal.
-* Assert the blanking signal to blank the display.
+* Clear the blanking signal to blank the display.
-* Set the address input to 0.
+* Set the address input to 1.
-* Latch the contents of the column drivers‘shift registers into the column drivers‘ output registers using the LATCH signal.
+* Latch the contents of the column driver's shift registers to the output registers using the LATCH signal.
-* De-assert the blanking signal to display rows 1 and 33.
+* Make the blanking signal high to display rows 1 and 33.
 * Repeat the process for each of the pairs of rows in the display for 31 times.

@@ Line 791: / Line 791: @@
 The collision was detected using a 64x64 matrix which replicated the actual display canvas. Each traffic vehicle updated its corresponding position with '1' in the matrix and the user vehicle updated its position with 2. When there was an overlap of two vehicles their values added up. This added up value determined collision. The collision was detected using for loop for the entire rows in which user car existed. So around 60 x 3 pixels were constantly monitored for collision. To reduce task CPU consumption we added minor delays so the task yields, this reduced CPU consumption without affecting its performance
 <br>
 ===== User Car Task=====

@@ Line 791: / Line 791: @@
 The collision was detected using a 64x64 matrix which replicated the actual display canvas. Each traffic vehicle updated its corresponding position with '1' in the matrix and the user vehicle updated its position with 2. When there was an overlap of two vehicles their values added up. This added up value determined collision. The collision was detected using for loop for the entire rows in which user car existed. So around 60 x 3 pixels were constantly monitored for collision. To reduce task CPU consumption we added minor delays so the task yields, this reduced CPU consumption without affecting its performance
 <br>
 ===== User Car Task=====

@@ Line 842: / Line 842: @@
 ===== Restart =====
-In-order improve game-play experience each player is provided with 3 lives after which the game ends. A game restart button was added to restart the game. This button only works when the player loses all 3 lives.
+In-order improve game-play experience each player is provided with 3 lives after which the game ends. A game restart button was added to restart the game. This button only works when the player loses all 3 lives. Once the button is pressed the buffer will be cleared and we will get the get the welcome screen along with the car in initial position.
 ===== Level Up button =====
 The Level Up button to the left makes the user to play the game a level ahead. This would reduce the distance to the upcoming traffic and also increase the score. This can also be used to jump small vehicles to avoid oncoming traffic.

@@ Line 756: / Line 756: @@
 </center>
-The traffic class contained functions to randomize the vehicle selection, speed and location of each vehicle within a lane. The speed of the oncoming traffic increased with the change in levels. Initially, the speed was restricted between 1 – 3. As levels progressed this range was increased 2-5, 3-6 and so on. The scoring system was directly related to level. Initial levels meant the increment in scores was slow and as levels progressed the increment gradually increased. The position of the used car is at the bottom of the display during earlier levels and this position gradually increases to the middle of the display in later stages
+The traffic class contained functions to randomize the vehicle selection, speed and location of each vehicle within a lane. The speed of the oncoming traffic increased with the change in levels. Initially, the speed was restricted between 1 – 3. As levels progressed this range was increased 2-5, 3-6 and so on. The scoring system was directly related to level. Initial levels meant the increment in scores was slow and as levels progressed the increment gradually increased. The position of the used car is at the bottom of the display during earlier levels and this position gradually increases to the middle of the display in later stages. Once the traffic is created the pixels which are used by the traffic are set in the buffer to detect collision.
 ===== Collision =====

← Older revision		Revision as of 11:17, 27 May 2018
Line 634:		Line 634:

	We began by creating a 4-lane road on the display as shown below. Each lane would contain one vehicle at any given time. Current Level would be displayed at the left of the display along with lives remaining and the current score at the right		We began by creating a 4-lane road on the display as shown below. Each lane would contain one vehicle at any given time. Current Level would be displayed at the left of the display along with lives remaining and the current score at the right
		+
		+	<syntaxhighlight lang="C">
		+	void road(void *p){
		+	while(1){
		+
		+	display_road.drawFastVLine(5,0,64,0xFFFF);
		+	display_road.drawFastVLine(58,0,64,0xFFFF);
		+
		+	//LANE1
		+	display_road.fillRect(18,0,1,4,0xFFFF);
		+	display_road.fillRect(18,10,1,4,0xFFFF);
		+	display_road.fillRect(18,20,1,4,0xFFFF);
		+	display_road.fillRect(18,30,1,4,0xFFFF);
		+	display_road.fillRect(18,40,1,4,0xFFFF);
		+	display_road.fillRect(18,50,1,4,0xFFFF);
		+	display_road.fillRect(18,60,1,4,0xFFFF);
		+
		+	//LANE2
		+	display_road.fillRect(31,0,1,4,0xFFFF);
		+	display_road.fillRect(31,10,1,4,0xFFFF);
		+	display_road.fillRect(31,20,1,4,0xFFFF);
		+	display_road.fillRect(31,30,1,4,0xFFFF);
		+	display_road.fillRect(31,40,1,4,0xFFFF);
		+	display_road.fillRect(31,50,1,4,0xFFFF);
		+	display_road.fillRect(31,60,1,4,0xFFFF);
		+
		+	//LANE3
		+	display_road.fillRect(44,0,1,4,0xFFFF);
		+	display_road.fillRect(44,10,1,4,0xFFFF);
		+	display_road.fillRect(44,20,1,4,0xFFFF);
		+	display_road.fillRect(44,30,1,4,0xFFFF);
		+	display_road.fillRect(44,40,1,4,0xFFFF);
		+	display_road.fillRect(44,50,1,4,0xFFFF);
		+	display_road.fillRect(44,60,1,4,0xFFFF);
		+
		+	vTaskDelay(5);
		+	}
		+	}
		+	</syntaxhighlight>

	===== Vehicle types =====		===== Vehicle types =====

@@ Line 600: / Line 600: @@
 [[File:CMPE244 S18 mainflow.png|250px|thumb|center|Traffic Menace main flow]]
-Different tasks are created like drawing lanes, for generating random traffic, to detect collision, for displaying scores, welcome screen, crash screen and displaying player car. Interrupt is enable in for using level up and restart button.
+Different tasks are created like displaying lanes, for generating random traffic, to detect collision, for displaying scores, welcome screen, crash screen and displaying player car. Interrupt is enable in for using level up and restart button.
 <syntaxhighlight lang="C">

@@ Line 599: / Line 599: @@
 [[File:CMPE244 S18 mainflow.png|250px|thumb|center|Traffic Menace main flow]]
 ===== Lanes =====
 <center>

@@ Line 495: / Line 495: @@
 [[File:CMPE244_S18_driverflow.png|300px|thumb|center|The flow of Driver]]
-To design the driver for the LED Display it is required to have a clear-cut understanding of working LED.  So it is recommended to read the hardware part before trying to understand the driver. The SJone board is interfaced to the LED using 14 GPIO pins.  All these pins are set as output. Except OE all other pins are initialized low. OE is set high as it is active low.The display driver makes use of a buffer which stores the color code to be set at particular pixel on the display. Whenever a pixel is to be lighten up the corresponding color to be lighten up will be stored in the buffer. The size of the buffer is 2048. For the first and thirty third row the buffer[0] to buffer [63] is made use. For second thirty fourth buffer [64] to buffer [127] is used and so on. Each element of buffer is 1 byte and each bit that is from bit 2 to bit 8 has the value of R1 G1 B1 R2 G2 B2.  If once a colour is set for a particular pixel then the buffer will be updated and when the pixel is to be turned off then the buffer should be cleared.  A timer interrupt is used to update the display ones in 0. 9ms. When an interrupt occurs 2 rows are updated. Once the full display is written the row is set back to initial value and the same process continues. The time interval for updating the display is so fast that the human eye would believe to see motion.
+To design the driver for the LED Display it is required to have a clear-cut understanding of working LED.  So it is recommended to read the hardware part before trying to understand the driver. The SJone board is interfaced to the LED using 14 GPIO pins.  All these pins are set as output. Except OE all other pins are initialized low. OE is set high as it is active low.The display driver makes use of a buffer which stores the color code to be set at particular pixel on the display. Whenever a pixel is to be lighten up the corresponding color to be lighten up will be stored in the buffer. The size of the buffer is 2048. For the first and thirty third row the buffer[0] to buffer [63] is made use. For second thirty fourth buffer [64] to buffer [127] is used and so on. Each element of buffer is 1 byte and each bit that is from bit 2 to bit 8 has the value of R1 G1 B1 R2 G2 B2.  If once a colour is set for a particular pixel then the buffer will be updated and when the pixel is to be turned off then the buffer should be cleared.  A timer interrupt is used to update the display ones in 0. 9ms. When an interrupt occurs 2 rows are updated. Once the full display is written the row is set back to initial value and the same process continues. The time interval for updating the display is so fast that the human eye would believe to see motion.The RGB class is used for initializing the LED and set the LED blinking frequency to operate.
 <syntaxhighlight lang="C">
@@ Line 531: / Line 530: @@
     #endif
 </syntaxhighlight>

← Older revision		Revision as of 10:59, 27 May 2018
Line 496:		Line 496:

	To design the driver for the LED Display it is required to have a clear-cut understanding of working LED. So it is recommended to read the hardware part before trying to understand the driver. The SJone board is interfaced to the LED using 14 GPIO pins. All these pins are set as output. Except OE all other pins are initialized low. OE is set high as it is active low.The display driver makes use of a buffer which stores the color code to be set at particular pixel on the display. Whenever a pixel is to be lighten up the corresponding color to be lighten up will be stored in the buffer. The size of the buffer is 2048. For the first and thirty third row the buffer[0] to buffer [63] is made use. For second thirty fourth buffer [64] to buffer [127] is used and so on. Each element of buffer is 1 byte and each bit that is from bit 2 to bit 8 has the value of R1 G1 B1 R2 G2 B2. If once a colour is set for a particular pixel then the buffer will be updated and when the pixel is to be turned off then the buffer should be cleared. A timer interrupt is used to update the display ones in 0. 9ms. When an interrupt occurs 2 rows are updated. Once the full display is written the row is set back to initial value and the same process continues. The time interval for updating the display is so fast that the human eye would believe to see motion.		To design the driver for the LED Display it is required to have a clear-cut understanding of working LED. So it is recommended to read the hardware part before trying to understand the driver. The SJone board is interfaced to the LED using 14 GPIO pins. All these pins are set as output. Except OE all other pins are initialized low. OE is set high as it is active low.The display driver makes use of a buffer which stores the color code to be set at particular pixel on the display. Whenever a pixel is to be lighten up the corresponding color to be lighten up will be stored in the buffer. The size of the buffer is 2048. For the first and thirty third row the buffer[0] to buffer [63] is made use. For second thirty fourth buffer [64] to buffer [127] is used and so on. Each element of buffer is 1 byte and each bit that is from bit 2 to bit 8 has the value of R1 G1 B1 R2 G2 B2. If once a colour is set for a particular pixel then the buffer will be updated and when the pixel is to be turned off then the buffer should be cleared. A timer interrupt is used to update the display ones in 0. 9ms. When an interrupt occurs 2 rows are updated. Once the full display is written the row is set back to initial value and the same process continues. The time interval for updating the display is so fast that the human eye would believe to see motion.
		+
		+
		+	<syntaxhighlight lang="C">
		+	#ifndef RGB_h
		+	#define RGB_h
		+
		+	#include "mfGFX.h"
		+
		+	class RGB : public GFX {
		+
		+	public:
		+
		+	static RGB& getRGBInstance();
		+	static RGB* rgbInstance;
		+
		+	void
		+	begin(void),
		+	drawPixel(uint16_t x, uint16_t y, uint16_t c),
		+	fillScreen(uint16_t c),
		+	updateDisplay(void);
		+
		+	void init(uint8_t rows, uint32_t a, uint32_t b, uint32_t c,uint32_t d , uint32_t e,
		+	uint8_t sclk, uint32_t latch, uint8_t oe, bool dbuf,
		+	uint8_t width);
		+	private:
		+
		+	uint8_t nRows;
		+	RGB();
		+	uint8_t _sclk, _latch, _oe, _a, _b, _c, _d,_e;
		+
		+	volatile uint8_t row;
		+	volatile uint8_t *buffptr;
		+	};
		+
		+	#endif
		+	</syntaxhighlight>

	==== Game Algorithm ====		==== Game Algorithm ====