Petrel 2 Download

[Anton Lundin]

On 17 May, 2015 - Rick Walsh wrote:

> >
> > Try bt-device yada connect something and re-pair the computer with your dongle.
> >
> > Link keys are kept by the os so if you paired that device with that dongle under a different os you need to re-pair the devices.
> >
> 
> I don't have (on Fedora 22 beta-ish) bt-device, but I think
> bluetoothctl is the equivalent command.  This is what it does for me.
> I have the Petrel upload load countdown going the whole time, or start
> again when it times out. **are my comments

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.

> 
> [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.

Then try to connect via rfcomm:

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


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