Project

# Title Team Members TA Documents Sponsor
5 Running Cadence Monitor Belt
 Alex Jin
Dante Vasudevan
Nick Bergerhouse
 Koushik Udayachandran design_document2.pdf
final_paper1.pdf
other1.pdf
photo1.png
presentation1.pdf
proposal2.pdf
video
Team Members:
- Nick Bergerhouse (ncb7)
- Dante Vasudevan (dgv2)
- Alexander Jin (amjin2)

# Problem
Running cadence is the number of steps a runner takes per minute while running, commonly measured in strides per minute (SPM). It is a useful measurement for runners as it can provide insight into efficiency, form, and stride length. An ideal cadence for most runners typically falls into the range of 170 to 180 SPM although this is dependent on height and pace.

Currently there are already products on the market that can measure running cadence. For example, most “running watches” have cadence as an included measurement. However, it can be cumbersome for runners to constantly be switching through display screens to monitor multiple data points at the same time such as pace, heart rate, distance, cadence. Furthermore, unless a runner is running with their arm locked in front of them, continuous monitoring of cadence is impossible with a running watch. Other products take a different approach such as the foot-mounted ARION Footpod non-GPS 1.0 and Stryd. These products can track the cadence over the duration of the run in much the same way that a running watch would, but they don’t have the ability to provide that information to the runner without the use of a watch or smartphone.

In both the watch and foot-mounted solution, there is a lack of a product that provides easy, hands-free haptic feedback to the runner informing them when their cadence falls outside of the ideal cadence range.

# Solution

Our design will consist of a lightweight, belt-mounted device consisting of several PCBs that utilizes an IMU for the purposes of step detection. A running mean time between a certain number of previous steps will be used to calculate the runner’s current cadence. Based on the measured cadence, the microcontroller will control vibration motors to create haptic feedback, which will inform the user based on vibration patterns in real time how to adjust their cadence to achieve perfect running efficiency. The device itself will be mounted on the user’s back, as this is already a popular spot for runners to store items, such as phone mounts or fanny packs. This also increases user comfort by keeping the device clear of the front and sides, where there may be hand movement. The system will be powered by a mobile battery, such as a LiPo battery, that is also connected to the belt.

Our solution also offers user customization. Users can adjust their target cadence from the default 180 to any lower target cadence they want. Users will also be able to adjust the strength of the feedback from the haptic motors.

# Solution Components

**Step Measurement (IMU)**

The Step Measurement board will house the IMU which actually does the detecting in our system. We have tentatively selected the BNO08X family as our IMU. The board will contain the necessary peripheral components, such as pullups/downs, capacitors, etc.

BNO08X Family:
(small differences in power consumption, calibration, cost.)
https://www.digikey.com/en/products/detail/ceva-technologies-inc/BNO085/9445940
https://www.digikey.com/en/products/detail/ceva-technologies-inc/BNO086/14114190

**Microcontroller**

The Microcontroller board will house the microcontroller itself as well as the power supply subsystem. There may need to be several voltage regulators as small regulators (to accomplish our unintrusive, lightweight and compact design) generally have low power output. We have tentatively selected the AP2112K-3.3TRG1 as our voltage regulator.

We will be integrating a ESP32-C6-WROOM-1-N8 engineering module onto a custom PCB with the required peripherals to configure it, such as basic resistors, capacitors, or diodes. It should also allow it to be programmed from a computer with a Micro-USB or USB-C port,and allow it to be wired to communicate with both the Haptic Feedback board and the Step Measurement board. Inter-board communication will be accomplished with either ribbon cables or jumper wires, depending on the feasibility of physically grouping required signals onto a header on the PCB.

ESP32-C6-WROOM-1-N8:
https://www.adafruit.com/product/5671

AP2112K-3.3TRG1:
https://www.digikey.com/en/products/detail/diodes-incorporated/AP2112K-3-3TRG1/4470746

**Haptic Feedback**

The Haptic Feedback board will consist of a 2N7002ET7G BJT to allow microcontroller control of the Seeed 316040001 vibrating disk motor we will use to provide haptic feedback. This board will also most likely have its own voltage regulator due to avoiding having any motor power consumption interfere with the microcontroller’s operation. In addition, two low-profile tactile switches will be present on this board to control the desired target cadence and vibration intensity of the system. Their inclusion on this board specifically allows the user to access the controls right next to the source of haptic feedback, allowing convenient location of control. An example low-profile button, the PTS526 SM15 SMTR2 LFS, has been linked. The software on the microcontroller will interpret actions such as holding the button, singular presses, or double presses into commands. The button does not have to be this specific part.

Seeed 316040001:
https://www.digikey.com/en/products/detail/seeed-technology-co.,-ltd/316040001/5487672

2N7002ET7G:
https://www.digikey.com/en/products/detail/onsemi/2N7002ET7G/13886993

PTS526 SM15 SMTR2 LFS:
https://www.digikey.com/en/products/detail/c&k/PTS526%2520SM15%2520SMTR2%2520LFS/10056633



# Reach Goal: Phone Bluetooth Connectivity + App for improved user experience

Our reach goal utilizes the ESP32 module’s built-in bluetooth antenna to connect with the user's phone. We will develop an app which will work with our device to provide an improved user experience. This app can control the phone’s vibration to provide an alternative source of haptic feedback to the user, provide advanced customization capabilities including the cadence target range and feedback strength, and can track analytics such as the percentage of the run within the desired cadence range.

This reach goal can be implemented as an addendum to an already completed device. It is all software implementation; we would need to build the app and modify the arduino code on the ESP32 module.

# Criterion For Success

- The product must accurately measure cadence of the user.
- Vibration motors must activate when cadence becomes too low or high relative to target cadence.
- The device must be able to recognize when the user is not running, and will pause counting accordingly.
- The product should comfortably fit on the waistline of the runner.
- The target cadence and vibration strength of the product must be user adjustable.
- The product must be able to run off a battery power source.

Cloud-controlled quadcopter

Anuraag Vankayala, Amrutha Vasili

Cloud-controlled quadcopter

Featured Project

Idea:

To build a GPS-assisted, cloud-controlled quadcopter, for consumer-friendly aerial photography.

Design/Build:

We will be building a quad from the frame up. The four motors will each have electronic speed controllers,to balance and handle control inputs received from an 8-bit microcontroller(AP),required for its flight. The firmware will be tweaked slightly to allow flight modes that our project specifically requires. A companion computer such as the Erle Brain will be connected to the AP and to the cloud(EC2). We will build a codebase for the flight controller to navigate the quad. This would involve sending messages as per the MAVLink spec for sUAS between the companion computer and the AP to poll sensor data , voltage information , etc. The companion computer will also talk to the cloud via a UDP port to receive requests and process them via our code. Users make requests for media capture via a phone app that talks to the cloud via an internet connection.

Why is it worth doing:

There is currently no consumer-friendly solution that provides or lets anyone capture aerial photographs of them/their family/a nearby event via a simple tap on a phone. In fact, present day off-the-shelf alternatives offer relatively expensive solutions that require owning and carrying bulky equipment such as the quads/remotes. Our idea allows for safe and responsible use of drones as our proposed solution is autonomous, has several safety features, is context aware(terrain information , no fly zones , NOTAMs , etc.) and integrates with the federal airspace seamlessly.

End Product:

Quads that are ready for the connected world and are capable to fly autonomously, from the user standpoint, and can perform maneuvers safely with a very simplistic UI for the common user. Specifically, quads which are deployed on user's demand, without the hassle of ownership.

Similar products and comparison:

Current solutions include RTF (ready to fly) quads such as the DJI Phantom and the Kickstarter project, Lily,that are heavily user-dependent or user-centric.The Phantom requires you to carry a bulky remote with multiple antennas. Moreover,the flight radius could be reduced by interference from nearby conditions.Lily requires the user to carry a tracking device on them. You can not have Lily shoot a subject that is not you. Lily can have a maximum altitude of 15 m above you and that is below the tree line,prone to crashes.

Our solution differs in several ways.Our solution intends to be location and/or event-centric. We propose that the users need not own quads and user can capture a moment with a phone.As long as any of the users are in the service area and the weather conditions are permissible, safety and knowledge of controlling the quad are all abstracted. The only question left to the user is what should be in the picture at a given time.

Project Videos