Team Status Report for 09/25/2021

As of now, no significant risk is evident based on current progress. This week primarily revolved on making sure we deliver an excellent proposal presentation.  Apart from the technical challenges discussed in the proposal, nothing else pops out for now.

One feedback we got from the TA and professors was to make sure we don’t spend a lot of time getting Shelley up and running. If by Tuesday Shelley isn’t ready, we will most likely scrap that part as she is not critical to our project and it would be better to spend time on the other components.

No changes have been made yet. This week we plan on getting a basic demo setup, which involves getting a bluetooth module setup and raspberry pi up and running with Django integrated. If that works as intended, we expect at least the initial stages of the project to move forward at the pace proposed in the GANTT chart.

 

Team Status Report for 09/18/2021

Hello World! This semester will see the development of a novel IoT cat tracking system, and we’re so excited for the road ahead! 

The past few weeks saw a whirlwind of activity as the team weighed several solution approaches for how to best tackle the problem of sensing cat illness. After meeting with Professor Mukherjee and our TA, Edward, we realized that our decision to make the project consist of several distributed components needed more concrete reasoning – why would a system of separate sensor tags be better than a large, single device. After re-evaluating the problem area of analyzing cat eating habits, we found that a distributed system allowed for more modularity and customization around users’ unique circumstances. For example, users with only one pet would have no need for tracking unique cats and thus could not justify the additional cost of a built-in RFID sensor subsystem. A modular system architecture would allow users to simply add or remove RFID sensor tags based on their need to distinguish between multiple pets.

The team also researched various wireless communication protocols and conducted a trade study between using Bluetooth Low Energy (BLE) versus WiFi for Tag←→Hub data transmissions. While the longer range of the WiFi standard made it a tempting pick, we ultimately settled on BLE because of its highly superior power consumption and lower development complexity. Lucas began searching for specific BLE modules and settled on a shortlist, to be written out as a trade study by next week.

Writing the proposal slidedeck was the bulk of this week’s work. With Proposal Presentations coming up this week, MeeDm has been practising extensively to prepare. We’re so excited to present this project and hear feedback!

Tarush’s Status Report for 09/18/2021

This week we worked on writing up our proposal presentation slides based on the feedback we received from our meeting with Tamal and Edward. 

In order to broaden my scope for the project, I worked on figuring out more ideas for the web application that could be integrated into our project like sending email notifications to the user, adding a login system, figuring out different ways we could add more data analysis etc. Along with the web app, other parts I would be working on would be writing the code to analyze the information sent from our sensors to the Raspberry Pi, as well as converting the information to a JSON file to be read by our web application. 

As of now I am currently on schedule. My next steps would be to create a design diagram for what I would want the web app to look like and finalize on how I would want to implement it. I have also scheduled a meeting with one of the TAs to discuss the implementation as well.