Measurement Computing TempBook rev.3.0 - Manual (Page 97)

Enhanced API Programming Models (TempBook)
10
TempBook User’s Manual Enhanced API Programming Models (TempBook) 10-1
Overview
The enhanced Application Programming Interface (API) allows you to create custom software to satisfy
your TempBook data acquisition requirements. Two chapters explain the enhanced API: this chapter gives
you the basic concepts needed to write effective programs, and chapter 11 describes the API functions in
detail. This chapter explains how to combine the API functions into useful routines and is divided into 3
parts:
•
Data Acquisition Environment outlines related concepts and defines system capabilities the
programmer must work with (the API, hardware features, and signal management).
•
Programming Models explains the sequence and type of operations necessary for data acquisition.
These models provide the software building blocks to develop more complex and specialized
programs. The description for each model has a flowchart and example program excerpt.
•
Summary Guide of Selected API Functions is an easy-to-read table that describes when to use the
basic API functions.
Note: The TempBook enhanced API is a subset of the DaqX API which provides a common interface for
32-bit data acquisition applications (TempBook, WaveBook, DaqBook, DaqBoard, Daq PC-Card,
etc). This manual describes the commands that pertain to the TempBook.
Data Acquisition Environment
In order to write effective data acquisition software, programmers must understand:
•
Software tools (the API documented in this manual and the programming language—you may need to
consult documentation for your chosen language)
•
Hardware capabilities and constraints
•
General concepts of data acquisition and signal management
Application Programming Interface (API)
The API includes all the software functions needed for building a data acquisition system with the hardware
described in this manual. Chapter 11 (daqCommand Reference—Enhanced API) supplies the details about
how each function is used (parameters, hardware applicability, etc). In addition, you may need to consult
your language and computer documentation.
Enhanced vs Standard API
Major differences between the enhanced and standard APIs were described in the introductory chapter
(Programmer’s Guide). Language support varies as follows:
•
The enhanced API (32-bit only) accommodates C, Visual Basic, and Delphi.
•
The standard API (16-bit only) accommodates C, QuickBASIC, Visual Basic, and Turbo Pascal 7.
Note: Coding for the enhanced and standard API cannot be used together; enhanced and standard models
are slightly different (this chapter is for the enhanced API models; chapters 6 to 8 demonstrate examples
using the standard API).
Hardware Capabilities and Constraints
To program the system effectively, you must understand your hardware capabilities. Obviously you cannot
program the hardware to perform beyond its design and specifications, but you also want to take full
advantage of the system’s power and features. You may need to refer to sections that describe your
hardware’s capability. In addition, you may need to consult your computer documentation. In some cases,
you may need to verify the hardware setup, use of channels, and signal conditioning options (some
hardware devices have jumpers and DIP switches that must match the programming, especially as the
system evolves).