Long range data transfer from central to peripheral

RE: Long range data transfer from central to peripheral

ovrebekk — Wed, 17 Nov 2021 09:02:50 GMT

That is great to hear. I will consider the case resolved then 🙂

Best regards
Torbjørn

RE: Long range data transfer from central to peripheral

sowmiya — Tue, 16 Nov 2021 13:51:19 GMT

hi ovrebekk,

Its working in LR mode data transfer .NRF_SDH_BLE_GAP_EVENT_LENGTH increased the event lenght too , Its working now

Thanks.

RE: Long range data transfer from central to peripheral

ovrebekk — Mon, 01 Nov 2021 11:32:16 GMT

Hi Sowmiya

Are you saying that almost exactly the same code (only changed to support coded phy) will allow you to send 247 bytes of data in 1M mode, but not in coded phy mode?

Can you run the two examples with logging enabled to see if there are any warning or error messages printed that might indicate why the MTU size can not be increased?

Could you try to capture a sniffer trace of the BLE communication when you connect the devices and try to send 247 bytes of data (using the nRF Sniffer for instance)?

Best regards
Torbjørn

RE: Long range data transfer from central to peripheral

sowmiya — Fri, 29 Oct 2021 14:28:59 GMT

Hi ovrebekk ,

[quote userid="2116" url="~/f/nordic-q-a/80687/long-range-data-transfer-from-central-to-peripheral/336633#336633"]Another reason to use the ble_app_uart example is that it handles the MTU exchange for you. The blinky example does not, since you don't need extended MTU to send a single byte back and forth ;)[/quote]

blinky i have changed the MTU to transfer 247 bytes data and increased the MTU size you can see in LBS service in my demo example and the reason almost its all done In 1mpbs mode data transfer already in my project and now adding PHYcoded data transfer.

i have tested with ble_app_uart_example and the same way i have tried out still its sending only 27 bytes in PHY coded .

RE: Long range data transfer from central to peripheral

ovrebekk — Fri, 29 Oct 2021 09:39:52 GMT

Hi Sowmiya

Another reason to use the ble_app_uart example is that it handles the MTU exchange for you. The blinky example does not, since you don't need extended MTU to send a single byte back and forth ;)

In order to see how this is done I would recommend simply having a look at the ble_app_uart and ble_app_uart_c example. In particular, take a look at the implementation of the void gatt_init(void) function in main.c, which configures the GATT module that is responsible for handling the MTU exchange.

Best regards
Torbjørn

RE: Long range data transfer from central to peripheral

sowmiya — Thu, 28 Oct 2021 13:50:58 GMT

devzone.nordicsemi.com/.../NRF_5F00_15_5F00_2.rar

yes , Lbs i have already changes done on service configurations. and For PHY coded increased the size of GAP_DATA_LENGTH but not able to transfer more then 27 bytes , i have attached my demo file please advice what i have missed here.

#ifndef NRF_SDH_BLE_GAP_DATA_LENGTH
#define NRF_SDH_BLE_GAP_DATA_LENGTH 251
#endif

#ifndef NRF_SDH_BLE_GAP_EVENT_LENGTH
#define NRF_SDH_BLE_GAP_EVENT_LENGTH 6
#endif

// <o> NRF_SDH_BLE_GATT_MAX_MTU_SIZE - Static maximum MTU size.
#ifndef NRF_SDH_BLE_GATT_MAX_MTU_SIZE
#define NRF_SDH_BLE_GATT_MAX_MTU_SIZE 247
#endif

regards

sowmiya

RE: Long range data transfer from central to peripheral

ovrebekk — Thu, 28 Oct 2021 11:46:56 GMT

Good to hear you got it working 🙂

It should be possible to extend the length, yes, but you need to increase the NRF_SDH_BLE_GAP_DATA_LENGTH and NRF_SDH_BLE_GATT_MAX_MTU_SIZE parameters in sdk_config.h in order to be able to support extended MTU. Once you do this you will also need to increase the amount of RAM assigned to the SoftDevice (as shown in this Youtube video).

Finally, you would need to change the service configuration as well, since the LBS service only supports 1 byte data transfer, but possibly you already did this?
This is another reason to use the NUS service instead, as it is set up to support longer packets.

Best regards
Torbjørn

RE: Long range data transfer from central to peripheral

sowmiya — Wed, 27 Oct 2021 15:58:47 GMT

hi ,

its working in LBS service now !! and data transfer maximum length 27 bytes when using Coded PHY ?it possible to extend the length ?

RE: Long range data transfer from central to peripheral

ovrebekk — Tue, 26 Oct 2021 12:37:06 GMT

