This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

SD130 Packet per interval as central

Hi,

I've been trying to send a batch of data from 2 nRF51-DK boards, peripheral to central, and it seemed that there is a bottleneck on BLE since the buffer on the peripheral side continuously overflows. I have read that on SD120 a central device is limited to accepting only 1 packet/interval. Is this still the case on SD130? Could this be my bottleneck?

Thanks

  • FormerMember
    +1 FormerMember

    The latest version of S130, S130 v.2.0.0, should support up to 6 packets per connection interval when being a central. I would assume that 6 packets per connection interval only is possible to achieve when the S130 device is acting a central only, and with only one peripheral connected.

    When the softdevice specification for S130 v.2.0 has been released, it will be possible to find this information there.

    In order to achieve the maximum bandwidth, the softdevice will have to be configured that way, see release notes:

    The API to configure the bandwidth of BLE connections is now functional. The application can configure the bandwidth of BLE connections with the BLE_OPT_CONN_BW_SET option before the BLE connection is established (DRGN-6468). When using the configurable bandwidth option the application must have specified beforehand, at BLE stack initialization time, a set of connection bandwidth that includes the ones that it intends to use through this option. The sd_ble_gap_connect() and sd_ble_gap_adv_start() SV calls can now return NRF_ERROR_NO_MEM if there is not enough memory to honor the requested bandwidth configuration.

    The S130 v.2.0 API is not out on the infocenter yet, however it should be done the same way as for S132:

    • Use sd_ble_opt_set(..) to set the bandwidth configuration.

    • The bandwidth configuration struct can be found here.

Related