It's page 9 on this thread. Let's do a TLDR.
Don't use computers from different manufacturers and expect the same results.
Don't use computers from different manufacturers and expect the same results.
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
I got a different TLDR:It's page 9 on this thread. Let's do a TLDR.
Don't use computers from different manufacturers and expect the same results.
Nope. Two computers using the same mathematical model with exactly the same parameters should yield similar results.It's page 9 on this thread. Let's do a TLDR.
Don't use computers from different manufacturers and expect the same results.
I found a similar issue with OSTC: Ceiling on 2nd dive - forum.heinrichsweikamp.com Just like here, with comments about computers being different, it was hard to get anyone to even understand that there was an issue.That's the plan. But which one though?
Shearwater or OSTC?
To have a third term of comparison, we set up Subsurface with BUL settings and gradients 70/85. The result from Subsurface would have been even more conservative compared to both dive computers. (in the images, the deco suggested by Subsurface is shown in green, the one by RATIO in red).
For anyone interested i am attaching the logs here:
Garmin VS Ratio – Google Drive
drive.google.com
I found a similar issue with OSTC: Ceiling on 2nd dive - forum.heinrichsweikamp.com Just like here, with comments about computers being different, it was hard to get anyone to even understand that there was an issue.
Since it doesn't really affect my diving I didn't really put more effort into investigating after that. Looking back at those dives I do get Subsurface and OSTC to line up if I shorten the surface interval and works the same on a few other dives that I have. So now my guess is that the OSTC is counting time a bit too slow when it's in sleep mode on the surface. I'll see if I can do some more investigation next time I go diving. Maybe keeping the OSTC awake during the surface interval gives a different result.
This is the ceiling I get when loading your dives in subsurface: View attachment 840699
The only way I can get the subsurface ceiling to match what the Ratio support got is to set the surface interval to 3 min.
View attachment 840701
With the full 93 min surface interval the maximum Surface GF is 78% according to Subsurface, with a 3 min one it is 99%. It's hard to get the Subsurface and Ratio ceilings to match up. With 33 min surface interval they are similar length, but shifted a bit from each other, so it doesn't seem to just be a shortening of the surface interval. Maybe accumulation of shortened surface intervals for all the previous dives would do, but it starts getting messy.
(The reason for using 93, 33 and 3 min is just because the previous dive ended at 09:17 and it was nicer to use :20 :50 and so on for the minutes).
Uwatec had this bug in the past: when diving Nitrox it used the same percentage for the surface intervals (instead of Air):So maybe the Ratio somehow messed up the surface intervals?
Thanks. How do i check the SI recorded?Hi @harvalen
Seems odd, but very interesting. An error in the SI would affect both the NDL and the CNS O2, a unifying explanation. From the logs, I would imagine @pisauron could check the SI recorded for this dive by both computers, not that it would ensure that time was credited. I don't think I have ever heard of a dive computer error in not correctly crediting the SI, there's always a first time.
From the graphs of the implicated dive:
Ratio: 1 min NDL and 26% CNS O2
Garmin: 13 min NDL and 16% CNS O2
The difference in CNS O2 represents a significant portion of one 90 min half-life of O2 elimination
Hi @pisauronThanks. How do i check the SI recorded?
Thanks. How do i check the SI recorded?
Also i think Ratio support addressed that somehow
<dive number='2' date='2014-04-04' time='14:59:00' duration='43:00 min'>