IWR6843: potential bug in max-range calculation in mmWaveSensingEstimator v2.2.2

daniel zelyanski

Part Number: IWR6843

Hi,

Seems that the calculation for max-range is incorrect. In the previous version 2.2.1, I was getting different values.
My guess is that it has to do with bad calculation of the IF frequency which remains constant (10MHz) in this latest version (2.2.2)

over 2 years ago

0 Nathan Block over 2 years ago

TI__Mastermind 37785 points

Hi Daniel,

I know the max range calculation has some safety factor built into it, like 80-90% to avoid aliasing. Is that the behavior you're experiencing?

Best,

Nate

0 daniel zelyanski over 2 years ago in reply to Nathan Block

Prodigy 20 points

Hi Nathan.
No the issue isn't the safety factor, but rather a bad computation of the max-range.
e.g:

for this configuration:
profileCfg 0 61 2.5 3 24 0 0 5.2 1 128 6500 0 0 48
I'm getting 288m max range in v2.2.2
and was getting 150m in v2.2.1

0 Nathan Block over 2 years ago in reply to daniel zelyanski

TI__Mastermind 37785 points

Hi Daniel,

Thank you for this screenshot. I'll forward it to the relevant team. Give me a day or two to get an answer.

Best,

Nate

+1 Luke Rouleau over 2 years ago in reply to daniel zelyanski

TI__Expert 4448 points

Hi Daniel,

Thank you for pointing out this bug. The fix has been deployed in v2.2.2.

Regards,
Luke

Sensors

Sensors forum

IWR6843: potential bug in max-range calculation in mmWaveSensingEstimator v2.2.2