| ScanWorks®
JTAG Process Automation Scripting 
ScanWorks Object
Model Description
The process automation scripting feature consists of a set
of objects, each encapsulating both data and functionality.
The way these objects are organized, together with the way
the data and functionality is allocated to each object is
called the ScanWorks object model.
The object model is a hierarchy of objects rooted in a single
top-level object called the API object. The API object contains
all the other objects in the object model. Objects in the
ScanWorks Object model are named according to the portion
of the ScanWorks application they represent. For example a
Project object represents a ScanWorks Project. You can access
objects in the ScanWorks object model only when the API object
exists (That is, when ScanWorks is running).
The ScanWorks object model provides high-level access to
your projects, design descriptions, and actions. To access
the data contained in an object, you use the properties of
that object. In all instances, you can get data from the object
using properties. In some instances, properties can be used
to change (or set) data in an object. To access functionality
continued in an object, you use the methods of that object.
Methods initiate some kind of action on an object. For example,
the Run method of the Action object causes ScanWorks to run
the action.
ScanWorks Process Automation Scripting uses the following
objects to access ScanWorks functions. Properties and methods
of each object are documented in the ScanWorks Online Users
Guide.
| Actions |
CreateActionResult |
Path |
Step |
| Action |
Configuration |
Paths |
SequenceResults |
| ActionResults |
Controllers |
Pins |
SequenceResult |
| ActionResult |
Controller |
Pin |
Symbols |
| API |
Designs |
Projects |
Symbol |
| AttributeInfo |
Design |
Project |
TestRegisters |
| BuildResults |
Members |
ResourceMappings |
TestRegister |
| BuildResult |
Member |
ResourceMapping |
UUT |
| Buses |
Net |
Sequences |
|
| Bus |
Nets |
Sequence |
|
| Buffer |
OperationInfo |
Steps |
|
Previous : Next Page
2 of 2 |