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: AR1xController Function

Part Number: AWR1243

I wanted to know the difference between the following two functions. I am trying to multiple data captures turning on and off various TXs. I have a feeling that one power up/down the TX while the other enable/disable the outputs.

ar1.ChanNAdcConfig_mult(dev_list[i],Tx1[i],Tx2[i],Tx3[i],Rx1,Rx2,Rx3,Rx4[i],nbits,data_format,IQ_swap,cascade_mode_list[i])

vs.

ar1.ChirpConfig_mult(dev_list[i],0, 0, 0, 0, 0, 0, 0,Tx1_Enable[i],Tx2_Enable[i],Tx3_Enable[i])

Thanks in advance.

Gabriel

  • Hi Gabriel,

    Please refer to the AWR1xxx_Radar_Interface_Control.pdf document that is released as part of the DFP package (www.ti.com/.../MMWAVE-DFP). This document lists all the APIs supported by the device.

    The ar1.* functions in RadarStudio/mmWaveStudios invoke these APIs - although the names do not strictly match.

    The ChanNAdcConfig API calls the rlSetChannelConfig() API and the rlSetAdcOutConfig() API. The rlSetChannelConfig() API turns on or off the analog circuits accordingly for the corresponding TX/RX channels.

    This is a static configuration and is done once before rlRfInit() is called.

    The ChirpConfig is a dynamic configuration - this allows you to specify which TXs are active during a chirp. You can call this API multiple times to have different TXs enabled for different chirps. All the TXs that you wish to use in different chirps must have been enabled earlier in the rlSetChannelConfig() API.

    Hope this helps.

    Best Regards,
    Anand
  • Thanks. I'll see how that works out.