Several are working on CO2 monitors and at least one manufacturer has a O2 injection if the loop PO2 falls below .19. But more importantly, where does the error-proofing stop? At what point do we say there are some requirements of the diver? I personally prefer to have my unit provide information and let me decide what to do. There are safety protocols built in but ultimately it is my job to run the rebreather, not vice-versa.
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.
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