Customize Testing with Scripting

Scripting is a powerful feature that allows you to extend the functionality of the Signature Touch 1, 1100R+, 1100H+, Easy-Touch®, CH2, or CR. It is available as a separately purchased option. With Scripting you can combine custom test processes with the tester’s standard capability to maximize flexibility and speed.

Scripts use the LUA programming language (similar to JavaScript) to create instructions that control the tester. Scripts are text files written using a text editor. You can write your own scripts, use our standard scripts, or even modify a standard script for your application.

To use a script you need to copy the script file to the tester. For the Touch1, you can copy the file to the tester’s hard drive or a network directory the Touch1 can access. For the 1100 testers, you can copy the script file to the tester using the supplied PC program: 1100 File Explorer.

Three kinds of scripts are available:

Test Event Scripts,
Custom Component Scripts,
Custom Report Scripts.

Each script type helps you customize a different aspect of the tester’s operation.

1. Test Event Scripts (.LUA and .EVT extensions)

An event such as “Test Complete,” “Low Voltage Test Start,” “High Voltage Test Start,” etc. triggers the execution of an associated Test Event Script. These scripts need to be attached to a wirelist before they will run. There are two kinds of Test Event Scripts: “LUA” and “EVT”. LUA scripts do not accept parameters, they run exactly as written. EVT scripts accept event parameters that are set up in the wirelist. This allows you to use the same EVT script with different parameters on several wirelists, giving you more flexibility than a .LUA script.

Requirements:

EVT Test Event Scripts require:: 1100 – Software Version 4.0 and higher; Touch1 – Software Version 3.24 (Linux OS) and higher
LUA Test Event Scripts require:: 1100 – Software Version 4.0 and higher; Touch1 – Software Version 2.4 and higher

2. Custom Component Scripts (.CMP extension)

Custom component scripts allow you to create a test process for almost any type of component you may need. Once you create a custom component you attach it to a wire list and use it just like a standard component (resistor, capacitor, diode, etc.). Any number of custom components can be added to a wirelist, each one with different parameters. The process to test a custom component is the same for each instance, but the parameters are specific to each custom component.

Requirements:

Custom Component Scripts require:: 1100 – Software Version 4.0 and higher; Touch1 – Software Version 3.17 and higher with at least 8MB RAM

3. Custom Report Scripts (.RPT extension) – Available on Touch 1 only

Custom Report Scripts allow you to customize the look of your printed test reports or labels. These scripts are custom replacements for the five standard printing tasks in the Touch1. They are system wide and do not need to be attached to a wirelist. (If you need a report specific to a wirelist, use an EVT Test Event Script.) You can replace any of the Touch1’s following five standard print tasks with a custom report script:

Test Summary
Touch 1 Cable Documentation (wirelist report)
Error Report
Test Status – Good Only (automatic print)
Test Status – Errors Only (automatic print)

Requirements:

RPT Custom Report Scripts require:: 1100 – Currently not available; Touch1 – Software Version 3.10 and higher

Lua is a programming language this is similar to JavaScript. Here is some code from a Lua script. This code defines a function that prompts an operator to enter a serial number:

function PromptForSerialNumber()
  local sPromptLine1 = "Enter Serial Number"
  local sPromptLine2 = ""
  local iSerialNumberExists = 0
  local iStyle = 1
  local iMaxChars = 30
  sgSerialNumber = ""

  sgSerialNumber = PromptForUserInformation(iStyle, sPromptLine1, sPromptLine2, iMaxChars, "")
  iSerialNumberExists = StringNotEmpty(sgSerialNumber)
  if iSerialNumberExists == 0 then
    sgSerialNumber = sgNO_SERIAL_NUMBER
  end
end

By putting this code in a Touch 1 script you could prompt for a serial number.

Examples of How you can Customize Your Testing Using Scripts:

Here are a few of the things that can be done with scripts. Many of the items on this list have already been done with scripting. Call us for more information – 1-800-441-9910.

Light L.E.D.s in the device under test
Test Zener Diodes
Test SCSI Terminators (Active and Passive)
Test Gas Fuses, TVS arrays
Store Custom SPC Data
Override the tester’s standard testing mode to suit your own special applications
The tester can control, and be controlled by external devices
Create custom labels/reports/graphics for printers
Communicate with other devices
Create “custom component” tests that can be imbedded into a standard test program
Imbed the Touch 1 into automated machine applications
Test multiple parts at the same time and discriminate which one is bad
Use serial numbers and bar code scanners
Put Operator Comments into the test program
Trigger loading of parent/child wirelists

With scripting your tester becomes a high speed multi-point Volt-ohmmeter where you can specify where to put the leads, what measurements you want to make, and what to do with the results, all controlled automatically.

Cable and Harness Testers