Project

# Title Team Members TA Documents Sponsor
25 Building Interior Reconnaissance Drone (BIRD)
Jack Lavin
Jacob Witek
Mark Viz
Shiyuan Duan design_document1.pdf
final_paper1.pdf
presentation1.pdf
proposal1.pdf
video
# Building interior reconnaissance drone proposal

Team Members:
- Mark Viz (markjv2)
- Jack Lavin (jlavin4)
- Jacob Witek (witek5)

# Problem

There are many situations when law enforcement or emergency medical service professionals need quick, real-time, useful information about a non-visible location without sending in a human to gather this information due to present risks. One of the most important things to know in these situations is if there are people in a room or area, and if so, where they are located. While there are current promising solutions used by these professionals, they can rarely be operated by one person and take away time and manpower from situations which usually greatly require both. Our solution attempts to address these issues while providing an easy-to-use interface with critical information.

# Solution

Our solution to this issue is to use a reconnaissance drone equipped with a camera and other sensing components and simple autonomous behavior capabilities, and process the video feed on a separate laptop to determine an accurate location of all people in view of the drone relative to the location of a phone or viewing device nearby. This phone or viewing device would run an augmented-reality application using position information from the drone system to overlay the positions of people near the drone over first-person perspective video. The end result would allow someone to slide/toss the drone into a room, and after a second or two, be able to "see through the wall" where anyone in the room is.

# Solution Components

## Drone and Sensors

The drone itself will be a basic lightweight quadcopter design. The frame will be constructed using a 2D design cut from a sheet of carbon fiber and assembled with aluminum hardware and thread locks. The total volume including the rotor blades should not exceed 4" H by 8" W by 8" L at maximum (ideally much less). This simple frame will consist of a rectangular section to mount the PCB and a 2S (7.4 V) LiPo pack of about 2" x 2" or less, and four identical limbs mounted to the corners. On each of the four limbs will be brushless DC motors (EMAX XA2212 2-3S) driven by electronic speed controllers from the PCB (assuming they can't be pre-purchased). The PCB will have a two-pin DuPont/JST connectors for battery leads, a TP4056 LiPo discharging circuit, and buck converters for necessary voltage(s) all on the underside. On top, the PCB will house an ESP32-S3 microcontroller, an IMU with decent accuracy, a set of mmWave 24 GHz human presence sensor (like the LD2410) and ultrasonic transducers to form a phase array sensor with an accurate, narrow beam to scan for human presence with range. These components will allow the drone to be programmed with very simple and limited autonomous flight behaviors (fly up 5 feet, spin 360 degrees, land) and properly/safely control itself. The ultrasonic transducers and human sensing radars will be the primary method of determining human presence and mostly calculated on the ESP-32, however additional calculation will need to be made on the AR end with the received data. If time and budget allow, we may also include a small 2 MP or 5 MP camera for WiFi video stream or a composite video camera for an analog video stream as a backup/failsafe to the other sensors.

A working rough breakdown of the expected mass of each component will go as follows:

- 4 hobby motors: ~ 50 grams (based on consumer measurements)
- Carbon fiber frame: ~ 40 grams (estimate based on similar style and sized frames)
- 2S 500 mAh battery: ~30 grams (based on common commercial LiPo product info)
- PCB with MCU & peripherals: ~50 grams (based on measurements of similar boards)
- 10-20 ultrasonic transducers: ~50 grams (based on commercial component info)
- Metal hardware/fasteners & miscellaneous: ~25 grams (accounting for error as well)
- Total mass: ~255 grams
- Total thrust (at 7.6 V 7.3 A): ~2000 grams (from manufacturer ratings)
- Thrust/weight is well over 2.0 and should allow for quick movement and considerable stability along with the improved frame considerations, and also extra room for more weight if needed.

## AR Viewer or Headset

To create a useful augmented-reality display of the collected position data, the simplest way will be to write an app that uses the digital camera and gyroscope/IMU API's of a smart phone to overlay highlighted human position data on a live camera view. We would use the android studio platform to create this custom app which would interface with the data incoming from the drone. Building upon the android API's we would overlay the data to the phone camera. If we have more time to develop one, a headset or AR glasses could make the experience more useful (hands-free) and immersive. We may also use a laptop at this stage to run a server alongside the app for better processing.

# Working Supply List

