NI-VISA 2022 Q3 Known Issues
Overview
This document contains the NI-VISA known issues that were discovered before and since the release of NI-VISA 2022 Q3. 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 |
|---|---|---|---|
| 197500 | 283686 |
Rebooting a system or refreshing Devices & Interfaces in MAX will remove a key in visaconf.iniIf the following key is added to disable the error replacement character when performing 9-bit VISA serial reads, refreshing Devices & Interfaces in MAX or rebooting the system will remove that key from visaconf.ini: [ASRL-RSRC-ALIAS] DisableErrorReplacement=1
Workaround: There is currently no known workaround for this issue. |
Reported Version: NI-VISA 5.0 Resolved Version: N/A Added: Aug 9, 2011 |
| 197474 | 255456 |
Two applications simultaneously calling viLock and viUnlock on the same VISA INSTR resource will eventually result in an errorTwo applications that are both trying to lock and unlock a VISA INSTR resource using viLock and viUnlock will result in one of the applications eventually returning error -1073807204: VISA: (Hex 0xBFFF009C) The current session did not have a lock on the resource. Workaround: There is currently no known workaround for this issue. |
Reported Version: NI-VISA 5.0.1 Resolved Version: N/A Added: Aug 9, 2011 |
| 197481 | 491750 |
The viStatusDesc function in LabWindows/CVI may return an incorrect status value when built in 64-bit configurationThe viStatusDesc function in LabWindows/CVI may incorrectly report "VI_SUCCESS" for unknown error codes instead of returning "VI_WARN_UNKNOWN_STATUS" when built in 64-bit configuration. Workaround: There is currently no known workaround for this issue. |
Reported Version: Unknown Resolved Version: N/A Added: Aug 3, 2015 |
| 202346 | 366314 |
TCP VISA Read/Write calls have 2000 ms timeout.If you pass an invalid TCP resource to VISA Read or VISA Write, the call will take 2000 ms to timeout. This occurs regardless of the timeout value originally specified with the VISA Set Timeout call. Due to the synchronous operation of VISA Open, a secondary effect will occur in which parallel VISA calls hang for 2000 ms if an invalid TCP resource is provided to VISA Open.
Workaround: Programmatically check to ensure VISA TCP resource is valid before calling VISA Read/Write/Open.
|
Reported Version: Unknown Resolved Version: N/A Added: Aug 4, 2014 |
| 449848 | 145966 |
Third-Party USB device communication may timeout after host PC is put into standbyA Windows-based machine communicating with a third-party USB device using a driver not developed by the VISA Driver Development Wizard may timeout if the PC is put into standby mode in the middle of a NI-VISA USB transfer. After the PC is woken up, it thinks the USB device should resend the entire data packet and eventually times out because the packet is not resent. Workaround: There is currently no known workaround for this issue. |
Reported Version: NI-VISA 4.4 Resolved Version: N/A Added: Aug 25, 2010 |
| 450323 | 644336 |
VISA & GPIB arbitration not supported in LabVIEW NXG with multiple sessions on the same Controller in Charge interfaceApplications which make use of both VISA sessions and traditional GPIB sessions on the same Controller in Charge interface can experience race conditions and intermittent errors when running in LabVIEW NXG. For more information, please visit www.ni.com/info and enter info code 'gpibvisaconvert'.
Workaround: Migrate from deprecated GPIB palette to VISA palette for existing applications.
|
Reported Version: NI-VISA 17.0 Resolved Version: N/A Added: Apr 27, 2017 |
| 449851 | 308006 |
Providing VISA remote access to a cRIO device may cause duplicate Serial & Parallel entries in MAXAdding a new permission to the Remote Access List under the VISA Server for a cRIO device may cause duplicate Serial & Parallel entries to appear underneath the device in MAX. Workaround: There is currently no known workaround for this issue. |
Reported Version: NI-VISA 4.6 Resolved Version: N/A Added: Aug 9, 2011 |
| 451061 | 412663 |
VISA Interactice Control help cannot be opened on Linux computersWorkaround: There is currently no known workaround for this issue. |
Reported Version: NI-VISA 5.4 Resolved Version: N/A Added: Sep 6, 2013 |
| 450815 | 90238 |
NI-VISA leaks Mach ports on Mac OS X when communicating with USB Raw devicesWhen performing a VISA Open and VISA Close on a USB Raw device multiple times inside a loop, the number of Mach ports in Mac OS X increases. This may cause a crash if the code performing these calls is run over an extended period of time. Workaround: Restart the development/run-time environment |
Reported Version: NI-VISA 3.4 Resolved Version: N/A Added: Aug 25, 2010 |
| 450826 | 109538 |
Slot path shows up incorrectly for multifunction and bridged NI-VISA-based PXI devicesPXI devices that are either behind a PCI bridge or have multiple functions (for example, both Ethernet and SCSI device) show an incorrect slot path in MAX when using a driver generated by the VISA Driver Development Wizard. Workaround: There is currently no known workaround for this issue. |
Reported Version: NI-VISA 4.3 Resolved Version: N/A Added: Aug 25, 2010 |
| 451630 | 105956 |
Viewing NI-VISA Options tab on Real-Time controller may hang MAXOn PXI and PC Real-Time controllers with VISA Server installed, MAX occasionally may hang when trying to view the VISA Options tab. Workaround: There is currently no known workaround for this issue. |
Reported Version: NI-VISA 4.3 Resolved Version: N/A Added: Aug 25, 2010 |
| 451305 | 475562 |
Only serial aliases are returned with I/O Name Filtering in LabVIEW 32-bit.When using I/O Name Filtering with Include these Aliases set to All defined aliases for resources of this class, LabVIEW 32-bit only returns serial aliases. For LabVIEW 64-bit, all defined aliases are returned. Workaround: Set the aliases with MAX. |
Reported Version: NI-VISA 14.0 Resolved Version: N/A Added: Aug 4, 2014 |
| 450832 | 157577 |
Instrument I/O Assistant code generation fails when the FIPS algorithm policy is enabled.The Instrument I/O Assistant fails to generate code in Measurement Studio for Visual Studio 2005 and Visual Studio 2008 when the FIPS (Federal Information Processing Standards) algorithm policy is enabled on a machine. Workaround: 1. Disable the FIPS algorithm policy on the machine. 2. Open or restart Visual Studio 2005 or Visual Studio 2008 and re-generate code in the Instrument I/O Assistant. 3. Re-enable the FIPS algorithm policy on the machine. See this Microsoft KB for more information.
|
Reported Version: NI-VISA 4.5 Resolved Version: N/A Added: Apr 30, 2009 |
| 451482 | 126535 |
VISA Read STB on Mac OS X waits for NI-VISA-defined timeout even if USB device responds soonerVISA Read STB always waits for the timeout defined in NI-VISA before returning, even if a USB device returns a response quicker than the timeout value. Workaround: There is currently no known workaround for this issue. |
Reported Version: NI-VISA 4.4 Resolved Version: N/A Added: Aug 25, 2010 |
| 451432 | 523556 |
NI-VISA may return error 0xBFFF003A (VI_ERROR_INV_SETUP) when enumerating Keysight devicesIn some cases, NI-VISA will return error 0xBFFF003A (VI_ERROR_INV_SETUP) when attempting to enumerate Keysight devices. This occurs because both the Tulip and Serial passports return duplicate information about the devices. Workaround: Disable either the Tulip or Serial passport. |
Reported Version: NI-VISA 14.0.1 Resolved Version: N/A Added: Aug 3, 2015 |
| 1555478 |
NI Drivers Fail to Load and Can Prevent 3rd-party Drivers From Loading on macOS 11.4 and Later With System Integrity Protection EnabledNI-488.2 devices or NI-VISA PCI(e)/PXI(e) devices do not work by default on macOS 11.4 or later if System Integrity Protection is enabled. In addition, 3rd-party drivers may fail to load causing 3rd-party applications to return errors. To check whether your system has System Integrity Protection enabled, use the following command: csrutil status Workaround: It is necessary to explicitly add the NI team ID as an allowed kernel extension publisher. This must be done from macOS Recovery.
After reboot, verify that NI team ID has been added to the system with the following command: spctl kext-consent list |
Reported Version: NI-VISA 21.0 Resolved Version: N/A Added: Aug 2, 2021 |
|
NI-VISA Fails to Install on Linux Kernel 5.13 or Later with Fatal ErrorWhen 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-VISA 21.5 Resolved Version: NI-VISA 2023 Q2 Added: May 10, 2022 |
||
| 2044178 |
Few Installed LabVIEW Versions Are Missing from LabVIEW IDFinder in NI-MAXThe LabVIEW IDFinder field from the VISA Properties tab of a GPIB resource does not list all installed LabVIEW versions. If LabVIEW 2021 or higher is installed, the field is grayed out and shows LabVIEW Not Detected.  Workaround: Install the required instrument drivers using NI Package Manager instead of LabVIEW IDFinder. |
Reported Version: NI-VISA 21.0 Resolved Version: NI-VISA 2023 Q2 Added: Jul 13, 2022 |
|
| 2126414 |
NI driver software fails to install on RHEL9 because of missing /sbin/chkconfigWhen I try to install an NI driver on RHEL9, it fails with an error message indicating that chkconfig is missing. Many NI drivers use chkconfig in initialization of their services and will fail installation if it is not present. It was present in the base images of previous RHEL versions, but as of RHEL9 needs to be installed prior to NI drivers. The latest releases of most NI drivers will automatically install chkconfig on RHEL 9, however there are still a few that don't automatically install it. And none of the older NI driver versions prior to 2022Q4 automatically install it. Installing chkconfig will fix this issue. However there is a chance that chkconfig may not install successfully on RHEL9 (for several reasons) see #2126697 for workarounds if installing chkconfig fails.
Workaround: To explicitly avoid this issue, install chkconfig (which is in one of the RHEL9 default repositories) by running prior to installing NI software on RHEL9.
|
Reported Version: NI Linux Device Drivers 2022 Q4 Resolved Version: N/A Added: Sep 30, 2022 |
|
| 2126697 |
Chkconfig fails to install on RHEL9When running an NI installer on RHEL9, I get an error message which says Failed: chkconfig-1.20-2.el9.x86_64 Error: Transaction failed Workaround: 1. Backup the /etc/init.d folder to somewhere 2. Install chkconfig 3. Restore the backup sudo cp -u /home/<your username>/initd_backup /etc/init.d/ |
Reported Version: NI Linux Device Drivers 2022 Q4 Resolved Version: N/A Added: Sep 30, 2022 |
|
| 2131226 |
NI driver software fails to install on OpenSUSE 15.3+ because of missing /sbin/insservWhen I try to install an NI driver on OpenSUSE 15.3 or 15.4, it fails with an error message indicating that insserv is missing. Many NI drivers use insserv in initialization of their services and will fail installation if it is not present. It was present in the base images of previous OpenSUSE versions, but as of OpenSUSE Leap 15.3 needs to be installed prior to NI drivers. The latest releases of most NI drivers will automatically install insserv on OpenSUSE, however there are still a few that don't automatically install it. And none of the older NI driver versions prior to 2022Q4 automatically install it. Installing insserv will fix this issue.
Workaround: To explicitly avoid this issue, install chkconfig (which is in one of the RHEL9 default repositories) by running prior to installing NI software on OpenSUSE.
|
Reported Version: NI Linux Device Drivers 2022 Q4 Resolved Version: N/A Added: Sep 30, 2022 |
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).