Rohde & Schwarz HMF2525 Operating and maintenance manual

¸HMF2525
¸HMF2550
Arbitrary Function Generator
SCPI Programmers Manual
SCPI Programmers Manual
Version 01
*5800571802*
5800571802

SCPI Commands HMF series Remote Control
2
SCPI Programmers Manual
Content
1 Basics.............................................................................................................................................. 3
1.1 Remote Control Interfaces .............................................................................................................. 3
1.1.1 RS-232 Interface ............................................................................................................................. 3
1.1.2 USB Interface.................................................................................................................................. 4
1.1.3 Ethernet (LAN) Interface ................................................................................................................. 4
1.1.4 GPIB Interface (IEC/IEEE Bus Interface).......................................................................................... 5
1.2 Setting Up a Network (LAN) Connection ....................................................................................... 5
1.2.1 Connecting the Instrument to the Network ................................................................................... 5
 1.2.2 ConguringLANParameters .......................................................................................................... 6
1.3 Switching to Remote Control.......................................................................................................... 7
1.4 Messages and Command Structure ............................................................................................... 7
1.4.1 Messages........................................................................................................................................ 7
1.4.2 SCPI Command Structure............................................................................................................... 8
1.5 Command Sequence and Synchronization................................................................................... 11
1.5.1 Preventing Overlapping Execution................................................................................................ 11
2 Command Reference .................................................................................................................... 13
2.1 Common Commands................................................................................................................. 13
2.2 System related commands........................................................................................................ 16
 2.4 CongurationCommands.......................................................................................................... 22
 2.4.1 GeneralOutputCongurations.................................................................................................. 22
 2.4.2 SineWaveConguration............................................................................................................ 24
 2.4.3 SquareWaveConguration....................................................................................................... 27
 2.4.3 RampConguration................................................................................................................... 32
 2.4.4 PulseConguration.................................................................................................................... 37
 2.4.4 ArbitraryConguration............................................................................................................... 42
2.5 Modulation commands.............................................................................................................. 47
2.5.1 AM Modulation.......................................................................................................................... 47
2.5.2 FM Modulation........................................................................................................................... 50
2.5.3 PM Modulation.......................................................................................................................... 52
2.5.4 FSK Modulation.......................................................................................................................... 55
2.5.5 PWM Modulation....................................................................................................................... 58
2.6 Sweep commands..................................................................................................................... 61
2.7 Burst commands........................................................................................................................ 66
2.8 Trigger commands..................................................................................................................... 68
2.9 Screenshot commands.............................................................................................................. 70
3 SCPI Commands (in alphabetic order).......................................................................................... 72

SCPI Commands HMF series Remote Control
3
Basics
SCPI Programmers Manual
1 Basics
This chapter provides basic information on operating an instrument via remote control.
1.1 Remote Control Interfaces
For remote control, RS-232 / USB (standard interface HO720), Ethernet / USB (optional interface
HO730) or GPIB (optional interface HO740) can be used. The optional interfaces replaces the RS-
232 / USB HO720 interface module on the rear panel.
NOTICE
Within this interface description, the term GPIB is used as a synonym for the IEC/IEEE
bus interface.
SCPI (Standard Commands for Programmable Instruments) SCPI commands - messages - are
used for remote control. Commands that are not taken from the SCPI standard follow the SCPI
syntax rules.
NOTICE
The end character must be set to linefeed (LF) or carriage return + linefeed (CR-LF).
1.1.1 RS-232 Interface
If you use classic RS-232 you do not need any driver. In order to set the interface parameter at
the HMF, please press the button MENU at the front panel and choose the menu item INTER-
FACE. Make sure the RS-232 interface is chosen. The menu item PARAMETER opens a menu
where you can set and save all parameter for the RS-232 communication. Setting of the RS-232
musttthesettingofthecorrespondingPCCOMport.
In general, there are exist two options for the RS-232 communication: with or without interface
handshake. If you are working without handshake you have to integrate appropriate delays
between the commands to make sure that all commands are executed correctly (approx. 50ms
to100ms).Withouthandshakeyoucanhavetheproblemthattheinterfacebuffercanoverow
(e.g. missing commands). If you are working with interface handshake (set on both sides, HMF
and PC) you don‘t need to integrate delays.
In the interface settings of the HMF you can set the interface handshake (button MENU). If you
have a look into the menu item INTERFACE you can choose the menu item HANDSHAKE. There
youcanndtheitemsNONEorCTS/RTS.CTS/RTSmeanstheactivationoftheinterfacehands-
hake. Please note that you choose the same settings in your appropriate software.

