Deleting peers

RE: Deleting peers

Simonr — Mon, 18 Jan 2021 07:53:59 GMT

I didn't notice that it's the same file_id that's deleted, but that's strange indeed. I also see that you start scanning before the peers are deleted successfully. Can you please try waiting to start the radio until the PM_EVT_PEER_DELETE_SUCCEEDED event has occurred to avoid the undefined state I mentioned.

Best regards,

Simon

RE: Deleting peers

DmitrySol — Fri, 15 Jan 2021 10:21:13 GMT

Hi. Simon.

DEBUG was added already for logs above.
Deleted file id's are the same.
Is it not strange?
(Deleted File_id=0x5500 - in both deleting cases.)
Hanging up is strange too.

BR.

RE: Deleting peers

Simonr — Fri, 15 Jan 2021 10:06:57 GMT

Can you also add the debug log here by adding DEBUG to your preprocessor definitions? From this log it seems like you successfully delete two peers, so it is strange if only one of them were deleted.

Best regards,

Simon

RE: Deleting peers

DmitrySol — Thu, 14 Jan 2021 14:34:52 GMT

After restart was seen one peer was deleted another was not deleted.

RE: Deleting peers

DmitrySol — Thu, 14 Jan 2021 14:31:12 GMT

Log below shows how system hangs up.

Firstly were connected two devices.
Disconnections were performed.
pm_peers_delete was executed.
After that system is in hang up state.

<info> app: BLE_GAP_EVT_RSSI_CHANGED: 1 rssi=--63dBm ch_index=0x6
<info> app: BLE_GAP_EVT_RSSI_CHANGED: 0 rssi=--56dBm ch_index=0x6

<info> app: sd_ble_gap_disconnect result 0
<info> app: BLE_GAP_EVT_RSSI_CHANGED: 0 rssi=--50dBm ch_index=0x29
<info> app: ble_nus_c_evt_handler(): conn_handle=0x2000, evt_type=0x2
<info> app: Scanning start
<info> app: BLE_GAP_EVT_DISCONNECTED: 0 , reason=0x16

<info> app: sd_ble_gap_disconnect result 0
<info> app: Scanning start
<info> app: BLE_GAP_EVT_ADV_REPORT peer_id=0x0
<info> app: Start_connection for Bonded peer
<info> app: BLE_GAP_EVT_RSSI_CHANGED: 1 rssi=--62dBm ch_index=0x6
<info> app: ble_nus_c_evt_handler(): conn_handle=0x2000, evt_type=0x2
<info> app: Scanning start
<info> app: BLE_GAP_EVT_DISCONNECTED: 1 , reason=0x16

<info> app: pm_peers_delete result 0
<info> app: Scanning start
<error> peer_manager_handler: Peer deleted successfully: peer_id: 0
<info> app: PM_EVT_PEER_DELETE_SUCCEEDED: peer_id=0x0
<info> app: Deleted File_id=0x5500
<info> app: Event: FDS_EVT_DEL_FILE received (FDS_SUCCESS)
<error> peer_manager_handler: Peer deleted successfully: peer_id: 0
<info> app: PM_EVT_PEER_DELETE_SUCCEEDED: peer_id=0x0
<info> app: Deleted File_id=0x5500
<info> app: Event: FDS_EVT_DEL_FILE received (FDS_SUCCESS)

RE: Deleting peers

Simonr — Thu, 14 Jan 2021 10:37:30 GMT

Can you please specify where exactly the system "hangs up"? Do you get any error in return when trying to debug this? Please make sure you are not connected to any of the peer devices you're trying to delete as there's a chance you end up in an undefined state if you're trying to delete the bonding information of a connected device.

Best regards,

Simon

RE: Deleting peers

DmitrySol — Thu, 14 Jan 2021 10:22:32 GMT

Deleting one by one device is working (pm_peers_delete()).
But deleting all devices by pm_peers_delete() hangs up all system without any logs.

RE: Deleting peers

Ivan Herrera — Wed, 25 Nov 2020 17:20:44 GMT

Yes, you need to wait before the actual disconnected event before you can delete the bond. You should be able to run sd_ble_gap_disconnect in rapid succession for all your current handles without any issue, but you should always verify the return code.

RE: Deleting peers

DmitrySol — Wed, 25 Nov 2020 13:50:06 GMT

