• State Verified Answer
  • Replies 2 replies
  • Subscribers 69 subscribers
  • Views 533 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 237166
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Is it impossible to communicate with other peripherals for a certain period of time during scanning?

Sawada

Scan in the background while connected to one Peripheral in a multi-linking central.

In this state, we confirmed that there was a period during which Central could not communicate with the connected peripheral.

Does scanning in the background create such a period of inability to communicate?

Also, it seems that this incommunicable period is related to the value of SCAN_WINDOW. Do you know anything about it?

Parents
  • +1

    Hi,

    It is physically impossible to do both RX and TX at the same time, or to do two different RX at the same time.

    The way the SoftDevice achieves concurrent connection and scanning is by scheduling scan events and connection events after each other. If a scan event and a connection event overlaps, it will choose one or the other according to a set of priorities.

    The length of the scan event is determined by the scan window. If the scan window equals the scan interval it means you scan 100 % of t he time. Then there is no time to fit a connection event.

    For the full picture, please have a look at the Scheduling chapter of the SoftDevice Specification. In particular the Suggested intervals and windows section should be of interest.

    Regards,
    Terje

Reply
  • +1

    Hi,

    It is physically impossible to do both RX and TX at the same time, or to do two different RX at the same time.

    The way the SoftDevice achieves concurrent connection and scanning is by scheduling scan events and connection events after each other. If a scan event and a connection event overlaps, it will choose one or the other according to a set of priorities.

    The length of the scan event is determined by the scan window. If the scan window equals the scan interval it means you scan 100 % of t he time. Then there is no time to fit a connection event.

    For the full picture, please have a look at the Scheduling chapter of the SoftDevice Specification. In particular the Suggested intervals and windows section should be of interest.

    Regards,
    Terje

Children
No Data
Related