problem 2.70

[nepturion]

hello, Sunday I did a dive to 98 meters x 25 min run time, when I compared my lifts OSTC 2 with two equal and there were very different values
gave my first stop at 54 mt and tts 74min, while the other two gave the first stage at 60 and 130 min tts.
while I climbed to get to the first stop at 54 mt, while I was at 57 pointed me to the stage at 60, so I had to go back down, then pointed me to the stage I climbed to 54 and while I was off again to 57 meters because 'signaled a breakthrough stage.
this is very strange

[Rob]

Hi Nepturion,

do you have CF25 activated?
Can you read the binaries (e.g. with ostctools) and post or mail them?

If both computers are really configured identically and both have the same firmware than iis really strange.

regards
Rob

[reivilos]

Well this looks like the problem I had with beta before ... Reaching a deco stop, and then the stop time shoots up from 1' to much more, and then the OSTC tells you that there is a deeper deco stop, so it goes "in the red" !
In my case it was only a 57m dive, I decided to continue the ascent according to back-up runtime, and the OSTC apparently became consistent again at the 9m stop.
But it is unsettling, because you lose confidence in the deco computation.

[reivilos]

May I add that on a previous 75m dive earlier in May of this year, my buddy had his OSTC MkII (running 2.50) suddenly display something like "Stop time 66'" (real expected stop time was maybe 1' or 2'), my OSTC 2N (also in 2.50 at the time) was normal and we continued the ascent by following my OSTC. Coming up to the shallow stops his OSTC went back to normal with TTS comparable to mine.