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

AWR1443: Problem with AWR1443 configuration parameters

hittx
Prodigy 240 points
Part Number: AWR1443


The project requires the use of the AWR1443 chip for long-distance detection. However, by configuring the mmWave Demo Visualizer to configure the best range mode, it is found that it cannot be configured to pass. There will always be errors.The ccs project for the application is mmw_mss_14XX.The error is as follows

I found the following statement execution problem by tracking software。
  • 0
    TI__Guru**** 150224 points
    Hi,

    The configuration is probably not correct.

    Can you please share the configuration file with us?

    Thank you
    Cesar
  • 0 in reply to Cesar
    Prodigy 240 points

    This is my profile：

    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 1 1 0
    adcCfg 0 1
    adcbufCfg 0 1 0 1
    profileCfg 0 77 7 12.2 79.72 0 0 20.76 1 900 12000 0 0 36
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 0
    frameCfg 0 1 16 0 100 1 0
    guiMonitor 1   1 1  0 0  1
    cfarCfg 0 2 8 4 3 0 1200
    peakGrouping  1 1 1 1 224
    multiObjBeamForming 1 0.5
    calibDcRangeSig 0 -5 8 256
    clutterRemoval 0
    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 127 0
    CQSigImgMonitor 0 111 4
    analogMonitor 0 0
    sensorStart

  • 0 in reply to Cesar
    Prodigy 240 points
    I want to detect the distance of 70M. The distance resolution is not considered first. Is it possible to recommend some parameters?
  • 0 in reply to Cesar
    Prodigy 240 points
    I tried this set of parameters is not OK, please take a look
    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 5 0
    adcCfg 0 1
    adcbufCfg 0 1 0 1
    profileCfg 0 77 465 7 21.85 0 0 44.4 1 256 18500 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 4
    frameCfg 0 1 16 0 100 1 0
    lowPower 0 0
    guiMonitor 1 1 0 0 0 1
    cfarCfg 0 2 8 4 3 0 1280
    peakGrouping 1 1 1 1 229
    multiObjBeamForming 1 0.5
    clutterRemoval 0
    calibDcRangeSig 0 -5 8 256
    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 43 0
    CQSigImgMonitor 0 127 4
    analogMonitor 0 0
    sensorStart
  • 0 in reply to hittx
    TI__Guru 70100 points

    Hello,

    There are tools and app-note available on ti.com which will surely help you to get the correct configuration to meet your use-case.

    mmWave Sensing Estimator (training for this tool), Programming Chirp Parameters (this appnote will help you understand significant of mmwave configuration parameters), chirp database.

    Parameters you are providing in profileCfg command is not falling under valid chirp-configurations window because of which this API returns an error.

    We would recommend going over above-mentioned links to get this issue resolved.

    Regards,

    Jitendra