devel

devel@libdivecomputer.org

3 participants
290 discussions

Mares Nemo Excel - Nitrox bug?
by Björn Spruck 29 Mar '12

29 Mar '12

Hi, Strange behaviour for Nemo Excel. If I readout my dives, they are set to Nitrox 32 while the internal Logbook shows them as AIR (which they actually were!). My guess: there is an additional AIR/EAN flag. Tschau, Bjoern

2 5

Patch: Mares Nemo Nitrox/Air detection
by Björn Spruck 27 Mar '12

27 Mar '12

--- /tmp/tmp183gxE-meld/src/mares_nemo_parser.c +++ /home/bjoern/Dokumente/libdivecomputer/src/mares_nemo_parser.c @@ -248,7 +248,20 @@ break; case FIELD_TYPE_GASMIX: gasmix->helium = 0.0; - gasmix->oxygen = p[53 - 43] / 100.0; + switch(p[53-1]){ + default:/// Mode unknown + return PARSER_STATUS_UNSUPPORTED; + case 2: /// FREE, can not happen!! + return PARSER_STATUS_UNSUPPORTED; + case 3: /// Bottom timer... no idea what to do... lets unsupport it + return PARSER_STATUS_UNSUPPORTED; + case 0: /// AIR + gasmix->oxygen = 0.21; + break; + case 1: + gasmix->oxygen = p[53 - 43] / 100.0; + break; + } gasmix->nitrogen = 1.0 - gasmix->oxygen - gasmix->helium; break; default:

1 0

Mares M1 data format
by Björn Spruck 27 Mar '12

27 Mar '12

Hi, I reverse engineered a bit the M1 data format and would like to add events like "deco", "slow warning" etc in the data stream. Actually the format is similar to other mares computers (nemo), just shifted a bit. How do I submit patches? Tschau, Björn

2 6

ProPlus 2.1 Temperature Values
by Sam Calhoun 01 Mar '12

01 Mar '12

Hi, Just writing to say that after using libdivecomputer in my program and testing it with a few different devices, I have found one small bug. The ProPlus 2.1 (the version with metal buttons) did not parse temperature values correctly. Here's the small change to "oceanic_atom2_parser.c" that fixed the issue for me (relative to the latest snapshot on the download page): --- oceanic_atom2_parser.c-revBASE.svn000.tmp.c Wed Feb 29 23:08:42 2012 UTC +++ oceanic_atom2_parser.c Mon Feb 6 23:48:19 2012 UTC @@ -37,6 +37,7 @@ #define VEO20 0x4359 #define VEO30 0x435A #define ZENAIR 0x4442 +#define PROPLUS21 0x4444 #define GEO20 0x4446 #define OC1B 0x4449 @@ -329,7 +330,7 @@ temperature = data[offset + 3]; } else { unsigned int sign; - if (parser->model == ATOM2) + if (parser->model == ATOM2 || parser->model == PROPLUS21) sign = (data[offset + 0] & 0x80) >> 7; else sign = (~data[offset + 0] & 0x80) >> 7; Thanks, Sam

2 1

device_set_fingerprint
by Steve Boyd 29 Jan '12

29 Jan '12

I am starting to write my own program to download my dive computer using the libdivecomputer DLL. I am a bit confused about exactly what the device_set_fingerprint function does. The documentation suggests that it has something to do with limiting downloads to just new dives, but it is unclear about exactly how it accomplishes that. Any light you can shed on this is appreciated.

2 1

Pro Plus 2
by Philip Balister 15 Jan '12

15 Jan '12

So I have the right cable now and I can download dives from my computer into subsurface. A couple of things: 1) I have six dives in the computer, but only the first 5 show in subsurface. 2) There is no pressure information shown in subsurface. I'll look at these issues some more, I am not sure if it is libdivecomputer, subsurface, or the computer that is the issue. Philip

4 9

Re: Oceanic Pro Plus 2
by Philip Balister 12 Jan '12

12 Jan '12

