NI-SCOPE 2024 Q1 Bug Fixes

Overview

The following items are notable issues fixed between the release of NI-SCOPE 2023 Q4 and NI-SCOPE 2024 Q1, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of NI-SCOPE.

Bug Number

Legacy ID

Description

Details

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:

NI-SCOPE 20.7

Added:

Dec 17, 2018

1024555, 1265225, 227456 717236

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

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

Workaround:

  1. Manually type in the name of the device that you want to use. Or
  2. Use LabVIEW version 21.0 or later.

Reported Version:

NI-SCOPE 18.7

Resolved Version:

NI-SCOPE 21.0

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:

NI-SCOPE 2023 Q1

Added:

Dec 17, 2018

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:

NI-SCOPE 2023 Q4

Added:

Feb 13, 2011

1265225 413671

No device names appear when I create a session with NI-SCOPE devices on Linux

When selecting a resource name with niSCOPE Initialize.vi or niSCOPE Initialize With Options.vi in LabVIEW with a LabVIEW version prior to 21.0 on an NI Linux Real-Time target, the drop-down menu for selecting resources appears empty and you cannot select a device that is in your system.

Workaround:

  1. Manually enter the resource name for the device you want to use. Use NI Measurement and Automation Explorer (NI MAX) or NI System Configuration software to retrieve the resource name for any devices in the system. Or
  2. Use LabVIEW version 21.0 or later. 

Reported Version:

NI-SCOPE 20.7

Resolved Version:

NI-SCOPE 21.0

Added:

Jun 17, 2021

1664534 413671

NI-SCOPE throws errors on CentOS 8 in LV unless logged in as root

When using NI-SCOPE in LabVIEW on a CentOS 8 operating system, the "read" VI throws an unexpected error (such as -1073807346 "The given session or object reference is invalid.") unless LV was started with root privileges.

Workaround:

There is no known workaround at this time other than to run LabVIEW with root privileges.

Reported Version:

NI-SCOPE 21.0

Resolved Version:

NI-SCOPE 2022 Q3

Added:

Jun 17, 2021

1265225

No device names appear when initializing a session with NI-SCOPE on Linux Desktop

When selecting a resource name with niSCOPE Initialize.vi in LabVIEW on Linux Desktop, the drop-down menu for selecting resources appears empty and you cannot select a device that is in your system.


Workaround:

Manually enter the resource name for the device you want to use. Use the Hardware Configuration Utility or NI System Configuration software to retrieve the resource name for any devices in the system.

Reported Version:

NI-SCOPE 19.0

Resolved Version:

NI-SCOPE 21.0

Added:

Apr 19, 2022

1860393

NI-SCOPE Fails to Install on Linux Kernel 5.13 or Later with Fatal Error

When installing certain NI drivers onto a Linux system using kernel version 5.13 or later, the installation fails with an error about not finding all the dependencies it needs such as:

/var/lib/dkms/nikal/21.5.0f129/build/nikal.c:32:16: fatal error: config/modversions.h: No such file or directory

Workaround:

Reattempt the installation after adding modversions.h to the kernel headers for your current system kernel. For example:
sudo touch /usr/src/linux-headers-$(uname -r)/include/config/modversions.h

Reported Version:

NI-SCOPE 21.0

Resolved Version:

NI-SCOPE 2022 Q3

Added:

May 10, 2022

Additional Patch Information

Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.

These patches currently do not have any special instructions.

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