LE Coded PHY S=2(500 Kb/s) test

RE: LE Coded PHY S=2(500 Kb/s) test

Simonr — Tue, 17 Nov 2020 07:40:03 GMT

You can, for example, check by making sure that the Coded PHY bit is set and that BT_CONN_LE_OPT_CODED is used after a bt_conn_le_phy_update() and that the BT_CONN_LE_PHY_OPD_CODED_S2 is used, and not the S8 call. You should also be able to see it on the data throughput and range of your application.

Best regards,

Simon

RE: LE Coded PHY S=2(500 Kb/s) test

cbe9 — Tue, 17 Nov 2020 02:10:45 GMT

Thank you very much.

Let's check using bt_conn_le_phy_update ().

So there is one more point to confirm.
How can I be sure that it is working with S = 2?

RE: LE Coded PHY S=2(500 Kb/s) test

Simonr — Wed, 11 Nov 2020 10:28:07 GMT

Yes, the nRF5340 and the nRF Connect SDK (v1.4.0) does support Coded PHY S=2. If you use I.E. the HR_coded examples in NCS, the simplest way to implement S=2 would be to do it as part of a connection PHY parameter update by calling bt_conn_le_phy_update(), see https://github.com/nrfconnect/sdk-zephyr/blob/master/include/bluetooth/conn.h#L427. The preferred coding scheme is part of the PHY options: https://github.com/nrfconnect/sdk-zephyr/blob/master/include/bluetooth/conn.h#L90.

Best regards,

Simon