![]() ![]() In Visual Basic, this reference takes the form of a class data type, while in Visual C , a CLSID must be specified. IVI-COM drivers, like all COM components, must be created using a specific, hard-coded reference to the main COM class. For more information on how to use the IVI Configuration Server, see IVI-3.5: Configuration Server Specification available on the IVI Foundation web site. The IVI Configuration Server is installed automatically by the IVI Shared Component installer. Thus, the Foundation provides a COM component known as the IVI Configuration Server for programmatically reading and writing information to the Configuration Store. The Configuration Store is highly self-referential and easily corrupted if modified directly. The IVI Foundation discourages users and driver developers from directly manipulating the Configuration Store XML file (IviConfigurationStore.xml). End users can specify logical names for IVI drivers and virtual names for channels.įor more information on the structure of the IVI Configuration Store, see IVI-3.5: Configuration Server Specification available on the IVI Foundation web site. End users add information to the Configuration Store to describe how they intend to use IVI drivers in their system. IVI driver installers are required to populate the Configuration Store with information such as the instrument classes supported, the instrument models for which the driver is designed, and the physical channel names understood by the driver. This file is known as the IVI Configuration Store and serves as a central repository for IVI driver configuration information. When the IVI Shared Components are installed, a special XML file named IviConfigurationStore.xml is placed in the \Data directory. The IVI Shared Component installer is available for download from the IVI Foundation web site. The root of this directory structure is referred to as the IVI install directory () and is typically \IVI Foundation\IVI. The IVI Shared Component installer creates a directory structure to house the IVI Shared Components as well as IVI drivers themselves. Third parties are not allowed to develop custom installation programs for the IVI Shared Components. Moreover, the Foundation's Shared Component installer is the only IVI-compliant way to install the IVI Shared Components. The IVI Foundation provides an installer for the IVI Shared Components. The following sections provide a brief overview of some of the most important IVI Shared Components. In fact, IVI driver installation programs are required to check for the presence of the IVI Shared Components before installing. These components are collectively referred to as the IVI Shared Components, and they must be installed on any computer that will use IVI drivers. The instrument’s documentation to see what commands it recognizes.In order to facilitate IVI driver development and to ensure a consistent experience for end users building IVI-based test systems, the IVI Foundation develops and maintains a series of freely available software components. Make sure you are using the correct instrument command. Problems sending or receiving, you may need to configure communication When you have connected, you can communicate with your device. IVI configuration store, and configuring communication using an IVI-C classĬompliant interface, see Read Waveforms Using the IVI-C Class-Compliant Interface. For instructions on creating an IVI object, constructing an You can create an ividev object to communicate with Provide additional information about the instrument or device. MATLABDriver ResourceName VendorDriver Model SerialNumber VXI plug
0 Comments
Leave a Reply. |