| Info | Contains Python APIs for interacting with RFmx CDMA2K Product. |
|---|---|
| Author | National Instruments |
Table of Contents
About
The nirfmx-python repository generates Python bindings (Application Programming Interface) for interacting with the RFmx Products.
nirfmx-python follows Python Software Foundation support policy for different versions.
RFmx Instr Python API Status
| Item | Details |
|---|---|
| Driver Version Tested | 2026 Q4 |
| Supported Python Versions | Python 3.9+ (64-bit) |
| Documentation | RFmx Instr Docs |
RFmx CDMA2K Python API Status
| Item | Details |
|---|---|
| Driver Version Tested | 2026 Q4 |
| Supported Python Versions | Python 3.9+ (64-bit) |
| Documentation | RFmx CDMA2K Docs |
Documentation
You can find the latest API documentation for the nirfmx-python package on Read the Docs
Refer to the RFmx User Manual for an overview of RFmx, system requirements, troubleshooting, key concepts, etc.
Operating System Support
nirfmx-python supports Windows systems where the supported drivers are installed. Refer to NI Hardware and Operating System Compatibility for which versions of the driver support your hardware on a given operating system.
Installation
You can use pip to download nirfmxcdma2k and install it.
$ python -m pip install nirfmxcdma2k
To also install gRPC support for remote NI gRPC Device Server communication:
$ python -m pip install "nirfmxcdma2k[grpc]"
License
This project is licensed under the MIT License. While the source code is not publicly released, the license permits binary distribution with attribution.
Note: This Python driver depends on several third-party components that are subject to separate commercial licenses. Users are responsible for ensuring they have the appropriate rights and licenses to use those dependencies in their environments.
gRPC Features
For driver APIs that support it, passing a GrpcSessionOptions instance as a parameter to nirfmxcdma2k.Session.init() is subject to the NI General Purpose EULA.
SSL/TLS Support
The server supports both server-side TLS and mutual TLS. Security configuration is accomplished by setting the server_cert, server_key and root_cert values in the server's configuration file. The server expects the certificate files specified in the configuration file to exist in a certs folder that is located in the same directory as the configuration file being used by the server. For more detailed information on SSL/TLS support refer to the Server Security Support wiki page.
Support and Feedback
For support with Python API, hardware, the driver runtime or any other questions, please visit NI Community Forums.
RFmxCDMA2K Example
import nirfmxinstr
import nirfmxcdma2k
import numpy
instr_session = None
cdma2k = None
try:
# Create a new RFmx Session
instr_session = nirfmxinstr.Session(resource_name="RFSA", option_string="")
# Get CDMA2k signal
cdma2k = instr_session.get_cdma2k_signal_configuration()
# Configure RFmx Session
instr_session.configure_frequency_reference(selector_string="",
frequency_reference_source="OnboardClock", frequency_reference_frequency=10.0e6)
# Configure CDMA2k signal
cdma2k.configure_rf(selector_string="", center_frequency=833.49e6, reference_level=0.0,
external_attenuation=0.0)
cdma2k.configure_digital_edge_trigger(
selector_string="",
digital_edge_source="PFI0",
digital_edge=nirfmxcdma2k.DigitalEdgeTriggerEdge.RISING_EDGE,
trigger_delay=0.0,
enable_trigger=False,
)
# Select CHP Measurement
cdma2k.select_measurements(selector_string="",
measurements=nirfmxcdma2k.MeasurementTypes.CHP, enable_all_traces=True)
# Configure CHP Measurement
cdma2k.chp.configuration.configure_sweep_time(selector_string="",
sweep_time_auto=nirfmxcdma2k.ChpSweepTimeAuto.TRUE, sweep_time_interval=1.67e-3)
cdma2k.chp.configuration.configure_averaging(
selector_string="",
averaging_enabled=nirfmxcdma2k.ChpAveragingEnabled.FALSE,
averaging_count=10,
averaging_type=nirfmxcdma2k.ChpAveragingType.RMS,
)
cdma2k.initiate(selector_string="", result_name="")
# Retrieve Results
carrier_absolute_power, error_code = cdma2k.chp.results.fetch_carrier_absolute_power(
selector_string="", timeout=10.0
)
# The numpy arrays are passed in pre-allocated. If the pre allocated array size does not match the
# actual array size returned by the measurement, the array is automatically resized to fit the data,
# which may invalidate the previously created view. Passing an empty array (size 0) is fine;
# it will be resized as needed.
spectrum = numpy.empty(0, dtype=numpy.float32)
x0, dx, error_code = cdma2k.chp.results.fetch_spectrum(selector_string="", timeout=10.0,
spectrum=spectrum)
# Print Results
print(f"Carrier Absolute Power (dBm) : {carrier_absolute_power}")
except Exception as e:
print("ERROR: " + str(e))
finally:
# Close Session
if cdma2k is not None:
cdma2k.dispose()
cdma2k = None
if instr_session is not None:
instr_session.close()
instr_session = None
Numpy array size handling in RFmx APIs
The numpy arrays are passed in pre-allocated. If the pre allocated array size does not match the actual array size returned by the measurement, the array is automatically resized to fit the data, which may invalidate the previously created view. Passing an empty array (size 0) is fine; it will be resized as needed.
Metadata
Release files for nirfmxcdma2k 26.8.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nirfmxcdma2k-26.8.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / nirfmxcdma2k-26.8.0-py3-none-any.whl
| Download URL | nirfmxcdma2k-26.8.0-py3-none-any.whl |
|---|---|
| Size | 214.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9fdcde033df8051d09a3df66e043099103c87be2dd337f197982cf93b70838ef
|
|
BLAKE2b-256 checksum How to use checksums |
adb4cba122aeac0ca2e4f8e997cea11d26f3f310c28bd9e37a9318dc7cd1ea5b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.11
|
Security for nirfmxcdma2k 26.8.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.