long range beacon LECODED

RE: long range beacon LECODED

Vidar Berg — Mon, 04 Oct 2021 12:33:06 GMT

The Radio receiver sensitivity is specified for both CODED and 1M in the PS here: Receiver operation

RE: long range beacon LECODED

buja — Mon, 04 Oct 2021 11:58:11 GMT

Okay, I understand that. What should be the minimum RSSI value for the scanner to receive the beacon properly for Legacy Advertising and LECODED advertising ? Is there a standard value for this ?

RE: long range beacon LECODED

Vidar Berg — Fri, 01 Oct 2021 15:08:53 GMT

Hi,

Yes, I would expect the average current to be about the same for both scenarios for the reason you mentioned.

RE: long range beacon LECODED

buja — Fri, 01 Oct 2021 14:54:32 GMT

Hi Vidar, Thank you for your reply. But the link doesnt work

[quote userid="4240" url="~/f/nordic-q-a/80178/long-range-beacon-lecoded/332154#332154"]The advantage may be a lower radio TX current[/quote]

I understand that the peak current will be less. But don't you think, on average, current consumption will be same in both situations ? Because, for LECODED the radio has to be in ON state for more time than in Legacy.

RE: long range beacon LECODED

Vidar Berg — Fri, 01 Oct 2021 13:04:05 GMT

The advantage may be a lower radio TX current while a disadvantage is that you will need an observer that supports scanning on CODED phy.

Note that our online power profiler (https://devzone.nordicsemi.com/nordic/power/w/opp ) allows you to estimate current consumption for CODED PHY if you select the nRF52840 and connection. It might be helpful to visualize the difference.

Edit: fixed link to the online power profiler.

RE: long range beacon LECODED

buja — Fri, 01 Oct 2021 11:24:39 GMT

Thank you for your reply.

We thought we would be able to send long range beacons with same energy budget for legacy advertising.

What is the advantage of long range advertising with respect to BLE 5.0, when we can simply increase the TX power of legacy advertising to increase the range ?

RE: long range beacon LECODED

Vidar Berg — Fri, 01 Oct 2021 11:17:12 GMT

Then you are left with s=8 I'm afraid.

RE: long range beacon LECODED

buja — Fri, 01 Oct 2021 11:15:12 GMT

Hi Vidar,

We are using SDK 17.1.0

RE: long range beacon LECODED

Vidar Berg — Fri, 01 Oct 2021 11:14:02 GMT

Hi,

Yes, there is some additional overhead when you include advertising on data channels (advertising on the primary channel has to include information about the secondary channel). But more importantly, LE CODED lowers the bitrate so it effectively takes 2x or 8x times longer to transmit data depending on the coding you use (s=2 vs. s=8). This means the radio has to spend more time in TX to transmit the same amount of data.

Are you using the nRF connect SDK (NCS) or the nRF5 SDK? The nRF5 SDK only supports s=8, for NCS I would have to check.