FTB-2 и FTB-2 Pro. Руководство пользователя - часть 26

 

  Главная      Учебники - Разные     FTB-2 и FTB-2 Pro. Руководство пользователя

 

поиск по сайту            правообладателям  

 

 

 

 

 

 

 

 

содержание      ..     24      25      26      27     ..

 

 

FTB-2 и FTB-2 Pro. Руководство пользователя - часть 26

 

 

IEEE 488.2 and Specific Command Reference
IEEE 488.2 Required Commands
*IDN?
Description
The intent of the *IDN? query is for the unique
identification of devices over the system
interface.
Syntax
*IDN?
Parameter(s)
None
Response Syntax
<Identification>
Response(s)
Identification:
The response data syntax for <Identification> is
defined as an <ARBITRARY ASCII RESPONSE
DATA> element.
The response syntax for the *IDN? query,
<Identification> is defined as an <ARBITRARY
ASCII RESPONSE DATA> element. This implies
that the *IDN? query should be the last <QUERY
MESSAGE UNIT> in a <TERMINATED PROGRAM
MESSAGE>.
The response is organized into four fields
separated by commas. The field definitions are
as follows:
Field 1 (Manufacturer): EXFO Inc.
Field 2 (Model): Instrument Model
FTB-2 and FTB-2 Pro
391
IEEE 488.2 and Specific Command Reference
IEEE 488.2 Required Commands
*IDN?
Field 3 (Serial number): ASCII character (0 if not
available)
Field 4 (Firmware level): ASCII character (0 if
not available)
ASCII character 0 represents a single
ASCII-encoded byte with a value of 30 (48
decimal).
The presence of data in all fields is mandatory. If
either field 3 or 4 is not available, the ASCII
character 0 shall be returned for that field. A field
may contain any 7-bit ASCII-encoded bytes in the
range of 20 through 7E (32 through 126 decimal)
except commas (2C, 44 decimal) and
semicolons (3B, 59 decimal).
Example(s)
*IDN? returns EXFO Inc.,
FTB-2 Pro,125-2A55,1.0.1.97
Notes
The overall length of the *IDN? response is less
than or equal to 72 characters.
392
FTB-2 and FTB-2 Pro
IEEE 488.2 and Specific Command Reference
IEEE 488.2 Required Commands
*OPC
Description
The *OPC command makes synchronization
between the instrument and an external
controller possible. The *OPC command causes
the instrument to set bit 0 (Operation Complete)
in the Standard Event Status Register to the TRUE
(logic 1) state when the instrument completes all
pending operations. Detection of the Operation
Complete message can be accomplished by
continuous polling of the Standard Event Status
Register using the *ESR? common query
command. However, using a service request
eliminates the need to poll the Standard Event
Status Register thereby freeing the controller to
do other useful work.
Syntax
*OPC
Parameter(s)
None
See Also
*OPC?
*WAI
FTB-2 and FTB-2 Pro
393
IEEE 488.2 and Specific Command Reference
IEEE 488.2 Required Commands
*OPC?
Description
The *OPC? query makes possible the
synchronization between the instrument and an
external controller by reading the Output Queue
or by waiting for a service request on the
Message Available (MAV) bit in the Status Byte
Register. The *OPC? query causes the instrument
to place an ASCII character, 1, into its Output
Queue when the device completes all pending
operations. A consequence of this action is that
the MAV bit in the Status Byte Register is set to
state 1.
Syntax
*OPC?
Parameter(s)
None
Response Syntax
<Acknowledge>
Response(s)
Acknowledge:
The response data syntax for <Acknowledge> is
defined as a <NR1 NUMERIC RESPONSE DATA>
element.
The <Acknowledge> response is a single
ASCII-encoded byte corresponding to 1.
The receipt of an <Acknowledge> response
indicates that all pending selected device
operations have been completed.
Example(s)
*OPC? returns 1
See Also
*OPC
*WAI
394
FTB-2 and FTB-2 Pro
IEEE 488.2 and Specific Command Reference
IEEE 488.2 Required Commands
*RST
Description
The *RST command performs a device reset.
This command is the third reset level in a
three-level reset strategy. The Reset command
shall do the following:
a) Sets the device-specific functions to a known
state that is independent of the past-use history
of the device.
b) Forces the device into OCIS state (Operation
complete Command Idle State).
c) Forces the device into OQIS state (Operation
complete Query Idle State).
The Reset command explicitly DOES NOT affect
the following:
a) The state of the Communication interface.
b) The Output Queue.
c) Any Event Enable Register setting, including
the Standard Event Status Enable Register setting.
d) Any Event Register setting, including the
Standard Event Status Register settings.
e) Calibration data that affects device
specifications.
f) The Service Request Enable Register setting.
Syntax
*RST
Parameter(s)
None
FTB-2 and FTB-2 Pro
395
IEEE 488.2 and Specific Command Reference
IEEE 488.2 Required Commands
*SRE
Description
The *SRE command sets the Service Request
Enable Register bits. See the contents of this
register below. This register contains a mask
value to enable the bits in the Status Byte
Register.
Serv ice Request Enable
MSB
LSB
Register
N.U.
N.U.
ESB
MAV
N.U.
EAV
N.U.
N.U.
Syntax
*SRE<wsp><RegisterValue>
Parameter(s)
RegisterValue:
The program data syntax for <RegisterValue> is
defined as a <DECIMAL NUMERIC PROGRAM
DATA> element.
The <RegisterValue> value ranges from 0
through 255.
The <RegisterValue>, expressed in base 2
(binary), represents the bit values of the Service
Request Enable Register.
396
FTB-2 and FTB-2 Pro
IEEE 488.2 and Specific Command Reference
IEEE 488.2 Required Commands
*SRE
See the contents of this register below.
Bit
Weight
Meaning
N.U.
128
Not used
N.U.
64
Not used
ESB
32
Event Summary Bit Enable
MAV
16
Message AVailable Enable
N.U.
8
Not used
EAV
4
Error / Event AVailable Enable
N.U.
2
Not used
N.U.
1
Not used
A bit value of zero shall indicate a disabled
condition.
Example(s)
*SRE 52
where 52 = (bit ESB, bit MAV and bit EAV)
See Also
*SRE?
*STB?
FTB-2 and FTB-2 Pro
397
IEEE 488.2 and Specific Command Reference
IEEE 488.2 Required Commands
*SRE?
Description
With the *SRE? query you can determine the
current contents of the Service Request Enable
Register. See the contents of this register below.
Serv ice Request Enable
MSB
LSB
Register
N.U.
N.U.
ESB
MAV
N.U.
EAV
N.U.
N.U.
Bit
Weight
Meaning
N.U.
128
Not used
N.U.
64
Not used
ESB
32
Event Summary Bit Enable
MAV
16
Message AVailable Enable
N.U.
8
Not used
EAV
4
Error / Event AVailable Enable
N.U.
2
Not used
N.U.
1
Not used
Syntax
*SRE?
Parameter(s)
None
Response Syntax
<RegisterValue>
398
FTB-2 and FTB-2 Pro
IEEE 488.2 and Specific Command Reference
IEEE 488.2 Required Commands
*SRE?
Response(s)
RegisterValue:
The response data syntax for <RegisterValue> is
defined as a <NR1 NUMERIC RESPONSE DATA>
element.
The <RegisterValue> ranges from 0 through 255.
When converted to binary (base 2), the
<RegisterValue> represents the current bit
values of the Service Request Enable Register.
Example(s)
*SRE returns 32 (bit ESB)
See Also
*SRE
*STB?
FTB-2 and FTB-2 Pro
399
IEEE 488.2 and Specific Command Reference
IEEE 488.2 Required Commands
*STB?
Description
With the *STB? query you can read the status
byte and Master Summary Status bit. See the
content of this register below.
MSB
Status By te Register
LSB
RQS/
N.U.
ESB
MAV
N.U.
EAV
N.U.
N.U.
MSS
Syntax
*STB?
Parameter(s)
None
Response Syntax
<RegisterValue>
400
FTB-2 and FTB-2 Pro
IEEE 488.2 and Specific Command Reference
IEEE 488.2 Required Commands
*STB?
Response(s)
RegisterValue:
The response data syntax for <RegisterValue> is
defined as a <NR1 NUMERIC RESPONSE DATA>
element.
The <RegisterValue> ranges from 0 through 255.
The <RegisterValue> value, expressed in base 2
(binary) represents the bit values of the Status
Byte Register. See the contents of this register
below.
Bit
Weight
Meaning
N.U.
128
Not used
RQS/
64
ReQuest Service (read by serial
MSS
polling)/MaSter Summary bit
(read by *STB?)
ESB
32
Event Summary Bit Enable
MAV
16
Message AVailable Enable
N.U.
8
Not used
EAV
4
Error / Event AVailable Enable
N.U.
2
Not used
N.U.
1
Not used
Example(s)
*STB? returns 68
where 68 = (bit MSS and bit EAV)
See Also
*SRE
*SRE?
FTB-2 and FTB-2 Pro
401
IEEE 488.2 and Specific Command Reference
IEEE 488.2 Required Commands
*TST?
Description
The *TST? query causes an internal self-test and
places a response into the Output Queue
indicating whether or not the device completed
the self-test without any detected errors. Upon
successful completion of *TST?, the device
settings is restored to their values prior to the
*TST?.
Syntax
*TST?
Parameter(s)
None
Response Syntax
<Result>
Response(s)
Result:
The response data syntax for <Result> is
defined as a <NR1 NUMERIC RESPONSE DATA>
element.
The <Result> value ranges from -32767 through
+32767.
A <Result> with a value of zero indicates that
the self-test has been completed without errors
detected. A <Result> with a value not equal to
zero indicates that the self-test was not
completed or was completed with errors
detected.
Example(s)
*TST? returns 0
(self-test was completed with success)
402
FTB-2 and FTB-2 Pro
IEEE 488.2 and Specific Command Reference
IEEE 488.2 Required Commands
*WAI
Description
The *WAI command shall prevent the device
from executing any further commands or queries
until the no-operation-pending flag becomes
TRUE.
Syntax
*WAI
Parameter(s)
None
Example(s)
*WAI
See Also
*OPC
*OPC?
FTB-2 and FTB-2 Pro
403
IEEE 488.2 and Specific Command Reference
Specific Commands—Quick Reference
Specific Commands—Quick Reference
The table below contains a summary of the FTB-2 and FTB-2 Pro specific
commands. These commands are fully explained on the following pages.
Command
Parameter(s)
FORMat
[DATA]
ASCii|PACKed[,<Length>]
[DATA]?
INSTrument
CATalog?
CATalog
FULL?
SYSTem
DATE
<Year>,<Month>,<Day>
DATE?
ERRor
[NEXT]?
TIME
<Hour>,<Minute>,<Seconds>
TIME?
VERSion?
404
FTB-2 and FTB-2 Pro
IEEE 488.2 and Specific Command Reference
Specific Commands
Specific Commands
:FORMat[:DATA]
Description
The FORMat[:DATA] command selects the data
format and <Length>. The <Length>
parameter is optional for all data format, its
meaning is dependent on the data format
selected.
If PACKed type is selected, the data is transferred
in a <DEFINITE BLOCK RESPONSE DATA>. The
ASCii-type data is automatically identified by its
syntax. Therefore, in these cases, the FORMat
subsystem is only necessary to determine the
output format.
At *RST, ASCii is selected as the default data
format and the <Length> is set to 0.
Syntax
:FORMat[:DATA]<wsp>ASCii|PACKed[,<Lengt
h>]
Parameter(s)
Type:
The program data syntax for the first parameter is
defined as a <CHARACTER PROGRAM DATA>
element. The allowed <CHARACTER PROGRAM
DATA> elements for this parameter are:
ASCii|PACKed.
FTB-2 and FTB-2 Pro
405
IEEE 488.2 and Specific Command Reference
Specific Commands
:FORMat[:DATA]
In ASCii format, the numeric data is transferred
to ASCii bytes in <NR1 NUMERIC RESPONSE
DATA>, <NR2 NUMERIC RESPONSE DATA> or
<NR3 NUMERIC RESPONSE DATA>
representation, as appropriate.
In PACKed format, data is transferred to a
<DEFINITE BLOCK RESPONSE DATA>, in a
manner specified in the device documentation.
Length:
The program data syntax for <Length> is
defined as a <DECIMAL NUMERIC PROGRAM
DATA> element.
When ASCii data format is selected, the optional
<Length> parameter specifies the number of
significant digits to be returned. A <Length>
value of zero indicates that the device selects the
number of significant digits to be returned. When
a <Length> of zero has been specified, the
FORMat[:DATA]? query returns zero as its second
parameter.
When the PACKed data format is selected, the
optional parameter <Length> it not used.
Example(s)
FORM ASC
FORM ASC,6
FORM:DATA PACKED
See Also
FORMat[:DATA]?
406
FTB-2 and FTB-2 Pro

 

 

 

 

 

 

 

содержание      ..     24      25      26      27     ..