Hello,
If I don't have,where should I go to download it?
Thanks.
Hello,
If I don't have,where should I go to download it?
Thanks.
I suggest you ask SEGGER on their forum, my best guess is that it's a work in progress.
Does any of the other targets work with the 52811?
In addition to the distance, I need to transfer a lot of data.
Maybe 250kbps
If throughput is related to distance, I will consider how to choose
"not have a reference design" , this refers to [Bluetooth5.1 direction finding],
or [Bluetooth5.1 direction finding] + [Long Range]?
Thank you
In addition to the distance, I need to transfer a lot of data.
Maybe 250kbps
If throughput is related to distance, I will consider how to choose
"not have a reference design" , this refers to [Bluetooth5.1 direction finding],
or [Bluetooth5.1 direction finding] + [Long Range]?
Thank you
tony55723 said:
If throughput is related to distance, I will consider how to choose
"not have a reference design" , this refers to [Bluetooth5.1 direction finding],
or [Bluetooth5.1 direction finding] + [Long Range]?
I'm afraid I do not understand what you are asking.
At 250kbps you cannot use BLE Long Range as it's symbol rate is 125kbps.
I suggest you use two nRF52811's with the Throughput example and measure the distance you can get with a throughput of 250kbps.
I am sorry that my expression is not very good.
I want to know, is there a document about "Long Range" in SDK 15.3.0, or example?(nRF52811)
Not limited to the SDK, there are more documents about "Long Range", I want to read
In the introduction of nRF52811 picture, [Bluetooth5.1 direction finding],
This technology is more accurate positioning?(more accurate location?)
But this feature is not available in SDK15.3.0?
Maybe the next version(SDK15.4.0?) will have this feature?
If the maximum rate of the Long Range is 125Kbps, I will test if it meets the requirements.
In the SDK, is there an example of throughput?
Thank you
I believe the two features 'Long Range' (Coded PHY) and 'direction finding' are mutually exclusive and cannot be used for the same link and the same time.
We are working on a reference design for an Angle of Arrival and Angle of Departure solution that will have all the necessary documentation, white papers, SDK support, and HW design files for the antenna array.
If you want to test the throughput with Coded PHY then you can do that with the Throughput example in 'nRF5_SDK_15.3\examples\ble_central_and_peripheral\experimental\ble_app_att_mtu_throughput'.
If so, I might consider giving up [Bluetooth 5.1 direction finding], [Long Range] is very important to me.
Should there be rssi function before Bluetooth 5.0?
Maybe the positioning is not very accurate
But after some algorithms, should be able to get the approximate position?
Is there an example of the rssi algorithm?
Is there a conflict between rssi and Long Range?
Thank you
The direction finding provisions in BT 5.1 does not use just RSSI, but rather Angle of Arrival and Angle of Departure to establish a vector between two BLE devices.
RSSI measurements have been a part of the spec since it's conception, and there are many companies that specializes in using RSSI for object tracking, etc, already. We do not have such solutions ourselves, but we should be able to find some of our customers who does provide such solutions.
What exactly are your application's requirements?