THORLABS LDC40 Series User manual

Series 4000
LDC40xx
TED4015
ITC40xx
SCPI
Programmer's Reference
Manual
2015

Version:
Date:
3.3
08-Apr-2015
Copyright © 2015 Thorlabs

Foreword
Contents 4
1 General Information 5
2 Introduction to the SCPI Language 6
62.1 Syntax Conventions 72.2 Command Separators 72.3 Using the MIN, MAX and DEF Parameters 82.4 Querying Parameter Settings 82.5 Command Terminators 82.6 Parameter Types 82.6.1 Numeric Parameters 92.6.2 Discrete Parameters 92.6.3 Boolean Parameters 92.6.4 ASCII String Parameters
3 Commands by Subsystem 10
103.1 IEEE-488.2 Commands 113.1.1 *IDN? - Identification Query 113.1.2 *RST - Reset 123.1.3 *SAV, *RCL, *SDS - Save/Recall Setup 123.1.4 *TST? - Self Test 123.1.5 *OPC, *OPC? - Operation Complete 133.1.6 *WAI - Wait To Continue 133.1.7 *STB? 143.1.8 *SRE, *SRE? 143.1.9 *CLS 143.1.10 *ESR?, *ESE, *ESE? 163.2 System Subsystem Commands 163.2.1 Beeper 163.2.2 Error Query 173.2.3 Line Frequency 173.2.4 SCPI Version Query 183.3 Measurement Commands 223.3.1 Abort Measurement in Progres 223.3.2 Configuring a Measurement 243.3.3 Initiating a Measurement 243.3.4 Fetch a Measurement 263.3.5 Read Measurement Data 263.3.6 Simple Measurement 283.4 LD Output Commands 293.4.1 Output State

293.4.2 Switch-On Delay 303.4.3 Polarity 303.4.4 Noise Reduction Filter 313.4.5 Protection Voltage 313.4.6 Temperature Protection Mode 323.4.7 LD-ENABLE Input Mode 333.4.8 Protection Queries 343.5 PD Input Commands 343.5.1 Polarity 353.5.2 BIAS State 353.5.3 BIAS Voltage 363.5.4 Input Routing 373.6 Thermopile/Power Meter Input Commands 373.6.1 Input Routing 383.7 LD Source Commands 403.7.1 LD Source Function 403.7.2 LD Current Limit 413.7.3 LD Current Setpoint 413.7.4 LD Optical Power 433.7.5 LD Power Feedback 433.7.6 LD Amplitude Modulation 443.7.7 QCW Pulse Setting 453.8 PD Sense Commands 453.8.1 Photodiode Current Range 463.8.2 Photodiode Current Protection 463.8.3 Photodiode Responsivity 473.8.4 Photodiode Power Range 473.8.5 Photodiode Power Protection 473.9 Thermopile/Power Meter Sense Commands 483.9.1 Thermopile/Power Meter Voltage Range 493.9.2 Thermopile/Power Meter Voltage Protection 493.9.3 Thermopile/Power Meter Responsivity 503.9.4 Thermopile/Power Meter Power Range 503.9.5 Thermopile/Power Meter Power Protection 513.10QCW Pulse Trigger Commands 513.10.1 QCW Trigger Source 523.11TEC Source Commands 533.11.1 TEC Source Function 543.11.2 TEC Current Limit 543.11.3 TEC Current Setpoint 553.11.4 TEC Temperature Setpoint Limit 553.11.5 TEC Temperature Setpoint 563.11.6 PID Loop Constants

