Posted on

Matthew’s status report 3/16

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

I tested the new ultrasonic and capacitance measurements over several different liquids and types of cups to determine a correlation between capacitance and the liquid/cup material. Doing so required soldering the copper tape to wires, as well as setting up arduino code to accurately measure capacitance.

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

Behind schedule, since the ultrasonic that we received was bugged, returning a constant value only

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

I plan on having the ultrasonic and capacitance all working so that we can begin making an overall draft for the MVP, and start to turn the data we receive into more user friendly pieces of data such as volume

Posted on

Erin’s Status Report Week of March 16

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, I worked on bluetooth code for the app side. I was able to create a bluetooth manager object in the app and a tester page for it. Using that I was able to work with Alan to connect the app to the arduino. To do this I also had to set up the app onto my iPhone which took some additional time.

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

On schedule

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

Over the next week, I plan on writing more of the app for the bluetooth page as well as more of the backend data structure for the app.

Posted on

Team Status Report for 03/16/24

  • 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 largest issue we currently have is that our waterproof ultrasonic sensor does not work. We believe the unit we received is defectful. We purchased a new one, and also purchased RS485 modules to test with a sensor we have, that requires this part to work. Another issue is that the difference of capacitance between liquids is not as large as we expected. We will try to use it as a dimension in classification, but we also have turbidity as an alternative metric to test.

 

  • 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?

We are considering adding a turbidity sensor, to increase classification accuracy, either instead of, or in addition to, capacitance. We also purchased a new ultrasonic sensor and RS485 modules, as the sensor we were testing does not seem to work. We have room in the budget for these new parts, but we will also try to return the sensor that does not work to receive that money back.

Posted on

Alan’s Status Report for 03/16/24

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, I worked on bluetooth. I managed to connect the ItsyBitsy boards to my phone using the Adafruit’s testing app, to my computer using a python script and, finally, to our app (with Erin working on the bluetooth code for React)! I relayed sensor data (temperature, pressure, and color), and tested that transmission is reliable. I also received data back from my cellphone to the Arduino board, also reliably. Furthermore, I wrote the FSM to only relay liquid level data the first time after a bottle is closed (to avoid wasting power).

Other than this, I tested the new waterproof ultrasonic sensor, which doesn’t seem to be working, so I ordered a new one, as well as RS485 communication modules to test with another sensor we had also tried. I did some work (both by myself and with Matt) on capacitance testing, and it seems that the variations found in liquids (from a study done by Matt) are rather small, and heavily affected by room temperature. Finally, I looked into turbidity as a possible metric and ordered a sensor to test it.

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

On schedule

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

Over the next week, I plan on writing a classifier, based on color, density, and possibly capacitance and turbidity, and tests its accuracy with different drinks. For this first step, I will write it in a Python project, for ease of testing.

 

Bluetooth communication:

Arduino serial monitor:

 

Adafruit’s Bluefruit testing app, showing the device, the transmitted data, and the received data:

Posted on

Erin’s Status Report for 03/09/2024

• 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 I created the storage system and the home page of the app as well as an async function that saves total intake at the end of each day. I also created the template for the streak calendar page and created the react objects behind them.
In terms of project management, I helped write the design report and created most of the figures in the report. I also helped CAD a more detailed version of the bottle.

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

On schedule

• What deliverables do you hope to complete in the next week?
Finish streak page, integrate Bluetooth

Posted on

Alan’s Status Report for 03/09/2024

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

Last week, I mostly work on the design report. Once this was finished, I turned back to the hardware and integration. I helped Matt test the waterproof ultrasonic sensor, and figured out the issue was with the RS485 protocol. I placed the order for the new sensor. I also investigated an issue with an order we hadn’t received (a photoelectric water level sensor) and coordinated to re-place the order – the sensor should be here sometime next week.

Finally, I picked up the Adafruit ItsyBitsy board from receiving, set them up for usage (soldered pins and burned bootloaders) and assembled the bottle circuits on a breadboard! As you can see on the picture, there are two independent circuits. The one on the left is the bottom assembly, with a thermometer, color sensor, and pressure plate, while the one on the right is the top assembly, with an ultrasonic sensor and a pressure plate. I used driver code (adapted and combined from online tutorials) to ensure that all the sensors worked together as I assembled them.

Finally, I began testing the bluetooth connection. I succesfully ran bluetooth code from the ItsyBitsy, but am having issues on the React end.

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

On schedule

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

Next week, I hope to successfully connect the ItsyBitsy board to the app over BLE. I will also write the FSM to only update the level reading when necessary, according to the pressure plate readings.

 

Circuit:

Posted on

Team’s status report for 03/09/2024

  • 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 main issue we found is that the waterproof ultrasonic sensor we were using was not working as expected. We discovered that this is because it communicated using the Rs485 protocol, and we need an adapter for it to work with the arduino boards, leading to added space, power consumption, and engineering complexity. The order for our contingency plan – a photoelectric water level sensor – had some issues, did not arrive, and needed to be reordered. It should arrive sometime next week, and we will test it as soon as we receive it. We also purchased a sensor that does not require an adapter. In the meantime, we are testing for our proof-of-concept with a non-waterproof ultrasonic sensor.

 

  • 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?

We are considering changing the ultrasonic sensor for a photoelectric sensor. We also purchased a new waterproof ultrasonic sensor. We have room in the budget for it, but it can be returned (within 30 days)  if we deem the photoelectric sensor adequate.

 

