Reading the device name as central from adv data

RE: Reading the device name as central from adv data

uC_newbie — Fri, 30 Jun 2017 14:46:15 GMT

Worked perfectly, thank you :)

RE: Reading the device name as central from adv data

Jørgen Holmefjord — Fri, 30 Jun 2017 09:35:05 GMT

First, the central is always the one initiating a connection. The peripheral only advertise its precence and the central is the one to decide if it wants to connect, and initiate the connection. What you are describing is exactly what happens in the examle I linked above:

You get a BLE_GAP_EVT_ADV_REPORT event in the on_ble_evt()handler, and the function on_adv_report() is called.
on_adv_report() checks if the name given in m_target_periph_name is found in the advertising data.
If the name is found, the central connects to the device. If not, the advertising packet is discarded and scanning continues.

RE: Reading the device name as central from adv data

uC_newbie — Thu, 29 Jun 2017 14:38:50 GMT

hi, thank you.

i think i want to do something else: i want to check the peripherals name that wants to connect to my central before connecting and in case of not matching a desired name declining the connection/not connecting.

i thought i can do this inside the on_ble_evt() function. am i wrong?

RE: Reading the device name as central from adv data

Jørgen Holmefjord — Thu, 29 Jun 2017 14:29:32 GMT

Hi,

There is no separate field in the struct for the name. The name can be put in the advertising data (data field), but it is not required.

Check out the BLE multilink central example and the function adv_report_parse() for details on how tha name can be extracted from the advertising data.

Best regards,

Jørgen