Characteristics when connecting a peripheral to central

RE: Characteristics when connecting a peripheral to central

Petter Myhre — Tue, 03 Jan 2017 12:21:44 GMT

I see, you want to get characters as well. Then maybe you can try one of the two following suggestions:

Modify the nRF LOG backend interface library so that the characters are relayed to the application. Please compare uart_event_handler() inside nrf_log_backend_serial.c in ble_app_hrs and uart_event_handler() inside app_uart_fifo.c in ble_app_uart.
Use RTT as serial backend instead of UART, and implement the functionality in ble_app_uart in the same way in ble_app_hrs.

RE: Characteristics when connecting a peripheral to central

John — Fri, 30 Dec 2016 13:20:04 GMT

Yes, but I want the uart_event handle to work which is how I can have UART in the HRS relay example. Is there a way to incorporate that without have uart_init()?

RE: Characteristics when connecting a peripheral to central

Petter Myhre — Thu, 29 Dec 2016 09:34:34 GMT

Can't you just print the address using NRF_LOG_INFO instead of printf?

RE: Characteristics when connecting a peripheral to central

John — Wed, 28 Dec 2016 19:22:31 GMT

Hi Petter, one question that could potentially solve it for me. How do I call the uart_event_handle without the uart_init because I have NRF_LOG_INFO instead of printf()? This is part of the APP_UART_FIFO_INIT(&comm_params, UART_RX_BUF_SIZE, UART_TX_BUF_SIZE, uart_event_handle, APP_IRQ_PRIORITY_LOW, err_code);

RE: Characteristics when connecting a peripheral to central

John — Wed, 28 Dec 2016 15:16:15 GMT

This is how I have it set up:

case BLE_GAP_EVT_ADV_REPORT: {

        if (strlen(m_target_periph_name) != 0)
        {
            if (find_adv_name(&p_gap_evt->params.adv_report, m_target_periph_name))
            {
                // Initiate connection.
                err_code = sd_ble_gap_connect(&p_gap_evt->params.adv_report.peer_addr,
                                              &m_scan_params,
                                              &m_connection_param);
                if (err_code != NRF_SUCCESS)
                {
                    NRF_LOG_INFO("Connection Request Failed, reason %d\r\n", err_code);
                }
            }
        }
					
					
        else
        {
           /** We do not want to connect to two peripherals offering the same service, so when
            *  a UUID is matched, we check that we are not already connected to a peer which
            *  offers the same service. */
						
						const ble_gap_evt_adv_report_t * p_adv_report = &p_gap_evt->params.adv_report;
						
            if ((is_uuid_present(&m_adv_uuids[0], p_adv_report)))
								
            {
                // Initiate connection.
                err_code = sd_ble_gap_connect(&p_adv_report->peer_addr,
                                              &m_scan_params,
                                              &m_connection_param);
								
								
                if (err_code == NRF_SUCCESS)
            {
                
                printf("Connecting to target %02x%02x%02x%02x%02x%02x\r\n",
                         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; // BLE_GAP_ADV_REPORT

The problem is trying to get the UUID characteristics to show up in the UART terminal such as Termite when inputting buttons on a peripheral device. The NRF52 board should act as a central and peripheral.So that is why I am trying to incorporate the UART example with HRS relay example.

RE: Characteristics when connecting a peripheral to central

Petter Myhre — Wed, 28 Dec 2016 14:49:04 GMT

Can't you just do something like this when you receive an advertising report:

    case BLE_GAP_EVT_ADV_REPORT:
    {
        const ble_gap_evt_adv_report_t * p_adv_report = &p_gap_evt->params.adv_report;

        if (is_uuid_present(&m_nus_uuid, p_adv_report))
        {
            err_code = sd_ble_gap_connect(&p_adv_report->peer_addr,
                                          &m_scan_params,
                                          &m_connection_param);
            APP_ERROR_CHECK(err_code);
        }
    }break;

Instead of checking the name like you are doing now. I'm have trouble understand what the problem is, maybe I'm misunderstanding you?

RE: Characteristics when connecting a peripheral to central

John — Wed, 28 Dec 2016 14:37:37 GMT

That is what I was doing with the ble_app_hrs_c example by trying to put UART from ble_app_uart_c because it is not really working with regards to finding the UUID. However, it works when you put the m_target_periph_name[] as I said before. What parts do I have to add for the ble_app_hrs_c, I have incorporated the UART portions from the example, but I am not sure if it is everything. Can you check my code out that I provided above, if possible. Thanks.

RE: Characteristics when connecting a peripheral to central

Petter Myhre — Wed, 28 Dec 2016 14:11:49 GMT

I'm not saying that you have to use the ble_app_uart_c example, but you can port parts of it to the ble_app_hrs_c, or add peripheral role to the ble_app_uart_c example. Up to you.

RE: Characteristics when connecting a peripheral to central

Petter Myhre — Wed, 28 Dec 2016 14:10:30 GMT

Yes, it is possible, but then you must add the peripheral part to it of course.

RE: Characteristics when connecting a peripheral to central

John — Wed, 28 Dec 2016 13:58:22 GMT

I could do that but I want it so that the NRF52 board acts as both a central and peripheral which is similar to the HRS relay example. Is that possible to do that with the ble_app_uart_c example?

RE: Characteristics when connecting a peripheral to central

Petter Myhre — Wed, 28 Dec 2016 09:39:24 GMT

Can't you just do as in the ble_app_uart_c example? And look for the UUID instead of the name.

RE: Characteristics when connecting a peripheral to central

John — Tue, 27 Dec 2016 15:46:41 GMT

Actually, I don't think ble_nus_c_rx_notif_enable() is the main problem as I was working on it yesterday. First, I tried to figure out how to incorporate is_uuid_present() from the UART example instead of find_adv_uuid() from the HRS example. It is because I have a 128 bit UUID from my peripheral device. I think if I can get that connected by UUID, then it should get the characteristics. However, right now I am only connected with m_target_periph_name[] from the HRS example with specifying the device name. Any ideas how I can incorporate the UUID in the HRS example? The code that I provided is what I have so far.

RE: Characteristics when connecting a peripheral to central

Petter Myhre — Tue, 27 Dec 2016 10:53:52 GMT

ble_nus_c_rx_notif_enable() doesn't work? Does it return an error code?