Team Status Report for 2/25/2023

What are the most significant risks that could jeopardize the success of the project? How are these risks being managed? What contingency plans are ready?

Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?

Since last sunday, we developed the block diagram, design requirements, and system specification for our new project for the design review presentation. Some of the changes we made are stated in the slides:

We were also considering making a change from the STM32 to another micro-controller. Details on this will be discussed today.

Please discuss teaming with your team.. and, please enumerate how you have adjusted your team work assignments to fill in gaps related to either new design challenges or team shortfalls (e.g. a team member missing a deadline).

Since we changed our entire project last week, we made significant changes to our team work assignments to account for these changes:

Nish: Pressure Thresholding, Xcode + Kivy Interface

Caroline: PCB and Glove Design

Lee: CV processing

Testing and verification remained the same

Lee’s Status Report for 2/25/2023

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 past week, I worked with my group to refine our design review presentation slides. Some of the changes we made to my initial slides were about the testing and verification section. I initially had descriptions of the unit tests we would conduct and any additional information that would need to be stated would be conveyed verbally (I did this since we were given the suggestion last time to have less text). After discussion with my group, we opted to follow the format provided in the design review template which asked us to describe the inputs and outputs of our test and how it was relevant to the quantitative design requirements. Since this was quantitative it stood to reason that so should these test cases.

Additionally, during the the week I contributed to submit design review peer forms during scheduled class times.

Lastly, I researched what part to order for the phone mount that would attach to the laptop. I had to make sure the phone mount wouldn’t be magnetic since I didn’t like the idea of attaching a phone mount permanently to the laptop via an adhesive strip on both devices. I opted to go for a clamp option since it would leave no trace and it wouldn’t be attached when our product was not in use. Furthermore, I went to find a design on Amazon that had a 180 degree rotation so that the phone could swivel and point at a 45 degree downward towards the piano layout.

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

Our project is on schedule. We recently adjusted it to account for the change in project, but since by the end of this week we have mainly figured out which exact components we want to order most of what it left is then continuing on to work on our individual parts. For me, that is working on the CV component and I have already done so preliminary research into the functionality and example code for OpenCV so I can familiarize myself with it’s syntax. I took Computer Vision 16-385 and even though we did not use OpenCV, the fundamentals of what the built-in functions do were certainly taught and some of which we even implemented on our own.

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

By the end of the next week, I hope to have OpenCV package installed on my laptop and have done additional research on the application towards a piano layout. Also looking to research for some sort of preliminary basic code for objection detection for finger-tips.

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

 

Team Status Report for 2/18/2023

What are the most significant risks that could jeopardize the success of the project? How are these risks being managed? What contingency plans are ready?

The most significant risk that we are facing right now is being behind because we just changed our whole capstone project idea last week. We received lots of feedback from our proposal presentation, and we believed that it would be best if we changed our idea. Our previous idea contained a lot of moving parts that didn’t necessarily fit together, but we tried to force them together. In addition, we decided to switch because, as a whole, we are more passionate and interested in our new project idea. Lastly, the original idea had some fundamental issues regarding practically and cost that made it seem as a whole more infeasible.

Because this is a huge setback, we are working overtime in order to not fall too far behind. We started to order parts already and are in the process of finalizing our design review presentation.

Since we are changing our project so late in the semester, we have a contingency plan that involves creating a simple MVP project first, and then building on it when we have time. This allows us to create a product that meets our expectations while not overcomplicating it and bringing in too many factors. We would love for our project to be as complex as possible, but with the given time, we realize that it may not be feasible to add every single component that we want.

Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?

Because we completely changed our project idea, we have created a new requirements for our the new design of our system. The first set of requirements is that we want our product to be light and portable (weight and size) while still retaining a level of robustness. These changes are necessary so the user can have the accessibility and agency to conduct music arrangement and composition anywhere they are. Additional requirements were regarding number of chords, volumes, and octaves the user could play on this piano. This was also necessary since the user needs to feel that this product can be worth-while to use rather than the effort used to find a real piano. These requirements provides the fundamental needs of the arranger and composer so that our product can stand on its own uniqueness (portable) and be differentiated from most pianos. Lastly, the requirements that target accuracy is beyond paramount for the user since they desire a reliable and accurate product for their needs. If our note and playback is inaccurate, then it won’t be sufficient for the user to enjoy using this over other pianos.

The costs that these changes incur take up our own time to edit and develop these changes to the design.  Moving forward, additional costs to our time can be mitigated by finalizing our design after the design review this next week so there won’t be any confusion and fewer errors.

Provide an updated schedule if changes have occurred.

Here is a link to our new GANTT chart: https://docs.google.com/spreadsheets/d/1Cjl4wdKSUFSZtF_5Mw1JuqtcA23wlrnsTV8MYDUDK88/edit?usp=sharing

Please enumerate one or more principles of engineering, science and mathematics that your team used to develop the design solution for your project.

We used the reliability principle of engineering to design how each of the components in our design, when integrated, would remain functional while also providing the user a strong sense of our product’s robustness and accessibility. We designed our product to be simple so that it would remain lightweight and portable for the user including dependencies on everyday devices (phones and laptops) so the user would not have to bring additional equipment with them to enjoy a level of satisfaction that comes with playing the piano anywhere they go.

 

Lee’s Status Report for 2/18/2023

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).

Over the past week, I worked with my group and speaking with Tamal and Professor Sullivan regarding our project change to our new idea of our AR piano. I expressed many concerns and thoughts about the new project idea which gave us the necessary ability to address many of the caveats that came along with this change. Lastly, I helped take the information discussed in a google doc which was divided up into sections in the abstract to creating a rough draft of the slideshow presentation for the design review.  Here are some example slides below of my work:

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

Due to changing our project idea, our progress is a bit behind. We worked this week to ensure that our design idea was fleshed out and thorough to get back to the same pace as the design from our original idea. Because our idea is more simple and has less complexity, it also means there will be less confusion amongst group members as well as a more cohesive design review presentation.

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

For the next week, I plan on working on the peer review forms for the presentations next week. I am also eager to await for the feedback on our design review presentation so we can also make the necessary changes to our project too before we dig ourselves a hole we cannot get out of. In the meantime, I also plan on working on my side of the Gantt scheduling for my part of the project.

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 ?

For our project, the courses 16-385 (Computer vision), 18-220 (Circuits), 18-349 (Embedded Systems) covered the main science and mathematical concepts and principles for our design.

Caroline’s Status Report for 12/18/2023

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).

In the past week, we decided to change our project idea, so I helped research more different types of distance sensors that could fit onto people’s fingers. Due to the fact that we changed our project idea, I created a new GANTT chart to accurately reflect our new project. I also ordered some pressor sensors that we want to use so that we could be on track next week. In addition, I helped create slides for the design review next week.

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

I believe that we are currently a bit behind schedule because, in our new GANTT chart, we aimed to have finished our breadboarding by this week, but we have not finished ordering or have not received the necessary parts that we need for our project. In order to combat this, we will be starting on other tasks simultaneously while we wait for our parts to arrive.

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

In the next week, we hope to have a preliminary demonstration of how our pressure sensors can work and how we can use the CV to track fingers.

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 tell us how you learned those principles over the last week?

I will be using the information and content that I learned from 18220, 18021, and 18290 for our project.

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).

Caroline’s Status Report for 2/11/2023

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).

In the past week, I worked with my other team members to produce our Proposal Presentation Slideshow. This involved researching and adding more information regarding our scanners, batteries, and PCB. From this research, we determined that we wanted our PCB to have an RFID module, Bluetooth module, accelerometer, and break beam sensor. I also created a GANTT chart so that we can keep each other accountable for our tasks and so we could have an even labor distribution. In addition, I presented our presentation to my fellow peers and we received lots of feedback on our proposal.

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

I believe that we are currently a bit behind schedule because, in our GANTT chart, we aimed to have all of our research and ordering done this week, but we have not ordered any parts that we need for our project. In order to combat this, we will be ordering our parts and I will start on the PCB design as soon as possible.

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

In the next week, I hope to finalize our project idea and order the necessary parts for our project. From the feedback that we received, we realized that we might need to pivot our idea slightly in order to create the best product that we had in mind. In addition, because it will take time to design and order our custom PCB, I will try to start designing our breadboard so that our next steps aren’t postponed because of this.

Lee’s Status Report for 2/11/2023

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 past week for this project, I worked on  developing the intitial rough draft slideshow of our project proposal demonstration. Here are some example slides below: 

Later on, I worked with my group to refine these slides so that they would be ready for the presentation for Monday and Wednesday. For Monday’s and Wednesday’s class I also worked on doing peer reviews for my other classmate’s proposal presentations.

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

Our progress might be a bit behind as we would like to order parts as soon as possible (preparing for design review presentation might be of higher importance depending on unknown variables). Therefore, the first course of action will be to ensure that all of our design details are fully fleshed out, specified, and finalized.

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

Our deliverables I hope to complete in the next week is to make the necessary modifications provided from the feedback of our proposal presentation and use that to create a design that will not only be suitable and well-established for our design review presentation but also to begin ordering parts for our project since the lead time on that could very well be longer than expected.

Team Status Report for 2/11/2023

What are the most significant risks that could jeopardize the success of the project? How are these risks being managed? What contingency plans are ready?

Some of the risks are that some of the components we want to use in our design may align well with our use case requirements. As an example, for our coin battery, it may not supply the 2 year length of time we have for our use case requirement. It also may perform differently depending on the use of the coin battery, which could make results unpredictable. We’ll try to manage this risk by being very thorough with our research when analyzing datasheets.

Another risk that could pose complications would be having ill-equipped foresight of how our solution approach may not take into account well of envisioning every stage of where the product ends up affected by. We should analyze how our product would perform when being checked in, on the conveyer belt, being loaded onto the airplane, being picked up at baggage claim, etc. To manage this risk, we plan on creating block diagrams like we did for our theivery flow slide in order to illustrate and demonstrate how this would work. By planning out every minute detail, we increase the chances of a successful project.

Lastly, we might want to consider the risks of how practical our product would be for consumers in real life. This also means looking into whether there are some forms of data communication that may be better than others such as bluetooth or wifi. Some contingency plans we thought of in order to address these risks is writing out some of the pros and cons to both. We discussed how wifi had security issues or that not every user connected to the airport wifi, but bluetooth also had a shorter range than wifi as well.

Another practical risk was addressing multiple passengers who would go through the scanner or a family of passengers and their luggages, and how we would adress our solution approach to address these issues. To address this risk, RFID ensures that each luggage and user would be paired with the same data that identifies them correctly. So multiple people passing through with different data that identifies them would not intefere with each other. For the families with mutiple bags who go through the scanner, it is a grounded assumption that families register themselves and their children under the same account for the airlines. Using this information, we would give them luggage tags with the same identification data so that the scanner would be looking for the luggage tags to match with any one of the tags on the family members. These are some of the ways we plan on mitigating these risks to practicality.  

Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?

Over the week we decided to make the change to remove the geolocation, airtag capabilities on the luggage tag. After discussing with course staff  and ourselves, we concluded that it was an additional task to locate the luggage and would be outside the scope of our use case of preventing baggage claims thefts. Knowing the location of the luggage might aid in that effort, but the issue is that location doesn’t prevent, it only helps with identifying where the missing luggage went after the event. Furthermore, the widespread use of apple airtags makes this task pretty much already solved, so it we would rather focus our efforts toward something that consumers would be more interested in solving (no reason to reinvent the wheel).  

Provide an updated schedule if changes have occurred.

The above change was conduced this past week before we created our schedule, so the schedule created for the proposal presentation is still up to date.

“Our project includes considerations for __________”

Our project includes considerations for public safety and welfare for airport passengers, which could have a global impact as air travel is a commonly used technology used world-wide. Since our use case for our product aims at diminishing luggage claims theft or midhandling this would help in the safety and security of people’s property and possessions. Lastly, there could be an environmental benefit, as we plan on making these RFID tags reusable by having a disposable bin outside airport exits for people to dispose of their tags so that they can be reprogrammed by the airlines to be used for future passengers.