563.11.7 PID Auto Tune 583.12Temperature Sense Commands 603.12.1 Sensor Selection 603.12.2 Thermistor Calculations 613.12.3 Transducer Offset 623.12.4 Temperature Protection 633.13TEC Output Commands 633.13.1 Output State 643.13.2 Protection Queries 653.14Status Subsystem Commands 683.14.1 Programming and Reading Registers 693.14.2 Auxiliary Register Group 703.14.3 Measurement Register Group 713.14.4 Questionable Register Group 723.14.5 Operation Registers Group 733.14.6 Status Preset Command 743.15Memory Subsystem Commands 743.15.1 Number of State Memories 743.15.2 State Memories Names 753.16Display Subsystem Commands 753.16.1 Display Brightness 753.16.2 Display Contrast 763.17Digital I/O Output Commands 763.17.1 Digital I/O Output 773.17.2 Digital I/O Configuration 773.18Digital I/O Input Commands 783.18.1 Digital I/O Input 793.19Unit Subsystem Commands 793.19.1 Temperature Unit Commands 803.20Calibration Subsystem Commands 803.20.1 Calibration String
4 SCPI Error Messages 81
824.1 Command Errors 834.2 Execution Errors 844.3 Device Specific Errors 844.4 Query Errors 854.5 Instrument Errors
5 Appendix 86
865.1 Instrument Default Settings 915.2 Copyright and Exclusion of Reliability 925.3 Thorlabs Worldwide Contacts

© 2015 Thorlabs
We aim to develop and produce the best solution for your application
in the field of optical measurement technique. To help us to live up to
your expectations and improve our products permanently we need
your ideas and suggestions. Therefore, please let us know about
possible criticism or ideas. We and our international partners are
looking forward to hearing from you.
Thorlabs GmbH
Warning
Sections marked by this symbol explain dangers that might result in
personal injury or death. Always read the associated information
carefully, before performing the indicated procedure.
Please read these advices carefully!
This manual also contains "NOTES" and "HINTS" written in this form.
Attention
Paragraphs preceeded by this symbol explain hazards that could
damage the instrument and the connected equipment or may cause
loss of data.
Note
4

© 2015 Thorlabs
1 General Information
5
1 General Information
This part of the programmer’s reference manual contains specific information about the SCPI
command set of the Series 4000 instruments. A general description is followed by explanations
of how to use the SCPI commands. The command set is according to the SCPI 1999.0
standard.
The Series 4000 instruments provide a USB 2.0 Full Speed link according to the USB 2.0
specification, the USBTMC specification and the USBTMC USB488 specification.
The instrument’s command buffer accepts commands with a maximum length of 255
characters. The instrument’s message output buffer can contain response messages of up to
255 characters.
There are VXIpnp/VISA instrument drivers available for Series 4000 instruments. See
www.thorlabs.com for downloads.
Related documents:
TED4000 Series Operation Manual available at www.thorlabs.com
LDC4000 Series Operation Manual available at www.thorlabs.com
ITC4000 Series Operation Manual available at www.thorlabs.com
USB Test and Measurement Class (USBTMC) Specification, Revision 1.0, available at
www.usb.org
USB Test and Measurement Class, Subclass USB488 Specification (USBTMC USB488),
Revision 1.0, available at www.usb.org
IEEE Std 488.2-1992, IEEE Standard Codes, Formats, Protocols, and Common
Commands, available at www.ieee.org
SCPI Specification, Version 1999.0, May, 1999, available at www.ivifoundation.org

