Difference between revisions of "F22: Bob Burgers"

Hardware Design

Discuss your hardware design here. Show detailed schematics, and the interface here.

Hardware Interface

Circuit Block Diagram

In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high level workings rather than inner working of your project.

Software Design

Gameplay Flowchart

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.

Led Matrix

Hardware Implementation and Design

All the pins were set up to be close to each other for better readability. The led matrix required 16 pins as specified above with two being ground. It required 5v with at least 2.1A current. The led matrix uses daisy chaing shift registers to set up the rows. The RGB1 pins set up the color of the top half leds and the RGB2 pins set up the color of the lower half leds. To control the lower half leds both RGB1 and RGB2 need to be set simultaneously. The matrix is 64x64, but works more like a 32x64 matrix. Pins A through E will select the row of the top half. For example, pixel 32x1, will light up when pixel 1x1 is on. This means that both RGB1 and RGB2 need to be set or reset simultaneously. For one pixel to be set, all other pixels need to be reset.

Software Implementation and Design

We used premade 64x64 arrays for the background and smaller arrays for game objects. Those arrays were set to refresh the matrix after anything was drawn on the board. The led task was in charge to reset the board to the original background after vtaskdelay was call. This was done to erased the previous positions of the ball or blocks after they had moved.

void led_driver__refill_refresh(uint8_t (*update_matrix)[64]) {
 for (int row = 0; row < 64; row++) {
   for (int col = 0; col < 64; col++) {
     led_matrix_refresh_array[row][col] = update_matrix[row][col];
   }
 }
}

A background driver was created to introduced full objects to the game. Instead of updating every pixel at a time to create a ball or block, the background driver takes in different size arrays and adds them to the game. There are multiple functions for different game objects but they work the same. All they require is the axis of the pins and the size of the arrays. This made it easier to code the movement of the objects by just following the first pixel of the object in the display. Instead of updating every pixel at a time, the led matrix buffer as a whole will be refresh whenever a new pixel was added. If an object was only on the top or bottom half, the other side was set to off.

static void fill_word(uint8_t y, uint8_t x, uint8_t array_x, uint8_t array_y, uint8_t insert_word[array_y][array_x],
                     color_code color) {
 for (int row = 0; row < array_y; row++) {
   for (int col = 0; col < array_x; col++) {
     if (insert_word[row][col] == 1) {
       led_driver__setPixel(row + y, col + x, color);
     } else {
       led_driver__setPixel(row + y, col + x, insert_word[row][col]);
     }
   }
 }
}

Finally, the led task is runs all of this functions to set up the display. The psuedocode below demonstrate the events the task goes through.

Pseudocode

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.

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? Make a smooth transition to testing section and described what it took to test your project.

Include sub-sections that list out a problem and solution, such as:

<Bug/issue name>

Bugs

• Joystick input had a fixed paddle speed
• Pause and Reset buttons service with ISR was difficult to debounce, moving button input detection to a Task would be more practical

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?

Project Video

SOCCER PONG Youtube Link

Project Source Code

SOURCE CODE GITLAB

References

Acknowledgement

Any acknowledgement that you may wish to provide can be included here.

References Used

List any references used in project.

Appendix

You can list the references you used.

• Everything You Didn't Want to Know About RGB Matrix Panels
• DY-SV5W Voice Playback ModuleDatasheet
• DY-SV5W Choosing an MP3 Player for Arduino
• Daisy-Chain Shift Registers || Essential Engineering Tutorial using Arduino