• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 354 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.

AWR2944: about 2944 monitorings wave unexpected chirps.

XiangLiping
Prodigy 230 points
Part Number: AWR2944

Tool/software:

hw:awr2944

1. call <rlRfSetCalMonTimeUnitConfig>

parama list :

calibMonTimeUnit      =   2
numOfCascadeDev   =   1
devId                          =   0
monitoringMode         =   0
2. call <rlRfAnaMonConfig>
parama list :
enMask1             = 0xF1FF3FF1U
ldoVmonScEn     = 0
enMask2             = 3
3.i find these chirps are not belonging to the profile we set.
4.call <rlRfAnaMonConfig>
parama list :
enMask1             = 0x0
ldoVmonScEn     = 0
enMask2             = 0
5. now chirps in <step 3> disappeared.
So, my questions are :
q1.which bits in enMask1/enMask2 set to 1 will cause unexpected chirps like <step 3>.
q2.these monitorings in q1 wave how many chirps per bit or cost how much time per bit .
  • +1
    TI__Mastermind 29935 points

    Hello,

    Certain calibrations and monitors will transmit a signal on the TX output port which will produce emissions in the mmWave frequency band. The user should be aware of the operation of these monitors and calibrations in cases where out of band emissions in the radar frequency band need to be controlled.

    Emissions Due to Calibrations

    Table below provides a list of calibrations that will transmit on the TX output port.

    Boot-time Calibrations

    Runtime Calibrations

    TX Power Boot-time Calibration

    Closed Loop Power Control TX Power Runtime Calibration

    TX Phase Shifter Boot-time Calibration

     

    RX IQMM Boot-time Calibration

     

    The boot-time calibrations will only be performed once for each boot cycle, whereas runtime calibrations can occur multiple times during runtime. There are two options to manage the emissions from calibrations. The first option is to use the factory save-restore process to disable the boot-time calibrations during operation in the field. Additionally, the TX power run-time calibration can be configured for open-loop power control mode, which relies only on an internal LUT to set the TX stage code.

    The second option is to specify the calibration and monitor frequency and power limits using the AAWR_CAL_MON_FREQUENCY_TX_POWER_LIMITS_SB API (AWR294x only) API. This monitor will set the upper and lower limits on the frequency and power for certain calibrations and monitors. There are several considerations when using this API. For proper usage, please refer to the interface control document provided in the mmWave DFP.

    For more comprehensive details on usage and operation of the various calibrations supported by TI mmWave sensors, refer to the Self-Calibration in TI’s mmWave Radar Devices application note.

    Emissions Due to Monitors

    TI mmWave sensors support various internal monitors that allow users to achieve their end product safety goals. Just as with the calibrations, there are several monitors that will transmit a signal on the TX output port that can produce emissions in the mmWave frequency band. The list of transmitting monitors is detailed in table below.

    Table below provides list of Transmitting Monitors

    Monitors

    TXn Power Monitor

    TXn Ballbreak Monitor

    TXn Internal Signals Monitor

    TX Gain Phase Mismatch Monitor

    TXn Phase Shifter Monitor

    RX Mixer Input Power Monitor

    As with the calibrations, the frequency range and power of the monitors can be controlled using the AWR_CAL_MON_FREQUENCY_TX_POWER_LIMITS_SB API. However, the exception is the TX ballbreak monitor, which can still operate outside of the bounds defined by the AWR_CAL_MON_FREQUENCY_TX_POWER_LIMITS_SB API and must be separately configured using the MON_START_FREQ_CONST and TX_POWER_BACKOFF fields within the monitor API. For more details on the various device monitors, please refer to the interface control document provided in the mmWave DFP.

    Regards,

    Adrian