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.

AWR1843: Frame timing for coherent processing of multiple frames

Part Number: AWR1843

Hi,

I want to coherently process ramps from multiple radar frames together - similar to the vital signs demo. The goal is to get very fine Doppler resolution due to the long overall measurement time.

How precise is the timing from one frame to the next? Is there any specification on jitter that I need to take into account?

Best regards

Sebastian

  • The beginning of the frame can be triggered in Sw or Hw.

    When sw frame trigger is used, the beginning of next frame is computed based on timer running in firmware at 200MHz

    thank you
    cesar
  • Hi Cesar,

    we use the software trigger, no external trigger is supplied to the AWR18. The waveform config has fixed frame periodicity and an infinite number of frames.

    Is the frame timing cycle accurate? I.e., one frame to the next is always the same number of 200 MHz clock cycles?

    Sebastian
  • Hi Sebastian,
    Processing multiple frames at a time may require more memory to store the intermediate results. So you need to consider this condition while trying this experiment.
    What is "precise" mean here? While switching to next frame device internally takes time to configure and trigger the next frame but overall it maintains the full frame period as configured by the application.

    So for the application, it sees the frame (timing) as the numbers it has configured the device.


    Regards,
    Jitendra
  • Hi Jitendra,

    the waveform needs to be set up to leave enough memory for long-time data collection, of course.

    When calculating speed based on the phase difference of a target from one frame to the next (for very low speeds) the frame periodicity and any jitter on that will affect the result.

    What is the maximum deviation from the set, e.g. 40 ms, frame periodicity? 1/(200MHz)=5ns? Is there any device specification that this value can be derived from?

    Sebastian

  • Sebastian

    I still don't have an answer for this question.

    It should take a few more days

    thank you
    Cesar
  • I am sorry for the delay

    Was still not able to get a response from the design team

    The goal is to have an answer early next week

    thank you
    Cesar
  • Hi Sebastian,
    Frame to frame jitter is a couple of nsec and same no. of chirp jitter.
    You can refer Driver Vital sign demo where it checks for phase coherency across frames.

    Regards,
    Jitendra