ScanWorks^® Test Automation
Save time by merging separate steps into one simple operation

Test Automation

Once ScanWorks has automatically generated JTAG or boundary scan tests, any of a number of ScanWorks tools can take the automation process even further by performing many of the manual tasks associated with testing or programming operations. Distinct ScanWorks tests or programming actions can be combined with other similar processes in one seamless process requiring no manual intervention. In addition, if you want to automate a comprehensive test and programming suite, ScanWorks has tools for combining ScanWorks processes with other test technologies in an automated environment that increases productivity and reduces the chance of human error.

Depending on your need, ScanWorks has the process automation tool you need to achieve your objective. ScanWorks process automation tools include:

• Defining a ScanWorks Sequence
• ScanWorks Macro Language
• ScanWorks Process Automation Scripting

ScanWorks process automation tools with other technologies include:

• ScanWorksAPI
• ScanWorks Process Automation Scripting
• National Instruments Integration
• Windows-based Integration Tools

Automating ScanWorks Operations

Defining a ScanWorks Sequence

If you are debugging a prototype, repairing a board or setting up a ScanWorks test station, defining a ScanWorks Sequence is the easiest and most convenient method for automating a series of ScanWorks boundary-scan (JTAG) tests. You simply select the tests (ScanWorks Actions) from a list of previously generated tests and specify the order of execution and any flow-control parameters. ScanWorks sequences can be run from any ScanWorks development, diagnostic and repair, or manufacturing station.

ScanWorks Macro Language

ScanWorks has a built-in macro language that quickly creates simple programs as part of a test sequence without invoking external compilers or interpreters. The ScanWorks Macro Language is a high-level, powerful programming language for generating complete tests or even controlling and observing JTAG or boundary scan functions down to the pin level. Macros often test clusters of non-boundary-scan logic by specifying input stimulus patterns and expected output patterns on a scan-by-scan basis. Macro routines can also precondition boards or systems for testing by setting constraints or by cycling the board through a power-up or reset process.

ScanWorks Macro Example Program.

Back to top of page

ScanWorks Process Automation Scripting

ScanWorks Process Automation Scripting is an extensive library of JTAG function calls that support a wide range of testing activities as simple as specifying the value for a specific boundary-scan cell or as complex as the execution of comprehensive sequences of scan operations. All of the functions supported by ScanWorks’ Macro Language can be done as a script program written in the test language you are most familiar with, including Tcl, Perl, Visual Basic or any language that supports Microsoft's Common Object Model (COM), such as C++ or C#. Boundary-scan operations can be performed through a script program implemented as part of a ScanWorks Action or a script program can be called from a command line within ScanWorks.

ScanWorks Process Automation Scripting Tcl Example Program.

Back to top of page

Automating ScanWorks with Other Technologies

ScanWorksAPI

Some manufacturing operations have standardized on a certain test environment that technicians have become familiar with. Rather than disturb established procedures, ScanWorksAPI integrates ScanWorks tests into existing environments, combining JTAG testing with other types of tests in an automatic, seamless process. ScanWorksAPI is a library of functions specifically designed for the execution of ScanWorks tests in a production setting. ScanWorksAPI features a complete National Instruments VI (Virtual Instrument) library that has native support for NI’s LabView™. It also features a Windows standard complied Dynamic Link Library (DLL) interface for easy integration into other third-party functional and environmental test tools such as NI’s TestStand and LabWindows/CVI™, Agilent VEE™, Visual Basic, C++, C# and others.

ScanWorksAPI Example Functions.

Back to top of page

Process Automation Scripting

With Process Automation Scripting the boundary-scan or JTAG capabilities of ScanWorks are available through many of the programming languages that test engineers are most familiar with. Process Automation Scripting software objects can be created and controlled with interpreted languages like Tcl, Perl, or Visual Basic or compiled languages such as C++ or C#. Process Automation Scripting uses Component Object Model (COM), which makes its objects available to any language that supports COM.

Some of the common uses of Process Automation Scripting include:

• Gathering design description data – Automatically retrieve the input files such as CAE/CAD design files, BSDL files and netlists that ScanWorks needs to create tests.
• Creating and managing ScanWorks projects and design descriptions – Automatically create ScanWorks projects, directory structures and ScanWorks Actions.
• Applying scan vectors – In a familiar programming language, create custom boundary-scan tests and applications such as controlling BIST operations.
• Logging fault coverage and test results data - With no manual intervention, organize and manage test results.

ScanWorks Process Automation Scripting Tcl Example Program.

Back to top of page

National Instruments Integration

The ScanWorksAPI tool features a complete VI (Virtual Instrument) library that has native support for NI’s LabView™. LabView is a graphical development environment for creating flexible and scalable test, measurement and control applications.

ScanWorksAPI also features a Windows-standard complied Dynamic Link Library (DLL) interface for easy integration into TestStand and LabWindows/CVI™. TestStand is a test management environment for organizing, controlling and running automated production test systems on the factory floor. It also generates customized test reports and integrates product and test data across an entire enterprise over the Internet. LabWindows/CVI is an ANSI C development environment and compiler with built-in libraries for acquisition, analysis and presentation.

Several of ScanWorks’ tools can be used to automate ScanWorks operations in combination with NI’s systems. ScanWorks Actions, Sequences, and ScanWorksAPI and its NI VI library can all be used to combine ScanWorks boundary-scan tests and other activities with LabView and LabWindows/CVI, providing an unrivaled flow from basic scan operation to a fully automated boundary-scan test application running in the complete test management environment such as TestStand.

National Instruments VI Example Functions.

Back to top of page

Windows-Based Integration Tools

ScanWorksAPI has a Windows-standard compiled Dynamic Link Library (DLL) interface for easy integration into third-party Windows-based functional and environmental test tools such as Agilent VEE™, Visual Basic, C++ and C#, as well as NI’s Windows-based systems (TestStand and LabWindows/CVI™).

Back to top of page