OSTC Sport won't connect for update

128 views
Skip to first unread message

Stephen Hemminger

unread,
Feb 24, 2022, 12:13:33 AM2/24/22
to subsurfac...@googlegroups.com
Bluetooth connection for updating OSTC Sport does not work.
Machine x86-64 12 core with Debian testing (bookworm)
Subsurface 5.0.6

From File->Change Settings on Dive Computer
  Connect via Bluetooth
  Scan (finds device)
  Right click and pair
  Save

Red banner unsupported operation. Other times it gives missing rfcomm

Log on console is
void QBluetoothDeviceDiscoveryAgentPrivate::stop()
Detecting bluetoothd version
Using /proc/<pid>/exe
Using /proc/<pid>/cmdline
Detected bluetoothd version 5.62
Bluetoothd: "5.62"
Using BlueZ LE DBus API
qt_ble_open( 00:80:25:4A:10:77 )
QLowEnergyControllerPrivateBluezDBus::connectToDevice()
###### "org.bluez.Device1" QMap(("Connected", QVariant(bool, true)))
###### "org.bluez.Device1" QMap(("ServicesResolved", QVariant(bool, true)))
BTLE_DBUS::connect() failed "org.bluez.Error.NotAvailable" "br-connection-profile-unavailable"
failed to connect to the controller  00:80:25:4A:10:77 with error "Unknown Error"

Jason Bramwell

unread,
Feb 24, 2022, 1:52:12 AM2/24/22
to subsurfac...@googlegroups.com
How new is this computer? Is it brand new or have you had it a while? The reason I ask is that the newest OSTC computers are built around some different components that need an update that hasn’t yet made it into Subsurface. This only affects the newest OSTC’s though.

Jason

Sent from my iPhone

On 24 Feb 2022, at 05:13, Stephen Hemminger <stephen....@gmail.com> wrote:


--
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/CAJjQ54W3h9p%2BWCNf5%3DzM7VTijQMAypnA3Sdq0RLEGd3FSW%3DSuQ%40mail.gmail.com.

Stephen Hemminger

unread,
Feb 24, 2022, 10:49:04 AM2/24/22
to subsurfac...@googlegroups.com
This is old model. From 2015?

Stephen Hemminger

unread,
Feb 24, 2022, 11:27:52 AM2/24/22
to subsurfac...@googlegroups.com
The longer answer is that this is a early model from 2015.
Finally, getting to dive again, and found it in drawer.
Had not used it in long time and wanted to get firmware updated, and that is proving more difficult than expected.

JB2Cool

unread,
Feb 24, 2022, 11:45:58 AM2/24/22
to Subsurface Divelog
Ok, thanks for the update, i can't really help but being on a testing version of Debian is probably not helping your cause.

To get up and running quickly i'd maybe suggest OSTConf mobile phone app, that's how i typically update my firmware.

Jef Driesen

unread,
Feb 24, 2022, 12:17:42 PM2/24/22
to subsurfac...@googlegroups.com, Stephen Hemminger
The OSTC bluetooth is dual stack. Can you try again and select Bluetooth Classic
instead of Bluetooth Low Energy (BLE) in the Bluetooth mode selection? That's
sometimes a bit more reliable (and faster too) on a PC.

Gmail im Auftrag von Martin Gröger

unread,
Feb 24, 2022, 12:26:25 PM2/24/22
to subsurfac...@googlegroups.com
hm...

it could be that the firmware is a bit too old to get it updated by subsurface or the OSTC companion app.
maybe you should take a look to the HW forum or contact matthias directly

keep on howling

grey

Gmail im Auftrag von Martin Gröger

unread,
Feb 24, 2022, 12:29:08 PM2/24/22
to subsurfac...@googlegroups.com

Stephen Hemminger

unread,
Feb 24, 2022, 2:12:11 PM2/24/22
to subsurfac...@googlegroups.com
Managed to update via Android HwOS config app on Android.

Jason Bramwell

unread,
Feb 24, 2022, 5:05:43 PM2/24/22
to subsurfac...@googlegroups.com
Does this now allow you to communicate with Subsurface? Mine has always been solid on an old OSTC mk2 and 2 different OSTC Plus

Sent from my iPhone

On 24 Feb 2022, at 19:12, Stephen Hemminger <stephen....@gmail.com> wrote:



Stephen Hemminger

unread,
Feb 25, 2022, 3:42:55 PM2/25/22
to subsurfac...@googlegroups.com
I got connection to work, there seems to be a UI issue in the "Configure Dive computer" that might be related.

The following generates error:
   File -> dive settings
   Connect via bluetooth -> right click pair -> Save
 
At this point if I just hit "Advance settings" it gives unsupported red bar.

But if I do "retrieve available details" it works.

If tabs are not available until after first read they should be disabled or a warning should happen first.


Reply all
Reply to author
Forward
0 new messages