SCPI Commands HMF series Remote Control
4
Basics
SCPI Programmers Manual
NOTICE
If you want to use the RS-232 interface we recommend to activate the interface hand-
shake to avoid timing problems.
1.1.2 USB Interface
If you are using USB you need to install a USB driver which is available on the Rohde & Schwarz
Website.
NOTICE
All descriptions regarding the USB interface are true for the HO720 interface card as
well as for the optional HO730 USB part. All currently available USB driver are fully
tested, functional and released for Windows XP™, Windows Vista™, Windows 7™ or
Windows 8™, both as 32Bit or 64Bit versions.
The HMP USB interface has to be chosen in the MENU and does not need any setting.
NOTICE
If the virtual COM port will be used, you have to install the virtual COM port part of
the HO720 / HO730 USB driver. The virtual COM port (VCP) will be activated in the PC
device explorer.
1.1.3 Ethernet (LAN) Interface
The settings of the parameter will be done after selecting the menu item Ethernet. You can set
axIPadressoradynamicIPsettingviatheDHCPfunction.PleaseaskyourITdepartmentfor
the correct setting at your network.
IP address
To set up the connection the IP address of the instrument is required. It is part of the resource
string used by the program to identify and control the instrument. The resource string has the
form:
TCPIP::‹IP_address›::‹IP_port›::INSTR
The default port number for SCPI socket communication is 5025. IP address and port number
are listed In the „Ethernet Settings“ of the HMP series, see also: chapter1.2.2,“ConguringLAN
Parameters“.
Example (HO732): If the instrument has the IP address 192.1.2.3; the valid resource string is
TCPIP0::192.1.2.3::inst0::INSTR

SCPI Commands HMF series Remote Control
5
Basics
SCPI Programmers Manual
If the LAN is supported by a DNS server, the host name can be used instead of the IP address.
The DNS server (Domain Name System server) translates the host name to the IP address. The
resource string has the form:
TCPIP::‹host_name›::‹IP_port›::INSTR
1.1.4 GPIB Interface (IEC/IEEE Bus Interface)
An optional GPIB interface is also available for the HMF series. This solution is particularly attrac-
tive for customers who already have an existing GPIB environment. With minimum efforts, an
old instrument can be replaced by a model of the HMF series.
To be able to control the instrument via the GPIB bus, the instrument and the controller must be
linked by a GPIB bus cable. A GPIB bus card, the card drivers and the program libraries for the
programming language must be provided by the controller. The controller addresses the instru-
ment with the GPIB instrument address.
Characteristics
The GPIB interface is described by the following characteristics:
• Up to 15 instruments can be connected
• The total cable length is restricted to a maximum of 15m; the cable length between two
instruments should not exceed 2m.
• A wired „OR“-connection is used if several instruments are connected in parallel.
GPIB Instrument Address
In order to operate the instrument via remote control, it must be addressed using the GPIB
address. The remote control address is factory-set to 20, but it can be changed in the network
environment settings or in the HMF MENU under INTERFACE -> PARAMETER. For remote
control, a GPIB address from 0 to 30 are allowed. The GPIB address is maintained after a reset of
the instrument settings.
1.2 Setting Up a Network (LAN) Connection
1.2.1 Connecting the Instrument to the Network
NOTICE
Risk of network failure
Before connecting the instrument to the network or conguring the network, consult
your network administrator. Errors may affect the entire network.
The network card can be operated with a 10 Mbps Ethernet IEEE 802.3 or a 100 Mbps Ethernet
IEEE 802.3u interface.

