Hi all! Just tested the BT on my OSTC Sport.
Version: Subsurface-4.6-Beta-2-x86_64.AppImage OS: Debian GNU/Linux 8.6 (jessie) So far everything worked fine (unfortunately only after a few tries) At first I always have to "redo" the BT connection every time.. That means whenever I start subsurface and want to download dives the "Device or mount point" in the windows looks like "00:80:25:49:F9:4D" a connection with this entry is not possible. I first have to start the "Remote bluetooth device selection" and scan for the OSTC Sport again, select the discovered device and click on OK. Then the MAC Number from the "Device or mount point" changed to "OSTCs 12100" and everything works again. Unfortunately if I close the download window and open it again - the "device and mount point" again switched to show only the MAC address (which is again not working for connections) and I have to rescan again. Sometimes (to me it seems I tried too fast) it also says "Error registering the event handler" or even "Insufficient privileges to open the device 00:80:25:49:F9:4D Heinrichs Weikamp (OSTC Sport)". But now back to the good news. I updated the firmware from 10.26 to 10.31 without any problems. It told me that my firmware is old - I gave it a try and .. now its 10.31 - so no problems so far with a firmware update. Though I had again some connection problems while assigning the first connection. The output from console is the following: ./Subsurface-4.6-Beta-2-x86_64.AppImage can't find Qt localization for locale "en-GB" searching in "/usr/share/qt5/translations" Plugins Directory: QDir( "/tmp/.mount_mHiOKe/usr/bin" , nameFilters = { "*" }, QDir::SortFlags( Name | IgnoreCase ) , QDir::Filters( Dirs|Files|Drives|AllEntries ) ) qt.bluetooth.bluez: void QBluetoothSocketPrivate::_q_readNotify() 33 error: -1 "Resource temporarily unavailable" Connection on channel 1 failed. Trying on channel number 5. Failed to connect to device 00:80:25:49:F9:4D . Device state QBluetoothSocket::UnconnectedState . Error: QBluetoothSocket::UnknownSocketError [9.469210] ERROR: Failed to open the serial port. [in ../../src/hw_ostc3.c:344 (hw_ostc3_device_open)] qt.bluetooth.bluez: Bluez 5 detected. qt.bluetooth.bluez: Creating QtBluezDiscoveryManager qt.bluetooth.bluez: Discovered: "00:80:25:49:F9:4D" "OSTCs 12100" Num UUIDs 5 total device 0 cached RSSI 0 Class 7936 qt.bluetooth.bluez: void QBluetoothDeviceDiscoveryAgentPrivate::stop() The connection on RFCOMM channel number 1 took more than expected. Wait another 15 seconds. [5.890507] ERROR: Unsupported command. [in ../../src/hw_ostc3.c:217 (hw_ostc3_transfer)] The connection on RFCOMM channel number 1 took more than expected. Wait another 15 seconds. qt.bluetooth.bluez: void QBluetoothSocketPrivate::_q_readNotify() 30 error: -1 "Resource temporarily unavailable" Failed to connect to device 00:80:25:49:F9:4D . Device state QBluetoothSocket::UnconnectedState . Error: QBluetoothSocket::UnknownSocketError [17.275994] ERROR: Failed to open the serial port. [in ../../src/hw_ostc3.c:344 (hw_ostc3_device_open)] [2.074706] ERROR: Unsupported command. [in ../../src/hw_ostc3.c:217 (hw_ostc3_transfer)] QObject::connect: No such slot ConfigureDiveComputer::dc_close() qt.bluetooth.bluez: void QBluetoothSocketPrivate::_q_readNotify() 24 error: -1 "Resource temporarily unavailable" Connection on channel 1 failed. Trying on channel number 5. The connection on RFCOMM channel number 5 took more than expected. Wait another 15 seconds. qt.bluetooth.bluez: void QBluetoothSocketPrivate::_q_readNotify() 24 error: -1 "Resource temporarily unavailable" Failed to connect to device 00:80:25:49:F9:4D . Device state QBluetoothSocket::UnconnectedState . Error: QBluetoothSocket::UnknownSocketError [6.039782] ERROR: Failed to open the serial port. [in ../../src/hw_ostc3.c:344 (hw_ostc3_device_open)] Hope this helps a bit. regards Werner On 08/01/17 21:54, Dirk Hohndel wrote: > >> On Jan 8, 2017, at 12:50 PM, Stefan Fuchs <sfu...@gmx.de >> <mailto:sfu...@gmx.de>> wrote: >> >> Hi All, >> >> Am 07.01.2017 um 21:13 schrieb Dirk Hohndel: >>> >>>> On Jan 7, 2017, at 12:01 PM, Stefan Fuchs <sfu...@gmx.de >>>> <mailto:sfu...@gmx.de>> wrote: >>>> >>>> Hallo Dirk, >>>> >>>> >>>> Am 07.01.2017 um 20:40 schrieb Dirk Hohndel: >>>>> >>>>> OK, so that's a USB device, not BT. One of my concerns is our BT >>>>> support - I'm hoping that the newer version of Qt that I switched >>>>> to won't give us any regressions, but of course you never know... >>>>> >>>> I will be able to recruit at least one OSTC (2C?!) BT beta tester. >>>> Wolf (in copy) will test the 4.6 beta 2 tomorrow and give some feedback. >>> >> Wolf sent me a WhatsApp this afternoon that he successfully tested the >> download via BT as well. >> Setup: >> - Win 10 >> - OSTC 2 "new", hwOS 2.09 >> - Bluetooth via a bt dongle >> >> All his dives were downloaded successfully. > > Thank you so much. That really helps me feel more confident about a release. > > /D > > > _______________________________________________ > subsurface mailing list > subsurface@subsurface-divelog.org > http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface > _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface