Re: Group assign tank sizes, desktop

2018-03-12 Thread Miika Turkia 
On Fri, Mar 2, 2018 at 11:18 PM, James Cialdea  wrote:

> I came back from a trip where we used a few different nitrox mixes, but
> all the same tank size. I imported all the dive profiles from my Suunto
> vyper air.  Then, I selected all the dives and set the cylinder size in one
> mutli-dive-edit operation.
>
> I expected the cylinder size to be set on all dives and no other updates
> to happen. Instead, all dives were assigned the gas mix from the first
> dive, and all were assigned the same, expected, cylinder. The start and end
> pressure, which is on the same line when editing cylinder or gas mix, were
> unchanged, as expected.
>
> Is this behavior of updating the gas mix on all dives when only the
> cylinder is changed intentional?
>

Did you modify the cylinder size or did you copy-paste the size? If you
change the size, then it should be changed for all the selected dives with
no changes in the other information. If you paste cylinder information,
that will change other info than the size as well.

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

RFC: PSCR dive plots: Part 1

2018-03-12 Thread Willem Ferguson 
After Anton's current PR dealing with PSCR code has been pulled, I plan, 
as a SECOND step, to incorporate (again) the display of OC_pO2 with the 
PSCR pO2 graph. OC-equivalent pO2 has a role very similar to setpoint 
for CCR dives. It allows the evaluation of the pO2 drop over the gas 
injector, probably the most important gas management activity for PSCR. 
Taking into account Anton's strong preference that the setpoint variable 
should not be abused for PSCR dive profiles, my plan would be:


1) Create a new PartialPressureGasitem element, starting with the qt 
diveplotmodel and using createPPgas() in profilewidget2.cpp


2) Contol its display by setting its setVisible attribute.

Does this sound like a useful approach at all? In this way the setpoint 
variable is not involved at all.


The THIRD step would then be to implement bailout events and display gas 
pressures as a function of whether the diver is on the loop or on 
bailout. This would probably affect the CCR code as well. There is a 
separate thread (part 2) on this topic on this mail list.


Does this approach appear at least semi-useful?

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

RFC: PSCR dive plots: Part 2.

2018-03-12 Thread Willem Ferguson 
I am slowly working towards providing for bailout in the dive profile 
display. There are a few decisions that need to be made and I would 
appreciate any comment.


1) Recording bailout events by dive computers:

On Shearwater, each dive sample has a boolean that indicates whether the 
sample was during Loop or during Bailout. At the moment this boolean is 
not exposed by libdivecomputer, but Jef and myself are having 
discussions about making this information available in the API. I only 
have access to Shearwater equipment. According to Jef the 
Ratio/DiveSystem and DiveRite Nitek Q have similar systems of recording 
bailout, while H-W records discete events. Obviously, if one implements 
bailout, one would like to do it in a way that is as compatible with 
what most dive computers do. Anyone using other hardware for ccr/pscr, 
please comment on how your computer handles bailout events while 
logging? Given the system for Shearwater, Ratio, etc, it is unavoidable 
that an additional byte would be needed in the sample structure.


2) Showing bailout events in the Subsurface dive profile. This would 
have two aspects.


    a) Indicating bailout with an icon on the dive profile. The 
inclusion of appropriate events is by far the easiest way to implement 
this. Currently the dive events are closely tied to the libdivecomputer 
events, so this is somewhat limiting.


    b) Adapting the gas partial pressure graphs to reflect what the 
diver breathes during bailout. When rendering the dive by creating a 
plot_info structure for each sample, the easiest mechanism of 
incorporating bailout would be to use the Shearwater approach: have a 
byte indicating Loop or Bailout and perform the appropriate calculation 
for gas partial pressures. Alternatively, it may be possible to 
reference the linked list of existing events, find the next bailout 
event and plot the pO2 depending on the type of bailout event (i.e. 
Bailout or OC->Loop). But this would incur significantly more 
computational overhead since this lookup will be needed for each 
plot_info on the dive profile.


What worries me about the above is that it uses a dual system (events as 
well as sample-wise boolean values).


Is this approach too complex?

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

mail hickup

2018-03-12 Thread Dirk Hohndel 
The mailing list deamon on my server got stuck about 10 days ago - and with all 
the activity via GitHub it appears no one noticed... until yesterday I sent out 
an announcement of the new Android Beta and then realized that it hadn't come 
back...

So, please accept my apologies, enjoy ten days worth of email, and next time 
you send something to the mailing list and you don't get it back in your inbox 
within a few minutes, please drop me a line so I can look into it :-)

