• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 32 subscribers
  • Views 329 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: GUI Speed

Mark Ackerson
Genius 10190 points
Part Number: IWR1642BOOST

When using the heatmap, the GUI lags the sensor by about 45 seconds. If I make a target change in front of the sensor, I have to wait 45 seconds before the GUI graphs update. If I click the Stop button or download button, I have to wait 45 seconds for the GUI to catch up before the stop or download takes effect.

This makes testing difficult.  Why the long delays?

Regards,
Mark

  • 0
    TI__Mastermind 23725 points

    HI Mark,

    This because of the limitation of the data speeds of UART.

    For heat map we send out a large amount of data per frame to be displayed and uart needs enough time to send that and display it.

    A few options you could play with is:

    Reduce the number of samples per chirp

    This will reduce the range resolution and you can see further implications for in mmWave Estimator tool.  However it will still let you get a feel for the scene as sensed by mmWave Device sensor.

    And can serve as a good debug view only feature.

    After that you can switch to the desire ADC sample number for sensing mode in visualizer.

    Also please make sure you have only one heat map on at a time  either the doppler or the range azimuth as each of these have their own data set streamed out when enabled.

    If you see yourself needing to use this mode often then you might want to try the TSW1400 setup which provides snapshot over a few frames.

    Although not streaming it will still capture those few frames at run time speed.

    mmWave Sensor Raw Data Capture Using the TSW1400 Board

    Thank you,

    Vaibhav