SparkFun Forums 

Where electronics enthusiasts find answers.

All things pertaining to wireless and RF links
By orlox
#47528
Hi. I aquired three witilt v3 accelerometers and I've been trying to connect to them via bluetooth in ubuntu (linux).

I can't seem to get this working (never had much experience on using bluetooth...).

When i use hcitool to scan for devices, the accelerometer appears (it's named as FireFly-D427, FireFly-D42B or FireFly-D41D dependig on wich of my three accelerometers is on):

pablo@pablo-desktop:/dev$ hcitool scan
Scanning ...
00:06:66:00:D4:27 FireFly-D427

I don't know how to set a connection to this device...If I try to use gnome bluez utilities, I get the error message:

"Can't show «obex://[00:06:66:00:D4:1D]/». Error: host down. Select another viewer and try again."

Any help on how to get a succesfull connection, and on how to start the terminal after the connection is achieved would be very appreciated.

Thanks!
By orlox
#47536
SOLVED!

I set up my /etc/bluetooth/rfcomm file as:
Code: Select all
rfcomm0 {
        # Automatically bind the device at startup
        bind yes;
 
        # Bluetooth address of the device
        device 00:06:66:00:D4:2B; # FireFlyD42B
        # RFCOMM channel for the connection
        channel 1;
 
        # Description of the connection
        comment "D42B accelerometer";
}
rfcomm1 {
        # Automatically bind the device at startup
        bind yes;
 
        # Bluetooth address of the device
        device 00:06:66:00:D4:1D; # FireFlyD41D
        # RFCOMM channel for the connection
        channel 1;
 
        # Description of the connection
        comment "D41D accelerometer";
}
rfcomm2 {
        # Automatically bind the device at startup
        bind yes;
 
        # Bluetooth address of the device
        device 00:06:66:00:D4:27; # FireFlyD427
        # RFCOMM channel for the connection
        channel 1;
 
        # Description of the connection
        comment "D427 accelerometer";
}
and then run
Code: Select all
sudo rfcomm bind all
this generates the /dev/rfcomm0, /dev/rfcomm1, /dev/rfcomm2 to wich I can connect using minicom.