© 2015 Thorlabs6
Series 4000 SCPI Programmers Reference Manual
2 Introduction to the SCPI Language
SCPI (Standard Commands for Programmable Instruments) is an ASCII based instrument
command language designed for test and measurement instruments, based on a hierarchical
tree structure. It means associated commands are grouped together under a common node.
For example:
SOURce[1]
:CURRent
:LIMit
[:AMPLitude] {MIN|MAX|<amps>}
SOURce is the root level keyword of the command, CURRent is the second level keyword, LIMit
is the third level keyword and AMPLitude is the fourth level keyword, which can be omitted in
this case. A colon (:) separates between command levels.
For further information about SCPI please see SCPI Standard available at
www.ivifoundation.org.
2.1 Syntax Conventions
The format used in this manual for commands is illustrated below:
SOURce[1]:CURRent {MINimum|MAXimum|<amps>}
The command syntax shows most commands (and some parameters) as a mixture of upper-
and lower-case letters. The upper-case letters indicate the abbreviated spelling for the
command. For shorter program lines, you can use the abbreviated form. For better program
readability, you can send the long form. In the above example CURR and CURRent are both
acceptable syntax spellings. Other spellings like CUR or CURRe are not allowed and will generate
an error. Commands are not case sensitive.
Curly braces ({}) enclose the parameter choices for a given command string. Braces are not
sent with the command string.
A vertical bar (|) separates multiple parameter choices for a given command string. For
example, {MINimum|MAXimum|<amps>} in the above command indicates that you can specify a
numeric current parameter, or MINimum, or MAXimum. The bar is not sent with the command
string.
Triangle brackets (<>) indicate that you must specify a value for the enclosed parameter. For
example, the above syntax statement shows the <amps> parameter enclosed in triangle
brackets. The brackets are not sent with the command string. You must specify a value for the
parameter (for example 5.0) unless you select one of the other options shown in the syntax (for
example MIN).
Some parameters and even parts of the command itself are enclosed in square brackets ([]).
This indicates that the part of the command or the parameter is optional and can be omitted.
The brackets are not sent with the command string. If you do not specify a value for an optional
parameter, the instrument chooses a default value.

© 2015 Thorlabs
2 Introduction to the SCPI Language
7
2.2 Command Separators
A colon (:) is used to separate a command keyword from a lower-level keyword. You must
insert a blank space to separate a parameter from a command keyword. If a command requires
more than one parameter, you must separate adjacent parameters using a comma (,) as
shown below:
MEM:STAT:NAME 1,"My setting"
A semicolon (;) is used to separate commands within the same subsystem, and can also
minimize typing. For example, sending the following command string:
DISP:BRIG 1;CONT 0.5
... is the same as sending the following two commands:
DISP:BRIG 1
DISP:CONT 0.5
Use a semicolon and a colon to link commands from different subsystems. The colon resets
the command tree to the root level. For example:
SOURce:CURRent 0.5;:OUTPut ON
2.3 Using the MIN, MAX and DEF Parameters
For many commands, you can substitute MINimum or MAXimum in place of a parameter. In some
cases you may also substitute DEFault.
For example, consider the following command:
SOURce:TEMPerature:PROTection:WINDow {MIN|MAX|DEF|<temp>}
SOURce[1]
:CURRent
:LIMit
[:AMPLitude] {MIN|MAX|<amps>}
Instead of selecting a specific value for the <temp> parameter, you can substitute MIN or
MINimum to set the value to its minimum, MAX or MAXimum to set the value to its maximum, DEF
or DEFault to set the value to the default value.
For reasons of clarity the following parts of commands are written in short form only throughout
this manual:
Original Form
Short Form
{MINimum|MAXimum|DEFault|<value>}
{MIN|MAX|DEF|<value>}
{MINimum|MAXimum|DEFault}
{MIN|MAX|DEF}
{MINimum|MAXimum|<value>}
{MIN|MAX|<value>}
{MINimum|MAXimum}
{MIN|MAX}

© 2015 Thorlabs8
Series 4000 SCPI Programmers Reference Manual
2.4 Querying Parameter Settings
You can query the current value of most parameters by adding a question mark (?) to the
command. For example, the following command sets the temperature setpoint:
SOURce:CURRent 5.0
You can then query the value by typing:
SOURce:CURRent?
You can also query the minimum or maximum and - where specified - the default values as
follows:
SOURce:CURRent? MINimum
SOURce:CURRent? MAXimum
2.5 Command Terminators
A command string sent to the instrument must terminate with a <new line> (<NL>) character.
Command string termination will always reset the current SCPI command path to the root level.
2.6 Parameter Types
The SCPI language defines several data formats to be used in program messages and
response messages.
2.6.1 Numeric Parameters
Commands that require numeric parameters will accept all commonly used decimal
representations of numbers including optional signs, decimal points, and scientific notation.
Special values for numeric parameters such as MIN, MAX, and DEF may also be accepted. You
can also send engineering unit suffixes with numeric parameters (e.g., M, k, m, or u). If a
command accepts only certain specific values, the instrument will automatically round the input
numeric parameter to the accepted values.
Additionally numeric parameters can be programmed using binary, decimal, hexadecimal or
octal data formats for the parameter value (for a detailed description of numeric formats see
chapter 7.7.4 <NONDECIMAL NUMERIC PROGRAM DATA> of IEEE488.2-1992).
Example
The four commands program the Auxiliary Enable Register to the same value:
STAT:AUX:ENAB 2081
Program the Auxiliary Enable Register with 2018 decimal.
STAT:AUX:ENAB #H821
Program the Auxiliary Enable Register with 821 hexadecimal.
STAT:AUX:ENAB #Q4041
Program the Auxiliary Enable Register with 4041 octal.
STAT:AUX:ENAB #B100000100001
Program the Auxiliary Enable Register with 100000100001 binary.

© 2015 Thorlabs
2 Introduction to the SCPI Language
9
2.6.2 Discrete Parameters
Discrete parameters are used to program settings that have a limited number of values (like
CELSius, FAHRenheit or KELVin). They have a short form and a long form just like command
keywords. You can mix upper- and lower-case letters. Query responses will always return the
short form in all upper-case letters.
Example
The following command requires a discrete parameter for the temperature unit:
UNIT:TEMPerature {C|CEL|CELSius|F|FAR|FAHRenheit|K|KELVin}
Discrete parameters may also have a default condition. In this manual the default conditions
are underlined.
2.6.3 Boolean Parameters
Boolean parameters represent a single binary condition that is either true or false. For a false
condition, the instrument will accept OFF or 0. For a true condition, the instrument will accept ON
or 1. When you query a boolean setting, the instrument will always return 0 or 1.
Boolean parameters may also have a default condition. In this manual the default conditions
are underlined.
2.6.4 ASCII String Parameters
String parameters can contain virtually any set of ASCII characters. A string must begin and
end with matching quotes; either with a single quote or a double quote. You can include the
quote delimiter as part of the string by typing it twice without any characters in between.

© 2015 Thorlabs10
Series 4000 SCPI Programmers Reference Manual
3 Commands by Subsystem
3.1 IEEE-488.2 Commands
The IEEE-488.2 standard defines a set of common commands that perform functions such as
reset, self-test, and status operations. Common commands always begin with an asterisk (*),
are three characters in length, and may include one or more parameters. The command
keyword is separated from the first parameter by a blank space. Use a semicolon (;) to
separate multiple commands. IEEE488.2 commands are device commands that are common
to all devices according to the IEEE488.2 standard. Most of the commands are described in
detail in this section. The following common commands associated with the status structure are
related to the STATus Subsystem Commands section: *CLS,*ESE,*ESE?,*ESR?
,*SRE,*SRE?,*STB?
See also figure Status Structure .
Table <%TABLENO++%>: IEEE-488.2 commands
Mnemonic
Name
Description
*CLS
Clear status
Clear all event registers and Error Queue
*ESE <value>
Event enable
command
Program the Standard Event Enable Register
*ESE?
Event enable query
Read the Standard Event Enable Register
*ESR?
Event status register
query
Read and clear the Standard Event Register
*IDN?
Identification query
Read the unit’s identification string
*OPC
Operation complete
command
Set the Operation Complete bit in the Standard Event Register
*OPC?
Operation complete
query
Place a 1 into the output queue when all device operations have
been completed
*RCL <value>
Recall command
Return the unit to the user-saved setup
*RST
Reset command
Return the unit to the *RST default condition
*SAV <value>
Save default device
setting
Initialize the content of save/recall registers
*SDS <value>
Save default device
setting
Initialize the content of save/recall registers
*SRE <value>
Service request
enable command
Program the Service Request Enable Register
*SRE?
Service request
enable query
Read the Service Request Enable Register
*STB?
Status byte query
Read the Status Byte Register
*TST?
Self-test query
Perform the unit’s self-test and return the result.
*WAI
Wait-to-continue
command
Wait until all previous commands are executed
65
65
14
14
14
14
11
12
12
12
11
12
12
13
13
13
12
13

