Re: [subsurface-4.7.8-81-gb930c39eade0] issue on displaying GF

[Chirana Gheorghita Eugeniu Theodor]

Please ignore this. It was from the general settings of the application...

On Thu, Apr 26, 2018 at 11:14 AM, Chirana Gheorghita Eugeniu Theodor <
off...@adaptcom.ro> wrote:

> I have this dive opened on the windows version of libdcNG continuous
> build 4.7.8-81-gb930c39eade0. I see the dive computer setup as GF30/70 but
> in the dive profile screen it shows GF30/75. Issue of display glitch?
> Please see attached screenshot.
>
> What is the "official"  release of the NG that is beeing maintained? Maibe
> I am using the wrong one?
>
> --
> 
> Cu stima/Best regards/Mit freundlichen Grüßen,
>
> Chirana-Gheorghita Eugeniu-Theodor
> Bucharest, Romania
>
> e-mail : off...@adaptcom.ro
> mobile: 0743 698721
> 0747 447675
> SSI diver ID: 1118289
>



-- 

Cu stima/Best regards/Mit freundlichen Grüßen,

Chirana-Gheorghita Eugeniu-Theodor
Bucharest, Romania

e-mail : off...@adaptcom.ro
mobile: 0743 698721
0747 447675
SSI diver ID: 1118289
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [subsurface-4.7.8-81-gb930c39eade0] issue on displaying GF

[Anton Lundin]

On 26 April, 2018 - Chirana Gheorghita Eugeniu Theodor wrote:

> Please ignore this. It was from the general settings of the application...
> 
> On Thu, Apr 26, 2018 at 11:14 AM, Chirana Gheorghita Eugeniu Theodor <
> off...@adaptcom.ro> wrote:
> 
> > I have this dive opened on the windows version of libdcNG continuous
> > build 4.7.8-81-gb930c39eade0. I see the dive computer setup as GF30/70 but
> > in the dive profile screen it shows GF30/75. Issue of display glitch?
> > Please see attached screenshot.
> >
> > What is the "official"  release of the NG that is beeing maintained? Maibe
> > I am using the wrong one?


Maybe we should try to clarify the gf settings ontop of the profile so
its clear that those are the settings that _subsurface_ are using, and
not the ones from the dc.


//Anton


-- 
Anton Lundin+46702-161604
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [subsurface-4.7.8-81-gb930c39eade0] issue on displaying GF

[Willem Ferguson]

On 26/04/2018 10:18, Chirana Gheorghita Eugeniu Theodor wrote:
Please ignore this. It was from the general settings of the 
application...


On Thu, Apr 26, 2018 at 11:14 AM, Chirana Gheorghita Eugeniu Theodor 
mailto:off...@adaptcom.ro>> wrote:


I have this dive opened on the windows version of libdcNG
continuous build 4.7.8-81-gb930c39eade0. I see the dive computer
setup as GF30/70 but in the dive profile screen it shows GF30/75.
Issue of display glitch? Please see attached screenshot.

What is the "official"  release of the NG that is beeing
maintained? Maibe I am using the wrong one?

I suspect here the GF on the left (30/70) is the gradient factor that 
the dive computer used. This is a function of the dive computer 
settings. The value on the right (30/75) is  the GF that Subsurface has 
been set to in the Subsurface Preferences (i.e. the displayed profile GF).

Kind regards,
willem


--
This message and attachments are subject to a disclaimer.

Please refer to 
http://upnet.up.ac.za/services/it/documentation/docs/004167.pdf 
 for
full 
details.
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [subsurface-4.7.8-81-gb930c39eade0] issue on displaying GF

[Chirana Gheorghita Eugeniu Theodor]

 Yes I figured that out , but would pose more sense if there would be no
subsurface setting in this matter. It makes no sense to setup the dive log
to display 30/75 when the dive computer reports it was using 30/70 for that
dive. Even more what if during a dive I change the GF settings on the
computer (which is possible on th eshearwater)??? what will subsurface than
display? it should display a icon in the dive profile just like a cylinder
change. Right?

On Thu, Apr 26, 2018 at 11:37 AM, Willem Ferguson <
willemfergu...@zoology.up.ac.za> wrote:

> On 26/04/2018 10:18, Chirana Gheorghita Eugeniu Theodor wrote:
>
> Please ignore this. It was from the general settings of the application...
>
> On Thu, Apr 26, 2018 at 11:14 AM, Chirana Gheorghita Eugeniu Theodor <
> off...@adaptcom.ro> wrote:
>
>> I have this dive opened on the windows version of libdcNG continuous
>> build 4.7.8-81-gb930c39eade0. I see the dive computer setup as GF30/70 but
>> in the dive profile screen it shows GF30/75. Issue of display glitch?
>> Please see attached screenshot.
>>
>> What is the "official"  release of the NG that is beeing maintained?
>> Maibe I am using the wrong one?
>>
> I suspect here the GF on the left (30/70) is the gradient factor that the
> dive computer used. This is a function of the dive computer settings. The
> value on the right (30/75) is  the GF that Subsurface has been set to in
> the Subsurface Preferences (i.e. the displayed profile GF).
> Kind regards,
> willem
>
>
> This message and attachments are subject to a disclaimer.
> Please refer to http://upnet.up.ac.za/services/it/documentation/docs/
> 004167.pdf for full details.
>



-- 

Cu stima/Best regards/Mit freundlichen Grüßen,

Chirana-Gheorghita Eugeniu-Theodor
Bucharest, Romania

e-mail : off...@adaptcom.ro
mobile: 0743 698721
0747 447675
SSI diver ID: 1118289
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [subsurface-4.7.8-81-gb930c39eade0] issue on displaying GF

[Anton Lundin]

On 26 April, 2018 - Chirana Gheorghita Eugeniu Theodor wrote:

>  Yes I figured that out , but would pose more sense if there would be no
> subsurface setting in this matter. It makes no sense to setup the dive log
> to display 30/75 when the dive computer reports it was using 30/70 for that
> dive. Even more what if during a dive I change the GF settings on the
> computer (which is possible on th eshearwater)??? what will subsurface than
> display? it should display a icon in the dive profile just like a cylinder
> change. Right?

There are two portions here. The deco calculations done by your
computer, and whats done after the fact in subsurface.

Both can be displayed in the profile.

The subsurface setting affects the deco calculations that subsurface are
doing, on the data (depth / time) from your dc.

If you're to change your deco settings while diving, that will just
affect the deco data generated by your computer.


This way, you can compare dive computers deco algorithms with the
subsurface implementation.


//Anton


-- 
Anton Lundin+46702-161604
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Fwd: Re: [subsurface-4.7.8-81-gb930c39eade0] issue on displaying GF

[Willem Ferguson]

On 26/04/2018 10:53, Chirana Gheorghita Eugeniu Theodor wrote:
Yes I figured that out , but would pose more sense if there would be 
no subsurface setting in this matter. It makes no sense to setup the 
dive log to display 30/75 when the dive computer reports it was using 
30/70 for that dive. Even more what if during a dive I change the GF 
settings on the computer (which is possible on th eshearwater)??? what 
will subsurface than display? it should display a icon in the dive 
profile just like a cylinder change. Right?


On Thu, Apr 26, 2018 at 11:37 AM, Willem Ferguson 
> wrote:


On 26/04/2018 10:18, Chirana Gheorghita Eugeniu Theodor wrote:

Please ignore this. It was from the general settings of the
application...

On Thu, Apr 26, 2018 at 11:14 AM, Chirana Gheorghita Eugeniu
Theodor mailto:off...@adaptcom.ro>> wrote:

I have this dive opened on the windows version of libdcNG
continuous build 4.7.8-81-gb930c39eade0. I see the dive
computer setup as GF30/70 but in the dive profile screen it
shows GF30/75. Issue of display glitch? Please see attached
screenshot.