SCPI Commands HMF series Remote Control
6
Basics
SCPI Programmers Manual
NOTICE
To establish a network connection, connect a commercial RJ-45 cable to one of the
LAN ports of the instrument and to a PC.
1.2.2 Conguring LAN Parameters
Depending on the network capacities, the TCP/IP address information for the instrument can be
obtained in different ways.
• IfthenetworksupportsdynamicTCP/IPcongurationusingtheDynamicHostConguration
Protocol (DHCP), and a DHCP server is available, all address information can be assigned
automatically.
• Otherwise, the address must be set manually. Automatic Private IP Addressing (APIPA) is not
supported.
Bydefault,theinstrumentisconguredtousedynamicTCP/IPcongurationandobtainall
address information automatically. This means that it is safe to establish a physical connection to
theLANwithoutanypreviousinstrumentconguration.
NOTICE
Risk of network errors
Connection errors can affect the entire network. If your network does not support
DHCP, or if you choose to disable dynamic TCP/IP conguration, you must assign valid
address information before connecting the instrument to the LAN. Contact your net-
work administrator to obtain a valid IP address.
Conguring LAN parameters
• Press the MENU key and choose INTERFACE.
• Press the knob, choose ETHERNET (SELECT INTERFACE) and PARAMETER.
• DenetheIPandportsettingsoftheinstrument.
• Select the IP Port - the port number for SCPI socket communication.
NOTICE
By default the instrument is not set to DHCP. If the instrument is set to DHCP and can-
not nd a DHCP server, it takes about two minutes until the Ethernet menu is available.
Checking LAN and SCPI connection
• Check the LAN connection using ping: ping xxx.yyy.zzz.xxx.
• If the PC can access the instrument, enter the IP address into your PC internet browser:
http//:xxx.yyy.zzz.xxx
The „Instrument Home“ page appears. It provides information of the instrument and the LAN
connection.

SCPI Commands HMF series Remote Control
7
Basics
SCPI Programmers Manual
1.3 Switching to Remote Control
When you switch on the instrument, it is always in manual operation state („local“ state) and can
be operated via the front panel. When you send a command via PC, it will be received and exe-
cuted by the instrument. The display remains on, manual operation via the front panel is always
possible.
1.4 Messages and Command Structure
1.4.1 Messages
Instrument messages are employed in the same way for all interfaces, if not indicated otherwise
in the description.
See also:
• Structure and syntax of the instrument messages: chapter 1.4.2, „SCPI Command Structure“.
• Detailed description of all messages: chapter 2, „Command Reference“.
There are different types of instrument messages:
• Commands
• Instrument responses
Commands
Commands (program messages) are messages which the controller sends to the instrument.
They operate the instrument functions and request information. The commands are subdivided
according to two criteria:
According to the instrument effect:
• Setting commands cause instrument settings such as a reset of the instrument or setting the
frequency.
• Queriescausedatatobeprovidedforremotecontrol,e.g.foridenticationoftheinstrument
or polling a parameter value. Queries are formed by appending a question mark to the com-
mand header.
According to their denition in standards:
• ThefunctionandsyntaxoftheCommoncommandsarepreciselydenedinstandardIEEE
488.2. They are employed identically on all instruments (if implemented). They refer to func-
tions such as management of the standardized status registers, reset and self test.
• Instrument control commands refer to functions depending on the features of the instrument
such as voltage settings. Many of these commands have also been standardized by the SCPI
committee. These commands are marked as „SCPI compliant“ in the command reference
chapters.CommandswithoutthisSCPIlabelaredevice-specic,however,theirsyntaxfollows
SCPI rules as permitted by the standard.
Instrument responses
Instrument responses (response messages and service requests) are messages which the instru-
ment is sent to the controller after a query. They can contain measurement results, instrument
settings and information on the instrument status.

