Other Parts Discussed in Thread: IWR1642
I'm trying to do a mid-range tracking chirp configuration for the IWR1642. I looked up how to write/edit .cfg files in mmWave SDK user guide, then edited the traffic monitoring lab's .cfg file to my own specifications, which I used mmWave Sensing Estimator to come up with. Really what I only end up editing is the profileCFG line.When I try to run this using the demo provided, the program crashes. What would I need to do to have my specified chirp configuration while using the demo?
Here is the configuration I wrote:
dfeDataOutputMode 1
channelCfg 15 3 0
adcCfg 2 1
adcbufCfg 0 1 1 1
profileCfg 0 76 2 4.9 52.4 0 0 16.17 1 195 4193 0 0 48
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
frameCfg 0 1 125 0 33.3 1 0
lowPower 0 1
guiMonitor 1 0 0 0
cfarCfg 4 4 15 16 8 6 0 63 63 0 1
doaCfg 1 0 1047 3 600 10 100
sceneryParam 1 -15 15 0.0 75.0 0 0 0 0 1 1.25 11.0 20.0 50.0 0 0 0 0
gatingParam 12 8 4 0
stateParam 3 10 20 2000 10
allocationParam 30 60 1.0 3 2.8 2.0
variationParam 1.15 0.433 1.0
trackingCfg 1 1 250 20 78 110 33 90
compRangeBiasAndRxChanPhase 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
sensorStart
And here is the original configuration for the traffic monitoring demo:
dfeDataOutputMode 1
channelCfg 15 3 0
adcCfg 2 1
adcbufCfg 0 1 1 1
profileCfg 0 76 2 4.9 52.4 0 0 16.17 1 195 4193 0 0 48
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
frameCfg 0 1 125 0 33.3 1 0
lowPower 0 1
guiMonitor 1 0 0 0
cfarCfg 4 4 15 16 8 6 0 63 63 0 1
doaCfg 1 0 1047 3 600 10 100
sceneryParam 1 -15 15 0.0 75.0 0 0 0 0 1 1.25 11.0 20.0 50.0 0 0 0 0
gatingParam 12 8 4 0
stateParam 3 10 20 2000 10
allocationParam 30 60 1.0 3 2.8 2.0
variationParam 1.15 0.433 1.0
trackingCfg 1 1 250 20 78 110 33 90
compRangeBiasAndRxChanPhase 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
sensorStart
The SDK user guide I was using is 2.01.00.04
