Skip to contentSkip to conversation

EVT_EXTENDED_INQUIRY_RESULT

Bluez-devel Andreas Faerber 3 participants 8 messages Mar 23, 2006 – Apr 13, 2006 Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

Hello,

We've just received an HCI 2.0 dongle (Belkin/Broadcom) and I've recompiled my periodic scan code (on SuSE 10.1b8 w/BlueZ 2.24) to enable support for EVT_EXTENDED_INQUIRY_RESULT. Unfortunately I still get the "old" EVT_INQUIRY_RESULT only; I could not find an OCF_EXTENDED_PERIODIC_INQUIRY command or the like so my expectation was to simply get back EVT_EXTENDED_INQUIRY_RESULT from OCF_PERIODIC_INQUIRY now that our hardware supports it (and I include it in the filter).

Am I missing anything? Do I need to enable this feature somewhere?

We want either EVT_INQUIRY_RESULT_WITH_RSSI or EVT_EXTENDED_INQUIRY_RESULT because we need to read the RSSI without connecting.

Regards,

Andreas

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

maintainer
#1 lore raw

Hi Andreas,

Quoted 8 lines

We've just received an HCI 2.0 dongle (Belkin/Broadcom) and I've recompiled my periodic scan code (on SuSE 10.1b8 w/BlueZ 2.24) to enable support for EVT_EXTENDED_INQUIRY_RESULT. Unfortunately I still get the "old" EVT_INQUIRY_RESULT only; I could not find an OCF_EXTENDED_PERIODIC_INQUIRY command or the like so my expectation was to simply get back EVT_EXTENDED_INQUIRY_RESULT from OCF_PERIODIC_INQUIRY now that our hardware supports it (and I include it in the filter).

Quoted 5 lines

Am I missing anything? Do I need to enable this feature somewhere?

We want either EVT_INQUIRY_RESULT_WITH_RSSI or EVT_EXTENDED_INQUIRY_RESULT because we need to read the RSSI without connecting.

call "hciconfig hci0 inqmode 1" first to switch the device into the correct inquiry mode. However the extended inquiry will be only supported by Bluetooth 2.1 (aka Lisbon) devices.

You can also check the features with "hciconfig hci0 features" if it tells you it supports inquiry with RSSI. However in case of some Broadcom chips, this doesn't mean anything, because they support it anyway even if the features bit is not set.

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#2 lore raw

Hi Marcel,

Quoted 3 lines

call "hciconfig hci0 inqmode 1" first to switch the device into the correct inquiry mode.

Thanks a lot, that worked!

Quoted 6 lines

You can also check the features with "hciconfig hci0 features" if it tells you it supports inquiry with RSSI. However in case of some Broadcom chips, this doesn't mean anything, because they support it anyway even if the features bit is not set.

The feature is actually listed. The only weird thing I'm still tracking down is that I only get inquiry results every five minutes while it did work as expected with the previous dongles...

Thanks again,

Andreas

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

maintainer
#3 lore raw

Hi Andreas,

Quoted 8 lines
Quoted 5 lines

You can also check the features with "hciconfig hci0 features" if it tells you it supports inquiry with RSSI. However in case of some Broadcom chips, this doesn't mean anything, because they support it anyway even if the features bit is not set.

The feature is actually listed. The only weird thing I'm still tracking down is that I only get inquiry results every five minutes while it did work as expected with the previous dongles...

ask Broadcom, I have no idea. You might wanna try to compare it against a CSR based dongle.

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#4 lore raw

Hi Marcel,

Quoted 8 lines
Quoted 4 lines

The only weird thing I'm still tracking
down is that I only get inquiry results every five minutes while it did work as expected with the previous dongles...

ask Broadcom, I have no idea. You might wanna try to compare it against a CSR based dongle.

The problem has not reappeared today; my period length is set to 30 (*1.28s) now and today the visible repetition of the inquiry results was more around 3 seconds or less... ;-) That's not too bad, we're happy it works at all as a proof of concept.

I did ask you for a recommendation of reference hardware available in Germany some weeks ago on the list but I got no reply. We had a very difficult time finding a supplier of any hardware with HCI >1.1 as webshops or shops like Saturn don't really know about the chipsets and the manufacturers' sites don't always list such details. If you let us know what USB hardware (as opposed to chipset) we should/could use we might consider that.

Best regards,

Andreas

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

maintainer
#5 lore raw

Hi Andreas,

Quoted 13 lines
Quoted 8 lines
Quoted 4 lines

The only weird thing I'm still tracking
down is that I only get inquiry results every five minutes while it did work as expected with the previous dongles...

ask Broadcom, I have no idea. You might wanna try to compare it against a CSR based dongle.

The problem has not reappeared today; my period length is set to 30 (*1.28s) now and today the visible repetition of the inquiry results was more around 3 seconds or less... ;-) That's not too bad, we're happy it works at all as a proof of concept.

Quoted 7 lines

I did ask you for a recommendation of reference hardware available in Germany some weeks ago on the list but I got no reply. We had a very difficult time finding a supplier of any hardware with HCI >1.1 as webshops or shops like Saturn don't really know about the chipsets and the manufacturers' sites don't always list such details. If you let us know what USB hardware (as opposed to chipset) we should/could use we might consider that.

I have been really busy lately and thus I am not able to answer all emails on the BlueZ mailing lists. Hopefully some other people will step in at some point. However you should check my EDR page:

http://www.holtmann.org/linux/bluetooth/edr.html

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#6 lore raw
Quoted 22 lines · Marcel Holtmann

Hi Andreas,

Quoted 12 lines
Quoted 7 lines
Quoted 4 lines

The only weird thing I'm still tracking
down is that I only get inquiry results every five minutes while it did work as expected with the previous dongles...

ask Broadcom, I have no idea. You might wanna try to compare it against a CSR based dongle.

The problem has not reappeared today; my period length is set to 30 (*1.28s) now and today the visible repetition of the inquiry results was more around 3 seconds or less... ;-) That's not too bad, we're happy it works at all as a proof of concept.

Quoted 7 lines

I did ask you for a recommendation of reference hardware available in Germany some weeks ago on the list but I got no reply. We had a very difficult time finding a supplier of any hardware with HCI >1.1 as webshops or shops like Saturn don't really know about the chipsets and the manufacturers' sites don't always list such details. If you let us know what USB hardware (as opposed to chipset) we should/could use we might consider that.

Quoted 6 lines

I have been really busy lately and thus I am not able to answer all emails on the BlueZ mailing lists. Hopefully some other people will step in at some point. However you should check my EDR page:

http://www.holtmann.org/linux/bluetooth/edr.html

in germany karstadt is selling the csr-based cellink bta-6030.

regards
martin

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#7 lore raw

Re: [Bluez-devel] Periodic inquiry issues [was: EVT_EXTENDED_INQUIRY_RESULT]

Hi,

Quoted 1 line · Martin Karger

in germany karstadt is selling the csr-based cellink bta-6030.

We've got our Cellink BTA-6030 with CSR chipset now and the problems are exactly the same as with the Broadcom based dongle. Maybe I'm doing something stupid...?

Let me repeat that this is on SuSE 10.1b8 with BlueZ 2.24 and I'm using HCI to do a periodic inquiry. The oddities from my point of view are the following:

- On our original CSR based D-Link DBT-120 if there's one discoverable device then an inquiry returns this device and then after the specified time period a second time etc. On the Broadcom based Belkin and on the CSR based Cellink the repetition is *irregular* - from subsecond to minutes before and between results. (and the D-Link unfortunately doesn't support inqmode > 0, whereas Belkin inqmodes 1,2 and Cellink inqmode 1) What is the exact relation between max_period, min_period and length within the struct periodic_inquiry_cp and what are recommended value combinations? Could that be the source of the problem? Currently I'm using length < min_period < max_period, e.g. length=30, min_period=31, max_period=45 (have also tried some other numbers) with num_rsp=100 and believe the times to be in units of 1.28 seconds according to the header file comments.

- We are doing the periodic inquiry to get a /live/ RSSI without needing to connect - however the RSSI remains constant (over a long time) even if we walk away with the discovered device... do I need to purge some kind of cache or is this a hardware problem? (observed on multiple/all? devices) I'd expect to see some change on both 10 m and 100 m dongles.

- Both the batostr function and my own C code get the device address as AA:BB:CC:DD:EE:FF (...->bdaddr.b[0..5]) while "hcitool scan" outputs them as 00:FF:EE:DD:CC:BB - could someone please explain this?

I've double-checked array bounds etc. and haven't found a clue. Any hints or ruling-out would be appreciated!

Best regards and Happy Easter,

Andreas

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel