Project

# Title Team Members TA Documents Sponsor
62 Multi-Game Card Dealer
 Daniel Gutierrez
Matthew Tzeng
 Jason Jung design_document1.pdf
final_paper1.pdf
grading_sheet1.pdf
proposal1.pdf
video
# Multi-Game Card Dealer
Team Members:

- Daniel Gutierrez (danielg9)

- Matthew Tzeng (mttzeng2)

- Third Member (______)

# Problem
Dealers are the heart of every card game imaginable. Cards must be dealt out in a certain, specific fashion both at the beginning and throughout the game. Humans are the ones who have been dealing cards for centuries, however, human error has remained a factor. Misdeals slow down setups, mess up gameplay, and ruin the card game experience for players.

# Solution

To remove errors from the dealing process, we propose an automatic card dealing machine that can act just as a human dealer with knowledge of multiple different games and rules. Our solution aims to achieve three goals:

- Eliminate misdeals from the playing card experience
- Provide validation for players that the dealt cards are fair and the playing field is level.
- Offer “human dealer” actions, such as player identification and responses to player action (such as dealing more cards, or moving on to the next player)

# Components

## Dealing subsystem
- Nema 17 Stepper Motor [Link](https://www.amazon.com/STEPPERONLINE-Stepper-Bipolar-Connector-compatible/dp/B00PNEQKC0?mcid=e981ddab58e43534b29effba82c3f107&hvocijid=1482600293604330599-B00PNEQKC0-&hvexpln=73&tag=hyprod-20&linkCode=df0&hvadid=721245378154&hvpos=&hvnetw=g&hvrand=1482600293604330599&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9022185&hvtargid=pla-2281435179978&psc=1)
- 5V Stepper Motor (ECE Supply Shop)

## Swivel subsystem
- HITEC STANDARD SERVO (E-shop)
## Player Detection subsystem

- TOF10120 Time-of-Flight Distance Laser Distance Measuring Sensor 5-180cm UART I2C Output [Link](https://www.amazon.com/HUABAN-TOF10120-Flight-Distance-Measuring/dp/B089SLWYZ9)
- Focus 5MP OV5647 Sensor [Link](https://www.arducam.com/product/arducam-ov5647-standard-raspberry-pi-camera-b0033/)

## Deal Validation/Card Identification subsystem
- Raspberry Pi 3
- Focus 5MP OV5647 Sensor [Link](https://www.arducam.com/product/arducam-ov5647-standard-raspberry-pi-camera-b0033/)
## Bluetooth/Wifi subsystem
- Raspberry Pi 3
- Player’s phones / web browser
## Power subsystem
- Spektrum 11.1V 1300mAh 3S 30C Smart G2 LiPo Battery [Link](https://www.spektrumrc.com/product/11.1v-1300mah-3s-30c-smart-g2-lipo-battery-ic3/SPMX133S30.html)
- 5V 3A Buck (Step-down)
- 3.3V 1A Buck
- 6V–12V Adjustable Buck

# Criterion For Success
- Dealer can “simple” deal (eject one card at a time at a constant speed with perfectly even angles)
- Dealer can “real-world” deal (eject one card at a time with variable speeds depending on the distance and variable angles depending on each player's position at the table)
- Dealer can rotate 360 degrees around a pivot point and stop at different specified angles with high accuracy
- Player detection: The front camera is successfully able to detect when a player has sat down to play or got up to leave
- Deck validation: The inside camera can detect when there is a fault deck (either duplicated cards or missing cards)
- Potentially accomplished with cool ejection patterns
- Bluetooth/Wi-Fi GUI (App or external GUI) connected to the inside camera to add statistics for a better viewing experience

Antweight Battlebot Project

Jeevan Navudu, Keegan Teal, Avik Vaish

Antweight Battlebot Project

Featured Project

# Antweight Battlebot

Team Members:

- Keegan Teal (kteal2)

- Avik Vaish (avikv2)

- Jeevan Navudu (jnavudu2)

# Problem

In order to compete in Professor Gruev’s robot competition, there are many constraints that need to be met, including:

- Maximum weight (2lbs)

- Allowed materials (3D-printed thermoplastics)

- Locomotion system and fighting tool

- Wireless control via Bluetooth or Wifi

The main goal of this competition is to design a Battlebot that is capable of disrupting the functionality of the other Battlebots with our fighting tool while maintaining our own functionality.

# Solution

For the project, we plan to build a battlebot with a custom electronic speed controller (ESC) that can independently control three brushless motors: two for the drive system, and one for the fighting tool. This ESC will be controlled by an STM32 microcontroller, to which we will add a Bluetooth module to connect to it and specify how much power we want to send to each motor. To communicate with our robot, we will use a laptop that can connect to Bluetooth.

# Solution Components

## Vehicle Controller

The main subsystem of the robot will be a combined vehicle control board and ESC. This subsystem will contain an STM32 Microcontroller that will serve as the brain for the whole robot. With this MCU, we’ll be able to flash our whole software package that will be able to control the speed and direction of the robot, the robot’s weapon, and the Bluetooth communication.

## Power Module

This subsystem includes the battery, the voltage regulators/converters needed to power the electronics, and the necessary battery monitoring circuitry. Specifically, for the battery, we will use a 14.8V 4S2P LiPo pack to power all the components. There will also be a voltage short detection circuit for the battery that will shut down the robot in case of a short to ensure safe practices. This subsystem also contains a 5V linear regulator and 3.3V linear regulator to power the low voltage electronics.

## Drivetrain/Powertrain

This subsystem includes the motors and H-bridges needed to control both the wheels and weapon of the robot. The H-bridges will be made with regular N-MOSs that will be controlled by a PWM signal sent from the STM32 MCU. This H-bridge setup will be able to control the voltage and polarity sent to the motors, which will be able to control the speed of the wheels or weapon. This subsystem will also include the mechanical wheels of the robot and actual hardware of the weapon, which will be a spinning object. Since all the wheels and the weapon have the same mechanical motion, they can all use the same hardware and software electronically, with minor adjustments in motor selection and the actual mechanical hardware/peripheral.

## Bluetooth Module

One big requirement for this project is the ability for the robot to be controlled wirelessly via laptop. The STM32 MCU has bluetooth capabilities, and with additional peripheral hardware, the robot will be able to communicate over bluetooth with a laptop. The goal for the laptop is to be able to control the speed, direction, and weapon of the robot wirelessly and also have a display for live telemetry.

## Mechanical Design

The last part of our project would be the mechanical design of the robot chassis and weapon. For the chassis and weapon material, we decided to go with PLA+ as it offers a blend of being strong and robust but not being too brittle. The drive system will be a 2-wheeled tank style drive with one motor controlling each side of the robot. For the weapon, we are looking to utilize a fully 3D-printed drum that will have a 100% infill to maximize the rotational inertia which can lead to bigger impacts.

## Criterion for Success

We would consider our project a success if we are able to communicate with the robot from our computer as in sending throttle and steering commands to the robot, if those commands are then processed on the robots microprocessors and the motors are sent the according power needed to move and behave in the way that we want during a match.

## Alternatives

The most commonly used electronics in current antweight battlebots consist mostly of RC drone parts. We plan to create a very similar ESC to those on the market but it will have an integrated Bluetooth wireless capability as well as telemetry monitoring. We also want to focus on minimizing packaging size to lower weight and increase flexibility as much as possible.

Project Videos