Yokogawa DL6154, DLM6104, DL6104, DL6054, DLM6054 User Manual

IM DLM6054-17EN
1st Edition
Digital Oscilloscope/ Mixed Signal Oscilloscope
DL6000/DLM6000 Series
Communication Interface
i
Thank you for purchasing the DL6000/DLM6000 Series Digital Oscilloscope/Mixed Signal Oscilloscope (DL6054/DL6104/DL6154/DLM6054/DLM6104, hereafter referred to as the DL6000/DLM6000). This Communication Interface User’s Manual describes the functions and commands of the following communication interfaces.
USB Interface
• Ethernet Interface (Optional)
• GB-IB Interface To ensure correct use, please read this manual thoroughly before beginning operation. After reading the manual, keep it in a convenient location for quick reference whenever a question arises during operation. The following manuals are provided for the DL6000/DLM6000. Please read all of them.
Manual Title Manual No. Description
DL6000/DLM6000 Series Digital Oscilloscope/ Mixed Signal Oscilloscope User’s Manual
IM DLM6054-01EN Explains all functions and procedures of the DL6000/
DLM6000 series excluding the communication functions.
DL6000/DLM6000 Series Digital Oscilloscope/ Mixed Signal Oscilloscope Communication Interface User’s Manual (in CD)
IM DLM6054-17EN This manual. Explains the communication interface
functions of the DL6000/DLM6000 series.
DL6000/DLM6000 Series Digital Oscilloscope/ Mixed Signal Oscilloscope Serial Bus Signal Triggering and Analysis Function User’s Manual
IM DLM6054-51EN Explains the optional I2C bus signal, CAN bus
signal, LIN bus signal, SPI bus signal, and UART bus signal triggering and analysis features and how to use them.
DL6000/DLM6000 Series Digital Oscilloscope/ Mixed Signal Oscilloscope Power Supply Analysis Function User’s Manual
IM DLM6054-61EN Explains the optional power supply analysis features
and how to use them.
Notes
• You can check the firmware version of your DL6000/DLM6000 on the overview screen. For instructions on how to open the overview screen, see section 18.4 in the User’s Manual IM 701331-01E.
To upgrade to the latest firmware version, go to the following Web page, and then browse to the
download page. http://tmi.yokogawa.com/service-support/downloads/
The contents of this manual are subject to change without prior notice as a result of continuing
improvements to the instrument’s performance and functions.
Every effort has been made in the preparation of this manual to ensure the accuracy of its
contents. However, should you have any questions or find any errors, please contact your nearest YOKOGAWA dealer.
Copying or reproducing all or any part of the contents of this manual without the permission of
Yokogawa Electric Corporation is strictly prohibited.
1st Edition: October 2009 (YK) All Rights Reserved, Copyright © 2009 Yokogawa Electric Corporation
ii
USB Interface and Ethernet Interface
• The items below are needed on the PC to use the communication functions via the USB interface.
• DL Series Library (TMCTL)
• USB device driver for connecting the PC and the DL9000 series
• The items below are needed on the PC to use the communication functions via the Ethernet interface.
DL Series Library (TMCTL)
To download the libraries and drivers listed above, go to the following Web page, and then browse
to the download page. http://tmi.yokogawa.com/service-support/downloads/
Sample Programs
To download sample programs, go to the following Web page, and then browse to the download page. http://tmi.yokogawa.com/service-support/downloads/
Trademarks
• DLM is pending trademark of Yokogawa Electric Corporation.
• Microsoft, MS-DOS, Visual C++, Windows, and Windows NT are registered trademarks of Microsoft Corporation in the United States and/or other countries.
Adobe and Acrobat are trademarks of Adobe Systems Incorporated.
• For purposes of this manual, the TM and ® symbols do not accompany their respective trademark names or registered trademark names.
Other company and product names are trademarks or registered trademarks of their respective
holders.
Revisions
1st Edition: October 2009
iii

How to Use This Manual

