This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

IWR6843: Bug in CFG File Parameters for "Vital Signs Demo"

Part Number: IWR6843

I have found an issue with the parameters in the CFG files for the Vital Signs demo provided by the lab (mmwave_industrial_toolbox_4_12_1\labs\Vital_Signs\68xx_vital_signs\gui\gui.exe\VitalSignsRadar_Demo.exe).

The CFG files for "Front" and "Back" input seem to have incorrect parameters.

P.S.The CFG files for Front and Back are located at:

mmwave_industrial_toolbox_4_12_1\labs\Vital_Signs\68xx_vital_signs\gui\profiles\xwr68xx_profile_VitalSigns_20fps_Back.cfg.
mmwave_industrial_toolbox_4_12_1\labs\Vital_Signs\68xx_vital_signs\gui\profiles\xwr68xx_profile_VitalSigns_20fps_Front.cfg.

The parameter "calibDcRangeSig -1 0 0 0 0" in both CFG files must not have a "0" in the fifth item, or it will return an error: "Number of averaged chirps is not power of two."

The Vital Signs demo provided by the lab (...omitted...\gui.exe\VitalSignsRadar_Demo.exe) does not perform handshaking, so it can still display even if there is a problem.

Although the example still works normally, friends who are used to using handshaking to ensure stable transmission of UART may encounter development problems, maybe it does not work properly. (Yes, that's me...) Additionally, I found that changing the parameter to "calibDcRangeSig -1 0 0 0 4" seems to make the waveform of breathing and heart more obvious and accurate. (To be verified...)

Although this example seems to no longer be updated after "Radar toolbox 1.00.00.26", I still hope it can help everyone.
If this is not a BUG or if I am mistaken, please let me know. Thanks!!

Have a great day.