Duplicate Events - Periph + Central Database Discovery SDK14

RE: Duplicate Events - Periph + Central Database Discovery SDK14

LukeC — Fri, 23 Feb 2018 18:26:24 GMT

One issue that has come up from the SDK14 and the way it handles the events to the services is that my NUS Central was receiving events from the NUS Peripheral.

I added this to my ble_nus_c_on_ble_evt. I did the opposite for the ble_nus_on_ble_evt. Perhaps there is a recommended my to do this other than this but this seems to work for me.

    uint16_t conn_handle = p_ble_evt->evt.gap_evt.conn_handle;
    uint16_t role = ble_conn_state_role(conn_handle);

    // Based on the role this device plays in the connection, dispatch to the right handler.
    if (role == BLE_GAP_ROLE_PERIPH )
    {
        return;
    }

RE: Duplicate Events - Periph + Central Database Discovery SDK14

LukeC — Fri, 16 Feb 2018 17:51:28 GMT

Edvin,

Thanks, that is helpful to understand how the events are being setup using the macros.

The issue I believe was that I used the BLE_DB_DISCOVERY_ARRAY_DEF(m_ble_db_discovery, 2);from the dual mode example when I should have just used the single discovery instance of LE_DB_DISCOVERY_DEF(m_ble_db_discovery);

RE: Duplicate Events - Periph + Central Database Discovery SDK14

Edvin — Thu, 15 Feb 2018 10:09:41 GMT

Hello,

If you look in the SDK14\examples\ble_central\ble_nuc_c example you can see that there is no function called ble_event_handler. There is also no dispatch function, like there was in the older SDKs.

From SDK14.0.0, the instances are initialized in the macros near the top of the main.c file, such as BLE_NUS_C_DEF(m_ble_nus_c). You can see in the definition of this macro(in ble_nus_c.h), that the event handler is set here, ble_nus_c_on_ble_evt(). Therefore, you do not need to include the ble_nuc_c_on_ble_evt() function in ble_event_handler(). It is already set up when you initialize the ble_nuc_c instance in the BLE_NUS_C_DEF macro.

Best regards,
Edvin