KEPCO KLR SERIES Instruction Manual

KEPCO®
THE POWER SUPPLIER™
MODEL
DEVELOPER’S GUIDE
ORDER NO. REV. NO.
KEPCO, INC. !131-38 SANFORD AVENUE !FLUSHING, NY. 11355 U.S.A. !TEL [phone] !FAX [phone]
email: [e-mail] !World Wide Web: http://www.kepcopower.com
KEPCO INC.
An ISO 9001 Company.
KLR SERIES
POWER SUPPLY
2400 WATT PROGRAMMABLE POWER SUPPLY
KLR SERIES
DEVELOPER’S GUIDE
©2013, KEPCO, INC
P/N 243-1298
IMPORTANT NOTES:
1) This manual is valid for the following Model and associated serial numbers:
FIRMWARE VERSION NOTE
10.07 and higher
2) A Change Page may be included at the end of the manual. All applicable changes and
revision number changes are documented with reference to the equipment serial num-
bers. Before using this Instruction Manual, check your equipment serial number to identify
your model. If in doubt, contact your nearest Kepco Representative, or the Kepco Docu-
mentation Office in New York, [phone], requesting the correct revision for your
particular model and serial number.
3) The contents of this manual are protected by copyright. Reproduction of any part can be
made only with the specific written permission of Kepco, Inc.
Data subject to change without notice.

KLR DEVGD 020498 i
TABLE OF CONTENTS
SECTION PAGE
SECTION 1 - INTRODUCTION
1.1 General Description .................................................................................................................................... 1-1
1.1.1 Drivers ..................................................................................................................................................... 1-1
1.1.2 Communication ....................................................................................................................................... 1-2
1.1.3 Programming........................................................................................................................................... 1-2
1.2 Driver Overview .......................................................................................................................................... 1-2
1.2.1 Initialization.............................................................................................................................................. 1-3
1.2.2 Output Control ......................................................................................................................................... 1-3
1.2.3 Measurement .......................................................................................................................................... 1-3
1.2.4 Limit Models (User-defined Voltage/Current Limits)................................................................................ 1-3
1.2.5 Save/Recall (Storage of User-Programmed Active Settings).................................................................. 1-3
1.2.6 LIST (User-Programmed Sequences)..................................................................................................... 1-3
1.2.7 Status ...................................................................................................................................................... 1-4
1.2.7.1 Status Reporting Structure................................................................................................................. 1-4
1.2.7.2 Status Byte Register Set .................................................................................................................... 1-6
1.2.7.3 Standard EvenT Status Register Set ................................................................................................. 1-6
1.2.7.4 Operation Status Register Set ........................................................................................................... 1-7
1.2.7.5 QUEStionable Status Register Set .................................................................................................... 1-7
1.2.7.6 Error/Event Queue ............................................................................................................................. 1-8
1.2.8 Trigger ..................................................................................................................................................... 1-8
SECTION 2 - COMMUNICATION
2.2 Front Panel (local) Control.......................................................................................................................... 2-1
2.3 Digital Control via LAN [E-Series Models Only].......................................................................................... 2-2
2.4 Digital Control via GPIB .............................................................................................................................. 2-3
2.5 Digital Control via RS 232 [Standard Models only]..................................................................................... 2-3
SECTION 3 - IVI-COM DRIVER
3.1.1 Specification Compliance ........................................................................................................................ 3-1
3.1.2 Range Checking and Coercion ............................................................................................................... 3-1
3.1.3 Multithreading Support ............................................................................................................................ 3-1
3.1.4 Context-Sensitive Help............................................................................................................................ 3-2
3.1.5 Installer.................................................................................................................................................... 3-2
3.1.6 Rights ...................................................................................................................................................... 3-2
3.2 IVI-COM Instrument Driver Functions......................................................................................................... 3-2
3.3 Examples Using C ...................................................................................................................................... 3-4
3.3.1 Setting the output to a value and Making a Measurement ...................................................................... 3-4
3.3.2 Using a list to Perform a Series of Operations ........................................................................................ 3-8
3.3.3 Setting Limit Model.................................................................................................................................. 3-11
3.4 Examples Using Visual Basic ..................................................................................................................... 3-12
3.4.1 Setting the Output to a Value and Taking a Measurement ..................................................................... 3-12
3.4.2 Using a List to Perform a Series of Operations ....................................................................................... 3-15
3.4.3 Setting Limit Model.................................................................................................................................. 3-16
3.5 Examples Using LabView ........................................................................................................................... 3-17
3.5.1 Setting the output to a value.................................................................................................................... 3-18
3.5.2 Getting a voltage and current reading from the power supply................................................................. 3-18
3.5.3 Changing the limit model......................................................................................................................... 3-19
SECTION 4 - LABVIEW G DRIVER
4.2 LabView G Instrument Driver...................................................................................................................... 4-1
4.3 LabView G Instrument Driver Functions..................................................................................................... 4-1
4.4 Using the Driver Functions ......................................................................................................................... 4-3
4.4.1 KepcoDCPwr Configure Voltage Level.vi ........................................................................................ 4-3
4.4.1.1 Connector Panel ................................................................................................................................ 4-3
4.4.1.2 Controls and Indicators ...................................................................................................................... 4-3
4.4.1.3 Block Diagram Description................................................................................................................. 4-4
4.4.2 KepcoDCPwr Measure [MSR].vi ..................................................................................................... 4-5

