Admin Production ni-theme
Current Publication

Reset Interchange Check

IVI Compliance Package

ClassPrefix Reset Interchange Check

IVI Inherent Function

To form the ClassPrefix VI name, use the prefix of the class driver that you are working with. For example, if you are working with the IviDmm class driver, use the prefix IviDmm to create the correct VI name, IviDmm Reset Interchange Check. Details.

instrument handle The instrument handle that you obtain from the ClassPrefix Initialize or ClassPrefix Initialize With Options VI. The handle identifies a particular instrument session.
error in (no error) The error in cluster can accept error information wired from VIs previously called. Use this information to decide if any functionality should be bypassed in the event of errors from other VIs.

The pop-up option Explain Error (or Explain Warning) gives more information about the error displayed.
instrument handle out The instrument handle that you obtain from the ClassPrefix Initialize or ClassPrefix Initialize With Options VI. The handle identifies a particular instrument session.
error out The error out cluster passes error or warning information out of a VI to be used by other VIs.

The pop-up option Explain Error (or Explain Warning) gives more information about the error displayed.

ClassPrefix Reset Interchange Check Details

When developing a complex test system that consists of multiple test modules, it is generally a good idea to design the test modules so that they can run in any order. To do so requires ensuring that each test module completely configures the state of each instrument it uses. If a particular test module does not completely configure the state of an instrument, the state of the instrument depends on the configuration from a previously executed test module. If you execute the test modules in a different order, the behavior of the instrument and therefore the entire test module is likely to change. This change in behavior is generally instrument specific driver and represents an interchangeability problem.

You can use this VI to test for such cases. After you call this VI, the interchangeability checking algorithms in the specific driver ignore all previous configuration operations. By calling this VI at the beginning of a test module, you can determine whether the test module has dependencies on the operation of previously executed test modules.

This VI does not clear the interchangeability warnings from the list of previously recorded interchangeability warnings. If you want to guarantee that the ClassPrefix Get Next Interchange Warning VI only returns those interchangeability warnings that are generated after calling this VI, you must clear the list of interchangeability warnings. You can clear the interchangeability warnings list by repeatedly calling the ClassPrefix Get Next Interchange Warning VI until no more interchangeability warnings are returned. If you are not interested in the content of those warnings, you can call the ClassPrefix Clear Interchange Warnings VI.