A newly created EEZ project contains only the basic items in the Settings tab as shown on Fig. 1. organized into General and Build sections.


Fig. 1: Settings tab for the newly created project

The General sections is used to define SCPI documentation folder path that will be using during SCPI help HTML files import and update. Please be sure that newly created project is saved first, before this option is used. The recommended path to the SCPI help HTML files is doc subfolder in the folder where project file has been saved.

Additionally, we can found here all ESP's currently available Project features. For making an IEXT the following three items has to be added:

  • ESW extension definitions
  • SCPI and
  • Shortcuts

Each of the above mentioned items will add its own tab that follows the Settings tab icon as shown on the Fig. 2.


Fig. 2: Additional tabs for selected Project features

The Build section contains Destination folder path where IEXTs will be created. The project file folder is defined by default (hence single dot) as shown on Fig. 3.


Fig. 3: Build destination folder

The Build sections also contains Configurations and Files subsections while Files is still not used for building an IEXT. Configurations sections for a newly created project include only Default configuration which can be renamed is necessary. The Configurations is used to define parameters that is shared between more instruments within the same family, for example, the rigol_ds_mso_1000 IEXT in the time of this writing includes four configurations (Fig. 4).


Fig. 4: Multiple Build configurations example

The Configuration items are as follows:



Configuration name that describe e.g. instrument family, or group of instrument models with the same feature within the same family.

For example, the same Rigol DS1000 series instruments exists in two variants with signal generator installed (-S model) or without signal generator. Consequently model with additional feature comes with more SCPI commands. Creating two configurations give us possibility to select what SCPI command set is supported in one or another model even if SCPI commands are located in the same SCPI help file (chapter). The process of how to assign SCPI command help to one or more instruments will be described later in Project file Subsystems chapter.


Additional information about the configuration, e.g. manufacturers promotional text of the instrument family.


Various Instrument configuration parameters. If defined they will override default ESW values.


There is no limitation in number of Build Configurations, and at least on has to be defined. Configuration adding and removing can be accomplished using options shown on the Fig. 5.


Fig. 5: Build configuration Add and Remove options




The certain instrument model/type within a larger family of instruments, that is possible to define as Build configurations and described under Settings section, is defined under Extension definitions tab. A newly created project does not contain any instrument definition. Use Add option to create as many as needed different instruments (Fig. 1.).


Fig. 1: Add new instrument definition


A newly added instrument definition will produce few error caused by automated checking mechanism (Fig. 2). Reported errors pointed to the mandatory fields.


Fig. 2: Empty instrument definition errors

The Extension definitions has the following parameters (mandatory parameters are marked bold) that follows the Instrument definition file (IDF) structure of Keysight's Offline Command Expert command set:



Instrument name, has to be unique.


Instrument specific description that will be displayed together with Build Definition description as specified in Settings section.

Do not build

Exclude instrument from collection that will be made during the IEXT building process.

Build configuration

List of all build configuration defined in Settings section.

Build folder

Destination folder when IEXT will be build. Default value is empty for using the same folder as the project file.

Extension name

Target IEXT .zip file name, for example rigol_mso1104zs is used to create rigol_mso1104zs_xxx.zip where xxx is defined by IDF revision number (see below).


Instrument picture that will be displayed in ESW for easier instrument recognition. If not specified a default “image no selected” icon will be used.


Identification string that contains manufacturer name, followed by model name that is expected at the beginning of the received result from *IDN? Query (e.g. RIGOL TECHNOLOGIES,DS1054Z).


Instrument specific ESW properties, if specified will override Properties defined in the Build configurations described in Settings section (e.g. instrument specific color scheme).

IDF name


IDF short name


IDF firmware version

Instrument firmware version


Instrument's GUID (Globally Unique Identifier). A new value will be generated each time when accompanied “+” option is selected.

IDF revision number (extension version)

Revision number that is used as IEXT .zip file suffix and to distinguish between more IEXT's revision of the same instrument.

IDF description

Instrument information that will be displayed next to instrument name in ESW IEXT list (e.g. 70 MHz Digital Oscilloscope for Rigol Rigol DS1074Z model).

IDF supported models

??? Može li ovo biti lista?

IDF revision comments

Additional revision information (e.g. what's new, etc.)

IDF author

Information about IEXT author (e.g. Envox for EEZ instruments)

SDL friendly name

??? gdje/kada se koristi?


The Subsystems section is used to define SCPI commands (organized in subsystems) searchable help section and SCPI commands and queries syntax used by ESW to assemble a valid SCPI command ready for execution.

Opening a new or existing EEZ Studio project can be done by selecting options from the File menu in ESW or ESP if it is opened. Note that on the EEZ Studio start, the ESW module will be opened by default.


Fig. 1: EEZ Studio New project option

The EEZ Studio project items are organized into the following sections: