Using the new Connection State module to decide role

RE: Using the new Connection State module to decide role

run_ar — Wed, 25 Nov 2015 14:44:30 GMT

I think it's either this or add one more || to BLE_GAP_ROLE_CENTRAL like this:
else if ((role == BLE_GAP_ROLE_CENTRAL)
|| (p_ble_evt->header.evt_id == BLE_GAP_EVT_ADV_REPORT
|| (p_ble_evt->header.evt_id == BLE_GAP_EVT_TIMEOUT))

RE: Using the new Connection State module to decide role

Chris — Wed, 25 Nov 2015 10:14:55 GMT

Thanks. I assume it's because there is no connection so p_ble_evt->evt.gap_evt.conn_handle is set to BLE_CONN_HANDLE_INVALID

RE: Using the new Connection State module to decide role

run_ar — Wed, 25 Nov 2015 10:08:00 GMT

I'll check the connection state module to see why you get BLE_GAP_ROLE_INVALID.

RE: Using the new Connection State module to decide role

Chris — Wed, 25 Nov 2015 10:06:47 GMT

I'm not sure if this is the "best" answer but I've added the following to the end of my ble_evt_dispatch function:

...
else if (p_ble_evt->header.evt_id == BLE_GAP_EVT_TIMEOUT)
{  
    ble_advertising_on_ble_evt(p_ble_evt);
    on_ble_central_evt(p_ble_evt);
    on_ble_peripheral_evt(p_ble_evt);
}

The advertising, central and peripheral event handlers can then decide who should handle the timeout based on the value of p_gap_evt->params.timeout.src

RE: Using the new Connection State module to decide role

run_ar — Wed, 25 Nov 2015 10:03:36 GMT

So ble_gap_evt_timeout_t contains the src data fields(source). This will give you the GAP Timeout sources.

In the Relay example we handle
BLE_GAP_TIMEOUT_SRC_ADVERTISING in ble_advertising_on_ble_evt,
BLE_GAP_TIMEOUT_SRC_CONN are handled in on_ble_central_evt.
BLE_GAP_TIMEOUT_SRC_SCAN are not handled as there is no timeout configured in the example, so this would have to be stopped using sd_ble_gap_scan_stop.
BLE_GAP_TIMEOUT_SRC_SECURITY_REQUEST is not handled in the experimental release of the peer manager, but we have a task to add this to the "production" release.

If you want to handle BLE_GAP_TIMEOUT_SRC_SCAN I suggest you do this in on_ble_central_evt. Note that connecting and scanning is only used in the central role (or observer role for scanning), which is why this is handled as a central event. Check src like this:
if (p_gap_evt->params.timeout.src == BLE_GAP_TIMEOUT_SRC_CONN)

RE: Using the new Connection State module to decide role

Eric Stutzenberger — Tue, 24 Nov 2015 18:47:30 GMT

Hmm. I wonder if this is invalid operation by the SDK. BLE_GAP_EVT_TIMEOUT occurs for both Scanning timeout and Advertising timeout. However, in your case, I am not sure how the code is supposed to determine if BLE_GAP_EVT_TIMEOUT comes from a scanning timeout or from an Advertising timeout. If your peripheral advertising never times out, then you could work on the assumption that the timeout is always from scanning and never from advertising. Then you could handle it as a special case. My guess is that there is someway of determining that the timeout is from the central that doesn't depend on the role function since, as you said, this event is always a connectionless event.