ADP Inspiration Dive Logs

[Justin Steele-Davies]

I have had a look around the forum and at some of the information about divecomputer library to import dives from ADP Inspiration Vision 2020 . I have not found a discussion on this so far.

Is there a way of converting the logs into a format that can be imported or some other way of getting the logs in?

There is an XML (uddf) format and a binary (ccl) format for the log.

The uddf format does not seem to import ppO2. Is there a change i can make to fix this? This is a waypoint from the file;
<waypoint>
                        <depth>40.6</depth>
                        <divetime>1752.4</divetime>
                        <ppo2 ref="o2sensor_c1_1">131000.0</ppo2>
                        <ppo2 ref="o2sensor_c1_2">127000.0</ppo2>
                        <ppo2 ref="o2sensor_c1_3">130000.0</ppo2>
                        <ppo2 ref="o2sensor_c2_1">131000.0</ppo2>
                        <ppo2 ref="o2sensor_c2_2">127000.0</ppo2>
                        <ppo2 ref="o2sensor_c2_3">130000.0</ppo2>
                        <batteryvoltage ref="battery_c1_1">6.4</batteryvoltage>
                        <batteryvoltage ref="battery_c1_2">6.4</batteryvoltage>
                        <batteryvoltage ref="battery_c2_1">6.3</batteryvoltage>
                        <batteryvoltage ref="battery_c2_2">6.4</batteryvoltage>
                        <temperature>290.4</temperature>
                        <gradientfactor>0.50</gradientfactor>
                        <cns>0.16</cns>
                        <otu>42.0</otu>
                        <timetosurface>1080.0</timetosurface>
                        <decostop kind="mandatory" decodepth="13.9" duration="10.0"/>
                        <scrubber ref="tempstik" units="">62</scrubber>
                    </waypoint>

[chic]

I have an Inspiration too.   I do the following

1. Open up the dive in AP Divesight

2. Open the tab for "Data"

3. On the bottom of the screen click on Copy to Clipboard

4. Open an excel spread sheet and paste the data

5. Save the excel spreadsheet as a .csv

6. Open Subsurface

7. Click on Import -> Import Dive Log or click CTRL+I

8. Follow instructions to import the data

I know it's time consuming, but it's what I do.....

[Miika Turkia]

Uddf import is done via xslt. Following link gets you to the source code around the line where ppo2 should be implemented 

https://github.com/subsurface/subsurface/blob/fc0a569cb6e4db8f9696957264108b01830853dc/xslt/uddf.xslt#L568

On 20. Jul 2024, at 22.10, Justin Steele-Davies <j.d.stee...@gmail.com> wrote:

I have had a look around the forum and at some of the information about divecomputer library to import dives from ADP Inspiration Vision 2020 . I have not found a discussion on this so far.

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/f475869f-c105-48df-b7d5-c57f9407de5an%40googlegroups.com.

[Michael Keller]

Hi Justin.

It looks like the format exported by APD does not follow the UDDF specification here - the field containing the measured ppO2 is called `ppo2`, in the UDDF specification it is called `measuredpo2`: https://www.streit.cc/extern/uddf_v321/en/measuredpo2.html

But the export / import method described by chic is working quite well for the APD Inspiration.

Ngā mihi

  Michael Keller

--

You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/f475869f-c105-48df-b7d5-c57f9407de5an%40googlegroups.com.

--

GCS$/CC/E/IT d- s+ a C++ UL+++/S++ P L++ E-
W++ N o? K? w O(++) M-- V+ PS+ PE+ Y? PGP+ t
5? X R tv b++ DI++ D++ G e+++ h---- r+++ y+++

[Michael Keller]

I should probably have added that Subsurface currently only imports the setpoint ppO2 from UDDF, but not any sensor readings.

Cheers

  Michael Keller

[Justin Steele-Davies]

This I think is ciritcal, so it does not matter if i fix for format of the UDDF file, it will never work at the moment. Yay manual copy and paste it is.

Justin

[Michael Keller]

Hi Justin.

On 30/07/24 21:59, Justin Steele-Davies wrote:
> This I think is ciritcal, so it does not matter if i fix for format of
> the UDDF file, it will never work at the moment. Yay manual copy and
> paste it is.

Are you actually the maintainer of AP DiveSight - or were you just
thinking of writing a converter for the files written by AP DiveSight?


I agree that getting the ppO2 sensor readings is quite crucial for files
generated by a CCR.

My statement was just that ppO2 sensor reading import is not _currently_
supported when importing UDDF files - not that this can not be done. I
think this should be possible without too much hassle.

Basically how UDDF import works in Subsurface is that the XML-based UDDF
is converted into the XML-based SSRF format that is the native format
that Subsurface stores its logs in, and then imported as SSRF. The
conversion is done through XSLT, which is an XML-based transformation
language for XML - a bit hard to learn but quite powerful. The
conversion code in question is in
https://github.com/subsurface/subsurface/blob/master/xslt/uddf.xslt,
with the code to convert the setpoint in
https://github.com/subsurface/subsurface/blob/2b7900b68dd362bc5f2dc7f13dbee49787106072/xslt/uddf.xslt#L568-L576


