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.
So redundancy is the name of the game. Do you run two of the same computers? Do you run a computer and a bottom timer? Two different computers? I currently dive a Petrel 2 and I am starting an/dp so I need a backup solution, and I'm wondering what other people are doing. I have thought about picking up another petrel 2 so they would be / function identically, but the idea of both computers running the same firmware / software seems like it could be construed as a single point of failure.
I agree that the same computer with the same firmware is a single point of failure.
My primary computer is highly readable. My backup runs the same algorithm but is not as readable (and was a lot less expensive), which I am perfectly okay with.
On deep dives and/or on charters dives where I paid for each dive in advance I use two identical computers, a watch and depth gauge. On every local dive I use a watch a depth gauge and on some of those dives one computer, mostly as an easy read BIG numbers depth gauge and for easy reference data for my log.
Most of my 2000+ logged dives were done without a computer. As a result I don't consider a computer as essential equipment and often dive without one.
I'm unclear how two separate pieces of gear can be considered a single failure point. If one stops working, the other still functions.
So redundancy is the name of the game. Do you run two of the same computers? Do you run a computer and a bottom timer? Two different computers? I currently dive a Petrel 2 and I am starting an/dp so I need a backup solution, and I'm wondering what other people are doing. I have thought about picking up another petrel 2 so they would be / function identically, but the idea of both computers running the same firmware / software seems like it could be construed as a single point of failure.
Anything you can use as a bottom timer. We mostly use the Uwatec/scubapro 330. You wont be using a wrist mounted computer to plan your dives. Money better spent on software like multideco for your laptop, ipad, iphone for planning.
I'm unclear how two separate pieces of gear can be considered a single failure point. If one stops working, the other still functions.[/QUOTE]
Software or firmware that has the same bug in the code that triggers at the same time rendering both computers inaccurate.
@AfterDark the risk is that if there is a software problem that is inherent to the firmware, the same computers have the potential to encounter the same error at the same time. I don't personally think it's anything to worry about, especially since there are a lot more potential and likely problems of having to use two different computers. Different GUI, different gas switching procedures, etc etc etc
I'm glad @PfcAJ posted his comment. We do not dive with backup computers. My buddy has my backup computer and I have his. We don't do dives quite like AJ, very few do, but we are still regularly doing 3+ hour cave dives with fairly significant deco obligations and that is assuming the dpv's don't fail and we have to kick out. The primary plan is in the event of a computer failure, we will basically ride out the others decompression schedule and usually pad with an extra 3-5 minutes just because one persons gas mix may be a point higher or lower than the other. We run identical algorithms with identical gradient factors, and since we get our fills at the same time from the same place, the gas mix is usually identical. We do carry watches with us though. When we end up on CCR next year we will each have a backup computer because of the slight variations in loop PO2, but it will mainly be because we already have the standalone computers....
Software or firmware that has the same bug in the code that triggers at the same time rendering both computers inaccurate.[/QUOTE]
That's a rather remote possibility. I'm a lot less trusting of the hardware. I build and test hi-tech mass data storage equipment. My experience is that the code issues usually show up front, although I do agree it's possible.
That's a rather remote possibility. I'm a lot less trusting of the hardware. I build and test hi-tech mass data storage equipment. My experience is that the code issues usually show up front, although I do agree it's possible.[/QUOTE]
it's remote, and I don't believe it's an issue, but it's there. In the US the decision is pretty simple though. For serious technical diving, you basically have Shearwater or Shearwater.... Pick your poison between Petrel, Nerd, and Perdix but that's about all we have.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
