definition of features and configurations in adrv9002

Hi all , 

after I read some part of the ug1828 (the user guide for the adrv9002 ) I would like the get a simpler explanations/definitions for the following topics:

1. what is the ORx1/2 signal and what it used for? 

2.what is the DPD functionality?

3. when using the frequency hopping mode do I need to operate on TDD DUPLEX or can I choose to operate on FDD ?

4. why in the TES SW there is two tables ?

5.how can I create the frequency hopping table ? is there anything that I need to consider when building my own table(like HW limitations) ? is there an alternative option to implement the hopping table like in a regular c scripting ?

6. is the configure tab in the TES SW configure the profile.bin file or other tabs in the SW configure also the profile configurations ?

I thank for your answer .

with best regards .

DROR 

Parents
  • +1
    •  Analog Employees 
    on Sep 27, 2021 9:07 AM

    Hello Dror,

    I will attempt to simplify these definitions for you:

    1. ORx1/2 are Observation receiver channels. The use the same signal chain as the normal Rx channels, and therefore you cannot use Rx1 and ORx1 at the same time. However ORx1 and Rx1 have different ports on the physical device. Rx1 will have better RF performance over the operating range of the device due to the port location on the device. ORx1/2 are design to be used as feedback paths for tracking calibrations, such as DPD.
    2. Digital Pre Distortion uses an external loopback after the PA on an External Tx signal chain (Tx1 -> ORx1 OR Tx2 -> ORx2, Tx1 -> ORx2 DOES NOT WORK) to account for PA compression, allowing users to drive their PA at it's max power output and efficiency without suffering from reduced noise performance. Using the data that comes in over the ORx channel, our proprietary DPD Coefficients engine searches a Look Up Table for a set of coefficients used to alter the Tx data in the Digital Front End, accounting for the PAs compression.
    3. Frequency Hopping MUST be operated in TDD mode, as our Frequency Hopping implementation relies on there being both time to retune the LO and control signals which power up and down the signal chains as needed (i.e. for the best results with Frequency Hopping you must use Auto TDD)
    4. I'm assuming you're referring to the tables presented on the connections tab? One table describes the Hardware identified in the system as well as the TES version used, the other table details the FW and Server found in the SD card.
    5. We have examples of Frequency Hopping tables provided as part of the TES, simply navigate to "...\ADRV9001 Transceiver Evaluation Software\Examples\Hop Tables\" to see the format used. No other method of Frequency Hopping is supported in our SW, C scripting will not work to nearly the same efficiency. You are welcome to generate C99 code which uses our APIs and go through a loop of RESET - INITIALIZE - CALIBRATE - ENABLE - DISABLE - RESET but this is far more prone to errors and much much slower than what our in-built software can offer.
    6. Many tabs go into the production of the Profile.bin files. These binary files are what control the onboard ARM processor and the Stream processors, both of which do an enormous amount of work depending on the configuration. For example, an Auto TDD configuration which uses Frequency Hopping will offload a huge amount of work to the ARM processor, allowing it to handle Enabling and Disabling the RF signal chains and retuning the LOs, as well as any calibrations needed, Initial or Tracking.

    I do hope this answer is sufficient for you! Do reach out if you have any follow-up questions!

    Best Regards,
    Oisín.

Reply
  • +1
    •  Analog Employees 
    on Sep 27, 2021 9:07 AM

    Hello Dror,

    I will attempt to simplify these definitions for you:

    1. ORx1/2 are Observation receiver channels. The use the same signal chain as the normal Rx channels, and therefore you cannot use Rx1 and ORx1 at the same time. However ORx1 and Rx1 have different ports on the physical device. Rx1 will have better RF performance over the operating range of the device due to the port location on the device. ORx1/2 are design to be used as feedback paths for tracking calibrations, such as DPD.
    2. Digital Pre Distortion uses an external loopback after the PA on an External Tx signal chain (Tx1 -> ORx1 OR Tx2 -> ORx2, Tx1 -> ORx2 DOES NOT WORK) to account for PA compression, allowing users to drive their PA at it's max power output and efficiency without suffering from reduced noise performance. Using the data that comes in over the ORx channel, our proprietary DPD Coefficients engine searches a Look Up Table for a set of coefficients used to alter the Tx data in the Digital Front End, accounting for the PAs compression.
    3. Frequency Hopping MUST be operated in TDD mode, as our Frequency Hopping implementation relies on there being both time to retune the LO and control signals which power up and down the signal chains as needed (i.e. for the best results with Frequency Hopping you must use Auto TDD)
    4. I'm assuming you're referring to the tables presented on the connections tab? One table describes the Hardware identified in the system as well as the TES version used, the other table details the FW and Server found in the SD card.
    5. We have examples of Frequency Hopping tables provided as part of the TES, simply navigate to "...\ADRV9001 Transceiver Evaluation Software\Examples\Hop Tables\" to see the format used. No other method of Frequency Hopping is supported in our SW, C scripting will not work to nearly the same efficiency. You are welcome to generate C99 code which uses our APIs and go through a loop of RESET - INITIALIZE - CALIBRATE - ENABLE - DISABLE - RESET but this is far more prone to errors and much much slower than what our in-built software can offer.
    6. Many tabs go into the production of the Profile.bin files. These binary files are what control the onboard ARM processor and the Stream processors, both of which do an enormous amount of work depending on the configuration. For example, an Auto TDD configuration which uses Frequency Hopping will offload a huge amount of work to the ARM processor, allowing it to handle Enabling and Disabling the RF signal chains and retuning the LOs, as well as any calibrations needed, Initial or Tracking.

    I do hope this answer is sufficient for you! Do reach out if you have any follow-up questions!

    Best Regards,
    Oisín.

Children
No Data