Four times the distance should be more or less expected given that the transmission power is boosted by 12dB. I'd be curious to see tests showing the RX sensitivity gains.
Roughly 5 dB RX gain on nRF21540 DK vs nRF52840 DK, so theoretically you can expect almost 2x range improvement from RX alone. Of course, environmental factors play in, which limits the theoretical range improvements.
Need this setup with the FEM, but with an external antenna port in a small SWaP form factor. Any ideas for protyping this? Closest I've found is the Nordic-Thingy53 but not sure a dependable way to go from its SWF RF port to a u.fl antenna.
Nch excellent in hardware, but documentation for programming is very complex, and very lengthy and time consuming that.....this is not expected from grate company
on which sdk example are the peripheral and central running ?, and on what tx power it was set in this demonstration, plus can it also run on an example based on ncs, zephyr os ?
This sample (developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/central_and_peripheral_hr/README.html) runs both central and peripheral, but in this video it runs modified versions of peripheral UART and central UART . We recommend you to read the associated blog post, where it is described: devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/testing-max-range-with-ble-with-nrf21540dks-and-nrf52840-dks TX Power is mentioned in the video is +8dBm with nRF52840 DK and +20dBm with nRF21540 DK, you can find this info in the above blog. These examples are based on nRF Connect SDK examples, so yes they can.
This depends on the regulatory side of things. In the US for example, Bluetooth LE long range limits TX output power to 14 dBm. So you will see improvements from long range, but you lose 6 dBm from the TX side. See graph for more info: www.nordicsemi.com/Products/Range-extenders#txPowerLimits
@@jeffking3693 This really depends on the use case. In most regions, Bluetooth long range could make sense as the TX output power is limited at 10 dBm. In the US, long range should give you theoretically 12 dB greater link budget than Bluetooth 1 Mbps (hence the marketing push for 4x the range). 14 dBm + 12 dB = 26 dBm which is greater than the 20 dBm TX output from the nRF21540. But remember that long range also reduces the throughput. So you need to spend more time on air than 1 Mbps, which increases power consumption. Best you can do is test out both for the use case you want and see what works best regarding range and power consumption.
In the blog on DevZone you can find an overview over distance, but not power consumption: hubs.li/Q017F0Dh0 When measuring distance, power consumption is not the most important aspect. These tests are not power optimized.
It makes no sense doing a throughput test with the nRF21540 DK. We've done a throughput demo using nRF52840 DK, please see this DevZone blogpost for details: devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/throughput-and-long-range-demo Video available: ruclips.net/video/K1ItqEZ2_tw/видео.html
I tested it (the nrf52840) and I got no more than 350 metres of range... Sending advertisements spaced each other 100 ms, with 250 bytes of data in extended PDU using Codec PHY, with +8 dBm of tx power.
There are multiple variables on where you did the testing that can have an effect. We recommend that you reach out to our tech support team on DevZone with details on your testing, location, which SDK etc. devzone.nordicsemi.com
It depens on which SDK you are using. This DevZone blog explains how to do in the nRF5 SDK: devzone.nordicsemi.com/f/nordic-q-a/37928/just-set-tx-power/146835 In nRF Connect SDK it is done in Kconfig with CONFIG_BT_CTLR_TX_PWR: developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/kconfig/index.html#CONFIG_BT_CTLR_TX_PWR
Wow!
Four times the distance should be more or less expected given that the transmission power is boosted by 12dB. I'd be curious to see tests showing the RX sensitivity gains.
Roughly 5 dB RX gain on nRF21540 DK vs nRF52840 DK, so theoretically you can expect almost 2x range improvement from RX alone. Of course, environmental factors play in, which limits the theoretical range improvements.
Need this setup with the FEM, but with an external antenna port in a small SWaP form factor. Any ideas for protyping this? Closest I've found is the Nordic-Thingy53 but not sure a dependable way to go from its SWF RF port to a u.fl antenna.
Please reach out directly to our community and tech support team on DevZone for idea: devzone.nordicsemi.com/
Nch excellent in hardware, but documentation for programming is very complex, and very lengthy and time consuming that.....this is not expected from grate company
Thanks for the feedback. We're constantly working on improving our documentation.
on which sdk example are the peripheral and central running ?, and on what tx power it was set in this demonstration, plus can it also run on an example based on ncs, zephyr os ?
This sample (developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/central_and_peripheral_hr/README.html) runs both central and peripheral, but in this video it runs modified versions of peripheral UART and central UART . We recommend you to read the associated blog post, where it is described: devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/testing-max-range-with-ble-with-nrf21540dks-and-nrf52840-dks
TX Power is mentioned in the video is +8dBm with nRF52840 DK and +20dBm with nRF21540 DK, you can find this info in the above blog. These examples are based on nRF Connect SDK examples, so yes they can.
Wonder what it would be with the long range mode?
This depends on the regulatory side of things. In the US for example, Bluetooth LE long range limits TX output power to 14 dBm. So you will see improvements from long range, but you lose 6 dBm from the TX side. See graph for more info: www.nordicsemi.com/Products/Range-extenders#txPowerLimits
@@NordicSemi looks like everywhere but the u.s. is limited to 10dBm. So is this worth it for lr vs the higher power allowed on standard ble?
@@jeffking3693 This really depends on the use case. In most regions, Bluetooth long range could make sense as the TX output power is limited at 10 dBm. In the US, long range should give you theoretically 12 dB greater link budget than Bluetooth 1 Mbps (hence the marketing push for 4x the range). 14 dBm + 12 dB = 26 dBm which is greater than the 20 dBm TX output from the nRF21540. But remember that long range also reduces the throughput. So you need to spend more time on air than 1 Mbps, which increases power consumption. Best you can do is test out both for the use case you want and see what works best regarding range and power consumption.
Would it be possible, that you add a table with distance and power consumption?
In the blog on DevZone you can find an overview over distance, but not power consumption: hubs.li/Q017F0Dh0 When measuring distance, power consumption is not the most important aspect. These tests are not power optimized.
fantastic.. throughput test?
It makes no sense doing a throughput test with the nRF21540 DK. We've done a throughput demo using nRF52840 DK, please see this DevZone blogpost for details: devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/throughput-and-long-range-demo Video available: ruclips.net/video/K1ItqEZ2_tw/видео.html
I bought this - but zephyr pulled me in.
Haha ... true
I tested it (the nrf52840) and I got no more than 350 metres of range... Sending advertisements spaced each other 100 ms, with 250 bytes of data in extended PDU using Codec PHY, with +8 dBm of tx power.
There are multiple variables on where you did the testing that can have an effect. We recommend that you reach out to our tech support team on DevZone with details on your testing, location, which SDK etc. devzone.nordicsemi.com
I would like to see that code? Would you be able to post it on the DevZone? 🤔I have 2x nRF52840_DK's
How to increase arduino ble 33 Tx power
It depens on which SDK you are using. This DevZone blog explains how to do in the nRF5 SDK: devzone.nordicsemi.com/f/nordic-q-a/37928/just-set-tx-power/146835
In nRF Connect SDK it is done in Kconfig with CONFIG_BT_CTLR_TX_PWR: developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/kconfig/index.html#CONFIG_BT_CTLR_TX_PWR