NI-SCOPE 20.0 Known Issues

Aperçu

This document contains the NI-SCOPE 20.0 known issues that were discovered before and since the release of NI-SCOPE 20.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.

Bug Number

Legacy ID

Description

Details

227466 709944

Dynamic Error Elaboration does not work on Linux

On Linux systems, error messages in LabVIEW are not populated correctly.

Workaround:

No current workaround.

Reported Version:

NI-SCOPE 18.7

Resolved Version:

N/A

Added:

Dec 17, 2018

227114 669761

NI System Configuration API within LabVIEW is Slow on Linux Systems

On Linux systems, CPU resource utilization and execution time for calls to the NI System Configuration API during instrument driver sessions within LabVIEW are high.

Workaround:

Close and relaunch LabVIEW to improve performance.

Reported Version:

NI-SCOPE 17.2

Resolved Version:

N/A

Added:

Dec 17, 2018

227386 413671

Self-Calibration for Certain Oscilloscopes is Not Supported on Linux Systems

On Linux systems, self-calibration is not supported for the PXI-5922, PCI-5922, PXIe-5185, and PXIe-5186.

Workaround:

No current workaround.

Reported Version:

NI-SCOPE 18.7

Resolved Version:

N/A

Added:

Jul 11, 2019

227456 717236

NI-SCOPE LabVIEW I/O Controls Do Not Autopopulate on Linux Systems

On Linux systems, NI-SCOPE I/O controls in LabVIEW do not autopopulate, and the dropdown arrow on the control is greyed out.

Workaround:

Manually type in the name of the device that you want to use.

Reported Version:

NI-SCOPE 18.7

Resolved Version:

N/A

Added:

Dec 17, 2018

227458 721036

Program that uses NI-SCOPE intermittently crashes when exiting and returns non-zero exit code

On Linux systems, programs that use the NI-SCOPE API may crash intermittently when exiting and return a non-zero exit code.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-SCOPE 18.7

Resolved Version:

N/A

Added:

Dec 17, 2018

877671 644979

Code Using API in niScopeObsolete.llbs and Converted for LabVIEW NXG Is Broken

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-SCOPE 17.0

Resolved Version:

N/A

Added:

May 18, 2017

890924 705654

Error -250043 occurs at niTClk Synchronize when synchronizing different device models

An error can occur if the TClk timebase of the Sync Pulse Sender device is not a multiple of the timebase of each slave device.

Workaround:

If you have set the Absolute Sample Clock Offset or Phase DAC Oscillator NI-SCOPE properties on synchronized devices of different model numbers, place a different device model first in the array of session references that are being synchronized.

Reported Version:

NI-SCOPE 18.6

Resolved Version:

N/A

Added:

Aug 31, 2018

534713 276615

Cannot enable a Peer-to-Peer stream after calling an Abort.

When you abort a Peer-to-Peer stream using niP2P Abort, you cannot call the niP2P Enable function until you call the niP2P Flush and Disable function first.

Workaround:

Call "niP2P Flush And Disable Peer to Peer Stream" first. Then call "niP2P Enable Peer to Peer Stream"

Reported Version:

NI-SCOPE 3.7

Resolved Version:

N/A

Added:

Feb 13, 2011

535213 287156

NI 5122 - Changing the Rate of the External Clock

When using an NI 5122, to change the rate of the external clock within the same session, you need to first change the rate by setting the Sample Clock Timebase Rate attribute, then change the rate of your source, then call the function niScope_Commit. If you change the rate of the source before setting the attribute, you may get an error.

Workaround:

Another workaround is to abort the acquisition after fetching the data but before changing the rate.

Reported Version:

NI-SCOPE 3.5.1

Resolved Version:

N/A

Added:

Mar 15, 2011

535214 287160

NI PXI/PCI-5142, NI PXIe-5622 TClk Synchronization is not Fully Supported for Certain Cases

