Antenna pattern AoD

RE: Antenna pattern AoD

Simonr — Thu, 03 Nov 2022 07:10:42 GMT

Got an update from our devs: The Kconfig value of BT_CTLR_DC_MAX_ANT_SW_PATTERN_LEN is used by the controller to check that the provided number of antenna IDs is not greater than the value used during building. By default it's 12 as seen below.

config BT_CTLR_DF_MAX_ANT_SW_PATTERN_LEN
    int "Maximum length of antenna switch pattern"
    range 2 38 if SOC_COMPATIBLE_NRF
    range 2 75 if !SOC_COMPATIBLE_NRF
    default 12
    help
      Defines maximum length of antenna switch pattern that controller
      is able to store. For nRF5x-based controllers, the hardware imposes
      the value is within range 2 to 38, where last value is maximum.
      For general use cases Bluetooth Core 5.1 spec. required the value
      to be within range 2 up to 75.

Best regards,

Simon

RE: Antenna pattern AoD

enoop — Wed, 02 Nov 2022 14:47:28 GMT

Hello,

Yes, here is a screenshot of what I receive every time after changing the char size. U can see the sizeArg = 1 all the time.

As an alternative, do you think I can read the antenna pattern from a .text file? (Instead of inputting a pattern as a command? I actually tried reducing the size of my command, so that I can have larger strings, but still, I get the same message.) Therefore, I think the problem should be somewhere else.

I'm very sorry for such a time-consuming question. I truly appreciate your patience and your kind responses.

Best,

RE: Antenna pattern AoD

Simonr — Wed, 02 Nov 2022 13:00:42 GMT

Not as far as I know but I have asked the developers to make sure. I will get back to you when I know. In the meantime, can you confirm that you also get the "too many arguments" when the number of elements are set to more than 10?

Best regards,

Simon

RE: Antenna pattern AoD

enoop — Tue, 01 Nov 2022 21:51:11 GMT

Dear Simon,

I've already changed this value to more than 10 (for example 14), yet I still receive the same Error. May I ask if the Zephyr has any limitations on this?

Thanks a lot,

Best,

RE: Antenna pattern AoD

Simonr — Mon, 31 Oct 2022 10:17:00 GMT

From your screenshot it seems like you've set the array size to include/support 10 elements yourself ( char elem [10]; ), and then you get this error of too many arguments when trying to write 11 elements in your array (since 40 is printed twice). Can't you just increase the size of this array on your end, as I don't know of a restriction in the Zephyr controller on the number of antennas you can use.

Best regards,

Simon

RE: Antenna pattern AoD

Susheel Nuguru — Fri, 28 Oct 2022 06:58:10 GMT

Hi Simon is OoO until Monday and he is a right person to answer you. It would be great if you can wait until Monday. Thanks a lot for your patience so far.

RE: Antenna pattern AoD

enoop — Tue, 25 Oct 2022 13:18:39 GMT

I added these two files myself. It's a compatible Zephyr version, but I'm only using the necessary parts for my application from the SDK. So, I'm combining several codes with each other. (That's why I have Bluetooth.h)

I'm working directly with Zephyr, and I'm sending a command through the shell to specify the antenna pattern. Here is the code screenshot: (Is there a limit on the number of arguments with Zephyr?)

Here is the problem. I try to connect to the serial port, and I'm sending this command to change the antenna pattern, but I receive the following message. (40, 41, ... are the gpios for the antennas)

Can it be a limit to the length of command in the terminal? I'm using minicom to connect to the port.

RE: Antenna pattern AoD

Simonr — Mon, 24 Oct 2022 07:48:14 GMT

Hi Pooneh

Did you change the dfe-antenna-num to match the number of antennas you'd like to use, as this is the number of antennas you want to use. dfe-pdu-antenna sets what antenna you want to be the default used for PDU transmissions.

These mBluetooth.h and gBluetooth.c does not seem to be part of the nRF Connect SDK at all, have you added these yourself or are you using a version of Zephyr outside of the nRF Connect SDK?

Can you upload the log where this "too many arguments" message is returned as well so we can get a better idea of what's happening?

Best regards,

Simon

RE: Antenna pattern AoD

enoop — Sat, 22 Oct 2022 10:01:53 GMT

Hello,

Thanks for your response. I am using the Zephyer Controller.

I only have one *.overlay file in my child image that is written based on nRF5x SoC . dfe-antenna-num = <4>; in this file. Also in this file, I defined 7 gpios. (dfegpio0-gpios = <&gpio1 1 0>; …). In this file, I also define: dfe-pdu-antenna = <0x40>. That’s all!

(I am using an antenna array with 4 switches that each of which switches 16 antennae. (64 in total) Separately, they all are functioning well)

In my mBluetooth.h file (in modules), I have defined the BLE_ANT_PATTERN 17,

In the gBluetooth.c file (in src), I have: static unit8_t ant_pattern[] = {0x40, …} (I’m using gpio 4)

Then I build the whole project, with no errors. (build target = nrf5340dk_nrf5340_cpuapp)

Once I programmed my dev board, I connect to the Port (ttyACM1), to change the antenna pattern, and then, I come across the error that I can not put more than 10 gpios when entering the new pattern. (I am using aod_tx )

Best,

Pooneh

RE: Antenna pattern AoD

Simonr — Mon, 17 Oct 2022 11:44:09 GMT

I assume you're using the Direction Finding peripheral sample project, correct? And are you using the SoftDevice controller or the Zephyr controller? Can you check what

dfe-antenna-num is set to in your nrf5340dk_nrf5340.overlay file? In our sample project this is set to 12 for the nRF52833 and nRF53 builds, but 10 for the nRF52820 overlay file. This is the first thing that comes to mind when you ask for why more than 10 defined antennas would cause issues. However I don't see why it wouldn't trig until you set the antenna pattern above 17 though, so I might have to ask the developers if there is some setting I'm not aware of here. But please, first answer my questions and check what dfe-antenna-num is set to in your application.

Best regards,

Simon