Apeks DSX

[8bits Coding]

Hi,

I just got an Apeks DSX for tech diving and I would like to help bringing its support to Subsurface (btw I take the occasion to thank all of the contributor for this amazing software !!).

Unfortunately, aside from a reference to send the log of libdivecomputer I did not find any documentation on how to contribute a new dive computer to the code base.

I am certain that I'm missing something obvious, but could someone be so kind to point me in the right direction?

Cheers.

Arnaud. 

[Michael Keller]

Hi Arnaud.

Dive computer support in Subsurface is 'a bit special': It is done
through the 'libdivecomputer' library
(https://github.com/libdivecomputer/libdivecomputer) and not directly in
Subsurface . But Subsurface is then using a long-lived branch of
libdivecomputer (https://github.com/subsurface/libdc) that has got some
improvements over the 'vanilla' library, and supports some dive computer
models that the released version of libdivecomputer doesn't. Updates to
libdivecomputer are regularly pulled into the branch that Susurface is
using, so it is up to you to decide if you want to contribute this to
Subsurface, or to libdivecomputer directly.

The libdivecomputer branch is included in the Subsurface source
repository (https://github.com/subsurface/subsurface) as a submodule,
but naturally all changes to it will need to happen through pull
requests into the actual repository (https://github.com/subsurface/libdc).

As for the Apeks DSX, this model has been discussed on the Subsurface
developer mailing list
(http://lists.subsurface-divelog.org/pipermail/subsurface/2023-July/036458.html)
- have a look at this to see where the problems lie. In short as the
manufacturer wants to force their customers into using the paid version
of their logging software if they want more than very basic logging, it
will require the protocol to be reverse engineered / hacked in order to
get it supported in Subsurface.

Sing out if you've got more questions.


Ngā mihi

  Michael Keller

[8bits Coding]

oh... That's not good for the manufacturer position...