What is the "official"  release of the NG that is beeing
maintained? Maibe I am using the wrong one?


I suspect here the GF on the left (30/70) is the gradient factor
that the dive computer used. This is a function of the dive
computer settings. The value on the right (30/75) is  the GF that
Subsurface has been set to in the Subsurface Preferences (i.e. the
displayed profile GF).
Kind regards,
willem



I am not sure that this is generally doable.

Firstly, only a handful dc's record GF. Most do not. How should one deal 
with the dc's that do not record GF? How should one provide for the 
multiple ways in which different dive computers determine conservatism? 
Most dc's use conservatism levels, not GF.


Secondly, how is GF recorded in the Subsurface dive log? This is a 
function of the way libdivecomputer extracts data from the dive 
computer. I am not convinced that libdivecomputer has the ability to 
capture on-the-fly changes in GF during a dive, so your suggestion is 
probably not possible anyway. My Uwatec automatically adjusts the 
conservatism if the diver oversteps the deco requirements, but this is 
not captured by libdivecomputer. And I do not care too much about that.  
If this is a critical factor for you, then consider a dc like Shearwater 
that provides its own set of dive ceilings for each dive, reflecting the 
GF settings of the dc, including on-the-fly changes in GF. 
Libdivecomputer captures that perfectly.


Thirdly, the displayed GF in the Subsurface dive profile is a broad and 
general yard stick to evaluate the deco during the dive. Is it really 
crucial to modify the ceiling in a detailed way to reflect GF changes 
during the dive? All the a diver wants to do is to get a reasonable 
*overall* impression of how well the deco went in terms of tissue 
compartment gas pressures.


Kind regards,
willem


--
This message and attachments are subject to a disclaimer.

Please refer to 
http://upnet.up.ac.za/services/it/documentation/docs/004167.pdf 
 for
full 
details.
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Any brave dive computer download testers out there?

[Pedro Neves]

Hi all:

I've just tested downloading from my Scubapro G2 using the latest master 
built with libdivecomputer v0.7.0-devel-Subsurface-NG. It failed the 
first time, but worked fine at the second attempt.


Now I'd like to test downloading from G2 using USB.

@ Linus: my sytem (Arch Linux) detects the G2 :

usb 1-10: new full-speed USB device number 6 using xhci_hcd
[ 3494.833727] usb 1-10: New USB device found, idVendor=2e6c, idProduct=3201
[ 3494.833730] usb 1-10: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3

[ 3494.833732] usb 1-10: Product: G2 dive computer
[ 3494.833733] usb 1-10: Manufacturer: Uwatec AG
[ 3494.833734] usb 1-10: SerialNumber: 
[ 3494.835381] hid-generic 0003:2E6C:3201.0004: hiddev2,hidraw3: USB HID 
v1.00 Device [Uwatec AG G2 dive computer] on usb-:00:14.0-10/input0


But fails to add an interface for it. Have you used the USB connection 
to download data from your G2? Any hints?


Cheers:

Pedro
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [subsurface-4.7.8-81-gb930c39eade0] issue on displaying GF

[Dirk Hohndel]

> On Apr 26, 2018, at 1:53 AM, Chirana Gheorghita Eugeniu Theodor 
>  wrote:
> 
> Yes I figured that out , but would pose more sense if there would be no 
> subsurface setting in this matter. It makes no sense to setup the dive log to 
> display 30/75 when the dive computer reports it was using 30/70 for that 
> dive. Even more what if during a dive I change the GF settings on the 
> computer (which is possible on th eshearwater)??? what will subsurface than 
> display? it should display a icon in the dive profile just like a cylinder 
> change. Right?

You gave the reason why there is a Subsurface setting yourself.
Most dive computers don't tell you at all what GF settings were used (and many 
don't use Bühlmann, anyway). And the Shearwater doesn't tell you if and when GF 
was switched. Subsurface calculates its own deco ceiling and visualizes that in 
addition to the dive computer reported ceiling. And the Subsurface GF settings 
control THAT calculated ceiling.

/D

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [subsurface-4.7.8-81-gb930c39eade0] issue on displaying GF

[Dirk Hohndel]

> On Apr 26, 2018, at 1:14 AM, Chirana Gheorghita Eugeniu Theodor 
>  wrote:
> 
> What is the "official"  release of the NG that is beeing maintained? Maibe I 
> am using the wrong one?

I will delete all of the NG builds as all of that code has now been merged into 
master.

/D

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Any brave dive computer download testers out there?

[Jef Driesen]

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 Linux laptop with working BLE...)


Note that the magic channel/port number thing is Linux 
desktop-specific:


  #if defined(Q_OS_LINUX) && !defined(Q_OS_ANDROID)

And it was literally the Petrel 2 that triggered that "try channel 5".

I have no idea how that is supposed to work, or what the crazy rules
about rfcomm ports even -are-. I'm just looking at the code, and going
"eww".

Also note that on Linux and Windows, we could just use the
libdivecomputer bluetooth backend that just uses the raw socket.

Also, Jef just uses port 0 for everything.

So the whole "port/channel" thing may be entirely pointless.


In the libdivecomputer rfcomm implementation, port 0 means 
auto-detection. On linux it does an SDP discovery internally to find the 
correct rfcomm port number, and on Windows it uses the rfcomm uuid 
instead of the port number. That way, it should always just work. And on 
the hardware I tested, it does indeed.


I also don't know the exact details on how these port numbers are 
assigned. I guess it depends on the dive computer firmware and/or its 
bluetooth stack. The valid range for rfcomm ports is 1-30 if I remember 
correctly.


The Petrel is certainly not the only one which is using a different port 
number. I'm currently testing the divecomputer.eu and it seems to use 
port 6.


Jef
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Any brave dive computer download testers out there?

[Linus Torvalds]

On Thu, Apr 26, 2018 at 2:29 AM, Pedro Neves  wrote:
>
> @ Linus: my sytem (Arch Linux) detects the G2 :
>
> usb 1-10: new full-speed USB device number 6 using xhci_hcd
> [ 3494.833727] usb 1-10: New USB device found, idVendor=2e6c, idProduct=3201
> [ 3494.833730] usb 1-10: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [ 3494.833732] usb 1-10: Product: G2 dive computer
> [ 3494.833733] usb 1-10: Manufacturer: Uwatec AG
> [ 3494.833734] usb 1-10: SerialNumber: 
> [ 3494.835381] hid-generic 0003:2E6C:3201.0004: hiddev2,hidraw3: USB HID
> v1.00 Device [Uwatec AG G2 dive computer] on usb-:00:14.0-10/input0
>
> But fails to add an interface for it.

All you need is the raw usb device, something like

   /dev/bus/usb/001/010

and you need to have access rights to it.

> Have you used the USB connection to
> download data from your G2? Any hints?

Yup, it "JustWorks(tm)" for me.

But you need to have an udev rule to make sure you can access it. Something like

   SUBSYSTEM=="usb",ATTR{idVendor}=="2e6c",ATTR{idProduct}=="3201",MODE="0666"

in a udev rule file. I'm not sure where Arch Linux keeps its udev
rules, but usually it's one (or both) of

/etc/udev/rules.d
/usr/lib/udev/rules.d/

and after you've created your own file (call it "91-Scubapro-G2.udev"
or something, you need to make sure udev knows about the new rules (no
need to reboot, do "udevadm control --reload").

Oh. Or just do some googling. This looks like the proper docs:

https://wiki.archlinux.org/index.php/udev

and obviously you can do better than MODE="0666" that just gives
everybody access. Some distros have a "plugdev" group that console
users get added to, but you can do anything like just making you the
owner (USER="nevesdiver" in the udev rule) etc.

 Linus
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Any brave dive computer download testers out there?

[Linus Torvalds]

On Thu, Apr 26, 2018 at 7:44 AM, Jef Driesen  wrote:
>
> I also don't know the exact details on how these port numbers are assigned.
> I guess it depends on the dive computer firmware and/or its bluetooth stack.
> The valid range for rfcomm ports is 1-30 if I remember correctly.
>
> The Petrel is certainly not the only one which is using a different port
> number. I'm currently testing the divecomputer.eu and it seems to use port
> 6.

Ok, sounds like we should use port 0 too.

And that really makes most of the special cases just go away. So a
patch like the attached.

Dirk? Anybody with an rfcomm device? Willing to test the attached
"remove all the crazy crud" patch?

 Linus
 core/qtserialbluetooth.cpp | 32 ++--
 1 file changed, 2 insertions(+), 30 deletions(-)

diff --git a/core/qtserialbluetooth.cpp b/core/qtserialbluetooth.cpp
index bc274dbd9..13f4ee8c5 100644
--- a/core/qtserialbluetooth.cpp
+++ b/core/qtserialbluetooth.cpp
@@ -113,34 +113,6 @@ static dc_status_t qt_serial_open(qt_serial_t **io, dc_context_t *context, const
 	timer.setSingleShot(true);
 	loop.connect(&timer, SIGNAL(timeout()), SLOT(quit()));
 
-#if defined(Q_OS_LINUX) && !defined(Q_OS_ANDROID)
-	// First try to connect on RFCOMM channel 1. This is the default channel for most devices
-	QBluetoothAddress remoteDeviceAddress(devaddr);
-	serial_port->socket->connectToService(remoteDeviceAddress, 1, QIODevice::ReadWrite | QIODevice::Unbuffered);
-	timer.start(msec);
-	loop.exec();
-
-	if (serial_port->socket->state() == QBluetoothSocket::ConnectingState) {
-		// It seems that the connection on channel 1 took more than expected. Wait another 15 seconds
-		qDebug() << "The connection on RFCOMM channel number 1 took more than expected. Wait another 15 seconds.";
-		timer.start(3 * msec);
-		loop.exec();
-	} else if (serial_port->socket->state() == QBluetoothSocket::UnconnectedState) {
-		// Try to connect on channel number 5. Maybe this is a Shearwater Petrel2 device.
-		qDebug() << "Connection on channel 1 failed. Trying on channel number 5.";
-		serial_port->socket->connectToService(remoteDeviceAddress, 5, QIODevice::ReadWrite | QIODevice::Unbuffered);
-		timer.start(msec);
-		loop.exec();
-
-		if (serial_port->socket->state() == QBluetoothSocket::ConnectingState) {
-			// It seems that the connection on channel 5 took more than expected. Wait another 15 seconds
-			qDebug() << "The connection on RFCOMM channel number 5 took more than expected. Wait another 15 seconds.";
-			timer.start(3 * msec);
-			loop.exec();
-		}
-	}
-#elif defined(Q_OS_ANDROID) || (QT_VERSION >= 0x050500 && defined(Q_OS_MAC))
-	// Try to connect to the device using the uuid of the Serial Port Profile service
 	QBluetoothAddress remoteDeviceAddress(devaddr);
 #if defined(Q_OS_ANDROID)
 	QBluetoothUuid uuid = QBluetoothUuid(QUuid("{1101--1000-8000-00805f9b34fb}"));
@@ -148,7 +120,7 @@ static dc_status_t qt_serial_open(qt_serial_t **io, dc_context_t *context, const
 	serial_port->socket->setPreferredSecurityFlags(QBluetooth::NoSecurity);
 	serial_port->socket->connectToService(remoteDeviceAddress, uuid, QIODevice::ReadWrite | QIODevice::Unbuffered);
 #else
-	serial_port->socket->connectToService(remoteDeviceAddress, 1, QIODevice::ReadWrite | QIODevice::Unbuffered);
+	serial_port->socket->connectToService(remoteDeviceAddress, QIODevice::ReadWrite | QIODevice::Unbuffered);
 #endif
 	timer.start(msec);
 	loop.exec();
@@ -160,7 +132,7 @@ static dc_status_t qt_serial_open(qt_serial_t **io, dc_context_t *context, const
 		timer.start(4 * msec);
 		loop.exec();
 	}
-#endif
+
 	if (serial_port->socket->state() != QBluetoothSocket::ConnectedState) {
 
 		// Get the latest error and try to match it with one from libdivecomputer
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Averages and time zone

[tormento]

Launching latest NG version, a nice poll asked me what I'd like to see.

I'd like to see average depth and average heartbeat, plus a local time zone
correction.

Now in Italy we are in UTC+2 (UTC+1+daylight saving time) and Subsurface
gets an error of +1 hour on my Windows 10 with italian regional settings.
Scubapro G2 is set as UTC (+2 now), to get correct time when travelling
around the world.
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

G2 skin temperature and work load

[tormento]

 G2 can output (I can see from LogTrak) skin temperature and work load.

Is it possible to import them or is there a limitation from libdive?
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Averages and time zone

[Linus Torvalds]

On Thu, Apr 26, 2018 at 9:42 AM, tormento  wrote:
>
> I'd like to see average depth and average heartbeat, plus a local time zone
> correction.

Average depth is already there, it shows up as a "average until this
point" line in the graph if you have it enabled (because some tech
divers find that useful).

Average heartbeat somebody would have to just implement. Nobody has
asked for it.

Local time zone you need to either

 - fix your computer use to use local time when diving (that's what
everybody else does, and most dive computers don't support anything
*but* that)

 - edit the time by hand after the download.

We've discussed having a per-trip timezeone setting, but nobody really
wants the confusion or room for error.

Linus
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: G2 skin temperature and work load

[Linus Torvalds]

On Thu, Apr 26, 2018 at 9:43 AM, tormento  wrote:
> G2 can output (I can see from LogTrak) skin temperature and work load.
>
> Is it possible to import them or is there a limitation from libdive?

libdivecomputer doesn't parse it, and we don't really know where the
data is hidden. It might be largely synthetic too (ie LogTrak may just
calculate its own "workload" estimate it based on other imput like
SAC-rate, temperature, heartrate etc).

So it *might* be a "small matter of adding parsing to libdivecomputer"
and teaching subsurface about a new field, or it might be a lot of
black magic.

Linus
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: G2 skin temperature and work load

[tormento]

Got it.

Il giorno gio 26 apr 2018 alle ore 19:22 Linus Torvalds <
torva...@linux-foundation.org> ha scritto:

> On Thu, Apr 26, 2018 at 9:43 AM, tormento  wrote:
> > G2 can output (I can see from LogTrak) skin temperature and work load.
> >
> > Is it possible to import them or is there a limitation from libdive?
>
> libdivecomputer doesn't parse it, and we don't really know where the
> data is hidden. It might be largely synthetic too (ie LogTrak may just
> calculate its own "workload" estimate it based on other imput like
> SAC-rate, temperature, heartrate etc).
>
> So it *might* be a "small matter of adding parsing to libdivecomputer"
> and teaching subsurface about a new field, or it might be a lot of
> black magic.
>
> Linus
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Any brave dive computer download testers out there?

[Pedro Neves]

On 26-04-2018 17:08, Linus Torvalds wrote:

Oh. Or just do some googling. This looks like the proper docs:

 https://wiki.archlinux.org/index.php/udev

and obviously you can do better than MODE="0666" that just gives
everybody access. Some distros have a "plugdev" group that console
users get added to, but you can do anything like just making you the
owner (USER="nevesdiver" in the udev rule) etc.


Linus:

Thanks for the detailed explanations. I created the rule and all is good.
The usb download is so much faster than the bluetooth...

Cheers:

Pedro

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface