I was reviewing the control commands sent when using the the OOB SDK demo (attached below) and I noticed that couple commands were repeated with different arguments. I am not really clear if this intentionally done and why?
% Carrier frequency GHz 60.25 % Ramp Slope MHz/us 156 % Num ADC Samples 256 % ADC Sampling Rate Msps 12.5 % ADC Collection Time us 20.48 % Extra ramp time required (start time) us 3 % Chirp time (end time - start time) us 21 % Chirp duration (end time) us 24 % Sweep BW (useful) MHz 3194.88 % Total BW MHz 3744 % Max beat freq (80% of ADC sampling rate) MHz 10 % Max distance (80%) m 9.62 % Range resolution m 0.047 % Range resolution (meter per 1D-FFT bin) m/bin 0.047 % % Inter-chirp duration us 7 % Number of chirp intervals in frame - 64 % Number of TX (TDM MIMO) 2 % Number of Tx elevation antennas 0 % Number of RX channels - 4 % Max umambiguous relative velocity kmph 72.28 % mileph 45.17 % Max extended relative velocity kmph 144.56 % mileph 90.35 % Frame time (total) ms 1.984 % Frame time (active) ms 1.536 % Range FFT size - 256 % Doppler FFT size - 32 % Radar data memory required KB 272 % Velocity resolution m/s 1.25 % Velocity resolution (m/s per 2D-FFT bin) m/s/bin 1.25 % Velocity Maximum m/s 20.08 % Extended Maximum Velocity m/s 40.16 % Maximum sweep accorss range bins range bin 0.85 % sensorStop flushCfg dfeDataOutputMode 1 channelCfg 15 5 0 adcCfg 2 1 adcbufCfg -1 0 1 1 1 lowPower 0 0 profileCfg 0 60.25 568 7 53.57 0 0 70 1 224 4915 0 0 30 chirpCfg 0 0 0 0 0 0 0 1 chirpCfg 1 1 0 0 0 0 0 4 frameCfg 0 1 16 0 100 1 0 guiMonitor -1 1 0 0 0 0 0 cfarCfg -1 0 0 8 4 4 0 1280 1 cfarCfg -1 1 0 4 2 3 1 1280 1 multiObjBeamForming -1 1 0.5 calibDcRangeSig -1 0 -5 8 256 clutterRemoval -1 1 compRangeBiasAndRxChanPhase 0.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 measureRangeBiasAndRxChanPhase 0 1.5 0.2 aoaFovCfg -1 -90 90 -90 90 cfarFovCfg -1 0 0 8.42 cfarFovCfg -1 1 -1 1.0 sensorStart
