Project

# Title Team Members TA Documents Sponsor
31 Gamified Focus-Detection Tamagotchi
Khushi Murthy
Michael Yang
Noah Yi
Tim Jiang
# Problem

We are currently living in a time where Gen Z’s attention span is being reduced due to short form media content and various social and technological distractions, leading to decreased productivity. As such, students who force themselves to sit through hours of studying will often find themselves struggling to stay motivated and on task. Methods such as the Pomodoro strategy have been shown to help increase productivity through structure, yet continuous accountability and immediate feedback when a user becomes distracted are still missing factors.

# Solution

We propose an interactive, desk-based smart companion inspired by a Tamagotchi. The device monitors several indicators of user focus and translates them into the emotional and physical behavior of a desktop pet. A host computer will collect simple focus-related signals, including active application information, keyboard and mouse activity, and whether the user is present at the desk. These signals will be combined into a focus score and transmitted to a microcontroller contained inside a 3D printed enclosure through USB serial communication. The microcontroller will maintain the pet's behavioral state and control its physical outputs. Sustained focus may cause the pet to appear happy or energetic, while extended inactivity or distraction may cause it to appear sad, tired, or perform a physical gesture such as waving its arms to attract the user’s attention. Therefore, our goal is for the companion to create an immediate, external feedback loop that gamifies focus and reinforces effective work habits.

The project is divided into three primary subsystems:

It will have 3 different subsystems:
Software Logic Subsystem: We will connect the board to the laptop to collect focus-related information from the host and compute a focus score.
Microcontroller Subsystem: The embedded controller itself that manages the pet’s behavioral state machine and controls the hardware outputs.
The Display: Provides the user-facing visual and mechanical feedback for the pet’s state

# Solution Components

## Subsystem 1 : Software Logic Subsystem

Description: Runs in the background on the host computer to monitor focus. It tracks active application titles, keyboard/mouse input activity, and uses the host webcam to detect desk presence via basic face tracking. To keep the image-processing component feasible, the webcam will not attempt complex activity, emotion, or identity recognition. It will perform a constrained presence-detection task using an existing computer-vision library such as OpenCV or MediaPipe. The system will assume a relatively fixed webcam position and desk environment. It aggregates these metrics into a scoring metric that represents focus state and sends periodic command packets over USB-serial to the hardware. The main software design challenge of this subsystem will be the fusion of multiple imperfect signals into a reliable and explainable focus metric, rather than relying on computer vision alone.

Parts:
Host PC
Software packages

## Subsystem 2 : Microcontroller and Custom Control PCB Subsystem

Description: A custom PCB will integrate the Raspberry Pi Pico with the system's power distribution, display interface, actuator-control circuitry, peripheral connectors, and protection components. The board will receive focus-state information from the host computer over USB and generate the electrical control signals required by the display and mechanical actuators.
Parts:
Microcontroller Board: Raspberry Pi Pico (Part #: SC0915)
USB interface
Voltage regulation and power distribution circuitry
Servo control interfaces
Display communication interface

## Subsystem 3 : Display and Actuation Subsystem

Description: Provides the physical feedback that makes the device function as a desktop companion. A small display will show animated facial expressions corresponding to the current behavioral state of the pet. One or more servo motors will provide additional mechanical feedback by moving physical components such as the pet's arms.

Parts:
Small OLED or TFT display
Micro servo motors
Mechanical arm linkage
3D-printed enclosure
Supporting power and signal circuitry

# Criterion For Success

Success would consist of meeting our objectives for both the hardware and software portion of the project. The software must successfully collect application activity, keyboard/mouse activity, and webcam-based desk-presence information and combine these inputs into a reproducible focus score or state. The host computer must successfully transmit low-latency focus-state updates to the hardware with outputs being shown within 1-2 seconds. The microcontroller must reliably maintain at least four distinct behavioral states, with each state transition determined by documented focus-score thresholds and timing conditions. Finally, Given the same sequence of focus inputs, the system should produce the same behavioral response. Every pet expression and mechanical action should therefore be traceable to a specific focus metric or state-machine transition.

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