![]() You will need to upgrade those drivers/applications to the new IVI Shared Components and to build on Visual Studio 2005 or higher, or you will need to build those drivers/applications on a different machine that does not have version 2.x of the IVI Shared Components. NET solutions with IO Libraries Suite 15.5.)Ĭaution: Once you have installed version 2.x of the IVI Shared Components (for example, by installing Keysight IO Libraries Suite 15.5), you will not be able to build IVI drivers and applications developed with earlier versions. NET Framework 2.0, and as a result, Visual Studio 2003 may not be used to develop. (Microsoft Visual Studio 2003 does not recognize. For example, if you are using Visual Studio to develop C# or VB.NET applications, you must use Visual Studio 2005 or higher. NET programs, the development environment that you are using must support. NET Framework version 2.0 (SP1 on Windows Vista and Windows 7, SP2 on Windows XP). 64-bit support is unavailable at this time.ġKeysight IO Libraries version 15.5 installs version 2.0.0.0 of the IVI Shared Components (see ) and. VXI (E8491A/B Firewire to VXI controller and E1406A GPIB to VXI controller) are only supported on 32-bit OS's.However, the IO Libraries Suite will function correctly when normal PC operation resumes. If you run the IO Libraries Suite on a Vista or Windows 7 PC, we suggest that you configure the PC to never enter sleep mode automatically, because you may lose I/O events during sleep. On Windows Vista and Windows 7, services cannot prevent the transition to standby, so the PC will sleep even during I/O activity. Power management on Windows Vista and Windows 7: On Windows XP, the Keysight IO Libraries Service prevents transition to standby mode, meaning that if the computer attempts to “sleep” or “hibernate” when the Keysight IO Libraries Service is running, it will not be able to do so.Location of programming samples changed: The default installation location for programming samples is now:Ĭ:\ProgramData\Keysight\Keysight IO Libraries Programming SamplesĬ:\Documents and Settings\All Users\Keysight\IO Libraries Suite Programming Samples. ![]() ![]() In Windows XP it is:Ĭ:\Documents and Settings\All Users\Application Data\Keysight\Keysight IO LibrariesĪnd in Windows Vista and Windows 7 it is:Ĭ:\ProgramData\Keysight\Keysight IO Libraries To the standard Windows location for program data. Location of Keysight Connection Expert log changed: As part of the migration to Vista, we moved the location of the Ace.log file out of:Ĭ:\Program Files\Keysight\IO Libraries Suite.NI-VISA, for example, requires the 4-digit hexadecimal form for USB devices. Shared Components To make it easier to combine drivers and other software from various vendors, the IVI Foundation members have cooperated to provide common. Note: If another vendor’s 32-bit VISA is installed and Keysight VISA is the secondary 32-bit VISA, the parsing rules for regular expressions in viFindRsrc called from 32-bit programs are determined by the other vendor’s VISA. This release enables vendors to provide 64-bit VISA and IVI drivers to test and measurement. This behavior applies to both 32-bit and 64-bit applications using Keysight VISA. The IVI Foundation announces the release of the 64-bit IVI Shared Components and VISA Shared Components. If hexadecimal is used or the VendorId and/or ModelCode is not specified in the regular expression, the hexadecimal format resource string will be returned. If decimal is used, the decimal format of the resource string will be returned. Matching resources will be returned from viFindRsrc in the format you use to specify them. ![]() If you use a regular expression to return USB instruments and you specify a VendorId and/or ModelCode, you can use either hexadecimal or decimal format. In a viOpen call, either format can be used, but the behavior of viFindRsrc has changed. In IO Libraries Suite 15.5, they are displayed as 4-digit hexadecimal numbers (change mandated by the new VISA spec): In previous versions of the Keysight IO Libraries Suite, the VendorId and ModelCode fields were displayed as decimal numbers.
0 Comments
Leave a Reply. |