Project

# Title Team Members TA Documents Sponsor
33 HelpMeRecall
Michael Jiang
Sravya Davuluri
William Li
Hossein Ataee design_document2.pdf
proposal3.pdf
# HelpMeRecall

Team Members:
- Sravya Davuluri (sravyad2)
- William Li (wli202)
- Michael Jiang (mbjiang2)

# Problem

Many individuals have difficulty remembering recent activities and completing routine tasks like eating or taking medication.

# Solution

A standalone assistive device that supports activity recall using sensor-gated voice interaction. It allows users to verbally log activities they have completed, and later query if a specific activity has been performed. It uses an onboard microphone and on-device audio processing on a microcontroller to perform keyword detection.

This device is always on and will be verifiable with an LED, but the voice input is only accepted if the device is worn (capacitive touch sensor) and specific words from a limited vocabulary is said to avoid accidental logging. To address the possibility of reduced correct detection of supported keywords, we will have various keywords targeted for an activity. So in the case of taking medicine, it might be medicine, medication, pill, drug, and prescription. This also simplifies the problem and prevents confidence rate issues. To validate a completed action, the action is logged only if an accelerometer detects physical movement around the time in order to reduce false logging. If a voice log is accepted, haptic feedback is provided by the device. Activities are also timestamped and stored in local memory. If the device notes that a specific activity has been completed, it affirms it including the timestamp using an integrated speaker.

The logs reset at midnight automatically since the activities repeat on the daily. There is also an option of a hard reset button to clear logs. There will also be a button to delete the latest log in case of a logging mistake by the user.

# Solution Components

## Subsystem 1: Microcontroller Unit and Controls

Acts as the central unit for logic. Manages the sensor inputs, and executes a finite state machine. The FSM states are start, idle, listening, logging, and replying.

Components: ESP32-S3-WROOM-1

## Subsystem 2: Audio input processing unit

Captures the voice input from the user and performs keyword detection on a limited vocabulary, where each action can be mapped to multiple set keywords to improve detection.

Components: Digital MEMS microphone (INMP441), ESP32-S3-WROOM-1

## Subsystem 3: Sensor gating and activity validation

Uses a capacitive touch sensor and an accelerometer to detect motion, which ensures that voice input is only received and accepted if the device is worn and recent movement is detected by the accelerometer instead of continuous voice recognition. A "cooldown" period is enforced where the microphone will be disabled for 10 seconds if there's motion but no logging during the listening period multiple times in a row to help conserve some battery.

Components: Capacitive touch sensor (AT42QT1010), Accelerometer (MPU-6050)

## Subsystem 4: Feedback and Output

Uses a speaker for audio feedback as a response to the user’s query. This subsystem also provides haptic feedback as an indication of an accepted user voice log. To indicate if the device is on, the LED is green. If the device is listening, the LED is yellow. If the device is low on power, the LED will be red.

Components: Speaker (8 ohm speaker), amplifier (MAX98357A), coin vibration motor, transistor (2N3904), RGB LED

## Subsystem 5: Time logging and local storage

Stores the activity voice logs along with timestamps. Allows automatic reset at midnight to support daily repetitive tasks. Timekeeping is done using ESP32’s internal RTC.

Components: ESP32-S3-WROOM-1

## Subsystem 6: Power

Supplies power to the device.

Components: Battery (Li-Po battery)

# Criterion For Success
- Correctly detects supported keywords with an accuracy of at least 80% in a quiet environment
- Device will only log upon verifying physical activity and hearing a keyword from the user within a 5 second window
- Upon successful logging, the speaker will output audibly and haptic feedback can be felt by the user with a 2 second vibration
- While querying logs, speaker will output and LED will be solid
- Logs will be automatically cleared at midnight and can be manually reset with the reset button
- Latest log will be deleted upon pushing a separate button
- LED stays solid while device is powered
- False log rate < 1 per hour in normal conversation when worn.

Control System and User Interface for Hydraulic Bike

Iain Brearton

Featured Project

Parker-Hannifin, a fluid power systems company, hosts an annual competition for the design of a chainless bicycle. A MechSE senior design team of mechanical engineers have created a hydraulic circuit with electromechanical valves, but need a control system, user interface, and electrical power for their system. The user would be able to choose between several operating modes (fluid paths), listed at the end.

My solution to this problem is a custom-designed control system and user interface. Based on sensor feedback and user inputs, the system would change operating modes (fluid paths). Additionally, the system could be improved to suggest the best operating mode by implementing a PI or PID controller. The system would not change modes without user interaction due to safety - previous years' bicycles have gone faster than 20mph.

Previous approaches to this problem have usually not included an electrical engineer. As a result, several teams have historically used commercially-available systems such as Parker's IQAN system (link below) or discrete logic due to a lack of technical knowledge (link below). Apart from these two examples, very little public documentation exists on the electrical control systems used by previous competitors, but I believe that designing a control system and user interface from scratch will be a unique and new approach to controlling the hydraulic system.

I am aiming for a 1-person team as there are 6 MechSE counterparts. I emailed Professor Carney on 10/3/14 and he thought the general concept was acceptable.

Operating modes, simplified:

Direct drive (rider's pedaling power goes directly to hydraulic motor)

Coasting (no power input, motor input and output "shorted")

Charge accumulators (store energy in expanding rubber balloons)

Discharge accumulators (use stored energy to supply power to motor)

Regenerative braking (use motor energy to charge accumulators)

Download Competition Specs: https://uofi.box.com/shared/static/gst4s78tcdmfnwpjmf9hkvuzlu8jf771.pdf

Team using IQAN system (top right corner): https://engineering.purdue.edu/ABE/InfoFor/CurrentStudents/SeniorProjects/2012/GeskeLamneckSparenbergEtAl

Team using discrete logic (page 19): http://deepblue.lib.umich.edu/bitstream/handle/2027.42/86206/ME450?sequence=1