Mares Quad mit Mares Bluelink Pro Probleme

Allgemeines zu Diving Log 6.0 - Fragen und Hinweise
Post Reply
Slight
Posts: 2
Joined: Fri Mar 09, 2018 15:54

Mares Quad mit Mares Bluelink Pro Probleme

Post by Slight » Fri Mar 09, 2018 16:03

Hallo,

vieleicht kann mir jemand helfen bevor ich noch durchdrehe.

Habe mir dem Mares Quad gekauft und versuche verzweifelt meine Tauchgänge mittels Mares Bluelink pro zu übertragen.

Ich bekomme den Fehler DC_STATUS_NOACCESS angezeigt.
Habe in den Bluetooth Einstellungen COM 5 als Anschluss Eingehend angegeben aber dort erscheint leider auch nicht das Interface als Name.

Bin am verzweifeln und hoffe mir kann jemand helfen.

Gruß
Peter

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

Re: Mares Quad mit Mares Bluelink Pro Probleme

Post by TnT » Mon Mar 12, 2018 12:27

The Mares Bluelink interface isn't supported yet, only the USB interface.
libdivecomputer developer
Support the libdivecomputer project with a donation!
http://www.libdivecomputer.org/donate.html

mschauer
Posts: 1
Joined: Sat Aug 03, 2019 19:14

Re: Mares Quad mit Mares Bluelink Pro Probleme

Post by mschauer » Sat Aug 03, 2019 19:17

Hello,
is it still impossible to import via Mares Blue Link?

Kind regards Marco

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

Re: Mares Quad mit Mares Bluelink Pro Probleme

Post by divinglog » Sat Aug 03, 2019 21:04

Hi

Mares Bluelink is now supported in the latest version.

Kind regards,
Sven

Stephan
Posts: 10
Joined: Thu Jul 14, 2011 20:10

Re: Mares Quad mit Mares Bluelink Pro Probleme

Post by Stephan » Mon Oct 21, 2019 15:50

Hallo,

bei mir funktioniert der Mares Bluelink Pro auch nicht.
Habe die Version 6.0.16 (Update1)
In Bluetooth und andere Geräte sehe ich meinen Mares Bluelink Pro gekoppelt.
Wenn im im Quad Air auf PC Ready gehe, wechselt der Mares Bluelink Pro in den Status Verbunden.

Aber beim Downloader
Verbindung: BLE
Hersteller: Mares
Tauchcomputer: Quad Air

ekomme ich folgende Fehler: Quad Air nicht gefunden ........(DC_STATUS_TIMEOUT)

Anbei das Fehler LOG:

INFO: Open: transport=32
INFO: Configure: baudrate=115200, databits=8, parity=2, stopbits=0, flowcontrol=0
INFO: Timeout: value=1000
INFO: DTR: value=0
INFO: RTS: value=0
INFO: Purge: direction=3
INFO: Write: size=2, data=C267
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in mares_iconhd.c:270 (mares_iconhd_packet)]
INFO: Purge: direction=1
INFO: Write: size=2, data=C267
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in mares_iconhd.c:270 (mares_iconhd_packet)]
INFO: Purge: direction=1
INFO: Write: size=2, data=C267
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in mares_iconhd.c:270 (mares_iconhd_packet)]
INFO: Purge: direction=1
INFO: Write: size=2, data=C267
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in mares_iconhd.c:270 (mares_iconhd_packet)]
INFO: Purge: direction=1
INFO: Write: size=2, data=C267
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in mares_iconhd.c:270 (mares_iconhd_packet)]


BLE Protocol:


INFO: libdivecomputer-0.dll version: 0.7.0-devel
INFO: Diving Log version: 6.0.16.1
INFO: Windows 10 (1903 | Build 18362), Version 6.3.18362

Was mache ich falsch?

Gruß Stephan

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

Re: Mares Quad mit Mares Bluelink Pro Probleme

Post by divinglog » Mon Oct 21, 2019 17:06

Hallo Stephan

Probiere mal bitte diese Datei herunterzuladen und den Inhalt in den Diving Log Programmordner zu kopieren. Sag bitte Bescheid ob es dann funktioniert.

Schöne Grüße,
Sven

Stephan
Posts: 10
Joined: Thu Jul 14, 2011 20:10

Re: Mares Quad mit Mares Bluelink Pro Probleme

Post by Stephan » Mon Oct 21, 2019 19:19

Hallo Sven,

hab die dll in das Verzeichnis kopiert.
Hat leider nicht funktioniert. Die gleiche Fehlermeldung.

Gruß Stephan

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

Re: Mares Quad mit Mares Bluelink Pro Probleme

