• State Verified Answer
  • Locked Locked
  • Replies 1 reply
  • Subscribers 62 subscribers
  • Views 781 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 110322
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Advertising processing too long => crash

Fabien Comte

Hello,

I do connections between nRF51 in my application.

When the central detect an advertising frame, it ask to a server is the device is allowed (few ms). When server response is late, the central crash on connection try. Is there any way to have a longer connection window ? Avoid crashing ?

Thank you.

  • 0

    I assume you are using a softdevice in your nRF51 application.

    I'm not sure that I understand the problem, is the CONNECT_REQ packet send too late?

    The softdevice will not issue the CONNECT packet immediately after the 'sd_ble_gap_connect' call is performed. It will make sure to time the packet correctly (150 micro seconds after ADV).

    Do you have a sniffer trace?

Related

core_v2_widget.Hide()