Posted on

Brandon’s Status Report: 3/27

Due to midterms and several large homeworks, I was unable to get as much done as I wanted this week. That being said, I have completed the calibration routine and am working on the color masking for the computer vision. An example of the calibration can be seen in the image below:

where you can click on the picture and it will automatically calibrate to the RGB threshold values to +/- a delta of the pixel you have highlighted. In addition, I have finished the CAD, so we should be getting ready to 3D print soon!

 

Posted on

Zongpeng Yu’s Status Report 3/27

So we decided to make some changes to the servo subsystem. Instead of hooking the servo up directly to raspberry pi, we hooked it up to Arduino instead. The reason for this is because Raspberry Pi’s GPIO pins aren’t  able to  reliably read feedback PMW from the servo.  Attached is a video of servo spinning 90 degree each second. it is also capable from rotating more than 360 degrees if we want to thanks to it being a continuous servo. The library i used is from here:  https://github.com/HyodaKazuaki/Parallax-FeedBack-360-Servo-Control-Library-4-Arduino. Next step I will set up the serial communication between Raspberry Pi and Arduino so the GST(game state tracker) could send me the location where the servo should turn to.

Posted on

Patrick Status Report 3/27

This week I made substantial progress on writing the foundation for the Player UI and Dealer UI. I used a game module called “Pygame” to write the following GUIs.

This is a basic home-screen that will be used for the Dealer UI. Clicking on each square takes your to the appropriate screen.

This is the “Start Game” screen which simply displays the current players in the game and the pot size in the middle.

This is the “Add /Delete Players” screen which allows you to add and remove players from the table. Clicking on a specific spot will prompt the user to provide a name for the player.

I was last working on the “Chip Color Configuration” screen which will allow the user to change the denominations for the the given chip colors (white, red, green, blue, black).

In the upcoming weeks, I plan to refine these interfaces and also complete a “Stack Size” calibration screen which will allow the Dealer to edit the stack sizes of the players in the game.

I will be more focused on refining these interfaces and making them easily integrable into the main system and the Game State Tracker.

 

Posted on

Team Status Report 3/27

This week our team focused on completing the design review report. There was a lot of work left to do, and major design choices to be made. Almost of all of our parts have been shipped, and we are just waiting on a few Raspberry Pis to come through. This week marks the end of our Brainstorming/Design phase in our schedule, so we will now be moving into our Development phase. Our team is looking forward to a productive next few weeks, and really focusing on developing our product and bringing our project to life.

Posted on

Patrick Kollman Status Report 3/20

This week the majority of my work was spent doing the design report. After doing our presentation, we realized a lot of our design choices were unspecified or didn’t have enough detail. For me personally, this meant specifying how  the Dealer UI and Player UI would interact with the other subsystems. So this week, I worked on writing pseudocode for the interconnections between my UI modules and the Game State Tracker.  Deciding as a team how our modules will interact with each other was a major decision we made this week. I also remedied an issue with our shipment orders for parts, so hopefully everything will be shipped by the end of this weekend.

Posted on

Brandon’s Status Report 3/13

This week, I did not get as much done on the vision side. This was mainly due to slow lead times on item delivery. However, I did manage to create several models for the design of our turntable, layout, and visualization for the report. Once I receive the Pi next week, I will begin experimenting with CV on it.

Servo Model

Table Isometric

Table Top View

Posted on

Team Status Report: 03/13/2021

This week everyone had midterms so we didn’t meet at a group. However, we finalized the table design and people are starting to work on their own tasks. Pat and Brandon are still waiting for their parts. They should arrive soon. Next week we will be able to start writing code for our individual components. And after that’s done we will work on the game state control together.

Posted on

Zongpeng Yu’s Status Report for 03/13/2021

I picked up all the parts this Friday. However because I had a bunch of midterms this week I wasn’t able to do much. I did set up raspbian so next step will be hooking up the servo to the board and set up i2c connections and use servo library to do some simple testing. Once thats done, I will need to talk to Pat who’s in charge of dealer software and game state control to figure out how to rotate the servo based on which player is in action.

Posted on

Patrick’s Status Report 3/13/21

This week began with the design presentations. I thought our presentation went very well and I enjoyed learning from other teams and the issues they face. In regards to my personal work, I’ve chosen to use a module called “Pygame” for the UI and GUI  of our game. I haven’t used this module in awhile, so this week I’ve been playing around with its features and planning out how I’m going to structure my modules for the game. I’ve been doing this on my personal laptop while I wait for my Raspberry Pi order to come in. I am also returning to Pittsburgh soon where I plan to meet up with Steve and begin working together as a “2/3” team (sorry Brandon). Looking forward to next week, and finally being able to grind out some code as a team.

Posted on

Zongpeng Yu’s Status Report for 03/06/2021

Our team worked on the slides for design presentation.  Since I was not home for the past 2 weeks, I didn’t have the pi on me.  However, I did look up how to set up rasbian OS, read the syntax for adafruit servo library to control the servo, and learn how to  configure i2c for the adafruit motor driver. The code shouldn’t be too bad so I planned to start writing the firmware for servo after the midterm week and finish it in a week. I think the most challenging part is to integrate everything together so we might dedicate more time for the integrating phase.