Fwd: RE: Shearwater Petrel Download Bug

[Jef Driesen]

On 2014-01-15 00:00, Rodrigo Severo wrote:
> On Tue, Jan 14, 2014 at 8:55 PM, Dirk Hohndel <dirk at hohndel.org> wrote:
>> Silly bluetooth stuff. Did some syntax change or is this just a bug in
>> the manual? I can't easily connect to the native bluetooth from Linux
>> here (I run Mac OS on the hardware and Linux in a VM for a number of
>> reasons)
>> 
> 
> I can't tell for sure as I'm new to Subsurface (and even to bluetooth 
> to be
> truthful).
> 
> "rfcomm bind" never worked for me. "rfcomm connect" always works.
> 
> If nobody else has anything clever to say about it, I would change the
> manual.

The "bind" command associates the /dev/rfcommX with a specific bluetooth 
device (by means of its address). No connections is made. Only when an 
application opens the /dev/rfcommX, the bluetooth stack will attempt to 
connect to the device. The "connect" command will immediately establish 
a connection with to the device.

I have no idea why "bind" doesn't work for you.

Note that you can easily automate the "bind" with the 
/etc/bluetooth/rfcomm.conf configuration file. This is much more 
convenient than having to run the "bind" command every time. I have 
included my rfcomm.conf file as an example.

Jef


#
# RFCOMM configuration file.
#

rfcomm0 {
	# Automatically bind the device at startup
	bind yes;

	# Bluetooth address of the device
	device 00:12:6F:21:6A:CD;

#	# RFCOMM channel for the connection
#	channel	1;

	# Description of the connection
	comment "Heinrichs Weikamp Frog";
}

rfcomm1 {
	# Automatically bind the device at startup
	bind yes;

	# Bluetooth address of the device
	device 00:13:43:04:59:9F;

#	# RFCOMM channel for the connection
#	channel	1;

	# Description of the connection
	comment "Shearwater Petrel";
}