YSI Data Scout Advanced - Manual (Page 67)

YSI Incorporated Data Scout Advanced 63
5 . 0 T E S T I N G T R A N S D U C E R S
This chapter details the Test functions available to typical users. There is one Execute Script function available. Chapter 3 described
how to activate this function from the main Data Scout Advanced window’s Test menu. Here the separate Execute Script window
(with its own unique visible and hidden controls) is described in its fullest functional detail with pictures and examples. For details on
writing custom Scripts (also called Command files) see Appendix C.
5.1 THE EXECUTE SCRIPT WINDOW’S CONTROLS
Unlike the main Data Scout Advanced window and the Run window, the Execute Script window has no menu bar below its title bar
(figure 5.1). Instead it has several visual control frames, each containing text boxes, visible buttons, and other “hidden” controls (e.g.,
double-clicking a File Name text box is the same as clicking its Browse button).
Each frame allows the user to control the three main phases of operating this function: (1) choosing a Script (command) file to be
executed, (2) choosing a Log file to record results of script execution, and (3) actually executing the script and viewing its progress.
After Script file execution, the Log file may be examined to see the response of every command executed.
Figure 5.1
Once a File Name is selected by the user in the Script File to Execute: (first) frame, a default File Name is selected automatically for the
Log File to Write: (second) frame. The default Log file is named <cmdname>_<date>_<time>.log. If one executes the same
command multiple times, the same log file name will be overwritten, unless one changes the log file name by manual editing. However,
if you exit the form and reselect it, and then execute the same command file again, a new log file name (with unique date/time) is
created for this new session.
The window has a separate Exit button, though the [X] button at extreme right end of its Title Bar works the same. If a script’s
execution is in progress, these exit functions will not work, and instead will “beep” and show a warning message. The user must
explicitly click the button Abort Script to overtly stop the script’s execution, or wait for its completion, before exit is possible.