DC_STATUS_DATAFORMAT with i470TC

Discussions about Diving Log 6.0 - questions and hints
Post Reply
voets
Posts: 15
Joined: Fri Oct 30, 2020 10:14

DC_STATUS_DATAFORMAT with i470TC

Post by voets »

I'm trying to download the first 2 dives out of my Aqualung i470TC
Downloading dives works on my phone with the Diverlog+ app, but that is too limited in fucntionality.

The divecomputer is paired to my laptop, and Divinglog sees the right device to start a Bluetooth connection.
But then it fails with error DC_STATUS_DATAFORMAT.
The dumpfile is added below, any ideas how to get the connection working? I'd love to switch to Diving Log, but only if I can actually download my dives.

00:00:000 INFO: 2020-11-01 15:35:20
00:00:001 INFO: Libdivecomputer version: 0.7.0-devel (3e89e1b871d41b42f8411702984cdc20c1d82fc8)
00:00:002 INFO: Diving Log version: 6.0.19.0
00:00:002 INFO: Windows version: Windows 10 ( | Build 19041), 6.3.19041
00:00:003 INFO: OnlyNewDives=False, FingerprintAvailable=False, LastDiveDate=
00:00:003 INFO: Start download (BLE): Aqualung i470TC
00:00:504 INFO: Connecting to: BluetoothLE#BluetoothLE18:5e:0f:0b:57:06-d2:f0:00:00:1a:6a
00:00:741 INFO: 6 services found
00:00:741 INFO: Is paired=True
00:00:741 INFO: Protection level=Encryption
00:00:745 INFO: 6 services found
00:00:745 INFO: 00001801-0000-1000-8000-00805f9b34fb
00:00:745 INFO: 00001800-0000-1000-8000-00805f9b34fb
00:00:746 INFO: 0000180a-0000-1000-8000-00805f9b34fb
00:00:746 INFO: 0000180f-0000-1000-8000-00805f9b34fb
00:00:746 INFO: cb3c4555-d670-4670-bc20-b61dbc851e9a
00:00:746 INFO: 9e5d1e47-5c13-43a0-8635-82ad38a1386f
00:00:746 INFO: Connected to service: cb3c4555-d670-4670-bc20-b61dbc851e9a
00:00:794 INFO: 5 characteristics found
00:00:795 INFO: 5ee30931-ccaa-4870-ab32-6b87ef1f78ed (Read)
00:00:795 INFO: 17738114-18db-467c-b15f-a5bdb84025be (Read)
00:00:795 INFO: 6606ab42-89d5-4a00-a8ce-4eb5e1414ee0 (Read/Write/WriteWithoutResponse)
00:00:796 INFO: a60b8e5c-b267-44d7-9764-837caf96489e (Read/Write/Notify)
00:00:796 INFO: a60b8e5c-b267-44d7-9d65-857bad95479f (Read)
00:04:442 INFO: BLE connected
00:09:896 INFO: BLE connected
00:10:034 INFO: Set Notify: a60b8e5c-b267-44d7-9764-837caf96489e: Success
00:10:035 INFO: Open: transport=32
00:10:035 INFO: Configure: baudrate=38400, databits=8, parity=0, stopbits=0, flowcontrol=0
00:10:036 INFO: Timeout: value=1000
00:10:036 INFO: DTR: value=1
00:10:036 INFO: RTS: value=0
00:10:036 INFO: Sleep: value=100
00:10:137 INFO: RTS: value=1
00:10:138 INFO: Sleep: value=100
00:10:239 INFO: Purge: direction=3
00:10:251 INFO: Write: size=5, data=CD40000184
00:10:283 INFO: Read: size=20, data=CDE000105A415155413437304320314120313032
00:10:284 INFO: Read: size=6, data=CDC10002347F
00:10:285 INFO: Ioctl: request=0x40006200 (dir=1, type=98, nr=0, size=0)
00:10:285 INFO: Ioctl: name=Bluetooth d2:f0:00:00:1a:6a
00:10:286 INFO: Ioctl read: size=9, data=000000000000000000
00:10:293 ERROR: DC_STATUS_DATAFORMAT
00:04:442 INFO: BLE disconnected
00:10:293 INFO: BLE disconnected
voets
Posts: 15
Joined: Fri Oct 30, 2020 10:14