SCPI Commands HMF series Remote Control
8
Basics
SCPI Programmers Manual
GPIB Interface Messages
Interface messages are transmitted to the instrument on the data lines with the attention line
(ATN) being active (LOW). They are used for communication between the controller and the
instrument and can only be sent by a PC which has the function of a GPIB bus controller. GPIB
interface messages can be further subdivided into:
• Universal commands: act on all instruments connected to the GPIB bus without previous
addressing; universal commands are encoded in the range 10 through 1F hex. They affect all
instruments connected to the bus and do not require addressing.
• Addressed commands: only act on instruments previously addressed as listeners;
addressed commands are encoded in the range 00 through 0F hex. They only affect instru-
ments addressed as listeners.
1.4.2 SCPI Command Structure
SCPI commands consist of a so-called header and, in most cases, one or more parameters. The
header and the parameters are separated by a „white space“. The headers may consist of several
mnemonics (keywords). Queries are formed by appending a question mark directly to the hea-
der.Thecommandscanbeeitherdevice-specicordevice-independent(commoncommands).
Commonanddevice-speciccommandsdifferintheirsyntax.
Syntax for Common Commands
Common (= device-independent) commands consist of a header preceded by an asterisk (*) and
possibly one or more parameters.
Examples:
*RST Reset Resets the instrument.
*ESE Event Status Enable Sets the bits of the event status enable registers.
*ESR? Event Status Query Queries the content of the event status register.
*IDN? IdenticationQuery Queriestheinstrumentidenticationstring.
Table 1.4: Examples of Common Commands
Long and short form
The mnemonics feature a long form and a short form. The short form is marked by upper case
letters, the long form corresponds to the complete word. Either the short form or the long form
can be entered; other abbreviations are not permitted.
Example: VOLTage:OFFSet? is equivalent to VOLT:OFF?

SCPI Commands HMF series Remote Control
9
Basics
SCPI Programmers Manual
NOTICE
Case-insensitivity
Upper case and lower case notation only serves to distinguish the two forms in the
manual, the instrument itself is case-insensitive.
Special characters
|
Parameters
Averticalstrokeinparameterdenitionsindicatesalternativepossibilitiesinthe
sense of „or“. The effect of the command differs, depending on the used parameter.
Example:
FUNCtion {SINusoid | SQUare | RAMP | PULSe | ARBitrary}
FUNC SIN sets the sine wave function.
FUNC SQU sets the square wave function.
{ }
Parameters in curly brackets are optional and can be inserted once or several times,
or omitted.
Example:
PERiod {<Period in sec> | MINimum | MAXimum}
The following are valid commands:
PER MIN
PER MAX
Table 1.5: Special characters
SCPI Parameters
Many commands are supplemented by a parameter or a list of parameters. The parameters
must be separated from the header by a „white space“ (ASCII code 0 to 9, 11 to 32 decimal, e.g.
blank). Allowed parameters are:
• Numeric values
• Special numeric values
• Boolean parameters
• Text
• Character strings
• Block data
Therequiredparametersandtheallowedvaluerangearespeciedinthecommanddescription.
Numeric values
Numeric values can be entered in the following form. Values exceeding the resolution of the
instrument are rounded up or down.
Example:
VOLT 5V = VOLT 5
VOLT 800mV = VOLT 0.8

SCPI Commands HMF series Remote Control
10
Basics
SCPI Programmers Manual
Special numeric values
The text listed below are interpreted as special numeric values. In the case of a query, the nume-
ric value is provided.
• MIN/MAX
• MINimum and MAXimum denote the minimum and maximum value.
Example:
VOLT MAX
VOLT MAX?, Response: 2.00000E+01
Queries for special numeric values
The numeric values associated to MAXimum/MINimum can be queried by adding the correspon-
ding mnemonics to the command. They must be entered following the quotation mark.
Example:
VOLT? MAX
Returns the maximum numeric value.
Boolean parameters
Boolean parameters represent two states. The „ON“ state (logically true) is represented by „ON“
or a numeric value 1. The „OFF“ state (logically untrue) is represented by „OFF“ or the numeric
value 0. The numeric values are provided as the response for a query.
Example:
OUTPut ON
OUTPut?, Response: ON
Overview of Syntax Elements
The following table provides an overview of the syntax elements:
:The colon separates the mnemonics of a command.
,The comma separates several parameters of a command.
?The question mark forms a query.
*The asterisk marks a common command.
“Quotation marks introduce a string and terminate it.
A „white space“ (ASCII-Code 0 to 9, 11 to 32 decimal, e.g. blank) separates the
header from the parameters.
Table 1.6: Syntax Elements
Responses to Queries
Aqueryisdenedforeachsettingcommand.Itisformedbyaddingaquestionmarktothe
associated setting command. According to SCPI, the responses to queries are partly subject to
stricter rules than in standard IEEE 488.2.

SCPI Commands HMF series Remote Control
11
Basics
SCPI Programmers Manual
• The requested parameter is transmitted without a header.
Example:
VOLTage:UNIT VOLT
VOLTage:UNIT?, Response: VOLT
1.5 Command Sequence and Synchronization
Asequentialcommandnishestheexecutionbeforethenextcommandisstarting.Inorderto
make sure that commands are actually carried out in a certain order, each command must be
sent in a separate command line.
NOTICE
As a general rule, send commands and queries in different program messages.
1.5.1 Preventing Overlapping Execution
Command Action Programming the controller
*OPC
Sets the Operation Complete bit in
the ESR after all previous commands
have been executed.
• Setting bit 0 in the ESE
• Setting bit 5 in the SRE
• Waiting for service request (SRQ)
*OPC?
Stops command processing until
1 is returned. This is only the case
after the Operation Complete bit has
been set in the ESR. This bit indi-
cates that the previous setting has
been completed.
Sending *OPC? directly after the
command whose processing should be
terminated before other commands can
be executed.
*WAI
Stops further command processing
until all commands have been exe-
cuted before *WAI.
Sending *WAI directly after the com-
mand whose processing should be
terminated before other commands are
executed
Table 1.7: Synchronization using *OPC, *OPC? and *WAI
To prevent an overlapping execution of commands the commands *OPC, *OPC? or *WAI can be
used. All three commands cause a certain action only to be carried out after the hardware has
been set. The controller can be forced to wait for the corresponding action.
NOTICE
The HMF series does not support parallel processing of remote commands. If OPC?
returns a „1“, the device is able to process new commands.

SCPI Commands HMF series Remote Control
12
Basics
SCPI Programmers Manual
1.6 Contents of the Status Registers
The SCPI standard contains an event handling system for all available interfaces that can be used
to be informed about the processes within the oscilloscope. According to the standard the oscil-
loscope replies only after receiving a query but the event handling enables the device to inform
the user that an extraordinary event took place.
Event Status Register (ESR) and Event Status Enable Register (ESE)
TheESRisdenedinIEEE488.2.Theeventstatusregistercanbereadoutusingcommand
*ESR?. If a bit is set in the ESE and the associated bit in the ESR changes from 0 to 1, the ESB
bit in the STB is set. The ESE register can be set using the command *ESE and read using the
command *ESE?.
Status Byte (STB) and Service Request Enable Register (SRE)
TheSTatusByte(STB)isalreadydenedinIEEE488.2.Itprovidesaroughoverviewofthe
instrument status by collecting the pieces of information of the lower registers. A special feature
is that bit 6 acts as the sum bit of the remaining bits of the status byte. The STB is read using the
command *STB or a serial poll.
The STatus Byte (STB) is linked to the Service Request Enable (SRE) register. Each bit of the STB
is assigned a bit in the SRE. Bit 6 of the SRE is ignored. If a bit is set in the SRE and the associa-
ted bit in the STB changes from 0 to 1, a service request (SRQ) is generated. The SRE can be set
using the command *SRE and read using the command *SRE?.
TheSRERdeneswhichinterfacesmayaskforpermissiontotransmit.TheGPIBinterfaceisthe
only one which has a hardware connection to the user for the transmission request (RQS bit);
the status of this line will tell whether an event happened.
All other interfaces (RS-232, USB, Ethernet) do not support this. If the user want to use the event
handling feature, he will have to read the status, e.g. by polling, from the instrument in every
case. Eventually, the status byte SBR will yield the desired information.
Error Queue
Each error state in the instrument leads to an entry in the error queue. The entries of the error
queue are detailed plain text error messages that can be looked up in the error log or queried via
remote control using SYSTem:ERRor[:NEXT]?. Each call of SYSTem:ERRor[:NEXT]? provides one
entry from the error queue. If no error messages are stored, the instrument responds with 0, „No
error“.
For further description of the error queue and the device error codes, please refer to chapter 2.

