On 28/04/2024 19:03, Kevin Metcalf wrote:
Just checking in to see if you learned anything from the files. I am wondering
if my computer will work going forward as I haven't had this issue in the past.
As suspected, this was indeed a problem with the memory layout. Your Geo has an
older
On 11/01/2024 21:27, Robert Helling wrote:
I have a question re the Divesoft Liberty CCR. From their website I understand
it has a total of four (2x2) O2 sensors rather than the three other rebreathers
have. We now had a user reporting Subsurface to crash when handling a dive from
that
On 7/12/2023 20:21, Dirk Hohndel via subsurface wrote:
There is an oddity about the way this works. GitHub only does releases for tags.
So there are basically two options:
(a) do a "latest" tag and post all the binaries under that (which is what I've
done so far)
(b) create a tag for every
On 8/12/2023 20:56, Philippe Massart via subsurface wrote:
Since several years now, I import .DLF files from my Divesoft Freedom computer
without any problem.
I saw that Divesoft Freedom and Liberty where integrated into libdivecomputer,
and that a next release of Subsurface could include
On 13/11/2023 01:44, micha via subsurface wrote:
Option 4 : Figure out why Subsurface is importing a "gaschange" event
to a third cylinder instead of assigning it to one of the cylinders with
transmitter values attached.
That's easy to answer. You have 4 configured gas mixes:
1. (off)
On 18/05/2023 09:49, Berthold Stoeger via subsurface wrote:
Currently I am locked out of GitHub, because it changed to two-factor
authentication. This is somewhat annoying as currently I have a number of more
"interesting" problems.
It seems that I have to install an application such as
On 18/12/2022 20:22, Attilla de Groot wrote:
Shearwater has solved this issue in their latest update (v93). It now looks
nicely in their own app as well and I’m able to download the logs directly into
subsurface.
Fixed as in new dives are now recorded correctly? Or is the data also fixed for
On 5/09/2022 17:25, Attilla de Groot wrote:
I looked at the dive profile and the xml, but I don’t see anything that would
explain this. I was just diving with 100% o2 and AIR as diluent. I did have a
transmitter to my bailout stage that also had AIR. Could this be related?
I have downloaded the
On 5/09/2022 12:46, Attilla de Groot wrote:
On 5 Sep 2022, at 12:19, Jef Driesen <mailto:j...@libdivecomputer.org>> wrote:
According to the logs, there were two dives downloaded:
2022-07-29 21:14:40
2017-01-01 01:31:37
That's clearly not a dive done "this morning", but
On 4/09/2022 13:34, Attilla de Groot via subsurface wrote:
This morning I made my first ccr dive (of course it was horrible, I need to
learn to dive again...) .
I have a Petrel3 with it, but I'm unable to download the dive log to the android
app (I'll try later with my laptop). It connects,
On 13/06/2022 05:04, Dirk Hohndel via subsurface wrote:
A couple of dive computers will import all gases that are configured, even if
you never switched to them. And if you have a default cylinder configured in
Subsurface, then this turns into these ghost cylinders.
One reason libdivecomputer
On 29/05/2022 13:50, Daniel Azuelos via subsurface wrote:
[ Rédigé dans le sens de lecture normal.
Written in the usual reading direction. ]
Le (on) 29/05/2022, Jef Driesen a écrit (wrote):
[...]
| This is a problem at the bluetooth (or driver) layer. Subsurface is unable
| to connect, so
On 27/05/2022 18:23, Daniel Azuelos via subsurface wrote:
Since Subsurface 5.0.8 was crashing sometimes during repeated tests,
I went back to 4.9.7 which seemed to be crash proof in the exact
same radio environment.
Distance from my Mac to the i770R: 30 cm.
i770R
On 8/02/2022 21:54, Dirk Hohndel via subsurface wrote:
I haven't spent any time at all on the GitHub wiki setup to know how easily we
could curate this and more importantly how easily one can create useful deep
links to specific answers that could be posted into email / the forum. I
understand
On 25/10/2021 19:25, Linus Torvalds wrote:
On Mon, Oct 25, 2021 at 10:13 AM Jef Driesen wrote:
What's the reason for ignoring the fingerprint if you don't have the
corresponding dive anymore?
Simple: you successfully downloaded all the dives, but had some
problems, and never saved them
On 24/10/2021 02:12, Dirk Hohndel via subsurface wrote:
(3) close the cloud storage, open a local .xml file; download again
-> fingerprint file is found, but the matching dive is not in the dive
list, so fingerprint gets ignored (but why are we even looking at it???)
-> dives are
On 8/07/2021 08:40, duefer--- via subsurface wrote:
my BT connection to my Ratio iX3M dosen´t work.
Which iX3M model do you have? The screenshot shows a Bluetooth Low Energy (BLE)
connection to an iX3M 2021 GPS Tech+. That is the latest model which indeed
supports BLE, but the older model
On 11/01/2021 20:49, Linus Torvalds via subsurface wrote:
On Mon, Jan 11, 2021 at 11:37 AM Markus Hinkelmann via subsurface
wrote:
I tried to import my dives from my Mares Quad Air using the Interface „Mares
BLUELINK Pro“ to subsurface.
I'm afraid that the Mares BlueLink Pro has been the
On 31/10/2020 17:56, Dirk Hohndel via subsurface wrote:
On Oct 31, 2020, at 3:35 AM, Matthias Heinrichs via subsurface
wrote:
BT LE however fails repeatedly with this error:
Subsurface: v4.9.7-223-gbd0d7bd0faa1, built with libdivecomputer
v0.7.0-devel-Subsurface-NG
On 11/08/2020 19:22, Jef Driesen wrote:
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
Dirk,
I don't see a description of the problem in the email thread, so I'm probably
missing some context here. Anyway, from a quick inspection of the
libdivecomputer logfile, the contents of the compact headers looks suspicious.
The first 4 entries all look good:
i=0, offset=0, current=1,
On 8/05/2020 00:57, Linus Torvalds wrote:
Ok, so I've just spent several hours re-synchronizing our subsurface
branch with Jef's upstream.
...
I'll have a look, allthough that might take a while. Been a bit busy with real
life during the corona crisis (day job, kids and family), so a bit
On 2020-03-10 01:22, Matt Thompson via subsurface wrote:
Device Path: /dev/bus/usb/001/002
Device Class: Use class information in the Interface Descriptors (0x0)
Vendor ID: 0403
Vendor Name (reported): Suunto
Vendor Name (from DB): Future Technology Devices International, Ltd
Product ID:
On 2020-03-09 22:39, Miika Turkia via subsurface wrote:
This is what I get on dmesg when attaching the D4 cable:
---8<---
[30804.146977] usb 1-2: new full-speed USB device number 12 using
xhci_hcd
[30804.301648] usb 1-2: New USB device found, idVendor=0403,
idProduct=6001
[30804.301653] usb
On 9/03/2020 21:37, Christof Arnosti via subsurface wrote:
- Suunto D4 (uses SUUNTO_D9): App (or Download?) Crashes after about 4
downloaded drives. There should be a mail with logs in the support mail address.
Do we have a download log for this case? That might give some more clues. I
didn't
On 7/03/2020 13:50, Christof Arnosti via subsurface wrote:
Can you explain this a bit more?
I think that DKIM / DMARC does exactly what it should: preventing modification
of mails with "MailFrom" from my domain on-the-fly.
I also have SPF configured, which should in theory also lead to a
On 2020-02-13 12:49, Martin de Weger wrote:
Where can I download the build for the Mac so I can test it?
I know there have been some issues with the daily build on the site.
At the moment there is no build with the fix yet.
Jef
___
subsurface
On 2020-02-11 09:01, Martin de Weger wrote:
It is correct. This was the first trip I’ve used this computer (as a
backup computer), and I thought I did set up the gas mixture
correctly.
I have pushed a fix for the incorrect depth, and implemented the gas
switches too.
Jef
On 2020-02-08 10:46, Martin de Weger wrote:
Yep, here it is.
It looks like there are gas switches in the dives that fail to parse. Is
that correct? Two of those dives are a bit unusual, so I want to double
check with you.
For example the dive on 2020-01-27 14:51:00 starts with Air. After
On 5/02/2020 21:33, Martin de Weger wrote:
Here is the logfile and the print from the Cressi App. I also added screenshots
from the nRF Connect app, hop this is what you wnt. The weird thing is, They
iPhone is able to connect using BT, not the macbook (with the Cressi app)..
Can you export
On 2020-02-05 13:35, Martin de Weger wrote:
I’ll have a look. When using the dum-file option (in the Beta version
of subsurface) an error is thrown (something went wrong). I wanted to
install the stable version from the website, but that link is broken
On 2/11/19 07:41, tormento wrote:
I am getting errors while importing dives from Perdix AI with its BT dongle (I
don't hava any other to try) while it's own software can import dives correctly.
I select choose Bluetooth mode, find the Perdix and save.
When I try to import, I get:
Connecting
On 7/09/19 20:16, Linus Torvalds wrote:
Now, there are other changes that Jef did to the Mares code, but the
BLE-specific change I see is his changes to do the BLE packet cache,
so it really looks like that might be it.
I doubt that change will fix Fabio's problem. That patch is needed to
On 2019-07-01 23:26, Patrick Briscadieu wrote:
Hello I ve got a Mares Quad,
And since the dive number 48 I can’t imports dives from my computer.
Can you analyses the files attached in this mail please
This is most likely because you have a newer generation Mares Quad with
more flash memory.
On 2019-04-22 19:02, Linus Torvalds wrote:
I think Jef is also on the subsurface list, but I'm just adding him
here as an explicit participant in case he only tracks it
occasionally.
I'm indeed subscribed to the list. I try to follow up on the
development, especially the libdivecomputer
On 4/02/19 21:59, Gaetan Bisson wrote:
[2019-02-04 11:59:34 +0100] didier duriez:
j'utilise comme ordinateur, un Mares Genius, je ne le trouve pas dans votre
liste d'ordinateur,
Notre logiciel communique avec les ordinateurs de plongée par le biais
de cette bibliothèque :
On 6/12/18 19:48, Dirk Hohndel wrote:
On Thu, Dec 06, 2018 at 06:10:25PM +0100, Robert Helling wrote:
a user ask on Facebook about accessing his Galileo Luna computer from
Android. That dive computer has an irda interface and he has an OTG
usb-irda cable. Is there a chance to get this to work
On 2018-12-05 17:17, Long, Martin wrote:
I've noticed some problems with the import of gases on Shearwater
computers. There are possible 2 issues here, but these seem to be
related.
1) I just imported 4 dives from last weekend, all CCR. The first 3
were on 13/60 diluent and the last one on
On 2018-09-27 02:37, Linus Torvalds wrote:
So it turns out that "BLE is slow" is actually the *reason* for the
problem.
There's some really odd timing thing, where when we send the read
command as two different packets (first the two command bytes, then
the 8 bytes of offset/length), and wait
On 2018-09-26 19:40, Linus Torvalds wrote:
Jef, what are the semantics for
ret = dc_iostream_read(iostream, buf, sizeof(buf), NULL);
meant to be when there is only a partial read? Right now it returns
DC_STATUS_SUCCESS and garbage in the end of "buf". Which really does
seem wrong. The
the special aqualung USB cable that retails for
something ridiculous like $85 USD.
Even more sadly, I don't think libdivecomputer actually supports the i100
at all. I assume that it is very similar to the i200 and i300 that *are*
supported, but it might take some debugging and some help from Jef Driesen
On 2018-09-08 01:48, Dirk Hohndel wrote:
On Sep 7, 2018, at 3:11 PM, Linus Torvalds
wrote:
So realistically I'm weeks away, and that's not some guarantee either.
I'm really happy with how quickly the Garmin parser came together, and
we have that going for us, but plan on it being USB-only for
On 2018-08-14 16:47, Dirk Hohndel wrote:
On Aug 14, 2018, at 7:40 AM, Jan Mulder wrote:
Since May 19, 2018 Heinrichs-Weikamp introduced something new with
respect to firmware numbering. On that date a version was released
called 2.97 SP1. As I found a simple bug related to CNS display
On 2018-08-06 01:01, Dirk Hohndel wrote:
a) tiny change to libdivecomputer (Linus, this was so trivial that I
simply pushed it to our branch... Jef, I /think/ you want this as
well) to recognize the Aqualung i750TC as Bluetooth capable
divecomputer. I don't know, yet, if it needs any additional
On 22-07-18 00:15, stra...@wp.pl wrote:
I have tried to import the dive data from computer logs. I could only get 2 last
dives whlie there is 6 in the computer log book history.
I checked your data, and there are only two dives present. You have configured a
(very short) 2 second sample rate,
On 2018-07-05 21:10, Otto Strassen wrote:
After updating to 4.8.0 I can no longer sync my OSTC3 with subsurface.
I have re-paired the device but it still does not work.
Someone else seems to be having the same problem:
On 2018-06-16 01:16, Dirk Hohndel wrote:
We have lapsed on our goal to do regular releases.
Can we use the next two weeks to get both desktop and mobile into
releasable shape? Linus and I are doing "in the field testing" this
week in Japan - and true to our past track record, we have brought a
On 11-06-18 20:21, Anton Lundin wrote:
On 04 June, 2018 - Dirk Hohndel wrote:
I don't have an outstanding patch from you, so not sure what you are referring
to.
There was a diff a while back in this thread, in
20180523144751.gc12...@hirohito.acc.umu.se , which made the code fall
back to the
On 25-05-18 16:35, Willem Ferguson wrote:
On 25/05/2018 15:55, Jef Driesen wrote:
The main disadvantage is that you'll no longer know which type of ppO2
(sensor or voted/average) you are getting. Especially if you only have
one sensor.
I would agree, but at least one gets the calculated pO2
On 2018-05-23 16:47, Anton Lundin wrote:
On 23 May, 2018 - Anton Lundin wrote:
The simple solution is to just emit the average/voted ppO2 when we
can't
find the calibration values.
Its a graceful degradation of functionality, and way better than not
showing any ppO2 at all.
It should be
andard Petrel and the Fischer Petrel 2.
The
most knowledgeable person to approach is Jef Driesen but he would need
some specific information from your download. A first approach is to
inspect the .bin dumpfile generated for debug in Subsurface. Then use
his dctool executable (If I remember cor
On 2018-04-23 19:07, Linus Torvalds wrote:
On Mon, Apr 23, 2018 at 12:56 AM, Sébastien Dugué
wrote:
On Sun, Apr 22, 2018 at 10:09 PM, Linus Torvalds
wrote:
It still has the exact same problem it always had: it's random
On 2018-04-25 22:12, Linus Torvalds wrote:
On Wed, Apr 25, 2018 at 11:51 AM, Dirk Hohndel
wrote:
I have a Petrel (single stack BT) and Petrel 2 (dual stack) and will
test
those over lunch today. I'll try to test Mac and Android
(embarrassingly,
I currently don't have a
On 2018-04-20 20:25, Linus Torvalds wrote:
On Thu, Apr 19, 2018 at 4:29 AM, Jef Driesen <j...@libdivecomputer.org>
wrote:
On 2018-04-19 12:10, Dirk Hohndel wrote:
To the best of my knowledge, no version of the Predator / Petrel /
Nerd
family has a wired serial interface, all they do
On 2018-04-20 04:56, Matt Thompson wrote:
My Atomic Cobalt2 worked on Windows and macOS but failed on Linux. I
think
the failure on Linux is a configuration issue on my part but for
completeness I get the following in the console:
ERROR: Failed to open the usb device. [in
On 22-04-18 18:37, Linus Torvalds wrote:
On Sun, Apr 22, 2018 at 3:52 AM, Jérémie Guichard wrote:
I just tried Scubapro G2 over bluetooth on Android build and it did not
work, but I must say this was already the case on Android for the normal
release.
Hmm. I just tried
It looks like some data got transferred succesfully. But then the logging
stops. Can you send the libdivecomputer logfile? That should give some more
info. (I'm not sure whether android app supports saving libdc log.)
Jef
On April 22, 2018 12:52:48 PM GMT+02:00, "Jérémie Guichard"
Hi,
I just fixed a nasty bug in the ostc3 backend that was introduced with
the BLE support (commit 0978f8c0fa70710bad3fb865ffe3a20961c408dc).
Ironically everything works fine when using BLE, but not for bluetooth
classic or its serial emulation.
Please upgrade asap, because this bug not
On 2018-04-19 12:10, Dirk Hohndel wrote:
I have a question about the meaning of the transport flags.
My understanding was that DC_TRANSPORT_SERIAL is an indication that the
dive computer supports some form of wired serial interface (Rs232 or
more
typically serial over USB). What I don't
On 2018-04-19 09:42, Sébastien Dugué wrote:
On Thu, Apr 19, 2018 at 1:50 AM, Linus Torvalds
wrote:
On Wed, Apr 18, 2018 at 4:18 PM, Linus Torvalds
wrote:
Hmm. Which IRDA chip is it that is in the Uwatec dongle?
Is it perhaps the
On 2018-04-19 08:40, Dirk Hohndel wrote:
On Wed, Apr 18, 2018 at 11:37:53PM -0700, Dirk Hohndel wrote:
On Thu, Apr 19, 2018 at 08:13:23AM +0200, Jef Driesen wrote:
>
> You can also get the mask with the built-in transports from libdivecomputer
> with the dc_context_get_transports()
On 2018-04-19 06:25, Dirk Hohndel wrote:
@@ -123,10 +109,31 @@ void fill_computer_list()
dc_iterator_t *iterator = NULL;
dc_descriptor_t *descriptor = NULL;
+ int transportMask = 0;
+#if defined(BT_SUPPORT)
+ transportMask |= DC_TRANSPORT_BLUETOOTH;
+#endif
+#if
On 2018-04-12 20:57, Linus Torvalds wrote:
On Thu, Apr 12, 2018 at 10:52 AM, Allen Hall
wrote:
BLE communications log is attached. I may be able to tease out more
verbose
info if needed, but this looks pretty complete to me.
This looks like it does contain all the
On 2018-04-10 16:42, Davide DB wrote:
On 10 April 2018 at 16:10, Willem Ferguson
wrote:
On a Samsung S6 (Android 7.0) the phone sees my Petrel 2 and pairs to
it.
However, when downloading dives, the phone only sees a BTLE device and
apparently cannot handle
On 2018-04-10 18:44, Linus Torvalds wrote:
On Tue, Apr 10, 2018 at 9:26 AM, Dirk Hohndel wrote:
What's our best bet to create a process to do this?
Ask people to send their dive computers to Linus? Tempting, but maybe
not as scalable as one might hope.
Yeah. Especially
On 2018-02-28 11:52, Willem Ferguson wrote:
1) In both CCR mode as well as SCR mode, the Petrel 2 allows switching
between OC bailout gases and CC gases. This done by performing
selecting either BO->SC or SC->BO from the Shearwater menu. These
events must be recorded in the dive log but are
On 2018-02-07 07:48, Willem Ferguson wrote:
I will be using Shearwater again within the next week and cross-check.
I will also be diving the same Predator with a single sensor two weeks
from now. One thing that may be relevant is that the Shearwater has
two different calibration modes, one for 3
On 2018-02-05 15:42, Willem Ferguson wrote:
I definitely did pick the Predator option, both in the Linux OS
Bluetooth setup and within Subsurface. The O2 sensor on the computer
was calibrated using oxygen in the way specified in the user manual
and it performed very well. I have no idea how this
On 2018-02-05 15:35, Davide DB wrote:
On 5 February 2018 at 13:49, Jef Driesen <j...@libdivecomputer.org>
wrote:
Last week, I merged a change to disable the ppO2 samples if all
(calibrated) sensors have the factory default calibration value
(2100). If
you happen to have a unit that d
On 2018-02-05 14:00, Anton Lundin wrote:
On 05 February, 2018 - Willem Ferguson wrote:
This weekend I used a Shearwater predator dive computer. Connecting
via Bluetooth no problem, had to force it to classical bt as it
defaulted to LE. However, downloading the dive to Subsurface
provides two
On 2018-02-05 11:31, Willem Ferguson wrote:
This weekend I used a Shearwater predator dive computer. Connecting
via Bluetooth no problem, had to force it to classical bt as it
defaulted to LE. However, downloading the dive to Subsurface provides
two problems:
1) The duration for each dive is
On 03-02-18 18:05, Berthold Stoeger wrote:
On Samstag, 3. Februar 2018 17:46:10 CET Rob Mason wrote:
Hi Berthold - the subgear is irda, not bluetooth. It has worked previously
on older versions, but unable to connect on 4.7.6-1 on Mint Linux 18.3. --
Yes I know. Nevertheless, the "interface
On 19-01-18 14:14, Robert Helling wrote:
Dirk,
On 19. Jan 2018, at 08:52, Dirk Hohndel > wrote:
Here's a quick heads up: I am planning to shut down some of the services that I
provide on my hardware (and that aren't really used anymore). In the next
On 22-12-17 10:53, Davide DB wrote:
I added this bug on Github for future reference:
https://github.com/Subsurface-divelog/subsurface/issues/971
I think Anton's suggestion, to check the calibration factors and emit the
average ppo2 instead of the individual values if they are all equal to
On 2017-12-02 22:39, Anton Lundin wrote:
On 02 December, 2017 - Anton Lundin wrote:
I saw something odd looking at that data. There's another calibration
value in the data, which we never figured out the meaning of.
In all other sample data its bin zero or low values like 2. In your
data
its
On 01-12-17 17:43, Davide DB wrote:
On 1 December 2017 at 16:54, Jef Driesen <j...@libdivecomputer.org> wrote:
On 2017-12-01 15:57, Davide DB wrote:
That's already good to know. So that means that either the calibration
constant, our calibration formula, or even the decoding of the mil
On 2017-12-01 15:57, Davide DB wrote:
Yes, what do you need exactly?
I this thread I shared the dctool raw data file and some screenshots
of Shearwater desktop and Subsurface of the same dive.
I can share the Subsurface xml file and maybe an export from
shearwater desktop if exist.
Eventually I
On 2017-11-27 17:27, Anton Lundin wrote:
On 27 November, 2017 - Davide DB wrote:
On 17 November 2017 at 21:59, Davide DB wrote:
Dctool is a lucky process. 99% of the times I get errors like this:
[73.192176] ERROR: Failed to receive the response packet. [in
On 2017-11-20 02:45, Linus Torvalds wrote:
I just pushed out support for the new Suunto EON Core to the
subsurface branch of libdivecomputer, but I don't actually have access
to the hardware, so it's purely based on reporting from Nick Shore.
It almost certainly "just works" (just different USB
17 00:00:00 2001
From: Jef Driesen <jefdrie...@users.sourceforge.net>
Date: Mon, 13 Nov 2017 09:30:41 +0100
Subject: [PATCH] Add support for the Scubapro Aladin Square
---
src/descriptor.c | 1 +
src/device.c | 2 +-
src/uwatec_g2.c | 14 --
On 14-11-17 21:33, Linus Torvalds wrote:
On Tue, Nov 14, 2017 at 12:15 PM, Jef Driesen <j...@libdivecomputer.org> wrote:
Ah that explains the difference. In upstream libdivecomputer the buffer is
one byte larger:
unsigned char buf[TX_PACKET_SIZE + 1];
And that may actually end up
On 14-11-17 21:15, Jef Driesen wrote:
On 14-11-17 21:04, Linus Torvalds wrote:
On Tue, Nov 14, 2017 at 11:57 AM, Jef Driesen <j...@libdivecomputer.org> wrote:
I suspect this is not caused by a difference in the libusb version, but a
difference in the subsurface branch of libdiveco
On 14-11-17 21:04, Linus Torvalds wrote:
On Tue, Nov 14, 2017 at 11:57 AM, Jef Driesen <j...@libdivecomputer.org> wrote:
I suspect this is not caused by a difference in the libusb version, but a
difference in the subsurface branch of libdivecomputer. If you look at the
g2.log of the succ
On 14-11-17 20:29, Linus Torvalds wrote:
On Tue, Nov 14, 2017 at 11:17 AM, Linus Torvalds
wrote:
On Tue, Nov 14, 2017 at 10:52 AM, vavincavent wrote:
and ... i join usb.pcap file!
Ok, that's a good dump. I see
- device 1: root hub
On 12-11-17 19:09, Linus Torvalds wrote:
On Sun, Nov 12, 2017 at 5:16 AM, vavincavent wrote:
I try with joined file scubapro_g2.c to download from scubapro square.
Hmm. Can I see what the packets on the wire are, just in case we have
some odd libusb issue or
On 2017-11-10 14:52, vavincavent wrote:
It was the libdivecomputer log file, from subsurface :
Subsurface: v4.7.2-54-g97712559192c, built with libdivecomputer v0.6.0-
devel-Subsurface-branch (7de3a549ee588fef4702ee9d894e390aca43950d)
INFO: Open: vid=c251, pid=2006
INFO: Open: interface=0,
On 31-10-17 23:35, Berthold Stoeger wrote:
On Dienstag, 31. Oktober 2017 11:29:00 CET Jef Driesen wrote:
I believe you have the model number wrong. I think it should be 0x17,
and your test seems to confirm that:
Well, I put a printf directly after "rc = scubapro_g2_transfer (d
On 2017-10-31 12:12, Berthold Stoeger wrote:
Hi Jef,
On Dienstag, 31. Oktober 2017 11:29:00 CET Jef Driesen wrote:
On 2017-10-23 00:55, Berthold Stoeger wrote:
> On Sonntag, 22. Oktober 2017 04:31:39 CEST Linus Torvalds wrote:
>> so you literally *could* try to claim it's a G2 and t
On 2017-10-23 00:55, Berthold Stoeger wrote:
On Sonntag, 22. Oktober 2017 04:31:39 CEST Linus Torvalds wrote:
so you literally *could* try to claim it's a G2 and try to see how far
it downloads.
The handshake is different. The G2 client sends 1b and 1c1027 and
expects
01 as the answer
On 2017-10-27 05:00, Malcolm wrote:
I get a data error message when I try and download dives from my
Oceanic VT
4.1 dive computer. I am using a new laptop computer. Attached are the
files
suggested in subsurface help
It looks like this is yet another case of a corrupt ringbuffer begin
On 25-09-17 19:33, Linus Torvalds wrote:
I still think that the most likely reason (by an absolutely _enormous_
margin) is simply calibration issues with the pressure sensor.
All the dive computers I've ever seen basically consider a 1m depth to
be "surface", probably partly because you might
On 2017-08-23 06:43, Dirk Hohndel wrote:
On Aug 22, 2017, at 7:55 AM, Jef Driesen <j...@libdivecomputer.org>
wrote:
I don't understand what you gain with those comments. I mean it's just
comments. Don't you need this kind of info at runtime instead?
Yup - I simply have a tool that
On 2017-08-22 05:29, Gregory Sin wrote:
Please find testing result and files/log/screens below.
DC: iX3M DEEP (Os 4.0.26/013). Clean DC, no dives logged.
Mac:10.12.4
SUBSURF:4.6.4.737
BT: Only DC and Mouse are paired, but only
On 2017-08-21 16:51, Dirk Hohndel wrote:
BTW: I have added some annotation in the Subsurface-branch to help us
decide which dive computers to offer as choices on mobile devices
(this is in src/descriptor.c):
[...]
This basically just adds a comment at the end of every line that
follows a
On 2017-08-21 23:30, Steve wrote:
On 2017-07-13 10:11, Robert Helling wrote:
we have a user report on the forum that gets incredibly low SAC rates
for dives downloaded from a newly acquired Ratio iX3M. Looking at the
xml I see there surface pressure values of above 9bar. Does anybody
have an
Greg,
I suspect the correct port should be /dev/tty.usbserial-DN02DP66. The
others are certainly not the correct for usb-serial adapters on Mac.
In one of the screenshots, you have selected a model from the iDive
series. That won't work with a model from the iX3M series. This is one
of the
On 19-08-17 12:00, Benjamin wrote:
So, after a few trials, I'm getting the following in the subsurface.log file:
INFO: Open: name=00:13:43:0C:56:29
ERROR: Failed to open the serial port. [in ../../src/shearwater_common.c:46
(shearwater_common_open)]
This shows exactly what the problem is! A
On 2017-07-20 10:08, Jef Driesen wrote:
On 19-07-17 22:08, Linus Torvalds wrote:
Anyway, what this all builds up to is that I'd actually like to just
set the time automatically when I connect the dive computer to my
laptop (or my cellphone, for that matter - usually those end up being
On 2017-07-13 10:11, Robert Helling wrote:
we have a user report on the forum that gets incredibly low SAC rates
for dives downloaded from a newly acquired Ratio iX3M. Looking at the
xml I see there surface pressure values of above 9bar. Does anybody
have an idea how those come about? Maybe
On 2017-08-16 11:46, Anton Lundin wrote:
Step one would be some documentation. How to read and write settings
to the computer. Whats the protocol? Which settings are there and how
to
interpret the data.
The information doesn't need to be "public", but the code we write
based
on it will be. As
1 - 100 of 177 matches
Mail list logo