S120/S130 scan, getting client device friendly name

RE: S120/S130 scan, getting client device friendly name

KevinLiao — Wed, 02 Mar 2016 12:06:34 GMT

Yes. I used the adv_report_parse() function, and get the device name. It's works.

RE: S120/S130 scan, getting client device friendly name

Florin — Thu, 15 Jan 2015 20:52:02 GMT

I'm pretty sure the BLE_GAP_AD_TYPE_COMPLETE_LOCAL_NAME doesn't get broadcasted. What's interesting is that the BLE device scanner apps do display the friendly name. I'll try, with ble_app_hrs, thanks for the advice. florin

RE: S120/S130 scan, getting client device friendly name

Petter Myhre — Tue, 13 Jan 2015 16:06:51 GMT

Are you sure you have a name? I have just tested this with ble_app_hrs and ble_app_hrs_c and it seems to be working fine with BLE_GAP_AD_TYPE_COMPLETE_LOCAL_NAME. Could you test with those examples first? Please see the Core Specification Supplement (CSS) v5 for information on the format of advertising data.

RE: S120/S130 scan, getting client device friendly name

Florin — Sat, 10 Jan 2015 07:36:20 GMT

Hi Petter, sorry for the late response. The scan doesn't receive any of the definitions you've listed. I'm getting the following:

BLE_GAP_AD_TYPE_APPEARANCE
BLE_GAP_AD_TYPE_FLAGS
BLE_GAP_AD_TYPE_TX_POWER_LEVEL
BLE_GAP_AD_TYPE_128BIT_SERVICE_UUID_COMPLETE (I'm broadcasting a 128bit uuid)

I have access to the ble_evt_t data structure and I think the friendly name is buried there somewhere. The struct is quite nested and gdb freezes in its attempt to list it. I can give you more details if needed.

florin

RE: S120/S130 scan, getting client device friendly name

Petter Myhre — Wed, 17 Dec 2014 12:52:57 GMT

Have you tried the adv_report_parse() function found in the ble_app_hrs_c S120 example in SDK 7.1.0?

I haven't tested it myself, but hopefully you can use it with the appropriate BLE_GAP_AD_TYPE_DEFINITIONS, for example BLE_GAP_AD_TYPE_SHORT_LOCAL_NAME or BLE_GAP_AD_TYPE_COMPLETE_LOCAL_NAME.

Please add a comment if you get into trouble.