Software adjustments to improve bluetooth range

[Maos]

Hi!

Working on a system with a ble central communicationg with one or more peripherials both the central and peripherals using the nrf52840.

We want to know what we can do get the maximum range between them?

So far we have:
Enabled CONFIG_BT_CTLR_PHY_CODED on both sides

Set BT_CONN_LE_OPT_CODED | BT_CONN_LE_OPT_NO_1M in connection options before calling bt_conn_le_create on central side

Set phy to BT_GAP_LE_PHY_CODED and option to BT_CONN_LE_PHY_OPT_CODED_S8 and calling bt_conn_le_phy_update on both sides in connected callback

Set BT_LE_ADV_OPT_EXT_ADV | BT_LE_ADV_OPT_CODED in advertising options before calling bt_le_ext_adv_create

Do you have any suggestions on what more we can do?
I understand no specific figures can be given but some indication on what would have an impact on batter lifetime (for any changes to peripherial side)?

Is there any version of the example code provided in this blogpost: devzone.nordicsemi.com/.../testing-long-range-coded-phy-with-nordic-solution-it-simply-works-922075585 adpated to the new sdk?

BR,
Mårten

[Kazi Afroza Sultana]

Hello Mårten,

Coded Phy is supported in recent SDKs. You can look at these examples from our latest NCS documentation of Bluetooth: Peripheral Heart Rate Monitor with Coded PHY https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/peripheral_hr_coded/README.html#peripheral-hr-coded and Bluetooth: Central Heart Rate Monitor with Coded PHY (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/central_hr_coded/README.html)

Thanks.

Best Regards,

Kazi

[Maos]

Hi!

Thanks for the reply.

yes, we have seen that example and part of the things we have done/tried come from that example.
(Noticing that in that example I can't find that they set the BT_CONN_LE_PHY_OPT_CODED_S8 option explicitly.)
Comparing the things I enumerated above to that example I don't find anything we have missed relevant for this issue, do you see that we have missed anything?

And apart from what we already tried is there anything more we can do? Some other option or api-call that would be beneficial to try?
And if there is would that have a noticeable impact on battery life time?

What would the setting be if not setting BT_CONN_LE_PHY_OPT_CODED_S8 explicitly? Would it be BT_CONN_LE_PHY_OPT_CODED_S2 or BT_CONN_LE_PHY_OPT_CODED_S8?
Is there any API to request what the current setting is?

BR,
Mårten