When the DDC Enabled property or the NISCOPE_ATTR_DDC_ENABLED attribute is set to True, there are certain configurations for which shared triggers cannot be TClk synchronized. For all cases, it is assumed that the DDC is enabled. If the DDC is not enabled, there are no restrictions on TClk synchronization.

Workaround:

Add red/green table for more information on which configurations are supported.

Reported Version:

NI-SCOPE 3.6.1

Resolved Version:

N/A

Added:

Mar 15, 2011

535401 480522

Windows 8.0 to Windows 8.1 upgrade issue

Upgrading the version of Windows on a system with this driver installed may result in the loss of device names, the loss of device configuration, and/or devices appearing disconnected. For more information on how to resolve this, visit ni.com/info and enter the Info Code 'excrxm'.

Workaround:

Reconfigure your devices in Measurement & Automation Explorer

Reported Version:

NI-SCOPE 14.0

Resolved Version:

N/A

Added:

Jun 30, 2014

535266 285864

Dynamic Mode in the LabVIEW FPGA Module is not Supported with P2P Streaming

Using dynamic FPGA interfaces (also known as dynamic mode) in the LabVIEW FPGA Module is not supported when using peer-to-peer streaming.

Workaround:

Dynamic mode is enabled by default in the LabVIEW FPGA Module 2010. To disable Dynamic mode, complete the following steps: 1. Place the Open FPGA VI Reference function on the LabVIEW block diagram. 2. Right-click the function and select Configure Open FPGA VI Reference. 3. Remove the checkmark from the Dynamic mode listbox.

Reported Version:

NI-SCOPE 3.7

Resolved Version:

N/A

Added:

Mar 15, 2011

535252 258807

NI 5622 acquisitions synchronized using TClk can be misaligned under certain conditions

When using TClk synchronization where two or more NI 5622 acquire at different I/Q rates with DDC enabled, it is possible for the acquired data to be misaligned. The misalignment manifests itself as a skew where the data from one device appears to be leading/lagging the data from the other device. The time delay between the data acquired by the master and a slave is constant for the combination of the hardware settings configured on the two devices. This skew is repeatable and does not vary with time.

Workaround:

Since the skew does not vary with time, users can empirically determine the expected misalignment and correct the acquired data manually.

Reported Version:

NI-SCOPE 3.6

Resolved Version:

N/A

Added:

Feb 22, 2011

535267 287099

Traditional NI-DAQ installs support for only the latest installed version of LabVIEW

Beginning with version 7.4.2, Traditional NI-DAQ (Legacy) will install support for the latest version of LabVIEW found on the system.

Workaround:

If you require support for more than one version of LabVIEW, complete the following steps: Install Traditional NI-DAQ (Legacy)(included in the NI-SCOPE installer). Restart the system. Copy the following folders from the latest version of LabVIEW to the folder of the older version of LabVIEW. [LVDIR] indicates the folder of the latest LabVIEW version. [LVDIR]\vi.lib\daq [LVDIR]\examples\daq [LVDIR]\help\lvdaq.chm [LVDIR]\menus\default\daq You should now be able to use Traditional NI-DAQ (Legacy) with both versions of LabVIEW. The Traditional NI-DAQ (Legacy) API is mass-compiled in LabVIEW 7.0. This will not affect the functionality of your VIs. However, LabVIEW will prompt you to save the Traditional NI‑DAQ (Legacy) subVIs if your LabVIEW version is greater than 7.0. To avoid the prompts, mass-compile the folders referenced above. If you require Traditional NI‑DAQ (Legacy) support for earlier versions of LabVIEW, you need an earlier version of Traditional NI-DAQ (Legacy).

Reported Version:

NI-SCOPE 3.8

Resolved Version:

N/A

Added:

Mar 15, 2011

535256 278469

Hybernating a system with a PXIe 5185/5186 immediately after booting will cause the system to hang

When the system boots, the NI PXIe 5185/5186 performs a power-up calibration procedure. If the system is forced to hybernate/sleep while the power-up calibration is in progress, you will have to wait until the calibration is complete before the system can be brought out of hybernation. The LEDs on the PXIe 5185/5196 turn green once power-up calibration is complete.

