Bluetooth blues

[Rick Walsh]

On 24 Oct 2015 00:51, "Claudiu Olteanu" <olteanu.vasilica.claudiu at gmail.com>
wrote:
>
> > I was under the impression that the Petrel 2 and the Uemis were your
test
> > devices when coding the Bluetooth interface and that access to the
Petrel 2
> > has more or less been sorted out?? Am I mistaken?
>
> I have only two devices: OSTCs and OSTC 2. Rick helped me to test the
> connectivity with a Petrel 2 device.
>
> > Do you know whether the Petrel 2 definitely needs a pin number?
> I have no idea. You can test it using the bluetoothctl tool. Here is an
example:
>
> $ bluetoothctl
> [bluetooth]# agent KeyboardOnly
> Agent registered
> [bluetooth]# default-agent
> Default agent request successful
> [bluetooth]# pair 00:13:43:0D:21:0D
> Attempting to pair with 00:13:43:0D:21:0D
> [CHG] Device 00:13:43:0D:21:0D Connected: yes
> Request PIN code
> [agent] Enter PIN code: 0000
>
> If it doesn't need a PIN code, then the last part will be missing.

I have tested my petrel 2 with two laptop  onboard Bluetooth controllers
and 3 usb Bluetooth controllers.

>From memory, with one of the usb controllers, I needed to enter the PIN
0000 (using bluetoothctl or KDE's bluetooth ui) to pair.  With the others I
didn't need to enter a PIN.  I guess the PIN 0000 was assumed when pairing
with the other controllers.

R
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20151024/95c0fc84/attachment.html>