Bluetooth LE Download Support (Beta)

Allgemeines zu Diving Log 6.0 - Fragen und Hinweise
God-of-Games
Posts: 118
Joined: Wed Feb 02, 2011 23:24

Bluetooth LE Download Support (Beta)

Post by God-of-Games » Tue Apr 09, 2019 17:08

Hallo Sven,
ich habe mir nun auch mal die Beta heruntergeladen.
TC: Scubapro Aladin H Matrix
  1. Alle alten Kopplungen habe ich vor dem Test entfernt. Funktion mit LogTrack war gegeben.
  2. Downloader => Scubapro => Aladin Sport Matrix ausgewählt.
  3. Im TC BT aktiviert.
  4. Klick auf Discover.
  5. Aladin (Unpaired) ausgewählt und mit OK bestätigt.
  6. Fehlermeldung:

    Code: Select all

    BLE Protocol:
    Select device BluetoothLE#BluetoothLEd0:57:7b:e5:0c:0d-00:13:43:40:62:10
    Device selected: Aladin
    Number of Gatt Services: 0
    Device ID: BluetoothLE#BluetoothLEd0:57:7b:e5:0c:0d-00:13:43:40:62:10
    Is Paired: False
    Starting to pair...
    Connection status changed: Connected
    Pairing Result: Paired
    Paired device name: Aladin H
    Number of Gatt Services: 6 (50 Pairing Loops)
    Connected to service: fdcdeaaa-295d-470e-bf15-04217b7aa0a0
    Error: Das Attribut muss vor dem Lesen oder Schreiben zunächst authentifiziert werden. (Ausnahme von HRESULT: 0x80650005)
    
    
    INFO: libdivecomputer-0.dll version: 0.7.0-devel
    INFO: Diving Log version: 6.0.15.0
    INFO: Windows 10 (1803 | Build 17134), Version 6.3.17134
  7. Danach ist der TC unter den BT-Geräten in der Systemsteuerung als gekoppelt aufgeführt.
  8. Erneuter Verbindungsversuch mit Aladin (Paired):

    Code: Select all

    INFO: Open: transport=32
    INFO: Configure: baudrate=57600, databits=8, parity=0, stopbits=0, flowcontrol=0
    INFO: Timeout: value=3000
    INFO: Purge: direction=3
    DEBUG: cmd: size=0, data=
    INFO: Write: size=2, data=0110
    INFO: Read: size=0, data=
    ERROR: Failed to receive the packet. [in uwatec_smart.c:320 (uwatec_smart_usbhid_receive)]
    ERROR: Failed to receive the answer. [in uwatec_smart.c:406 (uwatec_smart_transfer)]
    
    
    BLE Protocol:
    
    
    INFO: libdivecomputer-0.dll version: 0.7.0-devel
    INFO: Diving Log version: 6.0.15.0
    INFO: Windows 10 (1803 | Build 17134), Version 6.3.17134
Neuer Versuch, diese Mal vorher über die Systemsteuerung gekoppelt (mit PIN):
  1. Klick auf Discover.
  2. Aladin (Paired) ausgewählt und mit OK bestätigt.
  3. Fehlermeldung:

    Code: Select all

    INFO: Open: transport=32
    INFO: Configure: baudrate=57600, databits=8, parity=0, stopbits=0, flowcontrol=0
    INFO: Timeout: value=3000
    INFO: Purge: direction=3
    DEBUG: cmd: size=0, data=
    INFO: Write: size=2, data=0110
    INFO: Read: size=0, data=
    ERROR: Failed to receive the packet. [in uwatec_smart.c:320 (uwatec_smart_usbhid_receive)]
    ERROR: Failed to receive the answer. [in uwatec_smart.c:406 (uwatec_smart_transfer)]
    
    
    BLE Protocol:
    Select device BluetoothLE#BluetoothLEd0:57:7b:e5:0c:0d-00:13:43:40:62:10
    Device selected: Aladin
    Number of Gatt Services: 6
    Device ID: BluetoothLE#BluetoothLEd0:57:7b:e5:0c:0d-00:13:43:40:62:10
    Is Paired: True
    Connected to service: fdcdeaaa-295d-470e-bf15-04217b7aa0a0
    Connection status changed: Connected
    Characteristics found: a188b7dd-debb-449a-852d-c243d46b4b1a (Write)
    Characteristics found: aa0c68f0-ea9c-493d-8112-62879e72af68 (Read/Notify)
    GattDescriptor written Notify to aa0c68f0-ea9c-493d-8112-62879e72af68: Success (1 Connection Loops)
    Connection successful!
    Sent data 01-10 to a188b7dd-debb-449a-852d-c243d46b4b1a: Success
    BLE_Read: Timeout
    
    
    INFO: libdivecomputer-0.dll version: 0.7.0-devel
    INFO: Diving Log version: 6.0.15.0
    INFO: Windows 10 (1803 | Build 17134), Version 6.3.17134
