USER_ADVERTISE_DATA

Hi Ruchi Patel

Please check the ble_app_barebone example of the SDK which demonstrates dynamically change of user advertising data. Yes, you can send more than 1 advertisement packets with different payloads. The ble_app_barebone example demonstrates that functionality, too. The advertising string should have a specific format, like . The blocks of code that you have posted have this format, so it is possible to do that. The advertisement packet transmission rate can be customized in the user_undirected_advertise_conf structure of
user_config.h file. The advertising packets are transmitted in specific advertising intervals which can be changed in that structure

Thanks PM_dialog

Hi Ruchi Patel,

You can configure the advertisement packet transmission rate by changing the .intv_min or .intv_max menbers of user_adv_conf structure, which is defined in user_config.h. In this way, you can define the minimum and maximum intervals for advertising. Regarding the advertising data, you are able to modify not only the manufacturing advertising data. Also you able to modify more than 1 bytes of advertising data. The ble_app_barebone example of the SDK changes the propriety data of the advertising string dynamically. The propriety data have 2 bytes length in the specific example, but the length of them can be changed. In the advertising string you can append your specific data and update them from your application. The advertising message is created in app_easy_gap_undirected_advertise_start_create_msg() function and then is saved in the cmd structure when the app_easy_gap_undirected_advertise_get_active() function is invoked. The cmd pointer will have a full message that you can send to the stack including some default adv data taken from the USER_ADVERTISE_DATA, so what you can do is after the app_easy_gap_undirected_advertise_get_active() returns, target the array in the cmd pointer that holds the advertising data (cmd->info.host.adv_data) and change them as you like – your data will have to be according to the BLE specification.

Thanks PM_dialog

Hi Ruchi Patel,

关于NMI_handler是独立于你dual-role application. The NMI_handler will be issued due to the WatchDog timer. Please check where the Watchdog hits into your application. Regarding the switching between broadcasting and observer mode, you shouldn’t do any additional changes. In the case of the broadcasting are you advertising as a non-connectable device? If not, you can use the app_easy_gap_non_connectable_advertise_start API to create the advertising message for non-connectable advertising. Also, I suggest you to use the .app_on_adv_nonconn_complete callback function when the advertising is done since this callback is triggered when advertising as a non-connectable device.

Thanks PM_dialog

Hi Ruchi Pate,

The #define “USER_ADVERTISE_DATA” is appended into the .NVDS_TAG_APP_BLE_ADV_DATA item of nvds_data_storage structure as you said in your post. You can define more than one USER_ADVERTISE_DATA, but only one of that can be appended in that structure due to the unique .NVDS_TAG_APP_BLE_ADV_DATA item. If you want to have more than one advertising data, you are able to do it but with a different way. I suggest you to define the USER_ADVERTISE_DATA as empty, and then append your different advertising data dynamically. When the device starts advertising, the user_app_adv_start() is executed and then the cmd is created by app_easy_gap_undirected_advertise_get_active(). The app_easy_gap_undirected_advertise_get_active() function returns the app_easy_gap_undirected_advertise_start_create_msg() function which creates the advertising message for a connectable undirected event. The advertising message includes the user advertising configurations, the advertising data and other data. The app_easy_gap_adv_read_from_NVDS() function reads USER_ADVERTISE_DATA from the nvds_data_storage structure, so if you have empty the USER_ADVERTISE_DATA define, your advertising data will be empty. By this way, you are able to append your different advertising data depending on your application dynamically by using app_add_ad_struct() in the user_app_adv_start() function.

Regarding the manufacturer data, when the device is in observer mode, the .app_on_adv_report_ind ind callback function (in user_callback_config.h file) will executed, so it shouldn’t be NULL and you should define a function to be triggered. When a GAPM_ADV_REPORT_IND is received, the gapm_adv_report_ind_handler() will executed which is executes the .app_on_adv_report_ind ind callback. This handler has input parameter the gapm_adv_report_ind structure, which includes the adv_report structure. The manufacturer data should be at the data[ADV_DATA_LEN] item of the adv_report scucture. So how do you actually check that the manufacturer data are not being received and all the other data received properly?

Thanks PM_dialog

Hi Ruchi Patel,

Depending how you are using the SDK and which example you are using be aware that the SDK will append any extra data that don’t fit in the advertising string in the scan response data, so make sure that the data that you are interested in is in the advertising string and not the scan response data. In the first indication (advertising indication) the advertising data will populate the data member of the adv_report struct, and then in the second indication (scan response indication) the scan response data will populate the struct. In order to catch the scan response data, you should configure your device as GAPM_SCAN_ACTIVE to get a scan response. If you configure your device as GAPM_SCAN_PASSIVE, the observer only receives advertising data and doesn’t send a scan request to receive a scan response, so you will not able to read your scan response data. I’ve also tested this using an observer and the ble_app_barebone, I was able to get the increment in the advertising string or in the scan response data.

Thanks PM_dialog

Hi Ruchi Patel,

As I have pointed out in a previous post, you are not able to define more than one USER_ADVERTISE_DATA, because the #define “USER_ADVERTISE_DATA” is appended into the .NVDS_TAG_APP_BLE_ADV_DATA item of nvds_data_storage structure. The advertising string has 31 byte length, but 3 bytes of them are reserved from the stack, the advertising filter policy and the advertising data length, so you are able to use up to 28bytes. The data that are appended into the advertising string will be populated by user_app_adv_start with the procedure I have already mentioned in a previous post. In case you want to add your custom data into the advertising string you should copy them into the correct array of the cmd which is into user_app_adv_start() function. The cmd is created by app_easy_gap_undirected_advertise_get_active(). In your application you can have the USER_ADVERTISE_DATA empty and copy your data into the advertising string. The custom data should be valid and should follow the structure of USER_ADVERTISE_DATA, as in order to start advertising correctly. You should have 2bytes as length and flag into your data, so finally you are able to append up to 26bytes into the advertising string. In the following code, I will present you how you can do that.

void user_app_adv_start(void)
{

uint8_t advdata[28] = {0x1B,0xFF,0x31,0x32,0x33,0x34,0x35,0x36,0x37,0x38,0x39,0x31,0x32,0x33,0x34,0x35,0x36,0x37,0x38,0x39,0x31,0x32,0x33,0x34,0x35,0x36,0x37,0x38};

// Schedule the next advertising data update
app_adv_data_update_timer_used = app_easy_timer(APP_ADV_DATA_UPDATE_TO, adv_data_update_timer_cb);

struct gapm_start_advertise_cmd* cmd;
cmd = app_easy_gap_undirected_advertise_get_active();

memcpy(cmd->info.host.adv_data, advdata , 28);

// add manufacturer specific data dynamically
//mnf_data_update();
app_add_ad_struct(cmd, &mnf_data, sizeof(struct mnf_specific_data_ad_structure));

app_easy_gap_undirected_advertise_start();
}

If you add 26bytes data into the advertising string and you want to populate additional data, you can append them into scan response data, but in the other side, the observer should be configured as GAPM_SCAN_ACTIVE in order to send the scan request.

Thanks PM_dialog