*some can be found in student self-service, some need to be ordered
- Carbon fiber sheet (find appropriate size and 2-3 mm thick)
- Aluminum machine screws with lock-tite or bolt/nut with locking washer
- 4 EMAX brushless DC motors and mounting hardware
- 4 quadcopter rotor blades
- 2S (7.6 V) 500 mAh LiPo battery
- Custom PCB
- ESP32-S3 chip w/ PCB antenna
- 20 ultrasonic (40 kHz) transducer cans
- 4 mmWave 24 GHz human presence radar sensors
- TP 4056 LiPo Charging IC (find other necessary SMD components)
- DuPont two-pin connector for LiPo charging/discharging (choose whether removable battery design)
- Various SMD LEDs to indicate functionalities or states on PCB
- Voltage buck converter circuit components
- ESC circuit components
- Adafruit Accelerometer

# Criterion For Success

The best criteria for the success of this project is whether our handheld device or headset can effectively communicate human position data of a visually obstructed location to a nearby user within an accuracy of 1-2 meters while still allowing the user to carry out personal tasks. The video feed should be stable with minimal latency as to be effective and usable, and estimated human positions should be updated only when they are positively in view and information about the recency of data should be apparent (maybe a red highlight on new people, yellow on a stale location, and green for a newly updated position).

Resonant Cavity Field Profiler

Salaj Ganesh, Max Goin, Furkan Yazici

Resonant Cavity Field Profiler

Featured Project

# Team Members:

- Max Goin (jgoin2)

- Furkan Yazici (fyazici2)

- Salaj Ganesh (salajg2)

# Problem

We are interested in completing the project proposal submitted by Starfire for designing a device to tune Resonant Cavity Particle Accelerators. We are working with Tom Houlahan, the engineer responsible for the project, and have met with him to discuss the project already.

Resonant Cavity Particle Accelerators require fine control and characterization of their electric field to function correctly. This can be accomplished by pulling a metal bead through the cavities displacing empty volume occupied by the field, resulting in measurable changes to its operation. This is typically done manually, which is very time-consuming (can take up to 2 days).

# Solution

We intend on massively speeding up this process by designing an apparatus to automate the process using a microcontroller and stepper motor driver. This device will move the bead through all 4 cavities of the accelerator while simultaneously making measurements to estimate the current field conditions in response to the bead. This will help technicians properly tune the cavities to obtain optimum performance.

# Solution Components

## MCU:

STM32Fxxx (depending on availability)

Supplies drive signals to a stepper motor to step the metal bead through the 4 quadrants of the RF cavity. Controls a front panel to indicate the current state of the system. Communicates to an external computer to allow the user to set operating conditions and to log position and field intensity data for further analysis.

An MCU with a decent onboard ADC and DAC would be preferred to keep design complexity minimum. Otherwise, high MIPS performance isn’t critical.

## Frequency-Lock Circuitry:

Maintains a drive frequency that is equal to the resonant frequency. A series of op-amps will filter and form a control loop from output signals from the RF front end before sampling by the ADCs. 2 Op-Amps will be required for this task with no specific performance requirements.

## AC/DC Conversion & Regulation:

Takes an AC voltage(120V, 60Hz) from the wall and supplies a stable DC voltage to power MCU and motor driver. Ripple output must meet minimum specifications as stated in the selected MCU datasheet.

## Stepper Drive:

IC to control a stepper motor. There are many options available, for example, a Trinamic TMC2100. Any stepper driver with a decent resolution will work just fine. The stepper motor will not experience large loading, so the part choice can be very flexible.

## ADC/DAC:

Samples feedback signals from the RF front end and outputs the digital signal to MCU. This component may also be built into the MCU.

## Front Panel Indicator:

Displays the system's current state, most likely a couple of LEDs indicating progress/completion of tuning.

## USB Interface:

Establishes communication between the MCU and computer. This component may also be built into the MCU.

## Software:

Logs the data gathered by the MCU for future use over the USB connection. The position of the metal ball and phase shift will be recorded for analysis.

## Test Bed:

We will have a small (~ 1 foot) proof of concept accelerator for the purposes of testing. It will be supplied by Starfire with the required hardware for testing. This can be left in the lab for us to use as needed. The final demonstration will be with a full-size accelerator.

# Criterion For Success:

- Demonstrate successful field characterization within the resonant cavities on a full-sized accelerator.

- Data will be logged on a PC for later use.

- Characterization completion will be faster than current methods.

- The device would not need any input from an operator until completion.

Project Videos