YOKOGAWA AQ7277 User manual
User’s
Manual AQ7277 Remote OTDR
Communication Interface
IM AQ7277-17EN
2nd Edition
i
IM AQ7277-17EN
Foreward Thank you for purchasing YOKOGAWA’s AQ7277.
This Communication Interface User’s Manual describes the functions and commands
of USB and Ethernet interface. To ensure proper use of the USB/Ethernet interfaces,
please read this manual thoroughly.Keep the manual in a safe place for quick reference
whenever a question arises.
Notes
• Thecontentsofthismanualaresubjecttochangewithoutpriornoticeasaresultof
improvements in instrument’s performance and functions.
• Everyefforthasbeenmadeinthepreparationofthismanualtoensuretheaccuracy
of its contents. However, should you have any questions or find any errors, please
contact your nearest YOKOGAWArepresentative.
• Copyingorreproductionofalloranypartofthecontentsofthismanualwithout
YOKOGAWA’s permission is strictly prohibited.
Trademarks
• Microsoft,InternetExplorer,Windows,andWindowsVistaareeitherregistered
trademarks or trademarks of Microsoft Corporation in the United States and/or other
countries.
• Adobe,Acrobat,andPostScriptareeithertrademarksorregisteredtrademarksof
Adobe Systems incorporated.
• Forpurposesofthismanual,the®andTMsymbolsdonotaccompanytheir
respective registered trademark names or trademark names.
• Otherproductnamesareregisteredtrademarksortrademarksoftheirrespective
holders.
Revisions 1st Edition: March 2011
2nd Edition: October 2017
2nd Edition :October 2017 (YMI)
All Rights Reserved, Copyright © 2011, Yokogawa Test & Measurement Corporation
ii IM AQ7277-17EN
How to Use this Manual
Structure of the Manual
This User’s Manual consists of the following sections:
Chapter 1 Remote Control Function Overview
Gives an overview of the various communication interfaces.
Chapter 2 Connecting the PC
Describes the functions and specifications of the USB interface and the
EthernetInterfaceusedtocontroltheAQ7277fromaPC.
Chapter 3 Before Programming
Describesthesyntaxusedtotransmitcommands.
Chapter 4 Remote Commands
Describes each command that is available.
iii
IM AQ7277-17EN
Conventions Used in This Manual
Notations Used in the Procedural Explanations
On pages that describe the operating procedures in each chapter, the following notations
areusedtodistinguishtheprocedurefromtheirexplanations.
Procedure This subsection contains the operating procedure used to carry out
the function described in the current section. The procedures are
writtenwithinexperiencedusersinmind;experiencedusersmaynot
need to carry out all the steps.
Explanation This subsection describes the setup parameters and the limitations
on the procedures.
Note
Calls attention to information that is important for proper operation of
the instrument.
Units
Symbol Description Example
k 1000 400km
K 1024 459KB (file size)
iv IM AQ7277-17EN
Symbols Used in Syntax Descriptions
SymbolswhichareusedinthesyntaxdescriptionsinChapter4areshownbelow.
ThesesymbolsarereferredtoasBNFnotation(Backus-NaurForm).
Fordetailedinformation,seesection3.4,“Data.”
Symbol Description Example Example of Input
<>
Defined value SET:M<x> <x> = 1,2,3 -> SET:M2
{} One of the options LMTechnique {LSA|TPA} -> LMTechnique TPA
in {} is selected.
| ExclusiveOR
Conventions Used in This Manual
v
IM AQ7277-17EN
1
2
3
4
5
App
Index
Index
How to Use this Manual....................................................................................................................ii
Conventions Used in This Manual...................................................................................................iii
Chapter 1 Remote Control Function Overview
1.1 Remote Interface.............................................................................................................. 1-1
1.2 Switching between Remote and Local Modes ................................................................. 1-2
Chapter 2 Connecting the PC
2.1 Connecting via the USB................................................................................................... 2-1
2.2 Connecting via the Ethernet Interface.............................................................................. 2-2
Chapter 3 Before Programming
3.1 Messages ......................................................................................................................... 3-1
3.2 Commands ....................................................................................................................... 3-3
3.3 Response ......................................................................................................................... 3-6
3.4 Data.................................................................................................................................. 3-7
3.5 SynchronizationwiththeController.................................................................................3-11
Chapter 4 Commands
4.1 A List of Commands......................................................................................................... 4-1
4.2 Common Commands ....................................................................................................... 4-4
4.3 Device-SpecicCommands ............................................................................................. 4-6
ACQuire Group......................................................................................................... 4-6
ANALysis Group....................................................................................................... 4-9
COMMunicate Group.............................................................................................. 4-13
DISPlayGroup........................................................................................................ 4-14
FILEGroup............................................................................................................. 4-16
MENU Group.......................................................................................................... 4-16
MISC Group............................................................................................................ 4-17
NETWork Group..................................................................................................... 4-18
SETup Group.......................................................................................................... 4-19
STATus Group........................................................................................................ 4-19
WAVedataGroup .................................................................................................... 4-20
SYSTem Group....................................................................................................... 4-21
4.4 Condition Register.......................................................................................................... 4-22
4.5 Output Queue and Error Queue..................................................................................... 4-23
4.6 ErrorMessages .............................................................................................................. 4-24
1-1
IM AQ7277-17EN
Remote Control Function Overview
1
2
3
4
5
App
Index
1.1 Remote Interface
The AQ7277 is equipped with the following remote interfaces.
USB 1.1 Interface (Type B. See Chapter 2)
ThisinterfaceisusedbyacontrollersuchasaPCtoremotelycontroltheAQ7277.
A controller is connected to this interface.
Remote commands are used to control the AQ7277.
DedicatedcommandsfortheAQ7277complyingwithSCPI(StandardCommandsfor
ProgrammableInstruments)areavailablefortheremotecommands(seechapter4).
Ethernet Interface (See Chapter 2)
ThisinterfaceisusedbyacontrollersuchasaPCtoremotelycontroltheAQ7277via
the network.
Downloading the Library and Driver
TheitemsbelowareneededonthePCtousethecommunicationfunctionsviatheUSB
interface.
• CommunicationLibrary(TMCTL)
• USBconnectiondevicedriverbetweenthePCandAQ7277(YKUSB)
TheitemsbelowareneededonthePCtousethecommunicationfunctionsviathe
Ethernet interface.
• CommunicationLibrary(TMCTL)
The library and driver above can be downloaded from the following Web page.
http://www.yokogawa.com/tm/dl_driver.htm
Chapter 1 Remote Control Function Overview
1-2 IM AQ7277-17EN
1.2 Switching between Remote and Local Modes
When Switching from Local to Remote Mode
The AQ7277 is in local mode when it is being controlled with the remote controller for the
AQ7277 Remote OTDR. It is in remote mode when it is being controlled through the use
of communication commands.
In remote mode, the soft keys on the remote controller for the AQ7277 Remote OTDR
are disabled.
• Allkeysexceptthe"Local"keyaredisabled.
• SettingsenteredinlocalmodearepassedonevenwhentheAQ7277switchesto
remote mode.
When Switching from Remote to Local Mode
In remote mode, if you press Local on the remote controller for the AQ7277 Remote
OTDR, the AQ7277 switches to local mode.
• YouwillbeabletousetheremotecontrollerfortheAQ7277RemoteOTDR.
• SettingsenteredinremotemodeareretainedevenwhentheAQ7277switchesto
local mode.
2-1
IM AQ7277-17EN
Connecting the PC
1
2
3
4
5
App
Index
2.1 Connecting via the USB
YoucancontroltheAQ7277fromaPCusingtheUSBinterface.
USB Interface Functions and Specifications
Reception Function
You can specify the same settings as those specified by front panel key operations.
Receives output requests for measured and computed data, setup data, and error codes.
Transmission Function
Outputs measured and computed data.
Outputs setup data and the status byte.
Outputs error codes that have occurred.
USB Interface Specifications
Electrical and mechanical specifications: Conforms to USB Rev.1.0
Connector: Type B connector (receptacle)
Number of ports: 1
Powersupply: Self-powered
CompatiblePCsystems: PCswithstandardUSBportsrunning
WindowsXP,WindowsVista,orWindows7.
(A separate device driver is required to
connecttoaPC.)
Connection Procedure
Connecting a USB Cable to Remotely Control the AQ7277
Connect a USB cable to the Type B connector.
PrecautionstoBeTakenWhenConnectingtheCable
• ConnecttheUSBcablebyinsertingtheconnectorfirmlyintotheUSBconnector.
• DonotconnectordisconnecttheUSBcableafterthepoweristurnedONuntilthe
AQ7277isreadyforoperation(approximately20s).
Chapter 2 Connecting the PC
2-2 IM AQ7277-17EN
2.2 Connecting via the Ethernet Interface
YoucancontroltheAQ7277fromaPCbyconnectingtheAQ7277toaLANusingthe
Ethernet interface.
Ethernet Interface Functions and Specifications
Reception Function
You can specify the same settings as those specified by AQ7277 Remote Controller.
Receives output requests for measured and computed data, setup data, and error codes.
Transmission Function
Outputs measured and computed data.
Outputs setup data and the status byte.
Outputs error codes that have occurred.
Ethernet Interface Specifications
Number of communication ports: 1
Electricalandmechanicalspecifications: ConformstoIEEE802.3
Transmission system: Ethernet (10BASE-T/100BASE-TX)
Data rate: 10 Mbps/100 Mbps
Communicationprotocol: TCP/IP
Connector type: RJ45 connector
Portnumberused: 10001/tcp
Note
When using the Ethernet interface, a user name and password are required when connecting
tothenetwork.Fortheproceduretoentertheusernameandpassword,seetheUser,s Manual
of AQ7277 Remote Controller
2-3
IM AQ7277-17EN
Connecting the PC
1
2
3
4
5
App
Index
Connection Procedure
ConnectaUTP(UnshieldedTwisted-Pair)cableoranSTP(ShieldedTwisted-Pair)cable
thatisconnectedtoahub,forexample,tothe100BASE-TXport.
Precautions to Be Taken When Connecting the Cable
• BesuretouseastraightcableviaahubfortheconnectionbetweentheAQ7277and
thePC.
• WhenusingaUTPcable(straightcable),useacableofcategory5.
Note
SettheTCP/IPaddressusingtheremotecontrollerfortheAQ7277RemoteOTDR.Forthe
procedure, see the user's manual for the remote controller for the AQ7277 Remote OTDR.
2.2 Connecting via the Ethernet Interface
3-1
IM AQ7277-17EN
Before Programming
1
2
3
4
5
App
Index
3.1 Messages
Blocks of message data are transferred between the controller and this instrument during
communications.Messages sent from the controller to this instrument are called program
messages, and messages sent back from this instrument to the controller are called
response messages.
If a program message contains a query command, i.e.a command which requests a
response, this instrument returns a response message. A single response message is
always returned in reply to a program message.
Program Messages
Program Message Unit
Aprogrammessageconsistsofoneormoreprogrammessageunits;eachunit
correspondstoonecommand.Thisinstrumentexecutescommandsonebyone
according to the order in which they are received.
Programmessageunitsaredelimitedbya";.
"Foradescriptionoftheformatoftheprogrammessageunit,refertotheexplanation
given furtherbelow.
:ACQuire:AVERage:MODE HIREFLECTION;TIME AUTO<PMT>
Unit Unit
Example
<PMT>
PMTisaterminatorusedtoterminateeachprogrammessage.Thefollowingthreetypes
of terminator are available.
• NL(NewLine)
SameasLF(LineFeed).ASCIIcode"0AH"isused.
• ^END
END message defined in IEEE488.1. (EOI signal)
(The data byte sent with an END message will be the final item of the program
message unit.)
• NL^END
NL with an END message attached(NL is not included in the program message unit.)
<Program Header>
Aprogramheaderisusedtoindicatethecommandtype.Fordetails,refertopage3-3.
<Program Data>
Ifcertainconditionsarerequiredfortheexecutionofacommand,programdatamust
beadded.Programdatamustbeseparatedfromtheheaderbyaspace(ASCIIcode
"20H").Ifmultipleitemsofprogramdataareincluded,theymustbeseparatedbya","
(comma).Fordetails,refertopage3-5.
:ACQuire:AVERage:MODE HIREFLECTION<PMT>
Header Data
Example
Chapter 3 Before Programming
3-2 IM AQ7277-17EN
Response Messages
<Response Message Units>
A response message consists of one or more response message units: each response
messageunitcorrespondstooneresponse.Responsemessageunitsaredelimitedbya";"
(semicolon).
:ACQuire:AVERage:MODE HIREFLECTION;TIME AUTO<PMT>
Unit Unit
Example
<RMT>
RMT is the terminator used for every responsemessage. Only one type of response
messageisavailable;NL^END.
<Response Header>
A response header sometimes precedes the response data. Response data must be
separatedfromtheheaderbyaspace.Fordetails,refertopage3-5.
<Response Data>
Response data is used to define a response. If multiple items of response data are used,
theymustbeseparatedbya","(comma).Fordetails,refertopage3-5.
:ACQuire:AVERage:MODE HIREFLECTION<PMT>
Header Data
Example 1200<RMT>
Data
If a program message contains more than one query, responses are made in the same
order as the queries. Normally, each query returns only one response message unit,
but there are some queries which return more than one response message unit. The
first response message unit always responds to the first query, but it is not always true
that the 'n'th unit always responds to the 'n'th query. Therefore, if you want to make sure
that a response is made to eachquery, the program message must be divided up into
individual messages.
Points to Note Concerning Message Transmission
• Itisalwayspossibletosendaprogrammessageifthepreviousmessagewhichwas
sent did not contain any queries.
• Ifthepreviousmessagecontainedaquery,itisnotpossibletosendanother
program message until a response message has been received. An error will occur
if a program message is sent before a response message has been received in its
entirety. A response message which has not been receivedwill be discarded.
• Ifanattemptismadebythecontrollertoreceivearesponsemessage,evenifthere
it no response message, an error will occur. An error will also occur if the controller
makes an attempt to receive a response message before transmission of a program
message has been completed.
• Ifaprogrammessageofmorethanoneunitissentandsomeoftheunitsare
incomplete, this instrument receives program message units which the instrument
thinkscompleteandattemptstoexecutethem.However,theseattemptsmay
not always be successful and a response may not always be returned, even if the
program message contains queries.
3.1 Messages
3-3
IM AQ7277-17EN
Before Programming
1
2
3
4
5
App
Index
3.2 Commands
There are two types of command (program header)which can be sent from the controller
to this instrument. They differ in the format of their program headers.
Common command header
Common Command Header Commands defined in IEEE 488.2-1987 are called common
commands.
An asterisk (*) must always be attached to the beginning of a command.
Anexampleofacommoncommand
*CLS
Compound headerCompound Header Commands designed to be used only with this instrument are
classified and arranged in a hierarchy according to their function. The format of a
compound header is below. Acolon (:) must be used when specifying a lower-level
header.
Anexampleofacompoundheader
: ACQuire: AVERage: MODE
3-4 IM AQ7277-17EN
When Concatenating Commands
Command Group
A command group is a group of commands which havethe same compound header.
A command group maycontain sub-groups.
ExampleCommandsrelatingtoacquisitionsettings
:ACQuire:AVERage:MODE
:ACQuire:ATTenuation
:ACQuire:AVERage:TYPE
:ACQuire:DRANge
:ACQuire:PWIDth
:ACQuire:REALtime:STARt
:ACQuire:SETTing
When Concatenating Commands of the SameGroup
This instrument stores the hierarchical level of the command which is currently being
executed,andperformsanalysisontheassumptionthatthenextcommandtobesentwill
also belong to the same level.Therefore, it is possible to omit the header if thecommands
belong to the same group.
Example
:ACQuire:AVERage:MODE HIREFLECTION;TIME AUTO<PMT>
When Concatenating Commands of DifferentGroups
A colon (:) must be included before the header of a command, if the command does not
belong to the same group as the preceding command. It is impossible to omit a colon (:).
Example
:ACQuire:AVERage:MODE HIREFLECTION;:DISPlay:CURSor
:SECond ON<PMT>
When Concatenating Common Commands
Common commands defined in IEEE 488.2-1987 are independent of hierarchical level.
Thus, it is not necessary to add a colon (:) before a commoncommand.
Example
:ACQuire:AVERage:MODE HIREFLECTION;*CLS;TIME AUTO<PMT>
When Separating Commands with <PMT>
If a terminator is used to separate two commands,each command is a separate
message. Therefore, thecommon header must be typed in for each commandeven when
commands of the same command groupare being concatenated.
Example
:ACQuire:AVERage:MODE HIREFLECTION<PMT>:ACQuire:AVERage
:TIME AUTO<PMT>
3.2 Commands
3-5
IM AQ7277-17EN
Before Programming
1
2
3
4
5
App
Index
Upper-level QueryAn upper-level query is a compound header to which aquestion mark is appended.
Executionofanupper-levelqueryallowsallagroup’ssettingstobeoutputatonce.
Some query groups comprising more than threehierarchical levels can output all their
lower level settings.
Example
:ANALysis:THReshold?<PMT>
->:ANAL:THR:EOF 3.0;FERL 40.0;FESL 1.00;RLOS 70.0
;SLOS 0.03
Note
• Inreplytoaquery,aresponsecanbereturnedasaprogrammessagetothisinstrument.
Transmittingaresponsecanrestorethesettingsmadewhenthequerywasexecuted.
• Notallagroup’sinformationwillnecessarilybesentoutasaresponse.Some upper-
levelqueries will not return setup data which is not currently in use.
Header Interpretation Rules
This instrument interprets the header receivedaccording to the following rules.
• Mnemonicsarenotcasesensitive.
Example
"DRANge"canalsobewrittenas"drange"or"Drange."
• Thelowercasepartofaheadercanbeomitted.
Example
"DRANge"canalsobewrittenas"DRANG"or"DRAN."
• Iftheheaderendswithaquestionmark,thecommandisaquery.Itisnotpossibleto
omit the question mark.
Example
"DRANge?"cannotbeabbreviatedtoanythingshorterthan"DRAN?."
• Ifthe"x"attheendofamnemonicisomitted,itisassumedtobe"1."
ExampleIf"M<x>"iswrittenas"M,"thisrepresents"M1."
Note
A mnemonic is a character string made up of alphanumeric characters.)
3.2 Commands
3-6 IM AQ7277-17EN
3.3 Response
Form On receiving a query from the controller, this instrument returns a response message to
the controller. Aresponse message is sent in one of the following two forms.
Response Consisting of a Header and Data
If the query can be used as a program messagewithout any change, a command header
is attachedto the query, which is then returned.
Example:ACQUire:MODE?<PMT>->:ACQUire:MODENORMAL<RMT>
Response Consisting of Data Only
If the query cannot be used as a program messageunless changes are made to it (i.e.
it is a query-onlycommand), no header is attached and only the datais returned. Some
query-only commands can bereturned after a header is attached to them.
Example:MEASure:CHANnel1:PTOPeak:VALue?<PMT>->10.0E+00<RMT>
When Returning a Response without a Header
It is possible to remove the header from a responseconsisting of a header and data.
The"COMMunicate:HEADer"commandisusedtodothis.
Abbreviated FormNormally, the lowercase part is removed from are sponse header before the response
isreturnedtothecontroller.Naturally,thefullformoftheheadercanalsobeused.For
this, the
"COMMunicate:VERBose"commandisused.Thepartenclosedby[]isalsoomittedin
the abbreviatedform.
3-7
IM AQ7277-17EN
Before Programming
1
2
3
4
5
App
Index
3.4 Data
A data section comes after the header. Aspace must be included between the header
and the data. The data contains conditions and values. Data is classified as below.
Data Description
<Decimal> Valueexpressedasadecimalnumber
(Example:Averagetime -> ACQuire:AVERage:TIME 60)
<Distance><Time> Physicalvalue
<Wavelength><Loss> (Example:Distancerange-> ACQuire:DRANge 500)
<Register> Registervalueexpressedaseitherbinary,octal,decimalorhexadecimal
(Example:Extendedeventregistervalue-> STATus:EESE #HFE)
<Characterdata> Specifiedcharacterstring(mnemonic).Canbeselectedfrom{}
(Example:Setupmode
-> ACQuire:SETTing{SIMPLE|DETAIL|WIZARD|MULTI})
<Boolean> IndicatesON/OFF.SettoONorOFF
(Example:Faulteventdisplay -> ANALysis:FEDetection ON)
<Characterstringdata> Arbitrarycharacterstring
(Example:Commenttobesaved
-> FILE:SAVe:COMMent "ABCDEF")
<Filename> Givesthenameofafile.
(Example:Nameoffiletobesaved
-> FILE:SAVE:WAVeform:NAME "CASE1")
<Blockdata> Arbitrary8-bitdata
(Example:Responsetoacquiredwaveformdata
-> #800000010ABCDEFGHIJ)
<Decimal>
<Decimal>indicatesavalueexpressedasadecimalnumber,asshowninthetable
below.DecimalvaluesaregivenintheNRformspecifiedinANSIX3.42-1975.
Symbol Description Example
<NR1> Integer 125 –1+1000
<NR2> Fixedpointnumber 125.0–.90+001.
<NR3> Floatingpointnumber 125.0E+0–9E–1+.1E4
<NRf> Anyoftheforms<NR1>to<NR3>isallowed.
• Decimalvalueswhicharesentfromthecontrollertothisinstrumentcanbesentinany
oftheformsto<NR3>.Inthiscase,<NRf>appears.
• Forresponsemessageswhicharereturnedfromthisinstrumenttothecontroller,
theform(<NR1>to<NR3>tobeused)isdeterminedbythequery.Thesameformis
used, irrespective of whether the valueis large or small.
• Inthecaseof<NR3>,the"+"afterthe"E"canbeomitted,butthe"–"cannot.
• Ifavalueoutsidethesettingrangeisentered,thevaluewillbenormalizedsothatitis
justinsidetherange.
• Ifthevaluehasmorethanthesignificantnumberofdigits,thevaluewillberounded.
3-8 IM AQ7277-17EN
<Distance>, <Time>, <Wavelength>, and <Loss>
<Distance>,<Time>,<Wavelength>,and<Loss>indicatedecimalvalueswhichhave
physicalsignificance.<Multiplier>or<Unit>canbeattachedto<NRf>.Theycanbe
entered in any of the following forms.
Form Example
<NRf><Multiplier><Unit> 0.85UM
<NRf><Unit> 500m
<NRf><Multiplier> 5M
<NRf> 5E-3
<Multiplier>
Multipliers which can be used are shown below.
Symbol Word Description
EX Exa 1018
PE Peta 1015
T Tera 1012
G Giga 109
MA Mega 106
K Kilo 103
M Milli 10–3
U Micro 10–6
N Nano 10–9
P Pico 10–12
F Femto 10–15
A Atto 10–18
<Unit>
Units which can be used are shown below.
Symbol Word Description
M Meter Distance
S Second Time
dB Decibel Level
UM Micro meter Wavelength
• <Multiplier>and<Unit>arenotcasesensitive.
• "U"isusedtoindicate"µ."
• "MA"isusedforMega(M)todistinguishitfromMilli.
• Ifboth<Multiplier>and<Unit>areomitted,thedefaultunitwillbeused.
3.4 Data
3-9
IM AQ7277-17EN
Before Programming
1
2
3
4
5
App
Index
<Register>
<Register>indicatesaninteger,andcanbeexpressedinhexadecimal,octal,orbinary
aswellasadecimalnumber.<Register>isusedwheneachbitofavaluehasa
particularmeaning.<Register>isexpressedinoneofthefollowingforms.
Form Example
<NRf> 1
#H<Hexadecimalvaluemadeupofthedigits0to9,andAtoF> #H0F
#Q<Octalvaluemadeupofthedigits0to7> #Q777
#B<Binaryvaluemadeupofthedigits0and1> #B001100
• <Register>isnotcasesensitive.
• Responsemessagesarealwaysexpressedas<NR1>.
<Character Data>
<Characterdata>isaspecifiedstringofcharacterdata(amnemonic).Itismainlyused
to indicate options,and is chosen from the character strings given in { }.
Forinterpretationrules,referto“HeaderInterpretationRules”onpage3-5.
Form Example
{SIMPLE|DETAIL|WIZARD|MULTI} DETAIL
• Aswithaheader,the"COMMunicate:VERBose"commandcanbeusedtoreturna
response message in its full form. Alternatively, the abbreviated form can be used.
• The"COMMunicate:HEADer"commanddoesnotaffect<characterdata>.
<Boolean>
<Boolean>isdatawhichindicatesONorOFF,andisexpressedinoneofthefollowing
forms.
Form Example
{ON|OFF|<NRf>} ON OFF 1 0
• When<Boolean>isexpressedin<NRf>form,OFFisselectediftheroundedinteger
valueis"0"andONisselectediftheroundedintegeris"Not0."
• Aresponsemessageisalways"1"ifthevalueisONand"0"ifitisOFF.
3.4 Data
Other manuals for AQ7277
3
This manual suits for next models
1
Table of contents
Other YOKOGAWA Recording Equipment manuals
YOKOGAWA
YOKOGAWA Daqstation DX1000 User manual
YOKOGAWA
YOKOGAWA ScopeCorder DL350 User manual
YOKOGAWA
YOKOGAWA IB100 User manual
YOKOGAWA
YOKOGAWA DXAdvancedR4 DX1000 User manual
YOKOGAWA
YOKOGAWA PR300 User manual
YOKOGAWA
YOKOGAWA SMARTDAC+ GX20 User manual
YOKOGAWA
YOKOGAWA Daqstation DX1000N User manual
YOKOGAWA
YOKOGAWA UTAdvanced Series User manual
YOKOGAWA
YOKOGAWA Daqstation DX2000 User manual
YOKOGAWA
YOKOGAWA DX2004T User manual
