CTE on NRF52833

RE: CTE on NRF52833

user62951 — Sun, 05 Jun 2022 02:58:27 GMT

I am only asking for examples and nRF Connect SDK has many problems.

I found the answer in another post:

https://devzone.nordicsemi.com/f/nordic-q-a/49231/nrf52811-aoa-tx-timing-does-this-require-manual-timing

Just doing what NWP_36 says isn't enough to get CTE generated (I verified this with a digital spectrum analyzer in zero span and FM decoding of the packet by the spectrum analyzer

RE: CTE on NRF52833

user91187 — Thu, 02 Jun 2022 13:53:11 GMT

Hi, sorry for the confusion but we at Nordic do not provide any non-controller code. So here are the current options:

- Use the code in the nRF Connect SDK with either the SoftDevice Controller (AoA connectionless TX only, should get a valid QDID with the 2.0.0).

- Use Zephyr controller (all modes supported).

- Write the ale the code yourself.

You can find the answers needed in the PS as well as in the nWP036. And use the Zephyr Controller implementation as a guideline on how to implement this if you plan to write your own.

Regards,
Jonathan

RE: CTE on NRF52833

user62951 — Tue, 31 May 2022 13:11:17 GMT

This is for non-Bluetooth based code and the example you show is for bluetooth code.

RE: CTE on NRF52833

user91187 — Tue, 31 May 2022 12:34:30 GMT

Hi,

Check out the latest version in nRF Connect SDK (NCS) for direction finding. the white paper is no longer updated.
Beacon: Bluetooth: Direction finding connectionless beacon — nRF Connect SDK 1.9.99 documentation (nordicsemi.com)

Locator: Bluetooth: Direction finding connectionless locator — nRF Connect SDK 1.9.99 documentation (nordicsemi.com)
Bluetooth: Direction finding connectionless locator — nRF Connect SDK 1.9.1 documentation (nordicsemi.com)

This could be a issue with receiver code, cant say. So recommendation is to switch to NCS as it will be updated.

Regards,
Jonathan