Archived: NI-VISA 5.2.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 NI-VISA 5.2.x known issues that were discovered before and since the release of NI-VISA 5.2.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.2.x Known Issues 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
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
226865 Drivers developed by the VISA Driver Development Wizard on Windows XP Dutch do not install correctly
90238 3WP9E800 NI-VISA leaks Mach ports on Mac OS X when communicating with USB Raw devices
242354 VISA always adds a parallel port resource
255456 Two applications simultaneously calling viLock and viUnlock on the same VISA INSTR resource will eventually result in an error
283686 Rebooting a system or refreshing Devices & Interfaces in MAX will remove a key in visaconf.ini
308006 Providing VISA remote access to a cRIO device may cause duplicate Serial & Parallel entries in MAX
342419 Block diagram doesn't fully load when using VISA 5.1.x, System Configuration 5.3.x, and LVRT
358525 NI-VISA LabVIEW support pieces are only visible in the feature tree if the corresponding LabVIEW version is installed on the system
375426 Unable to communicate with Agilent GPIB ENet Device



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
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
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
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
242354

Return
VISA always adds a parallel port resource
VISA will always add a static resource bound to LPT1 in visaconf.ini. If a system does not have a parallel port, this resource will show up with a yellow exclamation mark in MAX.

Workaround: Delete the parallel port in MAX

Reported Version: 5.0    Resolved Version: 15.0    Added: 08/09/2011
255456

Return
Two applications simultaneously calling viLock and viUnlock on the same VISA INSTR resource will eventually result in an error
Two 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: N/A

Reported Version: 5.0.1    Resolved Version: N/A    Added: 08/09/2011
283686

Return
Rebooting a system or refreshing Devices & Interfaces in MAX will remove a key in visaconf.ini
If 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: N/A

Reported Version: 5.0    Resolved Version: N/A    Added: 08/09/2011
308006

Return
Providing VISA remote access to a cRIO device may cause duplicate Serial & Parallel entries in MAX
Adding 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: N/A

Reported Version: 4.6    Resolved Version: N/A    Added: 08/09/2011
342419

Return
Block diagram doesn't fully load when using VISA 5.1.x, System Configuration 5.3.x, and LVRT

Workaround: resize or minimize/maximize the block diagram

Reported Version: 5.1    Resolved Version: 5.2    Added: 08/06/2012
358525

Return

NI-VISA LabVIEW support pieces are only visible in the feature tree if the corresponding LabVIEW version is installed on the system

Workaround: N/A

Reported Version: 5.2    Resolved Version: N/A    Added: 08/06/2012
375426

Return

Unable to communicate with Agilent GPIB ENet Device

Workaround: N/A

Reported Version: 5.2    Resolved Version: N/A    Added: 10/31/2012

 

Document last updated on 08/06/2012

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