devel August 2015

devel@libdivecomputer.org

6 participants
5 discussions

[PATCH] Skip unconnected ppo2 sensors
by Anton Lundin 09 Sep '15

09 Sep '15

The HwOS devices logs ppo2 sensor values even in Auto / Fixed SP mode, but they log them as reading zero, if there are no sensors there. This skips us reporting those zero values. Signed-off-by: Anton Lundin <glance(a)acc.umu.se> --- This shows one of the flaws with re-using the DC_SAMPLE_PPO2 value. Should we report unconnected sensors? how should a application actually handle them? Maybee we should look at the ppO2 value too, but for now this POC only looked at the mV values. src/hw_ostc_parser.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/hw_ostc_parser.c b/src/hw_ostc_parser.c index 6db9d27..954f6f7 100644 --- a/src/hw_ostc_parser.c +++ b/src/hw_ostc_parser.c @@ -885,6 +885,9 @@ hw_ostc_parser_samples_foreach (dc_parser_t *abstract, dc_sample_callback_t call value = data[offset + j]; } else { value = data[offset + j * 3]; + // Skip zero mV sensors, as they are most likely unconnected + if (array_uint16_le (data + offset + j * 3 + 1) == 0) + continue; } sample.ppo2 = value / 100.0; if (callback) callback (DC_SAMPLE_PPO2, sample, userdata); -- 2.1.4

2 7

Individual O2 sensor readings
by Anton Lundin 03 Sep '15

03 Sep '15

Nowadays Subsurface have a way to represent individual o2 sensor values, but none of the libdivecomputer backends export such. The diverite_nitekq and shearwater_predator backends have support for exposing DC_SAMPLE_PPO2 samples, which looks to be the calculated / voted PPO2. The hwOS-based HW computers have such sensor values stored, and probably the Shearwater ext devices to. I was thinking about implementing support for the hwOS based devices, and was thinking if anyone have some preference on how such values should be represented in libdivecomputer? Should we go for DC_SAMPLE_PPO2_SENSOR1 or something like that to expose the individual sensor values? Or do anyone else have some other, better, idea? //Anton -- Anton Lundin +46702-161604

2 6

Virtual environment is rough for us rookies
by Terry Lowe 29 Aug '15

29 Aug '15

I am a fan of Diving Log 6.0. I normally used a Mac, so installed VirtualBox just so that I could run Windows 7 in order to run Diving Log 6.0 Everything loads fine…the drivers install without error. When I try to download dives from my Cobalt 2, I get the following error in my log file: INFO: Write: size=1, data=01 INFO: Read: size=16, data=3039313430303337FC0802000200A002 INFO: Write: size=1, data=09 ERROR: Failed to receive the answer. [in atomics_cobalt.c:288 (atomics_cobalt_read_dive)] INFO: libdivecomputer-0.dll version: 0.5.0-devel I Installed the Atomic Cobalt Logbook, and it finds the computer and downloads the dives, but this software is pretty bad. Was hoping there would be an easy fix to allow this to work using Virtual Box. I am not opposed to using some other virtual environment if it has been shown to work. Thanks!! Terry

2 1

Apeks quantum
by Brodie O'Rourke 24 Aug '15

24 Aug '15

Hello, I have an Apeks quantum dive computer. It came with a computer interface computer & disk. The disk contained pc log book, but no driver. I used this website to help me find a driver to work. Zeagle worked, at least my computer says it recognizes the device & it's working normally. I still can't download the data into pc log book. I downloaded diving log 6.0 & tried quantum as well as quantum x & several other options, but it kept saying the device is not connected. Sven Knoch at dive log suggested I send analysis data from my dive computer to this mailing group What kind of information is required? Also, when I connect the dive computer to the interface before the driver is installed, the Green light stays on & the computer goes from pc mode to dive mode. Once the driver is installed, the Green light stays off & flashes when trying to connect to pc dive log & diving log 6.0. Any information & support would be greatly appreciated. Regards, Brodie

2 1

Problem with reading data from a "Scubapro Chromis"
by Patrik Martinsson 22 Aug '15

22 Aug '15

Hi, I'm trying to get my "Scubapro Chromis" to work with "libdivecomputer", but it doesn't seem to work. Is this tested with a real "Scubapro Chromis" or is the support "just added on belief that it should work" (I noticed that the support was added a couple of months ago for the Chromis) ? This is what I get when I try to dump the memory from the Chromis, ./universal -n "Scubapro Chromis" -b "meridian" /dev/ttyUSB0 DATETIME 2015-07-14T14:07:51Z (1436882871) VERSION 0.5.0-devel (0158739bcff3c4c3f8944e6e06932d836821cf28) Opening the device (Scubapro Chromis, /dev/ttyUSB0). ERROR: Failed to receive the header. [in uwatec_meridian.c:111 (uwatec_meridian_transfer)] Registering the event handler. Registering the cancellation handler. Downloading the memory dump. Event: progress 0.00% (0/4294967295) ERROR: Failed to receive the header. [in uwatec_meridian.c:111 (uwatec_meridian_transfer)] universal.c:795: Error downloading the memory dump. Result: Timeout I would be surpriced if there was something wrong with the watch, however that is of course possible. Looking at the code I can see that there is an "echo" that is being received before the header, so something is going on right (or am I missing something) ? Thankful for any pointers/help etc. Kinda stuck on an Malaysian Island and would love to get my dive log working =) Best regards, Patrik Martinsson

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

devel August 2015