开云体育

you want to find the orbit brand of valves to use for the expiratory valve.

Thanks for the excellent suggestions!

Gordon - great idea on the PCB, and if it's still an option, I would be very interested to see your PCB.? One of my team is working on his own PCB design based off of some different components on his end, whereas I am working on the more OTS version.

Steve - Re: valves, we do plan on integrating a NO valve for exhalation, but very good note nonetheless!? Rainbirds were unfortunately a bit harder to come by for me right now, but I have some on the way.

Tom - As for buttons - I am looking into easy to find waterproof buttons (re: Steve), but I had no idea about this button design potentially failing.? Thanks for the head's up!

On Thu, Apr 23, 2020 at 11:06 AM, Alex Gravenstein wrote:

This is a demo of our current software design. v0.8

Looks really good.?

Just make sure in a unit for actual use you use a better button. If the buttons are the type they look like, one or both pins will push back out of the back of the plastic and the buttons will fail to make contact. Doesn't take many presses for this to happen. Maybe those are an improved design, like better stronger plastic, but best I can tell these buttons have had the same design for over 20+ years.?

Tom, wb6b

Hey Alex, nice work!

I like the menu system and the red LED with the alarm. One concern from a clinical perspective is the adjustable time on the alarm mute. The mute is just meant to temporarily silence the alarm while you are actively addressing the problem. A long alarm mute could give the false impression that the problem has been fixed, particularly if the operator forgot that they set a long duration, or if it was changed on a? previous shift etc. Nearly every other monitor I'm aware of has a non-adjustable 2 min alarm pause, so that's what we're accustomed to. A significantly longer duration is a potential source of error. If you
This is just my opinion of course, other clinicians may have other thoughts.

Two other things that I learned from own design.
1: Is that potentiometer just for backlight adjustment, or is that part of your user input? If your final design involves a pot, keep in mind that waterproof pots aren't as easily available as say, waterproof buttons.

2: If both of your valves are normally closed, it might be a good idea to either have a backup non-electrical valve or at least design the software so that as soon as the device is powered, the expiatory valve locks open until active ventilation begins. This way if the MCU resets and doesn't immediately begin ventilating, at least the system will be open for the patient to breath spontaneously.?


Keep up the great work

Steve S

Hey all,

This is a demo of our current software design. v0.8


It should be readily adaptable to the UF team's hardware design, for those who are following a similar approach.

Our main focus is readability, adaptability for various sensors and valves, as well as aiming for an intuitive menu system.

75% Program Space
45% Dynamic Memory

Highlights:

• sensor disconnect/reconnect support (still has some problems)
• alarm submenu, including muting alarms
• options submenu, including testing plateau pressure and calibration
• "Cancel/Confirm" validation for certain tasks

What we are still missing

• use of a second BMP280 (we have analog pressure sensor support)
• Assisted breathing
• Flow measurement

If anyone has any thoughts or concerns they would like to share, then we would like to hear them!

Cheers,

-Alex