Project

# Title Team Members TA Documents Sponsor
51 BTTL BOT PROPOSAL
Aditya Saxena
Laksh Sharma
Xiyue Zhu design_document1.pdf
proposal1.pdf
# Dual Smash: Ant-Weight Battle Bot

Team Members:

-Aditya Saxena (saxena11)

-Laksh Sharma (lsharma2)

# Problem

This is our team's entry for the Fall 2026 ECE 445 Battlebots competition. We will build a sub-2 lb combat robot that can be controlled wirelessly from a laptop and compete against other robots in the arena.

Most battlebot designs use a spinning weapon, wedge, or single attacking mechanism. Our idea is to use two side-mounted hammers that swing horizontally. The hammers can be controlled separately, or both can be activated at the same time in a mode we call "Dual Smash." The goal is to use the two hammers to strike, push, or destabilize an opposing robot while still keeping the robot responsive and easy to control.


# Solution

We will build a 3D-printed ant-weight battlebot controlled by an ESP32-S3 through WiFi. The robot will use differential drive with two brushed DC gearmotors, allowing it to move forward, backward, and turn in place.

The main fighting system will consist of two side-mounted horizontal hammer arms. Each hammer will be driven by its own motor or high-torque actuator. The driver will be able to activate the left hammer, right hammer, or both simultaneously. Activating both hammers together will be called Dual Smash.

The robot will also contain an onboard camera and time-of-flight sensors. The camera will provide a live video feed to the driver's laptop, while the ToF sensors will provide distance information about nearby robots or obstacles. This information will be displayed in the driver interface and used to help position the robot before attacking.

A custom PCB will contain the ESP32-S3, motor-control circuitry, sensor connections, power regulation, and safety circuitry. The robot will be powered using a 2S LiPo battery.

# Solution Components

## Subsystem 1: Camera and Driver Interface

- Hardware: ESP32-S3-WROOM-1 microcontroller and OV5640 camera module connected through the ESP32-S3 camera interface.

- Software: The ESP32-S3 will capture and transmit camera frames over WiFi to a laptop. The laptop interface will display the live camera feed, robot status, ToF measurements, and controls for movement and the two hammer weapons.

The driver interface will allow separate commands for the left hammer, right hammer, and Dual Smash mode.

## Subsystem 2: Time-of-Flight Sensing

- Hardware: Four VL53L1X time-of-flight sensors positioned around the robot, with sensors facing the front, rear, left, and right sides.

- Software: The ESP32-S3 will configure and read each ToF sensor over I2C. Since the sensors share the same default I2C address, their XSHUT pins will be used during startup to assign separate addresses.

The distance measurements will be transmitted to the driver laptop and displayed alongside the camera feed. The sensor data will help the driver determine when an opposing robot is within range of the side hammers.

## Subsystem 3: Drive and Dual Smash Weapon System

- Hardware: Two brushed DC gearmotors will provide differential drive. A TB6612FNG dual H-bridge motor driver will control the drive motors.

The weapon system will contain two independently controlled side-mounted horizontal hammer arms. Each hammer will be connected to its own high-torque motor or actuator through a mechanical linkage. The final motor and gear ratio will be selected based on the required hammer speed, torque, and robot weight. Motor-driver circuitry will allow the ESP32-S3 to control the direction and activation of each hammer.

- Software: The ESP32-S3 will generate PWM and direction signals for the drivetrain and hammer actuators. The driver will be able to activate either hammer individually or activate both at the same time using Dual Smash.

The software will also enforce a cooldown or reset period between hammer activations so that the mechanism has time to return to its starting position before another strike.

A communication-loss safety system will disable the drive and weapon motors if the WiFi connection to the driver laptop is lost.

## Subsystem 4: Power System

- Hardware: A 2S LiPo battery will provide power to the drivetrain, hammer motors, and electronics. The battery capacity will be selected after measuring the final current requirements and checking the total robot weight.

Voltage regulation will provide the required voltage rails for the ESP32-S3, camera, ToF sensors, and supporting electronics. The custom PCB will also contain decoupling capacitors, power distribution, motor connections, and protection circuitry.

A MOSFET-based motor cutoff and manual emergency stop will be included so that power to the drivetrain and hammer system can be disabled quickly.

- Software: The ESP32-S3 will monitor communication status and place the robot into a safe state if the wireless connection is lost. Motor commands will default to zero during startup, connection loss, or emergency shutdown.

# Criterion For Success

1. The completed robot will weigh less than 2 lb, including the battery, PCB, camera, sensors, drivetrain, and both hammer mechanisms.
2. The robot will respond correctly to forward, reverse, left, and right movement commands from the laptop during repeated testing.
3. The camera system will provide a continuous live video feed to the driver's laptop during a full 2-minute match.
4. All four VL53L1X sensors will initialize correctly and provide distance measurements that are consistent with measured physical distances.
5. The left and right hammer mechanisms will each complete at least 20 consecutive strike and reset cycles without mechanical or electrical failure.
6. Dual Smash will activate both side hammers together, with both hammer movements beginning within 100 ms of each other.
7. The robot will be able to strike or destabilize another ant-weight robot using either an individual hammer or Dual Smash.
8. Drive and weapon power will be disabled within 500 ms of losing the WiFi control connection.
9. The robot will remain controllable while simultaneously transmitting camera and ToF data to the driver laptop.
10. The complete system will operate continuously for the duration of a full 2-minute match without requiring a controller reset.

Disclaimer: We used AI to help format and word this document.

ClassroomClarity: Portable Teacher Support Hub

Maddie Donku, Kaitlin Gowens, Jesse Gruber

ClassroomClarity: Portable Teacher Support Hub

Featured Project

# ClassroomClarity: Portable Teacher Support Hub

Team Members:

- Maddie Donku (mdonku2)

- Kaitlin Gowens (kgowens2)

- Jesse Gruber (jgruber5)

# Problem

In the classroom today, students may be reluctant to raise their hands to ask a question, or the professor may not see them. Questions that are critical to understanding the material go unanswered as a result. Asking questions and getting clarification on class material is fundamental to learning, which is why the classroom needs to be more accommodating to students’ questions.

While there are tools such as Mentimeter, these platforms require professors to use time outside of class to create slides and also take up screen space on the lectern. Another issue with the variety of sites used for student engagement is that there is no uniformity for the students. Cell phones and laptops can become clogged with numerous bookmarks for these applications for different classes. Lastly, professors may need an easily detectable, portable, physical alert to remind them to look at questions that students have posted, which cannot be provided by online means.

Professors and students can benefit from a tool that will easily show them how the class is handling material and any questions that may arise. A hub that is consistent between classes will simplify the learning experience for both students and professors.

# Solution

Our solution introduces a clarity hub to the classroom. The hub will sit in the sight of a professor with indicator lights, relaying both how the students are absorbing the class material and any questions that have been sent to the hub. The hub will have a “raise-hand” feature which will notify a professor when a student wants to vocally ask their question and host a screen that will display questions that students may send in using an app. The hub will have a specific passcode that must be entered into the app to access the hub. A wearable will vibrate when a question is present to remind the teacher to look at the hub. This could either be worn or sit near the hub for alerts.

# Solution Components

## 1) Hub Control System

The control system of the hub facilitates communication between each subsystem and allows for user input through tactile means. This system would include the microcontroller as the brain of the device, as well as a series of LEDs, buttons, and dials. The ESP32-PICO-V3 microcontroller was chosen for its built-in Bluetooth, 520 KB SRAM to store student’s questions, ample GPIOs, and is supported by the Arduino IDE. The LEDs can be obtained from the supply center and will be in the colors; green, yellow, orange, and red (606-4302H5-5V, HLMP3401, 39K995, HLMP3301). The buttons to select and resolve questions will be D6C90 F2 LFS to provide tactile input on press. The dial to scroll through the questions will consist of a knob (EH71-1SB2S) connected to a 10k rotary potentiometer (P0915N-FC15BR10K).

## 2) Hub Power System

This subsystem provides power to the microcontroller and its peripherals. To power the microcontroller, we believe a LITH-ION 3.7V 850MAH battery (1568-1495-ND) would be the best option. Its voltage and current rating provide enough range to handle the microcontroller in peak active mode (3.3V, 360mA) while reducing wires in the workspace, and increasing portability. The 3.7V is also within range to power the different colored LEDs and other peripherals. To meet the requirements of the different components, a voltage regulator (LM317T (NAT)) will be used with corresponding resistors and 1uF capacitors to step down the voltage.

### 3) Communication System

The communication subsystem works as the link between the app, main hub, and the wearable band. As discussed in #1, #4, and #5, we will be using bluetooth to transmit data from the app to the main hub and to send a signal to the band to initiate the vibration. Since we are planning to use the ESP32 microcontrollers in the band and main hub, the bluetooth functionality is already built in.

## 4) App

The app is the student interface which will allow students to submit data to the main hub to pose questions to the teacher and indicate their current understanding. We plan to use Android Studio Software to code our own app that will include sliders to rate understanding on a 1-5 scale, question submission through text or “raise hand” modes, and a way to connect to the hub via bluetooth. We want to use Android Studio because it works for both Android and IOS app development and we have worked with it in the past.

## 5) Wearable Band

The wearable band acts as a tactile notification system for the teacher. It vibrates when a new question is submitted to subtly notify the teacher. For the same reasons as discussed in #1, we are looking at using an ESP32-PICO-V3 microcontroller to control the vibrations. Similarly, to power the microcontroller, we are currently looking at a LITH-ION 3.7V 850MAH battery (1568-1495-ND). The band vibration would be made using a vibration motor like ROB-08449-ND because it requires low voltage (3V), is small and therefore wearable, and operates within the battery specifications. A voltage regulator like LM317T (NAT) along with resistors and 1uF capacitors will be used to step down the voltage.

# Criterion For Success

- Students able to send questions wirelessly to the hub through an app

- Students able to submit engagement ratings wirelessly to the hub through an app

- Hub uses lights to indicate general class understanding based on incoming data

- Hub displays questions asked by students or indicates that a student raised their hand

- Hub allows anonymous/not anonymous posting when submitting a question

- Wearable that vibrates upon a question being posted, will have different modes that allow for repeat vibrations if there is a question on the hub (reminders)

- Professor able to clear questions on the hub one by one

Project Videos