custom_ble_service_example - LED's

RE: custom_ble_service_example - LED's

Simon — Thu, 30 Aug 2018 15:15:48 GMT

thank-you

RE: custom_ble_service_example - LED's

haakonsh — Thu, 30 Aug 2018 09:12:41 GMT

One option is to track the SDK with Git and make a branch for each "project". Then you can safely make small modifications to the SDK without it impacting other projects. I suggest you use the master branch as an unaltered version of the SDK, and only include the components and example folders in order to keep the size down.

RE: custom_ble_service_example - LED's

Simon — Sun, 26 Aug 2018 01:30:26 GMT

Switched to ble_app_template in sdk 15.0 to test again, and I'm looking for all the disconnects that have start_advertisment.
The disconnect event that seems to trigger before the disconnect in main, is in ble_advertising.c:

case BLE_GAP_EVT_DISCONNECTED:
on_disconnected(p_advertising, p_ble_evt);
break;

When disconnecting, the on_disconnected in ble_advertising.c will execute and cause LED_1 to blink very faintly. If you try to comment this line, then the program seems to go into sleep_mode after the disconnected event in main. By adding ble_advertising_start to disconnected in main.c seems to give better control over the LEDs when advertising again.

But since this is an sdk file now all the examples that advertise are now affected with this comment. How then not to have to edit an sdk file and keep advertising control in main for each specific example?

thank-you,

In ble_advertising.c, 

        case BLE_GAP_EVT_DISCONNECTED:
            //on_disconnected(p_advertising, p_ble_evt);
            break;

In main.c, 


        case BLE_GAP_EVT_DISCONNECTED:
            NRF_LOG_INFO("Disconnected.");
           //LED indication will be changed when advertising starts.

          //Add BSP_INDICATE_IDLE to stop advertising LED 1 		
            err_code = bsp_indication_set(BSP_INDICATE_IDLE);
            APP_ERROR_CHECK(err_code);

          //If you comment "on_disconnected(p_advertising, p_ble_evt);" 
          //in ble_advertising.c, then LED_2 below will not be reached.		
            nrf_gpio_cfg_output(LED_2);
            nrf_gpio_pin_set(LED_2);
            nrf_gpio_pin_clear(LED_2);
            nrf_delay_ms(500);
            nrf_gpio_pin_set(LED_2);

          //Add ble_advertising_start to start advertising LED 1 		
            ret_code_t err_code = ble_advertising_start(&m_advertising, BLE_ADV_MODE_FAST);
            APP_ERROR_CHECK(err_code);

            break;

        case BLE_GAP_EVT_CONNECTED:
            NRF_LOG_INFO("Connected.");

//            err_code = bsp_indication_set(BSP_INDICATE_CONNECTED);
//            APP_ERROR_CHECK(err_code);

            //When you comment the line above, BSP_INDICATE_CONNECTED, 
            //and do not set BSP_INDICATE_IDLE, then LED_1 will blink 
            //like it is advertising!!!	
            err_code = bsp_indication_set(BSP_INDICATE_IDLE);
            APP_ERROR_CHECK(err_code);

            nrf_gpio_cfg_output(LED_3);
            nrf_gpio_pin_set(LED_3);
            nrf_gpio_pin_clear(LED_3);
            nrf_delay_ms(500);
            nrf_gpio_pin_set(LED_3);

            m_conn_handle = p_ble_evt->evt.gap_evt.conn_handle;
            err_code = nrf_ble_qwr_conn_handle_assign(&m_qwr, m_conn_handle);
            APP_ERROR_CHECK(err_code);
            break;

RE: custom_ble_service_example - LED's

gercer — Fri, 24 Aug 2018 19:32:22 GMT

If you want to change which LED turns on you have to modify bsp_config.h (around line 110). If you want the LED_3 turn on instead of LED_1, change BSP_BOARD_LED_0 (which is LED 1) to BSP_BOARD_LED_2 (LED_3) for each of the status you wanna modify.

RE: custom_ble_service_example - LED's

haakonsh — Thu, 09 Aug 2018 09:06:57 GMT

Search your project for any call to start_advertisment() or whatever call is used to start advertisements, and then make sure it's only present in one of the on_disconnected event handlers and once to start the first advertisements of course.

RE: custom_ble_service_example - LED's

Simon — Thu, 09 Aug 2018 02:06:42 GMT

I've been able to stay within main.c without having to edit the SDK file bsp.c so as not to have the LED's overlap, except for when it comes to Disconnect.

RTT output: (app: Disconnect -* is just a label to help identify location in code)
-->> when clicking Connect in nrf connect
0> <info> app: Disconnect - ble_evt_handler
0> <info> app: Disconnect - default

-->> when clicking Disconnect in nrf connect
0> <info> app: Disconnect - on_adv_evt
0> <info> app: Fast advertising. <<<---- advertising already comes on
0> <info> app: Disconnect - ble_cus_on_ble_evt
0> <info> app: BLE event received. Event type = 17
0>
0> <info> app: Disconnect - on_disconnect <<<--- from ble_cus.c
0> <info> app: Disconnect - ble_evt_handler
0> <info> app: Disconnected. <<<--- disconnect led is then executed from main.c
--->>> Fast advertising should come here after Disconnected, and not before for the LED's not to overlap

On the DK you can faintly see the advertising LED1 already going on and off as the disconnect routine is still executing.

How to get advertising to only start after completing disconnect?

thank-you,

devzone.nordicsemi.com/.../54752.main.c

RE: custom_ble_service_example - LED's

Simon — Tue, 07 Aug 2018 05:42:08 GMT

almost there, now to understand why when clicking disconnect it goes quickly into fast advertising before disconnecting (according to RTT)

RE: custom_ble_service_example - LED's

haakonsh — Mon, 06 Aug 2018 13:15:04 GMT

If you want to change the behavior of the BSP then you need to go to where bsp_indication_set(BSP_INDICATE_CONNECTED) in bsp.c and change it there.