BLE manual connect and Disconnect

RE: BLE manual connect and Disconnect

Einar Thorsrud — Fri, 16 Nov 2018 08:37:56 GMT

I do not immediately see the problem. But going back to your post from two days ago you wrote that there is a system reset. As I mentioned, that is typically due to an error check so seeing which error check was hit and what the error code was will typically show you the issue in a few minutes. Can you check that? (You can refer to this blog post for an intro into error handling in the SDK if that is new to you).

RE: BLE manual connect and Disconnect

Murugan — Fri, 16 Nov 2018 06:29:35 GMT

yes, already tested same like your comment. Here with enclosed my code, i dont know what i am doing wrong . please guide me.

devzone.nordicsemi.com/.../18418.main.c

RE: BLE manual connect and Disconnect

Einar Thorsrud — Thu, 15 Nov 2018 14:40:32 GMT

Yes, you can adjust the scan parameters and filters runtime. But you have to stop scanning by calling nrf_ble_scan_stop() before you reconfigure.

RE: BLE manual connect and Disconnect

Murugan — Thu, 15 Nov 2018 11:40:40 GMT

possible to change scan filter while running time ? because while scanning i will set UUID scaning , when establish connection i will set UUID and ADDR both scanning. The above examples are one time initialization process, i want to random scan initialization. Is this possible ?

RE: BLE manual connect and Disconnect

Einar Thorsrud — Thu, 15 Nov 2018 08:35:16 GMT

It should be straight-forward. You can see how it is used in two examples in SDK 15.2:

examples\ble_central\ble_app_gatts\main.c (around line 693)
examples\ble_central\ble_app_hrs_c\main.c (around line 882)

RE: BLE manual connect and Disconnect

Murugan — Thu, 15 Nov 2018 04:40:57 GMT

i want to know filter settings are correct based on SCAN_ADDR_FILTER ?

RE: BLE manual connect and Disconnect

Einar Thorsrud — Wed, 14 Nov 2018 13:47:21 GMT

Hi,

If the system goes to reset that is typically due to an APP_ERROR_CHECK. If you build debug version of the project and use logging, you should see which file, line and error code triggered this.

RE: BLE manual connect and Disconnect

Murugan — Wed, 14 Nov 2018 09:50:16 GMT

@Einar Thorsrud as per your suggestion set init_scan.connect_if_match = false scan the device list then try to connect like below

init_scan.connect_if_match = true;
init_scan.conn_cfg_tag = APP_BLE_CONN_CFG_TAG;

err_code = nrf_ble_scan_init(&m_scan, &init_scan, scan_evt_handler);
APP_ERROR_CHECK(err_code);

err_code = nrf_ble_scan_filter_set(&m_scan, SCAN_ADDR_FILTER, &GI8u_Device_List[GI8u_Device_ID-1][0]);
APP_ERROR_CHECK(err_code);

err_code = nrf_ble_scan_filters_enable(&m_scan, NRF_BLE_SCAN_ADDR_FILTER, false);
APP_ERROR_CHECK(err_code);

after calling this function the system goes to reset. I thing filter setting may be wrong ?. please help further process.

RE: BLE manual connect and Disconnect

Murugan — Wed, 14 Nov 2018 07:48:57 GMT

now scanning process ok. little error in ble_evt_handler i am just modified ble_gap_evt_adv_report_t const * p_adv_report to ble_gap_evt_adv_report_t const * p_adv_report= &p_gap_evt->params.adv_report.

then i will try connection process in case any issue i will come back. Thank you.

RE: BLE manual connect and Disconnect

Murugan — Wed, 14 Nov 2018 07:39:54 GMT

also i am tried as per your suggestion set init_scan.connect_if_match = false and add some code in ble_evt_handler like below

case BLE_GAP_EVT_ADV_REPORT:

ble_gap_evt_adv_report_t const * p_adv_report;
uint16_t data_len;
data_len = p_adv_report->data.len;

if (ble_advdata_name_find(p_adv_report->data.p_data,data_len,"Nordic_UART"))
{

NRF_LOG_INFO("Scan Device %02x%02x%02x%02x%02x%02x",
p_adv_report->peer_addr.addr[0],
p_adv_report->peer_addr.addr[1],
p_adv_report->peer_addr.addr[2],
p_adv_report->peer_addr.addr[3],
p_adv_report->peer_addr.addr[4],
p_adv_report->peer_addr.addr[5]
);
}

break;

but unable to process ble_advdata_name_find () this function.

RE: BLE manual connect and Disconnect

Murugan — Wed, 14 Nov 2018 04:43:15 GMT

in SDK12.3.0 i have complete my requirement. Function on_ble_evt have BLE_GAP_EVT_ADV_REPORT field, here i will do filter name(p=strstr((const char *)p_adv_report->data,"Nordic_UART")) , list the peripherals and connect if match UUID (is_uuid_present(&m_nus_uuid, p_adv_report)). but i dont have option in SDK15.2.0 .

RE: BLE manual connect and Disconnect

Einar Thorsrud — Tue, 13 Nov 2018 11:45:10 GMT

I see. Then, referring to NUS central example, you should do the initial scanning with connect_if_match set to false to find all peripherals that match your criteria. Then when you subsequently want to connect to a specific peripheral you adjust the criteria so that it only matches one of them (typically filtering on the BLE address using SCAN_ADDR_FILTER). Then set connect_if_match to true before you start to scan so that it will connect to the peripheral with the specific address.

RE: BLE manual connect and Disconnect

Murugan — Tue, 13 Nov 2018 07:29:28 GMT

Thanks for reply. connection and disconnection ok , but I want to collect the peripheral list and choose one from the list for connection. Here when we start scan its automatically connected.

Flow : 1) Start Scan 2) List the peripheral 3) Choose one from list for connection 4) Then Disconnect when we need

RE: BLE manual connect and Disconnect

Einar Thorsrud — Mon, 12 Nov 2018 10:14:40 GMT

Hi,

The ble_app_uart_c example uses the scan module and configures it so that it will automatically connect if it finds a peripheral with the NUS service. If you want to control weather to connect or disconnect yourself I would say that the most natural would be to modify the example so that it only calls scan_start() (which in turn calls nrf_ble_scan_start()) when you want to connect, or instance after a button press. You may also want to stop scanning after a timeout or for another reason. In that case you can call nrf_ble_scan_stop(). Similarly you could use a button press to decide if you should call sd_ble_gap_disconnect() to disconnect (allready implemented in the example, just search for BSP_EVENT_DISCONNECT).