Teledyne LeCroy USB Analyzer Automation Manual - Manual (Page 7)

Teledyne LeCroy Automation API Reference Manual for USBTracer, USB Advisor, and Voyager USB Protocol
Suite
7
1.3 Setting Up Automation for Remote Use
If you intend to run automation remotely over a network, you must perform DCOM configuration. These
steps are described in the Appendix.
The USB Protocol Suite API exposes the following objects and interfaces:
Objects Interfaces Description
UsbAnalyzer
IUsbAnalyzer
IUsbAnalyzer3 Primary Analyzer interface
_IAnalyzerEvents Analyzer event source
UsbTrace
IUsbTrace Trace file interfaces
IUsbTrace2
UsbRecOptions
IUsbRecOptions Recording options interface
UsbDevice
IUsbDevice USB device interface
AnalyzerErrors
IAnalyzerErrors Error collection interface
Only the UsbAnalyzer object is creatable at the top level (that is, via the CoCreateInstance call),
instantiation of an object of other classes requires API calls. The following diagram represents the object
dependencies:
All interfaces are dual interfaces, which allow simple use from typeless languages as well as from C++.
All objects implement the ISupportErrorInfo interface for easy error handling from the client.
The examples of C++ code given in this document assume using the “import” technique of creating COM
clients, using the corresponding include statement:
#import "UsbAutomation.tlb" no_namespace named_guids
and creating appropriate wrapper classes in .tli and .tlh files by the compiler.
Samples of WSH, VBScript, and C++ client applications are provided.
UsbAnalyzer
UsbRecOptions UsbTrace UsbDevice
AnalyzerErrors