NI-VISA Improvement and Bug Fixes

Overview

The following items are the IDs and titles of issues fixed between NI-VISA 4.4 and 15.0.1. For earlier releases of NI-VISA, consult the readme for that version of NI-VISA. If you have a CAR ID, you can search this list to validate that the issue has been fixed.
IDFixed IssueFixed Version
103875viPrintf and variants did not support the %@2 identifier when using short integer arrays nor the %@3 identifier when using any arrays4.4
114300In MAX, VISA options may not reflect manual modifications made to visaconf.ini4.4
92346The C examples would build with warnings when using Microsoft Visual C++ 2005 or higher4.4
93267VISA may crash when trying to close a session in use by a different thread4.4
132397In the VISA COM driver, attribute accessing functions returning a VARIANT_BOOL now return VARIANT_TRUE (-1) instead of VI_TRUE (+1) when the specified attribute is true. This applies for all functions except the raw GetAttribute call, which will continue to return VI_TRUE4.5
93245VISA resources on a CVS target did not appear in the MAX tree4.5
121227Previously, MAX would crash when expanding the "Serial & Parallel" tree item if the settings for a port in VISA are different than those in Windows Device Manager4.5
105351Calling viFindRsrc using 64-bit VISA may cause a command window to flash on the screen4.5
112150Previously, it was not possible to disable 64-bit passports4.5
89395Searching for VXI-11 resources may not find some instruments when multiple Ethernet interfaces are present4.5
135045The nimdnsResponder service may corrupt the routing table4.5.1
177456On LabVIEW RT (Phar Lap ETS), trying to set the attribute VI_ATTR_TCPIP_NODELAY on a TCPIP SOCKET session to VI_FALSE returned an error4.6
165973When closing a TCPIP INSTR session for which an interrupt channel has been established, NI-VISA would not explicitly close the interrupt channel4.6
88858On Windows Vista, an NI-VISA application communicating to a USBTMC device may cause system crash (blue screen) if the device firmware hits a debug assertion4.6
186322When building installers from NI software, VISA 4.6 components were incorrectly labeled as version 4.5 in the installer properties dialog4.6.1
195038Improper message displayed when using VISA Driver Development Wizard to install a driver on Mac OS X without elevated privileges, indicating the driver cannot be installed5.0
208212viStatusDesc causes a memory leak on Linux5.0
233365VISA Driver Development Wizard does not install composite USB device drivers correctly5.0
185549GPIB passport always returns VI_SUCCESS_DEV_NPRESENT if ibln is disabled5.0
173379Real-time support of some NI software may fail to install if NI-VISA is already installed5.0
154617VISA does not recognize the serial number of some USB RAW devices5.0
244124USB communication timeout cannot be set to values greater than 60 seconds5.0.2
258031USB RAW control requests always timeout after 5 seconds5.0.4
207832VISA Read To File does not write text to file on Mac OS X5.1
247629TCP/IP resources cannot only have numbers in LAN device name5.1
285159NI 3110 is not listed under VISA Remote Systems5.1
354588Calls to viLock fail after lock is set in a program that crashes.5.4
375426NI-VISA 5.2 cannot communicate with some third party Ethernet GPIB devices.5.4
382487.NET 4.5 Examples for VisaNS are not installed5.3
388578TCP/IP INSTR resources cannot be added in MAX if the LAN device name only contains numbers.5.4
393875Using VISA asynchronous writes along with VISA events in LabVIEW may cause corrupted data to be written to the serial port.5.4
404486Removing and reconnecting a USB device that has interrupt enabled causes a system crash on VxWorks.5.4
409398GPIB instruments improperly labeled as Not Present in NI Web-base Configuration & Monitoring5.4
420012In VISA Interactive Control, File»Exit closes all open sessions regardless of selection.14.0
437513When opening a session with serial devices that don't support events on Linux operating systems, NI-VISA throws an Unknown System error.14.0
454512Accessing the built-in serial ports on an NI cRIO-9068 using the VISA property node returns error -1073807343 in NI-VISA 5.4.1.14.0
182027Setting serial baud rate with NI-VISA may return errors from third-party serial drivers.15.0
242354VISA always adds a parallel port resource even if the system does not have a parallel port.15.0
543928Extra 0xFF characters may be received when using NI-VISA to read from serial ports on Linux RT targets.15.0.1
580283
328827
Opening a session to VISA resources with resource names longer than 249 bytes can cause LabVIEW or NI MAX to crash. Special thanks to Frederick Angstadt for bringing this issue to the attention of NI.16.0
536772Connection to HiSLIP devices may be dropped if HiSLIP data message contains MessageID parameter of 'None' (0xFFFFFFFF)16.0

 

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