• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 687 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.

IWR1443: A very strong false target is always exsiting in the Range 0

William Gao
Intellectual 630 points
Part Number: IWR1443
Other Parts Discussed in Thread: DCA1000EVM, ,

I am using the DCA1000EVM and the IWR1443BOOST to capture data for 2s. However, by analyzing the data I captured with 2DFFT, I found that there was always a very strong amplitude at range 0 and doppler 0（in 2D heatmap plot).  Actually, there is no target at range 0. It really puzzled me. I tried many scenarios, but this promblem still exists. 

Could you help me solve this problem and give me an explaination of that?

Looking forward to your reply!

William

  • 0
    TI__Mastermind 21295 points
    Hello William,

    The mmWave SDK mmw (out-of-box) demo comes with a CLI command called calibDcRangeSig which is designed to help compensate for the behavior you describe. Here is the description of that command from the mmWave SDK 1.2 user guide (section "3. 4. Configuration (.cfg) File Format"):

    "DC range calibration config message to datapath.

    Antenna coupling signature dominates the range bins close to the radar. These are the bins in the range FFT output located around DC.

    When this feature is enabled, the signature is estimated during the first N chirps, and then it is subtracted during the subsequent chirps.

    During the estimation period the specified bins around DC are accumulated and averaged. It is assumed that no objects are present in the vicinity of the radar at that time.

    This procedure is initiated by the following CLI command, and it can be initiated any time while radar is running. Note that the maximum number of compensated bins is 32.

    The values in this command can be changed between sensorStop and sensorStart and even when the sensor
    is running.

    This is a mandatory command."

    Regards,
    John
  • 0 in reply to JohnH
    Intellectual 630 points
    Hi John

    Thanks for your reply! I understand what you explains. However, I am not sure of how to solve it in DCA1000EVM.
    When I used the IWR1443 board, I could changed the CLI command in 'mmWAve Demo Visualizer'. Now, To support the DCA1000EVM, I need to use the'mmWAve Demo Visualizer' , instead of the 'mmWAve Demo Visualizer'. In 'mmWAve Demo Visualizer', there is no such place where I could change the CLI command.

    Thanks,

    William
  • 0 in reply to William Gao
    TI__Mastermind 21295 points
    Hi William,

    The DCA1000EVM allows the user to capture raw ADC data from the mmWave device which can then be analyzed using mmWave Studio or post-processed by custom algorithms developed by the user. If you wanted to apply any specific type of post-processing algorithm to the data then you would need to implement the algorithm and apply it to the data. The specific "calibDcRangeSig" algorithm I mentioned is only implemented in the mmWave SDK demo which runs on the device and performs all the processing of the raw ADC data on the device.

    Regards,
    John