| ScanWorks®
JTAG Programming Stations 
CAE/CAD Design Data Import and Use
ScanWorks uses data imported from the design tools as a netlist
for interconnect testing and as schematic and layout data
for graphical views of the design. Netlists are extracted
from the data used for graphical displays or from traditional
netlists provided by design tools. All popular formats are
supported for both types of data. Netlist data is used for
verifying connections between boundary-scan devices, non-boundary-scan
devices (such as memory devices) as well as for determining
access to flash memories for on-board programming and creating
scan path verification tests.
CAE/CAD data provides access to design information at all
stages of the product development cycle. With the intelligent
design browser provided with the design management software,
design engineers, test engineers, and repair technicians can
view the design data in either schematic or layout views.
Faults detected by interconnect tests are highlighted on the
layout view, enabling repair technicians to easily locate
the fault on the board.

Organizing and Managing your Design and Test Data
The design management software enables you
to keep all the design and test data associated with a design
together. Similar designs can be kept together in project
folders. Projects and/or designs can be easily exported to
another ScanWorks Test Development station, to a ScanWorks
Manufacturing station, or to an Agilent ScanWorks for the
3070 installation as a single compressed file. This eases
the process of transferring to manufacturing and ensures that
all files needed are available.
All test or programming operations are implemented
as actions. An action encapsulates all the information needed
to run a test and diagnose the results. Actions can be executed
individually or organized into sequences. A sequence can be
executed in a batch mode. The design management software includes
a simple test executive that enables you to run sequences.
All actions and sequences can be exported as part of the design
or project when moving to manufacturing.
User Access Control
In ScanWorks, system administrators and supervisors can control
who has access to specific ScanWorks features by specifying
groups of users and setting the access rights of the groups.
The ability to edit, delete, run, and save tests can be limited
to the engineers responsible for the tests.
Macro Programming Language
The ScanWorks macro programming language is a powerful, high-level
language that provides access to your design at any level,
from individual scan cells to entire test registers or subsets
of test registers. With specialized functions and procedures
you can control or observe a specific pin or create a complete
test for a cluster of non-boundary-scan logic. With a macro
program you can establish “safe” conditions before entering
the boundary-scan test mode or maintain a safe state throughout
testing.
ScanWorks Application Programming Interface (API)
As part of the design management software, you have access
to three APIs designed for creating custom user interfaces
for manufacturing operators and to automate the test generation
and application process. All three APIs support LabVIEW, LabWindows,
Agilent (HP)-VEE, Visual Basic, C++, Test Stand, and other
tools for creating test executives and one supports common
scripting languages such as Test Control Language (Tcl) or
Perl. With ScanWorks APIs, you can integrate ScanWorks tests
and programming into a UI with the same look and feel your
operators are accustomed to using with other test tools. ScanPort
provides functions to apply ScanWorks actions and control
the action parameters from your UI. ScanWorksAPI provides
functions to apply actions as they were created in a Test
Development Station, making test program creation easier.
ScanWorks process automation scripting allows you to use a
script to create ScanWorks projects, designs, and actions,
and then integrate application of the actions into test flows
along with any other test types that can be run with a script
program. Using scripts for repetitive test generation processes
can save enormous amounts of test development time.
Previous : Next
Page
2 of 2 |