Project

# Title Team Members TA Documents Sponsor
10 OmniSense-Dual — Dual-Wearable 360° Blind-Spot Detection, Directional Haptic Hazard Alerts, and Belly-Based Navigation for Pedestrian Safety
 Alex Jin
Jiateng Ma
Simon Xia
 Wesley Pang design_document1.pdf
proposal1.pdf
Team Members:
- Simon Xia (hx17)
- Jiateng Ma (jiateng4)
- Alex Jin (jin50)

**1. Problem Statement**
Pedestrians in urban and campus environments frequently share space with bicycles, e-scooters, cars, and other pedestrians approaching from all directions. Unlike drivers, who benefit from mirrors and active driver-assistance systems, pedestrians have:
- Unprotected blind spots
Fast-approaching objects from behind or from diagonal sectors are often perceived too late, especially on shared bike/pedestrian paths and narrow sidewalks.
- Reduced situational awareness
Headphones, smartphones, and other distractions degrade auditory and visual awareness, making it harder to detect hazards or notice subtle visual cues.
- Navigation burden
Outdoor and indoor navigation typically depend on visually checking a smartphone map or listening to voice guidance. Both approaches demand attention, occupy hands or ears, and can themselves be unsafe in traffic or crowded environments. For visually impaired users, relying solely on audio is also not ideal.

Existing systems (smartphone maps, voice navigation, cycling radars, blind canes) each address part of the problem but do not provide integrated 360° safety sensing plus hands-free navigation with clear separation of meaning.

**2. Solution Overview**
We propose OmniSense-Dual, a dual-wearable system consisting of:
- A waist/belly-mounted sensing, compute, and navigation haptic module, and
- A head-mounted sensing + haptic hazard alert module

Key design choice:
- Head channel = hazard alerts only
- Belly channel = navigation cues only

This cleanly separates “something is dangerous around you” from “where you should go.”

Core functions:

- 360° Blind-Spot Hazard Awareness
The belly module uses mmWave and ToF/ultrasonic sensors to detect approaching objects around the torso. The head module provides an additional sensing plane for head-level obstacles. When a hazard is detected, the headband vibrates on the corresponding side/direction, signaling an urgent warning.
Hands-Free Navigation
- A smartphone app provides waypoints (outdoor via GPS; optionally indoor via BLE/UWB). The belly module fuses waypoints with IMU heading and encodes navigation instructions as gentle vibration patterns on the belly module (e.g., left side of belt = turn left soon). Navigation never uses the head motors, so it cannot be confused with hazard alerts.

OmniSense-Dual is designed for campus walking, urban commuting, and accessibility support, with a strong emphasis on non-visual, non-auditory, and clearly distinguishable feedback.

**3. Solution Components**
**Component A: Waist/Belly Perception & Compute Module**
Placement:
Worn around waist or belly using elastic belt.
Sensors:
- Rear + Rear-Diagonal (L/R): mmWave radar (60 GHz)
- Left + Right: ToF (e.g., VL53 series) or ultrasonic
- Front-Lower: ToF/IR for low obstacles (curbs, poles, steps)

Functions:
- Provides 360° sensing at waist plane
- Detects moving vs static obstacles
- Includes 6-DoF IMU for heading + gait
- Includes battery + charger + regulators
- Belly haptics used only for navigation

**Component B: Head-Mounted Hazard Alert Module**
Placement:
Headband, cap insert, or lightweight strap.
Haptic Feedback:
8 directional motors placed at:
- Front (0°)
- Front-Left (45°)
- Left (90°)
- Rear-Left (135°)
- Rear (180°)
- Rear-Right (225°)
- Right (270°)
- Front-Right (315°)

Electronics:
- Small BLE SoC/MCU
- Optional short-range ToF for head-height obstacles
- Small battery or wired power from belt

Role:
- Only hazard alerts
- No navigation patterns

