Posted on

Nish’s Status Report 2/25

What did you personally accomplish this week on the project? Give files orphotos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

This week, I worked for a few hours on making the slides for the presentation. I think spent another few hours practicing and delivering the presentation. Following that, I’ve been working on putting together the materials we need to order, such as sourcing the wrist strap and bluetooth module. We are also meeting to order the PCB this week, so it will arrive during spring break.

 

I made the block diagrams and testing plans, as well as further extensions.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

 

I think we are slightly behind, but once we can order the PCB and parts I think we will be on track, and we can start working on setting up the code base.

What deliverables do you hope to complete in the next week?

 

I want to create a dummy app that creates a Kivy Interface from an Xcode wrapper. Hopefully, I will also be implementing camera and bluetooth access in the app, to make sure we can connect to the iPhone infrastructure.

Posted on

Nish’s Status Report for 2/18

 

  1. What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

This week, we completely changed our project. Caroline and I spent a few hours trying to figure out how to pivot from our MyTagMyBag idea into something else that is centered our identification, or even in IoT. We went through our old list of ideas and came across our Virtual Piano idea, so we got to work on flushing that out. After talking through initial designs with a few TAs, I created a new abstract for our new idea. I spent a lot of time figuring the different use cases and parts that we would need, such as which finger sensors, and how our glove should look. I also met with Professor Sullivan to discuss how to scope our idea to something that is feasible.  I am also writing the presentation for next week.

 

2. Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

We are definitely behind as we changed our project this week. However, we did work on creating a new abstract in order to catch up, and also met with Professor Sullivan and a few TAs in order to more thoroughly think through our project. We will have to catch up by tomorrow night anyways in order to do our Design Overview, and I think that we have gotten to a good place besides actually ordering our parts and working on our code.

3.  What deliverables do you hope to complete in the next week?

Once we finish the Design Overview (we are currently working on putting together) Presentation, we will work on the Report and try to order our parts. While we wait for the PCB, we will probably begin working on the interface and CV portion of the project, as the pressure sensors can be added in later. Next week, I will get done the presentation and I also hope to finish designing the glove with the small PCB and get that ordered.

 

4. Please list the particular ECE courses (if any) that covered the engineering science and mathematics principles your team used to develop your design ? If there are no courses please tells us how you learned those principles over the last week ?

16-370, Computer Vision

18-349, Intro to Embedded Systems

18-449, Distributed Embedded Systems

 

Posted on

Nish’s Status Report Feb 11

Originally located: http://course.ece.cmu.edu/~ece500/projects/s23-teamb6/weekly-status-reports/nish-weekly-status-report-for-february-11th/

In the past week, we worked mainly on our proposal presentation. I worked on our “Thievery Flow” as well as flushing out the different components in our solution to try and make it more cohesive.  I identified specific versions of products we could use, such as the STM32 + RAK4600 Bluetooth that would complement each other, and researched the other components we were considering working with. We worked as a team to edit all the slides together.

  

I think we are a little behind on our design. Though we tried to edit our use case requirements, I think we still have written our requirements based on our selected implementation, leading to aspects of our design that may seem unnecessary, such as having Bluetooth. To make sure our design review goes smoothly, I would like to go back and refine our requirements, or perhaps pick another use case where we can implement a similar type of sensing mechanism as people are walking through a certain space, allowing for identification of who is passing through. I think we have been trying to overcomplicate a simple solution with a lot of “nice-to-haves” without having a solid foundation.;

We plan to have a meeting to focus on our project, whether that be through a different use case or refining our current one and redoing the requirements. I plan to bring a few ideas for different use cases to this meeting.

Next week, I want to have a complete parts list and have ordered the different components we need. We might need some more time on the PCB side because once we decide on the components, we still need to put the actual PCB together. I want us as a team to revisit each component we were thinking about and make sure having it serves a requirement in our use case rather than something that would be making our project more complex for the sake of it. Once we have our components ready, we can also set up our repo with the starter code (especially for something like the STM32, if we choose to continue using it).