I-Tech IT8800 Series Operating instructions

Programmable DC Electronic
Load
Series IT8800 Programming Guide
Model: IT8811/IT8812/IT8812B/IT8812C
IT8813/IT8813B/IT8813C/IT8814/IT8814B/
IT8814C/IT8816/IT8816B/IT8816C/IT8817/
IT8817B/IT8817C/IT8818/IT8818B/IT8818C/
IT8818D/IT8830/IT8830B/IT8830H/IT8831/
IT8831B/IT8831H/IT8832/IT8832B/IT8832H/
IT8833/IT8833B/IT8833H/IT8834B/IT8834H/
IT8835B/IT8835H/IT8836B/IT8836H/IT8837B/
IT8837H/IT8838B/IT8838H/IT8839B/IT8839H
Revision: V2.0

Statement
© Itech Electronic, Co., Ltd. 2018
No part of this manual may be
reproduced in any form or by any means
(including electronic storage and
retrieval or translation into a foreign
language) without prior permission and
written consent from Itech Electronic,
Co., Ltd. as governed by international
copyright laws.
Manual Article No.
IT8800-402159
Revision
Revision 2, published on
Nov. 20, 2018
Itech Electronic, Co., Ltd.
Trademark Statement
Pentium is a registered trademark of
Intel Corporation in the United States.
Microsoft, Visual Studio, Windows and
MS Windows are trademarks of
Microsoft Corporation in the United
States and/or other countries/regions.
Guarantee
Materials in the document are provided
talis qualis and may be changed in
future revisions without prior notice. In
addition, within the maximum allowable
extent of laws, ITECH is not committed
to any explicit or implied guarantee for
this manual and all information therein,
including but not limited to the implied
guarantee on marketability and
availability for some special purposes.
ITECH shall not be responsible for any
error or incidental or indirect losses
caused by the provision, use or
application of this documents and
information therein. If some guarantee
clauses in other written agreements
between ITECH and users are not
consistent with clauses herein, those
clauses in other written agreements
shall prevail.
Technology license
Hardware and/or software in this
document cannot be provided without a
license and can only be used or copied
according to the license.
Restricted permission statement
Restricted permissions of the U.S.
government. Permissions for software
and technical data which are authorized
to the U.S. Government only include
those for custom provision to end users.
ITECH follows FAR 12.211 (technical
data), 12.212 (computer software).
DFARS 252.227-7015 (technical
data--commercial products) for national
defense and DFARS 227.7202-3
(permissions for commercial computer
software or computer software
documents) while providing the
customized business licenses of
software and technical data.
Safety Statement
“Caution” signs indicate danger. It is
required to pay attention to the contents
of these signs during implementation of
operations.
The damage to the product or loss of
important data may be caused in case of
improper operation steps or failure to
follow operation steps. Do not continue
to implement any improper operation
indicated in “Caution” signs when the
specified conditions are not fully
understood or these conditions are not
satisfied.
“Warning” indicates danger. It is
required to pay attention to the contents
of these signs during implementation of
operation steps. Personal casualties
may be caused in case of improper
operation steps or failure to follow these
operation steps. Do not continue to
implement any improper operation
indicated in “Warning” signs when the
specified conditions are not fully
understood or these conditions are not
satisfied.
NOTE
“Instructions” indicates operation
instructions. It is required to refer to the
contents of these signs during operation
steps. These signs are used for
providing tips or supplementary
information for operators.

IT8800 Programming Guide
Copyright © ITECH Electronic Co., Ltd. i
Certification and Quality Assurance
IT8800 series electronic load completely reaches nominal technical indicators
in the manual.
Warranty service
ITECH Company will provide one-year warranty services for the product
materials and manufacturing (excluding the following limitations).
When warranty service or repair is needed, please send the product to the
service unit specified by ITECH Company.
When the product is sent to ITECH Company for warranty service, the
customer must pay the one-way freight to the maintenance department of
ITECH, and ITECH will be responsible for return freight.
If the product is sent to ITECH for warranty service from other countries,
the customer will be responsible for all the freight, duties and other taxes.
Limitation of Warranty
Warranty service does not apply to the damage caused in the following
circumstances:
Damage resulting from customer-wired circuits or customer-supplied parts
or accessories;
Product which has been modified or repaired by the customer;
Damage caused by the circuit installed by the customer or damage caused
by operation of the product in non-specified environment;
The product model or serial number is altered, deleted, removed or made
illegible by customer;
Damage caused by accidents, including but not limited to lightning, water,
fire, abuse or negligence.
Safety signs
DC power
ON (with the power
switched on)
AC power
OFF (with the power
supply switched off)
Both DC and AC power supply
Power supply
switching-on status
Protective grounding terminal
Power supply
switching-off status
Grounding terminal
Reference terminal
Danger sign
Positive terminal
Warning sign (refer to specific
“Warning” or “Caution”
information in the manual)
Negative terminal
Ground wire connection end
sign
-
-