Structure of This Manual
This user’s manual consists of the following sections.
Chapter 1 Overview of the USB Interface
Describes the functions and specifications of the USB interface.
Chapter 2 Overview of the Ethernet Interface (Optional)
Describes the functions and specifications of the Ethernet interface.
Chapter 3 Overview of the GP-IB Interface
Describes the functions and specifications of the GP-IB interface.
Chapter 4 Before Programming
Describes the syntax used to transmit commands.
Chapter 5 Command
Describes all the commands one by one.
Chapter 6 Status Reports
Describes the status byte, various registers, and queues.
Appendix
Describes reference material such as an ASCII character code table.
iv
Symbols and Notations Used in This Manual
Communication Command Notation
In the detailed explanations of the communication commands in chapter 5, DLM6000-specific commands are written in blue italics. These commands are not available on the DL6000.
Safety Markings
The following markings are used in this manual.
CAUTION
Calls attentions to actions or conditions that could cause light injury to the user
or damage to the instrument or the user’s data, and precautions that can be taken to prevent such occurrences.
Note
Calls attention to information that is important for proper operation of the
instrument.
Notation Used in the Procedural Explanations
On pages that describe the operating procedures in chapters 1 through 3, the following notations are used to distinguish the procedures from their explanations.
Procedure
Carry out the procedure according to the step numbers. All procedures are
written with inexperienced users in mind; experienced users may not need to
carry out all the steps.
Explanation
This section describes the setup items and the limitations regarding the
procedures.
Notation of User Controls
Operation/Soft Key Names and Menu Items Set in Boldface
Boldface type indicates the names of user-controlled operation keys on the instrument panel, and soft key items and menu items displayed on screen.
SHIFT+Panel Key
The SHIFT+Panel key means you will press the SHIFT key to turn ON the indicator of SHIFT key and then press the panel key. The menu marked in purple above the pressed key appears on the screen.
Unit
k: Denotes “1000.” Example: 100 kS/s (sample rate) K: Denotes “1024.” Example: 720 KB (file data size)
Symbols Used in the Syntax
The following table indicates symbols that are used in the syntax mainly in chapters 4 and 5. These symbols are referred to as BNF (Backus-Naur Form) symbols. For details on the data, see pages 4-5 and 4-6.
Symbol Meaning Example Example of Input
< >
Defined value
CHANnel<x> <x> = 1 to 4 CHANNEL2
{}
Select from values given in { }
COUPling {AC|DC|DC50|GND} COUPLING AC
|
Exclusive OR
[]
Can be omitted
TRIGger [:SIMPle]:SLOPe TRIGger:SLOPe
How to Use This Manual
v
Contents
How to Use This Manual .................................................................................................................. iii
Chapter 1 Overview of the USB Interface
1.1 Part Names and Functions ............................................................................................... 1-1
1.2 USB Interface Functions and Specications .................................................................... 1-2
1.3
Connection via the USB Interface .................................................................................... 1-4
1.4
Setting the DL6000/DLM6000 (USB) ............................................................................... 1-5
Chapter 2 Overview of the Ethernet Interface (Optional)
2.1 Part Names and Functions ............................................................................................... 2-1
2.2 Ethernet/VXI-11 Interface Features and Specications .................................................... 2-2
2.3
Connecting to the Ethernet/VXI-11 Interface .................................................................... 2-4
2.4
Setting the DL6000/DLM6000 (Network) ......................................................................... 2-5
Chapter 3 Overview of the GP-IB Interface
3.1 Part Names and Functions ............................................................................................... 3-1
3.2 Connecting the GP-IB Card .............................................................................................. 3-2
3.3
GP-IB Interface Functions ................................................................................................ 3-3
3.4
GP-IB Interface Specications ......................................................................................... 3-4
3.5
Setting the DL6000/DLM6000 (GP-IB) ............................................................................. 3-5
3.6
Responses to Interface Messages ................................................................................... 3-6
Chapter 4 Before Programming
4.1 Messages ......................................................................................................................... 4-1
4.2 Commands ....................................................................................................................... 4-3
4.3
Response ......................................................................................................................... 4-5
4.4
Data .................................................................................................................................. 4-6
4.5
Synchronization with the Controller .................................................................................. 4-8
Chapter 5 Commands
5.1 List of Commands ............................................................................................................ 5-1
5.2 ACQuire Group .......................................................................................................
........ 5-35
5.3 ANALysis Group ......................................................................................................
....... 5-36
5.4 ASETup Group ......................................................................................................
......... 5-58
5.5 CALibrate Group ......................................................................................................
...... 5-59
5.6 CHANnel Group ......................................................................................................
....... 5-60
5.7 CLEar Group ......................................................................................................
............ 5-62
5.8 COMMunicate Group ..................................................................................................... 5-63
5.9
CURSor Group ......................................................................................................
......... 5-65
5.10 DISPlay Group ......................................................................................................
......... 5-74
5.11 FILE Group .......................................................................................................
.............. 5-77
5.12 GONogo Group ......................................................................................................
........ 5-81
5.13 HCOPy Group ......................................................................................................
.......... 5-90
5.14 HISTory Group .......................................................................................................
......... 5-92
5.15 IMAGe Group ......................................................................................................
......... 5-101
5.16 INITialize Group .......................................................................................................
..... 5-102
5.17 LOGic Group ......................................................................................................
.......... 5-103
5.18 MATH Group................................................................................................................. 5-106
5.19
MEASure Group ......................................................................................................
......5-111
1
2
3
4
5
6
App
Index
vi
Contents
5.20 REFerence Group ......................................................................................................
.. 5-120
5.21 SEARch Group .......................................................................................................
...... 5-121
5.22 SNAP Group .......................................................................................................
.......... 5-132
5.23 SSTart Group .......................................................................................................
......... 5-133
5.24 STARt Group ......................................................................................................
.......... 5-134
5.25 STATus Group ......................................................................................................
........ 5-135
5.26 STOP Group .......................................................................................................
.......... 5-136
5.27 SYSTem Group ......................................................................................................
...... 5-137
5.28 TELecomtest (Mask) Group ......................................................................................... 5-139
5.29
TIMebase Group ......................................................................................................
.... 5-143
5.30 TRIGger Group .......................................................................................................
...... 5-144
5.31 WAVeform Group .......................................................................................................
... 5-170
5.32 ZOOM Group .......................................................................................................
......... 5-173
5.33 Common Command Group .......................................................................................... 5-175
Chapter 6 Status Reports
6.1 Overview of the Status Report ......................................................................................... 6-1
6.2 Status Byte ......................................................................................................
................. 6-3
6.3 Standard Event Register .................................................................................................. 6-4
6.4
Extended Event Register .................................................................................................. 6-5
6.5
Output Queue and Error Queue ....................................................................................... 6-6
Appendix
Appendix 1 ASCII Character Codes ......................................................................................App-1
Appendix 2 Error Messages .................................................................................................. App-2
Appendix 3
Waveform Parameter Name Table ..................................................................... App-4
Appendix 4
Eye Pattern Parameter Name Table................................................................... App-5
Index
1-1
Overview of the USB Interface
1

Chapter 1 Overview of the USB Interface

1.1 Part Names and Functions

Front Panel
PRINT
FILE
UTILITY
DISPLAY
ACQUIRE
X - Y
VERTICAL
POSITION
PUSH ODIV
PUSH FINE
SCALE
HORIZONTAL
POSITION
TIME/DIV
PUSH 50% 0 s
TRIGGER
LEVEL
TRIG’D
PUSH 50%
ZOOM
EDGE
ENHANCED
MODE B TRIG
ACTION
GO / NO-GO
ZOOM1 ZOOM2
SEARCH
4
3
21
RUN / STOP
SHIFT
DELAY
1
2
3
4
LOGIC
ESC
CLEAR
SNAP
CURSOR
MEASURE
ANALYSIS
MATH/REF
FFTFFTMASK
MENU
AUTO SETUP
SETUP MENU
HISTORY
SINGLE
REST SE T
SYSTEM key
Press this key to select the USB interface.
SHIFT + CLEAR key
Press this key to clear the remote mode (controlled via communications) and enter the local mode in which key operations are enabled. However, this act is invalid if the instrument has been set to Local Lockout mode (see page 1-3) by the controller.
Rear Panel
WARNING
警告
CAUTION
注意
VIDEO OUT
(XGA)
PROBE POWER
( )
12 V DC
TRIG IN
TRIG OUT
ETHERNET
100BASE-TX
ACT
LINK
USB
GO/NOG O
MAIN POWER
OFF ON
100 - 120/2 20 - 24 0 V AC
300 VA MAX 50/60 H z
MODEL
NO.
SUFFIX
Made in Japan
No Auto-MDIX
WARNING
警告
Do not operate without reading safety precautions in user’s manual.
安全にご私用していただくために、取扱説明書に記載の注意事項を必ずお守りください。
CAUTION
注意
Protect the instrument from vibration or shock when power is ON.
故障を防ぐために、電源投入中は、振動/衝撃を避けてください。
PROBE POWER (±12 V DC
)
VIDEO OUT
(
XGA
)
TRIG IN
TRIG OUT
USB
GO/NOGO
ETHERNET 100BASE-TX
ACT
LINK
LOGIC PROBE
A
B C D
N20 0
MAIN POWER
OFF
ON
100 - 120/220 - 240 V AC
300 VA MAX 50/60 Hz
No Auto-MDIX
DL6000
DLM6000
USB interface connector
Connector used to connect the DL6000/DLM6000 to the controller (such as a PC) using a USB cable.
USB interface connector
Connector used to connect the DL6000/DLM6000 to the controller (such as a PC) using a USB cable.
1-2

1.2 USB Interface Functions and Specifications

USB Interface Functions
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 parameters of the panel, and
error codes.
Transmission Function
Outputs measured and computed data. Outputs panel setup parameters and the status byte. Outputs error codes that have occurred.
USB Interface Specifications
Electrical and mechanical specifications: Conforms to USB Rev. 2.0 Connector: Type B connector (receptacle) Number of ports: 1 Power supply: Self-powered PC system supported: PC running Windows 2000 or Windows XP with a standard USB
port (a separate device driver is needed to connect to a PC).
Data Rate
Controller: PC (Pentium4 3.4 GHz, USB2.0) and OS (Windows XP Professional
SP1)
Language used:
Visual C++
The table below lists the reference response times when outputting waveform data of analog signals.
Number of Data Points Word Data ASCII Data
2500 Approx. 51 ms Approx. 0.469 s 125000 Approx. 193 ms Approx. 22.766 s 1250000 Approx. 1606 ms Approx. 224.890 s 2500000 Approx. 3188 ms Approx. 451.297 s 6250000 Approx. 7841 ms Approx. 1127.625 s
The table below lists the reference response times when outputting waveform data of logic signals.
Number of Data Points Word Data ASCII Data
2500 Approx. 78 ms Approx. 0.141 s 125000 Approx. 625 ms Approx. 3.516 s 1250000 Approx. 5547 ms Approx. 34.531 s 2500000 Approx. 11156 ms Approx. 69.375 s 6250000 Approx. 27812 ms Approx. 173.266 s
1-3
Overview of the USB Interface
1
1.2 USB Interface Functions and Specifications
Switching between Remote and Local Modes
When Switching from Local to Remote Mode
If the DL6000/DLM6000 receives a “:COMMunicate:REMote ON” command from the PC when it is
in the local mode, it switches to the remote mode.
REMOTE is displayed in the center of the upper section of the screen.
• All keys except the
SHIFT + CLEAR key are disabled.
Settings entered in local mode are retained even when the DL6000/DLM6000 switches to remote
mode.
When Switching from Remote to Local Mode
Pressing SHIFT + CLEAR in remote mode puts the instrument in local mode. However, this is void
when the DL6000/DLM6000 has received a “:COMMunicate:LOCKout ON” command from the PC (local lockout condition). When the DL6000/DLM6000 receives a “:COMMunicate:REMote OFF” command from the PC, the DL6000/DLM6000 switches to the local mode regardless of the local lock condition.
REMOTE indication in the center of the upper section of the screen disappears.
• Key operations are enabled.
• Settings entered in remote mode are retained even when the DL6000/DLM6000 switches to local mode.
Note
The USB interface cannot be used simultaneously with another interface (Ethernet or GP-IB interface).
1-4

1.3 Connection via the USB Interface

Precautions to Be Taken When Making Connections
• Connect the USB cable by inserting the connector firmly into the USB connector.
• When connecting multiple devices using USB hubs, connect the DL9710L to the USB hub that is closest to the controller.
Do not insert the USB cable into the GO/NO-GO output terminal. If you do, the instrument may
malfunction.
1-5
Overview of the USB Interface
1

1.4 Setting the DL6000/DLM6000 (USB)

Procedure
UTILITY_Remote Control_UBS Menu
Press UTILITY, the Remote Control soft key, and then the USB soft key to display the following.
To remotely control the DL6000/DLM6000 using communication commands through the USB port, select USBTMC and then enable the setting by restarting the DL6000/DLM6000.
Note
• Only the communication interface selected by Remote Control is enabled. The DL6000/DLM6000 does
not accept commands that are transmitted to other unselected communication interfaces.
• To control the DL6000/DLM6000 remotely using communication commands through the USB port, select
“TMC” in the menu above, and carry out the procedure below.
• You must restart the DL6000/DLM6000 to activate the TMC or Mass Storage setting. Wait at least 10
seconds after you turn the power switch OFF, and then turn the switch back ON.
• Install YOKOGAWA’s TMC (Text and Measurement Class) driver into your PC. To obtain YOKOGAWA’
s USB TMC driver, contact your nearest YOKOGAWA dealer or access the following USB driver page
at our Web site and download it.
http://www.yokogawa.com/tm/tm-softdownload.htm
• Only use the USB TMC driver (or software) provided by YOKOGAWA.
• You cannot use keys to perform file operations when a PC is connected to the DL6000/DLM6000 and the
Mass Storage setting is enabled. You cannot use communication commands to perform file operations
either. To perform file operations, you must restart the DL6000/DLM6000 after disconnecting the PC or
enabling the TMC setting.
2-1
Overview of the Ethernet Interface (Optional)
1
2

2.1 Part Names and Functions

