PHY Coded transmission issue

[Kubek]

Hi there!

I face issue with setting the connection using PHY Coded.

I've:

- set the #define NRF_BLE_SCAN_SCAN_PHY 4 (it's Coded one) on Central side.

- forced PHY Coded to be set on GAP Update in "ble_evt_handler" function on both Central and Peripheral side: 

case BLE_GAP_EVT_PHY_UPDATE_REQUEST:
{
ble_gap_phys_t const phys =
{
.rx_phys = BLE_GAP_PHY_CODED,
.tx_phys = BLE_GAP_PHY_CODED,
};

- extended #define NRF_BLE_SCAN_BUFFER 255 on Central side (according to some other DevZone topic)

- let everything else like in PHY 1M project.

But I see it's not PHY Coded, because range didn't extend. What else am I supposed to do?

[Simonr]

Hi again

I just tested the examples I sent you for good measure, and they work as intended on two DKs, so it might indeed be an issue with the PDK. You can try flashing the .hex files from my side to make sure.

ble_app_uart_c_pca10056_s140.hex

3348.ble_app_uart_pca10056_s140.hex

They should connect immediately (LED 1 on both devices staying constantly on) and you should be able to write messages on one UART terminal (like PuTTY) that will output on the other.

Regarding your Android device, it should be able to scan for and connect to CODED PHY devices if the phone supports it. This is generally not supported in cheaper/older models, but flagship models for most brands the last 2 years or so generally support BLE Coded PHY, so if you have a rather new phone and use the DK as a peripheral I think you should be able to connect to it.

Best regards,

Simon