Scubapro G2 does, possibly some of their other models?
Welcome to ScubaBoard, the world's largest scuba diving community. Registration is not required to read the forums, but we encourage you to join. Joining has its benefits and enables you to participate in the discussions.
Benefits of registering include
You still haven’t answered why a 24 or 48 hour lockup is a reasonable solution to violation of a conservatism buffer, but not the M value.
No. It’s really one question. Just with an added clarification. But, you answered, so I appreciate it. Your reasoning makes sense for you.That's two questions.
No. It’s really one question. Just with an added clarification.
No argument there. However, there are situations that arise that may warrant cutting Plan A a bit short. I’ve been chased out of the water by sharks before. Didn’t break NDL, but I would likely use my judgment if I had a mandatory stop and faced with a similar issue.So, what is your deco limit? It is what your computer says it is depending on the deco algorithm it is running and the personal settings you have set. Some are more conservative and some are more liberal. Regardless, you are obliged to follow you computer.
That’s the crux of the issue. Does a minor violation warrant a 24 hour surface interval? Or would a shorter break be OK? It really is up to the individual. Setting GF Hi at 75 and overshooting to 80 is not the same as surfacing at 110.If not, you run the risk of violating deco and ending up in violation gauge mode.
I don’t think you meant this the way I’m reading it. DCS risk is dependent on time, depth, and personal factors. It is not dependent on the computer you use. Though some computers will let you get closer to the limits than others. I think that’s what you meant.The risk of DCS is dependent on time at depth, it will vary dependent on the computer you use.
Not even close. The mental leap from what I asked to this is dizzying.Yeah, just like "have you quit beating your wife yet" is really one question, just with a tiny little added implication.
Not even close. The mental leap from what I asked to this is dizzying.
You still haven’t answered why a 24 or 48 hour lockup is a reasonable solution to violation of a conservatism buffer, but not the M value.
That’s rich. Especially considering that my question was based on a rewording of your statement. So, perhaps the reason why you didn’t get a ”legible response” is because your questions have been loaded.There is a name for that dizzying mental leap: "loaded question". Read the wiki and be enlightened: Loaded question - Wikipedia
This was a rewording of your post. It is also the basis of my question that you called loaded. Your response without directly answering the question is enough for me to understand the logic (or lack of) behind your position.I still haven't figured out why anyone would set their conservatism to 75%, surface at 80%, and then think it's reasonable when the computer says they overshot their target setting and locks out for 24 or 48 hours. All my random poking and prodding here failed to elicit a legible response, so yeah: I don't understand. And I don't expect I ever will.
More computers going to Buhlmann ZH-L16C with GF. Too bad it's proprietary
There’s a lot of research pointing to using GF for deep dives.More computers going to Buhlmann ZH-L16C with GF. Too bad it's proprietary transmitters