Measurement Computing GPIB-488.2 - Manual (Page 5)

GPIB 488.2 Porting Guide 978492 Introduction 1-3
API Replacement, the Four Levels of Effort
Direct Replacement
IOtech: lol(Handle)
MCC: Send(Board)
The MCC API command is directly related to the associated IOtech API and
can therefore be easily substituted for the IOtech API. However, conceptual issues
must be dealt with. For example, Handles do not exist within the MCC API;
instead, the address of the controller is passed to the function.
Minor Modification
IOtech: ClearList(Handle, Array of device names)
MCC: DevClearList(Board, Array of device address)
The IOtech device handle [of the GPIB controller] becomes the controller board
address in the MCC call. There is no device name in the MCC API, so an array of
device address is passed to the function call. NOTE: with all address list arrays in
the MCC API, the array terminator ‘NOADDR’ is used to signify the end of the list.
See the MCC GPIB manual for more information.
Major Modification
IOtech: Abort(Handle)
MCC: ResetSys(Board, Array of device address)
SendIFC(Board)
Equivalent functionality of the IOtech Abort command is achieved by calling the
MCC ResetSys command with an array of device addresses to be reset and then
calling the MCC SendIFC command.
No Equivalent Command
IOtech: KeepDevice(Handle)
MCC: No Equivalent Command
The MCC API has no concept of Devices and their associated settings as a complete
entity. As such, a device cannot be stored for later use, or duplicated for use with
other similar devices. If this functionality is required, the programmer must
implement it.