If the RTT Viewer does not have nRF52811...

RE: If the RTT Viewer does not have nRF52811...

haakonsh — Tue, 27 Aug 2019 11:27:53 GMT

If you want any kind of directional position with just RSSI you will need an array of devices working together in order to get an estimate.

With AoA/AoD you will only need two devices. Our AoA/AoD reference design is scheduled for release in Q4 I believe.
If you need something before that and want to use RSSI only I can ask our local Regional Sales Manager if he knows a third party who can help you with direction finding with RSSI on the nRF52840.

RE: If the RTT Viewer does not have nRF52811...

tony55723 — Tue, 27 Aug 2019 10:07:34 GMT

My needs are as follows

1.Control distance further

2.Mobile phone is master, and pair as many nRF52811(slave) as possible

3.Need to know, nRF52811 paired by mobile phone, and where is the approximate direction?

(For example, my right front 5 meters) (The general direction can be)

Thank you

RE: If the RTT Viewer does not have nRF52811...

haakonsh — Tue, 27 Aug 2019 09:33:22 GMT

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?

RE: If the RTT Viewer does not have nRF52811...

tony55723 — Tue, 27 Aug 2019 06:08:46 GMT

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

RE: If the RTT Viewer does not have nRF52811...

haakonsh — Mon, 26 Aug 2019 07:40:12 GMT

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'.

RE: If the RTT Viewer does not have nRF52811...

tony55723 — Fri, 23 Aug 2019 04:03:05 GMT

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

RE: If the RTT Viewer does not have nRF52811...

haakonsh — Thu, 22 Aug 2019 11:21:48 GMT

[quote user="tony55723"][/quote]

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.

RE: If the RTT Viewer does not have nRF52811...

tony55723 — Wed, 21 Aug 2019 14:10:05 GMT

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

RE: If the RTT Viewer does not have nRF52811...

haakonsh — Wed, 21 Aug 2019 11:32:18 GMT

With 52811's in both ends of the link transmitting at +4dBm with LR (125kbps Coded-PHY) you should be able to get 500+ meter range in line-of-sight. The range is also dependent on your throughput needs. What exactly is your throughput needs, in terms of kbps?

Each mobile phone has a different BLE performance that usually results in shorter range than what our devices are capable of.

We do not have a reference design for direction finding yet.

RE: If the RTT Viewer does not have nRF52811...

tony55723 — Wed, 21 Aug 2019 10:14:20 GMT

NO SD81, is SDK , sorry

RE: If the RTT Viewer does not have nRF52811...

tony55723 — Wed, 21 Aug 2019 10:12:42 GMT

Thank you for your reply

Okey, maybe I will use "printf" to debug first.

I want to use the Long Range of 52811,

If do not add PA chip,

Two 52811, or a mobile phone and a 52811, the distance can reach 100m?

Is there a document on Long Range that can be referenced?

Is there still no SD81 Bluetooth5.1 direction finding SDK (maybe SDK15.4.0?)

but Long Range technology, can already be used in SDK15.3.0?

Thanks

RE: If the RTT Viewer does not have nRF52811...

haakonsh — Wed, 21 Aug 2019 09:28:26 GMT

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?