This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Strange current in Long Range Beacon

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;

Parents
  • Hi Mateusz

    You're correct, you have yo use extended advertising for long range. Slip up on my end. I tested this myself on an nRF52840DK. However, we did not get this fourth peak when advertising. Have you tried this on more than one chip? Are you using an nRF52840 DK or a custom chip? Are you using one of our examples or is this your own project? Are you sure you're not doing anything else in addition to advertising?

    If you want, you could upload your project here (preferably with some instructions on your setup) and we can test it here on our end. If you don't want to share your project with the community, just say so and I will set this case to private so that only you and Nordic engineers will be able to see the case.

    Best regards,

    Simon

  • 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 ).

Reply
  • 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 ).

Children
No Data
Related