• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 30 subscribers
  • Views 1109 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

IWRL6432: Parameters of Antenna Geometry

chiachih chang
Prodigy 90 points
Part Number: IWRL6432

Hi Expert,

I have two questions of antenna geometry. 

1. I am using the new designed antenna, and from the "MotionPresenceDetectionDemo_documentation.pdf", the parameters of the antenna geomtry needs to be changed. If I change the antenna to virtual 1*6 antenna array, based on the explanation of the document, is the parameter of gDoaRngGateCfg_2D = {3, {2,0,1,1,0,1},{2,2,1,1,2,1},{2,4,1,1,4,1}} correct?

2. Could you tell me where to change the parameter of gDoaRngGateCfg_2D in the motion_and_presence_detect_demo code? Because I cannot find gDoaRngGateCfg_2D in the code.

Thanks for the help in advance

Best regards,

ChiaChih

  • 0
    TI__Mastermind 20901 points

    Hi ChiaChih,

    1. I am checking internally to confirm if this parameter is appropriate for your antenna geometry. Please allow me to get back to you with an answer on this tomorrow.

    2. This parameter is located in the SDK as part of the doaproc DPU. <SDK_INSTALL>\source\datapath\dpu\doaproc\v0\doaproc.c

    Best Regards,

    Josh

  • 0 in reply to Josh Dye
    Prodigy 90 points

    Hi Josh,

    Thanks for the answer.

    I am curious that I saw gDoaRngGateCfg_1D. In my case, this will be suitble, right?

    Also, if gDoaRngGateCfg_1D is applied, what should I change?

    Best regards,

    ChiaChih

  • 0 in reply to chiachih chang
    TI__Mastermind 20901 points

    Hi ChiaChih, 

    Yes, you are absolutely correct. gDoaRngGateCfg_1D was used for testing purposes and is not applicable for the antenna pattern on the IWRL6432BOOST EVM but it would be suitable in your case. Your suggested change using 3 paramsets would also work but would be slightly less efficient. 

    chiachih chang said:
    Also, if gDoaRngGateCfg_1D is applied, what should I change?

    Please clarify. Are you looking for the additional changes required in order to use gDoaRngGateCfg_1D?

    Best Regards,

    Josh

  • 0 in reply to Josh Dye
    Prodigy 90 points

    Hi Josh,

    Good to hear that I am correct!

    No, I am not loking for the additional changes required. I am just curious because now I am using one-dimensional antenna pattern.

    Best regards,

    ChiaChih

  • 0 in reply to chiachih chang
    TI__Mastermind 20901 points

    Hi ChiaChih, 

    I'm sorry, I don't think I quite understand the question. Are you asking how the processing differs for a 2-D antenna pattern vs. a 1-D antenna pattern?

    Regards,

    Josh

  • 0 in reply to Josh Dye
    Prodigy 90 points

    Hi Josh,

    1. Sorry that I misunderstand your question.

    Answering the question of "Are you looking for the additional changes required in order to use gDoaRngGateCfg_1D?"

    Yes, I am looking for the additional changes required to use gDoaRngGateCfg_1D.

    Based on the figure, my antenna pattern is 1-D, then if I want to use the gDoaRngGateCfg_1D, is that ok for me just use it directly? or what else should I change?

    2. What do you mean "less efficient" while I use gDoaRngGateCfg_2D in my case? Does this affect the Tx power?

    Best regards,

    ChiaChih

  • +1 in reply to chiachih chang
    TI__Mastermind 20901 points

    Hi ChiaChih, 

    No problem!

    chiachih chang said:
    Based on the figure, my antenna pattern is 1-D, then if I want to use the gDoaRngGateCfg_1D, is that ok for me just use it directly? or what else should I change?

    Yes, you should be able to use it directly; but to be able to use it in the first place you will need to make some minor modifications to the code. 

    For instance, Line 456 of file doaproc.c is where rngGateCfg is set based on the value of the procOption variable. You will want procOption = 1 to use gDoaRngGateCfg_1D. To accomplish this you have a couple options:

    1. Use the already defined DPU_DOAPROC_ISK_BOARD for deviceSelect.board. This is set on line 908 of motion_detect.c. 
    2. Create a new macro for your own custom board using #define. Then add an additional a logical OR in the conditional on line 445 of doaproc.c. So that the same 1D settings are applied for your custom board. 
    chiachih chang said:
    What do you mean "less efficient" while I use gDoaRngGateCfg_2D in my case? Does this affect the Tx power?

    No, Tx power is not affected. I just mean in terms of number of HWA operations. gDoaRngGateCfg_2D = {3, {2,0,1,1,0,1},{2,2,1,1,2,1},{2,4,1,1,4,1}} will do the same thing as gDoaRngGateCfg_1D = {1, {6,0,1,1,0,1}} but with 3 HWA operations rather than 1. 

    Best Regards, 

    Josh

  • 0 in reply to Josh Dye
    Prodigy 90 points

    Hi Josh,

    Big thanks for the reply.

    Best regards,

    ChiaChih

  • 0 in reply to chiachih chang
    TI__Mastermind 20901 points

    Hi ChiaChih, 

    No problem! If your question is answered then I will go ahead and close this thread. Please don't hesitate to create a new post if you have any additional questions. 

    Best Regards,

    Josh