IVI Names in the IVI Compliance Package 2.0 and later Are Case-SensitivePrimary Software: Instrument Drivers/IVI>>IVI Compliance PackagePrimary Software Version: 2.0 Primary Software Fixed Version: N/A Secondary Software: N/A
Problem: The IVI Compliance Package 2.0 (ICP 2.0) and later versions handle all names as case-sensitive. If you use logical names, driver session names, or virtual names in your program, make sure that the name you use matches the name defined in the IVI Drivers section in the Measurement and Automation Explorer (MAX) exactly, without any variations in the case of the characters in the name. The IVI Foundation established new specifications that the IVI Configuration Store file format now requires that all names be case-sensitive. This file is used by MAX to store IVI Driver information. The effect of this change to case-sensitivity is that you must now use the correct case for the logical names, driver session names, and virtual channel names that you use in your programs. Class driver Initialize functions require a logical name or driver session name. These names are now case-sensitive. Specific instrument driver Initialize functions require a logical name, driver session name, or VISA resource name. (Typically, you pass VISA resource names to specific drivers). Logical names and driver session names passed to specific driver Initialize functions will be treated in a case-sensitive manner, but VISA resource names passed to the same function will be treated in a case insensitive manner. Many IVI driver functions require channel names. Channel names can be physical or virtual. Typically, you pass physical channel names to specific drivers. Although virtual channel names will now be handled in a case-insensitive manner, the new IVI specifications require that specific drivers handle physical channel names in a case-insensitive manner. If one of these names does not match in case between the IVI Drivers section in MAX and your program, you could get a -1074130429 error. This error states that, "The session name or logical name could not be resolved to a session or driver session." Solution: To avoid any potential issues, make the logical names, driver session names, and virtual channel names in your application match the names in the IVI Drivers section in MAX (and the IVI Configuration Store file) exactly on case. Related Links: Drivers and Updates: IVI Compliance Package Attachments:
Report Date: 02/18/2003 Last Updated: 03/26/2008 Document ID: 2UHEPVDT |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
