Filter
Top Products
420
S:\agilent\8920\8920b\PRGGUIDE\BOOK\CHAPTERS\ibasic.fb
Chapter 7, IBASIC Controller
The TESTS Subsystem
Writing Programs For the TESTS Subsystem
The Agilent 83224A IBASIC Developer’s Tool Kit for Windows is required for
developing programs which use the Tests Subsystem. Contact your local Agilent
Technologies sales representative or sales office for ordering and pricing
information.
TESTS Subsystem File Descriptions
Three types of files are used in the TESTS Subsystem to store different types of
information.
Code Files
The first aspect of an automated definition is the code itself. This is just a standard
IBASIC Code file that can reside either on the Memory card, on an external disk
drive connected to the GPIB port of the Test Set, or in an internal RAM disk. The
name of this file is preceded by a lower case c in the Test Set. This tells the TESTS
Subsystem that this particular file contains program code.
Library Files
A Library indicates all of the available test subroutines in the code, the set of all
parameters that might be entered using the user-interface screens, and all
specifications that might be used by the subroutines in the code to decide if a test
point passes or fails.
Only one Library is defined for each Code file. The name of this file is preceded by
a lower case l in the Test Set, telling the TESTS system that this is a Library file.
Also, both the Library and Code file should have the same base name to indicate
the relationship between them.
A Library is required to use the user-interface screen functions of the TESTS
Subsystem. If the program is simple enough that there is no need for user-input, or
if all the user-input is simple enough to be accomplished with INPUT statements, a
[NO LIB] option is available.