# Title Team Members TA Documents Sponsor
4 Bluetooth Enabled eWalker
Darren Domingo
Gregory Tow
Lukas Adomaviciute
Akshatkumar Sanatbhai Sanghvi design_document1.pdf
# Bluetooth Enabled e-Walker

Team Members:
- Lukas Adomaviciute (lukasa3)
- Darren Domingo (ddd3)
- Gregory Tow (gtow2)

# Problem

Walkers are primarily used by people over 65 years old with musculoskeletal or neurological problems. Some conditions that require a person to use a walker include arthritis and Parkinson's disease. When a person uses a walker, one or both hands are occupied supporting themselves with the walker which makes it more difficult for the user to access their smartphone's features. In recent years more devices have become smart devices paired with our smartphones for additional features, but walkers and walking canes have been left behind. When looking for existing solutions, we have found some canes that support lighting and charging, but none with IoT. We believe this would be the next logical step in innovation to support people with conditions that struggle to interface with touch screen displays.

# Solution

We would like to bridge the gap between features that would be used on a smartphone to the walker itself. It would be particularly useful to implement an easily accessible contact system on the walker that could be used in an emergency situation where time is of the essence and the user might struggle to use their smartphone.

# Solution Components
## Walker Construction
- Walker itself
- 3D-printed electronic component housing
- Phone mount

Our solution will be constructed onto a standard folding walker with two forward facing wheels. We plan on constructing a 3D printed housing that will contain the required electronic components. The electronic component housing will attach to the walker below the hand rests and should be positioned in a manner that does not put restraints on the folding machinism or interfere with walking. We also would like to add a physical phone mount to the walker so the smartphone microphone and display can optionally be utilized when the walker’s systems are triggered.

## Communication and Interfacing (IoT)
- 3 contacts - 911, Main (call, text), Backup (call,text)
- Arduino Reader to read in the phone numbers and map those to specific buttons on the walker
- Pressing a button will trigger an automated text or a call through the connected phone through bluetooth
- NFC Readers to store information such as phone numbers or automated texts

Our primary goal for communication and interfacing is to configure a five button system that will allow the user to quickly send text message notifications or preconfigured phone calls through BlueTooth once the device has been paired with their smartphone. One button will be preconfigured for an emergency 911 call. Two buttons can be configured for emergency contact phone calls with phone numbers that can be written by the user. Two buttons can be configured for emergency contact text messages with the contact and message content written by the user. Our group discussed utilizing an NFC reader to store the configured phone contact numbers, text contact numbers, and text message content. The user should be able to utilize an NFC writing app on their smartphone to write the required data to the walker controller. We plan on implementing this system by utilizing an Arduino for BlueTooth communication. We currently plan on utilizing the Arduino RFID module to communicate with the smartphone and read the data written from the user’s smartphone. After the implementation of the button configuration, our group will continue to implement more IoT functionality.

## Sensors

Our Arduino control system will utilize information from our gyroscope sensor to identify when the walker is in a horizontal position or when the walker is on a downwards incline. When the gyroscope indicates the walker in a horizontal position it will utilize the communication and interfacing subsystem to send a text notification that a fall has occurred to the preconfigured button contacts. The control system will also use information from the GPS to text the user’s location to preconfigured contacts in emergency situations.

## Power Management
- Power to Arduino System,
- Integrated USB port for charging internal battery
- Battery Life Indicator

The power management subsystem handles how power is distributed throughout the entire system. We will use an internal rechargeable battery as the main source of power. In order to charge other devices while providing power to the Arduino system, we will make use of a step up DC-DC converter. To turn on the entire system, a power switch will be used in line with the connection to the DC-DC converter, with an appropriate fuse in the positive terminal to prevent damage to the rest of the circuit in the case of a battery issue. To charge the battery, we will use an integrated USB Type C port which connects to the battery. To charge devices, we will use two integrated USB Type A ports connected to the battery which will support quick charging. Lastly, to monitor the charge of the battery, we will make use of LEDs and a LM3914 chip or similar to display the charge status in a color bar approach.

# Criterion For Success
We plan to test if our walker charges properly and if it can be turned on and off. The two charging ports will be tested as well. We will also be ensuring that the walker will be able to make calls and send texts through the push buttons we will have. The text messaging test will also confirm that the GPS is working. Lastly for the gyroscope, we will confirm that it knows the exact orientation our walker is in, and that the text messaging system sends out the proper severity of text.


Smart Frisbee

Ryan Moser, Blake Yerkes, James Younce

Smart Frisbee

Featured Project

The idea of this project would be to improve upon the 395 project ‘Smart Frisbee’ done by a group that included James Younce. The improvements would be to create a wristband with low power / short range RF capabilities that would be able to transmit a user ID to the frisbee, allowing the frisbee to know what player is holding it. Furthermore, the PCB from the 395 course would be used as a point of reference, but significantly redesigned in order to introduce the transceiver, a high accuracy GPS module, and any other parts that could be modified to decrease power consumption. The frisbee’s current sensors are a GPS module, and an MPU 6050, which houses an accelerometer and gyroscope.

The software of the system on the frisbee would be redesigned and optimized to record various statistics as well as improve gameplay tracking features for teams and individual players. These statistics could be player specific events such as the number of throws, number of catches, longest throw, fastest throw, most goals, etc.

The new hardware would improve the frisbee’s ability to properly moderate gameplay and improve “housekeeping”, such as ensuring that an interception by the other team in the end zone would not be counted as a score. Further improvements would be seen on the software side, as the frisbee in it’s current iteration will score as long as the frisbee was thrown over the endzone, and the only way to eliminate false goals is to press a button within a 10 second window after the goal.