can not connect BLE when enable DirectionFinding

RE: can not connect BLE when enable DirectionFinding

loquat — Thu, 26 Oct 2023 14:28:57 GMT

OK.Thanks.

RE: can not connect BLE when enable DirectionFinding

Marte Myrvold — Thu, 26 Oct 2023 13:58:54 GMT

Hi,

This is not a bug, so I do not think there will be changes to this.
CONFIG_BT_CTLR_DF_CONN_CTE_RX enables connected mode for CTE receiver, so this must be enabled for connected mode to work when you have CTE receiver enabled.

Best regards,
Marte

RE: can not connect BLE when enable DirectionFinding

loquat — Wed, 25 Oct 2023 14:21:01 GMT

OK.

I tested it and it worked fine.
Will it be fixed in the future to allow connection even when CONFIG_BT_CTLR_DF_CONN_CTE_RX=n?

RE: can not connect BLE when enable DirectionFinding

Marte Myrvold — Wed, 25 Oct 2023 09:26:25 GMT

Hi,

You are correct. It seems like I made some other changes to the sample as well when testing, causing me to get an incorrect result.

The reason connection does not work is because you also need to set CONFIG_BT_CTLR_DF_CONN_CTE_RX=y to enable connection based CTE receiver. Enabling this in the Peripheral power profiling sample causes an error due to RAM size, but you can test it in a smaller sample, such as the Peripheral LBS sample.

However, if you want to use direction finding in the Peripheral power profiling sample I recommend looking at the Direction finding peripheral sample instead of the central sample.

Best regards,
Marte

RE: can not connect BLE when enable DirectionFinding

loquat — Wed, 25 Oct 2023 02:39:08 GMT

wrong.The result is the opposite.

When CONFIG_BT_CTLR_DF_CTE_RX=y, the connection will fail.

When CONFIG_BT_CTLR_DF_CTE_RX=n, the connection will be successful.

RE: can not connect BLE when enable DirectionFinding

Marte Myrvold — Tue, 24 Oct 2023 08:20:02 GMT

Hi,

It is because CONFIG_BT_CTLR_DF_CTE_RX=y enables CONFIG_BT_CTLR_DF_PHYEND_OFFSET_COMPENSATION_ENABLE, which enables a workaround to make sure that inter frame spacing is maintained for connection events. Without this, the system_off_work work item will cause the connection to fail. If you remove system_off_work in the sample, then connection works even with CONFIG_BT_CTLR_DF_CTE_RX=n.

Best regards,
Marte

RE: can not connect BLE when enable DirectionFinding

loquat — Sat, 21 Oct 2023 04:22:22 GMT

no. That's not the issue.
Add the following to your project's child_image/hci_rpmsg.conf.
GATT connection will not possible.
Just change to "CONFIG_BT_CTLR_DF_CTE_RX=n", GATT connection is possible.
What's the problem?

CONFIG_BT_LL_SW_SPLIT=y
CONFIG_BT_CTLR_DF=y
CONFIG_BT_CTLR_DF_CTE_TX=n
CONFIG_BT_CTLR_DF_CONN_CTE_TX=n
CONFIG_BT_CTLR_DF_ANT_SWITCH_TX=n
CONFIG_BT_CTLR_DF_CONN_CTE_RSP=n
CONFIG_BT_CTLR_DF_CTE_RX=y
CONFIG_BT_CTLR_DF_CONN_CTE_RX=n
CONFIG_BT_CTLR_DF_ANT_SWITCH_RX=n
CONFIG_BT_CTLR_DF_CONN_CTE_REQ=n

RE: can not connect BLE when enable DirectionFinding

Marte Myrvold — Mon, 16 Oct 2023 13:17:35 GMT

Hi,

You are missing some Kconfig and devicetree configurations for direction finding. Can you try the project I have attached? I started with the peripheral power profiling sample and added the configurations from the direction finding peripheral sample. I have not added any code or functionality for direction finding, but with this I am able to connect to the device while pressing button 1.

devzone.nordicsemi.com/.../peripheral_5F00_power_5F00_profiling_5F00_direction_5F00_finding.zip

Best regards,
Marte

RE: can not connect BLE when enable DirectionFinding

loquat — Fri, 13 Oct 2023 14:16:40 GMT

no
As the file name suggests, it is based on peripheral_power_profiling.
Just setting the config value for DirectionFinding causes the problem.

RE: can not connect BLE when enable DirectionFinding

Marte Myrvold — Fri, 13 Oct 2023 09:52:38 GMT

Hi,

Is the direction finding part of your project based on our samples that use connection, or the connectionless samples?

Best regards,
Marte

RE: can not connect BLE when enable DirectionFinding

Marte Myrvold — Thu, 12 Oct 2023 13:57:04 GMT

Hi,

I have started looking into your case and will get back to you tomorrow.

Best regards,
Marte