• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 345 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.

IWR6843ISK: Detect when using extended velocity and compensation

JINHYEONG LEE
Intellectual 740 points
Part Number: IWR6843ISK

Hi, 

I tested IWR6843ISK unsing OOB Demo in SDK3.5.

 

I observed the detection result of the same target through the visualizer by changing only the extendedMaxVelocity and compRangeBiasAndRxChanPhase command in Cfg.

(The correction value was measured by referring to the SDK guide)

 

When the correction and the velocity extend were used together, the target detection result was strange.

(The detected range is the same, but the doppler and angle seem to be wrong)

 

Below is the result when using either one or not both.

 

Below are the results when using both.

 

Below is the cfg file used for testing.

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 7 0
adcCfg 2 1
adcbufCfg -1 0 1 1 1
profileCfg 0 60 105 7 33.64 0 0 30 1 320 12499 0 0 158
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 4
chirpCfg 2 2 0 0 0 0 0 2
frameCfg 0 2 16 0 100 1 0
lowPower 0 0
guiMonitor -1 1 1 1 0 0 1
cfarCfg -1 0 2 8 4 3 0 15 1
cfarCfg -1 1 0 4 2 3 1 15 1
multiObjBeamForming -1 1 0.5
clutterRemoval -1 0
calibDcRangeSig -1 0 -5 8 256
extendedMaxVelocity -1 1
% extendedMaxVelocity -1 0
bpmCfg -1 0 0 1
lvdsStreamCfg -1 0 0 0
compRangeBiasAndRxChanPhase 0.0762179 -0.60397 -0.64542 -0.66522 -0.66946 -0.64209 -0.70471 -0.37708 -0.86667 -0.76633 -0.37451 -0.84061 -0.35657 -0.78491 -0.30798 -0.61557 -0.57355 -0.83316 0.55045 -0.82367 0.56708 -0.82932 0.52661 -0.97696 0.17557
% compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
measureRangeBiasAndRxChanPhase 0 1.5 0.2
CQRxSatMonitor 0 3 4 79 0
CQSigImgMonitor 0 105 6
analogMonitor 0 0
aoaFovCfg -1 -90 90 -90 90
cfarFovCfg -1 0 0 49.99
cfarFovCfg -1 1 -10 10.00
calibData 0 0 0
sensorStart

  

How do I use extendedMaxVelocity and compRangeBiasAndRxChanPhase together?

Thanks.

  • 0
    TI__Genius 17265 points

    Hi,

    Just to be clear, the results appear correct when using ONLY compRangeBiasAndRxChanPhase  and also when using ONLY extendedMaxVelocity, correct? I just want to ensure it's not just a potential issue with only one of the commands.

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Intellectual 740 points

    Hi,

    Alec May said:
    Just to be clear, the results appear correct when using ONLY compRangeBiasAndRxChanPhase  and also when using ONLY extendedMaxVelocity, correct?

    Correct.

    Only use compRangeBiasAndRxChanPhase

    compRangeBiasAndRxChanPhase만 사용
  • 0 in reply to JINHYEONG LEE
    TI__Mastermind 37805 points

    Hi,

    I notice the range resolution is quite coarse and the max range is quite long with this configuration. What is the intended application here? I wonder if you would see similar results if you made the cfg easier to test locally by setting a denser range resolution. See our sensing estimator tool here under the "Chirp Design and Tuning" tab for an interactive gui for setting the cfg file.

    When I demo it locally, I don't see much a difference either way because the range is set so high.

    You might also consider re-generating the compRangeBiasAndRxChanPhase line with a more reasonable cfg. If you generated that with a cfg that has very large range bins, it may not be so accurate.

    Best

    Nate

  • 0 in reply to Nathan Block
    Intellectual 740 points

    Hi, Thank you for reply.

    Nathan Block said:
    I notice the range resolution is quite coarse and the max range is quite long with this configuration. What is the intended application here? I wonder if you would see similar results if you made the cfg easier to test locally by setting a denser range resolution. See our sensing estimator tool here under the "Chirp Design and Tuning" tab for an interactive gui for setting the cfg file.

    I created the cfg in mmWave Demo Visualizer v3.5 and only changed cfarFovCfg, extenedMaxVelocity, compRangeBiasAndRxChanPhase. 

    Below are GUI settings to create.

     Anyway, as your advice, I'll test again by reducing the max range and range resolution.

     

    Nathan Block said:
    You might also consider re-generating the compRangeBiasAndRxChanPhase line with a more reasonable cfg. If you generated that with a cfg that has very large range bins, it may not be so accurate

    For Range Bias and Rx Gain/Offset measurement and compensation, I measured the compensation value with the <SDK demo>/profile/profile_calibartion.cfg file referring to the demo doxygen and sdk guide.

    According to demo doxygen, distance and phase error are related to HW, so it is not necessary to calibrate again after calibrating once.

    As you mentioned, should I proceed with the cfg I actually want to use when measurement?

     

    Thanks.

  • 0 in reply to JINHYEONG LEE
    TI__Mastermind 37805 points

    Hi,

    JINHYEONG LEE said:

    As you mentioned, should I proceed with the cfg I actually want to use when measurement?

    The profile_calibration.cfg file should be fine. Please also verify you're able to get consistent results with the calibration over multiple attempts to ensure correctness.

    Best,

    Nate