Team Status Report for 2/11

Our proposal presentation was done by Thomas on Monday, 2/6. We worked on getting started on our project after the proposal, which included submitting an order for AX200 wifi card to be used with PicoScenes, conducting further research on our respective areas, and getting PicoScenes set up.

Right now, our biggest concern is making sure all of our hardware will correctly interface together. We have double-checked the documentation and made sure that there will not be too much leg work required, but are still worried we have missed something. Our first chunk of development will happen on a laptop, so other than antennas or the wifi card, we don’t rely on other extra hardware which means getting parts is less of a concern. We’re currently ahead of schedule since this week was reserved for the proposal and initializing. There are no changes to be made to the schedule; likewise, there are no changes to be made to the existing design.

Our project includes considerations for privacy of individuals – our project aims to enable the users to be aware of what kind of IoT devices exist around them, which is especially valuable since IoT devices that can spy on people can be prevalent and hard to detect by visual means; while this may be a concern for locating individuals from their devices, we are building our system assuming access to walk around the space and constant devices, both of which we think will minimize possible harms to individual privacy.

Ethan’s Status Report for 2/11

After helping finishing up the proposal slides, I worked on getting PicoScenes set up on my laptop this week. My laptop happens to have AX210 which PicoScenes can work with, and the initial setup and monitoring works. This week was reserved for the proposals and getting started, so we’re not behind. For next week, I plan to work on further playing around with PicoScenes and scripting. If I get time, I will also work on beacon spoofing that will be used for the WiPeep technique.