A bunch of words on dive computers

Please register or login

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

  • Ability to post and comment on topics and discussions.
  • A Free photo gallery to share your dive photos with the world.
  • You can make this box go away

Joining is quick and easy. Log in or Register now!

immersed

Contributor
Messages
72
Reaction score
1
Location
Tucson
I'm placing this here instead of under Equipment/Computers because the information applies to all dive computers regardless of brand or type, and I believe it's more of an issue for new divers – seasoned divers generally become aware (albeit some sooner than others <grin>) of the subject at hand. I apologize for it being so long, and hopefully you can work your way all the way through it.

At some point during your dive training, someone describes the various equipment used, telling you what each item is and what it does. You learn about what an SPG is, what a BC is used for, why you get two regulators, why compasses aren't just for scouts, etc. Dive computers are almost invariably mentioned, along with a statement similar to "dive computers are great because you can dive longer on a computer".

Our time in the underwater universe is limited by essentially two things: air supply and nitrogen absorption. Nitrogen is what "the bends" are about, but you'll probably find that once you're edjumacated you don't call it that very often. In very simple terms, the deeper your dive, the more nitrogen you absorb. The longer your dive (in terms of time) the more nitrogen you absorb. The subject is actually a lot more complex, but keeping in mind the title of this forum and the real intent of this thread, we're just going to leave it at that.

Before dive computers, and for those who dive without them (and believe me, there are thousands and thousands), nitrogen absorption is primarily determined with the use of a table called the Recreational Dive Planner. There are other methods, but we're not going to go into those. You use the table by looking at the maximum depth of your dive and the total length of time of your dive.

Recreational divers usually don't descend to the dive's maximum depth, spend the entire length of the dive at that depth, and then ascend to the surface. A more common dive profile is composed of various depths and times. When you use the RDP, you are determining a 'worst case' by pretending that you were at that maximum depth for the whole time.

A dive computer 'credits' you for those shallower depths by keeping a running tally of your actual depth and time spent. The computer, then, is more realistic, although the worst-case conservatism from the table is lost. This is how you can 'dive longer on a computer'.

