• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 549 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.

WEBENCH® Tools/IWR1843BOOST: Simple example for doppler/azimut heatmap

Arnaud DOME
Prodigy 50 points
Part Number: IWR1843BOOST
Other Parts Discussed in Thread: IWR1843

Tool/software: WEBENCH® Design Tools

Hello,

I want a simple example which stream at more than 5 FPS azimut and/or doppler heatmap. I find the "Out of box" project in Industrial labs but the FPS is really limited for azimut heatmap because it is computed in Demo_Visualizer.

Is there an exemple which stream preprocessed doppler and azimut heatmap into a UI?

  • 0
    TI__Mastermind 25835 points

    Hello,

        Unfortunately, This limitation is coming from the UART baud rate which is set to 921600. At higher frame rates number of data points exceeds max available baud rate, Hence higher frame rates could be challenging.

    You could refer to below section from the demo visualizer user-guide.

    https://www.ti.com/lit/ug/swru529c/swru529c.pdf

        

    However, you could reduce the number points by some performance trade-offs such as using 1 Tx 1 Rx or 1Tx two Rx etc.. and have only one plot.. (Configure chirp in such a manner which reduces data throughput under the UART max limit). 

    If still problem exist you may have port the demo with other interface such as SPI interface, and you way have to build your own application interface for this. Unfortunately TI doesn't have demo GUI for this purpose. 

    Thanks and regards,

    CHETHAN KUMAR Y.B.

  • 0 in reply to CHETHAN KUMAR Y.B.
    Prodigy 50 points

    I the IWR1843, if I want to stream the doppler range heatmap, its resolution is 64x48xsizeof(uint16), so you can't stream more than 1 fps at 921600?

    More in Demo Visualizer, the azimut heatmap is processed in the GUI whereas in "Vital sign occupancy " project the heatmap is processed in DSS and just display in matlab and the stream have more fps than the " Demo Visualizer" binary from Out of box.

    So at 921600 you can stream at more than 1 fps azimut heatmap and doppler heatmap (at 64*48) so does the limitation come from the MailBox between DSS and MSS? 

  • Former Member
    0 Former Member in reply to Arnaud DOME

    Hello,

    The frame rate limitation is a check that was imposed by the visualizer since users can conceivably configure a chirp cfg with idle time that is too short to allow for the subset of the radar cube to be sent out.

    However this limitation is removed in the latest SDK version (3.4+) if you configure the demo to use a custom higher baud rate. Please see Serial Port Setup: https://www.ti.com/lit/ug/swru529c/swru529c.pdf?ts=1594073638017

    "Data_port: Use the COM port XDS110 Class Auxiliary Data Port and set Baud: 921600. User can leverage higher baud rates than 921600 by selecting "custom" in the Baud Rates drop down and setting the desired value (max: 3125000). Recommended values are: 1834000 or 3125000. Note that the sensor should be in stopped or rebooted state for the changes to take effect. Visualizer communicates with the sensor over CLI port to configure it to the user provided baud rate in this dialog box."

    Depending on your configuration you may achieve a higher frame rate than 5FPS. However, as noted other demos such as the Vehicle Occupancy Demo compute the heatmap on the device and display at a higher frame rate  http://dev.ti.com/tirex/explore/node?node=ACYlsTvoGX5xmOEhr6PyFA__AocYeEd__LATEST You can use this demo as a reference for your application. However note the heatmap here is not the same as the static r ange-azimuth heatmap in the OOB demo.

    Amanda

     

  • 0 in reply to Former Member
    Prodigy 50 points

    AmandaN said:

    The frame rate limitation is a check that was imposed by the visualizer since users can conceivably configure a chirp cfg with idle time that is too short to allow for the subset of the radar cube to be sent out.

    I want  to remove radar cube in package and just send the azimut_heat_map processed data.

    AmandaN said:

    Depending on your configuration you may achieve a higher frame rate than 5FPS. However, as noted other demos such as the Vehicle Occupancy Demo compute the heatmap on the device and display at a higher frame rate  http://dev.ti.com/tirex/explore/node?node=ACYlsTvoGX5xmOEhr6PyFA__AocYeEd__LATEST You can use this demo as a reference for your application. However note the heatmap here is not the same as the static r ange-azimuth heatmap in the OOB demo.

    Indeed my goad was to use that example and to send the azimut heat map. Was is the differents between heatmap and range-azimuth heatmap ?

  • Former Member
    0 Former Member in reply to Arnaud DOME

    At a high level the OOB demo shows the static range azimuth heatmap (signal only from zero doppler bin) while the VOD demo shows the dynamic range azimuth heatmap (signal only from >0 doppler bins). Additionally the VOD demo has additional algorithms to "clean up" the heatmap to enable better localization.

  • 0 in reply to Former Member
    Prodigy 50 points

    And what is the azimut heatmap output type in the MMwave Visualizer? 

  • Former Member
    0 Former Member in reply to Arnaud DOME

    When I refer to the OOB above this is the same as the mmWave Visualizer