IT8800 Programming Guide
Copyright © ITECH Electronic Co., Ltd. ii
Safety Precautions
General safety precautions below must be followed in each phase of instrument
operation. In case of failure to follow these precautions or specific warnings in
other parts of the manual, violation against the safety standards related to the
design, manufacture and purpose of the instrument will occur. If the user does
not follow these precautions, ITECH will bear no responsibility arising there
from.
Working voltage of IT8800 series includes 110V/220V. To prevent burnout,
be sure to check whether the AC voltage setting of electronic load is
consistent to the supply voltage before start-up!
The electronic load is provided with a three-core power line during delivery
and should be connected to a three-core junction box. Before operation, be
sure that the electronic load is well grounded.
Use electric wires of appropriate load. All loading wires should be capable
of bearing maximum short-circuit of electronic load without overheating.
Ensure the voltage fluctuation of mains supply is less than 10% of the
working voltage range in order to reduce risks of fire and electric shock.
To prevent burnout, please pay special attention to positive and negative
polarities of electronic load during connection!
Do not use damaged equipment. Please check the housing before using
the equipment. Check whether the instrument is subject to cracking or is
lack of plastic. Do not operate the instrument in the environment with
explosive gas, steam or dust.
Observe all tags on the equipment before connection.
Do not install alternative parts on the instrument or perform any
unauthorized modification.
Do not use the equipment when the removable cover is dismantled or
loose.
Please use the power adapter supplied by the manufacturer to avoid
accidental injury.
Do not use the equipment on the life support system or other equipment
with safety requirements.
If the equipment is not used in the manner specified by the manufacturer,
its protection may be damaged.
Always use dry cloth to clean the equipment housing. Do not clean the
inside of the instrument.
Do not block the air vent of the equipment.
Environmental conditions
The IT8800 series electronic load can only be used indoors or in low
condensation areas. The following table shows general environmental
requirements for this instrument.
Environmental conditions
Requirement
Operating temperature
0°C～40°C
0°C - 40°C
Operating humidity
20% - 80% (non condensing)
Storage temperature
-20°C - 70 °C

IT8800 Programming Guide
Copyright © ITECH Electronic Co., Ltd. iii
Altitude
≤2,000m
Pollution
Grade 2 pollution
Note
In order to ensure the accuracy of measurement, it is recommended to operate the
instrument half an hour after start-up.
Regulation tag
The CE tag shows that the product
complies with the provisions of all relevant
European laws (if the year is shown, it
indicates that the year when the design is
approved).
This instrument complies with the WEEE
directive (2002/96/EC) tag requirements.
This attached product tag shows that the
electrical/electronic product cannot be
discarded in household waste.
This symbol indicates that no danger will
happen or toxic substances will not leak or
cause damage in normal use within the
specified period. The service life of the product
is 10 years. The product can be used safely
within the environmental protection period;
otherwise, the product should be put into the
recycling system.
Waste electrical and electronic equipment (WEEE)
directive
Waste electrical and electronic equipment (WEEE)
directive, 2002/96/EC
The product complies with tag requirements of the
WEEE directive (2002/96/EC). This tag indicates that the
electronic equipment cannot be disposed of as ordinary
household waste.
Product Category
According to the equipment classification in Annex I of
the WEEE directive, this instrument belongs to the
“Monitoring” product.
If you want to return the unnecessary instrument,
please contact the nearest sales office of ITECH.

IT8800 Programming Guide
Copyright © ITECH Electronic Co., Ltd. iv
Compliance Information
Complies with the essential requirements of the following applicable European
Directives, and carries the CE marking accordingly:
Electromagnetic Compatibility (EMC) Directive 2014/30/EU
Low-Voltage Directive (Safety) 2014/35/EU
Conforms with the following product standards:
EMC Standard
IEC 61326-1:2012/ EN 61326-1:2013 ¹²³
Reference Standards
CISPR 11:2009+A1:2010/ EN 55011:2009+A1:2010 (Group 1, Class A)
IEC 61000-4-2:2008/ EN 61000-4-2:2009
IEC 61000-4-3:2006+A1:2007+A2:2010/ EN 61000-4-3:2006+A1:2008+A2:2010
IEC 61000-4-4:2004+A1:2010/ EN 61000-4-4:2004+A1:2010
IEC 61000-4-5:2005/ EN 61000-4-5:2006
IEC 61000-4-6:2008/ EN 61000-4-6:2009
IEC 61000-4-11:2004/ EN 61000-4-11:2004
1. The product is intended for use in non-residential/non-domestic environments. Use of the
product in residential/domestic environments may cause electromagnetic interference.
2. Connection of the instrument to a test object may produce radiations beyond the specified
limit.
3. Use high-performance shielded interface cable to ensure conformity with the EMC standards
listed above.
Safety Standard
IEC 61010-1:2010/ EN 61010-1:2010

