Owner's manual
Table Of Contents
- SECTION 1 - INTRODUCTION
- SECTION 2 - INSTALLATION
- SECTION 3 - CALIBRATION
- SECTION 4 - OPERATION
- FIGURE 1-1. Remotely Controlled Power Supply Configurations Using Kepco Products
- SECTION 1 - INTRODUCTION
- 1.1 Scope of Manual
- 1.2 General Description
- TABLE 1-1. Kepco BIT 488, BIT 4882, and BIT 4886 Digital Programming Cards
- TABLE 1-2. Applicability of BIT 4882, 4882-F and BIT 4886 Cards to Specific BOP Models
- 1.3 Specifications, BIT 4882, BIT 4882-F and BIT 4886
- TABLE 1-3. Specifications, BIT 4882, BIT 4882-F AND BIT 4886
- SECTION 2 - INSTALLATION
- 2.1 Unpacking and Inspection
- 2.2 Set Start-up DefaultS
- 2.2.1 Set (GPIB) Device Address
- 2.2.2 Start-up Language Default
- 2.2.3 IEEE Cable Shield Ground Selection
- 2.2.4 Set Power Supply Identification Switch
- FIGURE 2-1. BIT 4882 and BIT 4882-F Switch and Adjustment Locations
- TABLE 2-1. Power Supply Identification Switch S2 Setting
- 2.3 Installation of Interface Card into the BOP
- TABLE 2-2. Device Address Selection
- FIGURE 2-2. Installation of Model BIT 4882-f into BOP
- FIGURE 2-3. Installation of Model BIT 4882 into BOP
- 2.4 Input/OUtput Signals
- TABLE 2-3. Input/Output Pin Assignments
- FIGURE 2-4. IEEE 488 (GPIB) Connector
- SECTION 3 - CALIBRATION
- 3.1 Equipment Required
- 3.2 Adjustment of the Bop ±10 Volt Calibration Controls (R31, R32)
- 3.3 Adjustment of the Ammeter Zero (R50)
- FIGURE 3-1. BOP Power Supply, Internal Calibration Control Locations
- 3.4 Adjustment Of The Output Voltage Zero (R81)
- 3.5 Adjustment of the Full Scale Output Voltage (R21)
- TABLE 3-1. BOP Power Supply, Internal Calibration Controls
- 3.6 Voltage Reading Zero Calibration (R35)
- 3.7 Voltage Reading Calibration (R19)
- 3.8 Adjustment of the Output Current Zero (R83)
- 3.9 Adjustment of the Full Scale Output Current (R22)
- 3.10 Current Reading Zero Calibration (R36)
- TABLE 3-2. Calibration Measurements and Tolerances - Current
- TABLE 3-3. Suggested Sense Resistors
- FIGURE 3-2. Current Shunt Connections
- 3.11 Current Reading Calibration (R20)
- SECTION 4 - OPERATION
- 4.1 General
- 4.2 IEEE 488 (GPIB) Bus Protocol
- TABLE 4-1. IEEE 488 (GPIB) Bus Interface Functions
- TABLE 4-2. IEEE 488 (GPIB) Bus Command Mode Messages
- TABLE 4-3. IEEE 488 (GPIB) Bus Data Mode Messages
- 4.3 SCPI Programming
- 4.3.1 SCPI Messages
- 4.3.2 Common Commands/Queries
- 4.3.3 SCPI Subsystem Command/Query Structure
- FIGURE 4-1. Tree Diagram of SCPI Commands Used with BIT 4882, BIT 4882-F and BIT 4886 Interface Card
- 4.3.4 Program Message Structure
- TABLE 4-4. SCPI Command Index
- 4.3.4.1 Keyword
- TABLE 4-5. Rules Governing Shortform Keywords
- FIGURE 4-2. Message Structure
- 4.3.4.2 Keyword Separator
- 4.3.4.3 Query Indicator
- 4.3.4.4 Data
- 4.3.4.5 Data Separator
- 4.3.4.6 Message Unit Separator
- 4.3.4.7 Root Specifier
- 4.3.4.8 Message Terminator
- 4.3.5 Understanding The Command Structure
- 4.3.6 Program Message Syntax Summary
- 4.3.7 SCPI Program Example
- FIGURE 4-3. Typical Example of Interface Card Program Using SCPI Commands
- 4.4 CIIL Programming
- APPENDIX A - SCPI COMMON COMMAND/QUERY DEFINITIONS
- TABLE A-1. IEEE 488.2 Command/query Index
- A.2 *CLS — Clear Status Command
- A.3 *ESE — Standard Event Status Enable Command
- TABLE A-2. Standard Event Status Enable Register and Standard Event Status Register Bits
- A.4 *ESE? — Standard Event Status Enable Query
- A.5 *ESR? — Event Status Register Query
- A.6 *IDN? — Identification Query
- A.7 *OPC — Operation Complete Command
- A.8 *OPC? — Operation Complete Query
- A.9 *RST — Reset Command
- FIGURE A-1. GPIB Commands
- A.10 *SRE — Service Request Enable Command
- TABLE A-3. Service Request Enable and Status Byte Register Bits
- A.11 *SRE? — Service Request Enable Query
- A.12 *STB? — Status Byte Register Query
- A.13 *TRG — Trigger Command
- A.14 *TST? — Self Test Query
- A.15 *WAI — Wait-To-Continue Command
- APPENDIX B - SCPI COMMAND/QUERY DEFINITIONS
- B.1 Introduction
- TABLE B-1. SCPI Subsystem Command/query Index
- B.2 INITiate[:IMMediate] Command
- B.3 INITiate:CONTinuous Command
- B.4 INITiate:CONTinuous Query
- FIGURE B-1. Programming the Output
- B.5 MEASure[:SCALar]:CURRent[:DC]? Query
- B.6 MEASure:VOLTage[:SCALar][:DC]? Query
- B.7 [SOURce:]CURRent[:LEVel][:IMMediate][:AMPlitude] Command
- B.8 [SOURce:]CURRent[:LEVel][:IMMediate][:AMPlitude] Query
- B.9 [SOURce:]CURRent:[:LEVel]TRIGgered[:AMPlitude] Command
- B.10 [SOURce:]CURRent:[:LEVel]TRIGgered[:AMPlitude]? Query
- B.11 .[SOURce:]VOLTage[:LEVel][:IMMediate][:AMPlitude] Command
- B.12 [SOURce:]VOLTage[:LEVel][:IMMediate][:AMPlitude]? Query
- B.13 [SOURce:]VOLTage:[:LEVel]TRIGgered[:AMPlitude] Command
- B.14 [SOURce:]VOLTage:[:LEVel]TRIGgered[:AMPlitude]? Query
- B.15 [SOURce:]FUNCtion:MODE
- B.16 STATus:OPERation:CONDition Query
- TABLE B-2. Operation Condition Register, Operation Enable Register, and Operation Event Register ...
- B.17 STATus:OPEReration:ENABle Command
- B.18 STATus:OPEReration:ENABle? Query
- B.19 STATus:OPERation[:EVENt] Query
- B.20 STATus:PRESet Command
- B.21 STATus:QUEStionable[:EVENt]? Query
- TABLE B-3. Questionable Event Register, Questionable Condition Register and Questionable Conditio...
- B.22 STATus:QUEStionable:CONDition? Query
- FIGURE B-2. Using Status Commands and Queries
- B.23 STATus:QUEStionable:ENABle Command
- B.24 STATus:QUEStionable:ENABle? Query
- B.25 SYSTem:ERRor? Query
- TABLE B-4. Error Messages
- B.26 SYSTem:LANGuage Command
- B.27 SYSTem:VERSion Query
- FIGURE B-3. Using System Commands and Queries
- APPENDIX C - CIIL COMMAND DEFINITIONS
- TABLE C-1. CIIL Subsystem Command/query Index
- FIGURE C-1. FNC — Function Command
- FIGURE C-2. INX — Initiate Op Code Command
- FIGURE C-3. FTH — Fetch Command
- FIGURE C-4. SET Command
- FIGURE C-5. RST — Reset Command
- FIGURE C-6. CNF, IST — Confidence Test, Internal Self Test Commands
- TABLE C-2. CIIL Error Messages
- FIGURE C-7. STA — Status Command
- TABLE C-3. CIIL Error Handling Utility Commands
- FIGURE C-8. GAL — Go to alternate Language Command
BIT 4882 030507 4-7
4.3.4.8 MESSAGE TERMINATOR
The message terminator defines the end of a message. Three message terminators are permit-
ted:
• new line (<NL>), ASCII 10 (decimal) or 0A (hex)
• (<CR>), ASCII 13 (decimal) or 0D (hex)
• both of the above (<CR> <NL>)
Your GPIB interface card software will automatically send a message terminator. For example,
the HP BASIC OUTPUT statement inserts <NL> after the last data byte. When binary data is
exchanged, <END> must be used. The combination <NL><END> terminator can be used for all
data except binary data.
NOTE: Kepco power modules require a message terminator at the end of each program mes-
sage. The examples shown in this manual assume a message terminator will be added
at the end of each message. Where a message terminator is shown it is represented
as <NL> regardless of the actual terminator character.
4.3.5 UNDERSTANDING THE COMMAND STRUCTURE
Understanding the command structure requires an understanding of the subsystem command
tree illustrated in Figure 4-3. The “root” is located at the top left corner of the diagram. The
parser goes to the root if:
• a message terminator is recognized by the parser
• a root specifier is recognized by the parser
Optional keywords are enclosed in brackets [ ] for identification; optional keywords can be omit-
ted and the power supply will respond as if they were included in the message. The root level
keyword [SOURce] is an optional keyword. Starting at the root, there are various branches or
paths corresponding to the subsystems. The root keywords for the Interface Card are :INITiate,
:MEASure, :OUTPut, [:SOURce], :STATus, and :SYSTem. Because the [SOURce] keyword is
optional, the parser moves the path to the next level, so that VOLTage, CURRent, and FUNC-
tion commands are at the root level.
Each time the parser encounters a keyword separator, the parser moves to the next indented
level of the tree diagram. As an example, the STATus branch is a root level branch that has
three sub-branches: OPERation, PRESet, and QUEStionable. The following illustrates how
SCPI code is interpreted by the parser:
STAT:PRES<NL>
The parser returns to the root due to the message terminator.
STAT:OPER?;PRES<NL>
The parser moves one level in from STAT. The next command is expected at the level defined
by the colon in front of OPER?. Thus you can combine the following message units
STAT:OPER? and STAT:PRES;
STAT:OPER:COND?;ENAB 16<NL>
After the OPER:COND? message unit, the parser moves in one level from OPER, allowing the
abbreviated notation for STAT:OPER:ENAB.