devel

devel@libdivecomputer.org

3 participants
290 discussions

Windows build
by Vincent Hagen 12 Aug '23

12 Aug '23

Hi Jef, I am looking for the windows build of the latest version of libdivecomputer. In the past you made windows builds where I could download the dll's. When I try this myself on either windows or linux via minGW, I am losing all support for USBHID, Bluetooth, etc. On linux it works fine if I install all the correct packages with headers. Do you still have the pre-builds, or a solution how to build the windows dlls more consistently? With kind regards, Vincent Hagen

2 1

Apeks DSX Support
by Moritz Barz 19 Jul '23

19 Jul '23

Are there plans to add support to sync with the fairly new Apeks DSX computer?

2 1

Backwards incompatible API changes
by Jef Driesen 17 May '23

17 May '23

Hi, I'm going to make a few changes that will break backwards compatibility. The plan is to ship a new release in the next few days, and then introduce all those changes at once, to keep the impact as small as possible. If you need to be able to build against both the new and old api, you'll be able to use a construct like this: #if DC_VERSION_CHECK(0,9,0) /* New */ #else /* Old */ #endif What follows is an overview of the planned changes: 1. The dc_parser_set_data() function will be removed. The only purpose of this function is to be able to re-use a parser object with new data. Since the state in the parser is typically very small, there is almost no advantage in doing that. It also adds unnecessary complexity in the implementation, because each backend needs to be able to reset its internal state. Keeping a reference to the data has also caused issues for applications in the past (especially those implemented in a garbage collected language). Therefore, the data and size parameters will be passed directly to the dc_parser_new() and dc_parser_new2() function, and the data will get copied internally: /* Old */ dc_parser_new (&parser, device); dc_parser_set_data (parser, data, size); /* New */ dc_parser_new (&parser, device, data, size); 2. The devtime and systime arguments will be removed from the dc_parser_new2() function. Applications will have to call dc_parser_set_clock() to set those parameters: /* Old */ dc_parser_new2 (&parser, context, descriptor, devtime, systime); dc_parser_set_data (parser, data, size); /* New */ dc_parser_new2 (&parser, context, descriptor, data, size); dc_parser_set_clock (parser, devtime, systime); 3. The sample callback function will be changed to pass the sample by reference instead of by value. Passing by value means the size of the struct can't be changed without also changing the function signature and breaking backwards compatibility. This prevented adding some new features. /* Old */ sample_cb (dc_sample_type_t type, dc_sample_value_t value, void *userdata) /* New */ sample_cb (dc_sample_type_t type, const dc_sample_value_t *value, void *userdata) Some examples of new features that will be added: * Add a TTS field to the deco sample. * Add a sensor index field to the ppO2 sample. * Add a tank/gasmix usage field, to indicate whether a tank or gasmix is used in a sidemount configuration or as oxygen/diluent on a rebreather. 4. Change the sample time units from seconds to milliseconds. This is necessary to support some freediving computers with a higher sample rate. If your application doesn't support the millisecond resolution (yet), you can discard the extra resolution, and (optionally) skip the samples with a duplicate timestamp. Jef

1 1

[ANNOUNCE] Version 0.8.0 now available
by Jef Driesen 12 May '23

12 May '23

Hi, The v0.8.0 release is now available! http://www.libdivecomputer.org/releases/libdivecomputer-0.8.0.tar.gz The v0.8.0 release is mainly a bugfix release, and brings in support for a number of new devices. This release is fully backwards compatible with the previous one. New features: * Add support for new backends: - excursion: Deep Six Excursion, Crest CR-4, Genesis Centauri, Tusa TC1, Scorpena Alpha - screen: Seac Screen and Action - cosmiq: Deepblu Cosmiq+ - s1: Oceans S1 - freedom: Divesoft Freedom and Liberty * Add support for some new devices: - Aqualung: i200C - Cressi: Donatello, Michelangelo, Neon - Mares: Puck Pro + - Oceanic: Geo Air - Ratio: iX3M 2 - Scubapro: G2 TEK - Shearwater: Petrel 3, Perdix 2 - Sherwood: Amphos Air 2.0 * Add support for parsing the decompression model * Add a public api to configure the depth calibration * Add a public api to configure the clock synchronization * Add a basic Android build system Removed/changed features: * Migrate to Visual Studio 2013 (or newer) * Move the Visual Studio project to the contrib directory Jef

1 0

Re: Teric sample rate fail
by Peter B 08 Dec '22

08 Dec '22

2 1

Teric sample rate fail
by Peter 07 Dec '22

07 Dec '22

2 1

dctool, Shearwater Predator and macos
by Henrik B A 05 Dec '22

05 Dec '22

Hi. I'm having problems downloading dives from my Shearwater Predator, so I decided to try dctool: dctool -l predator-download.log -f predator download -f raw -o predator-download.raw /dev/tty.Predator This worked fine! But when I try again, all subsequent tries gives me an error: DATETIME 2022-12-05T08:31:28Z (1670229088) VERSION 0.7.0 Opening the I/O stream (serial, /dev/tty.Predator). Opening the device (Shearwater Predator). Registering the event handler. Registering the cancellation handler. Downloading the dives. Event: progress 0.00% (0/10000) ERROR: Failed to receive the packet. [in shearwater_common.c:239 (shearwater_common_slip_read)] ERROR: Failed to receive the response packet. [in shearwater_common.c:358 (shearwater_common_transfer)] ERROR: Error downloading the dives. [in dctool_download.c:228 (download)] ERROR: Timeout I've also tried xml output and dump, with the same results. I've used these commands: dctool -l predator-download-xml.log -f predator download -o predator-download.xml /dev/tty.Predator dctool -l predator-dump.log -f predator dump -o predator-dump /dev/tty.Predator What can be the issue here? I'm on macOS 12.6.1. Predator has latest firmware (v63). I can send the one working raw download if needed. Thanks, Henrik

3 5

[ANNOUNCE] Version 0.7.0 now available
by Jef Driesen 07 May '21

07 May '21

Hi, The v0.7.0 release is now available! http://www.libdivecomputer.org/releases/libdivecomputer-0.7.0.tar.gz The main highlight of the v0.7.0 release is the introduction of the new I/O interface. With this common interface, the dive computer backends can more easily use different I/O implementations at runtime, including an application defined one. This is needed to support Bluetooth Low Energy (BLE), for which there is no built-in implementation available. Due to the fundamental changes to the I/O layer, this release is not backwards compatible. New features: * A new I/O interface * Add support for new backends: - goa: Cressi Goa and Cartesio - divecomputereu: Tecdiving DiveComputer.eu - extreme: McLean Extreme - lynx: Liquivision Xen, Xeo, Lynx and Kaon - sp2: Sporasub SP2 * Add support for many new devices: - Aqualung: i100, i200C, i300C, i470TC, i550C, i770R - Heinrichs Weikamp: OSTC 2 TR - Mares: Genius, Horizon, Quad Air, Smart Air - Oceanic: Geo 4.0, Pro Plus 4, Pro Plus X, Veo 4.0 - Ratio: iDive Color, iX3M GPS, iX3M 2021 - Scubapro: A1, A2, Aladin H Matrix, G2 Console, G2 HUD - Seac: Guru, Jack - Shearwater: Peregrine, Teric - Sherwood: Amphos 2.0, Beacon, Sage, Wisdom 4 - Suunto: D5, EON Steel Black - Tusa: Talis * Firmware upgrade support for the Ratio computers * Support for semi-closed circuit diving Removed/changed features: * Unify the Uwatec Smart, Meridian and G2 backends Jef

1 0

Is there a way to build with bluetooth support on a mac?
by Ryan Gardner 06 May '21

06 May '21

I'm hoping to add a new bluetooth dive computer to libdivecomputer. I've spent a fair amount of time reverse engineering the sync protocol between it and the android app that it uses, and have a general idea of how it communicates. I'm primarily on a mac - looking at the source for it, when I do my normal configure operation it claims: Transports: Serial : yes USB : yes USBHID : yes IrDA : no Bluetooth : no BLE : no It looks like it uses bluez or windows bluetooth apis - is there something I need to do to get it to work with bluetooth on OS X? I can work on an older linux machine as well - but it will take a bit longer to get it set up to do development on. Ryan

3 6

USB communication changes
by Jef Driesen 11 Aug '20

11 Aug '20

Hi, Native USB communication (used only by the Atomic Aquatics Cobalt backend) was not yet ported to the I/O stream interface. This has now changed because I just pushed a new USB based I/O transport implementation the libdivecomputer master branch. This means the application is now responsible for setting up the USB I/O stream, just like all others transports. The Atomic Aquatics Cobalt backend does no longer open the USB device internally. Passing a NULL pointer for the iostream will no longer work! The advantage is that an application can now also use a custom implementation on platforms where libusb isn't available (iOS) or doesn't work very well due to permission problems (Android). Jef

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

devel