-
Notifications
You must be signed in to change notification settings - Fork 55
NI RFmx LTE Configuration Functions
- Configure RF
- RFmxLTE_CfgReferenceLevel
- RFmxLTE_CfgExternalAttenuation
- RFmxLTE_CfgRFAttenuation
- RFmxLTE_CfgMechanicalAttenuation
- RFmxLTE_AutoLevel
- Trigger
- RFmxLTE_SendSoftwareEdgeTrigger
- RFmxLTE_CfgLinkDirection
- RFmxLTE_CfgDuplexScheme
- RFmxLTE_CfgeNodeBCategory
- RFmxLTE_CfgNumberOfDUTAntennas
- RFmxLTE_CfgTransmitAntennaToAnalyze
- RFmxLTE_CfgNumberOfSubblocks
- RFmxLTE_CfgSubblockFrequencyDefinition
- RFmxLTE_CfgBand
- RFmxLTE_CfgComponentCarrierSpacing
- RFmxLTE_CfgNumberOfComponentCarriers
- RFmxLTE_CfgComponentCarrier
- RFmxLTE_CfgAutoResourceBlockDetectionEnabled
- RFmxLTE_CfgAutoDMRSDetectionEnabled
- RFmxLTE_CfgDownlinkTestModel
- RFmxLTE_CfgDownlinkAutoCellIDDetectionEnabled
-
Ch Configuration
- Uplink
-
Downlink
- RFmxLTE_CfgDownlinkChannelConfigurationMode
- RFmxLTE_CfgDownlinkAutoChannelDetection
- RFmxLTE_CfgCellSpecificRatio
- RFmxLTE_CfgDownlinkSynchronizationSignal
- RFmxLTE_CfgPBCH
- RFmxLTE_CfgPDCCH
- RFmxLTE_CfgDownlinkNumberOfSubframes
- RFmxLTE_CfgPCFICH
- RFmxLTE_CfgPHICH
- RFmxLTE_CfgNumberOfPDSCHChannels
- RFmxLTE_CfgPDSCH
- RFmxLTE_BuildSubblockString
- RFmxLTE_BuildCarrierString
- RFmxLTE_BuildSubframeString
- SideLink
- NB IoT
- RFmxLTE_CfgEMTCAnalysisEnabled
- Array Configuration
- RFmxLTE_BuildSubblockString
- RFmxLTE_BuildCarrierString
- RFmxLTE_BuildClusterString
- ModAcc
-
ACP
- RFmxLTE_ACPCfgAveraging
- RFmxLTE_ACPCfgSweepTime
- RFmxLTE_ACPCfgNoiseCompensationEnabled
- RFmxLTE_ACPCfgMeasurementMethod
- RFmxLTE_ACPCfgConfigurableNumberOfOffsetsEnabled
- RFmxLTE_ACPCfgUTRAAndEUTRAOffsets
- RFmxLTE_ACPCfgNumberOfUTRAOffsets
- RFmxLTE_ACPCfgNumberOfEUTRAOffsets
- RFmxLTE_ACPCfgNumberOfGSMOffsets
- RFmxLTE_ACPCfgRBWFilter
- RFmxLTE_ACPCfgPowerUnits
- RFmxLTE_ACPValidateNoiseCalibrationData
- RFmxLTE_BuildSubblockString
- CHP
- OBW
-
SEM
- RFmxLTE_SEMCfgAveraging
- RFmxLTE_SEMCfgSweepTime
- RFmxLTE_SEMCfgUplinkMaskType
- RFmxLTE_SEMCfgDownlinkMask
- RFmxLTE_SEMCfgComponentCarrierMaximumOutputPower
- RFmxLTE_SEMCfgNumberOfOffsets
- RFmxLTE_SEMCfgOffsetFrequency
- RFmxLTE_SEMCfgOffsetBandwidthIntegral
- RFmxLTE_SEMCfgOffsetRBWFilter
- RFmxLTE_SEMCfgOffsetLimitFailMask
- RFmxLTE_SEMCfgOffsetAbsoluteLimit
- RFmxLTE_SEMCfgOffsetRelativeLimit
- RFmxLTE_BuildSubblockString
- RFmxLTE_BuildOffsetString
- Array Configuration
- PVT
- SlotPhase
- SlotPower
int32 __stdcall RFmxLTE_CfgFrequency (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 centerFrequency);
Configures the expected carrier frequency of the RF signal to acquire. The signal analyzer tunes to this frequency. Use "subblock<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the subblock number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0" "signal::sig1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
centerFrequency | float64 | Specifies the center frequency of the acquired RF signal for a single carrier. The parameter specifies the reference frequency of the subblock for intra-band carrier aggregation. Depending on the RFMXLTE_ATTR_SUBBLOCK_FREQUENCY_DEFINITION) attribute, the center frequency can either be an absolute frequency or relative to the absolute frequency of the center frequency of the first subblock. All component carrier frequencies within the subblock are defined with respect to this frequency. The default value of this parameter is hardware dependent. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgFrequencyReference (niRFmxInstrHandle instrumentHandle, char channelName[], char frequencyReferenceSource[], float64 frequencyReferenceFrequency);
Configures the Reference Clock and the frequency reference source.
This function is a wrapper over the RFmx Instruments API, and calls the RFmxInstr_CfgFrequencyReference) function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
channelName | char[] | Set this parameter to "" (empty string) or NULL. |
frequencyReferenceSource | char[] | Specifies the frequency reference source. |
RFMXLTE_VAL_ONBOARD_CLOCK_STR (OnboardClock) |
PXIe-5663/5663E: The RFmx locks the PXIe-5663/5663E to the PXIe-5652 LO source onboard clock. Connect the REF OUT2 connector (if it exists) on the PXIe-5652 to the PXIe-5622 CLK IN terminal. On versions of the PXIe-5663/5663E that lack a REF OUT2 connector on the PXIe-5652, connect the REF IN/OUT connector on the PXIe-5652 to the PXIe-5622 CLK IN terminal. PXIe-5665: The RFmx locks the PXIe-5665 to the PXIe-5653 LO source onboard clock. Connect the 100 MHz REF OUT terminal on the PXIe-5653 to the PXIe-5622CLK IN terminal. PXIe-5668R: Lock the PXIe-5668 to the PXIe-5653 LO SOURCE onboard clock. Connect the LO2 OUT connector on the PXIe-5606 to the CLK IN connector on the PXIe-5624. PXIe-5644/5645/5646: The RFmx locks the device to its onboard clock. |
---|---|
RFMXLTE_VAL_REF_IN_STR (RefIn) |
PXIe-5663/5663E: Connect the external signal to the PXIe-5652 REF IN/OUT connector. Connect the REF OUT2 connector (if it exists) on the PXIe-5652 to the PXIe-5622 CLK IN terminal. PXIe-5665: Connect the external signal to the PXIe-5653 REF IN connector. Connect the 100 MHz REF OUT terminal on the PXIe-5653 to the PXIe-5622 CLK IN connector. If your external clock signal frequency is set to a frequency other than 10 MHz, set the frequencyReferenceFrequency parameter according to the frequency of your external clock signal. PXIe-5668R: Connect the external signal to the PXIe-5653 REF IN connector. Connect the LO2 OUT on the PXIe-5606 to the CLK IN connector on the PXIe-5622. If your external clock signal frequency is set to a frequency other than 10 MHz, set the frequencyReferenceFrequency parameter according to the frequency of your external clock signal. PXIe-5644R/5645R/5646R: The RFmx locks the device to the signal at the external REF IN connector. |
RFMXLTE_VAL_PXI_CLK_STR(PXI_Clk) |
PXIe-5668R: Lock the PXIe-5653 to the PXI backplane clock. Connect the PXIe-5606 LO2 OUT to the LO2 IN connector on the PXIe-5624R. PXIe-5644/5645/5646, PXIe-5663/5663E/5665: The RFmx locks these devices to the PXI backplane clock. |
RFMXLTE_VAL_CLK_IN_STR (ClkIn) |
PXIe-5663/5663E: The RFmx locks the PXIe-5663/5663E to an external 10 MHz signal. Connect the external signal to the PXIe-5622 CLK IN connector, and connect the PXIe-5622 CLK OUT connector to the REF IN/OUT connector on the PXIe-5652. PXIe-5665: The RFmx locks the PXIe-5665 to an external 100 MHz signal. Connect the external signal to the PXIe-5622 CLK IN connector, and connect the PXIe-5622 CLK OUT connector to the REF IN connector on the PXIe-5653. Set the frequencyReferenceFrequency parameter to 100 MHz. PXIe-5668: Lock the PXIe-5668 to an external 100 MHz signal. Connect the external signal to the CLK IN connector on the PXIe-5624, and connect the PXIe-5624 CLK OUT connector to the REF IN connector on the PXIe-5653. Set the frequencyReferenceFrequency parameter to 100 MHz. PXIe-5644/5645/5646: This configuration does not apply to the PXIe-5644/5645/5646. |
frequencyReferenceFrequency | float64 | Specifies the Reference Clock rate when you set the frequencyReferenceSource parameter to RFMXLTE_VAL_CLK_IN_STR or RFMXLTE_VAL_REF_IN_STR. This value is expressed in 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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgFrequencyEARFCN (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 linkDirection, int32 band, int32 EARFCN);
Configures the expected carrier frequency of the RF signal to acquire. The signal analyzer tunes to the E-UTRA absolute radio frequency channel number (EARFCN) frequency. Use "subblock<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the subblock number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0" "signal::sig1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
linkDirection | int32 | Specifies the link direction of the received signal. |
RFMXLTE_VAL_LINK_DIRECTION_DOWNLINK (0) | The measurement uses 3GPP LTE downlink specification to measure the received signal. |
---|---|
RFMXLTE_VAL_LINK_DIRECTION_UPLINK (1) | The measurement uses 3GPP LTE uplink specification to measure the received signal. |
band | int32 | Specifies the E-UTRA operating frequency band of a subblock as defined in section 5.2 of the 3GPP TS 36.521 specification. Valid values are from 1 to 255, inclusive. |
EARFCN | int32 | Specifies the evolved universal terrestrial radio access (E-UTRA) absolute radio frequency channel number. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgReferenceLevel (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 referenceLevel);
Configures the reference level, which represents the maximum expected power of an RF input signal.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
referenceLevel | float64 | Specifies the reference level, which represents the maximum expected power of the RF input signal. This value is expressed in dBm for RF devices and Vpk-pk for baseband devices. The default value of this parameter is hardware dependent. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgExternalAttenuation (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 externalAttenuation);
Specifies the attenuation of a switch or cable connected to the RF IN connector of the signal analyzer.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
externalAttenuation | float64 | Specifies the attenuation of a switch or cable connected to the RF IN connector of the signal analyzer. This value is expressed in dB. For more information about attenuation, refer to the RF Attenuation and Signal Levels topic for your device in the NI RF Vector Signal Analyzers Help. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgRFAttenuation (niRFmxInstrHandle instrumentHandle, char channelName[], int32 RFAttenuationAuto, float64 RFAttenuationValue);
Configures the nominal attenuation and the RFmx setting.
This function is a wrapper over the RFmx Instruments API, and calls the RFmxInstr_CfgRFAttenuation) function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
channelName | char[] | Set this parameter to "" (empty string) or NULL. |
RFAttenuationAuto | int32 | Specifies whether the RFmx computes the RF attenuation. |
RFMXLTE_VAL_RF_ATTENUATION_AUTO_FALSE(0) | Specifies that the RFmx uses the value configured using the RFAttenuationValue parameter. |
---|---|
RFMXLTE_VAL_RF_ATTENUATION_AUTO_TRUE(1) | Specifies that the RFmx computes the RF attenuation. |
RFAttenuationValue | float64 | Specifies the nominal attenuation setting for all attenuators before the first mixer in the RF signal chain when you set the RFAttenuationAuto parameter to RFMXLTE_VAL_RF_ATTENUATION_AUTO_FALSE. This value is expressed in dB. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgMechanicalAttenuation (niRFmxInstrHandle instrumentHandle, char channelName[], int32 mechanicalAttenuationAuto, float64 mechanicalAttenuationValue);
Configures the mechanical attenuation and the RFmx attenuation hardware settings.
This function is a wrapper over the RFmx Instruments API, and calls the RFmxInstr_CfgMechanicalAttenuation) function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
channelName | char[] | Set this parameter to "" (empty string) or NULL. |
mechanicalAttenuationAuto | int32 | Specifies whether the RFmx chooses an attenuation setting based on the hardware settings. |
RFMXLTE_VAL_MECHANICAL_ATTENUATION_AUTO_FALSE(0) | Specifies that the RFmx uses the value configured in the mechanicalAttenuationValue parameter. |
---|---|
RFMXLTE_VAL_MECHANICAL_ATTENUATION_AUTO_TRUE(1) | Specifies that the measurement computes the mechanical attenuation. |
mechanicalAttenuationValue | float64 | Specifies the level of mechanical attenuation for the RF path. This value is expressed in dB. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_AutoLevel (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 measurementInterval, float64* referenceLevel);
Examines the input signal to calculate the peak power level and sets it as the value of the RFMXLTE_ATTR_REFERENCE_LEVEL) attribute. Use this function to calculate an approximate setting for the reference level. The RFmxLTE Auto Level function completes the following tasks: You can also specify the starting reference level using RFMXLTE_ATTR_AUTO_LEVEL_INITIAL_REFERENCE_LEVEL) attribute. When using PXIe-5663/5665/5668R devices, NI recommends that you set an appropriate value for mechanical attenuation before calling the RFmxLTE Auto Level function. Setting an appropriate value for mechanical attenuation reduces the number of times the attenuator settings are changed by this function; thus reducing wear and tear, and maximizing the life time of the attenuator.
- Resets the mixer level, mixer level offset, and IF output power offset.
- Sets the starting reference level to the maximum reference level supported by the device based on the current RF attenuation, mechanical attenuation, and preamplifier enabled settings.
- Iterates to adjust the reference level based on the input signal peak power.
- Uses immediate triggering and restores the trigger settings back to user setting after the execution.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
measurementInterval | float64 | Specifies the acquisition length. This value is expressed in seconds. Use this value to compute the number of samples to acquire from the signal analyzer. Auto Level VI does not use any trigger for acquisition. It ignores the user-configured trigger properties. NI recommends that you set a sufficiently high measurement interval to ensure that the acquired waveform is at least as long as one period of the signal. |
Output | ||
Name | Type | Description |
referenceLevel | float64* | Returns the estimated peak power level of the input signal. This value is expressed in dBm for RF devices and Vpk-pk for baseband devices. The default value of this parameter is hardware dependent. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_DisableTrigger (niRFmxInstrHandle instrumentHandle, char selectorString[]);
Configures the device to not wait for a trigger to mark a reference point within a record. This function defines the signal triggering as immediate.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgDigitalEdgeTrigger (niRFmxInstrHandle instrumentHandle, char selectorString[], char digitalEdgeSource[], int32 digitalEdge, float64 triggerDelay, int32 enableTrigger);
Configures the device to wait for a digital edge trigger and then marks a reference point within the record.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
digitalEdgeSource | char[] | Specifies the source terminal for the digital edge trigger. This parameter is used when you set the RFMXLTE_ATTR_TRIGGER_TYPE) attribute to RFMXLTE_VAL_TRIGGER_TYPE_DIGITAL_EDGE. The default value of this parameter is hardware dependent. |
RFMXLTE_VAL_PFI0_STR (PFI0) | The trigger is received on PFI 0. |
---|---|
RFMXLTE_VAL_PFI1_STR (PFI1) | The trigger is received on PFI 1. The trigger is received on PFI 1. |
RFMXLTE_VAL_PXI_TRIG0_STR (PXI_Trig0) | The trigger is received on PXI trigger line 0. |
RFMXLTE_VAL_PXI_TRIG1_STR (PXI_Trig1) | The trigger is received on PXI trigger line 1. |
RFMXLTE_VAL_PXI_TRIG2_STR (PXI_Trig2) | The trigger is received on PXI trigger line 2. |
RFMXLTE_VAL_PXI_TRIG3_STR (PXI_Trig3) | The trigger is received on PXI trigger line 3. |
RFMXLTE_VAL_PXI_TRIG4_STR (PXI_Trig4) | The trigger is received on PXI trigger line 4. |
RFMXLTE_VAL_PXI_TRIG5_STR (PXI_Trig5) | The trigger is received on PXI trigger line 5. |
RFMXLTE_VAL_PXI_TRIG6_STR (PXI_Trig6) | The trigger is received on PXI trigger line 6. |
RFMXLTE_VAL_PXI_TRIG7_STR (PXI_Trig7) | The trigger is received on PXI trigger line 7. |
RFMXLTE_VAL_PXI_STAR_STR (PXI_STAR) | The trigger is received on the PXI star trigger line. |
RFMXLTE_VAL_PXI_STAR_DStarB (PXI_DStarB) | The trigger is received on the PXI DStarB trigger line. |
RFMXLTE_VAL_TimerEvent (TimerEvent) | The trigger is received from the Timer Event. |
digitalEdge | int32 | Specifies the source terminal for the digital edge trigger. This parameter is used when you set the RFMXLTE_ATTR_TRIGGER_TYPE) attribute to RFMXLTE_VAL_TRIGGER_TYPE_DIGITAL_EDGE. |
RFMXLTE_VAL_DIGITAL_EDGE_RISING_EDGE (0) | The trigger asserts on the rising edge of the signal. |
---|---|
RFMXLTE_VAL_DIGITAL_EDGE_FALLING_EDGE (1) | The trigger asserts on the falling edge of the signal. |
triggerDelay | float64 | Specifies the trigger delay time. This value is expressed in seconds. If the delay is negative, the measurement acquires pretrigger samples. If the delay is positive, the measurement acquires posttrigger samples. |
enableTrigger | int32 | Specifies whether to enable the trigger. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgIQPowerEdgeTrigger (niRFmxInstrHandle instrumentHandle, char selectorString[], char IQPowerEdgeSource[], int32 IQPowerEdgeSlope, float64 IQPowerEdgeLevel, float64 triggerDelay, int32 triggerMinQuietTimeMode, float64 triggerMinQuietTimeDuration, int32 IQPowerEdgeLevelType, int32 enableTrigger);
Configures the device to wait for the complex power of the I/Q data to cross the specified threshold and then marks a reference point within the record. To trigger on bursty signals, specify a minimum quiet time, which ensures that the trigger does not occur in the middle of the burst signal. The quiet time must be set to a value smaller than the time between bursts, but large enough to ignore power changes within a burst.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
IQPowerEdgeSource | char[] | Specifies the channel from which the device monitors the trigger. This parameter is used only when you set the RFMXLTE_ATTR_TRIGGER_TYPE) attribute to RFMXLTE_VAL_TRIGGER_TYPE_IQ_POWER_EDGE. The default value of this parameter is hardware dependent. |
IQPowerEdgeSlope | int32 | Specifies whether the device asserts the trigger when the signal power is rising or when it is falling. The device asserts the trigger when the signal power exceeds the specified level with the slope you specify. This parameter is used only when you set the RFMXLTE_ATTR_TRIGGER_TYPE attribute to RFMXLTE_VAL_TRIGGER_TYPE_IQ_POWER_EDGE. |
RFMXLTE_VAL_IQ_POWER_EDGE_RISING_SLOPE (0) | The trigger asserts when the signal power is rising. |
---|---|
RFMXLTE_VAL_IQ_POWER_EDGE_FALLING_SLOPE (1) | The trigger asserts when the signal power is falling. |
IQPowerEdgeLevel | float64 | Specifies the power level at which the device triggers. This value is expressed in dB when you set the IQPowerEdgeLevelType parameter to RFMXLTE_VAL_IQ_POWER_EDGE_TRIGGER_LEVEL_TYPE_RELATIVE, and this value is expressed in dBm when you set the IQPowerEdgeLevelType parameter to RFMXLTE_VAL_IQ_POWER_EDGE_TRIGGER_LEVEL_TYPE_ABSOLUTE. The device asserts the trigger when the signal exceeds the level specified by the value of this parameter, taking into consideration the specified slope. This parameter is used only when you set the RFMXLTE_ATTR_TRIGGER_TYPE attribute to RFMXLTE_VAL_TRIGGER_TYPE_IQ_POWER_EDGE. The default value of this parameter is hardware dependent. |
triggerDelay | float64 | Specifies the trigger delay time. This value is expressed in seconds. If the delay is negative, the measurement acquires pretrigger samples. If the delay is positive, the measurement acquires posttrigger samples. |
triggerMinQuietTimeMode | int32 | Specifies whether the measurement computes the minimum quiet time used for triggering. |
RFMXLTE_VAL_TRIGGER_MINIMUM_QUIET_TIME_MODE_MANUAL (0) | The minimum quiet time for triggering is the value of the minQuietTime parameter. |
---|---|
RFMXLTE_VAL_TRIGGER_MINIMUM_QUIET_TIME_MODE_AUTO (1) | The measurement computes the minimum quiet time used for triggering. |
triggerMinQuietTimeDuration | float64 | Specifies the time duration for which the signal must be quiet before the signal analyzer arms the I/Q power edge trigger. This value is expressed in seconds. If you set the RFMXLTE_ATTR_IQ_POWER_EDGE_TRIGGER_SLOPE attribute to RFMXLTE_VAL_IQ_POWER_EDGE_RISING_SLOPE, the signal is quiet below the trigger level. If you set the RFMXLTE_ATTR_IQ_POWER_EDGE_TRIGGER_SLOPE attribute to RFMXLTE_VAL_IQ_POWER_EDGE_FALLING_SLOPE, the signal is quiet above the trigger level. |
IQPowerEdgeLevelType | int32 | Specifies the reference for theIQPowerEdgeLevel parameter. The IQPowerEdgeLevelType parameter is used only when you set the RFMXLTE_ATTR_TRIGGER_TYPE attribute to RFMXLTE_VAL_TRIGGER_TYPE_IQ_POWER_EDGE. |
RFMXLTE_VAL_IQ_POWER_EDGE_TRIGGER_LEVEL_TYPE_RELATIVE (0) | The IQ Power Edge Level attribute is relative to the value of the RFMXLTE_ATTR_REFERENCE_LEVEL) attribute. |
---|---|
RFMXLTE_VAL_IQ_POWER_EDGE_TRIGGER_LEVEL_TYPE_ABSOLUTE (1) | The IQ Power Edge Level attribute specifies the absolute power. |
enableTrigger | int32 | Specifies whether to enable the trigger. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgSoftwareEdgeTrigger (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 triggerDelay, int32 enableTrigger);
Configures the device to wait for a software trigger and then marks a reference point within the record.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
triggerDelay | float64 | Specifies the trigger delay time. This value is expressed in seconds. If the delay is negative, the measurement acquires pretrigger samples. If the delay is positive, the measurement acquires posttrigger samples. |
enableTrigger | int32 | Specifies whether to enable the trigger. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SendSoftwareEdgeTrigger (niRFmxInstrHandle instrumentHandle);
Sends a trigger to the device when you use the RFmxLTE_CfgTrigger function to choose a software version of a trigger and the device is waiting for the trigger to be sent. You can also use this function to override a hardware trigger. This function returns an error in the following situations:
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgLinkDirection (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 linkDirection);
Configures the link direction of the signal being measured.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
linkDirection | int32 | Specifies the link direction of the received signal. |
RFMXLTE_VAL_LINK_DIRECTION_DOWNLINK (0) | The measurement uses 3GPP LTE downlink specification to measure the received signal. |
---|---|
RFMXLTE_VAL_LINK_DIRECTION_UPLINK (1) | The measurement uses 3GPP LTE uplink specification to measure the received signal. |
RFMXLTE_VAL_LINK_DIRECTION_SIDELINK (2) | The measurement uses 3GPP LTE sidelink specification to measure the received signal. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgDuplexScheme (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 duplexScheme, int32 uplinkDownlinkConfiguration);
Configures the duplexing technique of the signal being measured.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
duplexScheme | int32 | Specifies the duplexing technique of the signal being measured. |
RFMXLTE_VAL_DUPLEX_SCHEME_FDD (0) | Specifies that the duplexing technique is frequency-division duplexing. |
---|---|
RFMXLTE_VAL_DUPLEX_SCHEME_TDD (1) | Specifies that the duplexing technique is time-division duplexing. |
RFMXLTE_VAL_DUPLEX_SCHEME_LAA (2) | Specifies that the duplexing technique is license assisted access. |
uplinkDownlinkConfiguration | int32 | Specifies the configuration of the LTE frame structure in the time division duplex (TDD) mode. To configure the LTE frame, refer to table 4.2-2 of the 3GPP TS 36.211 specification. |
RFMXLTE_VAL_UPLINK_DOWNLINK_CONFIGURATION_0 (0) | The configuration of the LTE frame structure in the TDD duplex mode is 0. |
---|---|
RFMXLTE_VAL_UPLINK_DOWNLINK_CONFIGURATION_1 (1) | The configuration of the LTE frame structure in the TDD duplex mode is 1. |
RFMXLTE_VAL_UPLINK_DOWNLINK_CONFIGURATION_2 (2) | The configuration of the LTE frame structure in the TDD duplex mode is 2. |
RFMXLTE_VAL_UPLINK_DOWNLINK_CONFIGURATION_3 (3) | The configuration of the LTE frame structure in the TDD duplex mode is 3. |
RFMXLTE_VAL_UPLINK_DOWNLINK_CONFIGURATION_4 (4) | The configuration of the LTE frame structure in the TDD duplex mode is 4. |
RFMXLTE_VAL_UPLINK_DOWNLINK_CONFIGURATION_5 (5) | The configuration of the LTE frame structure in the TDD duplex mode is 5. |
RFMXLTE_VAL_UPLINK_DOWNLINK_CONFIGURATION_6 (6) | The configuration of the LTE frame structure in the TDD duplex mode is 6. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgeNodeBCategory (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 eNodeBCategory);
Configures the eNodeB category of the signal being measured.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
eNodeBCategory | int32 | Specifies the downlink eNodeB (Base Station) category. |
RFMXLTE_VAL_ENODEB_WIDE_AREA_BASE_STATION_CATEGORY_A (0) | Specifies the eNodeB is Wide Area Base Station - Category A. |
---|---|
RFMXLTE_VAL_ENODEB_WIDE_AREA_BASE_STATION_CATEGORY_B_OPTION1 (1) | Specifies the eNodeB is Wide Area Base Station - Category B Option1. |
RFMXLTE_VAL_ENODEB_WIDE_AREA_BASE_STATION_CATEGORY_B_OPTION2 (2) | Specifies the eNodeB is Wide Area Base Station - Category B Option2. |
RFMXLTE_VAL_ENODEB_LOCAL_AREA_BASE_STATION (3) | Specifies the eNodeB is Local Area Base Station. |
RFMXLTE_VAL_ENODEB_HOME_BASE_STATION (4) | Specifies the eNodeB is Home Base Station. |
RFMXLTE_VAL_ENODEB_MEDIUM_RANGE_BASE_STATION (5) | Specifies the eNodeB is Medium Range Base Station. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgNumberOfDUTAntennas (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 numberOfDUTAntennas);
Configures the number of physical antennas used for transmission by the DUT in a MIMO setup.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
numberOfDUTAntennas | int32 | Specifies the number of physical antennas available at the DUT for transmission in a MIMO setup. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgTransmitAntennaToAnalyze (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 transmitAntennaToAnalyze);
Configures the current physical antenna of the DUT in the MIMO setup being tested.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
transmitAntennaToAnalyze | int32 | Specifies the physical antenna connected to the analyzer. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgNumberOfSubblocks (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 numberOfSubblocks);
Configures the number of subblocks.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
numberOfSubblocks | int32 | Specifies the number of subblocks that are configured in the intra-band noncontiguous carrier aggregation. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgSubblockFrequencyDefinition (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 subblockFrequencyDefinition);
Configures the subblock center frequency definition, which can be an absolute frequency or relative to the absolute frequency of the first subblock. Use "subblock<n>" as the selector string to configure this function. Refer to the Center Frequency) topic for more information.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the subblock number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0" "signal::sig1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
subblockFrequencyDefinition | int32 | Specifies if the subblock center frequency is an absolute frequency or relative to the absolute frequency of the first subblock. This parameter is ignored for the first subblock and its center frequency is considered to be absolute by the measurement. |
RFMXLTE_VAL_SUBBLOCK_FREQUENCY_DEFINITION_RELATIVE (0) | Subblock center frequency is relative to the center frequency of the first subblock. |
---|---|
RFMXLTE_VAL_SUBBLOCK_FREQUENCY_DEFINITION_ABSOLUTE (1) | Subblock center frequency is an absolute 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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgBand (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 band);
Configures the evolved universal terrestrial radio access (E-UTRA) operating frequency band of a subblock. Use "subblock<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the subblock number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0" "signal::sig1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
band | int32 | Specifies the E-UTRA operating frequency band of a subblock as defined in section 5.2 of the 3GPP TS 36.521 specification. Valid values are from 1 to 255, inclusive. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgComponentCarrierSpacing (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 componentCarrierSpacingType, int32 componentCarrierAtCenterFrequency);
Configures the componentCarrierSpacingType and componentCarrierAtCenterFrequency parameters, which help to set the spacing between adjacent component carriers within a subblock. Use "subblock<n>" as the selector string to configure this function. Refer to the Channel Spacing) and Carrier Frequency Offset Definition and Reference Frequency) topics for more information about carrier spacing.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the subblock number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0" "signal::sig1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
componentCarrierSpacingType | int32 | Specifies the spacing between the two adjacent component carriers within a subblock. |
RFMXLTE_VAL_COMPONENT_CARRIER_SPACING_TYPE_NOMINAL (0) | Calculates the frequency spacing between component carriers as defined in section 5.4.1A of the 3GPP TS 36.521 specification, and sets the RFMXLTE_ATTR_COMPONENT_CARRIER_FREQUENCY) attribute. |
---|---|
RFMXLTE_VAL_COMPONENT_CARRIER_SPACING_TYPE_MINIMUM (1) | Calculates the frequency spacing between component carriers as defined in section 5.4.1A of the 3GPP TS 36.521 specification, and sets the RFMXLTE_ATTR_COMPONENT_CARRIER_FREQUENCY attribute. |
RFMXLTE_VAL_COMPONENT_CARRIER_SPACING_TYPE_USER (2) | The CC frequency that you configure in the RFMXLTE_ATTR_COMPONENT_CARRIER_FREQUENCY attribute is used. |
componentCarrierAtCenterFrequency | int32 | Specifies the index of the component carrier having its center at the user-configured center frequency. RFmxLTE uses this attribute along with the CC Spacing Type attribute to calculate the component carrier 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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgNumberOfComponentCarriers (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 numberOfComponentCarriers);
Configures the number of component carriers within a subblock. Use "subblock<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the subblock number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0" "signal::sig1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
numberOfComponentCarriers | int32 | Specifies the number of component carriers configured within a subblock. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgComponentCarrier (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 componentCarrierBandwidth, float64 componentCarrierFrequency, int32 cellID);
Configures the componentCarrierBandwidth, componentCarrierFrequency, and cellID of the component carrier. Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
componentCarrierBandwidth | float64 | Specifies the channel bandwidths of the signal being measured. |
componentCarrierFrequency | float64 | Specifies the offsets of the component carrier from the subblock center frequency that you configure in the RFMXLTE_ATTR_CENTER_FREQUENCY) attribute. This parameter is applicable only if you set the RFMXLTE_ATTR_COMPONENT_CARRIER_SPACING_TYPE) attribute to RFMXLTE_VAL_COMPONENT_CARRIER_SPACING_TYPE_USER. |
cellID | int32 | Specifies the physical layer cell identities. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgAutoResourceBlockDetectionEnabled (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 autoResourceBlockDetectionEnabled);
Configures whether the values of the RFMXLTE_ATTR_PUSCH_MODULATION_TYPE), RFMXLTE_ATTR_PUSCH_NUMBER_OF_RESOURCE_BLOCK_CLUSTERS), RFMXLTE_ATTR_PUSCH_RESOURCE_BLOCK_OFFSET), and RFMXLTE_ATTR_PUSCH_NUMBER_OF_RESOURCE_BLOCKS) attributes are automatically detected by the measurement or if you specify the values of these attributes. The measurement ignores this function, when you set the RFMXLTE_ATTR_LINK_DIRECTION) attribute to RFMXLTE_VAL_LINK_DIRECTION_DOWNLINK.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
autoResourceBlockDetectionEnabled | int32 | Specifies whether the values of the RFMXLTE_ATTR_PUSCH_MODULATION_TYPE, PUSCH Num Clusters, RFMXLTE_ATTR_PUSCH_RESOURCE_BLOCK_OFFSET, and RFMXLTE_ATTR_PUSCH_NUMBER_OF_RESOURCE_BLOCKS attributes are automatically detected by the measurement or if you specify the values of these attributes. |
RFMXLTE_VAL_AUTO_RESOURCE_BLOCK_DETECTION_ENABLED_FALSE (0) | The values of the RFMXLTE_ATTR_PUSCH_MODULATION_TYPE, RFMXLTE_ATTR_PUSCH_NUMBER_OF_RESOURCE_BLOCK_CLUSTERS, RFMXLTE_ATTR_PUSCH_RESOURCE_BLOCK_OFFSET, and RFMXLTE_ATTR_PUSCH_NUMBER_OF_RESOURCE_BLOCKS attributes that you specify are used for the measurement. |
---|---|
RFMXLTE_VAL_AUTO_RESOURCE_BLOCK_DETECTION_ENABLED_TRUE (1) | The values of the RFMXLTE_ATTR_PUSCH_MODULATION_TYPE, RFMXLTE_ATTR_PUSCH_NUMBER_OF_RESOURCE_BLOCK_CLUSTERS, RFMXLTE_ATTR_PUSCH_RESOURCE_BLOCK_OFFSET, and RFMXLTE_ATTR_PUSCH_NUMBER_OF_RESOURCE_BLOCKS attributes are detected automatically and used for the 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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgAutoDMRSDetectionEnabled (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 autoDMRSDetectionEnabled);
Configures whether the demodulation reference signal (DMRS) parameters are configured by a user or automatically detected by a measurement.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
autoDMRSDetectionEnabled | int32 | Specifies whether you need to configure the DMRS parameters, such as the values of the RFMXLTE_ATTR_UPLINK_GROUP_HOPPING_ENABLED), RFMXLTE_ATTR_UPLINK_SEQUENCE_HOPPING_ENABLED), RFMXLTE_ATTR_CELL_ID), RFMXLTE_ATTR_PUSCH_N_DMRS_1), RFMXLTE_ATTR_PUSCH_N_DMRS_2), and RFMXLTE_ATTR_PUSCH_DELTA_SEQUENCE_SHIFT) attributes, or if the measurement should automatically detect the values of these attributes. |
RFMXLTE_VAL_AUTO_DMRS_DETECTION_ENABLED_FALSE (0) | The user-defined DMRS parameters are used. |
---|---|
RFMXLTE_VAL_AUTO_DMRS_DETECTION_ENABLED_TRUE (1) | The DMRS parameters are automatically detected. Measurements returns an error if you set the RFMXLTE_ATTR_MODACC_SYNCHRONIZATION_MODE) attribute to RFMXLTE_VAL_MODACC_SYNCHRONIZATION_MODE_FRAME because it is not possible to get the frame boundary when RFmx automatically detects the DMRS parameters. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgDownlinkTestModel (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 downlinkTestModel);
Configures the EUTRA test model type. Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
downlinkTestModel | int32 | Specifies the EUTRA test model type when you set the RFMXLTE_ATTR_DOWNLINK_CHANNEL_CONFIGURATION_MODE) attribute to RFMXLTE_VAL_DOWNLINK_CHANNEL_CONFIGURATION_MODE_TEST_MODEL. Refer to section 6.1.1 of the 3GPP 36.141 specification for more information regarding test model configurations. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM1_1 (0) | Specifies an E-UTRA Test Model 1. |
---|---|
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM1_2 (1) | Specifies an E-UTRA Test Model 1.2. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM2 (2) | Specifies an E-UTRA Test Model 2. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM2A (3) | Specifies an E-UTRA Test Model 2a. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM2B (8) | Specifies an E-UTRA Test Model 2b. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM3_1 (4) | Specifies an E-UTRA Test Model 3.1. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM3_1A (7) | Specifies an E-UTRA Test Mode 3.1a. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM3_1B (9) | Specifies an E-UTRA Test Model 3.1b. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM3_2 (5) | Specifies an E-UTRA Test Model 3.2. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM3_3 (6) | Specifies an E-UTRA Test Model 3.3. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgDownlinkAutoCellIDDetectionEnabled (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 autoCellIDDetectionEnabled);
Configures whether the cell ID is configured by the user or auto-detected by the measurement.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
autoCellIDDetectionEnabled | int32 | Specifies whether to enable autodetection the of cell ID. If signal being measured does not contain primary and secondary sync signal (PSS/SSS), autodetection of the cell ID is not possible. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgPUSCHModulationType (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 modulationType);
Configures the modulation scheme used in the physical uplink shared channel (PUSCH) channel of the signal being measured. Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
modulationType | int32 | Specifies the modulation scheme used in the PUSCH channel of the signal being measured. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgPUSCHResourceBlocks (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 resourceBlockOffset, int32 numberOfResourceBlocks);
Configures the start and number of resource blocks allocated for the physical uplink shared channel (PUSCH) cluster. Use "cluster<l>" or "carrier<k>" or "subblock<n>/carrier<k>/cluster<l>" as the selector string to configure this result.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number, carrier number, and the cluster number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0/cluster0" "signal::sig1/subblock0/carrier0/cluster0" You can use the RFmxLTE_BuildClusterString) function to build the selector string. |
resourceBlockOffset | int32 | Specifies the starting resource block number of a PUSCH cluster. |
numberOfResourceBlocks | int32 | Specifies the number of consecutive resource blocks in a PUSCH cluster. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgNumberOfPUSCHResourceBlockClusters (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 numberOfResourceBlockClusters);
Configures the number of clusters of resource allocations. Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
numberOfResourceBlockClusters | int32 | Specifies the number resource allocation clusters, with each cluster including one or more consecutive resource blocks. For more information about the physical uplink shared channel (PUSCH) number of clusters, refer to 5.5.2.1.1 of the 3GPP TS 36.213 specification. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_BuildSubblockString (char selectorString[], int32 subblockNumber, int32 selectorStringOutLength, char selectorStringOut[]);
Creates the subblock string to use as the selector string with the subblock configuration or fetch attributes and functions.
Input | ||
---|---|---|
Name | Type | Description |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the result name. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "signal::sig1" "result::r1" "signal::sig1/result::r1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
subblockNumber | int32 | Specifies the number of subblocks that are configured in the intra-band noncontiguous carrier aggregation. Set this parameter to 1, which is the default, for single carrier and intra-band contiguous carrier aggregation. |
selectorStringOutLength | int32 | Specifies the length of the string that is returned by the selectorStringOut parameter. To get the minimum buffer size required to build the selector string, set the selectorStringOutLength parameter to 0. |
Output | ||
Name | Type | Description |
selectorStringOut | char[] | Returns the selector string created by this function. |
Name | Type | Description |
---|---|---|
statusOrRequiredSize | 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. When the statusOrRequiredSize return value returns the buffer size, the status code is not returned. To obtain a text description of the status code and additional information about the error condition, call the RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_BuildCarrierString (char selectorString[], int32 carrierNumber, int32 selectorStringOutLength, char selectorStringOut[]);
Creates the carrier string to use as the selector string with the SEM and ACP carrier configuration or fetch attributes and functions.
Input | ||
---|---|---|
Name | Type | Description |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the result name. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "signal::sig1" "result::r1" "signal::sig1/result::r1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
carrierNumber | int32 | Specifies the carrier number for building the selector string. |
selectorStringOutLength | int32 | Specifies the length of the string that is returned by the selectorStringOut parameter. To get the minimum buffer size required to build the selector string, set the selectorStringOutLength parameter to 0. |
Output | ||
Name | Type | Description |
selectorStringOut | char[] | Returns the selector string created by this function. |
Name | Type | Description |
---|---|---|
statusOrRequiredSize | 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. When the statusOrRequiredSize return value returns the buffer size, the status code is not returned. To obtain a text description of the status code and additional information about the error condition, call the RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_BuildClusterString (char selectorString[], int32 clusterNumber, int32 selectorStringOutLength, char selectorStringOut[]);
Creates a cluster string to use as the selector string with the ModAcc cluster configuration or the fetch attributes and functions.
Input | ||
---|---|---|
Name | Type | Description |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the result name. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "signal::sig1" "result::r1" "signal::sig1/result::r1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
clusterNumber | int32 | Specifies the cluster number. |
selectorStringOutLength | int32 | Specifies the length of the string that is returned by the selectorStringOut parameter. To get the minimum buffer size required to build the selector string, set the selectorStringOutLength parameter to 0. |
Output | ||
Name | Type | Description |
selectorStringOut | char[] | Returns the selector string created by this function. |
Name | Type | Description |
---|---|---|
statusOrRequiredSize | 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. When the statusOrRequiredSize return value returns the buffer size, the status code is not returned. To obtain a text description of the status code and additional information about the error condition, call the RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgDownlinkChannelConfigurationMode (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 channelConfigurationMode);
Configures the downlink channel configuration mode.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
channelConfigurationMode | int32 | Specifies the channel configuration mode. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgDownlinkAutoChannelDetection (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 autoPDSCHChannelDetectionEnabled, int32 autoControlChannelPowerDetectionEnabled, int32 autoPCFICHCFIDetectionEnabled, int32 reserved);
Configures whether the values of physical downlink shared channel (PDSCH) parameters, control channel signal powers, and physical control format indicator channel (PCFICH) CFI are configured by a user or auto-detected by the measurement. The measurement ignores this function, when you set the RFMXLTE_ATTR_LINK_DIRECTION) attribute to RFMXLTE_VAL_LINK_DIRECTION_UPLINK.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
autoPDSCHChannelDetectionEnabled | int32 | Specifies whether the values of the RFMXLTE_ATTR_PDSCH_RESOURCE_BLOCK_ALLOCATION) attribute, the corresponding PDSCH CW0 Modulation Type attribute, and the PDSCH Power attribute are auto-detected by the measurement or user-specified. This parameter is not valid, when you set the RFMXLTE_ATTR_DOWNLINK_CHANNEL_CONFIGURATION_MODE) attribute to RFMXLTE_VAL_DOWNLINK_CHANNEL_CONFIGURATION_MODE_TEST_MODEL. |
RFMXLTE_VAL_AUTO_PDSCH_CHANNEL_DETECTION_ENABLED_FALSE (0) | The value of the RFMXLTE_ATTR_PDSCH_RESOURCE_BLOCK_ALLOCATION attribute, the corresponding values of PDSCH CW0 Modulation Type, and the PDSCH Power attribute that you specify are used for the measurement. |
---|---|
RFMXLTE_VAL_AUTO_PDSCH_CHANNEL_DETECTION_ENABLED_TRUE (1) | The value of the RFMXLTE_ATTR_PDSCH_RESOURCE_BLOCK_ALLOCATION attribute, the corresponding values of PDSCH CW0 Modulation Type, and the PDSCH Power attribute are auto-detected and used for the measurement. |
autoControlChannelPowerDetectionEnabled | int32 | Specifies whether the value of PSS Power, SSS Power, PBCH Power, PDCCH Power, and PCFICH Power attributes are auto-detected by the measurement or user-specified. Currently, auto-detectionPHICH Power attribute is not supported. This parameter is not valid, when you set the RFMXLTE_ATTR_DOWNLINK_CHANNEL_CONFIGURATION_MODE attribute to RFMXLTE_VAL_DOWNLINK_CHANNEL_CONFIGURATION_MODE_TEST_MODEL. |
RFMXLTE_VAL_AUTO_CONTROL_CHANNEL_POWER_DETECTION_ENABLED_FALSE (0) | The value of the PSS Power, SSS Power, PDCCH Power, PBCH Power, PHICH Power, and PCFICH Power attributes that you specify are used for the measurement. |
---|---|
RFMXLTE_VAL_AUTO_CONTROL_CHANNEL_POWER_DETECTION_ENABLED_TRUE (1) | The value of the PSS Power, SSS Power, PDCCH Power, PBCH Power, and PCFICH Power attributes are auto-detected and used for the measurement. |
autoPCFICHCFIDetectionEnabled | int32 | Specifies whether the value of RFMXLTE_ATTR_PCFICH_CFI) attribute is auto-detected by the measurement or user-specified. This parameter is not valid, when you set the RFMXLTE_ATTR_DOWNLINK_CHANNEL_CONFIGURATION_MODE attribute to RFMXLTE_VAL_DOWNLINK_CHANNEL_CONFIGURATION_MODE_TEST_MODEL. |
RFMXLTE_VAL_AUTO_PCFICH_CFI_DETECTION_ENABLED_FALSE (0) | The value of RFMXLTE_ATTR_PCFICH_CFI attribute that you specify is used for the measurement. |
---|---|
RFMXLTE_VAL_AUTO_PCFICH_CFI_DETECTION_ENABLED_TRUE (1) | The value of RFMXLTE_ATTR_PCFICH_CFI attribute is auto-detected and used for the measurement. This value is obtained by decoding the PCFICH channel. |
reserved | int32 | This parameter is not supported in this release and it is reserved for future enhancements. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgCellSpecificRatio (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 cellSpecificRatio);
Configures the cellSpecificRatio parameter. Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
cellSpecificRatio | int32 | Specifies the ratio �b/�a for the cell-specific ratio of one, two, or four cell-specific antenna ports as described in Table 5.2-1 in section 5.2 of the 3GPP TS 36.213 Specifications. This parameter determines the power of the channel resource element (RE) in the symbols that do not contain the reference symbols. |
RFMXLTE_VAL_DOWNLINK_USER_DEFINED_RATIO_P_B0 (0) | Specifies a ratio of 1 for one antenna port and 5/4 for two or four antenna ports. |
---|---|
RFMXLTE_VAL_DOWNLINK_USER_DEFINED_RATIO_P_B1 (1) | Specifies a ratio of 4/5 for one antenna port and 1 for two or four antenna ports. |
RFMXLTE_VAL_DOWNLINK_USER_DEFINED_RATIO_P_B2 (2) | Specifies a ratio of 3/5 for one antenna port and 3/4 for two or four antenna ports. |
RFMXLTE_VAL_DOWNLINK_USER_DEFINED_RATIO_P_B3 (3) | Specifies a ratio of 2/5 for one antenna port and 1/2 for two or four antenna ports. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgDownlinkSynchronizationSignal (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 PSSPower, float64 SSSPower);
Configures the synchronization signal power relative to the cell-specific reference signal. Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
PSSPower | float64 | Specifies the power of the primary synchronization signal (PSS) relative to the power of the cell-specific reference signal. This value is expressed in dB. |
SSSPower | float64 | Specifies the power of the secondary synchronization signal (SSS) relative to the power of the cell-specific reference signal. This value is expressed in dB. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgPBCH (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 PBCHPower);
Configures the power of physical broadcast channel (PBCH) power relative to the cell-specific reference signal. Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
PBCHPower | float64 | Specifies the power of the PBCH relative to the power of the cell-specific reference signal. This value is expressed in dB. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgPDCCH (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 PDCCHPower);
Configures the physical downlink control channel (PDCCH) power relative to the cell-specific reference signal. Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
PDCCHPower | float64 | Specifies the power of the PDCCH relative to the power of the cell-specific reference signal. This value is expressed in dB. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgDownlinkNumberOfSubframes (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 numberOfSubframes);
Configures the number of unique subframes that are transmitted from the DUT. Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
numberOfSubframes | int32 | Specifies the number of subframes to be configured. If you set the RFMXLTE_ATTR_DOWNLINK_CHANNEL_CONFIGURATION_MODE) attribute to RFMXLTE_VAL_DOWNLINK_CHANNEL_CONFIGURATION_MODE_TEST_MODEL, this parameter will be set to 10 for FDD and 20 for TDD by default. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgPCFICH (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 CFI, float64 power);
Configures the CFI and power parameters of the physical control format indicator channel (PCFICH). Use "subframe<l>" or "carrier<k>" or "subblock<n>" or "subblock<n>/carrier<k>/subframe<l>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number, carrier number, and subframe number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0/subframe0" "signal::sig1/subblock0/carrier0/subframe0" You can use the RFmxLTE_BuildSubframeString) function to build the selector string. |
CFI | int32 | Specifies the control format indicator (CFI) carried by PCFICH. CFI is used to compute the number of OFDM symbols which will determine the size of physical downlink control channel (PDCCH) within a subframe. |
power | float64 | Specifies the power of the PCFICH relative to the power of the cell-specific reference signal. This value is expressed in dB. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgPHICH (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 resource, int32 duration, float64 power);
Configures the resource, duration, and power parameters of the physical hybrid-ARQ indicator channel (PHICH). Use "subframe<l>" or "carrier<k>" or "subblock<n>" or "subblock<n>/carrier<k>/subframe<l>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number, carrier number, and subframe number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0/subframe0" "signal::sig1/subblock0/carrier0/subframe0" You can use the RFmxLTE_BuildSubframeString) function to build the selector string. |
resource | int32 | Specifies the PHICH resource value. This value is expressed in Ng. This parameter is used to calculate number of PHICH resource groups. Refer to section 6.9 of the 3GPP 36.211 specification for more information about PHICH. |
duration | int32 | Specifies the PHICH duration. |
power | float64 | Specifies the power of all BPSK symbols in a PHICH sequence. This value is expressed in dB. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgNumberOfPDSCHChannels (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 numberOfPDSCHChannels);
Configures the number of different physical downlink shared channel (PDSCH) allocations in a subframe. Use "subframe<l>" or "carrier<k>" or "subblock<n>" or "subblock<n>/carrier<k>/subframe<l>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number, carrier number, and subframe number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0/subframe0" "signal::sig1/subblock0/carrier0/subframe0" You can use the RFmxLTE_BuildSubframeString) function to build the selector string. |
numberOfPDSCHChannels | int32 | Specifies the number of PDSCH allocations in a subframe. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgPDSCH (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 CW0ModulationType, char resourceBlockAllocation[], float64 power);
Configures the codeword0 modulation type, resource block, and relative power of a physical downlink shared channel (PDSCH) allocation. Use "PDSCH<m>" or "subframe<l>" or "carrier<k>" or "subblock<n>" or "subblock<n>/carrier<k>/subframe<l>/PDSCH<m>" as the selector string to configure or read this attribute.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number, carrier number, subframe number, and PDSCH number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0/subframe0/PDSCH0" "signal::sig1/subblock0/carrier0/subframe0/PDSCH0" You can use the RFmxLTE_BuildPDSCHString) function to build the selector string. |
CW0ModulationType | int32 | Specifies the modulation type of Codeword0 PDSCH allocation. |
resourceBlockAllocation | char[] | Specifies the resource blocks of the PDSCH allocation. The following string formats are supported fo this attribute: 1) RBStartValue1-RBStopValue1,RBStartValue2-RBStopValue2 2) RB1,RB2 3) RBStartValue1-RBStopValue1, RB1,RBStartValue2-RBStopValue2,RB2 For example: If the RB allocation is 0-5,7,8,10-15, the RB allocation string specifies contiguous resource blocks from 0 to 5, resource block 7, resource block 8, and contiguous resource blocks from 10 to 15. |
power | float64 | Specifies the PDSCH power level (�a) relative to the power of the cell-specific reference signal. This value is expressed in dB. Measurement uses the cell specific Ratio attribute to calculate �b. Refer to section 3.3 of the 3GPP 36.521 specifications for more information about �a. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_BuildSubblockString (char selectorString[], int32 subblockNumber, int32 selectorStringOutLength, char selectorStringOut[]);
Creates the subblock string to use as the selector string with the subblock configuration or fetch attributes and functions.
Input | ||
---|---|---|
Name | Type | Description |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the result name. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "signal::sig1" "result::r1" "signal::sig1/result::r1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
subblockNumber | int32 | Specifies the number of subblocks that are configured in the intra-band noncontiguous carrier aggregation. Set this parameter to 1, which is the default, for single carrier and intra-band contiguous carrier aggregation. |
selectorStringOutLength | int32 | Specifies the length of the string that is returned by the selectorStringOut parameter. To get the minimum buffer size required to build the selector string, set the selectorStringOutLength parameter to 0. |
Output | ||
Name | Type | Description |
selectorStringOut | char[] | Returns the selector string created by this function. |
Name | Type | Description |
---|---|---|
statusOrRequiredSize | 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. When the statusOrRequiredSize return value returns the buffer size, the status code is not returned. To obtain a text description of the status code and additional information about the error condition, call the RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_BuildCarrierString (char selectorString[], int32 carrierNumber, int32 selectorStringOutLength, char selectorStringOut[]);
Creates the carrier string to use as the selector string with the SEM and ACP carrier configuration or fetch attributes and functions.
Input | ||
---|---|---|
Name | Type | Description |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the result name. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "signal::sig1" "result::r1" "signal::sig1/result::r1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
carrierNumber | int32 | Specifies the carrier number for building the selector string. |
selectorStringOutLength | int32 | Specifies the length of the string that is returned by the selectorStringOut parameter. To get the minimum buffer size required to build the selector string, set the selectorStringOutLength parameter to 0. |
Output | ||
Name | Type | Description |
selectorStringOut | char[] | Returns the selector string created by this function. |
Name | Type | Description |
---|---|---|
statusOrRequiredSize | 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. When the statusOrRequiredSize return value returns the buffer size, the status code is not returned. To obtain a text description of the status code and additional information about the error condition, call the RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_BuildSubframeString (char selectorString[], int32 subframeNumber, int32 selectorStringOutLength, char selectorStringOut[]);
Creates the subframe string to use as the selector string with the configuration or the fetch attributes and functions.
Input | ||
---|---|---|
Name | Type | Description |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number, and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
subframeNumber | int32 | Specifies the subframe number for building the selector string. |
selectorStringOutLength | int32 | Specifies the length of the string that is returned by the selectorStringOut parameter. To get the minimum buffer size required to build the selector string, set the selectorStringOutLength parameter to 0. |
Output | ||
Name | Type | Description |
selectorStringOut | char[] | Returns the selector string created by this function. |
Name | Type | Description |
---|---|---|
statusOrRequiredSize | 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. When the statusOrRequiredSize return value returns the buffer size, the status code is not returned. To obtain a text description of the status code and additional information about the error condition, call the RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgPSSCHModulationType (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 modulationType);
Configures the modulation scheme used in the physical sidelink shared channel (PSSCH) channel of the signal being measured. Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
modulationType | int32 | Specifies the modulation scheme used in the PSSCH channel of the signal being measured. The default value is RFMXLTE_VAL_PSSCH_MODULATION_TYPE_QPSK |
RFMXLTE_VAL_PSSCH_MODULATION_TYPE_QPSK (0) | Specifies a QPSK modulation scheme. |
---|---|
RFMXLTE_VAL_PSSCH_MODULATION_TYPE_QAM16 (1) | Specifies a 16-QAM modulation scheme. |
RFMXLTE_VAL_PSSCH_MODULATION_TYPE_QAM64 (2) | Specifies a 64-QAM modulation scheme. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgPSSCHResourceBlocks (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 resourceBlockOffset, int32 numberOfResourceBlocks);
Configures the start and number of resource blocks allocated for the physical sidelink shared channel (PSSCH) allocation. Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
resourceBlockOffset | int32 | Specifies the starting resource block number of the PSSCH allocation. |
numberOfResourceBlocks | int32 | Specifies the number of consecutive resource blocks in the PSSCH allocation. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_BuildSubblockString (char selectorString[], int32 subblockNumber, int32 selectorStringOutLength, char selectorStringOut[]);
Creates the subblock string to use as the selector string with the subblock configuration or fetch attributes and functions.
Input | ||
---|---|---|
Name | Type | Description |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the result name. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "signal::sig1" "result::r1" "signal::sig1/result::r1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
subblockNumber | int32 | Specifies the number of subblocks that are configured in the intra-band noncontiguous carrier aggregation. Set this parameter to 1, which is the default, for single carrier and intra-band contiguous carrier aggregation. |
selectorStringOutLength | int32 | Specifies the length of the string that is returned by the selectorStringOut parameter. To get the minimum buffer size required to build the selector string, set the selectorStringOutLength parameter to 0. |
Output | ||
Name | Type | Description |
selectorStringOut | char[] | Returns the selector string created by this function. |
Name | Type | Description |
---|---|---|
statusOrRequiredSize | 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. When the statusOrRequiredSize return value returns the buffer size, the status code is not returned. To obtain a text description of the status code and additional information about the error condition, call the RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_BuildCarrierString (char selectorString[], int32 carrierNumber, int32 selectorStringOutLength, char selectorStringOut[]);
Creates the carrier string to use as the selector string with the SEM and ACP carrier configuration or fetch attributes and functions.
Input | ||
---|---|---|
Name | Type | Description |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the result name. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "signal::sig1" "result::r1" "signal::sig1/result::r1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
carrierNumber | int32 | Specifies the carrier number for building the selector string. |
selectorStringOutLength | int32 | Specifies the length of the string that is returned by the selectorStringOut parameter. To get the minimum buffer size required to build the selector string, set the selectorStringOutLength parameter to 0. |
Output | ||
Name | Type | Description |
selectorStringOut | char[] | Returns the selector string created by this function. |
Name | Type | Description |
---|---|---|
statusOrRequiredSize | 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. When the statusOrRequiredSize return value returns the buffer size, the status code is not returned. To obtain a text description of the status code and additional information about the error condition, call the RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgNBIoTComponentCarrier (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 NCellID, int32 uplinkSubcarrierSpacing);
Configures the Ncell ID and Uplink Subcarrier Spacing parameters for the NB-IoT signal. Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
NCellID | int32 | Specifies the narrowband physical layer cell identity. |
uplinkSubcarrierSpacing | int32 | Specifies the subcarrier bandwidth of an NB-IoT signal. This parameter specifies the spacing between adjacent subcarriers. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgNPUSCHFormat (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 format);
Configures the format of the narrowband physical uplink shared channel (NPUSCH). Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
format | int32 | Specifies the NPUSCH format. A value of 1 indicates that NPUSCH carries user data (UL-SCH) and a value of 2 indicates, NPUSCH carries uplink control information. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgAutoNPUSCHChannelDetectionEnabled (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 autoNPUSCHChannelDetectionEnabled);
Configures whether the values of the RFMXLTE_ATTR_NPUSCH_TONE_OFFSET), NPUSCH Num Tones, and RFMXLTE_ATTR_NPUSCH_MODULATION_TYPE) attributes for the NPUSCH channel are auto-detected by the measurement or specified by you.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
autoNPUSCHChannelDetectionEnabled | int32 | Specifies whether the values of RFMXLTE_ATTR_NPUSCH_TONE_OFFSET, NPUSCH Number of Tones, and RFMXLTE_ATTR_NPUSCH_MODULATION_TYPE attributes are auto-detected by the measurement or specified by you. |
RFMXLTE_VAL_AUTO_NPUSCH_CHANNEL_DETECTION_ENABLED_FALSE (0) | The measurement uses the values that you specify for the RFMXLTE_ATTR_NPUSCH_TONE_OFFSET, NPUSCH Number of Tones, and NPUSCH ModType attributes. |
---|---|
RFMXLTE_VAL_AUTO_NPUSCH_CHANNEL_DETECTION_ENABLED_TRUE (1) | The measurement uses the values of the RFMXLTE_ATTR_NPUSCH_TONE_OFFSET, NPUSCHÂ Number of Tones, and RFMXLTE_ATTR_NPUSCH_MODULATION_TYPE attributes that are auto-detected. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgNPUSCHTones (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 toneOffset, int32 numberOfTones, int32 modulationType);
Configures the values of toneOffset, numberOfTones, and modulationType parameters for NPUSCH channel. Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
toneOffset | int32 | Specifies the location of the starting subcarrier (tone) within the 200 kHz bandwidth that is allocated to the NPUSCH channel. For 15 kHz subcarrier spacing, the valid values are as follows: For 3.75 kHz subcarrier spacing, the valid values are 0 to 47, inclusive. |
numberOfTones | int32 | Specifies the number of subcarriers (tones) within the 200 kHz bandwidth that is allocated to the NPUSCH channel. For Format 1 and 15 kHz subcarrier spacing, the valid values are 1, 3, 6, and 12. For Format 1, 3.75 kHz subcarrier spacing, and Format 2, the valid value is 1. |
modulationType | int32 | Specifies the modulation type that is used by the NPUSCH channel. This parameter is valid when numberOfTones is equal to 1 and RFMXLTE_ATTR_NPUSCH_FORMAT) is equal to 1. The modulation type for other configurations is defined in Table 10.1.3.2-1 of the 3GPP TS 36.211 specification. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgNPUSCHStartingSlot (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 startingSlot);
Configures the starting slot of the NPUSCH burst. Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
startingSlot | int32 | Specifies the starting slot number of the NPUSCH burst. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgNPUSCHDMRS (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 NPUSCHDMRSBaseSequenceMode, int32 NPUSCHDMRSBaseSequenceIndex, int32 NPUSCHDMRSCyclicShift, int32 NPUSCHDMRSGroupHoppingEnabled, int32 NPUSCHDMRSDeltaSS);
Configures the base sequence mode, base sequence index, cyclic shift, delta sequence shift of the narrowband physical uplink shared channel (NPUSCH) DMRS and specifies whether group hopping is enabled. Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
NPUSCHDMRSBaseSequenceMode | int32 | Specifies whether the NPUSCHDMRSBaseSequenceIndex is computed by the measurement or user-specified. This parameter is valid when you set the NPUSCHDMRSGroupHoppingEnabled parameter to RFMXLTE_VAL_NPUSCH_DMRS_GROUP_HOPPING_ENABLED_FALSE, the value of RFMXLTE_ATTR_NPUSCH_FORMAT) attribute to 1, and the value of NPUSCH Number of Tones attribute to 3, 6, or 12. |
RFMXLTE_VAL_NPUSCH_DMRS_BASE_SEQUENCE_MODE_MANUAL (0) | The measurement uses the value that you specify for the NPUSCHDMRSBaseSequenceIndex parameter. |
---|---|
RFMXLTE_VAL_NPUSCH_DMRS_BASE_SEQUENCE_MODE_AUTO (1) | The measurement uses the value of RFMXLTE_ATTR_NCELL_ID) attribute to compute the NPUSCHDMRSBaseSequenceIndex as defined in section 10.1.4.1.2 of the 3GPP TS 36.211 specification. |
NPUSCHDMRSBaseSequenceIndex | int32 | Specifies the base sequence index of the NPUSCH DMRS as defined in section 10.1.4.1.2 of the 3GPP TS 36.211 specification. This parameter is valid when you set the NPUSCHDMRSGroupHoppingEnabled parameter to RFMXLTE_VAL_NPUSCH_DMRS_GROUP_HOPPING_ENABLED_FALSE, the NPUSCHDMRSBaseSequenceMode parameter to RFMXLTE_VAL_NPUSCH_DMRS_BASE_SEQUENCE_MODE_MANUAL, and the value of NPUSCH Number of Tones attribute to 3, 6, or 12. |
NPUSCHDMRSCyclicShift | int32 | Specifies the cyclic shift of the NPUSCH DMRS as defined in table 10.1.4.1.2-3 of the 3GPP TS 36.211 specification. This parameter is valid when you set the value of RFMXLTE_ATTR_NPUSCH_NUMBER_OF_TONES) attribute to 3 or 6. If the value of RFMXLTE_ATTR_NPUSCH_NUMBER_OF_TONES attribute is 12, the NPUSCH DMRS Cyclic Shift parameter has a fixed value of 0. |
NPUSCHDMRSGroupHoppingEnabled | int32 | Specifies whether group hopping is enabled for the NPUSCH DMRS. This parameter is valid when the value of RFMXLTE_ATTR_NPUSCH_FORMAT) is equal to 1. |
RFMXLTE_VAL_NPUSCH_DMRS_GROUP_HOPPING_ENABLED_FALSE (0) | Group hopping is disabled. |
---|---|
RFMXLTE_VAL_NPUSCH_DMRS_GROUP_HOPPING_ENABLED_TRUE (1) | Group hopping is enabled. The sequence group number is calculated as defined in section 10.1.4.1.3 of the 3GPP TS 36.211 specification |
NPUSCHDMRSDeltaSS | int32 | Specifies the delta sequence shift of the NPUSCH DMRS that is used to calculate the sequence shift pattern, which in turn is used to compute the sequence group number as defined in section 10.1.4.1.3 of the 3GPP TS 36.211 specification. This parameter is valid when you set the NPUSCHDMRSGroupHoppingEnabled parameter to RFMXLTE_VAL_NPUSCH_DMRS_GROUP_HOPPING_ENABLED_TRUE. The default value is 0. Valid values are 0 to 29, inclusive. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgEMTCAnalysisEnabled (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 EMTCAnalysisEnabled);
Configures whether the component carrier contains an enhanced machine type communications (Cat-M1 or Cat-M2) transmission. Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
EMTCAnalysisEnabled | int32 | Specifies whether the component carrier contains an eMTC transmission. |
RFMXLTE_VAL_EMTC_ANALYSIS_ENABLED_FALSE (0) | The measurement considers the signal as LTE FDD/TDD transmission. |
---|---|
RFMXLTE_VAL_EMTC_ANALYSIS_ENABLED_TRUE (1) | Detects the eMTC half duplex pattern, narrow band hopping, and eMTC guard symbols present in the uplink transmission. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgComponentCarrierArray (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 componentCarrierBandwidth[], float64 componentCarrierFrequency[], int32 cellID[], int32 numberOfElements);
Configures an array of bandwidths, carrier offset frequencies, and cell IDs of component carriers. Use "subblock<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the subblock number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0" "signal::sig1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
componentCarrierBandwidth | float64[] | Specifies the array of channel bandwidths of the signal being measured. |
componentCarrierFrequency | float64[] | Specifies the array of offsets of the component carrier from the subblock center frequency that you configure in the RFMXLTE_ATTR_CENTER_FREQUENCY) attribute. This parameter is applicable only if you set the RFMXLTE_ATTR_COMPONENT_CARRIER_SPACING_TYPE) attribute to RFMXLTE_VAL_COMPONENT_CARRIER_SPACING_TYPE_USER. |
cellID | int32[] | Specifies the array of the physical layer cell identities. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CfgDownlinkTestModelArray (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 downlinkTestModel[], int32 numberOfElements);
Configures the EUTRA test model type for each component carrier within the subblock.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the subblock number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0" "signal::sig1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
downlinkTestModel | int32[] | Specifies the array of EUTRA test model types when you set the RFMXLTE_ATTR_DOWNLINK_CHANNEL_CONFIGURATION_MODE) attribute to RFMXLTE_VAL_DOWNLINK_CHANNEL_CONFIGURATION_MODE_TEST_MODEL. Refer to section 6.1.1 of the 3GPP 36.141 specification for more information regarding test model configurations. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM1_1 (0) | Specifies an E-UTRA Test Model 1. |
---|---|
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM1_2 (1) | Specifies an E-UTRA Test Model 1.2. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM2 (2) | Specifies an E-UTRA Test Model 2. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM2A (3) | Specifies an E-UTRA Test Model 2a. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM2B (8) | Specifies an E-UTRA Test Model 2b. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM3_1 (4) | Specifies an E-UTRA Test Model 3.1. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM3_1A (7) | Specifies an E-UTRA Test Mode 3.1a. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM3_1B (9) | Specifies an E-UTRA Test Model 3.1b. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM3_2 (5) | Specifies an E-UTRA Test Model 3.2. |
RFMXLTE_VAL_DOWNLINK_TEST_MODEL_TM3_3 (6) | Specifies an E-UTRA Test Model 3.3. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_BuildSubblockString (char selectorString[], int32 subblockNumber, int32 selectorStringOutLength, char selectorStringOut[]);
Creates the subblock string to use as the selector string with the subblock configuration or fetch attributes and functions.
Input | ||
---|---|---|
Name | Type | Description |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the result name. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "signal::sig1" "result::r1" "signal::sig1/result::r1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
subblockNumber | int32 | Specifies the number of subblocks that are configured in the intra-band noncontiguous carrier aggregation. Set this parameter to 1, which is the default, for single carrier and intra-band contiguous carrier aggregation. |
selectorStringOutLength | int32 | Specifies the length of the string that is returned by the selectorStringOut parameter. To get the minimum buffer size required to build the selector string, set the selectorStringOutLength parameter to 0. |
Output | ||
Name | Type | Description |
selectorStringOut | char[] | Returns the selector string created by this function. |
Name | Type | Description |
---|---|---|
statusOrRequiredSize | 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. When the statusOrRequiredSize return value returns the buffer size, the status code is not returned. To obtain a text description of the status code and additional information about the error condition, call the RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_BuildCarrierString (char selectorString[], int32 carrierNumber, int32 selectorStringOutLength, char selectorStringOut[]);
Creates the carrier string to use as the selector string with the SEM and ACP carrier configuration or fetch attributes and functions.
Input | ||
---|---|---|
Name | Type | Description |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the result name. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "signal::sig1" "result::r1" "signal::sig1/result::r1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
carrierNumber | int32 | Specifies the carrier number for building the selector string. |
selectorStringOutLength | int32 | Specifies the length of the string that is returned by the selectorStringOut parameter. To get the minimum buffer size required to build the selector string, set the selectorStringOutLength parameter to 0. |
Output | ||
Name | Type | Description |
selectorStringOut | char[] | Returns the selector string created by this function. |
Name | Type | Description |
---|---|---|
statusOrRequiredSize | 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. When the statusOrRequiredSize return value returns the buffer size, the status code is not returned. To obtain a text description of the status code and additional information about the error condition, call the RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_BuildClusterString (char selectorString[], int32 clusterNumber, int32 selectorStringOutLength, char selectorStringOut[]);
Creates a cluster string to use as the selector string with the ModAcc cluster configuration or the fetch attributes and functions.
Input | ||
---|---|---|
Name | Type | Description |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the result name. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "signal::sig1" "result::r1" "signal::sig1/result::r1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
clusterNumber | int32 | Specifies the cluster number. |
selectorStringOutLength | int32 | Specifies the length of the string that is returned by the selectorStringOut parameter. To get the minimum buffer size required to build the selector string, set the selectorStringOutLength parameter to 0. |
Output | ||
Name | Type | Description |
selectorStringOut | char[] | Returns the selector string created by this function. |
Name | Type | Description |
---|---|---|
statusOrRequiredSize | 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. When the statusOrRequiredSize return value returns the buffer size, the status code is not returned. To obtain a text description of the status code and additional information about the error condition, call the RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_ModAccCfgAveraging (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 averagingEnabled, int32 averagingCount);
Configures averaging for the ModAcc measurement.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
averagingEnabled | int32 | Specifies whether to enable averaging for the measurement. |
RFMXLTE_VAL_MODACC_AVERAGING_ENABLED_FALSE (0) | The measurement is performed on a single acquisition. |
---|---|
RFMXLTE_VAL_MODACC_AVERAGING_ENABLED_TRUE (1) | The measurement is averaged over multiple acquisitions. The number of acquisitions is obtained by the averagingCount parameter. |
averagingCount | int32 | Specifies the number of acquisitions used for averaging when you set the averagingEnabled parameter to RFMXLTE_VAL_MODACC_AVERAGING_ENABLED_TRUE. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_ModAccCfgSynchronizationModeAndInterval (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 synchronizationMode, int32 measurementOffset, int32 measurementLength);
Configures the synchronizationMode, the measurementOffset, and the measurementLength parameters of the ModAcc measurement. Refer to the LTE Modulation Accuracy (ModAcc)) topic for more information about ModAcc measurements.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
synchronizationMode | int32 | Specifies whether the measurement is performed from the frame or the slot boundary. When you set the RFMXLTE_ATTR_LINK_DIRECTION) attribute to RFMXLTE_VAL_LINK_DIRECTION_DOWNLINK, the measurement supports only frame synchronization mode. |
RFMXLTE_VAL_MODACC_SYNCHRONIZATION_MODE_FRAME (0) | The frame boundary is detected, and the measurement is performed over the measurementLength parameter, starting at the measurementOffset parameter from the frame boundary. When you set the RFMXLTE_ATTR_TRIGGER_TYPE) attribute to RFMXLTE_VAL_TRIGGER_TYPE_DIGITAL_EDGE, the measurement expects a trigger at the frame boundary. |
---|---|
RFMXLTE_VAL_MODACC_SYNCHRONIZATION_MODE_SLOT (1) | The slot boundary is detected, and the measurement is performed over the measurementLength parameter starting at the measurementOffset parameter from the slot boundary. When you set the RFMXLTE_ATTR_TRIGGER_TYPE attribute to RFMXLTE_VAL_TRIGGER_TYPE_DIGITAL_EDGE, the measurement expects a trigger at any slot boundary. |
RFMXLTE_VAL_MODACC_SYNCHRONIZATION_MODE_MARKER (2) | The measurement expects a marker (trigger) at the frame boundary from the user. The measurement takes advantage of triggered acquisitions to reduce processing resulting in faster measurement time. Measurement is performed over the measurementLength parameter starting at the measurementOffset parameter from the frame boundary. |
measurementOffset | int32 | Specifies the measurement offset, in slots, to skip from the synchronization boundary. The synchronization boundary is specified by the synchronizationMode parameter. |
measurementLength | int32 | Specifies the number of slots to be measured. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_ModAccCfgEVMUnit (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 EVMUnit);
Configures the units of the EVM results.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
EVMUnit | int32 | Specifies the units of the EVM results. |
RFMXLTE_VAL_MODACC_EVM_UNIT_PERCENTAGE (0) | The EVM is reported in percentage. |
---|---|
RFMXLTE_VAL_MODACC_EVM_UNIT_DB (1) | The EVM is reported in dB. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_ModAccCfgFFTWindowOffset (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 FFTWindowOffset);
Configures the position of the FFT window that is used to calculate the EVM.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
FFTWindowOffset | float64 | Specifies the position of the FFT window that is used to calculate the EVM. The offset is expressed as a percentage of the cyclic prefix length. If you set this parameter to 0, the EVM window starts from the end of cyclic prefix. If you set this parameter to 100, the EVM window starts from the beginning of cyclic prefix. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_ModAccCfgCommonClockSourceEnabled (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 commonClockSourceEnabled);
Configures the Reference Clock and specifies whether same Reference Clock is used for local oscillator and D/A converter. The modacc measurement ignores this function, when you set the RFMXLTE_ATTR_LINK_DIRECTION) attribute to RFMXLTE_VAL_LINK_DIRECTION_DOWNLINK.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
commonClockSourceEnabled | int32 | Specifies whether the same Reference Clock is used for the local oscillator and the D/A converter. When the same Reference Clock is used, the carrier frequency offset is proportional to the Sample Clock error. |
RFMXLTE_VAL_MODACC_COMMON_CLOCK_SOURCE_ENABLED_FALSE (0) | The Sample Clock error is estimated independently. |
---|---|
RFMXLTE_VAL_MODACC_COMMON_CLOCK_SOURCE_ENABLED_TRUE (1) | The Sample Clock error is estimated from carrier frequency offset. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_ModAccCfgFFTWindowPosition (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 FFTWindowType, float64 FFTWindowOffset, float64 FFTWindowLength);
Configures the FFT window position used for an EVM calculation. Refer to the LTE Modulation Accuracy (ModAcc)) topic for more information about FFT window position.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
FFTWindowType | int32 | Specifies the FFT window type used for an EVM calculation. |
RFMXLTE_VAL_MODACC_FFT_WINDOW_TYPE_3GPP (0) | The maximum EVM between the start window position and the end window position is returned according to the 3GPP specification. The window positions are specified by the FFTWindowLength parameter. For more information about the FFT window specification, refer to the 3GPP TS 36.521 specification, Annexe E.3.2. |
---|---|
RFMXLTE_VAL_MODACC_FFT_WINDOW_TYPE_CUSTOM (1) | Only one FFT window position is used for the EVM calculation. The FFT window position is specified by the FFTWindowOffset parameter. |
FFTWindowOffset | float64 | Specifies the position of the FFT window used to calculate the EVM. The offset is expressed as a percentage of the cyclic prefix length. If you set this parameter to 0, the EVM window starts from the end of cyclic prefix. If you set this parameter to 100, the EVM window starts from the beginning of cyclic prefix. |
FFTWindowLength | float64 | Specifies the FFT window length. This value is expressed in a percentage of the cyclic prefix length. This parameter is used when you set the FFTWindowType parameter to RFMXLTE_VAL_MODACC_FFT_WINDOW_TYPE_3GPP, where you need to calculate the EVM using two different FFT window positions, Delta_C-W/2, and Delta_C+W/2. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_ModAccCfgInBandEmissionMaskType (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 inBandEmissionMaskType);
Configures the inBandEmissionMaskType parameter to be used.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
inBandEmissionMaskType | int32 | Specifies the in-band emissions mask type to be used for measuring in-band emission margin (dB) and subblock in-Band emission margin (dB) results. Refer to section 6.5.2.3.5 of the 3GPP 36.521-1 specification for more information. |
RFMXLTE_VAL_MODACC_IN_BAND_EMISSION_MASK_TYPE_RELEASE_8_10 (0) | Specifies the mask type to be used for UE, supporting 3GPP Release 8 to 3GPP Release 10 specification. |
---|---|
RFMXLTE_VAL_MODACC_IN_BAND_EMISSION_MASK_TYPE_RELEASE_11_ONWARDS (1) | Specifies the mask type to be used for UE, supporting 3GPP Release 11 and higher specification. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_ACPCfgAveraging (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 averagingEnabled, int32 averagingCount, int32 averagingType);
Configures averaging for the ACP measurement.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
averagingEnabled | int32 | Specifies whether to enable averaging for the measurement. |
RFMXLTE_VAL_ACP_AVERAGING_ENABLED_FALSE (0) | The measurement is performed on a single acquisition. |
---|---|
RFMXLTE_VAL_ACP_AVERAGING_ENABLED_TRUE (1) | The measurement is averaged over multiple acquisitions. The number of acquisitions is obtained by the averagingCount parameter. |
averagingCount | int32 | Specifies the number of acquisitions used for averaging when you set the averagingEnabled parameter to RFMXLTE_VAL_ACP_AVERAGING_ENABLED_TRUE. |
averagingType | int32 | Specifies the averaging type for averaging multiple spectrum acquisitions. The averaged spectrum is used for the measurement. |
RFMXLTE_VAL_ACP_AVERAGING_TYPE_RMS (0) | The power spectrum is linearly averaged. RMS averaging reduces signal fluctuations but not the noise floor. |
---|---|
RFMXLTE_VAL_ACP_AVERAGING_TYPE_LOG (1) | The power spectrum is averaged in a logarithmic scale. |
RFMXLTE_VAL_ACP_AVERAGING_TYPE_SCALAR (2) | The square root of the power spectrum is averaged. |
RFMXLTE_VAL_ACP_AVERAGING_TYPE_MAXIMUM (3) | The peak power in the spectrum at each frequency bin is retained from one acquisition to the next. |
RFMXLTE_VAL_ACP_AVERAGING_TYPE_MINIMUM (4) | The lowest 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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_ACPCfgSweepTime (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 sweepTimeAuto, float64 sweepTimeInterval);
Configures the sweep time.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
sweepTimeAuto | int32 | Specifies whether the measurement computes the sweep time. |
RFMXLTE_VAL_ACP_SWEEP_TIME_AUTO_FALSE (0) | The measurement uses the sweep time that you specify in the sweepTimeInterval parameter. |
---|---|
RFMXLTE_VAL_ACP_SWEEP_TIME_AUTO_TRUE (1) | The measurement uses a sweep time of 1 ms. |
sweepTimeInterval | float64 | Specifies the sweep time when you set the sweepTimeAuto parameter to RFMXLTE_VAL_ACP_SWEEP_TIME_AUTO_FALSE. This value is expressed in seconds. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_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 | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_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. |
RFMXLTE_VAL_ACP_NOISE_COMPENSATION_ENABLED_FALSE (0) | Disables compensation of the channel powers for the noise floor of the signal analyzer. |
---|---|
RFMXLTE_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 remeasured. supportedDevices: 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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_ACPCfgMeasurementMethod (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 measurementMethod);
Configures the method for performing the ACP measurement.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
measurementMethod | int32 | Specifies the method for performing the ACP measurement. |
RFMXLTE_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. |
---|---|
RFMXLTE_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. Supported Devices: PXIe-5665/5668R |
RFMXLTE_VAL_ACP_MEASUREMENT_METHOD_SEQUENTIAL_FFT (2) | The ACP measurement acquires I/Q samples specified by the RFMXLTE_ATTR_ACP_SWEEP_TIME_INTERVAL) attribute. These samples are divided into smaller chunks defined by the RFMXLTE_ATTR_ACP_SEQUENTIAL_FFT_SIZE) attribute, and 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 the acquisition are not used. If the total acquired samples is not an integer multiple of the FFT size, the remaining samples at the end of the acquisition are not used. Use this method to optimize for speed. The accuracy of results may be reduced when using this measurement method. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_ACPCfgConfigurableNumberOfOffsetsEnabled (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 configurableNumberOfOffsetsEnabled);
Configures whether the number of offsets will be computed by the measurement or configured by the user.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
configurableNumberOfOffsetsEnabled | int32 | Specifies whether the number of offsets is computed by measurement or configured by you. When the carrier bandwidth is 200 kHz or the RFMXLTE_ATTR_LINK_DIRECTION) is RFMXLTE_VAL_LINK_DIRECTION_DOWNLINK, the default value is false. Incase of downlink, this attribute is applicable only for number of EUTRA offsets. For the number of UTRA offsets, only 3GPP specification defined values are supported. |
RFMXLTE_VAL_ACP_CONFIGURABLE_NUMBER_OF_OFFSETS_ENABLED_FALSE (0) | Measurement will set the number of offsets. |
---|---|
RFMXLTE_VAL_ACP_CONFIGURABLE_NUMBER_OF_OFFSETS_ENABLED_TRUE (1) | Measurement will use the user configured value for number of offsets. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_ACPCfgUTRAAndEUTRAOffsets (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 numberOfUTRAOffsets, int32 numberOfEUTRAOffsets);
Configures the number of universal terrestrial radio access (UTRA) and evolved universal terrestrial radio access (E-UTRA) adjacent channels of the subblock. This function is valid only for uplink single carrier, and contiguous carrier aggregation. In case of uplink non-contiguous multi-carrier and downlink, the number of UTRA/EUTRA offsets are determined from the 3GPP specification. Use "subblock<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the subblock number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0" "signal::sig1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
numberOfUTRAOffsets | int32 | Specifies the number of UTRA adjacent channel offsets to be configured at offset positions as defined in the 3GPP specification. |
numberOfEUTRAOffsets | int32 | Specifies the number of E-UTRA adjacent channel offsets to be configured at offset positions as defined in the 3GPP specification. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_ACPCfgNumberOfUTRAOffsets (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 numberOfUTRAOffsets);
Configures the number of universal terrestrial radio access (UTRA) adjacent channels of the subblock, when you set the ACP Configurable Number of Offset Enabled attribute to true. Use "subblock<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the subblock number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0" "signal::sig1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
numberOfUTRAOffsets | int32 | Specifies the number of UTRA adjacent channel offsets to be configured at offset positions, when you set the ACP Configurable Number of Offset Enabled attribute to true. In case of downlink, only 3GPP specification defined values are supported. In case of non-contiguous carrier aggregation, the configured value will be used only for the outer offsets and the offset channels in the gap region are defined as per the 3GPP specification. Offset power reference for the outer UTRA offsets are set according to the value of RFMXLTE_ATTR_ACP_EUTRA_OFFSET_DEFINITION) attribute. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_ACPCfgNumberOfEUTRAOffsets (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 numberOfEUTRAOffsets);
Configures the number of evolved universal terrestrial radio access adjacent channels of the subblock, when you set the ACP Configurable Number of Offset Enabled attribute to true. Use "subblock<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the subblock number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0" "signal::sig1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
numberOfEUTRAOffsets | int32 | Specifies the number of E-UTRA adjacent channel offsets to be configured at offset positions, when you set the ACP Configurable Number of Offset Enabled attribute to true. In case of non-contiguous carrier aggregation, the configured value will be used only for the outer offsets and the offset channels in the gap region are defined as per the 3GPP specification. Offset integration bandwidth and offset power reference for the outer E-UTRA offsets are set according to the value of RFMXLTE_ATTR_ACP_EUTRA_OFFSET_DEFINITION) attribute. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_ACPCfgNumberOfGSMOffsets (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 numberOfGSMOffsets);
Configures the number of GSM adjacent channels of the subblock, when you set the ACP Configurable Number of Offset Enabled attribute to true. Use "subblock<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the subblock number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0" "signal::sig1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
numberOfGSMOffsets | int32 | Specifies the number of GSM adjacent channel offsets to be configured when the channel bandwidth is 200 kHz (NB-IOT), when you set the ACP Configurable Number of Offset Enabled attribute to true. The frequency offset from the center of NB-IOT carrier to the center of the first offset is 300 kHz as defined in the 3GPP specification. The center of every other offset is placed at 200 kHz from the previous offset's center. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_ACPCfgRBWFilter (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 RBWAuto, float64 RBW, int32 RBWFilterType);
Configures the RBW filter.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
RBWAuto | int32 | Specifies whether the measurement computes the RBW. |
RFMXLTE_VAL_ACP_RBW_FILTER_AUTO_BANDWIDTH_FALSE (0) | The measurement uses the RBW that you specify in the RBW parameter. |
---|---|
RFMXLTE_VAL_ACP_RBW_FILTER_AUTO_BANDWIDTH_TRUE (1) | The measurement computes the RBW. |
RBW | float64 | Specifies the bandwidth of the RBW filter used to sweep the acquired signal, when you set the RBWAuto parameter to RFMXLTE_VAL_ACP_RBW_FILTER_AUTO_BANDWIDTH_FALSE. This value is expressed in Hz. |
RBWFilterType | int32 | Specifies the shape of the digital RBW filter. |
RFMXLTE_VAL_ACP_RBW_FILTER_TYPE_FFT_BASED (0) | No RBW filtering is performed. |
---|---|
RFMXLTE_VAL_ACP_RBW_FILTER_TYPE_GAUSSIAN (1) | An RBW filter with a Gaussian response is applied. |
RFMXLTE_VAL_ACP_RBW_FILTER_TYPE_FLAT (2) | An RBW filter with a flat 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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_ACPCfgPowerUnits (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 powerUnits);
Configures the units for absolute power.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
averagingEnabled | int32 | Specifies the units for absolute power. |
RFMXLTE_VAL_ACP_POWER_UNITS_DBM (0) | The absolute powers are reported in dBm. |
---|---|
RFMXLTE_VAL_ACP_POWER_UNITS_DBM_BY_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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_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 | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "" "signal::sig1" You can use the RFmxLTE_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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_BuildSubblockString (char selectorString[], int32 subblockNumber, int32 selectorStringOutLength, char selectorStringOut[]);
Creates the subblock string to use as the selector string with the subblock configuration or fetch attributes and functions.
Input | ||
---|---|---|
Name | Type | Description |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the result name. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "signal::sig1" "result::r1" "signal::sig1/result::r1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
subblockNumber | int32 | Specifies the number of subblocks that are configured in the intra-band noncontiguous carrier aggregation. Set this parameter to 1, which is the default, for single carrier and intra-band contiguous carrier aggregation. |
selectorStringOutLength | int32 | Specifies the length of the string that is returned by the selectorStringOut parameter. To get the minimum buffer size required to build the selector string, set the selectorStringOutLength parameter to 0. |
Output | ||
Name | Type | Description |
selectorStringOut | char[] | Returns the selector string created by this function. |
Name | Type | Description |
---|---|---|
statusOrRequiredSize | 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. When the statusOrRequiredSize return value returns the buffer size, the status code is not returned. To obtain a text description of the status code and additional information about the error condition, call the RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CHPCfgAveraging (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 averagingEnabled, int32 averagingCount, int32 averagingType);
Configures averaging for the CHP measurement.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
averagingEnabled | int32 | Specifies whether to enable averaging for the measurement. |
RFMXLTE_VAL_CHP_AVERAGING_ENABLED_FALSE (0) | The measurement is performed on a single acquisition. |
---|---|
RFMXLTE_VAL_CHP_AVERAGING_ENABLED_TRUE (1) | The measurement is averaged over multiple acquisitions. The number of acquisitions is obtained by the averagingCount parameter. |
averagingCount | int32 | Specifies the number of acquisitions used for averaging when you set the averagingEnabled parameter to RFMXLTE_VAL_CHP_AVERAGING_ENABLED_TRUE. |
averagingType | int32 | Specifies the averaging type for averaging multiple spectrum acquisitions. The averaged spectrum is used for the measurement. |
RFMXLTE_VAL_CHP_AVERAGING_TYPE_RMS (0) | The power spectrum is linearly averaged. RMS averaging reduces signal fluctuations but not the noise floor. |
---|---|
RFMXLTE_VAL_CHP_AVERAGING_TYPE_LOG (1) | The power spectrum is averaged in a logarithmic scale. |
RFMXLTE_VAL_CHP_AVERAGING_TYPE_SCALAR (2) | The square root of the power spectrum is averaged. |
RFMXLTE_VAL_CHP_AVERAGING_TYPE_MAXIMUM (3) | The peak power in the spectrum at each frequency bin is retained from one acquisition to the next. |
RFMXLTE_VAL_CHP_AVERAGING_TYPE_MINIMUM (4) | The lowest 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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CHPCfgSweepTime (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 sweepTimeAuto, float64 sweepTimeInterval);
Configures the sweep time.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
sweepTimeAuto | int32 | Specifies whether the measurement computes the sweep time. |
RFMXLTE_VAL_CHP_SWEEP_TIME_AUTO_FALSE (0) | The measurement uses the sweep time that you specify in the sweepTimeInterval parameter. |
---|---|
RFMXLTE_VAL_CHP_SWEEP_TIME_AUTO_TRUE (1) | The measurement uses a sweep time of 1 ms. |
sweepTimeInterval | float64 | Specifies the sweep time when you set the sweepTimeAuto parameter to RFMXLTE_VAL_CHP_SWEEP_TIME_AUTO_FALSE. This value is expressed in seconds. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CHPCfgIntegrationBandwidthType (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 integrationBandwidthType);
Configures the type of integration bandwidth (IBW), which selects one of the frequency ranges over which the CHP is measured. Refer to the LTE Channel Power (CHP)) topic for more information.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
integrationBandwidthType | int32 | Specifies the integration bandwidth (IBW) type used to measure the power of the acquired signal. Integration bandwidth is the frequency interval over which the power in each frequency bin is added to measure the total power in that interval. |
RFMXLTE_VAL_CHP_INTEGRATION_BANDWIDTH_TYPE_SIGNAL_BANDWIDTH (0) | The IBW excludes the guard bands at the edges of the carrier or subblock from the power calculation. |
---|---|
RFMXLTE_VAL_CHP_INTEGRATION_BANDWIDTH_TYPE_CHANNEL_BANDWIDTH (1) | The IBW includes the guard bands at the edges of the carrier or subblock from the power calculation. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CHPCfgRBWFilter (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 RBWAuto, float64 RBW, int32 RBWFilterType);
Configures the RBW filter.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
RBWAuto | int32 | Specifies whether the measurement computes the RBW. |
RFMXLTE_VAL_CHP_RBW_FILTER_AUTO_BANDWIDTH_FALSE (0) | The measurement uses the RBW that you specify in the RBW parameter. |
---|---|
RFMXLTE_VAL_CHP_RBW_FILTER_AUTO_BANDWIDTH_TRUE (1) | The measurement computes the RBW. |
RBW | float64 | Specifies the bandwidth of the resolution bandwidth (RBW) filter, used to sweep the acquired signal, when you set the RBWAuto parameter to RFMXLTE_VAL_CHP_RBW_FILTER_AUTO_BANDWIDTH_FALSE. This value is expressed in Hz. |
RBWFilterType | int32 | Specifies the shape of the digital RBW filter. |
RFMXLTE_VAL_CHP_RBW_FILTER_TYPE_FFT_BASED (0) | No RBW filtering is performed. |
---|---|
RFMXLTE_VAL_CHP_RBW_FILTER_TYPE_GAUSSIAN (1) | An RBW filter with a Gaussian response is applied. |
RFMXLTE_VAL_CHP_RBW_FILTER_TYPE_FLAT (2) | An RBW filter with a flat 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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_CHPValidateNoiseCalibrationData (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 | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "" "signal::sig1" You can use the RFmxLTE_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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_OBWCfgAveraging (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 averagingEnabled, int32 averagingCount, int32 averagingType);
Configures averaging for the OBW measurement.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
averagingEnabled | int32 | Specifies whether to enable averaging for the measurement. |
RFMXLTE_VAL_OBW_AVERAGING_ENABLED_FALSE (0) | The measurement is performed on a single acquisition. |
---|---|
RFMXLTE_VAL_OBW_AVERAGING_ENABLED_TRUE (1) | The measurement is averaged over multiple acquisitions. The number of acquisitions is obtained by the averagingCount parameter. |
averagingCount | int32 | Specifies the number of acquisitions used for averaging when you set the averagingEnabled parameter to RFMXLTE_VAL_OBW_AVERAGING_ENABLED_TRUE. |
averagingType | int32 | Specifies the averaging type for averaging multiple spectrum acquisitions. The averaged spectrum is used for the measurement. |
RFMXLTE_VAL_OBW_AVERAGING_TYPE_RMS (0) | The power spectrum is linearly averaged. RMS averaging reduces signal fluctuations but not the noise floor. |
---|---|
RFMXLTE_VAL_OBW_AVERAGING_TYPE_LOG (1) | The power spectrum is averaged in a logarithmic scale. |
RFMXLTE_VAL_OBW_AVERAGING_TYPE_SCALAR (2) | The square root of the power spectrum is averaged. |
RFMXLTE_VAL_OBW_AVERAGING_TYPE_MAXIMUM (3) | The peak power in the spectrum at each frequency bin is retained from one acquisition to the next. |
RFMXLTE_VAL_OBW_AVERAGING_TYPE_MINIMUM (4) | The lowest 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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_OBWCfgSweepTime (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 sweepTimeAuto, float64 sweepTimeInterval);
Configures the sweep time.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
sweepTimeAuto | int32 | Specifies whether the measurement computes the sweep time. |
RFMXLTE_VAL_OBW_SWEEP_TIME_AUTO_FALSE (0) | The measurement uses the sweep time that you specify in the sweepTimeInterval parameter. |
---|---|
RFMXLTE_VAL_OBW_SWEEP_TIME_AUTO_TRUE (1) | The measurement uses a sweep time of 1 ms. |
sweepTimeInterval | float64 | Specifies the sweep time when you set the sweepTimeAuto parameter to RFMXLTE_VAL_OBW_SWEEP_TIME_AUTO_FALSE. This value is expressed in seconds. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_OBWCfgRBWFilter (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 RBWAuto, float64 RBW, int32 RBWFilterType);
Configures the RBW filter.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
RBWAuto | int32 | Specifies whether the measurement computes the RBW. |
RFMXLTE_VAL_OBW_RBW_FILTER_AUTO_BANDWIDTH_FALSE (0) | The measurement uses the RBW that you specify in the RBW parameter. |
---|---|
RFMXLTE_VAL_OBW_RBW_FILTER_AUTO_BANDWIDTH_TRUE (1) | The measurement computes the RBW. |
RBW | float64 | Specifies the bandwidth of the resolution bandwidth (RBW) filter, used to sweep the acquired signal, when you set the RBWAuto parameter to RFMXLTE_VAL_OBW_RBW_FILTER_AUTO_BANDWIDTH_FALSE. This value is expressed in Hz. |
RBWFilterType | int32 | Specifies the shape of the digital RBW filter. |
RFMXLTE_VAL_OBW_RBW_FILTER_TYPE_FFT_BASED (0) | No RBW filtering is performed. |
---|---|
RFMXLTE_VAL_OBW_RBW_FILTER_TYPE_GAUSSIAN (1) | An RBW filter with a Gaussian response is applied. |
RFMXLTE_VAL_OBW_RBW_FILTER_TYPE_FLAT (2) | An RBW filter with a flat 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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgAveraging (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 averagingEnabled, int32 averagingCount, int32 averagingType);
Configures averaging for the SEM measurement.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
averagingEnabled | int32 | Specifies whether to enable averaging for the measurement. |
RFMXLTE_VAL_SEM_AVERAGING_ENABLED_FALSE (0) | The measurement is performed on a single acquisition. |
---|---|
RFMXLTE_VAL_SEM_AVERAGING_ENABLED_TRUE (1) | The measurement is averaged over multiple acquisitions. The number of acquisitions is obtained by the averagingCount parameter. |
averagingCount | int32 | Specifies the number of acquisitions used for averaging when you set the averagingEnabled parameter to RFMXLTE_VAL_SEM_AVERAGING_ENABLED_TRUE. |
averagingType | int32 | Specifies the averaging type for averaging multiple spectrum acquisitions. The averaged spectrum is used for the measurement. |
RFMXLTE_VAL_SEM_AVERAGING_TYPE_RMS (0) | The power spectrum is linearly averaged. RMS averaging reduces signal fluctuations but not the noise floor. |
---|---|
RFMXLTE_VAL_SEM_AVERAGING_TYPE_LOG (1) | The power spectrum is averaged in a logarithmic scale. |
RFMXLTE_VAL_SEM_AVERAGING_TYPE_SCALAR (2) | The square root of the power spectrum is averaged. |
RFMXLTE_VAL_SEM_AVERAGING_TYPE_MAXIMUM (3) | The peak power in the spectrum at each frequency bin is retained from one acquisition to the next. |
RFMXLTE_VAL_SEM_AVERAGING_TYPE_MINIMUM (4) | The lowest 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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgSweepTime (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 sweepTimeAuto, float64 sweepTimeInterval);
Configures the sweep time.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
sweepTimeAuto | int32 | Specifies whether the measurement computes the sweep time. |
RFMXLTE_VAL_SEM_SWEEP_TIME_AUTO_FALSE (0) | The measurement uses the sweep time that you specify in the sweepTimeInterval parameter. |
---|---|
RFMXLTE_VAL_SEM_SWEEP_TIME_AUTO_TRUE (1) | The measurement uses a sweep time of 1 ms. |
sweepTimeInterval | float64 | Specifies the sweep time when you set the sweepTimeAuto parameter to RFMXLTE_VAL_SEM_SWEEP_TIME_AUTO_FALSE. This value is expressed in seconds. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgUplinkMaskType (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 uplinkMaskType);
Configures the standard defined mask type that has to be used in the measurement for uplink.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
uplinkMaskType | int32 | Specifies the standard-defined spectrum emission mask used in the measurement for uplink. The following mask types are supported: general, NS_03orNS_11orNS_20orNS_21, NS_04, NS_06orNS_07, CA_NS_04, custom, generalCAClassB, CA_NC_NS_01, NS_27, and NS_35. Each mask type refers to a different Network Signalled (NS) value. CA_NS_04 and CA_NC_NS_01 refers to carrier aggregation case. You must set the mask type to CUSTOM to configure the custom offset masks. Refer to section 6.6.2.1 of the 3GPP 36.521 specification for more information about standard-defined mask types. |
RFMXLTE_VAL_SEM_UPLINK_MASK_TYPE_GENERAL_NS01 (0) | The measurement selects the offset frequencies and limits for the SEM as defined in Table 6.6.2.1.5-1, 6.6.2.1.5-2, 6.6.2.1A.5-1, and 6.6.2.1A.5-2 in section 6.6.2 of the 3GPP TS 36.521-1 specification. |
---|---|
RFMXLTE_VAL_SEM_UPLINK_MASK_TYPE_NS03_OR_NS11_OR_NS20_OR_NS21 (1) | The measurement selects the offset frequencies and limits for the SEM as defined in Table 6.6.2.2.5.1-1 and 6.6.2.2.5.1-2 in section 6.6.2 of the 3GPP TS 36.521-1 specification. |
RFMXLTE_VAL_SEM_UPLINK_MASK_TYPE_NS04 (2) | The measurement selects the offset frequencies and limits for the SEM in Table 6.6.2.2.3.2-3 in section 6.6.2 of the 3GPP TS 36.521-1 specification. When RFMXLTE_ATTR_COMPONENT_CARRIER_BANDWIDTH is 1.4 MHz or 3 MHz, the measurement selects the offset frequencies and limits for the SEM as defined in Table 6.6.2.2.5.2-1 in section 6.6.2 of the 3GPP TS 36.521-1 specification. |
RFMXLTE_VAL_SEM_UPLINK_MASK_TYPE_NS06_OR_NS07 (3) | The measurement selects the offset frequencies and limits for the SEM as defined in Table 6.6.2.2.5.3-1 and 6.6.2.2.5.3-2 in section 6.6.2 of the 3GPP TS 36.521-1 specification. |
RFMXLTE_VAL_SEM_UPLINK_MASK_TYPE_CANS04 (4) | The measurement selects the offset frequencies and limits for the SEM as defined in Table 6.6.2.2A.1.5.1-1 in section 6.6.2 of the 3GPP TS 36.521-1 specification. This mask applies only for aggregated carriers. |
RFMXLTE_VAL_SEM_UPLINK_MASK_TYPE_CUSTOM (5) | You need to configure the RFMXLTE_ATTR_SEM_NUMBER_OF_OFFSETS), RFMXLTE_ATTR_SEM_OFFSET_START_FREQUENCY), RFMXLTE_ATTR_SEM_OFFSET_STOP_FREQUENCY), RFMXLTE_ATTR_SEM_OFFSET_ABSOLUTE_LIMIT_START), RFMXLTE_ATTR_SEM_OFFSET_ABSOLUTE_LIMIT_STOP), RFMXLTE_ATTR_SEM_OFFSET_SIDEBAND), RFMXLTE_ATTR_SEM_OFFSET_RBW_FILTER_BANDWIDTH), RFMXLTE_ATTR_SEM_OFFSET_RBW_FILTER_TYPE), and RFMXLTE_ATTR_SEM_OFFSET_BANDWIDTH_INTEGRAL) attributes for each offset. |
RFMXLTE_VAL_SEM_UPLINK_MASK_TYPE_GENERAL_CACLASSB (6) | The measurement selects offset frequencies and limits for the SEM as defined in Table 6.6.2.1A.1.5-3 and 6.6.2.1A.1.5-4 in section 6.6.2 of 3GPP TS 36.521-1 specification. |
RFMXLTE_VAL_SEM_UPLINK_MASK_TYPE_CANCNS01 (7) | The measurement selects offset frequencies and limits for the SEM as defined in Table 6.6.2.2A.3.5-1 and 6.6.2.2A.3.5-2 in section 6.6.2 of 3GPP TS 36.521-1 specification. |
RFMXLTE_VAL_SEM_UPLINK_MASK_TYPE_NS27 (8) | The measurement selects offset frequencies and limits for the SEM as defined in Table 6.6.2.2.5.4-1 in section 6.6.2.2.5.4 of 3GPP TS 36.521-1 specification. |
RFMXLTE_VAL_SEM_UPLINK_MASK_TYPE_NS35 (9) | The measurement selects offset frequencies and limits for the SEM as defined in Table 6.6.2.2.5.5-1 in section 6.6.2.2.5.5 of 3GPP TS 36.521-1 specification. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgDownlinkMask (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 downlinkMaskType, float64 deltaFMaximum, float64 aggregatedMaximumPower);
Configures the downlinkMaskType, deltaF_max, and aggregatedMaximumOutputPower parameters for the SEM measurement in LTE downlink.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
downlinkMaskType | int32 | Specifies the standard-defined spectrum emission mask used in the measurement for the downlink. You must set the mask type to CUSTOM to configure the custom offsets and the masks. Refer to section 6.6.3 of the 3GPP 36.141 specification for more information about standard-defined mask types. |
RFMXLTE_VAL_SEM_DOWNLINK_MASK_TYPE_ENODEB_CATEGORY_BASED (0) | Specifies limits are applied based on eNodeB Category attribute. |
---|---|
RFMXLTE_VAL_SEM_DOWNLINK_MASK_TYPE_BAND46 (1) | Specifies that limits are applied based on Band 46 test requirements. |
RFMXLTE_VAL_SEM_DOWNLINK_MASK_TYPE_CUSTOM (5) | You need to configure the RFMXLTE_ATTR_SEM_NUMBER_OF_OFFSETS), RFMXLTE_ATTR_SEM_OFFSET_START_FREQUENCY), RFMXLTE_ATTR_SEM_OFFSET_STOP_FREQUENCY), RFMXLTE_ATTR_SEM_OFFSET_ABSOLUTE_LIMIT_START), RFMXLTE_ATTR_SEM_OFFSET_ABSOLUTE_LIMIT_STOP), SEM Offset Rel Limit Start, RFMXLTE_ATTR_SEM_OFFSET_RELATIVE_LIMIT_STOP), RFMXLTE_ATTR_SEM_OFFSET_SIDEBAND), RFMXLTE_ATTR_SEM_OFFSET_RBW_FILTER_BANDWIDTH), RFMXLTE_ATTR_SEM_OFFSET_RBW_FILTER_TYPE), and RFMXLTE_ATTR_SEM_OFFSET_BANDWIDTH_INTEGRAL) attributes for each offset. |
deltaFMaximum | float64 | Specifies the stop frequency for the last offset segment to be used in the measurement. This value is expressed in Hz. |
aggregatedMaximumPower | float64 | Specifies the aggregated maximum output power of all the transmit antenna connectors. This value is expressed in dBm. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgComponentCarrierMaximumOutputPower (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 componentCarrierMaximumOutputPower);
Configures the maximum output power of the component carrier. Use "carrier<k>" or "subblock<n>/carrier<k>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number and carrier number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/carrier0" "signal::sig1/subblock0/carrier0" You can use the RFmxLTE_BuildCarrierString) function to build the selector string. |
componentCarrierMaximumOutputPower | float64 | Specifies the maximum output power per carrier, which is used only to choose the limit table for Medium Range Base Station. This value is expressed in dBm. Refer to the section 6.6.3 of the 3GPP 36.141 specification for more details. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgNumberOfOffsets (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 numberOfOffsets);
Configures the number of offset segments for the SEM measurement.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, result name, and subblock number. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "subblock0" "signal::sig1/subblock0" "result::r1/subblock0" "signal::sig1/result::r1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
numberOfOffsets | int32 | Specifies the number of SEM offset segments. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgOffsetFrequency (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 offsetStartFrequency, float64 offsetStopFrequency, int32 offsetSideband);
Configures the start and stop frequencies and the sideband of an offset segment. Use "offset<n>" or "subblock<n>/offset<n>" as the selector string to configure from this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number, and offset number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/offset0" "signal::sig1/subblock0/offset0" You can use the RFmxLTE_BuildOffsetString) function to build the selector string. |
offsetStartFrequency | float64 | Specifies the start frequency of an offset segment relative to the carrier channel bandwidth edge (single-carrier) or the subblock aggregated channel bandwidth edge (multi-carrier). This value is expressed in Hz. |
offsetStopFrequency | float64 | Specifies the stop frequency of an offset segment relative to the carrier channel bandwidth edge (single-carrier) or the subblock aggregated channel bandwidth edge (multi-carrier). This value is expressed in Hz. |
offsetSideband | int32 | Specifies whether the offset segment is present on one side, or on both sides of the carrier. |
RFMXLTE_VAL_SEM_OFFSET_SIDEBAND_NEGATIVE (0) | Configures a lower offset segment to the left of the leftmost carrier. |
---|---|
RFMXLTE_VAL_SEM_OFFSET_SIDEBAND_POSITIVE (1) | Configures an upper offset segment to the right of the rightmost carrier. |
RFMXLTE_VAL_SEM_OFFSET_SIDEBAND_BOTH (2) | Configures both the negative and the positive offset segments. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgOffsetBandwidthIntegral (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 offsetBandwidthIntegral);
Configures the bandwidth integral of the offset segments. Use "offset<n>" or "subblock<n>/offset<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number, and offset number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/offset0" "signal::sig1/subblock0/offset0" You can use the RFmxLTE_BuildOffsetString) function to build the selector string. |
offsetBandwidthIntegral | int32 | Specifies the resolution of the spectrum to compare with the spectral mask limits as an integer multiple of the RBW. When you set this parameter to a value greater than 1, the measurement acquires the spectrum with a narrow resolution and then processes it digitally to get a wider resolution that is equal to the product of a bandwidth integral and a RBW. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgOffsetRBWFilter (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 offsetRBW, int32 offsetRBWFilterType);
Configures the offset RBW and the offset RBW filter type. Use "offset<n>" or "subblock<n>/offset<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number, and offset number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/offset0" "signal::sig1/subblock0/offset0" You can use the RFmxLTE_BuildOffsetString) function to build the selector string. |
offsetRBW | float64 | Specifies the bandwidth of an RBW filter used to sweep an acquired offset segment. This value is expressed in Hz. |
offsetRBWFilterType | int32 | Specifies the shape of the digital RBW filter. |
RFMXLTE_VAL_SEM_OFFSET_RBW_FILTER_TYPE_FFT_BASED (0) | No RBW filtering is performed. |
---|---|
RFMXLTE_VAL_SEM_OFFSET_RBW_FILTER_TYPE_GAUSSIAN (1) | The RBW filter has a Gaussian response. |
RFMXLTE_VAL_SEM_OFFSET_RBW_FILTER_TYPE_FLAT (2) | The RBW filter has a flat response. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgOffsetLimitFailMask (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 limitFailMask);
Configures the limit fail mask of the offset segments that specify the criteria to determine the measurement fail status. Use "offset<n>" or "subblock<n>/offset<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number, and offset number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/offset0" "signal::sig1/subblock0/offset0" You can use the RFmxLTE_BuildOffsetString) function to build the selector string. |
limitFailMask | int32 | Specifies the criteria to determine the measurement fail status. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgOffsetAbsoluteLimit (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 offsetAbsoluteLimitStart, float64 offsetAbsoluteLimitStop);
Configures the start and the stop limit of an offset segment. Use "offset<n>" or "subblock<n>/offset<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number, and offset number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/offset0" "signal::sig1/subblock0/offset0" You can use the RFmxLTE_BuildOffsetString) function to build the selector string. |
offsetAbsoluteLimitStart | float64 | Specifies the absolute power limit corresponding to the beginning of an offset segment. This value is expressed in dBm. |
offsetAbsoluteLimitStop | float64 | Specifies the absolute power limit corresponding to the end of an offset segment. This value is expressed in dBm. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgOffsetRelativeLimit (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 relativeLimitStart, float64 relativeLimitStop);
Configures the start and stop relative limit of the offset segment. Use "offset<n>" or "subblock<n>/offset<n>" as the selector string to read results from this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, subblock number, and offset number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0/offset0" "signal::sig1/subblock0/offset0" You can use the RFmxLTE_BuildOffsetString) function to build the selector string. |
relativeLimitStart | float64 | Specifies the relative power limit corresponding to the beginning of the offset segment. This value is expressed in dB. |
relativeLimitStop | float64 | Specifies the relative power limit corresponding to the end of the offset segment. This value is expressed in dB. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_BuildSubblockString (char selectorString[], int32 subblockNumber, int32 selectorStringOutLength, char selectorStringOut[]);
Creates the subblock string to use as the selector string with the subblock configuration or fetch attributes and functions.
Input | ||
---|---|---|
Name | Type | Description |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the result name. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "signal::sig1" "result::r1" "signal::sig1/result::r1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
subblockNumber | int32 | Specifies the number of subblocks that are configured in the intra-band noncontiguous carrier aggregation. Set this parameter to 1, which is the default, for single carrier and intra-band contiguous carrier aggregation. |
selectorStringOutLength | int32 | Specifies the length of the string that is returned by the selectorStringOut parameter. To get the minimum buffer size required to build the selector string, set the selectorStringOutLength parameter to 0. |
Output | ||
Name | Type | Description |
selectorStringOut | char[] | Returns the selector string created by this function. |
Name | Type | Description |
---|---|---|
statusOrRequiredSize | 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. When the statusOrRequiredSize return value returns the buffer size, the status code is not returned. To obtain a text description of the status code and additional information about the error condition, call the RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_BuildOffsetString (char selectorString[], int32 offsetNumber, int32 selectorStringOutLength, char selectorStringOut[]);
Creates the offset string to use as the selector string with SEM and ACP offset configuration or fetch attributes and functions.
Input | ||
---|---|---|
Name | Type | Description |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the result name. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "signal::sig1" "result::r1" "signal::sig1/result::r1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
offsetNumber | int32 | Specifies the offset number for building the selector string. |
selectorStringOutLength | int32 | Specifies the length of the string that is returned by the selectorStringOut parameter. To get the minimum buffer size required to build the selector string, set the selectorStringOutLength parameter to 0. |
Output | ||
Name | Type | Description |
selectorStringOut | char[] | Returns the selector string created by this function. |
Name | Type | Description |
---|---|---|
statusOrRequiredSize | 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. When the statusOrRequiredSize return value returns the buffer size, the status code is not returned. To obtain a text description of the status code and additional information about the error condition, call the RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgComponentCarrierMaximumOutputPowerArray (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 componentCarrierMaximumOutputPower[], int32 numberOfElements);
Configures the array of maximum output power of the component carrier. Use "subblock<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the subblock number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0" "signal::sig1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
componentCarrierMaximumOutputPower | float64[] | Specifies the array of maximum output power per carrier, which is used only to choose the limit table for Medium Range Base Station. This value is expressed in dBm. Refer to the section 6.6.3 of the 3GPP 36.141 specification for more details. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgOffsetFrequencyArray (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 offsetStartFrequency[], float64 offsetStopFrequency[], int32 offsetSideband[], int32 numberOfElements);
Configures the arrays of the start and stop frequencies and the sideband of an offset segment. Use "subblock<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, result name, and subblock number. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "subblock0" "signal::sig1/subblock0" "result::r1/subblock0" "signal::sig1/result::r1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
offsetStartFrequency | float64[] | Specifies the array of the start frequency values of the offset segment relative to the carrier channel bandwidth edge (single-carrier) or the subblock aggregated channel bandwidth edge (multi-carrier). This value is expressed in Hz. |
offsetStopFrequency | float64[] | Specifies the array of the stop frequency values of the offset segment relative to the carrier channel bandwidth edge (single-carrier) or the subblock aggregated channel bandwidth edge (multi-carrier). This value is expressed in Hz. |
offsetSideband | int32[] | Specifies whether the offset segment is present on one side, or on both sides of the carrier for each offset. |
RFMXLTE_VAL_SEM_OFFSET_SIDEBAND_NEGATIVE (0) | Configures a lower offset segment to the left of the leftmost carrier. |
---|---|
RFMXLTE_VAL_SEM_OFFSET_SIDEBAND_POSITIVE (1) | Configures an upper offset segment to the right of the rightmost carrier. |
RFMXLTE_VAL_SEM_OFFSET_SIDEBAND_BOTH (2) | Configures both the negative and the positive offset segments. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgOffsetBandwidthIntegralArray (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 offsetBandwidthIntegral[], int32 numberOfElements);
Configures the array of the bandwidth integral of the offset segments. Use "subblock<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, result name, and subblock number. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "subblock0" "signal::sig1/subblock0" "result::r1/subblock0" "signal::sig1/result::r1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
offsetBandwidthIntegral | int32[] | Specifies the array of the resolution values of the spectrum to compare with the spectral mask limits as an integer multiple of the RBW. When you set this parameter to a value greater than 1, the measurement acquires the spectrum with a narrow resolution and then processes it digitally to get a wider resolution that is equal to the product of a bandwidth integral and an RBW. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgOffsetRBWFilterArray (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 offsetRBW[], int32 offsetRBWFilterType[], int32 numberOfElements);
Configures the offset RBW and the offset RBW filter type arrays. Use "subblock<n>" as the selector string to configure from this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, result name, and subblock number. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "subblock0" "signal::sig1/subblock0" "result::r1/subblock0" "signal::sig1/result::r1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
offsetRBW | float64[] | Specifies the array of the RBW filter bandwidth values used to sweep the acquired offset segment, when you set the SEM Offset RBW Auto attribute to False. This value is expressed in Hz. |
offsetRBWFilterType | int32[] | Specifies the array of the shape of a digital RBW filter. |
RFMXLTE_VAL_SEM_OFFSET_RBW_FILTER_TYPE_FFT_BASED (0) | No RBW filtering is performed. |
---|---|
RFMXLTE_VAL_SEM_OFFSET_RBW_FILTER_TYPE_GAUSSIAN (1) | The RBW filter has a Gaussian response. |
RFMXLTE_VAL_SEM_OFFSET_RBW_FILTER_TYPE_FLAT (2) | The RBW filter has a flat response. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgOffsetLimitFailMaskArray (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 limitFailMask[], int32 numberOfElements);
Configures the array of limit fail mask of the offset segments that specifies the criteria to determine the measurement fail status. Use "subblock<n>" as the selector string to read results from this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, result name, and subblock number. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "subblock0" "signal::sig1/subblock0" "result::r1/subblock0" "signal::sig1/result::r1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
limitFailMask | int32[] | Specifies the array of criterion to determine the measurement fail status. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgOffsetAbsoluteLimitArray (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 offsetAbsoluteLimitStart[], float64 offsetAbsoluteLimitStop[], int32 numberOfElements);
Configures the array of the start limit and the stop limit of the offset segments. Use "subblock<n>" as the selector string to configure this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name and the subblock number. If you do not specify the signal name, the default signal instance is used. Example: "subblock0" "signal::sig1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
offsetAbsoluteLimitStart | float64[] | Specifies the array of the absolute power limits corresponding to the beginning of an offset segment. This value is expressed in dBm. |
offsetAbsoluteLimitStop | float64[] | Specifies the array of the absolute power limits corresponding to the end of an offset segment. This value is expressed in dBm. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SEMCfgOffsetRelativeLimitArray (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 relativeLimitStart[], float64 relativeLimitStop[], int32 numberOfElements);
Configures the array of start and stop relative limits of the offset segments. Use "subblock<n>" as the selector string to read results from this function.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name, result name, and subblock number. If you do not specify the signal name, the default signal instance is used. If you do not specify the result name, the default result instance is used. Example: "subblock0" "signal::sig1/subblock0" "result::r1/subblock0" "signal::sig1/result::r1/subblock0" You can use the RFmxLTE_BuildSubblockString) function to build the selector string. |
relativeLimitStart | float64[] | Specifies the array of relative power limits corresponding to the beginning of the offset segment. This value is expressed in dB. |
relativeLimitStop | float64[] | Specifies the array of relative power limits corresponding to the end of the offset segment. This value is expressed in dB. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_PVTCfgAveraging (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 averagingEnabled, int32 averagingCount, int32 averagingType);
Configures averaging for the power versus time (PVT) measurement.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
averagingEnabled | int32 | Specifies whether to enable averaging for the measurement. |
averagingCount | int32 | Specifies the number of acquisitions used for averaging when you set the averagingEnabled parameter to true. |
averagingType | int32 | Specifies the averaging type for averaging multiple spectrum acquisitions. The averaged spectrum is used for the 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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_PVTCfgMeasurementMethod (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 measurementMethod);
Configures the method for performing the power versus time (PVT) measurement. Refer to the LTE PVT (Power Vs Time) Measurement topic for more information about measurement method.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
measurementMethod | int32 | Specifies the method for performing the PVT measurement. Supported Devices: PXIe-5644/5645/5646/5840/5841. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_PVTCfgOFFPowerExclusionPeriods (niRFmxInstrHandle instrumentHandle, char selectorString[], float64 OFFPowerExclusionBefore, float64 OFFPowerExclusionAfter);
Configures the OFF power exclusion periods for the power versus time (PVT) measurement. Refer to the LTE PVT (Power Vs Time) Measurement topic for more information about OFF power exclusion periods.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
OFFPowerExclusionBefore | float64 | Specifies the time excluded from the OFF region before the burst. This value is expressed in seconds. |
OFFPowerExclusionAfter | float64 | Specifies the time excluded from the OFF region after the burst. This value is expressed in seconds. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SlotPhaseCfgSynchronizationModeAndInterval (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 synchronizationMode, int32 measurementOffset, int32 measurementLength);
Configures the synchronizationMode, measurementOffset, and measurementLength parameters of SlotPhase measurement.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
synchronizationMode | int32 | Specifies whether the measurement is performed from the frame or the slot boundary. |
RFMXLTE_VAL_SLOTPHASE_SYNCHRONIZATION_MODE_FRAME (0) | The frame boundary in the acquired signal is detected, and the measurement is performed over the number of slots specified by the measurementLength parameter, starting at the offset from the boundary specified by the measurementOffset parameter. When you set the RFMXLTE_ATTR_TRIGGER_TYPE) attribute to RFMXLTE_VAL_TRIGGER_TYPE_DIGITAL_EDGE, the measurement expects a trigger at the frame boundary. |
---|---|
RFMXLTE_VAL_SLOTPHASE_SYNCHRONIZATION_MODE_SLOT (1) | The slot boundary the acquired signal is detected, and the measurement is performed over the number of slots specified by the measurementLength parameter, starting at the offset from the boundary specified by the measurementOffset parameter. When you set the RFMXLTE_ATTR_TRIGGER_TYPE attribute to RFMXLTE_VAL_TRIGGER_TYPE_DIGITAL_EDGE, the measurement expects a trigger at any slot boundary. |
measurementOffset | int32 | Specifies the measurement offset to skip from the synchronization boundary. The synchronization boundary is specified by the Synchronization Mode parameter. This value is expressed in slots. |
measurementLength | int32 | Specifies the number of slots to be measured. This value is expressed in slots. |
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 RFmxLTE_GetError) function. The general meaning of the status code is as follows: |
Value | Meaning |
---|---|
0 | Success |
Positive Values | Warnings |
Negative Values | Errors |
int32 __stdcall RFmxLTE_SlotPowerCfgMeasurementInterval (niRFmxInstrHandle instrumentHandle, char selectorString[], int32 measurementOffset, int32 measurementLength);
Configures the measurementOffset and measurementLength parameters of SlotPower measurement.
Input | ||
---|---|---|
Name | Type | Description |
instrumentHandle | niRFmxInstrHandle | Specifies the instrument session. The RFmx obtains this parameter from the RFmxLTE_Initialize) function. |
selectorString | char[] | Specifies a selector string) comprising of the signal name. If you do not specify the signal name, the default signal instance is used. Example: "signal::sig1" You can use the RFmxLTE_BuildSignalString) function to build the selector string. |
measurementOffset | int32 | Specifies the measurement offset to skip from the frame boundary or the marker (external trigger) location. This value is expressed in subframes. |
measurementLength | int32 | Specifies the number of subframes to be measured. This value is expressed in subframes. |
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 RFmxLTE_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