MercuryiTC
©2014 Oxford Instruments Omicron NanoScience. All rights reserved.
Page 102
8 COMMAND REFERENCE GUIDE
8.1 Nomenclature used in this section
The following conventions are used in this document when listing SCPI commands:
Capital letters designate a keyword that must be entered literally (e.g. SET).
Capital letters in angle brackets designate a parameter that must be substituted by the required
value (e.g. <UID> might represent DB2, MB1 etc.).
Several words in square brackets, separated by vertical lines, indicate alternative values that a
parameter can take (e.g. [LIN | SPL | LAGR].
8.2 SCPI and legacy command sets
The iTC supports two separate sets of remote commands:
• SCPI commands are based on the SCPI command set, although the iTC may not be fully
compliant with SCPI.
• Legacy commands were used in previous models (e.g. ITC503).
The user configures the iTC to use one set or the other.
It is recommended that new applications use the SCPI command set, as these commands
provide greater functionality. The legacy command set is provided so that the iTC is compatible
with any existing remote applications that have been written to drive earlier Oxford Instruments
equipment.
8.3 SCPI commands
This section specifies the command message format for communication using the SCPI derived
protocol. The Mercury instrument uses a proprietary defined command set which is similar in
architecture to the SCPI (Standard Commands for Programmable Instruments 1990
(IEEE 488.2)) command architecture but does not claim to fully support this architecture. Below
are examples of standard SCPI commands which are NOT supported:-
To Next Page
Loading...
Need help?
General