Thanks

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

New Android beta

2018-03-12 Thread Dirk Hohndel 

We now have a version of the map widget for the mobile app, thanks to Lubomir.

I pushed an Android update to the beta channel and would appreciate testing and 
feedback.

Thanks

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

Displaying OC pO2 in pscr dives

2018-03-12 Thread Willem Ferguson 
After Anton's current PR dealing with PSCR code has been pulled, I plan,
as a SECOND step, to incorporate (again) the display of OC_pO2 with the
PSCR pO2 graph. OC-equivalent pO2 in PSCR has a role very similar to
setpoint
for CCR dives. It allows the evaluation of the pO2 drop over the
mouthpiece, probably the most important gas management activity for
PSCR. Taking into account Anton's strong preference that the setpoint
variable should not be 'abused' for PSCR dive profiles, I will then not
use the setpoint variable at all. So my plan would be:

1) Create a new PartialPressureGasitem element, starting with the qt
diveplotmodel and using createPPgas() in profilewidget2.cpp

2) Contol its display by setting its setVisible attribute.

Does this sound like a useful approach at all? In this way the setpoint
vaiable is not involved at all.

The THIRD step would then be to implement bailout events and display gas
pressures as a function of whether the diver is on the loop or on
bailout. This would probably affect the CCR code as well. There is a
separate thread on this topic on this mail list.

Does this approach appear at least semi-useful?

Kind regards,

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

Re: map-widget-mobile WIP

2018-03-12 Thread Lubomir I. Ivanov 
On 8 March 2018 at 22:55, Lubomir I. Ivanov  wrote:
> On 5 March 2018 at 00:37, Lubomir I. Ivanov  wrote:
>> got the map widget working on the mobile version (testing on Desktop):
>> 
>> (the whole OS crashed at some point while running Google Chrome + this)
>>
>> WIP branch:
>> https://github.com/neolit123/subsurface/tree/map-mobile
>>
>
> working POC:
> https://github.com/Subsurface-divelog/subsurface/pull/1156
>
> waiting on feedback and reviews.
> also, if anyone has ideas how to package the google maps plugin for
> mobile, please drop a comment.
>

APK for testing:
https://github.com/Subsurface-divelog/subsurface/pull/1156#issuecomment-372057243

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

Showing OC-equivalent pO2 on PSCR dive profiles.

2018-03-12 Thread Willem Ferguson 


After Anton's current PR dealing with PSCR code has been pulled, I plan, 
as a SECOND step, to incorporate (again) the display of OC_pO2 with the 
PSCR pO2 graph. OC-equivalent pO2 has a role very similar to setpoint 
for CCR dives. It allows the evaluation of the pO2 drop over the 
mouthpiece, probably the most important gas management activity for 
PSCR. Taking into account Anton's strong preference that the setpoint 
variable should not be 'abused' for PSCR dive profiles, I will then not 
use the setpoint variable at all. So my plan would be:


1) Create a new PartialPressureGasitem element, starting with the qt 
diveplotmodel and using createPPgas() in profilewidget2.cpp


2) Contol its display by setting its setVisible attribute.

Does this sound like a useful approach at all? In this way the setpoint 
vaiable is not involved at all.


The THIRD step would then be to implement bailout events and display gas 
pressures as a function of whether the diver is on the loop or on 
bailout. This would probably affect the CCR code as well. There is a 
separate thread on this topic on this mail list.


Does this approach appear at least semi-useful?

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 Cloud access through authenticated proxy on Windows

2018-03-12 Thread Davide DB 
On 2 March 2018 at 20:01, Dirk Hohndel  wrote:
> Yeah, the subject line shows how narrow this is... I think Davide was the one 
> who kept running into this problem.
>
> We had a bug that prevented us from using a proxy on Windows when that proxy 
> required authentication.
>
> Davide (or anyone else who has the ability to test this), any chance that you 
> could test this installer?
>
> https://github.com/Subsurface-divelog/subsurface/releases/download/continuous-windowsProxy/subsurface-4.7.7-69-gf144add732d5.exe
>

Hi DIrk,

I feel guilty for this :)

Anyway I tried it and still not quite there.

Short version:

Cloud connection OK but no fetch: Operation timeout.
Maps work anyway so the map plugin is successfully going through the proxy.

Long version, see the console logs attached:

C:\Program Files (x86)\Subsurface>subsurface.exe -v

