Project

# Title Team Members TA Documents Sponsor
2 Antweight Battlebot
Gauthami Yenne
Jingyu Kang
Nandika Vuyyuri
Haocheng Bill Yang proposal1.pdf
# Antweight Battlebot
Nandika Vuyyuri (vuyyuri2) \
Gauthami Yenne (gyenne2) \
Jingyu Kang (jingyuk2)

# Problem
The goal of this project is to create an antweight battlebot that would weigh less than 2 lbs in order to participate in the Antweight Battlebot Competition. The criteria given are that all robots must have clearly visible and controlled mobility; must be controlled via either Bluetooth or WIFI using a microcontroller with an manual operation for disconnection; and rotational blade which would contact the arena 5 inches above the ground level and could come to a complete stop within 60 seconds.

# Solution
The battlebot will be mounted with a tombstone attacking mechanism in order to disable the opponent’s vehicle.

# Solution Components
## Power System:
We need a max of 16V considering the motor we are using for moving our robot around so we plan to use Thunder Power 325 mAh 3s battery (THP 325-3SR70J) which is 35g and is the lightest battery we could find that met our requirements. Other battery options weighted about 65g to 105g which would be too heavy to meet the criteria since the weight limit for the entire battlebot should be about 900g. \
Another option is to use flat lithium batteries since the weight of the batteries are significantly lighter than the regular batteries. However, the problem of this would be that the power would not be sufficient enough for the battlebot to move and perform the tasks required as most of the lithium batteries cannot produce significant power at a single instant but rather is a long lasting battery.

## MCU:
The ESP32-C3 (ESP32-C3-DevKitM-1), which is known for its low power consumption, will be used for connection between the battlebot and the controller utilizing its built-in Wifi and Bluetooth system. We will use Arduino IDE in order to program the ESP32-C3 to control the robot. We will use this to control the robot’s mobility and attacking mechanism. \n We have access to debugging and flashing tools that are compatible with the ESP32-C3 MCU.

## Attacking mechanism:
We plan to use the Emax RS2205 2600KV motor which is 30g. This motor has a fast RPM and is often used for drones actually which we are hoping will be a powerful attacking mechanism.

## Robot mobility
To maneuver the battlebot we will use a dual H-bridge configuration using the DRV8833 motor driver paired with high-torque Pololu Micro Metal Gear Motors and integrate the parts with the ESP32-C3-DevKitM-1.


## Materials
We plan to use a mixture of lightweight PET-G, ABS, and PLA+ materials. The primary reason for this choice is since they are more durable and flexible as well as heat-resistant which would be ideal for the nature of battlebots. Furthermore, considering majority of the parts would be created through 3D-printing, we assume that ABS or PEEK filament, which is primarily used for 3D-printers, would be ideal.


# Criterion For Success
Our High-level goal is to maneuver the robot away from the opponent with precision and control. Another goal is to have a horizontal spinning attacking mechanism which is ‘powerful’ enough to knock out robots of other shapes should not just ‘flick’ the other robot but actually make a significant impact to disable the opponent’s robot.

Master Bus Processor

Clay Kaiser, Philip Macias, Richard Mannion

Master Bus Processor

Featured Project

General Description

We will design a Master Bus Processor (MBP) for music production in home studios. The MBP will use a hybrid analog/digital approach to provide both the desirable non-linearities of analog processing and the flexibility of digital control. Our design will be less costly than other audio bus processors so that it is more accessible to our target market of home studio owners. The MBP will be unique in its low cost as well as in its incorporation of a digital hardware control system. This allows for more flexibility and more intuitive controls when compared to other products on the market.

Design Proposal

Our design would contain a core functionality with scalability in added functionality. It would be designed to fit in a 2U rack mount enclosure with distinct boards for digital and analog circuits to allow for easier unit testings and account for digital/analog interference.

The audio processing signal chain would be composed of analog processing 'blocks’--like steps in the signal chain.

The basic analog blocks we would integrate are:

Compressor/limiter modes

EQ with shelf/bell modes

Saturation with symmetrical/asymmetrical modes

Each block’s multiple modes would be controlled by a digital circuit to allow for intuitive mode selection.

The digital circuit will be responsible for:

Mode selection

Analog block sequence

DSP feedback and monitoring of each analog block (REACH GOAL)

The digital circuit will entail a series of buttons to allow the user to easily select which analog block to control and another button to allow the user to scroll between different modes and presets. Another button will allow the user to control sequence of the analog blocks. An LCD display will be used to give the user feedback of the current state of the system when scrolling and selecting particular modes.

Reach Goals

added DSP functionality such as monitoring of the analog functions

Replace Arduino boards for DSP with custom digital control boards using ATmega328 microcontrollers (same as arduino board)

Rack mounted enclosure/marketable design

System Verification

We will qualify the success of the project by how closely its processing performance matches the design intent. Since audio 'quality’ can be highly subjective, we will rely on objective metrics such as Gain Reduction (GR [dB]), Total Harmonic Distortion (THD [%]), and Noise [V] to qualify the analog processing blocks. The digital controls will be qualified by their ability to actuate the correct analog blocks consistently without causing disruptions to the signal chain or interference. Additionally, the hardware user interface will be qualified by ease of use and intuitiveness.

Project Videos