If you are keen to work on improving this I am happy to help.


Cheers

  Michael Keller

[Nick Clark]

I worked with the team from AP Diving between Dec 2020 and Oct 2021 on the implementation of the UDDF export from AP DiveSight.  My role was testing but we encountered a large number of potential data elements that were not supported by the UDDF v3.2.3 schema so I was also involved in many discussions with Kai Schröder about making some additions to UDDF. 

The result was an alpha version of Universal Dive Data Format (UDDF) Version v3.3.0 schema which provided a number of additions pertinent to CCR, but sadly it appears this may never have been published by the UDDF team. One of the agreements was to depreciate <measuredpo2> in favour of a new <ppo2> element to allow individual cell values to be exported. 

The AP Tempstick was another item that proved to be quite tricky to agree a data element that was not totally manufacturer specific. 

I'm happy to contribute my knowledge of the data exported by DiveSight in UDDF to any effort to extend conversion through XSLT to bring more information into Subsurface.

ATB

Nick

[Michael Keller]

Hi Nick.

On 31/07/24 22:38, Nick Clark wrote:
> I worked with the team from AP Diving between Dec 2020 and Oct 2021 on
> the implementation of the UDDF export from AP DiveSight.  My role was
> testing but we encountered a large number of potential data elements
> that were not supported by the UDDF v3.2.3 schema so I was also
> involved in many discussions with Kai Schröder about making some
> additions to UDDF.

Oh nice, thanks for responding here. I am a long time AP Inspiration
diver, and I can totally see that using UDDF to transfer data out of the
AP application will be much better than copy / paste for data in table
form.

> The result was an alpha version of Universal Dive Data Format
> (UDDF) Version v3.3.0 schema which provided a number of additions
> pertinent to CCR, but sadly it appears this may never have been
> published by the UDDF team. One of the agreements was to depreciate
> <measuredpo2> in favour of a new <ppo2> element to allow individual
> cell values to be exported.

I saw the 3.3.0 version attribute in an UDDF that I exported from
DiveSight, and wondered about this version. So the intention is (or at
least was) that this should be published at some point?

I think it be a much better case for adding support for this to
Subsurface if this is an agreed standard.

Do you happen to be able to supply an XSD for the proposed standard?

> The AP Tempstick was another item that proved to be quite tricky to
> agree a data element that was not totally manufacturer specific.

Yes, I can see that - the approaches for scrubber / CO2 monitoring that
different CCR manufacturers are so different that there probably won't
be much scope for a unified way to represent the data.

> I'm happy to contribute my knowledge of the data exported by DiveSight
> in UDDF to any effort to extend conversion through XSLT to bring more
> information into Subsurface.

Thank you! I think UDDF 3.3.0 shouldn't be too different from the
currently implemented version, so we should be able to extend it to make
it support both formats, and allow for the import of sensor readings.

It would be great if we could have some documentation about the format
to publish along the change, so that others wanting to support it won't
have to make their own assumptions.


Ngā mihi

  Michael Keller

[Olivier VIENNET]

Hello,

For a friend who wants to upgrade to Subsurface I am looking to export files from his AP Diving to Subsurface.

On the one hand the ccl files of the dives are not recognized by Subsurface and therefore I cannot import them.

Furthermore, Subsurface does not offer the AP diving computer to directly import dives.

I found this page but don't really understand what to do...

How to do it?

Thanks for your help.

[1978bandit]

I use the AP software to download the dive logs.   I then copy and paste the data for each dive into an excel spreadsheet.    You can save the file as ,csv and import that into Subsurface

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/8ccb2ef8-379c-4ee6-a65e-1df4b9dda850n%40googlegroups.com.

[Olivier VIENNET]

Le mardi 11 février 2025 à 15:36:15 UTC+1, 1978bandit a écrit :

I use the AP software to download the dive logs.   I then copy and paste the data for each dive into an excel spreadsheet.    You can save the file as ,csv and import that into Subsurface

But How to copy the data ?

There is no menu entry and Crtl+C does nothing with AP DiveSight

Thanks

[Olivier VIENNET]

OK I found the "Data" Sheet and then "Copy to clipboard".
But the manual import created 1448 dives...
And other AP import mode did not import anything

[1978bandit]

That is one dive.   It imported wrong.    After you paste the data into excel, add 3 new columns on the left.   They should be dive number, date, and time.    Fill in every row with the same dive number (subsurface), date, and time of the start of the dive

--

You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/aa5adcb8-8460-44bb-83a3-84a269704751n%40googlegroups.com.

[Michael Keller]

Hi Olivier.

Can you describe the steps you take to import?

Copy / pasting the APD CSV into a file, and then using 'Import log file' should work pretty well for this.

Ngā mihi

  Michael Keller

--

You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/aa5adcb8-8460-44bb-83a3-84a269704751n%40googlegroups.com.

[Olivier VIENNET]

In divesight I go to the data window, copy the data and paste to excel

The two first line of the csv file are :

Dive Time (s);Depth (m);PPO2 Setpoint (Bar);PPO2 C1 Cell 1 (Bar);PPO2 C1 Cell 2 (Bar);PPO2 C1 Cell 3 (Bar);PPO2 C1 Measured (Bar);PPO2 C2 Cell 1 (Bar);PPO2 C2 Cell 2 (Bar);PPO2 C2 Cell 3 (Bar);PPO2 C2 Measured (Bar);C1 Battery 1 (Volts);C1 Battery 2 (Volts);C2 Battery 1 (Volts);C2 Battery 2 (Volts);Ambient Temp. (°C);OTU Exposure (%);CNS Exposure (%);Deco Ceiling (m);Gradient Factor
0.0;1.2;0.70;0.72;0.74;0.69;0.73;0.72;0.74;0.69;0.73;6.38;6.38;6.38;6.38;8.30;0.0;0.0;0.0;95

Then I try to import with profile APD Log Viewer DC1 or DC2 or manually.

But in any case I won't be able to do this to recover my friend's hundreds of dives one by one...

So I saw in AP Divesight an option to save in UDDF format which allows you to process all the files at once. It works but loses a lot of information.

However, I will be satisfied with it, no other choice.

[Michael Keller]

Hi Olivier.

On 12/02/25 21:26, Olivier VIENNET wrote:

In divesight I go to the data window, copy the data and paste to excel

The two first line of the csv file are :

Dive Time (s);Depth (m);PPO2 Setpoint (Bar);PPO2 C1 Cell 1 (Bar);PPO2 C1 Cell 2 (Bar);PPO2 C1 Cell 3 (Bar);PPO2 C1 Measured (Bar);PPO2 C2 Cell 1 (Bar);PPO2 C2 Cell 2 (Bar);PPO2 C2 Cell 3 (Bar);PPO2 C2 Measured (Bar);C1 Battery 1 (Volts);C1 Battery 2 (Volts);C2 Battery 1 (Volts);C2 Battery 2 (Volts);Ambient Temp. (°C);OTU Exposure (%);CNS Exposure (%);Deco Ceiling (m);Gradient Factor
0.0;1.2;0.70;0.72;0.74;0.69;0.73;0.72;0.74;0.69;0.73;6.38;6.38;6.38;6.38;8.30;0.0;0.0;0.0;95

Then I try to import with profile APD Log Viewer DC1 or DC2 or manually.

Yes, this should work.

But in any case I won't be able to do this to recover my friend's hundreds of dives one by one...

So I saw in AP Divesight an option to save in UDDF format which allows you to process all the files at once. It works but loses a lot of information.

However, I will be satisfied with it, no other choice.

Unfortunately AP Divesight uses a version of the UDDF format that has not yet been finalised or released. Once the format has been released Subsurface will eventually add support for it, so you'll be able to re-import the dives then and get more complete logs.

Cheers

  Michael Keller

[Olivier VIENNET]

Hi Michael,

Thank you !

[Michael Keller]

Hi all.

Since no official documentation on UDDF 3.3 has been forthcoming for a long time now I have decided to go ahead and implement the parts that are defined in the format produced by APD DiveSight, and made educated guesses about how they should be interpreted:

https://github.com/subsurface/subsurface/pull/4493

In some cases the APD format is incorrect or missing parts, like links for locations and dive buddies, I will be trying to contact them and work with them on getting this fixed.

But in the meantime, if somebody can download the artifacts linked in the pull request above, and give them a spin and provide feedback that will be great.

Ngā mihi

  Michael Keller

[Will Pimblett]

Hey Michael

Just found this discussion after searching around about how to make the best use of subsurface with an AP rebreather. I found the UDDF import near the start of the year and now know why it works a hell of a lot better now!

I've imported around 12 dives using the updated importer and not noticed any problems so far. Thank you for the efforts here!

[Michael Keller]

Hi Will.

On Tue, 29 Jul 2025 at 12:40, Will Pimblett <wi...@pimblett.me.uk> wrote:

Just found this discussion after searching around about how to make the best use of subsurface with an AP rebreather. I found the UDDF import near the start of the year and now know why it works a hell of a lot better now!

I've imported around 12 dives using the updated importer and not noticed any problems so far. Thank you for the efforts here!

 

Thank you for the feedback, much appreciated. 

There are a few minor shortcomings in the UDDF generated by APD, mostly around additional data added in AP DiveSight, like dive sites and buddies. I have raised these with APD, but they still have to implement the fixes in a future version of AP DiveSight.

The new process is also covered in the documentation now: https://subsurface-divelog.org/subsurface-user-manual/?lang=en#_importing_from_apd_inspiration_ccr

Ngā mihi

  Michael Keller