On 01/10/2012 02:34 PM, Jef Driesen wrote: > > Can you try with Oceanlog? If it's not working either, there is very > little I can do, and you better contact Oceanic support. If it does > work, we can try to figure out what is wrong. Before buying a download cable for an Oceanic product read this: http://www.oceanicworldwide.com/us/faq/Personal_Dive_Computer_and_USB_Compu… The correct cable is on order now and I will let you know how it works out. Philip

2 1

Oceanic Pro Plus 2
by Philip Balister 09 Jan '12

09 Jan '12

I am trying to download data from the Pro Plus 2 dive computer. dmesg shows ttyUSB0 being created and I have added myself to the proper group. Also tried as root. It looks like nothing is coming back from the computer. I entered the 2 minute download mode and can watch the time count down. Anymore suggestions? Philip [balister@nomad examples (master*)]$ sudo ./vtpro /dev/ttyUSB0 DEVICE=/dev/ttyUSB0 oceanic_vtpro_device_open Timeout: value=3000 DTR: value=1 RTS: value=1 Sleep: value=100 Flush: queue=3, input=4, output=0 Write: timer=0, size=2, data=AA00, remaining=2 Read: timer=3000, size=3, data=000000, remaining=0 oceanic_vtpro.c:182: Failed to receive the answer. oceanic_vtpro_test.c:37: Error opening serial port. SUMMARY ------- test_dump_memory: Timeout

2 2

Atomic Cobalt
by Kurt 27 Dec '11

27 Dec '11

I have been looking at Subsurface dive log 1.2 which offers to download Atomic Cobalt. I can't make it work. I suppose that it may not be implemented, or that my bonafide software installation which includes libusb may interfering or incompatible. My installation and connection works fine with the Atomic software. I can't see any Atomic support in the latest snapshot, so I suppose it is the former. If this is a work in progress I may be of some [not insignificant] help to the implementor(s). If they are interested, get in touch with me. Perhaps there is Fog in the cockpit and I am doing something wrong? My platform is Win7/32 and I am entering COM3 as the device. "COM3" works fine with Uwatec. The Cobalt is attached and "Connected" (enumerated and recognized by PC) I have tried three different firmwares, currently 1.13/1 Is there a special device name or sequence. Cheers, kurt

4 12

uwatec time format suggestion
by Kurt 23 Dec '11

23 Dec '11

Jeff and all Thanks for the good and interesting work on the libdivecomputer project. By way of introduction I will say that I have been writing Aladin readers and logs for my own use since the prior century. I still have a working Palm Pilot and home made cable. Alas, the Palm platform and SDK changed too frequently to make publishing worthwhile. I also wrote my own reader for the Smart and was quite excited/disappointed to see that you got no further decoding Smart Com/Pro than I did. (c: Down to business: I don't know why, but everyone since time immemorial has wanted to complicate the calculation of Uwatec time by attempting to attach it to an epoch. It changes from model to model and becomes problematic with battery changes and other malfunctions, though it will will seem to work most of the time. I believe this is the wrong approach. The Aladin computers since the days of MemoMouse have utilized a 500 ms counter (2 tics/second). It is not attached to any particular epoch though it may appear that way since the factory has to initialize the counter with _something_. However, battery changes and other vagaries may change that. Each dive has a four byte tic count (UInt32) Each *download* also specifies the tic count at the time of download in the old MemoMouse, or you explicitly retrieve the Dive Computer Time (in tics) as outlined in the Uwatec Smart protocol page. The difference between the two divided by two: ( DiveComputerTimeInTics-DiveTimeInTics ) >> 1 is the total number of seconds since the dive began. This is perfectly clean number that is completely independent of epoch, timezone or platform. It is also independent of Aladin platform, be it plain, Nitrox, ultra, tech or smart. You don't need any +/- 1800 adjusters magic numbers or anything of that sort. The introduction of epochs and timezone adjustments are then left to the implementor and platform as they should be. This also generally reduces time errors since the difference between ticsnow and ticsthen, is much smaller quantity of tics to be operated on and time interpretation accuracy will depend on the host computer time source instead of the dive computer. Regards, kurt

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

devel