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.

IWR1843BOOST: Request for Guidance on Editing TI IWR1843BOOST .cfg File to Enable Long-Term Zero-Doppler Detection and Zone Monitoring

Part Number: IWR1843BOOST
Other Parts Discussed in Thread: DCA1000EVM

Tool/software:

I’m using a TI IWR1843BOOST radar (no DCA1000EVM).
The only thing I need right now is to tune the on-board .cfg file.

Enable long-dwell zero-Doppler (stationary) detections for vehicles & pedestrians, raise point-cloud density, and mark ~15 rectangular zones (≈ 8 m × 10 m) for dwell-time statistics.

  1. Which exact .cfg commands & fields directly affect stationary detections

  2. How to tweak each parameter—state which direction to move the value (increase / decrease / disable) and why it lengthens the visibility of stationary objects for 5–15 minutes.

  3. my current config file:            

    % ***************************************************************

    % Created for SDK ver:03.06

    % Created using Visualizer ver:3.6.0.0

    % Frequency:77

    % Platform:xWR18xx

    % Scene Classifier:best_range

    % Azimuth Resolution(deg):15

    % Range Resolution(m):0.32

    % Maximum unambiguous Range(m):45

    % Maximum Radial Velocity(m/s):16.2

    % Radial velocity resolution(m/s):1.02

    % Frame Duration(msec):100

    % RF calibration data:None

    % Range Detection Threshold (dB):15

    % Doppler Detection Threshold (dB):15

    % Range Peak Grouping:enabled

    % Doppler Peak Grouping:enabled

    % Static clutter removal:disabled

    % Angle of Arrival FoV: Full FoV

    % Range FoV: Full FoV

    % Doppler FoV: Full FoV

    % ***************************************************************

    sensorStop

    flushCfg

    dfeDataOutputMode 1

    channelCfg 15 5 0

    adcCfg 2 1

    adcbufCfg -1 0 1 1 1

    profileCfg 0 77 8 7 22.06 0 0 33.333 1 176 12499 0 0 30

    chirpCfg 0 0 0 0 0 0 0 1

    chirpCfg 1 1 0 0 0 0 0 4

    frameCfg 0 1 32 0 100 1 0

    lowPower 0 0

    guiMonitor -1 1 1 0 0 0 1

    cfarCfg -1 0 2 8 4 3 0 15 1

    cfarCfg -1 1 0 8 4 4 1 15 1

    multiObjBeamForming -1 1 0.5

    clutterRemoval -1 0

    calibDcRangeSig -1 0 -5 8 256

    extendedMaxVelocity -1 0

    lvdsStreamCfg -1 0 0 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 43 0

    CQSigImgMonitor 0 87 4

    analogMonitor 0 0

    aoaFovCfg -1 -90 90 -90 90

    cfarFovCfg -1 0 0 44.99

    cfarFovCfg -1 1 -16.2 16.20

    calibData 0 0 0

    sensorStart                                                                                                                                                                                                                                                                                                                                   

  4. How to add commands to the existing cfg files?

    • Which exact .cfg commands & fields directly affect stationary detections

    Disable clutter removal if you want to detect stationary objects

    • How to tweak each parameter—state which direction to move the value (increase / decrease / disable) and why it lengthens the visibility of stationary objects for 5–15 minutes.

    retaining an absolutely stationary target for 5-15 minutes is not within the scope of this demo. You may adjust the state machine in stateParams, but your performance is not guaranteed.

  • 1. I have disabled static clutter removal

    2.  The stateparams is not recognised when I am trying to add in  the config file. The warning/error message is provided below

    Warning: The command stateParam 15 10 10 1000 10 1000 sent to the board responded with a message other than 'Done'. The following response is received from the board:
    'stateParam' is not recognized as a CLI command
    The following config file is been used 
    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 5 0
    adcCfg 2 1
    adcbufCfg -1 0 1 1 1
    profileCfg 0 77 8 7 27.23 0 0 50 1 240 12499 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 4
    frameCfg 0 1 64 0 33.333 1 0
    lowPower 0 0
    guiMonitor -1 1 1 0 0 0 1
    cfarCfg -1 0 2 8 4 3 0 15 1
    cfarCfg -1 1 0 8 4 4 1 15 1
    multiObjBeamForming -1 1 0.5
    clutterRemoval -1 0
    calibDcRangeSig -1 0 -5 8 256
    extendedMaxVelocity -1 0
    lvdsStreamCfg -1 0 0 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 59 0
    CQSigImgMonitor 0 119 4
    analogMonitor 0 0
    aoaFovCfg -1 -90 90 -90 90
    cfarFovCfg -1 0 0 29.99
    cfarFovCfg -1 1 -13.82 13.82
    stateParam 15 10 10 1000 10 1000
    calibData 0 0 0
    sensorStart
    Please let me know, how do i configure the parameters pertaining to stationary object detection in the config file
  • Hi,

    You need to match the configuration file to the demo. stateParams is only used in demos that use the tracker software, so you will want to use something like the area scanner/people tracking/traffic monitor demos if you want to use this configuration line.

    See people counting here : https://dev.ti.com/tirex/explore/node?a=1AslXXD__1.30.00.05&a=1AslXXD__3.10.00.05&node=A__ANjUW438.4uhprheaQjwgQ__radar_toolbox__1AslXXD__3.10.00.05&r=1AslXXD__1.00.00.26&r=1AslXXD__1.00.01.07

    Best,

    Nate