I-Tech IT-N2100 Series Operating instructions

Solar Array Simulator
IT-N2100 Series Programming Guide
Model: IT-N2100
Version: V1.0

Notices
© Itech Electronic, Co., Ltd. 2023
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 Part Number
IT-N2100
Revision
First Edition: May 30th,2023
Itech Electronic, Co., Ltd.
Trademarks
Pentium is U.S. registered trademarks
of Intel Corporation.
Microsoft, Visual Studio, Windows and
MS Windows are registered trademarks
of Microsoft Corporation in the United
States and/or other countries and
regions.
Warranty
The materials contained in this
document are provided “as is”, and
is subject to change, without prior
notice, in future editions. Further, to
the maximum extent permitted by
applicable laws, ITECH disclaims
all warrants, either express or
implied, with regard to this manual
and any information contained
herein, including but not limited to
the implied warranties of
merchantability and fitness for a
particular purpose. ITECH shall
not be held liable for errors or for
incidental or indirect damages in
connection with the furnishing, use
or application of this document or of
any information contained herein.
Should ITECH and the user enter
into a separate written agreement
with warranty terms covering the
materials in this document that
conflict with these terms, the
warranty terms in the separate
agreement shall prevail.
Technology Licenses
The hardware and/or software
described herein are furnished under a
license and may be used or copied only
in accordance with the terms of such
license.
Restricted Rights Legend
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 Notices
A CAUTION sign denotes a
hazard. It calls attention to an
operating procedure or practice
that, if not correctly performed
or adhered to, could result in
damage to the product or loss of
important data. Do not proceed
beyond a CAUTION sign until
the indicated conditions are fully
understood and met.
A WARNING sign denotes a
hazard. It calls attention to an
operating procedure or practice
that, if not correctly performed
or adhered to, could result in
personal injury or death. Do not
proceed beyond a WARNING
sign until the indicated
conditions are fully understood
and met.
NOTE
A NOTE sign denotes
important hint. It calls attention
to tips or supplementary
information that is essential for
users to refer to.

IT-N2100 Programming Guide
Copyright © Itech Electronic Co., Ltd. i
Quality Certification and Assurance
We certify that IT-N2100 series instruments meet all the published
specifications at time of shipment from the factory.
Warranty ITECH warrants that the product will be free from defects in material and
workmanship under normal use for a period of one (1) year from the date of
delivery (except those described in the Limitation of Warranty below).
For warranty service or repair, the product must be returned to a service center
designated by ITECH.
The product returned to ITECH for warranty service must be shipped
PREPAID. And ITECH will pay for return of the product to customer.
If the product is returned to ITECH for warranty service from overseas, all
the freights, duties and other taxes shall be on the account of customer.
Limitation of Warranty
This Warranty will be rendered invalid in case of the following:
Damage caused by circuit installed by customer or using customer own
products or accessories;
Modified or repaired by customer without authorization;
Damage caused by circuit installed by customer or not operating our
products under designated environment;
The product model or serial number is altered, deleted, removed or made
illegible by customer;
Damaged as a result of accidents, including but not limited to lightning,
moisture, fire, improper use or negligence.
Safety Symbols
Direct current
ON (power on)
Alternating current
OFF (power off)
Both direct and alternating
current
Power-on state
Protective conductor terminal
Power-off state
Earth (ground) terminal
Reference
terminal
Caution, risk of electric shock
Positive terminal
Warning, risk of danger (refer
to this manual for specific
Warning or Caution
information)
Negative terminal

