Can't "save changes to device" with 4.9.3 and OSTC Sport

32 views
Skip to first unread message

Dmitry Burstein

unread,
Sep 30, 2019, 12:56:17 PM9/30/19
to Subsurface Divelog
SD: 4.9.3
OS: Fedora 30, kernel: 5.2.17
DC: OSTC Sport 2nd gen. (black buttons), FW: 10.61

Can connect with BT, can read the dives, can "retrieve available details" from the DC, but when changing the safety stop's start depth and trying to save it back to the device, the "configure dive computer" dialog reports an error, and then the program becomes unresponsive and has to be force killed. When asked to save the DC log file, got a file of 15G - so I'm not sure you want it :)
I'm not sure the problem is Linux specific, but your Android app doesn't have the configure DC option (would be nice ;), and I haven't tried the Windows version yet (can try later if you need me to).
Thanks ahead!

Dmitry Burstein

unread,
Jun 13, 2020, 8:28:16 PM6/13/20
to Subsurface Divelog
A year later, the problem still exists.
By now it's:
    SD: 4.9.4
    OS: Fedora 32, kernel: 5.6.16
    DC: OSTC Sport 2nd gen. (black buttons), FW: 10.67
Now Subsurface remains responsive, but still reports an error when trying to save the changed data back to the dive computer.
Log file attached.

subsurface.log

Grey Wolf

unread,
Jun 14, 2020, 1:33:00 AM6/14/20
to subsurfac...@googlegroups.com
hi

just asking: why you don't  change the value in the settings of the OSTC itself?
my OSTC plus sometimes does the same. some values can be changed by subsurface, some not.

but you can ask matthias in the ostc-forum. 


greez

martin

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/2c10e2af-9571-44b2-907d-b0323138b910o%40googlegroups.com.

Dmitry Burstein

unread,
Jun 14, 2020, 4:17:38 AM6/14/20
to Subsurface Divelog
Unfortunately, this particular value can not be changed through the DC's interface itself.
BTW, I have successfully changed it a few years ago with Subsurface, but it was with earlier versions of the program (and the firmware).
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-divelog+unsub...@googlegroups.com.

Grey Wolf

unread,
Jun 14, 2020, 8:37:48 AM6/14/20
to subsurfac...@googlegroups.com
by the way....
you can not change the depth of the safty-stop - it is fixed

keep on howling
grey

To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/c8efc852-d442-4793-ba07-b27184bd957eo%40googlegroups.com.

Jason Bramwell

unread,
Jun 14, 2020, 9:01:28 AM6/14/20
to subsurfac...@googlegroups.com

I’ve change the stop depth of my OSTS Plus via Subsurface. I think it used to kick in at 5m but now it kicks in at 6m.

 

JB

 

Sent from Mail for Windows 10

Grey Wolf

unread,
Jun 14, 2020, 11:10:05 AM6/14/20
to subsurfac...@googlegroups.com
@6m??

sounds strange to me.....
it seems there is some chaos in the settings of the dc..

but.......
look into the deco-settings. is there the last stop at 6m?

have you read the manual?

keep on howling
grey

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/5ee61fa4.1c69fb81.c47ed.3b43%40mx.google.com.

Jason Bramwell

unread,
Jun 14, 2020, 11:36:23 AM6/14/20
to subsurfac...@googlegroups.com
Yes, I have my last deco stop set to 6m but I also wanted my safety stop set to 6m too so my deco dives would have a similar final stop to my no-deco dives, Subsurface allowed me to make this change and it works how I want it.

It’s not for everyone but it works for me.

Jb

Sent from my iPhone

On 14 Jun 2020, at 16:10, Grey Wolf <megr...@gmail.com> wrote:



Dmitry Burstein

