-
Notifications
You must be signed in to change notification settings - Fork 50
NI RFmx LTE General Attributes
Dane Stull edited this page Feb 28, 2022
·
2 revisions
- RFMXLTE_ATTR_SELECTED_PORTS
- RFMXLTE_ATTR_CENTER_FREQUENCY
- RFMXLTE_ATTR_REFERENCE_LEVEL
- RFMXLTE_ATTR_EXTERNAL_ATTENUATION
- RFMXLTE_ATTR_REFERENCE_LEVEL_HEADROOM
- RFMXLTE_ATTR_LINK_DIRECTION
- RFMXLTE_ATTR_DUPLEX_SCHEME
- RFMXLTE_ATTR_UPLINK_DOWNLINK_CONFIGURATION
- RFMXLTE_ATTR_ENODEB_CATEGORY
- RFMXLTE_ATTR_SPECIAL_SUBFRAME_CONFIGURATION
- RFMXLTE_ATTR_NUMBER_OF_DUT_ANTENNAS
- RFMXLTE_ATTR_TRANSMIT_ANTENNA_TO_ANALYZE
- RFMXLTE_ATTR_NUMBER_OF_SUBBLOCKS
- RFMXLTE_ATTR_SUBBLOCK_FREQUENCY_DEFINITION
- RFMXLTE_ATTR_BAND
- RFMXLTE_ATTR_COMPONENT_CARRIER_SPACING_TYPE
- RFMXLTE_ATTR_COMPONENT_CARRIER_AT_CENTER_FREQUENCY
- RFMXLTE_ATTR_RESULT_FETCH_TIMEOUT
Data Type: | char [] |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeString RFmxLTE_GetAttributeString |
Description: | Specifies the instrument port to be configured to acquire a signal. Use RFmxInstr_GetAvailablePorts function to get the valid port names. You do not need to use a selector string to configure or read this attribute for the default signal instance. Refer to the Selector Strings topic for information about the string syntax for named signals. Valid values: PXIe-5830: if0, if1 Other devices: (empty string) PXIe-5831/5832: if0, if1, rf<0-1>/port, where 0-1 indicates one (0) or two (1) mmRH-5582 connections and x is the port number on the mmRH-5582 front panel Default values: PXIe-5830: if1 Other devices: (empty string) Get Function: RFmxLTE_GetSelectedPorts Set Function: RFmxLTE_SetSelectedPorts |
Data Type: | float64 |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeF64 RFmxLTE_GetAttributeF64 |
Description: | For a single carrier, this attribute specifies the center frequency of the acquired RF signal. For intra-band carrier aggregation, this attribute specifies the reference frequency of the subblock. 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. This value is expressed in Hz. Use 'subblock(n)' as the selector string to configure or read this attribute. Refer to the Center Frequency topic for more information. The default value of this attribute is hardware dependent. Get Function: RFmxLTE_GetCenterFrequency Set Function: RFmxLTE_SetCenterFrequency |
Data Type: | float64 |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeF64 RFmxLTE_GetAttributeF64 |
Description: | Specifies the reference level which represents the maximum expected power of the RF input signal. This value is configured in dBm for RF devices and as Vpk-pk for baseband devices. You do not need to use a selector string to configure or read this attribute for the default signal instance. Refer to the Selector Strings topic for information about the string syntax for named signals. The default value of this attribute is hardware dependent. Get Function: RFmxLTE_GetReferenceLevel Set Function: RFmxLTE_SetReferenceLevel |
Data Type: | float64 |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeF64 RFmxLTE_GetAttributeF64 |
Description: | Specifies the attenuation of a switch or cable connected to the RF IN connector of the signal analyzer. This value is expressed in dB. Refer to the RF Attenuation and Signal Levels topic for your device in the NI RF Vector Signal Analyzers Help for more information about attenuation. You do not need to use a selector string to configure or read this attribute for the default signal instance. Refer to the Selector Strings topic for information about the string syntax for named signals. The default value is 0. Get Function: RFmxLTE_GetExternalAttenuation Set Function: RFmxLTE_SetExternalAttenuation |
Data Type: | float64 |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeF64 RFmxLTE_GetAttributeF64 |
Description: | Specifies the margin RFmx adds to the RFMXLTE_ATTR_REFERENCE_LEVEL attribute. The margin avoids clipping and overflow warnings if the input signal exceeds the configured reference level. RFmx configures the input gain to avoid clipping and associated overflow warnings provided the instantaneous power of the input signal remains within the RFMXLTE_ATTR_REFERENCE_LEVEL plus the RFMXLTE_ATTR_REFERENCE_LEVEL_HEADROOM. If you know the input power of the signal precisely or previously included the margin in the RFMXLTE_ATTR_REFERENCE_LEVEL, you could improve the signal-to-noise ratio by reducing the RFMXLTE_ATTR_REFERENCE_LEVEL_HEADROOM. You do not need to use a selector string to configure or read this attribute for the default signal instance. Refer to the Selector Strings topic for information about the string syntax for named signals. Supported devices: PXIe-5668, PXIe-5830/5831/5832/5840/5841. Default values: PXIe-5668: 6 dB PXIe-5830/5831/5832/5841: 1 dB PXIe-5840: 0 dB Get Function: RFmxLTE_GetReferenceLevelHeadroom Set Function: RFmxLTE_SetReferenceLevelHeadroom |
Data Type: | int32 |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeI32 RFmxLTE_GetAttributeI32 |
Description: | Specifies the link direction of the received signal. You do not need to use a selector string to configure or read this attribute for the default signal instance. Refer to the Selector Strings topic for information about the string syntax for named signals. The default value is RFMXLTE_VAL_LINK_DIRECTION_UPLINK. Get Function: RFmxLTE_GetLinkDirection Set Function: RFmxLTE_SetLinkDirection |
Values: |
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 specifications to measure the received signal. |
Data Type: | int32 |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeI32 RFmxLTE_GetAttributeI32 |
Description: | Specifies the duplexing technique of the signal being measured. You do not need to use a selector string to configure or read this attribute for the default signal instance. Refer to the Selector Strings topic for information about the string syntax for named signals. The default value is RFMXLTE_VAL_DUPLEX_SCHEME_FDD. Get Function: RFmxLTE_GetDuplexScheme Set Function: RFmxLTE_SetDuplexScheme |
Values: |
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. |
Data Type: | int32 |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeI32 RFmxLTE_GetAttributeI32 |
Description: | Specifies the configuration of the LTE frame structure in the time division duplex (TDD) mode. Refer to table 4.2-2 of the 3GPP TS 36.211 specification to configure the LTE frame. You do not need to use a selector string to configure or read this attribute for the default signal instance. Refer to the Selector Strings topic for information about the string syntax for named signals. The default value is RFMXLTE_VAL_UPLINK_DOWNLINK_CONFIGURATION_0. Get Function: RFmxLTE_GetUplinkDownlinkConfiguration Set Function: RFmxLTE_SetUplinkDownlinkConfiguration |
Values: |
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. |
Data Type: | int32 |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeI32 RFmxLTE_GetAttributeI32 |
Description: | Specifies the downlink eNodeB (Base station) category. Refer to the 3GPP 36.141 specification for more details. You do not need to use a selector string to configure or read this attribute for the default signal instance. Refer to the Selector Strings topic for information about the string syntax for named signals. The default value is Wide Area Base Station - Category A. Get Function: RFmxLTE_GeteNodeBCategory Set Function: RFmxLTE_SeteNodeBCategory |
Values: |
RFMXLTE_VAL_ENODEB_WIDE_AREA_BASE_STATION_CATEGORY_A (0) | Specifies eNodeB is Wide Area Base Station - Category A. |
---|---|
RFMXLTE_VAL_ENODEB_WIDE_AREA_BASE_STATION_CATEGORY_B_OPTION1 (1) | Specifies eNodeB is Wide Area Base Station - Category B Option1. |
RFMXLTE_VAL_ENODEB_WIDE_AREA_BASE_STATION_CATEGORY_B_OPTION2 (2) | Specifies eNodeB is Wide Area Base Station - Category B Option2. |
RFMXLTE_VAL_ENODEB_LOCAL_AREA_BASE_STATION (3) | Specifies eNodeB is Local Area Base Station. |
RFMXLTE_VAL_ENODEB_HOME_BASE_STATION (4) | Specifies eNodeB is Home Base Station. |
RFMXLTE_VAL_ENODEB_MEDIUM_RANGE_BASE_STATION (5) | Specifies eNodeB is Medium Range Base Station. |
Data Type: | int32 |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeI32 RFmxLTE_GetAttributeI32 |
Description: | Specifies the special subframe configuration index. It defines the length of DwPTS, GP, and UpPTS for TDD transmission as defined in the section 4.2 of 3GPP 36.211 specification. You do not need to use a selector string to configure or read this attribute for the default signal instance. Refer to the Selector Strings topic for information about the string syntax for named signals. The default value is 0. Valid values are 0 to 9, inclusive. Get Function: RFmxLTE_GetSpecialSubframeConfiguration Set Function: RFmxLTE_SetSpecialSubframeConfiguration |
Data Type: | int32 |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeI32 RFmxLTE_GetAttributeI32 |
Description: | Specifies the number of physical antennas available at the DUT for transmission in a MIMO setup. You do not need to use a selector string to configure or read this attribute for the default signal instance. Refer to the Selector Strings topic for information about the string syntax for named signals. The default value is 1. Valid values are 1, 2, and 4. Get Function: RFmxLTE_GetNumberOfDUTAntennas Set Function: RFmxLTE_SetNumberOfDUTAntennas |
Data Type: | int32 |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeI32 RFmxLTE_GetAttributeI32 |
Description: | Specifies the physical antenna connected to the analyzer. You do not need to use a selector string to configure or read this attribute for the default signal instance. Refer to the Selector Strings topic for information about the string syntax for named signals. The default value is 0. Valid values are from 0 to N-1, where N is the number of DUT antennas. Get Function: RFmxLTE_GetTransmitAntennaToAnalyze Set Function: RFmxLTE_SetTransmitAntennaToAnalyze |
Data Type: | int32 |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeI32 RFmxLTE_GetAttributeI32 |
Description: | Specifies the number of subblocks that are configured in intra-band noncontiguous carrier aggregation. You do not need to use a selector string to configure or read this attribute for the default signal instance. Refer to the Selector Strings topic for information about the string syntax for named signals. The default value is 1. Set this attribute to 1 for single carrier and intra-band contiguous carrier aggregation. Get Function: RFmxLTE_GetNumberOfSubblocks Set Function: RFmxLTE_SetNumberOfSubblocks |
Data Type: | int32 |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeI32 RFmxLTE_GetAttributeI32 |
Description: | Specifies if the subblock center frequency definition is an absolute frequency or relative to the absolute frequency of the first subblock. This attribute is ignored for the first subblock and is considered to be absolute by the measurement. Refer to the Center Frequency topic for more information. Use 'subblock(n)' as the selector string to configure or read this attribute. The default value is RFMXLTE_VAL_SUBBLOCK_FREQUENCY_DEFINITION_RELATIVE. Get Function: RFmxLTE_GetSubblockFrequencyDefinition Set Function: RFmxLTE_SetSubblockFrequencyDefinition |
Values: |
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. |
Data Type: | int32 |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeI32 RFmxLTE_GetAttributeI32 |
Description: | Specifies the evolved universal terrestrial radio access (E-UTRA) operating frequency band of a subblock, as defined in section 5.2 of the 3GPP TS 36.521 specification. Use 'subblock(n)' as the selector string to configure or read this attribute. The default value is 1. Valid values are from 1 to 255, inclusive. Get Function: RFmxLTE_GetBand Set Function: RFmxLTE_SetBand |
Data Type: | int32 |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeI32 RFmxLTE_GetAttributeI32 |
Description: | Specifies the spacing between two adjacent component carriers within a subblock. Refer to the Channel Spacing and Carrier Frequency Offset Definition and Reference Frequency topics for more information about component carrier spacing. Use 'subblock(n)' as the selector string to configure or read this attribute. The default value is RFMXLTE_VAL_COMPONENT_CARRIER_SPACING_TYPE_NOMINAL. Get Function: RFmxLTE_GetComponentCarrierSpacingType Set Function: RFmxLTE_SetComponentCarrierSpacingType |
Values: |
RFMXLTE_VAL_COMPONENT_CARRIER_SPACING_TYPE_NOMINAL (0) | Calculates the frequency spacing between component carriers, as defined in section 5.4.1A in 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. |
Data Type: | int32 |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeI32 RFmxLTE_GetAttributeI32 |
Description: | Specifies the index of the component carrier having its center at the user-configured center frequency. RFmxLTE uses this attribute along with RFMXLTE_ATTR_COMPONENT_CARRIER_SPACING_TYPE attribute to calculate the value of the RFMXLTE_ATTR_COMPONENT_CARRIER_FREQUENCY. Refer to the Carrier Frequency Offset Definition and Reference Frequency topic for more information about component carrier frequency. Use 'subblock(n)' as the selector string to configure or read this attribute. Valid values are -1, 0, 1 ... n - 1, inclusive, where n is the number of component carriers in the subblock. The default value is -1. If the value is -1, the component carrier frequency values are calculated such that the center of aggregated carriers (subblock) lies at the Center Frequency. This attribute is ignored if you set the RFMXLTE_ATTR_COMPONENT_CARRIER_SPACING_TYPE attribute to User. Get Function: RFmxLTE_GetComponentCarrierAtCenterFrequency Set Function: RFmxLTE_SetComponentCarrierAtCenterFrequency |
Data Type: | float64 |
---|---|
Access: | read/write |
Functions: | RFmxLTE_SetAttributeF64 RFmxLTE_GetAttributeF64 |
Description: | Specifies the time to wait before results are available. This value is expressed in seconds. Set this value to a time longer than expected for fetching the measurement. A value of -1 specifies that the RFmx waits until the measurement is complete. You do not need to use a selector string to configure or read this attribute for the default signal instance. Refer to the Selector Strings topic for information about the string syntax for named signals. The default value is 10. Get Function: RFmxLTE_GetResultFetchTimeout Set Function: RFmxLTE_SetResultFetchTimeout |
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