Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NRF52832 BLE_CENTER NUS_C seiver

When I was using a master slave integrated host, when I quickly disconnected the connection and then set up the connection immediately, it was found that the original disconnected connection could also receive data, that is to say, the new connection could receive data, and the old disconnected connection could also receive data.

The host project I used is ble_central_and_peripheral\experimental\ble_app_hrs_rscs_relay

The slave Engineering I used is nRF5_SDK_14.2.0_17b948a\examples\ble_peripheral\ble_app_uart\pca10040

  • Hi!

    I don't quite understand your question.
    Could you please explain a bit closer what you are trying to acheive and what is going wrong?
    Adding details about what SDK version etc. could also be useful information when posting an issue here on DevZone.

    Are you disconnecting a device from your central, and then initiating a connection with a new device?
    But after connecting the new device to the central, the device you disconnected is still connected to the central as well?

    Also, I'm not quite sure what you mean by "BLE_CENTER NUS_C seiver" in the header.

    I'm sorry if I'm misunderstanding.

    Best regards.
     

  • Hi.

    Ok, so you are not using two different slaves? You are just reconnecting the same slave to the central?

    How are you disconnecting the slave from the central?
    And does the disconnection return any errors?

    One possibility could be that you are not waiting long enough for the disconnect event to get returned, before reconnecting.

     

Related