How it Works
Rohde&Schwarz
Loading...
GTSL
User Manual
241 pgs3.52 Mb0
Table of contents
Loading...

Rohde&Schwarz GTSL User Manual

Download
Page 1
R&S®GTSL Generic Test Software Library User Manual
1143645042 Version 26
Page 2
This Software Description is valid for the following software versions.
●
R&S®GTSL version 3.00 and higher versions
© 2021 Rohde & Schwarz GmbH & Co. KG Mühldorfstr. 15, 81671 München, Germany Phone: +49 89 41 29 - 0 Email: info@rohde-schwarz.com Internet: www.rohde-schwarz.com Subject to change – data without tolerance limits is not binding.
R&S® is a registered trademark of Rohde & Schwarz GmbH & Co. KG. Trade names are trademarks of the owners.
1143.6450.42 | Version 26 | R&S®GTSL
The following abbreviations are used throughout this manual: R&S®GTSL is abbreviated as R&S GTSL.
Page 3
R&S®GTSL

Contents

Contents
1 General....................................................................................................5
2 Software Installation..............................................................................6
3 Functional Description........................................................................ 14
4 R&S GTSL License Management........................................................18
5 Configuration Files.............................................................................. 22
6 Editing and Running Test Sequences................................................33
7 Test Libraries........................................................................................50
8 Signal Routing....................................................................................104
9 Creation of Test Libraries..................................................................149
10 Creation of Self Test Libraries.......................................................... 200
11 Instrument Soft Panels...................................................................... 221
3User Manual 1143.6450.42 ─ 26
Page 4
R&S®GTSL
Contents
4User Manual 1143.6450.42 ─ 26
Page 5
R&S®GTSL

1 General

The Generic Test Software Library R&S GTSL is a collection of libraries for specific test tasks like measurements, switching and signal generation. An ASCII file contains the relevant configuration data which can be assigned to certain test sequences. So mea­surement parameters can be changed and adjusted easy and quickly with a standard editor.
Any test management software may be used to control the test sequence. This soft­ware combines the individual test sequences to form an executable test program. It also adds all other functions important to the production operation, such as user administration, execution of multiple test sequences in multi-threading or parallel oper­ation, collection and storage of relevant measurement results and report generation.
The individual test cases of the Generic Test Software Library R&S GTSL can also be combined by a C program into an executable test program.
Requirements
●
Knowledge of Microsoft Windows operating systems is needed to operate and work with the Generic Test Software Library R&S GTSL.
●
Knowledge of C-programming is needed to create your own test libraries.
General
5User Manual 1143.6450.42 ─ 26
Page 6
R&S®GTSL
Software Installation
Installation

2 Software Installation

2.1 General

The Generic Test Software Library R&S GTSL can be downloaded from R&S GLORIS server. After extracting the compressed installation file, the whole contents of the installation package can be found in the target directory.
Please read the README.TXT file before starting the installation by executing the SETUP.EXE file.
To install the Generic Test Software Library R&S GTSL under Windows 10 or Windows 7, the user must be logged in as administrator or as a user with administrator rights.
For additional information on the de-installation of previous versions of the Generic Test Software Library R&S GTSL or concerning installation, consult the README.TXT file in the installation package and the chapter “Installation of R&S CompactTSVP and R&S GTSL” of the “R&S System Manual TSVP”.

2.2 Installation

2.2.1 Runtime Setup

Before installing the Generic Test Software Library R&S GTSL the runtime environment of the computer must be setup. The installation package contains setup routines for the initial setup of the runtime environment.
It is not necessary to setup the runtime environment with each R&S GTSL installation or update, but only in the case of an initial setup, or if the version number of one of the components has changed. To get more information about whether the runtime environ­ment has to be updated or not, please refer to the README.TXT file on the installation package.
The directory Runtime Setup on the installation package comprises some subdirec­tories.
Each subdirectory contains a separate installation application. Wherever more informa­tion is helpful for the proper installation of one item, there is also a README.TXT file located in the subdirectory. Please read this file before installing the specific runtime setup item.
6User Manual 1143.6450.42 ─ 26
Page 7
R&S®GTSL

2.2.2 R&S GTSL

Software Installation
Installation
The Generic Test Software Library R&S GTSL is installed on the computer of the TSVP Test System Versatile Platform or on any external computer via an installation routine. Start the installation as follows:
1. Extract the compressed installation zip-file to a directory on the hard disk drive.
2. Start the installation routine by executing the file setup.exe which is located in the directory where the compressed installation zip-file has been extracted to.
3. The following pictures describe the installation process.
● Installation wizard welcome screen
Figure 2-1: Setup Welcome Screen
● Accept the License Agreement
7User Manual 1143.6450.42 ─ 26
Page 8
R&S®GTSL
Software Installation
Installation
Figure 2-2: Setup License Agreement
● Enter a user name and company name
Figure 2-3: Setup Customer Information
● Select the directory, where the R&S GTSL program files are to be installed.
8User Manual 1143.6450.42 ─ 26
Page 9
R&S®GTSL
Software Installation
Installation
Figure 2-4: Setup Choose Destination Location
● Select the directory, where R&S GTSL application data is to be installed.
Figure 2-5: Setup Data Directory
● Select the program features to be installed
9User Manual 1143.6450.42 ─ 26
Page 10
R&S®GTSL
Software Installation
Installation
Figure 2-6: Setup Select Program Components
● Display of the current setup settings
Figure 2-7: Setup Settings
● Display of the Setup Status
10User Manual 1143.6450.42 ─ 26
Page 11
R&S®GTSL
Software Installation
File Structure
Figure 2-8: Setup Status
● Close the installation routine
Figure 2-9: Setup Complete

2.3 File Structure

The test libraries supplied by ROHDE & SCHWARZ are stored in fixed directories at the time of installation. The following directory structure can be found as subdirectories below the R&S GTSL program files directory which was specified during the installation process.
11User Manual 1143.6450.42 ─ 26
Page 12
R&S®GTSL
Software Installation
File Structure
Figure 2-10: File structure program files
Description of installed R&S GTSL program files directories:
Table 2-1: File structure
Directory Contents
GTSL
GTSL\Bin
GTSL\Develop
Libraries
●
Sample
●
Tools
●
GTSL\Documentation
GTSL\EGTSL
GTSL\Firmware Update
GTSL\Include
Generic Test Software Library. The root directory for the R&S GTSL software can have any name.
Contains the test libraries (.DLL, .LIB) and the help files (.HLP, .CHM) belonging to the test libra­ries.
The directory ..\Libraries contains generally valid examples for the creation of a high-level test library and a customer-specific selftest library.
The directory ..\Samples contains two sample applications that show how to call R&S GTSL func­tions and driver functions.
The directory ..\Tools contains the R&S GTSL Selftest application.
Contains the various items of documentation in PDF file format.
Appears only if the feature was selected at installa­tion time. For detailed information please refer to the document 'Software Description EGTSL.pdf'.
This directory contains the firmware update applica­tion with which the firmware of all TSVP Test Sys­tem Versatile Platform plug-in boards can be upda­ted to a newer version when available.
Contains the h-files (include files) needed for the development of new test libraries.
GTSL\Operator Interface
GTSL\Sequences
Contains the run time module for the operator inter­face of TestStand. A TestStand run time licence is required.
Contains the test sequence examples created by ROHDE & SCHWARZ.
The application data is stored in the following directory structure below the R&S GTSL application data directory which was specified during the installation process.
12User Manual 1143.6450.42 ─ 26
Page 13
R&S®GTSL
Software Installation
File Structure
Figure 2-11: File structure application data
Description of installed R&S GTSL application data files directories.
Table 2-2: Application data files directories
Directory Contents
GTSL\Configuration
GTSL\EGTSL
GTSL\IC-Check
GTSL\License
Contains samples of the two configuration files PHYSICAL.INI and APPLICATION.INI.
Appears only if the feature was selected at installa­tion time. Contains correction data for Enhanced Generic Test Software Library.
For detailed information, please refer to the docu­ment Software Description EGTSL.pdf.
Contains example configuration data for the IC­Check application.
Contains one or more subdirectories with optional license key files.
13User Manual 1143.6450.42 ─ 26
Page 14
R&S®GTSL
Functional Description

3 Functional Description

Figure 3-1: R&S GTSL layer model
In terms of its structure, the Generic Test Software Library R&S GTSL developed by ROHDE & SCHWARZ is divided into different supply components and software layers.
A distinction is made between the software components supplied by ROHDE & SCHWARZ and the components which must be supplied or adapted by the customer. The software components to be provided by the customer may for example include the following elements (specific to the customer and to the unit under test).
●
device drivers
●
calibration data
●
test libraries
●
test sequences
The software used in the R&S GTSL is divided into three different layers.
●
The lowest level of the R&S GTSL accommodates the device drivers needed for the hardware used (Device Driver Layer). These include the device drivers for the following hardware:
– hardware developed and used by ROHDE & SCHWARZ.
– standard hardware.
●
The middle level of the R&S GTSL accommodates the different test libraries (Library Layer). These test libraries provide the functions needed to execute test sequences. At this level, further information concerning the two files PHYSICAL.INI and APPLICATION.INI is transferred to the Resource Manager Library. The different device drivers of the lowest level are called from this level.
●
The highest level accommodates the test sequences for the execution of the indi­vidual test functions (Application Layer). The test sequences call functions from the libraries in the middle level.
14User Manual 1143.6450.42 ─ 26
Page 15
R&S®GTSL
Functional Description
Figure 3-2: Software structure
The test libraries form the core of the software and of the test sequences. The test functions stored in the test libraries (Dynamic Link Library .DLL) are combined within a test sequencer into executable test sequences.
The individual test functions access the test system hardware via the device drivers.
The hardware initialized in the Generic Test Software Library is managed by the Resource Manager. The Resource Manager is likewise a .DLL file.
Thanks to the hardware management of the Resource Manager, the created test sequences are independent of the current hardware configuration, so test sequences do not need to be modified if the hardware or hardware settings are changed. All infor­mation needed to run the test sequences is sent to the Resource Manager via two con­figuration files (.INI files):
PHYSICAL.INI
●
APPLICATION.INI
●
Only these files need to be modified if the hardware or hardware settings are changed. They can be edited with any text editor.
The Resource Manager also manages the hardware during the parallel execution of test sequences. The Resource Manager prevents conflicts in accessing different test functions or test sequences on the same hardware.
When using the Generic Test Software Library R&S GTSL, the user only has to make changes to certain components of the software. In all cases, the user creates the test sequences for the test applications at the highest level (Application Layer).
The user has to adapt the configuration file APPLICATION.INI to the relevant test application. The user only has to adapt the configuration file PHYSICAL.INI in the event of a change to the hardware configuration.
15User Manual 1143.6450.42 ─ 26
Page 16
R&S®GTSL
Functional Description
Operation of a Test Sequence
Since an APPLICATION.INI configuration file normally exists for every test applica­tion performed on the system, the file name can be matched to the test application in question, e.g. APP_XXX.INI. The Resource Manager is told during setup which con­figuration file is to be used.
On the other hand, only one PHYSICAL.INI configuration file is ever available on the system.
For ease of comprehension, the file names APPLICATION.INI and PHYSICAL.INI are used for the configuration files in the manual.

3.1 Operation of a Test Sequence

Figure 3-3: Test sequence operation
16User Manual 1143.6450.42 ─ 26
Page 17
R&S®GTSL
Functional Description
Operation of a Test Sequence
The operation of every created and executed test sequence is divided into three stages:
SETUP
1. First of all, the SETUP function of the Resource Manager (RESMGR) is called. Dur­ing this function call, information from the two configuration files PHYSICAL.INI and APPLICATION.INI is loaded. Then, the SETUP functions of the individual libraries needed to perform the test steps are called (ROUTE, SIGANL, ICT etc.). The necessary hardware and software components are requested, the relevant device drivers are initialized and the devices are placed in a defined state.
MAIN
2. The individual test steps are performed.
CLEANUP
3. The CLEANUP functions of the Resource Manager and of the used libraries are called. The system resources reserved during the setup functions and the reserved hardware are freed again. A CLEANUP call is needed for every SETUP call. The different CLEANUP function calls are executed even if the operation of the test steps is interrupted. This ensures that the used system resources are always freed again, and the used hardware is always returned to a defined basic state.
The division of the execution operation of a test sequence into these three subareas takes place in the test sequence control system that is used.
17User Manual 1143.6450.42 ─ 26
Page 18
R&S®GTSL
R&S GTSL License Management

4 R&S GTSL License Management

Starting with GTSL 3.30, no GTSL license is required.
During the installation of the Generic Test Software Library R&S GTSL, all available test libraries are copied to the system. You need a License Key File in order to access the functions from the test libraries. Refer to Chapter 7, "Test Libraries", on page 50 for the license key required for each test library.
Without a valid License Key File, the functions of the test library will only work in „demo mode". Access to the hardware is only simulated.
Each license is bound to a system serial number. The enabled test libraries can only be run on the system with this serial number. The hardware system used is identified via the system module TS-PSYS (R&S CompactTSVP, R&S PowerTSVP).
Figure 4-1: License Check
During license checking, the serial number and the name of the called test library are compared with the License Key from the License Key File. The test library in question will only be enabled if these coincide. The serial number and the name of the test library are encoded in the License Key.
18User Manual 1143.6450.42 ─ 26
Page 19
R&S®GTSL
R&S GTSL License Management
Example:
License Key File
[Header]
FileVer=1.0
[Project]
Info=GTSL
[Modul]
Product=TS-LBAS
SerialNumber=850000008E4BD202
Key=C146648E1DEF9AD78663728A5D8E8D25885F457367D7F7C359F2C63BDB926 ...
The serial number is queried and a new License Key File is installed via the R&S GTSL License Viewer. To open the R&S GTSL License Viewer, select
" Start" -> "Programs" -> "GTSL" -> "License Viewer"
Figure 4-2: R&S License Viewer
"System Identification" The serial number of the system
"Program Status" Displays the current status of theR&S GTSL License
Viewer.
"Licensed Components" Displays the test libraries for which a License Key
File has been imported.
Copies the displayed serial number to the clipboard.
19User Manual 1143.6450.42 ─ 26
Page 20
R&S®GTSL
R&S GTSL License Management
Imports a new License Key File into the R&S GTSL License Viewer. The path and the file name of the License Key File to be imported can be selected via a file browser dialog.
Reads the serial number into theR&S GTSL License Viewer.
Closes the R&S GTSL License Viewer.
"File > Exit" Closes the R&S GTSL License Viewer.
"Configure > System Identification" Opens the configuration dialog (see Figure 4-3).
"Help > About License Viewer" Shows version and copyright information about the
R&S GTSL License Viewer.
Figure 4-3: Configuration Dialog
"iButton" This option is not available for Windows 7.
"PSYS" "CAN Board" and "Controller" define the board and
interface Id of the CAN interface controlling the R&S TS-PSYS module.
Default = 0
"Frame" defines the R&S CompactTSVP or R&S PowerTSVP frame number where the R&S TS­PSYS module is located.
Default = 1
"Slot": The only valid slot number for the R&S TS­PSYS module is 15.
The settings made in the Configuration Dialog are accepted with the "OK" button.
The settings made in the Configuration Dialog are rejected with the "Cancel" button.
For each installed PSYS, a subdirectory with the relevant serial number is created in the ..\GTSL\License directory. The License Key Files installed via the R&S GTSL License Viewer are stored in the relevant subdirectory.
20User Manual 1143.6450.42 ─ 26
Page 21
R&S®GTSL
R&S GTSL License Management
If further test libraries are enabled, the serial number must be sent to ROHDE & SCHWARZ. To avoid writing errors, the serial number can be copied from the R&S GTSL License Viewer via the clipboard.
The License Key File newly created by ROHDE & SCHWARZ must be installed via the R&S GTSL License Viewer. After that, unrestricted use of the test libraries is possible.
If, during a test sequence, test functions are used or called from a non-enabled test library, a warning code will be displayed upon execution in TestStand. If non-enabled functions are called during Resource Manager Setup, an error message will be dis­played:
Figure 4-4: Error message from Resource Manager
If the error message is acknowledged by selecting in "demo mode".
"Ignore", the test sequence will run
21User Manual 1143.6450.42 ─ 26
Page 22
R&S®GTSL
Configuration Files
Syntax

5 Configuration Files

The required configuration files are stored by default in the ..\GTSL\Configuration directory.

5.1 Syntax

The syntax of the Physical Layer Configuration File (PHYSICAL.INI) and of the Appli­cation Layer Configuration File (APPLICATION.INI) is identical. The only difference between the two files is in terms of how they are used (see Chapter 5.2, "PHYSI-
CAL.INI", on page 26 and Chapter 5.3, "APPLICATION.INI", on page 30).
Both files use the standard INI file format.
Example of standard INI file format:
[section]
key = value
...
A section begins with the section name written inside closed brackets ([ ]). The follow­ing lines contain pairs of keywords and values. The keywords and the assigned values are separated by an equals sign ("=").
In the section names and keywords, no distinction is made between upper and lower case characters. However, the values after the equals sign are transferred exactly as they are written in the file. Leading and trailing spaces are truncated.

5.1.1 Naming Conventions

In the Physical Layer Configuration File and in the Application Layer Configuration File, several groups of keywords and sections are allowed. These refer to other sections and reflect the relationships and interconnections.
The section names follow the naming conventions indicated below.
The section name begins with the section type followed by an arrow ("->", a minus sign followed by a greater than sign). A unique name appears after the arrow. No spaces are permitted between the name and the arrow.
In the section names, no distinction is made between upper and lower case characters.
The following characters are permitted for the logical names, the device names and the bench names.
Table 5-1: Character set for names
"A" ... "Z" Upper case characters
"a" ... "z" Lower case characters
22User Manual 1143.6450.42 ─ 26
Page 23
R&S®GTSL
Configuration Files
Syntax
"0" ... "9" Numbers
"_" Underscore
"." Decimal point
The following maximum character lengths are permitted for section names, keywords and values:
Table 5-2: Maximum character lengths
section 80 characters
key 80 characters
value 260 characters
[LogicalNames] This section contains a list of names of devices and
benches. Any name can be used to identify a device or bench (Application Layer Configuration File).
[Device->...] A device section contains different keywords to
identify the devices. These include the GPIB address, the device type etc. (Physical Layer Con­figuration File and Application Layer Configuration File).
[Bench->...] This section contains a group of device entries
[ResourceManager] This section contains information for the configura-

5.1.2 [LogicalNames] Section

The [LogicalNames] section is used to assign a short, meaningful name to a device or bench. Any name can be chosen. This section contains a list of unique name alloca­tions. The values on the right side of the expressions must be valid names of a bench or of a device section.
The [LogicalNames] section is an optional entry and is used only in the Application Layer Configuration File.
Example:
[LogicalNames]
ICT = bench->ict
Power = device->psu_14
which together form a bench. A High Level Library requires the name of a bench in its setup routine (Application Layer Configuration File).
tion of the Resource Manager.
23User Manual 1143.6450.42 ─ 26
Page 24
R&S®GTSL

5.1.3 [Device] Section

Configuration Files
Syntax
The [Device] section contains a list of keywords and assigned values. These keywords and values precisely describe the relevant device. The name of the [Device] section begins with "Device->" followed by a unique name. Any name can be chosen.
There must be a [Device] section for each device in the Physical Layer Configuration File.
A [Device] section with the same name can be defined in the Application Layer Config­uration File. Additional device information can be given at this point by means of further keywords and values, or device information from the Physical Layer Configuration File can be overwritten. However, it is not possible to define a [Device] section in the Appli­cation Layer Configuration File which is not present in the Physical Layer Configuration File.
The keywords in a [Device] section and their meaning depend on the libraries used by the devices.
Table 5-3: Standard keywords of [Device] section
Keyword Description
Description Optional entry
Device description, remarks
Type Mandatory entry
Device type (e.g. CMU etc.)
ResourceDesc Mandatory entry
VISA device properties and device description in the form: GPIB[card number]::
[primary address]:: [secondary address] PXI[segment number]: :[device number]::[function]::INSTR
Examples:
GPIB0::15 or PXI0::16::0::INSTR
DriverSetup Optional entry
Special setup string for IVI driver, e.g. for simulation of devices
The "Type" and "ResourceDesc" entries are required for the test libraries. Both entries must be present in the Physical Layer Configuration File.
The information from the "Type" entry allows the test libraries to distinguish between different supported devices (such as CMD55 or CMU). This information is also needed for the system self-test.
The information from the "ResourceDesc" entry is needed to set up the device driver and create the physical connection with the indicated device.
Example:
24User Manual 1143.6450.42 ─ 26
Page 25
R&S®GTSL

5.1.4 [Bench] Section

Configuration Files
Syntax
[device->CMD55]
Description = Radio Communication Tester CMD55
Type = CMD55
ResourceDesc = GPIB0::4
The [Bench] section contains a list of keywords and assigned values which describes a group of devices and their use. The name of the [Bench] section begins with "Bench->" followed by a unique name. Any name can be chosen.
A [Bench] section can only be defined in the Application Layer Configuration File.
The keywords in a [Bench] section depend on the test library used by the bench. A keyword always provides at least one reference to a device entry. Other keywords may be necessary to describe the bench. The following keywords are predefined and should be present in each [Bench] section.
Table 5-4: Standard keywords of [Bench] section
Keyword Description
Description Optional entry
Bench description, remarks
Simulation Optional entry
If set to 1, the complete bench is simulated by the test library.
Trace Optional entry
If set to 1, the tracing function is enabled for the test library
The [Bench] section can contain further useful keywords and values which are used by a test library.
Example:
[bench->ICT]
Simulation = 0
Trace = 0
ICTDevice1 = device->psam
SwitchDevice1 = device->pmb_15
AnalogBus = device->ABUS
AppChannelTable = io_channel->ICT

5.1.5 [ResourceManager] Section

The [ResourceManager] section contains keywords and assigned values to control the behaviour of the Resource Manager library. The following keywords are supported:
25User Manual 1143.6450.42 ─ 26
Page 26
R&S®GTSL
Configuration Files
PHYSICAL.INI
Table 5-5: Keywords of [ResourceManager] section
Key name Remarks
Trace Blocks the tracing function (value = 0), enables the
tracing function (value = 1). The function impacts on all libraries.
TraceFile Defines the path and the name of the trace file.
TraceToScreen The tracing information is displayed on the standard
screen (value = 1).
TraceTimeStamp Writes the time of day at the start of each tracing
line (value = 1).
TraceThreadID Writes the ID of the current thread at the start of
each tracing line (value = 1).

5.2 PHYSICAL.INI

In the file PHYSICAL.INI (Physical Layer Configuration File), all hardware assemblies available in the Generic Test Software Library are described along with the correspond­ing definitions and settings (see example PHYSICAL.INI file). This file also contains definitions which are applicable to all test applications to be executed on the system (e.g. type definition). The information entered in this file is used by all test libraries and thus by each test step.
The PHYSICAL.INI file normally exists only once in the system as it reflects the exact physical structure. The file must only be modified in the event of a hardware change.
The Resource Manager calls and administers the information from the PHYSICAL.INI file.
With help of the Instrument Soft Panels application you can create a physical.ini file for the current system configuration. This is useful if new modules are added, a new sys­tem controller was assembled or if the slot assignments were changed. Refer to Chap-
ter 11.4.2, "Create Physical.ini", on page 238.
26User Manual 1143.6450.42 ─ 26
Page 27
R&S®GTSL

5.2.1 Example file for PHYSICAL.INI

Configuration Files
PHYSICAL.INI
[device->PAM]
Description
Type
ResourceDesc
DriverDll
DriverPrefix
DriverOption
SFTDll
SFTPrefix
[device->PSAM]
Description
Type
ResourceDesc
DriverDll
DriverPrefix
DriverOption
; Note: the self test DLL and prefix keywords must be removed for the first TS-PSAM module, because it is already tested in the basic self test.
= "TS-PAM, Analyzer Module, Slot 5"
= PAM
= PXI1::13::0::INSTR
= rspam.dll
= rspam
= "Simulate=0,RangeCheck=1"
= sftmpam.dll
= SFTMPAM
= "TS-PSAM, Source and Measurement Module, Slot 8"
= PSAM
= PXI1::10::0::INSTR
= rspsam.dll
= rspsam
= "Simulate=0,RangeCheck=1"
Descrip­tion
1
2
3
4
5
6
7
8
9
1
2
3
4
5
6
7
10
;SFTDll
;SFTPrefix
[device->PICT]
Description
Type
ResourceDesc
DriverDll
DriverPrefix
DriverOption
SFTDll
SFTPrefix
= sftmpsam.dll
= SFTMPSAM
= "TS-PICT, In-Circuit Test Extension Module, Slot 9"
= PICT
= PXI2::15::0::INSTR
= rspict.dll
= rspict
= "Simulate=0,RangeCheck=1"
= sftmpict.dll
= SFTMPICT
10
10
1
2
3
4
5
6
7
8
9
27User Manual 1143.6450.42 ─ 26
Page 28
R&S®GTSL
Configuration Files
PHYSICAL.INI
[device->PMB_15]
Description
Type
ResourceDesc
DriverDll
DriverPrefix
DriverOption
SFTDll
SFTPrefix
[device->PSM1_16]
Description
Type
ResourceDesc
DriverDll
DriverPrefix
DriverOption
SFTDll
SFTPrefix
= "TS-PMB, Matrix Module, Slot 15"
= PMB
= CAN0::0::1::15
= rspmb.dll
= rspmb
= "Simulate=0,RangeCheck=1"
= sftmpmb.dll
= SFTMPMB
= "TS-PSM1, Power Switch Module, Slot 16"
= PSM1
= CAN0::0::1::16
= rspsm1.dll
= rspsm1
= "Simulate=0,RangeCheck=1"
= sftmpsm1.dll
= SFTMPSM1
Descrip­tion
1
2
3
4
5
6
7
8
9
1
2
3
4
5
6
7
8
9
[device->PSYS1]
Description
Type
ResourceDesc
DriverDll
DriverPrefix
DriverOption
SFTDll
SFTPrefix
; Analog bus pseudo-device, used by ROUTE, SWMGR and EGTSL
[device->ABUS]
Description
Type
[io_channel->system]
.DMM_HI
.DMM_LO
= "TS-PSYS1, System Module, Slot 15 (rear)"
= PSYS1
= CAN0::0::5::15
= rspsys.dll
= rspsys
= "Simulate=0,RangeCheck=1"
= sftmpsys.dll
= SFTMPSYS
= "Analog Bus"
= AB
= PSAM!DMM_HI
= PSAM!DMM_LO
1
2
3
4
5
6
7
8
9
10
1
2
3
11
12
12
28User Manual 1143.6450.42 ─ 26
Page 29
R&S®GTSL

5.2.2 Description of Example File PHYSICAL.INI

Configuration Files
PHYSICAL.INI
The description is based on the example file in Chapter 5.2.1, "Example file for PHYSI-
CAL.INI", on page 27. The indicated numbers refer to the corresponding positions in
the example file. The place-holder "XY" in the following listing stands for the corre­sponding entries.
Table 5-6: Description of PHYSICAL.INI
1
[device->XY]
Defines the name under which the device is called in the test libraries. A separate entry must be made for each device. The entry in square brackets [ ] defines a new section within which new definitions are made.
2
3
4
5
6
7
8
Description = "XY"
Type = "XY"
ResourceDesc = "XY"
DriverDll = XY
DriverPrefix = XY
Driver Option = XY
SFTDll = XY
Gives a detailed description of the defined device. The entry is optional.
Gives the exact designation of the defined device. This designation is needed to call the corresponding device driver. The entry is mandatory.
Gives the necessary hardware information required for the defined device.
The entry is mandatory.
Details provided at this point include, for example:
GPIB address: GPIB1::20::1 (example)
GPIB[card number]::[primary address]:: [secondary address]
Serial interface: COMX
PXI address: PXI1::10::0::INSTR (example)
PXI[segment number]::[device number]:: [function]::INSTR
Gives the path and the file name of the device driver.
Gives a prefix for the device driver.
Gives certain options applicable to the device driver.
Gives the path and the file name of the self test device driver.
9
10
11
+
12
13
SFTPrefix = XY
[IO_Channel->system]
ResourceDesc_XY =
Gives a prefix for the self test device driver.
Text appearing after a semicolon (;) is interpreted as a comment.
The following definitions of I/O channels apply to all applications executed on the system. On the right side are the physical channel names as defined by the hardware and by the device driver. On the left side are the logical channel names as used in the test libraries.
In the case of certain devices, special subassemblies can be addressed directly through their primary address and secondary address. The relevant hard­ware information can be indicated especially for this subassembly with the corresponding designation.
29User Manual 1143.6450.42 ─ 26
Page 30
R&S®GTSL
Configuration Files
APPLICATION.INI

5.3 APPLICATION.INI

In the APPLICATION.INI file (Application Layer Configuration File) is a description of how the individual test libraries and the test functions use the hardware components (see example file APPLICATION.INI). Different hardware components can be com­bined into groups (bench). This bench can then be used within the test function. Fur­thermore, definitions are made in this file which apply to certain test applications to be executed on the system (e.g. definition of designations in the case of multi-channel operation).
The Resource Manager calls and administers the information from the APPLICATION.INI file.
Since an Application Layer Configuration File (APPLICATION.INI) normally exists for each test application executed on the system, the file name can be matched to the test application in question, e.g. APP_XXX.INI. The Resource Manager is told during setup which Application Layer Configuration File is to be used.
For ease of comprehension, the file name APPLICATION.INI is used for the Applica­tion Layer Configuration File in the manual.

5.3.1 Example File for APPLICATION.INI

[ResourceManager]
; general trace settings (normally off)
Trace
TraceFile
[LogicalNames]
ICT
[bench->ICT]
Description
Simulation
Trace
ICTDevice1
ICTDevice2
SwitchDevice1
= 0
= resmgr_trace.txt
= bench->ICT
= ICT bench
= 0
= 0
= device->psam
= device->pict
= device->pmb_15
Description
1
2
3
4
5
6
7
8
9
10
11
11
11
; used for functional test
SwitchDevice2 = device->PSM1_16
2
11
30User Manual 1143.6450.42 ─ 26
Page 31
R&S®GTSL
Configuration Files
APPLICATION.INI
AnalogBus = device->ABUS
AppChannelTable
AppWiringTable
[io_channel->ICT]
GND
INPUT
OUTPUT
TR1.B
TR1.C
TR1.E
VCC
[io_wiring->ICT]
GND
INPUT
OUTPUT
TR1.B
TR1.C
TR1.E
VCC
= io_channel->BenchGSM
= io_wiring->ICT
= pmb1!P1
= pmb1!P2
= pmb1!P3
= pmb1!P4
= pmb1!P5
= pmb1!P6
= pmb1!P7
= F1 S15 X10A1
= F1 S15 X10A2
= F1 S15 X10A3
= F1 S15 X10A4
= F1 S15 X10A5
= F1 S15 X10A6
= F1 S15 X10A7
Description
11
12
13
14
15
15
15
15
16
16
16
17
18
18
18
18
18
18
18

5.3.2 Description of Example File APPLICATION.INI

The description is based on the example file in Chapter 5.3.1, "Example File for APPLI-
CATION.INI", on page 30. The indicated numbers refer to the corresponding positions
in the example file. The place-holder "XY" in the following listing stands for the corre­sponding entries.
Table 5-7: Description of APPLICATION.INI
1
2
3
4
[ResourceManager]
Trace = x
Tracefile = fn
Defines a new section (identified by the square brackets [ ]) with information evaluated directly by the Resource Manager.
Text appearing after a semicolon (;) is interpreted as a comment.
Enables (value = 1) or disables (value = 0) tracing function.
Defines the path and the name of the trace file.
31User Manual 1143.6450.42 ─ 26
Page 32
R&S®GTSL
Configuration Files
APPLICATION.INI
5 to 6
7
8
9
10
11
[LogicalNames]
[bench->XY]
Description = x
Simulation = x
Trace = x
Defines a new section in which logical short names are defined. The short names can be used to call the libraries.
Defines a new bench with its name. The name, which is defined at this point, is called in the SETUP routine of the corre­sponding test library.
Gives a detailed description of the defined bench.
Blocks simulation of all entered devices (value = 0). Enables sim­ulation of the entered devices (value = 1).
Blocks the tracing function for that bench (value = 0). Enables the tracing function for that bench (value = 1).
The listed devices with the rele­vant defined names are assigned to the bench. The addressed devi­ces must be defined in the PHYS­ICAL.INI file with their details.
12
13
14 to 16
17 to 18
AppChannelTable = xy
AppWiringTable = xy
[io_channel->XY]
[io_wiring->XY]
Refers to a section [io_channel­>…] with defined channel names in APPLICATION.INI.
Refers to a section [io_wiring->…] with the definitions of the wiring table that is to apply for this bench.
Contains a list of user-specific channel names which are assigned to the physical device names and to the physical device channel names. The defined names apply only to the relevant application.
The physical wiring from the UUT pins to the front connectors of the R&S TS-PMB Matrix Cards. The test points (nodes) are on the left. The front connector locations are on the right in the form:
F<frame number> S<slot num­ber> X10<column><row>
F1 S15 X10A1 means:
TSVP frame 1
Slot 15
Front connector X10, column A, row 1
32User Manual 1143.6450.42 ─ 26
Page 33
R&S®GTSL

6.1.1 General

Editing and Running Test Sequences
TestStand

6 Editing and Running Test Sequences

6.1 TestStand

The test sequences created by ROHDE & SCHWARZ are edited under the TestStand Sequence Editor from National Instruments.
This section provides just a brief description of how a test sequence is edited and run.
A full description of the operation and functions of the individual menu windows of the TestStand Sequence Editor will be found in the enclosed User Manual or the online documentation.
A test sequence is edited as follows:
1.
Open TestStand Sequence Editor with "Start" -> "Programs" -> "National
Instruments TestStand "-> "Sequence Editor" or by clicking the "Sequence Editor" icon on Windows desktop. You will now see the main screen of the
Sequence Editor. Enter your user name and password (see Figure 6-1). The user name and password are stored in the user profiles of the TestStand software. Default setting:
● User Name: administrator
● Password: no password needed
Figure 6-1: Login
33User Manual 1143.6450.42 ─ 26
Page 34
R&S®GTSL
Editing and Running Test Sequences
TestStand
Figure 6-2: TestStand main screen
Note: User name and password can be set according to your specific company requirements.
2. Open an existing test sequence with "File" -> "Open." The test sequences created and supplied by ROHDE & SCHWARZ are stored by default in the directory C:\Program Files\GTSL\Sequences. If a different directory was specified during the software installation, the test sequences will be stored there (...\Sequences). The opened test sequence and its steps are displayed in the working window.
34User Manual 1143.6450.42 ─ 26
Page 35
R&S®GTSL
Editing and Running Test Sequences
TestStand
Figure 6-3: Working window

6.1.2 Editing a Test Step

Edit an individual test step as follows:
1. Double-click the test step you wish to edit in the working window. This opens the
"Test Step Setup" menu window.
35User Manual 1143.6450.42 ─ 26
Page 36
R&S®GTSL
Editing and Running Test Sequences
TestStand
Figure 6-4: Test step setup
Settings for the selected test step are made in this window. The name of the step and the type of call are shown in the title bar.
2. Click "Specify Module" to open the "Edit DLL Call" menu window for editing the test step.
36User Manual 1143.6450.42 ─ 26
Page 37
R&S®GTSL
Editing and Running Test Sequences
TestStand
Figure 6-5: Edit DLL Call
The settings for the selected test step are made on the "Module" tab in this win­dow.
"DLL Pathname:" Shows the name of the test library or the name of
the dynamic link library (DLL) of the test library. The memory path of the DLL file is displayed.
"Browse..." Opens the directory structure for the selection of the
test library (DLL)
"Function" Shows a pick list of the test functions in the test
library. The selected test function is displayed.
"?" Shows the help text for the selected test function.
The function, purpose and parameters of the test function are displayed.
"Reload Prototype" The test function is reloaded
"Calling Convention:" Always set to Standard Call in the case of R&S test
functions
"Parameter:" Displays a pick list of the parameters contained in
the test function. The selected parameter is dis­played.
"Category:" Shows the various parameter settings. These set-
"Object Type"
tings are parameter specific.
"Value Expression"
37User Manual 1143.6450.42 ─ 26
Page 38
R&S®GTSL

6.1.3 Running Test Sequences

Editing and Running Test Sequences
Generic Test Operator Interface R&S GTOP
"Browse..."
"New..." These buttons are used to insert, delete and move
parameters manually.
"Delete..."
"Move Up"
"Move Down"
The edited test sequence can be run directly in the TestStand Sequence Editor.
The opened test sequence is run once with "Execute" -> "Single Pass".
The started test sequence is run in a separate window. The result of the test sequence is displayed in a Report Window.
Select "Execute" -> "Test UUTs" to run the open test sequence in a continuous loop. The operator is prompted to enter a serial number before each run. The started test sequence is run in a separate window. Clicking "Stop" in the serial number input win­dow cancels the test sequences. The results of the test sequences are displayed in a Report Window with the corresponding serial number.
The Report Window must be closed when the test sequences have completed.

6.2 Generic Test Operator Interface R&S GTOP

6.2.1 General

The generated test sequences can also be executed via the Generic Test Operator Interface R&S GTOP. The R&S GTOP is a user interface, which has been specifically developed for application in multi-channel systems in the production area. R&S GTOP can only be used to run test sequences. Test sequences cannot be created or altered. Neither is it possible to debug test sequences.
The TestStand Run Time Engine and the Operator Interface Library are required to run the test sequences in the Generic Test Operator Interface (R&S GTOP). Figure 6-6 shows the integration of the R&S GTOP when performing a test sequence.
38User Manual 1143.6450.42 ─ 26
Page 39
R&S®GTSL
Editing and Running Test Sequences
Generic Test Operator Interface R&S GTOP
Figure 6-6: Integration of Generic Test Operator Interface R&S GTOP
The Operator Interface Library provides the functions for interaction between the test sequence in the TestStand and R&S GTOP.
The individual functions in the Operator Interface Library are described in the enclosed help file.
The directory ...\gtsl\operatorinterface\develop\gtop contains several example files, which render the configuration and the running of R&S GTOP apparent. These files include:
gtop_demo.bat
●
shows how to call R&S GTOP from the command line.
gtop_demo.ini
●
is a sample configuration file for R&S GTOP
gtop_demo.seq
●
is a channel-independent sequence which shows how to
– use the OPERINT functions in the PreUUT and PostUUT callbacks
– use OPERINT_Get_Channel to find out if R&S GTOP is available and on which
channel the sequence is running.
– make a sequence independent from the operator interface, i.e. how it can run
with optimum results on R&S GTOP and with good results on a different opera­tor interface like the TestStand sequence editor.
gtop_demo_phys.ini, gtop_demo_appl.ini
●
The files are the physical and application layer ini files for the resource manager
39User Manual 1143.6450.42 ─ 26
Page 40
R&S®GTSL
Editing and Running Test Sequences
Generic Test Operator Interface R&S GTOP
Although R&S GTOP has been designed to meet many wishes of our customers, you may want to customize the appearance or functionality of the operator interface. There­fore, the R&S GTOP application and the OPERINT library are shipped with source code. You will find the sources in the following directories:
...\gtsl\operatorinterface\develop\gtop
●
...\gtsl\develop\libraries\operint
●
Do not modify the original source files. Copy all files to a different directory outside the R&S GTSL directory tree and work on the copy, otherwise your changes may be over­written after the next R&S GTSL update.
How to modify the appearance of R&S GTOP:
Load the project file GTOP.PRJ in CVI and open the file GTOP.UIR. Modify text and colors, include your company logo etc. as required. However, be careful with modifica­tions of size and position of any panel.
How to modify the functionality of R&S GTOP:
Load the project file GTOP.PRJ in CVI and modify the source code. The R&S GTOP project is based on the National Instruments CVI operator interface, which is part of TestStand. Once you understand how the CVI operator interface works, you will also be able to modify the functionality of R&S GTOP.
Most of the R&S GTOP-specific functions can be found in the source module applspec.c.

6.2.2 Running R&S GTOP

The Generic Test Operator Interface R&S GTOP is run using the gtop.exe file. When running the file a R&S GTOP configuration file name must also be given (see Chap-
ter 6.2.4, "R&S GTOP Configuration File", on page 47).
Example: gtop.exe gtop_demo.ini
If, when run, GTOP configuration file is not specified, an error message is issued and the start of the program is canceled.
Figure 6-7: Start Error Message
If a valid R&S GTOP configuration file is present, R&S GTOP is started with the details specified within it. The start screen is displayed (see Figure 6-8) and a request to enter the user name and password (see Figure 6-9). The user name and password are specified in the TestStand software’s user profile.
40User Manual 1143.6450.42 ─ 26
Page 41
R&S®GTSL
Editing and Running Test Sequences
Generic Test Operator Interface R&S GTOP
Figure 6-8: Start Screen
Figure 6-9: Login
Default Configuration
User Name: administrator
Password: No password required
User name and password can be defined in company-specific terms.
The exact procedure for defining a user name and password is described in the enclosed TestStand documentation.
After a valid user name and password is entered the test sequences contained in the R&S GTOP configuration file are loaded and automatically started. It is not possible to stop individual test sequences. It is only possible to terminate the complete Generic Test Operator Interface R&S GTOP using the "File" -> "Exit" menu item.
41User Manual 1143.6450.42 ─ 26
Page 42
R&S®GTSL

6.2.3 Operator Interface

6.2.3.1 Representation
Editing and Running Test Sequences
Generic Test Operator Interface R&S GTOP
The Generic Test Operator Interface R&S GTOP shown below is configured for a 2­channel system. If a 1-channel system configuration is used, the right-hand operator interface remains blank.
Figure 6-10: Generic Test Operator Interface R&S GTOP
1 = Display panel, channel 2 2 = Test-sequence display, channel 2 3 = Banner display, channel 2 4 = Information line, channel 2 5 = Statistic line, channel 2 6 = Statistic line, channel 1 7 = Information line, channel 1 8 = Banner display, channel 1 9 = Test-sequence display, channel 1 10 = Display panel, channel 1 11 = Menu bar
6.2.3.2 Menu Bar
The menu bar is used to call up the functions for operating and configuring the Generic Test Operator Interface R&S GTOP. The menu items called up from R&S GTOP then open the corresponding dialogs in TestStand. The menu items are enabled or blocked in accordance with the user’s privileges (see also the TestStand documentation).
The table below describes the available functions.
42User Manual 1143.6450.42 ─ 26
Page 43
R&S®GTSL
Editing and Running Test Sequences
Generic Test Operator Interface R&S GTOP
Table 6-1: Menu Bar
File Login Login using another name (shift
change, administrator login)
Exit Terminate all sequences, exit
Generic Test Operator Interface R&S GTOP
Execute Tracing Enabled Switch tracing on and off in the
test sequence display
Configure Adapters Default TestStand configuration
dialog
Station Options Default TestStand configuration
dialog
External Viewers Default TestStand configuration
dialog
Search Directories Default TestStand configuration
dialog
Statistic Options Configuration of statistic options
(see Chapter 6.2.3.6, "Statistic
Display", on page 46)
Report Options Default TestStand configuration
dialog
Database Options Default TestStand configuration
dialog
Help About Display information on Generic
Test Operator Interface R&S GTOP (version number)
43User Manual 1143.6450.42 ─ 26
Page 44
R&S®GTSL
6.2.3.3 Test Sequence Display
Editing and Running Test Sequences
Generic Test Operator Interface R&S GTOP
Figure 6-11: Test Sequence Display
The test sequence display represents a small section of the current test sequence. If under the <Execute> <Tracing Enabled> menu item, tracing is activated (ticked off), the current step is marked by an arrow "->". Step flags are displayed by letters (e.g. "S" for skip). This is followed by the step result (Done, Passed, Failed,..) and the name of the step. Faulty steps are displayed in another color (red).
6.2.3.4 Banner
Banners are changing, colored highlighted displays. Certain banners may cover up the test sequence display. The various banners are filed in the Operator Interface Library as functions and can be integrated into the test sequence.
During a standard process, each channel of the test sequence process and the "Test­ing..." banner below are displayed. Invoking the corresponding function from the Oper­ator Interface Library enables the selected banner to be superimposed over the test sequence and thus displayed. The selected banner is displayed until:
●
the display of a new banner is invoked from the test sequence.
●
the function for clearing the selected banner is invoked from the test sequence.
Banners are not placed on top of each other. Only one banner is displayed per chan­nel. It is therefore not necessary to explicitly delete every single banner. Only when the test sequence display is to be shown again, is it necessary to delete the displayed ban­ner.
There are two types of banner:
44User Manual 1143.6450.42 ─ 26
Page 45
R&S®GTSL
Editing and Running Test Sequences
Generic Test Operator Interface R&S GTOP
1. Permanent banners
Pass Banner
Close Bench Banner
Fail Banner
Terminated Banner
Error Banner
Permanent banner text is given in the appropriate function of the Operator Inter­face Library. The texts can be easily converted to UIR files without any modification to the source code. On the "Fail Banner" and "Error Banner" additional free text can also be displayed. The text is transferred from the test sequence to the banner. See also the help file in the Operator Interface Library.
2. Configurable banners
Text Banner
Dialog Banner
Dialog and Prompt Banner
The content of the configurable banners is transferred over the corresponding Operator Interface Library functions from the test sequence to the Generic Test Operator Interface R&S GTOP. The following configurations are possible:
● Text content
● Button inscription
● Text and background color
The "Text Banner" displays a freely selectable text. The "Text Banner" is displayed until a new banner is invoked or the banner displayed is deleted.
45User Manual 1143.6450.42 ─ 26
Page 46
R&S®GTSL
6.2.3.5 Information Bar
6.2.3.6 Statistic Display
Editing and Running Test Sequences
Generic Test Operator Interface R&S GTOP
The "Dialog Banner" displays a freely selectable text and up to two buttons. The "Dialog Banner" is displayed until a button is clicked. The "Dialog and Prompt Banner" displays a freely selectable text and an input capability (e.g. for entering a serial number). Here too, up to two buttons can be displayed. The data entered is returned to the test sequences. The "Dialog and Prompt Banner " is displayed until a button is clicked. See also the help file in the Operator Interface Library.
The user can display freely selectable text on the information bar. The text content is given in the corresponding functions in the Operator Interface Library and integrated into the test sequence. The text in the information bar is displayed until it is overwritten by a new text.
Data is collated and displayed for the statistic display throughout the test sequence process.
Total Displays the number of tests performed.
Pass Ratio Displays the tests demarcated as PASS as a per-
centage.
since Displays the date, from which the statistic data has
been collated.
In order to ensure that the statistics can continue to be collated over an extended period of time and beyond, the corresponding data is stored in the configuration file when exiting the Generic Test Operator Interface R&S GTOP (see Chapter 6.2.4, "R&S
GTOP Configuration File", on page 47). The next time the R&S GTOP is started this
data is then loaded again and continued.
The <Configure><Statistic Options> menu item enables the dialog window for configur­ing the statistic options to be called up (see Figure 6-12).
46User Manual 1143.6450.42 ─ 26
Page 47
R&S®GTSL
Editing and Running Test Sequences
Generic Test Operator Interface R&S GTOP
Figure 6-12: Statistic Options
Statistics Reset Period This selector switch enables the time period to be
configured for determining when the statistic data should automatically be reset.
Reset Statistics Resets the statistic data.
OK The configurations made are saved in the configura-
Cancel The configurations made are cancelled and the dia-

6.2.4 R&S GTOP Configuration File

The R&S GTOP configuration file is, as everywhere in the R&S GTOP, structured simi­lar to a Windows INI file.
Day
●
The statistic data is automatically reset at the end of a day.
Week
●
The statistic data is automatically reset at the end of a week.
Month
●
The statistic data is automatically reset at the end of a month.
Manual
●
The statistic data can only be reset manually (Button "Reset Statistics")
tion file and the dialog window is closed.
log window closed.
47User Manual 1143.6450.42 ─ 26
Page 48
R&S®GTSL
Editing and Running Test Sequences
Generic Test Operator Interface R&S GTOP
Example:
[OperatorInterface]
NumPanels = 2
Statistics_Type = "daily"
[Panel_1]
SequenceFile = "C:\Program Files\GTSL\Sequences\test.seq"
Statistics_Start = "2001-04-03"
Total_Ok = 24
Total_Tested = 48
[Panel_2]
SequenceFile = "C:\Program Files\GTSL\Sequences\test.seq"
Statistics_Start = "2001-04-03"
Total_Ok = 24
Total_Tested = 48
The configuration file contains a general section [OperatorInterface] and a channel­specific section [Panel_n].
[OperatorInterface]
NumPanels =
Statistics_Type =
[Panel_n]
SequenceFile =
Statistics_Start =
Total_Ok =
Total_Tested =
Shows the number of channels which are to be dis­played in the Generic Test Operator Interface R&S GTOP. A channel-specific section [Panel_n] must be given for each channel.
Permissible value: 1 or 2
Indicates the period when the statistic data is to be automatically reset.
Permissible data:
●
daily
●
weekly
●
monthly
●
manually
Indicates the path and file name of the test sequen­ces to be performed in this channel.
Indicates the date, from which the statistic data has been collated.
Indicates the number of tests concluded with a PASS.
Displays the number of tests performed.
The "NumPanels" and "SequenceFile" entries must be given in the configuration file. If these entries are missing, an error message is issued and the start of the Generic Test Operator Interface R&S GTOP is terminated.
All other entries relate to statistic data. This data is automatically entered into the con­figuration file using default values (see Table 6-2).
48User Manual 1143.6450.42 ─ 26
Page 49
R&S®GTSL
Editing and Running Test Sequences
Generic Test Operator Interface R&S GTOP
Table 6-2: Configuration file Default Value
INI File Eintrag Standardwert
Statistics_Type
Statistics_Start
Total_Ok
Total_Tested
"manually"
Today’s date in "yyyy-mm-dd" format
0
0
49User Manual 1143.6450.42 ─ 26
Page 50
R&S®GTSL
Test Libraries
Generic Test Libraries

7 Test Libraries

The following sections briefly review the test functions which are available in the test libraries created by ROHDE & SCHWARZ.
A description of the individual test functions and their parameters will be found in the online help for the particular test library. The help files (.HLP, .CHM) are in the direc­tory ...\GTSL\BIN.

7.1 Generic Test Libraries

Starting with GTSL 3.30, no GTSL license is required.

7.1.1 Audio Analysis Library

7.1.1.1 General
Name of the dynamic link library (DLL):
Name of the help file: AUDIOANL.HLP, AUDIOANL.CHM
License required: R&S TS-LAAA
Supported devices: Not required
The Audio Analysis Library offers functions to analyze audio waveform data in memory. The following analysis functions are supported:
●
RMS calculation
●
Single-/Multitone frequency response
●
Distortion
●
Filters (low-pass, high-pass, band-pass, band-stop, CCIR weighted/unweighted)
●
Windows
7.1.1.2 Entries in PHYSICAL.INI
AUDIOANL.DLL
No entries required.
50User Manual 1143.6450.42 ─ 26
Page 51
R&S®GTSL
7.1.1.3 Entries in APPLICATION.INI
7.1.1.4 Functions
Test Libraries
Generic Test Libraries
Section [bench->...]
Keyword Value Description
Trace 0 / 1 Optional entry
Blocks the tracing function of the library (value = 0),
enables the tracing function of the library (value = 1).
Default = 0
Management
Setup AUDIOANL_Setup
Library Version AUDIOANL_Lib_Version
Cleanup AUDIOANL_Cleanup
Configuration
Configure Filter AUDIOANL_Configure_Filter
Calculation
Frequency Response AUDIOANL_Freq_Response
Distortion AUDIOANL_Distortion
RMS AUDIOANL_RMS
Filter Delay AUDIOANL_Filter_Delay

7.1.2 DC Power Supply Test Library

7.1.2.1 General
Name of the dynamic link library (DLL):
Name of the help file: CPWR.HLP, DCPWR.CHM
License required R&S TS-LBAS
Supported devices: R&S TS-PSAM Analog Stimulus Measurement Module
DCPWR.DLL
R&S TS-PSU Power Supply / Load Module
R&S TS-PSU12 Power Supply / Load Module 12V
Any DC Power Supply with an IVI device driver
The DCPWR Library controls one or more DC power supplies with drivers that conform to the IviDCPwr Class specification. It provides high level functions for controlling sev­eral DC power supply devices in one bench. Each power supply device provides one or more DC power channels.
51User Manual 1143.6450.42 ─ 26
Page 52
R&S®GTSL
7.1.2.2 Entries in PHYSICAL.INI
Test Libraries
Generic Test Libraries
Section [device->...]
Keyword Value Description
Type String Mandatory entry
for R&S TS-PSAM : PSAM
for R&S TS-PSU : PSU
for R&S TS-PSU12 : PSU12
for other IviDcPwr compliant instruments : IVI_DCPWR
ResourceDesc String Mandatory entry
VISA resource descriptor in the form
PXI[segment number]:: [device number]:: [function]::INSTR
CAN[board]:: [controller]::[frame]:: [slot]
GPIB[board]:: [primary address]:: [secondary address]
DriverPrefix String Mandatory entry
DriverDLL String Mandatory entry
DriverOption String Optional entry
7.1.2.3 Entries in APPLICATION.INI
Prefix for the IVI driver functions
for R&S TS-PSAM : rspsam
for R&S TS-PSU: rspsu
for R&S TS-PSU12: rspsu
for others: driver dependent
File name of the driver DLL
for R&S TS-PSAM: rspsam.dll
for R&S TS-PSU: rspsu.dll
for R&S TS-PSU12: rspsu.dll
for others: driver dependent
Option string being passed to the device driver during the driver's InitWithOptions function. See the online help file for the appropriate device driver.
Section [bench->...]
52User Manual 1143.6450.42 ─ 26
Page 53
R&S®GTSL
Test Libraries
Generic Test Libraries
Keyword Value Description
DCPwrSupply<i> String Mandatory entry
Reference to a DC power supply device section.
<i> stands for a number 1,2,3,...,n. Numbers must be in ascending order without gaps. <i> may be omitted in the case it is 1.
DCPwrChannelTable String Mandatory entry
Reference to the application channel table section.
Simulation 0 / 1 Optional entry
Enables/disables library-level sim­ulation, default = 0
Trace 0 / 1 Optional entry
Enables/disables tracing, default = 0
Section [io_channel->...] (Mandatory entries)
Contains a list of user-defined channel names with corresponding device names and device channel names. For details about channel name syntax see Chapter 8.3.4,
"Channel tables", on page 114.
Keyword Value Description
<user-defined name> String Physical channel description in
7.1.2.4 Functions
Management
Setup DCPWR_Setup
Library Version DCPWR_Lib_Version
Cleanup DCPWR_Cleanup
Configuration
Voltage Level DCPWR_Conf_Voltage_Level
Overvoltage Protection DCPWR_Conf_OVP
Current Limit DCPWR_Conf_Current_Limit
Output Range DCPWR_Conf_Output_Range
Output Enabled DCPWR_Conf_Output_Enabled
Information
Query Max Current Limit DCPWR_Query_Max_Current_Limit
Query Max Voltage Level DCPWR_Query_Max_Voltage_Level
Query Output State DCPWR_Query_Output_State
Utility
Reset DCPWR_Reset
Reset Output Protection DCPWR_Reset_Output_Protection
the form <device name>!<device channel name>
53User Manual 1143.6450.42 ─ 26
Page 54
R&S®GTSL
Test Libraries
Generic Test Libraries
Measurement
Measure DCPWR_Measure
Trigger
Configure Trigger Source DCPWR_Conf_Trigger_Source
Configure Triggered Voltage Level DCPWR_Conf_Triggered_Voltage_Level
Configure Triggered Current Limit DCPWR_Conf_Triggered_Current_Limit
Initiate DCPWR_Initiate
Abort DCPWR_Abort
Send Software Trigger DCPWR_Send_Software_Trigger
Instrument Driver Support
Get Instrument Handle DCPWR_Instrument_Get_Handle
TS-PSU Specific Functions
Configure Mode DCPWR_Conf_Mode
Configure Relay Protection DCPWR_Conf_Relay_Protection
Configure Remote Sensing DCPWR_Conf_Remote_Sensing
Configure PWM Output DCPWR_Conf_Output_PWM
Configure Trigger Output DCPWR_Conf_Trigger_Output
Configure Measurement DCPWR_Conf_Measurement
Initiate Trigger DCPWR_Initiate_Trigger
Acquisition
Configure Acquisition DCPWR_Conf_Acquisition
Initiate Acquisition DCPWR_Initiate_Acquisition
Fetch Acquisition DCPWR_Fetch_Acquisition
Abort Acquisition DCPWR_Abort_Acquisition
Arbitrary Waveform Output
Set Arbitrary Waveform DCPWR_Set_Arb_Wfm
Configure Arbitrary Waveform DCPWR_Conf_Arb_Wfm
Configure Arbitrary Waveform Abort DCPWR_Conf_Arb_Wfm_Abort
Initiate Arbitrary Waveform DCPWR_Initiate_Arb_Wfm
Abort Arbitrary Waveform DCPWR_Abort_Arb_Wfm
Gated Output
Configure Gated Output DCPWR_Conf_Gated_Output
Enable Gated Output DCPWR_Enable_Gated_Output
PAC Control
Configure PAC Control DCPWR_Conf_PAC_Control
Sink Modes
Configure Constant Current DCPWR_Conf_Const_Current
Configure Constant Resistance DCPWR_Conf_Const_Resistance
Configure Constant Power DCPWR_Conf_Const_Power
Query Sink State DCPWR_Query_Sink_State
TS-PSAM Specific Functions
Configure Pulsed Mode DCPWR_Conf_Pulsed_Mode
TS-PSU and TS-PSAM Specific Functions
Configure Ground Relay DCPWR_Conf_Ground_Relay
Wait Until Settled DCPWR_Wait_Until_Settled
54User Manual 1143.6450.42 ─ 26
Page 55
R&S®GTSL

7.1.3 Digital I/O Manager Library

7.1.3.1 General
Test Libraries
Generic Test Libraries
Name of the dynamic link library (DLL):
Name of the help file: DIOMGR.HLP, DIOMGR.CHM
License required: R&S TS-LBAS
Supported devices: R&S TS-PDFT, Digital Functional Test Module
DIOMGR.DLL
R&S TS-PIO3B, Digital I/O Module
R&S TS-PIO4, Digital Functional Test Module
R&S TS-PIO5, Digital Functional Test Module
The Digital I/O Manager (DIO Manager) provides high level functions for digital func­tional tests based on one or more R&S TS-PDFT module(s). These functions include:
●
Configuration of stimulus and response channels
●
Application of binary stimulus patterns
●
Collection of binary response data
Stimulus and response patterns can be executed at an arbitrary rate, usually under computer control. This is referred to as "Static Execution". Application of stimulus and collection of response patterns at a fixed clock rate is referred to as "Dynamic Execu­tion".
The "Static Execution" functions of the DIO Manager not only support R&S TS-PDFT modules, but also R&S TS-PIO3B modules.
The DIO Manager supports static and dynamic pattern execution across several R&S TS-PDFT modules and also static pattern executions across several R&S TS­PIO3B, R&S TS-PIO4 or R&S TS-PIO5 modules. Stimulus and response channels can be defined through logical channel names.
Dynamic pattern sets can be designed graphically with the waveform editor of the ALTERA "Quartus II Web Edition" software. The DIO Manager imports the waveform file, executes the pattern set and exports the results into a file. Deviations from the expected patterns can be easily located by comparing both files in the Quartus wave­form editor.
7.1.3.2 Entries in PHYSICAL.INI
Section [device->...]
55User Manual 1143.6450.42 ─ 26
Page 56
R&S®GTSL
Test Libraries
Generic Test Libraries
Keyword Value Description
Type String Mandatory entry
R&S TS-PDFT: pdft
R&S TS-PIO3B: pio3b
R&S TS-PIO4: pio4
R&S TS-PIO5: pio5
ResourceDesc String Mandatory entry
VISA resource descriptor in the form
PXI[segment number]:: [device number]:: [function]::INSTR
CAN[board]:: [controller]::[frame]:: [slot]
DriverPrefix String Mandatory entry
prefix for the IVI driver functions, without underscore
R&S TS-PDFT: rspdft
R&S TS-PIO3B: rspio3b
R&S TS-PIO4: rspio4
R&S TS-PIO5: rspio5
DriverDLL String Mandatory entry
DriverOption String Optional entry
7.1.3.3 Entries in APPLICATION.INI
Section [bench->...]
File name of the driver DLL
R&S TS-PDFT: rspdft.dll
R&S TS-PIO3B: rspio3b.dll
R&S TS-PIO4: rspio4.dll
R&S TS-PIO5: rspio5.dll
Option string being passed to the device driver during the Driver's InitWithOptions function. See the online help file for the appropriate device driver.
56User Manual 1143.6450.42 ─ 26
Page 57
R&S®GTSL
Test Libraries
Generic Test Libraries
Keyword Value Description
DIODevice<i> String Mandatory entry
Refers to a section with digital I/O devices in PHYSICAL.INI
<i> stands for a number from 1,2,3,...,40. The numbers must be assigned in ascending order with­out gaps. <i> may be omitted in the case it is 1.
DIOChannelTable String Mandatory entry
Refers to a section with defined channel names in APPLICATION.INI.
DIOTriggerLine String Optional entry
Specifies a PXI trigger line for synchronization of two or more R&S TS-PDFT modules
Valid values : 0 - 7
Default : 1
Simulation 0 / 1 Optional entry
Blocks simulation of all entered devices (value = 0).
Enables simulation of the entered devices (value = 1).
Default = 0
Trace 0 / 1 Optional entry
Blocks the tracing function (value = 0),
Enables the tracing function (value = 1).
Default = 0
ChannelTableCase Sensitive 0 / 1 Optional entry
The channel names in the chan­nel table are treated case-sensi­tive (value = 1) or case-insensitive (value = 0).
Section [io_channel->...] (Optional entries)
Mandatory entry
Contains a list of user-specific channel names which are assigned to the physical device names and to the physical device channel names. The defined names apply only to the relevant application. For details about channel name syntax see Chap-
ter 8.3.4, "Channel tables", on page 114.
57User Manual 1143.6450.42 ─ 26
Page 58
R&S®GTSL
Test Libraries
Generic Test Libraries
Keyword Value Description
<user-defined name> String Physical channel description in
the form:
<device name>!<device channel name>.
Permissible R&S TS-PDFT chan­nel names are:
OUT1 - OUT32 (stimulus chan­nesl)
IN1 - IN32 (response channels)
PO1 - PO4 (power output chan­nels)
Permissible R&S TS-PIO3B chan­nel names are:
PxIOy with x=0..7 and y=0..7(stimulus/response chan­nels)
P9TIOy with y=0..7 (stimulus/ response channels)
INH (inhibit stimulus channel)
Permissible R&S TS-PIO4 chan­nel names are:
OUT1 - OUT32 (stimulus chan­nels)
IN1 - IN32 (response channels)
Permissible R&S TS-PIO5 chan­nel names are:
OUT1 - OUT32 (stimulus chan­nels)
IN1 - IN32 (response channels)
7.1.3.4 Functions
Management
Setup DIOMGR_Setup
Library Version DIOMGR_Lib_Version
Cleanup DIOMGR_Cleanup
Configuration
Configure Stimulus DIOMGR_ConfigureStimulus
Configure Response DIOMGR_ConfigureResponse
Configure Loopback DIOMGR_ConfigureLoopback
Static Execution
Port Stimulus DIOMGR_PortStimulus
Port Response DIOMGR_PortResponse
Dynamic Execution
Configuration
Load Waveform DIOMGR_LoadWaveform
Configure Pattern Set Timing DIOMGR_ConfigurePatternSetTiming
Save Waveform DIOMGR_SaveWaveform
Unload Waveform DIOMGR_UnloadWaveform
58User Manual 1143.6450.42 ─ 26
Page 59
R&S®GTSL

7.1.4 DMM Test Library

Test Libraries
Generic Test Libraries
Action
Execute Pattern Set DIOMGR_ExecutePatternSet
Wait Until Pattern Set Complete DIOMGR_WaitUntilPatternSetComplete
Abort Pattern Set DIOMGR_AbortPatternSet
Results
Number of Executed Patterns DIOMGR_GetPatternSetExecutedPatternCount
Number of Failed Patterns DIOMGR_GetPatternSetFailedPatternCount
Number of Failed Channels DIOMGR_GetPatternSetFailedChannelCount
Failed Channel Names DIOMGR_GetPatternSetFailedChannelNames
High/Low Data of a Channel DIOMGR_GetPatternSetChannelData
Pass/Fail Results of a Channel DIOMGR_GetPatternSetChannelResults
Instrument Driver Support
Get Instrument Handle DIOMGR_Instrument_Get_Handle
7.1.4.1 General
Name of the dynamic link library (DLL):
Name of the help file: DMM.HLP, DMM.CHM
License required R&S TS-LBAS
Supported devices: National Instruments NI4060, any other DMM with
The DMM Library has been implemented to control numerous digital multimeter drivers that conform to the IviDmm Class specification. At present both the IVI-5 specification functions and those determined obsolete are supported.
The DMM Library provides high level functions for configuring and performing mea­surements.
7.1.4.2 Entries in PHYSICAL.INI
Section [device->...]
DMM.DLL
IVI compliant driver
R&S TS-PSAM
59User Manual 1143.6450.42 ─ 26
Page 60
R&S®GTSL
Test Libraries
Generic Test Libraries
Keyword Value Description
Type String Mandatory entry
NI4060 or IVI_DMM
psam = R&S TS-PSAM Analog Source and Measurement Module
ResourceDesc String Mandatory entry
VISA resource descriptor in the form
DAQ:: [deviceNumber]::INSTR (only
NI460)
PXI[segment number]:: [device number]:: [function]::INSTR
DriverPrefix String Mandatory entry
Prefix for the IVI driver functions, without underscore:
NI4060: niDMM
IVI_DMM: driver dependent
R&S TS-PSAM: rspsam
DriverDLL String Mandatory entry
DriverOption String Optional entry
PowerLineFrequency 50 or 60 Optional entry
7.1.4.3 Entries in APPLICATION.INI
Section [bench->...]
File name of the driver DLL
NI4060: nidmm_32.dll
IVI_DMM: driver dependent
R&S TS-PSAM: rspsam.dll
Option string being passed to the device driver during the Driver_Init function. See the online help file for the appropriate device driver.
Sets the power line frequency in Hz, default = 60
(not for R&S TS-PSAM)
60User Manual 1143.6450.42 ─ 26
Page 61
R&S®GTSL
7.1.4.4 Functions
Test Libraries
Generic Test Libraries
Keyword Value Description
DigitalMultimeter String Mandatory entry
Reference to multimeter device entry
Simulation 0 / 1 Optional entry
Enables/disables library-level sim­ulation, default = 0
Trace 0 / 1 Optional entry
Enables/disables tracing, default = 0
Setup DMM_Setup
Library Version DMM_Lib_Version
Configuration Functions
Configure Measurement DMM_Conf_Measurement
Configure Trigger DMM_Conf_Trigger
Configure Trigger Slope DMM_Conf_Trigger_Slope
Configure Auto Zero Mode DMM_Conf_Auto_Zero_Mode
Configure AC Bandwidth DMM_Conf_AC_Bandwidth
Configure Power Line Frequency DMM_Conf_Power_Line_Frequency
Configure Measurement Complete DMM_Conf_Meas_Complete_Dest
Configure Multi Point DMM_Conf_Multi_Point
Measurement Functions
Measure DC Voltage DMM_Meas_DC_Voltage
Measure DC Current DMM_Meas_DC_Current
Measure AC Voltage DMM_Meas_AC_Voltage
Measure AC Current DMM_Meas_AC_Current
Measure Resistance DMM_Meas_Resistance
Low Level Measurement Functions
Initiate DMM_Initiate
Fetch DMM_Fetch
Abort DMM_Abort
Send Software Trigger DMM_Send_Software_Trigger
Utility Functions
Reset DMM_Reset
TS-PSAM Specific Functions
Configure Lowpass Filter DMM_Conf_Lowpass_Filter
Configure Trigger Signal DMM_Conf_Trigger_Signal
Configure Analog Trigger DMM_Conf_Analog_Trigger
Configure Trigger Output DMM_Conf_Trigger_Output
Enable Trigger Output DMM_Enable_Trigger_Output
Send Software Signal DMM_Send_Software_Signal
Configure Coupling Relays DMM_Conf_Coupling_Relays
Configure Ground Relay DMM_Conf_Ground_Relay
Cleanup DMM_Cleanup
61User Manual 1143.6450.42 ─ 26
Page 62
R&S®GTSL

7.1.5 Factory Toolbox Library

7.1.5.1 General
Test Libraries
Generic Test Libraries
Name of the dynamic link library (DLL):
Name of the help file: FTBLIB.HLP, FTBLIB.CHM
License required R&S TS-LBAS
Supported devices: Digital IO Module 3B R&S TS-PIO3B
FTBLIB.DLL
The "Factory Toolbox" library offers functions for identifying adapters via the Digital IO Module 3B R&S TS-PIO3B. Two methods are available for this purpose:
●
Parallel adapter identification via ports
●
Serial adapter identification via SPI-EEPROM
The identification of test adapters is parameterized either via entries in a configuration file for the application layer (APPLICATION.INI) or via function calls in the test pro­gram. An R&S TS-PIO3B module must be entered in the file for configuring the system (PHYSICAL.INI).
Parallel Adapter Identification via Ports
The parallel adapter identification is especially easy to implement but requires one or two complete 8 bit IO ports. For this purpose, the 8 open drain ports (P0 to P7) are available on the R&S TS-PIO3B module. To be able to identify an adapter uniquely, it is only necessary to connect wires in the adapter with GND. Port bits that have not been wired are read as "high" by the internal pull-up resistors.
Serial Adapter Identification via SPI-EEPROM
The serial adapter identification uses an SPI-EEPROM in the adapter and can be set up easily in connection with an R&S TS-PTRF. The Atmel AT25160 module, a 16 kBit (2 kByte) EEPROM for SPI is supported. In this way, all the open drain IO ports remain free and only one SPI Chip-Select signal (E_CSx) of the R&S TS-PTRF is occupied. In the following example, E_CS3 (port 3) is used for the adapter identification. In this case you have to observe that the SPI signals (E_MOSI, E_MISO and E_SCLK) as well as the selected Chip-Select signal must be connected to the front panel (X10) via jumpers on the R&S TS-PTRF module.
Figure 7-1: Serial adapter identification via SPI-EEPROM
62User Manual 1143.6450.42 ─ 26
Page 63
R&S®GTSL
7.1.5.2 Entries in PHYSICAL.INI
Test Libraries
Generic Test Libraries
An R&S TS-PIO3B module must be installed in the system and the related entry must be available in the configuration file for the system.
Key Value Description
Type String Mandatory entry
PIO3B
ResourceDesc String Mandatory entry
resource descriptor in the form
CAN[board]:: [controller]::[frame]:: [slot]
DriverPrefix String Mandatory entry
Prefix for the IVI driver functions, without underscore: rspio3b
DriverDll String Mandatory entry
File name of the driver DLL
rspio3b.dll
DriverOption String Optional Entry
Description String Optional Entry
7.1.5.3 Entries in APPLICATION.INI
This configuration file is usually created individually for each unit under test / each test program. It can be assigned any name and stored in any directory. The following table provides an overview of the keywords.
Section [bench->...]
Key Value Description
AdaIdentDevice String Optional entry
Option string being passed to the device driver during the Driver_Init function. See the online help file for the appropriate device driver.
Gives a detailed description of the defined device.
Refers to the device section of the TS-PIO3B (e. g. AdaIdentDevice = device->rspio3b_1) if the adapter identification functionality.
AdaIdentParPortLo 0...7 Optional entry
R&S TS-PIO3B port from which the lower 8 bits of the adapter identification are read.
Default = 0
63User Manual 1143.6450.42 ─ 26
Page 64
R&S®GTSL
Test Libraries
Generic Test Libraries
Key Value Description
AdaIdentParPortHi 0...7 Optional entry
R&S TS-PIO3B port from which the higher 8 bits of the adapter identification are read.
If only one 8-bit identification is to be used, the same port as in the "AdaIdentPortLo" parameter is specified here.
The higher 8 bits in the result will then be set to 0.
Default = 0 (8 bit identification via port 0)
AdaIdentSpiPort 0..7 Optional entry
Controls the Chip-Select genera­tion via an R&S TS-PTRF module for the adapter identification with R&S TS-PIO3B via an SPI EEPROM. If the R&S TS-PTRF module is not available, this parameter will be ignored.
Default = 0
Simulation 0 / 1 Optional entry
Trace 0 / 1 Optional entry
7.1.5.4 Functions
The following routines are available for identifying a test adapter. Refer to the help file (FTBLIB.HLP) for a description.
Management
Setup FTBLIB_Setup
Library Version FTBLIB_Lib_Version
Cleanup FTBLIB_Cleanup
Blocks the simulation of the entered devices (value = 0).
Enables simulation of the entered devices (value = 1).
Default = 0
Blocks the tracing function of the library (value = 0).
Enables the tracing function of the library (value = 1).
Default = 0
Adapter Identification
Parallel Port
Parallel Config Port FTBLIB_AdaIdentParConfigPort
64User Manual 1143.6450.42 ─ 26
Page 65
R&S®GTSL

7.1.6 Function Generator Library

7.1.6.1 General
Test Libraries
Generic Test Libraries
Parallel Read FTBLIB_AdaIdentParRead
SPI EEPROM
SPI Config Port FTBLIB_AdaIdentSpiConfigPort
SPI Read FTBLIB_AdaIdentSpiRead
SPI Write FTBLIB_AdaIdentSpiWrite
Name of the dynamic link library (DLL):
Name of the help file: FUNCGEN.HLP, FUNCGEN.CHM
License required R&S TS-LBAS
Supported devices: R&S TS-PFG Arbitrary Waveform Generator
The Function Generator Library provides functions for waveform generators:
●
Standard Waveforms
●
Arbitrary Waveforms
●
Arbitrary Waveform Sequences
7.1.6.2 Entries in PHYSICAL.INI
Section [device->...]
Keyword Value Description
Type String Mandatory entry
FUNCGEN.DLL
Any other waveform generator with IVI compliant driver.
PFG = R&S TS-PFG Arbitrary Waveform Generator
IVI_FGEN = other IVI compliant generator
ResourceDesc String Mandatory entry
VISA resource descriptor in the form
PXI[segment number]:: [device number]:: [function]::INSTR
65User Manual 1143.6450.42 ─ 26
Page 66
R&S®GTSL
Test Libraries
Generic Test Libraries
Keyword Value Description
DriverPrefix String Mandatory entry
Prefix for the IVI driver functions, without underscore:
IVI_FGEN: driver dependent
R&S TS-PFG: rspfg
DriverDll String Mandatory entry
File name of the driver DLL
IVI_FGEN: driver dependent
R&S TS-PFG: rspfg.dll
DriverOption String Optional entry
Option string being passed to the device driver during the Driver_Init function. See the online help file for the appropriate device driver.
7.1.6.3 Entries in APPLICATION.INI
Section [bench->...]
Keyword Value Description
FunctionGenerator String Mandatory entry
Simulation 0 / 1 Optional entry
Trace 0 / 1 Optional entry
Reference to the device entry of the function generator in PHYSICAL.INI.
Blocks the simulation of the entered devices (value = 0).
Enables simulation of the entered devices (value = 1).
Default = 0
Blocks the tracing function of the library (value = 0),
enables the tracing function of the library (value = 1).
Default = 0
7.1.6.4 Functions
Setup FUNCGEN_Setup
Library Version FUNCGEN_Lib_Version
Basic Instrument Operation
Configure Operation Mode FUNCGEN_ConfigureOperationMode
Configure Output Mode FUNCGEN_ConfigureOutputMode
66User Manual 1143.6450.42 ─ 26
Page 67
R&S®GTSL
Test Libraries
Generic Test Libraries
Configure Ref Clock Source FUNCGEN_ConfigureRefClockSource
Configure Output Impedance FUNCGEN_ConfigureOutputImpedance
Configure Output Enabled FUNCGEN_ConfigureOutputEnabled
Initiate Generation FUNCGEN_InitiateGeneration
Abort Generation FUNCGEN_AbortGeneration
Standard Function Output
Configure Standard Waveform FUNCGEN_ConfigureStandardWaveform
Arbitrary Waveform Output
Query Arb Waveform Capabilities FUNCGEN_QueryArbWfmCapabilities
Create Arbitrary Waveform FUNCGEN_CreateArbWaveform
Configure Arbitrary Waveform FUNCGEN_ConfigureArbWaveform
Configure Sample Rate FUNCGEN_ConfigureSampleRate
Clear Arbitrary Waveform FUNCGEN_ClearArbWaveform
Arbitrary Frequency
Configure Arbitrary Frequency FUNCGEN_ConfigureArbFrequency
Arbitrary Sequence Output
Query Arb Sequence Capabilities FUNCGEN_QueryArbSeqCapabilities
Create Arbitrary Sequence FUNCGEN_CreateArbSequence
Configure Arbitrary Sequence FUNCGEN_ConfigureArbSequence
Clear Arbitrary Sequence FUNCGEN_ClearArbSequence
Clear Arbitrary Memory FUNCGEN_ClearArbMemory
Triggering
Configure Trigger Source FUNCGEN_ConfigureTriggerSource
Software Triggering
Send Software Trigger FUNCGEN_SendSoftwareTrigger
Burst Configuration
Configure Burst Count FUNCGEN_ConfigureBurstCount
Utility Functions
Import Waveform Data FUNCGEN_ImportWaveformData
Reset FUNCGEN_Reset
TS-PFG Specific Functions
Configure Trigger Delay FUNCGEN_ConfigureTriggerDelay
Configure Filter FUNCGEN_ConfigureFilter
Configure Arbitrary Marker FUNCGEN_ConfigureArbMarker
Configure Marker Output FUNCGEN_ConfigureMarkerOutput
Configure Coupling Relays FUNCGEN_ConfigureCouplingRelays
Configure Ground Relay FUNCGEN_ConfigureGroundRelay
Cleanup FUNCGEN_Cleanup

7.1.7 Operator Interface Library

7.1.7.1 General
Name of the dynamic link library (DLL):
Name of the help file: OPERINT.HLP, OPERINT.CHM
OPERINT.DLL
67User Manual 1143.6450.42 ─ 26
Page 68
R&S®GTSL
7.1.7.2 Entries in PHYSICAL.INI
Test Libraries
Generic Test Libraries
License required R&S TS-LBAS
Supported devices: not usable
The Operator Interface Library offers functions for interaction between the TestStand sequence and the R&S GTSL Operator Interface:
●
Display of Banners and other Information
●
Dialog Boxes
●
User Input
If the R&S GTSL Operator Interface is not available (e.g. when a sequence is started from the TestStand Sequence Editor), the dialog boxes are replaced by simple pop-up dialogs.
This library requires TestStand as test executive, it cannot be run in other environ­ments.
No entries
7.1.7.3 Entries in APPLICATION.INI
Section [bench->...]
Keyword Value Description
Trace 0 / 1 Optional entry
7.1.7.4 Functions
Setup OPERINT_Setup
Library Version OPERINT_Lib_Version
Information
Get Associated Channel Number OPERINT_Get_Channel
Display Functions
Show Banner OPERINT_Show_Banner
Show Customized Banner OPERINT_Show_Custom_Banner
Hide Banner OPERINT_Hide_Banner
Customized Dialog OPERINT_Custom_Dialog
Customized Input Prompt OPERINT_Custom_Prompt
Display Info Line OPERINT_Display_Info
Cleanup OPERINT_Cleanup
0 : Disable tracing
1 : Enable tracing
Default: 0
68User Manual 1143.6450.42 ─ 26
Page 69
R&S®GTSL

7.1.8 Resource Manager Library

7.1.8.1 General
Test Libraries
Generic Test Libraries
Name of the dynamic link library (DLL):
Name of the help file: RESMGR.HLP, RESMGR.CHM
License required R&S TS-LBAS
Supported devices: not usable
The Resource Manager Library provides functions for managing the hardware used in the test system.
7.1.8.2 Entries in PHYSICAL.INI
No entries
7.1.8.3 Entries in APPLICATION.INI
Section [Resource Manager]
Optional entry
Controls the tracing properties of the Resource Manager.
Keyword Value Description
RESMGR.DLL
Trace 0 / 1 Blocks the tracing function (value
= 0), enables the tracing function (value = 1).
Default = 0
TraceFile String Defines the path and the name of
the trace file. Default = ""
TraceToScreen 0 / 1 The tracing information is dis-
played on the standard screen (value = 1).
Default = 0
TraceTimeStamp 0 / 1 Writes the time of day at the start
of each tracing line (value = 1).
Default = 0
TraceThreadID 0 / 1 Writes the ID of the current thread
at the start of each tracing line (value = 1).
Default = 0
69User Manual 1143.6450.42 ─ 26
Page 70
R&S®GTSL
7.1.8.4 Functions
Test Libraries
Generic Test Libraries
Keyword Value Description
TraceAppend 0 / 1 Appends lines to existing trace file
(value = 1) Overwrites trace file (value = 0, default)
TraceAutoFlush 0 / 1 Writes trace lines immediately to
disk (value =1) Buffers disk write operations (value = 0, default) Note that enabling this feature may degrade application perfor­mance significantly.
Management
Setup RESMGR_Setup
Library Version RESMGR_Lib_Version
Cleanup RESMGR_Cleanup
Resource Functions
Allocate Resource RESMGR_Alloc_Resource
Free Resource RESMGR_Free_Resource
Informational
Resource Type RESMGR_Get_Resource_Type
Resource Name RESMGR_Get_Resource_Name
Get Value RESMGR_Get_Value
Compare Value RESMGR_Compare_Value
Number of Sections RESMGR_Number_Of_Sections
Nth Section Name RESMGR_Nth_Section_Name
Number of Keys RESMGR_Number_Of_Keys
Nth Key Name RESMGR_Nth_Key_Name
Key Value RESMGR_Get_Key_Value
Device Sessions
Open Session RESMGR_Open_Session
Get Session Handle RESMGR_Get_Session_Handle
Set Session Handle RESMGR_Set_Session_Handle
Close Session RESMGR_Close_Session
Open Sub-Session RESMGR_Open_SubSession
Get Session Sub-Handle RESMGR_Get_Session_SubHandle
Set Session Sub-Handle RESMGR_Set_Session_SubHandle
Close Sub-Session RESMGR_Close_SubSession
70User Manual 1143.6450.42 ─ 26
Page 71
R&S®GTSL
Test Libraries
Generic Test Libraries
Dynamic memory Management
Allocate Memory RESMGR_Alloc_Memory
Get Memory Pointer RESMGR_Get_Mem_Ptr
Free Memory RESMGR_Free_Memory
Allocate Shared Memory RESMGR_Alloc_Shared_Memory
Lock Shared Memory RESMGR_Lock_Shared_Memory
Unlock Shared Memory RESMGR_Unlock_Shared_Memory
Free Shared Memory RESMGR_Free_Shared_Memory
Locking
Lock Device RESMGR_Lock_Device
Unlock Device RESMGR_Unlock_Device
Support Functions
Read System Identification RESMGR_Read_ROM
Enable Tracing RESMGR_Enable_Tracing
Trace RESMGR_Trace
Set Trace Flag RESMGR_Set_Trace_Flag
Get Trace Flag RESMGR_Get_Trace_Flag

7.1.9 Self Test Support Library

7.1.9.1 General
Name of the dynamic link library (DLL):
Name of the help file: SFT.HLP, SFT.CHM
License required R&S TS-LBAS
Supported devices Self Test Multimeter: National Instruments
The self test support library contains functions which are common for all self test mod­ules like measurements, report generation, run-time state handling and operator dialog functions.
7.1.9.2 Entries in PHYSICAL.INI
SFT.DLL
NI4060 with Self Test Matrix Card R&S TS-PMA
or
Self Test Multimeter with integrated matrix R&S TS­PSAM
Section [device->...]
71User Manual 1143.6450.42 ─ 26
Page 72
R&S®GTSL
Test Libraries
Generic Test Libraries
Keyword Value Description
SFTDLL String Mandatory entry
File name of the self test DLL
R&S TS-PAM : sftmpam.dll
R&S TS-PDFT : sftmpdft.dll
R&S TS-PFG : sftmpft.dll
R&S TS-PICT : sftmpict.dll
R&S TS-PIO2: sftmpio2.dll
R&S TS-PMA : sftmpma.dll
R&S TS-PMB : sftmpmb.dll
R&S TS-PRL1 : sftmprl1.dll
R&S TS-PSAM : sftmpsam.dll
R&S TS-PSM1 : sftmpsm1.dll
R&S TS-PSM2 : sftmpsm2.dll
R&S TS-PSM3 : sftmpsm3.dll
R&S TS-PSM4 : sftmpsm4.dll
R&S TS-PSM5 : sftmpsm5.dll
R&S TS-PSU : sftmpsu.dll
R&S TS-PSU12 : sftmpsu.dll
R&S TS-PSYS : sftmpsys.dll
SFTPrefix String Mandatory entry
Prefix for the self test functions, without underscore. This entry is case sensitive:
R&S TS-PAM : SFTMPAM
R&S TS-PDFT : SFTMPDFT
R&S TS-PFG : SFTMPFT
R&S TS-PICT : SFTMPICT
R&S TS-PIO2: SFTMPIO2
R&S TS-PMA : SFTPMA
R&S TS-PMB : SFTMPMB
R&S TS-PRL1 :SFTMPRL1
R&S TS-PSAM : SFTMPSAM
R&S TS-PSM1 : SFTMPSM1
R&S TS-PSM2 : SFTMPSM2
R&S TS-PSM3 : SFTMPSM3
R&S TS-PSM4 : SFTMPSM4
R&S TS-PSM5 : SFTMPSM5
R&S TS-PSU : SFTMPSU
R&S TS-PSU12 : SFTMPSU
R&S TS-PSYS : SFTMPSYS
Example:
72User Manual 1143.6450.42 ─ 26
Page 73
R&S®GTSL
Test Libraries
Generic Test Libraries
[device->RelayCard1]
Description = TS-PRL1 in Slot 7
Type = PRL1
ResourceDesc = PXI0::1::17
DriverDll = rsprl1.dll
DriverPrefix = rsprl1
SFTDll = SFTMPRL1.DLL
SFTPrefix = SFTMPRL1
Example of a physical layer .ini file for a R&S CompactTSVP system:
If the recommended self test hardware is installed, the following device section must be added:
[device->psam]
Description = "TS-PSAM, source and measurement module, Slot 3"
Type = PSAM
ResourceDesc = PXI1::15::0::INSTR
DriverDll = rspsam.dll
DriverPrefix = rspsam
DriverOption = "Simulate=0,RangeCheck=1"
; Note: the self test DLL and prefix keywords must be removed for the
; first TS-PSAM module, because it is already tested in the
; basic self test.
;SFTDll = sftmpsam.dll
;SFTPrefix = SFTMPSAM
The type of the digital multimeter and the self test switch device must be "PSAM".
The "ResourceDesc" keys must match your hardware configuration.
Because this device is the self test instrumentation and under control of the self test library, this sections must not have the keys "SFTDll" and "SFTPrefix".
In order to test a Rohde & Schwarz CompactTSVP module (R&S TS-PFG, R&S TS­PMB, ... ) the device section of these modules must contain the entries "SFTDll and SFTPrefix". The following sections show the entries for a R&S TS-PFG and a R&S TS­PMB module:
[device->pfg]
Description = "TS-PFG, arbitrary function generator module, Slot 4"
Type = PFG
ResourceDesc = PXI1::14::0::INSTR
DriverDll = rspfg.dll
DriverPrefix = rspfg
SFTDll = sftmpfg.dll
SFTPrefix = SFTMPFG
[device->pmb]
Description = "TS-PMB, matrix module, Slot 10"
Type = PMB
ResourceDesc = CAN0::0::1::10
DriverDll = rspmb.dll
73User Manual 1143.6450.42 ─ 26
Page 74
R&S®GTSL
Test Libraries
Generic Test Libraries
DriverPrefix = rspmb
SFTDll = sftmpmb.dll
SFTPrefix = SFTMPMB
The values of the keys "SFTPrefix" and "DriverPrefix" are case sensitive.
The files CompactTSVP_physical.ini and SFT_CompactTSVP_application.ini in the GTSL\Configuration subdirectory are an example for the self test configuration of a R&S CompactTSVP test system.
Example of a physical layer .ini file for a Classic TSVP system:
If the recommended self test hardware is installed, the following two device sections must be added:
[device->SftRelayCard]
Description = "Self Test Matrix Card"
Type = PMA1
ResourceDesc = PXI2::11::0::INSTR
DriverPrefix = rspma
DriverDll = rspma.dll
DriverOption = "Simulate=0,DriverSetup=MCR:FFFFFFF6 CRAuto:1 BusSel:0"
[device->SftDMM]
Description = "Self Test Digital Multimeter"
type = NI4060
ResourceDesc = DAQ::2::INSTR
DriverPrefix = niDMM
DriverDll = nidmm_32.dll
DriverOption = "Simulate=0,DriverSetup=PXI-4060"
PowerLineFrequency = 50
The type of the switch device must be "PMA1"
The DriverSetup attribute in the DriverOption string of the PMA1 card must have the parameter setting "CRAuto:1"
The type of the digital multimeter must be "NI4060"
The "ResourceDesc" keys must match your hardware configuration
Because these two devices are the self test instrumentation and under control of the self test library these sections must not have the keys "SFTDll" and "SFTPrefix".
In order to test a Rohde & Schwarz TSVP module (R&S TS-PRL1, R&S TS-PMA) the device section of these cards must contain the new entries "SFTDll and SFTPrefix". The following sections show the entries for a R&S TS-PRL1 and a R&S TS-PMA card:
[device->RelayCard1]
Description = "Relay Card 1"
Type = PRL1
ResourceDesc = PXI3::10::0::INSTR
74User Manual 1143.6450.42 ─ 26
Page 75
R&S®GTSL
Test Libraries
Generic Test Libraries
DriverPrefix = rsprl1
DriverDll = rsprl1.dll
DriverOption = "Simulate=0"
SFTDll = SFTMPRL1.DLL
SFTPrefix = SFTMPRL1
[device->MatrixCard1]
Description = "Matrix Card 1"
Type = PMA1
ResourceDesc = PXI1::11::0::INSTR
DriverPrefix = rspma
DriverDll = rspma.dll
DriverOption = "Simulate=0,DriverSetup=MCR:FFFFFFF6 CRAuto:0 BusSel:0"
SFTDll = SFTMPMA.DLL
SFTPrefix = SFTMPMA
The values of the keys "SFTPrefix" and "DriverPrefix" are case sensitive
The DriverSetup attribute in the DriverOption string of a PMA card must have the parameter setting "CRAuto:0" for self test! This can also be configured in the self test application.ini file.
The files demo_physical.ini and sft_7100_application.ini in the GTSL\Configuration subdirectory are an example for the self test configuration of a single channel TS7100 test system.
7.1.9.3 Entries in APPLICATION.INI
Section [bench->SFT]
Keyword Value Description
DigitalMultimeter String Mandatory entry
SwitchDevice String Mandatory entry
Trace 0 / 1 Optional entry
Bench device link to the device entry of the multimeter:
For R&S TSVP: National Instru­ments DMM 4060
For R&S CompactTSVP: R&S TS-PSAM
Bench device link to the device entry of the matrix for the multi­meter (R&S TS-PMA1)
Enables/disables tracing, default = 0
Section [SftOptions]
75User Manual 1143.6450.42 ─ 26
Page 76
R&S®GTSL
Test Libraries
Generic Test Libraries
Keyword Value Description
SystemName String The Name of the system to be
tested. This Name appears in the header of the self test report.
Default "-"
SFTFixture 0 / 1 1 : TSVP self test fixture is con-
nected to the modules
0 : no SFT fixture present
Default 1
ManualInterventions 0 / 1 1 : Additional tests which require
user interaction
0 : SFT runs without further inter­action.
Default 1
ReportFile String Path and filename of report file
Default
C:\TEMP\SFT_Report.txt
ReportStyle 1 / 2 / 3 /... 1 : Only errors are reported
2 : Only a short report is gener­ated
3 : Generates a full report all other entries: A full report is generated
Default 1
ReportAppend 0 / 1 1 : Report is appended to existing
file
0 : Existing report file is overwrit­ten
Default 0
SuppressDialog 0 / 1 1 : Options dialog is not displayed
0 : Options dialog is displayed
Default 0
StopOnFirstFailure 0 / 1 1 : SFT is aborted on first test
case failure
0 : SFT is not aborted on first test case failure
Default 0
Section [SftParts]
PartX <PartName>, <BenchName>,<SelectFlag>
The keys have the format "PartX". Where X ist a continuous counter starting at 1. The values are comma separated lists with the following entries:
76User Manual 1143.6450.42 ─ 26
Page 77
R&S®GTSL
7.1.9.4 Functions
Test Libraries
Generic Test Libraries
Part Name An arbitrary name for a part to test. All parts must
have a unique name.
Bench Name Name of the corresponding bench
Select Flag Default value for the selection
1: Part selected
0: Part not selcted
Management
Setup SFT_Setup
Library Version SFT_Lib_Version
Cleanup SFT_Cleanup
Measurement
Dmm_reset SFT_Dmm_reset
Dmm_Connect SFT_Dmm_Connect
Dmm_Disconnect SFT_Dmm_Disconnect
Dmm_DisconnectAll SFT_Dmm_DisconnectAll
Dmm_MeasDelay SFT_Dmm_MeasDelay
Dmm_WaitForDebounce SFT_Dmm_WaitForDebounce
Dmm_ConfigureMeasurement SFT_Dmm_ConfigureMeasurement
Dmm_ConfigureAutoZeroMode SFT_Dmm_ConfigureAutoZeroMode
Dmm_Read SFT_Dmm_Read
Dmm_AverageMeasurement SFT_Dmm_AverageMeasurement
Dmm_checkForExternVoltage SFT_Dmm_checkForExternVoltage
Dmm_MeasureContact SFT_Dmm_MeasureContact
Dmm_MeasureIsolation SFT_Dmm_MeasureIsolation
Trigger
Dmm_TriggerConfSignal SFT_Dmm_TriggerConfSignal
Dmm_ConfigureTrigger SFT_Dmm_ConfigureTrigger
Dmm_EnableTriggerline SFT_Dmm_EnableTriggerline
Dmm_Initiate SFT_Dmm_Initiate
Dmm_trig_SendSoftwareSignal SFT_Dmm_trig_SendSoftwareSignal
Dmm_Fetch SFT_Dmm_Fetch
DC_Source
dcs_ConfigureVoltageLevel SFT_dcs_ConfigureVoltageLevel
dcs_ConfigureCurrentLimitRange SFT_dcs_ConfigureCurrentLimitRange
dcs_ConfigureCurrentLimit SFT_dcs_ConfigureCurrentLimit
dcs_ConfigureOutputEnabled SFT_dcs_ConfigureOutputEnabled
dcs_QueryOutputState SFT_dcs_QueryOutputState
CNX
cnx_ConfigureSwitches SFT_cnx_ConfigureSwitches
cnx_Gnd SFT_cnx_Gnd
cnx_DmmToGnd SFT_cnx_DmmToGnd
cnx_Matrix SFT_cnx_Matrix
cnx_Coupling SFT_cnx_Coupling
Report
CommentAddItem SFT_CommentAddItem
77User Manual 1143.6450.42 ─ 26
Page 78
R&S®GTSL
Test Libraries
Generic Test Libraries
WarningAddItem SFT_WarningAddItem
ErrorAddItem SFT_ErrorAddItem
ResultTextAddItem SFT_ResultTextAddItem
ProgramErrorAddItem SFT_ProgramErrorAddItem
TableAddItem SFT_TableAddItem
TableColumnSetAttrInt SFT_TableColumnSetAttrInt
TableColumnSetAttrString SFT_TableColumnSetAttrString
TableCellSetValueInt SFT_TableCellSetValueInt
TableCellSetValueDouble SFT_TableCellSetValueDouble
TableCellSetValueString SFT_TableCellSetValueString
ResultTabAddItem SFT_ResultTabAddItem
ResultTabLineGetAttrInt SFT_ResultTabLineGetAttrInt
ResultTabLineSetAttrDouble SFT_ResultTabLineSetAttrDouble
ResultTabLineSetAttrString SFT_ResultTabLineSetAttrString
ResultTabSetAttrInt SFT_ResultTabSetAttrInt
ResultTabColumnSetAttrInt SFT_ResultTabColumnSetAttrInt
ResultTabLineCalcAttrStatus SFT_ResultTabLineCalcAttrStatus
Run-time State
OptionGetAttrInt SFT_OptionGetAttrInt
PartSelect SFT_PartSelect
PartGetAttrInt SFT_PartGetAttrInt
PartGetAttrString SFT_PartGetAttrString
PartSetAttrInt SFT_PartSetAttrInt
ComponentAddItem SFT_ComponentAddItem
ComponentSelect SFT_ComponentSelect
ComponentSelectByIndex SFT_ComponentSelectByIndex
ComponentSetAttrInt SFT_ComponentSetAttrInt
ComponentGetAttrInt SFT_ComponentGetAttrInt
ComponentSetAttrString SFT_ComponentSetAttrString
ComponentGetAttrString SFT_ComponentGetAttrString
TestCaseAddItem SFT_TestCaseAddItem
TestCaseSelect SFT_TestCaseSelect
TestCaseSelectByIndex SFT_TestCaseSelectByIndex
TestCaseSetAttrInt SFT_TestCaseSetAttrInt
TestCaseGetAttrInt SFT_TestCaseGetAttrInt
TestCaseSetAttrString SFT_TestCaseSetAttrString
Dialog
ComponentShowDialog SFT_ComponentShowDialog
DlgProgressPrintInfo SFT_DlgProgressPrintInfo
Utility
Dmm_Test SFT_Dmm_Test
Dmm_writeRegister SFT_Dmm_writeRegister
Dmm_readRegister SFT_Dmm_readRegister
78User Manual 1143.6450.42 ─ 26
Page 79
R&S®GTSL

7.1.10 Signal Analyzer Library

7.1.10.1 General
Test Libraries
Generic Test Libraries
Name of the dynamic link library (DLL):
Name of the help file: SIGANL.HLP, SIGANL.CHM
License required R&S TS-LBAS
Supported devices: R&S TS-PAM, Analyzer Module
SIGANL.DLL
Any other module with IVI Scope compliant driver.
The Signal Analyzer Library provides configuration and measurement functions for waveform analyzers / digital oscilloscopes compliant with the IVI-4.1 IviScope instru­ment class. Furthermore it offers generic waveform analysis and utility functions.
These functions include:
●
Channel configuration
●
Time base configuration
●
Trigger configuration
●
Waveform acquisition
●
Waveform parameter measurement (Average, RMS)
●
Frequency measurement
●
Event counting (Slope, Peak)
●
Time measurement between events
●
Waveform comparison
●
Calculation of reference waveforms
●
Waveform import/export as file
●
Waveform display
7.1.10.2 Entries in PHYSICAL.INI
Section [device->...]
Keyword Value Description
Type String Mandatory entry
ResourceDesc String Mandatory entry
for R&S TS-PAM: PAM
for other IviScope compliant instruments: IVI_SCOPE
VISA resource descriptor in the form
PXI[segment number]::[device number]::[function]::INSTR
79User Manual 1143.6450.42 ─ 26
Page 80
R&S®GTSL
Test Libraries
Generic Test Libraries
Keyword Value Description
DriverPrefix String Mandatory entry
prefix for the IVI driver functions, without underscore
for R&S TS-PAM: rspam
for others: driver dependent
Driver DLL String Mandatory entry
File name of the driver DLL
for R&S TS-PAM: rspam.dll
for others: driver dependent
DriverOption String Optional entry
Option string being passed to the device driver during the Driver's InitWithOptions function. See the online help file for the appropriate device driver.
7.1.10.3 Entries in APPLICATION.INI
Section [bench->...]
Keyword Value Description
SignalAnalyzer String Mandatory entry
Simulation 0 / 1 Optional entry
Trace 0 / 1 Optional entry
Reference to the device entry of the signal analyzer in
PHYSICAL.INI
Blocks simulation of all entered devices (value = 0).
Enables simulation of the entered devices (value = 1).
Default = 0
Blocks the tracing function (value = 0).
Enables the tracing function (value = 1).
Default = 0
7.1.10.4 Functions
Setup SIGANL_Setup
Library Version SIGANL_Lib_Version
Basic Instrument Operation
Configure Acquisition Type SIGANL_ConfigureAcquisitionType
Configure Acquisition Record SIGANL_ConfigureAcquisitionRecord
Sample Rate SIGANL_SampleRate
80User Manual 1143.6450.42 ─ 26
Page 81
R&S®GTSL
Test Libraries
Generic Test Libraries
Actual Record Length SIGANL_ActualRecordLength
Configure Channel SIGANL_ConfigureChannel
Configure Chan Characteristics SIGANL_ConfigureChannelCharacteristics
Configure Trigger SIGANL_ConfigureTrigger
Configure Trigger Coupling SIGANL_ConfigureTriggerCoupling
Configure Edge Trigger Source SIGANL_ConfigureEdgeTriggerSource
Read Waveform SIGANL_ReadWaveform
Initiate Acquisition SIGANL_InitiateAcquisition
Acquisition Status SIGANL_AcquisitionStatus
Abort SIGANL_Abort
Fetch Waveform SIGANL_FetchWaveform
TS-PAM specific functions
Configure Coupling Relays SIGANL_ConfigureCouplingRelays
Configure Ground Relay SIGANL_ConfigureGroundRelay
Configure Trigger Output SIGANL_ConfigureTriggerOutput
Enable Trigger Output SIGANL_EnableTriggerOutput
Configure Trigger Pattern SIGANL_ConfigureTriggerPattern
Send Software Trigger SIGANL_SendSoftwareTrigger
Get Trigger Status SIGANL_GetTriggerStatus
Configure Scan SIGANL_ConfigureScan
Actual Scan SIGANL_ActualScan
Fetch Trigger SIGANL_FetchTrigger
Waveform Measurements
Configure Reference Levels SIGANL_ConfigureRefLevels
Read Waveform Measurement SIGANL_ReadWaveformMeasurement
Fetch Waveform Measurement SIGANL_FetchWaveformMeasurement
Waveform Analysis
Find Event in Waveform SIGANL_FindWaveformEvent
Count Events in Waveform SIGANL_CountWaveformEvents
Get Waveform Value SIGANL_GetWaveformValue
Calculate Limit Lines SIGANL_CalculateLimitLines
Compare Waveform SIGANL_CompareWaveform
Calculate Waveform Parameter SIGANL_CalculateWaveformParameter
Calculate Frequency SIGANL_CalculateFrequency
Waveform Display
Display Waveform in Diagram SIGANL_ShowWaveform
Display Waveform with Marker SIGANL_ShowWaveformMarker
Display Waveform with Limits SIGANL_ShowWaveformLimits
Utility Functions
Reset SIGANL_Reset
Is Invalid Waveform Element SIGANL_IsInvalidWfmElement
Import Waveform Data SIGANL_ImportWaveformData
Export Waveform Data SIGANL_ExportWaveformData
Cleanup SIGANL_Cleanup
81User Manual 1143.6450.42 ─ 26
Page 82
R&S®GTSL

7.1.11 Signal Routing Library

7.1.11.1 General
Test Libraries
Generic Test Libraries
Name of the dynamic link library (DLL):
Name of the help file: ROUTE.HLP, ROUTE.CHM
License required R&S TS-LSRL
Supported devices: R&S TS-PAM
ROUTE.DLL
R&S TS-PDFT
R&S TS-PFG
R&S TS-PIO2
R&S TS-PMB
R&S TS-PSAM
R&S TS-PSM1
R&S TS-PSM2
R&S TS-PSM3
R&S TS-PSM4
R&S TS-PSM5
R&S TS-PSU
R&S TS-PSU12
R&S TS-PSYS1
R&S TS-PSYS2
and all other switch devices that provide an IVI?C driver of the IviSwtch class.
The Signal Routing Library makes it possible to set up complex switched connections by means of switching commands. Switched connections can be automatically routed by the analog measurement bus, i.e. the software searches for free analog measure­ment bus lines and automatically switches the relays in the switching path.
Extensive switched connections can also be saved under a user-specific name and then called in the test program.
Refer to Chapter 8, "Signal Routing", on page 104, for a detailed description of the Sig­nal Routing Library.
The Signal Routing Library cannot be used together with the Switch Manager.
7.1.11.2 Entries in PHYSICAL.INI
Section [device->...]
Mandatory entry
Describes the properties of the switch modules installed in the system.
82User Manual 1143.6450.42 ─ 26
Page 83
R&S®GTSL
Test Libraries
Generic Test Libraries
Keyword Value Description
Type String Mandatory entry
for R&S TS-PAM:PAM
for R&S TS-PDFT:PDFT
for R&S TS-PFG: PFG
for R&S TS-PIO2: PIO2
for R&S TS-PMB: PMB
for R&S TS-PSAM: PSAM
for R&S TS-PSM1: PSM1
for R&S TS-PSM2: PSM2
for R&S TS-PSM3: PSM3
for R&S TS-PSM4: PSM4
for R&S TS-PSM5: PSM5
for R&S TS-PSU: PSU
for R&S TS-PSU12: PSU12
for R&S TS-PSYS1: PSYS1
for R&S TS-PSYS2: PSYS2
for other IviSwtch compliant instruments : IVI_SWITCH
ResourceDesc String Mandatory entry
VISA resource descriptor in the form:
PXI[segment number]:: [device number]:: [function]::INSTR
CAN[board]:: [controller]::[frame]:: [slot]
GPIB[board]:: [primary address]:: [secondary address]
83User Manual 1143.6450.42 ─ 26
Page 84
R&S®GTSL
Test Libraries
Generic Test Libraries
Keyword Value Description
DriverPrefix String Mandatory entry
Prefix for the IVI driver functions for
R&S TS-PAM: rspam
for R&S TS-PDFT: rspdft
for R&S TS-PFG: rspfg
for R&S TS-PIO2: rspio2
for R&S TS-PMB: rspmb
for R&S TS-PSAM: rspsam
for R&S TS-PSM1: rspsm1
for R&S TS-PSM2: rspsm2
for R&S TS-PSM3: rspsm3
for R&S TS-PSM4: rspsm4
for R&S TS-PSM5: rspsm5
for R&S TS-PSU: rspsu
for R&S TS-PSU12: rspsu
for R&S TS-PSYS1: rspsys
for R&S TS-PSYS2: rspsys
for others: driver dependent
84User Manual 1143.6450.42 ─ 26
Page 85
R&S®GTSL
Test Libraries
Generic Test Libraries
Keyword Value Description
DriverDLL String Mandatory entry
File name of the driver DLL
for R&S TS-PAM: rspam.dll
for R&S TS-PDFT: rspdft.dll
for R&S TS-PFG: rspfg.dll
for R&S TS-PIO2: rspio2.dll
for R&S TS-PMB: rspmb.dll
for R&S TS-PSAM: rspsam.dll
for R&S TS-PSM1: rspsm1.dll
for R&S TS-PSM2: rspsm2.dll
for R&S TS-PSM3: rspsm3.dll
for R&S TS-PSM4: rspsm4.dll
for R&S TS-PSM5: rspsm5.dll
for R&S TS-PSU: rspsu.dll
for R&S TS-PSU12: rspsu.dll
for R&S TS-PSYS1: rspsys.dll
for R&S TS-PSYS2: rspsys.dll
for others: driver dependent
DriverOption String Optional entry
Option string being passed to the device driver during the driver's InitWithOptions function. See the online help file for the appropriate device driver.
NOTE:
For R&S TS-PMB modules, the option "DriverSetup=CRAuto:1" must not be used.
Section [device->ABUS]
Mandatory entry
Device section for the analog bus.
Keyword Value Description
Type String Mandatory entry
AB
Section [io_channel->system]
Optional entry
The system channel table contains a list of user-specific channel names which are assigned to the physical device names and to the physical device channel names. The defined names apply to all test applications running on the system.
85User Manual 1143.6450.42 ─ 26
Page 86
R&S®GTSL
7.1.11.3 Entries in APPLICATION.INI
Test Libraries
Generic Test Libraries
Keyword Value Description
<logical channel name> String Physical channel description in
the combination <device name>! <physical device channel name>
Section [bench->...]
Mandatory entry
Contains a list of switch devices, options and links to the channel table and switch set­tings.
Keyword Value Description
SwitchDevice<i> String Mandatory entry
Refers to a device entry section of a switch device in PHYSICAL.INI. <i> stands for a number from 1,2,3,...,n. The num­bers must be assigned in ascend­ing order without gaps. <i> may be omitted in case it is 1.
AnalogBus String Mandatory entry
Refers to the device section of the analog bus in PHYSICAL.INI.
AppChannelTable String Mandatory entry
Refers to a section [io_channel­>...] with defined channel names in APPLICATION.INI.
SwitchSettings String Optional entry
Refers to a section [switch->...] with defined switch settings in APPLICATION.INI.
Simulation 0 / 1 Optional entry
Blocks the simulation of the entered devices (value = 0).
Enables simulation of the entered devices (value = 1).
Default = 0
Trace 0 / 1 Optional entry
Blocks the tracing function of the library (value = 0).
Enables the tracing function of the library (value = 1).
Default = 0
86User Manual 1143.6450.42 ─ 26
Page 87
R&S®GTSL
Test Libraries
Generic Test Libraries
Keyword Value Description
ChannelTableCaseSensitive 0 / 1 Optional entry
The channel names in the chan­nel table are treated case-sensi­tive (value = 1) or case-insensitive (value = 0).
Default = 0
SignalRoutingDisplay 0 / 1 Optional entry
Displays a window with actual sig­nal routing information (value=1).
Default = 0
Section [io_channel->...]
Mandatory entry
Contains a list of user-specific channel names which are assigned to the physical device names and to the physical device channel names. The defined names apply only to the relevant application. For details about channel name syntax see Chap-
ter 8.3.4, "Channel tables", on page 114.
Keyword Value Description
<logical channel name> String Physical channel description in
<logical channel name> String Logical channel name from the
Section [switch->...]
Optional entry
Contains a list of user-specific switch setting names which are assigned to signal rout­ing command strings. Refer to Chapter 8.3.4, "Channel tables", on page 114 for details.
Keyword Value Description
#<switch setting name> String Signal routing command
7.1.11.4 Functions
Setup ROUTE_Setup
Library Version ROUTE_Lib_Version
Signal Routing
Execute ROUTE_Execute
Cleanup ROUTE_Cleanup
the combination <device name>! <physical device channel name>
section [io_channel->system] from PHYSICAL.INI.
87User Manual 1143.6450.42 ─ 26
Page 88
R&S®GTSL

7.1.12 Switch Manager Library

7.1.12.1 General
Test Libraries
Generic Test Libraries
Name of the dynamic link library (DLL):
Name of the help file: SWMGR.HLP, SWMGR.CHM
License required R&S TS-LBAS
Supported devices: R&S TS-PAM
SWMGR.DLL
R&S TS-PDFT
R&S TS-PFG
R&S TS-PIO2
R&S TS-PMA
R&S TS-PMB
R&S TS-PRL0
R&S TS-PRL1
R&S TS-PSAM
R&S TS-PSM1
R&S TS-PSM2
R&S TS-PSU
R&S TS-PSU12
and all other switch devices that provide an IVI-C driver of the IviSwtch class.
The Switch Manager Library provides functions for the switching of signals. It controls the device drivers of the relevant switching modules (e.g. R&S TS-PRL1, R&S TS­PMA). The Test Library changes switch requests with channel names (standard I/O channels or system/application specific channels) into calls to the device drivers of the existing switch modules.
7.1.12.2 Entries in PHYSICAL.INI
Section [device->...]
Mandatory entry
Describes the properties of the switch cards installed in the system.
88User Manual 1143.6450.42 ─ 26
Page 89
R&S®GTSL
Test Libraries
Generic Test Libraries
Keyword Value Description
Type String Mandatory entry
pam = R&S TS-PAM Analyzer Module
pdft = R&S TS-PDFT Digital Functional Test Module
pfg = R&S TS-PFG Function Gen­erator Module
pio2 = R&S TS-PIO2 Analog/Digi­tal IO Module 2
pma1 = R&S TS-PMA Matrix Module with R&S TS-PMA1 Relay Modules
pma2 = R&S TS-PMA Matrix Module with R&S TS-PMA2 Relay Modules
pmb = R&S TS-PMB Matrix Mod­ule prl0 = R&S TS-PRL0 Univer­sal Relay Module
prl1 = R&S TS-PRL1 Universal Relay Module
psam = R&S TS-PSAM Analog Source and Measurement Module
psm1 = R&S TS-PSM1 Power Switch Module
psm2 = R&S TS-PSM2 Multiplex/ Switch Module 2
psu = R&S TS-PSU Power Sup­ply/Load Module
psu12 = R&S TS-PSU12 Power Supply/Load Module 12V
ivi_switch = any other switching module or any other switchpanel card with an IVI device driver.
ResourceDesc String Mandatory entry
VISA device properties and device description in the form:
PXI[segment number]:: [device number]:: [function]::INSTR
CAN[board]:: [controller]::[frame]:: [slot]
89User Manual 1143.6450.42 ─ 26
Page 90
R&S®GTSL
Test Libraries
Generic Test Libraries
Keyword Value Description
DriverPrefix String Mandatory entry
Prefix for the IVI driver functions
R&S TS-PAM: rspam
R&S TS-PDFT: rspdft
R&S TS-PFG: rspfg
R&S TS-PIO2: rspio2
R&S TS-PMA: rspma
R&S TS-PMB: rspmb
R&S TS-PRL0: rsprl0
R&S TS-PRL1: rsprl1
R&S TS-PSAM: rspsam
R&S TS-PSM1: rspsm1
R&S TS-PSM2: rspsm2
R&S TS-PSU: rspsu
R&S TS-PSU12: rspsu
Other designations: Dependent on the drivers used
Driver DLL String Mandatory entry
File name of the driver DLL
R&S TS-PAM: rspam.dll
R&S TS-PDFT: rspdft.dll
R&S TS-PFG: rspfg.dll
R&S TS-PIO2: rspio2.dll
R&S TS-PMA: rspma.dll
R&S TS-PMB: rspmb.dll
R&S TS-PRL0: rsprl0.dll
R&S TS-PRL1: rsprl1.dll
R&S TS-PSAM: rspsam.dll
R&S TS-PSM1: rspsm1.dll
R&S TS-PSM2: rspsm2.dll
R&S TS-PSU: rspsu.dll
R&S TS-PSU12: rspsu.dll
Other designations: Dependent on the drivers used
DriverOption String Optional entry
Optional indications which are passed to the device driver during the Driver_Init function. See the online help of the relevant switch device drivers.
Section [device->ABUS]
Mandatory entry
Device section for the analog bus.
90User Manual 1143.6450.42 ─ 26
Page 91
R&S®GTSL
7.1.12.3 Entries in APPLICATION.INI
Test Libraries
Generic Test Libraries
Keyword Value Description
Type String ab = Analog Bus
Section [io_channel->system]
Optional entry
Contains a list of user-specific channel names which are assigned to the physical device names and to the physical device channel names. The defined names apply to all test applications running on the system.
Keyword Value Description
<user-defined name> String Physical channel description in
the combination <device name>! <device channel name>
Section [bench->...]
Mandatory entry
Contains a list of switch devices
Keyword Value Description
SwitchDevice<i> String Mandatory entry
Refers to a section with switch devices in PHYSICAL.INI
<i> stands for a number from 1,2,3,...,n. The numbers must be assigned in ascending order with­out gaps.
<i> may be omitted in the case it is 1.
AnalogBus String Optional entry
Refers to the device section of the analog bus in PHYSICAL.INI.
AppChannelTable String Optional entry
Refers to a section with defined channel names in APPLICATION.INI.
Simulation 0 / 1 Optional entry
Blocks simulation of all entered devices (value = 0). Enables sim­ulation of the entered devices (value = 1).
91User Manual 1143.6450.42 ─ 26
Page 92
R&S®GTSL
Test Libraries
Generic Test Libraries
Keyword Value Description
Trace 0 / 1 Optional entry
Blocks the tracing function (value = 0), enables the tracing function (value = 1).
Default = 0
ChannelTableCase Sensitive 0 / 1 Optional entry
The channel names in the chan­nel table are treated case-sensi­tive (value = 1) or case-insensitive (value = 0).
Section [io_channel->...]
Optional entry
Contains a list of user-specific channel names which are assigned to the physical device names and to the physical device channel names. The defined names apply only to the relevant application. For details about channel name syntax see Chap-
ter 8.3.4, "Channel tables", on page 114.
Keyword Value Description
<user-defind name> String Physical channel description in
<user-defind name> String Channel names from the list
7.1.12.4 Functions
Management
Setup SWMGR_Setup
Library Version SWMGR_Lib_Version
Cleanup SWMGR_Cleanup
Configuration Functions
Configure Coupling Mode SWMGR_ConfigureCouplingMode
Configure Coupling Relays SWMGR_ConfigureCouplingRelays
Route Functions
Connect Channels SWMGR_Connect
the combination <device name>! <device channel name>
[io_channel->system] from the
PHYSICAL.INI.
Disconnect Channels SWMGR_Disconnect
Disconnect All Channels SWMGR_DisconnectAll
92User Manual 1143.6450.42 ─ 26
Page 93
R&S®GTSL

7.1.13 Utility Library

7.1.13.1 General
Test Libraries
Generic Test Libraries
Switch Is Debounced? SWMGR_IsDebounced
Wait For Debounce SWMGR_WaitForDebounce
Name of the dynamic link library (DLL):
Name of the help file: UTIL.HLP, UTIL.CHM
License required R&S TS-LBAS
Supported devices: not usable
Miscellaneous utility functions.
7.1.13.2 Entries in PHYSICAL.INI
No entries
7.1.13.3 Entries in APPLICATION.INI
No entries
7.1.13.4 Functions
Library Version UTIL_Lib_Version
Information
GTSL Version UTIL_GTSL_Version
GTSL Registry Value UTIL_GTSL_Registry_Value
Time Functions
Delay (obsolete) UTIL_Delay
High-resolution Timer
Sleep UTIL_Hrestim_Sleep
Sleep Until UTIL_Hrestim_Sleep_Until
Get Time Stamp UTIL_Hrestim_Time_Stamp
Get Timer Resolution UTIL_Hrestim_Resolution
TSVP Module Information
Module Search UTIL_Module_Search
Sort Module List UTIL_Module_Sort_List
Get Attribute (Integer) UTIL_Module_Get_Attribute_Int
Get Attribute (String) UTIL_Module_Get_Attribute_String
Free Module List UTIL_Module_Free_List
HTML Help
UTIL.DLL
93User Manual 1143.6450.42 ─ 26
Page 94
R&S®GTSL

7.2.1 IC-Check Library

7.2.1.1 General
Test Libraries
In-Circuit Test Libraries
Show HTML Help UTIL_Show_Html_Help
Close HTML Help UTIL_Close_Html_Help

7.2 In-Circuit Test Libraries

For further information on the In-Circuit-Test, R&S EGTSL and R&S IC-Check see
Software Description Enhanced Generic Test Software Library R&S EGTSL and Soft­ware Description Generic Test Software Library R&S IC-Check.
Name of the dynamic link library (DLL):
Name of the help file: ICCHECK.HLP, ICCHECK.CHM
License required R&S TS-LBAS and R&S TS-LICC
Supported devices: R&S TS-PMB Matrix Module R&S TS-PSAM Source
The IC-Check Test Library offers functions for the IC check using the R&S GTSL soft­ware and the R&S TS-PSAM and R&S TS-PMB modules. The functions allow to
●
load, run and debug ICC programs
●
generate a report
7.2.1.2 Entries in PHYSICAL.INI
Section [device->...]
ICCHECK.DLL
and Measurement Module
94User Manual 1143.6450.42 ─ 26
Page 95
R&S®GTSL
Test Libraries
In-Circuit Test Libraries
Keyword Value Description
Type String Mandatory entry
pmb = R&S TS-PMB Matrix Mod­ule
psam = R&S TS-PSAM Source and Measurement Module
ResourceDesc String Mandatory entry
VISA resource descriptor in the form
PXI[segment number]:: [device number]:: [function]::INSTR
CAN[board]:: [controller]::[frame]:: [slot]
DriverPrefix String Mandatory entry
prefix for the IVI driver functions, without underscore
R&S TS-PMB: rspmb
R&S TS-PSAM: rspsam
DriverDll String Mandatory entry
DriverOption String Optional entry
7.2.1.3 Entries in APPLICATION.INI
Section [bench->...]
File name of the driver DLL
R&S TS-PMB: rspmb.dll
R&S TS-PSAM: rspsam.dll
Option string being passed to the device driver during the driver's InitWithOptions function. See the online help file for the appropriate device driver.
95User Manual 1143.6450.42 ─ 26
Page 96
R&S®GTSL
Test Libraries
In-Circuit Test Libraries
Keyword Value Description
ICCDevice String Mandatory entry
Refers to the device section of the R&S TS-PSAM
SwitchDevice<i> String Mandatory entry
Refers to a device sections of a switch device R&S TS-PMB in PHYSICAL.INI.
<i> stands for a number from 1,2,3,...,n. The numbers must be assigned in ascending order with­out gaps.
<i> may be omitted in the case it is 1.
AppChannelTable String Mandatory entry
Refers to a section with defined channel names in APPLICATION.INI.
Simulation 0 / 1 Optional entry
Blocks the simulation of the entered devices (value = 0).
Enables simulation of the entered devices (value = 1).
Default = 0
Trace 0 / 1 Optional entry
Blocks the tracing function of the library (value = 0).
Enables the tracing function of the library (value = 1).
Default = 0
ChannelTableCaseSensitive 0 / 1 Optional entry
The channel names in the chan­nel table are treated case-sensi­tive (value = 1) or case-insensitive (value = 0).
Section [io_channel->...]
Contains a list of user-specific channel names (or ATG-defined channel names) which are assigned to the physical device names and to the physical device channel names. The defined names apply only to the relevant application. For details about channel name syntax see Chapter 8.3.4, "Channel tables", on page 114.
Keyword Value Description
<user-defined name> String Physical channel description in
the form: <device name>!<device channel name>.
96User Manual 1143.6450.42 ─ 26
Page 97
R&S®GTSL
7.2.1.4 Functions
Test Libraries
In-Circuit Test Libraries
Setup ICCHECK_Setup
Cleanup ICCHECK_Cleanup
Library Version ICCHECK_Lib_Version
Program Control
Load Program ICCHECK_Load_Program
Run Program ICCHECK_Run_Program
Debug Program ICCHECK_Debug_Program
Report Generation
Write Report to File ICCHECK_Write_Report
Load Detailed Report ICCHECK_Load_Detailed_Report
Get Detailed Report Entry ICCHECK_Get_Detailed_Report_Entry
Attribute Information
Get Attribute Int ICCHECK_Get_Attribute_Int
Get Attribute Real ICCHECK_Get_Attribute_Real
Get Attribute String ICCHECK_Get_Attribute_String

7.2.2 In-Circuit-Test Library

7.2.2.1 General
Name of the dynamic link library (DLL):
Name of the help file: ICT.HLP, ICT.CHM
License required R&S TS-LBAS and
Supported devices: R&S TS-PICT ICT Extension Module
The in-circuit test library offers functions for the in-circuit test using the R&S GTSL soft­ware and the R&S TS-PSAM, R&S TS-PICT, R&S TS PSU, R&S TS-PSU12 and R&S TS-PMB modules.
The functions allow to
ICT.DLL
R&S TS-LEGT or R&S TS-LEG2
R&S TS-PMB Matrix Module
R&S TS-PSAM Source and Measurement Module
R&S TS-PSU Power Supply / Load Module
R&S TS-PSU12 Power Supply / Load Module 12V
●
load, run and debug ICT programs
●
load limit files
●
generate a report
7.2.2.2 Entries in PHYSICAL.INI
Section [device->...]
97User Manual 1143.6450.42 ─ 26
Page 98
R&S®GTSL
Test Libraries
In-Circuit Test Libraries
Keyword Value Description
Type String Mandatory entry
pict = R&S TS-PICT ICT Exten­sion Module
pmb = R&S TS-PMB Matrix Mod­ule
psam = R&S TS-PSAM Source and Measurement Module
psu = R&S TS-PSU Power Sup­ply/Load Module
psu12 = R&S TS-PSU12 Power Supply/Load Module 12V
ResourceDesc String Mandatory entry
VISA resource descriptor in the form
PXI[segment number]:: [device number]:: [function]::INSTR
CAN[board]:: [controller]::[frame]:: [slot]
DriverPrefix String Mandatory entry
Prefix for the IVI driver functions, without underscore:
R&S TS-PICT : rspict
R&S TS-PMB : rspmb
R&S TS-PSAM : rspsam
R&S TS-PSU: rspsu
R&S TS-PSU12: rspsu
DriverDLL String Mandatory entry
File name of the driver DLL
R&S TS-PICT : rspict.dll
R&S TS-PMB : rspmb.dll
R&S TS-PSAM : rspsam.dll
R&S TS-PSU : rspsu.dll
R&S TS-PSU12 : rspsu.dll
DriverOption String Optional entry
Option string being passed to the device driver during the Driver_Init function. See the online help file for the appropriate device driver.
7.2.2.3 Entries in APPLICATION.INI
Section [bench->...]
98User Manual 1143.6450.42 ─ 26
Page 99
R&S®GTSL
Test Libraries
In-Circuit Test Libraries
Keyword Value Description
ICTDevice1 String Mandatory entry
Refers to the device section of the R&S TS-PSAM
ICTDevice2 String Optional entry
Refers to the device section of the R&S TS-PICT or R&S TS-PSU / R&S TS-PSU12
ICTDevice3 String Optional entry
Refers to the device section of the R&S TS-PICT or R&S TS-PSU / R&S TS-PSU12
SwitchDevice<i> String Mandatory entry
Refers to a section with switch devices in PHYSICAL.INI.
<i> stands for a number from 1,2,3,...,n. The numbers must be assigned in ascending order with­out gaps.
<i> may be omitted in the case it is 1.
AppChannelTable String Mandatory entry
Refers to a section with defined channel names in APPLICATION.INI.
Simulation 0 / 1 Optional entry
Blocks the simulation of the entered devices (value = 0). Ena­bles simulation of the entered devices (value = 1).
Default = 0
Trace 0 / 1 Optional entry
Blocks the tracing function of the library (value = 0). Enables the tracing function of the library (value = 1).
Default = 0
ChannelTableCase Sensitive 0 / 1 Optional entry
The channel names in the chan­nel table are treated case-sensi­tive (value = 1) or case-insensitive (value = 0).
Section [io_channel->...]
Contains a list of user-specific channel names (or ATG-defined channel names) which are assigned to the physical device names and to the physical device channel names. The defined names apply only to the relevant application. For details about channel name syntax see Chapter 8.3.4, "Channel tables", on page 114.
99User Manual 1143.6450.42 ─ 26
Page 100
R&S®GTSL
7.2.2.4 Functions
Test Libraries
In-Circuit Test Libraries
Keyword Value Description
<user-defined name> String Physical channel description in
the combination <device name>! <device channel name>
Setup ICT_Setup
Library Version ICT_Lib_Version
EGTSL Runtime Version ICT_Runtime_Version
Program Control
Load Program ICT_Load_Program
Run Program ICT_Run_Program
Debug Program ICT_Debug_Program
Unload Program ICT_Unload_Program
Report Generation
Write Report to File ICT_Write_Report
Load Detailed Report ICT_Load_Detailed_Report
Get Detailed Report Entry ICT_Get_Detailed_Report_Entry
Get Detailed Report Entry (Extended)
ICT_Get_Detailed_Report_Entry_Ex
Get TestStand Report Entry ICT_Get_TestStand_Report_Entry
Transfer Report to QUOTIS ICT_Transfer_Quotis_Report
Limit Loader
Load Limits ICT_Load_Limits
Error Handling
Get Error Log ICT_Get_Error_Log
Cleanup ICT_Cleanup

7.2.3 Vacuum Control Library

7.2.3.1 General
Name of the dynamic link library (DLL):
Name of the help file: VACUUM.HLP, VACUUM.CHM
License required: R&S TS-LBAS
Supported devices: R&S TS-PSYS1, System Module R&S TS-PSYS2,
The Vacuum Library offers functions for one or more vacuum control units R&S TS­PVAC.
VACUUM.DLL
System Module
100User Manual 1143.6450.42 ─ 26
Loading...
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use