• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 288 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.

Original question:

IWRL6432: how to determine the (Row0, Col0) for antenna geometry "antGeometryCfg"?

IWRL6432: Using custom antenna geometry file

Nir Flysher
Expert 3367 points
Part Number: IWRL6432

Tool/software:

Dear Team,

My customer is working with our IWR6843ISK. They are running the out of box MSS demo.

Inside the DSS there is a Antenna Geometry file which they’ve changed to accommodate their new antenna pattern.

Once they build the project they get exactly the same output.

It seems like nothing on the build scripts has a reference to the updated antenna geometry file.

Since they’re building it for object identification application it’s a bit odd that the build script doesn’t have any reference for the antenna geometry file.

 

Would anyone on the team be able to advise weather we’re missing something or is this a correct behavior of the scripts ?

Regards,

Nir.

  • 0
    TI__Mastermind 19520 points

    Hello.

    Are they rebuilding both the DSS and MSS projects after making the change to the antenna geometry file?

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    TI__Expert 3367 points

    Hi Santosh,

    Exactly.

    They need to bring up this demo urgently. Would it be possible to have a short conf call with them to make sure they're not missing anything ?

    Regards,

    nir.

  • 0 in reply to Nir Flysher
    TI__Mastermind 19520 points

    Nir,

    Can you please provide some information on what you mean regarding the exact same output?  What are they expecting to change between the original project and the new, updated project?

    Also, prior to making any change in the antenna geometry file, the ccs output for building the dss project looked like this:

    After I made a change, the build output looked like this:

    Is this what your customer is seeing?  If they are, then the changes are being compiled into the project and the data would more have to do with their environment.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    TI__Expert 3367 points

    Hi Santosh,

    The customer is going through exactly the same process you described above for the DSS and the MSS but gets two identical bin files whether they're using the default antenna pattern or their custom one. They're comparing the two bin files with beyond compare and the two files are exactly the same in every bit.

    1. Can you please try this on your environment ?

    2. Is this the expected behavior ? - If yes - then where do we take into account the custom antenna patterns ? If not - What are we missing ?

    Would you be available for a quick call sometime this week ?

    Regards,

    Nir.

  • 0 in reply to Nir Flysher
    TI__Mastermind 19520 points

    Hello Nir.

    The screenshots above are from my environment.  It looks like its identical to me; have you or the customer tried to run the two demos and see how the pointcloud behaves?  If the changes are actually making an impact with the incorrect antenna geometry the point cloud will behave incorrectly.  Can you please provide a screenshot or video of their performance when trying to run the two different binaries?

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    TI__Expert 3367 points

    Hi Santosh,
    The customer has investigated all the project code and couldn't find any reference to the custom antenna pattern file.
    The compiled bin files are exactly the same and it doesn't seem that any part of the code is actually using the custom antenna pattern file.
    This is the reason we suspect therwe've opened this thread.

    Would you be available for a quick call with them ?

    Regards,

    Nir

  • 0 in reply to Nir Flysher
    TI__Mastermind 19520 points

    Nir,

    After some further digging, I have found 2 things: 1) the ISK project, although the antenna geometry file is built into the DSS image, because the actual antenna geometry is not used in the MSS side, the binary remains the same and 2) the antenna geometry is derived from the config in mmwdemo_rfparser.c. 

    The ODS project actually uses the antenna geometry file as you were intending to use it for the ISK project, so what might be useful is to copy what is done in the ODS project for the ISK project to utilize the antenna geometry file. 

    Another option is to modify the mmwdemo_rfparser.c file(more specifically the MmwDemo_RFParser_parseConfig and MmwDemo_RFParser_parseCtrlConfig) to have it hardcode the antenna geometry you desire. 

    I think the first option would be a lot cleaner as it would allow you to repurpose the antenna_geometry.c file if needed for any other antenna changes.  The ODS project is MSS only, but it should still work as the antenna configuration is sent to the DSS during the DSP processing.

    Please let me know this resolves your issue.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 10 points

    Hi Santosh,
    Thanks for the help.
    We have tried to modify the ISK project to utilize the antenna geometry file but it takes too much effort for now. We are looking for a simple solution for our proof of concept.

    Your second option is to modify the mmwdemo_rfparser.c file.
    Can you help us understand exactly how to modify it?
    Which parameters to change?
    It seems that these functions are related to the configurations that are later used in the AoA process but i couldn't find any geometry parameters there.

    Thanks

  • 0 in reply to Gil Rad
    TI__Mastermind 19520 points

    Hello Gil.

    Gil Rad said:
    We have tried to modify the ISK project to utilize the antenna geometry file but it takes too much effort for now. We are looking for a simple solution for our proof of concept.

    Gil, have you tried modifying the project to match how it is implemented in the ODS project?  There are very few changes that need to be implemented to get it to match the ODS implementation.

    Gil Rad said:
    Your second option is to modify the mmwdemo_rfparser.c file.
    Can you help us understand exactly how to modify it?
    Which parameters to change?

    If you refer to the ODS project, you can see how the antDef maps to the txAntOrder and rxAntOrder and passed to the objectDetection.c  If you can match it this way from the ODS to the ISK project, that should be the only change required to support your antenna pattern.

    Sincerely,

    Santosh