-
Notifications
You must be signed in to change notification settings - Fork 52
NI RFmx SpecAn ACP Configuration Functions
- RFmxSpecAn_ACPCfgCarrierAndOffsets
- RFmxSpecAn_ACPCfgNumberOfCarriers
- RFmxSpecAn_ACPCfgCarrierMode
- RFmxSpecAn_ACPCfgCarrierFrequency
- RFmxSpecAn_ACPCfgCarrierIntegrationBandwidth
- RFmxSpecAn_ACPCfgCarrierRRCFilter
- RFmxSpecAn_ACPCfgNumberOfOffsets
- RFmxSpecAn_ACPCfgOffset
- RFmxSpecAn_ACPCfgOffsetIntegrationBandwidth
- RFmxSpecAn_ACPCfgOffsetPowerReference
- RFmxSpecAn_ACPCfgOffsetRelativeAttenuation
- RFmxSpecAn_ACPCfgOffsetRRCFilter
- RFmxSpecAn_ACPCfgPowerUnits
- RFmxSpecAn_ACPCfgMeasurementMethod
- RFmxSpecAn_ACPCfgNoiseCompensationEnabled
- RFmxSpecAn_ACPValidateNoiseCalibrationData
- RFmxSpecAn_ACPCfgRBWFilter
- RFmxSpecAn_ACPCfgSweepTime
- RFmxSpecAn_ACPCfgAveraging
- RFmxSpecAn_ACPCfgFFT
- RFmxSpecAn_ACPCfgOffsetFrequencyDefinition
- Array Apis
int32 __stdcall RFmxSpecAn_ACPCfgCarrierAndOffsets (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 integrationBandwidth, int32 numberOfOffsets, float64 channelSpacing);
Configures a carrier channel with offset channels on both sides of the carrier as specified by the number of offsets. The offset channels are separated by +/- n*channel spacing from the center of the carrier. Power is measured over the integration bandwidth for each channel.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name. If you do not specify the signal name, the default signal instance is used. Example: "" "signal::sig1" You can use the RFmxSpecAn_BuildSignalString) function to build the selector string). |
integrationBandwidth | float64 | Specifies the frequency range, in Hz, over which the measurement integrates the carrier power. |
numberOfOffsets | int32 | Specifies the number of offset channels. |
channelSpacing | float64 | Specifies the spacing between offset channels. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgNumberOfCarriers (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 numberOfCarriers);
Configures the number of carriers for the adjacent channel power (ACP) measurement.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name. If you do not specify the signal name, the default signal instance is used. Example: "" "signal::sig1" You can use the RFmxSpecAn_BuildSignalString) function to build the selector string). |
numberOfCarriers | int32 | Specifies the number of carriers. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgCarrierMode (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 carrierMode);
Configures whether to consider the carrier power as part of total carrier power measurement.
Use "carrier<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "carrier0" "signal::sig1/carrier0" You can use the RFmxSpecAn_BuildCarrierString2) function to build the selector string). |
carrierMode | int32 | Specifies whether to consider the carrier power as part of total carrier power measurement. |
RFMXSPECAN_VAL_ACP_CARRIER_MODE_PASSIVE (0) | The carrier power is not considered as part of total carrier power. |
---|---|
RFMXSPECAN_VAL_ACP_CARRIER_MODE_ACTIVE (1) | The carrier power is considered as part of total carrier power. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgCarrierFrequency (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 carrierFrequency);
Configures the center frequency of the carrier, relative to the RF center frequency.
Use "carrier<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "carrier0" "signal::sig1/carrier0" You can use the RFmxSpecAn_BuildCarrierString2) function to build the selector string). |
carrierFrequency | float64 | Specifies the center frequency, in Hz, of the carrier, relative to the RF center frequency). |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgCarrierIntegrationBandwidth (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 integrationBandwidth);
Configures the frequency range, in Hz, over which the measurement integrates the carrier power.
Use "carrier<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "carrier0" "signal::sig1/carrier0" You can use the RFmxSpecAn_BuildCarrierString2) function to build the selector string). |
integrationBandwidth | float64 | Specifies the frequency range, in Hz, over which the measurement integrates the carrier power. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgCarrierRRCFilter (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 RRCFilterEnabled, float64 RRCAlpha);
Configures the root-raised-cosine (RRC) filter to apply on the carrier channel before measuring the carrier channel power.
Use "carrier<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "carrier0" "signal::sig1/carrier0" You can use the RFmxSpecAn_BuildCarrierString2) function to build the selector string). |
RRCFilterEnabled | int32 | Specifies whether to apply the root-raised-cosine (RRC) filter on the acquired carrier channel before measuring the carrier channel power. |
RFMXSPECAN_VAL_ACP_RRC_FILTER_ENABLED_FALSE (0) | The channel power of the acquired carrier channel is measured directly. |
---|---|
RFMXSPECAN_VAL_ACP_RRC_FILTER_ENABLED_TRUE (1) | The RRC filter is applied on the acquired carrier channel before measuring the carrier channel power. |
RRCAlpha | float64 | Specifies the roll-off factor for the root-raised-cosine (RRC) filter. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgNumberOfOffsets (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 numberOfOffsets);
Configures the number of offsets for the adjacent channel power (ACP) measurement.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name. If you do not specify the signal name, the default signal instance is used. Example: "" "signal::sig1" You can use the RFmxSpecAn_BuildSignalString) function to build the selector string). |
numberOfOffsets | int32 | Specifies the number of offset channels. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgOffset (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 offsetFrequency, int32 offsetSideband, int32 offsetEnabled);
Configures an offset channel on one or both sides of the carrier with center-to-center spacing as specified by the offset frequency and offset frequency definition. In case of multiple carriers, offset frequency is relative to the closest carrier.
Use "offset<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name and offset number. If you do not specify the signal name, the default signal instance is used. Example: "offset0" "signal::sig1/offset0" You can use the RFmxSpecAn_BuildOffsetString2) function to build the selector string). |
offsetFrequency | float64 | Specifies the center or edge frequency, in Hz, of the offset channel, relative to the center frequency of the closest carrier as determined by the RFMXSPECAN_ATTR_ACP_OFFSET_FREQUENCY_DEFINITION) attribute. The sign of offset frequency is ignored and the offsetSideband parameter determines whether the upper, lower, or both offsets are measured. |
offsetSideband | int32 | Specifies whether the offset segment is present on one side, or on both sides of the carriers. |
RFMXSPECAN_VAL_ACP_OFFSET_SIDEBAND_NEGATIVE (0) | Configures a lower offset segment, which is an offset segment with negative offset frequency, relative to the lowest center frequency of the carrier. |
---|---|
RFMXSPECAN_VAL_ACP_OFFSET_SIDEBAND_POSITIVE (1) | Configures an upper offset segment, which is an offset segment with positive offset frequency, relative to the highest center frequency of the carrier. |
RFMXSPECAN_VAL_ACP_OFFSET_SIDEBAND_BOTH (2) | Specifies that both negative and positive offset segments are configured. |
offsetEnabled | int32 | Specifies whether to enable the offset channel for ACP measurement. |
RFMXSPECAN_VAL_ACP_OFFSET_ENABLED_FALSE (0) | Disables the offset channel for ACP measurement. |
---|---|
RFMXSPECAN_VAL_ACP_OFFSET_ENABLED_TRUE (1) | Enables the offset channel for ACP measurement. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgOffsetIntegrationBandwidth (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 integrationBandwidth);
Configures the frequency range, in Hz, over which the measurement integrates the offset channel power.
Use "offset<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name and offset number. If you do not specify the signal name, the default signal instance is used. Example: "offset0" "signal::sig1/offset0" You can use the RFmxSpecAn_BuildOffsetString2) function to build the selector string). |
integrationBandwidth | float64 | Specifies the frequency range, in Hz, over which the measurement integrates the carrier power. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgOffsetPowerReference (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 offsetReferenceCarrier, int32 offsetReferenceSpecific);
Configures the power reference to use for measuring the relative power of the offset channel.
Use "offset<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name and offset number. If you do not specify the signal name, the default signal instance is used. Example: "offset0" "signal::sig1/offset0" You can use the RFmxSpecAn_BuildOffsetString2) function to build the selector string). |
offsetReferenceCarrier | int32 | Specifies the carrier to be used as power reference to measure offset channel relative power. The offset channel power is measured only if you set the RFMXSPECAN_ATTR_ACP_CARRIER_MODE) attribute of the reference carrier to RFMXSPECAN_VAL_ACP_CARRIER_MODE_ACTIVE. |
RFMXSPECAN_VAL_ACP_OFFSET_POWER_REFERENCE_CARRIER_CLOSEST (0) | The measurement uses the power measured in the carrier closest to the offset channel center frequency, as the power reference. |
---|---|
RFMXSPECAN_VAL_ACP_OFFSET_POWER_REFERENCE_CARRIER_HIGHEST (1) | The measurement uses the highest power measured among all the active carriers as the power reference. |
RFMXSPECAN_VAL_ACP_OFFSET_POWER_REFERENCE_CARRIER_COMPOSITE (2) | The measurement uses the sum of powers measured in all the active carriers as the power reference. |
RFMXSPECAN_VAL_ACP_OFFSET_POWER_REFERENCE_CARRIER_SPECIFIC (3) | The measurement uses the power measured in the carrier that has an index specified by the RFMXSPECAN_ATTR_ACP_OFFSET_POWER_REFERENCE_SPECIFIC) attribute, as the power reference. |
offsetReferenceSpecific | int32 | Specifies the index of the carrier to be used as the reference carrier. The power measured in this carrier is used as the power reference for measuring the offset channel relative power, when you set the offsetReferenceCarrier parameter to RFMXSPECAN_VAL_ACP_OFFSET_REFERENCE_CARRIER_SPECIFIC. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgOffsetRelativeAttenuation (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 relativeAttenuation);
Configures the attenuation, in dB, relative to the external attenuation.
Use "offset<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name and offset number. If you do not specify the signal name, the default signal instance is used. Example: "offset0" "signal::sig1/offset0" You can use the RFmxSpecAn_BuildOffsetString2) function to build the selector string). |
relativeAttenuation | float64 | Specifies the attenuation, in dB, relative to the external attenuation. Use this parameter to compensate for variations in external attenuation when the offset channels are spread wide in frequency. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgOffsetRRCFilter (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 RRCFilterEnabled, float64 RRCAlpha);
Configures the root raised cosine (RRC) channel filter to be applied on the offset channel before measuring channel power.
Use "offset<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name and offset number. If you do not specify the signal name, the default signal instance is used. Example: "offset0" "signal::sig1/offset0" You can use the RFmxSpecAn_BuildOffsetString2) function to build the selector string). |
RRCFilterEnabled | int32 | Specifies whether to apply the root-raised-cosine (RRC) filter on the acquired carrier channel before measuring the carrier channel power. |
RFMXSPECAN_VAL_ACP_RRC_FILTER_ENABLED_FALSE (0) | The channel power of the acquired carrier channel is measured directly. |
---|---|
RFMXSPECAN_VAL_ACP_RRC_FILTER_ENABLED_TRUE (1) | The RRC filter is applied on the acquired carrier channel before measuring the carrier channel power. |
RRCAlpha | float64 | Specifies the roll-off factor for the root-raised-cosine (RRC) filter. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgPowerUnits (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 powerUnits);
Configures the units for the absolute power.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name. If you do not specify the signal name, the default signal instance is used. Example: "" "signal::sig1" You can use the RFmxSpecAn_BuildSignalString) function to build the selector string). |
powerUnits | int32 | Specifies the units for the absolute power. |
RFMXSPECAN_VAL_ACP_POWER_UNITS_DBM (0) | The absolute powers are reported in dBm. |
---|---|
RFMXSPECAN_VAL_ACP_POWER_UNITS_DBM_PER_HZ (1) | The absolute powers are reported in dBm/Hz. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgMeasurementMethod (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 measurementMethod);
Configures the method for performing the adjacent channel power (ACP) measurement.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name. If you do not specify the signal name, the default signal instance is used. Example: "" "signal::sig1" You can use the RFmxSpecAn_BuildSignalString) function to build the selector string). |
measurementMethod | int32 | Specifies the method for performing the ACP measurement. |
RFMXSPECAN_VAL_ACP_MEASUREMENT_METHOD_NORMAL (0) | The ACP measurement acquires the spectrum using the same signal analyzer setting across frequency bands. Use this method when measurement speed is desirable over higher dynamic range. |
---|---|
RFMXSPECAN_VAL_ACP_MEASUREMENT_METHOD_DYNAMIC_RANGE (1) | The ACP measurement acquires the spectrum using the hardware-specific optimizations for different frequency bands. Use this method to get the best dynamic range. supportedDevices: PXIe-5665, PXIe-5668. |
RFMXSPECAN_VAL_ACP_MEASUREMENT_METHOD_SEQUENTIAL_FFT (2) |
The ACP measurement acquires I/Q samples for a duration specified by the RFMXSPECAN_ATTR_ACP_SWEEP_TIME_INTERVAL attribute. These samples are divided into smaller chunks. The size of each chunk is defined by the RFMXSPECAN_ATTR_ACP_SEQUENTIAL_FFT_SIZE attribute. The overlap between the chunks is defined by the RFMXSPECAN_ATTR_ACP_FFT_OVERLAP_MODE attribute. FFT is computed on each of these chunks. The resultant FFTs are averaged to get the spectrum and is used to compute ACP. If the total acquired samples is not an integer multiple of the FFT size, the remaining samples at the end of acquisition are not used for the measurement. Sequential FFT method should be used for the following scenarios. 1. While performing fast ACP measurements by utilizing smaller FFT sizes. However, accuracy of the results may be reduced. 2. When measuring signals with time-varying spectral characteristics, sequential FFT with overlap mode set to Automatic should be used. The following attributes have limited support when you set the RFMXSPECAN_ATTR_ACP_MEASUREMENT_METHOD attribute to RFMXSPECAN_VAL_ACP_MEASUREMENT_METHOD_SEQUENTIAL_FFT. The RFMXSPECAN_ATTR_ACP_RBW_FILTER_AUTO_BANDWIDTH attribute will only support RFMXSPECAN_VAL_ACP_RBW_AUTO_TRUE value. The RFMXSPECAN_ATTR_ACP_RBW_FILTER_TYPE attribute will only support RFMXSPECAN_VAL_ACP_RBW_FILTER_TYPE_FFT_BASED value. The RFMXSPECAN_ATTR_ACP_SWEEP_TIME_AUTO attribute will only support RFMXSPECAN_VAL_ACP_SWEEP_TIME_AUTO_FALSE value. The RFMXSPECAN_ATTR_ACP_FFT_WINDOW attribute will only support RFMXSPECAN_VAL_ACP_FFT_WINDOW_NONE value. The RFMXSPECAN_ATTR_ACP_AVERAGING_COUNT attribute will only support a value of 1. The RFMXSPECAN_ATTR_ACP_NOISE_COMPENSATION_ENABLED attribute will only support RFMXSPECAN_VAL_ACP_NOISE_COMPENSATION_ENABLED_FALSE value. The RFMXSPECAN_ATTR_ACP_NUMBER_OF_ANALYSIS_THREADS attribute will only support a value of 1. The RFMXSPECAN_ATTR_ACP_AMPLITUDE_CORRECTION_TYPE attribute will only support a value of RFMXSPECAN_VAL_ACP_AMPLITUDE_CORRECTION_TYPE_RF_CENTER_FREQUENCY. The RFMXSPECAN_ATTR_ACP_OFFSET_RELATIVE_ATTENUATION attribute will only support a value of 0. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgNoiseCompensationEnabled (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 noiseCompensationEnabled);
Configures compensation of the channel powers for the inherent noise floor of the signal analyzer.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name. If you do not specify the signal name, the default signal instance is used. Example: "" "signal::sig1" You can use the RFmxSpecAn_BuildSignalString) function to build the selector string). |
noiseCompensationEnabled | int32 | Specifies whether to enable compensation of the channel powers for the inherent noise floor of the signal analyzer. |
RFMXSPECAN_VAL_ACP_NOISE_COMPENSATION_ENABLED_FALSE (0) | Disables compensation of the channel powers for the noise floor of the signal analyzer. |
---|---|
RFMXSPECAN_VAL_ACP_NOISE_COMPENSATION_ENABLED_TRUE (1) |
Enables compensation of the channel powers for the noise floor of the signal analyzer. The noise floor of the signal analyzer is measured for the RF path used by the ACP measurement and cached for future use. If signal analyzer or measurement parameters change, noise floors are measured again. Supported Devices: PXIe-5663/5665/5668, PXIe-5830/5831/5832 |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPValidateNoiseCalibrationData (niRFmxInstrHandle instrumentHandle, char selectorString[], int32* noiseCalibrationDataValid);
Indicates whether calibration data is valid for the configuration specified by the signal name in the selectorString parameter.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name. If you do not specify the signal name, the default signal instance is used. Example: "" "signal::sig1" You can use the RFmxSpecAn_BuildSignalString) function to build the selector string). |
Output | ||
Name | Type | Description |
noiseCalibrationDataValid | int32* | Returns whether the calibration data is valid. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgRBWFilter (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 RBWAuto, float64 RBW, int32 RBWFilterType);
Configures the resolution bandwidth (RBW) filter.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name. If you do not specify the signal name, the default signal instance is used. Example: "" "signal::sig1" You can use the RFmxSpecAn_BuildSignalString) function to build the selector string). |
RBWAuto | int32 | Specifies whether the measurement computes the RBW. Refer to the RBW and Sweep Time section in the ACP) topic for more information about RBW and sweep time. |
RFMXSPECAN_VAL_ACP_RBW_AUTO_FALSE (0) | The measurement uses the RBW that you specify in the RBW parameter. |
---|---|
RFMXSPECAN_VAL_ACP_RBW_AUTO_TRUE (1) | The measurement computes the RBW. |
RBW | float64 | Specifies the bandwidth, in Hz, of the RBW filter used to sweep the acquired carrier signal, when you set the RBWAuto parameter to RFMXSPECAN_VAL_ACP_RBW_AUTO_FALSE. |
RBWFilterType | int32 | Specifies the shape of the digital RBW filter. |
RFMXSPECAN_VAL_ACP_RBW_FILTER_TYPE_FFT_BASED (0) | No RBW filtering is performed. |
---|---|
RFMXSPECAN_VAL_ACP_RBW_FILTER_TYPE_GAUSSIAN (1) | An RBW filter with a Gaussian response is applied. |
RFMXSPECAN_VAL_ACP_RBW_FILTER_TYPE_FLAT (2) | An RBW filter with a flat response is applied. |
RFMXSPECAN_VAL_ACP_RBW_FILTER_TYPE_SYNCH_TUNED_4 (3) | An RBW filter with a 4-pole synchronously-tuned response is applied. |
RFMXSPECAN_VAL_ACP_RBW_FILTER_TYPE_SYNCH_TUNED_5 (4) | An RBW filter with a 5-pole synchronously-tuned response is applied. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgSweepTime (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 sweepTimeAuto, float64 sweepTimeInterval);
Configures the sweep time.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name. If you do not specify the signal name, the default signal instance is used. Example: "" "signal::sig1" You can use the RFmxSpecAn_BuildSignalString) function to build the selector string). |
sweepTimeAuto | int32 | Specifies whether the measurement computes the sweep time. |
RFMXSPECAN_VAL_ACP_SWEEP_TIME_AUTO_FALSE (0) | The measurement uses the sweep time that you specify in the sweepTimeInterval parameter. |
---|---|
RFMXSPECAN_VAL_ACP_SWEEP_TIME_AUTO_TRUE (1) | The measurement calculates the sweep time based on the value of the RFMXSPECAN_ATTR_ACP_RBW_FILTER_BANDWIDTH) attribute. Refer to the ACP) topic for more information about RBW. |
sweepTimeInterval | float64 | Specifies the sweep time, in seconds, when you set the sweepTimeAuto parameter to RFMXSPECAN_VAL_ACP_SWEEP_TIME_AUTO_FALSE. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgAveraging (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 averagingEnabled, int32 averagingCount, int32 averagingType);
Configures averaging for the adjacent channel power (ACP) measurement.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name. If you do not specify the signal name, the default signal instance is used. Example: "" "signal::sig1" You can use the RFmxSpecAn_BuildSignalString) function to build the selector string). |
averagingEnabled | int32 | Specifies whether to enable averaging for the measurement. |
RFMXSPECAN_VAL_ACP_AVERAGING_ENABLED_FALSE (0) | The measurement is performed on a single acquisition. |
---|---|
RFMXSPECAN_VAL_ACP_AVERAGING_ENABLED_TRUE (1) | The measurement uses the averagingCount parameter to calculate the number of acquisitions over which the spectrum is averaged. |
averagingCount | int32 | Specifies the number of acquisitions used for averaging when you set the averagingEnabled parameter to RFMXSPECAN_VAL_ACP_AVERAGING_ENABLED_TRUE. |
averagingType | int32 | Specifies the averaging type for averaging multiple spectrum acquisitions. The averaged spectrum is used for the measurement. Refer to the Averaging section of the Spectrum) topic for more information about averaging types. |
RFMXSPECAN_VAL_ACP_AVERAGING_TYPE_RMS (0) | The power spectrum is linearly averaged. RMS averaging reduces signal fluctuations but not the noise floor. |
---|---|
RFMXSPECAN_VAL_ACP_AVERAGING_TYPE_LOG (1) | The power spectrum is averaged in a logarithm scale. |
RFMXSPECAN_VAL_ACP_AVERAGING_TYPE_SCALAR (2) | The square root of the power spectrum is averaged. |
RFMXSPECAN_VAL_ACP_AVERAGING_TYPE_MAXIMUM (3) | The peak power in the spectrum at each frequency bin is retained from one acquisition to the next. |
RFMXSPECAN_VAL_ACP_AVERAGING_TYPE_MINIMUM (4) | The least power in the spectrum at each frequency bin is retained from one acquisition to the next. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgFFT (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 FFTWindow, float64 FFTPadding);
Configures window and FFT to obtain a spectrum for the adjacent channel power (ACP) measurement.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name. If you do not specify the signal name, the default signal instance is used. Example: "" "signal::sig1" You can use the RFmxSpecAn_BuildSignalString) function to build the selector string). |
FFTWindow | int32 | Specifies the FFT window type to use to reduce spectral leakage. Refer to the Window and FFT section of the Spectrum) topic for more information about FFT window types. |
RFMXSPECAN_VAL_ACP_FFT_WINDOW_NONE (0) | Analyzes transients for which duration is shorter than the window length. You can also use this window type to separate two tones with frequencies close to each other but with almost equal amplitudes. |
---|---|
RFMXSPECAN_VAL_ACP_FFT_WINDOW_FLAT_TOP (1) | Measures single-tone amplitudes accurately. |
RFMXSPECAN_VAL_ACP_FFT_WINDOW_HANNING (2) | Analyzes transients for which duration is longer than the window length. You can also use this window type to provide better frequency resolution for noise measurements. |
RFMXSPECAN_VAL_ACP_FFT_WINDOW_HAMMING (3) | Analyzes closely-spaced sine waves. |
RFMXSPECAN_VAL_ACP_FFT_WINDOW_GAUSSIAN (4) | Provides a good balance of spectral leakage, frequency resolution, and amplitude attenuation. Hence, this windowing is useful for time-frequency analysis. |
RFMXSPECAN_VAL_ACP_FFT_WINDOW_BLACKMAN (5) | Analyzes single tone because it has a low maximum side lobe level and a high side lobe roll-off rate. |
RFMXSPECAN_VAL_ACP_FFT_WINDOW_BLACKMAN_HARRIS (6) | Useful as a good general purpose window, having side lobe rejection >90dB and having a moderately wide main lobe. |
RFMXSPECAN_VAL_ACP_FFT_WINDOW_KAISER_BESSEL (7) | Separates two tones with frequencies close to each other but with widely-differing amplitudes. |
FFTPadding | float64 | Specifies the factor by which the time-domain waveform is zero-padded before FFT. The FFT size is given by the following formula: waveform size * padding. This parameter is used only when the acquisition span is less than the device instantaneous bandwidth of the device. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall ACPCfgOffsetFrequencyDefinition (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 offsetFrequencyDefinition);
Configures the offset frequency definition for the ACP measurement.
Use "offset<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name and offset number. If you do not specify the signal name, the default signal instance is used. Example: "offset0" "signal::sig1/offset0" You can use the RFmxSpecAn_BuildOffsetString2) function to build the selector string). |
offsetFrequencyDefinition | int32 | Specifies the offset frequency definition. The default value is RFMXSPECAN_VAL_ACP_CARRIER_CENTER_TO_OFFSET_CENTER. |
RFMXSPECAN_VAL_ACP_CARRIER_CENTER_TO_OFFSET_CENTER (0) | The offset frequency is defined from the center of the closest carrier to the center of the offset channel. |
---|---|
RFMXSPECAN_VAL_ACP_CARRIER_CENTER_TO_OFFSET_EDGE (1) | The offset frequency is defined from the center of the closest carrier to the nearest edge of the offset channel. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgOffsetArray (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 offsetFrequency[], int32 offsetSideband[], int32 offsetEnabled[], int32 numberOfElements);
Configures an offset channel on one or both sides of carrier with center-to-center spacing as specified by the offset frequency and offset frequency definition. In case of multiple carriers, offset frequency is relative to the closest carrier.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name. If you do not specify the signal name, the default signal instance is used. Example: "" "signal::sig1" You can use the RFmxSpecAn_BuildSignalString) function to build the selector string). |
offsetFrequency | float64[] | Specifies an array of center or edge frequencies, in Hz, of the offset channel, relative to the center frequency of the closest carrier as determined by the RFMXSPECAN_ATTR_ACP_OFFSET_FREQUENCY_DEFINITION) attribute. The sign of offset frequency is ignored and the RFMXSPECAN_ATTR_ACP_OFFSET_SIDEBAND) attribute determines whether the upper, lower, or both offsets are measured. |
offsetSideband | int32[] | Specifies whether the offset segment is present on one side, or on both sides of the carriers. Specify NULL if you do not want to set a value for this array. |
RFMXSPECAN_VAL_ACP_OFFSET_FREQUENCY_SIDEBAND_NEG (0) | Configures a lower offset segment, which is an offset segment with negative offset frequency, relative to the lowest center frequency of the carrier. |
---|---|
RFMXSPECAN_VAL_ACP_OFFSET_FREQUENCY_SIDEBAND_POS (1) | Configures an upper offset segment, which is an offset segment with positive offset frequency, relative to the highest center frequency of the carrier. |
RFMXSPECAN_VAL_ACP_OFFSET_FREQUENCY_SIDEBAND_BOTH (2) | Specifies that both negative and positive offset segments are configured. |
offsetEnabled | int32[] | Specifies whether to enable the offset channel for ACP measurement. Specify NULL if you do not want to set a value for this array. |
RFMXSPECAN_VAL_ACP_OFFSET_ENABLED_FALSE (0) | Disables the offset channel for ACP measurement. |
---|---|
RFMXSPECAN_VAL_ACP_OFFSET_ENABLED_TRUE (1) | Enables the offset channel for ACP measurement. |
numberOfElements | int32 | Specifies the number of elements in each array. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgOffsetPowerReferenceArray (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 offsetPowerReferenceCarrier[], int32 offsetPowerReferenceSpecific[], int32 numberOfElements);
Configures the power reference to use for measuring the relative power of the offset channel.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name. If you do not specify the signal name, the default signal instance is used. Example: "" "signal::sig1" You can use the RFmxSpecAn_BuildSignalString) function to build the selector string). |
offsetPowerReferenceCarrier | int32[] | Specifies the array of carriers to be used as power reference to measure offset channel relative power. The offset channel power is measured only if you set the RFMXSPECAN_ATTR_ACP_CARRIER_MODE) attribute of the reference carrier to RFMXSPECAN_VAL_ACP_CARRIER_MODE_ACTIVE. Specify NULL if you do not want to set a value for this array. |
RFMXSPECAN_VAL_ACP_OFFSET_POWER_REFERENCE_CARRIER_CLOSEST (0) | The measurement uses the power measured in the carrier closest to the offset channel center frequency, as the power reference. |
---|---|
RFMXSPECAN_VAL_ACP_OFFSET_POWER_REFERENCE_CARRIER_HIGHEST (1) | The measurement uses the highest power measured among all the active carriers as the power reference. |
RFMXSPECAN_VAL_ACP_OFFSET_POWER_REFERENCE_CARRIER_COMPOSITE (2) | The measurement uses the sum of powers measured in all the active carriers as the power reference. |
RFMXSPECAN_VAL_ACP_OFFSET_POWER_REFERENCE_CARRIER_SPECIFIC (3) | The measurement uses the power measured in the carrier that has an index specified by the RFMXSPECAN_ATTR_ACP_OFFSET_POWER_REFERENCE_SPECIFIC) attribute, as the power reference. |
offsetPowerReferenceSpecific | int32[] | Specifies the array of carrier indexes to use as the reference carrier for each offset channel. The power measured in this carrier is used as the power reference for measuring the offset channel relative power, when you set the offsetPowerReferenceCarrier parameter to RFMXSPECAN_VAL_ACP_OFFSET_POWER_REFERENCE_CARRIER_SPECIFIC. Specify NULL if you do not want to set a value for this array. |
numberOfElements | int32 | Specifies the number of elements in each array. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgOffsetRelativeAttenuationArray (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 relativeAttenuation[], int32 numberOfElements);
Configures the attenuation, in dB, relative to the external attenuation.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name. If you do not specify the signal name, the default signal instance is used. Example: "" "signal::sig1" You can use the RFmxSpecAn_BuildSignalString) function to build the selector string). |
relativeAttenuation | float64[] | Specifies an array of attenuation values, in dB, relative to the external attenuation. Use this parameter to compensate for the variations in external attenuation when offset channels are spread wide in frequency. Specify NULL if you do not want to set a value for this array. |
numberOfElements | int32 | Specifies the number of elements in each array. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxSpecAn_ACPCfgOffsetRRCFilterArray (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 RRCFilterEnabled[], float64 RRCAlpha[], int32 numberOfElements);
Configures the RRC channel filter to be applied on the offset channel before measuring channel power.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Identifies the RFmx session. You can obtain this parameter from the RFmxSpecAn_Initialize) function. |
selectorString | char[] | Comprises the signal name. If you do not specify the signal name, the default signal instance is used. Example: "" "signal::sig1" You can use the RFmxSpecAn_BuildSignalString) function to build the selector string). |
RRCFilterEnabled | int32[] | Specifies whether to apply the RRC filter on the acquired offset channel before measuring the offset channel power. Specify NULL if you do not want to set a value for this array. |
RFMXSPECAN_VAL_ACP_RRC_FILTER_ENABLED_FALSE (0) | The channel power of the acquired offset channel is measured directly. |
---|---|
RFMXSPECAN_VAL_ACP_RRC_FILTER_ENABLED_TRUE (1) | The measurement applies the RRC filter on the acquired offset channel before measuring the offset channel power. |
RRCAlpha | float64[] | Specifies an array of roll-off factors of the RRC filter to apply on the acquired offset channel before measuring the offset channel power. Specify NULL if you do not want to set a value for this array. |
numberOfElements | int32 | Specifies the number of elements in each array. |
Name | Type | Description |
---|---|---|
status | int32 | Returns the status code of this operation. The status code either indicates success or describes an error or warning condition. Examine the status code from each call to an RFmx function to determine if an error has occurred. To obtain a text description of the status code and additional information about the error condition, call the RFmxSpecAn_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
Creating and Setting Up a gRPC Server
Session Utilities API Reference
gRPC API Differences From C API
Sharing Driver Sessions Between Clients
C API Docs
NI-DAQmx
- gRPC API Differences From C API
- Task Configuration And Control
- Channel Configuration And Creation
- Timing
- Triggering
- Read Functions
- Write Functions
- Export Hardware Signals
- Scale Configuration
- Internal Buffer Configuration
- Advanced Functions
- System Configuration
- Error Handling
- Buffer Attributes
- Calibration Info Attributes
- Channel Attributes
- Device Attributes
- Export Signal Attributes
- Persisted Channel Attributes
- Persisted Scale Attributes
- Persisted Task Attributes
- Physical Channel Attributes
- Read Attributes
- Scale Attributes
- System Attributes
- Task Attributes
- Timing Attributes
- Trigger Attributes
- Watchdog Attributes
- Write Attributes
NI-DCPOWER
- Setup Functions
- Configure Functions
- Measurement Functions
- Control Functions
- Trigger And Event
- Attribute Functions
- Query Functions
- Calibration Functions
- Utility Functions
- Supported Device
- Source Attributes
- Transient Attributes
- Voltage Attributes
- Current Attributes
- Pulse Voltage Attributes
- Pulse Current Attributes
- Cutoff Attributes
- Measurement Attributes
- Trigger Attributes Functions
- Event Attributes
- Advanced Attributes
- Inherent Ivi Attributes
- Supported Device Attributes
NI-DIGITAL PATTERN DRIVER
- Init And Close Functions
- Session Locking Functions
- Utility Functions
- Error Handling Functions
- Calibration Functions
- Attributes Functions
- Pin Map Functions
- Low Level Functions
- Low Level Action Functions
- Pin Control Functions
- Static IO Functions
- Clock Generator Functions
- Levels And Timing Functions
- TDR Functions
- PPMU Configuration Functions
- DC Voltage Functions
- DC Current Functions
- PPMU Action Functions
- Pattern Configuration Functions
- Pattern Action Functions
- History Ram Functions
- Source Memory Functions
- Capture Memory Functions
- Triggers And Events Functions
- Conditional Jump Trigger Functions
- Sequencer Flag Functions
- Sequencer Register Functions
- Match Fail Combination Functions
- Pattern Results Functions
- Sort Results Functions
- Frequency Measurement Functions
- IVI Inherent Attributes
- Specific Driver Information Attributes, Read Only
- Driver Setup Information Attributes
- Device Attributes
- Pin Control Attributes
- Level Configuration Attributes
- Trigger Configuration Attributes
- PPMU Attributes
- Patterns Attributes
- Pattern Opcode Event Attributes
- Timing Offset Attributes
- Keep Alive Attributes
- Frequency Measurement Attributes
- Clock Generator Attributes
- History RAM
- Synchronization Attributes
- TDR Endpoint Termination Attributes
NI-FGEN
- Setup Functions
- Configuration Functions
- Standard Output Functions
- Arbitrary Waveform Output Functions
- Arbitrary Sequence Output Functions
- Incremental Waveform Write Functions
- Configure Clock Functions
- Trigger And Syncronizations Functions
- 5404 Routing Functions
- Script Output Functions
- Configure Onboard Signal Processing Functions
- Configure Peer To Peer Functions
- Attribute Functions
- Waveform Control Functions
- Error Functions
- Output Attributes
- Arbitrary Waveform Attributes
- Data Transfer Attributes
- Onboard Signal Processing Attributes
- Peer To Peer Attributes
- Standard Function Attributes
- Clock Attributes
- Event Attributes
- Triggering Attributes
- Instrument Specific Attributes
- Inherent IVI Attributes
- 5401 5411 5431
NI-RFmx Bluetooth
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Set And Get Attribute Functions
- Fetch Results Functions
- Utility Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- Packet Attributes
- Auto Detect Signal Attributes
- Modacc Attributes
- ACP Attributes
- Twenty dB Attributes
- Frequency Range Attributes
- TXP Attributes
- Advanced Attributes
NI-RFmx NR
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Set And Get Attributes Functions
- Fetch Results Functions
- Utility Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- Signal Detection Attributes
- Component Carrier Attributes
- List Attributes
- Modacc Attributes
- ACP Attributes
- CHP Attributes
- OBW Attributes
- SEM Attributes
- TXP Attributes
- Pvt Attributes
- Advanced Attributes
NI-RFmx LTE
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Ch Configuration Functions
- NB IoT Configuration Functions
- ModAcc Configuration Functions
- ACP Configuration Functions
- CHP Configuration Functions
- OBW Configuration Functions
- SEM Configuration Functions
- PVT Configuration Functions
- SlotPhase Configuration Functions
- SlotPower Configuration Functions
- Set And Get Attribute Functions
- ModAcc Fetch Functions
- ACP Fetch Functions
- CHP Fetch Functions
- OBW Fetch Functions
- SEM Fetch Functions
- PVT Fetch Functions
- SlotPhase Fetch Functions
- SlotPower Fetch Functions
- Utility Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- Component Carrier Attributes
- ModAcc Attributes
- ACP Attributes
- CHP Attributes
- OBW Attributes
- SEM Attributes
- PVT Attributes
- SlotPhase Attributes
- SlotPower Attributes
- Advanced Attributes
NI-RFmx SpecAn
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Set And Get Attribute Functions
- Read Functions
- Fetch Functions
- Utility Functions
- Marker Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- ACP Attributes
- Cdf Attributes
- CHP Attributes
- Fcnt Attributes
- Harm Attributes
- OBW Attributes
- SEM Attributes
- Spectrum Attributes
- Spur Attributes
- TXP Attributes
- AMPM Attributes
- Dpd Attributes
- IQ Attributes
- IM Attributes
- NF Attributes
- Phasenoise Attributes
- PAVT Attributes
- Advanced Attributes
NI-RFmx WLAN
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Set And Get Attribute Functions
- Fetch DSSS ModAcc Functions
- Fetch OFDM ModAcc Functions
- Fetch SEM Functions
- Fetch TXP Functions
- Fetch PowerRamp Functions
- Utility Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- OFDM Attributes
- Auto Detect Signal Attributes
- DSSS ModAcc Attributes
- OFDM ModAcc Attributes
- SEM Attributes
- TXP Attributes
- PowerRamp Attributes
- Advanced Attributes
NI-RFSA
- General Functions
- Configuration Functions
- Acquisition Functions
- Utility Functions
- Calibration Functions
- General Attributes
- Vertical Attributes
- Signal Path Attributes
- Acquisition Attributes
- Acquisition Attributes
- Triggers Attributes
- Events Attributes
- Device Characteristics Attributes
- Peer To Peer Streaming Attributes
- Configuration List Attributes
- Inherent IVI Properties Attributes
- De-embedding Attributes
- Self Calibration Attributes
- Factory Calibration Attributes
- External Alignment Attributes
- Device Specific Attributes
NI-RFSG
- General Functions
- Generation Configuration
- Utility Functions
- Calibration Functions
- Arb Attributes
- Clock Attributes
- Configuration List Attributes
- De-embedding Attributes
- Device Characteristics Attributes
- Device Specific Attributes
- Events Attributes
- External Calibration Attributes
- Inherent IVI Attributes Attributes
- IQ Impairment Attributes
- Load Configurations Attributes
- Modulation Attributes
- Obsolete Attributes
- Peer To Peer Attributes
- RF Attributes
- Self Calibration Attributes
- Triggers Attributes
NI-SCOPE
- Setup Functions
- Configure Functions
- Attribute Functions
- Acquisition Functions
- Measurement Functions
- Calibrate Functions
- Utility Funcitons
- Error Handling Functions
- IVI Compliance Or Obsolete Functions
- Vertical Attributes
- Horizontal Attributes
- Trigger Attributes
- Clocking Attributes
- Synchronization Attributes
- Acquisition Attributes
- Waveform Measurements Attributes
- Onboard Signal Processing Attributes
- Peer To Peer Streaming Attributes
- Device Attributes
- IVI Or Obsolete Attributes
- Instrument Capabilities Attributes
- If Digitizer Attributes
NI-XNET
- gRPC API differences from C APIs
- General Functions
- Cluster Properties
- Database Properties
- Device Properties
- ECU Properties
- Frame Properties
- Interface Properties
- LIN Schedule Entry Properties
- LIN Schedule Properties
- PDU Properties
- Session Ethernet Properties
- Session Frame Properties
- Session Interface Properties
- Session Properties
- Session SAE J1939 Properties
- Signal Properties
- Subframe Properties
- System Properties
- IP-Stack Functions
- Socket Options
- Socket Functions