Re: DC_STATUS_DATAFORMAT with i470TC

Post by voets »

Import from divecomputer worked fine using subsurface 4.9.7
Is this an libdivecomputer version issue then?
divinglog
Site Admin
Posts: 5764
Joined: Sat Feb 08, 2003 21:02
Location: Coburg
Contact:

Re: DC_STATUS_DATAFORMAT with i470TC

Post by divinglog »

Hi

I have to ask Jef from libdivecomputer. The problematic line is this:

00:10:286 INFO: Ioctl read: size=9, data=000000000000000000

The Bluetooth device name is not transfered to libdivecomputer, which is causing the error.

Kind regards,
Sven
voets
Posts: 15
Joined: Fri Oct 30, 2020 10:14

Re: DC_STATUS_DATAFORMAT with i470TC

Post by voets »

I tried the Android app, that one can import both dives that are on my watch.
The PC version still throws the same error
divinglog
Site Admin
Posts: 5764
Joined: Sat Feb 08, 2003 21:02
Location: Coburg
Contact:

Re: DC_STATUS_DATAFORMAT with i470TC

Post by divinglog »

Very interesting! Can you send me an error log from Android download? You can activate "Log Errors" in Android in the upper right corner and find the file after a successful download in the "Diving Log" folder in the root of the Android internal storage.

Edit: OK, I think I see what's happening and can send you a workaround later today. Looks like something has changed in the Windows BLE API regarding the device name.

00:10:285 INFO: Ioctl: name=Bluetooth d2:f0:00:00:1a:6a

The device name is just "Bluetooth", but there is an additional Hex string for some reason (d2:f0:00:00:1a:6a).
divinglog
Site Admin
Posts: 5764
Joined: Sat Feb 08, 2003 21:02
Location: Coburg
Contact:

Re: DC_STATUS_DATAFORMAT with i470TC

Post by divinglog »

Please download this zip file and copy the content into the Diving Log 6.0 program folder. Activate "Log Errors" and try to download again. Please send me the error log from here (even if it works):

C:\Users\Admin\AppData\Roaming\Diving Log\DC_FAMILY_XXX.txt

Thank you,
Sven
shiftylilbastrd
Posts: 1
Joined: Mon Nov 02, 2020 20:43

Re: DC_STATUS_DATAFORMAT with i470TC

Post by shiftylilbastrd »

Same computer and problem here's what I get after the patch

00:00:000 INFO: 2020-11-02 20:50:51
00:00:005 INFO: Libdivecomputer version: 0.7.0-devel (7f553c127654c6fc3a4b63c10e5b97c5fb299421)
00:00:010 INFO: Diving Log version: 6.0.19.0
00:00:015 INFO: Windows version: Windows 10 (20H2 | Build 19042), 6.3.19042
00:00:022 INFO: OnlyNewDives=True, FingerprintAvailable=True, LastDiveDate=10/29/2020 12:09:00 PM
00:00:026 INFO: Start download (BLE): Aqualung i470TC
00:00:051 INFO: Paired Bluetooth devices found: 1
00:00:057 INFO: Paired device: Name=GC001108, Address=BluetoothLE#BluetoothLE6c:71:d9:69:c6:be-d2:f0:00:00:12:8b
00:00:061 INFO: Connecting to: BluetoothLE#BluetoothLE6c:71:d9:69:c6:be-d2:f0:00:00:12:8b
00:00:184 INFO: 6 services found
00:00:189 INFO: Is paired=True
00:00:194 INFO: Protection level=Encryption
00:00:199 INFO: 6 services found
00:00:205 INFO: 00001801-0000-1000-8000-00805f9b34fb
00:00:210 INFO: 00001800-0000-1000-8000-00805f9b34fb
00:00:215 INFO: 0000180a-0000-1000-8000-00805f9b34fb
00:00:219 INFO: 0000180f-0000-1000-8000-00805f9b34fb
00:00:224 INFO: cb3c4555-d670-4670-bc20-b61dbc851e9a
00:00:229 INFO: 9e5d1e47-5c13-43a0-8635-82ad38a1386f
00:00:234 INFO: Connected to service: cb3c4555-d670-4670-bc20-b61dbc851e9a
00:00:251 ERROR: Oceanic connect:The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)
00:00:258 ERROR: DC_STATUS_PROTOCOL
divinglog
Site Admin
Posts: 5764
Joined: Sat Feb 08, 2003 21:02
Location: Coburg
Contact:

