BLE - BLE_GAP_EVT_PHY_UPDATE_REQUEST and sofet device 140

[Roei]

Hi,

I'm using NRF52840 in order to connect to a mobile app via BLE.

When connection to IOS, I have an event called BLE_GAP_EVT_PHY_UPDATE_REQUEST.

This event handle was under #ifndef s140, and I had to remove #ifndef so connection with IOS will be established.

I understand that this handle update physical layer to BLE_GAP_PHY_AUTO, and probably to 2mbps.

My question is - why was that under #ifndef s140? Does that may cause any issues to my device/connection?

Thanks!

[Simonr]

Hi

Can you provide some more details as to where exactly this BLE_GAP_EVT_PHY_UPDATE_REQUEST was called, and what SDK version you're using to develop your project. None of our BLE peripheral  examples has this #ifndef S140 before the BLE_GAP_EVT_PHY_UPDATE_REQUEST.

Best regards,

Simon

[Roei]

I will try to understand where that #ifndef came from.

Anyway - I'm using SDK 17.

BLE_GAP_EVT_PHY_UPDATE_REQUEST was called inside an event handler, in a function which receives ble_evt_t const * and void * for context. 

Do you know about any potential issues which may occur due to usage of BLE_GAP_EVT_PHY_UPDATE_REQUEST event handler with S140?

[Roei]

Is that possible that #ifndef came from older SDK versions?

[Simonr]

Hi

There is one call to #ifndef S140 in SDK v17.0.2 (and SDK v16.0.0, so there shouldn't be more in v17.0.0 either). This is in the multiprotocol BLE+ANT heart rate monitor example. Are you doing a multiprotocol application with ANT and BLE? Please note that it's strongly recommended to use SDK v17.0.2 instead of 17.0.0 as that is a bug fix.

Best regards,

Simon

[Roei]

Hi,

I don't really  understand what is BLE+ANT - I'm using my application in order to connect to a mobile device and to a PC via NFC pad. Where is that #ifndef S140 you are talking about?

Thanks!