Hi, On Tue, May 12, 2020 at 4:05 PM Ondrej Pilat <ondrej.pi...@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 > -- >
