Central peripheral BLE address connection check

RE: Central peripheral BLE address connection check

Edvin — Tue, 16 Apr 2019 10:45:37 GMT

Hello,

In the disconnected event you should have a conn_handle.

case BLE_GAP_EVT_DISCONNECTED:
NRF_LOG_INFO("Disconnected conn_handle %d", p_ble_evt->evt.gap_evt.conn_handle);
...

You can compare this conn_hande to the conn_handle that occured in the BLE_GAP_EVT_CONNECTED event. The connected event has both a conn_handle and an address.

So let us say that in the BLE_GAP_EVT_CONNECTED event you had conn_handle 0x01 and address 0xea88a2c41a92.

Then, later, you get a disconnect with conn_handle 0x01, this means that the device with address 0xea88a2c41a92 disconnected.

Best Regards,

Edvin

RE: Central peripheral BLE address connection check

yokokawa — Tue, 16 Apr 2019 06:05:32 GMT

I misunderstood the BLE address, but I thought that the number specified at the time of transmission was the BLE address.
When BLE communication is disconnected, the disconnected communication number can not be known.
When BLE communication is disconnected, the BLE address "p_gap_evt-> conn_handle" is always "0x00" in "BLE_NUS_C_EVT_DISCONNECTED", so it is not possible to know the disconnected number.
Please tell me how to check the disconnection number.

RE: Central peripheral BLE address connection check

Jimmy Wong — Thu, 11 Apr 2019 05:21:47 GMT

The address is 0xea88a2c41a92 (if you are using the nRF52 as central).

RE: Central peripheral BLE address connection check

Jimmy Wong — Thu, 11 Apr 2019 05:21:47 GMT

The address is 0xea88a2c41a92 (if you are using the nRF52 as central).

RE: Central peripheral BLE address connection check

yokokawa — Thu, 11 Apr 2019 05:03:23 GMT

"P_connected-> peer_addr.addr"
I checked the value of, but I do not know what it represents.
【Reading result】
[0]: 0x92
[1]: 0x1a
[2]: 0xc4
[3]: 0xa2
[4]: 0x88
[5]: 0xea
Please tell me the judgment method.

Is there a function to return connection status when BLE address is specified?

RE: Central peripheral BLE address connection check

Jimmy Wong — Thu, 11 Apr 2019 02:56:12 GMT

hi,

You get peer address at BLE_GAP_EVT_CONNECTED event (see ble_gap_evt_connected_t structure).

You can use the scan module if you are using the SDK 15.3. (it has the scan module).

https://github.com/jimmywong2003/nrf5-ble-multiple-role-example/blob/master/ble_app_lbs_nus_its_multi-role/main.c

/**@brief Function for handling Scaning events.
 *
 * @param[in]   p_scan_evt   Scanning event.
 */
static void scan_evt_handler(scan_evt_t const * p_scan_evt)
{
        ret_code_t err_code;

        switch(p_scan_evt->scan_evt_id)
        {
        case NRF_BLE_SCAN_EVT_CONNECTING_ERROR:
                err_code = p_scan_evt->params.connecting_err.err_code;
                APP_ERROR_CHECK(err_code);
                break;

        case NRF_BLE_SCAN_EVT_CONNECTED:
        {
                ble_gap_evt_connected_t const * p_connected =
                        p_scan_evt->params.connected.p_connected;
                // Scan is automatically stopped by the connection.
                NRF_LOG_INFO("Connecting to target 0x%02x%02x%02x%02x%02x%02x",
                             p_connected->peer_addr.addr[0],
                             p_connected->peer_addr.addr[1],
                             p_connected->peer_addr.addr[2],
                             p_connected->peer_addr.addr[3],
                             p_connected->peer_addr.addr[4],
                             p_connected->peer_addr.addr[5]
                             );
        } break;