RE: Issue with nRF52840 Long range feature

masterLee — Mon, 04 Mar 2024 08:58:45 GMT

Hi, so if I understand right,

1. I can leave the advertising initialization at 1MBPS (as it was without the addition of these three lines) since my two devices will be very close initially before connection.

2. Also, in the code that I uploaded, do you think that I miss something that would not establish long range ?

I am checking the example you sent me right now

-------------------------UPDATE-----------------------

I think I found the issues causing the problem in advertising PHY_CODED

a. In central code, Since I enabled the extended scanning packets, the buffer NRF_BLE_SCAN_BUFFER length (in sdk_config.h) was 31 Bytes and I needed to increase it to 255. Now it seems to work without errors.

b. Also, the BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE had to be set in the peripheral advertising data parameters

My main question remains though: Since my devices (peripheral and central) are in very close range until they connect, is it mandatory that I advertise PHY_CODED ? Why can't I leave it at 1MBPS and I just update it once the connection is established, in the ble_evt_handler() the way I do it now?

RE: Issue with nRF52840 Long range feature

Vidar Berg — Mon, 04 Mar 2024 08:08:45 GMT

Hi,

[quote user=""]But after reading some posts on the internet, it is said that I also need to set the advertising data of the peripheral to BLE_GAP_PHY_CODED[/quote]

When you perform connectable advertising with the CODED PHY, you enable the connection to be established using CODED PHY rather than 1M PHY. This approach is often preferred, as you may not be within 1M PHY range when attempting to establish the connection.

I posted an example of this here: https://devzone.nordicsemi.com/f/nordic-q-a/40476/unable-to-convert-to-long-range-after-looking-at-umpteen-examples--/157300#157300

Best regards,

Vidar