devel

devel@libdivecomputer.org

291 discussions

Re: Mares Smart Apnea
by Jef Driesen 09 Sep '15

09 Sep '15

On 2015-09-04 12:25, Giorgio Marzano wrote: > Right now, I noticed a bug in the mares_iconhd_get_model function, line > 120 > of mares_iconhd.c, where sizeof should be actually strlen. > > if (memcmp (device->version + 0x46, models[i].name, /*sizeof*/ strlen > (models[i].name) - 1) == 0) { This is not a bug. The name field is a 16 byte array, not a string. The initialization with a sting literal is convenient. The remainder of the array will automatically get padded with zero bytes, which is exactly what we need. The correct fix is to add a new entry containing "Mares Smart". Then, the next question is: what's the correct model number? According to the model number in the memory dump (e.g. byte at offset 0), it's 0x10 or SMART: {"Smart", SMART}, + {"Smart Apnea", SMART}, {"Icon HD", ICONHD}, But then how do we distinguish the normal smart from the apnea variant? That will be important, because both appear to use a different data format. The strange thing here is that the normal smart already had a freedive mode. The main difference is that we now not only get a summary of each freedive in the session, but also a detailed profile. I wonder if there is some kind of format indicator in the header that we can use to distinguish between dives with the enhanced apnea format and the more limited normal format. Jef

2 7

Re: Mares Smart Apnea
by Giorgio Marzano 09 Sep '15

09 Sep '15

Again on the Mares Smart Apnea topic. I think I have found a problem on the current SW implementation and I need some advice. Sorry for the long message. I have dumped my DC logbook, and some cross checking between the code and the expected results from the mares SW. I think I have found some problem in the code. In the function "mares_iconhd_extract_dives" it seems to me that the code points to the very end of the buffer, then it starts crawling back to the beginning of the last immersion: offset = layout->rb_profile_end - layout->rb_profile_begin; unsigned int nbytes = 4 + headersize + nsamples * samplesize; ... // Move to the start of the dive. offset -= nbytes; ...but it seems that on the Smart Apnea there is not a constant samplesize: one immersion is a variable length (nsamples) sequence of dives , each one having one header (dive time, surface time, temperature, ...) and a stream of "dive time" depth measurements. If this is true, the current approach can't work, as long as it is no longer possible to compute "nbytes". Am I wrong? Is there any reason to start from the end and not from the beginning (the "end of profile ring buffer" eop) and then move forward? I am getting familiar with the memory layout of the DC but still have many many doubts about the library code and architecture. Any help would be very appreciated. I can provide the annotated dump, but I am not sure what the mailing list netiquette says about big attachments. Thank you in advance Giorgio EXAMPLE: *** start immersion 2015 08 31 10.08 18 25 : LEN (in bytes) 00 00 : ?? *** sample 1 *** 0c 00 : maxdepth(1.2) sample 1 13 00 : dive time (19 secs) 00 00 : surface time (0) fc 00 ?? fc 00 ?? 04 00 ?? 17 00 ?? 0b 00 depth //19 depth measurements: 1 per second 0c 00 depth 0b 00 depth 0b 00 depth 0b 00 depth 0b 00 depth 0b 00 depth 0c 00 depth 0c 00 depth 0b 00 depth 0b 00 depth 0b 00 depth 0b 00 depth 0b 00 depth 0b 00 depth 0c 00 depth 0b 00 depth 0b 00 depth 09 00 depth **** sample 2 *** 11 00 maxdepth (1.2) 2d 00 divetime 3c 00 surftime fc 00 ?? fc 00 ?? 05 00 ?? ...

2 3

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

Sample data repository
by Christian Guimarães 02 Jul '15

02 Jul '15

Hi! Is there any place or repository that I can download some dive sample data? By the way, I have a dive computer (TUSA IQ-650 Element) but unfortunately it doesn't provide a PC interface to download dive data. Thanks! -- Christian Guimaraes

3 4

Salted or fresh water
by Stan 02 Jul '15

02 Jul '15

Hi, Does anybody know how to configure lidivecomputer in order to get depth in fresh water. (Assuming it calibrated for salted water). For the Reefnet Sensus Ultra, I get the raw pressure and then I compute the depth. I guess there is something to change in units.h ? Stanislas

2 2

[Reefnet Sensus Ultra] help for a beginner
by stan.speleo＠notgmail.fr 30 Jun '15

30 Jun '15

Hi, I am trying to use the libdivecomputer lib in order to GET and SET the INTERNALS (INTERVAL, THRESHOLD, ENDCOUNT, AVERAGING) of the Reefnet Sensus Ultra logger. On Linux. I have not found any software on linux which can manage this task. I have as well another less important question : how to get a csv data for the dives ? This would be great because the only software I could find, "Subsurface", gives the data in an xml format, which I have to parse in order to proceed it by myself. For your information, I am working on a scientific associative project, which consists on recording water height in caves, during a long period of time (one year or more if possible). I'm new on this mailing list, but I am decided to make it work :-) Thanks. Stanislas Francfort

5 4

[PATCH] Remove removed function from public header
by Anton Lundin 26 Jun '15

26 Jun '15

reefnet_sensusultra_device_set_maxretries was killed off back in v0.3, but was still lying around in the public header. Signed-off-by: Anton Lundin <glance(a)acc.umu.se> --- include/libdivecomputer/reefnet_sensusultra.h | 3 --- 1 file changed, 3 deletions(-) diff --git a/include/libdivecomputer/reefnet_sensusultra.h b/include/libdivecomputer/reefnet_sensusultra.h index 4cff902..72d1ed6 100644 --- a/include/libdivecomputer/reefnet_sensusultra.h +++ b/include/libdivecomputer/reefnet_sensusultra.h @@ -45,9 +45,6 @@ dc_status_t reefnet_sensusultra_device_open (dc_device_t **device, dc_context_t *context, const char *name); dc_status_t -reefnet_sensusultra_device_set_maxretries (dc_device_t *device, unsigned int maxretries); - -dc_status_t reefnet_sensusultra_device_get_handshake (dc_device_t *device, unsigned char data[], unsigned int size); dc_status_t -- 2.1.4

2 1

← Newer
1
...
11
12
13
14
15
16
17
...
30
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

devel