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.

AWR6843AOPEVM: Questions about Point Cloud for AWR6843AOPEVM

Part Number: AWR6843AOPEVM


Tool/software:

Dear Sir/Madam,

I am currently using the AWR6843AOPEVM for 3D occupancy detection and have encountered the following issue:

When using the default .cfg file, the point cloud distribution is accurate. However, after altering the TX phase shifts in the .cfg file, the point cloud signals corresponding to the objects under test appear to be shifted, even though the experimental setup remains unchanged.

Below is the point cloud generated using the default .cfg file.

Below is the .cfg file after changing the phase shifts.

I would like to confirm if there are any documents or explanations available that describe how changes in phase shift can affect the point cloud algorithm, resulting in the displacement of points representing the objects in the point cloud.

Thank you for your time and support.

Best regards,

Hsiu-Che Chang

  • Hi,

    Please start by following some of the documentation found in this other thread:

    https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/897880/ccs-iwr6843-txphaseshifter-setting

    Regards,

    Tim

  • Hi Tim,

    Thank you for your response and the provided documentation link.

    However, the documentation does not seem to address my specific issue. I am looking for information on how phase shifts applied to the TX affect the computation of the point cloud.

    In my experiments, it has been shown that applying phase shifts to the TX causes the points representing the object in the point cloud to shift, even though the object itself remains stationary.

    Could you please provide guidance on how to resolve this issue?

    Thank you for your assistance.

    Best regards,
    Hsiu-Che Chang

  • Hello,

    Can you give us a little more information as to why you are trying to change the TX phases? Changing the phases is going to affect your direction of arrival estimation for sure, so unless you are changing it to some calibrated value, it is likely not recommended. TX phase is also specific to the antenna pattern.

    Additionally, how are you changing the .cfg file? Which parameters are you modifying? There are multiple ways to do so in the .cfg

    Regards,

    Tim

  • Hi Tim,

    The reason we want to try changing the TX phases is to implement beamforming on the AWR6843AOPEVM. However, when we implement beamforming, the points of the DUT on the point cloud shift compared to when beamforming is not used.
    Therefore, we want to identify the relationship between the phase shift and the point cloud calculation and correct it.

    The parameter we are adjusting is <txPhaseShifter>, as shown below:


    The file location of this document is:
    C:/ti/mmwave_studio_02_01_01_00/docs/mmwave_studio_cascade_user_guide.pdf

    Best regards,

    Hsiu-Che Chang

  • Hi,

    we usually perform beamforming as a part of software. We have only tested the value of 0 in txPhaseShifter as a part of this demo, so we can't guarantee any behavior that this would create.

    Typically we change the phases as a part of compensation for the antenna geometry, so when you modify the tx phases, you are ignoring that compensation. This is likely why your results don't make sense.

    Regards,

    Tim