This document contains the NI-SCOPE known issues that were discovered before and since the release of NI-SCOPE 2025 Q1. 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.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 227386 | 413671 |
Self-Calibration for PXI/PCI-5922 is Not Supported on Linux SystemsOn Linux systems, self-calibration is not supported for the PXI-5922 or PCI-5922.
Workaround: There is currently no known workaround for this issue.
|
Reported Version: NI-SCOPE: 18.7 Resolved Version: N/A Added: Jun 17, 2021 |
| 890924 | 705654 |
Error -250043 occurs at niTClk Synchronize when synchronizing different device modelsAn 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: Sep 1, 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 14, 2011 |
| 535213 | 287156 |
NI 5122 - Changing the Rate of the External ClockWhen 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 16, 2011 |
| 535214 | 287160 |
NI PXI/PCI-5142, NI PXIe-5622 TClk Synchronization is not Fully Supported for Certain CasesWhen 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 16, 2011 |
| 535266 | 285864 |
Dynamic Mode in the LabVIEW FPGA Module is not Supported with P2P StreamingUsing 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 16, 2011 |
| 535252 | 258807 |
NI 5622 acquisitions synchronized using TClk can be misaligned under certain conditionsWhen 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 23, 2011 |
| 535256 | 278469 |
Hybernating a system with a PXIe 5185/5186 immediately after booting will cause the system to hangWhen 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 14, 2011 |
| 535268 | 287102 |
NI PXIe-5122 and NI PXIe-5622 Firmware Update is installed with NI-SCOPEA 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 16, 2011 |
| 535269 | 287103 |
Switching between Certain Trigger Slopes with NI-TClk Misses TriggersWhen 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 16, 2011 |
| 535270 | 287104 |
NI-SCOPE P2P Example Projects Prompt for Save on CloseNI-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 16, 2011 |
| 535271 | 287106 |
Window/FFT Results Differ between NI-SCOPE and LabVIEWIf 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 16, 2011 |
| 535272 | 287112 |
NI 515x Devices and NI-TClk SynchronizationWhen 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 16, 2011 |
| 227225 | 413671 |
Error -223449, -224101, or -1074107499 occurs during Self-calibration for PXIe-5185/5186 on Linux SystemsOn Linux, NISCOPE Cal Self Calibrate.vi occasionally throws one of the following errors when running on the PXIe-5185 or PXIe-5186: -223449 Internal Software Error, Component Name: nimxslu proxy -224101 Internal Software Error, Component Name: ni5185cal -1074107499 Device not available for routing. It is possible that the device needs to be reset or that the device is being reset. Workaround: Run self-calibration again.
|
Reported Version: NI-SCOPE: 18.7 Resolved Version: N/A Added: Jun 17, 2021 |
| 1210589, 2256290 |
NI-SCOPE devices may fail under Linux kernel DMA remappingAttempts to use NI-SCOPE devices may fail on Linux kernels that have enabled DMA remapping. The Linux kernel logs will contain errors similar to the following: Linux distributions that enable DMA remapping by default include Ubuntu 22.04 with kernel 6.8 or higher and Ubuntu 24.04.
Workaround: Modify the Linux kernel DMA remapping configuration as outlined in https://www.ni.com/r/iommu-linux.
|
Reported Version: NI-SCOPE: 19.1 Resolved Version: N/A Added: Sep 27, 2024 |
Issues found in this section will not be listed in future known issues documents for this product.
There are currently no issues to list.
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