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.

IWR1642BOOST: No Azimuth-Range Heatmap data was showed in the mmWave Demo Visualizer

Part Number: IWR1642BOOST

Hello,

I am using IWR1642Boost and want to see the Azimuth-Range Heatmap data with the mmWave Demo Visualizer. 

I first flash the OOB demo bin with SDK 3.5 to IWR1642BOOST, then connected it to the mmWave Demo Visualizer (Browser version) with uart cable (115200 for command, 921600 for data).

I was successfully plotting the detected points with the mmWave Demo Visualizer with the default settings of "Best Range Resolution"

Then, I choose to show "Range Azimuth Heat Map". However nothing was showed. I didn't reset the device before I send the new config to  IWR1642BOOST.

What is the possible reason?

Thank you very much!

Best,

Hang

  • Hello

    Can you please confirm that point cloud can be seen as expected. What configuration is being sent to the visualizer to enabled the Azimuth plots.

    Thank you,

    Vaibhav

  • Hi Vaibhav,

    Thanks for reply. Yes, I can see the detected pointcloud using the mmWave Demo Visualizer. 

    However, when I chose the Azimuth heat map, nothing was shown. 

    I have attached the cfg file. Thanks a lot. 

    % Scene Classifier:best_range_res
    % Azimuth Resolution(deg):15
    % Range Resolution(m):0.044
    % Maximum unambiguous Range(m):9.02
    % Maximum Radial Velocity(m/s):1
    % Radial velocity resolution(m/s):0.13
    % Frame Duration(msec):100
    % RF calibration data:None
    % Range Detection Threshold (dB):15
    % Doppler Detection Threshold (dB):15
    % Range Peak Grouping:enabled
    % Doppler Peak Grouping:enabled
    % Static clutter removal:disabled
    % Angle of Arrival FoV: Full FoV
    % Range FoV: Full FoV
    % Doppler FoV: Full FoV
    % ***************************************************************
    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 3 0
    adcCfg 2 1
    adcbufCfg -1 0 1 1 0
    profileCfg 0 77 429 7 57.14 0 0 70 1 256 5209 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 2
    frameCfg 0 1 16 0 100 1 0
    lowPower 0 1
    guiMonitor -1 0 0 0 1 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 0 0
    compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
    measureRangeBiasAndRxChanPhase 0 1.5 0.2
    CQRxSatMonitor 0 3 5 121 0
    CQSigImgMonitor 0 127 4
    analogMonitor 0 0
    aoaFovCfg -1 -90 90 -90 90
    cfarFovCfg -1 0 0 8.92
    cfarFovCfg -1 1 -1 1.00
    sensorStart

    Best,
    Hang

  • Hello Hang,

    Thank you for providing these details. Heat map must be selected before sending the .cfg. If you are still unable to see it, ensure that the frame rate is low (less than 5 fps).

    Finally, be sure you are using chrome for better performance.

  • Hi Sabeeh,

    Thanks! My bad, I should set the frame rate manually (less than 5). It works!

    Best,

    Hang

  • Hi Sabeeh,

    Actually, I have another quick question on the frame rate. I set the frame rate low than 5fps, then send the config to the IWR1642Boost and it worked. 

    However, in the cfg file, I didn't see the frame rate parameter. How the cfg file worked to make the frame rate lower?

    Thanks a lot!

    Best,

    Hang 

  • The fps is changed in frameCfg.

    For more information on chirp parameters, please see Table 1 of the mmWave User's guide after installing the mmWave SDK: https://www.ti.com/tool/MMWAVE-SDK