Hoffe du kannst damit was anfangen.

Grüße,
Jochen

Philipp
Posts: 25
Joined: Tue Nov 06, 2018 05:49
Location: Bad Brückenau

Re: Bluetooth LE Download Support (Beta)

Post by Philipp » Tue Apr 09, 2019 19:25

Gut dass es nicht nur mir so geht. Ich dachte zuerst dass es an meinem Rechner oder an mir liegt. Ich stehe in regem Kontakt mit Sven wegen dem gleichen Fehler.

divinglog
Site Admin
Posts: 5080
Joined: Sat Feb 08, 2003 21:02
Location: Coburg
Contact:

Re: Bluetooth LE Download Support (Beta)

Post by divinglog » Wed Apr 10, 2019 21:00

Hallo Jochen

Vielen Dank für's Testen! Ja, bei den Scubapro BLE Rechnern gibt's im Moment noch ein kleines Problem, bei Shearwater und HeinrichsWeikamp klappt inzwischen alles. Ich hab morgen eine neue Testversion zum ausprobieren.

Schöne Grüße,
Sven

TnT
Posts: 257
Joined: Thu Nov 29, 2007 14:53
Contact:

Re: Bluetooth LE Download Support (Beta)

Post by TnT » Thu Apr 11, 2019 13:08

Strictly speaking the Scubapro Aladin H Matrix isn't supported yet in libdivecomputer. Most likely it doesn't need any changes and it will just work out of the box, but that's no guarantee. Does the Scubapro Aladin H Matrix support only BLE, or also usb? If it does support usb, then you could already send me a memory dump. Then way I can already take care of adding it to libdivecomputer, while Sven addresses the BLE communication.
libdivecomputer developer
Support the libdivecomputer project with a donation!
http://www.libdivecomputer.org/donate.html

divinglog
Site Admin
Posts: 5080
Joined: Sat Feb 08, 2003 21:02
Location: Coburg
Contact:

Re: Bluetooth LE Download Support (Beta)

Post by divinglog » Thu Apr 11, 2019 13:57

Hi Jef