SCPI Commands HMF series Remote Control
13
Command Reference
SCPI Programmers Manual
2 Command Reference
This chapter provides the description of all remote commands available for HMC8012. The
commands are sorted according to the menu structure of the instrument. A list of commands in
alphabetical order ist given in the „List of Commands“ at the end of this documentation.
2.1 Common Commands
Common commands are described in the IEEE 488.2 (IEC 625-2) standard. These commands
have the same effect and are employed in the same way on different devices.The headers of
these commands consist of ” * “ followed by three letters. Many common commands are related
to the Status Reporting System.
Available common commands:
*CLS ........................................................................................................................................... 13
*ESE <Value> ............................................................................................................................. 13
*ESR? ......................................................................................................................................... 14
*IDN? .......................................................................................................................................... 14
*OPC ........................................................................................................................................... 14
*RST ........................................................................................................................................... 14
*SRE <Contents> ....................................................................................................................... 15
*STB? ......................................................................................................................................... 15
*WAI ........................................................................................................................................... 15
*CLS 
CLear Status
Sets the status byte (STB), the standard event register (ESR) and the EVENt part of the QUE-
Stionable to zero. The command does not alter the mask and transition parts of the registers. It
clears the output buffer.
Usage: Setting only
*ESE <Value>
Event Status Enable
Setstheeventstatusenableregistertothespeciedvalue.Thequery*ESE?returnsthecontents
of the event status enable register in decimal form.
Parameters:
<Value> Range: 0 to 255

SCPI Commands HMF series Remote Control
14
Command Reference
SCPI Programmers Manual
*ESR?
Event Status Read
Returns the contents of the event status register in decimal form and subsequently sets the
register to zero.
Return values:
<Contents> Range: 0 to 255
Usage: Query only
*IDN?
IDeNtication
Returnstheinstrumentidenticationstring.
Return values:
<ID>  HAMEG,‹devicetype›,‹serialnumber›,‹rmwareversion›
Example: HAMEG,HMF2550,011299686,HW90000000,SW02.300
Usage: Query only
*OPC
OPeration Complete
Sets bit 0 in the event status register when all preceding commands have been executed. This
bit can be used to initiate a service request. The query *OPC? writes a „1“ into the output buffer
as soon as all preceding commands have been executed. This is used for command synchroniza-
tion.
NOTICE
The HMF series does not support parallel processing of remote commands. If OPC?
returns a „1“, the device is able to process new commands.
*RST
ReSeT
Setstheinstrumenttoadeneddefaultstatus.Thedefaultsettingsareindicatedinthedescrip-
tion of commands.
Usage: Setting only

