RF Recording Software 1.0 Known Issues

Created Jul 8, 2024

Overview

This document contains the RF Recording Software known issues that were discovered before and since the release of RF Recording Software 1.0. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.

Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community; see Additional Resources.

Glossary of Terms

Bug Number	Legacy ID	Description	Details
		ICsc Calibration GetStatus Returns Empty Field When Using LabVIEW gRPC Client API When calling the GetStatus method from the ICsc Phase Calibration gRPC Client API in LabVIEW, the magnitude_difference array within the GetStatusResponse cluster is empty and the magnitude_difference data is appended to the phase_difference array within the GetStatusResponse cluster. This issue does not impact the ICsc Phase Calibration gRPC Client API for other programming languages. Workaround: Split the phase_difference array in half, then store the first half of the array back into the phase_difference element of the GetStatusResponse cluster and the second half of the array into the magnitude_difference element of the GetStatusResponse cluster.	Reported Version: RF Recording Software 1.0 Resolved Version: RF Recording Software 1.0 Added: Jun 27, 2024

Bug Number

Legacy ID

Description

Details

ICsc Calibration GetStatus Returns Empty Field When Using LabVIEW gRPC Client API

When calling the GetStatus method from the ICsc Phase Calibration gRPC Client API in LabVIEW, the magnitude_difference array within the GetStatusResponse cluster is empty and the magnitude_difference data is appended to the phase_difference array within the GetStatusResponse cluster.

This issue does not impact the ICsc Phase Calibration gRPC Client API for other programming languages.

Workaround:

Split the phase_difference array in half, then store the first half of the array back into the phase_difference element of the GetStatusResponse cluster and the second half of the array into the magnitude_difference element of the GetStatusResponse cluster.

Reported Version:

RF Recording Software 1.0

Resolved Version:

RF Recording Software 1.0

Added:

Jun 27, 2024

Final Time Issue Listed

Issues found in this section will not be listed in future known issues documents for this product.

There are currently no issues to list.

Additional Resources

Explore Support Content and Product Documentation

Ask the NI Community

Request Support from an Engineer

A valid service agreement may be required, and support options vary by country

Glossary of Terms

Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com. You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
Legacy ID – An older issue ID that refers to the same issue. You may instead find this issue ID in older known issues documents.
Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
Workaround - Possible ways to work around the problem.
Reported Version - The earliest version in which the issue was reported.
Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
Date Added - The date the issue was added to the document (not the reported date).