Re: DC_STATUS_DATAFORMAT with i470TC

Post by divinglog »

Please restart the PC and try again, looks like a temporary issue.
voets
Posts: 15
Joined: Fri Oct 30, 2020 10:14

Re: DC_STATUS_DATAFORMAT with i470TC

Post by voets »

Thanks for picking this up so quickly!

I've installed the patch and restarted my laptop.
It's now throwing DC_STATUS_TIMEOUT

Here's my log:

00:00:000 INFO: 2020-11-03 08:26:51
00:00:000 INFO: Libdivecomputer version: 0.7.0-devel (7f553c127654c6fc3a4b63c10e5b97c5fb299421)
00:00:001 INFO: Diving Log version: 6.0.19.0
00:00:003 INFO: Windows version: Windows 10 (20H1 | Build 19041), 6.3.19041
00:00:003 INFO: OnlyNewDives=True, FingerprintAvailable=False, LastDiveDate=
00:00:004 INFO: Start download (BLE): Aqualung i470TC
00:00:570 INFO: Connecting to: BluetoothLE#BluetoothLE18:5e:0f:0b:57:06-d2:f0:00:00:1a:6a
00:00:855 INFO: 6 services found
00:00:857 INFO: Is paired=True
00:00:860 INFO: Protection level=Encryption
00:00:862 INFO: 6 services found
00:00:864 INFO: 00001801-0000-1000-8000-00805f9b34fb
00:00:864 INFO: 00001800-0000-1000-8000-00805f9b34fb
00:00:864 INFO: 0000180a-0000-1000-8000-00805f9b34fb
00:00:865 INFO: 0000180f-0000-1000-8000-00805f9b34fb
00:00:865 INFO: cb3c4555-d670-4670-bc20-b61dbc851e9a
00:00:865 INFO: 9e5d1e47-5c13-43a0-8635-82ad38a1386f
00:00:866 INFO: Connected to service: cb3c4555-d670-4670-bc20-b61dbc851e9a
00:00:918 INFO: 5 characteristics found
00:00:921 INFO: 5ee30931-ccaa-4870-ab32-6b87ef1f78ed (Read)
00:00:921 INFO: 17738114-18db-467c-b15f-a5bdb84025be (Read)
00:00:921 INFO: 6606ab42-89d5-4a00-a8ce-4eb5e1414ee0 (Read/Write/WriteWithoutResponse)
00:00:921 INFO: a60b8e5c-b267-44d7-9764-837caf96489e (Read/Write/Notify)
00:00:921 INFO: a60b8e5c-b267-44d7-9d65-857bad95479f (Read)
00:12:392 INFO: BLE connected
00:12:505 INFO: Set Notify: a60b8e5c-b267-44d7-9764-837caf96489e: Success
00:12:540 INFO: Open: transport=32
00:12:541 INFO: Configure: baudrate=38400, databits=8, parity=0, stopbits=0, flowcontrol=0
00:12:542 INFO: Timeout: value=1000
00:12:542 INFO: DTR: value=1
00:12:543 INFO: RTS: value=0
00:12:543 INFO: Sleep: value=100
00:12:646 INFO: RTS: value=1
00:12:647 INFO: Sleep: value=100
00:12:758 INFO: Purge: direction=3
00:12:815 INFO: Write: size=5, data=CD40000184
00:22:820 ERROR: BLE read timeout
00:22:821 INFO: Read: size=0, data=
00:22:822 ERROR: Failed to receive the answer. [in oceanic_atom2.c:676 (oceanic_atom2_packet)]
00:22:823 INFO: Sleep: value=100
00:22:940 INFO: Purge: direction=1
00:22:941 INFO: Sleep: value=1
00:22:983 INFO: Write: size=5, data=CD40000184
00:23:111 INFO: Read: size=20, data=CDE000105A415155413437304320314120313032
00:23:111 INFO: Read: size=6, data=CDC10002347F
00:23:112 INFO: Ioctl: request=0x40006200 (dir=1, type=98, nr=0, size=0)
00:23:113 INFO: Ioctl: name=Bluetooth d2:f0:00:00:1a:6a
00:23:114 INFO: Ioctl read: size=9, data=426C7565746F6F7400
00:23:114 INFO: Sleep: value=1
00:23:165 INFO: Write: size=14, data=CD40010AE54535443F3F44000080
00:33:174 ERROR: BLE read timeout
00:33:175 INFO: Read: size=0, data=
00:33:176 ERROR: Failed to receive the answer. [in oceanic_atom2.c:676 (oceanic_atom2_packet)]
00:33:177 INFO: Sleep: value=100
00:33:281 INFO: Purge: direction=1
00:33:282 INFO: Sleep: value=2
00:33:310 INFO: Write: size=14, data=CD40010AE54535443F3F44000080
00:43:316 ERROR: BLE read timeout
00:43:317 INFO: Read: size=0, data=
00:43:319 ERROR: Failed to receive the answer. [in oceanic_atom2.c:676 (oceanic_atom2_packet)]
00:43:319 INFO: Sleep: value=100
00:43:436 INFO: Purge: direction=1
00:43:437 INFO: Sleep: value=3
00:43:476 INFO: Write: size=14, data=CD40010AE54535443F3F44000080
00:53:488 ERROR: BLE read timeout
00:53:489 INFO: Read: size=0, data=
00:53:490 ERROR: Failed to receive the answer. [in oceanic_atom2.c:676 (oceanic_atom2_packet)]
00:53:493 ERROR: DC_STATUS_TIMEOUT
00:56:258 INFO: BLE disconnected
01:06:088 INFO: BLE connected
voets
Posts: 15
Joined: Fri Oct 30, 2020 10:14

