![]() The function and attribute hierarchies are managed separately because IVI-C development was heavily influenced by VXI Plug-n-Play driver standards, which had already established this bifurcation. The attribute hierarchy is managed in a separate file called the attribute information file (.sub). The function panel file (.fp) is a variable-record binary file that presents the function hierarchy only. Instead, IVI-C drivers use two additional files to present the logical organization of driver functions and attributes. Since IVI-C drivers rely upon basic Windows DLL technology, there is no way to represent a hierarchy of driver functionality in the DLL itself. IVI-C drivers use VISA data types, such as ViInt32, ViReal64, and ViChar. You use an IVI-C driver by including the header file in your program source code and then linking to the. In addition to the DLL, IVI-C drivers include a header file (.h) and an import library (.lib). IVI-C drivers are provided as conventional Windows DLLs with entry points exposed for each function supported by the driver. NET programming languages, as is discussed later in this topic. This also allows IVI-COM drivers to be used seamlessly in. This makes them easier to use in building programs because the developer only has to reference a single DLL to import the driver into their development environment. Since the type library information is baked into the DLL, IVI-COM drivers are fully self-describing. This information is called the type library and offers such details as the name and signature of all driver functions, version information, parameter input/output direction, and even help information. However, unlike conventional Windows components, IVI-COM DLLs contain description information about the functionality of the driver. IVI-COM drivers are packaged as DLLs, like conventional Windows components. IVI-COM drivers use standardized COM data types that can be understood in a wide variety of ADEs (application development environments). IVI-COM methods and properties are organized into interfaces that together form a hierarchy of driver functionality. ![]() COM is a proven standard for building reusable, cross-language components on Windows. IVI-COM drivers use Microsoft's standard COM technology to expose the driver's methods and properties. Memory must be allocated by the client program.Strings and arrays require extra parameters to indicate size.Memory can be allocated by the driver or by the client.Strings and arrays are self-describing.Multiple instrument classes per driver possible.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |