Posted on

Zongpeng Yu’s Status Report for 02/27/2021

This week I looked for motor that we gonna use to spin the camera. We decided on using a servo because we can have it rotate to an exact location. Also there is no need for motor controller because we are only having one servo and we need external power supply for it.

The part i picked is a 360 continuous rotation servo with feedback from adafruit. With the feedback, we can determine the location/rotation of the servo and we could use PWM to let it rotate to certain player’s position. Also this servo provides enough torque to support the camera on top of it. 

The link is: https://www.adafruit.com/product/3614?gclid=Cj0KCQiA-OeBBhDiARIsADyBcE4ks19fWb6nEjYKXbqq6JSbYBFpyEwgnjR2dLRSK4ZkQxkaQgekr6MaArZCEALw_wcB

Servo driver: https://www.digikey.com/en/products/detail/adafruit-industries-llc/815/4990757?s=N4IgjCBcoLQBxVAYygMwIYBsDOBTANCAPZQDa4ArAEwIC6AvvYVWSHGBSIWAGwAESABboAdiNyYQDIA

Brandon also shared a servo on raspberry pi tutorial: https://learn.adafruit.com/adafruit-16-channel-servo-driver-with-raspberry-pi/using-the-adafruit-library

Posted on

Patrick’s Status Report 2/27/21

I started this week by presenting our team’s slides for the proposal presentation. The presentation went well and I received great feedback from my peers. After presenting, I looked into the software that I would be working with for the Dealer UI and the game state logic. We decided as a team that the best solution to integrate all components of this project is to use a Raspberry Pi.  Using a Raspberry Pi will allow us to centralize all our information, so all of our different Python modules can communicate with each other effectively. For the physical Dealer UI controls, we brainstormed ideas like using keys on a keyboard or even buying a Raspberry Pi touchscreen. We plan on finalizing these decisions in a couple days and placing orders for parts ASAP.

Posted on

Team Status Report: 2/27/2021

We spent the beginning of the week participating in the group presentation review. At the end of the week, we met and solidified our thoughts regarding specific software and hardware choices. To summarize, we decided to use a Servo as the motor for our spinning camera, a standard web camera for our CV, and to centralize all our software on a Raspberry Pi. A minor setback this week is deciding who should receive the parts, as some of the team is currently located outside of Pittsburgh. Once we finalize that and other outstanding design choices, we will begin placing orders.

Posted on

Brandon’s Status Report: 02/27/21

This week’s progress has been slightly slower than I had expected. I spent some time reacquainting myself with OpenCV and looking at hardware elements we might need for the project. Two examples of good cameras I have found are:

Both meet the technical requirements we placed for the cameras except maybe for power. However, since USB 2.0 is power limited by 0.5 A max, then the theoretical upper bound on the webcam power usage is 2.5 W, which is perfectly acceptable.

 

Next week, I hope our team can get together and work on the design for representing game state.

 

Posted on

Zongpeng Yu’s Status Report for 02/19/2021

Like everyone else mentioned, we pivoted our design. What I did for this week is thinking about the positioning of the camera/cameras so occlusion won’t become an issue. We will need to add some constraints(designated area on poker table) to where players have to put their stack and bets. I am still a little uncertain about where the pot size has to go because normally people put those in the middle of the table. However, if our camera is in the center, the pot will block off player’s bet and stack size. One way to avoid this is to raise the camera in the center so it is viewing players stack and bet size at an angle. However, I am not exactly sure how the computer vision software can handle this.

 

Posted on

Patrick Kollman Status Report 2/19/21

This week we pivoted from using RFID to mainly using CV for our project. I have more background in RFID and less in CV, so this past week I’ve been doing my own personal research and browsing around the internet on the basics on CV so I can familiarize myself with key concepts. I’m planning on focusing more on the software side of things and writing the interface for our product, but it’ll help knowing the basics of CV to connect everything together. Love the way things are going for our project and the pivot we took.

Posted on

Team Status Report: 2/19/21

Our project has shifted focus away from the original idea; rather than using RFID to read cards and CV to read chips to make information easier to use, we are trying to create a table which speeds up the game through usability. This involves creating a system that automatically goes through the players in the order of the game and tracks their actions and bets during each round, allowing the dealer to have an easier time running the game. We dropped the RFID idea and instead are opting for a camera that sweeps through the table, stopping at each player’s position to read stacks and bets along the way. The plan is to display information such as pot size and player’s stack size that are available to users on online/virtual poker in real life poker. While changes are expected to happen as we go along, we feel our current objective is much more exciting and useful than our previous one.

Posted on

Brandon’s Status Report: 02/19/21

So far, I have mostly been looking for parts and ideas on how to design the system this week. Since we shifted focus away from the original idea, which used RFID, I have been more focused on looking at cameras and motors, along with power supplies, for the device. While I expect changes to happen as we go along, given how our last idea shifted focus away from reading cards to more of a ease-of-use service device, I think these parts will stay pretty constant to any iteration of this project from here on.