Skip to content

RFmx 2026 Q3 Bug Fixes#1267

Open
RahulBenaka wants to merge 11 commits into
mainfrom
users/rnagaraj/rfmx_bug_fix
Open

RFmx 2026 Q3 Bug Fixes#1267
RahulBenaka wants to merge 11 commits into
mainfrom
users/rnagaraj/rfmx_bug_fix

Conversation

@RahulBenaka

@RahulBenaka RahulBenaka commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

What does this Pull Request accomplish?

Updates niRFmxInstr metadata and generated gRPC code to 26.5.0.
Updates niRFmxPulse metadata and generated gRPC code to 26.5.0.
Updates niRFmxVNA metadata and generated gRPC code to 26.5.0.
Updates niRFmxWLAN metadata and generated gRPC code to 26.5.0.
Updates README driver support entries for RFmx Pulse, RFmx VNA, and RFmx WLAN.

Fixes the WLAN CfgDigitalEdgeTriggerRequest parameter naming inconsistency by correcting digital_edge_source_raw to match the expected digital_edge_source naming.
Adds the missing RFmxInstr Split APIs, including CfgSParameterExternalAttenuationTableSplit and FetchRawIQDataSplit.
Adds the missing WLAN OFDMModAccFetchReferenceDataConstellationTrace APIs, including interleaved IQ and split variants.
Corrects the RFmxVNA CalkitManagerCalkitCalibrationElementSetPortConnectors generated API signature.
Corrects the RFmxPulse FetchAcquiredAmplitudeTrace generated API parameter naming/signature.
Regenerates affected proto, client, service, library, mock library, and compilation test files.

Work items addressed:
Bug 3277255: [GRPC WLAN] digital_edge_source_raw parameter naming is inconsistent for SpecAn and WLAN for API "CfgDigitalEdgeTriggerRequest" in the proto file
Bug 3277313: [RFmx Instr] Grpc Server : Split APIs are missing
Bug 3277224: [WLAN] FetchReferenceDataConstellationTrace API not present in GRPC proto
Bug 3814050: Wrong gRPC implementation for RFmx APIs: VNA: CalkitManagerCalkitCalibrationElementSetPortConnectorsRequest and Pulse: FetchAcquiredAmplitudeTraceRequest

Why should this Pull Request be merged?

These changes bring the RFmxInstr, RFmxPulse, RFmxVNA, and RFmxWLAN generated gRPC metadata and code in line with the 26.5.0 RFmx APIs.

This fixes missing or incorrect gRPC API surfaces that would otherwise prevent users from calling the affected RFmxInstr Split APIs, WLAN reference constellation trace APIs, and the corrected RFmxVNA/RFmxPulse APIs through grpc-device.

The fixes also make the generated proto and service implementations consistent with the underlying driver API signatures and expected parameter names.

What testing has been done?

Manually inspected generated files.
Copied files from grpc-device-scrapigen/out/rfmxinstr/export/ to grpc-device/source/codegen/metadata/nirfmxinstr/ and built grpc-device successfully.
Manually inspected nirfmxinstr.proto file.
Copied files from grpc-device-scrapigen/out/rfmxpulse/export/ to grpc-device/source/codegen/metadata/nirfmxpulse/ and built grpc-device successfully.
Manually inspected nirfmxpulse.proto file.
Copied files from grpc-device-scrapigen/out/rfmxvna/export/ to grpc-device/source/codegen/metadata/nirfmxvna/ and built grpc-device successfully.
Manually inspected nirfmxvna.proto file.
Copied files from grpc-device-scrapigen/out/rfmxwlan/export/ to grpc-device/source/codegen/metadata/nirfmxwlan/ and built grpc-device successfully.
Manually inspected nirfmxwlan.proto file.

@RahulBenaka RahulBenaka added binary-breaking Change to proto file that requires client updates source-breaking Change to proto file that will break client if they update labels Jun 19, 2026
nidevice_grpc.Session instrument = 1;
string selector_string = 2;
int32 array_size = 3;
int32 timeout = 3;

@reckenro reckenro Jun 19, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for tagging the PR breaking.

Can you also briefly call out in a new section in the PR description each of these breaking changes and for which API they're for?

That makes it easier when we make a release to comb through and see at a high level what breaking changes are associated with the breaking PRs so we can include that info in the release notes.


//---------------------------------------------------------------------
// This file is generated from NI-RFMXINSTR API metadata version 25.3.0
// This file is generated from NI-RFMXINSTR API metadata version 26.5.0

@reckenro reckenro Jun 19, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment is just to block the PR . Similar reasoning as the comment in the other PR

grpc-device will be having an early 2.18 release for some critical changes before releasing again for 2.19. This process will be starting tomorrow 6/16 and would want this change to go in after that early release has happened which should be done before the end of the week June 19th.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

binary-breaking Change to proto file that requires client updates source-breaking Change to proto file that will break client if they update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants