niDCPower Reset Interchange Check

Configures interchangeability-checking algorithms to ignore all previous configuration options.

Details

	instrument handle identifies a particular instrument session. instrument handle is obtained from the niDCPower Initialize or the niDCPower Initialize With Options VI.
	error in (no error) describes error conditions that occur before this VI runs. status is TRUE (X) if an error occurred before this VI ran or FALSE (checkmark) to indicate a warning or that no error occurred before this VI ran. The default is FALSE. code is the error or warning code. The default is 0. If status is TRUE, code is a negative error code. If status is FALSE, code is 0 or a warning code. source describes the origin of the error or warning and is, in most cases, the name of the VI that produced the error or warning. The default is an empty string.
	instrument handle out passes the handle used to identify the session in all subsequent NI-DCPower VI calls.
	error out contains error information. If error in indicates that an error occurred before this VI ran, error out contains the same error information. Otherwise, it describes the error status that this VI produces. status is TRUE (X) if an error occurred or FALSE (checkmark) to indicate a warning or that no error occurred. code the error or warning code. If status is TRUE, code is a non-zero error code. If status is FALSE, code is 0 or a warning code. source describes the origin of the error or warning and is, in most cases, the name of the VI that produced the error or warning.

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 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 can change. This behavior change is generally instrument-specific and represents an interchangeability problem.

You can use the niDCPower Reset Interchange Check VI to test for such cases. After you use this VI, the interchangeability-checking algorithms in NI-DCPower ignore all previous configuration operations. By using 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.