YOKOGAWA DL6054 (01) PDF Document

You can check the firmware version of your YOKOGAWA DL6054 on the overview screen. For instructions on how to open the overview screen, please refer to section 18.4 in the User’s Manual IM 701331-01E.

The following manuals are provided for the YOKOGAWA DL6054 series oscilloscope. It is recommended to read all of them for correct use.

To use the communication functions of the YOKOGAWA DL6054, you will need the following items on your PC:

For the USB Interface:

• DL Series Library (TMCTL)

• USB device driver for connecting the PC and the DL9000 series

For the Ethernet Interface:

• DL Series Library (TMCTL)

The manual for the YOKOGAWA DL6054 uses the following symbols and notations to describe communication commands and syntax:

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.

Units:

• k: Denotes “1000.” Example: 100 kS/s (sample rate)

• K: Denotes “1024.” Example: 720 KB (file data size)

Symbols Used in the Syntax (BNF – Backus-Naur Form):

Front Panel Controls:

• 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 action is invalid if the instrument has been set to Local Lockout mode by the controller.

Rear Panel Controls:

• USB interface connector: This is the connector used to connect the YOKOGAWA DL6054 to a controller (such as a PC) using a USB cable.

USB Interface Functions:

• Reception Function: You can specify the same settings as those specified by front panel key operations. It receives output requests for measured and computed data, setup parameters of the panel, and error codes.

• Transmission Function: It outputs measured and computed data, panel setup parameters, the status byte, and error codes that have occurred.

USB Interface Specifications:

The following are reference response times when outputting waveform data. The test environment consists of a PC (Pentium4 3.4 GHz, USB2.0) with Windows XP Professional SP1, using Visual C++.

Analog Signals:

Logic Signals:

Switching from Local to Remote Mode

If the YOKOGAWA DL6054 receives a “:COMMunicate:REMote ON” command from the PC while in local mode, it will switch to 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.

Switching from Remote to Local Mode

Pressing SHIFT + CLEAR in remote mode puts the instrument in local mode. However, this is not possible if the YOKOGAWA DL6054 has received a “:COMMunicate:LOCKout ON” command from the PC (local lockout condition).

When the YOKOGAWA DL6054 receives a “:COMMunicate:REMote OFF” command, it switches to local mode regardless of the local lock condition.

• The REMOTE indication on the screen disappears.

• Key operations are enabled.

• Settings entered in remote mode are retained.

Note: The USB interface cannot be used simultaneously with another interface (Ethernet or GP-IB).

When making connections to the USB interface of your YOKOGAWA DL6054, please observe the following precautions:

• Connect the USB cable by inserting the connector firmly into the USB connector.

• When connecting multiple devices using USB hubs, connect the oscilloscope 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.

To set up the USB interface for remote communication on your YOKOGAWA DL6054, follow these steps:

1. Press the UTILITY key.

2. Press the Remote Control soft key.

3. Press the USB soft key to display the USB menu.

4. To remotely control the oscilloscope using communication commands through the USB port, select USBTMC.

5. Restart the YOKOGAWA DL6054 to enable the setting.

Important Notes:

• Only the communication interface selected under Remote Control is enabled. The oscilloscope will not accept commands transmitted to other unselected interfaces.

• You must restart the oscilloscope to activate the TMC or Mass Storage setting. Wait at least 10 seconds after turning the power switch OFF before turning it back ON.

• You must install YOKOGAWA’s TMC (Test and Measurement Class) driver on your PC. Only use the USB TMC driver or software provided by YOKOGAWA.

• You cannot use keys or communication commands to perform file operations when a PC is connected and the Mass Storage setting is enabled. To perform file operations, you must restart the oscilloscope after disconnecting the PC or enabling the TMC setting.

Ethernet/VXI-11 Interface Features:

• Reception Feature: Allows you to specify the same settings through an Ethernet connection as you can with the front panel keys. The oscilloscope can receive output requests for measured data, panel settings, and error codes.

• Transmission Feature: The oscilloscope can transmit measured and computed data, panel setting data, the status byte, and error codes when they occur.

Ethernet/VXI-11 Interface Specifications:

The Ethernet interface also includes a user authentication feature, requiring a user name and password for access.

The following tables show approximate waveform data response times. The test was conducted using a PC (Pentium 4 3.4-GHz) with Windows XP Professional SP1, a Corega FEther PCI-TXL network adapter, and Visual C++ programming language.

