NI-RFmx SpecAn 1.2 Known Issues

Overview

This list contains the known issues for SpecAn 1.2.

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-RFmx SpecAn in which the issue was reported. If you discover the issue appears in an earlier version of NI-RFmx SpecAn 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

513757 SEM spectrum trace is incorrect when Power Units = dBm/Hz and RBW is not same across all offset segments and carriers.
517907 The RFmxInstr Close VI crashes TestStand 2013 and later when run with LabVIEW Run-Time Engine.


ID Known Issue
513757

SEM spectrum trace is incorrect when Power Units = dBm/Hz and RBW is not same across all offset segments and carriers.

In SEM, when Power Units = dBm/Hz and RBW is not same across all offset segments and carriers, the spectrum trace is incorrectly scaled. However, the peak amplitude and margins reported are correct.
Workaround: When Power Units = dBm/Hz, set the same RBW across all offset segments and carriers.

Reported Version: 1.0    Resolved Version: N/A    Added: 02/12/2015
517907

The RFmxInstr Close VI crashes TestStand 2013 and later when run with LabVIEW Run-Time Engine.

TestStand 2013 and later loads the latest version of the LabVIEW Run-Time Engine available on the machine before executing a sequence. If you do not select the latest version of the LabVIEW Run-Time Engine in the LabVIEW Adapter settings for sequences having LabVIEW steps, executing a step that calls RFmxInstr Close.vi can cause TestStand to crash.

Reported Version: 1.1    Resolved Version: 1.2    Added: 03/19/2015

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