From Saturday, Nov 23rd 7:00 PM CST - Sunday, Nov 24th 7:45 AM CST, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Saturday, Nov 23rd 7:00 PM CST - Sunday, Nov 24th 7:45 AM CST, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
The following items are known issues in NI-VISA sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 157577 Return | 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 412663 Return | VISA Interactice Control help cannot be opened on Linux computers Workaround: N/A
| |||||
| 366314 Return |
TCP VISA Read/Write/Open calls have 2000 ms timeout. 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.
| |||||
| 475562 Return | 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.
| |||||
| 491750 Return | The viStatusDesc function in LabWindows/CVI may return an incorrect status value when built in 64-bit configuration The 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: N/A
| |||||
| 523556 Return | NI-VISA may return error 0xBFFF003A (VI_ERROR_INV_SETUP) when enumerating Keysight devices In 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.
| |||||
| 536772 Return | Connection to HiSLIP devices may be dropped if HiSLIP data message contains MessageID parameter of 'None' (0xFFFFFFFF) If NI-VISA receives a HiSLIP data message with a MessageID parameter of 'None' (0xFFFFFFFF), it will drop the connection to the HiSLIP device. Workaround: N/A
| |||||
| 543928 Return | Extra 0xFF characters may be received when using NI-VISA to read from serial ports on Linux RT targets There is a known issue with the Linux kernel used in LabVIEW Real-Time 2013 and 2014. It can cause extra 0xFF characters to be returned by a call to VISA Read on a serial port. For more information, go to ni.com/info and enter Info Code NIVISA1501Update_en.Workaround: N/A
| |||||
| 569122 Return | VisaNS Runtime Appears Twice in Measurement Studio Installer Builder Measurement Studio Installer Builder may display two duplicate options for including the VisaNS runtime in the installer. Workaround: Choose one of the instances of the VisaNS runtime, and it will be correctly included in your installer.
| |||||
| 644336 Return | VISA & GPIB arbitration not supported in LabVIEW NXG with multiple sessions on the same Controller in Charge interface Applications 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.
|
Document last updated on 9/6/2018