Ethernet Interface (Analog Signals):

VXI-11 Ethernet Interface (Analog Signals):

Follow this procedure to connect your YOKOGAWA DL6054 to a network:

1. Connect a UTP (Unshielded Twisted-Pair) or STP (Shielded Twisted-Pair) cable to the 100BASE-TX port on the rear panel of the oscilloscope.

2. Connect the other end of the cable to a hub or other network device.

The 100BASE-TX Ethernet port features two LEDs:

• LINK LED: Illuminates when a link is established between the oscilloscope and another device.

• ACT LED: Blinks when packets are being sent and received normally.

Notes about Connections:

• Always connect the YOKOGAWA DL6054 to a PC through a hub using straight cables. Direct connection with a cross cable may not work properly.

• If you use UTP (straight) cables, ensure they are category 5.

To configure the network settings for remote control of your YOKOGAWA DL6054, follow these steps:

1. Press the UTILITY key.

2. Press the Remote Control soft key.

3. Press the Network or Network(VXI-11) soft key to display the network menu.

From this menu, you can configure the following settings:

• User Name and Password: The Ethernet interface has a user authentication feature. Set the user name (up to 30 characters, default is “anonymous”) and password (up to 30 characters). User names and passwords are case-sensitive. Note: If you select VXI-11, the user authentication menu will not appear.

• Timeout Value: Specify a period of time after which the YOKOGAWA DL6054 will disconnect from the controller if it is not accessed.

• TCP/IP: You must specify the IP address, Subnet mask, and Default gateway. For details on how to specify these settings, refer to the User’s Manual (IM DLM6054-01EN).

Note: Only the interface selected under Remote Control is valid. The oscilloscope will not accept commands transmitted to other unselected interfaces.

To connect the YOKOGAWA DL6054 via GP-IB, you will need an NI PCMCIA-GPIB card by National Instruments and the GP-IB cable that comes with it.

Connection Procedure:

Insert the GP-IB card into the PC card slot on the rear panel of the YOKOGAWA DL6054.

Precautions for Making Connections:

• Turn OFF the PC and the YOKOGAWA DL6054 before connecting or disconnecting communication cables to prevent erroneous operation or damage.

• Refer to the GP-IB card’s manual for handling instructions.

• Attach the GP-IB card correctly with the front face up.

• Connect the GP-IB card to the oscilloscope’s PC card slot first, then turn the oscilloscope ON.

• You can connect up to 15 devices (including the controller) on a single bus. Each device must have a unique address.

• Use cables of 2 m or less for connecting devices. The total cable length must not exceed 20 m.

• When communicating, ensure at least two-thirds of the devices are turned ON.

• Connect multiple devices in a star or linear configuration. Do not wire them in a loop or parallel configuration.

GP-IB Interface Functions:

• Listener Capability: All settings available via panel keys (except power and communication parameters) can be set through the GP-IB interface. It receives commands for setup information, waveform data, and status reports.

• Talker Capability: Outputs setup information, waveform data, and other information.

GP-IB Interface Specifications:

Functional specifications:

To set up the GP-IB interface on your YOKOGAWA DL6054, follow these steps:

1. Press the UTILITY key.

2. Press the Remote Control soft key.

3. Press the GPIB soft key to display the menu.

From this menu, you need to set the address:

• Setting the Address: Set the address of the YOKOGAWA DL6054 within the range of 0 to 30. Each device connected via GP-IB must have a unique address to distinguish it from others. When you connect the oscilloscope to a PC, ensure you assign a unique address to the YOKOGAWA DL6054.

Note: Do not change the address while the controller is communicating with the oscilloscope or other devices over the GP-IB.

The YOKOGAWA DL6054 responds to specific GP-IB interface messages (also known as bus commands) issued by the controller. Here is a summary of the responses:

Responses to a Uni-Line Message:

• IFC (Interface Clear): Clears the talker and listener functions. Stops data output if it is in progress.

• REN (Remote Enable): Switches the oscilloscope between the remote and local modes.

Responses to a Multi-Line Message (Address Command):

• GTL (Go To Local): Switches the oscilloscope to the local mode.

• SDC (Selected Device Clear): Clears the program message (command) being received and the output queue. Any *OPC and *OPC? commands in execution are voided. The *WAI and COMMunicate:WAIT commands are immediately terminated.

Responses to a Multi-Line Message (Universal Command):

