USER_ADVERTISE_DATA

Hi Ruchi Patel

请检查SDK的BLE_APP_BAREBONE示例，该示例演示了用户广告数据的动态变化。是的，您可以发送超过1个具有不同有效载荷的广告数据包。BLE_APP_BAREBONE示例也展示了该功能。广告字符串应具有特定格式，如。您发布的代码块具有此格式，因此可以执行此操作。广告分组传输速率可以在user_undirected_advertise_conf结构中定制
user_config.h文件。广告数据包以特定的广告间隔传输，该间隔可以在该结构中更改

Thanks PM_dialog

嗨Ruchi Patel，

您可以通过更改user_adc_conf结构的.intv_min或.intv_max engers来配置广告分组传输速率。通过这种方式，您可以定义广告的最小和最大间隔。关于广告数据，您不仅可以修改制造广告数据。您还可以修改超过1个字节的广告数据。SDK的BLE_APP_BAREBONE示例可动态更改广告字符串的适当数据。特定示例中的完整数据具有2个字节的长度，但可以更改它们的长度。在广告字符串中，您可以将特定数据追加并从应用程序中更新它们。广告消息是在app_easy_gap_undirected_advertise_start_create_msg（）函数中创建的，然后在调用app_easy_gap_undirected_advertise_get_active（）函数时保存在CMD结构中。CMD指针将有一条完整的消息，您可以发送到堆栈的堆栈，包括从user_advertise_data拍摄的一些默认的adv数据，因此您可以做的是在app_easy_gap_undirected_advertise_get_active（）返回之后，针对保存广告数据的CMD指针中的数组。（cmd-> info.host.adv_data）并根据需要更改它们 - 您的数据必须根据BLE规范。

Thanks PM_dialog

嗨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

嗨Ruchi Pate，

当您在帖子中说，#define“user_advertise_data”附加到.nvds_tag_app_ble_adv_data项目的nvds_data_storage结构。您可以定义多个User_Advertise_Data，但由于唯一的.nvds_tag_app_ble_adv_data项，只能在该结构中附加其中一个。如果您想要拥有多个广告数据，您可以使用不同的方式进行。我建议您将user_advertise_data定义为空，然后动态地附加不同的广告数据。当设备启动广告时，执行user_App_Adv_Start（），然后通过app_easy_gap_undirected_advertise_get_active（）创建CMD。app_easy_gap_undircated_advertise_get_active（）函数返回app_easy_gap_undircated_advertise_start_create_msg（）函数，为可连接的无向事件创建广告消息。广告消息包括用户广告配置，广告数据和其他数据。app_easy_gap_adv_read_from_nvds（）函数从nvds_data_storage结构中读取user_advertise_data，因此如果您有空的user_advertise_data定义，则您的广告数据将为空。通过这种方式，您可以根据user_app_add_start（）函数中的app_add_ad_struct（）动态地追加不同的广告数据。

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

嗨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

嗨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,0x36,0x37,0x38,0x39,0x31,0x32，0x33,0x34,0x35,0x36,0x37,0x38};

//安排下一个广告数据更新
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）;

//动态添加制造商特定数据
// mnf_data_update（）;
app_add_ad_struct（cmd，＆mnf_data，sizeof（struct mnf_specific_data_ad_structure））;

app_easy_gap_undirected_advertise_start();
}

如果将26bytes数据添加到广告字符串并希望填充其他数据，则可以将它们追加到扫描响应数据中，但在另一侧，观察者应配置为GAPM_SCAN_ACTIVE才能发送扫描请求。

Thanks PM_dialog