top of page

WEEK 3

We have confirmed with our client, Dr. Vesoulis, that we will be working with him this year. We have created our need statement, project scope, and have 13 initial design specifications. We are still working on adding more design specifications and adding specificity to already listed ones. We have come up with several topics to research, including metabolic carts, scuba diving, and types of sensors, and each of us is assigned to research one of these topics. We have found a preliminary sensor, an optical oxygen sensor. The next steps are figuring out if that sensor will work and if it can interface with Arduino and/or Matlab.

WEEK 4

The three of us have done research in scuba diving, metabolic carts, and oxygen sensors. We have learned more about the effects of increasing the partial pressure of oxygen, and we are hoping to observe the next Peak VO2 testing at Paraquad. We have also found an existing oxygen sensor, LuminOx Optical Oxygen Sensor, that we think could be useful for our project. The link is included below. We are planning on reaching out to the company to learn more about the sensor and how it works. We are also meeting early next week to put together our project timeline for the first semester. 

WEEK 5

We have continued our research on sensors and have found a galvanic cell type oxygen sensor, the GS Oxygen Sensor KE-25, that seems better suited for our application. We have contacted the company that manufactures them and have received forms containing technical information, precautions, and other product information. We are currently reading through these forms and taking notes on how this type of sensor works and what precautions we will need to take if we decide to use this sensor. We are in the early stages of writing our preliminary report and are planning on finishing it at our team meeting this weekend. 

WEEK 6

This week we focused on writing up our preliminary report. We did some patent and literature searches to find out if there are any existing solutions out there, but we did not find any. We found that many oxygen delivery or recording devices are either not made for infants or do not store the data they record. Also, many devices seem to be concerned with the patient's metabolic output rather than the input of oxygen, or other gases. We also started to work on our preliminary presentation which we will be giving on Monday.

WEEK 8

This week Chloe started working on our project's website. We also created an email account specifically for the project which can be used to access the website. Dr. Vesoulis emailed us about potentially sensing pressure as well as oxygen in the device, so we now have to cnsider if this is doable with our timeline and budget. We plan to meet and brainstorm ideas next week. 

WEEK 9

We submitted our webpage URL, and have been adding to and editing the webpage. We have a brainstorming session planned for this weekend to hash out more details about a potential prototype and we will also be adding information to our notebook to ensure that it is up to date. 

WEEK 9

WEEK 10

This week our team met to start discussing potential designs for the project. Before we figure out how to store and transfer data, we have to devise a way to record the oxygen delivery. Our initial idea is to purchase an oxygen sensor and insert that into some tubing that we can connect to the tubing used for oxygen delivery in the NICU. We spent some time discussing the pros and cons of various locations for our piece of tubing. We determined the best location is likely right before the tubing connects to the heater/humidifier since this device is used in everything oxygen delivery system. An alternate design we discussed was trying to access the data that is already being recorded by the hospital's computer monitors. However, Dr. Vesoulis had advised against this due to the complicated software and communication systems in place in the NICU. Additionally, we know that whatever oxygen sensor we choose needs to be compatible with Arduino and Matlab. Right now we think we are going to go with the Figaro KE-25 oxygen sensor (http://www.figarosensor.com/product/entry/ke-25.html) because it fits our criteria and Dr. Vesoulis said it looked like a good option. We have a meeting scheduled with Dr. Vesoulis for Friday (11/1) at 12:30pm to go over our current design ideas and see if he has any other alternate design ideas. 

WEEK 11

Last Friday (11/1) we met with Dr. Vesoulis to go over our initial design ideas. We added the notes from that meeting to our Client Meeting Notes folder in LabArchives, but in general he is happy with our progress and likes our design ideas. For next steps, we need to brainstorm more about additional alternative solutions. Specifically, we need to start thinking more about which method to use to transfer data and how the data will be displayed. We are planning on meeting next week to go over some more ideas and start working on our Pugh chart. 

WEEK 12

This week we met as team and went through our Pugh charts for various parts of the project. We created a Pugh chart for each possible location, mechanical alternative, software alternative, and sensor. We then went through the process of listing out the important design specs for each different Pugh chart. Then we weighed the design specs and went through the process of scoring each solution. We think we're close to a final solution, but would like to discuss it with Dr. Klaesner before we submit the Progress Report. Our plan is to stop by office hours on Monday the 18th.

WEEK 13

We have completed our Pugh charts and based on the scores we will be using an electrochemical sensor with a bluetooth Arduino board and connected by a t-tube implementation in location 3 (right before the heater/humidifier). On Monday we met with Dr. Klaesner to go over our various Pugh charts and the main comment he made was about expanding the potential USB solution to specify whether that was a USB cord, flashdrive, or IDE board connection. We have updated those Pugh charts and begun writing our Progress Report. Additionally we updated the design specifications.

WEEK 13

