LAUNCHXL-CC26X2R1: Simple Central Reading Device Name

Dhiego,

When an advertisement or a scan response is received by a central device, the stack will produce the GAP_EVT_ADV_REPORT event, which in turn is processed by the simple_central as a SC_EVT_ADV_REPORT event in function SimpleCentral_processAppMsg(). 

Upon reception, you can inspect the contents of the Advertisement Data structures and look for the short or complete local names. See Bluetooth Core Spec, Vol. 3 (Host), Part C (GAP), Chapter 11 at https://www.bluetooth.com/specifications/bluetooth-core-specification/. The AD Type identifiers for the local names are 0x08 and 0x09, as defined here: https://www.bluetooth.com/specifications/assigned-numbers/generic-access-profile/. So, you would need to do something like the SimpleCentral_findSvcUuid() example, but look for GAP_ADTYPE_LOCAL_NAME_SHORT or GAP_ADTYPE_LOCAL_NAME_COMPLETE instead of GAP_ADTYPE_16BIT_MORE (these are all defined in gap.h).

Now, keep in mind that there is a mandatory characteristic called Device Name with UUID 0x2A00 (see https://www.bluetooth.com/specifications/gatt/characteristics/). Read about it in Bluetooth Core Spec, Vol. 3 (Host), Part C (GAP), Chapter 12 at https://www.bluetooth.com/specifications/bluetooth-core-specification/, and in particular section 12.1. However, reading this characteristic requires to establish a connection first.

I hope this helps. If it does, please mark the thread as resolved!

-Luis