Project

# Title Team Members TA Documents Sponsor
45 Focus Dial: A Tactile Hardware Interface for Distraction-Free Focus
Ahan Goel
Amogh Mehta
Benjamin Loo
video
video
**Team Members:**
- Amogh Mehta (amoghm3)
- Ahan Goel (ahang5)
- Benjamin Loo (bloo2)

---

# Problem

Staying focused is increasingly difficult in an environment saturated with digital distractions. While most modern operating systems provide tools such as Focus Mode or Do Not Disturb, these solutions are embedded within smartphones or computers themselves. Activating or managing them often requires unlocking a phone, navigating menus, or interacting with the very device that causes distraction. This creates friction and makes it easy for users to abandon focus unintentionally.

Additionally, many existing productivity tools rely heavily on cloud services or voice assistants, raising concerns around privacy, reliability, and latency. There is a need for a more intentional, low-friction, and privacy-conscious way to manage focus that does not require constant screen interaction.

---

# Solution

We propose the **Focus Dial**, a standalone hardware controller that allows users to enter, manage, and visualize focus states through a simple physical interaction. By turning a rotary dial, users can activate focus modes, set timers, and receive feedback without opening a phone or navigating software menus.

The Focus Dial solves the problem by shifting distraction management from a screen-based interaction to a tactile, human-centered interface. The device communicates wirelessly with user devices (phones, tablets, and computers) to control Focus Mode or Do Not Disturb settings. In addition, the Focus Dial is designed to integrate with IoT devices on the local network, enabling environmental cues—such as smart lights, displays, or other connected devices—to reflect or respond to the user’s focus state.

At a high level, the system consists of:
- A physical user interface for intentional user input and feedback
- An embedded processing and communication subsystem
- Wireless integration with user devices and local IoT systems

---

# Solution Components

## Subsystem 1: Physical User Interface and Feedback

**Purpose:**
Functions as the primary **physical user interface**, allowing users to intentionally control focus modes and timers without interacting with screen-based devices.

**Function:**
This subsystem combines tactile input and multimodal feedback mechanisms to provide intuitive control and clear system state indication. It is composed of the following hardware elements:

- **Rotary Position Encoding:**
A rotary encoder detects rotational direction and position, enabling users to select focus modes, adjust durations, and confirm actions through deliberate physical motion.

- **Haptic Feedback:**
A vibration motor provides tactile confirmation for actions such as mode changes, timer start/stop events, and alerts, reinforcing interaction without requiring visual attention.

- **OLED/LCD Display:**
A circular OLED or LCD display presents contextual information such as the active focus mode, remaining time, or system status.

- **Lighting (LED Ring):**
An addressable LED ring provides glanceable visual feedback by indicating focus state, progress, or alerts through color and animation. The lighting can also mirror or augment connected IoT lighting systems.

**Components:**
- Rotary encoder with push-button (e.g., Bourns PEC11 series)
- Circular OLED or LCD display (e.g., 1.28\" round TFT display)
- Addressable LED ring (e.g., WS2812B / NeoPixel ring)
- Coin vibration motor

---

## Subsystem 2: Embedded Processing and Wireless Communication

**Purpose:**
Acts as the **central control unit**, coordinating input processing, system state management, and communication between subsystems and external devices.

**Function:**
Processes rotary encoder input, drives output peripherals (display, LEDs, haptics), and manages wireless communication protocols.

**Components:**
- Microcontroller with integrated Bluetooth and Wi-Fi (e.g., ESP32)
- Power management circuitry
- On-board memory for firmware and configuration storage

---

## Subsystem 3: Device and IoT Integration

**Purpose:**
Enables the Focus Dial to operate as a **local control hub**, synchronizing focus states across personal devices and connected IoT systems.

**Function:**
Transmits focus state changes to paired devices and triggers context-aware environmental responses.

**Components / Interfaces:**
- Bluetooth Low Energy (BLE) for communicating with a companion app or OS-level shortcuts
- Wi-Fi for local network communication
- Integration with IoT devices (e.g., smart lights, displays, or other networked devices) using local protocols such as MQTT or HTTP

This subsystem allows the Focus Dial to trigger actions such as dimming lights, changing light color, or notifying other devices when a focus session starts or ends.

---

# Criterion for Success

The project will be considered successful if it meets the following measurable criteria:

1. The rotary encoder reliably detects user input with greater than 95% accuracy.
2. The device activates or deactivates Focus Mode or Do Not Disturb on a paired device via Bluetooth within 1 second of user input.
3. The display, LED lighting, and haptic feedback consistently reflect the correct focus state.
4. The Focus Dial successfully communicates focus state changes to at least one IoT device on the local network.
5. Core functionality operates without requiring an active internet connection.

---

**Project Classification:** Innovation (human-centered hardware interface integrating embedded systems, wireless communication, and IoT interaction)

ATTITUDE DETERMINATION AND CONTROL MODULE FOR UIUC NANOSATELLITES

Shamith Achanta, Rick Eason, Srikar Nalamalapu

Featured Project

Team Members:

- Rick Eason (reason2)

- Srikar Nalamalapu (svn3)

- Shamith Achanta (shamith2)

# Problem

The Aerospace Engineering department's Laboratory for Advanced Space Systems at Illinois (LASSI) develops nanosatellites for the University of Illinois. Their next-generation satellite architecture is currently in development, however the core bus does not contain an Attitude Determination and Control (ADCS) system.

In order for an ADCS system to be useful to LASSI, the system must be compliant with their modular spacecraft bus architecture.

# Solution

Design, build, and test an IlliniSat-0 spec compliant ADCS module. This requires being able to:

- Sense and process the Earth's weak magnetic field as it passes through the module.

- Sense and process the spacecraft body's <30 dps rotation rate.

- Execute control algorithms to command magnetorquer coil current drivers.

- Drive current through magnetorquer coils.

As well as being compliant to LASSI specification for:

- Mechanical design.

- Electrical power interfaces.

- Serial data interfaces.

- Material properties.

- Serial communications protocol.

# Solution Components

## Sensing

Using the Rohm BM1422AGMV 3-axis magnetometer we can accurately sense 0.042 microTesla per LSB, which gives very good overhead for sensing Earth's field. Furthermore, this sensor is designed for use in wearable electronics as a compass, so it also contains programable low-pass filters. This will reduce MCU processing load.

Using the Bosch BMI270 3-axis gyroscope we can accurately sense rotation rate at between ~16 and ~260 LSB per dps, which gives very good overhead to sense low-rate rotation of the spacecraft body. This sensor also contains a programable low-pass filter, which will help reduce MCU processing load.

Both sensors will communicate over I2C to the MCU.

## Serial Communications

The LASSI spec for this module requires the inclusion of the following serial communications processes:

- CAN-FD

- RS422

- Differential I2C

The CAN-FD interface is provided from the STM-32 MCU through a SN65HVD234-Q1 transceiver. It supports all CAN speeds and is used on all other devices on the CAN bus, providing increased reliability.

The RS422 interface is provided through GPIO from the STM-32 MCU and uses the TI THVD1451 transceiver. RS422 is a twisted-pair differential serial interface that provides high noise rejection and high data rates.

The Differential I2C is provided by a specialized transceiver from NXP, which allows I2C to be used reliably in high-noise and board-to-board situations. The device is the PCA9615.

I2C between the sensors and the MCU is provided by the GPIO on the MCU and does not require a transceiver.

## MCU

The MCU will be an STM32L552, exact variant and package is TBD due to parts availability. This MCU provides significant processing power, good GPIO, and excellent build and development tools. Firmware will be written in either C or Rust, depending on some initial testing.

We have access to debugging and flashing tools that are compatible with this MCU.

## Magnetics Coils and Constant Current Drivers

We are going to wind our own copper wire around coil mandrels to produce magnetorquers that are useful geometries for the device. A 3d printed mandrel will be designed and produced for each of the three coils. We do not believe this to be a significant risk of project failure because the geometries involved are extremely simple and the coil does not need to be extremely precise. Mounting of the coils to the board will be handled by 3d printed clips that we will design. The coils will be soldered into the board through plated through-holes.

Driving the inductors will be the MAX8560 500mA buck converter. This converter allows the MCU to toggle the activity of the individual coils separately through GPIO pins, as well as good soft-start characteristics for the large current draw of the coils.

## Board Design

This project requires significant work in the board layout phase. A 4-layer PCB is anticipated and due to LASSI compliance requirements the board outline, mounting hole placement, part keep-out zones, and a large stack-through connector (Samtec ERM/F-8) are already defined.

Unless constrained by part availability or required for other reasons, all parts will be SMD and will be selected for minimum footprint area.

# Criterion For Success

Success for our project will be broken into several parts:

- Electronics

- Firmware

- Compatibility

Compatibility success is the easiest to test. The device must be compatible with LASSI specifications for IlliniSat-0 modules. This is verifiable through mechanical measurement, board design review, and integration with other test articles.

Firmware success will be determined by meeting the following criteria:

- The capability to initialize, configure, and read accurate data from the IMU sensors. This is a test of I2C interfacing and will be tested using external test equipment in the LASSI lab. (We have approval to use and access to this equipment)

- The capability to control the output states of the magnetorquer coils. This is a test of GPIO interfacing in firmware.

- The capability to move through different control modes, including: IDLE, FAULT, DETUMBLE, SLEW, and TEST. This will be validated through debugger interfacing, as there is no visual indication system on this device to reduce power waste.

- The capability to self-test and to identify faults. This will be validated through debugger interfacing, as there is no visual indication system on this device to reduce power waste.

- The capability to communicate to other modules on the bus over CAN or RS422 using LASSI-compatible serial protocols. This will be validated through the use of external test equipment designed for IlliniSat-0 module testing.

**Note:** the development of the actual detumble and pointing algorithms that will be used in orbital flight fall outside the reasonable scope of electrical engineering as a field. We are explicitly designing this system such that an aerospace engineering team can develop control algorithms and drop them into our firmware stack for use.

Electronics success will be determined through the successful operation of the other criteria, if the board layout is faulty or a part was poorly selected, the system will not work as intended and will fail other tests. Electronics success will also be validated by measuring the current consumption of the device when operating. The device is required not to exceed 2 amps of total current draw from its dedicated power rail at 3.3 volts. This can be verified by observing the benchtop power supply used to run the device in the lab.