ii KLR DEVGD 060713
TABLE OF CONTENTS
SECTION PAGE
4.5 Example of Setting the Output ................................................................................................................... 4-6
4.5.1 Initialization Function .............................................................................................................................. 4-7
4.5.2 Set the OUtput ON or OFF ..................................................................................................................... 4-9
4.5.3 Get Measurement and Status................................................................................................................. 4-9
4.5.4 Close Connection ................................................................................................................................... 4-9
4.6 Interactive demonstration program ............................................................................................................ 4-10
4.6.1 KepcoDCPwr Interactive Example.vi...................................................................................................... 4-10
4.6.2 Software timed ramp example................................................................................................................ 4-12
4.6.3 Software Timed Ramp Execution ........................................................................................................... 4-14
4.6.4 Function Generator................................................................................................................................. 4-15
SECTION 5 - VXI plug&play DRIVER
5.2 VXI plug&play Instrument Driver................................................................................................................ 5-1
5.3 VXI plug&play Instrument Driver Functions ............................................................................................... 5-1
5.4 Using the VXI plug&play driver .................................................................................................................. 5-3
5.4.1 Example 1: Setting Voltage and Current ................................................................................................ 5-3
5.4.2 Example 2: Using the power supply to create a voltage ramp................................................................ 5-5
5.4.3 Example 3: Using the power supply to Take Measurements.................................................................. 5-7
5.5 Demonstration Program Using the VXI plug&play Driver........................................................................... 5-9
5.5.1 Instrument Setup .................................................................................................................................... 5-9
5.5.2 Main Panel.............................................................................................................................................. 5-10
5.5.3 Power Supply Events.............................................................................................................................. 5-14
SECTION 6 - PROGRAMMING THE KLR USING SCPI COMMANDS
6.2 SCPI Messages ......................................................................................................................................... 6-1
6.3 Common Commands/Queries ................................................................................................................... 6-1
6.4 SCPI Subsystem Command/Query Structure............................................................................................ 6-1
6.4.1 DISPlay Subsystem................................................................................................................................ 6-1
6.4.2 TRIGger Subsystem ............................................................................................................................... 6-1
6.4.3 Abort Subsystem .................................................................................................................................... 6-2
6.4.4 LIST Subsystem ..................................................................................................................................... 6-2
6.4.5 MEASure Subsystem.............................................................................................................................. 6-2
6.4.6 OUTPut Subsystem................................................................................................................................ 6-2
6.4.7 STATus Subsystem................................................................................................................................ 6-2
6.4.8 STorage Subsystem ............................................................................................................................... 6-2
6.4.9 SYSTem subsystem ............................................................................................................................... 6-2
6.4.10 [SOURce:]VOLTage and [SOURce:]CURRent Subsystems .................................................................. 6-2
6.4.11 CALibrate Subsystem............................................................................................................................. 6-3
6.5 Program Message Structure ...................................................................................................................... 6-3
6.5.1 Keyword.................................................................................................................................................. 6-3
6.5.2 Keyword Separator................................................................................................................................. 6-4
6.5.3 Query Indicator ....................................................................................................................................... 6-5
6.5.4 Data ........................................................................................................................................................ 6-5
6.5.5 Data Separator ....................................................................................................................................... 6-5
6.5.6 Message Unit Separator......................................................................................................................... 6-5
6.5.7 Root Specifier ......................................................................................................................................... 6-5
6.5.8 Message Terminator............................................................................................................................... 6-5
6.6 Understanding The Command Structure ................................................................................................... 6-7
6.7 Program Message Syntax Summary ......................................................................................................... 6-7
6.7.1 Exceptions to the Rules.......................................................................................................................... 6-8
6.8 Programming Examples............................................................................................................................. 6-8

KLR DEVGD 020498 iii
TABLE OF CONTENTS
SECTION PAGE
SECTION 7 - IEEE 488.2 (GPIB) INTERFACE
7.2 IEEE 488 (GPIB) Bus Protocol ................................................................................................................... 7-1
7.2.1 Changing the GPIB Address ................................................................................................................... 7-3
SECTION 8 - RS 232C INTERFACE [STANDARD MODELS ONLY]
8.2 RS232-C Operation [Standard Models Only].............................................................................................. 8-1
8.2.1 RS 232 Implementation [Standard Models Only] .................................................................................... 8-1
8.2.2 Data Transfer Protocols [Standard Models Only].................................................................................... 8-2
8.2.2.1 Echo Mode [Standard Models Only] .................................................................................................. 8-3
8.2.2.2 Prompt Method [Standard Models Only] ............................................................................................ 8-3
8.2.2.3 XON XOFF Method [Standard Models Only] ..................................................................................... 8-3
8.2.2.4 Isolating RS 232 Communications Problems [Standard Models Only] .............................................. 8-4
SECTION 9 - LAN INTERFACE [E-Series MODELS ONLY]
9.2 Using Port 80 (Web Interface) .................................................................................................................... 9-1
9.3 Using Port 5024 (Telnet)............................................................................................................................. 9-1
9.4 Using Port 5025 (SCPI-RAW)..................................................................................................................... 9-2
9.5 Using Port 1024 (VXI-11)............................................................................................................................ 9-2
9.6 Using Port 5044 ( *TRG command)............................................................................................................ 9-2
9.7 SUNRPC Port 111 ...................................................................................................................................... 9-2
APPENDIX A - IEEE 488.2 COMMAND/QUERY DEFINITIONS
A.2 *CLS — Clear Status Command ............................................................................................................... A-1
A.3 *ESE — Standard Event Status Enable Command................................................................................... A-1
A.4 *ESE? — Standard Event Status Enable Query........................................................................................ A-2
A.5 *ESR? — Event Status Register Query..................................................................................................... A-2
A.6 *IDN? — Identification Query..................................................................................................................... A-2
A.7 *OPC — Operation Complete Command .................................................................................................. A-3
A.8 *OPC? — Operation Complete Query....................................................................................................... A-3
A.9 *OPT? — Operation Complete Query ....................................................................................................... A-4
A.10 *RCL — Recall Command ......................................................................................................................... A-4
A.11 *RST — Reset Command.......................................................................................................................... A-4
A.12 *SAV — Save Command........................................................................................................................... A-4
A.13 *SRE — Service Request Enable Command ............................................................................................ A-5
A.14 *SRE? — Service Request Enable Query ................................................................................................. A-6
A.15 *STB? — Status Byte Register Query ....................................................................................................... A-6
A.16 *TRG — Trigger Command ....................................................................................................................... A-6
A.17 *TST? — Self Test Query .......................................................................................................................... A-6
A.18 *WAI — Wait Command ............................................................................................................................ A-6
APPENDIX B - SCPI COMMAND/QUERY DEFINITIONS
B.1 Introduction ................................................................................................................................................ B-1
B.2 Numerical Values....................................................................................................................................... B-2
B.3 ABORtCommand...................................................................................................................................... B-2
B.4 CALibrate Commands and Queries .......................................................................................................... B-2
B.5 DISPlay[:Window]:TEXT[:DATA]? Query.................................................................................................. B-2
B.6 INITiate[:IMMediate] Command................................................................................................................ B-2
B.7 INITiate:CONTinuous Command .............................................................................................................. B-3
B.8 INITiate:CONTinuous Query ..................................................................................................................... B-4
B.9 [SOURce:]LIST:CLEar Command............................................................................................................. B-4
B.10 [SOURce:]LIST:CONTrol Command ......................................................................................................... B-4
B.11 [SOURce:]LIST:CONTrol? QUERY........................................................................................................... B-4
B.12 [SOURce:]LIST:CONtrol:POINts?Query.................................................................................................. B-4

