rjack321:To this I say...
Its not error proofing as much as its designing a system which stays on the road by itself. Can't cross the double yellow or the white shoulder lines.
But if you say left it goes that way. You do control all the various manipulations to get the ppO2 to rise or use off-board gas as a SCR whatever. But then there are some inherent rules of the road which limit your abilities. Tough - its for your own good.
In the new stealth fighter (F22 I think its called) the plane can pull an enormous turn, 20gs whatever. But the onboard computer limits the turn capability to make sure the pilot doesn't pass out in the process.
There seems to be a general attitude that most divers want to control their own RB using the info provided. But if you foolishly tell it to pull 20gs and pass out (e.g. by using the dilutant button when you should be using the O2 button on a mCCR is wheer I think this happened) That's a design flaw IMO.
Your example may be backwards. The only place I can think of where adding dil instead of O2 is bad is if you are on the surface and diving a trimix of 18/xx or less. Adding O2 when you meant to add dil can be very bad at depth. Either way, good point of what people have done to try and hurt themselves.
So here's what has happend in the last several years along those lines of development. Electronics have become dive smart - auto on. Electronics have added HUDs, buzzers and vibrating components to "inform" the diver of issues. But the haven't gotten here w/out controversy. Do you like a car that constantly beeps because you don't have your seatbelt on? (not a recommendation or an endorsement to not use a seatbelt in a car - always drive responsibly ) This goes on and on for nearly every part of any rebreather. You get the idea.
So how do you keep someone w/ their finger on the button... the O2 MAV from going hyperoxic? Have the computer monitor PO2 and inject dil when PO2 goes past 1.6? How is the diver suppose to keep from blowing to the surface w/ all that added buoyancy? Not a slam, just giving you a flavor of the stuff that gets "discussed" in the RB cyber world.
rjack321:The Cis seems to be an exception to this information but not that much computer control concept. The Kiss being one unit on the other end of the spectrum (as far as I can tell).
Am I way off base here? We can talk about internal fault correction next
It's been a while since I've touched the Cis on a table or talked to the owner, who was my RB instructor, so I can't list all it's shortcomings. Most everyone will agree that it was ahead of its time but those that know it will also say that the manual for it and the training was more like learning to fly intruments than take private pilot lessons. For non aviation folks, the difference between learning to drive an automatic car and a motorcycle. It was far from automatic. Any Cis gurus, feel free to flame me here.
trob09:Several are working on CO2 monitors and at least one manufacturer has a O2 injection if the loop PO2 falls below .19.
Not sure I understand what you are saying? My electronics injects O2 if the PO2 falls below the setpoint that I configure (i.e. .4 or 1.2) and non of them allow me to set the PO2 below 0.21. Most make you have something higher than 0.3. Not a slam but sounds like you are talking about adding a setpoint controller to a mCCR (mechanical). Trying to automate a dil flush for high CO2 has other issues other than just making a functional CO2 sensor system.
But deciding HOW to do something is part of the problem. Some makers and divers would say to inject O2 but others may say to inject diluent. Some say you need a wet switch and others say no. Look at all the debate we have just here on what needs to be fixed and what is right. We're getting there. Maybe if we can get one these Yahoo or Google founders to bring money and their type of innovation to the business.