6-6
Chapter 6: Creating Automated Scripts
Input
Getting input from the user is similar to outputting data. Again, there are two basic
methods of getting data from the user. You can use the MENU: command or the
GETTEXT: and GETVAR: commands. The MENU input method allows you to pick
from a list of choices such as type of device or features, while the GETTEXT and
GETVAR methods prompt the operator to input a value or string.
MENU: Command Input
MENU: input takes a number of parameters, from two to as many as you can
accommodate with 128 characters. The menu box gives the operator a list to select from.
The output in the variable (the first parameter is a variable) is the index of the selection.
MATH: and JUMP: commands can enable a scheme to branch to a variety of different
subroutines for different substrates with a common script file.
GETTEXT and GETVAR Input
The GETTEXT: command takes just one parameter: a prompt string to notify the user of
what the script is looking for. Whatever text is typed in is echoed to the logfile. This is a
good way to allow the user to annotate their logfile with pertinent data for the
measurement run. GETVAR: takes two parameters. The first parameter is the variable to
store the results in and the second parameter is a string to prompt the user. For example,
this can help a script to determine the number of iterations of measurements, all under
operator control.
Debugging Aids
The KMS-310/400 scripting language offers several features to make debugging,
including the:
DEBUG: command
OPMARK: command
OPERATOR: command
TEXT: command
BOX: command
LINE: command
The DEBUG: command, if followed with a 1 executes the script one step at a time. The
SELECT (or ENTER) key is used to process each step. This allows you to view what the
script is doing at each step, including what the variables are set to and what edges the
RP_EXEC: finds.
Another debugging feature is the OPMARK: command. This command is similar to the
MARK: command that describes a label, except that the Script menu has a button with
the GOTO name on it. All OPMARK:s in the currently loaded script will be present,
allowing instant access to a subroutine to speed up the debugging process.
The OPERATOR: command stops script processing and allows you to examine system
parameters with the icon bar. Use this command to break execution at a specific
location.
Содержание KMS-310
Страница 10: ...Contents viii...
Страница 11: ...About This Manual Intended Audience Manual Organization Conventions Contacting Technical Support 1...
Страница 33: ...System Overview Product Overview Subsystem Overview Functional Overview 3...
Страница 51: ...User Interface Overview Software Controls Software Organization 4...
Страница 53: ...KMS 310 400 Supervisor s Manual 4 3 Figure 4 1 Key Software Elements 1 2 3 4 5 6 7 1 2 3 4 5 6 7...
Страница 119: ...Creating Automated Scripts Overview Script Creation Script Locator Script Commands 6...
Страница 219: ...Operation Overview Access and Exit the Supervisor s Menu Set up a Program Measure Manage Measurement Data 7...
Страница 266: ...7 48 Chapter 7 Operation...
Страница 267: ...Maintenance Overview Lamp Replacement and Alignment Stage Maintenance Electronics Cabinet Maintenance System Cleaning 8...
Страница 292: ...8 26 Chapter 8 Maintenance...
Страница 293: ...Error Messages System Error Messages Script Error Messages 9...
Страница 297: ...Glossary...
Страница 304: ...I 4 Index...