iv KLR DEVGD 060713
TABLE OF CONTENTS
SECTION PAGE
B.13 [SOURce:]LIST:COUNtCommand............................................................................................................ B-4
B.14 [SOURce:]LIST:COUNt?Query................................................................................................................. B-4
B.15 [SOURce:]LIST:COUNt:SKIP Command................................................................................................... B-4
B.16 [SOURce:]LIST:COUNt:SKIP? Query ....................................................................................................... B-5
B.17 [SOURce:]LIST:CURRent Command........................................................................................................ B-5
B.18 [SOURce:]LIST:CURRent? Query............................................................................................................. B-5
B.19 [SOURce:]LIST:CURRent:POINts? Query................................................................................................ B-5
B.20 [SOURce:]LIST:DIRection Command ....................................................................................................... B-5
B.21 [SOURce:]LIST:DIRection? Query............................................................................................................ B-5
B.22 [SOURce:]LIST:DWELlCommand ............................................................................................................ B-5
B.23 [SOURce:]LIST:DWELl? Query ................................................................................................................. B-6
B.24 [SOURce:]LIST:DWELl:POINts? Query .................................................................................................... B-6
B.25 [SOURce:]LIST:QUERyCommand ........................................................................................................... B-6
B.26 [SOURce:]LIST:QUERy? Query ................................................................................................................ B-6
B.27 [SOURce:]LIST:VOLTage Command ........................................................................................................ B-6
B.28 [SOURce:]LIST:VOLTage? Query ............................................................................................................. B-6
B.29 [SOURce:]LIST:VOLTage:POINts? Query ................................................................................................ B-7
B.30 MEASure[:SCALar]:CURRent[:DC]? Query .............................................................................................. B-7
B.31 MEASure[:SCALar]:VOLTage[:DC]? Query .............................................................................................. B-7
B.32 MEMory:LOCation Command ................................................................................................................... B-7
B.33 MEMory:LOCation? Query ........................................................................................................................ B-7
B.34 OUTPut[:STATe] Command ...................................................................................................................... B-8
B.35 OUTPut[:STATe]? Query ........................................................................................................................... B-9
B.36 [SOURce:]CURRent[:LEVel][:IMMediate][:AMPlitude] Command............................................................ B-9
B.37 [SOURce:]CURRent[:LEVel][:IMMediate][:AMPlitude]? Query ................................................................ B-9
B.38 [SOURce:]CURRent:LIMit:HIGH Command ............................................................................................. B-9
B.39 [SOURce:]CURRent:LIMit:HIGH? Query .................................................................................................. B-10
B.40 [SOURce:]CURRent:MODE Command..................................................................................................... B-10
B.41 [SOURce:]CURRent:MODE? Query ......................................................................................................... B-10
B.42 [SOURce:]CURRent:PROTection[:LEVel] Command ............................................................................... B-11
B.43 [SOURce:]CURRent:PROTection[:LEVel]? Query.................................................................................... B-12
B.44 [SOURce:]CURRent:[:LEVel]TRIGgered[:AMPLitude] Command............................................................ B-12
B.45 [SOURce:]CURRent:[:LEVel]TRIGgered[:AMPlitude]? Query.................................................................. B-12
B.46 [SOURce:]FUNCtion:MODE Command .................................................................................................... B-12
B.47 [SOURce:]FUNCtion:MODE? Query ......................................................................................................... B-12
B.48 [SOURce:]VOLTage[:LEVel][:IMMediate][:AMPLitude] Command........................................................... B-12
B.49 [SOURce:]VOLTage[:LEVel][:IMMediate][:AMPLitude]? Query................................................................ B-13
B.50 [SOURce:]VOLTage:LIMit:HIGH Command.............................................................................................. B-13
B.51 [SOURce:]VOLTage:LIMit:HIGH? Query................................................................................................... B-13
B.52 [SOURce:]VOLTage:MODE Command ..................................................................................................... B-14
B.53 [SOURce:]VOLTage:MODE? Query.......................................................................................................... B-14
B.54 [SOURce:]VOLTage:PROTection[:LEVel] Command................................................................................ B-14
B.55 [SOURce:]VOLTage:PROTection[:LEVel]? Query .................................................................................... B-14
B.56 [SOURce:]VOLTage:[LEVel:]TRIGgered[:AMPLitude] Command............................................................ B-15
B.57 [SOURce:]VOLTage:[:LEVel]TRIGgered[:AMPLitude]? Query................................................................. B-15
B.58 STATus:OPERation:CONDition? Query ................................................................................................... B-16
B.59 STATus:OPERation:ENABle Command ................................................................................................... B-16
B.60 STATus:OPERation:ENABle? Query ........................................................................................................ B-16
B.61 STATus:OPERation[:EVENt]? Query ........................................................................................................ B-16
B.62 STATus:PRESet Command ...................................................................................................................... B-16
B.63 STATus:QUEStionable[:EVENt]? Query ................................................................................................... B-17
B.64 STATus:QUEStionable:CONDition? Query .............................................................................................. B-18
B.65 STATus:QUEStionable:ENABle Command .............................................................................................. B-18
B.66 STATus:QUEStionable:ENABle? Query ................................................................................................... B-18
B.67 SYSTem:COMMunication:GPIB:ADDRess Command............................................................................. B-18
B.68 SYSTem:COMMunication:GPIB:ADDRess? Query.................................................................................. B-18
B.69 SYSTem:COMMunication:LAN:AUTO Command..................................................................................... B-18
B.70 SYSTem:COMMunication:LAN:AUTO? Query ......................................................................................... B-19