• LLO (Local Lockout): Disables the SHIFT + CLEAR key combination 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 then polls the devices in order.

• SPD (Serial Poll Disable): Clears the serial polling mode of the talker function on all devices on the bus.

Note: IDY (Identify), PPC (Parallel Poll Configure), GET (Group Execute Trigger), TCT (Take Control), and PPU (Parallel Poll Unconfigure) are not supported.

Messages are used to exchange information between a controller and the YOKOGAWA DL6054. Messages sent from the controller are called program messages, and messages sent back are called response messages.

Program Messages

A program message consists of one or more program message units, separated by semicolons (;). Each unit corresponds to one command. The message ends with a program message terminator (PMT).

• Program Message Unit Format: ` [Space] `

• Program Header: Indicates the command type.

• Program Data: Required data for executing a command, separated from the header by a space. Multiple data sets are separated by commas (,).

• Program Message Terminator (PMT): Three types are available: NL (New Line, ASCII code 0AH), ^EOM (END message as defined by USBTMC), or NL^EOM.

Response Messages

If a program message contains a query (a command ending with “?”), the instrument returns a response message. A single response message is returned for a single program message.

• Response Message Unit Format: `[ Space] `

• Response Header: Sometimes precedes the response data, separated by a space.

• Response Data: Contains the content of the response. Multiple sets of response data are separated by commas (,).

• Response Message Terminator (RMT): A response message terminator, which is NL^EOM.

Note on Deadlock: A deadlock can occur if both transmit and receive buffers become full. To avoid this, keep the program message (including the PMT) below 1024 bytes. Deadlock will not occur if the program message does not contain a query.

Commands (program headers) sent to the YOKOGAWA DL6054 have three different formats:

1. Common Command Header: Defined in USBTMC-USB488, these commands begin with an asterisk (*). Example: `*CLS`

2. Compound Header: Dedicated commands arranged in a hierarchy. A colon (:) is used to specify a lower level. Example: `:ACQuire:MODE`

3. Simple Header: Functionally independent commands with no hierarchy. Example: `:STARt`

When Concatenating Commands (separating with a semicolon “;”):

• Commands of the Same Group: Common header sections can be omitted. Example: `:ACQuire:MODE NORMal;INTERLeave 1`

• Commands of Different Groups: A colon (:) must be placed in front of the header of the new group command. Example: `:ACQuire:MODE NORMal;:DISPlay:FORMat SINGle`

• Concatenating Simple Headers: A colon (:) is required before the simple header. Example: `:ACQuire:MODE NORMal;:STARt`

• Concatenating Common Commands: Common commands are independent of hierarchy and do not need a preceding colon. Example: `:ACQuire:MODE NORMal;*CLS;INTERLeave 1`

Note on Header Interpretation:

• Mnemonics are not case-sensitive (e.g., `CURSor` is the same as `cursor`).

• The lower-case section of a header can be omitted (e.g., `CURSor` can be written as `CURS`).

• A question mark (?) at the end indicates a query and cannot be omitted.

The YOKOGAWA DL6054 uses various data types in its communication commands. The data section follows the header, separated by a space.

Multiplier and Unit Details:

Overlap commands are commands where the execution of the next command may start before the previous one is completed. This can lead to receiving outdated information (e.g., querying a setting immediately after loading a file). To prevent this and ensure commands execute sequentially, you can use the following synchronization methods:

• Using the *WAI Command: The `*WAI` command holds subsequent commands until the current overlap command is completed. Place `*WAI` immediately before the command you want to delay. Example: `:FILE:LOAD:SETup:EXECute “CASE1”;*WAI;:CHANnel1:VDIV?` In this case, the `VDIV?` query will not execute until the file loading is complete.

• Using the COMMunicate:OVERlap command: This command can enable or disable overlap operation for specific command types. You can use it to disable overlap for media access commands, forcing them to execute sequentially.

• Using the *OPC Command: The `*OPC` command sets bit 0 (the OPC bit) of the standard event register to 1 when an overlap operation is completed. You can then poll the service request bit to wait for the operation to finish before sending the next command.

• Using the *OPC? Query: The `*OPC?` query will not generate a response until the overlap operation is completed. By waiting for the response, you ensure the previous command has finished before proceeding. Example: `:FILE:LOAD:SETup:EXECute “CASE1”;*OPC?` (Read response to *OPC?) `:CHANnel1:VDIV?`

