Creating an Application

To create an application:

  1. Open a new workspace and create a new project.

When you start ATEasy for the first time, it creates a new workspace and project. Otherwise, you can create the workspace and project as explained in Creating a Project.

  1. Add, develop, and configure drivers to the system.

Add a driver for each instrument to be used. Many instruments come with software that can be easily accessed and added to the Driver Libraries submodule. Existing DLLs, which typically come with plug-in test instruments, can be easily linked to ATEasy. For more information, see Using Dynamic Link Libraries (DLLs) with ATEasy.

  1. Develop the system submodules.

The system is generally just a container for drivers. You can develop applications using the system commands, events, procedures, variables, and data types. One reason to develop a system application is for functions that span more than one driver. For information on these submodules, see Overview of System, Drivers, and Interfaces, Overview of Commands, Overview of Module Events, Procedures Overview, and Overview of Variables.

  1. Create, develop, and debug the Test program.

Once the drivers and system are in place, you can write test programs. For information on programs, see About Programs, Tasks, and Tests.

  1. Add forms.

Forms give users an intuitive, visual method of controlling actions and displaying results. For information on forms, see Introduction To Forms.

  1. Analyze data.

External objects, such as a statistical package or spreadsheet, can manipulate or analyze data to provide more customized results. In a similar manner, you can send test results to or retrieve data from a database, so current results can be compared to previous tests.

  1. Repeat the process as needed.

Developing an application is an iterative process. You can use the edit, run, and debug steps as many times as necessary and in any order demanded by the situation. You can provide additional projects, drivers, systems, and programs at any time.

  1. View the test log.

The test results are sent to a Test log through the built-in Print command or the FormatLogString procedure (for a table-like appearance of the results). By default, the Test Log is in text format. However, ATEasy enables the formatting of the Test Log in HTML to allow users to enter pictures, charts or view the log with the Microsoft Internet Explorer browser.

  1. Once development is complete, build the EXE file.

Putting the application into production starts with running the Build command to compile the application and make the EXE file. The EXE file is a stand-alone file and does not need the ATEasy environment to operate. For more information, see Building Your Application.

  1. Distribute the files.

The final step is to ship all the needed files to the production destination. This includes the application EXE file, the ATEasy runtime files (atectl.dll and atert.dll), and any libraries or external files that the project requires. For more information, see Distributing Your Application.