• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 407 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.

RTOS/AWR1642BOOST: Problems due to change of idle time of Chirp

JP Park95
Expert 1100 points
Part Number: AWR1642BOOST

Tool/software: TI-RTOS

Hi, 

I tried to change the chirp idle time  & frame duration of configuration in lab0003_occupancy_detection, but What was detected in the previous configuration was not detected after the change. 

Does the idle time of Chirp & duration of frame affect the value of fft or hitmap ?

  • Existing configuration

              profileCfg 0 77 250 10 40 0 0 98 1 64 2200 0 0 40

             frameCfg 0 3 128 0 160 1 0

  • Changed configurationprofileCfg

              profileCfg 0 77 110 10 40 0 0 98 1 64 2200 0 0 40

             frameCfg 0 3 128 0 80 1 0

. SDK Version : sdk_02_00_00_04

  Tool Box Version : mmwave_automotive_toolbox_2_4_7.

Regards

JP

  • 0
    TI__Guru 69970 points
    Hi,
    Chirp and frame duration will impact the output specification (range, velocity, resolution etc.)
    I would recommend you go over the training material to get to know how these parameters are related to processing output.
    training.ti.com/mmwave-training-series

    Regards,
    JG
  • 0 in reply to Jitendra Gupta
    Expert 1100 points
    Hi JG,
    Thank you for your quick reply.

    Since the chirp idle time & frame duration affects the velocity resolution(V=/) , I thought that lab0003_occupancy_detection App would not affect hitmap data.
    Is my idea wrong ?
    If the hitmap value changes, please explain it in detail.
    Regards,
    JP
  • 0 in reply to JP Park95
    TI__Mastermind 21025 points

    The chirp configuration for this demo has been optimized for velocity resolution.  If you decrease the idle time so that you can increase the frame rate, then you are sacrificing velocity resolution to get more frames per second.  The heatmap is showing the strength of velocity changes, so you should expect to see reduced performance.

    Here's another way to do it:  Here, we keep the idle time as before, but we reduce the total number of chirps from 512 to 336 to increase the frame rate to 10fps.

    profileCfg 0 77 250 10 40 0 0 98 1 64 2200 0 0 40
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 2
    frameCfg 0 1 168 0 107 1 0