• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 103 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.

AWR2243: problem about test source MMWL_testSourceConfig ()

Ying Jin
Prodigy 10 points
Part Number: AWR2243

Tool/software:

Hello, we conducted testing on the test source MMWL_testSourceConfig () based on the AWR2243 "mmwave_devp-02_02/04_00" project, and encountered an issue where the results of our self-developed algorithm parsing CSI2 data were inconsistent with the test source parameters. For example, the test source sets the target number to 2 and the target distance to 10 meters, but the actual algorithm results in 7 targets and a target distance of 2 meters.
We confirm that configuring AWR2243 through MMWL_testSourceConfig () has been successful. Our self-developed algorithm has also tested other source data and verified that the algorithm has no problems. Now we have identified the issue with the output CSI2 data of AWR2243. May I ask:
1.Can AWR2243 stably output CSI2 data that matches the test source parameters after configuring with MMWL_testSourceConfig ()?
2.How are tsArgs.rxAntPos [i]. antPosX and tsArgs.rxAntPos [i]. antPosZ defined and set in the test source? Is it necessary to match the antenna layout on the RF board?

3. Is there any way to verify whether the output CSI2 data of AWR2243 matches the parameter configuration of the test source?

  • 0
    TI__Intellectual 2502 points

    Hi Ying,

    1. Yes, assuming that test source parameters are set to valid ranges

    2. Please refer to table 5.75 in the ICD (mmwave_dfp_02_02_04_00/docs/mmWave-Radar-Interface-Control.pdf)

    The RSS is not active in test source mode so it is technically not necessary to match the antenna layout on the RF board, but it would be useful to for testing purposes.

    3. Beyond running it through post-processing, I don't think so.

    Have you tried using the default test source configuration in mmWave Studio?  How is the CSI2 data being captured?

    Thank you,

    Jin