Petrel 2 Download

[Rick Walsh]

Thank you for your help and patience Anton,

On 19 May 2015 at 19:50, Anton Lundin <glance at acc.umu.se> wrote:
> bt-device and bt-adapter are quite nice tools from a old Gsoc project:
> https://code.google.com/p/bluez-tools/
>
> I don't know if they are packaged for Fedora.
>
If they are, it isn't obvious to me what package they're in.

>>
>> [bluetooth]# scan on
>> Discovery started
>> [CHG] Controller 00:15:83:3D:0A:57 Discovering: yes
>> [NEW] Device 00:13:43:0E:6B:D0 Petrel
>> [CHG] Device 00:13:43:0E:6B:D0 RSSI: -70              **I've deleted
>> further similar rows - noise telling me signal strength
>> [bluetooth]# remove 00:13:43:0E:6B:D0
>> [DEL] Device 00:13:43:0E:6B:D0 Petrel
>> Device has been removed
>> [NEW] Device 00:13:43:0E:6B:D0 Petrel
>> [bluetooth]# pair 00:13:43:0E:6B:D0
>> Attempting to pair with 00:13:43:0E:6B:D0
>> Failed to pair: org.bluez.Error.AuthenticationFailed
>> **BT INIT FAIL on Petrel screen, restart upload log timer
>> [bluetooth]# trust 00:13:43:0E:6B:D0
>> [CHG] Device 00:13:43:0E:6B:D0 Trusted: yes          **It appears I
>> need to trust the device
>> Changing 00:13:43:0E:6B:D0 trust succeeded
>> [bluetooth]# remove 00:13:43:0E:6B:D0
>> [DEL] Device 00:13:43:0E:6B:D0 Petrel
>> Device has been removed
>> [bluetooth]# agent on         **I don't know what this actually means,
>> but I manage to get further with agent on
>> Agent registered
>> [bluetooth]# default-agent
>> Default agent request successful
>> [bluetooth]# remove 00:13:43:0E:6B:D0
>> [DEL] Device 00:13:43:0E:6B:D0 Petrel
>> Device has been removed
>> [NEW] Device 00:13:43:0E:6B:D0 Petrel
>> [bluetooth]# trust 00:13:43:0E:6B:D0
>> [CHG] Device 00:13:43:0E:6B:D0 Trusted: yes
>> Changing 00:13:43:0E:6B:D0 trust succeeded
>> [bluetooth]# pair 00:13:43:0E:6B:D0
>> Attempting to pair with 00:13:43:0E:6B:D0
>> Request PIN code
>> [agent] Enter PIN code: 0000        *Trying any other PIN gives BT
>> INIT FAIL on Petrel screen
>> [CHG] Device 00:13:43:0E:6B:D0 Connected: yes
>> [CHG] Device 00:13:43:0E:6B:D0 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
>> [CHG] Device 00:13:43:0E:6B:D0 Paired: yes
>> Pairing successful
>> [CHG] Device 00:13:43:0E:6B:D0 Connected: no     **Countdown on Petrel
>> screen keeps going
>> [bluetooth]# connect 00:13:43:0E:6B:D0
>> Attempting to connect to 00:13:43:0E:6B:D0
>> [CHG] Device 00:13:43:0E:6B:D0 Connected: yes
>> Failed to connect: org.bluez.Error.NotAvailable
>> [CHG] Device 00:13:43:0E:6B:D0 Connected: no    **I can't connect for
>> more than a second or so
>>
>> Does this mean anything to anyone?  This example was using the Petrel
>> supplied dongle - turned on with hcitools, and hci0 (onboard
>> bluetooth) turned off.
>>
>
> Are 00:15:83:3D:0A:57 your external bluetooth dongle? In that case you
> managed to get them paired.
>
> Then you should be able to find your petrel, aka 00:13:43:0E:6B:D0 in
> /var/lib/bluetooth/00:15:83:3D:0A:57/linkkeys
>
> If so, they are correctly paired.


Yes, 00:15:83:3D:0A:57 is the bluetooth dongle that came with the
Petrel, so they are paired.

sudo -i
cat /var/lib/bluetooth/00\:15\:83\:3D\:0A\:57/00\:13\:43\:0E\:6B\:D0/info
[LinkKey]
Key=BBBC168472241C36157DC94FEEC889C1
Type=0
PINLength=0

[General]
Name=Petrel
SupportedTechnologies=BR/EDR;
Trusted=true
Blocked=false
Services=00001101-0000-1000-8000-00805f9b34fb;

>
> Then try to connect via rfcomm:
>
> sudo rfcomm -i 00:15:83:3D:0A:57 connect /dev/rfcomm0 00:13:43:0E:6B:D0
>

Connecting is the bit that doesn't work, either from within
bluetoothctl or with rfcomm.

sudo rfcomm -i 00:15:83:3D:0A:57 connect /dev/rfcomm0 00:13:43:0E:6B:D0
Can't connect RFCOMM socket: Connection refused

I tried with -i hci1 (=00:15:83:3D:0A:57) too just for good luck.
sudo rfcomm -i hci1 connect /dev/rfcomm0 00:13:43:0E:6B:D0
Can't connect RFCOMM socket: Connection refused

I tried running journalctl -f (systemd equivalent to tail -f
/var/log/messages) in a separate terminal, but nothing shows up when
trying to connect the device, except authentication messages that
result from using sudo.

>
> And when the connection is established, you should be able to point your
> universial tool or subsurface to /dev/rfcomm0 and download your dives.
>
>
> //Anton
>
>
> --
> Anton Lundin    +46702-161604

Rick