© 2015 Thorlabs
3 Commands by Subsystem
11
3.1.1 *IDN? - Identification Query
Syntax
*IDN?
Description
The identification query reads the instrument's identification code which contains four comma-
separated fields. The first field is the manufacturer, the second field is the model code, the third
filed is the serial number, and the fourth field is the firmware revision code which contains two
(LDC4000) or three (TED4000, ITC4000) codes separated by slashes (/).
The query is sent in the following format:
THORLABS,MMM,SSS,X.X.X/Y.Y.Y/Z.Z.Z
Where:
MMM
is the model code
SSS
is the serial number
X.X.X
is the instrument firmware revision level
Y.Y.Y
is the firmware revision level of the front panel board
Z.Z.Z
is the firmware revision level of the temperature controller board (TED4000,
ITC4000 only)
Example
*IDN?
Query the ID code.
THORLABS,ITC4020,E12345678,1.4.0/2.0.3/1.6.0
Typical response.
3.1.2 *RST - Reset
Syntax
*RST
Description
When the *RST command is sent, the instrument performs the following operations:
Switches off the instrument's outputs.
Sets the direction of general purpose I/O1..4 to input.
Switches photodiode BIAS to OFF

© 2015 Thorlabs12
Series 4000 SCPI Programmers Reference Manual
3.1.3 *SAV, *RCL, *SDS - Save/Recall Setup
Syntax
*SAV <value>
*RCL <value>
*SDS <value>
Description
Value: 0..7
Memory location 1 ... 8
Use the *SAV command to save the present instrument setup configuration in non-volatile
(state-) memory for later recall. The *RCL command is used to restore the instrument to the
saved setup configuration. Eight setup configurations can be saved and recalled.
Use the *SDS command to initialize the selected (state-) memory with factory default settings.
Your settings will be overwritten. See also chapter Memory Subsystem Commands and
appendix Instrument Default Settings .
Example
*SAV 1
Saves the present instrument setup configuration to memory location 2.
3.1.4 *TST? - Self Test
Syntax
*TST?
Description
Use this query command to perform the instrument self-test routine. The command places the
coded result in the output queue. A returned value of zero (0) indicates that the test passed,
other values indicate that the test failed and the error code is placed into the instrument’s error
queue.
3.1.5 *OPC, *OPC? - Operation Complete
Syntax
*OPC
*OPC?
Description
When *OPC is sent, the OPC bit in the Standard Event Register will be set after all pending
command operations are complete. When *OPC? is sent, an ASCII 1 is placed in the output
queue after all pending command operations are complete.
Typically, either one of these commands is sent after the INITiate command. The INITiate
command is used to take the instrument out of idle in order to perform measurements. While
operating within the trigger model layers, many sent commands will not execute. After all
programmed operations are completed, the instrument returns to the idle state at which time all
pending commands (including *OPC and/or *OPC?) are executed. When executing the OPC bit
in the status structure is set and/or an ASCII 1 is placed in the output queue.
74
86

© 2015 Thorlabs
3 Commands by Subsystem
13
3.1.6 *WAI - Wait To Continue
Syntax
*WAI
Description
The *WAI command is a no operation command for the instrument and thus, does not need to
be used. It is there for conformance to IEEE488.2.
3.1.7 *STB?
Syntax
*STB?
Description
The *STB? command queries the instrument's Status Byte Register. This is a read-only register
and the bits are not cleared when you read the register. See also figure Status Structure .
Table <%TABLENO++%>: Status Byte Register
Bit #
Decimal Value
Mnemonic - Description
0
1
AUX - Auxiliary Status Structure Summary Bit
One or more bits are set in the Auxiliary Event Register (bits must be enabled,
see Auxiliary Status Register Group ).
1
2
MEAS - Measurement Status Structure Summary Bit
One or more bits are set in the Measurement Event Register (bits must be
enabled, see Measurement Status Register Group ).
2
4
EAV - Error Available Bit
One or more errors have been stored in the Error Queue. Use the
SYSTem:ERRor?[:NEXT] command to read and delete errors.
3
8
QUES - Questionable Data Structure Summary Bit
One or more bits are set in the Questionable Event Register (bits must be
enabled, see Questionable Data Register Group ).
4
16
MAV - Message Available Bit
Data is available in the instrument's output buffer.
5
32
ESB - Standard Event Status Bit
One or more bits are set in the Standard Event Register (bits must be enabled,
see *ESE command).
6
64
RQS/MSS - Request Service / Master Summary Status Bit
One or more bits are set in the Status Byte Register and may generate a
Request for Service (RQS). Bits must be enabled using the *SRE
command.
7
128
OPER - Standard Operation Status Summary Bit
One or more bits are set in the Standard Operation Register (bits must be
enabled, see
STATus:OPERation:ENABle command).
65
69
70
16
71
14
14
72

© 2015 Thorlabs14
Series 4000 SCPI Programmers Reference Manual
3.1.8 *SRE, *SRE?
Syntax
*SRE <value>
*SRE?
Description
The *SRE command enables bits in the enable register (Service Request Enable Register) for
the Status Byte Register Group. See table Status Byte Register for a description of the bits.
Once enabled, the corresponding bits may generate a Request for Service (RQS) in the status
byte. This RQS event may generate a "call back" to your application as a type of asynchronous
interrupt.
3.1.9 *CLS
Syntax
*CLS
Description
The *CLS command clears the event registers in all register groups. This command also clears
the error queue.
3.1.10 *ESR?, *ESE, *ESE?
Syntax
*ESR?
*ESE <value>
*ESE?
Description
The *ESR? command queries the Standard Event Register. In order to be reported to the Status
Byte Register, the corresponding bits in the event register must be enabled using the *ESE
command.
The *ESE command enables bits in the enable register (Standard Event Status Enable
Register) for the Standard Event Register Group. The selected bits are then reported to bit 5 of
the Status Byte Register.
See also chapter Status Subsystem and figure Status Structure .
The following table lists the bit definitions for the Standard Event Register Group.
Table <%TABLENO++%>: Standard Event Register
Bit #
Decimal Value
Description
0
1
Operation Complete
All commands prior to and including *OPC have been executed
1
2
not used
2
4
Query Error
The instrument tried to read the output buffer but it was empty or a new
command line was received before a previous query has been read or both the
input and output buffers are full.
3
8
Device Dependent Error
A self-test or calibration error occurred (an error in the -300...-399 range or any
positive error has been generated). For a complete listing of error messages,
see chapter SCPI Error Messages .
13
65 65
12
81

© 2015 Thorlabs
3 Commands by Subsystem
15
Bit #
Decimal Value
Description
4
16
Execution Error
An execution error occurred (an error in the -200...-299 range has been
generated).
5
32
Command Error
A command syntax error occurred (an error in the -100...-199 range has been
generated).
6
64
User Request
7
128
Power On
Power has been turned off and on since the last time the event register was read
or cleared.
Example
*ESE 4
Sets bit 2 of the Standard Event Status Enable Register which enables bit 2 of the
Standard Event Register to be reported to bit 5 of the Status Byte Register.

