Re: one question on BLE device authentication error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Christina,

On Sun, Apr 7, 2013 at 2:23 AM, Huang, Christina
<christina.huang@xxxxxxxxx> wrote:
>
> Hi, Anderson
>
> I met one more issue on connecting with Wahoo BlueSC BLE speed / cadence sensor device, it could be discovered successfully, while fails in connection and reports error " Command Disallowed ". Could you suggest what I could do to allow the "connect" command?
> I found this same issue reported before but no available answer.
> http://www.spinics.net/lists/linux-bluetooth/msg30681.html

How are you doing the device discovery? You should use the BlueZ D-Bus
API instead of "hcitool lescan", because some (most?) BLE controllers
do not allow connection creation while in LE scanning state. If I
remember correctly, If the D-Bus API is always used the LE scan is
always disabled prior to LE Create Connection.

Also make sure you are not in advertising state (i.e. you did not run
"hciconfig hci0 leadv").

Best Regards,
-- 
Anderson Lizardo
Instituto Nokia de Tecnologia - INdT
Manaus - Brazil
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux