nrf52833 + Long Range + Scanner

RE: nrf52833 + Long Range + Scanner

user112081 — Thu, 16 Jun 2022 01:08:42 GMT

Hi Amanda,

I am currently measuring the range in the lab (not with clear line of sight). And it's around 30 meters where I see packets getting dropped with a default phy. At the same location, I am expecting Coded PHY to perform better. Also, I've confirmed adv packets are coded PHY in the scanner side by printing the data from adv packets on terminal and also using the nRF mobile App.

I've exact same configuration as mentioned in the sample application. My question here is, how do we configure S=2 or S=8 in adv packets? Is there anything else that needs to be configured for the maximum range?

TIA!

RE: nrf52833 + Long Range + Scanner

user77782 — Wed, 15 Jun 2022 08:47:26 GMT

Hi,

What is the distance you get? Can you compare the distance while using Central Heart Rate Monitor with Coded PHY and Peripheral Heart Rate Monitor with Coded PHY?

-Amanda

RE: nrf52833 + Long Range + Scanner

user112081 — Mon, 13 Jun 2022 17:42:33 GMT

Hi Amanda,

Thanks! I got it working after checking the configuration in the sample. With changes, I do see primary and secondary PHY of my adv as "LE Coded" now. However, I don't observe much change in the range compared to default phy.

I've kept the advertiser and scanner at a distance where I see drop in few packets with default phy. Then I replaced the default phy with Coded PHY and was expecting better performance (in terms of packets dropped) at the same distance. But I don't see much difference, even at the same distance, I see packets dropped with both default/coded phy. I am using same txpower for both the case. And experiments are done using nrf52833 on both the sides.

Is there anything else I need to configure to increase the range of advertisement packets with the Coded PHY?

This is what I changed to make my advertisements coded PHY.

	struct bt_le_adv_param param =
		BT_LE_ADV_PARAM_INIT(
				     BT_LE_ADV_OPT_USE_NAME | BT_LE_ADV_OPT_CONNECTABLE | BT_LE_ADV_OPT_ONE_TIME | BT_LE_ADV_OPT_CODED | BT_LE_ADV_OPT_EXT_ADV,
				     BT_GAP_ADV_FAST_INT_MIN_2,
				     BT_GAP_ADV_FAST_INT_MAX_2,
				     NULL);

TIA!

RE: nrf52833 + Long Range + Scanner

user77782 — Thu, 09 Jun 2022 07:59:22 GMT

Hi,

Did you enable CONFIG_BT_CTLR_PHY_CODED=y in the scan sample? I would suggest taking a look at the prj.conf and main.c of the Bluetooth: Central Heart Rate Monitor with Coded PHY sample.

Regards,
Amanda

RE: nrf52833 + Long Range + Scanner

user112081 — Tue, 07 Jun 2022 23:27:46 GMT

Just to add some more information, our adv parameters are:

    struct bt_le_adv_param param =
        BT_LE_ADV_PARAM_INIT(
                     BT_LE_ADV_OPT_USE_NAME | BT_LE_ADV_OPT_CONNECTABLE | BT_LE_ADV_OPT_ONE_TIME | BT_LE_ADV_OPT_CODED | BT_LE_ADV_OPT_EXT_ADV,
                     BT_GAP_ADV_FAST_INT_MIN_2,
                     BT_GAP_ADV_FAST_INT_MAX_2,
                     NULL);

So, it's extended Advertisements. And we can see them on nrfConnect App on S22 with primary and secondary PHY set as "LE Coded".

Are there any changes that we need to sniff/scan extended adv packets with nrf52833?