Post by divinglog » Mon Oct 21, 2019 20:07

Hallo Stephan

Was mich wundert ist dass das BLE Protokol leer ist. Zwischen den beiden Zeilen sollte eigentlich etwas stehen:

Code: Select all

...
BLE Protocol:

INFO: libdivecomputer-0.dll version: 0.7.0-devel
...
Kannst du nochmal über die Schaltfläche "Auswählen" am unteren Rand im Download Dialog den Mares direkt wählen? Wieder mit aktiviertem "Log Errors".

Schöne Grüße,
Sven

Stephan
Posts: 10
Joined: Thu Jul 14, 2011 20:10

Re: Mares Quad mit Mares Bluelink Pro Probleme

Post by Stephan » Mon Oct 21, 2019 20:13

Hallo Sven,

jetzt kommt mehr.

INFO: Open: transport=32
INFO: Configure: baudrate=115200, databits=8, parity=2, stopbits=0, flowcontrol=0
INFO: Timeout: value=1000
INFO: DTR: value=0
INFO: RTS: value=0
INFO: Purge: direction=3
INFO: Write: size=2, data=C267
INFO: Read: size=20, data=AA00000000000000000000000000000000000000
INFO: Read: size=20, data=0000000000000000000000000000000000000000
INFO: Read: size=20, data=0000000000000000000000000000000000000000
INFO: Read: size=5, data=0000000000
INFO: Read: size=20, data=0000000000005175616420416972000000000000
INFO: Read: size=20, data=000030312E30312E30300101000031302D30312D
INFO: Read: size=20, data=3138C8E753564E36373300000000000000000000
INFO: Read: size=17, data=00000000000000000000000000000000EA
INFO: Write: size=2, data=E742
INFO: Read: size=1, data=AA
INFO: Write: size=8, data=0C00000004000000
INFO: Read: size=1, data=EA
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in mares_iconhd.c:271 (mares_iconhd_packet)]
INFO: Purge: direction=1
INFO: Write: size=2, data=E742
INFO: Read: size=1, data=AA
INFO: Write: size=8, data=0C00000004000000
INFO: Read: size=1, data=EA
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in mares_iconhd.c:271 (mares_iconhd_packet)]
INFO: Purge: direction=1
INFO: Write: size=2, data=E742
INFO: Read: size=1, data=AA
INFO: Write: size=8, data=0C00000004000000
INFO: Read: size=1, data=EA
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in mares_iconhd.c:271 (mares_iconhd_packet)]
INFO: Purge: direction=1
INFO: Write: size=2, data=E742
INFO: Read: size=1, data=AA
INFO: Write: size=8, data=0C00000004000000
INFO: Read: size=1, data=EA
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in mares_iconhd.c:271 (mares_iconhd_packet)]
INFO: Purge: direction=1
INFO: Write: size=2, data=E742
INFO: Read: size=1, data=AA
INFO: Write: size=8, data=0C00000004000000
INFO: Read: size=1, data=EA
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in mares_iconhd.c:271 (mares_iconhd_packet)]
ERROR: Failed to read the memory. [in mares_iconhd.c:546 (mares_iconhd_device_foreach)]


