Central and peripheral Coded Phy running in nRF5340 and nRF52840 DKs

[Yashwanth]

Hi, 

I have nRF5340 DK and nRF52840 DK and Flashed Central_hr_coded in nRF52840, Peripheral_hr_coded in nRF5340 DK. Followed the steps of Testing as showed in below link. 

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/central_hr_coded/README.html#bluetooth-central-hr-coded

In the Putty and nRF terminal of VS Code, It is not showing the device connected.

1)My question is can we run the central and peripheral_hr_coded in different DKs? Any configuration need to change to allow both DKs connected to see the data in terminal?

2)I have tried to test the Peripheral_hr_Coded sample to see the HR data in nRF Connect App. The Device Name is not visible in App even though I added  CONFIG_BT_DEVICE_NAME="CODED PHY TEST". in prj.conf file. 

3)I would like to test Coded_PHY sample program for nRF5340 DK. Any Sample Coded PHY program to test the BLE Long range and Max data transfer to check?

Any Help Appreciated.

Thanks & Regards

Yashwanth

[Simonr]

Hi

We have a Coded PHY sample project as well in the nRF Connect SDK in the heart rate monitor with Coded PHY samples. Note that it's strongly recommended to lower the MTU size to 27 when using the Coded PHY. Since Coded PHY sends all packets 8 times longer packets have a large chance of packet loss with more data on the air for a longer period of time. It is better for both throughput and packet error rate to split the payload into several packets of 27 bytes when using the Coded PHY. The 247 MTU sizes are only recommended with the 1MBPS and 2MBPS PHY.

Best regards,

Simon