Liquivision DC support?

[Jef Driesen]

On 2013-02-19 09:42, Henrik Brautaset Aronsen wrote:
> Maybe a talk with the Diving Log guys could help?
>
>   "OK, great news: I've heard back from Liquivision and got already
> some material - and also a direct download with Diving Log seems not
> too far away, but I can't promise more about that right now. An 
> import
> is almost working already."
>
>   "So, here we go: Thanks to the documentation I got yesterday, I
> finally managed to read the Dive Log file format (*.lvd) and created 
> a
> first import which you can test. It works with the 2 logbook files I
> have, but it is possible that it has still bugs. I managed to import
> almost all data, except profile events (e.g. warnings and gas
> switches). If you have any logbook files containing dive profiles 
> with
> gas switches and warnings, please send me the files."
>
> (from http://www.divinglog.de/phpbb/viewtopic.php?f=4&t=1408 @ 
> Nov.2011)

That talk already happened around the time the above was posted. The 
first quote (regarding the direct download) was in fact posted due to 
that discussion :-)

In a nutshell, Sven (the Diving Log author) received from Liquivision 
some documentation about the data format (which he used to write the 
importer), and also a shared library for the communication. Sven asked 
me if I could write the necessary glue code to use this library from 
.NET (because he's not a C/C++ developer). I tried, but unfortunately I 
couldn't get it to work. The small prototype app I wrote did compile, 
and even managed to communicate with the device, but then crashed 
somewhere inside the shared library. I suspect this was due to the fact 
it's a C++ library and there was some mismatch between compiler versions 
(or options) and/or the stl libraries. C++ isn't as portable as C in 
that regard. I didn't really had the time to investigate in more detail.

Jef