Commands and Modules

ATEasy commands can be defined in each of the module types:

●        Driver commands provide a layer between the programs and the instruments instructions (for example, I/O Tables, DLL procedures). Although you can call I/O Tables and DLL procedures directly from programs, it is more convenient and more organized to do it using driver commands. Driver commands can start with the driver's shortcut name (for example, DMM) or with the Driver keyword. Using Driver in a command statement can be done only within the driver procedures. Used this way, it refers to the current driver. When using a command in a driver procedure that was defined within the driver, you should use the Driver name instead of the driver shortcut name. This is recommended because the driver shortcut name can be changed from system to system (or you may have two DMMs in your system: DMM1, DMM1).

●        System commands provide a layer between several instrument drivers and the program. A single command can be linked to a procedure using several instruments to perform a single task. Typically, system commands are used when a specific function or task needs to be accessible by all the programs in each project. System commands always start with the System module name.

●        Program commands improve programming by creating language elements specific to a UUT for repeated actions unique to a specific test program. While System and Driver commands are accessible by all modules in each project, the program statements can only be used within that program. Program commands always start with the Program module name.

Here are some examples of commands: