Data Fields
rlTxPhShiftMonConf_t Struct Reference

TX Phase shifter monitoring configuration. More...

#include <control/mmwavelink/include/rl_monitoring.h>

Data Fields

rlUInt8_t profileIndx
 This field indicates the Profile Index for which this configuration applies.
 
rlUInt8_t reportMode
 Value Definition
0 Report is sent every monitoring period without threshold check
1 Report is send only upon a failure (after checking for thresholds)
2 Report is sent every monitoring period with threshold check.
.
 
rlUInt16_t reserved0
 Reserved for Future use.
 
rlUInt8_t phShifterMonCfg
 Enable at least two phase settings to measure phase error and to apply threshold in reporting mode 1 and 2.
Bit Definition
b0 Phase shifter phase1 monitor enable bit
b1 Phase shifter phase2 monitor enable bit
b2 Phase shifter phase3 monitor enable bit
b3 Phase shifter phase4 monitor enable bit
b7:4 RESERVED.
 
rlUInt8_t rxEn
 This field indicates the RX channels that should be enabled for TX to RX loopback measurement. Setting the corresponding bit to 1 enables that channel for measurement and the average measured value is reported out.
Bit Definition
b0 RX0
b1 RX1
b2 RX2
b3 RX3
b7:4 RESERVED.
 
rlInt8_t monChirpSlope
 Frequency slope for each monitoring chirp is encoded in 1 bytes (8 bit signed number).
1 LSB = 3.6e9 * 900/2^26 Hz ~ 48.279 kHz/us
Valid range: -128 to +127 (Max 6.13 MHz/us) More...
 
rlUInt8_t reserved1
 Reserved for Future use.
 
rlUInt8_t phShifterIncVal1
 Phase shifter monitoring increment value for phase1, the monitoring phase will be incremented by this value in every FTTI interval.
In API based trigger MONITORING_MODE, it is important to trigger PS monitor every FTTI to make sure this logic works seamlessly.
Bits Phase shift definition
b1:0 Reserved (set it to 0b00)
b7:2 Phase shift increment value 1
1 LSB = 5.625 degrees
.
 
rlUInt8_t phShifterIncVal2
 Phase shifter monitoring increment value for phase2, the monitoring phase will be incremented by this value in every FTTI interval.
In API based trigger MONITORING_MODE, it is important to trigger PS monitor every FTTI to make sure this logic works seamlessly.
Bits Phase shift definition
b1:0 Reserved (set it to 0b00)
b7:2 Phase shift increment value 2
1 LSB = 5.625 degrees
.
 
rlUInt8_t phShifterIncVal3
 Phase shifter monitoring increment value for phase3, the monitoring phase will be incremented by this value in every FTTI interval.
In API based trigger MONITORING_MODE, it is important to trigger PS monitor every FTTI to make sure this logic works seamlessly.
Bits Phase shift definition
b1:0 Reserved (set it to 0b00)
b7:2 Phase shift increment value 3
1 LSB = 5.625 degrees
.
 
rlUInt8_t phShifterIncVal4
 Phase shifter monitoring increment value for phase4, the monitoring phase will be incremented by this value in every FTTI interval.
In API based trigger MONITORING_MODE, it is important to trigger PS monitor every FTTI to make sure this logic works seamlessly.
Bits Phase shift definition
b1:0 Reserved (set it to 0b00)
b7:2 Phase shift increment value 4
1 LSB = 5.625 degrees
.
 
rlUInt8_t phShifterMon1
 TXn Phase shifter phase1 monitor value.
Bits Phase shift definition
b1:0 Reserved (set it to 0b00)
b7:2 Phase shift monitor value 1
1 LSB = 5.625 degrees
.
 
rlUInt8_t phShifterMon2
 TXn Phase shifter phase2 monitor value.
Bits Phase shift definition
b1:0 Reserved (set it to 0b00)
b7:2 Phase shift monitor value 2
1 LSB = 5.625 degrees
.
 
rlUInt8_t phShifterMon3
 TXn Phase shifter phase3 monitor value.
Bits Phase shift definition
b1:0 Reserved (set it to 0b00)
b7:2 Phase shift monitor value 3
1 LSB = 5.625 degrees
.
 
rlUInt8_t phShifterMon4
 TXn Phase shifter phase4 monitor value.
Bits Phase shift definition
b1:0 Reserved (set it to 0b00)
b7:2 Phase shift monitor value 4
1 LSB = 5.625 degrees
.
 
rlUInt16_t txPhaseErrorThresh
 The threshold for deviation of the TX output phase difference between the measured phase values and configured phases for each enabled phase settings. The max error is compared against the threshold given here. The measured phase is part of the monitoring report message (Error bit is set if the max deviation is higher than this threshold, with the units of both quantities being the same).
1 LSB = 360(degree) /2^16.
Valid range: corresponding 0 degree to 359.9 degree
.
 
rlUInt16_t txAmplErrorThresh
 The threshold for deviation of the TX output amplitude difference between all enabled phase settings. The max error is compared against the threshold given here. The measured output amplitude is part of the monitoring report message (Error bit is set if the max deviation is higher than this threshold, with the units of both quantities being the same).
1 LSB = 0.1 dB
Valid range: 0 to 65535 (0 to 6553dB)
.
 
rlUInt32_t reserved2
 Reserved for Future use.
 
rlUInt32_t reserved3
 Reserved for Future use.
 

Detailed Description

TX Phase shifter monitoring configuration.

Definition at line 2521 of file rl_monitoring.h.

Field Documentation

◆ monChirpSlope

rlInt8_t rlTxPhShiftMonConf_t::monChirpSlope

Frequency slope for each monitoring chirp is encoded in 1 bytes (8 bit signed number).
1 LSB = 3.6e9 * 900/2^26 Hz ~ 48.279 kHz/us
Valid range: -128 to +127 (Max 6.13 MHz/us)

Note
: Monitoring Chirp Slope can be programmed based on the emission specifications. The device transmits on air during the execution of these monitors. The host can control the monitoring emission power spectral density (dBm/Hz) by programming this slope parameter. Each monitoring chirp is about 45us in duration. Therefore the overall RF sweep bandwidth for the monitoring chirp is given by Monitoring Chirp Slope * 45 us. Normally, low values of Monitoring Chirp Slope are recommended, as with non-zero slope in FMCW radar, any actual target reflections can potentially be interpreted as noise power and/or corrupt the loopback signal based gain/phase measurement.
The user has to ensure that the RF bandwidth selected for monitoring chirp based on slope and start frequency is within FREQ_LIMIT set in AWR_CAL_MON_FREQUENCY_TX_POWER_LIMITS_SB API.

Definition at line 2594 of file rl_monitoring.h.


The documentation for this struct was generated from the following file:

Copyright 2020, Texas Instruments Incorporated