SCPI Commands HMF series Remote Control
15
Command Reference
SCPI Programmers Manual
NOTICE
We recommend to start a program by *RST in order to set the instrument to a dened
status prior to starting a program.
*SRE <Contents>
Service Request Enable
Sets the service request enable register to the indicated value. This command determines under
which conditions a service request is triggered. The query *SRE? returns a decimal value of the
service request enable register which corresponds to the binary-weighted sum of all bits.
Parameters:
<Contents> Contents of the service request enable register in decimal form.
Bit 6 (MSS mask bit) is always 0.
Range: 0 to 255
NOTICE
The SRE is an enable register. Consequently, there are no denotations about the bits.
This register conduce for the „OR“ combination of the bits in the status byte.
*STB?
STatus Byte query
Returns the contents of the status byte in decimal form.
Usage: Query only
*WAI
WAIt to continue
Prevents servicing of the subsequent commands until all preceding commands have been exe-
cuted.
Usage: Event

SCPI Commands HMF series Remote Control
16
Command Reference
SCPI Programmers Manual
2.2 System related commands
SYSTem:NAME .......................................................................................................................... 16
SYSTem:NAME? ......................................................................................................................... 16
SYSTem:DATE <Year>,<Month>,<Day> ................................................................................... 16
SYSTem:DATE? .......................................................................................................................... 17
SYSTem:TIME <Hour>,<Minute>,<Second> ............................................................................ 17
SYSTem:TIME? ........................................................................................................................... 17
SYSTem:HARDware? ................................................................................................................. 17
SYSTem:SOFTware? ................................................................................................................... 17
SYSTem:SNUM? ....................................................................................................................... 18
SYSTem:TREE? ........................................................................................................................... 18
SYSTem:ELISt? ........................................................................................................................... 18
SYSTem:ERRor[:NEXT]? ............................................................................................................. 18
SYSTem:ERRor:ALL? <Error> .................................................................................................... 18
SYSTem:BEEPer:ERRor {ON | OFF | 0 | 1} .................................................................................. 19
SYSTem:BEEPer:ERRor? ............................................................................................................ 19
SYSTem:BEEPer:CONTrol {ON | OFF | 0 | 1} .............................................................................. 19
SYSTem:BEEPer:CONTrol? ......................................................................................................... 19
SYSTem:REFerence <Reference> .............................................................................................. 19
SYSTem:REFerence? .................................................................................................................. 20
SYSTem:NAME 
Denesaninstrumentname.
Parameters:
<Name> String with max. 20 characters
Example: SYST:NAME “MyHMF“
SYSTem:NAME? 
Queriesthedenedinstrumentname.
Return values: String with max. 20 characters
SYSTem:DATE <Year>,<Month>,<Day> 
Speciestheinternaldatefortheinstrument.
Parameters:
<Year> Default unit: a
<Month> Range: 1 to 12
<Day> Range: 1 to 31
Default unit: d

SCPI Commands HMF series Remote Control
17
Command Reference
SCPI Programmers Manual
Example: SYSTem:DATE 2014,10,1
Sets the device date to october 1st in the year 2014
SYSTem:DATE?
Returns 2014,10,1
Usage:  SCPIconrmed
SYSTem:DATE? 
Queries the system date.
Return values: e.g. 2015,9,3
SYSTem:TIME <Hour>,<Minute>,<Second> 
Speciestheinternaltimefortheinstrument.
Parameters:
<Hour> Range: 0 to 23
Default unit: h
<Minute> Range: 0 to 59
Default unit: min
<Second> Range: 0 to 59
Default unit: s
Example: SYSTem:TIME 12,15,0
Sets the time to quarter past twelve.
SYSTem:TIME?
Returns 12,15,0
Usage:  SCPIconrmed
SYSTem:TIME? 
Queries the instrument time.
Return values: e.g. 14,46,45
SYSTem:HARDware? 
Queries the hardware-ID of the instrument.
Usage: Query only
SYSTem:SOFTware? 
Queries the software revision oft he instrument.
Usage: Query only

