forum.heinrichsweikamp.com

FTDI drivers are installed, device is seen by the PC in the Bluetooth devices.
Any attempt to connect using either OSTC companion, OSTC tools, or Diving Log 6.0, on port COM12 fails and every of those applications just hangs/freezes up.
Bluetooth alone works fine, as my Shearwater Petrel communicates without any issue.

Help would be appreciated.

System - Windows 7/64 bit
OSTC 4 os - 1.1.1

Interestingly, when adding a device to the Bluettooth devices , it offers an option of pairing with a pairing code. Since I haven't found such code anywhere - I presume that the pairing is without code and that's how I used it.

One more thing - after rebooting the PC, and trying to connect from OSTC Companion, it asks for a connection code anyways.

Best regards
gorcio

Hello Gorcio,

A couple of points to your issues:
- You don't need FTDI drivers for Bluetooth OSTC's
- All current OSTC use "Secure Simple Pairing", no pin needed (It's set to 0000, but disabled in the OSTC)

> Any attempt to connect using either OSTC companion, OSTC tools, or Diving Log
> 6.0, on port COM12 fails and every of those applications just hangs/freezes up.

Delete the OSTC5 and Re-Pair with Bluetooth. Then right-click on the OSTC4 and choose "Preferences", check the COM-Port in the "Services" Tab. If there are two ports, always use the "Outgoing" or "SPP" one. If several different Apps freeze when trying to connect, maybe Administrator rights are required for these Apps to access the Bluetooth.

Regards,
Matthias

heinrichsweikamp Wrote:

> A couple of points to your issues:
> - You don't need FTDI drivers for Bluetooth
> OSTC's

understood. But their presence shouldn't cause any issue, right ?

> - All current OSTC use "Secure Simple Pairing", no
> pin needed (It's set to 0000, but disabled in the
> OSTC)

This however happens, will try 0000 just to check it.


> Delete the OSTC5 and Re-Pair with Bluetooth. Then
> right-click on the OSTC4 and choose "Preferences",
> check the COM-Port in the "Services" Tab. If there
> are two ports, always use the "Outgoing" or "SPP"
> one. If several different Apps freeze when trying
> to connect, maybe Administrator rights are
> required for these Apps to access the Bluetooth.

Will try that, probably tomorrow when I get back home.

Best regards

Gorcio

heinrichsweikamp Wrote:

> Delete the OSTC5 and Re-Pair with Bluetooth. Then
> right-click on the OSTC4 and choose "Preferences",
> check the COM-Port in the "Services" Tab. If there
> are two ports, always use the "Outgoing" or "SPP"
> one.

SPP on COM12 is already selected after re-adding it under Bluetooth devices. Then, starting up OSTC Companion shows port COM 13 as Bluetooth port. Connecting on it - freezes the OSTC Companion. Shutting the OSTC COmpanion down, using Diving LOg 6.0 results with what you see in the attachment - nothing happens.

Trying the same for the OSTC settings - access to port COM13 is denied.

INFO: Open: name=COM13
ERROR: Access is denied (5) [in serial_win32.c:169 (dc_serial_open)]
ERROR: Failed to open the serial port. [in hw_ostc3.c:338 (hw_ostc3_device_open)]


INFO: libdivecomputer-0.dll version: 0.5.0-devel

> If several different Apps freeze when trying
> to connect, maybe Administrator rights are
> required for these Apps to access the Bluetooth.

I have full admin rights on the machine.

Ok - connection from Companion solved - conflicting with a Bluetooth mouse dongle.

However, connectivity from Diving Log still keeps failing