Discrepancy between my computers during the dive

Please register or login

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.
  • You can make this box go away

Joining is quick and easy. Log in or Register now!

Does the depth reading appear to be stable? My Shearwaters sensors are off by a few MB. Combined with the Nerd being higher in the water column, I've seen them as much as 5 minutes off, but I wouldn't describe it as "all over the place".

They are on the same hand and reading the same depths during the dive.
 
Hello,

Been diving in Cyprus this week doing some cool wrecks.

Today i noticed something disturbing: My computers are showing me different NDL times.

1. Garmin descent mk2i with Buhlman 16c GF 70/85
2. Ratio ix3m 2 with buhlman 16c GF 70/85

The computers are on the same hand. This was in the second dive during the days. They were used simultaneously all the dives. They should show similar times.

So the Garmin shows significant more NDL (55 min) and the Ratio shows less (48 min). And this is after 3 minutes into the dive.

After ~half an hour the Ratio showed me deco times (NDL ended). The Garmin still had 15min NDL.

Anyone experienced this?

Which one makes more sense?
Are both computers using the same algorithm and gradient factors?
 
What counts as a discrepancy?

Short answer: I'd ignore 2-3 minutes. Long answer: start with the pressure sensor accuracy and water salinity settings(*), then read the specs on the processors and see what they say about floating point accuracy, then read the code and see what the fastest tissue compartment is(**), the sensor polling intervals are, what recalculation intervals are, and how it tracks precision and handles round-off and truncation errors.

On the theoretical side, I'd use the Nyquist limit for analogy and say the "meaningful quantum" is 1/2 of the fastest compartment's half-time.

*) Salinity setting doesn't affect the calculation but may affect the depth display, which could further confuse the user.
**) In ZH-L16 you can choose between 4 and 5 minutes.
 
Short answer: I'd ignore 2-3 minutes. Long answer: start with the pressure sensor accuracy and water salinity settings(*), then read the specs on the processors and see what they say about floating point accuracy, then read the code and see what the fastest tissue compartment is(**), the sensor polling intervals are, what recalculation intervals are, and how it tracks precision and handles round-off and truncation errors.

On the theoretical side, I'd use the Nyquist limit for analogy and say the "meaningful quantum" is 1/2 of the fastest compartment's half-time.

*) Salinity setting doesn't affect the calculation but may affect the depth display, which could further confuse the user.
**) In ZH-L16 you can choose between 4 and 5 minutes.

Does this info available for Garmin & Ratio computers?
 
Since I had a few occasions my computer died during liveaboard vacation (tank dropped on one, battery checked ok before trip not ok after third day and one computer went down the abyss during transition from dingy to boat) I nowadays take two computers, just in case Neptune claims another computer from me.

Being the geek that I am, I used to check both because they were there on my wrist and I was puzzled by the discrepancies (even when using the "same" algorithm). I now believe it is a combination of slight differences in sensor readings and sampling rates.

My solution to this: put the backup computer under the wetsuit's sleeve. During dive only use main computer. IF main computer dies, gets lost or whatever: pull backup computer from under sleeve and it becomes the new primary. Problem solved.

My first daughter had high fever when she was a few months old. My wife had about a dozen thermometers stashed in different locations, just for cases like this. Some were the same model and manufacturer, others not. So, first thermometer showed 41C, second showed 42C, some read 39.9C and one 43C. Off we went to ER, where they check temperature with only ONE thermometer, which showed 40C. High, but not something to run to the hospital. But we spent the weekend "for supervision" and my daughter was all right (She's 26 now). Back home I was annoyed by the temperature differences and accuracy between various thermometers, so I took them to my lab and compared vs. a set of thermocouples and a calibrated thermometer. And not surprisingly, the variance between the home thermometers was about +/-1.5C. I apologized to my wife and threw away all thermometers but one. Life became simpler with one thermometer only.

Most dive computers manufacturers write nothing about the specs of depth sensor, temperature sensor, AI transmitter, sampling rate and so on, but all these sensors have a certain accuracy, and even using same sensors you can have a difference in their readings.
 
threw away all thermometers but one. Life became simpler with one thermometer only.

Based on this advice, I'll be most happy if the op would just send me his extra computer and I'll take care of it instead of him going through the painful chore of throwing it away.

Excellent advice indeed 😃 💯 💯 💯
 
Since I had a few occasions my computer died during liveaboard vacation (tank dropped on one, battery checked ok before trip not ok after third day and one computer went down the abyss during transition from dingy to boat) I nowadays take two computers, just in case Neptune claims another computer from me.

Being the geek that I am, I used to check both because they were there on my wrist and I was puzzled by the discrepancies (even when using the "same" algorithm). I now believe it is a combination of slight differences in sensor readings and sampling rates.

My solution to this: put the backup computer under the wetsuit's sleeve. During dive only use main computer. IF main computer dies, gets lost or whatever: pull backup computer from under sleeve and it becomes the new primary. Problem solved.

My first daughter had high fever when she was a few months old. My wife had about a dozen thermometers stashed in different locations, just for cases like this. Some were the same model and manufacturer, others not. So, first thermometer showed 41C, second showed 42C, some read 39.9C and one 43C. Off we went to ER, where they check temperature with only ONE thermometer, which showed 40C. High, but not something to run to the hospital. But we spent the weekend "for supervision" and my daughter was all right (She's 26 now). Back home I was annoyed by the temperature differences and accuracy between various thermometers, so I took them to my lab and compared vs. a set of thermocouples and a calibrated thermometer. And not surprisingly, the variance between the home thermometers was about +/-1.5C. I apologized to my wife and threw away all thermometers but one. Life became simpler with one thermometer only.

Most dive computers manufacturers write nothing about the specs of depth sensor, temperature sensor, AI transmitter, sampling rate and so on, but all these sensors have a certain accuracy, and even using same sensors you can have a difference in their readings.

Hiding one is a solution. But I just wish to inform other divers before they make the choice of buying a Ratio.
 
Welp,

Now my Ratio is doing shenanigans again. This time I noticed my deco time on the Ratio was two minute early. Meaning the Ratio said I am clear of deco two minutes before my garmin.

Two minutes is not much and acceptable i guess. But still, what will happen when it's more...

So I checked my logs for the blue hole arch dive - and behold the Ratio deco times are now ~5 min different than Garmin. Damn.

Confucius says: If a man has a watch, he'll always know what time it is. If a man has two watches, he'll never be quite sure
These graphs would be more useful if you showed the DC computed ceiling.
 
These graphs would be more useful if you showed the DC computed ceiling.

Got it. Here they are
 

Attachments

  • garmin50.png
    garmin50.png
    130.5 KB · Views: 15
  • ratio504.png
    ratio504.png
    135 KB · Views: 15

Back
Top Bottom