We have completed our Pugh charts and based on the scores we will be using an electrochemical sensor with a bluetooth Arduino board and connected by a t-tube implementation in location 3 (right before the heater/humidifier). On Monday we met with Dr. Klaesner to go over our various Pugh charts and the main comment he made was about expanding the potential USB solution to specify whether that was a USB cord, flashdrive, or IDE board connection. We have updated those Pugh charts and begun writing our Progress Report. Additionally we updated the design specifications.

WEEK 16

This week our group completed our Yellow Stickies Project, which outlined the tasks that we have to complete this semester and the due dates for each task. We met on Wednesday briefly as a team before our second semester meeting with Dr. Klaesner to discuss which parts of the project we needed help with. During our meeting with Dr. Klaesner, we discussed the most challenging aspects of our project, such as how we can test our prototype and write code to interface with the Arduino and display the oxygen data. Chris ordered our oxygen sensor and Arduino Uno, which together totaled about $110. Next week, we will start our CAD drawing so that we can 3D print our T-tube connector. 

WEEK 17

This week our oxygen sensor and Arduino Uno arrived in the mail. Since they arrived on Thursday, we were not able to start the CAD drawings this week. We will therefore be starting the CAD drawings this weekend or next week. We are also planning on talking to our client Dr. Vesoulis to update him on our project status and ask about his ideas on how we can test our prototype.

WEEK 18

This week, we created a CAD drawing of our T-tube connector, and are planning on making a request to get this connector 3D printed within the next of couple days. We also reached out to our client Dr. Vesoulis and updated him on our project status and asked him about his ideas on how we should test our prototype. Next week, we will start to research how to put together our circuit. 

WEEK 19

This week, we got our T-tube connector 3D-printed but the dimensions are incorrect, so we are adjusting the dimensions and are planning on making another request. We are currently waiting to hear back from our client about his ideas on testing our prototype. Additionally, we began research on how to put together our circuit and are planning to start building once we have our T-tube connector with the correct dimensions. 

WEEK 20

This week, we 3D printed our second T-tube connector with the correct dimensions and verified that this T-tube fit onto the humidification chamber and the oxygen sensor. Additionally, our team met this week to discuss our plans moving forward. We brainstormed methods of verifying our design specifications and are planning to start working on the Validation and Verification Paper this upcoming weekend and next week. Next week, we are meeting in Widder's lab to set up our circuit and begin writing code for the Arduino to communicate with the sensor. We are also currently talking to our client, Dr. Vesoulis, on ways to test our prototype. He has suggested using a respiratory setup (bubble CPAP or servo-i on a mannequin or test lung) where we can turn the FiO2 up and down. We are planning on setting up a time with Dr. Vesoulis to start testing once we have our circuit and Arduino setup, most likely within a few weeks depending on Dr. Vesoulis's availability. 

WEEK 21

This week we set up our circuit by connecting the oxygen sensor's cathode to the Arduino's A0 pin, the sensor's anode to the Arduino's ground, and the Arduino to a laptop via a USB cable. Additionally we wrote a small amount of Arduino code to ensure that we could get our sensor to communicate with the Arduino. Since we successfully outputted voltage values from the sensor, this completed our proof-of-concept testing. The next step is to calibrate our sensor so that we can output accurate oxygen readings. We have also started FDA research and have begun to work on our Verification and Validation Report. Next week we plan on completing this report. 

WEEK 22

This week we focused on finalizing our verification and validation paper, as well as creating the presentation. We are turning in the V&V paper today and meeting with Uri about the presentation. We are still waiting to hear back from Dr. Vesoulis about the respiratory setup we will use for the device simulation and testing. We are turning in the V&V paper today.

WEEK 23

This week Hannah presented our Verification and Validation Report. We also started researching how to convert voltage to oxygen readings in the Arduino code by looking at the oxygen sensor's manual. 

WEEK 25

This week we reached out to our client to see if he would be able to help us test our prototype. Due to the COVID pandemic, access to the hospital is extremely limited, so we are unable to complete our testing. As a group, we discussed that we should be able to complete the other aspects of the project, including obtaining oxygen readings and transferring these measurements to Matlab to be displayed. There is no way, however, for us to ensure accuracy of these readings. 

WEEK 26

This week we calibrated the oxygen sensor so that it would output an average of 21% in ambient air. By taking a voltage reading every 2 seconds, we acquired 100 voltage readings and then averaged over these values. Once we had the average voltage output we used this value and the fact that oxygen percentage should be approximately 21% in ambient air to create an equation relating voltage and oxygen percentage. With this equation, we are able to output oxygen readings with an average of 21%. 

WEEK 27

This week we started working on the final report and started researching how to use App Designer to create a GUI to be able to display oxygen data in Matlab. Next week we will continue to make progress on the final report, start on the technical drawings, and continue to work on creating the GUI. 

WEEK 28

This week we have continued to make progress on the final report and our App Designer GUI for displaying and saving oxygen data. We have also started working on the design safe analysis. 

bottom of page