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

No Improvement of BLT 5 Long Range Mode

Hi, 

We have a product composes of a central and a peripheral which uses Nrf52840 as their MCU and communicate with each other via BLE. The peripheral will send some data and transfer audio captured by microphone to the central in real time. Currently they work perfectly.

Now I wanna implement long range mode to improve the distance performance.

However, modifying the firmware of the central and wearable for the implementation of the long range mode, I did the range test by comparing the two sets of the product(one is current version, the other one is of updated firmware), it seems that there is no distance improvement....

(By the way, the approach I conduct the range test is : I let the central and peripheral works, fixing the position of the central, and then move the peripheral away from the central, until the bluetooth connection is disconnected between the two)

Here I attach the codes of which I modified for long range mode, could you help me to check if there is something I miss?  Or there is some other causes can explain this?

(Peripheral)

(Central)

Parents
  • Hi

    1. Both SCANNABLE and NONSCANNABLE should be usable.

    2. Great, I just had to confirm it.

    3 & 4. Initially, I thought not, but it might be that both scan_phys and the primary_phy must be set to PHY_CODED. I can't confirm this with certainty though as both of our "long-range gurus" are out of the office this week. I'll be able to provide a definite answer early next week (maybe earlier if I'm able to reach either of them). In the meantime, I urge you to experiment with this, setting either or both of these parameters to CODED.

    Best regards and sorry I can't be of more help,

    Simon

Reply
  • Hi

    1. Both SCANNABLE and NONSCANNABLE should be usable.

    2. Great, I just had to confirm it.

    3 & 4. Initially, I thought not, but it might be that both scan_phys and the primary_phy must be set to PHY_CODED. I can't confirm this with certainty though as both of our "long-range gurus" are out of the office this week. I'll be able to provide a definite answer early next week (maybe earlier if I'm able to reach either of them). In the meantime, I urge you to experiment with this, setting either or both of these parameters to CODED.

    Best regards and sorry I can't be of more help,

    Simon

Children
No Data
Related