BLE - PHY definitions

RE: BLE - PHY definitions

Roei — Tue, 23 Mar 2021 11:23:48 GMT

Thanks!

RE: BLE - PHY definitions

Sigurd — Tue, 23 Mar 2021 11:20:00 GMT

[quote user="Roei"]What is the default?[/quote]

1M is the default. (unless you do extended advertising with secondary PHY set to something else).

[quote user="Roei"]

In addition - does PHY update has any effect on my PHY in future connections? Or does it reset on every connection?

[/quote]

It resets.

RE: BLE - PHY definitions

Roei — Mon, 22 Mar 2021 17:23:44 GMT

Hi, thanks for your answer!

I still don't understand how can I know what is my defined PHY, before my peer has requested to update. I do use S140. What is the default?

In addition - does PHY update has any effect on my PHY in future connections? Or does it reset on every connection?

Thanks!

RE: BLE - PHY definitions

Sigurd — Mon, 22 Mar 2021 17:18:28 GMT

Hi,

So for the sd_ble_gap_phy_update() documentation, we have:

If ble_gap_phys_t::tx_phys or ble_gap_phys_t::rx_phys is BLE_GAP_PHY_AUTO, then the stack will select PHYs based on the peer's PHY preferences and the local link configuration. The PHY Update procedure will for this case result in a PHY combination that respects the time constraints configured with sd_ble_cfg_set and the current link layer data length.

Example: If you are using S140, it supports 1M PHY, 2M PHY and Coded PHY. So if there is no time constraints, it will set preferred PHY to true for all the PHYs (1M PHY, 2M PHY and Coded PHY). If there are time constraints, i.e. you have set the value of NRF_SDH_BLE_GAP_EVENT_LENGTH in sdk_config.h to a low value(e.g. below 6), then there is no time to send a Coded PHY packet, and it will then set preferred PHY to 1M and 2M PHYs.

Also, some SoftDevices variants does not support Coded PHY, e.g. S112, and then it will only set preferred PHY to 1M and 2M PHY, and not Coded PHY.