Enabling long rage in nRF52840

RE: Enabling long rage in nRF52840

beemavishnu — Thu, 14 Nov 2019 09:11:25 GMT

Hi Simon,

Finally I am not getting exceptions. I missed setting to null. Its running fine. I need to check further by connecting to Central.

.scan_rsp_data =
{
.p_data = NULL,
.len = 0

}

Attaching file for future reference.

devzone.nordicsemi.com/.../2045.main.c

Thank you for your support.

Thanks & Regards

Vishnu Beema

RE: Enabling long rage in nRF52840

Simonr — Thu, 14 Nov 2019 08:06:39 GMT

Hi Vishnu

1. The flag seems to be set correctly.

2. I'm sorry, BLE_GAP_ADV_TYPE_EXTENDED_CONNECTABLE_NONSCANNABLE_UNDIRECTED should be the correct advertising type for Coded PHY.

3. Please check out this case, where a lot of common mistakes when setting up a long-range project are clarified by my colleague Håvard.

4. I'm sorry, but our SoftDevices does not support S=2 yet, so there is no way to enable this.

Best regards,

Simon

RE: Enabling long rage in nRF52840

beemavishnu — Thu, 14 Nov 2019 07:58:38 GMT

Aay updates on this please.

RE: Enabling long rage in nRF52840

beemavishnu — Wed, 13 Nov 2019 15:35:13 GMT

Hi Simon,

Thank you for your reply.

1) BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE is already in my code. Please crosscheck with my code snapshot and let me know if other structure I need to add.

2) I cannot fine BLE_GAP_ADV_TYPE_EXTENDED_CONNECTABLE_SCANNABLE_UNDIRECTED macro in ble_gap.h. I used BLE_GAP_ADV_TYPE_EXTENDED_CONNECTABLE_NONSCANNABLE_UNDIRECTED. But still I am getting fatal error.

3) As mentioned, the case statement is commented in the code attached in the link.

4) Is there a way to enable S=2 ?

5) Ok, got it. Thank you for confirmation.

To simplify, I did changes on actual code and the same I am attaching fill. Still with point 2 change I am getting fatal error.

static void advertising_init(void)
{
    ret_code_t    err_code;
    ble_advdata_t advdata;
    ble_advdata_t srdata;

    ble_uuid_t adv_uuids[] = {{LBS_UUID_SERVICE, m_lbs.uuid_type}};

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

    advdata.name_type          = BLE_ADVDATA_FULL_NAME;
    advdata.include_appearance = true;
    advdata.flags              = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;


    memset(&srdata, 0, sizeof(srdata));
    srdata.uuids_complete.uuid_cnt = sizeof(adv_uuids) / sizeof(adv_uuids[0]);
    srdata.uuids_complete.p_uuids  = adv_uuids;

    err_code = ble_advdata_encode(&advdata, m_adv_data.adv_data.p_data, &m_adv_data.adv_data.len);
    APP_ERROR_CHECK(err_code);

    err_code = ble_advdata_encode(&srdata, m_adv_data.scan_rsp_data.p_data, &m_adv_data.scan_rsp_data.len);
    APP_ERROR_CHECK(err_code);

    ble_gap_adv_params_t adv_params;

    // Set advertising parameters.
    memset(&adv_params, 0, sizeof(adv_params));

    #if 0
    adv_params.primary_phy     = BLE_GAP_PHY_1MBPS;
    adv_params.properties.type = BLE_GAP_ADV_TYPE_CONNECTABLE_SCANNABLE_UNDIRECTED;
    #else
    adv_params.primary_phy     = BLE_GAP_PHY_CODED; // For long range
    adv_params.secondary_phy   = BLE_GAP_PHY_CODED;

    adv_params.properties.type = BLE_GAP_ADV_TYPE_EXTENDED_CONNECTABLE_NONSCANNABLE_UNDIRECTED;
    #endif

    adv_params.duration        = APP_ADV_DURATION;
    
    adv_params.p_peer_addr     = NULL;
    adv_params.filter_policy   = BLE_GAP_ADV_FP_ANY;
    adv_params.interval        = APP_ADV_INTERVAL;

    err_code = sd_ble_gap_adv_set_configure(&m_adv_handle, &m_adv_data, &adv_params);
    APP_ERROR_CHECK(err_code);
}

devzone.nordicsemi.com/.../main.c

Thanks & Regards

Vishnu Beema

RE: Enabling long rage in nRF52840

Simonr — Wed, 13 Nov 2019 14:45:19 GMT

Hi Vishnu

1. You also have to include the following advertising flag for your Coded PHY application to be discovered. adv_data.flags = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;

2. You have to use extended advertising in order to use Coded PHY, so this will cause an issue. Please use the BLE_GAP_ADV_TYPE_EXTENDED_CONNECTABLE_SCANNABLE_UNDIRECTED advertising type.

3. I don't know if I understand this question. Why do you want to comment out BLE_GAP_EVT_PHY_UPDATE_REQUEST?

4. This example uses S=8 by default.

5. No, phones that do not support Coded_PHY (BLE 5.0) can not communicate with devices that use Coded_PHY.

Best regards,

Simon