Home Support Documentation Bugs

Archived: NI Spectral Measurements Toolkit 2.6, 2.6.1, 2.6.2, and 2.6.3 Known Issues

Updated Mar 10, 2020

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 Spectral Measurements Toolkit 2.6, 2.6.1, 2.6.2, and 2.6.3 known issues that were discovered before and since the release of NI Spectral Measurements Toolkit 2.6, 2.6.1, 2.6.2, and 2.6.3. 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

IDKnown Issue
276991

On LabVIEW 2010, the SMT Basic Zoom Power Spectrum (Complex Input) VI slows down indefinitely

When using a small dt such as 100 ps, span=1 on LabVIEW 2010, the SMT Basic Zoom Power Spectrum (Complex Input) VI slows down indefinitely. With span=1, execution takes a long time (20 sec) with dt set to 1 uSec. The VI runs faster when dt is set to 100 nSec or 1 nSec.

Workaround: N/A

Reported Version: 2.6  Resolved Version: N/A  Added: 1/17/2011
294171

Opening VI in LV projects with Spectral Measurement Toolkit (SMT) dependencies results in Project Dependency Conflict Detected error

If you open a VI from a LabVIEW project that has SMT dependencies, the toolkit displays an error about conflicts between different dir.mnu files.

Workaround: N/A

Reported Version: 2.6  Resolved Version: N/A  Added: 7/21/2011
280673

Need to relink deprecated VIs/subVIs for which the path has changed

If an application built with NI Spectral Measurements Toolkit 2.5.1 or earlier uses deprecated VIs or subVIs from previous versions of the NI Spectral Measurements Toolkit, and you upgrade to NI Spectral Measurements Toolkit 2.6, the application may not find the deprecated VIs/subVIs after you upgrade to NI Spectral Measurements Toolit 2.6, even though the VIs are present on the disk.

Workaround: Manually relink the deprecated VIs/subVIs for which the paths have changed.

Reported Version: 2.6  Resolved Version: N/A  Added: 1/17/2011
281106

Upgrading Spectral Measurements Toolkit from a previous installation

Upgrading to Spectral Measurements Toolkit 2.5.1 for LabVIEW from a previous version may lead to the installation of the Spectral Measurement Toolkit files to versions of LabVIEW that are not present on the system, in addition to versions of LabVIEW present on the system. This happens only if any of the following standard-specific toolkits are installed on the system:
  • NI GPS Simulation Toolkit for LabVIEW
  • NI WLAN Measurement Suite
  • NI Measurement Suite for Fixed WiMAX
  • NI Measurement Suite for Mobile WiMAX
Workaround: Uninstall the standard-specific toolkits before upgrading to the latest version of NI Spectral Measurements Toolkit for LabVIEW. Install the standard-specific toolkits after upgrading to NI Spectral Measurements Toolkit 2.5.1.

Reported Version: 2.6  Resolved Version: N/A  Added: 1/17/2011
320267

License Manager unable to check out Spectral Measurements Toolkit license from certain packages in a volume license file

If you purchase a bundle, such as ASL or DevSuite that includes the Spectral Measurements Toolkit, the license of Spectral Measurements Toolkit is not present in the list of licenses for that bundle. Hence, you will be unable to use the licensed version of Spectral Measurements Toolkit.

Workaround: Use a local license for Spectral Measurements Toolkit.

Reported Version: 2.6  Resolved Version: N/A  Added: 12/3/2011


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.

Back to top

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