Strange current in Long Range Beacon

[Mateusz Gancarczyk]

Hi, I measure current in beacon in Long Range mode. Behind 3 current peaks witch represent TX on channel CH37 CH38 CH39 there is a strange current peak, witch I don't understand. When I switch to 1MBps this current peaks dosn't occur.

Here is my configuration for adv init:

 

/* long range*/
		m_adv_params.properties.type = BLE_GAP_ADV_TYPE_EXTENDED_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED;
    m_adv_params.primary_phy   	 = BLE_GAP_PHY_CODED;
    m_adv_params.secondary_phy 	 = BLE_GAP_PHY_CODED;
/* 1MBPS  */
//    m_adv_params.properties.type = BLE_GAP_ADV_TYPE_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED;

[Simonr]

Hi Mateusz

No, you are not listening for scan requests/responses when advertising nonconnectable and nonscannable. But the extended advertising might be what causes this extra "spike". Could you try advertising in long-range mode "normally" and not extended?

Best regards,

Simon

[Mateusz Gancarczyk]

hmm..how I can do that? I guess i have to only change:

m_adv_params.properties.type = BLE_GAP_ADV_TYPE_EXTENDED_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED;

to:

m_adv_params.properties.type = BLE_GAP_ADV_TYPE_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED;

but when I change it, I get error after function:

err_code = sd_ble_gap_adv_set_configure(&m_adv_handle, &m_adv_data, &m_adv_params);
APP_ERROR_CHECK(err_code);

error_code = 0x07 ( NRF_ERROR_INVALID_PARAM ).

What else I should to change to get non exteneded advertise?
Advertising in Long Range mode, works only in BLE_GAP_ADV_TYPE_EXTENDED_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED. I try all other type and it's not working.