Le Lange range unconnectable advertising Mode Setting and Protocol analysis

RE: Le Lange range unconnectable advertising Mode Setting and Protocol analysis

Vidar Berg — Mon, 17 Jul 2023 09:44:29 GMT

Do you have another device that broadcasts the correct payload that you can compare against? From the picture you posted, it is not clear if app code, counter, etc should be included in the manufacturer field or not.

RE: Le Lange range unconnectable advertising Mode Setting and Protocol analysis

quiqiuyu — Fri, 14 Jul 2023 08:32:44 GMT

Hi，

thanks for respond.I am completely unaware of what operations I have performed on the protocol stack. Currently, I have organized ad info, app code, Counter, and ODID Msg in order to form a data packet and assigned the pointer to pdata under ble_advdata_manuf_data_t. However, the data I observed on nrf_connect contains flags and company identifier, which seems to be inconsistent with my requirements. The attached figure is the protocol I am broadcasting.

and blew is the data from nrf_connect

RE: Le Lange range unconnectable advertising Mode Setting and Protocol analysis

Vidar Berg — Thu, 13 Jul 2023 12:02:23 GMT

Hello,

You only need to encode the advdata yourself using the ble_advdata_encode() function. The Bluetooth stack will populate the other fields in the advertising header.

[quote user="quiqiuyu"]This is the broadcast I'm currently configuring and I'm not sure if it's right. For example, for the uuid in advdata in the figure, should I define ble_advdata_service_data_t or write as broadcast data before m_beacon_info in ble_advdata_manuf_data_t. [/quote]

It depends on whether you want the UUID to be placed in the manufacturer field or not. Are you trying to implement the beacon payload according to a specific beacon standard that needs to work with third-party scanners, or are you creating a custom beacon?

You may find the demo examples I posted here relevant: RE: Problem with scanning 1Mbps and Coded Phy at the same time

Best regards,

Vidar

RE: Le Lange range unconnectable advertising Mode Setting and Protocol analysis

quiqiuyu — Thu, 13 Jul 2023 06:28:05 GMT

    my_Nus_Decoded(fstorage);
		Prepare_MulticopterPackage1(m_beacon_info);

    manuf_specific_data.data.p_data = (uint8_t *) m_beacon_info;
    manuf_specific_data.data.size   = APP_BEACON_INFO_LENGTH;
		
		ble_advdata_service_data_t   m_odid_data;
		m_odid_data.service_uuid  = 0xFFFA;
		m_odid_data.data.p_data   = count_code;
		m_odid_data.data.size     = 2;

    // Build and set advertising data.
    memset(&advdata, 0, sizeof(advdata));

    advdata.name_type             = BLE_ADVDATA_NO_NAME;
    advdata.flags                 = flags;
    advdata.p_manuf_specific_data = &manuf_specific_data;
    advdata.p_service_data_array  = &m_odid_data;
    // Initialize advertising parameters (used when starting advertising).
    memset(&m_adv_params, 0, sizeof(m_adv_params));

    m_adv_params.properties.type = BLE_GAP_ADV_TYPE_EXTENDED_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED;
    m_adv_params.p_peer_addr     = NULL;    // Undirected advertisement.
    m_adv_params.filter_policy   = BLE_GAP_ADV_FP_ANY;
    m_adv_params.interval        = NON_CONNECTABLE_ADV_INTERVAL;
    m_adv_params.duration        = 0;       // Never time out.
    m_adv_params.primary_phy     =BLE_GAP_PHY_CODED;
		m_adv_params.secondary_phy   =BLE_GAP_PHY_CODED;  
    		
    err_code = ble_advdata_encode(&advdata, m_adv_data.scan_rsp_data.p_data, &m_adv_data.scan_rsp_data.len);
    APP_ERROR_CHECK(err_code);
//		m_advertising.adv_handle = BLE_GAP_ADV_SET_HANDLE_NOT_SET;
    err_code = sd_ble_gap_adv_set_configure(&m_adv_handle, &m_adv_data, &m_adv_params);
    APP_ERROR_CHECK(err_code);

This is the broadcast I'm currently configuring and I'm not sure if it's right. For example, for the uuid in advdata in the figure, should I define ble_advdata_service_data_t or write as broadcast data before m_beacon_info in ble_advdata_manuf_data_t.