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.

AWR1642BOOST: demo visualizer cannot work when select 'range azimuth heat map'

Part Number: AWR1642BOOST

I am running the demo fron SDK3.5,and check the result using demo visualizer.

First,I didn't select 'range azimuth heat map' or 'range doppler heat map'.And visualizer worked correctly,I can see the point cloud.

However,when I select 'range azimuth heat map' or 'range doppler heat map',I can see nothing.

visualizer

There is the console message:

mmwDemo:/>% ***************************************************************
Skipped

mmwDemo:/>% Created for SDK ver:03.05
Skipped

mmwDemo:/>% Created using Visualizer ver:3.5.0.0
Skipped

mmwDemo:/>% Frequency:77
Skipped

mmwDemo:/>% Platform:xWR16xx
Skipped

mmwDemo:/>% Scene Classifier:best_range_res
Skipped

mmwDemo:/>% Azimuth Resolution(deg):15
Skipped

mmwDemo:/>% Range Resolution(m):0.044
Skipped

mmwDemo:/>% Maximum unambiguous Range(m):9.02
Skipped

mmwDemo:/>% Maximum Radial Velocity(m/s):1
Skipped

mmwDemo:/>% Radial velocity resolution(m/s):0.13
Skipped

mmwDemo:/>% Frame Duration(msec):100
Skipped

mmwDemo:/>% RF calibration data:None
Skipped

mmwDemo:/>% Range Detection Threshold (dB):15
Skipped

mmwDemo:/>% Doppler Detection Threshold (dB):15
Skipped

mmwDemo:/>% Range Peak Grouping:enabled
Skipped

mmwDemo:/>% Doppler Peak Grouping:enabled
Skipped

mmwDemo:/>% Static clutter removal:disabled
Skipped

mmwDemo:/>% Angle of Arrival FoV: Full FoV
Skipped

mmwDemo:/>% Range FoV: Full FoV
Skipped

mmwDemo:/>% Doppler FoV: Full FoV
Skipped

mmwDemo:/>% ***************************************************************
Skipped

mmwDemo:/>sensorStop
Ignored: Sensor is already stopped

Done

mmwDemo:/>flushCfg
Done

mmwDemo:/>dfeDataOutputMode 1
Done

mmwDemo:/>channelCfg 15 3 0
Done

mmwDemo:/>adcCfg 2 1
Done

mmwDemo:/>adcbufCfg -1 0 1 1 0
Done

mmwDemo:/>profileCfg 0 77 429 7 57.14 0 0 70 1 256 5209 0 0 30
Done

mmwDemo:/>chirpCfg 0 0 0 0 0 0 0 1
Done

mmwDemo:/>chirpCfg 1 1 0 0 0 0 0 2
Done

mmwDemo:/>frameCfg 0 1 16 0 100 1 0
Done

mmwDemo:/>lowPower 0 1
Done

mmwDemo:/>guiMonitor -1 1 1 0 1 1 1
Done

mmwDemo:/>cfarCfg -1 0 2 8 4 3 0 15 1
Done

mmwDemo:/>cfarCfg -1 1 0 4 2 3 1 15 1
Done

mmwDemo:/>multiObjBeamForming -1 1 0.5
Done

mmwDemo:/>clutterRemoval -1 0
Done

mmwDemo:/>calibDcRangeSig -1 0 -5 8 256
Done

mmwDemo:/>extendedMaxVelocity -1 0
Done

mmwDemo:/>bpmCfg -1 0 0 1
Done

mmwDemo:/>lvdsStreamCfg -1 0 0 0
Done

mmwDemo:/>compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
Done

mmwDemo:/>measureRangeBiasAndRxChanPhase 0 1.5 0.2
Done

mmwDemo:/>CQRxSatMonitor 0 3 5 121 0
Done

mmwDemo:/>CQSigImgMonitor 0 127 4
Done

mmwDemo:/>analogMonitor 0 0
Done

mmwDemo:/>aoaFovCfg -1 -90 90 -90 90
Done

  • Hello Chenming,

    Do you mean the Range Azimuth heat map is blank? Actually, heatmap display is not automatically adjusted according to the selected configuration. You might want to follow the steps highlighted in the below thread :

    About the recorded data of mmWave Demo Visualizer - Sensors forum - Sensors - TI E2E support forums

    e2e.ti.com
    Other Parts Discussed in Thread: IWR6843AOPEVM , IWR6843AOP Hi, Please help with the questions below: Testing environment: IWR6843AOPEVM ES2.0 mmWave Demo

    Please let us know if you're still not able to see the results.

    Regards,

    Ishita

  • Hello Ishita,

    Thank you for your reply,I will try it later.

    But what I really need,is to get the data of azimuth heat map.

    I have recorded about 3MB.

    But then I find all the packets content (and only content) 5 types of TLV.They are 

    MMWDEMO_OUTPUT_MSG_DETECTED_POINTS
    MMWDEMO_OUTPUT_MSG_DETECTED_POINTS_SIDE_INFO
    MMWDEMO_OUTPUT_MSG_RANGE_PROFILE
    MMWDEMO_OUTPUT_MSG_STATS
    MMWDEMO_OUTPUT_MSG_TEMPERATURE_STATS
    Now I need azimuth heat map,so I want to know how to get it.
  • Hey Chenming,

    The range azimuth heatmap results take a significant amount of time to be transmitted out of the device. The configuration you are testing with doesn't have sufficient interframe time for the results to be transmitted. Your framerate is set to 10fps, try resetting the device, setting the framerate to 5fps or lower and test again.

    Here's an example of insufficient interframe time:

    For the default configuration (only change being the framerate which I set to 5fps), the interframe processing takes about 6,500 usec, leaving 180,000 usec of interframe processing margin. The results are transmitted from the device in this margin.

    If I enable the range azimuth heatmap output, output transmit takes up about 100,000 usec. With it disabled, transmit output takes 8,700 usec. That is more than a 10x jump in output transmit time.

    If I set the framerate to 10fps, the interframe processing margin is around 80,000 usec. This is less than the 100,000 usec required to export the range azimuth heatmap. If I enable the range azimuth heatmap with 10fps, it would not finish transmitting the results for a frame by the time the next frame arrives, and would cause the program to crash. I think it is likely that the same is happening in your case. Let me know if reducing the framerate still doesn't resolve the issue.

    To check the interframe margins, transmit output times, etc on your end, enable statistics under plots selection, and have a look at the Plots->Profiling tab.

    Regards,

    Aayush