KLR DEVGD 020498 v
TABLE OF CONTENTS
SECTION PAGE
B.71 SYSTem:COMMunication:LAN:DHCP Command .................................................................................... B-19
B.72 SYSTem:COMMunication:LAN:DHCP? Query ......................................................................................... B-19
B.73 SYSTem:COMMunication:LAN:DNS Command....................................................................................... B-19
B.74 SYSTem:COMMunication:LAN:DNS? Query............................................................................................ B-19
B.75 SYSTem:COMMunication:LAN:GATE Command..................................................................................... B-19
B.76 SYSTem:COMMunication:LAN:GATE? Query ......................................................................................... B-19
B.77 SYSTem:COMMunication:LAN:IP Command........................................................................................... B-20
B.78 SYSTem:COMMunication:LAN:IP? Query................................................................................................ B-20
B.79 SYSTem:COMMunication:LAN:MAC? Query ........................................................................................... B-20
B.80 SYSTem:COMMunication:LAN:MASK Command .................................................................................... B-20
B.81 SYSTem:COMMunication:LAN:MASK? Query......................................................................................... B-20
B.82 SYSTem:COMMunication:SERial:BAUD CommanD................................................................................ B-20
B.83 SYSTem:COMMunication:SERial:BAUD? Query..................................................................................... B-20
B.84 SYSTem:COMMunication:SERial:ECHO Command................................................................................ B-21
B.85 SYSTem:COMMunication:SERial:ECHO? Query..................................................................................... B-21
B.86 SYSTem:COMMunication:SERial:ENABle Command ............................................................................. B-21
B.87 SYSTem:COMMunication:SERial:ENABle? Query .................................................................................. B-21
B.88 SYSTem:COMMunication:SERial:PACE Command ................................................................................ B-21
B.89 SYSTem:COMMunication:SERial:PACE? Query ..................................................................................... B-21
B.90 SYSTem:COMMunication:SERial:PROMpt Command ............................................................................ B-21
B.91 SYSTem:COMMunication:SERial:PROMpt? Query ................................................................................. B-22
B.92 SYSTem:ERRor[:NEXT]? Query ............................................................................................................... B-22
B.93 SYSTem:ERRor:CODE[:NEXT]? Query.................................................................................................... B-22
B.94 SYSTem:ERRor:CODE:ALL? Query ......................................................................................................... B-22
B.95 SYSTem:KLOCkCommand ...................................................................................................................... B-22
B.96 SYSTem:KLOCk? Query ........................................................................................................................... B-23
B.97 SYSTem:LANGuage Command................................................................................................................ B-23
B.98 SYSTem:LANGuage? Query .................................................................................................................... B-23
B.99 SYSTem:PASSword:CENable Command ................................................................................................ B-24
B.100 SYSTem:PASSword:CDISable Command ............................................................................................... B-24
B.101 SYSTem:PASSword:NEW Command....................................................................................................... B-24
B.102 SYSTem:PASSword[:CENable]:STATe? Query ....................................................................................... B-24
B.103 SYSTem:SECurity:IMMediate Command ................................................................................................. B-24
B.104 SYSTem:SET Command ........................................................................................................................... B-24
B.105 SYSTem:SET? Query................................................................................................................................ B-25
B.106 SYSTem:VERSion? Query........................................................................................................................ B-25
B.107 TRIGger[:SEQuence]:SOURce Command............................................................................................... B-25
B.108 TRIGger[:SEQuence]:SOURce? Query ................................................................................................... B-25

LIST OF FIGURES
FIGURE TITLE PAGE
vi KLR DEVGD 060713
1-1 Status Reporting Structure......................................................................................................................... 1-5
2-1 KLR Communication, Block Diagram ......................................................................................................... 2-1
3-1 Example of Setting the Output and taking a measurement, written in C++................................................ 3-6
3-2 Example of Using a List, written in C#........................................................................................................ 3-9
3-3 Setting the Output and taking a measurement Example, written in Visual Basic....................................... 3-14
3-4 Example of Using a List, written in Visual Basic......................................................................................... 3-15
3-5 Setting Limit Model, Written in Visual Basic ............................................................................................... 3-17
3-6 Setting the Output Using LabView with IVI-COM Driver ............................................................................ 3-18
3-7 Measuring Voltage and Current Using LabView with IVI-COM Driver ....................................................... 3-19
3-8 Setting the Limit Model Using LabView with IVI-COM Driver..................................................................... 3-19
4-1 KepcoDCPwr Configure Voltage Level.vi Connector Panel ....................................................................... 4-3
4-2 KepcoDCPwr Configure Voltage Level.vi Block Diagram .......................................................................... 4-5
4-3 KepcoDCPwr Configure Voltage Level.vi Error Block Diagram ................................................................. 4-5
4-4 KepcoDCPwr Measure [MSR].vi Control Panel ......................................................................................... 4-5
4-5 KepcoDCPwr Measure [MSR].vi Block Diagram........................................................................................ 4-6
4-6 Setting the Output, Overall Block Diagram................................................................................................. 4-8
4-7 Front Panel Window ................................................................................................................................... 4-10
4-8 Software Ramp Panel, Current Ramp Example......................................................................................... 4-12
4-9 Ramp Function Panel, Current Ramp ........................................................................................................ 4-14
4-10 Function Generator Panel .......................................................................................................................... 4-16
4-11 Configure User Sequence.vi Block Diagram ............................................................................................. 4-16
4-12 Ramp Function, Block Diagram.................................................................................................................. 5-17
4-13 Function Generator, List Functionality, Block Diagram .............................................................................. 5-19
5-1 Example 1: Setting Voltage and Current .................................................................................................... 5-4
5-2 Example 2: Using the power supply to create a voltage ramp ................................................................... 5-5
5-3 Example 3: Using the power supply to Take Measurements ..................................................................... 5-7
5-4 Instrument Setup Window .......................................................................................................................... 5-9
5-5 Main Panel window .................................................................................................................................... 5-10
5-6 Protection Window ..................................................................................................................................... 5-11
5-7 Store/Recall Window .................................................................................................................................. 5-11
5-8 Trigger Window .......................................................................................................................................... 5-11
5-9 Calibration Window .................................................................................................................................... 5-12
5-10 Limit Model Window ................................................................................................................................... 5-12
5-11 Utilities Window .......................................................................................................................................... 5-13
5-12 Utilities Window with Output Test Running ................................................................................................ 5-13
5-13 Power Supply Event Window ..................................................................................................................... 5-14
6-1 Message Structure ..................................................................................................................................... 6-4
6-2 Tree Diagram of SCPI Commands Used with KLR Power Supply............................................................. 6-6
6-3 Typical Example Of KLR Power Supply Program Using SCPI Commands ............................................... 6-9
8-1 RS 232 Implementation [Standard Models Only] ....................................................................................... 8-2
A-1 GPIB Commands ....................................................................................................................................... A-5
B-1 Programming the Output............................................................................................................................ B-3
B-2 Using LIST Commands and Queries.......................................................................................................... B-8
B-3 Programming Limit Models......................................................................................................................... B-10
B-4 Programming as a Current Stabilizer ......................................................................................................... B-11
B-5 Programming as Voltage Stabilizer ............................................................................................................ B-15
B-6 Using Status Commands and Queries ....................................................................................................... B-17
B-7 Using System Commands and Queries ..................................................................................................... B-23

KLR DEVGD 020498 vii
LIST OF TABLES
TABLE TITLE PAGE
1-1 VISA Resource String Corresponding to Interface .....................................................................................1-2
2-1 Front Panel Lockout Commands ................................................................................................................2-2
2-2 RS 232 Setup ..............................................................................................................................................2-4
3-1 KLR IVI-COM Driver Functions ...................................................................................................................3-3
4-1 KLR LabView G Driver Functions ...............................................................................................................4-2
4-2 KepcoDCPwr Configure Voltage Level.vi Input/Output Descriptions ........................................................4-4
4-3 Error (or Explain Warning) Codes ...............................................................................................................4-4
4-4 KepcoDCPwr Measure [MSR].vi Input/Output Descriptions ......................................................................4-6
5-1 KLR VXI plug&play Driver Functions ..........................................................................................................5-1
6-1 Rules Governing Shortform Keywords ........................................................................................................6-4
6-2 VISA Resource String Corresponding to Interface .....................................................................................6-8
7-1 IEEE 488 Port Connector (J4) Pin Assignments .........................................................................................7-1
7-2 IEEE 488 (GPIB) Bus Interface Functions ..................................................................................................7-2
7-3 IEEE 488 (GPIB) Bus Command Mode Messages .....................................................................................7-2
7-4 IEEE 488 (GPIB) Bus Data Mode Messages ..............................................................................................7-3
9-1 Telnet Port 5024 and SCPI Raw Port 5025 Control Characters .................................................................9-1
A-1 IEEE 488.2 Command/query Index ........................................................................................................... A-1
A-2 Standard Event Status Enable Register and Standard Event Status Register Bits ................................... A-1
A-3 Service Request Enable and Status Byte Register Bits ............................................................................. A-6
B-1 SCPI Subsystem Command/query Index .................................................................................................. B-1
B-2 Operation Condition Register, Operation Enable Register,
and Operation Event Register Bits .......................................................................................................... B-16
B-3 Questionable Event Register, Questionable Condition Register
and Questionable Condition Enable Register Bits .................................................................................. B-18
B-4 Factory Default Calibration Passwords ...................................................................................................... B-24
B-5 Error Messages .......................................................................................................................................... B-25

KLR-DEV 060713 1-1
SECTION 1 - INTRODUCTION
This manual contains instructions for digital programming of the KLR series of 1200W output
power, stabilized voltage or current, d-c power supplies manufactured by KEPCO, Inc., Flush-
ing, New York, U.S.A. Basic operation of the front panel controls as well as analog programming
of the KLR Series is covered in the KLR User Manual. (When analog programming is in use, the
unit will still respond to digital queries related to status and readback.) Refer to the KLR User
Manual for all other installation and operating instructions.
1.1 GENERAL DESCRIPTION
The KLR is a power supply class of instrument. The KLR supports all Power supply class func-
tionality including measurement and trigger. The KLR has additional functionality beyond the
class requirements, including a 250 step list, state storage, and hyperbolic power capability. The
KLR Power Supply Series can be digitally programmed using SCPI commands and queries sent
from a computer via one of two interfaces. Standard models (also referred to as -1200 models)
include the IEEE 488.2 (GPIB) and RS 232 interface. E-Series models (formerly referred to as -
1.2K models) include the IEEE 488.2 (GPIB) and LAN interfaces.
1.1.1 DRIVERS
Three instrument drivers are available which allow remote operation via virtual front panels.
• IVI-COM driver supplied with the unit [E-Series Models only] This is a state-of-the-art
driver which provides wrappers to allow use within Visual C, Visual Basic, LabView and
LabWindows/CVI environments to fully control the KLR power supply. (see Section 3).
• LabView G driver supplied with the unit. This driver is written in native LabView code
using the VISA write and read functions. (see Section 4).
• VXI plug&play driver supplied with the unit. This driver is written in C using VISA write
and read functions. It is compliant with the VXI plug&play specification and can be used
in an ANSI compatible C program such as LabWindows /CVI. It is also portable to Linux
and Apple operating systems, however verification of these environments has not been
completed. (see Section 5).
The drivers (and the raw programming examples found in this manual), do not communicate
directly to the KLR. They use the operating system or vendor specific interface drivers to handle
the actual communication of the serial, Ethernet or GPIB cables. Vendors such as National
instruments, Agilent technologies and Keithley have created a VISA (Virtual Instrument System
Architecture) library. The VISA library uses consistent commands to open a connection, write
and read data, read the interrupt status and perform standard functions such as lock, unlock
and device clear.
The VISA libraries “open” command creates the handle for all other functions. The open com-
mand requires a resource string that provides the physical address of the unit and also specifies
the type of interface that will be used. Table 1-1 provides the resource strings for the four possi-
ble interfaces to the KLR. All KLR Models include the GPIB interface. The serial interface is
included only in standard Models; the LAN interface is included only in E-Series Models.
These drivers require a helper application (visa32.dll) to be installed on the computer being
used. VISA uses resource strings (see Table 1-1) to address the unit. The IVI-COM, and VXI
plug&play drivers require that all calls to an instrument be made through the VISA library. The

1-2 KLR-DEV 060713
LabView G driver also uses VISA calls, allowing it to work on all ports of the KLR. The examples
given in Programming, Section 6, PAR. 6.8, all utilize VISA calls so they are universally applied.
1.1.2 COMMUNICATION
Communication between a KLR and a computer system may be via one of three methods: IEEE
488.2, RS 232 and LAN. These three interfaces communicate by sending formatted strings to
the KLR which are then parsed to perform specific actions.
• IEEE 488.2 (GPIB) Interface (see Section 7).
• RS 232 Interface [standard models only] (see Section 8).
• LAN interface [E-Series models only] (see Section 9).
1.1.3 PROGRAMMING
SCPI and IEEE 488 common commands/queries are the building blocks used to control the
KLR power supply. These sections are provided to allow a user to write their own program to
control the KLR power supply or to use the various interactive tools provided by Measurement
Computing, National Instruments, Agilent Technologies and Microsoft to send strings to a
device over the RS 232, GPIB or LAN interfaces. SCPI commands and queries are supported
by all three interfaces.
• Description of SCPI Syntax (see Section 6).
• IEEE 488 Common commands supported (see Appendix A).
• Listing of SCPI commands supported (see Appendix B).
1.2 DRIVER OVERVIEW
The three drivers for KLR all have common functional groups Each group contains similar func-
tions which work together. The four different environments, IVI-COM, LabView G, VXI
Plug&Play and Programming all have common functionality.
The KLR power supply, like most instrument power supplies, has four subsystems: output, trig-
ger, status and measurement. In additional to these subsystems, the KLR has a storage system
and a list system. The commands to use these subsystems have been grouped by function as
detailed in the following paragraphs. These functional groupings are also used in the examples
that are presented in Sections 3 (IVI-COM Driver), 4 (LabView G Driver), and 5 (VXI plug&play
Driver).
TABLE 1-1. VISA RESOURCE STRING CORRESPONDING TO INTERFACE
INTERFACE VISA RESOURCE STRING COMMENT
GPIB GPIB::xx::INSTR The GPIB address replaces xx.
SERIAL ASRLy::INSTR The com port number replaces y.
LAN-SCPI-RAW TCIP::192.168.0.100::5025::SOCKET This is the fastest LAN interface, similar to the serial port with
automatic XON XOFF protocol support.
LAN-VXI-11 TCIP::192.168.0.100::INSTR This LAN interface requires a more complex handshake for data
and is inherently slower than a socket interface. It is similar to the
GPIB interface where you tell the device when to take data and
when it is acceptable to receive data.

KLR-DEV 060713 1-3
1.2.1 INITIALIZATION
When an instrument is first accessed, it is desirable to have it start at a standard state and to
verify that the instrument is the correct one. These functions utilize standard commands which
are common to all power supply class instruments such as *IDN? *CLS and *RST. In the various
drivers, this functional group also includes an open and close functionality.
1.2.2 OUTPUT CONTROL
The power supply class instrument has specific requirements to support voltage and current
settings, output enable and protection. These functions are common to all power supplies in the
power supply class.
1.2.3 MEASUREMENT
The Power supply has the ability to measure the voltage and current at the output and display
this information on the front panel. The measurement system provides the ability to read this
back from the unit.
1.2.4 LIMIT MODELS (USER-DEFINED VOLTAGE/CURRENT LIMITS)
The KLR Power Supply can be programmed to user-defined values that can be lower than the
maximum values. For example, although the KLR 40-60 is factory set to 40V and 60A (2400
Watts), arbitrary limits, e.g., 40A@30V or 30A@35V can be established. Once the limits are set,
setting values exceeding the limit values will not be accepted. The limit model settings are pass-
word protected.
1.2.5 SAVE/RECALL (STORAGE OF USER-PROGRAMMED ACTIVE SETTINGS)
The KLR Power Supply contains 40 memory locations that can be used to store active settings.
Values are stored in the nonvolatile memory and are retained when the unit is turned off. The
stored settings can then be recalled and applied as desired. See PAR. A.13 for *SAV (Save)
and A.13 for *RCL (Recall). The unit has the ability to read or set the storage locations without
affecting the output of the power supply. These setting are cleared when a calibration is per-
formed. Recalling a location which has never been loaded with data will cause a -221,”Settings
conflict” error and the output is unchanged.
If a limit model setting (PAR. 1.2.4) is changed and a stored parameter is outside the range
established by the new limit model, when that location is recalled, the parameter recalled
appears at the output as the default minimum (zero V or minimum A), but the stored value is
unchanged, and no error message is issued.
1.2.6 LIST (USER-PROGRAMMED SEQUENCES)
Using the LIST functions, up to 250 locations are available for programming the KLR output.
These locations enable the user to program the output using multiple command sequences
which may be initiated by a single command (see PARs B.9 through B.29). The repeatable user-
determined sequences are stored in volatile memory and are retained until reprogrammed, the
power supply is turned off, a calibration is performed, a LIST:CLEar command is received, or
limit model settings are changed.
Each location defines values for the active channel (either output voltage or output current), a
dwell time duration (between 0.010 and 655.36 seconds) for the programmed settings, and the
state of the internal relay. By programming the output to change in small increments, complex
outputs can be generated.

1-4 KLR-DEV 060713
NOTES: 1. When programming sequential voltage levels, it is important to set the Overvoltage
to accommodate the highest voltage of the sequence. Otherwise, when going from
higher to lower voltage levels, the overvoltage protection will trip and shut down the
unit because the overvoltage setting registers faster than the power supply can
attain the lower voltage.
2. To operate the internal relay using the LIST commands, first configure the internal
relay to LIST using the UTIL menu from the front panel (see KLR User Manual).
3. The message dLST appears in the front panel status display while a LIST program
is running.
4. Removing the unit from remote digital programming mode will immediately termi-
nate a running LIST program.
5. The LIST capability is disabled for master /slave configurations and all LIST com-
mands will generate error message -221,”Configuration conflict.”
1.2.7 STATUS
The KLR status system consists of the standard register configuration as defined by the IEEE
488.2 and SCPI standards. This configuration allows the errors to be reported and causes inter-
rupts to be sent to the computer. The drivers provide the ability to set and clear these registers
but the interrupt functionality is not supported by the drivers. Using interrupts requires special
programming techniques that are environment-specific. See PAR. 1.2.7.1 through 1.2.7.5 for
details on the process required to implement this in a VISA environment.
The serial poll response of the KLR power supply provides summary bits of the status and error
reporting system. (The simplest status report is the “command valid” reporting and data avail-
ability. The successful decoding of a command string generates no error and is indicated by the
bit 3 of the serial poll response being a zero.) The setting of bit 4 in the status byte indicates
data is available to the controller in response to a command query message.
1.2.7.1 STATUS REPORTING STRUCTURE
The status reporting of the KLR uses four status register sets, illustrated in Figure 1-1. These
register sets are the Questionable, Operation, Event Status and Status Byte register sets. The
Questionable and Operation registers are 16 bit registers whose inputs are unique to each
instrument, while the Event Status and Status Byte registers are 8 bit registers with standard
inputs defined by IEEE 488.2. Each of these four register sets is comprised of event and enable
registers, with the Questionable and Operation sets adding condition and transition registers.
The Questionable and Operation condition registers hold unlatched events reported in real-time
by the instrument, viewable at any time using the appropriate query. The contents of the Ques-
tionable and Operation condition registers are latched in the corresponding event registers,
which hold records of specific event occurrences as determined by the accompanying transition
register; for KLR, all transition register bits are configured to record low-to-high (0 to 1) bit states
only, so that a 1 in the condition register is always stored as a 1 in the event register. Since the
event register bits are reset when read, the event register provides a record of changes in status
since the last time the event register was read.
For all four register sets the contents of each event register is gated by an accompanying
enable register. The user must set the corresponding enable bit value to one (high) in order to
include the specific event bit in the reported status.

KLR-DEV 060713 1-5
For example, if an overvoltage error is detected, bit 0 of the Questionable Status Condition reg-
ister is set. The 0 to 1 transition causes bit 0 to be stored as a 1 in the corresponding Event reg-
ister. If bit 0 of the Questionable Status Enable register has bit 0 set, bit 3 of the Status Byte
(STB) register is asserted. If bit 3 of the Service Request Enable (SRE) register is also set to 1,
then bit 6 of the STB is set to 1 (true), causing the power supply to assert the SRQ line to the
host computer.
FIGURE 1-1. STATUS REPORTING STRUCTURE

1-6 KLR-DEV 060713
When the service request is executed, the STB register bits are read: bit 3 set indicates Ques-
tionable Status; bit 2 set indicates the error/event queue is not empty; bit 4 set indicates that a
message is available in the output buffer. bit 5 set indicates event status; bit 7 set indicates
operation status. The host computer program might then issue a query to read one of the indi-
cated register set.
Reading an Event or Condition register clears all of the bits found in that register. Event register
contents are also cleared when the *CLS command is received. Condition register bits are only
cleared when the corresponding condition is not present.
1.2.7.2 STATUS BYTE REGISTER SET
The Status Byte register set is comprised of the Status Byte (STB) and the Service Request
Enable (SRE) registers. The STB register is read by issuing the *STB? query (see Appendix A,
PAR. A.15). The SRE register is read using the *SRE? query (see Appendix A, PAR. A.14) and
modified using the *SRE command (see Appendix A,.PAR. A.13), except that bit 6 (request for
service) of STB is not masked by SRE.
• 0 - Not Used - always 0.
• 1 - LIST Running - 1 indicates that a LIST sequence is presently running. Read (and
clear) Operation Event register using STAT:OPER?
• 2 - Error Queue — 1 indicates error queue is not empty. Read error queue using
SYST:ERR?
• 3 - Questionable Status Summary — 1 indicates a Questionable Status register bit has
been set (see Appendix B, Table B-5 for details). Read (and clear) Questionable Event
register using STAT:QUES?.
• 4 - Message Available — 1 indicates a message is waiting in the output buffer.
• 5 - Event Status Summary — 1 indicates an Event Status register bit has been set. Read
(and clear) Questionable Event register using *ESR?.
• 6 - Service Request — Either RQS (Request for Service) or MSS (Master Status Sum-
mary (see Appendix A, PAR. A.13 for details).
• 7 - Operation Status Summary — 1 indicates an Operation Status register bit has been
set (see Appendix B, Table B-5 for details). Read (and clear) Operation Event register
using STAT:OPER?.
1.2.7.3 STANDARD EVENT STATUS REGISTER SET
The Standard Event Status register set is comprised of the Event Status (ESR) and Event Sta-
tus Enable (ESE) registers. The ESR register is read by issuing the *ESR? Query (see Appen-
dix A, PAR. A.5). The ESE register is read using the *ESE? query (see Appendix A, PAR. A.4)
and modified using the *ESE command (see Appendix A, PAR. A.3).
• 0 - Operation complete — 1 indicates the operation is complete and the unit is ready to
accept another command, or that query results are ready to be transferred.
• 1 - Request Control — Not used (always zero).
• 2 - Query Error — 1 indicates a query error has occurred (see Appendix B, Table B-5 for
details).
• 3 - Device Dependent Error — 1 indicates device dependent error has occurred (see
Appendix B, Table B-5 for details).

KLR-DEV 060713 1-7
• 4 - Execution Error — 1 indicates execution error has occurred (parameter exceeded
allowable range) (see Appendix B, Table B-5 for details).
• 5 - Command Error — 1 indicates a command syntax error has occurred (see Appendix
B, Table B-5 for details).
• 6 - User Request — Not used (always zero).
• 7 - Power On — set once upon power-up, however ESE bit 7 set to 0 prevents Status
Byte bit 5 from being set.
1.2.7.4 OPERATION STATUS REGISTER SET
The Operation Status register set is comprised of condition, transition, event and enable regis-
ters (see Figure 1-2). Appendix B, PAR’s B.58 through B.61 provide detailed explanations of the
queries/commands for reading and modifying these registers as applicable; the transition regis-
ter cannot be modified.
The Operation condition registers record conditions which are a part of the instrument’s normal
operation. The definition of each of these bits (condition register) is as follows:
• 0 through 4 — Not used (always zero).
• 5 - Waiting for Trigger Summary — 1 indicates the unit is waiting for trigger
• 6 and 7 — Not used (always zero).
• 8 - Constant Voltage — 1 indicates the instrument is in constant voltage mode.
• 9 — Not used (always zero).
• 10 - Constant Current — 1 indicates the instrument is in constant current mode.
• 11 through 13 — Not used (always zero).
• 14 - Program Running — 1 indicates the program is running.
• 15 — Not used (always zero).
1.2.7.5 QUESTIONABLE STATUS REGISTER SET
The Questionable Status register set is comprised of condition, transition, event and enable reg-
isters (see Figure 1-2). Appendix B, PAR’s B.63 through B.66 provide detailed explanations of
the queries/commands for reading and modifying these registers as applicable; the transition
register cannot be modified.
The Questionable Condition register (see Figure 1-1) contains status bits representing data/sig-
nals which give an indication of the quality of various aspects of the signal.

1-8 KLR-DEV 060713
A bit set in the Questionable Condition register indicates that the data currently being acquired
or generated is of questionable quality due to some condition affecting the parameter associ-
ated with that bit.
• 0 - Overvoltage Error — 1 indicates an overvoltage fault has been detected.
• 1 - Overcurrent Error — 1 indicates an overcurrent fault has been detected.
• 2 - Power Lead Error — 1 indicates that output lead connections are not complete.
• 3 - Overtemperature Error — 1 indicates a thermal error has been detected.
• 4 - Input Power Error — 1 indicates input mains error.
• 5 - Fan Error — 1 indicates inoperative fan.
• 6 - Master/Slave Error — 1 indicates communication error between master and slave
units.
• 7 - 15 — Not used (always zero).
1.2.7.6 ERROR/EVENT QUEUE
The Error/Event queue is a FIFO (first in first out) buffer that stores errors as they occur. As it is
read, each error is removed from the queue and the next error message is made available.
When all errors have been read, the query returns 0,”No error”.
If more than 15 errors are accumulated, it will overflow. When overflow occurs, the oldest errors
stay in the queue, but the most recent errors are discarded. The last error in the queue will be -
350,”Too many errors.” Error messages are defined in Appendix B, Table B-5.
1.2.8 TRIGGER
The KLR unit has the ability to utilize both a software trigger and an external (hardware) trigger.
Model 1-2.K units have an additional software trigger capability accessed via Port 5044. When a
trigger event is properly enabled and received, the output voltage and current are set to the pre-
set trigger levels.
The TRIG:SOUR command (see PAR. B.107) determines whether the external (hardware)
(EXT) or software (INT) trigger is selected.
If external trigger mode is selected, the hardware trigger is activated by grounding the
EXT_TRG line (J2 pin 14 to pin 9, 11, 13 or 15); this creates the trigger event at which time the
trigger values (preset values VOLT:TRIG and CURR:TRIG) will become the setpoint values
(Vset and Cset) for the power supply. Refer to PARs. B.44, B.56, and B.94. The VOLT:TRIG
and CURR:TRIG values are reset to the default minimum (zero V or minimum A) when the unit
is calibrated or if a limit model setting is changed.
If software trigger is selected, trigger events are activated by *TRG (see PAR. A.16) or a GPIB
<GET> command.

KLR-DEV 060713 2-1
SECTION 2 - COMMUNICATION
2.1 INTRODUCTION
Figure 2-1 shows all paths used to communicate with the KLR. These include local control from
the front panel, GPIB, LAN (Ethernet) for E-Series models only, and RS 232 for standard mod-
els only.
FIGURE 2-1. KLR COMMUNICATION, BLOCK DIAGRAM
2.2 FRONT PANEL (LOCAL) CONTROL
Front panel control is the default upon power up (see the KLR User Manual). The unit automati-
cally enters remote mode upon receipt of a remote command. The front panel can be locked
and unlocked in all environments as shown in Table 2-1.
HOME PAGE
(UNIT DESCRIPTION)
LAN
CONFIGURATION
PAGE
OPERATE
INSTRUMENT
PAGE
WEB PORT 80
(8 CONNECTIONS)
STATUS
DISPLAY
FRONT PANEL
SUNRPC
PORT 111
UDP BROADCAST
SUNRPC
PORT 111
TCP/IP
UDP LXI
TRIGGER
PORT 5044
TCP/IP
TRIGGER
PORT 5044
TELNET
PORT 5024
2
CONNECTIONS
SCPI RAW
PORT 5025
2 CONNECTIONS
VXI-11
PORT 1024
4 CONNECTIONS
LAN PORT
LOCKING
INSTRUMENT
FUNCTIONS
CLASS A/B
STATUS
LOCAL CONTROL
SCPI, 488.2 LOCKING
GPIB
CONNECTION
3043146
LAN (ETHERNET) **
RS 232
CONNECTION *
REAR PANEL
* STANDARD MODELS ONLY
** E SERIES MODELS ONLY

2-2 KLR-DEV 060713
2.3 DIGITAL CONTROL VIA LAN [E-SERIES MODELS ONLY]
Figure 2-1 shows all the ports available to the LAN interface. These port are described in Sec-
tion 9, LAN INTERFACE [E-Series MODELS ONLY], and include:
• Port 80 - Web Interface. (See KLR User Manual for details on how to use the web inter-
face.) This port supports up to eight connections. For details as to how to access, oper-
ate and configure the unit using the web interface, refer to the KLR User Manual. In
addition, the web interface is compatible with \\LXI\instrument.xml and
\\LXI\instrument.xsd required by Version 1.2 of the LXI specification.
• Port 111 - SUNRPC (UDP Broadcast and TCP/IP). The SUNRPC port is used for discov-
ery when sent as a UDP broadcast message. The only command supported is the GET-
PORT. The ports that can be requested are detailed in the VXI specification and
repeated in the LXI specifications. The SUNRPC port can be also used with the TCP/IP
protocol. Again, the only command supported is the GETPORT. Port 111 is the method
(called the Discovery process) used by National Instruments and Agilent to find the
resource. KLR E-Series Models support the discovery process implemented by Version
1.1 of the LXI Specification using this port and a VXI-11 protocol, as well as the XML pro-
tocol proposed by Version 1.2 of the LXI specification.
• Port 1024 - VXI-11. This port supports up to two connections. VXI-11 uses one stan-
dard port (1024) and two assigned by the instrument when connections are opened. The
1024 port is open at all times to accept connection requests. The VXI-11 port requires
the use of a lock which prevents other VXI-11 connections from gaining access to the
instrument. This port is accessed using the VISA resource string ending in INST, e.g.:
TCIP0::192.168.1.100::INST
• Port 5024 - Telnet. This port supports up to two connections. the Telnet command pro-
vided with all windows operating systems can be run with the following command line
(use Start - Run) TELENET IPADDRESS PORT e.g.:
TELNET 192.168.0.100 5024
When the program is run, entering commands found in Appendix A and B of this Devel-
oper’s Guide allow the operation of the unit via the Telnet port.
TABLE 2-1. FRONT PANEL LOCKOUT COMMANDS
Environment Command Description
Programming SYSTem:KLOCk Follow with on or off. Setting on locks the front panel.
VXI plug&play Kp_KLR_SetResetKeyblock Requires the instrument session and a Boolean value of 0 for off and 1
to lock the keyboard.
LabView G Kepco Serial initialize with options The input defaults to lock the keyboard.
IVI-COM Requires the instrument session and a Boolean value of 0 for off and 1
to lock the keyboard.