Front Panel
PRINT
FILE
UTILITY
DISPLAY
ACQUIRE
X - Y
VERTICAL
POSITION
PUSH ODIV
PUSH FINE
SCALE
HORIZONTAL
POSITION
TIME/DIV
PUSH 50% 0 s
TRIGGER
LEVEL
TRIG’D
PUSH 50%
ZOOM
EDGE
ENHANCED
MODE B TRIG
ACTION
GO / NO-GO
ZOOM1 ZOOM2
SEARCH
4
3
21
RUN / STOP
SHIFT
DELAY
1
2
3
4
LOGIC
ESC
CLEAR
SNAP
CURSOR
MEASURE
ANALYSIS
MATH/REF
FFTFFTMASK
MENU
AUTO SETUP
SETUP MENU
HISTORY
SINGLE
REST SE T
SHIFT + CLEAR key
Press this key to switch from remote mode to local mode and enable the front panel keys. This key is disabled when the DL6000/DLM6000 has been set to Local Lockout mode (see page 2-3) by a controller.
SYSTEM key
Press this key to select the Ethernet or VXI-11 interface.
Rear Panel
WARNING
警告
CAUTION
注意
VIDEO OUT
(XGA)
PROBE POWER
( )
12 V DC
TRIG IN
TRIG OUT
ETHERNET
100BASE-TX
ACT
LINK
USB
GO/NOG O
MAIN POWER
OFF ON
100 - 120/2 20 - 24 0 V AC
300 VA MAX 50/60 H z
MODEL
NO.
SUFFIX
Made in Japan
No Auto-MDIX
WARNING
警告
Do not operate without reading safety precautions in user’s manual.
安全にご私用していただくために、取扱説明書に記載の注意事項を必ずお守りください。
CAUTION
注意
Protect the instrument from vibration or shock when power is ON.
故障を防ぐために、電源投入中は、振動/衝撃を避けてください。
PROBE POWER (±12 V DC
)
VIDEO OUT
(
XGA
)
TRIG IN
TRIG OUT
USB
GO/NOGO
ETHERNET
100BASE-TX
ACT
LINK
LOGIC PROBE
A
B C D
N20 0
MAIN POWER
OFF
ON
100 - 120/220 - 240 V AC
300 VA MAX 50/60 Hz
No Auto-MDIX
DL6000
DLM6000
Ethernet port
This port is for connecting the DL6000/DLM6000 to a controller (such as a PC) using an Ethernet cable.
Ethernet port
This port is for connecting the DL6000/DLM6000 to a controller (such as a PC) using an Ethernet cable.

Chapter 2 Overview of the Ethernet Interface (Optional)

2-2

2.2 Ethernet/VXI-11 Interface Features and Specifications

Ethernet/VXI-11 Interface Features
Reception Feature
The DL6000/DLM6000 reception feature allows you to specify the same settings through an
Ethernet connection that you can specify using the front panel keys.
The DL6000/DLM6000 can receive output requests for measu
red and computed data, panel setting
data, and error codes.
Transmission Feature
The DL6000/DLM6000 can transmit measured and computed data. The DL6000/DLM6000 can transmit panel setting data and the status byte. The DL6000/DLM6000 can transmit error codes when errors occur.
Ethernet/VXI-11 Interface Specifications
Electrical and mechanical specifications
IEEE802.3 compliant
Simultaneous connections 1 Port number Ethernet: 10001/tcp
VXI-11: 10240/tcp, 10250/tcp, 111/tcp, and 111/udp
Data Transfer Rates
Controller: PC (Pentium 4 3.4-GHz) with Windows XP Professional SP1 Network adapter: Corega FEther PCI-TXL Programming language: Visual C++
Ethernet Interface (/C8, /C9, /C10 and /C12 options)
The following table contains approximate waveform data response times for analog signals.
Number of Data Points Word Data ASCII Data
2500 Approx. 16 ms Approx. 0.391 s 125000 Approx. 259 ms Approx. 19.063 s 1250000 Approx. 2313 ms Approx. 189.812 s 2500000 Approx. 4595 ms Approx. 379.750 s 6250000 Approx. 10400 ms Approx. 950.532 s
The following table contains approximate waveform data response times for logic signals.
Number of Data Points Double Word Data ASCII Data
2500 Approx. 31 ms Approx. 0.078 s 125000 Approx. 704 ms Approx. 3.530 s 1250000 Approx. 6768 ms Approx. 35.327 s 2500000 Approx. 14081 ms Approx. 70.952 s 6250000 Approx. 34523 ms Approx. 177.313 s
VXI-11 Ethernet Interface (/C8, /C9, /C10 and /C12 options)
The following table contains approximate waveform data response times for analog signals.
Number of Data Points Word Data ASCII Data
2500 Approx. 31 ms Approx. 0.406 s 125000 Approx. 235 ms Approx. 19.172 s 1250000 Approx. 2286 ms Approx. 191.876 s 2500000 Approx. 4541 ms Approx. 383.012 s 6250000 Approx. 11150 ms Approx. 958.128 s
2-3
Overview of the Ethernet Interface (Optional)
1
2
The following table contains approximate waveform data response times for logic signals.
Number of Data Points Double Word Data ASCII Data
2500 Approx. 31 ms Approx. 0.094 s 125000 Approx. 828 ms Approx. 3.906 s 1250000 Approx. 6938 ms Approx. 37.345 s 2500000 Approx. 13344 ms Approx. 74.143 s 6250000 Approx. 32126 ms Approx. 184.894 s
Switching between Remote and Local Modes
When Switching from Local to Remote Mode
The DL6000/DLM6000 switches to remote mode when it is in local mode and it receives a
:COMMunicate:REMote ON
command from the PC.
“REMOTE” appears at the top center of the screen.
• All keys except the
SHIFT + CLEAR key are disabled.
Settings entered in local mode are retained even when the DL6000/DLM6000 switches to remote
mode.
When Switching from Remote to Local Mode
When the DL6000/DLM6000 is in remote mode and you press SHIFT + CLEARCLEAR, the
DL6000/DLM6000 switches to Local mode, unless it has received a
:COMMunicate:LOCKout
ON
command from the PC, in which case pressing SHIFT + CLEARCLEAR will have no effect.
The DL6000/DLM6000 switches to local mode when it receives a
:COMMunicate:REMote OFF
command from the PC, regardless of the local lockout state.
The “REMOTE” indicator at the top center of the screen disappears.
• Key operations are enabled.
• Settings entered in remote mode are retained even when the DL6000/DLM6000 switches to local mode.
Note
The Ethernet/VXI-11 interface cannot be used simultaneously with another interface (USB or GP-IB
interface).
User Authentication Feature
You must enter a user name and password to access the DL6000/DLM6000 through the Ethernet interface. If the DL Series Library (TMCTL) version is 1.40 or later, the password is encrypted using the MD5 algorithm (RSA Data Security, Inc. MD5 Message-Digest Algorithm) and then sent to the DL6000/ DLM6000. Set the user name and password in the Remote Control setup screen in the DL6000/DLM6000 UTILITY menu. For instructions on how to set the user name and password, see section 2.4, “Setting the DL6000/DLM6000 (Network).” If you select VXI-11 in the Device menu of the Remote Control setup screen (explained later), the user authentication setup menu will not appear in the Remote Control setup screen.
2.2 Ethernet/VXI-11 Interface Features and Specifications
2-4

2.3 Connecting to the Ethernet/VXI-11 Interface

Connection Procedure
Connect a UTP (Unshielded Twisted-Pair) or STP (Shielded Twisted-Pair) cable that is connected to a hub or other network device to the 100BASE-TX port on the DL6000/DLM6000 rear panel.
PC
DL6000/ DLM6000
Hub or router that supports 100BASE-TX
Straight UTP or STP cable
ETHERNET
100BASE-TX
ACT
LIN K
No Auto-MDIX
RJ-45 modular jack
100BASE-TX Ethernet port
LINK LED
Illuminates when a link is established between the DL9500/DL9700 and another device and the devices are capable of communicating with each other
ACT LED
Blinks when packets are being sent and received normally
Notes about Connections
• Be sure to connect the DL6000/DLM6000 to a PC through a hub using straight cables. The DL6000/ DLM6000 may not operate properly if you connect it to a PC directly using a cross cable.
If you use UTP cables (straight cables), make sure that they are category 5.
2-5
Overview of the Ethernet Interface (Optional)
1
2

2.4 Setting the DL6000/DLM6000 (Network)

Procedure
UTILITY_Remote Control_Network Menu
Press UTILITY, the Remote Control soft key, and then the Network or Network(VXI-11) soft key to display the following menu.
Select to use the Ethernet interface.
Select to use the VXI-11 interface.
Set the timeout value.
Set the timeout value.
Set the user name.
Set the password.
Note
• Only the interface that you select after pressing Remote Control is valid. The DL6000/DLM6000 does not
accept commands that are transmitted to other unselected communication interfaces.
• For details on how to operate the soft keyboard, see section 4.2, “Entering Values and Strings” in the
DL6000/DLM6000 User’s Manual (IM DLM6054-01EN).
• User names and passwords are case-sensitive.
Explanation
To use a controller to configure the same settings that you can configure using the DL6000/DLM6000 keys or to send setting parameters and waveform data to a controller, you must configure the settings described below.
User Name and Password
The Ethernet interface has a user authentication feature. Set the DL6000/DLM6000 user name and password in advance. If you select VXI-11 in the Device menu of the Remote Control setup screen, the user authentication setup menu will not appear in the Remote Control setup screen.
User Name
Set the user name using up to 30 characters. The default setting is “anonymous.”
Password
Set the password using up to 30 characters.
2-6
Timeout Value
The DL6000/DLM6000 disconnects itself from the controller if it is not accessed for the period of time that you specify using the timeout value.
TCP/IP
To use the Ethernet interface, you must specify the following TCP/IP settings.
• IP address
• Subnet mask
• Default gateway
For details on how to specify these settings, see section 14.2, “Setting Up the TCP/IP” in the DL6000/ DLM6000 User’s Manual (IM DLM6054-01EN).
Note
• The DL6000/DLM6000 terminates the connection if there is an error in the user authentication process.
• You do not need to enter a password when the user name is set to “anonymous.”
2.4 Setting the DL6000/DLM6000 (Network)
3-1
Overview of the GP-IB Interface
1
2
3

3.1 Part Names and Functions

Front Panel
PRINT
FILE
UTILITY
DISPLAY
ACQUIRE
X - Y
VERTICAL
POSITION
PUSH ODIV
PUSH FINE
SCALE
HORIZONTAL
POSITION
TIME/DIV
PUSH 50% 0 s
TRIGGER
LEVEL
TRIG’D
PUSH 50%
ZOOM
EDGE
ENHANCED
MODE B TRIG
ACTION
GO / NO-GO
ZOOM1 ZOOM2
SEARCH
4
3
21
RUN / STOP
SHIFT
DELAY
1
2
3
4
LOGIC
ESC
CLEAR
SNAP
CURSOR
MEASURE
ANALYSIS
MATH/REF
FFTFFTMASK
MENU
AUTO SETUP
SETUP MENU
HISTORY
SINGLE
REST SE T
SYSTEM key
Press this key to select the USB interface.
SHIFT + CLEAR key
Press this key to clear the remote mode (controlled via communications) and enter the local mode in which key operations are enabled. However, this act is invalid if the instrument has been set to Local Lockout mode (see page 3-3) by the controller.
Rear Panel
WARNING
警告
CAUTION
注意
VIDEO OUT
(XGA)
PROBE POWER
( )
12 V DC
TRIG IN
TRIG OUT
ETHERNET
100BASE-TX
ACT
LINK
USB
GO/NOG O
MAIN POWER
OFF ON
100 - 120/2 20 - 24 0 V AC
300 VA MAX 50/60 H z
MODEL
NO.
SUFFIX
Made in Japan
No Auto-MDIX
WARNING
警告
Do not operate without reading safety precautions in user’s manual.
安全にご私用していただくために、取扱説明書に記載の注意事項を必ずお守りください。
CAUTION
注意
Protect the instrument from vibration or shock when power is ON.
故障を防ぐために、電源投入中は、振動/衝撃を避けてください。
PROBE POWER (±12 V DC
)
VIDEO OUT
(
XGA
)
TRIG IN
TRIG OUT
USB
GO/NOGO
ETHERNET
100BASE-TX
ACT
LINK
LOGIC PROBE
A
B C D
N20 0
MAIN POWER
OFF
ON
100 - 120/220 - 240 V AC
300 VA MAX 50/60 Hz
No Auto-MDIX
DL6000
DLM6000
PC card slot
Connect a GP-IB card to the PC card slot and connect to a controller (such as a PC).
PC card slot
Connect a GP-IB card to the PC card slot and connect to a controller (such as a PC).

Chapter 3 Overview of the GP-IB Interface

3-2

3.2 Connecting the GP-IB Card

GP-IB Card
Use the NI PCMCIA-GPIB card by National Instruments.
GP-IB Cable
Use the GP-IB cable that comes with the GP-IB card.
Connection Procedure
Insert the GP-IB card into the DL6000/DLM6000 PC card slot.
To the PC card slot of the DL6000/DLM6000
GP-IB card
GP-IB cable
Precautions to Be Taken When Making Connections
• For the handling of the GP-IB card, see the manual that comes with the GP-IB card.
• Attach the GP-IB correctly with the front face up.
• Connect the GP-IB card to the DL6000/DLM6000 PC card slot first. Then, turn the DL6000/ DLM6000 ON.
Multiple cables can be used to connect multiple devices. However, no more than 15 devices
including the controller can be connected on a single bus.
When connecting multiple devices, each device must have its own unique address.
• Use a cable of length 2 m or less for connecting the devices.
• Make sure the total cable length does not exceed 20 m.
• When communicating, have at least two-thirds of the devices turned ON.
• When connecting multiple devices, connect them in a star or linear configuration (see the figure below). Do not wire them in a loop or parallel configuration.
CAUTION
When connecting or disconnecting communication cables, make sure to turn OFF the PC and the DL6000/DLM6000. Otherwise, erroneous operation or damage to the internal circuitry may result.
3-3
Overview of the GP-IB Interface
1
2
3

3.3 GP-IB Interface Functions

GP-IB Interface Functions
Listener Capability
• All of the information that you can set with the panel keys can be set through the GP-IB interface except for turning ON/OFF the power and setting the communication parameters.
Receives commands from a controller requesting the output of setup information, waveform data,
and other information.
Also receives status report commands.
Talker Capability
Outputs setup information, waveform data, and other information.
Note
Listen-only, talk-only, and controller capabilities are not available on the DL6000/DLM6000.
Switching between Remote and Local Modes
When Switching from Local to Remote Mode
Receiving a REN (Remote Enable) message from the PC when the DL6000/DLM6000 is in the local
mode causes the DL6000/DLM6000 to switch to the remote mode.
REMOTE is displayed in the center of the upper section of the screen.
• All keys except the
SHIFT + CLEAR key are disabled.
Settings entered in local mode are retained even when the DL6000/DLM6000 switches to remote
mode.
When Switching from Remote to Local Mode
Pressing SHIFT + CLEAR in remote mode puts the DL6000/DLM6000 in local mode. However, this
act is invalid if the DL6000/DLM6000 has been set to Local Lockout mode (see page 3-6) by the controller.
REMOTE indication in the center of the upper section of the screen disappears.
• Key operations are enabled.
• Settings entered in remote mode are retained even when the DL6000/DLM6000 switches to local mode.
Note
The GP-IB interface cannot be used simultaneously with another interfaces (USB or network interfaces).
3-4

3.4 GP-IB Interface Specifications

GP-IB Interface Specifications
Electrical and mechanical specifications: Conforms to IEEE St’d 488-1978 Functional specifications: See table below. Protocol: Conforms to IEEE St’d 488.2-1992 Code used: ISO (ASCII) code Mode: Addressable mode Address setting: The address can be set in the range from 0 to 30 on
the GP-IB setting screen that is played using the MISC menu.
Clear remote mode:
Remote mode can be cleared by pressing SHIFT +
CLEAR except when the DL6000/DLM6000 has been set to Local Lockout mode by the controller.
Functional specifications
Function Subset Name Description
Source handshaking SH1 Full source handshaking capability Acceptor handshaking AH1 Full acceptor handshaking capability Talker T6 B
asic talker capability, serial polling, untalk on MLA (My
Listen Address), and no talk-only capability
Listener L4 Basic listener capability
, unlisten on MTA (My Talk
Address), and no listen-only capability. Service request SR1 Full service request capability Remote local RL1 Full remote/local capability Parallel polling PP0 No parallel polling capability Device clear DC1 Full device clear capability Device trigger DT0 No device trigger capability Controller C0 No controller capability Electrical characteristics E1 Open collector
Data Rate
Controller: PC (Pentium4 3.4 GHz, USB 2.0), OS (Windows XP Professional SP1) Language used: Visual C++
The table below lists the reference response times when outputting waveform data of analog signals.
Number of Data Points Word Data ASCII Data
2500 Approx. 16 ms Approx. 0.390 s 125000 Approx. 344 ms Approx. 19.453 s 1250000 Approx. 3172 ms Approx. 194.516 s 2500000 Approx. 6282 ms Approx. 389.047 s 6250000 Approx. 15641 ms Approx. 971.985 s
The table below lists the reference response times when outputting waveform data of logic signals.
Number of Data Points Word Data ASCII Data
2500 Approx. 32 ms Approx. 0.078 s 125000 Approx. 859 ms Approx. 3.609 s 1250000 Approx. 8707 ms Approx. 36.172 s 2500000 Approx. 17365 ms Approx. 72.500 s 6250000 Approx. 43678 ms Approx. 182,000 s
3-5
Overview of the GP-IB Interface
1
2
3

3.5 Setting the DL6000/DLM6000 (GP-IB)

Procedure
UTILITY_Remote Control_GP-IB Menu
Press UTILITY, the Remote Control soft key, and then the GPIB soft key to display the following menu.
Select GP-IB.
Set the address.
Note
Only the communication interface selected by Remote Control is enabled. The DL6000/DLM6000 does not
accept commands that are transmitted to other unselected communication interfaces.
Explanation
Enter the following settings when using a controller to set information that can be specified through key operation on the DL6000/DLM6000 or when outputting setting parameters or output waveform data to the controller.
Setting the Address
Set the address of the DL6000/DLM6000 within the following range for the addressable mode. 0 to 30
Each device that can be connected via GP-IB has a unique address within the GP-IB system. This
address is used to distinguish the device from others. Therefore, when you connect the DL6000/ DLM6000 to a PC, for example, make sure to assign a unique address to the DL6000/DLM6000.
Note
Do not change the address while the controller is communicating with the DL6000/DLM6000 or other devices
over the GP-IB.
3-6

3.6 Responses to Interface Messages

Responses to Interface Messages
Responses to a Uni-Line Message
• IFC (Interface Clear)
Clears the talker and listener functions. Stops output if data are being output.
• REN (Remote Enable)
Switches between the remote and local modes.
IDY (Identify) is not supported.
Responses to a Multi-Line Message (Address Command)
• GTL (Go To Local)
Switches to the local mode.
• SDC (Selected Device Clear)
• Clears the program message (command) being received and the output queue (see page 6-5).
• *OPC and *OPC? commands in execution are void.
• The *WAI and COMMunicate:WAIT commands are immediately terminated.
PPC (Parallel Poll Configure), GET(Group Execute Trigger), and TCT (Take Control) are not
supported.
Responses to a Multi-Line Message (Universal Command)
• LLO (Local Lockout)
Disables CLEAR on the front panel to prohibit switching to the local mode.
DCL (Device Clear)
Same operation as the SDC message.
• SPE (Serial Poll Enable)
Sets the talker function on all devices on the bus to serial polling mode. The controller polls the
devices in order.
SPD (Serial Poll Disable)
Clears the serial polling mode of the talker function on all devices on the bus.
PPU (Parallel Poll Unconfigure) is not supported.
What Are Interface Messages
Interface messages are also referred to as interface commands or bus commands. They are commands that are issued by the controller. They are classified as follows:
Uni-Line Messages
A single control line is used to transmit uni-line messages. The following three types are available.
• IFC (Interface Clear)
• REN (Remote Enable)
• IDY (Identify)
3-7
Overview of the GP-IB Interface
1
2
3
Multi-Line Messages
Eight data lines are used to transmit multi-line messages. The messages are classified as follows:
• Address Commands
These commands are valid when the instrument is designated as a listener or as a talker. The
following five types are available.
Commands that are valid on an instrument that is designated
as a listener
• GTL (Go To Local)
• SDC (Selected Device Clear)
• PPC (Parallel Poll Configure)
• GET (Group Execute Trigger)
Commands that are valid on an instrument that is designated as a talker
• TCT (Take Control)
• Universal commands
These commands are valid on all instruments regardless of the listener and talker designations.
The following five types are available.
LLO (Local Lockout)
• DCL (Device Clear)
• PPU (Parallel Poll Unconfigure)
• SPE (Serial Poll Enable)
• SPD (Serial Poll Disable)
In addition, listener address, talker address, and secondary commands are also considered interface messages.
Interface messages
Uni-line
messages
Address
commands
Universal
commands
♦HIFC ♦HREN
IDY
♦HGTL ♦HSDC
PPC GET TCT
♦HLLO ♦HDCL
PPU
♦HSPE ♦HSPD
Listener
address
Talker
address
Secondary commands
Multi-line messages
Interface messages that DL6000/DLM6000 supports are indicated with ♦ marks.
Note
The Differences between SDC and DCL
In multi-line messages, SDC messages are those that require talker or listener designation and DCL
messages are those that do not require the designation. Therefore, SDC messages are directed at a
particular instrument while DCL messages are directed at all instruments on the bus.
3.6 Responses to Interface Messages
4-1
Before Programming
1
2
3
4

4.1 Messages

Program Message Unit Format
The program message unit format is shown below
,
<Program header>
<Program data>Space
<Program Header>
The program header indicates the command type. For details, see page 4-3.
<Program Data>
If certain conditions are required in executing a command, program data is added. A space (ASCII code “20H”) separates the program data from the header. If there are multiple sets of program data, they are separated by commas (,). For details, see page 4-5.
Example
:ACQuire:MODE NORMal<PMT>
Header Data
Response Messages
The response message format is shown belo.
<RMT>
;
<Response message unit>
<Response Message Unit>
A response message consists of one or more response message units; each response message unit corresponds to one response. Response message units are separated by a semicolon (;). For details regarding the format of the response message unit, see the next section.
Example
Unit Unit
:ACQUIRE:MODE NORMAL;HRMode 1<RMT>
<RMT>
A response message terminator. It is
NL^EOM
.
Messages
Messages are used to exchange information between the controller and the instrument. Messages that are sent from the controller to the instrument are called program messages and messages that are sent back from the instrument to the controller are called response messages. If a program message contains a message unit that requests a response (a query), the instrument returns a response message upon receiving the program message. A single response message is always returned in response to a single program message.
Program Messages
The program message format is shown below
<PMT>
;
<Program message unit>
<Program Message Unit>
A program message consists of zero or more program message units; each unit corresponds to one command. The instrument executes the received commands in order. Each program message unit is separated by a semicolon (;). For details regarding the format of the program message unit, see the next section.
Example
Unit Unit
:ACQuire:MODE NORMal;HRMode 1<PMT>
<PMT>
PMT is a program message terminator. The following three types are available.
NL
(New Line):
Same as LF (Line Feed). ASCII
code “0AH”
^EOM
:
The END message as defined by USBTMC
(The data byte that is sent simultaneously
with the END message is the last data of the program message.)
NL^EOM
:
NL with an END message added
(NL is not included in the program
message.)
Chapter 4
Before Programming
4-2
Response Message Unit Format
The response message unit format is shown belw.
,
<Response header>
<Response data>Space
<Response Header>
A response header sometimes precedes the response data. A space separates the data from the header. For details, see page 4-4.
<Response Data>
Response data contains the content of the response. If there are multiple sets of response data, they are separated by commas (,). For details, see page 4-5.
Example
1.25E-02<RMT> :ACQUIRE:MODE NORMAL<RMT>
HeaderData Data
If there are multiple queries in a program message, responses are made in the same order as the queries. In most cases, a single query returns a single response message unit, but there are a few queries that return multiple units. The first response message unit always corresponds to the first query, but the n
th
response
unit may not necessarily correspond to the n
th
query. Therefore, if you want to make sure that every response is retrieved, divide the program messages into individual messages.
Precautions to Be Taken when Transferring Messages
• If a program message that does not contain a query
is sent, the next program message can be sent at any time.
If a program message that contains a query is sent,
a response message must be received before the next program message can be sent. If the next program message is sent before the response message is received in its entirety, an error occurs. The response message that was not received is discarded.
If the controller tries to receive a response message
when there is none, an error occurs. If the controller tries to receive a response message before the transmission of the program message is complete, an error occurs.
If a program message containing multiple message
units is sent, and the message contains incomplete units, the instrument attempts to execute the ones that are believed to be complete. However, these attempts may not always be successful. In addition, if the message contains queries, the responses may not be returned.
Deadlock
The instrument can store in its buffer program and response messages of length 1024 bytes or more (The number of available bytes varies depending on the operating conditions). When both the transmit and receive buffers become full at the same time, the instrument can no longer continue to operate. This state is called a deadlock. In this case, operation can be resumed by discarding the program message. Deadlock will not occur if the program message (including the <PMT>) is kept below 1024 bytes. Furthermore, deadlock never occurs if a program message does not contain a query.
4.1 Messages
4-3
Before Programming
1
2
3
4

4.2 Commands

• When Concatenating Commands of the Same Group
The instrument stores the hierarchical level of the
command that is currently being executed, and performs analysis on the assumption that the next command sent will also belong to the same level. Therefore, common header sections can be omitted for commands belonging to the same group. Example
:ACQuire:MODE NORMal;
INTERLeave 1<PMT>
When Concatenating Commands of Different
Groups
If the following command does not belong to the
same group, a colon (:) is placed in front of the header (cannot be omitted). Example
:ACQuire:MODE NORMal;:DISPlay:
FORMat SINGle<PMT>
When Concatenating Simple Headers
If a simple header follows another command, a
colon (:) is placed in front of the simple header (cannot be omitted). Example
:ACQuire:MODE NORMal;:
STARt<PMT>
When Concatenating Common Commands
Common commands that are defined in the
USBTMC-USB488 are independent of hierarchy. Colons (:) are not needed before a common command. Example
:ACQuire:MODE NORMal;*CLS;
INTERLeave 1<PMT>
When Separating Commands with <PMT>
If a terminator is used to separate two commands,
each command is a separate message. Therefore, the common header must be specified for each command even when commands belonging to the same command group are being concatenated. Example
:ACQuire:MODE NORMal<PMT>:
ACQuire:INTERLeave 1<PMT>
Commands
There are three types of commands (program headers) that are sent from the controller to the instrument. They differ in their program header formats.
Common Command Header
Commands that are defined in the USBTMC-USB488 are called common commands. The header format of a common command is shown below. An asterisk (*) is always placed in the beginning of a cmmand.
*
<Mnemonic> ?
Common command example:
*CLS
Compound Header
Dedicated commands used by the instrument are classified and arranged in a hierarchy according to their functions. The format of a compound header is shown below. A colon (:) must be used to specify a lower hiearchy.
:
<Mnemonic> ?:
Compound header example:
:ACQuire:MODE
Simple Header
These commands are functionally independent and do not have a hierarchy. The format of a simple header is shownbelow.
<Mnemonic> ?:
Simple header example:
:STARt
Note
A <mnemonic> is a character string made up of
alphanumeric characters.
When Concatenating Commands
• Command Group
A command group is a group of commands that have
common compound headers arranged in a hierarchy. A command group may contain sub-groups.
Example
Group of commands related to acquisition
:ACQuire:AVERage:COUNt
:ACQuire:MODE
:ACQuire:AVERage:EWEight
:ACQuire:REPetitive
:ACQuire:RLENgth
:ACQuire:INTERLeave
4-4
Upper-Level Query
An upper-level query is a query in which a question mark (?) is appended to the highest level command of a group. Execution of an upper-level query allows all settings that can be specified in the group to be received at once. Some query groups which are comprised of more than three hierarchical levels can output all the lower level settings. Example
:ACQUIRE? -> :ACQUIRE:AVERAGE:
COUNT 2;EWEIGHT 16;:ACQUIRE:
HRMODE 0;INTERLEAVE 0;
INTERPOLATE 1;MODE NORMAL;
REPETITIVE 0;RLENGTH 12500
The response to an upper-level query can be transmitted as a program message back to the instrument. In this way, the settings that existed when the upper-level query was made can be restored. However, some upper-level queries do not return setup information that is not currently in use. It is important to remember that not all the group’s information is necessarily returned as part of a response.
Header Interpretation Rules
The instrument interprets the header that is received according to the rules below.
Mnemonics are not case sensitive.
Example “
CURSor
” can also be written as “
cursor
or “
Cursor
.”
The lower-case section of the header can be
omitted.
Example “
CURSor
” can also be written as “
CURSO
or “
CURS
.”
The question mark (?) at the end of a header
indicates that it is a query. The question mark (?) cannot be omitted.
Example
The shortest abbreviation for
CURSor?
is
CURS?
.
If the <x> (value) at the end of a mnemonic is
omitted, it is interpreted as a 1.
Example If “
CHANnel<x>
” is written as “
CHAN
,” it
means “
CHANnel1
.”
The section enclosed by braces ([]) can be
omitted.
Example
HISTory[:CURRent]:MODE
can also be
written as
HIST:MODE
.
However
, the last section enclosed by braces ([])
cannot be omitted in an upper-level query.
Example “
HISTory?
” and “
HISTory:CURRent?
are different queries.
4.2 Commands
4-5
Before Programming
1
2
3
4

4.3 Response

Response
When the controller sends a message unit that has a question mark (?) in its program header (query), the instrument returns a response message to the query. A response message is returned in one of the following two forms.
Response Consisting of a Header and Data
If the response can be used as a program message
without any change, it is returned with a command header attached. Example
:ACQUire:MODE?<PMT>
-> :ACQUire:MODE NORMAL<RMT>
Response Consisting of Data Only
If the response cannot be used as a program
message unless changes are made to it (query­only command), only the data section is returned. However, there are query-only commands that return responses with the header attached. Example
:MEASure:TRACe1:AREA1:PTOPeak:
VALue?<PMT> -> 10.0E+00<RMT>
When You Wish to Return a Response without a Header
Responses that return both header and data can be set so that only the data section is returned. The “
COMMunicate:HEADer
” command is used to do this.
Abbreviated Form
Normally, the lower-case section is removed from a response header before the response is returned to the controller. Naturally, the full form of the header can also be used. For this, the “
COMMunicate:VERBose
” command is used. The sections enclosed by braces ([]) are also omitted in the abbreviated form.
Loading...
+ 196 hidden pages