ligersandtions
Contributor
My husband and I were meeting a friend to make a night dive Saturday. While we were setting up our gear, he turned his computer on to see what pressure he had in his tank. For some reason, the computer thought he was already diving....he was standing at our truck, 30 feet above sea level, and his computer thought he was diving. It went through some dive profile of sorts, and then finally stopped at 46 feet or something like that....it was showing that he was at depth and his remaining air time (note that the air pressure in the tank was not decreasing, but for whatever reason, it would show that he had less and less air time).
While he was "at depth", the computer was keeping track of his dive time. Not wanting to call the dive, we decided to make a very conservative profile and that I would be continuously monitoring what his air pressure says versus what I would expect his air pressure to be based on mine. We went to a max depth of 82 feet and his computer said his max depth was 113 feet. We were at depth long enough for him to exceed the NDL (takes a whole lot less time at 113 feet than at 82) even though we were nowhere close in reality.
Obviously, not wanting to do 40 minutes of deco, we did not comply with the computer's wishes and it completely locked up. My questions are: what in the world would make this computer do that, and is this a known issue? And if you end up locking out your computer by not complying with the deco obligation, is there a way to reset it so it doesn't screw up subsequent dives?
While he was "at depth", the computer was keeping track of his dive time. Not wanting to call the dive, we decided to make a very conservative profile and that I would be continuously monitoring what his air pressure says versus what I would expect his air pressure to be based on mine. We went to a max depth of 82 feet and his computer said his max depth was 113 feet. We were at depth long enough for him to exceed the NDL (takes a whole lot less time at 113 feet than at 82) even though we were nowhere close in reality.
Obviously, not wanting to do 40 minutes of deco, we did not comply with the computer's wishes and it completely locked up. My questions are: what in the world would make this computer do that, and is this a known issue? And if you end up locking out your computer by not complying with the deco obligation, is there a way to reset it so it doesn't screw up subsequent dives?
