Suunto D4 max depth difference and missing information

3rd party extensions (phpDivingLog, dive computer downloader,...)
Post Reply
athelas
Posts: 6
Joined: Sun Jul 05, 2009 04:37

Suunto D4 max depth difference and missing information

Post by athelas »

Not sure whether to post it here or into general forum. First of all, XML file I have downloaded from the computer with the test tool is complete and consistent with what Suunto DM4 is saying, however data in the Diving Log differ.

Max depth difference:
Computer and DM4 show depth of 11.9 meters, DL indicates only 11.7
In the diveprofile, when looking at the samples, indeed the maximum recorded depth is 11.68 and this was picked by DL. However in the XML file at the beginning of a dive record there is field that is probably ignored by DL. Maximum depth was probably registered by the computer in between profile sampling:

Code: Select all

<dive>
<number>1</number>
<size>386</size>
<fingerprint>0C131FDB070B09</fingerprint>
<datetime>2011-11-09 12:19:31</datetime>
<divetime>45:04</divetime>
<maxdepth>11.86</maxdepth>
...
It would be nice if the DL took data for maximum depth from this field. With 20s sampling is not much of a difference, but with one minute?

This is probably only a Suunto import thing, but DL seems to completely ignore fast ascent warnings:

Code: Select all

<sample>
   <time>19:20</time>
   <depth>16.28</depth>
   <event type="3" time="12" flags="1" value="0">ascent</event>
   <event type="13" time="12" flags="1" value="0">safety stop (mandatory)</event>
   <event type="3" time="13" flags="2" value="0">ascent</event>
</sample>
It would be nice to have mandatory safe stop or too fast ascents indicated either in the main depth profile or in the asc./desc. profile. Or at least, do these get recorded somewhere in the database? From the profile documentation it looks like the profile 1 has fields to record such events.

Thanks!

Milan

TnT
Posts: 257
Joined: Thu Nov 29, 2007 14:53
Contact:

Re: Suunto D4 max depth difference and missing information

Post by TnT »

The difference in the maxdepth (or divetime) value is indeed because DL calculates this from the profile data, while the value in the xml shows the value stored in the dive header (with a fallback to a calculated value if there is no such header). So the support is already available in the libdivecomputer library, but it's not yet used by DL. I'll talk to Sven about this.

Note that DL isn't using the xml files because it gets the data directly from the dive computer. These xml files are only intended for debugging purposes.
libdivecomputer developer
Support the libdivecomputer project with a donation!
http://www.libdivecomputer.org/donate.html

Post Reply