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.

AWR2944: AWR2944 chirp period

Part Number: AWR2944

Hi experts,

  My company are using AWR2944 SDK 4.2 to develop some automotive applications, below question need to be clarified.

1.Is is possible to shorten the idle time between chirp since our customer maximum velocity requirement (Chirp period)

Our settings:

Sample Rate = 37.5MHz

rangeFFT real samples = 1536

ramp up time = 30us

idle time = 25us

We expect the total period is about 35us for one chirp.

Thanks for reply

Henry Lin

  • Please give us some time to review this question

    thank you

    Cesar

  • Hi,

    Please refer to the ICD (Interface control document) in the SDK folder under DFP package. The ICD document specifies the minimum chirp cycle time required for the device based on which you can make the required modifications to your configuration parameters. In your case you can shorten the idle time between chirps. Also, you can install the latest SDK for AWR2944 from the website. 

    Thanks,

    Pradipta.

  • Hi Pradipta:

      Below picture is the description in mmwave_dfp_02_04_03_01, we need to shorten the period based on 1536 real range samples, we have tried to modify idle time to meet our requirement, but the radar do not output data anymore, does the minimum chirp cycle time take the process time (DC statistic + interference mitigation + 1D FFT + compressing data ) into consideration? 

    Thanks for reply.

    Henry Lin

  • Hi,

    Can you let us know how you are configuring your profile, chirp and frame? Also, the processing time is not included in the chirp cycle time. The Radar subsystem is responsible for the generation and propagation of chirps while the processing is done in the digital sub system for 2944. You can refer to the OOB demo for the 2944 which displays the complete usage of the radar chip. 

    Thanks,

    Pradipta.

  • Hi Pradipta:

      We only modified the demo example in SDK4.2 with DDMA mode, the BSS settings are similar with SDK.

    Our settings

    Sample Rate = 37.5MHz

    rangeFFT real samples = 1536

    ramp up time = 30us

    idle time = 25us

    frame rate:50ms

    Total Tx:4

    Number of subbands:2

    Number of chirps (Total):192

    Above setting works but we can not meet the our customer maximum velocity requirement. 

    We knew that processing time is not included in chirp cycle time but the chirp processes are between chirps , do we need to consider the process time in chirp cycle since it not ready for dealing next chirp data?   

    Thanks for reply.

    Henry Lin

  • Hi Pradipta,

    The question now becomes: How long does the HWA 2.0 handle 1536 sampling (DC statistic + interference mitigation + 1D FFT + compressing data...etc.)?
    It looks the HWA 2.0 takes long time to process these 1536 samples and need to extend the idle time to meet the HWA 2.0 minimal processing time.

    Any suggestion to make idle time shorter?

  • Hi James,

    Please refer to the following link to find the plausible chirp time to accommodate the processing of a chirp on HWA before new chirp interrupt arrives.

    (+) AWR2944: AWR2944 range FFT and SDK 4.3 - Sensors forum - Sensors - TI E2E support forums

    Are there any blocks on the HWA 1D chain that can be bypassed to save time?

    Additionally, is it possible to let me know how much time you would need to save in processing to run with the chirp time as per your velocity requirement?

    Regards,

    Kaushik