How to achieve CODED-PHY (long range) in mesh chat example along with varying TX power values

[Vignesh R]

Hi

I am using ncs v2.3.0, mesh chat example

I have used CONFIG_BT_CTLR_TX_PWR_PLUS_8=y , and it works quiet well, now how can i implement CODED_PHY (long range) in this example.

I have also referred this ticket, but should i change the adv_params in the ncs\v2.3.0\zephyr\subsys\bluetooth\mesh\adv_ext.c and scan_params in ncs\v2.3.0\zephyr\subsys\bluetooth\mesh\adv.c as mentioned in there??

is that the actual way to do so??

Someone guide me on this.

[Hieu]

Hi Vignesh,

Please be informed the Mesh Protocol specification does not allow Coded PHY. Bluetooth Mesh is based on Bluetooth 4.2, in which Coded PHY is not yet introduced.

While you can set Coded PHY with the method described in that ticket, it will not be qualifiable.

As for the method, please give what Susheel wrote in that ticket a try. It sounds like the right approach.

Please also see tesc's answer in this DevZone thread regarding other potential issue of using Coded PHY in Bluetooth Mesh:  Unable to configure nodes using mesh provisioner example over CODED PHY .

Hieu

[taihle]

Hi,

I'm on a quest to implement a solution utilizes some long-range capabilities using BLE mesh network. Can you please confirm that we can or can not implement long-range with current BLE mesh network stack? What does "it will not be qualifiable" mean?

Is there any update on BLE mesh that is based on Bluetooth 5 to support long-range?

Thank you!

[Hieu]

Hi taihle,

The latest update for Mesh is Mesh Protocol 1.1. Section 3.3.1, Advertising bearer, still specifies ADV_NONCONN_IND_PDU as the only type of advertising packet allowed. Meanwhile, this type of packet doesn't work with Coded PHY/Long-range. This, Coded PHY is still not supported, at least as of the time of writing.

taihle said:

What does "it will not be qualifiable" mean?

Qualification is a process where a product is tested to ensure that it complies with the Bluetooth Specification and Mesh Protocol Specification.

Please refer to these resources for more information.
Qualify Your Product | Bluetooth Technology Website
Bluetooth qualification — nRF Connect SDK 2.6.1 documentation (nordicsemi.com)

By the way, we support engineers do not get notified for cases where an answer has been verified. Thus, if you need support, please open a new ticket, or tag us.

Hieu