RE: [TEST REQUEST] Windows Bluetooth LE build

[Steve]

-Original Message-
From: Lubomir I. Ivanov  
Sent: Wednesday, 13 June 2018 9:10 AM
To: Steve 
Subject: Re: [TEST REQUEST] Windows Bluetooth LE build

On 13 June 2018 at 02:06, Steve  wrote:
>
> Yes they were paired and setup in the OS, just to be sure I removed both them 
> and set them up again and then started again but got the exact same results.
>

thanks for re-checking.
"Remote device cannot be found" means that the BLE address passed to the 
backend code is invalid or empty.
what else you can do here is verify that the addresses for this device match in 
Subsurface and the "BLE explorer" app.
assuming that you are entering the correct BLE address, then this could be bug, 
but it might be difficult to catch why given i can't reproduce this locally.

haven't had time to do more testing / debugging here myself. maybe later this 
week.

lubomir
--

I just checked the OSTC3+ (see attachment) and I don't have the Petrel2 with me 
as I generally don't unplug it from the CCR so that will have to wait till 
tonight but I am fairly certain it is passing the correct address.

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

Fwd: [TEST REQUEST] Windows Bluetooth LE build

[Lubomir I. Ivanov]

forgot to to add the mailing list.


-- Forwarded message --
From: Lubomir I. Ivanov 
Date: 13 June 2018 at 02:39
Subject: Re: [TEST REQUEST] Windows Bluetooth LE build
To: Steve 


On 13 June 2018 at 02:06, Steve  wrote:
>
> Yes they were paired and setup in the OS, just to be sure I removed both them 
> and set them up again and then started again but got the exact same results.
>

thanks for re-checking.
"Remote device cannot be found" means that the BLE address passed to
the backend code is invalid or empty.
what else you can do here is verify that the addresses for this device
match in Subsurface and the "BLE explorer" app.
assuming that you are entering the correct BLE address, then this
could be bug, but it might be difficult to catch why given i can't
reproduce this locally.

haven't had time to do more testing / debugging here myself. maybe
later this week.

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

Re: [TEST REQUEST] Windows Bluetooth LE build

[Lubomir I. Ivanov]

On 12 June 2018 at 14:51, Steve  wrote:
>
>
> Running Windows 10 latest slow ring updates.
>
>
> First I tried HW OSTC3+
>
> Console output:
>
> Set the current dive site: 0
> Set the current dive site: 0
> Set the current dive site: 0
> Starting download from  BT
> Starting the thread 0
> Finishing the thread Unable to open %s %s (%s) dives downloaded 0
> Set the current dive site: 0
> Set the current dive site: 0
>
> See attached screenshot.
>
>
>
> Second I tried a Petrel 2
>
> Console output:
>
> Set the current dive site: 0
> Set the current dive site: 0
> Set the current dive site: 0
> Starting download from  BT
> Starting the thread 0
> Unimplemented code.
> qt_ble_open( 00:13:43:0D:DB:D4 )
> "The system cannot find the path specified."
> failed to connect to the controller  00:13:43:0D:DB:D4 with error "Remote 
> device cannot be found"
> Finishing the thread Unable to open %s %s (%s) dives downloaded 0
> Set the current dive site: 0
> Set the current dive site: 0
>
> Also took screenshot.
>
> Hope this offers some help.
>


hi, Steve. are your devices paired via the Windows "Bluetooth and
other devices" Control panel?
please, try to do that first.

the errors your are getting are related to the fact that our backend
cannot connect / pair to a device automatically for now.

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

Re: [TEST REQUEST] Windows Bluetooth LE build

[Willem Ferguson]

On 12/06/2018 10:39, tormento wrote:
I have a Bluegiga BT usb dongle that can work both as BT and BTLE. 
Unfortunately I can't find the way to switch between the two modes and 
the instructions I found in the SDK are a bit cryptic.


Can somebody help me, so I can test this feature with G2 too?


Assuming you do not, at this stage, want to change the code for 
Bluetooth download, you do as follows:


Do NOT try to connect your G2 using the operating system Bluetooth 
configuration: all this happens within Subsurface.


