IWR6843ISK: CLI command issue

Takatoshi Tsuji

Part Number: IWR6843ISK

Dear support team,

I am now creating some of CLI commands by changing chirp rate and number of loops. Unfortunately, below CLI command is not accepted.

It can be accepted if number of loops is reduced from 128 to 88. I am fine if you can advise which value should be reviewed by keeping number of loops = 128 & chirp rate = 64.

[NG]

profileCfg 0 60 230 10 60 0 0 64 1 144 3000 0 0 36
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 4
frameCfg 0 1 128 0 200 1 0

[OK]

profileCfg 0 60 230 10 60 0 0 64 1 144 3000 0 0 36
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 4
frameCfg 0 1 88 0 200 1 0

Bets regards,

Taka

over 4 years ago

0 Sabeeh Khan1 over 4 years ago

TI__Mastermind 30790 points

Hello,

Lowering the number of samples is one solution to your concern. I have tested this configuration on my IWR6843ISK and it is functional. See the example below. I have lowered number of samples to 95.

profileCfg 0 60 230 10 60 0 0 64 1 95 3000 0 0 36
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 4
frameCfg 0 1 128 0 200 1 0

0 Takatoshi Tsuji over 4 years ago in reply to Sabeeh Khan1

Expert 1550 points

Hello Sabeeh,

Thank you for your message. It seems there is limitation or rules among number of loops, number of samples and chirp rate. I am fine if you make clear it for me or introduce document to learn it.

Best regards,

Taka

0 Sabeeh Khan1 over 4 years ago in reply to Takatoshi Tsuji

TI__Mastermind 30790 points

Hello Taka,

We have some documents that can assist in your learning. First is the mmWave SDK User Guide. You can find this document after installing the mmWave SDK. The second document is an application note that describes other chirp parameters.

Link to mmWave SDK User Guide after installation: C:\ti\mmwave_sdk_03_05_00_04\docs\mmwave_sdk_user_guide.pdf

Link to app note: https://www.ti.com/lit/an/swra553a/swra553a.pdf?ts=1615416383966&ref_url=https%253A%252F%252Fwww.ti.com%252Fsensors%252Fmmwave-radar%252Findustrial%252Ftechnical-documents.html

0 Takatoshi Tsuji over 4 years ago in reply to Sabeeh Khan1

Expert 1550 points

Hello Sabeeh,

Excuse me that I can't find any description regarding the limitation among 3 parameters. I am fine if you advise where to check on it.

Best regards, Taka

+1 Sabeeh Khan1 over 4 years ago in reply to Takatoshi Tsuji

TI__Mastermind 30790 points

Hi Taka,

What was happening here is that the radar cube data was overloading the L3 memory. This was solved by lowering the number of samples. In Table 1 of the app note I linked above, you can see this kind of relationship between all of the chirp parameters. Though you have only experimented with three parameters, there are many more at play and will have an effect on performance (range resolution, angle resolution, L3 memory, etc.).

If you have an ICBOOST, you can debug the program and find this.

Sensors

Sensors forum

IWR6843ISK: CLI command issue