Re: DC_STATUS_DATAFORMAT with i470TC

Post by voets »

I also tried downloading dives out of my shearwater Petrel 2 and Perdix Ai
Both are bluetooth too, and both won't connect.
They show up as paired bluetooth devices, but no download happens.

IN the shearwater software I can download the dives without a problem.
Hope this helps in finding the issue
divinglog
Site Admin
Posts: 5764
Joined: Sat Feb 08, 2003 21:02
Location: Coburg
Contact:

Re: DC_STATUS_DATAFORMAT with i470TC

Post by divinglog »

EDIT: Before testing this, please try to unpair and re-pair the dive computer to see if that helps. Send me also an "Error Log" from the Android app, because I think the BLE device name reported by Windows is completely wrong and not just too long.

BEFORE:
Thank you for testing, looks like I cut the device name one byte too short. Please try again with this version this zip file
divinglog
Site Admin
Posts: 5764
Joined: Sat Feb 08, 2003 21:02
Location: Coburg
Contact:

Re: DC_STATUS_DATAFORMAT with i470TC

Post by divinglog »

Shearwater are a different issue which I'm currently looking into. Looks like all BLE issues are related to the latest Windows 10 20H1/H2 updates, which were pushed out recently.
voets
Posts: 15
Joined: Fri Oct 30, 2020 10:14

Re: DC_STATUS_DATAFORMAT with i470TC

Post by voets »

It works!

I have installed your latest version, restarted my laptop.
Then removed the i470tc as a bluetooth device and added it again.

After those steps the import via bluetooth worked fine and I can see all the data of my 2 dives sofar with this computer.

Thanks again for the quick fix
divinglog
Site Admin
Posts: 5764
Joined: Sat Feb 08, 2003 21:02
Location: Coburg
Contact:

Re: DC_STATUS_DATAFORMAT with i470TC

Post by divinglog »

Thank you, great to hear! In think the real fix was the re-pairing and restarting. Looks like it was a temporary Windows issue. About the Shearwater issue, can you please try this version: DivelogTest3.zip

Another user reported via email that this worked for him.
Post Reply