• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 31 subscribers
  • Views 551 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DCA1000EVM: waveform setup problem

Jacki Hsu
Intellectual 330 points
Part Number: DCA1000EVM

Hello,

When I use the different chirp setup for the same waveform, I will get the different results.

The following is an instance of my two different experimental results.

1st method,

     

2nd method,

Please help me to solve this problem. Thank you.

  • 0
    TI__Genius 11405 points

    Hi Jacki,

    In the figures you show, I couldn't tell which profile was used because profile 2 was selected for both cases. 

    The chirp profile should be carefully designed to fit the test range and use case. For that, mmwave sensor estimator  can help.

    Different profile supports different test range and the wrong profile can lead to false detection.

    Thanks and Regards,

    Michelle

  • 0 in reply to Michelle Liu
    Intellectual 330 points

    Hi Michelle,

    Thanks for your reply. I definitely used the mmwave sensor estimator to calculate the chirp parameter to fit my design.

    In the 1st method, I selected the option "Manage Profile" directly, and fill the needed values to finish the setup of chirp parameter. Unfortunately, the 2-D FFT map seems no response with the moving target.

    On the other hand, in the 2nd method, I fill the values in the blocks of sensor configuration instead, and leave the "Manage Profile" blank. The result is totally different with 1st method, and the 2-D FFT map change as the target as I expected.

    Best regards.

  • 0 in reply to Jacki Hsu
    TI__Genius 11405 points
    Jacki,

    I now understand what the issue is. I will need to run the test myself to check.
    In the meantime, here's some suggestions I would give if you haven't tried.

    1. Make sure in profile manager, you follow Edit> Save> Activate sequence
    2. Compare the output log of the two sequences to see what is different


    Thanks and Regards,
    Michelle
  • 0 in reply to Michelle Liu
    Intellectual 330 points
    Hi Michelle,

    Thanks for your suggestion and look forward to your experimental results.
    By the way, I used AWR1642EVM integrated with DCA1000.
    As your suggestion, I already followed Edit> Save> Activate sequence.
    The output log showed no difference between these two different method.

    Best regards,
    Jacki
  • 0 in reply to Jacki Hsu
    TI__Genius 11405 points
    Jacki,

    I've verified and mine is the same as yours. This could be a tool issue and I've reported to get response from the developers.

    Thanks and Regards,
    Michelle
  • 0 in reply to Michelle Liu
    Intellectual 330 points

    Hi Michelle,

    Thank you for your help and look forward to your response.

    Best regards,

    Jacki

  • 0 in reply to Jacki Hsu
    TI__Genius 11405 points
    Jacki,

    The issue is reported but it won't be fixed until next mmwave studio release.

    The problem is the profile parameters passed to matlab for post-processing is not handled correctly. One way to by-pass it is that you can set profile 3 same as profile 2, then you will see the same result.

    Let me know if you have any other requests.

    Thanks and Regards,
    Michelle
  • 0 in reply to Michelle Liu
    Intellectual 330 points
    Michelle,

    Thank you. I will try it by the method like you say.

    Best regards,
    Jacki