This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

BLE peripheral+observer role SCAN duration in connection status

Other Parts Discussed in Thread: CC2540

Hi,

I make the device(CC2540) to be the peripheral & observer role and let the device to be connected by the BLE dongle. I wonder to know the scan duration of BLE device in the connection status. I thought that the "scan duration" is related to the "connection interval". 

When the connection interval is 1000ms , then the scan duration have to larger than 1000ms in order to find the broadcaster. If the scan duration is less than the connection interval, the device cannot find the anything.

So what is the consideration between the connection interval and scan duration in the connection status?

And is the scan duration would block the connection interval?

THKS

  • Hi,

    When scanning inside a connection, the scan interval/window does influence the scanning, but it's also impacted by the fact that the radio must be reconfigured for the active connection every Conn Int. Scanning in this mode is sort of a 'background task'.

    Scan duration shouldn't really influence this, but if the broadcaster doesn't broadcast very often it's possible that, since you can't scan 100% of the time when connected, that you miss some of the broadcasts.

    BR,
    Aslak
  • Thank you for your reply.

    As you say that the scan duration is "background task", then the priority of connection event is higher than scan event. But I do the experiment does not like that.

    Experiment setting:

    >connection interval=1000ms

    >scan window = 20ms

    >scan interval = 20ms

    >scan duration =3000ms

    I send packet every one second.

    The result is that when I do scan work, the sending packet would miss for the while. And I don't know the blocking time and do not the reason.

    Thank you