Project

# Title Team Members TA Documents Sponsor
44 Head Controlled Mouse
Amanda Favila
Asher Mai
Lauren Wilcox
Sainath Barbhai design_document1.pdf
design_document2.pdf
final_paper1.pdf
other1.pdf
proposal1.pdf
video
# # Head Controlled Mouse

Team Members:
- Asher Mai (hanlinm2)
- Amanda Favila (afavila2)
- Lauren Wilcox (lwilcox4)

# Problem

There are many reasons why someone would want to use an eye or head-controlled mouse. Some people want to increase the rate at which they can move their mouse across the screen. Others may switch off between clicking and typing so much, and not having to take their hands off of the keyboard will save them time. Disabilities can also make using the standard computer mouse or trackpad difficult. Although eye and head-controlled mice have been invented, they typically require an expensive camera setup. On top of this expensive price and complicated setup, these devices are not universal to any device from Mac to PC to iPad. There is clearly a need for this technology to be more universally accessible. Additionally, there are people who dislike using cameras due to privacy concerns, so we believe there is another solution to this problem that does not need a camera.

# Solution

Our solution is to create a device that will process the user’s head motions to control the cursor on whatever device they are using. This device will be attached to a hat which is more comfortable for the user than a headband and can balance the weight of the device and its battery more evenly. This device will track when the user turns their head up, down, left, and right to move the cursor on their screen accordingly, and then either read a head tilt to click or use an external button that is large enough for accessibility requirements. Although there are similar technologies on the market for this problem, we believe we can decrease the cost of the device (less than $150) and make it more universally accessible across devices.

# Solution Components

## Subsystem 1: Internal Measurement Unit (IMU)
We will need an IMU to measure the head rotations of the user. This will include an angular velocity sensor (Gyroscope) and accelerometer that we can grab data from. Right now we are looking at the SCC1300-D02 gyroscope and the ADXL335 accelerometer.

## Subsystem 2: Power Supply

We will make use of a standard battery pack to supply the power to our device. If needed, we can also include a voltage regulator in our PCB, depending on what the rated voltages of our components are.

## Subsystem 3: Interface

We will be using a $10 USB Unifying Receiver, such as the Logitech 910-005235. This receiver will take in the cursor displacement data generated by on-board MCU that uses head position data from the IMU.

## Subsystem 4: Processing

This subsystem will be purely software via a programmed microcontroller (Arduino). It will map the gyroscope and accelerometer data from the IMU to the position on the screen. We will need to include a calibration sequence right when the user puts on the hat so that each user’s difference in head movement can be compensated.

# Criterion For Success

Our solution will allow users to control the direction of the computer mouse by moving their head while wearing the hat with the IMU and power supply attached to it. The user will be able to move the mouse anywhere on the screen. They will be able to left-click by pressing the large button and they will be able to right-click by pressing the large button twice, or there will be specific head tilt movements implemented to control left and right clicking.

One goal is for the total price of our device to not exceed $100 so that we can guarantee a sale price that is cheaper than the similar solutions that are already on the market.

Another goal is for the device to be able to be universally used on most devices.

If time allows, we have many ideas for additional features to be added to this device. One example is that the eye control feature of Windows only supports the US English keyboard, so we could expand this idea to other keyboards.

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.