Please write a paragraph or two describing how the product solution you are designing will meet a specified need…

Part A (Erin): with consideration of global factors. Global factors are world-wide contexts and factors, rather than only local ones. They do not necessarily represent geographic concerns. Global factors do not need to concern every single person in the entire world. Rather, these factors affect people outside of Pittsburgh, or those who are not in an academic environment, or those who are not technologically savvy, etc

The smart water bottle we are proposing will remind people to drink more water and help them meet their intake goals. A smart water bottle like Aqualotol can benefit everyone in the world but more so people in first and second world countries due to the cost of the water bottle. This bottle is also better for people with smart phone access since it will allow them to use the full feature set of the bottle. People who are not good with technology will still be able to use our intuitive UI in the phone app to track their water consumption level. This bottle is meant for anyone who has a smart phone and can afford the bottle. Although this may seem limited, 68% of the world owns a smart phone and many may want to buy the bottle.

 

Part B (Alan): with consideration of cultural factors. Cultural factors are encompass the set of beliefs, moral values, traditions, language, and laws (or rules of behavior) held in common by a nation, a community, or other defined group of people.

It has been concluded that the majority of Americans do not drink enough water each day [1] . The current culture, where people have very busy lifes, is, reasonably, one of the factors that impedes people from hitting their water drinking goals. This water bottle, as it is designed to be carried throughout the day, will help people incorporate more water drinking into their routines, helping in the mitigation of this issue. This effect will be further enhanced by the tracking of the amount of water drank, the reminders sent when the user hasn’t been drinking enough, and the social media hydration-streak tracking, allowing friends of the user to remind them to drink more water. Thus, our project can help improve water consumption among Americans, incentivizing healthier habits and reducing the health issues that stem from insufficient water consumption.

 

Sources:

1-https://civicscience.com/forty-seven-percent-of-americans-dont-drink-enough-water-plus-more-h2o-insights/

 

Part C (Matt): with consideration of environmental factors. Environmental factors are concerned with the environment as it relates to living organisms and natural resources.

The aqualotl project takes into account major environmental factors, since it is a smart and refillable water bottle. Plastic water bottles litter the ocean, and are harmful to the environment, causing the deaths of the unfortunate sea creatures who happen to stumble upon them. In fact, 500 billion plastic water bottles are being used each year, but at least 250 billion of it isnt properly recycled, and is usually littered and it is estimated that around 9 million tons of plastic waste is dumped into the ocean per year. We hope that our bottle will help promote reusable water bottles, instead of one time usage ones that several consumers are accustomed to today, as well as reducing the need for people to litter the environment.

Posted on

Matthew’s status report for 3/2 & 3/9

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

I developed the schematics of the electronic components, taking into account additional components and parts to switch out, such as a new microcontroller, OLED display, and removal of the accelerometer.  Along with that, I helped edit the Design Review report, and tested out a modified ultrasonic sensor(we cut a bit of the wire from the ultrasonic that we got), discovering that it could not sense anything properly

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

We are slightly behind schedule,  since we have to order a new ultrasonic/laser sensor instead of our old one to determine if it is compatible with our new microcontroller, but we will begin assembling the parts together as soon as they come

 

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

Roughly assemble all of the electronic components to determine if they can all work together, and order potential parts that we may have missed out on to get a final idea of what the CAD design will look like with potential wire mishaps.

Posted on

Team status report for 02/24/24

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

Right now, the biggest risk to the process’s success is the unreliability of the seeed board. We decided to pivot away from it to a different board (though we are still deciding between Adafruit ble boards, the Arduino nano ble, the Arduino Uno R4 Wi-fi (which is bluetooth capable), and the bluetooth module for non bluetooth-capable boards sold by Arduino).

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

Yes, we decided to pivot away from seeed boards. This change was necessary due to the unreliability of these boards when connecting to our computers, hindering development. We will incur costs in purchasing new boards. We will investigate whether we can return our seeed board, but, even if we can’t, we still have substantial room in our budget to purchase new boards, as our original plan was well below half of our budget.

We also decided to begin using the Expo framework, on top of React Native. This is because it will simplify development (due to simpler, friendlier starter code, and smoother connection with bluetooth libraries). Since it is strictly a software change, with no licenses involved, it will not incur any costs.

• Provide an updated schedule if changes have occurred.

Some of the goals for bluetooth connection and app settings were moved back to allow for the new boards to arrive.

Posted on

Matthew’s Status Report 2/24

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

At the start of the week, I got started on soldering the SEEED microcontroller, as well as making modifications to the ultrasonic so that it could be directly connected onto the microcontroller, as well as accounting for reducing the length of the wires.

Unfortunately, Alan and I noticed the flaws of the SEEED microcontrollers, due to connection issues with our respective computers, so we are currently debating using a different microcontroller, such as an Arduino NANO BLE or Adafruit BLE models. We also reconfirmed the usage of the copper wire to be used as plates for a parallel capacitor setup.

 

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

I am ahead of schedule with testing, but behind schedule with bluetooth testing and overall assembly thanks to the issue with the SEEED boards. I will have more time next week to work on the boards or even finding new microcontrollers

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

By next week I am hoping to have received a new microcontroller setup, and making modifications to the sensors that we have so that we can assemble all of the components together onto a breadboard setup.