Of course it does, your time is on your watch till you hit the station and reset the bezel for the first stop. After that you only have to reset for each stop. Not rocket science.But with none of their history.
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
Of course it does, your time is on your watch till you hit the station and reset the bezel for the first stop. After that you only have to reset for each stop. Not rocket science.But with none of their history.
If you say so.Whereas computers vanish leaving behind a shimmering outline of the word GAMEOVER
That’s what I trained and practiced for, that’s how I know and that old you must be perfect remark is pathetic,How do you know?
My friends who got bent would have sworn they did not make any mistakes if they had not had a computer profile of the dive to show them what mistakes they mare.
Now, I realize there is a difference between people who are perfect and mere mortals.
I dunno, I find this stuff interesting! The discussion has helped me to understand things better. But let me ask you about the second method.
I don't know if some dive computers have an internal algorithm like you describe - one that converts the ambient pressure to a depth based on a specified salinity, and then compares that result to an MOD calculated from the desired maximum PPO2, known mix and salinity. But even if that were to be the case, salinity would still be irrelevant in terms of giving you an unsafe PPO2, since you are just mathematically putting the salinity constant (right or wrong) in, and then taking it back out again, right?
And yes, I agree, in the example you give, the diver would hit 95 feet (actual depth), the PPO2 would hit 1.4 and the alarm will sound, no matter what you set the salinity to. The only outcome of that salinity setting error would be that the DC display would erroneously read 98 feet, even though the diver was actually at 95 feet.
That's your run time.Of course it does, your time is on your watch till you hit the station and reset the bezel for the first stop. After that you only have to reset for each stop. Not rocket science.
Run time is the total time elapsed since leaving the surface. For the assent I reset the bezel on the bottom and when reaching the station for each stop, the deco times are on the slate. Max depth is the first number put into the calculations and doesn’t change, for me that’s the deepest I can possibly go on any particular dive. In the event that you don’t reach the max depth it makes the dive more conservative. All my dives are planned for a max depth.That's your run time.
- It does not show the actual depth you were at for the deepest portion of your dive. That was another of the errors my friends made. They were sure they had stayed at a specific depth throughout the deepest portion of the dive--OK, OK, they may have dipped briefly below that from time to time. Well, the computer showed those "dips" were more significant than they would have imagined.
- In general, it does not show the details of the mental calculations of depth and time you made before that, calculations you are remembering with dead certainty but which may not have been quite what you thought they were.
No I don’t and could you please quote where I said I exclude the time to the first stop, my dives are planned from the surface which includes the decent and assent and all deco. Deco is calculated to include the decent, bottom time and assent., or consider the dive time excluding the ascent time (as @mac64 says he is doing,