IWR6843ISK: Does Demo Visualizer 3.6 support chirp per frame less than 16

Hello,

I changed the parameters of the frameCfg configuration chirp number in the .cfg file. After loading the configuration from the PC, mmWave Demo Visualizer could not visualize it. No error was reported, but there was no response when clicking the radar to start.

In addition, when using DCA1000 CLI to collect raw data without using mmWaveStudio, I found that DCA1000 did not flash and could not capture data.

Regards,

Gary

Hello Gary,

The mmWave Sensing Estimator will help with chirp design. Although the firmware will allow parameters to be within a certain range, the parameters must all together come to make a working chirp design. For example freqSlope is a value that the firmware can accept values above 240, but if you set timings too small such as rampEndTime, then the sensor won't be able to start. The sensing estimator tool will help point out when there are issues with the values you have set in your configuration.

With regards to the DCA1000, I will need more details in what you are doing and what you have tried in order to capture raw data. Note that the DCA1000 is for raw, unfiltered, unprocessed ADC data that dumps the IF signal. For things such as the point cloud a DCA1000 is not needed.

Best Regards,

Pedrhom

Hello，

Thank you for your reply. I hope mmWaveStudio is not used to obtain the raw ADC data, so DCA1000 seems necessary.
My. cfg file seems to have no errors configured in the millimeter wave sensor estimator, but it cannot start the radar after loading in the mmWave Demo Visualizer.
My configuration is as follows:

SensorStop
FlushCfg
DfeDataOutputMode 1
ChannelCfg 15 1 0
AdcCfg 2 1
AdcbufCfg-1 0 1 1 1 1
ProfileCfg 0 60 100 6 60 0 0 66 1 108 2000 0 158
ChirpCfg 0 0 0 0 0 0 0 0 1
FrameCfg 0 0 1 0 40 1 0
LowPower 0 0
GuiMonitor -1 0 1 0 0 0 0 0 0 0
CfarCfg-1 0 2 8 4 3 0 15 1
CfarCfg-1 1 0 4 2 3 1 15 1
MultiObjBeamForming -1 1 0.5
ClutterRemoval -1 0
CalibDcRangeSig-1 0-5 8 256
ExtendedMaxVelocity -1 0
BpmCfg-1 0 0 1
LvdsStreamCfg-1 0 1 0
CompRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0
MeasureRangeBiasAndRxChanPhase 0 1.5 0.2
CQRxSatMonitor 0 3 4 121 0
CQSigImgMonitor 0 39 4
AnalogMonitor 0 0
AoaFovCfg-1-90 90-90 90
CfarFovCfg-1 0 0 2.89
CfarFovCfg-1 1-0.41 0.41
CalibData 0 0 0
SensorStart

Regards，

Gary

Hello Gary,

Do you happen to own a MMWAVEICBOOST? With a 6843ISK + MMWAVEICBOOST you can get runtime debug and error messages which can give a detailed error code on where sensor start crashed.

If you do not have a MMWAVEICBOOST, what I would recommend is start with a known working "default" configuration, such as one found within the MMWAVE-SDK installation, and slowly change parameters one by one until it does not work. Based on the config you have sent, I am guessing there is something the sensor does not like between profileCfg and frameCfg. Does that same exist config work when only numLoops is changed?

Best Regards,

Pedrhom

Hello，

I don't have MMWAVEICBOOST. The configurations listed above are ineffective when only numLoops are modified compared to working properly.

Regards，

Gary

Hello Gary,

Your cfg has "-" all over the place and so I cannot test it and see what the error is. I tried guessing how it was supposed to be but could not proceed. Can you please provide your config as you send it to device?

Best Regards,

Pedrhom