Workaround:

Wait until the power-up calibration is complete.

Reported Version:

NI-SCOPE 3.8

Resolved Version:

N/A

Added:

Feb 13, 2011

535268 287102

NI PXIe-5122 and NI PXIe-5622 Firmware Update is installed with NI-SCOPE

A firmware update for the NI PXIe-5122 and NI PXIe-5622 is available with NI-SCOPE. This update enables peer-to-peer streaming functionality on these devices.

Workaround:

To update firmware, run the Firmware Updater application from one of the following locations: Windows XP and Windows 7/Vista 32-bit: C:\Program Files\National Instruments\NI-DAQ\fpgafiles\ni5122\NI PXIe-5122 Firmware Updater.exe. Windows 7 64-bit/Vista 64-bit: Program Files (x86)\National Instruments\NI-DAQ\fpgafiles\ni5122\NI PXIe-5122 Firmware Updater.exe. This application will upgrade your firmware to the latest available version that works with this driver. After the application has finished running, you will be required to power down your computer and PXIe chassis to complete the firmware update.

Reported Version:

NI-SCOPE 3.5.2

Resolved Version:

N/A

Added:

Mar 15, 2011

535269 287103

Switching between Certain Trigger Slopes with NI-TClk Misses Triggers

When synchronizing NI 5105 devices with NI-TClk and switching between negative digital trigger slope and immediate trigger, the immediate trigger will time out.

Workaround:

No current workaround.

Reported Version:

NI-SCOPE 3.0

Resolved Version:

N/A

Added:

Mar 15, 2011

535270 287104

NI-SCOPE P2P Example Projects Prompt for Save on Close

NI-SCOPE P2P Example Projects Prompt for Save on Close

Workaround:

NI-SCOPE Peer-to-Peer examples may require you to save them after opening the examples for the first time.

Reported Version:

NI-SCOPE 3.6

Resolved Version:

N/A

Added:

Mar 15, 2011

535258 280321

Measurement and Automation Explorer (MAX) appears to hang when resetting an NI PXIe 5185/5186

If an NI PXIe 5185/5186 is in the process of calibrating to a clock source and MAX requests a device reset, MAX must wait until the clock source calibration is complete and will be unresponsive. Clock source calibration can take several minutes.

Workaround:

Wait until clock source calibration completes.

Reported Version:

NI-SCOPE 3.8

Resolved Version:

N/A

Added:

Feb 13, 2011

535271 287106

Window/FFT Results Differ between NI-SCOPE and LabVIEW

If you perform a Window/FFT in NI-SCOPE, the results are slightly different compared to similar functions in LabVIEW. This is because NI-SCOPE uses a slightly different definition of Windowing than LabVIEW uses.

Workaround:

Refer to the NI High-Speed Digitizers Help for information on windowing.

Reported Version:

NI-SCOPE 3.0

Resolved Version:

N/A

Added:

Mar 15, 2011

535272 287112

NI 515x Devices and NI-TClk Synchronization

When using an NI 5152/ 5153/ 5154 device in TIS mode with NI-TClk synchronization and an external sample clock, the devices configured as the TClk slaves may fail to respond to reference triggers.

Workaround:

No current workaround.

Reported Version:

NI-SCOPE 3.6

Resolved Version:

N/A

Added:

Mar 15, 2011

535273 287114

Downgrading NI-SCOPE

If you need to downgrade the current version of NI-SCOPE to NI-SCOPE 2.1.4 or earlier, you must uninstall the current versions of NI-SCOPE and NI-DAQmx before installing the older version of NI-SCOPE. After the older version of NI-SCOPE is installed, you can then reinstall NI-DAQmx.

Workaround:

Uninstall the current installed versions of NI-SCOPE and NI-DAQmx before installing the older version of NI-SCOPE. After the older version of NI-SCOPE is installed, you can then reinstall NI-DAQmx.

Reported Version:

NI-SCOPE 3.0

Resolved Version:

N/A

Added:

Mar 15, 2011

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