Introduction, 1 system requirements, 2 setting up automation for local use – Teledyne LeCroy FireInspector Automation Application Programming Interface User Manual
Page 5: Chapter 1 introduction
1
FireInspector Automation User’s Manual
CATC
Version 1.0
1. Introduction
FireInspector Automation is an Application Programming Interface (API)
that allows users to create scripts or programs of FireInspector commands
and run these scripts or programs locally or remotely over a network. The
name Automation is derived from the goal of allowing engineers to
automate test procedures.
The FireInspector Automation API is composed of a command set that
duplicates most of the functionality of the FireInspector application.
Automation is implemented through the use of scripts or programs that the
user can write using late binding scripting languages such as VBScript and
WSH or early binding languages such as C++. CATC provides examples of
scripts written in C++.
Once an Automation script or program has been created, it can be run on the
PC attached to the analyzer (henceforth called the host computer) or
transmitted to the PC over a TCP/IP network from a remote location.
Automation uses the Distributed Component Object Model (DCOM)
protocol to transmit automation commands over a network. When run over
a network, the host computer is configured as a DCOM server and the
remote computer is configured as a DCOM client.
1.1 System Requirements
Automation is supported with FireInspector Software Version 2.0
The FireInspector software must be installed on both the host computer and
the remote computer for remote automation. For local automation, it needs
to be installed on the host computer.
1.2 Setting Up Automation for Local Use
If you intend to run automation on the host computer (i.e., the PC attached
to the analyzer), there is no need for any special configuration. You can
simply execute the scripts or programs you have created and they will
control the FireInspector application, which in turn controls the analyzer
box.