IWR6843: What's wrong with profileCfg of IWR6843's cfg?

user6005362

Part Number: IWR6843

Dear TechnicalSupport

I use IWR6843 ISK(ES2.0) following FW was burned.

C:\ti\mmwave_industrial_toolbox_4_2_1\labs\people_counting\68xx_3D_people_counting\prebuilt_binaries\3D_people_count_68xx_demo.bin

And, I can work IWR6843 using following cfg.

C:\ti\mmwave_industrial_toolbox_4_2_1\labs\people_counting\68xx_3D_people_counting\chirp_configs\ISK_6m_default.cfg

But, I changed "profileCfg", IWR6843 is not able to work.

What's wrong with profileCfg?

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

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 7 0
adcCfg 2 1
adcbufCfg -1 0 1 1 1
lowPower 0 0
%profileCfg 0 60.75 7 7 41.10 1184274 0 54.7125 1 96 2950.00 0 0 36 orginal
profileCfg 0 60 7 7 28 0 0 60 1 256 12500 0 0 48
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
chirpCfg 2 2 0 0 0 0 0 4
frameCfg 0 2 96 0 50 1 0
dynamicRACfarCfg -1 4 4 2 4 8 16 4 4 4.00 4.50 0.50 1 1
staticRACfarCfg -1 4 4 2 4 8 16 4 6 8.00 13.00 0.30 0 0
dynamicRangeAngleCfg -1 0.75 0.0010 1 0
dynamic2DAngleCfg -1 3 0.0300 1 0 1 0.50 0.85 8.00
staticRangeAngleCfg -1 1 8 2
antGeometry0 0 -1 -2 -3 -2 -3 -4 -5 -4 -5 -6 -7
antGeometry1 -1 -1 -1 -1 0 0 0 0 -1 -1 -1 -1
antPhaseRot 1 1 1 1 1 1 1 1 1 1 1 1
fovCfg -1 70.0 20.0
compRangeBiasAndRxChanPhase 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
staticBoundaryBox -2 2 2 8.5 -2 2
boundaryBox -2.5 2.5 0.5 6 -2.5 2.5
sensorPosition 2 0 10
gatingParam 3 1.5 1.5 2 0
stateParam 3 3 10 40 5 600
allocationParam 200 800 0.1 15 0.5 20
trackingCfg 1 2 1000 20 67 105 50
sensorStart

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

Best Regrads

over 5 years ago

0 Akash Gondalia over 5 years ago

TI__Guru 50240 points

Hi User,

Can you elaborate on why you have changed the profileCfg this way?

We'll need a few days for a response.

Regards,

0 Former Member over 5 years ago

The cfg you have created is invalid because it exceeds the radar cube size limitation. In your cfg the radar cube size would 1152 kB when the limit is 768.

Please see this thread on how you can perform these calculations yourself: https://e2e.ti.com/support/sensors/f/1023/t/895114

Amanda

0 user6005362 over 5 years ago in reply to Former Member

Intellectual 640 points

Dear Amanda

Thank you for your reply.

The calculate method of "radar cube size" is below, isn't it?

{radar cube size} = {float:4Byte} × {Tx Antenna:4} × {Tx Antenna:4} × numAdcSamples × numberOfLoops

But even if I reduce numberOfLoops to reduce radar cube size, it doesn't work.

The radar cube size of below cfg is 197kB and smaller than 768kB.

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

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 7 0
adcCfg 2 1
adcbufCfg -1 0 1 1 1
lowPower 0 0
%profileCfg 0 60.75 7 7 41.10 1184274 0 54.7125 1 96 2950.00 0 0 36 orginal
profileCfg 0 60 7 7 28 0 0 60 1 256 12500 0 0 48
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
chirpCfg 2 2 0 0 0 0 0 4
%frameCfg 0 2 96 0 50 1 0
frameCfg 0 2 16 0 50 1 0
dynamicRACfarCfg -1 4 4 2 4 8 16 4 4 4.00 4.50 0.50 1 1
staticRACfarCfg -1 4 4 2 4 8 16 4 6 8.00 13.00 0.30 0 0
dynamicRangeAngleCfg -1 0.75 0.0010 1 0
dynamic2DAngleCfg -1 3 0.0300 1 0 1 0.50 0.85 8.00
staticRangeAngleCfg -1 1 8 2
antGeometry0 0 -1 -2 -3 -2 -3 -4 -5 -4 -5 -6 -7
antGeometry1 -1 -1 -1 -1 0 0 0 0 -1 -1 -1 -1
antPhaseRot 1 1 1 1 1 1 1 1 1 1 1 1
fovCfg -1 70.0 20.0
compRangeBiasAndRxChanPhase 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
staticBoundaryBox -2 2 2 8.5 -2 2
boundaryBox -2.5 2.5 0.5 6 -2.5 2.5
sensorPosition 2 0 10
gatingParam 3 1.5 1.5 2 0
stateParam 3 3 10 40 5 600
allocationParam 200 800 0.1 15 0.5 20
trackingCfg 1 2 1000 20 67 105 50
sensorStart

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

Bes Regards.

0 Former Member over 5 years ago in reply to user6005362

Hello,

This issue is continues on this thread: https://e2e.ti.com/support/sensors/f/1023/t/897426

I'll close this one.

Thanks,

Amanda

Sensors

Sensors forum

IWR6843: What's wrong with profileCfg of IWR6843's cfg?