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: What is the actual effect of the analogMonitor command?

Part Number: AWR1642

Hi,

The default value of the analogMonitor in mmwwaveSDK v2.1.0.4 is "analogMonitor 1 1".

What is the actual effect of the analogMonitor command?

Is the setting of "analogMonitor 1 1" better than the setting of "analogMonitor 0 0"?

Also, I can not find the analogMonitor command in mmwaveSDK v3.1.1.2.

What is the reason for canceling this command?

Thanks.

The profile for mmwave SDK v2.1.0.4

===========================================================

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 3 0
adcCfg 2 1
adcbufCfg -1 0 0 1 0
profileCfg 0 77 7 7 58 0 0  68 1 256 5500 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
bpmCfg -1 0 0 1
frameCfg 0 1 32 0 100 1 0
lowPower 0 1
guiMonitor -1 1 1 1 0 0 1
cfarCfg -1 0 2 8 4 4 0 5120
cfarCfg -1 1 0 8 4 4 0 5120
peakGrouping -1 1 0 0 1 224
multiObjBeamForming -1 1 0.5
calibDcRangeSig -1 0 -5 8 256
extendedMaxVelocity -1 0
clutterRemoval -1 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
nearFieldCfg -1 0 0 0
CQRxSatMonitor 0 3 4 127 0
CQSigImgMonitor 0 63 8
analogMonitor 1 1
lvdsStreamCfg -1 0 0 0
sensorStart

===========================================================

  • Hi

    As described analogMonitor enables some of the monitoring features supported by the device.

    Some of the monitoring functions have changed in the firmware version supported by SDK 3.x

    This could be the reason they are no longer supported.

    Thank you
    Cesar