Good Afternoon,
I have purchased a PAN1740 evaluation kit from the board. I would like to customize the beacon's identifier strings (they are currently set as per the value indicated in UM-B-019).
How can I go about doing this? I have found reference to using the Smart Tag (proximity) samples from the SDK, but the software did not want to boot after programming (at least I could not see anything in the Locate application).
Thank you in advance for an indication of where I might be able to look for more information.
Best regards,
Mathew
Device:
Hi mgrabaunc,
In the Beacon sw on the SDK the advertising string is populated by the NVDS structure which is located in the nvds.c file (search for the NVDS_TAG_APP_BLE_ADV_DATA tag), the app_adv_func() is the function that will populate the advertising string and send the command to the kernel in order for the device to start advertising. So if you would like to change the default string you should start from there (be careful since if the provided string doesn't complies with the BLE spec the stack wont advertise and will return an error-please check the BLE spec in how an advertising string should be). Regarding the reference that you found was the proximity reporter (included in the SDK) or the Smart Tag reference design ? and what did you do in order to change the advertising string. Regarding the application that you ve used "Locate" as far as i know the application parses and shows only beacon formats and not generic advertising strings from devices, neither the proximity reporter or the Smart Tag advertise in any beacon format.
Thanks MT_dialog
I have been looking for the function app_adv_func(), but have not located it. I can only find app_adv_start(). I am currently looking at the ble_app_barebone sample.
Looking for the NVDS_TAG_APP_BLE_ADV_DATA has yielded some results. I just need to determine what to set the TX Power value in order to get the distance working properly.
Thank you thus far!
Hi mgrabaunc,
I had the impression that you were checking the Official Beacon reference design, the app_adv_func() function is located in the app_dialog_beacon_proj() and its only available in the SDK 3 (older version of the SDK). Since you are working with the ble_app_barebone example (SDK5) the top advertising function is the user_app_adv_start() (the user defined advertising function) and the advertising data are taken from the USER_ADVERTISE_DATA in the user_config.h file (which in turn populate the NVDS_TAG_APP_BLE_ADV_DATA).
Regarding what to set in the TX power value you can have a look at the UM-B-019_DA14580_Beacon_Reference_Application_v1.2.pdf on page 8, in the paragraph "Beacon in more detail using the DA14580", essentially you average a few of RSSI measurements taken in 1 meter distance and place the averaged value in the advertising's string Tx field.
Thanks MT_dialog
Sorry for the confusion, I had switched my project to the new SDK to try to make it easier to support my request. I have now sorted that out - thanks!
I will read the RSSI averaging procedure and conduct that experiment.
Thanks,