IT-N2100 Programming Guide
Copyright © Itech Electronic Co., Ltd. ii
Frame or chassis terminal
-
-
Safety Precautions
The following safety precautions must be observed during all phases of
operation of this instrument. Failure to comply with these precautions or specific
warnings elsewhere in this manual will constitute a default under safety
standards of design, manufacture and intended use of the instrument. ITECH
assumes no liability for the customer’s failure to comply with these precautions.
Do not use the instrument if it is damaged. Before operation, check the
casing to see whether it cracks. Do not operate the instrument in the
presence of inflammable gasses, vapors or dusts.
The electronic load is provided with a power line during delivery and should
be connected to a socket with a protective earth terminal. Before operation,
be sure that the instrument is well grounded.
Make sure to use the power cord supplied by ITECH.
Check all marks on the instrument before connecting the instrument to
power supply.
Use electric wires of appropriate load. All loading wires should be capable
of bearing maximum short-circuit current of electronic load without
overheating. If there are multiple electronic loads, each pair of the power
cord must be capable of bearing the full-loaded rated short-circuit output
current
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.
If you use the power supply to charge the battery, pay attention to the
positive and negative polarity of the battery when wiring, otherwise the
power supply will be damaged!
Do not install alternative parts on the instrument or perform any
unauthorized modification.
Do not use the instrument if the detachable cover is removed or loosen.
To prevent the possibility of accidental injuries, be sure to use the power
adapter supplied by the manufacturer only.
We do not accept responsibility for any direct or indirect financial damage
or loss of profit that might occur when using the instrument.
This instrument is used for industrial purposes, do not apply this product to
IT power supply system.
Never use the instrument with a life-support system or any other equipment
subject to safety requirements.
Failure to use the instrument as directed by the manufacturer may render
its protective features void.
Always clean the casing with a dry cloth. Do not clean the internals.

IT-N2100 Programming Guide
Copyright © Itech Electronic Co., Ltd. iii
Make sure the vent hole is always unblocked.
Environmental Conditions
The instrument is designed for indoor use and an area with low condensation.
The table below shows the general environmental requirements for the
instrument.
Environmental Conditions
Requirements
Operating temperature
0°C to 40°C
Operating humidity
20%-80% (non-condensation)
Storage temperature
-10°C to 70 °C
Altitude
Operating up to 2,000 meters
Pollution degree
Pollution degree 2
Installation category
II
Note
To make accurate measurements, allow the instrument to warm up for 30 min before
operation.
Regulatory Markings
The CE mark indicates that the product complies with all
the relevant European legal directives. The specific year
(if any) affixed refers to the year when the design was
approved.
The UKCA mark indicates that the product complies with
all relevant UK legal regulat
ions (if accompanied by a
year, it indicates the year the design was approved).
The instrument complies with the WEEE Directive
(2002/96/EC) marking requirement. This affixed product
label indicates that you must not discard the
electrical/electronic product in domestic household waste.
This symbol indicates the time period during which no
hazardous or toxic substances are expected to leak or
deteriorate during normal use. The expected service life
of the product is 10 years. The product can be used safely
during the 10-
year Environment Friendly Use Period
(EFUP). Upon expiration of the EFUP, the product must
be immediately recycled.

IT-N2100 Programming Guide
Copyright © Itech Electronic Co., Ltd. iv
Waste Electrical and Electronic Equipment (WEEE)
Directive
This product complies with the WEEE Directive (2002/96/EC)
marking requirement. This affix product label indicates that you
must not discard the electrical/electronic product in domestic
household waste.
Product Category
With reference to the equipment classifications described in the
Annex I of the WEEE Directive, this instrument is classified as a
“Monitoring and Control Instrument”.
To return this unwanted instrument, contact your nearest
ITECH office.

IT-N2100 Programming Guide
Copyright © Itech Electronic Co., Ltd. v
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:2015+A1:2016 Ed 6.1
IEC 61000-3-2: 2018 RLV
IEC 61000-3-3: 2013+A1:2017
IEC 61000-4-2:2008
IEC 61000-4-3 2006+A1:2007+A2:2010/ EN 61000-4-3 A1:2008+A2:2010
IEC 61000-4-4:2012
IEC 61000-4-5:2014+A1:2017
IEC 61000-4-6:2013+cor1:2015
IEC 61000-4-11:2004+A1:2017
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+A1:2016

