Project

# Title Team Members TA Documents Sponsor
38 Smart Stove System
 Aryan Gupta
Dinal Gunaratne
Nikil Nambiar
 Stasiu Chyczewski design_document1.pdf
design_document2.pdf
design_document3.pdf
final_paper1.pdf
proposal2.pdf
proposal1.pdf
Team Members:
Nikil Nambiar (nikiln2), Dinal Gunaratne (dinalg2), Aryan Gupta (aryang4)

**PROBLEM:**

In recent years, there has been a concerning rise in the number of house fires attributed to stoves being left unattended. Nearly 50% of house fires are caused by burners being left on and unattended. In addition, being able to control a stove away from the knobs allows for more control while cooking. As a result, there should be an easy solution where a user can remotely control and turn off any burner that is on.

**SOLUTION:**

Our solution involves having heat sensors on each of the stoves to determine which burners are on and relay this information to the user via an app. The user will be able to see which stoves are on, and control each stove remotely. To whatever level the user sets the stove, there will be a robotic clasp that will appropriately move the knob of the stove to the desired level. The robotic clasp’s movement will be controlled by a chassis on rails which will automatically go to the desired knob and then turn it off. We are planning on having this movement pre-configured so that it can be easily replicated. Additionally, all communication between the app and heat sensors will be done over a network connection.

This solution will also have automated features. We plan to add a thermometer probe the user can manually put in pots with soups or other liquids to add boil over protection. This probe will monitor the temperature and automatically turn down the temperature of the stove once there is a risk of a boil over (temperature rising significantly above boiling point).

Our app will contain a visual interface which allows users to see which exact burner is on, and change the burner intensity to whatever is desired, including off. Additionally, we will add push notifications to notify the user if a burner is on or if boil over was detected and handled.

If time permits, an additional feature we would like to implement is a separate smoke detecting component to allow for fire detection. This component would detect if a fire is forming and automatically turn off the burner to prevent or reduce the flame. It would also notify users via the app.

**PROJECT COMPONENTS:**

Microprocessor: Processor to control the robotic claspers’ movements, send and receive signals from app

Rail System: Simple motor powered rail system to guide the clasper along the stove top

Servo Motors: Used to move the robotic clasper along the rails

Chassis: Create a stable mechanism to hold the clasper mechanism

Clasper with Actuator: Use an actuator to press the clasper on the stove switch

Wifi adapter: Connects device to wifi to allow communication with app

App: phone app with front end to display which stove is on and allow users to close stove from app

Heat Sensors: Sensors to check the heat of each stove to tell if stove is off

Thermometer Probe: Sensor to check the temperature of liquid in pot

**CRITERIA FOR SUCCESS:**

Our main goal is making sure that a user is able to remotely turn off a stove. The system should be able display information regarding which stove is one and give the user the option to turn off the stove. All this communication between the system and user will be done through an app.
Our second goal is for boil over protection which should automatically detect when a liquid in a pot is being boiled for too long and either notify the user that their dish is about to boil over or remotely turn down the temperature of that specific burner to prevent the spill over before it occurs.
Stretch Goal: If time permits we would also like to add some sort of smoke detector sensor that would be able to detect if there's a fire on the pan or not. We would probably have to create our own module for this, and look into this further.

Covert Communication Device

Ahmad Abuisneineh, Srivardhan Sajja, Braeden Smith

Covert Communication Device

Featured Project

**Partners (seeking one additional partner)**: Braeden Smith (braeden2), Srivardhan Sajja (sajja3)

**Problem**: We imagine this product would have a primary use in military/law enforcement application -- especially in dangerous, high risk missions. During a house raid or other sensitive mission, maintaining a quiet profile and also having good situational awareness is essential. That mean's that normal two way radios can't work. And alternatives, like in-ear radios act as outside->in communication only and also reduce the ability to hear your surroundings.

**Solution**: We would provide a series of small pocketable devices with long battery that would use LoRa radios to provide a range of 1-5 miles. They would be rechargeable and have a single recessed soft-touch button that would allow someone to find it inside of pockets and tap it easily. The taps would be sent in real-time to all other devices, where they would be translated into silent but noticeable vibrations. (Every device can obviously TX/RX).

Essentially a team could use a set of predetermined signals or even morse code, to quickly and without loss of situational awareness communicate movements/instructions to others who are not within line-of-sight.

The following we would not consider part of the basic requirements for success, but additional goals if we are ahead of schedule:

We could also imagine a base-station which would allow someone using a computer to type simple text that would be sent out as morse code or other predetermined patterns. Additionally this base station would be able to record and monitor the traffic over the LoRa channels (including sender).

**Solutions Components**:

- **Charging and power systems**: the device would have a single USB-C/Microusb port that would connect to charging circuitry for the small Lithium-ion battery (150-500mAh). This USB port would also connect to the MCU. The subsystem would also be responsible to dropping the lion (3.7-4.2V to a stable 3.3V logic level). and providing power to the vibration motor.

- **RF Communications**: we would rely on externally produced RF transceivers that we would integrate into our PCB -- DLP-RFS1280, https://www.sparkfun.com/products/16871, https://www.adafruit.com/product/3073, .

-**Vibration**: We would have to research and source durable quiet, vibration motors that might even be adjustable in intensity

- **MCU**: We are likely to use the STM32 series of MCU's. We need it to communicate with the transceiver (probably SPI) and also control the vibration motor (by driving some transistor). The packets that we send would need to be encrypted (probably with AES). We would also need it to communicate to a host computer for programming via the same port.

- **Structural**: For this prototype, we'd imagine that a simple 3d printed case would be appropriate. We'd have to design something small and relatively ergonomic. We would have a single recessed location for the soft-touch button, that'd be easy to find by feel.

**Basic criterion for success:** We have at least two wireless devices that can reliably and quickly transfer button-presses to vibrations on the other device. It should operate at at *least* 1km LOS. It should be programmable + chargeable via USB. It should also be relatively compact in size and quiet to use.

**Additional Success Criterion:** we would have a separate, 3rd device that can stay permanently connected to a computer. It would provide some software that would be able to send and receive from the LoRa radio, especially ASCII -> morse code.