We used the NRF52840 in our product. I want to experiment with Long Range BLE using PHY Coded. I will be using:
-Peripheral - The Product
-Master NRF52840 DK
Are there any code examples for configuring the Master and Peripheral?
We used the NRF52840 in our product. I want to experiment with Long Range BLE using PHY Coded. I will be using:
-Peripheral - The Product
-Master NRF52840 DK
Are there any code examples for configuring the Master and Peripheral?
You can find the example code at github.com/.../nrf52-ble-range-estimator.
The link gives a 404 error for me? Could you give the full path?
You may also review the changes I made in the example I posted here: https://devzone.nordicsemi.com/f/nordic-q-a/40476/unable-to-convert-to-long-range-after-looking-at-umpteen-examples-- . It's based on an older SDK version, but the changes should still apply to newer versions.
Thanks, The 1st link is a good overview (I read it yesterday) but I was looking for how to enable PHY Coded using the Nordic SDK from the Nordic SDK Documentation. I will look at how you did it your sample code and apply to mine. Though I do find the Espressif ESP_32 documentation much easier to navigate than Nordic.
The documentation is a bit split between SDK modules documentation and the Softdevice API documentation when it comes to setting up an advertiser/scanner with CODED PHY.
Maybe you have seen them already, but here are some doc. links which I you may find relevant:
Advertising using extended advertising PDUs - message sequence chart illustrating how an extended advertisment set is configured and used
sd_ble_gap_adv_set_configure - Function for configuring an advertisment set
Advertising Module used by most ble peripheral examples to manage advertising
Thanks. Though from a user/integrator perspective it would be useful to have some feature based documentation, e.g. to use PHY Coded use these API's rather that have the information spread throughout several documents
Thanks. Though from a user/integrator perspective it would be useful to have some feature based documentation, e.g. to use PHY Coded use these API's rather that have the information spread throughout several documents
I definitely see your point. I will report this internally for future improvement. I think this documentation could be added to the existing Advertising and Scanning module documentation.