Coded phy for throughput example with nrf connect sdk 1.8

[Nikkolaus]

Hi

I´am pretty new with the nRF connect sdk. I want to check the features from BLE long range /coded phy. 

In the past I have allready worked with the ble_att_mtu_throughput example from the nRF SDK 16.0 and I was very happy with it. With the "new" sdk my task is to check if there is any difference with a view to datathroughput and I also want to check the new feature coded phy s=2 (here I´am exited on the result). 

My Setup are two nRF 52840 DK´s. The example works fine with phy 1M and 2M, but with coded phy s=2 (and s=8) it dont work: 

After the phy update I only get back a timeout error. (With error code=-11 ?!) 

I nothing changed in the example (instead of the output from the err value).

Did I miss something here? Or is that a known issue from the example? 

Thank you for your answears,

Nikko

[dejans]

Hi Nick, 

I have managed to reproduce what you reported but without the error code.
Are you experiencing problem only when one of the devices is configured for coded PHY or only when both are using coded PHY? 
Please provide more information about devices' physical configurations which do not work for you.

Best regards,
Dejan

[Nikkolaus]

Hello again,

Thank you for the answer :) 

It doesn´t matter if I configured only one or two of my boards with coded phy. (It should not be depended in general what the peripheral device is configured. The central sends a phy update anyway, or I´am wrong?)

I use two nRF52840-DK´s and each of them are connect via COM with my computer and I use PUTTY to configure the central one. 

The example works fine for the other two phy´s, so I´am think the Hardware is configured right. 

[dejans]

Hi Nick,

I asked internally about the throughput sample. I'll get back to you when I get more information.

Best regards,
Dejan

[dejans]

Hi Nick,

There is an option you need to add to the configuration file (prj.conf) -  CONFIG_BT_CTLR_PHY_CODED=y. 
Afterwards, both coded_s2 and coded_s8 should work normally.

Best regards,
Dejan