This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Coded PHY distance testing

We're developing Bluetooth tags that we would like to operate at both 1Mbps and coded (long range). From what I've read and seen from the Nordic testing, specifically "Testing Long Range (Coded PHY) with Nordic solution (It Simply Works)" found on the DevZone is that coded PHY should reach a distance of approximately twice as far (90%) as 1M PHY. With our initial distance testing on our product, we're not seeing much of a difference (if any) between the two PHY's. Our application is a custom beacon. We also tried the "nRF52-ble-long-range-demo" found on GitHub, which is the code that the previously mentioned article uses to do their testing. Using this unmodified hex file on the nRF52840 dev kits, we also found almost no difference in our distance testing. We're generally doing line of sight testing. I'm wondering what we could be doing wrong and have other users of coded PHY seen the twice the distance claim in their testing. We need to be able to achieve this advertised additional distance in our product.

Parents Reply Children
No Data
Related