The GxSmu package is supplied with an ATEasy driver for each of the board types supported by this package. The ATEasy driver uses the GxSmu.dll to program the board. Each ATEasy driver includes an example that contains a program and a system file for use with the ATEasy driver. Use the driver shortcut property page from the System Drivers sub-module to correct the board slot number (PCI) or base address (ISA) before attempting to run the example.
Plain language commands declared in the ATEasy driver are easier to use than using the DLL functions directly. The driver commands will also generate exception that allows the ATEasy application to trap errors without checking the status code returned by the DLL function after each function call.
The ATEasy driver commands are similar to the DLL functions in name and parameters, with the following exceptions:
The nHandle parameter is omitted. The driver handles this parameter automatically. ATEasy uses driver logical names instead i.e. AO1 for the first analog output board, AO2 for the second, etc.
The nStatus parameter was omitted. Use the Get Status commands instead of checking the status. After calling a DLL function the ATEasy driver will check the returned status and will call the error statement (in case of an error status) to generate exception that can be easily trapped by the application using the OnError module event or using the try-catch statement.
Some ATEasy drivers contain additional commands to permit easier access to the board features. For example, parameters for a function may be omitted by using a command item instead of typing the parameter value. The use of plain language commands is self-documenting. The syntax is similar to English. In addition, you may generate the commands from the code editor context menu or by using the ATEasy’s code completion feature instead of typing them directly.