Make communication between ble central and ble peripheral

RE: Make communication between ble central and ble peripheral

Sigurd — Thu, 15 Feb 2018 08:45:03 GMT

Hi vprasath,

When the peripheral devices connects to your central, you will get a event BLE_GAP_EVT_CONNECTED. In this event you can find the 48-bit BLE address of the peripheral

p_ble_evt->evt.gap_evt.params.connected.peer_addr

While the device is connected, you can then use the associated connection handle to identify the device. p_ble_evt->evt.gap_evt.conn_handle

RE: Make communication between ble central and ble peripheral

vprasath — Wed, 14 Feb 2018 13:46:08 GMT

Hi,

Where can i get the unique bluetooth address of peripheral device when it is connected to the central?

My application needs the unique bluetooth address of the peripheral,so that the central can identify each peripheral.

Thank You

RE: Make communication between ble central and ble peripheral

Sigurd — Tue, 19 Sep 2017 12:25:53 GMT

NUS_BASE_UUID is the base for the Nordic UART Service(NUS) UUID.

The peripheral(ble_app_uart) is advertising this BLE service NUS UUID in its advertising packet. When the central(ble_app_uart_c) is scanning, you will get a BLE_GAP_EVT_ADV_REPORT event with the content of any advertising packet it finds. The central application then calls the function is_uuid_present(), where it looks for the NUS UUID. If the UUID is found, it will connect to the peripheral.

You can use the same UUID on all your peripherals. The most common way to uniquely identify the peripherals is by using the unique Bluetooth address of the peripheral device. You could also give the peripherals different names(DEVICE_NAME), the default name for ble_app_uart example is Nordic_UART.

RE: Make communication between ble central and ble peripheral

lakshmi — Mon, 18 Sep 2017 07:12:53 GMT

Thank you for your response,

I referred the ble_app_uart_c for central.In that,NUS_BASE_UUID having 128-bit UUID value.Is that the peripheral UUID?But,in my task,the incoming uart data contains the UUID information about the peripheral device which I need to connect now.So while the uart event occurs,I am extracting the UUID information and then I connect to that particular peripheral.For that how can assign the NUS_BASE_UUID value.It can be changing according to the uart request data(multilink peripheral).And also I need to know how to create the custom UUIDs for each nordic devices or else each device has its own const UUID?

RE: Make communication between ble central and ble peripheral

Sigurd — Wed, 13 Sep 2017 09:39:03 GMT

Hi,

As a starting point, I would recommend taking a look at the Nordic UART over BLE examples that implement the Nordic UART Service (NUS).

For the Central use the following project:

<SDK_InstallFolder>\examples\ble_central\ble_app_uart_c

For the Peripheral use the following project:

<SDK_InstallFolder>\examples\ble_peripheral\ble_app_uart

RE: Make communication between ble central and ble peripheral

lakshmi — Tue, 12 Sep 2017 17:14:45 GMT

Thank you so much for your response,Just started to going through the basic tutorials like making communication between android device as central and nordic peripheral.My requirement is,based on the request from the BLE central, I need to fetch some sensor data at regular intervals from the nordic peripheral and send back to the central device via nus and store it in database through uart serial communication.Really I am not having any idea,how to give the connection interval,at central side where I need to enter the UUID of the device which is advertising,to detect the device while scanning happens.Please tell me from where I need to start and share some sample code for ble central and peripheral communication.I can able to understand the concept,but it is very confusing while implementing it with the events.

RE: Make communication between ble central and ble peripheral

endnode — Tue, 12 Sep 2017 16:37:14 GMT

Dear Lakshmi, you list HW, SDK and stack versions but they do nothing on their own, it's the APP FW which makes all the things (= through stack and SDK libs and HW of course;). So please tell us what is exactly running on your boards and then we might be able to help you... Also my feeling is that you will be disappointed: most of the things happening in deeply embedded systems like nRF5x are not really simple, they have certain level of complexity which cannot by magically taken away. So understanding some basic principles will be necessary to move forward (like have you read some good tutorial or training about all BLE stack layers and their function, have you read resources here and on Nordic Infocenter, have you done few basic examples from nRF5 SDK from the beginning till the end etc.)