nimble doesn't receive 31B scan response

[Ondrej Pilat <on...@ozobot.com>]

Hi All,

we have device which in the past had 29B scan response and nimble
properly asked for it. Now We extended scan response at 31B to use it
whole but now nimble doesn't ask for it. No ble_gap_disc_desc *disc with
disc->event_type === BLE_HCI_ADV_RPT_EVTYPE_SCAN_RSP for our device.

Where can be an issue? Does nimble support 31B scan response?

Regards

Ondrej

-- 

Re: nimble doesn't receive 31B scan response

[Andrzej Kaczmarek <an...@codecoup.pl>]

Hi,

Yes, it will scan only once - this is allowed by spec. I think for testing
you could try to remove the call to "ble_ll_scan_have_rxd_scan_rsp" from
"ble_ll_scan_send_scan_req" and it should scan everything unless you'll run
out of HCI buffers.

Best,
Andrzej


On Tue, May 12, 2020 at 8:17 PM Ondrej Pilat <on...@ozobot.com>
wrote:

> Hi,
>
> does nimble ask for the scan response only once? It looks that it was
> fault in our code and cheap sniffer doesn't catch it :(.
>
> Regards
>
> Ondrej
> Dne 5/12/2020 v 4:51 PM Andrzej Kaczmarek napsal(a):
>
> Hi,
>
> On Tue, May 12, 2020 at 4:05 PM Ondrej Pilat <on...@ozobot.com>
> wrote:
>
>> Hi All,
>>
>> we have device which in the past had 29B scan response and nimble
>> properly asked for it. Now We extended scan response at 31B to use it whole
>> but now nimble doesn't ask for it. No ble_gap_disc_desc *disc with
>> disc->event_type === BLE_HCI_ADV_RPT_EVTYPE_SCAN_RSP for our device.
>>
> The scanner cannot decide whether to send a scan request or not based on
> the length of the scan response because it does not know that length in
> advance. Did you really see that NimBLE does not send a scan request to
> your device? Could be simply that your device does not send a scan response
> or there's something wrong (configuration?) with advertising packets. The
> best would be if you could provide some logs (HCI, air, etc.) that would
> show us how advertising is configured on your device and how the scanner is
> configured in NimBLE.
>
>> Where can be an issue? Does nimble support 31B scan response?
>>
> Yes, it's required by spec.
>
>> Regards
>>
>> Ondrej
>>
> Best,
> Andrzej
>
>
>> --
>>
>
> --
>

Re: nimble doesn't receive 31B scan response

[Ondrej Pilat <on...@ozobot.com>]

Hi,

does nimble ask for the scan response only once? It looks that it was
fault in our code and cheap sniffer doesn't catch it :(.

Regards

Ondrej

Dne 5/12/2020 v 4:51 PM Andrzej Kaczmarek napsal(a):
> Hi,
>
> On Tue, May 12, 2020 at 4:05 PM Ondrej Pilat <ondrej.pilat@ozobot.com
> <ma...@ozobot.com>> wrote:
>
>     Hi All,
>
>     we have device which in the past had 29B scan response and nimble
>     properly asked for it. Now We extended scan response at 31B to use
>     it whole but now nimble doesn't ask for it. No ble_gap_disc_desc
>     *disc with disc->event_type === BLE_HCI_ADV_RPT_EVTYPE_SCAN_RSP
>     for our device.
>
> The scanner cannot decide whether to send a scan request or not based
> on the length of the scan response because it does not know that
> length in advance. Did you really see that NimBLE does not send a scan
> request to your device? Could be simply that your device does not send
> a scan response or there's something wrong (configuration?) with
> advertising packets. The best would be if you could provide some logs
> (HCI, air, etc.) that would show us how advertising is configured on
> your device and how the scanner is configured in NimBLE.
>
>     Where can be an issue? Does nimble support 31B scan response?
>
> Yes, it's required by spec.
>
>     Regards
>
>     Ondrej
>
> Best,
> Andrzej
>  
>
>     -- 
>
>
-- 

Re: nimble doesn't receive 31B scan response

[Andrzej Kaczmarek <an...@codecoup.pl>]

Hi,

On Tue, May 12, 2020 at 4:05 PM Ondrej Pilat <on...@ozobot.com>
wrote:

> Hi All,
>
> we have device which in the past had 29B scan response and nimble properly
> asked for it. Now We extended scan response at 31B to use it whole but now
> nimble doesn't ask for it. No ble_gap_disc_desc *disc with disc->event_type
> === BLE_HCI_ADV_RPT_EVTYPE_SCAN_RSP for our device.
>
The scanner cannot decide whether to send a scan request or not based on
the length of the scan response because it does not know that length in
advance. Did you really see that NimBLE does not send a scan request to
your device? Could be simply that your device does not send a scan response
or there's something wrong (configuration?) with advertising packets. The
best would be if you could provide some logs (HCI, air, etc.) that would
show us how advertising is configured on your device and how the scanner is
configured in NimBLE.

> Where can be an issue? Does nimble support 31B scan response?
>
Yes, it's required by spec.

> Regards
>
> Ondrej
>
Best,
Andrzej


> --
>