First, I cannot give Jamiei what he wants, because I inadvertantly violated the 1.6 PO2 setting I put into the Vyper today (chasing a fish to shoot - go figure - dinner was more important than the test, sorry) and cleaned its CNS clock, so to speak.
HOWEVER, I found a very interesting piece of data out while I was at it. I do have the profile from the dive, and it shows something that I did not expect.
I set a 1.6 PO2 in the computer. In fact, its STILL set to 1.6, and a 47% Nitrox mix (which I computed would put me between 1.4 and 1.6 PO2, thereby "tripping" the bug. Unfortunately I decended below 77', which invalidated the test....
BUT, when I downloaded the profile, SDM shows the PO2
in the display for the dive parameters and on the graph and computer "face" as 1.4! This despite the fact that I
explicitly requested 1.6 in the computer, it STILL shows the same 1.6 (I just checked - I was NOT drunk, stoned, or narc'd when I set the computer!) and the same FO2 that I had set.
Thus, it appears, to me at least,
that setting a PO2 of more than 1.4 on the Vyper is a noop in terms of its ACTUAL calculations, EXCEPT for where (or if) the PO2 alarm sounds!
That is, you can set it, and it won't *****
during the dive until you exceed 1.5 or 1.6, but
when you look at the profile later in SDM it not only doesn't pick up your 1.5 or 1.6 setting, it ALSO computes the "alarms" in the graph function as if it was set to 1.4! Worse, it does its "acceleration" thing based on a PO2 of 1.4, irrespective of what you set as your maximum PO2, and if its not 1.4, you get no warning that the acceleration took place unless you also violate your setpoint.
So basically, Suunto is grossly misrepresenting the settings available on this computer and what they do. There is no setting available for >1.4 PO2; despite it being there, it is non-functional and misleading to the diver. Further, there is a rounding error which can apparently cause the "over 1.4" PO2 acceleration to trip a few feet shy of the 1.4 alarm - and the alarm will NOT sound until a 1.5 or 1.6 setpoint is breached, even though the acceleration will STILL take place when 1.4 is exceeded.
This problem is, in my mind, somewhat MORE serious than I had first believed. Allowing a diver to set a parameter that should control the dive profile limits, displaying those limits (the MOD appropriately adjusts when the PO2 is changed) but then ignoring the setting the diver made in favor of an internal default is both a bug and quite dangerous.
Yet that, from a real dive and a real[/b] download today, is what we have here.
Unfortunately I toxed the computer on the first dive (badly enough that four hours later it STILL showed CNS off the charts) so I was unable to get anything useful on Dive #2. I will, however, take it with me again when I next get wet and will make another attempt to get a profile that adheres to the 1.4 < PO2 < 1.6 test sequence I intended for today.
I am including a point on the graph from the dive that shows what I'm talking about, however. After
manually resetting the PO2 in SDM to 1.6, which is where the computer is set, and going to a point only
three minutes into the dive, where depth over 77' has not yet been exceeded (look for yourself) I am showing 30% of the CNS clock gone.
AT THREE MINUTES OF EXPOSURE.
While the PO2 limits were exceeded just one minute later (and the rest of the test is thus invalid) this is pretty conclusive evidence of the acceleration that I'm talking about.
BTW, I looked at the computer just before going after that fish - and saw those same three bars, just three minutes into the dive - in real time.