IT8800 Programming Guide
Copyright © ITECH Electronic Co., Ltd. v
Contents
Certification and Quality Assurance...........................................................................................................................i
Warranty service.........................................................................................................................................................i
Limitation of Warranty...............................................................................................................................................i
Safety signs ................................................................................................................................................................i
Safety Precautions .....................................................................................................................................................ii
Environmental conditions..........................................................................................................................................ii
Regulation tag...........................................................................................................................................................iii
Waste electrical and electronic equipment (WEEE) directive..................................................................................iii
Compliance Information...........................................................................................................................................iv
Chapter1 Remote Control................................................................................................................................1
1.1 Overview.............................................................................................................................................................1
1.2 SCPI Command Introduction ..............................................................................................................................1
1.3 Command Type of SCPI .....................................................................................................................................1
1.4 Command Format................................................................................................................................................3
1.5 Data Type............................................................................................................................................................5
1.6 Response Data Type............................................................................................................................................6
1.7 Message Type of SCPI........................................................................................................................................7
1.8 SCPI Command Complete ..................................................................................................................................8
1.9 Remote Operation................................................................................................................................................9
1.10 Queue ..............................................................................................................................................................11
1.11 Status byte and service request (SRQ).............................................................................................................12
1.12 Serial poll and SRQ.........................................................................................................................................13
1.13 Trigger Model (GPIB Operation)....................................................................................................................13
Chapter2 SCPI Register.................................................................................................................................15
2.1 Status Register...................................................................................................................................................15
2.2 Condition register..............................................................................................................................................17
2.3 Event register.....................................................................................................................................................17
2.4 Enable register...................................................................................................................................................18
Chapter3 IEEE488.2 Commands..................................................................................................................19
*CLS —Clear Status ..............................................................................................................................................20
*ESE <NRf> —Event Enable ................................................................................................................................20
*ESR?......................................................................................................................................................................20
*IDN?......................................................................................................................................................................20
*OPC.......................................................................................................................................................................21
*PSC........................................................................................................................................................................21
*RCL.......................................................................................................................................................................22
*RST .......................................................................................................................................................................22
*SAV.......................................................................................................................................................................22
*SRE .......................................................................................................................................................................22
*STB?......................................................................................................................................................................23
*TRG.......................................................................................................................................................................23
*TST?......................................................................................................................................................................23
*WAI.......................................................................................................................................................................24
Chapter4 Essential Commands .....................................................................................................................25
STATus:QUEStionable? .........................................................................................................................................25
STATus:QUEStionable:ENABle ............................................................................................................................25
STATus:QUEStionable:PTRansition ......................................................................................................................25
STATus:QUEStionable:NTRansition .....................................................................................................................26
STATus:QUEStionable:CONDition?......................................................................................................................26
STATus:OPERation? ..............................................................................................................................................26
STATus:OPERation:ENABle .................................................................................................................................26
STATus:OPERation:CONDition?...........................................................................................................................27
STATus:PRESet......................................................................................................................................................27
Chapter5 System Commands ........................................................................................................................28
SYSTem:PRESet.....................................................................................................................................................28
SYSTem:POSetup...................................................................................................................................................28
SYSTem:VERSion? ................................................................................................................................................28

IT8800 Programming Guide
Copyright © ITECH Electronic Co., Ltd. vi
SYSTem:ERRor? ....................................................................................................................................................28
SYSTem:CLEar.......................................................................................................................................................29
SYSTem:LOCal ......................................................................................................................................................29
SYSTem:REMote....................................................................................................................................................29
SYSTem:RWLock...................................................................................................................................................29
SYSTem:KEY.........................................................................................................................................................29
DISPlay[:WINDow]:MODE ...................................................................................................................................30
DISPlay[:WINDow]:TEXT.....................................................................................................................................30
Chapter6 Measure Commands......................................................................................................................31
FETCh:VOLTage[:DC]?.........................................................................................................................................31
FETCh:VOLTage:MAX?........................................................................................................................................31
FETCh:VOLTage:MIN? .........................................................................................................................................31
FETCh:CURRent[:DC]? .........................................................................................................................................32
FETCh:CURRent:MAX? ........................................................................................................................................32
FETCh:CURRent:MIN?..........................................................................................................................................32
FETCh:POWer[:DC]?.............................................................................................................................................33
FETCh:CAPability? ................................................................................................................................................33
FETCh:TIME?.........................................................................................................................................................33
MEASure:VOLTage[:DC]? ....................................................................................................................................34
MEASure:VOLTage:MAX? ...................................................................................................................................34
MEASure:VOLTage:MIN?.....................................................................................................................................34
MEASure:CURRent[:DC]?.....................................................................................................................................34
MEASure:CURRent:MAX?....................................................................................................................................35
MEASure:CURRent:MIN? .....................................................................................................................................35
MEASure:POWer[:DC]?.........................................................................................................................................35
MEASure:CAPability?............................................................................................................................................36
MEASure:TIME?....................................................................................................................................................36
Chapter7 Trigger Subsystem.........................................................................................................................37
TRIGger ..................................................................................................................................................................37
TRIGger:SOURce ...................................................................................................................................................37
TRIGger:TIMer.......................................................................................................................................................37
Chapter8 Trace Subsystem............................................................................................................................39
TRACe:CLEar.........................................................................................................................................................39
TRACe:FREE?........................................................................................................................................................39
TRACe:POINts .......................................................................................................................................................39
TRACe:FEED .........................................................................................................................................................39
TRACe:FEED:CONTrol.........................................................................................................................................40
TRACe:DATA?.......................................................................................................................................................40
TRACe:FILTer........................................................................................................................................................40
TRACe:DELay........................................................................................................................................................40
TRACe:TIMer.........................................................................................................................................................40
Chapter9 Source Subsystem..........................................................................................................................42
[SOURce:]INPut .....................................................................................................................................................42
[SOURce:]INPut:SHORt.........................................................................................................................................42
[SOURce:]INPut:TIMer..........................................................................................................................................42
[SOURce:]INPut:TIMer:DELay .............................................................................................................................42
[SOURce:]REMote:SENSe.....................................................................................................................................43
[SOURce:]FUNCtion ..............................................................................................................................................43
[SOURce:]FUNCtion:MODE .................................................................................................................................43
[SOURce:]TRANsient.............................................................................................................................................43
[SOURce:]PROTection:CLEar ...............................................................................................................................44
[SOURce:]CURRent ...............................................................................................................................................44
[SOURce:]CURRent:RANGe .................................................................................................................................44
[SOURce:]CURRent:SLEW ...................................................................................................................................45
[SOURce:]CURRent:SLEW:POSitive....................................................................................................................45
[SOURce:]CURRent:SLEW:NEGative ..................................................................................................................45
[SOURce:]CURRent:SLEWrate:STATe.................................................................................................................46
[SOURce:]CURRent:PROTection:STATe..............................................................................................................46
[SOURce:]CURRent:PROTection ..........................................................................................................................46

IT8800 Programming Guide
Copyright © ITECH Electronic Co., Ltd. vii
[SOURce:]CURRent:PROTection:DELay..............................................................................................................46
[SOURce:]CURRent:TRANsient:MODE...............................................................................................................47
[SOURce:]CURRent:TRANsient:ALEVel .............................................................................................................47
[SOURce:]CURRent:TRANsient:BLEVel..............................................................................................................47
[SOURce:]CURRent:TRANsient:AWIDth.............................................................................................................47
[SOURce:]CURRent:TRANsient:BWIDth.............................................................................................................47
[SOURce:]CURRent:HIGH ....................................................................................................................................48
[SOURce:]CURRent:LOW.....................................................................................................................................48
[SOURce:]VOLTage...............................................................................................................................................48
[SOURce:]VOLTage:RANGe.................................................................................................................................48
[SOURce:]VOLTage:RANGe:AUTO[:STATe].....................................................................................................49
[SOURce:]VOLTage:ON........................................................................................................................................49
[SOURce:]VOLTage:LATCh .................................................................................................................................49
[SOURce:]VOLTage:TRANsient:MODE...............................................................................................................49
[SOURce:]VOLTage:TRANsient:ALEVel.............................................................................................................50
[SOURce:]VOLTage:TRANsient:BLEVel .............................................................................................................50
[SOURce:]VOLTage:TRANsient:AWIDth ............................................................................................................50
[SOURce:]VOLTage:TRANsient:BWIDth.............................................................................................................50
[SOURce:]VOLTage:HIGH....................................................................................................................................51
[SOURce:]VOLTage:LOW.....................................................................................................................................51
[SOURce:]RESistance.............................................................................................................................................51
[SOURce:]RESistance:RANGe...............................................................................................................................51
[SOURce:]RESistance:TRANsient:MODE ............................................................................................................51
[SOURce:]RESistance:TRANsient:ALEVel...........................................................................................................52
[SOURce:]RESistance:TRANsient:BLEVel...........................................................................................................52
[SOURce:]RESistance:TRANsient:0 ......................................................................................................................52
[SOURce:]RESistance:TRANsient:BWIDth ..........................................................................................................52
[SOURce:]RESistance:HIGH..................................................................................................................................53
[SOURce:]RESistance:LOW ..................................................................................................................................53
[SOURce:]RESistance:VDRop ...............................................................................................................................53
[SOURce:]RESistance:LATCh[:STATe]................................................................................................................53
[SOURce:]POWer...................................................................................................................................................53
[SOURce:]POWer:RANGe.....................................................................................................................................54
[SOURce:]POWer:TRANsient:MODE...................................................................................................................54
[SOURce:]POWer:TRANsient:ALEVel.................................................................................................................54
[SOURce:]POWer:TRANsient:BLEVel .................................................................................................................54
[SOURce:]POWer:TRANsient:AWIDth.................................................................................................................55
[SOURce:]POWer:TRANsient:BWIDth.................................................................................................................55
[SOURce:]POWer:HIGH........................................................................................................................................55
[SOURce:]POWer:LOW.........................................................................................................................................55
[SOURce:]POWer:PROTection..............................................................................................................................55
[SOURce:]POWer:PROTection:DELay..................................................................................................................56
[SOURce:]POWer:CONFig ....................................................................................................................................56
Chapter10 List Commands..............................................................................................................................57
[SOURce:]LIST:RANGe ........................................................................................................................................57
[SOURce:]LIST:COUNt.........................................................................................................................................57
[SOURce:]LIST:STEP............................................................................................................................................57
[SOURce:]LIST:LEVel? .........................................................................................................................................57
[SOURce:]LIST:SLEW...........................................................................................................................................58
[SOURce:]LIST:WIDth ..........................................................................................................................................58
[SOURce:]LIST:SAV .............................................................................................................................................58
[SOURce:]LIST:RCL..............................................................................................................................................58
Chapter11 Sense Subsystem ............................................................................................................................59
SENSe:AVERage:COUNt ......................................................................................................................................59
SENSe:TIME:VOLTage1 .......................................................................................................................................59
SENSe:TIME:VOLTage2 .......................................................................................................................................59
SYSTem:SENSe[:STATe] <BOOL>......................................................................................................................59
Chapter12 Calibration Commands.................................................................................................................61
CALibrate:SECure[:STATe]...................................................................................................................................61
CALibrate:INITial...................................................................................................................................................61

