Other Parts Discussed in Thread: IWR1642
Hi, TI teams,
In the traffic_monitoring Demo cinfig file(C:\ti\mmwave_industrial_toolbox_3_6_1\labs\lab0013_traffic_monitoring_16xx\chirp_configs\mmw_tm_demo_longRange.cfg)
-----------------------------------
sensorStop
sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 1 0
adcCfg 2 1
adcbufCfg 0 1 1 1
profileCfg 0 76 2 5 52.62 0 0 4.007 1 256 5490 0 0 48
chirpCfg 0 0 0 0 0 0 0 1
frameCfg 0 0 118 0 50 1 0
lowPower 0 1
guiMonitor 1 0 0 0
cfarCfg 4 12 2 16 8 4 0 63 63 0 1
doaCfg 3 0 1047 3 600 10 100
trackingCfg 1 1 250 20 189 330 50 90
%for 18xx board SN4855900006
compRangeBiasAndRxChanPhase -0.0438848 0.12320 -0.62793 0.08932 -0.50342 -0.03458 -0.58853 0.06812 -0.69101 -0.79391 -0.60803 -0.63580 -0.45255 -0.70901 -0.26627 -0.73044 -0.46078
sensorStart
---------------------------
I send the "Help" command to IWR1642, it responds:
******************************************
MMW TM Demo 0.0.0.2
******************************************
mmwDemo:/>help
Help: This will display the usage of the CLI commands
Command: Help Description
sensorStart: No arguments
sensorStop: No arguments
frameStart: No arguments
guiMonitor: <detectedObjects> <logMagRange> <rangeAzimuthHeatMap> <rangeDopplerHeatMap>
cfarCfg: <detMode> <discardLeft> <discardRight> <refWinSize1> <refWinSize2> <guardWinSize1> <guardWinSize2> <thre>
doaCfg: <doaMode> <doaGamma> <sideLobe_dB> <searchRange> <searchRes> <varThre>
trackingCfg: <enable> <paramSet> <numPoints> <numTracks> <maxDoppler> <framePeriod>
dataLogger: <mssLogger | dssLogger>
adcbufCfg: <adcOutputFmt> <SampleSwap> <ChanInterleave> <ChirpThreshold>
compRangeBiasAndRxChanPhase: <rangeBias> <Re00> <Im00> <Re01> <Im01> <Re02> <Im02> <Re03> <Im03> <Re10> <Im10> <Re11> <Im11> <Re12> <Im12> <Re13> <Im13>
sceneryParam: <numBoundaryBox> <Left1> <Right1> <Bottom1> <Top1> <Left2> <Right2> <Bottom2> <Top2> <numStaticBox> <Left1> <Right1> <Bottom1> <Top1> <Left2> <Right2> <Bottom2> <Top2>
gatingParam: <gating volume> <length> <width> <doppler>
stateParam: <det2act> <det2free> <act2free> <stat2free> <exit2free>
allocationParam: <SNRs> <minimal velocity> <points> <in distance> <in velocity>
variationParam: <height> <width> <doppler>
help: No help available
****************************************************
mmWave Extension Help
****************************************************
version: No help available
flushCfg: No help available
dfeDataOutputMode: No help available
channelCfg: No help available
adcCfg: No help available
profileCfg: No help available
chirpCfg: No help available
frameCfg: No help available
advFrameCfg: No help available
subFrameCfg: No help available
lowPower: No help available
contModeCfg: No help available
bpmCfgAdvanced: No help available
I find that some commands format are different with TI traffic_monitoring Demo cinfig file, for example,
CLI commands: trackingCfg: <enable> <paramSet> <numPoints> <numTracks> <maxDoppler> <framePeriod>
Demo config cmd: trackingCfg 1 1 250 20 189 330 50 90
they are different?
Regards
eric