Hello!

Thanks for replay.

 if (m_conn_handle != BLE_CONN_HANDLE_INVALID)
                {
                    err_code = sd_ble_gap_disconnect(m_conn_handle, 0x13);
                    APPL_LOG("sd_ble_gap_disconnect result %08lX", err_code);
                }
                else
                {
                    APPL_LOG("No physical link exists with peer");
                }

do I need to wait event of disconnecting before delete ?

could i run ten times this sd_ble_gap_disconnect(m_conn_handle, 0x13) for ten connected handles in central simultaenously ?

RE: Deleting peers

Simonr — Wed, 25 Nov 2020 06:57:57 GMT

An example on how to disconnect using button 4 on the DK can be seen in the ble_app_ipsp_initiator example. Please see the button_event_handler() function, more specifically the BSP_BUTTON_3. I have also added the snippet below. It will also return a log message "No physical link exits with peer" if there are no current connections.

/**@brief Function for handling button events.
 *
 * @param[in]   pin_no         The pin number of the button pressed.
 * @param[in]   button_action  The action performed on button.
 */
static void button_event_handler(uint8_t pin_no, uint8_t button_action)
{
    uint32_t err_code;
    if (button_action == APP_BUTTON_PUSH)
    {
        switch (pin_no)
        {
            case BSP_BUTTON_0:
            {
                if (m_conn_handle == BLE_CONN_HANDLE_INVALID)
                {
                    err_code = sd_ble_gap_connect(&m_peer_addr,
                                                  &m_scan_param,
                                                  &m_connection_param,
                                                  APP_IPSP_TAG);

                    if (err_code != NRF_SUCCESS)
                    {
                        APPL_LOG("Connection Request Failed, reason 0x%08lX", err_code);
                    }
                    APP_ERROR_CHECK(err_code);
                }
                else
                {
                     APPL_LOG("Connection exists with peer");
                }

                break;
            }
            case BSP_BUTTON_1:
            {
                if (m_conn_handle != BLE_CONN_HANDLE_INVALID)
                {
                    ble_ipsp_handle_t ipsp_handle;
                    ipsp_handle.conn_handle = m_conn_handle;
                    err_code = ble_ipsp_connect(&ipsp_handle);
                    APP_ERROR_CHECK_BOOL((err_code == NRF_SUCCESS) ||
                                         (err_code == NRF_ERROR_BLE_IPSP_CHANNEL_ALREADY_EXISTS));
                }
                else
                {
                     APPL_LOG("No physical link exists with peer");
                }
                break;
            }
            case BSP_BUTTON_2:
            {
                err_code = ble_ipsp_disconnect(&m_handle);
                APPL_LOG("ble_ipsp_disconnect result %08lX", err_code);
                break;
            }
            case BSP_BUTTON_3:
            {
                if (m_conn_handle != BLE_CONN_HANDLE_INVALID)
                {
                    err_code = sd_ble_gap_disconnect(m_conn_handle, 0x13);
                    APPL_LOG("sd_ble_gap_disconnect result %08lX", err_code);
                }
                else
                {
                    APPL_LOG("No physical link exists with peer");
                }
                break;
            }
            default:
                break;
        }
    }
}

Best regards,

Simon

RE: Deleting peers

DmitrySol — Tue, 24 Nov 2020 07:51:05 GMT

Good day!

Could you show example how to disconnect all peripherals from central.

Before using pm_peers_delete().

RE: Deleting peers

Simonr — Tue, 24 Nov 2020 07:11:19 GMT

As Ivan says, pm_peers_delete() is a function deleting all data stored for all peers. As for the disconnections, you do this however you like, for example by calling a sd_ble_gap_disconnect event.

Best regards,

Simon

RE: Deleting peers

DmitrySol — Mon, 23 Nov 2020 14:04:46 GMT

is any simple way to disconnect all connected to central devices?

and to guaranty disabling of connecting?

disabling ble operating for some time at all for example...

RE: Deleting peers

Ivan Herrera — Mon, 23 Nov 2020 13:57:06 GMT

You need to be disconnected from any peers you want to delete, and make sure they aren't able to connect during the small time-period you are deleting the bonds. You can remove all bonds on the device by running pm_peers_delete(), but the same warning applies to this function.