• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 1039 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AWR1843BOOST: Setting up chirp

Marvn Arcangel
Genius 13600 points
Part Number: AWR1843BOOST


Hi Team,

Good day. Can you please help with the inquiry below?

A customer is setting up the chirp configuration in the "ChirpConfigData.csv" file and trying to do time multiplexing, having Tx1 and Tx2 active alternatively. The setting are following:

0;0;0;0;0;0;01;0;0 in the second row and 0;1;1;0;0;0;0;0;1;0 in the third row

so that first the TX0 is active, and for the second chirp TX1 is active, and for now Tx2 is not in use

There are 128 chirps per frame and they are setting infinite frames, and stop the recording when needed

The customer wants to know if they should do the configuration for all 128 chirps, or if the first two chirps should work and the mmWave studio will repeat the configuration for the rest of 126 chirps?

Kindly refer to this document for more information: Supplementary documents.pdf

Would you kindly help further?

Thanks!

Regards,

Marvin

  • 0
    TI__Mastermind 33275 points

    Hi Marvin,

    Please find my comments below based on the document provided by the customer.

    Q) My first question is, what happens in this case? Are both Tx0 and Tx1 active and transmitting? Does TDM happen automatically because I have check marked both Txs under “StaticConfig” or do I need to configure the chirp and specifically determine which Tx is active for each chirp. Now that I have some of the measurement based on the figure below (without specifically determining the chirp configuration and having only one Tx checked), does it mean the recordings are based on the transmission from Tx0 only?

    Comment) In Static configuration when you enable a Tx then that Tx channel path is enabled and it can be used by profiles, chirps. It does not mean that the corresponding Tx will be used for transmitting automatically. TDM does not happen automatically you will need to design your configuration like that to perform this. So you will need to activate TX0 for chirp 0 and TX1 for chirp 1 and then send these two chirps one after the other. 

    Currently your recordings are based on TX0 only as only chipr0 was there which has TX0 enabled. 

    Q) Fig. 2. Tx0 and Tx1 are checked in “StaticConfig”. Is it enough for TDM setting? If Tx1 is not checked and configured under “Chirp > SensorConfig”.

    Comment) No

    Q) My second question which I brought up in first when TI opened a case for me is, if I specify that Tx0 is transmitting chirp 1, and Tx1 is transmitting chirp 2 (as shown in Fig. 5) does the radar understands to repeat this pattern for the rest of 126 chirps? Meaning that, is the third chirp transmitted by Tx0, fourth chirp by Tx1, and so on and so forth, or do I need to specify this for all 128 chirps? And could you please confirm the pattern I am following in Fig. 5 is correct or not?

    Comment) Radar will not make any automatic decisions for you. You will need to configure everything for the Radar. Currently i see that in your frames config the Start Chirp Index and End Chirp Index is 0. So only one chirp (chirp0) is selected and repeated for 128 times. (No of loops =128 in your config).

    Say, if you define two chirps (C0 and C1 with TX0 and TX1 enabled respectively) then in the frame settings you will need to transmit both the chirps. So, your end index should be 1. Now C0 will be transmitted then C1 then C0 then C1 and so on. C0 will be transmitted a total of 128 times and C1 will be transmitted a total of 128 times. That will be a TDM implementation which can then be processed by the TDM algorithm.

    Thanks,

    Pradipta. 

  • 0 in reply to Pradipta Bandyopadhyay
    TI__Genius 13600 points

    Hi Pradipta,

    Good day and thank you for answering.

    The customer has some follow up question, kindly refer to the pdf file I added below:

    Second part-recorded data length.pdf

    The customer use the fles below as a reference also:

    Mmwave Radar Device ADC Raw Data Capture:  https://www.ti.com/lit/an/swra581b/swra581b.pdf

    adc_data_config3chirps.zip

    Let me know if you need more information.

    Regards,

    Marvin

  • 0 in reply to Marvn Arcangel
    TI__Mastermind 33275 points

    Hi Marvin,

    Allow me some time to go through the files once. I will update when i have the answers.

    Thanks,

    Pradipta.

  • 0 in reply to Pradipta Bandyopadhyay
    TI__Genius 13600 points

    Thank you Pradipta. I look forward to your response.

  • 0 in reply to Marvn Arcangel
    TI__Genius 13600 points

    Hi Pradipta,

    Good day. I hope that you are able to run this on the bench.

    I just want to add some more explanations here for further clarification.The the issue is not just with the reading of raw data into MATLAB. Even if you use the "PostProc" option in the "mmWave Studio" and plot the results in" mmWave Studio" itself, it shows the same issue. It indicates two different interpretations even inside mmWave Studio GUI.
    In the transmitted signal setup, it considers 128 to be the number of chirp "Loops" each including 3 chirps sent from one of the transmitters. However, when you run "PostProc" it shows 128 chirps (instead of 384) per frame of the received signal. 
     
    Here is the customer settings in case you need to see them.
    Thanks!
    Regards,
    Marvin
  • 0 in reply to Marvn Arcangel
    TI__Mastermind 33275 points

    Hi Marvin,

    In the settings shared by the customer under frame configuration settings i can see that the Start Chirp Tx and End Chirp Tx are both set to zero. In this case only chirp is transmitted 128 times (as per other configurations) so the observations are correct. 

    The End Chirp Tx needs to be changed here to accommodate all the chirps that the user is designing. For reference the user can refer to the ICD for the frame config API.

    Thanks,

    Pradipta.

  • 0 in reply to Pradipta Bandyopadhyay
    TI__Genius 13600 points

    Hi Pradipta,

    Pradipta Bandyopadhyay said:
    For reference the user can refer to the ICD for the frame config API.

    Just to clarify, can you tell we where can I find ICD for the frame config API?

    Pradipta Bandyopadhyay said:
    The End Chirp Tx needs to be changed here to accommodate all the chirps that the user is designing. For reference the user can refer to the ICD for the frame config API.
    the "End Chirp TX" in the Frame setting should be set to 2 in my case, correct? and the previous setting 0 meant it only sent out chirp 0, 128 times? am I correct?
    Another follow-up question, The customer tried setting Start Chirp TX = 0, and End Chirp Tx = is 2 in the frame settings and the length of data the get now makes sense. So, in the raw received data (with ADC Samples being 256), the first 256 numbers are transmitted from Tx2, the second 256 samples are from Tx1, and the third 256 samples are from Tx0, and this is repeated 128 times per frame. Correct?
  • 0 in reply to Marvn Arcangel
    TI__Mastermind 33275 points

    Hi,

    Please find my comments below.

    Q) the "End Chirp TX" in the Frame setting should be set to 2 in my case, correct? and the previous setting 0 meant it only sent out chirp 0, 128 times? am I correct?

    Comment) Correct.

    Q) So, in the raw received data (with ADC Samples being 256), the first 256 numbers are transmitted from Tx2, the second 256 samples are from Tx1, and the third 256 samples are from Tx0, and this is repeated 128 times per frame. Correct?

    Comment) Correct. 

    Q) Just to clarify, can you tell we where can I find ICD for the frame config API?

    Comment) In your installed SDK version go to this path as below.

    \ti\mmwave_sdk_03_06_00_00-LTS\packages\ti\control\mmwavelink\docs\doxygen\html

    Here u can read about the all the API's.

    Thanks,

    Pradipta.

  • 0 in reply to Pradipta Bandyopadhyay
    TI__Genius 13600 points

    Hi Pradipta,

    Thanks! I do have a follow-up question.

    The customer just wants to confirm that their understanding of binary phase modulation (BPM) is also correct. Kindly refer to the attached PDF. The one for TDM and one for BPM. The main concern is about the virtual receiver array.

    TDM.pdf7416.BPM.pdf

    Looking forward to your response.

    Regards,

    Marvin

  • 0 in reply to Marvn Arcangel
    TI__Mastermind 33275 points

    Hi,

    I will need some time to evaluate the documents. Kindly allow me some time to verify them and then respond back on this. 

    Thanks,

    Pradipta.

  • 0 in reply to Pradipta Bandyopadhyay
    TI__Genius 13600 points

    Hi Pradipta.,

    I understand. I am looking forward to your response.

    If you need more information just let me know.

    Regards,

    Marvin

  • +1 in reply to Marvn Arcangel
    TI__Mastermind 33275 points

    Hi Marvin,

    The document attached previously was correct in theoretical understanding. 

    Thanks,

    Pradipta.