IT-N2100 Programming Guide
Copyright © Itech Electronic Co., Ltd. vi
Content
Quality Certification and Assurance ...........................................................................................................I
Warranty .....................................................................................................................................................I
Limitation of Warranty.................................................................................................................................I
Safety Symbols........................................................................................................................................... I
Safety Precautions .................................................................................................................................... II
Environmental Conditions......................................................................................................................... III
Regulatory Markings.................................................................................................................................III
Waste Electrical and Electronic Equipment (WEEE) Directive.................................................................IV
Compliance Information.............................................................................................................................V
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 Remote Operation............................................................................................................................... 6
Chapter2 FETCh & MEASure Subsystem........................................................................................... 1
MEASure[:SCALar]:CURRent[:DC]?.........................................................................................................1
FETCh[:SCALar]:CURRent[:DC]?............................................................................................................. 1
MEASure[:SCALar]:VOLTage[:DC]?.......................................................................................................... 1
FETCh[:SCALar]:VOLTage[:DC]?.............................................................................................................. 1
MEASure[:SCALar]:POWer[:DC]?............................................................................................................. 2
FETCh[:SCALar]:POWer[:DC]?................................................................................................................. 2
MEASure:ALL?.......................................................................................................................................... 2
FETCh:ALL?.............................................................................................................................................. 2
FETCh:TIME?............................................................................................................................................3
Chapter3 SOLar Subsystem................................................................................................................. 4
SOLar:Vmax <NRf+>................................................................................................................................. 4
SOLar:USER:VOC <NRf+>....................................................................................................................... 4
SOLar:EDIT:USER:IMP<NRf+>................................................................................................................5
SOLar:USER:VMP <NRf+> ....................................................................................................................... 5
SOLar:USER:ISC <NRf+>.........................................................................................................................6
SOLar:EDIT:SAS:VMP<NRf+>..................................................................................................................6
SOLar:EDIT:CURVe:PMP<NRf+> .............................................................................................................7
SOLar:EDIT:SAS:FORMula<CPD> ...........................................................................................................7
SOLar:EDIT:SAS:MATERial <NR1>............................................................................................................ 8
SOLar:FILTer:LEVel <CPD>........................................................................................................................ 9
SOLar:EDIT:TABLe:VOC <NRf+> .............................................................................................................9
SOLar:EDIT:TABLe:ISC <NRf+> .............................................................................................................10
SOLar:EDIT:TABLe:POINts <NR1>.........................................................................................................10
SOLar:EDIT:TABLe:VOLTage <NR1>,<NRf+>........................................................................................ 11
SOLar:EDIT:TABLe:CURRent <NR1>,<NRf+>....................................................................................... 11
SOLar:EDIT:FIXed:VOLTage <NRf+> .....................................................................................................12
SOLar:EDIT:FIXed:CURRent <NRf+>..................................................................................................... 12
SOLar:EDIT:FIXed:RESistance <NRf+>...................................................................................................13
SOLar:DOWNload................................................................................................................................... 13
SOLar:OUT:MODE <CPD>.......................................................................................................................14
Chapter4 OUTPut Subsystem............................................................................................................15
OUTPut[:STATe][:ALL] <bool>.................................................................................................................15
OUTPut:PROTection:CLEar....................................................................................................................15
OUTPut:DELay[:ON] <NRf+>..................................................................................................................15
OUTPut:DELay:OFF <NRf+>..................................................................................................................16
OUTPut:TIMer[:STATe]............................................................................................................................16
OUTPut:TIMer:DELay .............................................................................................................................17
OUTPut:PROTection:FOLDback[:MODE] <OFF|CC|CV>.......................................................................17
OUTPut:PROTection:FOLDback:DELay <NRf+>....................................................................................18
OUTPut:PONSetup[:STATe] <RST|LAST|LOFF> ...................................................................................18

IT-N2100 Programming Guide
Copyright © Itech Electronic Co., Ltd. vii
OUTPut:INHibit:MODE <OFF|LIVE|LATChing>......................................................................................19
Chapter5 SENSe Subsystem..............................................................................................................20
SENSe[:REMote][:STATe] <bool> ...........................................................................................................20
SENSe:FILTer:LEVel <SLOW|MEDium|FAST>.......................................................................................20
Chapter6 SOURce Subsystem........................................................................................................... 21
[SOURce:]CURRent:OVER:PROTection[:LEVel] <NRf+> ......................................................................21
[SOURce:]CURRent:OVER:PROTection:DELay <NRf+>.......................................................................21
[SOURce:]CURRent:OVER:PROTection:STATe <bool>.........................................................................22
[SOURce:]CURRent:UNDer:PROTection[:LEVel] <NRf+>......................................................................22
[SOURce:]CURRent:UNDer:PROTection:DELay <NRf+>......................................................................23
[SOURce:]CURRent:UNDer:PROTection:STATe <bool>........................................................................23
[SOURce:]CURRent:UNDer:PROTection:WARM <NRf+>......................................................................24
[SOURce:]CURRent:DECimal?...............................................................................................................24
[SOURce:]CURRent[:LEVel]:MAXimum <NRf+> ....................................................................................24
[SOURce:]VOLTage:OVER:PROTection[:LEVel] <NRf+>.......................................................................25
[SOURce:]VOLTage:OVER:PROTection:DELay <NRf+>........................................................................25
[SOURce:]VOLTage:OVER:PROTection:STATe <bool>..........................................................................26
[SOURce:]VOLTage:DECimal? ............................................................................................................... 26
[SOURce:]VOLTage[:LEVel]:MAXimum <NRf+>.....................................................................................27
[SOURce:]POWer[:LEVel]:LIMit[:MAX]?..................................................................................................27
[SOURce:]POWer:PROTection[:LEVel] <NRf+> .....................................................................................28
[SOURce:]POWer:PROTection:DELay <NRf+>......................................................................................28
[SOURce:]POWer:PROTection:STATe <Bool>........................................................................................28
[SOURce:]POWer:DECimal? ..................................................................................................................29
[SOURce:]LOOP:SPEEd <LOW|MEDium|HIGH> ..................................................................................29
[SOURce:]NPLC <NR1> .........................................................................................................................30
[SOURce:]LINE:FREQ <NR1>................................................................................................................30
[SOURce:]LEAK[:STATe] <Bool> ............................................................................................................31
Chapter7 System Subsystem.............................................................................................................32
SYSTem:VERSion?.................................................................................................................................32
SYSTem:ERRor[:NEXT]?........................................................................................................................32
SYSTem:REMote.....................................................................................................................................33
SYSTem:LOCal .......................................................................................................................................33
SYSTem:RWLock....................................................................................................................................34
Chapter8 TRIGger Subsystem ...........................................................................................................35
TRIGger[:IMMediate]...............................................................................................................................35
TRIGger:SOURce <MANUal|BUS|EXTernal>.........................................................................................35
TRIGger:EXTernal:DIRection <IN|OUT>.................................................................................................35
Chapter9 IEEE-488 Command............................................................................................................ 37
*CLS ........................................................................................................................................................ 37
*ESE <NRf>.............................................................................................................................................37
*IDN?.......................................................................................................................................................37
*OPC........................................................................................................................................................ 38
*PSC <Bool>............................................................................................................................................ 38
*RST ........................................................................................................................................................38
*SRE <NRf>............................................................................................................................................. 39
*STB? ...................................................................................................................................................... 39
*TRG........................................................................................................................................................40
*TST?....................................................................................................................................................... 40
Chapter10 STATus Subsystem.........................................................................................................41
STATus:QUEStionable[:EVENt]?.............................................................................................................41
STATus:QUEStionable:ENABle <state>..................................................................................................41
STATus:QUEStionable:PTRansition <NR1> ...........................................................................................42
STATus:QUEStionable:NTRansition <NR1>...........................................................................................42
STATus:QUEStionable:CONDition?........................................................................................................43
STATus:OPERation[:EVENt]? .................................................................................................................44

IT-N2100 Programming Guide
Copyright © Itech Electronic Co., Ltd. viii
STATus:OPERation:CONDition?.............................................................................................................44
STATus:OPERation:ENABle....................................................................................................................44
STATus:OPERation:PTRansition <NR1>................................................................................................45
STATus:OPERation:NTRansition <NR1>................................................................................................46
STATus:PRESet.......................................................................................................................................46
Chapter11 LIST Subsystem.............................................................................................................. 48
LIST:MODE:COUNt:REPeat <FIXed|CURVe|TABLe|USER>,<NR1>,<NR1>.......................................48
LIST:FIXed:PARameter <NR1>,<"volt,curr,res,time,jump">...................................................................48
LIST:CURVe:PARameter <NR1>,<"reg,vmp,pmp,material,time,jump">................................................49
LIST:TABLe:PARameter <NR1>,<"file,voc,isc,time,jump">.................................................................... 49
LIST:USER:PARameter <NR1>,<"voc,vmp,isc,imp,time,jump">............................................................50
LIST:SAVE <NR1>..................................................................................................................................50
LIST:RECall <NR1> ................................................................................................................................51
LIST[:STATe] <bool>...............................................................................................................................51
LIST:PAUSe[:STATe] <BOOLEAN> .......................................................................................................52
LIST:RUN:STEP?.................................................................................................................................... 52
LIST:RUN:REPeat?.................................................................................................................................53
Chapter12 Example........................................................................................................................... 54
Four Point ............................................................................................................................................54
Regulation............................................................................................................................................54

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.
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.
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.

Remote Control
Copyright © Itech Electronic Co., Ltd. 2
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. A message 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 lowerfor example:
*RST = *rst
:DATA? = :data?
:SYSTem:PRESet = :system:preset
Long-form and short-form versions
ASCPI command word can be sent in its long-form or short-form version.

Remote Control
Copyright © Itech Electronic Co., Ltd. 3
The command subsystem tables in Section 5 provide the in the
long-form version. 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 (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

Remote Control
Copyright © Itech Electronic Co., Ltd. 4
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
commands always start with an asterisk (*) and occupy 3 character sizes,

Remote Control
Copyright © Itech Electronic Co., Ltd. 5
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}

Remote Control
Copyright © Itech Electronic Co., Ltd. 6
ASCII string Parameter
String Parameter may actually include all ASCII 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
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 Remote Operation
Please refer to user manual for detailed introductions of the remote interface
connections. If the user want to change the settings of the instrument, for
instance, the output setting value, the command SYST:REM must be sent to
the instrument after finishing the connection between the instrument and PC.

FETCh & MEASure Subsystem
Copyright © Itech Electronic Co., Ltd. 1
Chapter2 FETCh & MEASure Subsystem
MEASure[:SCALar]:CURRent[:DC]?
This command is used to return the actual current value of power output.
Command Syntax:
MEASure[:SCALar]:CURRent[:DC]?
Return Parameters:
<NRf>
FETCh[:SCALar]:CURRent[:DC]?
This order is used to read the latest current to be processed from sampling
buffer. When you send this order, then our unit will communicate with PC, and
sending the current data to PC. This order will not affect our unit’s setting or
trigger the measurement operation. It only need the nearest reading it can get.
The returned readings will keep the old before it get a new data.
Command Syntax:
FETCh[:SCALar]:CURRent[:DC]?
Return Parameters:
<NRf>
MEASure[:SCALar]:VOLTage[:DC]?
The command returns the actual voltage value of the power supply output.
Command Syntax:
MEASure[:SCALar]:VOLTage[:DC]?
Return Parameters:
<NRf>
FETCh[:SCALar]:VOLTage[:DC]?
The command reads the most recent pre-processed voltage reading in the
sample buffer.
Command Syntax:
FETCh[:SCALar]:VOLTage[:DC]?
Return Parameters:
<NRf>

FETCh & MEASure Subsystem
Copyright © Itech Electronic Co., Ltd. 2
MEASure[:SCALar]:POWer[:DC]?
This command is used to return the actual power value of the power output.
Command Syntax:
MEASure[:SCALar]:POWer[:DC]?
Return Parameters:
<NRf>
FETCh[:SCALar]:POWer[:DC]?
This command is used to read the most recent pre-processed power reading in
the sample buffer.
Command Syntax:
FETCh[:SCALar]:POWer[:DC]?
Return Parameters:
<NRf>
MEASure:ALL?
This command is used to return the actual voltage, current, and power values of
the power supply output.
Command Syntax
MEASure:ALL?
Parameters None
RST Value Not applicable
Example MEAS:ALL?
Return Parameters
NRf,NRf,NRf
FETCh:ALL?
This command is used to read the most recent pre-processed voltage, current,
and power readings from the sample buffer.
Command Syntax
FETCh:ALL?

FETCh & MEASure Subsystem
Copyright © Itech Electronic Co., Ltd. 3
Parameters None
RST Value Not applicable
Example FETC:ALL?
Return Parameters
NRf,NRf,NRf
FETCh:TIME?
This command queries the time when the output is turned on after the timer
takes effect.
Command Syntax
FETCh:TIME?
Parameters None
RST Value Not applicable
Example FETC:TIME?
Return Parameters
NRf

SOLar Subsystem
Copyright © Itech Electronic Co., Ltd. 4
Chapter3 SOLar Subsystem
SOLar:Vmax <NRf+>
The command sets the maximum output voltage value in PV mode, i.e. the
maximum output voltage value of the instrument.
Subsystem SOLar
Command Syntax
SOLar:Vmax <NRf+>
Parameters <NRf+>
MIN|MAX|DEF|<Value>
Value range: MIN~MAX
Default value MIN
Example SOLar:Vmax 50
Query Syntax SOLar:Vmax?
Return Parameters
<NRf+>
SOLar:USER:VOC <NRf+>
The command sets the open-circuit voltage value, which is the VOC voltage in
User mode.
Subsystem
SOLar
Command Syntax
SOLar:USER:VOC <NRf+>
Parameters <NRf+>