User manual

Part 2: Automation Programming Reference
Automation Compared to IEEE 488.2 Remote Control
Automation does not necessarily replace the IEEE 488.2 legacy remote command set, which is also
supported by MAUI instruments (and will continue to be). Rather, it augments it and allows another class
of application to be created that can be executed locally or remotely.
Automation, however, can be considered as the “native language” of MAUI instruments. All of the
instrument’s controls and features are available to the Automation client, whereas only some of the
instrument features have been implemented in the 488.2 remote command set.
The following table summarizes the differences between the two approaches to remote control:
IEEE 488.2 Remote Control Automation Remote Control
Physical transport TCP/IP and LXI over Ethernet, GPIB, LSIB,
or USBTMC*
Inter-process using COM, inter-PC using
DCOM (TCP/IP)
Textual parsing of instrument
responses required
Yes, all instrument responses need
‘parsing’ to extract useful information
No, each element in the Automation
hierarchy appears as a “variable” to the
Automation client
Compatibility with legacy
programs/instruments
Yes, in most cases remote control
applications written for legacy
instruments will work without
modification
No, Automation is a standard first
introduced with MAUI (XStreamDSO)
Ability to control the oscilloscope
application from “inside the box”
Yes, by using the VICP (TCP/IP) protocol
to talk to the “localhost”
Yes, natively
Ease of use Not trivial, although easier using a tool
such as ActiveDSO** that hides some of
the complexities
Very easy with scripting languages and
MS Office productivity tools
Format of waveform results Binary or ASCII; both require parsing
before use
Arrays of floating point values
Control from MS Office suite Possible via ActiveDSO utility Yes, natively
* Not all interfacesavailable on allmodels. GPIB and LSIB availablewith hardware option.
** ActiveDSO is an ActiveX based driver for TeledyneLeCroy oscilloscopes
2-3