The Sport Matrix is BLE only (no USB), but I have confirmed that the download works with Subsurface (I've not checked the parsed data yet). But Philipp can send you a memory dump via Subsurface if you want to have a look at the data. I've attached the libdc protocol he sent me.

Sven
Attachments
subsurface.log
(461.45 KiB) Downloaded 43 times

divinglog
Site Admin
Posts: 5080
Joined: Sat Feb 08, 2003 21:02
Location: Coburg
Contact:

Re: Bluetooth LE Download Support (Beta)

Post by divinglog » Thu Apr 11, 2019 14:49

Ich hab eine neue Testversion für Aladin Sport Matrix und G2:

https://www.divinglog.com/beta/DivelogTest6.zip

Bitte sicherstellen das alle 3 Dateien aus der Zipdatei in den Programmordner kopiert und die vorhandenen Dateien ersetzt werden. Vielen Dank für's Ausprobieren ob's diesmal klappt. Eigentlich mache ich es genau gleich wie Subsurface.

Shaki
Posts: 2
Joined: Wed Jan 31, 2018 11:55

Re: Bluetooth LE Download Support (Beta)

Post by Shaki » Thu Apr 11, 2019 15:54

Hi, mit meinem G2 geht es nicht. Hab die 3 Dateien überschrieben und gestartet. G2 zeigt sofort verbunden an und nach ca. 6 Sekunden kommt von Diving Log die Fehlermeldung G2 nicht gefunden.

INFO: Open: transport=32
INFO: Configure: baudrate=57600, databits=8, parity=0, stopbits=0, flowcontrol=0
INFO: Timeout: value=3000
INFO: Purge: direction=3
DEBUG: cmd: size=0, data=
INFO: Write: size=2, data=0110
INFO: Read: size=0, data=
ERROR: Failed to receive the packet. [in uwatec_smart.c:320 (uwatec_smart_usbhid_receive)]
ERROR: Failed to receive the answer. [in uwatec_smart.c:406 (uwatec_smart_transfer)]


BLE Protocol:
Paired Device: G2
Paired Device found: G2
Select device BluetoothLE#BluetoothLEe4:a4:71:d6:d1:3d-00:13:43:59:cc:5d
Device selected: G2
Number of Gatt Services: 6
Device ID: BluetoothLE#BluetoothLEe4:a4:71:d6:d1:3d-00:13:43:59:cc:5d
Is Paired: True
Connected to service: fdcdeaaa-295d-470e-bf15-04217b7aa0a0
Connection status changed: Connected
GattDescriptor written Notify to aa0c68f0-ea9c-493d-8112-62879e72af68: Success
Characteristics found: a188b7dd-debb-449a-852d-c243d46b4b1a (Write)
Characteristics found: aa0c68f0-ea9c-493d-8112-62879e72af68 (Read/Notify)
Connection successful!
Sent data 01-10 to a188b7dd-debb-449a-852d-c243d46b4b1a: Success
BLE_Read: Timeout


INFO: libdivecomputer-0.dll version: 0.7.0-devel
INFO: Diving Log version: 6.0.15.0
INFO: Windows 10 (1809 | Build 17763), Version 6.3.17763

God-of-Games
Posts: 118
Joined: Wed Feb 02, 2011 23:24

Re: Bluetooth LE Download Support (Beta)

Post by God-of-Games » Thu Apr 11, 2019 16:43

Hallo Sven,
leider nicht.
Anbei die Logs mit der gleichen Vorgehensweise wie letztes Mal:

Code: Select all

BLE Protocol:
Select device BluetoothLE#BluetoothLEd0:57:7b:e5:0c:0d-00:13:43:40:62:10
Device selected: Aladin
Number of Gatt Services: 0
Device ID: BluetoothLE#BluetoothLEd0:57:7b:e5:0c:0d-00:13:43:40:62:10
Is Paired: False
Starting to pair...
Connection status changed: Connected
Pairing Result: Paired
Paired device name: Aladin H
Number of Gatt Services: 6 (51 Pairing Loops)
Connected to service: fdcdeaaa-295d-470e-bf15-04217b7aa0a0
Error: Das Attribut muss vor dem Lesen oder Schreiben zunächst authentifiziert werden. (Ausnahme von HRESULT: 0x80650005)


INFO: libdivecomputer-0.dll version: 0.7.0-devel
INFO: Diving Log version: 6.0.15.0
INFO: Windows 10 (1803 | Build 17134), Version 6.3.17134

Code: Select all

INFO: Open: transport=32
INFO: Configure: baudrate=57600, databits=8, parity=0, stopbits=0, flowcontrol=0
INFO: Timeout: value=3000
INFO: Purge: direction=3
DEBUG: cmd: size=0, data=
INFO: Write: size=2, data=0110
INFO: Read: size=0, data=
ERROR: Failed to receive the packet. [in uwatec_smart.c:320 (uwatec_smart_usbhid_receive)]
ERROR: Failed to receive the answer. [in uwatec_smart.c:406 (uwatec_smart_transfer)]


BLE Protocol:
Select device BluetoothLE#BluetoothLEd0:57:7b:e5:0c:0d-00:13:43:40:62:10
Device selected: Aladin H
Number of Gatt Services: 6
Device ID: BluetoothLE#BluetoothLEd0:57:7b:e5:0c:0d-00:13:43:40:62:10
Is Paired: True
Connected to service: fdcdeaaa-295d-470e-bf15-04217b7aa0a0
Connection status changed: Connected
GattDescriptor written Notify to aa0c68f0-ea9c-493d-8112-62879e72af68: Success
Characteristics found: a188b7dd-debb-449a-852d-c243d46b4b1a (Write)
Characteristics found: aa0c68f0-ea9c-493d-8112-62879e72af68 (Read/Notify)
Connection successful!
Sent data 01-10 to a188b7dd-debb-449a-852d-c243d46b4b1a: Success
BLE_Read: Timeout


INFO: libdivecomputer-0.dll version: 0.7.0-devel
INFO: Diving Log version: 6.0.15.0
INFO: Windows 10 (1803 | Build 17134), Version 6.3.17134

Code: Select all

INFO: Open: transport=32
INFO: Configure: baudrate=57600, databits=8, parity=0, stopbits=0, flowcontrol=0
INFO: Timeout: value=3000
INFO: Purge: direction=3
DEBUG: cmd: size=0, data=
INFO: Write: size=2, data=0110
INFO: Read: size=0, data=
ERROR: Failed to receive the packet. [in uwatec_smart.c:320 (uwatec_smart_usbhid_receive)]
ERROR: Failed to receive the answer. [in uwatec_smart.c:406 (uwatec_smart_transfer)]


BLE Protocol:
Select device BluetoothLE#BluetoothLEd0:57:7b:e5:0c:0d-00:13:43:40:62:10
Device selected: Aladin H
Number of Gatt Services: 6
Device ID: BluetoothLE#BluetoothLEd0:57:7b:e5:0c:0d-00:13:43:40:62:10
Is Paired: True
Connected to service: fdcdeaaa-295d-470e-bf15-04217b7aa0a0
Connection status changed: Connected
GattDescriptor written Notify to aa0c68f0-ea9c-493d-8112-62879e72af68: Success
Characteristics found: a188b7dd-debb-449a-852d-c243d46b4b1a (Write)
Characteristics found: aa0c68f0-ea9c-493d-8112-62879e72af68 (Read/Notify)
Connection successful!
Sent data 01-10 to a188b7dd-debb-449a-852d-c243d46b4b1a: Success
BLE_Read: Timeout


INFO: libdivecomputer-0.dll version: 0.7.0-devel
INFO: Diving Log version: 6.0.15.0
INFO: Windows 10 (1803 | Build 17134), Version 6.3.17134
Ich weiß nicht ob es relevant ist, ich betreibe aber den TC im Gauge-Modus. Der Import nach LogTrack war aber OK.

Philipp
Posts: 25
Joined: Tue Nov 06, 2018 05:49
Location: Bad Brückenau

Re: Bluetooth LE Download Support (Beta)

Post by Philipp » Thu Apr 11, 2019 17:28

Bei mir leider auch das gleiche wie gehabt.

Gruß
Philipp

divinglog
Site Admin
Posts: 5080
Joined: Sat Feb 08, 2003 21:02
Location: Coburg
Contact:

Re: Bluetooth LE Download Support (Beta)

Post by divinglog » Thu Apr 11, 2019 18:05

Hmm, das ist wirklich merkwürdig und so langsam bin ich mit meinem Latein am Ende. Die Verbindung steht, der Tauchcomputer antwortet aber einfach nicht. Das Protokoll von Subsurface ist identisch, allerdings kommt hier die Antwort vom Tauchcomputer:

Code: Select all

Starting download from  BT
qt_ble_open( 00:13:43:5D:AE:2E )
connected to the controller for device 00:13:43:5D:AE:2E
  .. discovering services
Found uuid: "{00001800-0000-1000-8000-00805f9b34fb}"
Found service "{00001800-0000-1000-8000-00805f9b34fb}"
 .. ignoring standard service "{00001800-0000-1000-8000-00805f9b34fb}"
Found uuid: "{00001801-0000-1000-8000-00805f9b34fb}"
Found service "{00001801-0000-1000-8000-00805f9b34fb}"
 .. ignoring standard service "{00001801-0000-1000-8000-00805f9b34fb}"
Found uuid: "{0000180a-0000-1000-8000-00805f9b34fb}"
Found service "{0000180a-0000-1000-8000-00805f9b34fb}"
 .. ignoring standard service "{0000180a-0000-1000-8000-00805f9b34fb}"
Found uuid: "{0000180f-0000-1000-8000-00805f9b34fb}"
Found service "{0000180f-0000-1000-8000-00805f9b34fb}"
 .. ignoring standard service "{0000180f-0000-1000-8000-00805f9b34fb}"
Found uuid: "{0000181a-0000-1000-8000-00805f9b34fb}"
Found service "{0000181a-0000-1000-8000-00805f9b34fb}"
 .. ignoring standard service "{0000181a-0000-1000-8000-00805f9b34fb}"
Found uuid: "{fdcdeaaa-295d-470e-bf15-04217b7aa0a0}"
Found service "{fdcdeaaa-295d-470e-bf15-04217b7aa0a0}"
 .. created service object QLowEnergyService(0x105cccd8)
 .. done discovering services
Found service "{fdcdeaaa-295d-470e-bf15-04217b7aa0a0}" "Unknown Service"
   c: "{a188b7dd-debb-449a-852d-c243d46b4b1a}"
   c: "{aa0c68f0-ea9c-493d-8112-62879e72af68}"
        d: "{00002902-0000-1000-8000-00805f9b34fb}"
Using service "{fdcdeaaa-295d-470e-bf15-04217b7aa0a0}" as preferred service
 .. enabling notifications
Using read characteristic "{aa0c68f0-ea9c-493d-8112-62879e72af68}"
now writing "0x0100" to the descriptor "{00002902-0000-1000-8000-00805f9b34fb}"
BLE write completed
QTime("20:15:17.898") packet SEND "0110"
QTime("20:15:17.898") packet WAIT
BLEObject::characteristicWritten
QTime("20:15:17.951") packet RECV "0132"
QTime("20:15:17.951") packet READ "0132"
Das einzige was wir noch probieren können ist zu überprüfen ob das "Notify" an den richtigen descriptor geschrieben wird. Ich nutze die automatische .NET Funktion, Subsurface wählt ihn manuell. Ich werde mal eine Testversion erstellen die alle Descriptors listet und schreibe das "Notify" auch manuell, mal schauen ob das hilft.

divinglog
Site Admin
Posts: 5080
Joined: Sat Feb 08, 2003 21:02
Location: Coburg
Contact:

Re: Bluetooth LE Download Support (Beta)

Post by divinglog » Thu Apr 11, 2019 19:16


Philipp
Posts: 25
Joined: Tue Nov 06, 2018 05:49
Location: Bad Brückenau

Re: Bluetooth LE Download Support (Beta)

Post by Philipp » Thu Apr 11, 2019 21:04

Hallo Sven,

leider war auch dieser Test erfolglos.

INFO: Open: transport=32
INFO: Configure: baudrate=57600, databits=8, parity=0, stopbits=0, flowcontrol=0
INFO: Timeout: value=3000
INFO: Purge: direction=3
DEBUG: cmd: size=0, data=
INFO: Write: size=2, data=0110
INFO: Read: size=0, data=
ERROR: Failed to receive the packet. [in uwatec_smart.c:320 (uwatec_smart_usbhid_receive)]
ERROR: Failed to receive the answer. [in uwatec_smart.c:406 (uwatec_smart_transfer)]


BLE Protocol:
Paired Device: Aladin
Paired Device found: Aladin
Select device BluetoothLE#BluetoothLE7c:c7:08:60:45:4f-00:13:43:40:6f:a8
Device selected: Aladin
Number of Gatt Services: 6
Device ID: BluetoothLE#BluetoothLE7c:c7:08:60:45:4f-00:13:43:40:6f:a8
Is Paired: True
Connected to service: fdcdeaaa-295d-470e-bf15-04217b7aa0a0
Characteristics found: a188b7dd-debb-449a-852d-c243d46b4b1a (Write)
Characteristics found: aa0c68f0-ea9c-493d-8112-62879e72af68 (Read/Notify)
Connection status changed: Connected
GattDescriptor written Notify to aa0c68f0-ea9c-493d-8112-62879e72af68: Success
Descriptor found: 00002902-0000-1000-8000-00805f9b34fb
GattDescriptor written 01-00 to 00002902-0000-1000-8000-00805f9b34fb: Success
Scubapro_Read_Character: aa0c68f0-ea9c-493d-8112-62879e72af68 (Read/Notify)
Connection successful!
Sent data 01-10 to a188b7dd-debb-449a-852d-c243d46b4b1a: Success
BLE_Read: Timeout


INFO: libdivecomputer-0.dll version: 0.7.0-devel
INFO: Diving Log version: 6.0.15.0
INFO: Windows 10 (1709 | Build 16299), Version 6.3.16299

Gruß
Philipp

God-of-Games
Posts: 118
Joined: Wed Feb 02, 2011 23:24

Re: Bluetooth LE Download Support (Beta)

Post by God-of-Games » Thu Apr 11, 2019 22:08

Philipp wrote:
Thu Apr 11, 2019 21:04
Hallo Sven,

leider war auch dieser Test erfolglos.
Dito. Dieses Mal nur Versuch 3.

Code: Select all

INFO: Open: transport=32
INFO: Configure: baudrate=57600, databits=8, parity=0, stopbits=0, flowcontrol=0
INFO: Timeout: value=3000
INFO: Purge: direction=3
DEBUG: cmd: size=0, data=
INFO: Write: size=2, data=0110
INFO: Read: size=0, data=
ERROR: Failed to receive the packet. [in uwatec_smart.c:320 (uwatec_smart_usbhid_receive)]
ERROR: Failed to receive the answer. [in uwatec_smart.c:406 (uwatec_smart_transfer)]


BLE Protocol:
Paired Device: Aladin H
Paired Device found: Aladin H
Select device BluetoothLE#BluetoothLEd0:57:7b:e5:0c:0d-00:13:43:40:62:10
Device selected: Aladin H
Number of Gatt Services: 6
Device ID: BluetoothLE#BluetoothLEd0:57:7b:e5:0c:0d-00:13:43:40:62:10
Is Paired: True
Connected to service: fdcdeaaa-295d-470e-bf15-04217b7aa0a0
Characteristics found: a188b7dd-debb-449a-852d-c243d46b4b1a (Write)
Characteristics found: aa0c68f0-ea9c-493d-8112-62879e72af68 (Read/Notify)
Connection status changed: Connected
GattDescriptor written Notify to aa0c68f0-ea9c-493d-8112-62879e72af68: Success
Descriptor found: 00002902-0000-1000-8000-00805f9b34fb
GattDescriptor written 01-00 to 00002902-0000-1000-8000-00805f9b34fb: Success
Scubapro_Read_Character: aa0c68f0-ea9c-493d-8112-62879e72af68 (Read/Notify)
Connection successful!
Sent data 01-10 to a188b7dd-debb-449a-852d-c243d46b4b1a: Success
BLE_Read: Timeout


INFO: libdivecomputer-0.dll version: 0.7.0-devel
INFO: Diving Log version: 6.0.15.0
INFO: Windows 10 (1803 | Build 17134), Version 6.3.17134
Grüße,
Jochen

divinglog
Site Admin
Posts: 5080
Joined: Sat Feb 08, 2003 21:02
Location: Coburg
Contact:

Re: Bluetooth LE Download Support (Beta)

Post by divinglog » Sat Apr 13, 2019 21:59

OK, letzter Versuch, wenn das nicht klappt bestelle ich Montag einen Sport Matrix und versuch das hier so lange bis es klappt :lol:

https://www.divinglog.com/beta/DivelogTest8.zip

Ich hab jetzt die Vermutung das es etwas mit der Pin Code Eingabe bei der Paarung zu tun haben könnte. Evt. verwendet dieser Computer eine zusätzliche Sicherheitsfunktion für die Kommunikation. Beim OSTC und Shearwater muss man bei der Paarung keinen Pin Code eingeben.

Philipp
Posts: 25
Joined: Tue Nov 06, 2018 05:49
Location: Bad Brückenau

Re: Bluetooth LE Download Support (Beta)

Post by Philipp » Sun Apr 14, 2019 10:06

Hallo Sven,

ich würde sagen du kannst dir einen Sport Matrix bestellen.

INFO: Open: transport=32
INFO: Configure: baudrate=57600, databits=8, parity=0, stopbits=0, flowcontrol=0
INFO: Timeout: value=3000
INFO: Purge: direction=3
DEBUG: cmd: size=0, data=
INFO: Write: size=2, data=0110
INFO: Read: size=0, data=
ERROR: Failed to receive the packet. [in uwatec_smart.c:320 (uwatec_smart_usbhid_receive)]
ERROR: Failed to receive the answer. [in uwatec_smart.c:406 (uwatec_smart_transfer)]


BLE Protocol:
Paired Device: Aladin Sport
Paired Device found: Aladin Sport
Select device BluetoothLE#BluetoothLE7c:c7:08:60:45:4f-00:13:43:40:6f:a8
Device selected: Aladin Sport
Number of Gatt Services: 6
Device ID: BluetoothLE#BluetoothLE7c:c7:08:60:45:4f-00:13:43:40:6f:a8
Is Paired: True
Protection Level: EncryptionAndAuthentication
Connected to service: fdcdeaaa-295d-470e-bf15-04217b7aa0a0
Characteristics found: a188b7dd-debb-449a-852d-c243d46b4b1a (Write)
Characteristics found: aa0c68f0-ea9c-493d-8112-62879e72af68 (Read/Notify)
Scubapro_Write_Character Protection: a188b7dd-debb-449a-852d-c243d46b4b1a (Plain)
Scubapro_Read_Character Protection: aa0c68f0-ea9c-493d-8112-62879e72af68 (Plain)
Scubapro_Write_Character Protection: a188b7dd-debb-449a-852d-c243d46b4b1a (EncryptionAndAuthenticationRequired)
Scubapro_Read_Character Protection: aa0c68f0-ea9c-493d-8112-62879e72af68 (EncryptionAndAuthenticationRequired)
Connection status changed: Connected
GattDescriptor written Notify to aa0c68f0-ea9c-493d-8112-62879e72af68: Success
Scubapro_Read_Character: aa0c68f0-ea9c-493d-8112-62879e72af68 (Read/Notify)
Connection successful!
Sent data 01-10 to a188b7dd-debb-449a-852d-c243d46b4b1a: Success
BLE_Read: Timeout


INFO: libdivecomputer-0.dll version: 0.7.0-devel
INFO: Diving Log version: 6.0.15.0
INFO: Windows 10 (1709 | Build 16299), Version 6.3.16299

Gruß
Philipp

Post Reply