BLE Protocol:
00:00:538 Select device BluetoothLE#BluetoothLE00:1a:7d:da:71:13-00:1a:85:e0:1c:e3
00:00:919 Device selected: Mares bluelink pro
00:00:939 Number of Gatt Services: 5
00:00:940 Device ID: BluetoothLE#BluetoothLE00:1a:7d:da:71:13-00:1a:85:e0:1c:e3
00:00:941 Is Paired: True
00:00:941 Protection Level: Encryption
00:00:943 Connected to service: 544e326b-5b72-c6b0-1c46-41c1bc448118
00:00:975 Characteristics found: 99a91ebd-b21f-1689-bb43-681f1f55e966 (Read/WriteWithoutResponse)
00:00:975 Characteristics found: 1d1aae28-d2a8-91a1-1242-9d2973fbe571 (Read/Notify)
00:01:617 GattDescriptor written Notify to 1d1aae28-d2a8-91a1-1242-9d2973fbe571: Success (1 Connection Loops)
00:01:617 Connection successful!
00:01:652 Sent data C2-67 to 99a91ebd-b21f-1689-bb43-681f1f55e966: Success
00:02:608 Data received: 20 Bytes
00:02:619 Data received: 40 Bytes
00:02:620 Data received: 60 Bytes
00:02:620 Data received: 65 Bytes
00:03:097 Data received: 85 Bytes
00:03:098 Data received: 105 Bytes
00:03:099 Data received: 125 Bytes
00:03:100 Data received: 142 Bytes
00:03:130 Sent data E7-42 to 99a91ebd-b21f-1689-bb43-681f1f55e966: Success
00:04:104 Data received: 143 Bytes
00:04:121 Sent data 0C-00-00-00-04-00-00-00 to 99a91ebd-b21f-1689-bb43-681f1f55e966: Success
00:04:598 Data received: 144 Bytes
00:14:599 BLE_Read: Timeout
00:14:609 Sent data E7-42 to 99a91ebd-b21f-1689-bb43-681f1f55e966: Success
00:15:603 Data received: 145 Bytes
00:15:607 Sent data 0C-00-00-00-04-00-00-00 to 99a91ebd-b21f-1689-bb43-681f1f55e966: Success
00:16:097 Data received: 146 Bytes
00:26:102 BLE_Read: Timeout
00:26:111 Sent data E7-42 to 99a91ebd-b21f-1689-bb43-681f1f55e966: Success
00:27:098 Data received: 147 Bytes
00:27:116 Sent data 0C-00-00-00-04-00-00-00 to 99a91ebd-b21f-1689-bb43-681f1f55e966: Success
00:28:601 Data received: 148 Bytes
00:38:617 BLE_Read: Timeout
00:38:627 Sent data E7-42 to 99a91ebd-b21f-1689-bb43-681f1f55e966: Success
00:40:097 Data received: 149 Bytes
00:40:101 Data received: 150 Bytes
00:40:114 Sent data 0C-00-00-00-04-00-00-00 to 99a91ebd-b21f-1689-bb43-681f1f55e966: Success
00:50:113 BLE_Read: Timeout
00:50:125 Sent data E7-42 to 99a91ebd-b21f-1689-bb43-681f1f55e966: Success
00:51:097 Data received: 151 Bytes
00:51:117 Sent data 0C-00-00-00-04-00-00-00 to 99a91ebd-b21f-1689-bb43-681f1f55e966: Success
00:51:603 Data received: 152 Bytes
01:01:607 BLE_Read: Timeout


INFO: libdivecomputer-0.dll version: 0.7.0-devel
INFO: Diving Log version: 6.0.16.1
INFO: Windows 10 (1903 | Build 18362), Version 6.3.18362

Gruß Stephan

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

Re: Mares Quad mit Mares Bluelink Pro Probleme

Post by TnT » Fri Oct 25, 2019 07:11

Stephen,

There are some known problems with the Bluelink interface. I have some fixes available that appear to improve things for some users, but makes things worse for others. So far nothing that seems to work for everyone. I'm still trying to understand the underlying problem.

Can you try these two builds:
https://libdivecomputer.org/builds/expe ... osplit.dll
https://libdivecomputer.org/builds/expe ... .delay.dll

Simply remove the nodelay/nosplit suffix from the filename and copy the dll into the Diving Log directory (backup the original dll, so you can restore it afterwards). Start the Diving Log application and try to download from your Mares Quad with the "Log Errors" checkbox enabled. Repeat for the other dll, and send us the log files of each attempt.

Jef
libdivecomputer developer
Support the libdivecomputer project with a donation!
http://www.libdivecomputer.org/donate.html

Stephan
Posts: 10
Joined: Thu Jul 14, 2011 20:10

Re: Mares Quad mit Mares Bluelink Pro Probleme

Post by Stephan » Fri Oct 25, 2019 15:58

Hey Jef,

it works with the nosplit dll file.

Thank you very much

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

Re: Mares Quad mit Mares Bluelink Pro Probleme

Post by TnT » Sat Oct 26, 2019 11:52

Can you also email me the log files? I really need the detailed info from those logs to figure out and understand the underlying problem. Just knowing one of those builds worked won't help me to fix the problem.
libdivecomputer developer
Support the libdivecomputer project with a donation!
http://www.libdivecomputer.org/donate.html

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

Re: Mares Quad mit Mares Bluelink Pro Probleme

Post by divinglog » Sat Oct 26, 2019 13:28

Hallo Stephan

Nach dem Download findest du jeweils das Error Log hier:

C:\Users\Dein Name\AppData\Roaming\Diving Log\DC_FAMILY_MARES_ICONHD.txt

Schöne Grüße,
Sven

Stephan
Posts: 10
Joined: Thu Jul 14, 2011 20:10

Re: Mares Quad mit Mares Bluelink Pro Probleme

Post by Stephan » Fri Nov 01, 2019 16:26

Hey Jef and Sven

here are both log files.
The download took a long time. But the dives have been transferred.

Stephan
Attachments
LOG_nosplit.txt
(103.67 KiB) Downloaded 12 times
LOG_nodelay.txt
(4.74 KiB) Downloaded 10 times

Post Reply