Archived: NI-VISA 5.0.x Known Issues

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Aperçu

This document contains the <product> <version> known issues that were discovered before and since the release of <product> <version>. 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.

This document has been archived and is no longer updated by National Instruments.

Overview

This document contains the NI-VISA 5.0.x known issues that were discovered before and since the release of NI-VISA 5.0.x. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.

Each Issue appears as a row in the table and includes these fields:

  • Issue ID
  • Legacy ID - The issue's legacy ID from NI's deprecated bug reporting database (if applicable)
  • Issue Title
  • Problem Description
  • Workaround
  • Reported Version - the earliest version of MAX the issue was reported in
  • Resolved Version - version the issue was resolved or was no longer applicable
  • Date Added - the date the issue was added to the document (not reported date)

Known Issues by Date

The following items are known issues in NI-VISA 5.0.x sorted by Date.

105956 Viewing NI-VISA Options tab on Real-Time controller may hang MAX
109538 Slot path shows up incorrectly for multifunction and bridged NI-VISA-based PXI devices
126535 VISA Read STB on Mac OS X waits for NI-VISA-defined timeout even if USB device responds sooner
145966 Third-Party USB device communication may timeout after host PC is put into standby
155527 Calling viBufRead multiple times causes incorrect timeout behavior in viBufRead
164621 NI-VISA does not recognize Bluetooth devices on Windows Mobile
166323 Using interrupts with NI-VISA-based PXI cards on NI RT Hypervisor system may cause hang on reboot
182027 Setting serial baud rate with NI-VISA may return errors from third-party serial drivers
183242 Calling viUsbControlIn on composite USB devices may cause system to blue screen
207832 VISA Read To File does not write text to file on Mac OS X
226865 Drivers developed by the VISA Driver Development Wizard on Windows XP Dutch do not install correctly
244124 NI-VISA USB communication using timeout values greater than 60 seconds do not time out properly
90238 3WP9E800 NI-VISA leaks Mach ports on Mac OS X when communicating with USB Raw devices



ID Known Issue
105956

Return
Viewing NI-VISA Options tab on Real-Time controller may hang MAX
On PXI and PC Real-Time controllers with VISA Server installed, MAX occasionally may hang when trying to view the VISA Options tab.

Workaround: N/A

Reported Version: 4.3    Resolved Version: N/A    Added: 08/25/2010
109538

Return
Slot path shows up incorrectly for multifunction and bridged NI-VISA-based PXI devices
PXI 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: N/A

Reported Version: 4.3    Resolved Version: N/A    Added: 08/25/2010
126535

Return
VISA Read STB on Mac OS X waits for NI-VISA-defined timeout even if USB device responds sooner
VISA 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: N/A

Reported Version: 4.4    Resolved Version: N/A    Added: 08/25/2010
145966

Return
Third-Party USB device communication may timeout after host PC is put into standby
A 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: N/A

Reported Version: 4.4    Resolved Version: N/A    Added: 08/25/2010
155527

Return
Calling viBufRead multiple times causes incorrect timeout behavior in viBufRead
When viBufRead is called with a discrete timeout, the function initially times out correctly. Every subsequent call to viBufRead times out immediately instead of waiting for the specified length of time.

Workaround: N/A

Reported Version: 4.4    Resolved Version: N/A    Added: 08/25/2010
164621

Return
NI-VISA does not recognize Bluetooth devices on Windows Mobile
On a Windows Mobile device, Bluetooth devices can act as virtual serial devices, giving them a COM port number. NI-VISA cannot recognize this COM port and gives errors when trying to access it through VISA functions.

Workaround: Use the non-NI-VISA Bluetooth VIs.

Reported Version: 4.4    Resolved Version: N/A    Added: 08/25/2010
166323

Return
Using interrupts with NI-VISA-based PXI cards on NI RT Hypervisor system may cause hang on reboot
If you are using interrupts with a PXI card that uses an NI-VISA-based driver on an NI RT Hypervisor system, independent reboot of the RT system may hang if the driver does not have the interrupt disarm sequence defined.

Workaround: N/A

Reported Version: 4.5.1    Resolved Version: N/A    Added: 08/25/2010
182027

Return
Setting serial baud rate with NI-VISA may return errors from third-party serial drivers
NI-VISA may return an error while setting the serial baud rate when using third-party serial drivers, even though setting this same baud rate may work in other third-party applications. This is due to how NI-VISA verifies baud rate settings.

Workaround: N/A

Reported Version: 4.5    Resolved Version: 15.0    Added: 08/25/2010
183242

Return
Calling viUsbControlIn on composite USB devices may cause system to blue screen
When using viUsbControlIn or VISA USB Control In.vi, if a composite USB RAW device is passed in as the VISA resource, the system may crash with a blue screen.

Workaround: N/A

Reported Version: 4.6    Resolved Version: N/A    Added: 08/25/2010
207832

Return
VISA Read To File does not write text to file on Mac OS X
VISA Read To File does not behave as expected on systems running Mac OS X. A VISA Read is performed and the file is created, but no text is written to the file.

Workaround: Perform VISA Read, then pass the output to another file I/O function, such as Write to Text File.

Reported Version: 4.5    Resolved Version: N/A    Added: 08/25/2010
226865

Return
Drivers developed by the VISA Driver Development Wizard on Windows XP Dutch do not install correctly
When using the VISA Driver Development Wizard on Windows XP Dutch, the OS does not correctly recognize the .inf file generated.

Workaround: N/A

Reported Version: 3.4    Resolved Version: N/A    Added: 08/25/2010
244124

Return
NI-VISA USB communication using timeout values greater than 60 seconds do not time out properly
If the NI-VISA timeout property for USB devices is set to a value greater than 60 seconds, communication still times out at 60 seconds instead of the larger value.

Workaround: N/A

Reported Version: 5.0    Resolved Version: N/A    Added: 08/25/2010
90238
3WP9E800

Return
NI-VISA leaks Mach ports on Mac OS X when communicating with USB Raw devices
When 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: 3.4    Resolved Version: N/A    Added: 08/25/2010

Document last updated on 8/25/2010

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