Xantrex Technology XMP 2600 User Manual
Smart choice for power
Xantrex
Multiple Output
Power System
XMP 2600
Programming Manual
www.xantrex.com
XMP 2600
Programming Manual
This document contains proprietary information. All rights reserved. Do not reproduce this
document or part of it. Do not translate to any other language.
The information contained herein is subject to change without notice.
Rev. 1.1 9/2003
Limited
Warranty
What does this warranty cover and how long does it
last?
This Limited Warranty is provided by Xantrex Technology, Inc. (“Xantrex”) and
covers defects in workmanship and materials in your XMP 2600 Power Supply. This
warranty lasts for a Warranty Period of 3 years from the date of purchase at point of
sale to you, the original end user customer.
What will Xantrex do?
Xantrex will, at its option, repair or replace the defective product free of charge,
provided that you notify Xantrex of the product defect within the Warranty Period,
and provided that Xantrex through inspection establishes the existence of such a
defect and that it is covered by this Limited Warranty.
Xantrex will, at its option, use new and/or reconditioned parts in performing
warranty repair and building replacement products. Xantrex reserves the right to use
parts or products of original or improved design in the repair or replacement. If
Xantrex repairs or replaces a product, its warranty continues for the remaining
portion of the original Warranty Period or 90 days from the date of the return
shipment to the customer, whichever is greater. All replaced products and all parts
removed from repaired products become the property of Xantrex.
Xantrex covers both parts and labor necessary to repair the product, and return
shipment to the customer via a Xantrex-selected non-expedited surface freight
within the contiguous United States and Canada. Alaska and Hawaii are excluded.
Contact Xantrex Customer Service for details on freight policy for return shipments
outside of the contiguous United States and Canada.
How do you get service?
If your product requires troubleshooting or warranty service, contact your merchant.
If you are unable to contact your merchant, or the merchant is unable to provide
service, contact Xantrex directly at:
Phone: 604 422 2777
Toll Free North America: 1 800 670 0707
Fax: 604 420 2145
Email: customerservice@xantrex.com
Direct returns may be performed according to the Xantrex Return Material
Authorization Policy. For some products, Xantrex maintains a network of regional
Authorized Service Centers. Call Xantrex or check our website to see if your
product can be repaired at one of these facilities.
In any warranty claim, dated proof of purchase must accompany the product and the
product must not have been disassembled or modified without prior written
authorization by Xantrex.
Proof of purchase may be in any one of the following forms:
The dated purchase receipt from the original purchase of the product
at point of sale to the end user, or
The dated dealer invoice or purchase receipt showing original
equipment manufacturer (OEM) status, or
b
The dated invoice or purchase receipt showing the product exchanged
under warranty
XMP 2600 Programming Manual rev. 1.1
What does this warranty not cover?
This Limited Warranty does not cover normal wear and tear of the product or costs
related to the removal, installation, or troubleshooting of the customer’s electrical
systems. This warranty does not apply to and Xantrex will not be responsible for any
defect in or damage to:
a. the product if it has been misused, neglected, improperly installed, physically
damaged or altered, either internally or externally, or damaged from improper
use or use in an unsuitable environment;
b. the product if it has been subjected to fire, water, generalized corrosion,
biological infestations, and high input voltage from lightning strikes;
c. the product if repairs have been done to it other than by Xantrex or its
authorized service centers (hereafter “ASCs”);
d. the product if it is used as a component part of a product expressly warranted by
another manufacturer;
e. the product if its original identification (trade-mark, serial number) markings
have been defaced, altered, or removed.
Disclaimer
Product
THIS LIMITED WARRANTY IS THE SOLE AND EXCLUSIVE WARRANTY
PROVIDED BY XANTREX IN CONNECTION WITH YOUR XANTREX
PRODUCT AND IS, WHERE PERMITTED BY LAW, IN LIEU OF ALL OTHER
WARRANTIES, CONDITIONS, GUARANTEES, REPRESENTATIONS,
OBLIGATIONS AND LIABILITIES, EXPRESS OR IMPLIED, STATUTORY OR
OTHERWISE IN CONNECTION WITH THE PRODUCT, HOWEVER ARISING
(WHETHER BY CONTRACT, TORT, NEGLIGENCE, PRINCIPLES OF
MANUFACTURER’S LIABILITY, OPERATION OF LAW, CONDUCT,
STATEMENT OR OTHERWISE), INCLUDING WITHOUT RESTRICTION
ANY IMPLIED WARRANTY OR CONDITION OF QUALITY,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. ANY
IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE TO THE EXTENT REQUIRED UNDER
APPLICABLE LAW TO APPLY TO THE PRODUCT SHALL BE LIMITED IN
DURATION TO THE PERIOD STIPULATED UNDER THIS LIMITED
WARRANTY.
IN NO EVENT WILL XANTREX BE LIABLE FOR ANY SPECIAL, DIRECT,
INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES, LOSSES,
COSTS OR EXPENSES HOWEVER ARISING WHETHER IN CONTRACT OR
TORT INCLUDING WITHOUT RESTRICTION ANY ECONOMIC LOSSES OF
ANY KIND, ANY LOSS OR DAMAGE TO PROPERTY, ANY PERSONAL
INJURY, ANY DAMAGE OR INJURY ARISING FROM OR AS A RESULT OF
MISUSE OR ABUSE, OR THE INCORRECT INSTALLATION, INTEGRATION
OR OPERATION OF THE PRODUCT.
Exclusions
If this product is a consumer product, federal law does not allow an exclusion of
implied warranties. To the extent you are entitled to implied warranties under federal
law, to the extent permitted by applicable law they are limited to the duration of this
Limited Warranty. Some states and provinces do not allow limitations or exclusions
on implied warranties or on the duration of an implied warranty or on the limitation
or exclusion of incidental or consequential damages, so the above limitation(s) or
exclusion(s) may not apply to you. This Limited Warranty gives you specific legal
rights. You may have other rights which may vary from state to state or province to
province.
XMP 2600 Programming Manual rev. 1.1 c
Information
WARNING:
Limitations
on Use
WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, UNLESS
SPECIFICALLY AGREED TO BY IT IN WRITING, XANTREX
a. MAKES NO WARRANTY AS TO THE ACCURACY, SUFFICIENCY OR
SUITABILITY OF ANY TECHNICAL OR OTHER INFORMATION
PROVIDED IN MANUALS OR OTHER DOCUMENTATION PROVIDED
BY IT IN CONNECTION WITH THE PRODUCT; AND
b. ASSUMES NO RESPONSIBILITY OR LIABILITY FOR LOSSES,
DAMAGES, COSTS OR EXPENSES, WHETHER SPECIAL, DIRECT,
INDIRECT, CONSEQUENTIAL OR INCIDENTAL, WHICH MIGHT ARISE
OUT OF THE USE OF SUCH INFORMATION.
THE USE OF ANY SUCH INFORMATION WILL BE ENTIRELY AT THE
USER’S RISK.
Please refer to your product manuals for limitations on uses of the product.
Specifically, please note that this power supply is not intended for use in connection
with life support systems and Xantrex makes no warranty or representation in
connection with any use of the product for such purposes.
Xantrex Technology, Inc.
8999 Nelson Way
Information
About Your
Power Supply
Release
Burnaby, British Columbia
Canada V5A 4B5
Please record the following information when you first open your Power Supply
package:
Model Number
Serial Number
Purchased From
Purchase Date
Release 1.1 (2003-09)
d
Copyright © 20 3 Xantrex Technology Inc. All rights reserved. 0
Printed in Israel
XMP 2600 Programming Manual rev. 1.1
Safety Summary
The following safety precautions are to be kept and observed by the user.
Noncompliance with these safety rules may cause hazard and is exclusively under
the user's responsibility.
IMPORTANT
Read this safety summary before operating the unit.
Power Supply
Grounding
Description
Of Power
Supply
Symbols
The XMP 2600 must be connected to an earth terminal. The unit comes with a three
wires power cord. The Yellow/Green wire must be connected to the earth terminal in
the electrical power outlet.
Disconnection of the earth wire might result in personal shock hazard.
The following table provides descriptions for the symbols that appear on the XMP
2600:
Symbol Description
Protective conductor terminal
On
Off
Caution, risk of electric shock
Warning (refer to accompanying documents)
XMP 2600 Programming Manual rev. 1.1 e
Input Mains
Voltage
Rating
The XMP 2600 operates at the following mains nominal voltages:
• 170Vac - 265Vac nominal (45 to 66Hz)
• 120Vac nominal, up to 1KW output power (45 to 66Hz)
Do not exceed this voltage range (nominal), as deterioration of performance or
damage to the unit is likely to occur. The following table shows the mains voltage
specification of the Power Supply:
Nominal Mains Nominal Current
230Vac Iin<15A
120Vac, Po<1KW Iin<15A
Mains supply voltage fluctuations may not exceed +/-10% of the nominal voltage.
Power plug shall be fitted according to each national electrical code, and rated for a
current of at least 20A.
WARNING
Do Not Open
The Unit
Air Inlets And
Air Outlet
Output
Voltages
The XMP 2600 must be operated at the proper mains voltage. Before operating
the unit make sure the mains voltage complies with the range described above.
Noncompliance with the input voltage may cause hazard and damage to the unit!
The user, except when replacing modules, should not open the unit.
WARNING
Make sure the power cord is disconnected from the mains before opening the
unit. High voltages inside the unit may cause electric shock.
The Power Supply is a forced air-cooled unit. Cooling is essential for the unit's
proper operation.
The unit includes four air inlet openings located in the front panel, in both the left
and right sides near the front panel and in the top cover near the front panel. The air
outlet is in the rear panel (all over its surface).
Make sure there are no obstructions for the airflow, at least two centimeters (0.8”)
away from these openings.
Obstructing these ventilation openings may cause fire and irreversible damage to the
unit.
The Power Supply's outputs (at the unit's rear) may carry high voltages. Make sure
to handle them properly to avoid shock hazard.
Unused outputs must be closed with load connectors (these connectors must include
sense lines connections).
Nonoperative
Modules
f
Do not operate the unit if it contains damaged or defective modules. Hazard or
damage may occur.
Damaged or defective units should be repaired by authorized personnel only.
XMP 2600 Programming Manual rev. 1.1
Power Supply
Safety
WARNING
Do not operate the unit with a missing module. Modules must be arranged
consecutively from left to right. Unused module locations must be closed with
ventilation obstructions. Operating the unit with missing modules or missing
internal ventilation obstructions may cause overheating and fire hazard.
WARNING — High Energy and High Voltage
Exercise caution when using and calibrating a power supply. High energy levels can
be stored at the output voltage terminals on a power supply in normal operation. In
addition, potentially lethal voltages exist in the power circuit and on the output and
sense connectors of a power supply with a rated output greater than 40 V. Filter
capacitors store potentially dangerous energy for some time after power is removed.
CAUTION
Operate the power supply in an environment free of flammable gases or fumes. To
ensure that the power supply’s safety features are not compromised, use the power
supply as specified in this manual and do not substitute parts or make any
unauthorized modifications. Contact the service technician for service and repair
help. Repairs must be made by experienced service technicians only
Regulatory Approvals and Safety Agency
Compliance
Regulatory
Approvals
European Standards: Electromagnetic Emissions and Immunity -meets Council
Directive 89/336/EEC
Electromagnetic Emissions: EN61326:1997 +A1:1998
EN61000-3-2:2000
EN61000-3-3:1995
Electromagnetic Immunity: EC61326:1997 +A1:1998
Safety
Agency
Compliance
European Standards:
Safety Meets EN61010 –1
American Standards:
Electromagnetic Emissions Meets FCC Class A
Safety Meets UL61010-1
XMP 2600 Programming Manual rev. 1.1 g
About this manual
This programming manual contains information on programming the XMP 2600.
Who should
use this
manual
Chapters
This manual is designed for users who understand basic electrical theory, especially
as applied to the operation of power supplies. This implies a recognition of constant
voltage and constant current operating modes and the control of input and output
power, as well as the observance of safe techniques while making connections to the
supply and any changes in settings.
Chapter 1: Interfacing the XMP 2600 describes the hardware and software basics
of connecting a remote controller (usually a PC) to the XMP 2600.
Chapter 2: Usage Guidelines explains the recommended methods of
communicating with the XMP 2600, setting it up and using it.
Chapter 3: Basic Programming describes the way to utilize the basic features of
the XMP 2600 power supply system.
Chapter 4: Advanced Features describes the advanced features of the XMP 2600
and the way to utilize those features.
Chapter 5: Commands and Queries Reference contains a full reference of the
available commands and queries you use for controlling the XMP 2600. A list of
commands and queries, divided by category, is also provided to help you find the
right command or query to use.
Chapter 6: Status Reporting describes the status structures maintained by the
XMP 2600 and the way to manipulate and use them. A list of possible error codes is
also included.
Terminology
The following explains the jargon unique to the XMP 2600 as used in this
programming manual:
Slot ................................. a physical location within the XMP’s mainframe
where power modules are installed. Each power
module occupies 1, 2 or 3 slots depending on its
voltage and current ratings.
Channel .......................... a logical location on the internal communications
link (connecting power modules to the XMP’s
main controller). Each location is identified by
an address in the range 1 to 16.
Module’s address............ the number of the channel the power module is
associated with. The power module address is
used to identify the power module in
programmed commands and other operations.
net................................... a communications link connecting power
modules to the XMP’s main controller. The net
comes in two flavors: internal net – running
inside the mainframe and external net –
interconnecting mainframes.
h
XMP 2600 Programming Manual rev. 1.1
Table of Contents
Table of contents
Chapter 1: Interfacing the XMP 2600 1
The GPIB interface 1
The serial interface 2
Serial Interface Capabilities 2
Computer Versus Terminal Operation 2
Programming messages formats 3
Listening Formats 3
Talking Formats 4
Chapter 2: Usage Guidelines 5
How to communicate with the XMP 2600 5
Using the comm. channels 5
Using the GPIB bus 5
Using an RS232 link 5
Recovering from communication halts 6
The XMP’s input and output queues 6
Communicate with the XMP 2600 6
Using queries 6
Using commands 6
Programming the XMP 2600 6
Recommendations on using the XMP 2600 7
Initialize the XMP 2600 7
Identify the XMP 2600 8
Enforce power-on conditions 8
Setup the XMP 2600 status system 8
Query installed Power Modules 8
Setup system level protection shutdown features 9
Initial setup of the Power Modules 9
Activation 10
On-going usage of the XMP 2600 11
Use queries 11
Using advanced features 11
A focus on status 11
Handling SRQ and the IEEE488.2 Status Structures 11
Definitions of structural elements 12
Status registers 12
Event registers 12
Event enable registers 12
Mask registers 12
Responding to SRQ events 13
The (main) status byte 13
Main controller events 13
Output message Queue 13
Remote communication time out 14
XMP 2600 Programming Manual rev. 1.1 i
Table of Contents
What happens when power is turned on 15
Chapter 3: Basic Programming 17
Basic setup and usage 17
Output Setup 17
Overview of output setup parameters 18
Output control 19
Output activation 19
Polarity and disconnect relays 20
Current limiting schemes 20
Voltage / current mode 20
Foldback 20
Retry 21
Shutdown on current limit 21
Primary engine status structure 14
Summary of power modules status 14
Power modules status structure 14
Power Module output rating 18
Output program limits 18
Output protection 18
Output settings 19
Reprogramming Delay 21
Chapter 4: Advanced Features 23
Workpoint window warning 23
Usage guidelines 23
Using the warnings 24
Checking the status 24
Using the events mechanism 24
Additional usages 25
Load protection 25
OVP and OCP 25
Current limitation 25
Protection using the workpoint window 25
Arm, trigger, sync and ramp 26
ARM 26
The trigger mechanism 26
The SYNC output 27
Output ramping 28
What is output ramping? 28
Output ramping setup 29
Output ramping initiation 29
Synchronization of operations 29
Simultaneous operations 29
j XMP 2600 Programming Manual rev. 1.1
Table of Contents
Output on/off 30
Other operations 30
Sequential Operations 30
Using hardware (TRIG and SYNC) to serialize operations 30
Using software (OPC mechanism) to serialize operations 31
Controller notification of Operation Complete 31
Selective shutdown 32
Shutdown grouping: single, group, global 32
The different shutdown grouping of modules 32
The commands to program shutdown grouping 32
Shutdown on non-fault events 33
Comm. time out 33
Responding to communication time out events 33
Turn-on and reset behavior 34
Time out events as reflected in the status structure 34
Chapter 5: Commands and Queries Reference 35
Categories 35
IEEE 488.1 BUS Commands 35
System Commands and Queries 35
Settings Commands and Queries 37
Output Control Commands and Queries 37
Protection Commands and Queries 37
Warnings Commands and Queries 38
Read-Back Queries 38
Trigger and Sync Commands and Queries 38
Status Reporting Commands and Queries 39
Synch. Commands and Queries 39
Alphabetical reference 40
Chapter 6: Status reporting 69
IEEE 488.2 compatible Status Structures 69
Power Modules Status Structure 69
The Events Register 69
The Warnings Register 69
The Output Register 70
The Faults Register 70
The Status Register 70
The Error Code 70
The Events Enable Register 70
The Events Filtering Positive Mask Register 71
The Events Filtering Negative Mask Register 71
Power Modules Summary Register - read with SRQS? 72
XMP 2600 System Status Structure 72
Standard Event Status Register - read with *ESR? 72
Standard Event Status Enable Register - set with *ESE read with *ESE? 73
Primary Status Register - read with PSR? 73
Primary Event Status Register - read with PER? 73
XMP 2600 Programming Manual rev. 1.1 k
Table of Contents
Self Test Results 75
Power Modules 75
Main Controller 76
Error Codes summary 77
Power Modules 77
Main Controller 77
Primary Event Status Enable Register - set with PEE, read with PEE? 73
Status Byte Register - read with *STB? 74
Service Request Enable Register - set with *SRE, read with *SRE? 74
Parallel Poll Enable Register - set with *PRE, read with *PRE? 74
BYTE 1 76
BYTE 2 76
Errors Reported by the Power Module 77
Errors Detected by the Main Controller 77
Power Modules Communications errors 77
RS232 Communications errors 78
GPIB Communications errors 78
Parser and Execution errors 78
l XMP 2600 Programming Manual rev. 1.1
Interfacing the XMP 2600 The GPIB interface
1
Interfacing the
XMP 2600
The XMP 2600 has two types of interfaces used for remotely controlling it: a GPIB
(IEEE 488) Interface and a Serial (RS232) Interface. The two interfaces differ only in the
communication hardware and protocol. Input and Output Queues, Command and Query
Parsing and Execution are identical no matter which interface is being used to remotely
control the XMP 2600.
The XMP 2600 has two remote controlling modes. Unless otherwise required, the IEEE
488.2 compatible mode should be used. The controlling mode in effect is DIP-Switch
selected (at the rear panel – please refer to the user’s guide) and may be overridden by a
Remote command.
The GPIB interface
The GPIB Interface is an IEEE 488.1 hardware interface with IEEE 488.2 capabilities.
The capabilities of the GPIB Interface are summarized below:
SH1 ........................Source handshake - FULL.
AH1 .......................Acceptor handshake - FULL.
T6........................... Talker - basic, serial poll, unaddressed if MLA.
L3........................... Listener - basic, listen only, unaddressed if MTA.
SR1 ........................Service request - FULL.
RL1 ........................Remote local - FULL.
PP1/PP2 .................Parallel poll - remote and local configuration.
DC1........................ Device clear - FULL.
DT1........................ Device trigger - FULL.
The size of the Input and Output Queues is 256 Bytes.
The XMP 2600 uses an Input Queue rather than an Input Buffer (as
required by IEEE 488.2). This enhancement practically prevents LockUps.
XMP 2600 Programming Manual
rev. 1.1 1
The serial interface Interfacing the XMP 2600
The serial interface
The Serial Interface is RS232 hardware interface with three types of operating modes: Monitor
Mode, Remote Terminal Control Mode and Remote Computer Control Mode.
Pressing the terminal’s ENTER key while the Serial Interface is in
Monitor Mode and the GPIB Interface is OFF will cause the Serial
Interface to switch to the Remote Terminal Control Mode.
Serial
Interface
Capabilities
In addition to the Transmit and Receive lines, the interface implements the following
hardware handshake lines:
DTR - ................. Data Terminal Ready.
CTS - .................Clear To Send.
RTS -..................Request To Send.
DCD - ................Data Carrier Detected.
The interface has the following programmable parameters:
Baud Rate - ........2400, 4800, 9600.
Xon/Xoff - .......Yes, No.
Stop Bits - .........1 or 2 depending on the Parity settings.
Parity - .............Odd, Even, None.
Echo - ...............Yes, No.
The number of Start Bits is fixed at 1.
The Serial Interface Parameters are set in the SERIAL SET-UP MODE (see: User’s
Guide).
The Serial Interface always uses “hardware handshake” (signals CTS and
RTS). If you do not wish to utilize those signals, short pins 7 and 8 of the
connecting cable, on the XMP’s side (see the User’s Guide for further
details).
Computer
Versus
Terminal
Operation
The selection of the ECHO parameter determines the Remote Control Mode of operation
by changing some aspects of the behavior of the Serial Interface, as detailed below:
echo Yes (terminal) No (computer)
echo echo each received character no echo
prompt '>' {ACK}
SRQ string '{bell}SRQ<' 'SRQ<'
terminators {CR} echoed as {CR}{LF} {CR}{LF} or {LF}
In the Computer Remote Control mode of operation, the XMP 2600 will respond to each
command string with an ASCII {ACK} - 06 HEX.
2 XMP 2600 Programming Manual rev. 1.1
Interfacing the XMP 2600 Programming messages formats
Programming messages formats
Listening
Formats
Programming messages received by the XMP 2600 are comprised of the following
elements:
Program Message.......................... a programming command, query or data sent to the
XMP 2600 from the Controller. A Program Message
may have zero or more of the following:
Program Message Unit .. the actual command or query (including data) sent to
the XMP 2600 by the Controller. A Program Message
Unit is either a Command Message Unit or a Query
Message Unit. The Program Message Unit is made
out of the following elements:
Command Program Header or Query Program Header
............................. the Program Header represents the operation to be
performed by the XMP 2600. A Query Program
Header is always ended with a “?”. Headers can be in
Lower or Upper Case letters.
Program Header Separator separates the Program Header
from the Program Data elements. It is the ASCII
character <white space>.
Program Data ...... zero or more Program Data elements separated by a
Program Data Separator may be included in the
Message Unit (as required by the specific Program
Header). A Program Data element may be one of the
following:
<ch> ............ Channel Number is a decimal number in the range 1
to 16.
<value> ....... a Decimal Value expressed either in implicit or
explicit point format. In some cases a sign (“+” or “-”)
may precede it.
<int>............ a Decimal Integer Value.
<string>....... a series of ASCII characters enclosed within a pair of
a specific character.
Program Data Separator separates Program Data elements. It is
the ASCII character “,” and may have any number of
<white space> characters surrounding it.
Program Message Unit Separator separates Program Message Units
contained within a single Program Message. The
Separator is the ASCII character “;” and may have
any number of <white space> characters surrounding
it.
Program Message Terminator ...... terminates the Program Message. Together they form
a complete transmission. The Terminator may be one
of the following:
<LF> or <NL>.............. Line Feed or New Line (ASCII code 10).
<CR><LF> ................... Carriage Return & Line Feed (ASCII codes 13 & 10).
<EOI>............................ the GPIB single line EOI message. It may be
combined with a <LF> ASCII code byte.
XMP 2600 Programming Manual
rev. 1.1 3
Programming messages formats Interfacing the XMP 2600
Here is an example of a Program Message:
VSET 1,10.2 ; VLOAD? 1 <LF>
Talking
Formats
Command
Program
Header
<ch>
Program
Message
Terminator
<ch>
Response Messages sent by the XMP 2600 are comprised of the following elements:
Response Message ......................... a message sent by the XMP 2600 in response to a
Program
Data
Separator
<value>
Query received from the Controller. The Response
Message is made out of the following elements:
Response Data...... one or more Response Data elements separated by a
Response Data Separator may be included in the
Response Message (as required by the specific Query
that generated that Response). A Response Data
element may be one of the following:
<value> ....... a Decimal Value expressed either in implicit or
explicit point format. In some cases a sign (“+” or “-”)
may precede it.
<int>............ a Decimal Integer Value 0 to 255.
<string>....... a series of ASCII characters.
Response Data Separator separates Response Data
elements. It is the ASCII character “,” and may have
<white space> characters surrounding it.
Response Message Terminator terminates the Response Message.
Together they form a complete transmission. The
Terminator is <CR><LF> (Carriage Return and Line
Feed ASCII codes 13 and 10). For GPIB the <LF>
character will have <EOI> asserted.
Program
Unit
Message
Separator
Query
Program
Header
4 XMP 2600 Programming Manual rev. 1.1
Usage Guidelines How to communicate with the XMP 2600
2
Usage Guidelines
How to communicate with the XMP 2600
The purpose of this section is to give the user of the XMP 2600 power system basic
guidelines on how to communicate with the Power Supply.
Communicating with the XMP 2600 involves proper usage of the communication
channels (either GPIB or RS232), understanding how the XMP 2600 handles the
communication from/to the controlling computer and learning the recommended way to
communicate with the XMP 2600.
The following sections will tackle the aforementioned issues, in detail.
Using the
comm.
channels
To communicate with the XMP 2600 one can use either the GPIB bus or an RS232 link.
Beyond the basic differences between the two communication mediums (not covered in
this manual) both provide the user of the XMP 2600 full access to the XMP’s features.
The only advantage of the GPIB bus (beyond its hardware characteristics) is the ability to
send bus commands, such as DCL (Device Clear).
Using the GPIB bus
There are several options for terminators to use when communicating with the XMP
2600:
1. EOI
2. LF (or CRLF)
3. LF + EOI
We recommend the use of LF (without EOI).
Do not use the “auto serial poll” feature of some GPIB drivers. If you want to use SRQs,
do the serial poll (or use the *STB? Query) in your program.
Using an RS232 link
RS232 is an asynchronous communication link. The XMP 2600 uses a software method
to synchronize communication with it: for every command or query message (ending
with a LF or CRLF) that you send to the XMP 2600 it will reply with the ASCII character
ACK (acknowledge) – 6 Hex.
This method provides assurance that the communication link is working properly and
serves the function of the handshake lines of the GPIB bus.
XMP 2600 Programming Manual
rev. 1.1 5
How to communicate with the XMP 2600 Usage Guidelines
To use this synchronization feature properly, you must follow each message sent to the
XMP 2600 with a read operation, reading one character and verifying its value (6).
Recovering from communication halts
If, for some reason, communication with the XMP 2600 halts, use one of the following
methods to clear the XMP’s input and output queues and reestablish communication:
1. Press the front panel LOCAL button.
2. Send a GPIB bus DCL (Device Clear) multi-line command.
3. Reset the XMP 2600 using the front panel buttons DEL & LOCAL.
4. Reset the XMP 2600 using the hardware command (on/off) connector at its rear.
5. Reset the XMP 2600 by cycling its power.
The XMP’s
input and
output
queues
Communicate
with the XMP
2600
The XMP 2600 uses two queues (256 bytes long, each) for holding input (data you send
to the XMP) and output (replies you should read from the XMP).
You must make sure not to fill those queues up or communication with the XMP 2600
may, in some situations, fail.
The following paragraphs elaborate on the proper usage of commands and queries while
communicating with the XMP 2600.
Using queries
When using queries (questions) with the XMP 2600, you must make sure that for each
query that you send to the XMP 2600, you read the reply the XMP 2600 has placed in its
output queue.
Although it is possible to send several queries and then read all the replies (you will need
a separate read for each reply), it is a better practice to send a single query and read its
reply before sending another query.
If for some reason you find out that the reply you are reading is not for the query you
have sent (lost of synchronization between replies and queries) send the BUFCLR
command or use one of the procedures depicted above at “recovering from
communication halts”. This operation will clear both the input and the output queues of
the XMP 2600 and resynchronize queries with replies.
Using commands
The XMP 2600 stores the commands (and queries) that you send to it in its input queue
until it is ready to parse and execute them.
Parsing and executing the commands and queries is done when the XMP 2600 is not busy
communicating with its Power Modules.
This means that command execution might be held of for as long as a second (usually
commands are executed within 200mS).
If you send many commands with short intervals between them, sometimes you may get
into a situation where the XMP’s input queue will fill up due to commands waiting for
execution. This might lead to a communication halt.
Programming the XMP 2600
Bearing in mind all of the above, you should follow the guidelines in the following
paragraphs:
6 XMP 2600 Programming Manual rev. 1.1
Usage Guidelines Recommendations on using the XMP 2600
Starting a session
Issue a CLR or RESET command (and wait for 15 seconds) when you start using the
XMP 2600.
This will ensure that the XMP 2600 is in a known state, ready for you to program it.
When queries are not used
If you do not use queries often (see bellow) in your program, send commands in small
groups (no more than 4 per second). Use delays to spread commands over time, if
necessary.
This way you can make sure you will not fill up the input queue of the XMP 2600.
Use queries
Following each group of commands, send a query and read its reply.
This procedure will make sure that the commands in the input queue were executed
(because the query was last in the queue) and the queue is empty.
It is a good practice to send status queries (*STB?) every now and then to make sure the
XMP 2600 has no errors or faults to report. Following each *STB? query, you may need
to send more status queries, depending on the reply of the XMP 2600 (see the Handling
SRQ and the IEEE488.2 Status Structures section for more details).
It is, also, a good idea to read the output voltage of each Power Module, following the
setup stage of your program. This way you can be sure that the XMP 2600 is outputting
the voltages you have requested.
If you follow each group of commands, sent to the XMP 2600, with a query (and read the
reply to the query) you may freely send commands as fast as the XMP 2600 is ready to
receive them.
A focus on status
Following every major operation with the XMP 2600 (such as changing output values,
turning a Power Module on or off, etc.), read its status (or use SRQ to be interrupted
when errors or faults occur).
Reading the status of the XMP 2600 often, ensures communication synchronization.
Recommendations on using the XMP 2600
The purpose of this section is to give the user of the XMP 2600 power system basic
guidelines on how to use the XMP 2600.
Using the XMP 2600 power system is divided into two tasks: initialization and on-going
usage.
The following sections will engage in giving the user of the XMP 2600 an understanding
of the recommended way to achieve those two tasks.
Initialize the
XMP 2600
XMP 2600 Programming Manual
When working with a device rich in features, like the XMP 2600, it is essential for the
user to know exactly what state the device is in and how it is setup.
Going through an ordered initialization phase can assure the user of the XMP 2600 that
the power system is setup exactly like he wanted it to be.
rev. 1.1 7
Recommendations on using the XMP 2600 Usage Guidelines
Identify the XMP 2600
Using the *IDN? query, it is possible to verify that the device you are communicating
with is indeed a XMP 2600 power system.
The *IDN? query also returns the firmware revision code for the XMP’s main controller.
Use the GPIB? query to make sure the XMP 2600 is operating in IEEE488.2 mode.
Enforce power-on conditions
Power-on retain
Using the XMP 2600 in a computer controlled environment eliminates the need to use the
Power On Retain feature because the controlling computer can easily re-program the
XMP 2600 to a required state.
Therefore, set the Power On Retain feature to OFF (or NO). This can be done manually
(using the front panel, in setup mode) or using the POR command. The XMP 2600 will
remember your selection when it is turned off.
Clear / Retain Event Enable Registers
Similar to the Power On Retain issue, it is better to let the XMP 2600 clear the Event
Enable Registers at power-on.
Clearing the Event Enable Registers is the default behavior of the XMP 2600 at poweron. Using the *PSC command, the XMP 2600 can be instructed to the behavior suitable
for the user.
Use a CLR or RESET command
Use either the CLR (clear) or the RESET command to force the XMP 2600 to its initial
conditions.
The RESET command will set the XMP 2600 to the exact state it would be in following
turn-on.
The CLR command is similar to the RESET command with the following differences:
It will take the minimum number of actions necessary to set the XMP 2600
to its turn-on state. In contrast to the RESET command, Power Modules
will not be reset if not necessary for clearing malfunctions.
The XMP 2600 main status structure is not cleared.
Following a CLR or RESET command you should wait for 15 seconds before attempting
to communicate with the XMP 2600.
Setup the XMP 2600 status system
Before dealing with the Power Modules and to complete the XMP 2600 power system
initialization, you should setup the mask registers of the XMP’s main controller status
structure.
Use commands like *ESE, *PRE, *SRE and PEE to setup the XMP’s event and SRQ
generation masks.
Query installed Power Modules
Before using the XMP 2600 power system, it is a good practice to make sure that the
system contains the Power Modules that you expect it to have.
8 XMP 2600 Programming Manual rev. 1.1
Usage Guidelines Recommendations on using the XMP 2600
Check occupied channels
Power Modules of the XMP 2600 have addresses that assign them to “channels” (or
“slots”).
Use the CHNL? query to find out which channels are occupied by Power Modules.
Check installed Power Modules
Once you know what channels are occupied, your next step is to verify that those
channels are assigned the correct Power Modules.
For each occupied channel, use the VMAX?, IMAX?, IMIN? and OPT? queries to learn
the following:
Output voltage rating of the Power Module.
Output current rating of the Power Module.
Minimal allowed value for current limit (or current set) programming of the
Power Module.
Installed options, like: output disconnect relays, polarity relays and type of
disconnect relays.
You may also use the SN? query to get the Power Module’s serial number, for further
identification.
Setup system level protection shutdown features
The XMP 2600 has many protection features geared at protecting the connected loads.
Some protection features have programmable system wide effect you should consider and
setup.
Reaction to Power Modules events
Use the CESE command to inform the XMP 2600 of the Power Modules whose events
you would like it to respond to.
Using commands like GLBL, GRP and SHUT you control the way the XMP 2600 reacts
to Power Modules faults and warnings.
Handling controller communications drops
The controller communications monitor function of the XMP 2600 give you the
confidence that the loads connected to the power system are protected even when
communication with the controlling computer is halted.
Use the TOGRP, TOSET and TOEN commands to setup this feature, when you intend to
use it.
Initial setup of the Power Modules
Following global setup of the XMP 2600 power system, you are now ready to setup
individual Power Modules.
The process of setting up a Power Module deals with three issues: protection features,
output settings and status reporting.
Note that most programmable features have default values (or states) that are suitable for
most applications, thus simplifying the setup process.
XMP 2600 Programming Manual
rev. 1.1 9
Recommendations on using the XMP 2600 Usage Guidelines
Protection setup
Use the PROT command to setup the way Over Voltage and Over Current protection
values are assigned (automatically or manually).
If you have decided to use manual protection settings, use the OVSET and OCSET
commands to setup the desired protection values.
Select the Foldback scheme you wish to use (FOLD command) and the amount of
reprogramming delay you wish to apply (DLY command).
If you wish to use the window feature of the XMP 2600 (in order to receive warnings or
employ an Under Voltage or Under Current protection mechanism) enable the proper
window level thresholds using the WHIGH and WLOW commands.
Use the POLEN command to enable the XMP 2600 to process negative voltage setting
values.
Output settings
Setup the desired output values (VSET and ISET commands) and, optionally, the window
thresholds (VLOW, VHIGH, ILOW and IHIGH).
Remember that high window values can only be programmed to values above the
appropriate set values. Thus, for example, if you wish to use a window high current
threshold value lower than the limiting output value (ISET) you should program ISET to
the expected value, setup the ILOW and IHIGH values and then raise ISET to the limit
value.
Set the desired initial state of the output disconnect (DISC command) and polarity (POL
command) relays.
If the hardware SYNC signal is going to be used, use the SYNC command to tell the
Power Module when to generate a SYNC signal.
Setup the Power Module’s reaction to a hardware or software trigger, using the TRIG
command.
Status reporting
If so desired, use the CMASK command to setup each Power Module’s event filtering
mechanism. This mechanism enables you to limit the type of events reported by the
Power Modules to the XMP’s main controller.
Activation
Once everything is setup properly, you are ready to activate the outputs of the XMP 2600.
Output on
For a Power Module’s output to be active, the following conditions must be met:
The Main Converter is operating. •
•
The XMP 2600 is globally “turned on”.
•
The Power Module is turned on.
•
The Power Module does not report any fault.
•
The output disconnect relay is closed.
To control the output of an individual Power Module, use the OUT command with the
module’s number as a parameter.
10 XMP 2600 Programming Manual rev. 1.1
Usage Guidelines Handling SRQ and the IEEE488.2 Status Structures
To globally control the outputs of all the Power Modules, use the OUT command with no
module number.
Verification
Read the output voltage and/or current of the activated Power Modules. Use the VOUT?
(measured at the output connector), VLOAD? (measured at the sense lines) and IOUT?
queries to verify proper operation. Allow at least a second from the output activation to
the time you read back the output’s actual values.
On-going
usage of the
XMP 2600
The XMP 2600 uses two queues (256 bytes long, each) for holding input (data you send
to the XMP) and output (replies you should read from the XMP).
You must make sure not to fill those queues up or communication with the XMP may, in
some situations, fail. For further details, please refer to the previous section.
Use queries
Following each group of commands, send a query and read its reply.
This procedure will ensure that the commands in the input queue have been executed
(because the query was last in the buffer) and the queue is empty.
It is a good practice to send status queries (such as *STB?) every now and then to make
sure the XMP 2600 has no errors or faults to report. Following each *STB? query, you
may need to send more status queries, depending on the reply of the XMP 2600 (see the
Handling SRQ and the IEEE488.2 Status Structures section for more details).
If you follow each group of commands, sent to the XMP 2600, with a query (and read the
reply to the query) you may freely send commands as fast as the XMP 2600 is ready to
process them.
Using advanced features
Consult the Advanced Features chapter of the programming manual and other application
notes on how to use the advanced features of the XMP 2600.
A focus on status
Following every major operation with the XMP 2600 (such as changing output values,
turning a Power Module on or off, etc.), read its status (or use SRQ to be interrupted
when errors or faults occurs).
Reading the status of the XMP 2600 often, ensures communication synchronization
Handling SRQ and the IEEE488.2 Status Structures
The purpose of this section is to clarify the usage of the XMP’s Status Structures, explain
how to set it up and how to respond to SRQ’s.
The Status Structures of the XMP 2600 follow the guidelines of the IEEE488.2 standard.
The Status Structures are based on a “tree” formation: the “leaves” are the detailed status
information and the branches summarize that information down to a single bit of
information.
A graphical depiction of the formation of the Status Structures is shown in the Status
Reporting chapter (chapter 6).
XMP 2600 Programming Manual
rev. 1.1 11
Handling SRQ and the IEEE488.2 Status Structures Usage Guidelines
The status reporting mechanisms of the XMP 2600 are rather complex. If
you do not intend to use the advanced warnings and protection features of
the XMP 2600 you may choose to disregard most of the reported status
with the exception of the main status byte and the error code registers.
Definitions of
structural
elements
We will start this discussion with a short explanation of the various elements comprising
the Status Structures.
Status registers
The status registers are collections of bits (usually 8) that depict the current state of
elements within the XMP 2600 system. Each bit reflects the actual state of a feature or
sub-assembly. When the state of the feature or sub-assembly changes so does the value of
the status bit.
For example, lets look at the STBY bit (bit 0) of the Output Status Register of a Power
Module. This bit will always reflect the state of the output of the Power Module: when
the Power Module’s output is in standby (i.e. the output is disabled and no voltage is
coming out of its connector) the bit value will be 1. When the Power Module’s output is
enabled, the bit value will be 0.
Event registers
Event registers indicate changes in the status of features or sub-assemblies. Note that in
contrast to the status registers, event bits remain set (having a value of 1) even if the
status changes back. The event indication will be cleared when the controlling computer
reads the event register.
For example, the FLT bit (bit 2) of the Event Register of a Power Module will be set
when a fault occurs (individual faults are indicated by the bits of the Faults Register).
When the fault condition is removed (e.g. an Over Temperature condition is no longer
valid) the corresponding Faults Register bit will be cleared but the FLT bit of the Event
Register will remain set.
When the computer reads the Event Register, the FLT bit is cleared even if the actual
fault condition is still true (as will be depicted by the Faults Register). The FLT bit will
be set again when a new fault condition occurs.
Event enable registers
As mentioned in the introduction, each status structure is summarized to a single bit that
is then used in the next level of status (or event) registers.
The Event Enable Register determines the way data is being summarized. The process is
fairly simple: the Event Register is ANDed with the Event Enable Register and if the
result has any set bits then the summary bit is set.
Mask registers
Some of the Status Structures of the XMP 2600 include (fixed or programmable) Mask
Registers. These registers determine which status changes will be registered as events.
For example, only positive Primary Status changes (i.e. a change from non-existing to
existing) are recorded in the Primary Event Register.
The Status Structure of the Power Modules include a programmable event filtering
mechanism that enables filtering of either positive or negative transitions of warning
conditions.
12 XMP 2600 Programming Manual rev. 1.1
Usage Guidelines Handling SRQ and the IEEE488.2 Status Structures
Responding
to SRQ
events
The SRQ event of the IEEE488.2 bus is the summary of the entire Status Structure of the
XMP 2600.
The following paragraphs will show how to traverse the Status Structure tree in order to
find the cause of the generated SRQ.
This explanation will, also, show how to setup the programmable elements of Status
Structure in order to be notified only on events of interest.
The (main) status byte
The SRQ event is generated in response to bits of the Status Byte being set (a positive
transition).
Each time a bit of the Status Byte is being set (changing from 0 to 1) the Status Byte is
being ANDed with the Service Request Enable Register. If the result of the AND
operation has any bits set to 1 – an SRQ will be generated. In other words – the SRQ
event (or flag) is the summary of the Status Byte and the Service Request Enable Register
is the “Event Enable Register”.
Thus, the first response to an SRQ event is to read the Status Byte. This can be achieved
in two fashions: performing a serial poll or issuing the *STB? Query.
Once we have got the value of the Status Byte, we can investigate the cause of the SRQ
event.
The Status Byte summarizes the following Status Structures:
ESB - XMP’s main controller events
MAV - Output Message Queue (Message AVailable).
COM TO – Remote Communications Time Out.
PRIM ERR - XMP’s Primary Engine (main converter) faults.
SRQ IS - Power Modules.
Whenever one of these bits is set, the corresponding higher level of the Status Structure
should be probed.
Main controller events
This part of the Status Structure is made out of an Event Register and its corresponding
Event Enable Register. The summary of this pair of registers appears in the Status Byte in
the form of the ESB bit.
The main controller’s Event Register (also called the Standard Event Status Register)
holds the Power On, Error and OPC events. The register is read using the *ESR? Query.
The last known error code is read using the ERR? Query.
The OPC event (OPeration Complete) occurs when the *OPC command follows a
lengthy operation (e.g. a change in the output voltage of a Power Module – VSET
command).
The PON event occurs when the XMP 2600 is powered up.
Output message Queue
The MAV (Message AVailable) bit of the Status Register is the only element of this part
of the Status Structure.
The bit is set to 1 whenever the Output Queue holds a response to a query.
This enables the software of the controlling computer to work with the XMP 2600
asynchronously.
XMP 2600 Programming Manual
rev. 1.1 13
Handling SRQ and the IEEE488.2 Status Structures Usage Guidelines
Remote communication time out
The Remote Communications Time Out bit is the only element of this part of the Status
Structure.
The bit is set to 1 when the Time Out mechanism is enabled and a Time Out event occurs.
Primary engine status structure
The Status Structure associated with the Primary Engine of the XMP 2600 is made out of
the Primary Status Register, a fixed positive Mask Register, the Primary Event Status
Register and the Primary Event Status Enable Register.
The summary bit of this Status Structure (the PRIM ERR bit) will be set when Primary
events are registered in the Primary Event Status Register and the corresponding bits of
the Primary Event Status Enable Register are set. Note that the Primary Event Status
Register records only occurrences of conditions and does not register anything when a
condition is removed (this is the work of the positive Mask Register).
If the PRIM ERR bit was read as 1, the Primary Event Status Register should be read
(using the PER? Query). This will reveal what Primary event has occurred since the
register was last read.
The actual status of the Primary Engine can be obtained using the PSR? Query.
Summary of power modules status
Each of the Power Modules in the XMP 2600 system has its own Status Structure. The
summary bits of those Status Structures are grouped in a 16-bit register (read as two 8 bit
registers) called the Power Modules Summary Register.
This register (read with the SRQS? Query) is summarized in the Status Byte as the SRQ
IS bit.
The SRQ IS bit will be set whenever one of the bits of the Power Modules Summary
Register is changed to 1.
The content of the Power Modules Summary Register is cleared when the controlling
computer reads the register.
Bits of the Power Modules Summary Register are set when Power Modules events seep
through the filters of the Power Modules Status Structures.
When the SRQ IS bit of the Status register was read as 1, the Power Modules Summary
Register should be read. For each set bit in the Power Modules Summary Register the
corresponding Power Modules Status Structure should be explored.
Power modules status structure
The Status Structure of the Power Modules is made out of the following elements:
• Status Registers – Warnings, Output state, Faults, Error Code and general
Status.
• Mask Registers – some are fixed and some are programmable.
• Event Register.
• Event Enable Register.
The summary bit of the entire structure is read at the Power Modules position in the
Power Modules Summary Register (e.g. the summary bit of module number 3 will be
evident at bit 2 of the summary register [bits are counted starting with 0]).
The Power Module Status Structure is read as a whole using the CSTS? Query.
14 XMP 2600 Programming Manual rev. 1.1
Usage Guidelines Handling SRQ and the IEEE488.2 Status Structures
The first element of the Power Module Status Structure we should look at is the Events
Register.
The Events Register
The Events Register, together with its corresponding Events Enable Register generates
the summary bit. Note that the Events Enable Register is common to all the Power
Modules.
The Events Enable Register determines which of the Power Modules Events may cause
an SRQ.
The content of the Events Register is cleared when read.
The Events Register, in turn, receives its data from the filtered status registers. The status
registers’ data is filtered using the mask registers. The following paragraphs will describe
the behavior of the status registers and their associated mask registers.
The Error Code
This register holds the last known error detected by the Power Module. The content of
this register is cleared when read.
Whenever the Power Module detects a new error, the corresponding bit of the Event
Register is set as well (a positive fixed mask).
The Faults Register
This register indicates the faults detected by the Power Module’s controller. This is a
status register (showing the current state of the Power Module) but most of the faults are
“sticky” – the fault condition remains true until a reset command is issued.
Any new fault detected by the Power Module’s controller will cause the corresponding bit
of the Events Register to be set (a positive fixed mask). The exception to this rule is the
Sense Warning condition, which is depicted in the Faults Register but is filtered the same
way that warning events are (see bellow).
The Output Register
This status register depicts the current state of the Power Module’s output circuitry.
Any change in the Output status register will cause the corresponding bit of the Events
Register to be set (no masking).
The Warnings Register
This status register indicates warning conditions. As it is a status register, it will indicate
the current true state of the warnings.
Using the programmable mask registers (both positive and negative masks) the conditions
that will cause the WRN bit of the Events Register to be set can be determined.
These mask registers are individual to each Power Module and enable a very flexible
setup. A description of this feature is included in the Status Reporting chapter of the
Programming Manual.
What
happens
when power
is turned on
XMP 2600 Programming Manual
An IEEE488.2 defined command (*PSC) determines what will the XMP 2600 do with the
event enable registers when turned on.
The *PSC command may enable the XMP 2600 to clear all the events enable registers
and the SRQ Enable Register.
This feature ensures that the XMP 2600 wakes up with a known state. It also ensures that
the XMP 2600 will not generate undesirable SRQ’s at power on.
rev. 1.1 15
Loading...