Thank you for purchasing the HIOKI "9557 RS-232C CARD / 9558 GP-IB
CARD" . To obtain maximum performance from the product, please read this
manual first, and keep it handy for future reference.
When using the HIOKI MEMORY HiCORDER can be used with the HIOKI
"9557 RS-232C CARD / 9558 GP-IB CARD" except following products, reffer to
the communication comands manual (Flopply disk) supplied with the
MEMORY HiCORDER.
■ The products consultable this manual:
8826, 8835, 8835-01, 8841, 8842
afety Notes
i
This manual contains information and warnings essential for safe operation of
the product and for maintaining it in safe operating condition. Before using
the product, be sure to carefully read the following safety notes.
DANGE
This product is designed to conform to IEC 61010 Safety Standards, and
has been thoroughly tested for safety prior to shipment. However,
mishandling during use could result in injury or death, as well as damage
to the product. Be certain that you understand the instructions and
precautions in the manual before use. We disclaim any responsibility for
accidents or injuries not resulting directly from product defects.
Safety symbol
The following symbols in this manual indicate the relative importance of
cautions and warnings.
In the manual, thesymbol indicates particularly important
information that the user should read before using the product.
The GP-IB (General Purpose Interface Bus) was developed as an interface for
general use by programmable instrumentation, and as an interface is rich in
expandability and has many distinctive features.
There are various interfaces with specific names apart from the GP-IB, such
as the IEEE-488 bus, the IEC bus, and the HP-IB which is an internal
standard within the Hewlett-Packard Company. These are basically the same
standard, but, because the number of connector pins and the arrangement of
the signals and so on differ, much care should be exercised.
GP-IB and RS-232
Interface
3
4
5
6
7
8
9
10
In this explanation of management and operation, only the GP-IB related
resources of the 8835 and 8826 will be described.
If more detailed knowledge of the GP-IB interface is required, reference should
be made to the following literature:
The Institute of Electrical and Electronics Engineers, Inc.: "IEEE Standard
Digital Interface for Programmable Instrumentation", IEEE Std 488.1-1987,
IEEE Std 488.2-1987 (1987)
IFC (Interface Clear)
SRQ (Service Request)Signal which requests a non-synchronous service.
REN (Remote Enable)
EOI (End or Identify)Indicates the last byte of data.
Signal which sets the interface bus system to the
initial condition.
Signal which performs changeover of remote and
local control.
RS-232C is a serial interface standard defined by the EIA (Electronic
Industries Association). It specifies the interface parameters for
communication between a DTE (Data Terminal Equipment) and DCE (Data
Communications Equipment).
The MEMORY HiCORDER incorporates a partial implementation of the RS232C specification (only certain signal lines) to allow data exchange and
remote control using a personal computer.
.2.2Specification
Standard
EIA RS-232C
General Specifications
Communication mode Full-duplex
Synchronization Start-stop synchronization
Transfer rate 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200
(bits/s), (set from the setting screen of the unit)
Start bit 1bit
Stop bits 1 or 2 bits
(set from the setting screen of the unit)
Data length 7 or 8 bits
Parity None, even, or odd
(set from the setting screen of the unit)
Delimiter LF, CR+LF
Flow control Xon/Xoff, hardware, none
The connector on the PC card is a D-sub 9-pin connector (male).
Make connection to the computer using a null-modem cable with the type of
connector that matches the computer.
The GP-IB or RS-232C interface is not isolated from the unit system.
Exercise caution, because the ground of the logic inputs and the GP-IB
or RS-232C interface ground are connected.
Connect GP-IB or RS-232C cable
3
4
5
6
7
8
Check that the power is ON for all
devices connected to the bus. (GP-IB
Check that the power is ON for the
unit. (RS-232C)
Set "INTERFACE.
Send orders to the controller
and perform remote control.
GP-IB set up
RS-232C set up
GP-IB mode
Address
Header
Transfer rate
Data length
Parity
Stop bits
Delimiter
Header
Flow control
When making the connection, the cable connector and PC card should be
properly aligned, so that the connector can be pushed in straight. Do not exert
strong force on the PC card connector, to prevent the possibility of damage
and contact problems.
This section explains procedures for connecting the cable using the 8835 as an
example. For other models, refer to the instruction manual included with the
unit.
(1) Cable and PC card connection
1. Pass the PC card protector through the connection cable, as shown below.
2. Plug the PC card end of the connection cable into the PC card. The top side
of the cable connector (marked with a ▲) should match the top side of the
PC card, as shown below.
The following actions may result in damage to the PC card or connector and
must be avoided.
・Inserting the card with the wrong orientation or in other ways than described
above.
・Inserting the card while attached to the connection cable.
・Moving the unit while the connection cable is connected to the card.
・Pulling the card out by the cable or exerting excessive force on the
connector.
・Placing objects on the connection cable connector.
1. Insert the PC card in the PC card slot on the unit. Verify that the ▲ mark
on the card points in the correct direction as shown below, and make sure
that the card is properly seated in the slot.
The PC card is keyed to prevent wrong insertion, but exerting excessive
force may damage the card or the slot.
1
2
3
4
5
6
2. Attach the PC card protector to the unit as shown below.
4. Enable or disable the headers.
Select whether or not this unit as talker should output
an identifying header at the beginning of each
message it sends.
Move the flashing cursor to the position shown in the
figure on left, and use the function keys to make the
setting.
: Header information is not appended.
: Header information is appended.
NOTE
・The unit automatically recognizes which type of PC card is inserted, and the
appropriate setting items appear on the display. Perform the setting
procedure after inserting the GP-IB card.
・Do not change the settings during communications.
Data received or sent by the GP-IB or RS-232C interface is called a message.
The following are the message types:
Message
Program messages
Response message
Of these, program messages are those received by the unit from the controller,
while response messages are those sent from the unit to the controller.
Program messages are command messages or query messages.
Command messages are orders for control of the device, such as for making
settings or for reset or the like.
Query messages are orders for responses relating to the results of operation,
results of measurement, or the state of device settings.
Response messages are sent in response to query program messages. After a
query message has been received, a response message is produced the moment
that its syntax has been checked.
Command program message
Query program messages
(2) Command syntax
When no ambiguity would arise, the term "command" is henceforth used to
refer to both command and query program messages.
The unit accepts commands without distinction between lower case and upper
case letters.
The names of commands are as far as possible mnemonic. Furthermore, all
commands have a long form, and an abbreviated short form.
In command references in this manual, the short form is written in upper case
letters, and then this is continued in lower case letters so as to constitute the long
form. Either of these forms will be accepted during operation, but intermediate
forms will not be accepted.
Further, during operation both lower case letters and upper case letters will
be accepted without distinction.
The unit generates response messages in the long form (when headers are
enabled) and in upper case letters.
(Example)
For "DISPlay", either "DISPLAY" (the long form) or "DISP" (the short form)
will be accepted. However, any one of "DISPLA", "DISPL", or "DIS" is wrong
and will generate an error.
Commands must have a header, which identifies the command in question.
There are three kinds of header: the simple command type, the compound
command type, and standard command type.
Simple command type header
The first word constitute the header.
Exampl
Simple comman
type header
:HEADer ON
Compound command type header
A header made up from a plurality of simple command type headers marked
off by colons.
Exampl
:CONFigure:TDIV 1.E-3
Simple command
type header
Compound command type heade
Dat
Standard command type header
A command beginning with an asterisk and stipulated by IEEE 488.2
Exampl
*RST
(4) Query program headers
These are for commands used for interrogating the unit about the result of an
operation or about a setting.
These can be recognized as queries by a question mark appearing after the
program header. The structure of the header is identical to that of a
command program header, with "?" always being affixed to the last command.
There are queries possible in each of the three previously described types of
command form.
Exampl
:HEADER? ON
Query program
header
Dat
(5) Response messages
Response messages relating to queries are made up from header portions
(which also may be absent due to header disablement) and data portions
identical to those of program messages, and as a general rule are sent in an
identical format to the format of the program message corresponding to their
originating query.
A terminator is used in order to separate the transmission of one message
from another, and this terminator is not itself included in the message.
GP-IB interface
LF, EOI, or LF+EOI is used as the message terminator, and LF+EOI is also
used as the response message terminator.
RS-232C interface
Set the delimiter for the message terminator (see Section 2.3.2).
Message Unit Separator
A semicolon ";" is used as a message unit separator when it is desired to set
out several messages on a single line.
Exampl
:CONFIGURE:TDIV 1. E-3;:CONFIGURE:SHOT 1
Message unit separato
Header separator
With a message which has both a header and data, a space "_" is used as a
header separator to separate the header from the data. The space "_" is used
by way of explanation, but it does not appear on the actual program.
Exampl
:CONFIGURE:SHOT_1
Header separato
Data separator
Commas are used as data separators for separating several data items from
one another.
Exampl
Simple command type heade
Compound command type heade
:DISPLAY:DRAW CH1,DARK
Data separato
Header separato
(7) The command tree
The rule when writing several messages of compound command form on the
same line, when no colon is prefixed to the next header after the semicolon
(the message unit separator), is that that header is considered as continuing
on from the header before the last colon in the message directly preceding.
This corresponds to the general concept of the current directory in the
directory structure of UNIX or MS-DOS, and this directly preceding header is
called the "current path".
Both Example 1 and Example 2 are messages setting TIME/DIV to 1 ms and
recording length to 15 divisions.
With Example 1, because there is a colon directly after the semicolon, the
current position is the "root". Accordingly the reference of the next command
is performed from the root.
On the other hand, with Example 2, because with ":CONF:TDIV 1. E-3;" the
current path has become ":CONF", it is now possible to omit the ":CONF:"
before "SHOT".
To reiterate, the colon at the beginning of a command forces the search for the
command to begin from the root. Thus in Example 1:
:CONFIGURE:TDIV 1.E-3
The first colon indicates that the "CONFIGURE" command is
at the root level.
(8) Data format
The unit uses character data, decimal data and character string data as a data
format.
Character data
The first character must be alphabetic.
The characters after the first character can only be alphabetic characters,
numerals, or underline characters (_).
As alphabetic characters, during sending only upper case letters are used,
but during receiving both upper case and lower case letters are permitted.
Decimal data
Decimal data values are represented in what is termed NR format.
There are three types of NR format from NR1 to NR3, and each of these can
appear as either a signed number or an unsigned number. Unsigned numbers
are taken as positive.
Further, if the accuracy of a numerical value exceeds the range with which the
unit can deal, it is rounded off. (5 and above is rounded up; 4 and below is
rounded down.)
NR1 format - integer data
Examples: +15, -20, 25
NR2 format - fixed point numbers
Examples: +1.23, -4.56, 7.89
NRf forma
NR3 format - floating point number
Examples: +1.0E-3, -2.3E+3
The term "NRf format" includes all these three formats.
When the unit is receiving it accepts NRf format, but when it is sending it utilizes
whichever one of the formats NR1 to NR3 is indicated in the particular command.
Character string data
Character string data is enclosed within quotation marks.
The data is composed of 8 bit ASCII characters.
Characters which cannot be handled by the unit are replaced by spaces.
When the unit is sending, only the double quotation mark (") is used as a
quotation mark, but when receiving both this double quotation mark and
also the single quotation mark (’) are accepted.
The summary of this register is set in bit 5 of the status byte.
For GP-IB, each bit is masked by setting the standard event status enable
register (which starts off at zero when the power is turned on).
The circumstances when the contents of the standard event status register are
cleared are as listed below.
1. When the *CLS command is received.
2. When the contents have been read by an *ESR? query.
3. When the power is turned off and turned on again.
Bit allocations in the standard event status register
bit 7
PON
bit 6
URQ
bit 5
CME
bit 4
EXE
The power has been turned on again.
Since this register was last read, the unit has been
powered off and on.
User request: not used.
Command error.
There is an error in a command that has been received;
either an error in syntax, or an error in meaning.
Execution error.
An error has occurred while executing a command.
Range error; Mode error.
Device dependent error.
bit 3
DDE
It has been impossible to execute some command, due to
an error other than a command error, a query error, or an
execution error.
bit 2
QYE
Query error.
The queue is empty, or data loss has occurred (queue
overflow).
bit 1Request for controller right (not used) Unused: 0
bit 0
OPC
Operation finished.
Only set for the *OPC command.
The following commands are used to read the standard event status register,
and to set or read the standard event status enable register.
Read the standard event status register *ESR?
Set the standard event status enable register *ESE (GP-IB)
Read the standard event status enable register *ESE? (GP-IB)
The summary of this register is set in bit 0 of the status byte.
For GP-IB, each bit is masked when the event status enable register 0 (which
starts off at zero when the power is turned on) is set.
The circumstances when the contents of event status register 0 are cleared are
as listed below.
1. When the *CLS command is received.
2. When the contents have been read by an :ESR0? query.
3. When the power is turned off and turned on again.
The bits of event status register 0
bit 7Waveform decision fail (NG).
bit 6Parameter decision fail (NG).
bit 5Parameter calculation finished.
bit 4Waveform processing calculation finished.
bit 3Printer operation finished (print, or copy output).
bit 2Trigger wait finished (set when the trigger event occurs).
bit 1Measurement operation concluded (set by STOP).
bit 0Error not related to the GP-IB interface; printer error etc
The following commands are used for reading the event status register 0, and
for setting the event status enable register 0 and for reading it.
Reading event status register 0 :ESR0?
Setting event status enable register 0 :ESE0 (GP-IB)
Reading event status enable register 0 :ESE0? (GP-IB)
This is the state in which the unit is controlled by its keys. When the power
is turned on, the unit always comes up in local state.
Remote state
In this state the unit is controlled from the GP-IB interface (the REN line is
"true"), and its keys are disabled. When in the remote state, the unit returns
to local state if the local key (the [LOCAL] function key) is pressed.
Local lockout state
When an LLO (Local Lockout) command (this is a GP-IB universal command)
is received, even if the local key is pressed, the unit is prevented from
returning to the local state. This state is called the local lockout state.
In order to return the unit from the local lockout state to the local state, it is
necessary either (a) to send a GTL (Go To Local) command (this is a GP-IB
universal command), or (b) to turn the power to the unit temporarily off and
then on again, or (c) to bring the line REN to "false".
If a command is sent with REN in the "false" state, then the only way to
return to the local state is with the local key.
REN "true", command sen
Local State
REN "false", GTL, local ke
REN "false", GTL
Local Lockout State
Program example HP-9816 (Hewlett-Packard)
local lockout LOCAL LOCKOUT 7
local LOCAL 7
Remote
LLO
(2) Device Clear
When the unit receives the device clear command, it clears the input buffer
and the output queue (see Section 2.6).
The device clear command is exemplified by the following:
HP 9816 (made by Hewlett-Packard)
CLEAR 7
The RS-232C interface can transfer data at the selected transfer rate, but if
the CPU cannot keep up with the data that are being sent, later data will
overwrite data that were received earlier. To prevent this, the receiving side
must alert the sending side when the reception buffer is about to become full,
so that the transfer can be temporarily paused. This is called flow control. Two
types of flow control are possible, namely hardware handshaking and software
handshaking.
(1) Hardware handshaking
Flow control is performed by setting the signal lines RTS (RS) and CTS (CS)
to ON and OFF.
Receiving data
When input buffer content exceeds 3/4, RTS is set to Low.
When input buffer content falls below 1/4, RTS is set to High.
Sending data
When CTS becomes Low, data send is interrupted.
When CTS becomes High, data send is resumed.
(2) Software handshaking
Flow control is performed using the Xon and Xoff code.
Receiving data
When input buffer content exceeds 3/4, D3 (13H) is sent.
When input buffer content falls below 1/4, D1 (11H) is sent.
Sending data
When D3 (13H) is received, data send is interrupted.
When D1 (11H) is received, data send is resumed.
*ESE AA: 0 to 255Sets SESER. (GP-IB only)
*ESE?A <NR1> 0 to 255Queries SESER
*ESR?A <NR1> 0 to 255Queries SESR.62Y YY
*SRE AA: 0 to 255Sets SRER. (GP-IB only)
*SRE?A <NR1> 0 to 63, 128 to 191Queries SRER.
*STB?A <NR1> 0 to 255Reads the STB and the MSS bit,
:ESE0 AA: 0 to 255Sets ESER0. (GP-IB only)
:ESE0?A <NR1> 0 to 255Queries ESER0.
:ESR0?A <NR1> 0 to 255Queries ESR0.64Y YY
(for a query, response data)
Data
Explanation
without performing serial polling.
Note 35: 8835 (-01), 26: 8826, 41: 8841, 42: 8842
20: 8720, Y: Yes, A: Advanced version
Ref
3526414220
page
62Y YY
63Y YY
63Y YY
64Y YY
.1.2Specific Commands
Execution control etc. (common to all functions)
Command
:STARtSame as the START key.65Y YY
:STOPSame as the STOP key.65Y YY
:ABORTForced halt.65Y YY
:PRINtSame as the PRINT key.65Y Y N
:HCOPySame as the COPY key.65Y Y N
:FEED AA: 1 to 255 (unit mm)Feeds the paper the specified distance.66Y Y N
:REPOrtSame as the FEED key + COPY key.66YY N
:AUTOSets the time axis and the voltage
:ERRor?A <NR1> error numberQueries 8835 error number.66Y Y Y
:HEADer A$A$: OFF, ONEnables and disables headers.
:HEADer?A$Queries headers.
:FUNCtion A$ A$: MEM, REC, RMS, R_M,
:FUNCtion?A$Queries the function.
(for a query, response data)
FFT
Data
Explanation
axis automatically. (Only the memory
recorder function)
CONFigure command (Setting and querying the time axis range, the recording length, etc.)
Command
:TDIV AA: TIME/DIV (unit seconds)
:TDIV?A <NR3> (unit seconds)Queries the time axis range.
:TDIV A, BA: TIME/DIV for REC,
:TDIV?A, B <NR3> (unit seconds)Queries the time axis ranges.
:SAMPle AA: sampling rate (unit
:SAMPle?A <NR3>Queries the sampling period.
(for a query, response data)
100 μs to 5 min/DIV
(MEM)
(0: external sampling
(except 8835))
10 ms to 1 h/DIV (REC)
(8835)
20 ms to 1 h/DIV (REC)
(8826, 8841, 8842)
5 s to 1 h/DIV (RMS)
B: TIME/DIV for MEM
seconds)
1 μs to 100 ms
Data
Explanation
Sets the time axis range.
Sets the time axis ranges.
Sets the sampling period.
Func
tion
MEM
REC
RMS
R&M68A Y N
REC69Y Y N
Ref
3526414220
page
68Y Y N
1
2
3
4
5
6
7
:SAMPle A$A: FAST, SLOWSets the sampling speed.
:SAMPle?A$Queries the sampling speed.
:FREQuency AA: 50, 60 (Hz)Sets the frequency.
:FREQuency?A <NR1>Queries the frequency.
:SHOT AA: recording length (unit
DIV)
1 to 20000: 8835 (MEM)
1 to 40000: 8835-01
1 to 160000: 8826, 8841,
8842
1 to CONT: (REC, RMS)
:SHOT?A <NR1> (unit DIV)Queries the recording length.YY N
:SHOT A, BA: REC recording length
B: MEM recording length
:SHOT?A, B <NR1> (unit DIV)Queries the recording lengths.
:RECTime AA: Recording time (unit s)
:FFTSAmple AA: 1000, 2000, 5000, 10000Sets the number of FFT points
:FFTSAmple?A <NR1>Queries the number of FFT
FFT90A Y N
points.
:RTSAve A$A$: ON, OFFSets the real time save
function.
R&M90N Y N
:RTSAve?A$Queries the real time save
function.
:CMPOld A$A$: ON, OFFSets comparison of separate
files.
All90N N Y
:CMPOld?A$Queries comparison of separat
files.
:OTSAve A$A$:FD,PC,MO,SCSI,LAN Sets one-touch save setting.
:OTSAve?A$Queries one-touch save setting
Note 35: 8835 (-01), 26: 8826,
MEM: memory recorder function REC: recorder function
RMS: RMS recorder function R&M: recorder and memory function
FFT: FFT function
All: all MEM, REC, RMS, R&M and FFT functions
TRIGger command (Setting and querying trigger.)
Command
(for a query, response data)
:MODE A$A$: SINGle, REPEat, AUTO
(MEM, FFT)
SINGle, REPEat (REC,
RMS)
SINGle, REPEat,
TIMEr (R&M)
Data
Explanation
Sets trigger mode.
All91N N Y
41: 8841, 42: 8842
20: 8720
Y: Yes
A: Advanced version
*: 8835-01 only
:KIND A$A$: POINT, RATIOSets the type of scaling.
:KIND?A$Queries the type of scaling.
:SET ch$, A$A$: OFF, SCI, ENGEnables and disables scaling.
:SET? ch$ch$, A$Queries scaling enablement.
:VOLT ch$, AA: -9.999E+9 to +9.999E+9Sets the scaling conversion
value (RATIO).
:VOLT? ch$ch$, A <NR3>Queries the scaling conversion
value.
:OFFSet ch$, A A: -9.999E+9 to +9.999E+9Sets scaling offset (RATIO).
:OFFSet? ch$ch$, A <NR3>Queries scaling offset.
:UNIT ch$, ’A$’A$: scaling unit (7
A: file size (bytes)
B$: function
C$: measurement contents
D: recording length
TDATE$: year/month/day o
trigger
TTIME$: trigger time
:DELEte NONO: file numberDeletes a file or directory.All164Y Y Y
:DELEte
’NAME1$.
NAME2$’
NAME1$:filename(upto8
characters)
NAME2$: file extension (up
Deletes a file or directory.
All164Y YY
to 3 characters)
:FORMat (A$)A$: 2DD, 2HD, 2HCFormats media.All164Y YY
:MKDIR ’A$’A$: directory nameCreates a directory.All164YY Y
:CHDIR NONO: file numberChanges the current directory.All165YY Y
:FILE?A <NR1>: number of filesQueries the number of files.All165YY Y
:NINFor? NONO,"NAME$", A$
NO: file number
NAME$: file name
Queries filename.
All165Y YY
A$: directory of a file
:DIR?A$: directory nameQueries the current directory.All165YY Y
:FREE?A$: allowable number of
When using the HIOKI MEMORY HiCORDER can be used with the HIOKI "9557
RS-232C CARD / 9558 GP-IB CARD" except following products, reffer to the
communication comands manual (Flopply disk) supplied with the MEMORY
HiCORDER.
■ The products consultable this manual: 8826, 8835, 8835-01, 8841, 8842
.2.1Explanation
The following sections describe the format and functions of individual
commands.
The following is an example of how the descriptions are organized.
Example
■ Changes and queries the function selection. Common
Syntax command :FUNCtion A$query :FUNCtion?response A$ = MEM : memory recorder functionREC : recorder functionRMS : RMS recorder function
Explanation Switches to the function designated by A$.Returns the name of the current function as character data
Example :FUNCtion:MEM
The function is set to the memory recorder function.
When allowed In MEM, REC and RMS
Command function
Command syntax
command gives the syntax of a command program message,
query the syntax of a query program message, and
response the format of the response message.
The parameters, referred to as data, are shown as follows:
A, B, C,... Numerical data (e.g. 1.5, 10E-3)
A$, B$,... Character data (e.g. A, B1, GND, OFF)
"A", "A$",... Character string data (e.g. "1.5", "mA")
(Single quotation marks (’) can be used instead of double quotation marks
(").)
The format of numerical data follows the formats <NR1>, <NR2>, and <NR3>.
Example
A <NR1> Numerical parameter in NR1 format
B <NR2> Numerical parameter in NR2 format
C <NR3> Numerical parameter in NR3 format
If no format is mentioned, <NR1> format is accepted.
NR1 format integer data
NR2 format fixed point numbers
NR3 format floating point numbers
The term "NRf format" includes all these three formats.
When the unit is receiving a command or query program message, it accepts
format, but when it is sending it utilizes whichever one of the formats <NR1>
to <NR3> is indicated in the particular command.
Response messages may or may not have headers prefixed.
Explanation of the command function.
Example of command use.
This lists the functions in which the command may be used.
MEM memory recorder function
REC recorder function
RMS RMS recorder function
Models
Common Common command that can be used for all the models
8835 Command that can be used for the 8835
8835-01 Command that can be used for the 8835-01
8826 Command that can be used for the 8826
8841 Command that can be used for the 8841
8842 Command that can be used for the 8842
8720 Command that can be used for the 8720
Execution of commands
・Commands are input into the input buffer and are executed in order.
・However the :ABORT command is executed immediately, even if commands
are waiting in the input buffer - more precisely, at the instant its terminator
is received.
・Commands other than those which can be handled by the unit in its current
state are not executed but generate execution errors. This happens, for
example, when in memory recorder function it is attempted to execute a
recorder mode setting.
・Further, almost all commands cannot be executed during measurement
operation.
8841 and 8842
Commands related to FFT, and recorder and memory functions are supported
from Version 2.00.
Regarding the command for specifying the channel number
Unless specifically mentioned, the ch$ character string specifying the channels
becomes as follows.
ch$ = CH1 to CH4 (8835)
CH1 to CH8 (8835-01)
CH1 to CH16 (8841, 8842, 8720)
CH1 to CH32 (8826)
■ Enables and disables headers, and queries header enablement.
Common
Syntax command :HEADer A$query :HEADer?
response A$
A$ = OFF, ON
Explanation Sets header enablement. When headers are enabled, responses to queries are
prefixed by headers; when headers are disabled, responses are not so prefixed.
Returns whether or not headers are prefixed to responses to queries. The
initial toggle state for headers (when the power is turned on) is OFF
Example Response to :HEADer?:
When headers are disabled: OFF
When headers are enabled: :HEADER ON
When allowed In all functions.
■ Changes and queries the function selection. Common
Syntax command :FUNCtion A$query :FUNCtion?
response A$
A$ = MEM: memory recorder functionREC: recorder functionRMS: RMS recorder functionR_M: recorder and memory function
FFT: FFT function
Explanation Switches to the function designated by A$.
Returns the name of the current function as character data.
Example :FUNCtion MEM
The function is set to the memory recorder function.When allowed In all functions.
■ Queries the communication errors. (RS-232C only) Common
Syntaxcommand :CERRor?
response A, B, C <NR1>
A: parity errorB: overrun errorC: framing error
Explanation The number of times of communication errors are returned in <NR1> as a
response A <NR3>, 0: External sampling (except 8835)
Explanation Sets the time axis range to a numerical value (unit seconds).Returns the currently set value of the time axis range as an NR3 numerical
value.
(If an attempt is made to set the time axis range to a non-permitted value,
and there is a range above that value, that range will be selected.)
Example :CONFigure:TDIV +500.0E‑6
Sets the time axis range to 500 μs.
When allowed In MEM, REC and RMS.
■ Sets and queries the time axis ranges (recorder and memory function).
8835 (-01) A, 8826, 8841, 8842
Syntax command :CONFigure:TDIV A, Bquery :CONFigure:TDIV?
response A, B <NR3>, 0: External sampling (except 8835)
A = time axis range for RECB = time axis range for MEM
Explanation Sets the time axis ranges, for both recorder and memory recorder modes, to
numerical values (unit seconds).
Returns the currently set values of the time axis ranges, for both REC and
MEM, as NR3 numerical values.
(If an attempt is made to set either of these time axis ranges to a nonpermitted value, and there is a range above that value, that range will be
selected.)
Example :CONFigure:TDIV +500.E‑3, +100.E‑6
Sets the time axis range for recorder mode to 500 ms, and the time axis range
for memoery recorder mode to 100 μs.
Explanation Sets the numerical value of the recording length (unit divisions).
Sets the recording length during memory segmentation.
Returns the currently set value of the recording length as an NR1 numerical
value.
0 indicates CONT.
Example :CONFigure:SHOT 15
Sets the recording length to 15 divisions.
When allowed In MEM, REC and RMS.
■ Sets and queries the recording length (recorder and memory function).
8835 (-01) A, 8826, 8841, 8842
Syntax command :CONFigure:SHOT A, Bquery :CONFigure:SHOT?
response A, B <NR1>
A = recording length for REC (0: continuous)B = recording length for MEM
Explanation Sets the numerical value of the recording lengths (unit divisions).Returns the currently set values of the recording lengths as NR1 numerical
values.
Example :CONFigure:SHOT 0,25
Sets the recording length for recorder mode to continuous, and the recording
length for memoery recorder mode to 25 divisions.
Explanation Sets the data recording time in units of seconds.
Recording length settings that exceed 10000 DIV cannot be set.
Sets to 0 for continuous recording.
Returns the currently set value of the recording time.
Example :CONFigure:RECTime 5025
Sets the recording time to 1 hour 23 minutes 45 seconds.
Sets the measuring time interval between single pieces of data.
Measured time is set to approximately 1 DIV for data recorded at a speed of
100x.
Returns the currently set value of the recording time.
A$ = OFF, FD, PC, LAN (8835)OFF, FD, PC, SCSI, MO, LAN (8826, 8841, 8842, 8720)OFF: Auto save is disabled. (B$ and C$ are omitted.)FD: Stores on floppy disk automaticallyPC: Stores on PC card automaticallySCSI: Stores on SCSI device automaticallyMO: Stores on MO disk automatically
LAN: Stores on PC connected to LAN.
B$ = store formatBin: binary dataText: text dataC$ = saved function (only in R&M)REC: Stores only the REC waveformMEM: Stores only the MEM waveformR_M: Stores both the REC and MEM waveforms
Explanation Sets the auto save function (output target).Omit B$ and C$ only when A$ = OFF.In the R&M function, sets the saved function as well.Returns the current setting of the auto save function as character data.
Example :CONFigure:ATSAve FD, Bin
Stores on floppy disk automatically as binary data.
:CONFigure:ATSAve PC, Text, RM
In the R&M function, stores on PC card automatically as text data (stores both
the REC and MEM waveforms).
When allowed In all functions.
■ Sets and queries the file name for auto save function.
8835-01,8826,8841,8842,872
Explanation Sets the degree of thinning that is applied when data is stored in text format
by the auto save function.
This setting can also be made when auto save is OFF or data is stored in
binary format, but the setting will not be reflected on the screen.
Returns the current setting of the degree of thinning as character data.
Example :CONFigure:THINout 12
Sets the degree of thinning to 1/2.
When allowed In all functions.
■ Sets and queries the waveform overlay function. Except 872
Syntax command :CONFigure:OVERlay A$query :CONFigure:OVERlay?response A$A$ = OFF, ON
Explanation Enables and disables screen waveform overlay.Returns the current enablement state of the waveform overlay as character
T_LIN: simple time axis averaging
T_EXP: exponential time axis averaging
F_LIN: simple frequency axis averaging
F_EXP: exponential frequency axis averaging
F_PEAK: frequency axis peak hold
Explanation Sets the averaging method designated by A$.Returns the currently set averaging method as character data.
■ Sets and queries the FFT channel mode.
8835 (-01) A, 8826, 8841, 8842
Syntax command :CONFigure:FFTMode A, ch1$ (,ch2$)
query :CONFigure:FFTMode?
response A <NR1>, ch1$, ch2$
A = 1: one-channel FFT mode
2: two-channel FFT mode
ch1$ = CH1 to CH32: analysis channel W1ch2$ = CH1 to CH32: analysis channel W2(8835: CH1 to CH4, 8841, 8842: CH1 to CH16)
Explanation Sets the FFT channel mode. I.e., designates the object channel or channels for
FFT channel mode and the number thereof. In the one-channel FFT mode
(only) the specification of channel 2 can be omitted, and if it is provided it is
ignored. Transfer function, coherence function, cross power spectrum, cross
correlation function and impulse response are only effective in the two-channel
FFT mode.
Returns the current FFT channel mode as a numerical value in NR1 format,
and the analysis channel as character data.
Example :CONFigure:FFTMode 2, CH3, CH5
The channel mode is set to the two-channel FFT mode, and the object
channels for FFT mode are set to be channel 3 and channel 5.
When allowedIn FFT.
■ Sets and queries the FFT window function.
8835 (-01) A, 8826, 8841, 8842
LIN: linear spectrum
RMS: RMS spectrum
PSP: power spectrum
ACR: auto-correlation function
HIS: histogram
TRF: transfer function (*)
CSP: cross power spectrum (*)
CCR: cross correlation function (*)
IMP: impulse response (*)
COH: coherence function (*)
OCT: octave analysis
(*) can only be used when the two-channel FFT mode is
set.
Explanation Sets the FFT analysis mode.
The FFT analysis mode can be set to transfer function, coherence function,
cross power spectrum, cross correlation function, or impulse response only in
the two-channel FFT mode (FFTMODE 2, ch1$, ch2$). In this case, the
corresponding function is calculated from channel 1 and channel 2. The result
of the calculation is displayed on the graph designated by A$. G2 can be
designated even if the display format is SINGLE, but this does not affect the
display.
Returns the current FFT analysis mode as character data.
Example :CONFigure:FORMat DUAL
The impulse response calculated from channel 1 and channel 3 is displayed on
G1, and the transfer function calculated from these channels is displayed on
G2.
Explanation Sets the display scaling method for the graph number designated by A$.Returns the current display scaling method for the graph number designated
by A$ as character data.
Example :CONFigure:FFTSCale G1,AUTO
The scaling method for graph number 1 is set to automatic.
Explanation Sets the x-axis of the graph number designated by A$. When the analysis
mode is octave analysis, 1_1oct or 1_3oct can be set; otherwise, LINhz or
LOGhz can be set. Some settings are not available for some analysis modes.
If a setting is not available, an execution error is generated (see the table on
the next page.)
Returns the current x-axis setting as character data.
Example :CONFigure:FFTXaxis G1, LINHZ
The setting for the x-axis of graph 1 is set to LINHZ.
When allowedIn FFT.
■ Sets and queries the FFT y-axis. 8835 (-01) A, 8826, 8841, 8842