IT8800 Programming Guide
Copyright © ITECH Electronic Co., Ltd. viii
CALibrate:SAVe.....................................................................................................................................................61
CALibrate:CURRent:POINt....................................................................................................................................61
CALibrate:CURRent[:LEVel].................................................................................................................................62
CALibrate:CURRent:METEr:POINt ......................................................................................................................62
CALibrate:CURRent:METEr[:LEVel] ...................................................................................................................62
CALibrate:VOLTage:POINt...................................................................................................................................62
CALibrate:VOLTage[:LEVel] ................................................................................................................................63
CALibrate:VOLTage:METEr:POINt......................................................................................................................63
CALibrate:VOLTage:METEr[:LEVel]...................................................................................................................63
Chapter13 Error Information .........................................................................................................................64

Remote Control
Copyright © ITECH Electronic Co., Ltd. 1
Chapter1 Remote Control
1.1 Overview
This chapter will provide following remote configuration introductions:
SCPI Command Introduction
Command type
Command format
Data format
Remote Operation
1.2 SCPI Command Introduction
SCPI is short for Standard Commands for Programmable Instruments which
defines a communication method of bus controller and instrument. It is based
on ASCII and supply for testing and measuring instruments. SCPI command is
based on hierarchical architecture which also known as tree system. In this
system, Relevant Command is returned to a common node or root, so that a
subsystem is formed.
A part of OUTPut subsystem is listed below:
OUTPut:
SYNC {OFF|0|ON|1}
SYNC:
MODE {NORMal|CARRier}
POLarity {NORMal|INVerted}
OUTPut is the root class keyword, SYNC is the second keyword, MODE and
POLarity are the third keyword. Colon(:) is used for separating the command
keyword and the next level keyword.
1.3 Command Type of SCPI
SCPI has two types of commands, common and subsystem.
Common commands generally are not related to specific operation but to
controlling overallelectronic load functions, such as reset, status, and
synchronization. All commoncommands consist of a three-letter mnemonic
preceded by an asterisk: *RST *IDN? *SRE 8.
Subsystem commands perform specific electronic load functions. They are
organized into an inverted tree structure with the "root" at the top. The
following figure shows a portion of a subsyste command tree, from which
you access the commands located along the various paths.

Remote Control
Copyright © ITECH Electronic Co., Ltd. 2
Multiple commands in a message
Multiple SCPI commands can be combined and sent as a single
message with one message terminator. There are two important
considerations when sending several commands within a single
message:
Use a semicolon to separate commands within a message.
Head paths influence how the instrument interprets commands.
We consider the head path as a string which will be inserted in front of
every command of a message.As for the first command of a message,
the head path is a null string; for each subsequent command, the head
path is a string which is defined to form the current command until and
including the head of the last colon separator. Amessage with two
combined commands: CURR:LEV 3;PROT:STAT OFF
The example indicates the effect of semicolon and explains the concept
of head path. Since the head path is defined to be "CURR" after "curr: lev
3", the head of the second command, "curr", is deleted and the
instrument explains the second command as: CURR:PROT:STAT OFF
If "curr" is explicitly included in the second command, it is semantically
wrong. Since combining it with the head path will become
"CURR:CURR:PROT:STAT OFF", resulting in wrong command.
Movement in the subsystem
In order to combine commands from different subsystems, you need to
be able to reset the header path to a null string within a message. You do
this by beginning the command with a colon (:), which discards any
previous header path. For example, you could clear the output protection
and check the status of the Operation Condition register in one message
by using a root specifier as follows:
PROTection:CLEAr;:STATus:OPERation:CONDition?
The following message shows how to combine commands from different
subsystems as well as within the same subsystem:
POWer:LEVel 200;PROTection 28; :CURRent:LEVel 3;PROTection:STATe ON
Note the use of the optional header LEVel to maintain the correct path
within the voltage and current subsystems, and the use of the root
specifier to move between subsystems.
Including Common Commands
You can combine common commands with subsystem commands in the
same message. Treat the common command as a message unit by
separating it with a semicolon (the message unit separator). Common
commands do not affect the header path; you may insert them anywhere
in the message.
VOLTage:TRIGgered 17.5;:INITialize;*TRG
OUTPut OFF;*RCL 2;OUTPut ONIT872X-3X SCPI Communication protocol 17
Case sensitivity
Common commands and SCPI commands are not case sensitive. You
can use upper or lower, for example:

Remote Control
Copyright © ITECH Electronic Co., Ltd. 3
*RST = *rst
:DATA? = :data?
:SYSTem:PRESet = :system:preset
Long-form and short-form versions
A SCPI command word can be sent in its long-form or short-form version.
The long-form version are listed in the following chapters. However, the
short-form version is indicated by upper case characters. Examples:
:SYSTem:PRESet long-form
:SYST:PRES short form
:SYSTem:PRES long-form and short-form combination
Note that each command word must be in long-form or short-form, and
not something in between.
For example, :SYSTe:PRESe is illegal and will generate an error. The
command will not be executed.
Query Observe the following precautions with queries:
Set up the proper number of variables for the returned data. For example, if
you are reading back a measurement array, you must dimension the array
according to the number of measurements that you have placed in the
measurement buffer.
Read back all the results of a query before sending another command to
the electronic load. Otherwise a Query Interrupted error will occur and the
unreturned data will be lost.
1.4 Command Format
Formats for command display are as follows:
[SOURce[1|2]:]VOLTage:UNIT {VPP|VRMS|DBM}
[SOURce[1|2]:]FREQuency:CENTer
{<frequency>|MINimum|MAXimum|DEFault}
Based on the command syntax, most commands (and certain Parameter) are
expressed in both upper and lower cases. Upper case refers to abbreviation of
commands. Shorter program line may send commands in abbreviated format.
Long-format commands may be sent to ensure better program readability.
For example, both formats of VOLT and VOLTAGE are acceptable in the above
syntax statements. Upper or lower case may be used. Therefore, formats of
VOLTAGE, volt and Volt are all acceptable. Other formats (such as VOL and
VOLTAG) are invalid and will cause errors.
Parameter options with given command strings are included in the brace
({ }). The brace is not sent along with command strings.
Vertical stripes (|) separate several parameter options with given command
strings. For example, {VPP|VRMS|DBM} indicates that you may assign
"APP", "VRMS" or "DBM" in the above commands. Vertical stripes are not
sent along with command strings.
Angle brackets (< >) in the second example indicates that a value must be
assigned to the parameter in the brace. For example, the parameter in the
angle bracket is <frequency> in the above syntax statements. Angle
brackets are not sent along with command strings. You must assign a value

Remote Control
Copyright © ITECH Electronic Co., Ltd. 4
(such as "FREQ:CENT 1000") to the parameter, unless you select other
options displayed in the syntax (such as "FREQ:CENT MIN").
Some syntax elements (such as nodes and Parameter) are included in
square brackets ([ ]). It indicates that these elements can be selected and
omitted. Angle brackets are not sent along with command strings. If no
value is assigned to the optional Parameter, the instrument will select a
default value. In the above examples, "SOURce[1|2]" indicates that you
may refer to source channel 1 by "SOURce" or "SOURce1" or "SOUR1" or
"SOUR". In addition, since the whole SOURce node is optional (in the
square bracket), you can refer to the channel 1 by omitting the whole
SOURce node. It is because the channel 1 is the default channel for
SOURce language node. On the other hand, if you want to refer to channel
2, "SOURce2" or "SOUR2" must be used in the program line.
Colon (:) It is used to separate key words of a command with the key words in next level.
As shown below:
APPL:SIN 455E3,1.15,0.0
In this example, APPLy command assigns a sine wave with frequency of 455
KHz, amplitude of 1.15 V and DC offset of 0.0 V.
Semicolon (;) It is used to separate several commands in the same subsystem and can also
minimize typing. For example, to send the following command string:
TRIG:SOUR EXT; COUNT 10
has the same effect as sending the following two commands:
TRIG:SOUR EXT
TRIG:COUNT 10
Question mark (?)
You can insert question marks into a command to query current values of most
Parameter. For example, the following commands will trigger to set the count as
10:
TRIG:COUN 10
Then, you may query count value by sending the following command:
TRIG:COUN?
You may also query the allowable minimum or maximum count as follows:
TRIG:COUN?MIN
TRIG:COUN?MAX
Comma (,) If a command requires several parameter, then a comma must be used to
separate adjacent parameter.
Space You must use blank characters, [TAB] or [Space] to separate Parameter with
key words of commands.
Generic commands (*)
Execute functions like reset, self inspection and status operation. Generic

Remote Control
Copyright © ITECH Electronic Co., Ltd. 5
commands always start with a asterisk (*) and occupy 3 character sizes,
including one or more Parameter. Key words of a command and the first
parameter are separated by a space. Semicolon (;) can separate several
commands as follows:
*RST; *CLS; *ESE 32; *OPC?
Command terminator
Command strings sent to the instrument must end with a <Newline> (<NL>)
character. IEEE-488 EOI (End or Identify) information can be used as <NL>
character to replace termination command string of <NL> character. It is
acceptable to place one <NL> after a <Enter>. Termination of command string
always resets current SCPI command path to root level.
Note
As for every SCPI message with one query sent to the instrument, the instrument will
use a <NL> or newline sign (EOI) to terminate response of return. For example, if
"DISP:TEXT?" is sent, <NL> will be placed after the returned data string to terminate
response. If an SCPI message includes several queries separated by semicolon
(such as "DISP?;DISP:TEXT?"), <NL> will terminate response returned after
response to the last query. In all cases, the program must read <NL> in response
before another command is sent to the instrument, otherwise errors will be caused.
1.5 Data Type
SCPI language defines several data types used for program message and
response messages.
Numerical parameter
Commands requiring numerical Parameter support the notations of all common
decimal notations, including optional signs, decimal points, scientific notation,
etc. Special values of numerical Parameter are also acceptable, such as MIN,
MAX and DEF. In addition, suffixes for engineering units can also be sent
together with numerical Parameter (including M, k, m or u). If the command
accepts only some specific values, the instrument will automatically round the
input Parameter to acceptable values. The following commands require
numerical Parameter of frequency value:
[SOURce[1|2]:]FREQuency:CENTer {<Frequency>|MINimum|MAXimum}
Discrete parameter
Discrete Parameter are used for settings with limited number of programming
values (such as IMMediate, EXTernal or BUS). They can use short and long
format like key words of commands. They may be expressed in both upper and
lower case. The query response always returns uppercase Parameter in short
format. The following commands require discrete Parameter in voltage unit:
[SOURce[1|2]:]VOLTage:UNIT {VPP|VRMS|DBM}
Boolean parameter
Boolean Parameter refer to true or false binary conditions. In case of false
conditions, the instrument will accept "OFF" or "0". In case of true conditions,
the instrument will accept "ON" or "1". In query of Boolean settings, the
instrument will always return "0" or "1". Boolean Parameter are required by the
following commands:
DISPlay {OFF|0|ON|1}
ASCII string Parameter
String Parameter may actually include allASCII character sets. Character
strings must start and end with paired quotation marks; and single quotation
marks or double quotation marks are both allowed. Quotation mark separators

Remote Control
Copyright © ITECH Electronic Co., Ltd. 6
may also act as one part of a string, they can be typed twice without any
character added between them. String parameter is used in the following
command:
DISPlay:TEXT <quoted string>
For example, the following commands display message of "WAITING..."
(without quotation marks) on the front panel of the instrument.
DISP:TEXT "WAITING..."
Single quotation marks may also be used to display the same message.
DISP:TEXT 'WAITING...'
1.6 Response Data Type
Character strings returned by query statements may take either of the following
forms, depending on the length of the returned string:
<CRD>
Character Response Data. Permits the return of character strings.
<AARD>
Arbitrary ASCII Response Data. Permits the return of undelimited 7-bit
ASCII. This data type has an implied message terminator.
<SRD>
String Response Data. Returns string parameters enclosed in double
quotes
Response messages
A response message is the message sent by the instrument to the computer in
response to aquery command.
Sending a response message
Afte sending a query command, the response message is placed in the Output
Queue. When the IT8800 Series is then addressed to talk, the response
message is sent from the Output Queue to the computer.
Multiple response messages
If you send more than one query command in the same program message (see
the paragraph entitled, “Multiple Command Messages”), the multiple response
messages for all the queries is sent to the computer when the IT8800 Series is
addressed to talk. The responses are sent in the order that the query
commands were sent and are separated by semicolons (;). Items within the
same query are separated by commas (,). The following example shows the
response message for a program message that contains four single item query
commands:
0; 1; 1; 0
Response message terminator (RMT)
Each response is terminated with an LF (line feed) and EOI (end or identify).
The following example shows how a multiple response message is terminated:
0; 1; 1; 0; <RMT>
Message exchange protocol
Two rules summarize the message exchange protocol:
Rule 1.You must always tell the IT8800 Series what to send to the computer.
The following two steps must always be performed to send information from the
instrument other computer:

Remote Control
Copyright © ITECH Electronic Co., Ltd. 7
1. Send the appropriate query command(s) in a program message.1.
2. Address the IT8800 Series to talk.
Rule 2.The complete response message must be received by the computer
before another program message can be sent to the IT8800 Series.
1.7 Message Type of SCPI
There are two types of SCPI messages, program and response.
Program message: A program message consists of one or more properly
formatted SCPI commands sent from the controller to the electronic load.
The message, which may be sent at any time, requests the electronic load
to perform some action.
Response message: A response message consists of data in a specific
SCPI format sent from the electronic load to the controller. The electronic
load sends the message only when commanded by a program message
called a "query."
The next figure illustrates SCPI message structure:
The Message Unit
The simplest SCPI command is a single message unit consisting of a command
header (or keyword) followed by a message terminator. The message unit may
include a parameter after the header. The parameter can be numeric or a
string.
VOLTage 20<NL>
Headers Headers, also referred to as keywords, are instructions recognized by the
electronic load. Headers may be either in the long form or the short form. In the
long form, the header is completely spelled out, such as VOLTAGE, STATUS,
and DELAY. In the short form, the header has only the first three or four letters,
such as VOLT, STAT, and DEL.
Query Indicator
Following a header with a question mark turns it into a query (VOLTage?,
VOLTage:PROTection?). If a query contains a parameter, place the query
indicator at the end of the last header(VOLTage:PROTection?MAX).

Remote Control
Copyright © ITECH Electronic Co., Ltd. 8
Message Unit Separator
When two or more message units are combined into a compound message,
separate the units with a semicolon (STATus:OPERation?;QUEStionable?).
Root Specifier When it precedes the first header of a message unit, the colon becomes the
root specifier. It tells the command parser that this is the root or the top node of
the command tree.
Message Terminator
A terminator informs SCPI that it has reached the end of a message. Three
permitted message terminators are:
newline (<NL>),decimal 10 or hexadecimal 0X0Ain ASCII.
end or identify (<END>)
both of the above (<NL><END>).
In the examples of this guide, there is an assumed message terminator at the
end of each message.
Command execution rules
Commands execute in the order that they are presented in the program
message.
An invalid command generates an error and, of course, is not executed.
Valid commands that precede an invalid command in a multiple command
program message are executed.
Valid commands that follow an invalid command in a multiple command
program message are ignored.
1.8 SCPI Command Complete
SCPI commands sent to the electronic load are processed either sequentially
or in parallel. Sequential commands finish execution before a subsequent
command begins. Parallel commands allow other commands to begin
executing while the parallel command is still executing. Commands that affect
trigger actions are among the parallel commands.
*WAI, *OPC, and *OPC:Common commands provide different ways of
indicating when all transmitted commands, including any parallel ones, have
completed their operations. Some practical considerations for using these
commands are as follows:
*WAI: This prevents the electronic load from processing subsequent commands
until all pending operations are completed.
*OPC?: This places a 1 in the Output Queue when all pending operations have
completed. Because it requires your program to read the returned value before
executing the next program statement, *OPC? can be used to cause the
controller to wait for commands to complete before proceeding with its
program.
*OPC: This sets the OPC status bit when all pending operations have
completed. Since your program can read this status bit on an interrupt basis,
*OPC allows subsequent commands to be executed.
Note
The trigger system must be in the Idle state in order for the status OPC bit to be true.

Remote Control
Copyright © ITECH Electronic Co., Ltd. 9
Therefore, as far as triggers are concerned, OPC is false whenever the trigger
system is in the Initiated state.
Using Device Clear
You can send a device clear at any time to abort a SCPI command that may be
hanging up the GPIB interface. The status registers, the error queue, and all
configuration states are left unchanged when a device clear message is
received. Device clear performs the following actions:
The input and output buffers of the electronic load are cleared.
The electronic load is prepared to accept a new command string.
The following statement shows how to send a device clear over the GPIB
interface using GW BASIC:
CLEAR 705 IEEE-488 Device Clear
The following statement shows how to send a device clear over the GPIB
interface using the GPIB command library for C or QuickBASIC.
IOCLEAR (705)
1.9 Remote Operation
IT8800 series electronic load is provided with three communication interfaces
to communicate with a computer for selection, including RS232, USB, and
GPIB.
GPIB function All electronic load functions except setting the communication parameters are
programmable over the GPIB. The IEEE 488.2 capabilities of the electronic
load are described in the following table.
GPIB Capabilities
Response
Interface
Function
Talker/Listener
All electronic load functions except for setting the communication
paraments are programmable over the GPIB. The electronic
load can send and receive messages over the GPIB. Status
information is sent using a serial poll.
AH1, SH1,AH1,
SH1,
T6, L4T6, L4
Service Request
The electronic load sets the SRQ line true if there is an enabled
service request condition.
SR1, SR1
Remote/Local
In local mode, the electronic load is controlled from the front
panel but will also execute commands sent over the GPIB.
If the electronic load is powered on in local mode, it remains in
local mode until it receives a command over the GPIB.
Once the electronic load is in remote mode the front panel REM
indicator is on, all front panel keys (exceptShift+7,Local and
Esc) are disabled, and the display is in normal metering mode.
Press Local on the front panel to returnto the local mode.
RL1
Device Trigger
The electronic load responds to the device triggers.
DT1
Group Execute
Trigger
The electronic load responds to the group execute triggers.
GETGET
Device Clear
The electronic load responds to the Device Clear (DCL) and
Selected Device Clear (SDC) interface commands. They
command the electronic load to clear any activity that would
prevent it from receiving and executing a new command
(including *WAI and *OPC?). DCL and SDC do not change any
programmed settings.
DCL,SDC

Remote Control
Copyright © ITECH Electronic Co., Ltd. 10
GPIB address
The electronic load operates from a GPIB address that is set from the front
panel. To set the GPIB address, press the Shift + System on the front panel
and enter the address using the keys. The address can be set from 0 to 30. The
GPIB address is stored in non-volatile memory.
RS-232 function
The electronic load provides an RS-232 programming interface, which can be
activated and set by pressing Shift + Systemon the front panel. All SCPI
commands are available through RS-232 programming. When the RS-232
interface is selected, The EIA RS-232 Standard defines the interconnections
between Data Terminal Equipment (DTE) and Data Communications
Equipment (DCE).The electronic load is designed to be a DTE. It can be
connected to another DTE such as a PC COM port through a null modem
cable.
Note
The RS-232 settings in your program must match the settings specified in the front
panel system menu. Press Shift + System to change the settings if they don’t match.
You can break data transmissions by sending a ^C or ^X character string to the
multimeter. This clears any pending operation and discards any pending output.
RS-232 data format
The RS-232 data is a 10-bit word with one start bit and one stop bit. The
number of start and stop bits is not programmable. However, the following
parity options are selectable after pressing Shift + System:
EVEN: Seven data bits with even parity
ODD: Seven data bits with odd parity
NONE:Eight data bits without parity
Parity options are stored in non-volatile memory.
Baud rate
After pressing Shift + System,you can select one of the following baud rates:
4800/9600/19200/38400/57600/115200
The baud rate is stored in the non-volatile memory.
RS-232 flow control
The RS-232 interface supports the following flow control:
CTS/RTS: the electronic load asserts its Request to Send (RTS) line to
signal hold-off when its input buffer is almost full, and it interprets its Clear
to Send (CTS) line as a hold-off signal from the controller.
XON/XOFF: when the input queue of the electronic load becomes more
than 3/4 full, the instrument issues an X_OFF command. The control
program should respond to this and stop sending characters until The
electronic load issues the X_ON, which it will do once its input buffer drops
to below half-full. The electronic load recognizes X_ON and X_OFF sent
from the controller. An X_OFF will cause the electronic load to stop
outputting characters until it sees an X_ON.
NONE: there is no flow control.
For each case, the electronic load will send a maximum of five characters after
hold-off is asserted by the controller. The electronic load is capable of receiving
as many as fifteen additional characters after it asserts hold-off.Flow control
options are stored in the non-volatile memory.