Connect 1 central and peripheral nrf52830 with 1 peripheral nrf52832

RE: Connect 1 central and peripheral nrf52830 with 1 peripheral nrf52832

Simon — Fri, 12 Oct 2018 14:17:47 GMT

This is because the advertising packet contains data such as device name and UUID, and nRF Connect can separate between devices based on that information. Here is a nice link in order to understand the advertising packet. It is also possible to to this an nRF chip, and here is a link showing how to decode the advertising data in the payload.

RE: Connect 1 central and peripheral nrf52830 with 1 peripheral nrf52832

hoàng khánh — Thu, 11 Oct 2018 01:24:31 GMT

Thank you for your reply, I have 1 more concern, could you explain for me if you have time?

Actually when a ble device is set as peripheral, I can discover it in my phone through nrf connect and choose which device to connect, but when connect between 2 nrf device, how can they recognize each other correctly because there are many other devices around them

RE: Connect 1 central and peripheral nrf52830 with 1 peripheral nrf52832

Simon — Wed, 10 Oct 2018 14:01:54 GMT

I think the Beacon Transmitter Sample Application located in examples/ble_peripheral/ble_app_beacon is convenient for your case. It can be flashed into the peripheral, and it will make the peripheral broadcast (advertise) information to the devices nearby. Here is a blog post explaining more about GAP advertising.

However, if you want to send more data, and establish a connection between the two devices, I would recommend you read about GATT, which stores the data in modules called Services and Characteristics. Here and here are some examples that can be loaded into respectively the peripheral and the central. These examples implements Nordics UART Service (emulates serial port over BLE), and is a nice place to start when learning about GAP connections.

Down below is also some nice tutorials to learn about advertising, characteristics and services

Best regards, Simon