Max. Tiefe fehlerhaft?

[Arno Jansen]

Thank you for your efforts! I now had a look in the xml-file and I think now it´s clear:

That´s how I did my dive today:
I was just 2-3 seconds with my OSTC on the bottom of our lake just to measure the actually deepest point because it varies from case to case (the depth there depends on the water in the river rhein, the rain, et cetera).

Here you see the information in the xml-File while approaching the deepest point of our lake:

  <sample time='29:10 min' depth='17.835 m' />
  <sample time='29:20 min' depth='17.723 m' />
  <sample time='29:30 min' depth='18.192 m' />
  <sample time='29:40 min' depth='18.049 m' />
  <sample time='29:50 min' depth='17.447 m' />


And these are the global information of the dive saved by my OSTC

<dive number='258' date='2013-02-23' time='10:49:00' duration='46:00 min'>
  <location gps='51.159216 6.754746'>Sandhofsee</location>
  <divemaster>Conny</divemaster>
  <buddy>Conny</buddy>
  <notes>beide tiefen Stellen, 1 Hecht gesehen</notes>
  <suit>Trocki</suit>
  <cylinder size='17.0 l' workpressure='232.0 bar' description='D8.5 232 bar' start='200.0 bar' end='120.0 bar' />
  <weightsystem weight='6.0 kg' description='Backplate-Gewicht' />
  <divetemperature air='-1.0 C'/>
  <divecomputer model='Heinrichs Weikamp OSTC 2N' deviceid='7fffffff' diveid='2834f547'>
  <depth max='18.5 m' mean='9.412 m' />
  <temperature water='3.5 C' />


So the OSTC samples every 10sec (default setting in custom function 20 of the OSTC) but he also samples perhaps every second the actual deepness and saves the deepest point separately.

Thanks guys for the help an sorry for the hassle.


Keep on diving,
Arno from germany





Am 23.02.2013 um 20:44 schrieb Linus Torvalds <torvalds at linux-foundation.org>:

> 2013/2/23 Robert C. Helling <helling at atdotde.de>:
>> 
>> Translation service for non-Germans: He says that his OSTC as well as the dive notes report a max-depth of 18.5m while the profile and the table only state 18.2m. But he likes V3.0 very much never the less!
> 
> This is common. Many dive computers report a "max depth" that doesn't
> actually match the deepest sample. And since it is almost always
> deeper than the deepest actual sample, my personal guess is that it's
> simply that samples are saved at some arbitrary points (say, every ten
> seconds), but that the computer is doing depth sensing and deco
> calculations more often (say once a second).
> 
> So we save the max depth separately.
> 
> That said, I think the dive table should show that separate max depth
> thing. I idly wonder why it doesn't, but I didn't spend any time
> looking into it.
> 
>              Linus