Measurement Computing GPIB-488.2 - Manual (Page 3)

GPIB 488.2 Porting Guide 978492 Introduction 1-1
Introduction to the GPIB Porting Guide 1
Overview …… 1-1
Major Conceptual Differences between IOtech and MCC Routines …… 1-2
API Replacement, the Four Levels of Effort …… 1-3
How to Use the Guide …… 1-4
Terms … 1-4
Comparing IOtech GPIB with MCC GPIB 488.2 Commands …… 1-5
Overview
This guide is to be used by individuals who need to port from the IOtech API to the MCC 488.2
API. The reason for this is that IOtech 488 devices have reached an End of Life phase and we
therefore recommend replacing the IOtech API with that used by MCC (Measurement
Computing Corporation).
Chapter 2 consists of tables which allow you to look up, either an IOtech or MCC API, and
cross reference it to its associated counterpart. Chapter 3 consists of command syntax and
usage notes.
For each API command a level of effort value icon is provided. These indicate the relative
effort needed to convert an IOtech function to so it can use the MCC API call. We have
identified four levels of effort. These are as follows:
Direct Replacement – The MCC API command is directly related to the
associated IOtech API. The MCC API can be easily substituted for the IOtech
API after the conceptual issues have been addressed.
Minor Modification – Simple modifications to the IOtech code are required
to achieve the same functionality, between the associated MCC and IOtech
command.
Major Modification – Substantial modifications to the IOtech code are
required to achieve the same functionality, between the associated MCC and
IOtech command. Modifications may include data type changes and/or calls
to multiple MCC APIs.
No Equivalent Command – Indicates one of the following two
possibilities.
(a) There is no mechanism to convert to, or to achieve equivalent or similar
functionality, between the IOtech function call and the MCC API. Digital
commands are an example of this category.
(b) Similar functionality can only be achieved by coding efforts, of such
magnitude, that they are beyond the scope of this document.