How to receive manufacturer specific data when using the LE Coded PHY

RE: How to receive manufacturer specific data when using the LE Coded PHY

ikubaku — Thu, 18 Jul 2019 07:58:24 GMT

Sorry for the late reply. Upgrading the softdevice solved the problem, and I could send manufacture specific data with the project you attached. Thank you very much.

RE: How to receive manufacturer specific data when using the LE Coded PHY

Vidar Berg — Fri, 21 Jun 2019 12:18:26 GMT

I quickly modified the central and peripheral example from the github repo you linked to. Please test and see if it gives you the expected result.

devzone.nordicsemi.com/.../nRF52_2D00_ble_2D00_long_2D00_range_2D00_demo.zip

Note: I used Softdevice 6.1.1 + API headers since 6.0.0 had experimental support for scanning. Replace the s140 folder (\components\softdevice\s140) with the one from SDK 15.3.0 and make sure you're uploading the correct version to your board.

RE: How to receive manufacturer specific data when using the LE Coded PHY

ikubaku — Thu, 20 Jun 2019 08:38:51 GMT

I could confirm the example project is working with my boards. Investigating the diff file, I found I did the most of the configurations in the source code I posted first except setting buffer sizes in sdk_config.h and setting the advertising mode to fast mode. However, I don't see any related definitions in peripheral_long_range_demo_kit/sdk_config.h, and the peripheral project does not seems to be handling the advertising mode(instead specifies the advertising interval directly). Is there any other things I'm missing to do?

RE: How to receive manufacturer specific data when using the LE Coded PHY

Vidar Berg — Wed, 19 Jun 2019 07:36:20 GMT

Sorry for the delayed response. Please take a look at the example uploaded here: https://devzone.nordicsemi.com/f/nordic-q-a/40476/unable-to-convert-to-long-range-after-looking-at-umpteen-examples--. I based it on the ble_app_uart_c and changed the scanner configuration to use the coded PHY. There is also a diff file included in the zip which shows the changes I made.

RE: How to receive manufacturer specific data when using the LE Coded PHY

ikubaku — Thu, 13 Jun 2019 07:18:14 GMT

No. data.len field of advertising report was zero (although the advertising packet was 26 octets long). bel_advdata_search also returned zero with the received advertising packet.

Here are the modifications I made on central_long_range_demo_kit/main.c, and the content of m_adv_data.scan_rsp_data.p_data after calling ble_advdata_encode on the peripheral side.

central_long_range_demo_kit/main.c:

//NRF_LOG_HEXDUMP_DEBUG(p_adv_report->data.p_data, p_adv_report->data.len);
uint16_t ofs;
uint16_t res = ble_advdata_search(p_adv_report->data.p_data, len, &ofs, BLE_GAP_AD_TYPE_MANUFACTURER_SPECIFIC_DATA);
if(res == 0) {
  NRF_LOG_DEBUG("manufdata not found.");
} else {
  NRF_LOG_HEXDUMP_DEBUG(p_adv_report->data.p_data+ofs, res);
}

Memory dump of m_adv_data.scan_rsp_data.p_data

RE: How to receive manufacturer specific data when using the LE Coded PHY

Vidar Berg — Thu, 06 Jun 2019 08:03:07 GMT

Hello,

The advertisement report event should give you the payload transmitted on the data channels. Does the size of the received advertisement packet correspond with the size of the packet you sent? You can use ble_advdata_search() to extract the manufacturer field from the encoded data.