Electronics Test Scripting Language

Scripting languages of varying types have been around for a long time such as those for testing software but what about one for testing electronics? So I developed a test scripting language of my own for automated functional testing of electronic assemblies. This is done by using simple commands for controlling test equipment and other instruments such as multi-meters, oscilloscopes, signal/waveform generators, power supplies and electronic loads. Almost any kind of instrument that has a GPIB, Serial or Ethernet interface can be used. 

For example, it takes only a few simple script commands to turn on a power supply, set the voltage to some setting, take a reading from a voltmeter and check it against a specification limit. Here is a short example of a script:

PS1.Output(“On”)
PS1.VSet(12)
Delay(200)  ‘milliseconds
DM1.VDCRead()
Evaluate(RANGE, 11.90, 12.1)
 

Data is read from the meter into a standard data buffer and a “Evaluate” command is used to check the measurement against a set the limits. In order the run the script the file is loaded into a User Interface application that sequences the commands providing feedback to the operator as the test is running and displaying the final test result. Data is saved into a SQL-Server compact edition database and a test report is saved to a folder in XML format.  

 If the syntax looks familiar it’s because it’s actually done in Visual Basic so you can use the free Visual Basic Express version to take advantage of Intellisense™, debugging and other error checking features of the Visual Studio environment. I wrote a module containing all the available script commands. These commands are used by a translating application that sequences the tests in a user interface I wrote called TestDirector. I’m also working on a version that will run in console mode if a user interface is not needed. This makes it easy to write and run test programs and avoid costly licensing fees. You can also pause and step through each command to check for faults and verify instrument settings.  

So I’m still thinking of a name for this “Electronics Test Scripting Language” and I’m in the process of writing up documentation and help files. I’m wondering if anyone else might be interested in using it for testing as I’m thinking about making it available for sale. I think there may be many small companies and labs that might find this approach useful.