SCPI Commands HMF series Remote Control
18
Command Reference
SCPI Programmers Manual
SYSTem:SNUM? 
Queries the serial number of the instrument.
Usage: Query only
SYSTem:TREE? 
Returns a list of implemented remote commands.
Usage: Query only
SYSTem:ELISt? 
Queries the error list.
Usage: Query only
SYSTem:ERRor[:NEXT]?
Queries an error and removes it from the queue. Positive error numbers are instrument-
dependent. Negative error numbers are reserved by the SCPI standard. If the queue is empty the
response is 0, “No error“.
Return values:
<error> 0, “No error“
-100, “Command error“
-102, “Syntax error“
-109, “Missing parameter
-200, “Execution error“
-350,“Queueoverow“
Usage: Query only
SYSTem:ERRor:ALL? <Error> 
Queries the error/event queue for all unread items and removes them from the queue.
The response is a comma separated list of error number and a short description of the error in
FIFO order. Positive error numbers are instrument-dependent. Negative error numbers are
reserved by the SCPI standard.
Return values:
<Error> List of: Error/event_number,“Error/event_description>[;Devicedependent info]“
If the queue is empty, the response is 0,“No error”
Usage: Query only
  SCPIconrmed

SCPI Commands HMF series Remote Control
19
Command Reference
SCPI Programmers Manual
SYSTem:BEEPer:ERRor {ON | OFF | 0 | 1} 
Activates or deactivates the error beeper function.
Parameters: ON | 1: Error beeper function will be activated
OFF | 0: Error beeper function will be deactivated
*RST: ON | 1
SYSTem:BEEPer:ERRor? 
Queries the state of the error beeper function.
Return values: ON: Error beeper function will be activated
OFF: Error beeper function will be deactivated
SYSTem:BEEPer:CONTrol {ON | OFF | 0 | 1} 
Activates or deactivates the control beeper function.
Parameters: ON | 1: Control beeper function will be activated
OFF | 0: Control beeper function will be deactivated
*RST: ON | 1
SYSTem:BEEPer:CONTrol? 
Queries the state of the control beeper function.
Return values: ON: Control beeper function will be activated
OFF: Control beeper function will be deactivated
SYSTem:REFerence <Reference> 
Sets the system reference clock (10MHz) to internal or external source.
Parameters:
<Reference> IMMediate | EXTernal
IMMediate
Selects the internal 10MHz reference frequency.
EXTernal
Selects the external reference frequency. The external 10MHz reference
   frequencysignalmustcomplywiththespecicationsgivenwith
respect to frequency accuracy and amplitude.
*RST: IMM

SCPI Commands HMF series Remote Control
20
Command Reference
SCPI Programmers Manual
SYSTem:REFerence? 
Queries the type of the system reference.
Return values: IMM | EXT
2.3 Basic Display Settings 
DISPlay:TRACe {OFF | ON | 0 | 1} ............................................................................................... 20
DISPlay:TRACe? ......................................................................................................................... 20
DISPlay:TRACe:INTensity {<Value in percent> | MINimum | MAXimum} ................................. 20
DISPlay:TRACe:INTensity? ......................................................................................................... 21
DISPlay:GRID {<Value in percent> | MINimum | MAXimum} .................................................... 21
DISPlay:GRID? ............................................................................................................................ 21
DISPlay:TRANsparancy {<Value in percent> | MINimum | MAXimum} .................................... 21
DISPlay:TRANsparancy? [MINimum | MAXimum] ..................................................................... 21
LED:BRIGhtness {HIGH | LOW} ................................................................................................. 21
LED:BRIGhtness? ....................................................................................................................... 21
DISPlay:TRACe {OFF | ON | 0 | 1} 
Activates or deactivates the trace display.
Parameters: ON | 1: Trace display will be activated.
OFF | 0: Trace display will be deactivated
*RST: ON | 1
DISPlay:TRACe? 
Queries the state of the trace display.
Return values: ON | OFF
ON: Trace display is activated.
OFF: Trace display is deactivated.
DISPlay:TRACe:INTensity {<Value in percent> | MINimum | MAXimum} 
Denesthetraceintensityinthediagram.*RSTdoesnotchangetheintensity.
Parameters:
<Value in percent> Range: 0 to 100
MIN: 0
MAX: 100