Even with sequential commands, synchronization may be needed for non-communication-related events, like waiting for a trigger and waveform acquisition to complete before querying the data. Sending a query too early can result in an error. Use one of the following methods to synchronize:

• Using the STATus:CONDition? Query: This query returns the contents of the condition register. You can poll this register to check the status of an operation. For example, bit 0 indicates if waveforms are being retrieved. You can loop and repeatedly send this query until bit 0 becomes “0”, indicating the acquisition is stopped, before sending the `WAVeform:SEND?` command.

• Using the Extended Event Register: You can configure the instrument to reflect changes in the condition register to the extended event register. Use the `STATus:FILTer` command to set a transition filter (e.g., `FALL` to detect when acquisition changes from running to stopped). Then, you can monitor the extended event register or generate a service request when the event occurs, and only then send the next command.

• Using the COMMunicate:WAIT Command: This command halts communications until a specific event is generated. You can configure a transition filter as above, and then use `COMMunicate:WAIT` to pause the program until the specified bit in the extended event register is set to “1”. After the wait, you can proceed with the next command. Example: `:STATus:FILTer1 FALL; :COMMunicate:WAIT 1; :WAVeform:SEND?`

The Status Byte is an 8-bit register that summarizes the status of the YOKOGAWA DL6054. It is read via a `*STB?` query or serial polling.

Status Byte Structure:

• Bits 0, 1, 7: Not used (always 0).

• Bit 2 EAV (Error Available): Set to 1 when the error queue is not empty (i.e., an error has occurred).

• Bit 3 EES (Extend Event Summary Bit): Set to 1 when an event defined by the Extended Event Register has occurred.

• Bit 4 MAV (Message Available): Set to 1 when the output queue is not empty (i.e., there is data to be read).

• Bit 5 ESB (Event Summary Bit): Set to 1 when an event defined by the Standard Event Register has occurred.

• Bit 6 RQS/MSS (Request Service / Master Status Summary): Set to 1 when any other enabled bit (2 through 5) in the status byte becomes 1, indicating a service request.

Operation:

A service request is generated when bit 6 becomes 1. This happens when any of the bits 2-5 are set to 1 AND their corresponding bits in the Service Request Enable Register are also 1. You can read the status byte to determine the cause of the service request. Reading via `*STB?` reads the MSS bit, while serial polling reads the RQS bit and then clears it.

The Standard Event Register records eight different types of standard events. Its status is summarized by bit 5 (ESB) of the Status Byte.

Standard Event Register Structure:

Operation:

When any of these bits are set to 1, if the corresponding bit in the Standard Event Enable Register is also 1, then bit 5 (ESB) of the Status Byte is set to 1. You can enable or disable these bits using the `*ESE` command.

Reading and Clearing:

The register can be read using the `*ESR?` query. Reading the register also clears it. It is also cleared by a `*CLS` command or when the instrument is power cycled.

Output Queue

The output queue stores response messages to queries. For example, when you send a `WAVeform:SEND?` command, the requested data is placed in the output queue to be read by the controller. Data is stored and read in a first-in, first-out order.

The output queue is emptied in the following situations:

• When a new message is received from the controller.

• When a deadlock occurs.

• When a device clear command (DCL or SDC) is received.

• When the instrument is power cycled.

To check if the output queue is empty, you can check bit 4 (MAV) of the status byte.

Error Queue

The error queue stores the error number and message when an error occurs. For example, if an incorrect program message is sent, “113, “Undefined header”” is stored. You can use the `STATus:ERRor?` query to read the contents of the error queue, which are read from oldest to newest.

If the error queue overflows, the last message is replaced by “350, “Queue overflow”.”

The error queue is cleared in the following situations:

• When a `*CLS` command is received.

• When the instrument is power cycled.

To check if the error queue is empty, you can check bit 2 (EAV) of the status byte.

The YOKOGAWA DL6054 uses a range of error codes to indicate issues with communication commands. The primary ranges are:

• 100-199: Communication syntax error

• 200-299: Communication execution error

• 400-499: Communication query error

Error in Communication Command (100-199)

Error in Communication Execution (200-299)

Error in Communication Query (400-499)

The names of waveform parameters displayed on the setup menu of the YOKOGAWA DL6054 correspond to specific names used in communication commands. This table provides the correlation:

The names of eye pattern parameters displayed on the setup menu of the YOKOGAWA DL6054 correspond to specific names used in communication commands. This table provides the correlation: