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

CONN_SUP_TIMEOUT issue in ble_app_multilink_peripheral

danbujak

I am able to set the connection timeout to 250ms in the ble_app_hrs peripheral sample, but in the ble_app_multilink_peripheral it will not advertise if I set it below 1000ms as below:

#define CONN_SUP_TIMEOUT                   MSEC_TO_UNITS(1000, UNIT_10_MS)

What could the reason for this be?

Parents
  • 0

    Because there are restrictions on the connection timeout vs the connection interval and slave latency in the BTLE spec.

    And it probably doesn't just 'not advertise' it probably goes into the error handler as a result of error checking the return from the advertising call. It really helps if people put a breakpoint in the error handler and see when the code has crashed out with an error which can then be traced back to the call which emitted it.

Reply
  • 0

    Because there are restrictions on the connection timeout vs the connection interval and slave latency in the BTLE spec.

    And it probably doesn't just 'not advertise' it probably goes into the error handler as a result of error checking the return from the advertising call. It really helps if people put a breakpoint in the error handler and see when the code has crashed out with an error which can then be traced back to the call which emitted it.

Children
Related
Terms of service