C:\Program Files (x86)\Subsurface>
Subsurface v4.7.7-69-gf144add732d5,
built with libdivecomputer v0.7.0-devel-Subsurface-branch
(7444cca876cf1637fd7c3d4ad1e48145b215aed8)
built with Qt Version 5.9.2, runtime from Qt Version 5.9.2
built with libgit2 0.26.0
validateGL(): created OpenGLContext.
validateGL(): obtained QOpenGLFunctions.
validateGL(): detected OpenGL version 3.3.
added supported DC:  Suunto   Solution

SNIP

Plugins Directory:  QDir( "C:/Program Files (x86)/Subsurface/plugins"
, nameFilters = { "*" },  QDir::SortFlags( Name | IgnoreCase ) ,
QDir::Filters( Dirs|File
cloud URL set as
"https://cloud.subsurface-divelog.org//git/dbdav...@gmail.com[dbdav...@gmail.com];
loading dive data from
("https://cloud.subsurface-divelog.org//git/dbdav...@gmail.com[dbdav...@gmail.com];)
git storage: Synchronising data file
git storage: update local repo
sync with remote
https://cloud.subsurface-divelog.org//git/dbdav...@gmail.com[dbdav...@gmail.com]
git storage: Sync with cloud storage
set proxy to "http://someuserpassword@someproxy:8080;
Cloud storage: checking connection to cloud server
Checking cloud connection...
git storage: fetch remote
git storage: Successful cloud connection, fetch remote
remote fetch failed (failed to send request: Timeout dell'operazione
)
git storage: Done syncing with cloud storage
git storage: Load dives from local cache
git storage: Successfully opened dive data
Set the current dive site: 591880146
Set the current dive site: 591880146

File locations:

cloud URL set as
"https://cloud.subsurface-divelog.org//git/dbdav...@gmail.com[dbdav...@gmail.com];
Local git storage:
C:\Users\someuser\AppData\Roaming\Subsurface/cloudstorage/29fc20f013e9f1fb
Cloud URL: 
https://cloud.subsurface-divelog.org//git/dbdav...@gmail.com[dbdav...@gmail.com]
Image hashes: C:\Users\someuser\AppData\Roaming\Subsurface/hashes
Local picture directory:
C:\Users\someuser\AppData\Roaming\Subsurface/picturedata/

Once I click on "File > Take cloud online" I get:


QNetworkAccessCache::addEntry: overriding active cache entry
'auth:proxy-http://someuser@someproxy:8080'
QNetworkAccessCache::addEntry: overriding active cache entry
'auth:proxy-http://someuser@someproxy:8080'
QNetworkAccessCache::addEntry: overriding active cache entry
'auth:proxy-http://someuser@someproxy:8080'
QNetworkAccessCache::addEntry: overriding active cache entry
'auth:proxy-http://someuser@someproxy:8080'
QNetworkAccessCache::addEntry: overriding active cache entry
'auth:proxy-http://someuser@someproxy:8080'
QNetworkAccessCache::addEntry: overriding active cache entry
'auth:proxy-http://someuser@someproxy:8080'
QNetworkReplyImplPrivate::error: Internal problem, this method must
only be called once.
QNetworkAccessCache::addEntry: overriding active cache entry
'auth:proxy-http://someuser@someproxy:8080'
QNetworkAccessCache::addEntry: overriding active cache entry
'auth:proxy-http://someuser@someproxy:8080'
QNetworkReplyImplPrivate::error: Internal problem, this method must
only be called once.
cloud URL set as
"https://cloud.subsurface-divelog.org//git/dbdav...@gmail.com[dbdav...@gmail.com];
Opening cloud storage from:
"https://cloud.subsurface-divelog.org//git/dbdav...@gmail.com[dbdav...@gmail.com];
Set the current dive site: 0
git storage: Synchronising data file
git storage: update local repo
sync with remote
https://cloud.subsurface-divelog.org//git/dbdav...@gmail.com[dbdav...@gmail.com]
git storage: Sync with cloud storage
set proxy to "http://someuserpassword@someproxy:8080;
Cloud storage: checking connection to cloud server
Checking cloud connection...
git storage: fetch remote
git storage: Successful cloud connection, fetch remote
remote fetch failed (failed to send request: Timeout dell'operazione
)
git storage: Done syncing with cloud storage
git storage: Load dives from local cache
git storage: Successfully opened dive data
Set the current dive site: 591880146
Set the current dive site: 591880146


-- 
Davide
https://vimeo.com/bocio/videos
___
subsurface mailing list
subsurface@subsurface-divelog.org

Fwd: Showing OC-equivalent pO2 on PSCR dive profiles.

2018-03-12 Thread Willem Ferguson 




After Anton's current PR dealing with PSCR code has been pulled, I plan,
as a SECOND step, to incorporate (again) the display of OC_pO2 with the
PSCR pO2 graph. OC-equivalent pO2 in PSCR has a role very similar to setpoint
for CCR dives. It allows the evaluation of the pO2 drop over the
mouthpiece, probably the most important gas management activity for
PSCR. Taking into account Anton's strong preference that the setpoint
variable should not be 'abused' for PSCR dive profiles, I will then not
use the setpoint variable at all. So my plan would be:

1) Create a new PartialPressureGasitem element, starting with the qt
diveplotmodel and using createPPgas() in profilewidget2.cpp

2) Contol its display by setting its setVisible attribute.

Does this sound like a useful approach at all? In this way the setpoint
vaiable is not involved at all.

The THIRD step would then be to implement bailout events and display gas
pressures as a function of whether the diver is on the loop or on
bailout. This would probably affect the CCR code as well. There is a
separate thread on this topic on this mail list.

Does this approach appear at least semi-useful?

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

Providing for ccr/pscr bailout - logging and interactions with libdivecomputer.

2018-03-12 Thread Willem Ferguson 
I am slowly working towards providing for bailout in the dive profile 
display. There are a few decisions that need to be made and I would 
appreciate any comment.


1) The recording of bailout events by dive computers. On Shearwater, 
each dive sample has a boolean that indicates whether the sample was 
during Loop or during Bailout. At the moment this boolean is not exposed 
by libdivecomputer, but Jef and myself are having discussions about 
making this information available in the API. I only have access to 
Shearwater equipment. How do other dive computers, e.g. H-W, record 
bailout events? Obviously, if one implements bailout, one would like to 
do it in a way that is as compatible with what most dive computers do. 
Anyone using other hardware for ccr/pscr, please comment on how your 
computer handles bailout events while logging?


