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.

  • TI Thinks Resolved

AWR1642BOOST: the number of range bins for range profile and noise profile

Prodigy 110 points

Replies: 3

Views: 105

Part Number: AWR1642BOOST

Many thanks for TI employees to solve my previous question about parsing dat file.

But I have another question. When I parse to range profile and noise profile, the length seems to be contradictory with mmw Demo Data Structure v0.1. From mmw Demo Data Structure v0.1, the length of the profile is #RangeBins * 4 bytes (#RangeBins=256?). But in fact, when I use 128 * 4 bytes, the parse result can be correct. Does #RangeBins equal to Range FFT size? Or maybe the data structure in mmw Demo Data Structure v0.1 is different from that in mmwave SDK 2.0?

Thank you very much.

  • Li,

    When you are configuring your profile, how many ADC samples are you capturing per chirp?

    Regards,
    Kyle
  • In reply to Kyle Cousino:

    Hi Kyle,
    I think the number of ADC samples is 256. Following is the configuration of the radar sensor:
    profileCfg 0 77 916 7 57.14 0 0 70 1 256 5209 0 0 30

    Best regards,
    Li
  • In reply to Li Lu:

    Li,

    The number of range bins is equal to the number of ADC samples. This squares with the information that you provided in your original post.

    Regards,
    Kyle

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.