© 2015 Thorlabs16
Series 4000 SCPI Programmers Reference Manual
3.2 System Subsystem Commands
Table <%TABLENO++%>: System Subsystem Commands
Command
Description
SYSTem
:BEEPer
[:IMMediate]
Issues an audible signal
:STATE {ON|1|OFF|0}
Activates/deactivates the beeper
:STATe?
Returns the state of the beeper
:ERRor
[:NEXT]?
Returns the latest <error code>, "Message"
:LFRequency {50|60|AUTO}
Sets the line frequency to fixed 50/60Hz or auto
detect
:ACTual?
Returns the used line frequency
:LFRequency?
Returns the line frequency setting
:VERSion?
Returns the level of SCPI standard (1999.0)
3.2.1 Beeper
Syntax
SYSTem:BEEPer[:IMMediate]
SYSTem:BEEPer:STATe {ON|1|OFF|0}
SYSTem:BEEPer:STATe?
Description
The SYSTem:BEEPer[:IMMediate] issues an audible signal.
The SYSTem:BEEPer:STATe command activates or deactivates the beeper.
Example
SYST:BEEP
The instrument will issue an audible signal.
SYST:BEEP:STAT?
Queries the state of the beeper activation.
1
Response for beeper activated. The response is ASCII 1 if the beeper is activated or an
ASCII 0 if the beeper is deactivated.
3.2.2 Error Query
Syntax
SYSTem:ERRor[:NEXT]?
Description
The SYSTem:ERRor[:NEXT]? command queries the instrument's error queue. This is a query-
only command. For a detailed list of possible error codes see chapter SCPI Error Messages .
22
16
16
17
17
17
81

© 2015 Thorlabs
3 Commands by Subsystem
17
Example
SYST:ERR?
Query the error queue.
+0,"No error"
Typical response.
3.2.3 Line Frequency
Syntax
SYSTem:LFRequency {50|60|AUTO}
SYSTem:LFRequency:ACTual?
SYSTem:LFRequency?
Description
The SYSTem:LFRequency sets the line frequency to use for signal filtering to the given value or
to automatic detection.
With the SYSTem:LFRequency:ACTual? query the actual used value can be retrieved.
The SYSTem:LFRequency? query returns the line frequency setting.
Example
SYST:LFR 50
Sets the line frequency setting to 50Hz.
SYST:LFR:ACT?
Queries the actual used line frequency.
60
Typical response.
3.2.4 SCPI Version Query
Syntax
SYSTem:VERSion?
Description
The SYSTem:VERSion? command queries the level of the SCPI standard implemented. This is
a query–only command.
Example
SYST:VERS?
Query the SCPI version.
1999.0
Typical response.

© 2015 Thorlabs18
Series 4000 SCPI Programmers Reference Manual
3.3 Measurement Commands
Table <%TABLENO++%>: Measurement Commands for a TED4000 Series Instrument
Command
Description
ABORt
Aborts the current measurement
CONFigure[:SCALar]
[:TEMPerature]
Configures instrument for temperature measurement
:CURRent[1][:DC]
Configures instrument for TEC current measurement
:VOLTage[1][:DC]
Configures instrument for TEC voltage measurement
:POWer[1]
Configures instrument for TEC power measurement
:TSENsor
Configures for sensor signal measurement
CONFigure?
Returns the current configuration
INITiate[:IMMediate]
Starts measurement
FETCh?
Returns the last measurement data. The data returned is the data
configured with the last
CONFigure[:SCALar] or the last
MEASure[:SCALar] command
FETCh
:TEMPerature?
Returns the last measured temperature
:CURRent[1][:DC]?
Returns the last measured TEC current
:VOLTage[1][:DC]?
Returns the last measured TEC voltage
:POWer[1]?
Returns the last measured TEC power
:TSENsor?
Returns the last measured sensor signal
READ?
Starts new measurement and returns data
MEASure[:SCALar]
[:TEMPerature]?
Measures temperature
:CURRent[1][:DC]?
Measures TEC current
:VOLTage[1][:DC]?
Measures TEC voltage
:POWer[1]?
Measures TEC power
:TSENsor?
Measures sensor signal
22
22
22
24
24
24
26
26