• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 813 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.

IWR6843: Inter Frame Time Issue.

MyungJoo Lee
Prodigy 40 points
Part Number: IWR6843
Other Parts Discussed in Thread: MMWAVE-SDK

hello.

I am testing the IWR6843 to apply it to my field.

I want to transmit Chirp continuously with minimum "Inter Frame Time".

Hope the Inter Frame Time is less than 100us.

I only want 1D-FFT results, I don't need Inter Frame Processing.

When the demo program is modified and executed, -1 is returned if the inter frame time is less than 300us.

(Detail Error Code is -3110 * 80, Frame config error & RL_RET_CODE_FRAME_PERIOD_1INVAL_IN)

Chirp Setting - Idle time : 5us, Ramp End Time : 55 us, (Total 60us)

Frame Setting - Chirp per Frame : 16, Frame repitition period : 1.26ms - Run OK /  1.25ms - Return Error Code)

Is it structurally impossible to inter frame time less than 300us?

Or is there something I did wrong?

Please give me some advice or examples.

Thank you.

  • +1
    TI__Guru 50240 points

    Hi MyungJoo

    There are a variety of resources to aid with chirp design and educate on the subject.

    Chirp Programming Guide

    mmWave Sensing Estimator

    Lastly the mmWave-SDK Doxygen is going to be another very helpful resource. It is located in the installed mmWave-SDK at the following location:

    <mmWave_SDK_Installation_Path>\packages\ti\demo\<Device Name>\mmw\docs\doxygen\html\index.html 

    Regards,

    AG

  • +1 in reply to Akash Gondalia
    Prodigy 40 points

    hi Akash.

    thank you for reply.

    --  Is your answer possible to set the Inter Frame time to less than 300us?

    I Already read the two documents and doxygen page above. 
    Some of the documents look like this:
    InterFrameBlankTime is primarily for sensor calibration/monitoring, thermal control, transferring out any safety monitoring data if requested, hardware reconfiguration for next frame, re-triggering of next frame. InterFrameBlankTime >= 300 us typically. 
    But, When the demo program is modified and executed, -1 is returned if the inter frame time is less than 300us. (Just use Range DPU)

    -- something I did wrong?