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.

AWR1642: About Sensing Estimator Setting Issue

Part Number: AWR1642

Hi Sir

We used Sensing Estimator to output some settings and use below command to set it

sensorStop

flushCfg

dfeDataOutputMode 1

channelCfg 15 3 0

adcCfg 2 1

adcbufCfg -1 0 0 1 0

profileCfg 0 77 7 4.9 78.91 0 0 41.13 1 307 4205 0 0 30

chirpCfg 0 0 0 0 0 0 0 1

chirpCfg 1 1 0 0 0 0 0 2

frameCfg 0 1 41 0 100 1 0

lowPower 0 1

guiMonitor -1 1 0 0 0 0 0

cfarCfg -1 0 0 8 4 4 0 5120

cfarCfg -1 1 0 4 2 3 0 5120

peakGrouping -1 1 0 0 1 255

multiObjBeamForming -1 1 0.5

clutterRemoval -1 0

calibDcRangeSig -1 0 -5 8 256

extendedMaxVelocity -1 0

bpmCfg -1 0 0 1

lvdsStreamCfg -1 0 0 0

nearFieldCfg -1 0 0 0

compRangeBiasAndRxChanPhase 0.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 5 123 0

CQSigImgMonitor 0 127 4

analogMonitor 1 1

sensorStart

 

  Above red part is replaced according to mmwave sensing estimator.

   1. when we sent the command , we got exception error feedback.

   2. we found the description of “numAdcSamlpe” at page 16 in mmwave_sdk_user_guide.pdf.

        “numAdcSamlpe” must be multiplicity of 4, but the estimator gives “307”.

  Is there any something wrong ? please advise

BR

Yimin

  • Hi,

    The sensing estimator will use mathematical equations to provide values for different parameters. The sensing estimator does not guarantee that all parameters are compatible with the mmWave SDK OOB demo data format.

    There is nothing wrong with sensing estimator.

    We recommend that you tweak the input parameters such as max range, range resolution etc slightly to get a multiple of 4 number of samples per chirp.

    Thank you
    Cesar