Setting Phy of PAWR

[saty9pd]

We have been able to enable coded phy with PAWR using

```

struct bt_le_adv_param *params = BT_LE_EXT_ADV_NCONN;
params->options |= BT_LE_ADV_OPT_USE_IDENTITY | BT_LE_ADV_OPT_USE_NAME | BT_LE_ADV_OPT_CODED;
params->sid = 0;

err = bt_le_ext_adv_create(params, &adv_cb, &pawr_adv);

```

And config

```

CONFIG_BT_CTLR_PHY_CODED=y

```

This seems to be using S=8 how can we select S=2 instead

[Einar Thorsrud]

Hi,

We do not recommend using S=2. Due to optimizations in our radio, there is no practical difference in the range between S=2 and using the normal 1 Mbps PHY.

[rbmarcus]

Sorry for reviving an old topic. Is there a significant difference between S=8 and 1Mbps PHY? I don't want to sacrifice the majority of my current throughput, but a substantial range increase may justify doing so.

[Einar Thorsrud]

Hi,

I recomend this blog post for comparing coded PHY (S=8 / 125 kbps) and 1 Mbps PHY. The post is old but the results are stil valid.