Mock Presentation

Description

Similar to the Design Doc Check and the Mock Demo, the Mock Presentation is an informal, mandatory event designed to better prepare you for your Final Presentation. In these sessions, you will present a few of your slides (about 10-15 minutes), and get feedback from the course staff as well as a few invited Department of Communication TAs. You will also be able to see a few of your peers' Mock Presentations, as there are up to 3 teams per time slot.

Requirements and Grading

The Mock Presentation is meant to be an opportunity for you to get feedback on a subset of your final presentation. It is recommended that you choose some aspect of your project, and present the design, results, and conclusions from that aspect. In order to get relevant feedback on your presentation skills, your Mock Presentation should also have an introduction and conclusion. You will receive feedback on your delivery, the format of your slides, and the organization of your presentation. Your slides should generally include:

  1. Title slide: Names, group #, title.
  2. Introduction slide: What is the project?
  3. Objective slide: What problem does this solve?
  4. Design Slides: A few slides on design, requirements and verification (should include block diagram, math, graphs, figures, tables).
  5. Conclusion: Wrap things up, future work.

Mock presentation is graded credit/no credit based on attendance and apparent effort; showing up completely unprepared will earn no credit.

Submission and Deadlines

Sign-up is handled through PACE. Time slots are 1 hour long, and multiple groups will share a time slot. This will give you an opportunity to give and receive feedback from your peers. You will be required to stay until all groups have presented and received feedback.

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.