I have worked with computers in some form or fashion for almost 30 years. I have worked with them long enough to know to never trust my life to one, at least not if I can possibly avoid it. Computers are designed and built by humans. Humans make mistakes. Ergo (woohoo haven't used that word in a long time) computers can make mistakes. We often think of computers as being smart, but they really aren't. They're the dumbest things on earth. They can only do what they've been told to do, and they make up for dumbness by being really, really fast.

Computers are so embedded in our lives that if you are a passenger on a jet or in a car or on an elevator, you are to some extent trusting your well-being to a computer. However, each of those systems has some sort of backup, be it mechanical or human. Jets these days are actually capable of taking off from an airport, navigating and flying to the destination airport, and landing themselves. But would you get on a jet that had no pilot? How about come snack time, the whole gang left the cockpit and sat down to eat peanuts and watch the movie – would you maybe get a little nervous?

I'm not saying to not use a dive computer – on the contrary, I have a really nice one that has a feature called 'air integration' – the computer is hooked up to my tank so it knows what the tank's pressure is. The benefit to the computer having this knowledge is that it can tell me how much air I have left in terms of time. Even cooler, it gave me real-time biofeedback and taught me how to breathe to achieve maximum airtime. A computer tells you how many minutes you have left in terms of nitrogen absorption, and of course the depth, length, and even the temperature of the dive.

HOWEVER, I know that this is nothing more than a tool of convenience for me, and I do not rely on it to do my dive for me. I know that its airtime remaining estimate is a snapshot of the moment; if I add air to my BC, the estimate is wrong. If I am particularly motionless (not exerting myself) while watching some creature, it's wrong. If I change my depth, it has to catch up. At any moment the computer could 'go on the fritz' completely or, and this is much, much worse, it could experience some sort of hiccup that causes it to give me wrong information. If I've been galavanting around at 80 feet/24 meters for 30 minutes and my computer keeps telling me I've got an hour of no decompression time (the nitrogen absorption thing) left, it's wrong. I have to know all of these things in order to detect the computer's falsehoods and for it to continue to be a useful tool. In other words, you have to understand what it's telling you, why it's telling you that, and when it's anything less than accurate.

The computer manufacturers test the stuffing out of their computers, and generally their reliability is quite high. However, once in a while a series of computers is recalled for some reason or other, and someone had to be the first one to encounter the reason for the recall. Further, the computer manufacturers can't look over your shoulder every day to make sure you're keeping the thing clean and replacing the batteries. Computers are finicky about the quality of their power, and corroded contacts or an aging/defective battery can cause unpredictable results.

Backup equipment is definitely an option but ultimately your best backup is the one between your ears and no amount of equipment replaces it. Use the computer, but don't be dependant on it. You're already smarter than it is, but you need to know at least as much as it does in order to keep your eye on it. You do that by learning how to use your RDP. Use it over and over and over, and you'll find that you'll gain real-time insight into where you are in terms of nitrogen absorption. Take the time and effort to determine your air consumption under different circumstances and take that into consideration in your dive plans. 'Physics' can be a scary word for someone who's not into science and math, but the physics of diving is really not very complicated – if you can ballpark a tip for the server at the restaurant and you know when you've been shortchanged by a cashier, you can learn it. It's important to understand why your air supply goes bye-bye a lot faster at 60 feet/18 meters than at 10 feet/3 meters. Get a waterproof watch and independently track the time of the dive.

"To err is human, but to really foul things up requires a computer". The whole reason we take the trip is to watch the movie. But don't forget that you are gonna have to land the plane.
 
Like I was taught, GIGO, Garbage In Garbage Out. No computer is any "smarter" than the programmer.
 
Very nice post, immersed. What prompted you to post on this topic?
 
No computer is any "smarter"...
Exactly true. Even when a group of programmers works on something, mistakes can still slip through the cracks.

jbd:
Very nice post, immersed. What prompted you...
Thank you. I had these thoughts when they told us about dive computers on the first night of OW class, and I've had the concerns ever since; people tend to think of computers as magical infallible machines. There was recently a thread in this forum on computers vs. tables. I almost replied then but knew that I'd be typing way more than 2 cents' worth and I didn't see a good spot to interject my thoughts (the thread had started to wander a little). Anyone who reads through all of it can pick up on some of the things I've said, but at least here it's all in one long ramble.
 
I am a new diver, but I have learned through life to always have a back up plan. I do consult my RDP to ensure that I know the maximum time I can be at the planned depth for the mix I am using, as well as taking PO2 into account. I then back 1/3 off of it to work with the "oops" factor (murphy lives!!). While this isn't the same as doing a full plan with the RDP, it does give me a small back up to my computer. But, as I was taught by my instructor and from the LDS that I bought the computer from, if anything does go wrong with the computer, surface. I have a spare set of gauges in my gear bag in case it goes bad also, as well as my tables in my log book just in case.
 
Everything you said is exactly why I have a difficult time with the agency that no longer teaches tables in OW and has their instructors issue computers to all their divers. Although I dive with a computer as well, I don't leave my brain at the dock and recogonize that the computer is a tool. Better IMO than an SPG because of the information it gives, but also carries more risk for the person who follows it blindly.
 
I under stand the need to have some redundancy, and the human brain is an amazing thing. However, if you are using the RDP to figure a rough estimate to check your computer against. What happens in a situation where you are going to do a wall dive where your deepest depth will be say, 92 fsw. The tables tell you that you (rounding up to 100) have a max of 20 min. As you ascend your computer will tell you have more time and the shallower you go and the longer you stay shallow the more time the computer will give you. I don't follow how you use that information to check up on your computer.
 
It's actually quite easy to do once you figure it out. The hard part is trying to explain it to someone else. :)

Take your RDP and plan a dive to 60ft for 30 minutes, then 40ft for 30 minutes.
According to PADI's RDP, after 30 minutes you're in pressure group L. Now you ascend to 40 ft. Pretend you have a surface interval of 0 minutes which leaves you in the same pressure group as before. Now switch over your third table which lists residual nitrogen times. Find the intersect of 40ft and L. According to the table you have 51 minutes of residual nitrogen time. For comparison, look at table 1 and see what time at 40 ft gives you a pressure group of L. A 60ft dive for 30 minutes is equivilent (in terms of nitrogen loading) to a 40ft dive for 51 minutes. Add the 30 minutes you want to stay at 40 feet and you get 81 minutes which places you in pressure group S.

Congratulations, you have now planned a 60 minute multilevel dive. By keeping this in mind you should be able to tell when your computer is acting up. Or you can just plan conservativly, stick to your plan and let your computer keep track of bottom time.
 
Good grief jokeborn, that sure looks like pretty full planning to me! Diving with you might keep me even further from the edge of DCS than I currently do (which is pretty far - I don't like the sound of 'permanent paralysis').

DiveMe, IMHO you've got the right attitude.

Doc, thanks and thanks - it's an interesting place to be sure. I've already learned some great stuff from you, bigjetdriver, jbd, UP, Diver0001, stirling, and others too numerous to mention.

ciret, for a wall dive I would plan a multi-level dive with The Wheel (tm) RDP. If I were a real tough guy :crafty: , I might even work up a couple of contingency plans & write them on my slate to follow in case the first plan didn't work well with where the cool stuff was - or ask the DM on the way out. On the few wall dives I've done, the DMs gave great briefings on what depths had what features and critters.

On edit (should've refreshed before posting):
SeanQ, I lent my wheel to a friend so he could learn how to use it - does that really work? Seems reasonable...
 

Back
Top Bottom