My wife and I are planning a dive tomorrow, with the goal of practicing basic skills such as buoyancy and finning technique. I'd also like to experiment with how our dive computers respond to safety violations, but am unsure how to do that in a safe way. (we are using Mares Smart, but I suspect the answer will not be model specific).
At our beginner stage of diving, I am most interested in seeing how our computers respond to excessive ascent speeds. The manual says they will beep and flash, but I have not found any way to simulate this behavior outside of an actual fast ascent. It seems to me that it would be good to learn what the alarm sounds like, while underwater and actually ascending, before I might need to recognize this during an emergency situation.
I guess I could ascend quickly just long enough to set the alarm off, but it doesn't strike me as the greatest idea to do even a little bit of something dangerous as part of a practice intended to increase safety! Also, at my current level of buoyancy skill I think I could start and then successfully arrest such an ascent, but am not absolutely sure of that, and would prefer not to find out by trying and failing
Are there better ways to practice this?
Looking to the future, the same question applies to NDL violations and decompression stops. To be clear, I have zero interest in ever intentionally going into required decompression, but before going deep would like to learn how my computer responds in case something were to go wrong.
I've read about people diving on Nitrox with a computer set to air (so the computer will exceed NDL while they are actually still inside it), or using two computers with one set to a more conservative algorithm (so they can exceed NDL on one while actually still being fine according to the other). Neither of these approaches sounds great to me, because:
I'd love something like a 2x multiplier setting, so I could tell the computer to treat my 50 foot dive as 100 feet, and a 25'/min ascent rate as if it were 50. But that appears not to exist...
At our beginner stage of diving, I am most interested in seeing how our computers respond to excessive ascent speeds. The manual says they will beep and flash, but I have not found any way to simulate this behavior outside of an actual fast ascent. It seems to me that it would be good to learn what the alarm sounds like, while underwater and actually ascending, before I might need to recognize this during an emergency situation.
I guess I could ascend quickly just long enough to set the alarm off, but it doesn't strike me as the greatest idea to do even a little bit of something dangerous as part of a practice intended to increase safety! Also, at my current level of buoyancy skill I think I could start and then successfully arrest such an ascent, but am not absolutely sure of that, and would prefer not to find out by trying and failing
Are there better ways to practice this?
Looking to the future, the same question applies to NDL violations and decompression stops. To be clear, I have zero interest in ever intentionally going into required decompression, but before going deep would like to learn how my computer responds in case something were to go wrong.
I've read about people diving on Nitrox with a computer set to air (so the computer will exceed NDL while they are actually still inside it), or using two computers with one set to a more conservative algorithm (so they can exceed NDL on one while actually still being fine according to the other). Neither of these approaches sounds great to me, because:
- They require additional training (Nitrox) or equipment (two computers) that I don't expect to have any time soon.
- Even using these tricks, pushing a computer outside NDL requires a long and deep dive. But I want to practice using my computer on a shallow, easy dive, as preparation for perhaps later diving deep. It seems needlessly risky to have to push almost to the limit in order to practice what happens if you ever accidentally went past that limit.
I'd love something like a 2x multiplier setting, so I could tell the computer to treat my 50 foot dive as 100 feet, and a 25'/min ascent rate as if it were 50. But that appears not to exist...