AWR2944: Zero detections in advanced subframe profile with fast rangeproc options

Dmitry Trots

Part Number: AWR2944

Tool/software:

Hi team,

In related thread I asked for help with short chirps processing. And it was adviced to use fast range processing options to decrease range FFT processing time.
It was verified with legacy frame configuration, but when rangeProcCfg options was enabled in advanced subframe configuration I found that second subframe processing result has no detected objects at output permanently.

I use mmw demo from SDK 4.7.1.3.
Could you please reproduce this trouble?

Regards,

Dmitry

5 days ago

0 Samhitha Bobba 4 days ago

TI__Mastermind 19980 points

Hi Dmitry,

I have tested the same at my end but I do not observe such behaviour. You can refer to the profile configuration that I have used and test the SDK demo without any changes.

sensorStop
flushCfg
dfeDataOutputMode 3
channelCfg 15 15 0
adcCfg 2 0
adcbufCfg -1 1 0 0 1
lowPower 0 0
%
profileCfg 0 77 267 7 57.14 0 0 70 1 384 13349 0 0 158
profileCfg 1 77 250 7 57.14 0 0 60 1 192 10000 0 0 158
%
chirpCfg 0 5 0 0 0 0 0 15
chirpCfg 6 11 1 0 0 0 0 15
%
advFrameCfg 2 0 0 1 0 2
subFrameCfg 0 0 0 6 16 200 0 1 1 200
subFrameCfg 1 0 6 6 64 200 0 1 1 200
%
guiMonitor -1 2 1 0 0 0 1
%
cfarCfg 0 1 3 16 0 0 1 24.0 0 7 0 1
cfarCfg 0 0 3 16 0 0 1 15.0 0 7 0 1
cfarCfg 1 1 3 16 0 0 1 24.0 0 7 0 1
cfarCfg 1 0 3 16 0 0 1 15.0 0 7 0 1
%
compressionCfg 0 1 0 0.5 8
compressionCfg 1 1 0 0.5 8
%
intfMitigCfg 0 15 18
intfMitigCfg 1 15 18
%
localMaxCfg 0 6 40
localMaxCfg 1 6 40
%
ddmPhaseShiftAntOrder 0 2 3 1
rangeProcCfg 2 0 300 300
antGeometryCfg 1 0 1 1 1 2 1 3 0 2 0 3 0 4 0 5 1 4 1 5 1 6 1 7 1 8 1 9 1 10 1 11 0.5 0.8
antennaCalibParams 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 1 0 1 0 1 0 1
measureRangeBiasAndRxChanPhase 0 1.5 0.2
analogMonitor 0 0
calibData 0 0 0x1f0000
%
aoaFovCfg -1 -90 90 -90 90
%
sensorStart

Attaching the output log for your reference - teraterm_oob_2944.log

Regards,

Samhitha

0 Dmitry Trots 22 hours ago in reply to Samhitha Bobba

Prodigy 40 points

Hi Samhitha

I have tested your profile and got object detections in both subframes.
My problem was in arguments of rangeProcCfg:

rangeProcCfg 2 0 10 12

I found that with your config (rangeProcCfg 2 0 300 300) in my environment detector returns fewer objects than in case of fast range processing option is disabled.
To restore objects number I had increased thresholds (rangeProcCfg 2 0 500 500).

Could you explain what magThresMinLim and magDiffThresMinLim actually mean?
Are these absolute values like ADC samples magnitudes?
How should I select these values?

Regards,

Dmitry

Sensors

Sensors forum

AWR2944: Zero detections in advanced subframe profile with fast rangeproc options