**Component C: Navigation & Belly Haptic Interface**
Input Source:
Phone provides route via GPS (outdoor) or BLE/UWB (indoor).
Processing on Belt Module:
- Receives desired bearing from phone
- Computes angle difference using IMU
- Triggers haptic cue on belt

**Component D: Safety Hazard Logic**
Inputs:
- mmWave + ToF/ultrasonic
- Optional head ToF
- IMU heading

Hazards Detected:
- Approaching fast objects (bike, scooter)
- Sudden close static obstacles
- Rear or diagonal intrusion
- Low objects in walking path

Head Feedback Patterns (Hazard Only):
- Default hazard → strong 0.5–1.0s pulse in correct motor direction
- High severity → repeated strong pulses
- Multiple hazards → priority by time-to-collision

**Component E: Electronics & PCB**
Belly PCB Includes:
- MCU (e.g., STM32H7 or ESP32-S3)
- Sensor interfaces (mmWave, ToF, IMU)
- BLE for phone + headband
- Haptic drivers for belt motors
- Li-ion charging + regulation

Head PCB Includes:
- BLE SoC (e.g., nRF52832/ESP32-C3-Mini)
- 8 motor drivers (directional)
- Optional ToF
- Small battery or connector

**4. Criterion for Success**
Safety
- Detect bikes/scooters ≥ 5 m away with ≥90% recall
- Head direction correctness ≥90%
- Alert latency ≤250 ms
- Dual-plane sensing reduces occlusion misses ≥30%

Navigation
- Turn accuracy using belly haptics ≥85%
- Heading deviation during “straight” ≤10°
- Navigation update latency ≤200 ms

Channel Separation
- Head = hazard, belly = navigation
- User classification accuracy (hazard vs nav) ≥90%

Usability
- Battery life ≥4 hours
- Total mass ≤350 g (head ≤150 g)

RFA: Any-Screen to Touch-Screen Device

Ganesh Arunachalam, Sakhi Yunalfian

Featured Project

# Any-Screen to Touch-Screen Device

Team Members:

\- Sakhi Yunalfian (sfy2)

\- Muthu Arunachalam (muthuga2)

\- Zhengjie Fan (zfan11)

# Problem

While touchscreens are becoming increasingly popular, not all screens come equipped with touch capabilities. Upgrading or replacing non-touch displays with touch-enabled ones can be costly and impractical. Users need an affordable and portable solution that can turn any screen into a fully functional touchscreen.

# Solution

The any-screen-to-touch-screen device uses four ultra-wideband sensors attached to the four corners of a screen to detect the position of a specially designed pen or hand wearable. Ultrawideband (UWB) is a positioning technology that is lower-cost than Lidar/Camera yet more accurate than Bluetooth/Wifi/RFID. Since UWB is highly accurate we will use these sensors to track the location of a UWB antenna (placed in the pen). In addition to the UWB tag, the pen will also feature a touch-sensitive tip to detect contact with the screen (along with a redundant button to simulate screen contact if the user prefers to not constantly make contact with the screen). The pen will also have a gyroscope and low profile buttons to track tilt data and offer customizable hotkeys/shortcuts. The pen and sensors communicate wirelessly with the microcontroller which converts the pen’s input data along with its location on the screen into touchscreen-like interactions.

# Solution Components

## Location Sensing Subsystem (Hardware)

This subsystem will employ Spark Microsystems SR1010 digitally programmable ultra-wideband wireless transceiver. The transceiver will be housed in a enclosure that can be attached to the corners of a screen or monitor. Each sensor unit will also need a bluetooth module in order to communicate with the microcontroller.

## Signal Processing Subsystem (Hardware and Software)

A microcontroller, specifically the STM32F4 series microcontroller (STM32F407 or STM32F429). Real-time sensor data processing takes away a considerable amount of computing power. The STM32F4 series contain DSP instructions that allow a smoother way to perform raw data processing and noise reduction. This subsystem will allow us to perform triangulation to accurately estimate the location on the screen, smooth real-time data processing, latency minimization, sensitivity, and noise reduction.

A bluetooth module, in order for the sensor to send its raw data to the microcontroller. We are planning to make the communication between the sensors and the pen to the microcontroller to be wireless. One bluetooth module we are considering is the HC05 bluetooth module.

The microcontroller itself will be wired to the relevant computer system via USB 2.0 for data transfer of touchscreen interactions.

## Pen/Hand Wearable Subsystem (Hardware)

The pen subsystem will employ a simple spring switch as a pen tip to detect pen to screen contact. We will also use a Sparkfun DEV-08776 Lilypad button to simulate a press/pen-to-screen contact for redundancy and if the user wishes to control the pen without contact to the screen. The pen will also contain several low profile buttons and a STMicroelectronics LSM6DSO32TR gyroscope/accelerator sensor to provide further customizable pen functionality and potentially aid in motion tracking calculations. The pen will contain a Taoglas UWC.01 ultra-wideband tag to allow detection by the location sensing subsystem and a bluetooth module to allow communication with the microcontroller. The unit will need to be enclosed within a plastic or 3D printed housing.

## Touch Screen Emulation Subsystem (Software)

A microcontroller with embedded HID device functionalities in order to control mouse cursors of a specific device connected to it. We are planning to utilize the STM32F4 series microcontroller with built in USB HID libraries to help emulating the touch screen effects. We will also include a simple GUI to allow the user to customize the shortcuts mapped to the pen buttons and specify optional parameters like screen resolution, screen curve, etc.

## Power Subsystem (Hardware)

The power subsystem is not localized in one area since our solution consists of multiple wireless devices, however we specify all power requirements and solutions here for organization purposes.

For the wireless sensors in our location sensing subsystem, we plan on using battery power. Given the UWB transceiver has ultra-low power consumption and an internal DC-DC converter, it makes sense to power each sensor unit with a small 3.3V 650mAh rechargeable battery (potential option: [https://a.co/d/acFLsSu](https://a.co/d/acFLsSu)). We will include recharging capability and micro usb recharging port.

For our pen, we plan on using battery power too. The gyroscope module, UWB antenna, and bluetooth module all have low-power consumption so we plan on using the same rechargeable battery system as specified above.

The microcontroller will be wired via USB 2.0 directly to the computer subsystem in order to transmit mouse data/touchscreen interaction and will receive 5V 0.9A power supply through this connection.

# Criterion For Success

## Hardware

The UWB sensor system is able to track the pens location on the screen.

The pen is able to detect clicks, screen contact, and tilt.

The microcontroller is able to take input from the wireless pen and the wireless sensors.

Each battery-powered unit is successfully powered and able to be charged.

## Software

The pen’s input and sensor location data can be converted to mouse clicks and presses.

The pen’s buttons can be mapped to customizable shortcuts/hotkeys.

## Accuracy and Responsiveness

Touch detection and location accuracy is the most crucial criteria for our project’s success. We expect our device to have a 95% touch detection precision. In order to correctly control embedded HID protocols of a device, the data sent and processed by the microcontroller to the device has to have a low error threshold when comparing cursor movements with wearable location.

Touch recognition and responsiveness is the next most important thing. We want our system, by a certain distance threshold, able to detect the device with a relatively low margin of error of about 1% or less. More specifically, this criteria for success is the conclusion to see if our communication network protocol between the sensors, USB HID peripherals, and the microcontroller are able to efficiently transfer data in real-time for the device to interpret these data in a form of cursor location updates, scrolls, clicks, and more.

Latency and lags should have a time interval of less than 60 millisecond. This will be judged based on the DSP pipeline formed in the STM32F4 microcontroller.

## Reliability and Simplicity

We want our device to be easily usable for the users. It should be intuitive and straightforward to start the device and utilize its functionalities.

We want our device to also be durable in the sense of low chances of battery failures, mechanical failures, and systematic degradations.

## Integration and Compatibility

We want our device to be able to be integrated with any type of screens of different architectural measurements and operating systems.

Project Videos