AOA Antenna Switching

[Farsley]

Hello

I am running the nrf/samples/bluetooth/direction_findinding_connectionless_rx App on an nRF52833-DK with nrf Connect SDK 2.2.0

I have set VS Code to use board nrf52833_nrf53833 and configuration to prj.conf

I am running the transmitter code on another board and in the terminal window see:

CTE[0]: samples count 45, cte type AOD 2 [us], slot durations: 2 [us], packet status CRC OK, RSSI -480
CTE[0]: samples count 45, cte type AOD 2 [us], slot durations: 2 [us], packet status CRC OK, RSSI -490
CTE[0]: samples count 45, cte type AOD 2 [us], slot durations: 2 [us], packet status CRC OK, RSSI -500

What I am not seeing is any changes on the antenna switching pins 03,04,28,29 when viewing them with an oscilloscope.

If I change

 dfe-pdu-antenna = <0x0>

to <0x5>

I can see the relevant antenna pins go high on the line:

err = bt_enable(NULL);

but they remain high and do not switch.

In a post similar to this it was suggested adding the following to the prj.conf, but I see no difference:

CONFIG_BT_CTLR_DF=y

CONFIG_BT_CTLR_DF_ANT_SWITCH_RX=y

CONFIG_BT_CTLR_DF_SCAN_CTE_RX=y

Why don't I see the antenna pins switching, Is there some setting I am missing?

Please can you tell me where in the code the antenna switching takes place.

Thank you

[Elfving]

Hello Nick,

Unfortunately, I might have to get back to you after the holidays when it comes to further details on this. Though I can tell that at least some parts of the issue is related to getting AoA and AoD mixed up. Both are considered Bluetooth direction finding, though AoA and AoD are mutually exclusive. CONFIG_BT_CTLR_DF_ANT_SWITCH_RX enables the switching on the Rx side, which is AoA. If your tag is claiming "cte type AOD", I believe it will be expecting to do antenna switching as well.

So are you trying to do AoD or AoA?

Regards and Happy Holidays,

Elfving