Project

# Title Team Members TA Documents Sponsor
15 Clogged Gutter Detector
Aryan Kataria
Eric Zhou
Nyle Raina
Jianchong Chen design_document1.pdf
proposal1.pdf
# Clogged Gutter Detector

Team Members:
- Aryan Kataria - akata5
- Nyle Raina - nrain3
- TBD - netid

# Problem

Homeowners have no easy way to know when their gutters are clogged with leaves or standing water until they overflow, which can cause damage to foundation or roofing. Checking them proactively requires repeatedly climbing a ladder, which is dangerous and annoying. A low-maintenance, automated monitoring solution is needed to alert users before damage occurs.

# Solution

We plan to create a small, weather-resistant PCB node that mounts next to the gutter's primary downspout. It will use a rain sensor to detect active precipitation and a flow sensor to detect water moving down the spout. If it is raining but there is no water flow, the system will recognize the gutter is clogged. To avoid the need for battery replacements, the board will feature a solar trickle-charging circuit. It will utilize an ESP32 microcontroller that stays in deep sleep most of the time, waking up periodically to take readings and transmit the data to a cloud dashboard.

# Solution Components

## Microcontroller Subsystem

This part handles the logic, sleep cycles, and wireless transmission. We will use an **ESP32-WROOM-32E** module because it has low-power deep sleep capabilities and built-in Wi-Fi to upload the sensor data to our backend.

## Sensor Subsystem

This subsystem detects active rain and monitors water clearing through the downspout to infer a clog.
* **Precipitation Sensor:** We will use a resistive rain sensor board on the top of the enclosure. This will detect when it is actively raining and wake the ESP32.
* **Flow Sensor:** We will mount a Hall-effect water flow sensor (like the YF-S201) at the top of the downspout. If the rain sensor detects water but the flow sensor registers zero movement, the system infers a clog.

## Power Subsystem

This subsystem makes sure the board can run on its own outside.
* **Charge Controller:** We will use a **Microchip MCP73871** charge controller to trickle power from a small 5V solar panel into a standard **18650 Lithium-Ion battery**.
* **Voltage Regulation:** A **Texas Instruments TLV70033** 3.3V regulator will step down the battery voltage to provide a safe, steady 3.3V to the ESP32.

# Criterion For Success

1. The precipitation sensor must output an analog signal that wakes the ESP32 from deep sleep within 10 seconds of active rainfall.
2. The Hall-effect flow sensor must output a reliable pulse signal that the ESP32 can read to accurately detect water movement in the downspout.
3. The power circuit must successfully provide charging current to the 18650 battery when the solar panel is under a bright light, while the regulator outputs a stable 3.3V.
4. The ESP32 must successfully execute its logic check (Rain = True, Flow = False), connect to a 2.4GHz Wi-Fi network, send a JSON alert packet to a test server, and go back to sleep in under 10 seconds.

Antweight Combat Robot

Ryan Middendorf, Teodor Tchalakov

Antweight Combat Robot

Featured Project

Antweight Combat Robot

Team Members:

Ryan Middendorf (ryanjm8),

Teodor Tchalakov (ttcha2)

Problem

The constraints for Professor Gruev’s competition are as follows:

Must weigh less than 2 lbs

Must be 3D printed in PET(G), ABS, or PLA(+)

Must have controlled movement

Must be controlled over bluetooth or wifi by a PC

Must have a fighting tool to use against other bots

The main challenges involved in this are making a custom control solution and designing a combat robot that will not only survive the 2 minute matches but actually win them by immobilizing the other robot.

Solution

To meet these constraints, we plan to create a custom PCB that contains 3 brushless electronic speed controllers (ESCs) to control the drive and weapon motors and uses a microcontroller to communicate with a PC over bluetooth and control the robot. For the actual robot design we plan to build a vertical spinner which usually performs best in this weight class. The "tool" will be spun by a brushless motor, and so will both sides drive wheels.

Subsystem 1 - Custom PCB and Power

Our first subsystem will be the custom PCB. It has to contain 3 brushless ESCs and interface with a bluetooth enabled microcontroller such as an ESP32 or STM32 that will receive instructions from a PC and turn them into usable PWM signals for the ESCs. It will also have to be powered by a LiPo battery through an XC30 connector and include an integrated screw switch so the robot can be turned on and off simply and safely.

Subsystem 2 - Drive train

Our second subsystem will be the drive train. Our robot will be driven by 2 brushless motors, 1 on each side. Each motor will drive 2 wheels that are connected by a belt so the robot will have a simplified 4 wheel drive in a tank drive configuration.

Subsystem 3 - Weapon/Tool Assembly

Our third subsystem will be the weapon/tool assembly. Our tool will be a robust vertical spinner, most likely a drum/eggbeater style. This type of tool has a lot of success in combat robotics due to its ability to dissipate the force of hitting an opponent into the floor very efficiently. This will be driven by a substantially larger brushless motor than the drive system so it can deliver much more powerful hits.

Subsystem 4 - Chassis

Our fourth subsystem will be the chassis. The chassis has to be very robust and able to withstand all the damage that will be dealt to it throughout a match. It also has to be able to contain all the electronics and prevent them from being damaged. The chassis will be 3D printed out of one of the approved materials listed above but most likely PLA+.

Subsystem 5 - Controlling from PC

Our fifth and final subsystem will be how our robot is controlled by a PC. This will be a program run locally on a PC that takes keyboard inputs and transforms them into instructions that are sent to the microcontroller inside the robot to control it.

Criterion for Success

We would consider our project a success if we are able to communicate with the robot from our computer and successfully drive it around the arena during a match. The commands sent from the pc need to be processed by the microcontroller and the motors need to be powered properly and behave correctly during a match. The robot will also have to be able to shut itself off if the bluetooth gets disconnected for some reason.