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.

AWR1243: Frame Trigger Delay with HW Trigger

Part Number: AWR1243

What is the impact of setting a frame trigger delay when using HW_TRIGGER mode?

I would like to use HW_TRIGGER mode with a frame delay. My understanding is that these are equivalent modes:
1) Sending the HW_TRIGGER pulse at time 0, and applying frame trigger delay = 5us
2) Delaying the HW_TRIGGER pulse by 5us in the host, and applying frame trigger delay = 0us

Thank you for your help.

Antonio

  • Hi Antonio,

    The AWR1243 will be ready to accept a new trigger one programmed "Frame Period" after the previous externally provided hardware trigger pulse.

    So if you wish to provide the HW_Trigger pulse 5us delayed in the host, with a 0 frame trigger delay, please ensure that the programmed frame periodicity is reduced accordingly to make sure the AWR1243 is ready to accept the new trigger.

    Best Regards,

    Anand

  • Hi Anand,

    Thanks for your response. To clarify - in the attached diagram:



    m
    y understanding is that it is ok to have different time between external frame trigger, as long as the device frame-periodicity is programmed to the minimum. In this example, frame-periodicity <= 10.5ms. Is this understanding correct?

    Thank you,
    Antonio

  • Hi Antonio,


    This understanding is correct.

    Note however that the device is no longer in low-power mode once it is waiting for the external hardware trigger, and delaying the hardware trigger indefinitely may not be a good idea. We do not extensively test for conditions where the hardware trigger is provided far from the expected frame periodicity.

    Best Regards,

    Anand