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;

[Mateusz Gancarczyk]

Hi Simon,

hmm.. I thing it's not hardware problem. I based from the example ble_app_beacon_pca10056_s140 for two board: one base on ISP1807 and second based on BT840E and add few lines to orginal example to change PHY:

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;

When I change it I see the same strange current peak as above. When I run orginal example - without change phy - peak dosn't occur. 

But I noticed something, check picture below:

Peak depend of selected secondary phy ( when we use extended adv ).

[Simonr]

Hi Mateusz

Thanks for your thorough research. You are correct, it seems like you've found a bug within the SDK. I was able to recreate it as well by following your approach. I have reported the issue internally to get some of the resident experts on long-range to look at it. It might take some time as summer vacation is approaching here, but I'll give you an update as soon as I know something!

Hang in there,

Simon