Teledyne LeCroy Automation API for Bluetooth Analyzers - Manual (Page 9)

3
Automation API for CATC Bluetooth Analyzers CATC Ver. 1.40
1.4 Setting Up Automation for Local Use
If you intend to run Automation on the Host Controller (i.e., the PC attached
to the analyzer) you do not need to perform any special configuration. You
can simply execute the scripts or programs you have created and they will
run the analyzer.
1.5 Setting Up Automation for Remote Use
If you intend to run automation remotely over a network, you will need to
perform DCOM configuration. An example of how to configure DCOM in
Windows 98 environment is given in Appendix A.
1.6 Initialization
Merlin II, Merlin and BTTracer are started in automation mode using the
standard command line switch when they are invoked through the
BTAnalyzer interface. To start the application in automation mode, call it
using the following arguments: /automation.
In this case the application does not present a GUI to the user but instead
runs in Minimized mode an icon in the taskbar without the option to
Maximize or Restore. The following screenshot shows an example of a
taskbar with BTTracer running in Minimized mode.
Interfaces to other tools will not be available if the application is not started
in automation mode (when the application was started by the user in GUI
mode and then later connected to by a client), or another client is currently
using the application. In either of these cases the BTAnalyzer:Status
property will be set to BTAPP_STATUS_BUSY. Multiple client
connections are queued and only the first client is allowed access to the
BTAnalyzer methods.
Since both BTTracer and Merlin are restricted to one instance of the
application running at a time, a user on the server side will not be able to
start the application from the shell while a client is connected to an instance
of the application that is running in automation mode.