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.

AWR1843AOP: How to remove InterFrameBlankTime in framePeriodicity

Part Number: AWR1843AOP
Other Parts Discussed in Thread: AWR1843

Tool/software:

Hi, i'm using awr1843 to get some data for application.

And i want to use all of the framePeriodicity except for InterFrameBlankTime.

For example, 

idleTime : 5us

RampEndTime : 95us

(total chirp time -> 100us)

infinite chirp, except for breaktime

But that was impossible.

This is because an error occurs in the frame configuration if the frame periodicity range limits and the minimum blank time of 150us are not included.

Is there any way to set the inter-frame blank time to 0 or less than 150us? I've tried various methods (such as configuring it without calibration), but an error occurs.

  • Hi,

    Inter frame blank time is a necessity for the chip it cannot be set to 0.

    Thanks,

    Pradipta.

  • HI, Pradipta Bandyopadhyay.

    is it possible to set interframeblanktime less than 150us ??

    i should config frame without interblanktime.

    Performance and stability don't matter. Since the application will only run for a short period, I want to find a way to definitely reduce this aspect.

    Thanks.

  • Hi,

    The Inter frame blank time is required. 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. 

    The API execution for frame configuration will not go through properly if you do set the parameters correctly. That is why you get the error as well.  

    The firmware on the chip is designed in this particular way only so it cannot be reduced below the minimum requirement. 

    The only option you have is to reduce the active chirp time to accommodate in the same frame periodicity. 

    Can you let us know what is the actual requirement here? Why do you want to eliminate this time?

    Thanks,

    Pradipta.

  • Hi,

    The reason I want to reduce that time is that the application I am developing has a very short cycle time (frame) of 100us.

    Therefore, if there is a minimum idle time(InterFrameBlankTime) of 150us between frames, it causes periods where normal operation cannot occur.

    As you mentioned earlier, I understand that various tasks can be performed during the InterBlankTime, such as calibration, monitoring data transferring,

    and reconfiguration, but I do not anticipate needing these tasks. This is because the total operating time of the application is limited to a few minutes at most.

    and i want to show you our configuration of our application.

    idleTime : 54.95

    RampEndTime : 44.95us

    (total chirp time -> 99.9us, this will be slightly changed at anytime)

    profileId : 0 (use only one profile. there are no subframes, so i don't need reconfiguraiton and re-triggering)

    chirpStartIdx : 0

    chirpEndidx : 133

    numLoops : 100

    (total chirps in 1 frame : 13400 / 1 is the number of frames from the AOP perspective, and 13400 is the number of frames from our perspective)

    framePeriodCity : 99.9us * 13400 + 150us

    This is precisely why I want to minimize the InterFrameBlankTime. After approximately 1.34 seconds of continuous operation,

    it enters an inactive mode for 150us.

    Until now, I have sometimes directly modified the contents within the SDK files, but it seems that this area cannot be modified by the user.

    Therefore, I am inquiring about it. If there is any way to reduce this time, please let me know.

    Thanks.

  • Hi,

    The time frame cannot be reduced. It is a necessity for the chip and designed that way. Hence that component in the frame periodicity cannot be reduced below its minimum required value. 

    Thanks,

    Pradipta.