Hi,
I do a test and show message by PC tool.
I find a error about Obj2D position and I think the sinAzim may be inverse.
Is something wrong or the setting not correct?
Please reference to below picture.

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.
Hi,
I do a test and show message by PC tool.
I find a error about Obj2D position and I think the sinAzim may be inverse.
Is something wrong or the setting not correct?
Please reference to below picture.

Hi,
What is the software used on the device? Seems like the results are mirrored? Is this one of our TIREX Labs?
Regards,
Aayush
Hi,
I use the sample from
\mmwave_automotive_toolbox_3_0_0\labs\lab0002_short_range_radar
Thanks
Hi,
We have not seen this type of issue with the TI matlab GUI.
Have you tried it? If TI GUI works fine, you would have to double check the implementation of your custom GUI
Thank you
Cesar
Hi,
This GUI is design it by myself, and I think it's not problem.
I use canfd to transfer data and show it by PC.
The hardware (antenna) design is by a hardware engineer, we don't use EV-BOARD.
Before this, I have already post similar situation and I think you can referent it.
Hi,
If the results are mirrored,
It is possible that there is an incorrect sign in the angle computation.
Thank you
Cesar
Hi,
Sorry for the delay
First
You can turn the EVM 180deg. If the detections are mirror image, than when the EVM is turned 180deg the detections should be correct in the GUI.
If this is the case, than you can modify either
thank you
Cesar
Hi Cesar,
This it the one situation.
I don't sent you all message.
Let me descript it.
When I from (0,0) to right, the object path sometimes over right sometimes over left.
When I from (0,0) to left, the object path sometimes over left sometimes over right.
The position wrong is happen, when target angle over 75 degrees.
Thanks
Hi,
If this happens at target angle over 75 degrees, this is expected.
This is due to the angle estimation that wraps around.
There is no solution to extend the field of view
Thank you
Cesar