1) In the main Subsurface menu, go Import -> Import from dive computer. 
This opens the panel in Fig1 (attached).


2) On the download panel, select your dive computer, which would be 
ScubaPro and, directly underneath, G2.


3) If "Choose Bluetooth download mode" is selected, then de-select it 
and select it again. If it is not selected, then select it. This opens a 
new panel used for setting up the Bluetooth link.


4) Hit the "Scan" button. Your G2 should appear in the box. Look closely 
at the entry in the box. If it says "Unpaired", then right-click on the 
G2 entry. A context menu appears asking Pair/Unpair. Select "Pair". This 
should pair the G2 and the information for your G2 should change to 
reflect that it is now paired.


5) On this panel, there is a dropdown list marked "Auto". Activate the 
dropdown list by clicking on Auto and select either "Force Classic mode" 
or "Force BLE mode".


Now you can save the Bluetooth setup information by hitting the Save 
button. There should be a message to the bottom left of the panel that 
gives you full information on the setup. Keep your eye on that 
information. If download is successful, you do not have to do this setup 
again: Subsurface remembers it. Next time, only use the download panel 
without any need for Bluetooth setup.


Now, in the download panel, select "Download". Download should start, 
and a list of dives should appear in the right-hand part of the panel. 
From this list of dives, select the dives you want downloaded. Then hit 
OK. Download done.


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: [TEST REQUEST] Windows Bluetooth LE build

[tormento]

I have a Bluegiga BT usb dongle that can work both as BT and BTLE.
Unfortunately I can't find the way to switch between the two modes and the
instructions I found in the SDK are a bit cryptic.

Can somebody help me, so I can test this feature with G2 too?

Il giorno lun 11 giu 2018 alle ore 22:21 Berthold Stoeger <
bstoe...@mail.tuwien.ac.at> ha scritto:

> On Montag, 11. Juni 2018 20:50:56 CEST Linus Torvalds wrote:
>
> > BLE is kind of odd. We also do things kind of oddly, because the way
> > we generate that 16-bit value is with
> >
> > QByteArray::fromHex("0100")
>
> I think the idiomatic way to do this is the
>QByteArrayLiteral("\x01\x00")
> macro invocation (don't look at the macro definition - you might weep).
> Here,
> the object is compile-time generated. Nevertheless, its use is not "free"
> as
> claimed in the docs. There's still useless code generated owing to
> reference
> counting. Well, perhaps the compiler could decide that deallocating the
> static
> storage is undefined behavior and simply not generate the deallocation
> branch.
> But "gcc -O2" does.
>
> TL;DR: writeCharacteristic() taking a "const QByteArray &" parameter is an
> API-bug. It should take an "array_view" (i.e. const pointer + length) to
> which
> QByteArray automatically converts.
>
> Berthold
>
>
> ___
> 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: converting logbook formats

[C. Hoefer]

Thanks a lot Anton,

I was aware of the 'simple solution', but just not a huge fan of
uploading privat stuff to any storage beyond my control. 

But the other solution sounds reasonable. I'll try that. I was about to
look into the logbook access in the source... _that_ would have meant
effort.

cheers
/Chris


On Mo, 2018-06-11 at 20:27 +0200, Anton Lundin wrote:
> On 08 June, 2018 - C. Hoefer wrote:
> 
> > Hello,
> > 
> > I'm trying to start using subsurface mobile.
> > 
> > Is there a tool to convert my xml logbook to the format used with the
> > mobile? Back and forth at best. :-)
> 
> The simple answer is Use the cloud service. Its the only supported
> source for subsurface mobile. It will handle everything for you.
> 
> 
> 
> To answer your literal question, Using Subsurface is the sane way of
> doing it. Just create a git repo, ex:
> 
> mkdir ~/TEST
> cd ~/TEST
> git init .
> 
> and choose save as, and point it to that repo, and add [branch-name] to
> it.
> 
> 
> If you're bat shit crazy like I am, you can then transplant that repo
> into the data folder of your mobile device, and you've loaded your
> logbook into your mobile device without the cloud service. It requires a
> lot of low level hacking, so its not recommended for anyone else.
> 
> 
> //Anton
> 
> 


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