bluetooth-usb-dongle failing after 'a while'

[thefullmooner]

Hi All,

I have a bluetooth-usb-dongle which is failing after 'a while'.

' A while' is not futher specified as it may happen after 15min or after a couple of hours but at least once a day.
The only solution i've till today is to unplug and pulg the BT-usb-dongle.

via lsudb i see the follwing:

pi@raspberrypi ~/sma $ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

if i try to scan i get the follwoing result via sudo hcitool scan

pi@raspberrypi ~/sma $ sudo hcitool scan
Scanning ...
Inquiry failed: Connection timed out

Anybody an idea what is going wrong over here?
Or can somebody tell me where i've to look to see more details of what is going wrong or how to debug this isse?

[honda4life]

Same problem here, do a search on "sma", and you will notice some similar issues

What software are you using?

[thefullmooner]

The software i use: http://code.google.com/p/sma-bluetooth/

Is it possible my USB-dongle (high range, 100M, usb2.1) is asking at a certain point (after 'a while') a current which is not possible to deliver by the raspberry pi ?

A powered USB-port might give a solution here or another BT-dongle which consume less power...

just a thought...
I'll keep you posted if I find more info...

[honda4life]

Same problems with class 2 dongles,

Power consumption doesn't exceed 60mA and used a 2,5A power supply.

[thefullmooner]

temp work-a-round.. i'll reboot my raspi a couple of times a day so the BT-device can reset hiself in the correct state.

Code: Select all

in the crontab from root
# this line reboot the RaspPi to reset the BT-device -= BUG work a round :( =-
0 7,11,15,19,23 * * * reboot

[honda4life]

Are you using Sunnybeam also?

[honda4life]

I *think* it's fixed with compiling latest bluez, but let's test another day.

The daemon doesn't start automatic and hci up is also needed.
What I also notice is that the only configuration files are main and rfcomm so it's worth a try to test it with only those files.

new main.conf

Code: Select all

[General]

# List of plugins that should not be loaded on bluetoothd startup
#DisablePlugins = network,input

# Default adaper name
# %h - substituted for hostname
# %d - substituted for adapter id
Name = %h-%d

# Default device class. Only the major and minor device class bits are
# considered.
Class = 0x000100

# How long to stay in discoverable mode before going back to non-discoverable
# The value is in seconds. Default is 180, i.e. 3 minutes.
# 0 = disable timer, i.e. stay discoverable forever
DiscoverableTimeout = 0

# How long to stay in pairable mode before going back to non-discoverable
# The value is in seconds. Default is 0.
# 0 = disable timer, i.e. stay pairable forever
PairableTimeout = 0

# Use some other page timeout than the controller default one
# which is 16384 (10 seconds).
PageTimeout = 8192

# Automatic connection for bonded devices driven by platform/user events.
# If a platform plugin uses this mechanism, automatic connections will be
# enabled during the interval defined below. Initially, this feature
# intends to be used to establish connections to ATT channels.
AutoConnectTimeout = 60

# What value should be assumed for the adapter Powered property when
# SetProperty(Powered, ...) hasn't been called yet. Defaults to true
InitiallyPowered = true

# Remember the previously stored Powered state when initializing adapters
RememberPowered = true

new rfcomm.conf:

Code: Select all

#
# RFCOMM configuration file.
#

#rfcomm0 {
#       # Automatically bind the device at startup
#       bind no;
#
#       # Bluetooth address of the device
#       device 11:22:33:44:55:66;
#
#       # RFCOMM channel for the connection
#       channel 1;
#
#       # Description of the connection
#       comment "Example Bluetooth device";
#}

Edit: Nope

[thefullmooner]

Yes, I am using a sunny boy 5000.

So compiling the latest bluez didn't gave an option?

[Himbeere]

See also here

http://www.raspberrypi.org/phpBB3/viewt ... 37&t=11771

and here

http://www.raspberrypi.org/phpBB3/viewt ... 50&t=11338

@Admins: Perhaps it is possible to "merge" some of these threads ...