Archived: NI-RFmx SpecAn 1.0 and 1.1 Known Issues

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Overview



This document contains the NI-RFmx SpecAn known issues that were discovered before and since the release of NI-RFmx SpecAn. Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that can be encountered.

Each issue appears as a row in the table and includes the following fields:

  • Issue ID - The number in at the top of each of the cells in the first column. When you report an issue to NI, you may be given this ID, you can also find IDs posted by NI on the discussion forums or in Knowledge Base articles.  "N/A" indicates that there is no ID assigned to the issue.
  • Issue Title (in italics) - Describes the issue in one sentence or less.
  • Problem Description - A few sentences which describe the problem in further detail. The brief description given does not necessarily describe the problem in full detail, and it is expected that you may want more information on an issue. If you would like more information on an issue, contact NI and reference the ID number given in the document.
  • Workaround - Possible ways to work around the problem. The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, visit www.ni.com/kb/ and enter the KnowledgeBase number in the search field to locate the specific document.
  • Reported Version - The earliest version of NI-RFSG in which the issue was reported. If you discover the issue appears in an earlier version of NI-RFSG than is reported in this field, report the discrepancy to NI to have the field updated.
  • 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).

Known Issues by Severity

  Composite measurment on a multi-carrier signal with atleast one measurement measuring a single carrier, results in incorrect measurement.
  If you do not have NI-RFSA 14.0 installed, RFMx may prompt you to save some RFmx VIs.
  Vector averaging is converted to RMS averaging in certain cases.
  Out of memory error occurs when performing spurious emissions measurement when analyzing wide ranges with narrow RBW



 

Composite measurment on a multi-carrier signal with atleast one measurement measuring a single carrier, results in incorrect measurement.

Composite measurement on a multi-carrier signal requires the minimum span of all the measurements to be greater than or equal to the bandwidth of the multi-carrier. The measurements which do not satisfy this criteria are prone to aliasing and measure incorrectly.

Workaround: Perform one measurement at a time.

Reported Version: 1.0    Resolved Version: N/A    Added: 06/25/2014
 

If you do not have NI-RFSA 14.0 installed, RFMx may prompt you to save some RFmx VIs.


Workaround: Save the VIs.

Reported Version: 1.1    Resolved Version: N/A    Added: 11/10/2014
456176

Vector averaging is converted to RMS averaging in certain cases.

Vector averaging is converted to RMS averaging when the acquisition span is greater than the device instantaneous bandwidth. In case of composite measurement, acquisition span is the highest span of all individual measurements.

Workaround: N/A

Reported Version: 1.0    Resolved Version: N/A    Added: 06/25/2014
447616

Out of memory error occurs when performing spurious emissions measurement when analyzing wide ranges with narrow RBW

Out of memory errors may occur when you are analyzing wide ranges with narrow RBW. This is because of the number of samples to be acquired might be huge and requires more processing power to compute spectrum and then perform peak search.

Workaround: Split a wide range into smaller ranges when using narrow RBW.

Reported Version: 1.0    Resolved Version: N/A    Added: 06/25/2014

Document last updated on 06/23/2014

Contacting NI

Contact NI regarding this document or issues in the document. If you contact NI in regards to a specific issue, reference the ID number given in the document. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting NI). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. Also contact us if you find a workaround for an issue that is not listed in the document.

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).