Are you able to share your project with me?
If so, please just zip the project folder, with source and project files included.

If so I can try to run it here, and see if I can reproduce the issue.

Best regards
Torbjørn

RE: Long range data transfer from central to peripheral

sowmiya — Mon, 25 Oct 2021 14:28:50 GMT

i have checked the demo code with s140_nrf52_6.1.0_softdevice its working.

same way checking on LBS service on central side ble_lbs_led_status_send is getting succes while connecting to send the message.

but on Periperal side connecting and disconnection happens.

ret_code_t err_code;
ble_advdata_t advdata;
ble_advdata_t srdata;
ble_advdata_manuf_data_t manuf_specific_data;

manuf_specific_data.company_identifier = APP_COMPANY_IDENTIFIER;
manuf_specific_data.data.p_data = (uint8_t *) NORMAL_BEACON;
manuf_specific_data.data.size = APP_BEACON_INFO_LENGTH;

// 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_NO_NAME;
advdata.include_appearance = false;
advdata.flags = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;
advdata.p_manuf_specific_data = &manuf_specific_data;
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));

printf("phy coded startes------\n");

adv_params.primary_phy = BLE_GAP_PHY_CODED;
adv_params.secondary_phy = BLE_GAP_PHY_CODED;
adv_params.properties.type = BLE_GAP_ADV_TYPE_EXTENDED_CONNECTABLE_NONSCANNABLE_UNDIRECTED;
// }
// else{
// adv_params.properties.type = BLE_GAP_ADV_TYPE_NONCONNECTABLE_SCANNABLE_UNDIRECTED;
// }
adv_params.p_peer_addr = NULL;
adv_params.filter_policy = BLE_GAP_ADV_FP_ANY;
adv_params.scan_req_notification = 1;
if(battery_level == 0 || battery_level >= BATTERY_VOLTAGE_MIN_FOR_DISPLAY){
adv_params.interval = ADV_INTERVAL;
}
else{
adv_params.interval = LOW_LEVEL_BATTERY_INTERVAL;
}
adv_params.duration = adv_timeout; // Never time out.

err_code = sd_ble_gap_adv_set_configure(&m_adv_handle, &m_adv_data, &adv_params);
APP_ERROR_CHECK(err_code);
sd_ble_gap_adv_set_configure(&m_adv_handle,&m_adv_data,&adv_params);
NRF_LOG_INFO("m_adv_data.adv_data.p_data address %p", m_adv_data.adv_data.p_data);

RE: Long range data transfer from central to peripheral

sowmiya — Mon, 25 Oct 2021 11:23:31 GMT

Hi ,

thanks for the reply , my application already added with LBS services to scan Both 1Mpbs and PHY CODED beaccons and now trying the same in connected mode to transfer data in LONG RANGE AND 1mpbs here 1mpbs connected and data transfer working. so adding the same for PHY CODED. I am using the softdevice s140_nrf52_6.1.0_softdevice in my application.

i have debugged the demo long range code https://devzone.nordicsemi.com/f/nordic-q-a/40476/unable-to-convert-to-long-range-after-looking-at-umpteen-examples--/157300#157300 here softdevice s140_nrf52_6.1.1_softdevice.hex

is this supported only on 6.1.1 softdevice ?

RE: Long range data transfer from central to peripheral

ovrebekk — Thu, 21 Oct 2021 07:56:53 GMT

Any reason you can't just use the UART example instead of blinky?

The only difference between the UART service and the LED button service is that the UART services uses variable length characteristics (to send strings), while the LED button service uses 1 byte characteristics (to send the LED and button status).

As for debugging the issue, have you tried to check the log output to see if there is anything there that could explain the issue?

Are you sure that the code for sending data is actually run?

Have you used the debugger to check whether or not the function for sending data runs, and if it returns any errors?

Best regards
Torbjørn

RE: Long range data transfer from central to peripheral

sowmiya — Wed, 20 Oct 2021 11:00:24 GMT

Hi ,

I have tried ble_app_uart and ble_app_uart_c examples in long range data gets transfer from central to peripheral . same way tried ble_app_blinky and ble_app_blinky_c example with lbs services in long range gets succesfully connected but stil no data transfer happens.in first query is my PHY_CODED chnages in ble_app_blinky example.

Would you please help provide more details as suggested.

RE: Long range data transfer from central to peripheral

ovrebekk — Fri, 15 Oct 2021 10:54:04 GMT

My colleague Vidar shared an example showing how to use the ble_app_uart and ble_app_uart_c examples in long range mode, and he shared the code in this case.

I would recommend you start by taking a look at his examples.

Then if you're still having issues I will do my best to help next week.

Best regards
Torbjørn