2) Showing bailout events in the Subsurface dive profile. This would 
have two aspects.


    a) Indicating bailout with an icon on the dive profile. The 
inclusion of appropriate events is by far the easiest way to implement 
this. Currently the dive events are very closely tied to the 
libdivecomputer events, so this is somewhat limiting.


    b) Adapting the gas partial pressure graphs to reflect what the 
diver breathes during bailout. When rendering the dive by creating a 
plot_info structure for each sample, the easiest mechanism of 
incorporating bailout would be to use the Shearwater approach: have a 
byte indicating Loop or Bailout and perform the appropriate calculation 
for gas partial pressures.


What worries me about the above is that it uses a dual system of events 
as well as sample-wise boolean values. In the case of Shearwater, the 
events would be created from the sample-wise boolean values. If the 
events are entered by hand, then the sample-wise bolean values would be 
created using the events.


Is this approach too complex?

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: map-widget-mobile WIP

2018-03-12 Thread Lubomir I. Ivanov 
On 5 March 2018 at 00:37, Lubomir I. Ivanov  wrote:
> got the map widget working on the mobile version (testing on Desktop):
> 
> (the whole OS crashed at some point while running Google Chrome + this)
>
> WIP branch:
> https://github.com/neolit123/subsurface/tree/map-mobile
>

working POC:
https://github.com/Subsurface-divelog/subsurface/pull/1156

waiting on feedback and reviews.
also, if anyone has ideas how to package the google maps plugin for
mobile, please drop a comment.

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

Re: who has BLE dive computers - which one, which OSs can you test

2018-03-12 Thread Josenivaldo Benito Junior 
I don't know if still needed but:

Perdix AI
Linux Mint
Windows 10 (not VM)
Android (currently Samsung S7, but have access to Moto X Play and other
samsung models)

Thanks


--
*Josenivaldo Benito Jr.*
*PU2LBD*


On Thu, Sep 28, 2017 at 11:40 PM, Steve 
wrote:

>
> Shearwater Petrel 2 dual stack
> Heinrich Weikamp OSTC3+ dual stack
>
> Windows 10
> Fedora Linux
> Android
>
> Steve
>
>
>
>
> Hi there,
>
> I asked almost the same question before, but only a few people answered...
>
> I'm trying to figure out how much coverage we have for testing BLE
> support, but at this point I can't really tell how many of us have access
> to such devices (and which OSs they might be testing on).
>
> So, could you please respond and tell me
>
> - which BLE dive computer do you have access to
>   (So far only support Suunto EON Steel, Heinrich Weikamp OSTC 4,
>   Shearwater Perdix AI (and dual stack Perdix / Petrel 2), and Scubapro G2
> --
>   if you have others, I'd love to know as well)
>
> - which OSs can you test on
>
>
> I'll start:
>
> Suunto EON Steel
> Shearwater Perdix AI
> Shearwater Petrel 2 dual stack
>
> Mac
> Linux (only Fedora on a physical machine, BLE doesn't work in a VM)
> Windows (currently an ancient netbook with BLE dongle) Android iOS
>
> Thanks
>
> /D
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Perdix AI won't download

2018-03-12 Thread Josenivaldo Benito Junior 
Hi guys,

I am trying to download from a Perdix AI without success, same message as
Malcolm's except that I have version 4.7.7 installed on Linux and Android
(2.0.3(4.7.7.52)).

On Android I can use Shearwater Cloud (terrible interface) if I do not pair
Perdix AI, however, subsurface only find perdix if I try to pair it first
but fails to communicate with Perdix (same happen on Linux, subsurface see
perdix as "unauthorized" before pair I won't let me save, once I pair it,
subsurface let's me save and download but fail with similar message as
Malcom's).

Any procedure I might forgot?

Thanks


--
*Josenivaldo Benito Jr.*
*PU2LBD*


On Tue, Feb 20, 2018 at 12:00 PM, Aaron Scheiner 
wrote:

> I do the same, it's fantastic.
>
> Aaron
>
> On 20 Feb 2018 16:42, "Long, Martin"  wrote:
>
> Malcolm,
>
> Your best bet is to download it using Subsurface mobile, then sync it
> through to the desktop using your cloud account. I do this using both my
> Perdix AI and the Petrel 2 on my rebreather. Works a treat.
>
> Martin
>
> On 13 February 2018 at 18:43, Dirk Hohndel  wrote:
>
>> Correct. We currently do not support Bluetooth LE devices on Windows.
>> This is documented in the manual.
>>
>> /D
>>
>> On Feb 10, 2018, at 6:14 PM, Malcolm  wrote:
>>
>> Hi
>> Perdix ai won’t download to subsurface, windows 10
>>
>> Regards
>> Malcolm Griffin
>>
>>
>> ___
>> subsurface mailing list
>> subsurface@subsurface-divelog.org
>> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>>
>>
>>
>> ___
>> subsurface mailing list
>> subsurface@subsurface-divelog.org
>> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>>
>>
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
>
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

snprintf cascades

2018-03-12 Thread Berthold Stoeger 
Dear all,

In the files core/plannernotes.c, core/statistics.c and core/uemis-
downloader.c, we have code of the kind
  snprintf(buffer + len, sz_buffer - len, ...);

I think this is wrong because the second argument to snprintf is size_t, i.e. 
unsigned. For len > sz_buffer, this will happily write past the end of the 
buffer.

Ad-hoc, I see three rather easy to implement fixes:

1)

int sane_snprintf(char *str, int size, const char *fmt, ...)
{
va_list ap;
va_start(ap, fmt);
int res = vsnprintf(str, max(0, size), fmt, ap);
va_end(ap);
return res;
}

2)

Use struct membuffer and put_format().

3)

Change to QString:
res += QString::asprintf(...);

Concerning the amount of work, I'd say it's 1 < 2 < 3 (from least to most work 
needed). Personally, I feel that nevertheless 3 would be the best option, even 
though I dislike QString (COW, UTF-16). This would remove back-and-forth 
conversion QString -> C-string -> QString and wouldn't change the C-logic at 
all. Moreover, for my tastes, it's the easiest-to-read version.

What do you think?

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

Aladin square with Subsurface-mobile

2018-03-12 Thread vavincavent 
Hi all,

I've try to connect my Aladin square divecomputer to Subsurface-mobile, 
but ... problem.

Divecomputer : Aladin square
Smartphone : Nexus 5X (OTG ok)
Subsurface-mobile : version 2.0.3 (4.7.7.52)

Can someone help me?

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

Re: Subsurface configure DC feature and OSTC Plus

2018-03-12 Thread Anton Lundin 
On 03 March, 2018 - Stefan Fuchs wrote:

> Hallo Matthias, hello Anton,
> 
> 
> Am 03.03.2018 um 16:24 schrieb Matthias Heinrichs:
> > Hi Stefan,
> >
> > The OSTC Plus can be seen as an OSTC3 or OSTC2 with Bluetooth. There
> > are only three types of current OSTC: OSTC with hwOS Tec and USB port
> > -> FTDI drivers, OSTC with Bluetooth and hwOS Tec and OSTC with
> > Bluetooth and hwOS Sport.
> >

As far as I've know, there is no difference in the communication, if its
done over bluetooth or ftdi-usb-serial. In subsurface case its all
transparent. Also, as far as i've know and from previous discussions
with Matthias and Co, hwOS Tec and hwOS Sport should just behave the
same way when trying to configure them, and hwOS Sport just ignores the
bits it doesn't "understand".

The odd child in the bunch is the OSTC4. Its a slightly different
protocol, with config variables meaning slightly different things.

> I read this as: We can add the OSTC Plus in the list together with the
> OSTC 2/3/Sport/cR and it should work?!

We should probably add the OSTC 2 TR to. There are quite a few config
variables thats new and should to be added to.

I haven't had the time to keep up with all the new interesting things
thats landed in hwos lately.


//Anton


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

Re: Subsurface configure DC feature and OSTC Plus

2018-03-12 Thread Matthias Heinrichs 

Hello,

Am 03.03.2018 um 21:30 schrieb Anton Lundin:

As far as I've know, there is no difference in the communication, if its
done over bluetooth or ftdi-usb-serial. In subsurface case its all
transparent. 


Correct. There is the exact same code on our (OSTC) side.


with Matthias and Co, hwOS Tec and hwOS Sport should just behave the
same way when trying to configure them, and hwOS Sport just ignores the
bits it doesn't "understand".


Also correct. We try to make these two branches as compatible as 
possible. All settings not included in the hwOS Sport are ignored from 
the hwOS Sport.



The odd child in the bunch is the OSTC4. Its a slightly different
protocol, with config variables meaning slightly different things.


The OSTC4 will be fully open-source very soon, as well (We're just 
cleaning up the code so it's a bit more understandable). So I hope to 
make the OSTC4 configuration-wise as compatible as possible then. 
Firmware update is and will be different, though.



We should probably add the OSTC 2 TR to. There are quite a few config
variables thats new and should to be added to.


Beside the firmware update (the OSTC 2 TR has a software-defined radio 
receiver which can be updated additionally to the normal firmware) the 
OSTC 2 TR is either an hwOS TEC or hwOS Sport OSTC. Nothing special for 
you to do.


regards,
Matthias


--
heinrichs weikamp gmbh * Adlerstr. 7 * 79098 Freiburg * Germany

Amtsgericht Freiburg HRB 713558 * Gerichtsstand Freiburg im Breisgau
Geschäftsführer: Matthias Heinrichs
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Subsurface configure DC feature and OSTC Plus

2018-03-12 Thread Stefan Fuchs 
Hallo Matthias,

could you please maybe answer the Subsurface and OSTC Plus related
question here:

https://github.com/Subsurface-divelog/subsurface/pull/1147

And maybe even quickly review the small change?

Thanks!


Viele Grüße
Stefan


-- 

Stefan Fuchs
Banzhaldenstr. 66
70469 Stuttgart
Tel.: 0711/4116289
Mobil: 0172/8922025
E-Mail: sfu...@gmx.de 

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

Group assign tank sizes, desktop

2018-03-12 Thread James Cialdea 
I came back from a trip where we used a few different nitrox mixes, but all
the same tank size. I imported all the dive profiles from my Suunto vyper
air.  Then, I selected all the dives and set the cylinder size in one
mutli-dive-edit operation.

I expected the cylinder size to be set on all dives and no other updates to
happen. Instead, all dives were assigned the gas mix from the first dive,
and all were assigned the same, expected, cylinder. The start and end
pressure, which is on the same line when editing cylinder or gas mix, were
unchanged, as expected.

Is this behavior of updating the gas mix on all dives when only the
cylinder is changed intentional?
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Subsurface Cloud access through authenticated proxy on Windows

2018-03-12 Thread Dirk Hohndel 
Yeah, the subject line shows how narrow this is... I think Davide was the one 
who kept running into this problem.

We had a bug that prevented us from using a proxy on Windows when that proxy 
required authentication.

Davide (or anyone else who has the ability to test this), any chance that you 
could test this installer?

https://github.com/Subsurface-divelog/subsurface/releases/download/continuous-windowsProxy/subsurface-4.7.7-69-gf144add732d5.exe

Thanks

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