unread,
Jun 14, 2020, 8:15:34 PM6/14/20
to Subsurface Divelog
Yep - this is exactly what I've done with mine in the past. However after some firmware update all the settings got reset, and now I'm unable to change it again :(

To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-divelog+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.

To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-divelog+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.

To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-divelog+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-divelog+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-divelog+unsub...@googlegroups.com.

Grey Wolf

unread,
Jun 14, 2020, 11:01:22 PM6/14/20
to subsurfac...@googlegroups.com
hi folks

you may be right - but I think it's not a subsurface issue. you can ask here: https://forum.heinrichsweikamp.com/

or contakt matthias directly by mail.


keep on howling

grey

To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.

To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.

To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/9b270bf3-6cf6-4a0e-a838-b01fef70c521o%40googlegroups.com.

Jef Driesen

unread,
Jun 16, 2020, 8:20:33 AM6/16/20
to subsurfac...@googlegroups.com, Dmitry Burstein
On 14/06/2020 02:28, Dmitry Burstein wrote:
> [7.234194] INFO: Write: size=1, data=69
> [7.254154] INFO: Read: size=1, data=69
> [7.254157] INFO: Read: size=64, data=79310A43446D69747279202020202020427572737465696E202020204020202020202020202020206E657473636170652E6E6574202020202020202020202020
> [7.254159] INFO: Read: size=1, data=4D
> [25.195177] INFO: Write: size=1, data=77
> [28.323475] INFO: Read: size=0, data=
> [28.323478] ERROR: Failed to receive the echo. [in hw_ostc3.c:295 (hw_ostc3_transfer)]
> [66.081502] INFO: Write: size=1, data=77
> [69.234715] INFO: Read: size=0, data=
> [69.234718] ERROR: Failed to receive the echo. [in hw_ostc3.c:295 (hw_ostc3_transfer)]
> [74.978193] INFO: Write: size=1, data=FF
> [77.827520] INFO: Read: size=0, data=
> [77.827524] ERROR: Failed to receive the echo. [in hw_ostc3.c:295 (hw_ostc3_transfer)]
> [77.827567] ERROR: Failed to send the command. [in hw_ostc3.c:557 (hw_ostc3_device_close)]

Based on the timings in the log, one possible reason for the failure is that the
dive computer timed out and closed the bluetooth connection. There is about 18
seconds of inactivity between the last successful read and the first write, and
another 38 seconds for the second write attempt.

Does it work when you save immediately?

Jef

Dmitry Burstein

unread,
Jun 16, 2020, 9:22:51 AM6/16/20
to Subsurface Divelog
No, it's not the case: I can see on DC's screen it's still connected. For you to be sure I'm attaching a new log file with just a few seconds in between read and write.
subsurface.log

JB2Cool

unread,
Jul 13, 2020, 12:49:50 PM7/13/20
to Subsurface Divelog
I can replicate this now, here is the last little snippet from my log

[6.066180] INFO: Read: size=1, data=72
[6.066212] INFO: Write: size=1, data=35
[6.105231] INFO: Read: size=1, data=00
[6.105262] INFO: Read: size=1, data=4D
[6.105362] INFO: Write: size=1, data=72
[6.147758] INFO: Read: size=1, data=72
[6.147787] INFO: Write: size=1, data=42
[6.162796] INFO: Read: size=1, data=00
[6.162815] INFO: Read: size=1, data=4D
[6.162872] INFO: Write: size=1, data=69
[6.200059] INFO: Read: size=1, data=69
[6.200076] INFO: Read: size=64, data=1E47030B4A2E4272616D77656C6C2020303739363120393535303737202020202020202020202020202020202020202020202020202020202020202020202020
[6.200085] INFO: Read: size=1, data=4D
[11.300768] INFO: Write: size=1, data=77
[14.154188] INFO: Read: size=0, data=
[14.154205] ERROR: Failed to receive the echo. [in hw_ostc3.c:301 (hw_ostc3_transfer)]
[23.044147] INFO: Write: size=1, data=FF
[26.104500] INFO: Read: size=0, data=
[26.104693] ERROR: Failed to receive the echo. [in hw_ostc3.c:301 (hw_ostc3_transfer)]
[26.104708] ERROR: Failed to send the command. [in hw_ostc3.c:589 (hw_ostc3_device_close)]

This was fine with the 3.07 firmware and Subsurface 4.9.3 but broken with 3.11 firmware and Subsurface 4.9.4 and 4.9.5 (for some reason 4.9.3 cannot see my bluetooth dongle so i can't test with that but 99% sure that would fail too).

Snippet from Subsurface stdout

Updating ManufacturerData for "72:ED:A2:97:2B:BD"
Updating RSSI for "CC:6E:A4:FC:40:C9" QVariant(short, -91)
Updating RSSI for "24:4B:03:A4:38:4C" QVariant(short, -73)
Updating RSSI for "67:A5:DB:C2:D9:04" QVariant(short, -59)
Updating RSSI for "CC:6E:A4:FC:40:C9" QVariant(short, -86)
Updating RSSI for "24:4B:03:A4:38:4C" QVariant(short, -65)
Updating RSSI for "67:A5:DB:C2:D9:04" QVariant(short, -59)
void QBluetoothDeviceDiscoveryAgentPrivate::stop()
Detecting bluetoothd version
Using /proc/<pid>/exe
Using /proc/<pid>/cmdline
Detected bluetoothd version 5.53
Bluetoothd: "5.53"
Using Bluetooth dbus socket implementation
Linux Bluez connecting to Uuid "{00001101-0000-1000-8000-00805f9b34fb}"
Registering client profile on "/qt/btsocket/Subsurface4249/3128692857" with options:
QMap(("Name", QVariant(QString, "QBluetoothSocket-4249"))("Role", QVariant(QString, "client"))("Service", QVariant(QString, "00001101-0000-1000-8000-00805f9b34fb")))
Profile Context: New Connection
QObject: Cannot create children for a parent that is in a different thread.
(Parent is QNativeSocketEngine(0xa9c49e0), parent's thread is QThread(0x1c9d0b0), current thread is ReadSettingsThread(0xab39ab0)
[16.052414] ERROR: Failed to receive the echo. [in /__w/subsurface/libdivecomputer/src/hw_ostc3.c:295 (hw_ostc3_transfer)]
[96.109602] ERROR: Failed to receive the echo. [in /__w/subsurface/libdivecomputer/src/hw_ostc3.c:295 (hw_ostc3_transfer)]
[96.110464] ERROR: Failed to send the command. [in /__w/subsurface/libdivecomputer/src/hw_ostc3.c:557 (hw_ostc3_device_close)]
Destroying QtBluezDiscoveryManager

Computer says:
Starting...done.
Download Mode enabled

Regards
Jason Bramwell

Dmitry Burstein

unread,
Jul 15, 2020, 3:58:51 PM7/15/20
to Subsurface Divelog
I'm on 4.9.6 and FW 10.67 now. The problem still exists.


On Monday, September 30, 2019 at 7:56:17 PM UTC+3, Dmitry Burstein wrote:
Reply all
Reply to author
Forward
0 new messages