limeyx
Guest
PerroneFord:I dive with a Vyper. Normally in guage mode. My question is why must it be in guage mode?
For those who own this product, you'll know that the logging has some enhanced information when the computer is used in it's normal mode. I'd really like to have that info in my logs. It will also track CNS and OTUs when used in nitrox mode.
It seems to me, the decision is whether or not to rely on the NDL information in the computer, as that is not in keeping with the DIR mindset. Does anyone see anything wrong with actually using this thing in nitrox mode but diving it to the tables?
Second question, would it be against DIR thinking to use the NDL information as a "bailout"? For instance, assume I have planned a 90 dive on EAN32 to 75ft. I do the dive, but because of an issue, I bail at 60 minutes. Normally, I wouldn't cut tables with that wide a lattitude for under/over. At that point, would it be taboo to rely on the computer's deco info? If the computer failed, I could always use the original deco schedule. But it might be nice to get out of the water a bit sooner. This, of course, assumes that the Vyper would give a deco profile I'd agree with in the first place, and I've never tested it for doing a real deco dive. I could run a simulation I suppose and see what it came up with versus VPlanner.
Thanks for your thoughts.
Not sure what "extra?" info t logs, but
CNS = Bottom Time/2 + Deco Time on 50% /2 and
OTU = BT*1.5 + DT *1.5
seem pretty easy to do in your head.
for a 90 min runtime at those depths, you are going to be in mandatory deco (which I dont think you are trained for?) and I definitely would NOT rely on the computer for "bailout" -- rely on your own profiles stored in your head and your team.
If you are the one running deco (even min deco) take an easy dive and either miss a stop or make a stop 1 minute too long. If your team doesn't alert you, you need to talk to them ...