SAT TOOLBOX II

User Manual

© 2003 by VA TECH SAT GmbH & Co

All rights reserved.

Any kind of disclosure and reproduction

whatsoever of this document or of parts thereof is
permitted only upon prior written consent by
VA TECH SAT.

Technical specifications are used for purposes of

product description only and are not guaranteed
specifications in the legal sense. Subject to
modifications - also with regard to technology.
 Identification TB2BH.105

Version.Revision 1.05.

Issuing date 23.07.2003

This document is applicable to the following product(s):

SAT TOOLBOX II Version 3.11

ii D30-500-1.05 TOOLBOX II Users Manual

 Table of Contents

Table of Contents

1. General................................................................................................................1-1
1.1. Supported operating systems...................................................................................................1-1
1.2. Login .........................................................................................................................................1-2
1.3. Administration of TOOLBOX II .................................................................................................1-3
1.3.1. Reorganising the database...............................................................................................1-3
1.3.2. TBIIPING...........................................................................................................................1-3
1.3.3. Region numbers support for SK and AM/SK-Mode..........................................................1-3
1.4. Spreadsheet function................................................................................................................1-5
1.4.1. The filter ............................................................................................................................1-5
1.4.2. Format columns ................................................................................................................1-5
1.4.3. Cut, Copy, insert values....................................................................................................1-6
1.4.4. Fill down,up,value, Autoincrement....................................................................................1-6
1.4.5. Search, Search and replace .............................................................................................1-6
1.4.6. Hide columns, Unhide columns ........................................................................................1-6
1.4.7. Fix range ...........................................................................................................................1-6
1.4.8. Sort....................................................................................................................................1-7
1.5. Selection ...................................................................................................................................1-8

2. web.engineering.................................................................................................2-1
2.1. Configuration ............................................................................................................................2-1
2.2. Use local serial port for loading ................................................................................................2-5

3. OPM II..................................................................................................................3-1
3.1. General .....................................................................................................................................3-1
3.1.1. Icons and Colours .............................................................................................................3-1
3.1.2. View ..................................................................................................................................3-3
3.1.3. Wizard...............................................................................................................................3-5
3.1.4. Plugins ..............................................................................................................................3-8
3.1.5. Acknowledgement dialog................................................................................................3-11
3.1.6. Menu Extras....................................................................................................................3-12
3.1.6.1. Automatic saving.....................................................................................................3-12
3.1.6.2. Options ....................................................................................................................3-12
3.1.7. Quick Reference .............................................................................................................3-16
3.1.8. Documentation................................................................................................................3-18
3.2. Images ....................................................................................................................................3-20
3.2.1. Overview .........................................................................................................................3-20
3.2.2. Handling..........................................................................................................................3-21
3.2.3. Typless images overview................................................................................................3-23
3.2.4. Typless Images handling ................................................................................................3-24
3.2.5. Hiding of link images.......................................................................................................3-26
3.2.6. Dynamic link images .......................................................................................................3-28
3.2.7. Create Images with pre and suffix ..................................................................................3-29
3.2.8. Change Order .................................................................................................................3-31
3.2.9. Search, Sorting and Order in the Tree............................................................................3-32
3.3. Typs ........................................................................................................................................3-33
3.3.1. Handling..........................................................................................................................3-33
3.3.2. Structure .........................................................................................................................3-34
3.3.3. User types overview........................................................................................................3-35
3.3.4. User types handling ........................................................................................................3-36
3.3.5. Linktypes overview..........................................................................................................3-37
3.3.6. Linktypes handling ..........................................................................................................3-38
3.3.7. Info types overview .........................................................................................................3-39
3.3.8. Infotypes handling...........................................................................................................3-40
3.3.9. Parameter types..............................................................................................................3-42

TOOLBOX II Users Manual D30-500-1.05 iii

 Table of Contents

3.3.10. Parameter Type Handling .............................................................................................. 3-44

3.4. Assign .................................................................................................................................... 3-45
3.4.1. Overview ........................................................................................................................ 3-45
3.4.2. Handling ......................................................................................................................... 3-47
3.4.3. Partly categorized woking with 1703.............................................................................. 3-48
3.5. Default values ........................................................................................................................ 3-49
3.5.1. Overview ........................................................................................................................ 3-49
3.5.2. Handling ......................................................................................................................... 3-50
3.5.3. Transfer.......................................................................................................................... 3-51
3.5.4. Wizard ............................................................................................................................ 3-53
3.6. Elcad ...................................................................................................................................... 3-54
3.6.1. Overview ........................................................................................................................ 3-54
3.6.2. Handling ......................................................................................................................... 3-55
3.6.3. Requirements................................................................................................................. 3-56
3.7. Formulae................................................................................................................................ 3-57
3.7.1. Overview ........................................................................................................................ 3-57
3.7.2. Handling ......................................................................................................................... 3-60
3.7.3. Performance................................................................................................................... 3-61
3.7.4. Formula editor ................................................................................................................ 3-62
3.7.5. Cascading of references and formulae .......................................................................... 3-64
3.7.6. Mathematic functions ..................................................................................................... 3-65
3.7.6.1. ABS() ...................................................................................................................... 3-65
3.7.6.2. DIV() ....................................................................................................................... 3-65
3.7.6.3. INT() ....................................................................................................................... 3-65
3.7.6.4. MOD()..................................................................................................................... 3-65
3.7.6.5. ROUND() ................................................................................................................ 3-66
3.7.6.6. TRUNC()................................................................................................................. 3-66
3.7.6.7. HSTR(Number, [width]) .......................................................................................... 3-66
3.7.7. String functions .............................................................................................................. 3-67
3.7.7.1. CONCAT() .............................................................................................................. 3-67
3.7.7.2. EXACT() ................................................................................................................. 3-67
3.7.7.3. FIND()..................................................................................................................... 3-67
3.7.7.4. HSTR() ................................................................................................................... 3-67
3.7.7.5. LEFT() .................................................................................................................... 3-68
3.7.7.6. LEN() ...................................................................................................................... 3-68
3.7.7.7. LOWER() ................................................................................................................ 3-68
3.7.7.8. MID()....................................................................................................................... 3-68
3.7.7.9. REPLACE() ............................................................................................................ 3-69
3.7.7.10. SEARCH() .............................................................................................................. 3-69
3.7.7.11. SUBST() ................................................................................................................. 3-69
3.7.7.12. T() ........................................................................................................................... 3-69
3.7.7.13. TRIM() .................................................................................................................... 3-70
3.7.7.14. UPPER()................................................................................................................. 3-70
3.7.7.15. VALUE() ................................................................................................................. 3-70
3.7.8. Control functions ............................................................................................................ 3-71
3.7.8.1. IF() .......................................................................................................................... 3-71
3.7.9. OPM specific functions................................................................................................... 3-72
3.7.9.1. GET ()..................................................................................................................... 3-72
3.7.9.2. GET (RELATIVE) ................................................................................................... 3-72
3.7.9.3. GETCAE () ............................................................................................................. 3-72
3.7.9.4. GETCAE (RELATIVE)............................................................................................ 3-72
3.7.9.5. GETINFO () ............................................................................................................ 3-73
3.7.9.6. GETINFO (RELATIVE)........................................................................................... 3-73
3.7.9.7. GETNAME () .......................................................................................................... 3-73
3.7.9.8. GETNAME_EX()..................................................................................................... 3-73
3.7.9.9. GETNAME_EXDN() ............................................................................................... 3-73
3.7.9.10. GETNAME_EXUP()................................................................................................ 3-73
3.7.9.11. GETPEA ().............................................................................................................. 3-74
3.7.9.12. GETPEA _EX()....................................................................................................... 3-74

iv D30-500-1.05 TOOLBOX II Users Manual

 Table of Contents

3.7.9.13. GETWLS ()..............................................................................................................3-74

3.7.9.14. GETWLS (RELATIVE) ............................................................................................3-74
3.7.9.15. CONCATBIN ()........................................................................................................3-74
3.7.9.16. GETprep() ...............................................................................................................3-75
3.7.9.17. LEVEL()...................................................................................................................3-75
3.7.9.18. LEVELROOT() ........................................................................................................3-76
3.7.9.19. LEVELDISTROOT() ................................................................................................3-76
3.7.9.20. GetBinInfo(Infotype, StartBit, NoOfBits)..................................................................3-77
3.7.9.21. GetBin(Parameter, StartBit, NoOfBits)....................................................................3-77
3.7.9.22. CONCATBIN(Par1, Bits1 [, Par2, Bits2, ...]) ...........................................................3-77
3.7.9.23. CONCATBIN(Par1, Bits1 [, Par2, Bits2, ...]) ...........................................................3-78
3.7.9.24. IOM(Parameter1, Width1 [, Parameter2, Width2, ...]).............................................3-78
3.7.9.25. IOMInfo(Infotype1, Width1 [, Infotype2, Width2, ...])...............................................3-78
3.8. Levels .....................................................................................................................................3-79
3.8.1. Overview .........................................................................................................................3-79
3.8.2. Handling..........................................................................................................................3-80
3.9. Library.....................................................................................................................................3-81
3.9.1. AU objects overview .......................................................................................................3-81
3.9.2. AU objects handling ........................................................................................................3-82
3.10. Bulk editing .............................................................................................................................3-84
3.10.1. Overview .........................................................................................................................3-84
3.10.2. Handling..........................................................................................................................3-85
3.10.2.1. Drag&Drop of Images in the Mass Editing..............................................................3-85
3.10.2.2. Drag&Drop of Types in the Mass Editing................................................................3-85
3.10.2.3. VTA Search Expression ..........................................................................................3-86
3.10.2.4. Drag&Drop a parameter from the Image ................................................................3-87
3.10.2.5. Selection of a parameter from the Edit Type (parameter tab) ................................3-87
3.10.2.6. Drag&Drop from the System Engineering in the Mass Editing ...............................3-88
3.10.3. User interface..................................................................................................................3-89
3.10.4. Wildcard selection...........................................................................................................3-90
3.10.5. Column layout .................................................................................................................3-92
3.10.5.1. Saving a Column Layout .........................................................................................3-92
3.10.5.2. Deletion of a Column Layout...................................................................................3-92
3.10.5.3. Selection of a Column Layout .................................................................................3-93
3.11. Source data management ......................................................................................................3-94
3.11.1. Overview .........................................................................................................................3-94
3.11.2. Import..............................................................................................................................3-96
3.11.2.1. Functions when importing .......................................................................................3-96
3.11.2.1.1. Event Log ........................................................................................................3-97
3.11.2.1.2. Formulas/References ......................................................................................3-97
3.11.2.1.3. Change Report ................................................................................................3-97
3.11.2.2. Log file.....................................................................................................................3-98
3.11.2.2.1. The "EOW_IN.DAT" File..................................................................................3-99
3.11.2.3. Separating Character ............................................................................................3-100
3.11.2.4. Preprocess and Postprocess ................................................................................3-101
3.11.2.5. SDM Settings ........................................................................................................3-101
3.11.2.6. Compatibility with Toolbox Version 3.10 ...............................................................3-102
3.11.2.7. Across-range Importing.........................................................................................3-103
3.11.3. Export............................................................................................................................3-104
3.11.3.1. Functions when exporting .....................................................................................3-104
3.11.3.2. Log file...................................................................................................................3-106
3.11.3.2.1. The "EOW_OUT.DAT" File............................................................................3-107
3.11.3.3. Postprocess...........................................................................................................3-107
3.11.3.4. Separation Characters ..........................................................................................3-108
3.11.3.5. SDM Settings ........................................................................................................3-109
3.11.3.6. Compatibility with Toolbox Version 3.10 ...............................................................3-110
3.11.3.7. Distributed Working...............................................................................................3-111
3.11.4. SDC Source Data Manager Commandline...................................................................3-112
3.11.4.1. Importing ...............................................................................................................3-112

TOOLBOX II Users Manual D30-500-1.05 v

 Table of Contents

3.11.4.2. Exporting .............................................................................................................. 3-113

3.11.5. Common OPM-Format (COF)...................................................................................... 3-114
3.11.5.1. "Fixed" Columns ................................................................................................... 3-115
3.11.5.1.1. The "FUNC" Column..................................................................................... 3-115
3.11.5.1.2. The "RANGE" Column.................................................................................. 3-116
3.11.5.1.3. The "Level Columns" .................................................................................... 3-116
3.11.5.1.4. The "NEWNAME" Column............................................................................ 3-116
3.11.5.1.5. The "DEFAULT" Column .............................................................................. 3-116
3.11.5.2. "Free" Columns .................................................................................................... 3-117
3.11.5.3. Example of the Structure of a COF File ............................................................... 3-117
3.11.6. Functions...................................................................................................................... 3-118
3.11.6.1. Overview of all functions ...................................................................................... 3-118
3.11.6.2. Update values....................................................................................................... 3-120
3.11.6.3. Create typeless images........................................................................................ 3-122
3.11.6.4. Create type images .............................................................................................. 3-123
3.11.6.4.1. Create a Typed Image by Means of Default Input........................................ 3-123
3.11.6.4.2. Create a Typed Image with Default Input and Update Values ..................... 3-125
3.11.6.5. Delete images....................................................................................................... 3-126
3.11.6.6. Rename images ................................................................................................... 3-127
3.11.6.6.1. Rename an Image ........................................................................................ 3-127
3.11.6.6.2. Rename an Image and Update Values ........................................................ 3-127
3.11.6.7. Create info types .................................................................................................. 3-128
3.12. Source data management up to V3.10 ................................................................................ 3-130
3.12.1. Overview ...................................................................................................................... 3-130
3.12.2. Import ........................................................................................................................... 3-131
3.12.3. COF format .................................................................................................................. 3-132
3.13. References........................................................................................................................... 3-133
3.13.1. Overview ...................................................................................................................... 3-133
3.13.2. Handling ....................................................................................................................... 3-135
3.13.3. Hide reference targets.................................................................................................. 3-137
3.14. System technique ................................................................................................................ 3-138
3.14.1. Overview ...................................................................................................................... 3-138
3.14.2. 1703 ACP - mode......................................................................................................... 3-139
3.14.3. BC 1703 ACP image parametrization .......................................................................... 3-140
3.14.3.1. Overview............................................................................................................... 3-140
3.14.3.1.1. Display and Display Elements ...................................................................... 3-140
3.14.3.2. Handling ............................................................................................................... 3-143
3.14.3.2.1. Starting the display parameterizing .............................................................. 3-143
3.14.3.2.2. Terminating the display parameterizing........................................................ 3-143
3.14.3.2.3. Display parameterizing ................................................................................. 3-143
3.14.3.3. Creating and Editing a Display ............................................................................. 3-144
3.14.3.4. Assignment to Display Elements.......................................................................... 3-150
3.14.3.5. Tool Display overview........................................................................................... 3-152
3.14.3.6. Tool Templates overview ..................................................................................... 3-155
3.14.3.7. Font ...................................................................................................................... 3-157
3.14.3.7.1. Structure of a Font-Bitmap............................................................................ 3-157
3.14.3.8. Display Element Text ........................................................................................... 3-159
3.14.3.9. Display Element Measured Value ........................................................................ 3-160
3.14.3.10. Construction of Measured-Value Bitmaps............................................................ 3-162
3.14.3.11. Display Element Symbol ...................................................................................... 3-164
3.14.3.11.1. Construction and Display of Operational-Equipment Symbol-Bitmaps ........ 3-165
3.14.3.12. Display Element LED............................................................................................ 3-167
3.14.3.13. Display Element Keyswitch .................................................................................. 3-168
3.14.3.14. Display Element Function Key ............................................................................. 3-169
3.14.4. BC 1703 ACP matrix .................................................................................................... 3-170
3.14.4.1. Overview............................................................................................................... 3-170
3.14.4.1.1. The Matrix ..................................................................................................... 3-170
3.14.4.2. Handling ............................................................................................................... 3-172
3.14.4.2.1. Starting the Matrix......................................................................................... 3-172

vi D30-500-1.05 TOOLBOX II Users Manual

 Table of Contents

3.14.4.2.2. Expanding and Compressing the Matrix .......................................................3-173

3.14.4.2.3. Setting, Inverting and Deleting Node Points of the Matrix.............................3-174
3.14.4.2.4. Properties for inputs and outputs ..................................................................3-175
3.14.4.2.5. Terminating the Matrix...................................................................................3-177
3.14.5. 1703 Ax - mode.............................................................................................................3-178
3.14.6. 1703 SK - mode ............................................................................................................3-179
3.14.7. Start of CAEx II .............................................................................................................3-180
3.14.8. Start of CAEx plus.........................................................................................................3-181
3.14.9. Navigate to an image ....................................................................................................3-182
3.14.10. Visibility of automation units .........................................................................................3-183
3.14.11. Detail routing.................................................................................................................3-184
3.14.12. Global detail routing export/import................................................................................3-185
3.14.13. Definition of regions and automation units ...................................................................3-188
3.14.14. Copy of automation units ..............................................................................................3-190
3.14.15. Customer parameter sets .............................................................................................3-192
3.14.16. Broadcast parametrizing ...............................................................................................3-193
3.14.17. Profibus parametrizing ..................................................................................................3-194
3.14.18. Documentation..............................................................................................................3-196
3.15. Transform and load ..............................................................................................................3-197
3.15.1. Overview .......................................................................................................................3-197
3.15.1.1. Loading..................................................................................................................3-198
3.15.2. When must be converted and loaded? .........................................................................3-199
3.15.3. SAT 250 ........................................................................................................................3-200
3.15.3.1. Link Images...........................................................................................................3-200
3.15.3.2. Handling ................................................................................................................3-200
3.15.3.3. Functions...............................................................................................................3-201
3.15.4. SAT 230 ........................................................................................................................3-203
3.15.4.1. Link Images...........................................................................................................3-203
3.15.4.2. Handling ................................................................................................................3-203
3.15.4.3. Functions...............................................................................................................3-204
3.15.5. SAT 1703 ......................................................................................................................3-206
3.15.5.1. Link Images...........................................................................................................3-206
3.15.5.2. Handling ................................................................................................................3-207
3.15.5.3. Functions...............................................................................................................3-207
3.15.6. CAEx II ..........................................................................................................................3-209
3.15.6.1. OPM II Destination Systems .................................................................................3-209
3.15.6.2. Link Images...........................................................................................................3-209
3.15.6.3. Handling ................................................................................................................3-210
3.15.6.4. Functions - Generate assignment code ...............................................................3-211
3.15.6.5. Functions - Generate IOM File.............................................................................3-212
3.15.7. CAEx plus .....................................................................................................................3-213
3.15.7.1. OPM II Destination Systems .................................................................................3-213
3.15.7.2. Link Images...........................................................................................................3-213
3.15.7.3. Handling ................................................................................................................3-214
3.15.7.4. Functions...............................................................................................................3-214

4. Assembly technique documentation................................................................4-1

4.1. Overview...................................................................................................................................4-1
4.2. Handling....................................................................................................................................4-4
4.3. Description of columns .............................................................................................................4-5

5. Data Distribution Center....................................................................................5-1

5.1. Overview...................................................................................................................................5-1
5.2. Handling....................................................................................................................................5-3
5.3. Automatic backup .....................................................................................................................5-7

6. CAEx plus ...........................................................................................................6-1

6.1. Overview...................................................................................................................................6-1

TOOLBOX II Users Manual D30-500-1.05 vii

 Table of Contents

6.2. Periodical to spontaneous data ............................................................................................... 6-4

6.3. Update Signal List.................................................................................................................... 6-5

7. CAEx II ................................................................................................................ 7-1

7.1. Status bits ................................................................................................................................ 7-1
7.2. Print.......................................................................................................................................... 7-3
7.3. MK and uK Support.................................................................................................................. 7-4

8. Data flow test ..................................................................................................... 8-1

8.1. Overview .................................................................................................................................. 8-1
8.2. Handling................................................................................................................................... 8-4
8.3. RTU filter.................................................................................................................................. 8-5
8.4. TBII filter................................................................................................................................... 8-6
8.5. Blocked data formats ............................................................................................................... 8-7

9. Diagnostic .......................................................................................................... 9-1

9.1. Overview .................................................................................................................................. 9-1
9.2. Handling................................................................................................................................... 9-3

10. Load firmware .................................................................................................. 10-1

10.1. Overview ................................................................................................................................ 10-1
10.2. Handling................................................................................................................................. 10-2

11. Plant management........................................................................................... 11-1

11.1. Overview ................................................................................................................................ 11-1
11.2. Handling................................................................................................................................. 11-3
11.3. Process-technical plants copy ............................................................................................... 11-5
11.4. Range copy............................................................................................................................ 11-6

12. HW-FW Configuration ..................................................................................... 12-1

12.1. Overview ................................................................................................................................ 12-1
12.2. Handling................................................................................................................................. 12-3
12.3. Grants for parametrization ..................................................................................................... 12-4

13. Master data update.......................................................................................... 13-1

13.1. Overview ................................................................................................................................ 13-1

14. ST emulation .................................................................................................... 14-1

14.1. Overview ................................................................................................................................ 14-1
14.2. Handling................................................................................................................................. 14-7

15. Service function online ................................................................................... 15-1

15.1. Overview ................................................................................................................................ 15-1
15.2. Handling................................................................................................................................. 15-2
15.3. Load the display for BC 1703 Ax ........................................................................................... 15-3

16. Parameterization.............................................................................................. 16-1

16.1. Overview ................................................................................................................................ 16-1
16.2. Handling................................................................................................................................. 16-3
16.3. Redundant operation of base system elements .................................................................... 16-5

17. Parameter Loader ............................................................................................ 17-1

17.1. Overview ................................................................................................................................ 17-1
17.1.1. Load Parameters............................................................................................................ 17-1
17.1.2. Parameter comparison................................................................................................... 17-2
17.2. Handling................................................................................................................................. 17-3

viii D30-500-1.05 TOOLBOX II Users Manual

 Table of Contents

18. Revision interrogation and display ................................................................18-1

18.1. Overview.................................................................................................................................18-1
18.2. Handling..................................................................................................................................18-3

19. Topology test....................................................................................................19-1

19.1. Overview.................................................................................................................................19-1
19.2. Handling..................................................................................................................................19-2

20. Message simulation .........................................................................................20-1

20.1. Overview.................................................................................................................................20-1

21. Toolbox II presets ............................................................................................21-1

21.1. Overview.................................................................................................................................21-1
21.2. Handling..................................................................................................................................21-3

22. Workgroups (Teamwork).................................................................................22-1

22.1. Overview.................................................................................................................................22-1
22.2. Distributed working .................................................................................................................22-3
22.2.1. Overview .........................................................................................................................22-3
22.2.1.1. System technique (Automation Units).....................................................................22-3
22.2.1.2. Process-Engineering Plant (VAN)...........................................................................22-4
22.2.1.3. Ranges of a Process-Engineering Plant .................................................................22-4
22.2.2. Handling..........................................................................................................................22-7
22.2.2.1. Export of OPM Data (process-engineering)............................................................22-7
22.2.2.2. Import of OPM Data (process-engineering) ............................................................22-7
22.2.2.3. Export of AU Data (system-engineering) ................................................................22-8
22.2.2.4. Import of AU Data (system-engineering) ................................................................22-9
22.2.3. Examples ......................................................................................................................22-10
22.2.3.1. One Range, 2 Users working with SAT 1703 and SAT 200 .................................22-10
22.2.3.2. One Range, 2 Users working on different AU's ....................................................22-11
22.2.3.3. 2 Ranges with higher-level SAT 200.....................................................................22-12
22.2.3.4. Creating New Images in a Range Copy................................................................22-13
22.2.3.5. Function Diagrams in CAEx plus ..........................................................................22-14

23. Parameter documentation ...............................................................................23-1

23.1. General parameters................................................................................................................23-1
23.1.1. Lk_Prep...........................................................................................................................23-1

TOOLBOX II Users Manual D30-500-1.05 ix

 General

1. General

1.1. Supported operating systems

The TOOLBOX II supports the following operating systems:

N Windows NT

N Windows 2000 Professionell

N Windows 2000 Server

N Windows 2000 Server with Terminal Services (see web.engineering)

N Windows XP Professionell

N Windows 2003 Server

N Windows 2003 Server with Terminal Services (see web.engineering)

TOOLBOX II Users Manual D30-500-1.05 1-1

 General

1.2. Login

The obligation of having to enter user name and password protects access to the use of a TOOLBOX II
tool.

N Licensed for
Display of licensing information

N User name
Name of user
In the presets, new users can be created or existing ones be changed.

N Password
The password is not shown on the user interface.
In the presets, it is possible to create new passwords or change existing ones. The definition of a
password is optional

1-2 D30-500-1.05 TOOLBOX II Users Manual

 General

1.3. Administration of TOOLBOX II

In the following, individual functions for the TOOLBOX Administration are described.

1.3.1. Reorganising the database

By reorganising the database, the data-stock of the Toolbox II Database are optimised. For intensive
work with the TOOLBOX II this function should be started weekly. Through this a considerable
improvement in performance can be achieved. A dialog will be shown after one week during the
TOOLBOX II startup, if this reorganisation is not done.

TOOLBOX II | TOOLBOX II PRESETS | REORGANISING THE DATABASE

The duration of the reorganisation is dependant on the amount of data

For reorganising a Peer-Server/TerminalServer, this function must be started directly on Peer-Server or
Terminalserver. If the Peer-Server database is accessed at this moment, the reorganisation stops. The
function is then only continued if no Client is working on the database.

This function can also executed by starting

INDEX_REORG.EXE

in a command line. A log file will be written to %TEMP%\index_reorg with the filename index_reorg.log .

1.3.2. TBIIPING

The environment variable LOCAL states which TOOLBOX II Database is checked. To check a particular
database it is necessary to set this environment variable in the same DOS window.

The database TOOLBOX II is to be checked. SET LOCAL=TBII, TBIIPING

1.3.3. Region numbers support for SK and AM/SK-Mode

Is used if AUs of the Type SK1703, AMx/SK-Mode are used with the same component number in
different regions, it is now possible to clearly address these AUs.

TOOLBOX II Users Manual D30-500-1.05 1-3

 General

An AU is clearly identified by the AU-Key (system-technical plant-ID, Region number, Component

number and Module number). To identify the directly connected AU, the AU-key must be read back to
the TOOLBOX II from the destination system. Presently, from an SK1703 or AMx 1703/SK-Mode only
the component number and module number can be read back. When installing new AU's in addition to
the component number and module number, the system-technical plant-Id and region number are also
automatically entered in the destination system parameters. When establishing connection between the
TOOLBOXII and the destination system, the AU-Key is read from the local AU and subsequently
checked, whether this AU belongs to the default system-technical plant. If this is not the case, the
connection to the destination system is disconnected and a corresponding error information output.
Exceptions are the "ST-Emulation" and "Initialising parameter loader functionality of local AU". In these
cases no check is carried out. For AU's, for which this information is not yet contained in the destination
system parameters, as previously the default system-technical plant-Id for this AU is adopted and as
region number the region number of the first AU found with the same component number and AU-type
is adopted from the plant management.

Note: For all TOOLBOX II Online tools, the region number and system-technical plant is only checked
for the directly connected AU (SK1703, AMx/SK-Mode). All remote functions evaluate as previously just
the component number (Virtuale module number).

If these above mentioned modules were installed with an older version than TBII 2.40 the following is to
be carried out:

No automatic "Update" of the destination system parameters is carried out. A Command-line tool
(SATSETREG.exe) is provided with which the system-technical plant-Id and region number are entered
in the destination system parameters for an entire system-technical plant.

The transfer parameter for this tool is the system-technical plant-Id. The short text and long text of this
system-technical plant is then output and the user is offered the possibility of aborting the procedure. If
the user continues, first whether the parameters of all AU's exist as original is checked. If this is not the
case, no modification of the destination system parameters takes place and the procedure is terminated
with a corresponding error information.

Incompatibility:

Since the system-technical plant-Id and region number in AMx 1703/SK-Mode are stored in a new
parameter block, the firmware data are no longer backwards-compatible (PSR-I does not "know" these
new parameter blocks). Asa result it is no longer possible to use the AU-parameters of the TOOLBOX-II
in PSR-I.

The individual functions of SATSETREG.exe:

SATSETREG /I [Inputfile]... The Inputfile is structured as follows: Reg# ; Comp# ; Bg# These must be
separated by ; It is also possible to use Wildcards (*)

SATSETREG /L outputs a list of all AUs, that do not yet have the R# stored in the destination system.

SATSETREG /H displays the help for SETREG.

SATSETREG /F [Logfile] specifies the LOG-File incl. path.

IMPORTANT: After using this function the modified components MUST be loaded.

1-4 D30-500-1.05 TOOLBOX II Users Manual

 General

1.4. Spreadsheet function

1.4.1. The filter

In the spreadsheet, filtering can take place using the following possibilities

N Flashfilter
Mark a cell content and start the function Flashfilter via the Pop Up Menu
Filter | Flashfilter
or Smart Icon. Only those linesare displayed that correspond to the selected content.
Note: Only the content of complete cells can be selected.

N Set filter
Mark one or more columns. Set filter function via Pop Up
Filter | set filter
or start Smart Icon.
The selected columns are displayed in a dialogue. The filter text can be entered in the column
content of this dialogue.
If the option "filter only for complete cells" is specified, then the filter text must match the content
of the complete cell. If this option is not set, then partial contents are also compared and
displayed.
Note: Wildcards (*, ? ..) are not allowed.
If the option "filter out empty cells" is specified, then rows with empty cells are also filtered out.
Thereby only the columns visible in the dialogue are taken into account.
If the option "filter out cellswith "-" "is specified, then rows with cells that contain the character "--
"are also filtered out. Thereby only the columns visible in the dialogue are taken into account.

N Filtering columns
By double-clicking on the column heading, a filter text can be entered directly. Only rows that
match partial contents of the filter text are displayed.
Note: Wildcards (*, ? ..) are not allowed

N Unique Filter
Mark one or more columns and start the function Uniquefilter via Pop Up Menu
Row filter - Uniquefilter
Only those rows with the same content are filtered out. Thereby only the selected columns are
taken into account.
Note: If several rows exist with the same content, then always only the first row is displayed in the
Spreadsheet.

1.4.2. Format columns

Via the Pop Up Menu

FORMAT COLUMNS

the cell display can be switched between fixed Font and proportional Font

TOOLBOX II Users Manual D30-500-1.05 1-5

 General

1.4.3. Cut, Copy, insert values

Via the Pop Up Menu

CUT, COPY, INSERT VALUES

values can be copies between cells.

1.4.4. Fill down,up,value, Autoincrement

By marking one or more columns or cells, via the Pop Up Menu

FILL

values can be filled.

1.4.5. Search, Search and replace

By marking one or more columns, via the Pop Up Menu

SEARCH, SEARCH AND REPLACE

values of the selected range can be searched for or via a dialogue, replaced with new values.
Note: No wildcards (*, ? ...) can be used.

1.4.6. Hide columns, Unhide columns

By marking one or more columns, via the Pop Up Menu

HIDE COLUMNS

All selected columns are hidden. Via the Menu item

UNHIDE COLUMNS

all or selective columns can be unhidden.

1.4.7. Fix range

By marking a cell and via the Pop Up Menu

FIX RANGE

above and left of the marked cell the spreadsheetis fixed. As a result during scrolling this range always
remains visible.

1-6 D30-500-1.05 TOOLBOX II Users Manual

 General

1.4.8. Sort

By marking one or several columns, via the Pop Up Menu

SORT

the entire spreadsheet is sorted

ASCENDING, DESCENDING, DEFINABLE

With the function definable, the order of the columns can be specified.
Note: If sorting according to the VTA , definable must always be used.

TOOLBOX II Users Manual D30-500-1.05 1-7

 General

1.5. Selection

N 2 columns are displayed; in the right column you can see various entries, in the left all those that
were selected.

N Several selection options can be used

Using the double arrow, you can move all entries to the side the arrow is pointing to
Using the single arrow, you will only move the selected entries
The wildcard search allows you to make a selection based on the parameter name

Click OK to finish the selection

1-8 D30-500-1.05 TOOLBOX II Users Manual

 web.engineering

2. web.engineering

2.1. Configuration

It is possible to operate the TOOLBOX II in Internet Explorer. All TOOLBOX II Clients thereby operate
with a centralTOOLBOX II Server

No installation is therefore required on the TOOLBOX II Client. The function can be used from Internet
Explorer 5.0 on.

As Server, a Windows 2000 Server withTerminal Server and WEB service must be installed
Subsequently, a normal TOOLBOX II Installation is carried out on this server. Important thereby is that
for each Client (minimal 2), that is to operate on this Server, an enabling must take place by entering a
WEB License.

The configuration on the Server.

The Server should beassigned a fixed IP address. If dynamic addressing must be used, then the name
of the Server must be able to be addressed by all Clients (Nameservices)

On the TOOLBOX II Installation- CD 1 there is a directory

WEB

This directory must be copied to an optional directory on the Server.

e.g.: C:\Inetpub\wwwroot

In this directory is the start file

index.htm

So that the Server uses this start file, the following configuration must be carried out:

START | SETTINGS | CONTROL PANEL | COMPUTER MANAGEMENT

TOOLBOX II Users Manual D30-500-1.05 2-1

 web.engineering

In this window, the Properties window for

SERVICES APPLICATIONS | INTERNET INFOMATION SERVICES | DEFAULT WEB SITE

must be opened. In the tab

HOME DIRECTORY

the previously copied directory must be specified.

2-2 D30-500-1.05 TOOLBOX II Users Manual

 web.engineering

Subsequently, the access authorisations must be defined, and a possible printer installed

The configuration on the Client

On the Client, in the Internet Explorer configurations

Activ-X and Cookies

must be allowed.

Start the TOOLBOX II on the Cient

On the Client the Internet Explorer must be opened, and the name of the server must be specified as
address. Thereby simply the name without "www" or "http" can be specified.

In Internet Explorer the start page then appears

WEB.ENGINEERING

As first step, the menu

CONFIGURATION

TOOLBOX II Users Manual D30-500-1.05 2-3

 web.engineering

is to be selected.

N Server: Name of the Server

N Domain: Network Domain

N Username: Name of the User as default setting for the Login dialogue

N Resolution: Setting the monitor resolution

N Full Screen : Full screen display ( can be switched over any time with the
strg alt pause key combination)

then via the menu item

START

the application is started.

2-4 D30-500-1.05 TOOLBOX II Users Manual

 web.engineering

2.2. Use local serial port for loading

If the TOOLBOX II is operated via Internet Explorer , then the local interface can be used for loading the
destination systemSAT 1703.

The Client PC thereby operates as Terminalserver, which uses the local serial port. In remote operation
the TCP/IP address of the Client PC is specified. The Port number can be freely configured on the
Client, and must match the definitions in the remote operation.

If the start page of the TOOLBOX Server is opened on the Client in Internet Explorer, via the Menu item

COMMUNICATION

a program can be started(JAVA Applet). this program is automatically loaded by the server during the
first start.

In this window

N Port number

N Port : Serial port

N Baud rate

N Frame: 8N1 (8 Data bit, No Parity, 1 Stopbit) for Ax and ACP

and 7O2 (7 Data bit, Odd Parity, 2 Stopbit) for SK - Mode

Via the button

START

the operation can be started.

TOOLBOX II Users Manual D30-500-1.05 2-5

 web.engineering

Via the display

OFFLINE / ONLINE

the status of the connection is represented.

As long as a connection to the destination via the serial port is required, this program must be running.

2-6 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3. OPM II

3.1. General

3.1.1. Icons and Colours

In the OPM II, types, images, default inputs, parameters and infotypes are distinguished by various
icons on the user interface.

Types

This icon marks the types.

This icon marks all displayed user types of a read range.

This icon marks all infotypes.

This icon marks all parameter types.

This icon marks parameters which do not correspond to the selected category (Lk_Kat) (e.g. the
Inversion parameter in a Command category).

Default inputs

This icon marks all default inputs.

Images

This icon marks all typed images which are not converted.

TOOLBOX II Users Manual D30-500-1.05 3-1

 OPM II

This icon marks all typed images which are completely converted (all converted SAT230 and SAT250
images as well as all 1703 images in which the 1703 part is converted, as well as the CAEx II or CAEx
plus periodic part)

This icon marks all typed images in which only the 1703 part has been converted. Note: if an image has
no parameters for CAEx periodic use and it is converted, then this icon also appears.

This icon marks all typed images in which only the CAEx periodic part of a 1703 image has been
converted.

This icon marks all typeless images .

Attribute Colours

Colours visualize the use of parameters or infotypes as the source or destination of a formula or
reference.

Colour Meaning

Black Attribute is neither a source nor a destination of a reference or formula.

Red Attribute is a source of a reference

Green Attribute is a destination of a reference

Dark blue Attribute is part of the link address

Grey Attribute is read only

Pink In this attribute a formula is defined

Light blue Attribute is an input for a formula

3-2 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.1.2. View

In the View-Menu there are various possible settings for simplifying the wortk with the OPM. These are
decribed here.

N Reference- and Formula-Mode

By selecting this entry the OPM can be switched to Reference and Formula Mode References
and Formulae can only be newly defined in this mode.

N Smarticons

With this option the display of Smart-Icons can be activated or deactivated.

N Error output

With this option the display of error output can be activated or deactivated. The error output
window is automatically reactivated by OPM with each destination system generation (regardless
of the setting)

N Read ranges

With this option the display of the read ranges can be switched on or off. The read ranges can be
added in the respective range, but made "invisible" with this option.

N Display Link addresses

With this setting it is possible to hide or unhide the Link addresses. If the Link addressis already
filled out, then this does not need to be changed any more and can therefore be hidden, which
leads to a simplified display of the OPM.

TOOLBOX II Users Manual D30-500-1.05 3-3

 OPM II

N Colour Reference sources

Wenn dieses Hakerl gesetzt ist werden die Quellen von Referenzen eingefärbt. Die Farben sind
unter Colors zu finden

N Referenzziele einfärben

If this tick is set the targets of the references are coloured in. The colours can be found under
Colors

N Colour Formula sources

If this tick is set all parameter that are input for a formula are coloured. The colours can be found
under Colors

N Colour Formula targets

If this tick is set all parameters that are calculated with a formula are coloured. The colours can
be found under Colors

N Display Tooltips

It is possible to hide the parameter Tooltips (brief help text)

N Display only default automation units

In the system technique, either all or only the default automation units are displayed. The
selection of the default AUs takes place in the Extras-Menu under "Default Automation Units"

N Display prepared Link images

In each signal it is possible to prepare the link images existing below. To obtain a better overview
it is possible to hide these prepared Link images Thus it is possible to form signal "over-types"
and to simply hide the links not required. As a result the clarity of these signal images is
considerably increased.

N Display targets of references and formulae

If a parameter is calculated with the help of a formula or formed as target of a reference , then it is
possible to hide these parameters from the image tree. With that only the sources of these are
now visible. The targets are automatically updated however, even if they are not visible. In the
mass editing, these non-visible attribute sare displayed on a grey background. With the source
data management however, all attributes are exported.

N Display only category-relevant parameters

In the OPM it is possible to display e.g. a single point informatiuon and a double-point information
in a link image. If e.g. categorising for the single-point informationtakes place, then all parameters
that cannot be parameterised fore a single-point information are greyed out. Now to obtain a
clearer overview, these geyed-out parameters (not belonging to the set category) can be hidden.
If the category is modified in retrospect, then automatically the respective parameters set for the
new category are displayed visible or invisible. Consequently it is possible to always display the
respective parameters for the set category, which greatly simplifies the work in OPM.

3-4 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.1.3. Wizard

If the OPM is started for the first time at a time when no customer and/or no plants have been created, a
wizard will pop up requesting you to make all the necessary entries.

The definition of the customer and the plants may now be entered directly in the OPM

The wizard is structured into several steps displayed on the right in a workflow diagram.

The first step is the definition of a customer

TOOLBOX II Users Manual D30-500-1.05 3-5

 OPM II

For this definition, it is possible to choose between an existing an a new customer. If the customer has
not yet been created in the database, it can be defined directly in this wizard.

Creating of a new customer:

N Name

Is the customer name

N Other customer information

This is where you can enter an optional customer information.

NEXT

N Branch

Is it an SAT branch where the project was ordered

N Number

Is assigned by SAT and unique worldwide (it is not necessary to enter leading zeros; this is done
automatically by the OPM)

NEXT

N CAEx customer name

Is the DOS-side path for the CAEx files

N Is necessary if a function diagram is configured

N CAEx drive

Is the drive where the files are stored.

Is necessary if a function diagram is configured

NEXT

Defining of a new process-technical plant

N Name

Is the name of the process-technical plant

N Branch

Is it an SAT branch where the project was ordered

N Number

Is assigned by SAT and unique worldwide

FINISH

This wizard is used to collect all the required data and create a plant, accordingly.

3-6 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

It will not be necessary to configure these settings in the Plant Management tool.

TOOLBOX II Users Manual D30-500-1.05 3-7

 OPM II

3.1.4. Plugins

By means of the plugin function, any programs can be started from the OPM.
Any external programs can be defined as plugins. The plugins are shown in the OPM as a menu item
with a name issued by the user. All defined plugins are found under a special menu item (Plugins).

Definition of Plugins

Functions can be defined in the form of executable files which can also be called up in a command
prompt (.exe, .cmd, etc.) .

In order to define a program as a plugin, it is entered into an INI file. The INI file must be placed in the

[TOOLBOX II Drive]:\SATTBII\PLUGINS\OPMPLUGINS.INI

folder and saved under the name opmplugins.ini. This folder is on the drive on which TOOLBOX II was
installed, is already created on installation of TOOLBOX II and is not changed on an update of
TOOLBOX II. If the INI file is present on initial start-up of the OPM, it is read in and the defined menu
items are displayed.

A plugin cannot access the user interface of the OPM. If data displayed in the OPM are changed by the
plugin, the OPM is not automatically updated but a Quit or a Refresh by means of F5 is required. This
Refresh can be carried out by an option automatically after calling the plugin (see below).

If the plugin accesses data of the OPM then these are the data which were written during the last save
process. This means that changes in the OPM without saving by the plugin are not visible.

Structure of the INI file

Each individual plugin is placed in a separate section which is marked by

[]

The name of the section must be unique. In the individual sections, the various data of the plugin are
given by special key words:

[Pluginname1]
Name: Documentation
File: C:\doc.cmd
Arguments: VIE-00000001
SaveRequest: 1
Refresh: 0
Separator:

[Pluginname2]
Name: ...
.............

3-8 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

N Name:

The name of the menu item. By means of "&" a mnemonic can be defined. The "&" must be put in
front of the desired letter:

Do&cumentation is displayed as Documentation, "C" is the mnemonic.

The following characters are permitted in the name: [a-z][A-Z][0-9][_][/][.]Space
The name must be unique otherwise, on entry, there is an error message and the corresponding
plugin is not displayed.
Note: Must be given, The input is case sensitive.

N File:

Name of the program, including the path, which is to be started.

Note: Must be given, The input is case sensitive.

N Arguments::

Arguments which should be transferred to the started program.

Any number of arguments can be given. The separation of the individual arguments is done with
spaces. If arguments with spaces should be transferred then they must be limited with double
quotation marks (e.g.: "C:\Program files").
The following variables are predefined by SAT. These can, similarly, be transferred as arguments
and are corrected before the call:

- $VanId ID of the current process-technical plant

- $BerNr Number of the current preset range
- $User Name of the current user

Note: Can be optionally given, The input is case sensitive.

N Save request:

0 Saving is not necessary

1 Save interrogation is made and the plugin can only be called if the user has saved.

Note: Can be optionally given, The input is case sensitive.

N Refresh:

0 No refresh
1 Refresh after successful call up of the plugin
Note: Can be optionally given, The input is case sensitive.

N Separator:

If this option is given then, in the OPM menu, a dash is displayed after this entry. This serves for
better legibility when there are many menu entries.

Note: Can be optionally given, The input is case sensitive.

Example

C:\SATTBII\PLUGIN\OPMPLUGIN.INI

TOOLBOX II Users Manual D30-500-1.05 3-9

 OPM II

[Parameter Loader]
Name: Parameter Loader
File: plo.exe
Separator:

[Diagnosis]
Name: Diagnosis
File: dia.exe

Plugin display

The defined plugins are displayed under the Plugins menu item on initial start-up of the OPM. This
menu item is only visible if plugins are also defined and is found under Tools. The plugins are displayed
in the same order as they are entered in the INI file. It is not possible to arrange the menu items
hierarchically - all plugins are displayed directly under the Plugin menu item. As menu item text,
precisely that name is displayed which the user has entered into the INI file. If in the INI file, the keyword
separator was entered between two plugins then a separator is also displayed in the menu. If a plugin is
incompletely defined (e.g. only a name or a file) then it is not displayed. If the INI file is changed, the
change only takes effect when next entered.

Calling a plugin

When calling a plugin a check is first made on whether the called file is present. If the file is not found an
error message is given.

If the file is found and the user has defined that it can only be called if it was saved in the OPM
(SaveRequest), then - if changes are present - the interrogation to save is made. Only if the user
confirms this interrogation with "Yes" and it was successfully saved is the plugin called. If the user has
not defined any save condition then the call is made immediately.

If the file cannot be called (e.g. no executable file and also no link present) then an error message is
given.

The OPM waits until the program has ended. During this time it is not possible to work in the OPM. If the
user has defined that, after termination of the process, the OPM should be updated (Refresh), then this
is done. After termination of the process or the refresh, a message is output which confirms the
successful carrying out of the plugin. If no refresh was carried out then the message contains a check
button that this message should not be output again on the next plugin call. The message is always
displayed when carrying out the refresh.

3-10 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.1.5. Acknowledgement dialog

In the acknowledgement dialogs a short functional descriptions and new functions can be found.

This dialog can be disabled with

DON'T DISPLAY THIS DIALOG AGAIN

In the extras menu, there is a function to reset all hidden dialogs and show them again.

TOOLBOX II Users Manual D30-500-1.05 3-11

 OPM II

3.1.6. Menu Extras

3.1.6.1. Automatic saving

With this function it can be determined whether and how often automatic saving is to be carried out. By
means of an option it is also possible to determine whether saving takes place immediately or after
confirming the save dialogue.

3.1.6.2. Options

With this function a dialogue is activated with several tabs

Tab General: Level separators permitted in the image

Each image is normally separated in the OPM by the level separator decimal point (.). By means of the
option

Level separators permitted in the image

it is possible to use decimal points in image names. If decimal points are used in image names in a
project serious disadvantages occur as a result:

N In the source data management, when exporting data the level information gets lost. Afterwards it
can no longer be differentiated, whether a decimal point is part of a name or represents a level
separator.

N The formula calculation cannot carry out any internal optimization, which leads to increased
computing times.

3-12 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

Tab General: Open Type editing window

If a new Type is created in the Type Overview, then it is possible to permit the Type editing window to
open automatically.

Tab General: }}-- }}--show information windows

All masked out Information windows of the OPM are displayed again.

Tab Typeless: Allow typeless images

With this option it is possible to partially or completely block the creation of typeless images. It is
possible to block generally the use of typeless images, to inquire whether the image may really be
typeless and to restrict the levels in which images can be typeless.
When selecting the levels it must be observed that always only the lowest level can be selected, in
which images may no longer be typeless.

TOOLBOX II Users Manual D30-500-1.05 3-13

 OPM II

Tab Delete

If types, images or default values are deleted, then depending on the setting a warning notice appears
that must be confirmed.

Tab Formulae

Here it is specified whether formulae are to be calculated topical or only in images, or calculated in
images and default values. If this option is deactivated, then the calculation of the formulae can be
started with F9.

3-14 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

Tab 1703

SSE CONNECT OVERLAPPING

With this option it is possible to connect to more than one peripheral element. If e.g. 16 binary
information inputs are to be connected to one peripheral element, and there are now however only 8
free, then it is possible with this option activated, to automatically connect the other 8 binary
informations to the next free peripheral element.

ACTIVATE CONSISTENCY CHECK WITH "CONVERT PARAMETERS"

If this option is selected, then no data are written for the SAT1703 conversion, instead only a test run
takes place for the consistency check of the parameters. A detailed output of the parameter differences
is output in the output window of the OPM II.

FOR DUPLICATE IEC - MESSAGE ADDRESS ONLY WARNING AND CONVERSION DESPITE THIS.

Within a process-engineering plant the message address for link images of the destination systems
ACP 1703 and Ax 1703 (IEC) must be unambiguous. The parameters CASDU1, CASDU2, IOA1, IOA2,
IOA3 (the TI is used not for the determination of the unambiguity) are checked. If CASDU1 and
CASDU2 are parameterized to the value 255 (not used), then this link image is not taken into account
during the check.
If this option is set, then the conversion operation is not aborted with identical message addresses,
instead only a warning notice is output in the error output.

Tab CAEx

In this tab the paths are specified in which the CAEx Macros are stored.

TOOLBOX II Users Manual D30-500-1.05 3-15

 OPM II

3.1.7. Quick Reference

F4 Recalculated message address

By pressing the F4 key it is possible to recalculate the message address of 1703 Ax. When doing this,
all message attributes are updated based on the filled-out link address. The message address is always
calculated from the selected image. If a higher value image is selected then all message addresses of
the subordinate images are calculated.

Note: The message address is always recalculated only in images

F5 Multi-user

By pressing the F5 key it is possible, in multi-user operation, to update the changed data on the user
interface. When doing this, the last-saved state is accessed.

F9 Calculate formula

By pressing the F9 key, all formulas are recalculated which are not up-to-date or invalid. A formula is
not up-to-date if the automatic calculation of the formula is switched off (Extras - Options) and a value
change of inputs of this formula is made. A formula is invalid if the result of the formula does not
correspond to the valid value range of the destination.

SHIFT + F9 Calculate formula unconditionally

By pressing the SHIFT + F9 key all formulas are always recalculated. This process can last some time.

Find in the Tree

In the OPM it is possible to search for images in the Edit Image window. In the popup menu of a level or
of an image, with the Find Image function an input window is opened into which the image name of the
image which is to be searched for can be entered. Wildcards (* or ?) are allowed.

Sort in the Tree

In the popup menu of typeless images (right mouse button on typeless image) there is the Sort menu
item. With this function typeless images which possess a common root image can be sorted
alphabetically. This sorting is only temporary. When the Image window is next opened, the original
sequence is displayed again.

Change Sequence in the Tree

With this function it is possible to alter the sequence of typeless images or of types. In the popup menu
of a type in the Type Overview window, the sequence can be changed with the function

Change sequence

If the sequence is changed in the type then that also has an effect on all (typed) images. The same
function is also available for typeless images in the Edit Image window.

3-16 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

Note: If types or images are edited with "Change sequence" then the sequence is saved the next time a
save is made. For the changing of the sequence, all ranges of the process-technical plant must possess
the original status.

Searching in Text Windows

A search can be started in text windows via the popup menu. The following functions can be selected:

N Forwards

The search is carried out downwards from the marked position.

N Backwards

The search is carried out upwards from the marked position.

N Repeat

If a search expression has been found then a search for the next occurrence of the search
expression can be started

TOOLBOX II Users Manual D30-500-1.05 3-17

 OPM II

3.1.8. Documentation

In the OPM images, default inputs and user types, the system technology and the contents of the bulk
editing can be documented.

Documentation of images, default inputs and user types

The documentation can be started via the PopUp menu of the corresponding tree.

The marked image, including all subimages, is documented.

After starting the documentation (Print Preview or Print), a dialog is opened in which the level up to
which the documentation should be created can be selected.

3-18 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

If the level parameter is selected then a further dialog is displayed in which all available parameters and
infotypes are listed and can be selected.

This selection enables specific documentation of the images, default inputs and user types and
parameters which are needed.

Documentation of the bulk editing

If the bulk editing has been started then the displayed data can be documented with the following menu
items:

SYSTEM | PAGE VIEW

or

SYSTEM | PRINT

Documentation of the system technique

The documentation of the parameters or their values is done by printing out the tree part of the system-
technical parameterization. The printout is in the form of a spreadsheet, i.e. the tree structure of the
system-technical parameterization is illustrated on a spreadsheet. The documentation can be selected
via the opUp menu of an AU or a system element.

It is possible to see a preview before printing. In addition, it is possible to select several system
elements and to print them out. In this case, the preview is only available for the first entry but all
selected system elements are printed out.

PD forms or spreadsheets can be printed out individually. This is done via the PopUp menu in the right-
hand part of the Explorer window.

TOOLBOX II Users Manual D30-500-1.05 3-19

 OPM II

3.2. Images

3.2.1. Overview

In contrast to Types that form a template for the structure (structural plan), images are concrete objects
in which parameter settings and value changes are carried out.
Each image represents a real object ( Branch north, busbar disconnector 1, natural gas transfer station
43,. . )

Properties of the typified images

N Typified images are created from Types (instanced)

N Typified images have the same structure as their Types

N If a structural change is made in a Type, this structural change is compensated in all typified
images of this Type. (inheritance)

N The use of typified images is all the more efficient, the more similar images are available

3-20 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.2.2. Handling

Method of procedure

TOOLS | TYPES- OVERVIEW

(if not yet open)

TOOLS | IMAGES

Drag and Drop a Type (from which a concrete image is to be created) from Type-Overview window into
the Image-processing window (in the appropriate level)

With this Drag and Drop, a concrete object (e.g. a branch) is now created of that Type (which is a
template)

After entering the name, an identically structured image (as the Type from which it is created) appears
in the left of the Image-processing window with the only difference being, that the Sub-Image names are
numbered automatically with 4-places, because the name of an individual plant must be unambiguous.

TOOLBOX II Users Manual D30-500-1.05 3-21

 OPM II

If an image is selected, then on the right of the Image-processing window a Spreadsheet appears, in
which

N the sub-image names are displayed in the first column

N the Type from which it is created is displayed in the second column

N the level of the image is displayed in the third column

3-22 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.2.3. Typless images overview

Typless images have no reference to the Types, i.e. no inheritance takes place

N Typless images are created, by creating the images directly in the Image-processing window

N Typless images are also created by structural changes to a typified Image (since the image no
longer has the same structure as the Type, it is typless)

N If images exist only once, the typless method of procedure is advantageous

N Typified images can be used below typless images (e. g. 20 kV Plant is typless because it exists
only once, all branches below it are typified images)

TOOLBOX II Users Manual D30-500-1.05 3-23

 OPM II

3.2.4. Typless Images handling

1. Direct creation

TOOLS | IMAGES

(if not yet open)

selection of a level and

M-CLICK-R | ADD NEW IMAGE | TYPLESS

Entering a name

A typless image is identified by a modified Icon

2. Structural change of an image

TOOLS | IMAGES

(if not yet open)

DELETE A SUB-IMAGE

and after a query, the image becomes typless, because the structure of the image differs from the
structure of the Type

In this example, the information of the busbar-disconnector has been deleted directly in the Image-
window. Through this the busbar-disconnector becomes typless. If the busbar-disconnector is typless,
the branch must also be typless, since if part of an object is no longer typified, then the entire object can
no longer be typified.

3-24 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

The other objects (e.g. LS) are not affected by this action however and remain typified

TOOLBOX II Users Manual D30-500-1.05 3-25

 OPM II

3.2.5. Hiding of link images

If images are created with a large number of link images, and not all are link images are needed for the
parameter setting, then it is possoble to set these images to Prepared and then mask them out

In the Screenshot it can be seen, that 4 Links are contained below the command "BEF_EIN_a". If not all
these links are used, then those not required can be set to Prepared. This takes place by changing the
parameter Lk_Vorb to the value "Prepared"

3-26 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

Via the menu item:

VIEW | DISPLAY PREPARED LINK IMAGES

prepared images can be masked out. A corresponding notice appears, that this change is first effective
after re-entering the Image-processing window. If this notice does not appear, then with

EXTRAS | OPTIONS | DISPLAY MASKED OUT NOTICE WINDOW AGAIN "RESET"

this window can be displayed again. This setting is effective everywhere in the OPM (in the image tree,
in the mass-editing, in the default input,..) To redisplay masked-out link images, the menu item

VIEW | DISPLAY PREPARED LINK IMAGES

must be selected once again.

TOOLBOX II Users Manual D30-500-1.05 3-27

 OPM II

3.2.6. Dynamic link images

Because of the dynamic Link Images it is possible to define parameters for various categories in one
Link-type.

Bewcause of this it is e.g. possible to crreate only one Link-type for 1703_DI, which contains all
necessary parameter of the sub-categories 1703_DI_EM and 1703_DI_DM. If the category is set in the
image, (e.g.: to USIO20/DI_EM) then all parameters that do not belong to this category are displayed
greyed-out. The greyed-out parameters are not taken into account during the conversion process.

3-28 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.2.7. Create Images with pre and suffix

If an image is created, then now it is possible to Assign a fixed prefix and suffix to the image names. For
this the Image-Create dialogue has been expanded:

In the upper part, the image name is entered and optionally a default input with which the image is to be
created. If several images are to be created at the same time, then this can be entered for Number.

The lower part of this dialogue can be folded out with "Expand".

If the "special functions for text generation" is checked, the following functions are possible:

N Start value

is the value which is counted from in ascending order during Image creation

N Increment value

is the value by which the start value is to be increased in stages

N Minimum number of places of the value

is the number of figures to be displayed after the image name and before the text-suffix

N Text-Suffix

is the text that is to be right at the end of the image name.

With OK all entries are accepted and the image is created.

These expansions are available for the following functions in the OPM:

N Copying of default Types

N Creating of images of a Type (and attaching to existing images as sub-images)

TOOLBOX II Users Manual D30-500-1.05 3-29

 OPM II

N Creating images from a default input

N Creation of typless images (and attaching to existing images as sub-images)

N Copying of images (and attaching to existing images as sub-images)

N Creation of default inputs from a Type

Creation of default inputs from an image

Copying of default inputs

3-30 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.2.8. Change Order

With this function it is possible to change the order of typeless images or of Types. This function is
started in the Pop-Up menu of a type in the Type Overview window as follows:

CHANGE ORDER

If the order in the Type is changed, then this also has an effect on all (typical) Images. The same
function is also available in the Edit Image window for typeless images.

Note: If Types or Images are edited with "Change order", then the order is stored the next time saving
takes place. To change the order, all ranges of the process-engineering plant must have the original
status.

TOOLBOX II Users Manual D30-500-1.05 3-31

 OPM II

3.2.9. Search, Sorting and Order in the Tree

Search in the tree

In the OPM it is possible to search for images in the Edit Image window. In the Pop-Up menu of a level
or an image, with the function Search Image an input mask is activated in which the name of the image
to be searched can be entered. Wildcard entries (* or ?) are allowed.

Sorting in the tree

In the Pop-Up menu of typeless images (right mouse-button on typeless image) there is the menu item
Sorting. With this function typeless images, that have a common root image can be sorted
alphabetically. This sorting is only temporary. With the next opening of the Image window the original
order is displayed again.

Change order in the tree

With this function it is possible to change the order of typeless images or of Types. In the Pop-Up menu
of a type in the Type Overview window, with the function

CHANGE ORDER

the order can be changed. If the order in the Type is changed, then this has an effect on all (typical)
Images. The same function is also available in the Edit Image window for typeless images.

Note: If Types or Images are edited with "Change order", then the order is stored the next time saving
takes place. To change the order, all ranges of the process-engineering plant must have the original
status.

3-32 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.3. Typs

3.3.1. Handling

Procedure

TOOLS | TYPES OVERVIEW

(if not yet open)

M- DClick- L on the user Type, the link level to be extended by parameters (Edit Type window will open)

PARAMETERS TAB

Select the desired parameters from a category and drag and drop them into the previously opened Edit
Type window

TOOLBOX II Users Manual D30-500-1.05 3-33

 OPM II

3.3.2. Structure

In the OPM, it is a principle to use already defined Types in Types of higher-value levels

N During Assignment, the structures of the already existing Type are applied

N If a Type is changed, this change will become effective in all existing assignments

The Assignment of Types to Types of higher levels makes it possible to generate complex structures
relatively easily

3-34 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.3.3. User types overview

Types are the basic elements (templates) for object-oriented work in the OPM. Based on the user types,
objects are defined that can be used several times in a plant.

N User types can be defined on every process-technical level (e.g. a SSTR on the operational
equipment level)

N The name of the user type can be assigned freely

N User types do not retain values (but only the parameters)

TOOLBOX II Users Manual D30-500-1.05 3-35

 OPM II

3.3.4. User types handling

Procedure

TOOLS | TYPES OVERVIEW

(if not yet open)

M- Click- R on a process-technical level in the Types Overview window

NEW TYPE

Entering of name and longtext (optional) of the new Type

OK

3-36 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.3.5. Linktypes overview

For each datapoint category, a separate link is defined

Linktypes are user Types except that they are defined on the lowest level.

N Every link Type contains the destination-system-specific parameters

N Within one link, only identical datapoint categories can be defined (e.g. measured value for 1703)

In the OPM, the link level connects the process-technical segment with the system-technical segment

N A process-technical signal can be assigned several links

N Every link corresponds to one point of entry or exit in the system

N In the OPM, link Types represent the system-technical segment

TOOLBOX II Users Manual D30-500-1.05 3-37

 OPM II

3.3.6. Linktypes handling

Procedure

TOOLS | TYPES OVERVIEW

(if not yet open)

M- Click- R on the LNK leven in the Types Overview window

NEW TYPE

Entering of name and longtext (optional) of the new link Type

OK

Use of already created Types (TYP in TYP)

M- DClick- L on the hierarchically higher-level user Type (Types Overview window will open) Dragging
and dropping from the Types Overview window to the Edit Type window

This action causes entry or exit points (links) to be assigned to each signal

3-38 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.3.7. Info types overview

N Infotypes are used to administrate any given values. (non-SAT systems, descriptions, additional
information)

N Infotypes can be created freely by the user.

N Default values of infotypes can be defined freely

N Infotypes can be used on any given VT level

TOOLBOX II Users Manual D30-500-1.05 3-39

 OPM II

3.3.8. Infotypes handling

Procedure

TOOLS | TYPES OVERVIEW

(if not yet open)

INFO TAB

M- Click- R into an empty area in the Types Overview window (if no info type has been created yet)

INFO TYPE NEW

Entering of name, longtext (optional), default value (optional), access group, Domain of the new info
type

Domain... value range

The access group must, if none has been made available yet, be created with "New". It is used for the
further subdivision of the info types

3-40 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

If an access group has already been made available, the access group can be selected as well during
the creation of a new info type

TOOLBOX II Users Manual D30-500-1.05 3-41

 OPM II

3.3.9. Parameter types

Parameter Types are used in order to administrate parameters for a certain destination system. (SAT
1703, SAT 250, SAT 230)

N Parameter Types and names are predefined by SAT and cannot be changed

N Parameter Types can only be used on the LINK level (or below the link Types)

The selected parameters (shown in black) are attached to the link Type. Furthermore, blue attributes
are created, the so-called link address

The link address is the unique address of a datapoint in the respective destination system (i.e. in the
SAT1703 link there are other attributes than in the SAT250 link)

The following attributes are the same in every link:

3-42 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

N Lk_ZS... describes the destination system (e.g.: SAT250, SAT1703)

N Lk_Kat... describes the datapoint category (e.g.: command, binary information, measured value)

N Lk_Vorb... describes the state of the entire datapoint (prepared or activated)

The remaining part of the link address is constituted by the respective addressing scheme of the
relevant system, e.g.:

N Lk_Reg, Lk_Komp, Lk_Bse, Lk_Proj, Lk_EAM for a CAEx function diagram addressing

N Lk_CAE_ID, Lk_TA for a SAT250 addressing

by means of the link address, a datapoint is unambiguously identifiable for the respective destination
system

TOOLBOX II Users Manual D30-500-1.05 3-43

 OPM II

3.3.10. Parameter Type Handling

TOOLS | TYPES- OVERVIEW

(if not yet open)

Double-click the left mouse-button on the User- Type, the Link Level which is to be expanded with
parameter (Edit Type window opens)

PARAMETER TAB

Select the required parameter from a category and drag into the previously opened Edit Type window
with Drag&Drop

3-44 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.4. Assign

3.4.1. Overview

Automatic assignment

The function "Automatic Assignment" is the automated assignment of one or several link images to one
or several HW pins or software datapoints of a system element.
By assigning Ax1703 link images to HW pins or software datapoints of a system element, the process-
technical segment is linked with the system-technical segment in the OPM II.

Automatic assignment in the OPM is done by dragging and dropping. For this purpose, the user can
select the following sources of the drag procedure:

N In the Edit Image window, one or several link images of the Ax 1703 destination system

N In the Mass Editing window, one or several lines each corresponding to a link image of the SAT
Ax 1703 destination system.

The destination of the drop procedure is the System-Technical Segment window.

TOOLBOX II Users Manual D30-500-1.05 3-45

 OPM II

Automatic assignment causes:

N the link address to be filled in automatically

N the spontaneous message address to be filled in automatically (if available, on for Ax 1703)

N the periodical data point for the use in Caex to be provided (if any)

N the VTA of the OPM and a freely definable longtext to be assigned to a HW pin

N all already assigned HW PIN's to be identified by closed switches.

N partly categorized images to be categorized.

Manual assignment

The function "Manual Assignment" is the manual completion of the link address of one or several link
images.
Contrary to Automatic Assignment, the system-technical segment will not be updated until the menu
item

DESTINATION SYSTEMS-SAT 1703-MANUAL ASSIGNMENT

is selected. Only after this operating step will the corresponding switches be closed, and the longtext
and the process-technical address be entered into the system-technical segment. In addition, the
function described for Automatic Assignment will be carried out, as well.

3-46 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.4.2. Handling

Automatic Assignment to HW pins

TOOLS | IMAGES

(if not yet open)

TOOLS | SYSTEM-TECHNICAL SEGMENT

Rearranging of windows

WINDOWS | SIDE BY SIDE

Dragging and dropping an image of the Type Ax 1703 to the node "HW Pins" or to a special HW pin.

Automatic Assignment to software datapoints

Same procedure as described above, only that the link image is assigned by dragging and dropping to
the respective SW datapoint.

Manual Assignment

TOOLS | IMAGES

(if not yet open)

Opening of the desired Ax 1703 link image. Manual completion of the link address by selecting the
attributes: Lk_Reg, Lk_Komp, Lk_BSE, Lk_ZSE, Lk_DP

Starting of manual Assignment

DESTINATION SYSTEMS | SAT 1703-> MANUAL ASSIGNMENT

TOOLBOX II Users Manual D30-500-1.05 3-47

 OPM II

3.4.3. Partly categorized woking with 1703

The Ax 1703 destination system provides for the options of working in a "categorized" and "partly
categorized" manner. In the categorized mode, the complete category is defined by the user in the
image in the parameter Lk_Kat. The category consists of firmware and DAI.

In the partly categorized mode it is only necessary to define the DAI in the image. To do so, the user
selects the desired DAI in the parameter Lk_Kat. The firmware is detected automatically when a link
image is assigned to a system element. This procedure makes a subcategory a category in the image.

N Firmware

Firmware is a software running in the destination system. The user can adapt this software to the
needs by means of parameters.
Example: USIO20

N DAI

Detailed Assembly Information is the description of the signal Type of the datapoints of a
firmware.
Example: DI_DM
Digital input - double-point information
Example: AI_IU
Analog Input - current or voltage

N Category
In Ax 1703, it corresponds to the firmware and DAI and is defined in the parameter Lk_Kat.
Example: USIO20/DI_DM
USIO20 / digital input - double-point information

N Subcategory
For Ax 1703, it corresponds to the DAI and is defined in the parameter Lk_Kat.
Example: DI_DM
Digital input - double-point information

3-48 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.5. Default values

3.5.1. Overview

Defaults allow you to predefine a vast variety of values (parameters, names, information..) for
standardized images. Defaults are always a copy of an image or Type

N DV's always pertain to a Type (standardized) and can only be used for (standardized) images of
the same Type. They are user Type, except that they are defined on the lowest level.

N DV's can be created for standardized images of any VT level

N DV's of lower-order levels can be used in DV's of higher-order levels. This makes it easy to
compose complex DV's.

N In the event of changes in the DV's, these changes are not inherited by the respective images

N In the event of changes in the DV's, these changes are not inherited by the respective images

N If values of standardized images are changed, this has no repercussions on the respective DV's.

N It is also possible to directly create new standardized images from DV's

TOOLBOX II Users Manual D30-500-1.05 3-49

 OPM II

3.5.2. Handling

Creating of a DV from the Type

TOOLS | TYPES OVERVIEW

(if not yet open)

M- CLICK- R ON A TYPE

GENERATE DEFAULT

Entering of name of default

-OK

An Edit Defaults window will open, with the default that has just been created, and all default values.

Creating a DV from an image

TOOLS | EDIT IMAGE

(if not yet open)

M- CLICK- R ON AN IMAGE

GENERATE DEFAULT

Entering of name of default

OK

An Edit Defaults window will open, with the default that has just been created, and all default values.

3-50 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.5.3. Transfer

Defaults can be transferred by means of a wizard or a menu. This transfer process accommodates 4
different options.

N Transfer to images of equal Type

This transfers the DV to images that match the Type of this default.

N Transfer to defaults of equal Type

This transfers the DV to all defaults that match the Type of this default, i.e., one "small" DV is
transferred to one or several larger DV's

N Transfer to defaults of equal Type

This transfers the DV to all defaults that match the Type of this default, i.e., one "small" DV is
transferred to one or several larger DV's

N Transfer to images of this default

It is stored in the system for every image, which DV it was created from, and which DV was
transferred to this image, as the case may be.

N Transfer to defaults to which a transfer has already taken place

It is stored in the system for every DV which DV is transferred to this DV. This menu item causes
the DV to be transferred to all DV's that match this DV.

Procedure

Tools | Defaults Overview

(if not yet open)

DRAGGING AND DROPPING THE DV FROM THE OVERVIEW WINDOW TO THE EDIT IMAGE WINDOW TO AN IMAGE
(THAT MATCHES THE TYPE OF THE DV)

After dropping, a menu will appear that allows you to choose from the following options:

TOOLBOX II Users Manual D30-500-1.05 3-51

 OPM II

N Values

Values are attributes that can be configured in the OPM (such as an inversion), In the OPM,
values are always shown in black. If "Selection" has been selected, then the so-called video-
recorder will be opened, in which various attributes can be selected

N System-technical address

The unambiguous datapoint address is concealed in the system-technical address This datapoint
address is composed of different attributes, depending on the destination system (such as
Lk_Reg, Lk_Komp, Lk_BSE, Lk_Proj, and Lk_EAM in a CAEX link). The system-technical
attributes are always characterized in that they start with "LK_" (corresponds to: link address).
They are always shown in dark-blue. If "selection" has been selected, then the so-called video-
recorder will be opened, in which various attributes can be selected

N References

In the OPM, references are used for 1:1 relations between parameters or for the formation of a
text address, as the case may be

N Names

By using the Transfer Names function, names of the various sub-DV's of a DV can be transferred

N Formulas

By using Formulas, all formulas used in the DV are transmitted

3-52 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.5.4. Wizard

The DV-Wizard is a graphics support feature for DV transfer.

The wizard is started by:

SELECTING A DEFAULT | RIGHT MOUSE BUTTON | TRANSFER DV | WIZARD

The wizard guides the user through all options of transferring a default.

Here, exactly the same options as in Transferring of DV are offered

TOOLBOX II Users Manual D30-500-1.05 3-53

 OPM II

3.6. Elcad

3.6.1. Overview

The OPM provides an interface for coupling with the construction tool ELCAD. Through this it is possible
to transfer images that are assigned to a SAT-1703 system element to ELCAD via this defined interface.

Thereby the longtext (Parameter Pin_Longtext) is used for the text designation in the ELCAD File. If the
parameter Pin_Longtext does not exist in the image, then the VTA is used as text.
For multi-bit information (e.g.: double-point information) in OPM the parameter LABEL must be used in
the Link Image. This parameter contains a selection of status texts (ON, OFF ..) that are added to the
text designation in the ELCAD file (see ELCAD_Prerequisites, ELCAD_Coupling file).

The KKS address in the ELCAD file is composed from the definition of assembly technique. (see
ELCAD_Prerequisites, ELCAD_Coupling file).

In the OPM 1703/Ax Converter (destination systems -- SAT 1703 -- conversion or manual Assignment)
the generation of an ELCAD file is possible via an option. If this option is flagged in the Converter
dialogue, then any path and filename can be specified for the ELCAD file.

3-54 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.6.2. Handling

The ELCAD coupling files are ASCII text files, that are ended with CR+LF. The file is created in PC-850
character set).

structure of the KKS-address

N signal =

N Text from the field Automation Function

N signal +

N Designation key for plant, station, installation location, cabinet/level in which the module carrier is
located.
These fields are combined without separating character.

N signal -

N Designation key of the module carrier in which the system element is located.

N Hardware Position (HwPos) of the periphery element in the module carrier (2-place decimal with
leading zeros)

N Card point

N Tabulator signal

N Pin_Longtext or VTA (Definition in the OPM - Link Image)

The sum of the address must not be longer than 32 signals. If the automation function fields or the
designation key of the assembly-technique fields are blank or contain the signal, the corresponding
address components are not generated. The signal = is only generated for a defined Automation
Function.

structure of the Signal text

N For assigned HW Pins, the data is generated from the corresponding OPM Link Images.

N If further associated Pins are necessary for assigned HW Pins (Measured value +/-, Double-point
information 0.1) then the signal text is generated for all associated Pins. If the parameter Label
exists in the OPM Link Image, then the corresponding status text is added to the signal text.
(separated by a space).

N Fixed texts are generated for HW Pins that have no reference in the OPM (e.g: common).

The sum of the signal text must not be longer than 54 characters (ELCAD limit). ELCAD automatically
carries out a sorting of the signals of the files, which is why the signals in the file are not sorted. (The
Label text must also be taken into account with the length.)

Following special characters to ELCAD are not allowed: \ # ^

TOOLBOX II Users Manual D30-500-1.05 3-55

 OPM II

3.6.3. Requirements

Definition of assembly technique

N Automation function
The definition takes place in the plant management in the window Define Automation Unit
e.g: 0AFC03

N Designation key - Assembly-technical plant

The definition can be defined either in the plant management or in the configuration.
Plant management : Assembly-technique -- define
Configure : View -- view assembly-technque
e.g: 01

N Designation key - Station

The definition can be carried out either in the plant management or in the configuration.
e.g: S

N Designation key - Installation location

The definition can be carried out either in the plant management or in the configuration.
e.g: E

N Designation key - Cabinet/Level

The definition can be carried out either in the plant management or in the configuration.
e.g: Sch

N Designation key - Module carrier

The definition can be carried out either in the plant management or in the configuration.
e.g: A0

N Designation key - HwPos

The definition of the Hardware Position of the module takes place in the configuration
e.g: 12

Result:

=0AFC03+01SESch-A012 x2 a1 [Text] [Label]

Definition of the Link Images in the OPM

N Link Images of the destination system 1703/Ax (Lk_ZS = 1703_Ax) are used for generating the
ELCAD files.

N If the parameter Pin_Longtext exists in this Link, then the contents of this parameter is used for
the signal text in the ELCAD file. If this parameter does not exist, the VTA is used as text in the
ELCAD file.

N If the Label parameter exists in this Link, then the selected status text (e.g.: ON/OFF) is added to
the corresponding signal texts. This way it is possible e.g.: to document all Hardware Pins for
double-point information.

3-56 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.7. Formulae

3.7.1. Overview

Formulae are used, in order to calculate values of parameters or Infotypes. The functions of the
formulae are split into 4 groups:

N Mathematical functions

N String functions

N Control functions (IF)

N OPM functions

Formulae can be assigned both in images as well as in defaults.

Assigning formulae

A formula is defined in a range and assigned the corresponding parameters or infotypes. The
assignment is carried out in the Reference- & Formula - Mode by selecting an already defined formula
from the Drop Down Listbox of a parameter or infotype.

Canceling the assignment

The canceling of the assignment is possible in 2 ways:

N In the Reference- & Formula - Mode the blank entry is selected in the Drop-Down-Listbox

N In the Normal-Mode a double-click is performed on a parameter or infotype, and the inquiry

appears whether or not the formula is to be detached.

If a formula is detached, then the result of the formula in the value of the attribute remains.

Deleting a formula

In the Reference- & Formula - Mode a formula can be deleted by means of the menu item

TOOLS | FORMULA | DELETE FORMULA

As a result all formula assignments are also deleted after confirmation.

Entering the formula directly in the Edit Image window

If a formula is to be entered directly in the Edit Image window, then after defining the formula name a
multi-line display appears for the input of the formula.

TOOLBOX II Users Manual D30-500-1.05 3-57

 OPM II

ComputerCode Check

When entering a formula, a formula ComputerCode Check always runs concurrently in the background.
Only when the formula ComputerCode is correct is the formula text displayed in black letters. An
incorrect ComputerCode is displayed in red.

Writing an " in a formula

If an " is to be displayed in the result of a formula, then this is to be entered as follows:

"\""

Topical calculation of formulae

Whether formulae are to be calculated topical can be defined in

EXTRAS | OPTIONS

. This setting ("topical" or "manage non-topical") is displayed in the OPM main window.

3-58 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

TOOLBOX II Users Manual D30-500-1.05 3-59

 OPM II

3.7.2. Handling

To be able to define Formulae one must switch to the Reference- & Formula- Mode.

VIEW | REFERENCE- & FORMULA - MODE

In the Edit Image window a Parameter type or Info type is marked, in which the Formula is to be
defined. In the Drop-Down-Listbox a new formula name is entered, or an existing one selected. When
the input is confirmed with Return, then the formula name appears in the values field of the parameter
or info type and in the upper part of the image window the Formula can be entered.

Formulae can also be defined using the Formula Editor.

3-60 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.7.3. Performance

When using formulae it must be taken into account, that each assigned formula must be recalculated
with a change in value of a formula input. A large number of formulae in one project therefore also leads
to losses in performance.
The following rules are to be observed when designing a project:

N Static values in attributes are non-critical for the performance. These values can be entered with
DL's or by means of the mass editing.

N For the performance, references are the best solution for the automatic filling of attributes.
However here only 1:1 relationships can be represented.

N Formulae are the most universal and also performance-critical variant of automatically generating
values in attributes.

N Formulae with many input parameters require more running time than formulae with less inputs.

TOOLBOX II Users Manual D30-500-1.05 3-61

 OPM II

3.7.4. Formula editor

THE FORMULA EDITOR IS STARTED BY MEANS OF

TOOLS | FORMULA | FORMULA EDITOR

or by selecting the button

FORMULA EDITOR

at the top right in the Edit Image window.

The Formula Editor can only be started in the Reference- & Formula - Mode.

3-62 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

The structure of the Formula Editor

N Formula name
Name of the Formula. (Another Formula can also be selected to change this)

N Formula
Enter the Formula ComputerCode.

N Result
By pressing the Button "Calculate" the Formula is calculated and the result displayed.

N OK
Acceptance of the entries

N Expanded
Entry help for the Formula ComputerCode

N Accept function
If a function is selected in the expanded display, then with "Accept function" this is placed directly
at the cursor position of the formula field

TOOLBOX II Users Manual D30-500-1.05 3-63

 OPM II

3.7.5. Cascading of references and formulae

From Version 3.0 of the TOOLBOX II it is possible, that a Formula can be used as input of a Reference.
As a result it is possible to transfer the result of a formula to other parameters or info types by means of
a reference.

3-64 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.7.6. Mathematic functions

3.7.6.1. ABS()

ABS (Number)

Delivers the absolute value of a number, i.e. a number without preceding sign

Example

ABS(-24) -> 24

3.7.6.2. DIV()

DIV (Number,Divisor)

Delivers the integer result of the division

Example

DIV(8,3) -> 2

3.7.6.3. INT()

INT (Number)

Rounds off a number to the next smaller integer number.

Example

INT(3.6723) -> 3

3.7.6.4. MOD()

MOD (Number,Divisor)

Delivers the rest, remaining after division with the divisor

Example

MOD(8,3) -> 2

TOOLBOX II Users Manual D30-500-1.05 3-65

 OPM II

3.7.6.5. ROUND()

ROUND (Number,Decimal Places)

Rounds off a number to the given number of decimal places

Example

ROUND (8.346,2) -> 8.35

3.7.6.6. TRUNC()

TRUNC (Number)

Truncates all decimal places with a number

Example

TRUNC(8.346) -> 8

3.7.6.7. HSTR(Number, [width])

The already existing function HSTR(number), that determines a Hexadecimal-String from a number, is
expanded with a formatting specification. The required Hexadecimal-String is then formatted with
leading zeros. The function determines a Hexadecimal-String from the given number (Integer), and fills
out this string with leading zeros, until the given width is reached. If the given width is smaller than the
Hexadecimal String, then the string is not filled out with leading zeros.

Example

HSTR(1563) delivers 61B

HSTR(1563, 5) delivers 0061B
HSTR(1563, 1) delivers B

3-66 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.7.7. String functions

3.7.7.1. CONCAT()

CONCAT (text1,text2,...)

text1, text2, ... combines the given texts to form one text.

Example

CONCAT("Total ", "Value") ->"Total Value".

3.7.7.2. EXACT()

EXCAT (text1,text2)

text1, text2 compares the 2 texts and delivers 1 if they are identical, otherwise 0

Example

EXACT("Total ", "Value") -> 0

EXACT ("Total ", "Total") -> 1

3.7.7.3. FIND()

FIND (text,Searchtext,StartPosition)

Searches for a search text in a text from the position Startposition and delivers the position of the
searched text

Example

FIND("Total", "o",1) -> 2

3.7.7.4. HSTR()

HSTR(Number [,Width])

Calculates the corresponding hexadecimal string from a given number and formats it to the given width.
If the string is longer than the given width, then it is truncated, otherwise it is filled out with zeros.

TOOLBOX II Users Manual D30-500-1.05 3-67

 OPM II

Example

HSTR (256) -> 100

3.7.7.5. LEFT()

LEFT (text,number)

Delivers the given number of characters of a text starting from the left

Example

LEFT("Total",2) -> To

3.7.7.6. LEN()

LEN (text)

Delivers the length of a text

Example

LEN("Total") -> 5

3.7.7.7. LOWER()

LOWER (TEXT)

Converts all capital letters in the text to small letters.

Example

LOWER("Total") -> total

3.7.7.8. MID()

MID (Text,StartPosition,number)

Delivers a given number of characters of the text starting from the Startposition

Example

MID ("TOTAL",2,3) -> OTA

3-68 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.7.7.9. REPLACE()

REPLACE (Text,StartPosition,Number of Characters,New Text)

Replaces a search text in a text with a text from a given Startposition to a number of characters.

Example

REPLACE("Valuexx",6 ,2,"y" ) -> Valuey

3.7.7.10. SEARCH()

SEARCH (Text,SearchText, StartPosition)

Searches for a search text in a text from the position Startposition and delivers the start position of the
sought text

Example

SEARCH ("Total", "ta",1) -> 3

Note:

This function is not case-sensitive

3.7.7.11. SUBST()

SUBST (Text,AlterText,NewText,number)

Substitutes a text in a text with a new text.

Example

SUBST( "Total","a" ,"o" ,1) -> Total

3.7.7.12. T()

T (number)

Converts a number to a text

Example

T(3) ->"3"

TOOLBOX II Users Manual D30-500-1.05 3-69

 OPM II

3.7.7.13. TRIM()

TRIM ("Text")

Removes all spaces in a text except the single spaces between the words.

Example

TRIM("Total Value") -> "Total Value"

3.7.7.14. UPPER()

UPPER (Text)

Converts all small letters in a text to capital letters

Example

UPPER(value) -> VALUE

3.7.7.15. VALUE()

VALUE (Text)

Converts a string to a number. If the string is an empty string or contains invalid characters, then 0 is
returned as result.

Example

VALUE("24") -> 24
VALUE("2ab") -> 0
VALUE("") -> 0

3-70 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.7.8. Control functions

3.7.8.1. IF()

IF (condition, value if true, value if false)

Delivers a value, depending on whether the condition is true or false

Example

IF (3==3, "OK", "NOK") -> OK

TOOLBOX II Users Manual D30-500-1.05 3-71

 OPM II

3.7.9. OPM specific functions

3.7.9.1. GET ()

GET (Parameter-type Name)

This function delivers within an image the value of the parameter with the given type name

Example

GET ("Blocking")

3.7.9.2. GET (RELATIVE)

GET (levels up, process-engineering address down, parameter-type name)

Climbs up the tree the number of Levels, then down the given process-engineering address, and
delivers the value of the parameter.

Example

GET (3,"LS.EM.1703Ax","Blocking")

3.7.9.3. GETCAE ()

GETCAE ()

Delivers within an image the value of the CAE long text

3.7.9.4. GETCAE (RELATIVE)

GETCAE (levels up, process-engineering address down)

Climbs up the tree the number of Levels, then down the given process-engineering address, and
delivers the value of the CAE-Longtext.

Example

GETCAE (3,"LS.EM.250EM")

3-72 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.7.9.5. GETINFO ()

GETINFO()

Delivers within an image the value of an Infotyp

Example

GETINFO ("Remark")

3.7.9.6. GETINFO (RELATIVE)

GETINFO (levels up, process-engineering address down, infotype name)

Climbs up the tree the number of Levels, then down the given process-engineering address, and
delivers the value of the Infotyp

Example

GETINFO (3,"LS.EM.1703Ax", "Remark")

3.7.9.7. GETNAME ()

No longer used. Has been replaced by GETNAME_EX().

3.7.9.8. GETNAME_EX()

GETNAME_EX(Levels up)

Delivers the name of the image, when one climbs the given number (1-n) of Levels in the tree.

3.7.9.9. GETNAME_EXDN()

GETNAME_EXDN(EbDn [,EbDn])

Delivers the name of the image, when one climbs down the given number EbDn (1..n) of levels from the
relevant root of the parameter image in the tree. Optionally, the image name can comprise several
steps. For this, one can climb down a certain number of levels from the specified place.

3.7.9.10. GETNAME_EXUP()

GETNAME_EXUP(EbUp [,EbDn])

TOOLBOX II Users Manual D30-500-1.05 3-73

 OPM II

Delivers the name of the image, when one climbs up the given number EbUp (1..n) of levels from the
parameter image in the tree. Optionally, the image name can comprise several steps. For this, one can
climb down a certain number of levels from the specified place.

3.7.9.11. GETPEA ()

No longer used. Has been replaced by GETPEA_EX().

3.7.9.12. GETPEA _EX()

GETPEA_EX (Levels up)

Delivers the process-engineering address of the image, when one climbs up the given number (1-n) of
Levels in the tree.

Example

GETPEA(3)

3.7.9.13. GETWLS ()

GETWLS()

Deliver within an image the value of the WLS longtext.

3.7.9.14. GETWLS (RELATIVE)

GETWLS(Levels up, process-engineering address down)

Climbs up the tree the number of Levels, then down the given process-engineering address, and
delivers the value of the WLS-Longtext.

Example

GETWLS(3,"LS.EM.230EM")

3.7.9.15. CONCATBIN ()

CONCATBIN(Par1, Bits1 [, Par2, Bits2, ...])

This function determines a number whose first n Bits (Bits1) match the value of the parameter Par1, and
whose next n Bits (Bits2) match the value of the parameter Par2 etc. Abbreviation: CB

3-74 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

Example

CONCATBIN(O1,8,O2,8) -> delivers 16 Bit number

3.7.9.16. GETprep()

GETprep()

This function delivers the value of the prepared flag (Lk_Prep). The following results of this Formula are
possible: 0 for image "activated", 1 for image "prepared", -1 if the image does not have a prepared flag.
(higher-value Images have no Prepared-Flag)

3.7.9.17. LEVEL()

This function delivers the hierarchy level of the image, in which the Formula is defined, as a number.

The hierarchy level of an image is produced from the number of Levels to the lowest Level starting from
the image. An image in the Link-level is located in the hierarchy level 1, an image in the Signal-level is
then located in the hierarchy level 2, etc.

In the above mentioned example, for the feeders the following Levels are to be found

Abzweig_1

Levelname Levelnumber Hierachy

Abzweig 4 4
(ABZ

LS 3 3
(BTR)

BEF 2 2
(SIG)

1703, 230 1 1

TOOLBOX II Users Manual D30-500-1.05 3-75

 OPM II

(LNK)

Abzweig_2

Levelname Levelnumber Hierachy

Abzweig 4 4
(ABZ

BEF 2 2
(SIG)

1703, 230 1 1
(LNK)

For feeder 1 no Levels have been skipped, i.e. the level number always corresponds with the hierarchy
number. For feeder 2 the operational equipment level has been skipped, i.e. level- and hierarchy
number are different above the signal level.

Example

LEVEL()

in an infotype of LS of the feeder 1 delivers 3

3.7.9.18. LEVELROOT()

This function delivers the Hierarchy Level of the relevant root image.

Example

LEVELROOT()

If the formula is defined in an optional Infotype, then the result is always 4 since the Images in this
example always hang on the ABZ Level.

3.7.9.19. LEVELDISTROOT()

This function delivers the number of Hierarchy levels from the image in which the Formula is defined, to
the root-image.

3-76 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

Example

LEVELDISTROOT()

If the formula is defined in an infotype of the feeder, then the result is 1. If the formula is defined in an
infotype of the LS, then the result is 2.

3.7.9.20. GetBinInfo(Infotype, StartBit, NoOfBits)

The function executes a binary operation. Based on the start bit (StartBit) and the number of bits
(NoOfBits) a new integer value is returned.

Example

GetBinInfo("FieldNumber", 0, 2)

The first 2 bits are masked out and returned as integer value.

FieldNumber = 4 result = 0
FieldNumber = 5 result = 1

3.7.9.21. GetBin(Parameter, StartBit, NoOfBits)

The function behaves exactly like GetBinInfo with the only difference being, that the source is a
parameter.

3.7.9.22. CONCATBIN(Par1, Bits1 [, Par2, Bits2, ...])

This function determines a number whose first n Bits (Bits1) match the value of the parameter Par1, and
whose next n Bits (Bits2) match the value of the parameter Par2 etc. Abbreviation: CB

Example

CB("CASDU1", 1, "CASDU2", 1)

The first bit of CASDU1 and CASDU2 is returned as result. Thereby the first parameter represents the
Low Byte.

CASDU1 = 1 CASDU2 = 0 result = 1

CASDU1 = 0 CASDU2 = 1 result = 2
CASDU1 = 1 CASDU2 = 1 result = 3

TOOLBOX II Users Manual D30-500-1.05 3-77

 OPM II

3.7.9.23. CONCATBIN(Par1, Bits1 [, Par2, Bits2, ...])

The function behaves exactly like CONCATBIN only with the difference, that the source is a parameter.
Abbreviation CBI.

3.7.9.24. IOM(Parameter1, Width1 [, Parameter2, Width2, ...])

The function fetches the value of parameter 1 formats the value using HSTR into a hexadecimal-string
with the given width, and then fetches the next given parameter etc. The individually determined
hexadecimal strings are then composed together. If the width of the formatting specification is shorter
than the value of the parameter, then the hexadecimal string is truncated to the given width.

Example

IOM("CASDU1", 2, "CASDU2", 2)

CASDU1 and CASDU2 are converted to hexadecimal and the result string truncated to 2 characters.
Both strings are then joined together as result.

CASDU1 = 10 CASDU2 = 11 result = 0a0b

3.7.9.25. IOMInfo(Infotype1, Width1 [, Infotype2, Width2, ...])

The function behaves exactly like IOM only with the difference, that the source is an infotype.

3-78 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.8. Levels

3.8.1. Overview

By defining of levels it is defined

N which steps the process-technical address comprises

N what the hierarchical relationships between these steps are

The levels are

N freely selectable within a process-technical plant

N can be extended at any time

N can only be deleted if no objects have been defined on this level

When defining levels it must be taken into account that the hierarchical relation is to be specified
correctly, i.e., the hierarchically highest object is to be defined in the uppermost line.

The last two VT levels having the short designations SIG (signal level) and LNK (link level) cannot be
deleted by the user (but renamed).

TOOLBOX II Users Manual D30-500-1.05 3-79

 OPM II

3.8.2. Handling

Procedure

SYSTEM | DEFINE LEVELS

M-CLICK-R | EDIT INSERT LINES

Entering of name and short designation of the VT levels

SYSTEM | SAVE

3-80 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.9. Library

3.9.1. AU objects overview

AU objects are predefined automation units directly available in the OPM in the form of libraries.

The use of AU objects brings about the following advantages:

N Predefined functions and HW/FW configuration of an AU

N Direct application of AU's from the OPM

N Functionalities that can be expanded or changed at any time

TOOLBOX II Users Manual D30-500-1.05 3-81

 OPM II

3.9.2. AU objects handling

The AU objects are used to create new AU's directly from the library

Opening the libraries in the OPM

TOOLS | LIBRARY OVERVIEW

The opened window contains two tabs, the right tab contains the actual AU objects, subdivided into
market sectors. When selecting an AU, a tool tip will appear, offering a short description of the AU
object. Double-clicking on the AU object will open it, and the HW/FW configuration can be viewed.

For actual HW/FW configuring of this AU object, the System-Technical Overview must be opened, as
well.

TOOLS | SYSTEM-TECHNICAL OVERVIEW

Now, you can use a drag and drop operation to simply drag the desired AU directly into the System-
Technical Overview. Following this drag and drop operation, a wizard will appear that requests the
necessary information (such as region number, component number, etc.) and creates the desired new
component.

3-82 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

Following this procedure, the automation unit will be fully HW/FW configured and the various peripheral
elements can be parameter-configured directly from the OPM.

TOOLBOX II Users Manual D30-500-1.05 3-83

 OPM II

3.10. Bulk editing

3.10.1. Overview

The mass-editing enables the simple and fast editing of large quantities of values of the images in table
form.

N In the lines, all VTA's of the images are displayed which correspond to the search expression

N In the columns, an excessive quantity of all attributes is displayed.

N Values that do not exist for an image are identified (with "--") and cannot be edited

N References and formulae are colour-coded

N All Standard Table Functions of the TOOLBOX II are available (filling, copying, auto-increment,
automatic text formation,..)

N The table structure can be stored for Export. (If e.g. "Quantities of data" that are often used are
defined to non-SAT manufacturers)

N Column layout:

It is possible to define a set of columns under a specific name. On opening the bulk editing, by
selection of such a set of columns, the defined columns are automatically selected and displayed.
When doing this, the position, the width and the font are also saved.

3-84 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.10.2. Handling

The selection of the quantity of data can take place in several ways:

With Drag&Drop of images in the Mass editing

With Drag&Drop of Types in the Mass editing

Entry of a VTA search expression (with wildcard functionality)

Drag&Drop a parameter of a Type or of an image in the Mass editing

Drag&Drop from the System engineering in the Mass editing

3.10.2.1. Drag&Drop of Images in the Mass Editing

Tools | Images

(if not yet open)

Tools | Mass editing

Drag&Drop one or several Images in the Mass editing

After this selection the Videorecorder is displayed in the Mass editing.

3.10.2.2. Drag&Drop of Types in the Mass Editing

TOOLS | TYPES OVERVIEW

(if not yet open)

TOOLBOX II Users Manual D30-500-1.05 3-85

 OPM II

TOOLS | MASS EDITING

Drag&Drop one of the selected types in the Mass editing

After this selection the Videorecorder is displayed in the Mass editing.

3.10.2.3. VTA Search Expression

TOOLS | MASS EDITING

In the blank Mass editing

M-CLICK-R | VTA-TEXT SEARCH

With the VTA-Text search all Images are displayed in the Mass editing based on their names (Wildcards
such as * ? are allowed)

3-86 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

After selection by means of the wildcard search the Videorecorder is displayed in the Mass editing.

3.10.2.4. Drag&Drop a parameter from the Image

TOOLS | MASS EDITING

TOOLS | IMAGES

DRAG&DROP A PARAMETER IN THE MASS EDITING

In the Mass editing now all Images are displayed that contain the parameter and have the same value
as that selected. Example: the parameter Lk_Reg is drawn into the Mass editing and in the image has
the value 100. In the Mass editing all Images are displayed in which the parameter Lk_Reg occurs and
which have the value 100.

3.10.2.5. Selection of a parameter from the Edit Type (parameter tab)

TOOLS | MASS EDITING

TOOLS | TYPE OVERVIEW | PARAMETER TAB

DRAG&DROP THE REQUIRED PARAMETER IN THE MASS EDITING

In the Mass editing now all (also typeless) Images are displayed that contain the selected parameter,
regardless of the value entered.

TOOLBOX II Users Manual D30-500-1.05 3-87

 OPM II

3.10.2.6. Drag&Drop from the System Engineering in the Mass Editing

TOOLS | MASS EDITING

TOOLS | SYSTEM ENGINEERING

The following Drag&Drop actions are possible

Drag&Drop a region in the Mass editing | all Images are displayed in which the selected region is
entered in the link address.

Drag&Drop a component in the Mass editing | all Images are displayed in which the selected region
and component are entered in the link address.

Drag&Drop a Basis System Element (BSE) in the Mass editing | all Images are displayed in which the
selected region-, component- and BSE-number are entered in the link address.

Drag&Drop a peripheral element (PE) in the Mass editing | all Images are displayed in which the
selected region-, component- and BSE-number as well as the peripheral element are entered in the link
address.

The list of the data can be stored with the table setup.

3-88 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.10.3. User interface

Smarticon-bar in the mass-editing

In the mass-editing the functions required mostly are also represented as Smarticons.

For each Smarticon, a Tooltip is superimposed explaning the respective function of the Smarticon.

Tooltips in mass-editing

If several parameters which have the same names are displayed in the mass-editing e.g. Lk_REG, then
it is possible to identify the destination system by displaying the Tooltip of the respective column-
heading.

In other words, the destination system for each parameter is displayed in the Tooltip.

There is already a selection of individual parameters for each destination system for the data-
compilation with the Video Recorder.

Fixed Font in the mass-editing

It is possible to define for each column, whether these are to be displayed in Fixed-Font or Proportional-
Font. This setting is used by the user to improve identification of possibly existing textual errors. With

SELECT THE ENTIRE COLUMN | RIGHT MOUSE BUTTON | FORMAT COLUMNS | FIXED FONT OR PROPORTIONAL
FONT

the display of the respective text can be changed.

Note:

These settings are naturally also saved with "Save table structure"

TOOLBOX II Users Manual D30-500-1.05 3-89

 OPM II

3.10.4. Wildcard selection

In contrast to the VTA text-search, the VTA wildcard search takes the association of the images to
levels into account. Inaddition it is possible to define the relationship of images to each other in the
search.

After selecting the POP UP menu item VTA Wildcard Search, the following dialogue is displayed in
which each level in the OPM is displayed in its own line:

In which level are the sought after images?

In this Dropdown Listbox that level is selected, that contains the sought after images.

Note:
In the mass-editing only data is displayed that contains parameter Types or Info Types. If a level is
selected (e.g.: SIG), that has no parameters, then an notification dialogue appears:
The selected images have no parameters

Which images of the above selected level are to be taken into account during the search?

In the search expression, the names of images of the selected level can be restricted. The following
Wildcards can be used:

? .. stands for any individual character

$ .. stands for 1 - n characters
* .. stands for 0 - n characters

Note:
If all images of this level are to be returned, the option All must be selected.

3-90 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

Relationships of the above selected images to images of other levels.

With this input, the search result can be further restricted. For each level the following can be defined:

N level must not have any images: Only those images are returned which have not been used in
this level in the VTA.

N level can have images (0-n): It is irrelevant for the result quantity, whether in the VTA an image
of this level has been used or not. (Default setting)

N level must have images with the selected search expression: Only those images are returned
which correspond to the defined search expression in this level in the VTA. The Wildcards *,$,?
can also be used in this search expression.

N level must have at least one image: : Onlythose images are returned which have been used in
this level in the VTA.

Example:

All Info Types are to be displayed in the mass-editing that have been defined directly in the signals with
the names X0*.

Solution:

N In which level are the sought after images located? :

SIG

N Which images of the above selected level are to be taken into account during the search?:
Search expression: X0*

N Relationships of the above selected images to images in other levels:

level can have images (0-n) (for all levels)

TOOLBOX II Users Manual D30-500-1.05 3-91

 OPM II

3.10.5. Column layout

3.10.5.1. Saving a Column Layout

In the bulk editing, with the popup menu item:

COLUM LAYOUT | SAVE

the user can save a particular column layout under a specific name.

N The column layout includes:

N which columns are displayed

N the respective column width

N the respective column font

N the position of the column in the table.

The column layout is saved per range and contains absolutely no description of the data which are
displayed in the spreadsheet (see Table Structure).

3.10.5.2. Deletion of a Column Layout

With the menu item:

COLUMN LAYOUT | DELETE

one or more column layouts defined in the bulk editing can be deleted.

3-92 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.10.5.3. Selection of a Column Layout

When selecting the columns for the bulk editing within the framework of data acceptance, the dialog can
be expanded via the "Extended >>" button by selecting already predefined column layout.

If the user selects a marked layout from the list with a double click or with the "Apply column layout"
button, then the "selected entries" are updated with the columns of the chosen layout.

Note:
This selection remains active beyond the program run until the user loads another selection. If a table
structure is loaded by the user then the column layout which is saved in the table structure applies.

TOOLBOX II Users Manual D30-500-1.05 3-93

 OPM II

3.11. Source data management

3.11.1. Overview

The source data management is the interface of the OPM to external programs. With this interface the
importing to and exporting of data from the OPM is possible.

Selection of the particular action of the source data management is done via the menu items:

TOOLS | SOURCE DATA MANAGEMENT | IMPORT...

TOOLS | SOURCE DATA MANAGEMENT | EXPORT...

The data exchange is done with the Common OPM Format (COF), for which a new format has been
defined for more extensive import and export possibilities as from Version 3.11 of the TOOLBOX II.

In order to keep compatibility with old versions of the COF file, via the dialog

EXTRAS | OPTIONS | GENERAL

the source data manager in the format up to Version 3.10 can be activated.

3-94 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

The importing and exporting of data can be done in 2 ways:

N Interactively via the Source data management dialogs Import or Export

N All commands can be started either manually via the command line or by means of control
through a batch file with the SDC Source Data Management Commandline which is a text mode
version of the source data manager.

The source data management provides a multitude of importing and exporting functions for OPM data
which extend from the accepting of values, creating of typeless or typed images and infotypes up to the
deleting and renaming of images. (See Functions)

TOOLBOX II Users Manual D30-500-1.05 3-95

 OPM II

3.11.2. Import

Under the term "Importing of engineering data" is understood the interpretation of the contents of a COF
file and the accepting of the data into the OPM data structure.

For this, the following is to be noted:

N The file is read-in in sequential sequence (line by line)

N Every line is checked for its syntax

N The data are checked for their plausibility (value ranges etc.)

N The function which is defined for a line in the file is executed in the OPM

3.11.2.1. Functions when importing

The importing of a COF file into the OPM can be done in two different ways:

INTERACTIVELY BY THE USER WITH THE MENU ITEM:

TOOLS | SOURCE DATA MANAGEMENT | IMPORT

Batch-controlled via a special version of the source data manager ("SDC Source Data Management
Commandline")

Depending on which of the two above methods the user uses to import a COF file into the OPM, all
successfully carried out events or errors which have occurred are output as an event log either to the
user interface of the OPM or into a corresponding log file.

3-96 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

Each event which is triggered by a COF file is immediately effective in the OPM, i.e. each line can build
on the results of the preceding line. Within an individual COF line the columns are executed from left to
right.

Note:
If an error occurs in a line then all the actions previously carried out are reversed.

3.11.2.1.1. Event Log

When importing, the so-called "event log" is output on the user interface of the OPM in order to show
the user whether all actions have been correctly carried out. For this, the event log contains the VTA of
the image on which the event was used. If, on execution of a particular event, an error occurs, the
nature of the error is entered into the event log too.

Note:
As several actions (e.g. create image and accept values) can be triggered in the OPM by a line in the
COF file, it can happen that for one line in the COF file there are several lines in the event log.

3.11.2.1.2. Formulas/References

When importing, the user can give whether values of attributes should be accepted from the COF file
which in the OPM are destinations of references or formulas.

If the values should be accepted, then the SDM behaves as follows:

If the value which is imported is not equal to the value in the OPM then the reference/formula allocation
is cancelled. If the value which is imported is equal to the value in the OPM then the reference/formula
allocation is retained.

Note:
If a reference source or a formula input is changed, then the corresponding destinations are updated.

3.11.2.1.3. Change Report

When importing, by means of Option the user can have shown the changes which arise due to the
importing of the COF file. All images and their values which change are then displayed in a
spreadsheet.

TOOLBOX II Users Manual D30-500-1.05 3-97

 OPM II

The following changes are shown in this change report:

N Value changes

N New images

N Deleted images

N Renamed images

N Created infotypes

If the user has selected the "Change report" option then, after displaying the change report, only those
data which will change are actually imported.

Note:
In the change spreadsheet it is possible to remove individual data records (lines) from the importing
process, i.e. you can choose not to accept certain changes which would result due to the importing.

3.11.2.2. Log file

When importing (interactively in the OPM or batch-controlled by means of SDC) it is also possible to
write into a log file the event log which is output on the user interface of the OPM. The path can be
freely given by the user.

3-98 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

When importing, the user has the possibility of choosing the type of log file processing:

N The log file is overwritten

N The log file is appended to an existing log file

N The log file automatically gets the date and time appended to the file name, i.e. on each importing
process, a unique name is generated

Note:
If no path is given for a log file then the file is at:

%SATTBII_TMP%\[WindowsUser].

If no name is given for a log file then, as standard, a file "SDM_IN.LOG" is created in the path:

%SATTBII_TMP%\[WindowsUser]

3.11.2.2.1. The "EOW_IN.DAT" File

On every import process, a file "EOW_IN.DAT" is written in the folder into which the log file is written.

Note:
If no path was given for a log file then the file is at:

TOOLBOX II Users Manual D30-500-1.05 3-99

 OPM II

"%SATTBII_TMP%\[WindowsUser].

The file looks as follows:

Start: <Date and time>

User: <Toolbox user>
Customer: <Customer long text>
Plant: <Name of the process-technical plant>
Range: <Name of the first affected range>
Range: <Name of the nth affected range>
End: <Date and time>
State: <A status of whether the import process was successful or not.
Possible values are OK and NOK.>

Note:
Error messages are not written into this file because these are simultaneously logged in the log file. The
file "EOW_IN.DAT" is deleted on each importing process.

3.11.2.3. Separating Character

When importing, the separating character for the COF file can be given by the user. As standard, a
semi-colon is preset. (A change by the user is only necessary if another separating character has been
used in the COF file.)

3-100 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.11.2.4. Preprocess and Postprocess

When importing, the user has the possibility of starting any preprocess before the start of the importing
process from the COF file, or any postprocess at the end (e.g. an EXE file, a batch job etc.).

Applications: Fetching or sending the COF file via FTP, preprocess the COF files, delete old log files
etc.

Note:
The importing process is only started if the preprocess could be started. The postprocess is also started
if, in the preceding importing process, an error occurred. The preprocess and postprocess do not exist
in batch-controlled mode.

3.11.2.5. SDM Settings

The settings which the user has carried out when importing (log file name, COF file name, preprocess,
postprocess etc.) can be stored by the user under a specific name and reloaded.

By choosing the "Extended" button, the dialog is supplemented by the "Load", "Save" and "Delete"
buttons. With these buttons

EXPAND | LOAD

EXPAND | SAVE

EXPAND | DELETE

predefined configurations can be saved, loaded and deleted.

TOOLBOX II Users Manual D30-500-1.05 3-101

 OPM II

Note:
If the settings are not explicitly saved, then the SDM notes the last settings which were defined during
the SDM import.

3.11.2.6. Compatibility with Toolbox Version 3.10

In the OPM the user can, in 'Extras', put with which SDM version he would like to work "Old" (up to
Version 3.10) or "New" (as from Version 3.11).

EXTRAS | OPTIONS | GENERAL

3-102 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.11.2.7. Across-range Importing

With the SDM it is possible to import across several ranges, i.e. by means of the "RANGE" column you
can control on which range in the OPM the action of the COF file should be carried out.

Note:
If a column number is not given in the COF file then the action is executed in the range in which the
user is now working ("preset range "), otherwise the range name is taken from the COF file.

Execution sequence of the ranges when importing.

If several ranges are given in the "RANGE" column in a COF file then first all actions are carried out
which affect the current range, and then the actions are further executed range by range.

TOOLBOX II Users Manual D30-500-1.05 3-103

 OPM II

3.11.3. Export

Under the term "Export" the OPM understands the writing of data of the OPM into a COF file. The
following data can be exported from the OPM:

N Images

N Values of parameter types

N Values of infotypes

N The parameter category

N The ready flag

N Lk_DS

N Lk_Env

For this, with the menu item

TOOLS | SOURCE DATA MANAGER | EXPORT

in the user interface of the OPM, the user interactively defines a table whose contents are converted
with the context menu

EXPORT

into the Common OPM Format and written into a COF file. Alternatively, the exporting can be started
with the "Export" smart button.

For this, each row of the table contains as an individual column the attributes of any image of the OPM.
Which attributes or which images the table should contain can be defined completely freely by the user
via operator prompting similarly arranged as in the Bulk Editing .

3.11.3.1. Functions when exporting

When exporting, the user can give which data should be generated in the COF file which is generated
when exporting. The following options can be chosen:

3-104 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

N Export for changes of values

The data are so written into the COF file so that, by means of this file, values can be accepted
into another OPM (corresponds to the 'U' function). The corresponding images must be present
on importing this file.

N Export for new creations of images

In principle, this function behaves in the same way as the "Export for changes of values" function.
The COF file is, however, so coded that, on importing of the COF file into another OPM, all the
images which are not present there are newly created. If an image already exists, its values are
updated (corresponds to the 'I' function).

The prerequisite for the new creation of the images is that both OPMs have the same default
inputs and types (important when importing).

N Export of changed images

In principle, this function behaves in the same way as the "Export for changes of values" function.
However, only the changes since the last export into the COF file are written. (Relates to the
preselected images in the table).

TOOLBOX II Users Manual D30-500-1.05 3-105

 OPM II

N Export plain texts

When exporting, the user has, by means of Option, the possibility of choosing whether the
internal keys or the plain texts are written into the COF file.

Note:
COF files in which there are plain texts cannot be re-imported. This function is only used for
documentation purposes.

N Table structure

The table structure can be taken either from the displayed data or from a stored schema.

Note:
When exporting, attention need not be given to formulas and references.

3.11.3.2. Log file

When exporting, it is possible to have the event log which is output on the user interface of the OPM
additionally written into a log file. The behaviour of the log file is as when importing.

When exporting, the user has the possibility of selecting the type of log file processing:

N The log file is overwritten

3-106 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

N The log file is appended to an existing log file (if a log file with this name already exists)

N The log file automatically gets the date and time appended to the file name, i.e. on each importing
process, a unique name is generated.

Note:
If no path is given for a log file then the file is at:

%SATTBII_TMP%\[WindowsUser].

If no name is given for a log file then, as standard, a file "SDM_OUT.LOG" is created in the path

%SATTBII_TMP%\[WindowsUser]

3.11.3.2.1. The "EOW_OUT.DAT" File

On every export process, a file "EOW_OUT.DAT" is written in the folder into which the log file is written.
If no path was given for a log file then the file is at :

%SATTBII_TMP%\[WindowsUser].

The file has the same appearance as the file "EOW_IN.DAT".

Start: <Date and time>

User: <Toolbox user>
Customer: <Customer long text>
Plant: <Name of the process-technical plant>
Range: <Name of the first affected range>
Range: <Name of the nth affected range>
End: <Date and time>
State: <A status of whether the export process was successful or not.
Possible values are OK and NOK.>

3.11.3.3. Postprocess

When exporting data, the user has the possibility of starting any post-process (e.g. an EXE file or a
batch job) after the COF file has been completed On starting this postprocess, the OPM II transfers the
COF file, which was generated by the OPM II during the exporting process, to the postprocess as an
input parameter.

Applications: Sending the COF file via FTP, deleting old log files etc.

TOOLBOX II Users Manual D30-500-1.05 3-107

 OPM II

Note:
The postprocess is also started if a fault occurred beforehand.

3.11.3.4. Separation Characters

The separation character which should be written into the COF file when exporting can be freely defined
by the user on the user interface. In addition, it is possible to choose the line terminator and the value
label.

3-108 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.11.3.5. SDM Settings

The settings which the user has made when exporting (log file name, COF file name, Postprocess etc.)
can, as for importing, be stored by the user under a specific name and reloaded.

By choosing the "Extended" button, the dialog is supplemented by the "Load", "Save" and "Delete"
buttons. With these buttons

EXTENDED | LOAD

EXTENDED | SAVE

EXTENDED | DELETE

predefined configurations can be saved, loaded and deleted.

TOOLBOX II Users Manual D30-500-1.05 3-109

 OPM II

Note:
If the settings are not explicitly saved, then the SDM notes the last settings which were defined during
the SDM export (across programs).

3.11.3.6. Compatibility with Toolbox Version 3.10

In the OPM, in 'Extras' the user can put with which SDM version he would like to work ("Old" (Version
3.10) or "New" (Version 3.11).

EXTRAS | OPTIONS | GENERAL

3-110 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.11.3.7. Distributed Working

When exporting, the original descriptor need not be given because no data are changed in the OPM.

TOOLBOX II Users Manual D30-500-1.05 3-111

 OPM II

3.11.4. SDC Source Data Manager Commandline

The SDM also exists in a text-mode version. This enables a user to import a COF file or export to a
COF file. The text-mode version of the SDM can be started either manually via the command line or by
controlling with a batch file.

In the Toolbox Version 3.10 this text-mode version is called "SDM". In the process of definition of a new
syntax for the COF format, there is - as from Version 3.11 - a second text-mode version which has the
name SDC (Source Data Manager Command line). In addition, the command line version has been
expanded by "batch-controlled exporting".

3.11.4.1. Importing

The syntax for batch-controlled SDM importing is as follows:

Usage: SDC.EXE IN username/password /P:VAN-ANL-ID [/R:Rangename] [/I:COF-

File] [/A:LOG-File] [/D:Delimiter] [/E] [/F] [/L:O|A|D]

Parameter Meaning Optional Default

IN Indicates that importing is No -

concerned

username/password Name of the TOOLBOX II No -

user
Password of the
TOOLBOX II user

/P Process-technical plant ID No -

/R Range name Yes -

/I Name of the COF file (inc. Yes COF_IN.CSV

path)

/A Name of the log file (inc. Yes SDM_IN.LOG

path)

/D Separating character of Yes -

the COF file

/E Level separating Yes -

character in image names

/F Import values for Yes -

reference or formula
destinations

/L:O|A|D Log file strategy: Yes /L:O

O: Overwrite
A: Append
D: Date and Time

If one of the above file names is not given, the SDC uses the name or settings given in the "Default"
column. If no path is given for both files then the SDC takes the folder as the path for these files.

%SATTBII_TMP%\[WindowsUser].

3-112 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

If a range name is transferred, then only those lines in the COF file which affect this range are
evaluated. If no range name is transferred then the ranges are taken from the "RANGE" column in the
COF file. The sequence of execution is the same as for an importing procedure from the user interface
of the OPM.

3.11.4.2. Exporting

The syntax for batch-controlled SDM exporting is as follows:

Usage: SDC.EXE OUT username/password /P:VAN-ANL-ID /R:Rangename [/I:COF-

File] [/A:LOG-File] /T:Table structure name [/O:U|I] [/C] [/L:O|A|D]

Parameter Meaning Optional Default

OUT Indicates that exporting is No -

concerned

username/password Name of the TOOLBOX II No -

user
Password of the
TOOLBOX II user

/P Process-technical plant ID No -

/R Range name Yes -

/I Name of the COF file (inc. Yes COF_OUT.CSV

path)

/A Name of the log file (inc. Yes SDM_OUT.LOG

path)

/D Separating character of Yes -

the COF file

/E Level separating Yes -

character in image names

/F Export values for Yes -

reference or formula
destinations

/L:O|A|D Log file strategy: Yes /L:O

O: Overwrite
A: Append
D: Date and Time

/T Table structure in the No -

OPM

/O:U|I Exporting strategy: Yes /O:U

U: Export for value
change
I: Export for new creation

/C Export changed images Yes -

The batch-controlled exporting determines which data have to be exported based on the transferred
table structure.

TOOLBOX II Users Manual D30-500-1.05 3-113

 OPM II

3.11.5. Common OPM-Format (COF)

A COF file is an ASCII file which is constructed in accordance with the Comma Separated Values
Format (CSV format). The CSV format is a format which is standardised and widespread in the EDP
world for the displaying of data which are represented in the form of tables.

As engineering data are usually signal orientated and, therefore, usually managed in the form of tables,
a COF file is especially well suited for the exchange of engineering data and is used for importing and
exporting in OPM with the help of the source data manager.

A table with engineering data is represented in such a way in the COF format that each table row shows
a line and each table cell shows a value in the line in the COF file.

Representation of a COF file

N Separating characters

The individual cell contents of the table are separated from one another in the COF file by a
separating character which can be freely defined by the user. The default for the separating
character in a COF file is a semi-colon. When reading a COF file into or out of the OPM, however,
the user can choose another separating character by means of an option dialog. (The separating
character must only be one character).

N Empty cell

If the contents of a cell in the table are empty then, in the COF file, two separating characters
follow immediately one after the other. If the first column of a table row contains no value, the first
character in the line of the COF file is a separating character. If the last column of a table row
contains no value, in the COF file the line change immediately follows a separating character.

3-114 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

N Empty text

If the contents of a table cell are empty text, this is transmitted into the COF file as two quotation
marks one immediately after the other. In accordance with the convention of the CSV format, the
COF file supports both leading and trailing blank characters of a table cell and these are
interpreted by the OPM as such when a COF file is imported.

N Character set

When importing or exporting a COF file, the OPM does not carry out any character set
conversion, i.e. the data of a COF file are always processed by the OPM II in the character set
which is currently set on the computer of the OPM II.

In principle, a COF file consists of a number of fixed, pre-input columns - the "fixed columns" - and
any number of "free columns"

3.11.5.1. "Fixed" Columns

The designations and the sequence of the individual columns looks as follows:

N FUNC (Action which should be carried out)

N RANGE (Range name of the range in which the action should be carried out)

N The "LEVEL COLUMNS" (Short text of the individual levels)

N NEWNAME (New name when renaming an image)

N DEFAULT (Name of the default input via which an image should be created)

The sequence of these fixed columns in the COF file is compulsory. "Fixed" columns are language-
independent.

3.11.5.1.1. The "FUNC" Column

In the "FUNC"(= Function) column the user defines which action should be carried out with the image
which is defined in the row. The "FUNC" column must always be filled in with a value.

The following values are permitted for the "FUNC" column:

N U (Update)

- Accept values from the COF file into the OPM

- Rename an image

N I (Insert)

- Create a new image (typed or typeless)

- Accept values from the COF file into the OPM
- Attach the infotype to a typeless image

TOOLBOX II Users Manual D30-500-1.05 3-115

 OPM II

N D (Delete)

- Delete image

3.11.5.1.2. The "RANGE" Column

In this column is the range name of the range on which the action of the row should have an effect.

This column need not be compulsorily filled in. If this column is not filled in then the given action is
carried out on the range of the OPM which is currently preset for the user.

If a range name other than the one preset for the user is in this column then the action is carried out in
the given range.

Sequence of execution

N All lines in the COF file which concern the current range

N All other lines in the COF file, i.e. these lines are executed range by range

3.11.5.1.3. The "Level Columns"

The so-called "Level Columns" represent the individual levels in the OPM.

The name of the individual columns comes from the short text (1-3 characters) of the levels which are
defined in the OPM. The sequence of the columns of the level short texts is in decreasing order, i.e. the
short text of a level which is higher in the hierarchy comes before the short text of a lower level. The
level short texts must be unique.

3.11.5.1.4. The "NEWNAME" Column

If an image is to be renamed, this column contains the new image name of the image.

Note:
This column need not be compulsorily filled in (Action Insert)

3.11.5.1.5. The "DEFAULT" Column

If a new image is to be created, the DEFAULT (= Default Input) column contains the name of the default
input based on which the image is being created. The default input must already exist in the OPM.

Note:
This column need not be compulsorily filled in (Action Insert)

3-116 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.11.5.2. "Free" Columns

The designations of the free columns are names of parameters or Infotypes of the images. All these
names must, therefore, correspond to the appropriate definitions in the OPM. This means that for each
free column of the COF file there must always be a parameter or infotype in the OPM.

Note: The parameter types and infotypes of the "free" columns are language independent.

Importing

If the attributes of the free columns are displayed on the user interfaces of the OPM in the form of plain
texts, the corresponding columns in the COF file contain as values the so-called keys to these plain
texts. A key is the internal representation of a plain text in the TOOLBOX II.

Example: Parameter formula (Destination system SAT 250):

Plain text = "Yes"; Key = "Y"

Plain text = "No"; Key = "N"

It is permissible for any of the free columns to have no value.

Exporting

When exporting it is possible to give, by means of an option, whether the internal keys or the
corresponding clear texts should be exported.

Exported plain texts cannot be imported again because, when exporting, the internal key is needed in
order to be language-independent. This function is only used for documentation purposes.

Note: The names of the free columns must be unique. (Example: In one COF file there must not be two
columns with the designation "Lk_Reg")

3.11.5.3. Example of the Structure of a COF File

The first three lines of a COF file could, for example, look as follows, for which 5 levels are defined in
the OPM (PLT, AGG, DEV, SIG and LNK):

FUNC;RANGE;PLT;AGG;DEV;SIG;LNK;NEWNAME;DEFAULT;Lk_Reg;Lk_Comp;TXT
I;;ST-Sdm;North;CB;CMD0000;DI_SI_A;;DV_SI;;;
I;;ST-Sdm;North;CB;CMD0000;DI_SI_B;;;10;2;Yes

TOOLBOX II Users Manual D30-500-1.05 3-117

 OPM II

3.11.6. Functions

3.11.6.1. Overview of all functions

By means of a Common OPM Format (COF) file, the following actions can be carried out in the OPM via
the source data management:

N Update values

N Create a typeless image

N Create a typed image (by means of default input)

N Create a typed image (by means of default input) and update values

N Delete an image

N Rename an image

N Rename an image and accept values

N Create an infotype (below a typeless image)

Syntax for the individual actions

In the following table the syntax in the COF file is described, i.e. which columns must be filled in for
which action:

FUNC RANGE Level NEWNAME DEFAULT Free Description

columns columns

"U" O X - - X Update
values

"I" O X - - - Create a
typeless
image

"I" O X - X - Create a
typed image

"I" O X - X X Create a
typed image
and update
values

"D" O X - - - Delete an
image

"U" O X X - - Rename an
image

"U" O X X - X Rename and

image and
update
values

"I" O X - - X 1) Create an
infotype and

3-118 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

update
values

1)
The "free" column must name an infotype

Meaning of characters:

X .. This field must be filled in

O .. This field can be filled in (optional)

- .. This field must not be filled in

TOOLBOX II Users Manual D30-500-1.05 3-119

 OPM II

3.11.6.2. Update values

The function "Update values" allows the changing of the values of any typeless or typed image of the
OPM. For this, it does not matter whether this image is a root image or a subimage.

The attributes of an image are:

N Parameter types

N Infotypes

N Lk_Cat (Parameter category)

N Lk_Prep (Preparation flag)

Note:
Parameter types occur only in link images!

The values of the following attributes of an image cannot be updated by means of SDM because these
values serve only as information.

Lk_DS (Destination system)

Lk_Env (Transformed flag)

Example: Update values

If you open the image "CaexAx" in the image tree at the link level "CMD0000" then you can see all its
parameters as illustrated in the following diagram:

3-120 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

In order to accept the value of the parameter "Long text", the COF file must look as follows:

FUNC;RANGE;PLT;AGG;DEV;SIG;LNK;NEWNAME;DEFAULT;Longtext
U;;ST-Sdm;North;CB;CMD0000;CaexAx;;;"New text"

"New text" is accepted as the new value for the "Longtext" parameter in the image "ST-
Sdm.North.CB.CMD0000.CaexAx".

TOOLBOX II Users Manual D30-500-1.05 3-121

 OPM II

3.11.6.3. Create typeless images

The function "Create a typeless image " allows the creation of typeless images in the OPM.

When using this function, note the following:

Typeless images can be created at each level as subimages of already existing typeless images
(depending on the option in the OPM).

Typeless link images can only be appended to typeless signal images.

Typeless images can be created at every level (depending on the option in the OPM)

Existing typeless images are not recreated

Levels can be left out

Example: Create a typeless image

In the image tree shown, the following COF file was imported by means of SDM in order to create
typeless images.

FUNC;RANGE;PLT;AGG;DEV;SIG;LNK;NEWNAME;DEFAULT
I;;ST-Sdm;West;;;;;
I;;;East;CB;;;;

After the importing process, the following images are in the OPM:

As can be seen, a typeless image "West" has been created below the typeless image "ST-Sdm" (Line 1
in the COF file). Besides this, a typeless root image "East" has been created at the "AGG" level with a
typeless child "CB".

3-122 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.11.6.4. Create type images

3.11.6.4.1. Create a Typed Image by Means of Default Input

The function "Create a typed image" enables the creation of a typed image in the OPM. The basis for
the new creation of a typed image illustrates the concept of the default input:

On each new creation of a typed image, in the COF file the user must give which default input will form
the basis for the creation of the new image. The default input is uniquely identified by its name.

As a corresponding default input must already exist at the time of this function, it is ascertained - based
on the default input - at which level the typed image is to be created. The corresponding typed image is
then generated from this default input.

If the default input describes the structure of a higher value image (e.g. a feeder with corresponding
disconnectors, signals, links and parameters) then the newly created image consists of exactly the
same structure. Therefore, a complete "image tree" thus arises.

When using this function, note the following:

N The level at which the typed image is created arises from the default input

N A default input with corresponding name must exist

N Levels can be left out

N The typed image can be created as the child of a typeless image

N The typed image cannot be created as the child of a typed image

N If the image already exists then no attempt is made to recreate it (i.e. the default input is ignored)

Example: Creation of a typed image (by means of default input)

In order to extend the "North" feeder by a further circuit breaker, the following COF file must be imported
for which the corresponding default input has the name "DV_CB" and lies at the "DEV" level.

FUNC;RANGE;PLT;AGG;DEV;SIG;LNK;NEWNAME;DEFAULT
I;;ST-Sdm;North;CB_2;;;;DV_CB

The result looks as follows:

TOOLBOX II Users Manual D30-500-1.05 3-123

 OPM II

As the default input lies at the same level, i.e. "DEV", as the "CB_2" image, a typed image with the
name "CB_2" has been created below the "North" feeder. This circuit breaker has the same structure as
the default input.

Leave out levels

In order to create a typed image "CB_3" from the default input "DV_CB" directly below the image "ST-
Sdm", i.e. the "AGG" level is left out, the following file must be imported:

FUNC;RANGE;PLT;AGG;DEV;SIG;LNK;NEWNAME;DEFAULT
I;;ST-Sdm;;CB_3;;;;DV_CB

The result looks as follows:

3-124 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.11.6.4.2. Create a Typed Image with Default Input and Update Values

This function allows the creation of typed images with simultaneous value updating. The function
"Create a typed image and update values" works by creating a new typed image (possibly with all its
typeless parents) in the first step, and then the corresponding values are accepted.

What should be noted for these steps has already been described.

TOOLBOX II Users Manual D30-500-1.05 3-125

 OPM II

3.11.6.5. Delete images

The "Delete an image" function permits the deletion of any root image or subimage of the OPM. For this
it does not matter whether the root image or subimage is a typed or a typeless image.

By means of this function, the following image types can be deleted.

N Typeless root image

N Typeless subimage

N Typed root image

N Typed subimage (for which the overlying image can be typeless)

Example: Deletion of an image

In order to delete the typed image "ST-Sdm.North.CB_2.CMD0001" and the typeless image "East.CB",
we import the following COF file:

FUNC;RANGE;PLT;AGG;DEV;SIG;LNK;NEWNAME;DEFAULT
D;;ST-Sdm;North;CB_2;CMD0001;;;
D;;;East;CB;;;;

The result in the OPM then looks as follows:

As can be seen, by the deletion of "ST-Sdm.North.CB_2.CMD0001", the image "ST-Sdm.North.CB_2"

has become typeless. The image "East.CB" has likewise been deleted.

Comment:
Depending on the settings in the OPM on whether it is permitted to make an image at a level typeless,
there is - or is not - an error message!

3-126 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.11.6.6. Rename images

3.11.6.6.1. Rename an Image

The function "Rename an image" allows the renaming of any root image or subimage of the OPM. For
this, it does not matter whether the image which is to be renamed is typeless or typed.

Example: Rename an image

The renaming of the circuit breaker "CB" to "Circuit breaker" is done as follows:

FUNC;RANGE;PLT;AGG;DEV;SIG;LNK;NEWNAME;DEFAULT
U;;ST-Sdm;North;CB;;;Circuit breaker;

Result:

3.11.6.6.2. Rename an Image and Update Values

The function "Rename an image and accept values" allows the renaming of any root image or subimage
of the OPM. For this, it does not matter whether the image which is to be renamed is typeless or typed.
The restrictions are those already mentioned above.

When using this function, note the following:

N Only the values of those attributes can be changed which lie directly below the image whose
name has been changed.

TOOLBOX II Users Manual D30-500-1.05 3-127

 OPM II

3.11.6.7. Create info types

The function "Create an Infotype" allows the creation of an infotype below a typeless image (root image
or subimage).

When using this function, note the following:

N The infotype must exist (it must be defined in the OPM)

N The image to which the infotype is appended must be typeless

N Parameter types cannot be appended

Example: Create an infotype and accept values

In order to create an infotype "TXT" below the typeless images "ST-Sdm.North", "ST-Sdm.West" and
"ST-Sdm" and which already exists in the OPM, the following file must be imported:

FUNC;RANGE;PLT;AGG;DEV;SIG;LNK;NEWNAME;DEFAULT;TXT
I;;ST-Sdm;North;;;;;;"North"
I;;ST-Sdm;West;;;;;;"West"
I;;ST-Sdm;;;;;;"ST"

The result looks as follows:

Infotypes were appended below three typeless images and also the values "North", "West" and "ST"
were accepted for these newly created infotypes, i.e. after the import process these attributes now have
the following values:

PEA TXT

0 ST-Sdm ST

1 ST-Sdm.North North

2 ST-Sdm.West West

3-128 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

TOOLBOX II Users Manual D30-500-1.05 3-129

 OPM II

3.12. Source data management up to V3.10

3.12.1. Overview

The Source Data Management is the interface between the OPM and external programs. This interface
makes swapping out and in of data into the OPM possible

Swapping out of data

N The selection of the data set for swapping out is to be defined just like in Mass Editing. (see:
Compiling of data in Mass Editing)

N The table structure for swapping out can be saved. (for example, if frequently used "data sets" for
other suppliers are defined)

N In the swapping-out process of data, several distinctions are made (swapping out of all lines for
changing of values and swapping out of only those lines that contain changes, or swapping out of
all lines for transfer to another OPM, as the case may be)

Once the swapping-out process is finished, a COF (Common OPM Format) file will have been created

Swapping in of data

N It is attempted to swap in all data from the COF file. The transfer of the data will be carried out
only if the swap-in has been completed properly.

N A detailed error report is output

N Depending on the change identifier in the COF file (FUNC column), there are several options
what should happen with the data during the swap-in process (the values of the image are
applied, new standardized images are created, new standardized images are created and the
values of these images are applied, images are deleted).

3-130 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.12.2. Import

Deleting of subimages still missing

Through source data management swap-in it is possible to unconditionally overwrite reference

destinations and formulas, as the case may be.

This function is needed, if values are changed in the external file that are formulas or reference
destinations in the OPM.

If the function "swap in values of the formula/reference destinations" has been selected, then the
formulas or references will be canceled and the value from the COF file will be applied

TOOLBOX II Users Manual D30-500-1.05 3-131

 OPM II

3.12.3. COF format

The COF format (Common OPM Format) is the description of the data format for the swapping-in and
swapping-out in the OPM by means of the Source Data Management. The various fields are saved in
the ASCII format and separated by a freely selectable separation character (default ";"). The first line
contains the column headings.

The system distinguishes between columns that must always be contained in the COF file (fixed
columns) and the free columns

Fixed columns

N FUNC column

The FUNC column specifies what is to happen with an image. This column must always have a
value
C... Create New Image
I... If an image does not exist yet, a new image will be created, and the values from the COF file
are transferred to the OPM. If an image already exists, only the values from the COF file are
transferred
D... Delete Image
U... Transfer values from the COF file to the OPM
U... Rename image
REM... Is an additional comment, and the following data are not transferred but only displayed

N PEATL column
If a new typeless image is to be created, the PEATL (= Process Engineering Address Typeless)
column contains the VTA of the new image to be created. Acceptable only in connection with
FUNC= I or FUNC= C. This field is optional.

N PEA column
The PEA column contains the standardized part of the VTA during the creation of a new image,
or the VTA of an existing image during the transfer of values. This column must always have a
value. This column is handled as unambiguous key for data coupling.

N PEANEW column
If an image is to be renamed, this column contains the new VTA of the image (FUNC= U). This
column need not have a value

N DV column
If a new image is to be created, the DV column (= default) contains the name of the default based
on which the image is created (for this purpose, the default must have been created beforehand
by the user in the OPM). To be defined in connection with FUNC= C and FUNC= I.

Free columns

N The contents of the first line of a COF file with regard to the designations of the free columns are
names of parameter Types or infotypes, as the case may be. In this connection, all these names
must be in agreement with the relevant definitions in the OPM. This means that there must
always be a parameter or infotype in the OPM for each free column of the COF file

3-132 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.13. References

3.13.1. Overview

References represent one of the most important concepts in the OPM, for preventing multiple inputs
(redundancy-free input). With a reference,a 1 : 1 relationship between a source and several destinations
can be established.

One differentiates between 2 Types of references:

N Value reference

The value reference isused to reference values that are the same. That means, that identical values of
parameters now only need to be input once.

N VTA Reference

The VTA reference is used for calculating the VTA (process-technology text address). For this
reference, the tree structure of the images is used as a basis for the VTA.

Important information

N Sourcesand destinations of references

Sources of references are displayed RED, destinations are displayed GREEN.
Always only one source and several destinations can be defined. The chaining of reference
(destination is again source) is not possible, however it is possible to define one source and
several destinations
To determine which parameter is source and which parameter is destination of a reference, one
must switch:
to the Reference and Formula mode
The parameters (either source or destination) marked and
M-Click-R | Reference-Source or Reference-Destination displayed
In a dialogue window the associated VTAs for the corresponding images and parameters appear.
After resolving a reference, the last calculated value remains in the parameter.

N The resolution of references in Normal mode

To be able to resolve references:
the value of a destination must be edited
Afterwards comes a query whether the reference is really to be resolved.
confirm with OK
and the reference is resolved.
After resolving a reference, the last calculated value remains in the parameter.

N The resolution of references in Reference mode

To be able to resolve references one must:
switch to Reference and Formula mode.
Select the parameter and
M-Click-R | resolve Reference-Source or Reference-destination
and the reference is resolved.
After resolving a reference, the last calculated value remains in the parameter.

TOOLBOX II Users Manual D30-500-1.05 3-133

 OPM II

N References and Default-specifications

References can also be created in the Default-specifications and then duplicated with DV-
transfer.

3-134 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.13.2. Handling

Creating a value reference

TOOLS | IMAGES

(if not yet open)

VIEW | REFERENCE- AND FORMULA MODE

Note: The mouse-cursor changes

PULL A REFERENCE WITH DRAG AND DROP FROM ONE PARAMETER (=SOURCE) TO ANOTHER (=DESTINATION)

Creating a VTA-Reference

TOOLS | IMAGES

(if not yet open)

VIEW | REFERENCE- AND FORMULA MODE

Note: The mouse-cursor changes

TOOLBOX II Users Manual D30-500-1.05 3-135

 OPM II

PULL A REFERENCE WITH DRAG AND DROP FROM ONE SIGNAL TO THE TEXT ADDRESS FIELD (LK_TTA FOR
SAT230, LK_TA FOR SAT250)

With this Drag and Drop, the tree-structure is then written in the text address field from the signal
upwards. If an image name now changes, then the text address is also changed.

3-136 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.13.3. Hide reference targets

It is possible with the menu item

VIEW | DISPLAY DESTINATIONS OF REFERENCES AND FORMULAE

Parameters of destinations of references are to be masked out

Advantage: All parameters that are to be automatically filled with referencesare masked out and the
entire view of the paramters is simplified.

If the source of a reference ischanged, then the "masked-out" destinationis naturally updated
regardless.

Important note:

In the mass-editing, the values of the parameters marked as "masked-out" are displayed with --. Can be
seen in the following Screenshot for the parameter Rema_Name

The destinations of the references can naturally be displayed at any time again with the same menu
item

VIEW | DISPLAY DESTINATIONS OF REFERENCE AND FORMULAE

Note: If this option is changed while the mass-editing is activated, then the changed setting is only valid
after a renewed start of the mass-editing.

TOOLBOX II Users Manual D30-500-1.05 3-137

 OPM II

3.14. System technique

3.14.1. Overview

In OPM II it is possible to parameterise both the parameters of the destination systems SAT 1703/Ax-
Mode, SAT 1703/ACP-Mode as well as the parameters of the destination system SAT 1703/Sk-Mode.
This means, that all parameterising tasks can be carried out in the OPM, without having to change the
tool. The display of the destinationsystem takes place in an Explorer representation

In the left of the Explorer-window of the system-technical overview the display takes place in tree-form(=
Tree-part of the Explorer-window). On the right of the Explorer-window, depending on choice, the
display takes the form of either

N a list of entries (Regions, Automation units, System elements, Parameters). This list always
represents the contents of the selected tree-entries at the left.

N alist of parameters. Thereby the change to values can be carried out directly in this list. The
parameterising can take place by selection texts, the input of Float values, Integer values or texts.
A check of the valid values is always carried out.

N a Spreadsheet ( e.g.: detailed routing, topology). Thereby, dependingon parameters, on the one
hand values can be edited directly, or parameterising carried out with selection texts.

N a PD-Form is displayed. The system elements of the destinationsystem SAT 1703/Sk-Mode are
displayed exclusively in PD-Forms.

3-138 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.14.2. 1703 ACP - mode

For 1703 ACP all system parameterising for basic system elements (BSE) and protocol elements (PRE)
is carried out in the system technique of the OPM II. The parameters are summarised to function groups
in the tree. The parameterising takes place with selection texts or by entering values. In the
Spreadsheet processing, selection texts are also possible.

The process-technical parameters of protocol elements (Protocol detailed routing) and all periphery
elements of 1703 ACP are parameterised in the images.

TOOLBOX II Users Manual D30-500-1.05 3-139

 OPM II

3.14.3. BC 1703 ACP image parametrization

3.14.3.1. Overview

The display parameterizing for the protection device BC 1703 ACP fulfills the following tasks:

N Creation of graphic feeder switch-diagrams (single-line switch-diagrams)

N Assignment of signals (commands, binary information, measured values etc.) to the individual
display elements (Symbols, LEDs, Measured values, Keyswitches, Function keys) of the
protection device

A display is created with the display parameterization of the OPM II, loaded into the destination system
and eventually displayed on the display module of the combination protection device.

3.14.3.1.1. Display and Display Elements

The panel of the protection device BC 1703 ACP consists of the following elements:

N Display (graphic display portrait format 128 x 240 points)

N LEDs

N Keyswitches

N Function keys

The number of LEDs, function keys and keyswitches on the panel is fixed defined and cannot be
parameterized.

The display visualizes a single-line switch diagram for the display of process-control information. The
single-line switch diagram can consist of several pages, these are switched over using the cursor keys
on the device.

3-140 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

The display of the protection device BC 1703 ACP is composed from the combination of individual
display elements. Thereby the following groups of display elements can be distinguished:

Static display elements:

N Display element LED

N Display element Keyswitch

N Display element Function Key

TOOLBOX II Users Manual D30-500-1.05 3-141

 OPM II

N The static display elements are assigned the corresponding elements of the panel of the
protection device BC 1703 ACP (LEDs, keyswitches, function keys). The number and position of
these display elements is predefined by the panel.

Dynamic display elements

N Display element Text

N Display element Measured Value

N Display element Operational-equipment Symbol

The dynamic display elements are provided for the representation of the single-line switch diagram on
the display of the combination protection device BC 1703 ACP.

The single-line switch diagram of the display can be split up into several pages. Each page can be
assigned an optional page background. The page background is used for facilitating the positioning of
the equipment symbols.

In addition, each display has a particular font for the representation of the texts contained. This font is
defined by the assignment of the Font.

All display elements are positioned on the display by means of Drag&Drop from the Tool Display-
Overview or by means of the context menu (see Creating and editing a display)

The following picture shows the Drag&Drop action of an equipment symbol onto a page-background
image, next to it already configured pages of a display are represented.

3-142 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.14.3.2. Handling

The display parameterizing is part of the tool System Technique.

3.14.3.2.1. Starting the display parameterizing

In the tool System Technique of the OPM II, the regions, AUs and system elements of the system-
technique plant to which the selected VAN belongs are represented in a tree structure.

For each automation unit of the type BC 1703 ACP there exists an entry "Display parameterizing" in the
tree structure of the system technique of the process-control basis system element.

If the user marks the entry "Display parameterizing", the image of the protection device BC 1703 ACP
appears in the editing window of the system technique.

3.14.3.2.2. Terminating the display parameterizing

For terminating the display parameterizing, no explicit command by the user is required. It is terminated
when the user marks another entry in the tree of the system technique or closes the system-technique
parameterizing.

3.14.3.2.3. Display parameterizing

The display parameterizing is described in detail in the chapters Creating and editing a display or
Assignment to display elements respectively.

TOOLBOX II Users Manual D30-500-1.05 3-143

 OPM II

3.14.3.3. Creating and Editing a Display

In order that a display can be successfully created and parameterized, first all display elements
necessary for this must be transferred into the tool Display-Overview.

The transfer of the display elements is carried out from the Tool Templates-Overview. In the tab
Displays all possible picture- and bitmap-templates for the various display elements are available
according to category (displays, equipment symbols, page-background images, measured value
graphics).

The individual display elements are thereby dragged from the library-overview as standard bitmaps into
the display overview by means of Drag&Drop. The assignment is always carried out for the
corresponding display-element category to the associated structure folder "Standard".

Already predefined image-templates of the library-overview that already contain all display elements are
filed as standard displays in the display-overview in the structure folder Displays

In addition, user-bitmaps can be freely defined by the user and stored in the Display-Overview in the
respective display-element category of the structure folder User. (see Tool Display-Overview)

3-144 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

After all display elements have been transferred into the Display-Overview, the display can be created.
The creation and editing of the display is carried out by means of the context menu Display.
Alternatively, many operator inputs can be executed by means of Drag&Drop in combination with the
Tool Display-Overview.

The context menu for creating and editing is described in detail below:

Context menu picture

PICTURE | NEW | EMPTY PICTURE

With this command, the display of a combination protection device is replaced by an empty display and
thereby deleted.

PICTURE | NEW | STANDARD PICTURE...

With this command, the user assigns the AU a standard display, which is selected by its name.

The use can also drag the Standard-Display from the Display-Overview into the display by means of
Drag&Drop.

PICTURE | FONT...

This command is used to select a font for the display currently being edited. A display can only have
one single font at any given time. That means, that all texts of a display are displayed in the same font.

TOOLBOX II Users Manual D30-500-1.05 3-145

 OPM II

When selecting a font, the user can determine whether only standard fonts, only user fonts or all fonts
are offered for selection. As long as no font has been selected for a display, a standard font is used that
is always available in the TOOLBOX II.

The user can also drag the font from the Display-Overview into the display by means of Drag&Drop.

PICTURE | ASSIGNMENTS | OVERVIEW

In the following overview-dialogue all assignments are represented.

3-146 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

PICTURE | ASSIGNMENTS | REMOVE ALL

This command cancels the assignments of all display elements of the display.

Context menu Page

PAGE | PASTE...

With this command the user inserts new pages into the display and can enter the number of pages to be
inserted. Thereby it can be selected, whether the pages are to be inserted before or after the current
page.

PAGE | GOTO...

This command permits the user to switch the current page. The paging using PgUp and PgDn by
means of keyboard input is also possible.

PAGE | DELETE

With this command the user can delete the current page after a security inquiry.

PAGE | BACKGROUND...

This command is used for selecting a background for the page currently being edited. A page can only
have one single background at any given time.

TOOLBOX II Users Manual D30-500-1.05 3-147

 OPM II

When selecting a background image the user can determine whether only standard background-
images, only user background-images or all background-images are offered for selection.

The user can also drag the background from the Display-Overview into the display by means of
Drag&Drop.

Context menu Picture element

PICTURE ELEMENT | INSERT | SYMBOL

With this command the user inserts a new symbol into the picture of the display currently being edited,
which is moved to the desired position by means of Drag&Drop.

In order to change attributes of the symbol (such as e.g. the bitmap used) the user must open the the
Properties-Dialogue for that symbol.(see Display Element -> Properties or Display Element Operational-
Equipment Symbol)

The user can also drag the symbol from the Display-Overview into the display by means of Drag&Drop.

PICTURE ELEMENT | INSERT | TEXT

With this command the user inserts a new text into the display currently being edited. After selecting the
command, a new text from the display parameterizing is placed in the display and can be moved to the
desired position by the user by means of Drag&Drop.

To change attributes of the text (such as e.g. the actual text), the user must open the Properties-
Dialogue. (see Display Element -> Properties... or Display Element Text)

PICTURE ELEMENT | INSERT | MEASURED VALUE

3-148 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

With this command the user inserts a new measured value into the display currently being edited. After
selecting the command, a new measured value from the display parameterizing is placed in the display
and can be moved to the desired position by the user by means of Drag&Drop.

The measured value is determined at runtime by the destination system and displayed on the display-
module in the display.

The measured value can be represented either as numerical value or as bar diagram.

To change attributes of the measured value (such as e.g. the required representation), the user must
open the Properties-Dialogue for that measured value.

A display element is selected with a single mouse-click and is thereby graphically highlighted. Only one
single display element can be selected at any given time. The following menu items are available for the
selected display element.

PICTURE ELEMENT | REMOVE ASSIGNMENT

This command cancels the assignment of the assigned links to the display element.

PICTURE ELEMENT | DELETE

The selected display element is removed from the display. The command is only available if a display
element is selected.

PICTURE ELEMENT | PROPERTIES...

With this command the user can view the properties of a display element and if necessary change them.
The command is only available if a display element is selected. The available properties are dependent
on the type of display element. (see detailed description of the display elements)

TOOLBOX II Users Manual D30-500-1.05 3-149

 OPM II

3.14.3.4. Assignment to Display Elements

This chapter describes how the user assigns Links to display elements.

Assignment can take place with either a SAT 1703-Link or a CAEx plus/ACP-Link.

The assignment to a display element generally takes place by means of precisely one Link. In the case
of a symbol, it can also be several (see below). Thereby only spontaneous datapoints can be used
(periodically transmitted datapoints cannot be used).

Various Links are used depending on the required assignment:

Assignment of Required Link with the following OPM-destination

systems

Display element <-> SAT 1703 optional ACP 1703- and Ax 1703(IEC)-Link

Display element <-> CAEx plus CAEx plus/ACP-Link (spontaneous)

The assignment of a display element by means of another Link (SAT 230, SAT 250, external computer)
is not possible. If necessary, for this a CAEx plus/ACP-Link can be used.

The user can cancel the assignment of a display element using the options of the context menu

PICTURE ELEMENT | REMOVE ASSIGNMENTS.

Assigning display element <-> SAT 1703

To define the assignment the user must carry out two operations. Both steps are described in the
following and can be carried out in any order.

N Assigning the Link to the display element

The user assigns the required Link to the display element. For this he drags a 1703-Link from the OPM-
tool images or from the mass editing into the feeder diagram and lets it drop onto the display element.

N Assigning the signal to SAT 1703 (see Assigning)

Assigning the display element <->CAEx plus

In order to assign, the user drags a CAEx plus/ACP-Link of the signal concerned from the OPM-tool
images or from the bulk editing into the feeder diagram and lets it drop on the corresponding display
element. When assigning a CAEx plus/ACP-Link to a display element, any spontaneous CAEx
plus/ACP-Link can be used. The following categories are available.

N IEC-Commands

N IEC Measured value with change thresholds

N IEC-Standard

3-150 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

Peculiarities when assigning to a Symbol

A symbol differs from other display elements in that it has more than one datapoint. This characteristic
is defined by the symbol-type of the display element.

The user therefore does not assign a symbol to one single link, but rather to as many links as the
symbol has datapoints.

Examples:

The display element LED has the permanently assigned type identification single-point information.
Consequently only a SAT1703-Link or CAEx plus/ACP-Link of a single-point information can be
assigned to an LED of the panel.

The display element equipment symbol circuit-breaker has for example the symbol-type "Double-point
information with switching operation running and double command". Consequently, in the display
SAT1703-Links or CAEx plus/ACP-Links for a double-point information, a single-point information and a
double command can be assigned to this circuit-breaker.

All assignments are displayed by means of the context menu

PICTURE | ASSIGNMENTS | OVERVIEW

TOOLBOX II Users Manual D30-500-1.05 3-151

 OPM II

3.14.3.5. Tool Display overview

This section describes the call, the function and the method of operation with the tool Display-Overview.

Call

The Display-Overview is called with the menu

TOOLS | DISPLAY OVERVIEW

or by means of the Smart-Icon .

Call function and method of operation

With the tool Display-Overview, all display elements required for the current display parameterizing can
be managed.

3-152 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

The display elements are divided in the tree structure of the Display-Overview into the following
categories.

N Displays

N Equipment symbols

N Page background

N Fonts

N Measured values

N In addition, the individual categories are subdivided into standard- and user-bitmaps according to
the structure folders "Standard" and "User" (see Managing standard- and user-bitmaps)

All display elements of the tool Display-Overview can be placed on the current picture of the display or
on various pages of the display by means of Drag&Drop or the context menu (see Creating and editing
a display).

The tool Display-Overview contains all standard displays on startup, Standard-Bitmaps and User-
Bitmaps of the currently preset system-technique plant.

Managing Standard- und User-Bitmaps

Already predefined bitmap- or picture-templates of display elements are transferred as standard-

bitmaps or pictures to the respective display-element category (structure folder Standard) from the Tool
Templates-Overview from the tab Displays by means of Drag&Drop.

Bitmaps, that the user can define himself, are designated as user-bitmaps to distinguish then from
standard bitmaps and managed in the structure folder "User" of the respective display-element
category.

Below the individual commands are explained, with which the user can manage the standard- or user-
bitmaps. The commands are called with the context menu of the entries in the Standard or User area in
the Display-Overview.

IMPORT BITMAP

This menu item is only available for User-Bitmaps. the following data must be specified depending on
display-element type or are displayed for information.

N Name

The name of the bitmap-file to be imported

N Bitmap-Type

The Bitmap-Type is determined by whether the user selects the context menu for a page-background
image, a symbol, a font or a measured value graphic.

N Symbol-Type

This field is only to be filled out if the user has selected "Symbol" as bitmap-type. The Symbol-Type
determines to which datapoints the symbol is allocated.

N Position Bars

TOOLBOX II Users Manual D30-500-1.05 3-153

 OPM II

At runtime the currently measured value is output in the form of a bar at this position (Pixel) in the
measured-value graphic.

N Size bars

At runtime the currently measured value is output in the form of a bar in the measured-value graphic
with this size (Pixel).

Only user-bitmaps can be imported.

Example: Importing an equipment symbol defined by the user

EXPORT BITMAP

With this command, any bitmap can be exported as a Windows-Bitmap file. Both User-Bitmaps as well
as Standard-Bitmaps can be exported.

DELETE BITMAP

The Bitmap is deleted. Both User-Bitmaps as well as Standard-Bitmaps can be deleted.

3-154 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.14.3.6. Tool Templates overview

This section describes the call, the function and the method of operation with the Tool Library-Overview.

Call

The templates overview is called by means of the menu

TOOLS | TEMPLATE OVERVIEW

or using the Smart-Icon . The library elements for the display parameterizing are available in the tab
Displays.

Call function and method of operation

The tool

TEMPLATES OVERVIEW | PICTURES

makes available the picture- and bitmap-templates for display elements provided by VA TECH SAT for
the display parameterizing.

TOOLBOX II Users Manual D30-500-1.05 3-155

 OPM II

The Templates-Overview is divided into the following categories.

N Displays

N Equipment Symbols

N Page-Background Images

N Fonts

N Measured-value graphics

N With Drag&Drop, picture- or bitmap-templates can be dragged into the Tool Display-Overview.
The templates can only be transferred as standard-bitmaps for the respective display-element
categories (see Creating and editing a display).

3-156 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.14.3.7. Font

The font of a display is represented by a file in the Windows Monochrome Bitmap Format.

Individual fonts are either provided by VA TECH SAT in the tool Templates-Overview-Displays as
Bitmap-templates or can be created by the user with a simple picture-editing program (e.g. MS Paint).

Precisely one font can be selected for each display. All texts contained in a display use this single font.

The assignment of the font is carried out either by means of Drag&Drop from the Tool Display-Overview
direct to the display or by means of the dialogue "Select font" of the PopUp menu

PICTURE | FONT

3.14.3.7.1. Structure of a Font-Bitmap

A font is divided into 256 segments in the form of a matrix with16 rows and 16 columns (numbered from
0 to 15). Each element of the matrix represents a special character of the font in the ASCII character
code.

Example

The letter A with the ASCII-Code 65 is located in row 4 and column 1 ( 65 = 4* 16 + 1). The following
illustrations show the bitmap of a font and a single character respectively.

TOOLBOX II Users Manual D30-500-1.05 3-157

 OPM II

The illustrated font with a maximum pixel area of 7x10 Pixels per character is represented by a bitmap
of 112x160 Pixels. In the character area, for each character at least one pixel row or -column should be
reserved at the right and lower edge as character- or line spacing, which results in a maximum
character size of 6x9 Pixels. Depending on the character size, this results in a variable bitmap size of
the font.

3-158 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.14.3.8. Display Element Text

A display element of the type Text is created with the PopUp menu

PICTURE ELEMENT | PASTE | TEXT

The properties of the selected display element can be changed with the PopUp menu

PICTURE ELEMENT | PROPERTIES

or by a double-click on the display element with the following dialogue.

Text

This attribute contains the actual text that is displayed in the display.

N The number of characters of the text displayed in the display results directly from the text entered.
The user cannot enter any minimum or maximum number of characters to be displayed, instead it
is fixed that all characters are represented. Only when a text is curtailed by the right display edge
are not all characters visible.

N The size of the text field cannot be changed with the mouse.

N The text output always takes place on one line.

Position

By specifying the right and upper coordinates (X,Y) the position of the text in the display can be
changed.

TOOLBOX II Users Manual D30-500-1.05 3-159

 OPM II

3.14.3.9. Display Element Measured Value

The display element Measured Value is represented by a file in the Windows Monochrome Bitmap
Format.

Measured values are available as bitmap-templates from VA TECH SAT in the Tool Templates-
Overview | Pictures or can be created by the user with a simple picture-editing program (e.g. MS Paint).

The assignment of the measured value directly to the display is carried out either by means of
Drag&Drop from the Tool Display-Overview or using the PopUp menu

PICTURE ELEMENT | PASTE | MEASURE VALUE

with the PopUp menu of the selected display element

PICTURE ELEMENT | PROPERTIES

or by a double-click on the display element Measured Value, the properties of the display element
Measured Value can be changed with the following dialogue.

Link

In the value field Link the process technical address of the assigned link is displayed for the respective
type identification TI. The user cannot edit this attribute directly, but rather assigns the link to the display
element by means of Drag&Drop from the image window.

3-160 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

Position

The position of the measured value in the display is independent of whether the measured value is
displayed as text or bar.

Display

A measured value supports the following display modes:

N Text

A measured value in numerical representation is defined by a placeholder text. The placeholder text can
on the one hand contain normal text characters (e.g. unit, value designation) and in addition a special
placeholder text, which is substituted by the numerical value (#####.###) or by a symbol character for
the data point identifier ($).

N Bar diagram

The measured value is displayed graphically in the form of a bar. For the selected name, the
measured-value graphic is displayed in the preview area. There are 4 different measured-value states

Representation of value

N For the value representation, optionally the values primary, secondary or percentage can be
selected in the display mode Text:

Format

The input field Format describes that format definition, that specifies how the measured value is to be
represented.

N ####.### Placeholder for decimal display

Each # character is substituted by a numeral, the point symbolizes the decimal place (can also be left
out). Additional zeros before the decimal point are substituted by spaces. If the number cannot be
displayed at the predefined place, then all numerals are substituted by a * symbol.

For negative figures it must be taken into account, that an additional place is required before the
decimal point for the polarity sign

N $ Placeholder for data point identifier

The $-symbol is substituted by a character for the data point identifier.

Character Function

Space Measured value is valid

Inverted question mark The measured value is marked with I-Bit or Not Topical

Inverted exclamation mark The measured value is marked with Overflow,

Substituted or Blocked

TOOLBOX II Users Manual D30-500-1.05 3-161

 OPM II

Example:

The specification of the measured value with the following format I1 = ###.## $ A can deliver the
following result:

I1 = 100.00 ! A (Amps)

3.14.3.10. Construction of Measured-Value Bitmaps

Measured-value graphics have the following structure and can be transferred to the tool Display-
Overview as user-definition using the dialogue of the PopUp menu

IMPORT BITMAP

N X-/Y-Position bar in pixels

At runtime, the currently measured value is output in the form of a bar at the X-/Y-position in the
measured-value graphic.

N Size bar (width and height in pixels)

At runtime, the currently measured value is output in the form of a bar in the measured-value graphic
with this size.

The user must draw a bitmap consisting of 4 part-graphics (1 column, 4 rows).

Bitmap Row State

1 Normal-state

2 The measured value is > 100%

3 The measured value is marked with

I-Bit or Not Topical

4 The measured value is marked with

Overflow, Substituted or Blocked

3-162 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

TOOLBOX II Users Manual D30-500-1.05 3-163

 OPM II

3.14.3.11. Display Element Symbol

The operational-equipment symbol (e.g. circuit-breaker, disconnector, withdrawable type circuit-breaker)

is represented by a file in the Windows Monochrome Bitmap Format.

Symbols are either provided as bitmap-templates by VA TECH SAT in the Tool Templates-Overview |
Pictures or can be created by the user with a simple picture-editing program (e.g. MS Paint).

The assignment of the display element is carried out either by means of Drag&Drop from the Tool
Display-Overview directly onto the display or by using the PopUp menu

PICTURE ELEMENT | PASTE | SYMBOL

with the PopUp menu of the selected display element

PICTURE ELEMENT | PROPERTIES

or by means of a double-click on the display element Measured Value, the properties of the display
element symbol can be changed with the following dialogue

Position

By specifying the right- and upper coordinates (X,Y) the position of the text in the display can be
changed

3-164 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

Symbol type

The symbol type establishes with which data points a given operational-equipment works. The following
symbol types are available and are already assigned standard operational-equipment or can be defined
by the user for User-Operational-Equipment symbols.

N Single-point information without command

N Double-point information without command

N Single-point information with single command

N Double-point information with double command

N Double-point information with double command and single-point information "Switching operation
running"

N Single command

N Measured value normalized

N Measured value scaled

N Measured value floating point

Links

In the value field Link the process technical address of the assigned link is displayed for the respective
type identification TI. The user cannot edit this attribute directly, but rather assigns the link to the display
element by means of Drag&Drop from the image window.

3.14.3.11.1. Construction and Display of Operational-Equipment Symbol-Bitmaps

For each symbol, optionally only one single- or double command is permitted. The user must draw a
bitmap consisting of
n
2 columns, and 2 rows.

n = the sum of the values for one single-point information (1) and one double-point information (2).
(Only data points in the signaling direction are assessed)

TOOLBOX II Users Manual D30-500-1.05 3-165

 OPM II

If the signals are marked with the I-Bit, then the symbol-graphic from the second row is selected and
displayed, otherwise the symbol-graphic from the first row.

Example

Operational-equipment circuit-breaker: Double-point information with "Switching operation running" and

double command

n = 3 (Double-point information = 2 + Switching operation running = single-point information = 1)

3*
2 2 (rows) = 16 Symbol-Graphics (see below)

I-Bit DIFF OFF ON FAULT DIFF OFF ON FAULT

SOR = 0 SOR = 1

SOR .. Switching operation running

Remark:

If the symbol is not assigned any binary information, the the bitmap consists of one symbol-graphic
(single command without status information).

3-166 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.14.3.12. Display Element LED

The LEDs with the numbers 11 – 19 can be assigned any single-point informations by means of the
display element LED. The color of the LEDs is optional (red, yellow, green).

The displays can take place static or transient handled (alarm-signaling sequence). In the position
REMOTE of the Keyswitch the display always takes place static.

Incoming binary information are displayed flashing rapidly, after acknowledgement displayed
continuously lit. Outgoing binary information are only then displayed flashing slowly, if the incoming
binary information has not yet been acknowledged, otherwise the LED is displayed dark.

With the PopUp menu of the selected display element

PICTURE ELEMENT | PROPERTIES

or with a double-click on the display element LED, the properties of the display element can be
changed with the following dialogue.

Link

In the value field Link, the process technical address of the assigned link is represented for the
respective type identification TI. The user cannot edit this attribute directly, but rather assigns the link to
the display element by means of Drag&Drop from the image window.

TOOLBOX II Users Manual D30-500-1.05 3-167

 OPM II

3.14.3.13. Display Element Keyswitch

Keyswitch 1 has the positions „Locked“ and „Not locked“, the state is transmitted as single-point
information and can be assigned in the TOOLBOX II.

Binary information state switch position (0 locked1 not locked)

Keyswitch 2 has three positions, „Local“, „Remote“ and „Test“. The state is transmitted via a double-
point information. Switching operations can only be carried out if the switch is in the position „Local“.

Binary information state switch position (00 Test, 01 Local, 10 Remote, 11 not used)

With the PopUp menu of the selected display element

PICTURE ELEMENT | PROPERTIES

or with a double-click on the display element the properties can be displayed with the following
dialogue.

Link

In the value field Link, the process technical address of the assigned link is represented for the
respective type identification TI. The user cannot edit this attribute directly, but rather assigns the link to
the display element by means of Drag&Drop from the image window.

3-168 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.14.3.14. Display Element Function Key

Both function keys F1, F2 can be assigned individual commands.

With the PopUp menu of the selected display element

PICTURE ELEMENT | PROPERTIES

or by means of a double-click on the display element the properties can be displayed with the following
dialogue.

Link

In the value field Link the process technical address of the assigned link is represented for the
respective type identification TI. The user cannot edit this attribute directly, but rather assigns the link to
the display element by means of Drag&Drop from the image window.

TOOLBOX II Users Manual D30-500-1.05 3-169

 OPM II

3.14.4. BC 1703 ACP matrix

3.14.4.1. Overview

The SAT protection device BC 1703 ACP consists of 2 Basis System Elements

Process-Control-BSE

N The process-control BSE is the "Center" of the combination protection device and fully supports
CAEx plus functionality. The user can therefore create optional function diagrams and load these
into the process-control BSE.

Protection-BSE

N The protection BSE controls all functionalities for "directional and non-directional protection" and
has no CAEx plus capability.

Despite this logic functions for fast logic operations and interlocks are required. The data input for these
interlock- and logic function operations is carried out therefore not by means of function diagrams, but
by means of the so-called "Matrix".

3.14.4.1.1. The Matrix

With the matrix, the user defines a concrete interlocking- and logic function logic. Thereby the following
entries can be carried out in the matrix by the user.

N Setting, Inverting and Deleting of node points, in order to connect inputs and outputs by means of
logical links.

The states of the inputs are AND-linked by means of a conjunction (vertical line), The outputs are
OR-linked by means of a disjunction (horizontal line).

N Assignment of inputs to concrete protection signals

3-170 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

Differences from CAEx plus

N While CAEx plus supports the dynamic creation of function diagrams, the input of the logic-
operation logic for the protection-BSE can only be carried out by means of the static matrix.

N No executable code

N Better performance, since the logic- and interlock data on the protection-BSE can be interpreted
directly by the Firmware software

N No online test possible

N No oscilloscope functions

TOOLBOX II Users Manual D30-500-1.05 3-171

 OPM II

3.14.4.2. Handling

The Matrix is part of the tool System Technique.

3.14.4.2.1. Starting the Matrix

In the tool System Technique of the OPM II, the regions, AUs and system elements of the system-
technique plant to which the selected VAN belongs are represented in a tree structure.

The matrix is part of the system-technique parameterizing and is always assigned to a protection-BSE.
Each protection -BSE contains 4 matrices. The respective "Result"-parameters are represented in 4
parameter groups. In the destination system always only one parameter group can be active.

The matrix is displayed by selecting the entry "Protection logic" of one of the 4 parameter groups.

3-172 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.14.4.2.2. Expanding and Compressing the Matrix

After the initial opening of a matrix, by default only the first 16 conjunctions are displayed. In principle,
two expand-modes are available to the user:

N 16 Conjunctions (Group 1)

N 32 Conjunctions (Group 2)

The user can switch optionally between these expand-modes by means of the PopUp menu

TOOLBOX II Users Manual D30-500-1.05 3-173

 OPM II

EXPAND

COMPRESS

of the matrix. If at least one connection point is set on a conjunction (horizontal line) in the expanded
range, then a compressed representation is no longer possible. The last-used display mode is always
displayed on reopening.

Example:

A connection point is set at conjunction 17. From this moment, the second group (conjunction 15 – 31)
can no longer be suppressed.

3.14.4.2.3. Setting, Inverting and Deleting Node Points of the Matrix

Node points of the matrix can be set with a simple mouse-click in the connection intersections of the
matrix (quadratic node point). With renewed clicking the node point is inverted (round node point). The
deletion of a node point is carried out with a further mouse-click.

Toggle-Mode: Setting - Inverting - Deleting

3-174 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

In addition, the deletion of connection points is supported by the context menu of the matrix by means of
the following menu items, through which the user is spared the laborious deletion of a series of
individual nodes.

DELETE CONNECTION-POINT | ALL

DELETE CONNECTION-POINT | NOT INVERTED

DELETE CONNECTION-POINT | INVERTED

3.14.4.2.4. Properties for inputs and outputs

The Properties-Dialogue is displayed automatically on entry into the matrix and can be activated by
means of a double-click on the individual inputs and outputs or by means of the context menu

PROPERTIES

The Properties-Dialogue is pinned by default, i.e. if another input or output is selected, then the
associated properties are automatically displayed and the labeling text of the currently selected input or
output is optically identified.

Example: Properties of inputs

Each input can be assigned a concrete protection signal with the Properties-Dialogue "Input
assignment".

Before each input-line the text of that protection signal is displayed, that is assigned to this input. If an
input has not yet been assigned, then the text "not assigned" is displayed.

TOOLBOX II Users Manual D30-500-1.05 3-175

 OPM II

Example: Properties of outputs

The properties of the output are described by the dynamic behaviors t1 and t2.

N Delay time for positive edge (t1)

N Delay time for negative edge (t2)

The following operating modes are provided:

t1 (sec) t2 (sec)

inactive inactive

delayed delayed

delayed pulse

delayed delayed and can be retriggered

delayed and can be retriggered pulse

Minimum time inactive

3-176 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

In the Properties-Dialogue for the outputs the output equation is displayed in text form. It must be noted
that an output equation can possibly be very long (32 conjunctions for each 32 OR logic operations =
1024 logic operations).

By positioning the mouse cursor on a matrix-output, the output equation can also be displayed by
means of a Tooltip.

The outputs are numbered consecutively, since an output itself is already a protection signal.

3.14.4.2.5. Terminating the Matrix

To terminate the matrix, no explicit command from the user is required. It is terminated when the user
marks another entry in the tree of the system-technique or closes the system-technique parameterizing.

TOOLBOX II Users Manual D30-500-1.05 3-177

 OPM II

3.14.5. 1703 Ax - mode

For AU's in 1703 Ax all system parameterising for basic system elements (BSE) and protocol elements
(PRE) can be carried out in the system technique of the OPM II. Alternatively, for compatibility reasons,
the possibility still exists of carrying out parameterising in tool parameters. Existing data can be
processed without conversion directly in the system technique of theOPM II. Aswitch between OPM II
and the Tool parameterising is also possible at any time. The existing PD Forms and detailed routing
are displayed in the system technique.

The process-technical parameters of protocol elements (Protocol detailed routing) and all periphery
elements with IEC funktionality are still only parameterised in the images of the OPM II. Periphery
elements with system-technical addressing can alternatively also be parameterised in the system-
technique of the OPM II or in tool parameterising.

Special functions for Ax 1703

N Copy / insert mirror parameters

This function is used for copying redundant BSE of an AU or various AUs. Thereby only those
parameters are overwritten, thatare defined as mirror parameters in the master data of the
TOOLBOX II. The Pop-Up menu item is only visible if mirror parameters are defined for this BSE.

N Process User error words

For each system-technical plant, texts of 8 Bits respectively are defined for user error words.
Directly under the node for the system-technical plant, there is a sub-node with the name Process
User error words. If the User selects this node, a table appears in the Spreadsheet-part of the
Explorer-window with which all parameterising can be carried out.

3-178 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.14.6. 1703 SK - mode

For AU's in 1703 SK - Mode, all parameterising can be carried out in the system-technique of the OPM
II. Alternatively, for compatibility reasons, the possibility is still available of carrying out parameterising in
the tool parameterising. Existing files can be edited directly without conversion in the system-technique
of the OPM II. A switch between the OPM II and the tool parameterising is possible at any time. The
existing PD Forms and detailed routing are displayed in the system technique.

Special functions for SK 1703

N WMBA and WMPRO

This function is used for reading out value- and information parameters for a system element of
the Type WMBA or WMPRO from a DPL-file and converting to parameters. The user can call this
function via a dynamic menu item in Pop-Up Menu, that is assigned to the system elements.
Dynamic means in this context, that the menu item only appears in the Pop-Up Menu of a system
element if with the system element, it has to do with the WMBA or the WMPRO. For all other
system elements, the menu item does not appear.

N Transferring detailed routing to SIP

Some SIPs for the destination system SAT 1703 SK-Mode require the parameter block detailed
routing and its communication elements for operation. So that these this parameter block is
transferred to the SIP on startup, in the statusbit word for it, the corresponding bit must be set.
The user can call this function via a dynamic menu item in the Pop-Up Menu, that is assigned to
the system element. Dynamic means in this context, that the menu item only then appears in the
Pop-Up Menu of a system element, if the system element is especially flagged in the master data
of the TOOLBOX II. For all other system elements, the menu item does not appear.

N Topology
For the destination system SAT 1703 SK-Mode, the topology is parameterised in parameter block
M36. The user can call this special PAR-function via a corresponding menu item in the Pop-Up
Menu for the node in the tree of the system-technical parameterising

N Editing DA-DFK
The data Type name and data format identification are defined for each system-technical plant.
Directly under the node for the system-technical plant there is a sub-node with the designation
DA-DFK. If the user selects this node, a table appears in the Spreadsheet-part of the Explorer-
window, with which all parameterising can be carried out.

TOOLBOX II Users Manual D30-500-1.05 3-179

 OPM II

3.14.7. Start of CAEx II

The start is carried out with the menu item

CAEX II

from a PopUp-Menu in the system-technical overview window. The Pop-Up menu is only available if the
AU contains at least one system element with a CAEx II - task and when CAEx II is installed.

N Start of CAEx II
During the start of CAEx II, it is first checked whether the plant path has been preset. If this is not
the case, the user is asked whether he wishes to preset the plant path.

N CAEx II-settings
The following CAEx II settings can be carried out in
Extras | Options | CAEx II :
- Presetting whether data are processed in the plant path or the test path.
- Path input for the test path and Macro-path

3-180 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.14.8. Start of CAEx plus

The start takes place with the menu item

CAEX PLUS

from a PopUp-Menu in the system-technical overview window. The Pop-Up menu is only available if the
AU contains at least one CAEx plus-capable system element and if CAEx plus is installed.

Before the start, it is first checked whether CAEx plus is running. If this is the case, the running CAEx
plus is brought to the foreground. If CAEx plus is not running, CAEx plus is called up.

TOOLBOX II Users Manual D30-500-1.05 3-181

 OPM II

3.14.9. Navigate to an image

In the tree of the system-technique, one can navigate from positionedHW-Pins and SW-Datapoints
directly into the corresponding image.

With the entry

PROCESS IMAGE

in the Pop-Up Menu of the HW-Pins or SW-Datapoints the Process Image window is opened directly
and the corresponding image opened in the tree.

3-182 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.14.10. Visibility of automation units

Hiding and unhiding automation units

View- only default automation functions

in the menu line of the OPM II only those automation units in the Tree-part of Explorer-window are
displayed that were previously defined in a list. This list can be compiled the following way:

EXTRAS - DEFAULT AUTOMATION UNITS

The following functions are available:

N Add

All in the automatision units of the currently preset system-technical plant are offered for
selection. By double-clicking on the line of the corresponding automationunit, or by selecting and
pressing the Button AU's one or more AU's are added to the list.

N Remove

All entries marked are removed from the list.

N Remove all

All entries are removed from the list.

A predefined list can be loaded. For selection thereby, all lists are offered that the currently preset
user has defined.
The list currently loaded is saved under another name. The name of the list can be freely selected
by the user. The list is assigned the currently preset User.

N Load list

A previously defined list can be loaded. For selection thereby, all lists are offered that the
currently preset user has defined.

N Save list

The currently loaded list is saved under another name. The name of the list can be freely selected
by the user. The list is assigned the currently preset User.

N Delete list

Via a selection dialogue, the user can select which list can be deleted. For selection thereby, all
lists are offered that the currently preset user has defined.

Dimming nodes in the Tree-part of the Explorer display

In the following cases, one or more nodes in the Tree of the Explorer display are dimmed:
The AU is exported, but exists as read-only. In this case the parameters of the AU can only be read, but
not processed, i.e. changed in their values.
The AU is exported, but does not exist as read-only. In thiscase it is not possible that further information
of the AU is displayed. The node of the AU does not have any further entries.

TOOLBOX II Users Manual D30-500-1.05 3-183

 OPM II

3.14.11. Detail routing

In the Toolbox II each detailed routing displayed in a spreadsheet can be exported. The import and
Export of individual spreadsheets is started directly via the Pop Up Menu

N Exporting individual detailed routing

The exported file corresponds to CSV Standard (ASCII File, column headings corresponds to the
headings of the detailed routing). In the Export dialogue, one can choose between all detailed
routing records or one range.

N Importing individual detailed routings

The file to be imported must have CSV-Format and the headings must be identifcal with those of
the detailed routing.
During import, one can select between the following options:
- Delete all: All detailed routing records are deleted and the contents of the CSV-File is imported.
- Replace range: A range to be specified is replaced with the content of the CSV-File.
- Do not modify and attach new: All records of the detailed routing remain unchanged and the
content of the CSV-Fileis attached.

During import an error protocol is displayed. The data are only copied in the detailed routing if the entire
import procedure has been successfully carried out.

3-184 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.14.12. Global detail routing export/import

It ispossible to import or Export all detailed routings of one or several AU's in one step. This function is
started via the Pop-Up Menu of the automation unit.

N Exporting detailed routing via control file

For this exporting procedure, an individual CSV-file is created for each detailed routing. All
definitions for this Export procedure are described in a control file.

N Importing detailed routing via control file

As with the Export of detailed routing, with importing, the function is selected in the main window
of the parameterising tool. All definitions for the import procedure are described in the same
control file.

Description of the control file

The control file corresponds to the CSV-Standard, whereby the user can select any separating
character. A line of the control file contains the necessary information for importing the detailed routing
for a BSE of an AU to a file, or exporting respectively. The first line of the control file contains as
headings the names of the individual columns. This control file must be created in an optional text Editor
by the user.

Column Description Necessary for (I)mporting

(E)xporting

File Name of the file incl. path from I,E

which or to which is to be
IMPORTED or EXPORTED. If the
file already exists during Export,
one is asked whether it is to be
replaced. In the Export dialogue,
the user can select the option

overwrite existing files

Reg Region number of the AU I,E

Comp Component number of the AU I,E

BSE Number of the basic system I,E

element

DR-Type Short text of the detailed routing I,E

Type to be IMPORTED or
EXPORTED. All possible short
texts can be displayed in the tool
defaultsTOOLBOX II

System - Toolbox Info - detailed

routing types

Function Possible entries for IMPORT or I,E

Export mode
- Range: specified range is
replaced or exported
-All: complete detailed routing is
replaced or exported
-Append: File is appended at the
end of the detailed routing (only
possible with import)

Imp - Yes: The line is processed during I

import

TOOLBOX II Users Manual D30-500-1.05 3-185

 OPM II

- No: the line is skipped during

import

ImpStart If the entry Range is specified in the I

column Function, then the start line
for the import is defined in this
column

ImpStop If the entry Range is specified in the I

column Function, then the last line
for the import is defined in this
column

Exp - Yes: The line is processed during E

import
- No: the line is skipped during
import

ExpStart If the entry Range is specified in the E

column Function, then the start line
for the import is defined in this
column

ExpStop If the entry Range is specified in the E

column Function, then the last line
for the import is defined in this
column.

Possible errors

N The column headings in the IMPORT or Export file must match the column headings in the
TOOLBOX II. In the case of errrors, a corresponding ouput occurs in Import- Export protocol

N If with selected function Range the import file contains less records than specified by ImpStart to
ImpStop, the missing records in the detailed routing are set to default. A corresponding notice is
output in the error protocol.

N If with selected function Range, the detailed routing contains less records than specified by
ExpStart to ExpStop, only the valid range is exported and indicated in the error protocol.

N During import, all records are checked for plausibility. A complete error list is output in the error
protocol.

N The import function only adopts the data with complete freedom or errors

N At the beginning of the import- Export proceudre, all Au's concerned are blocked for other
operations.

Import and Export in command line mode

The same functionallaty can be done in a command line. So it is possible to make the import and export
of detail Routing tables automatically.

Syntax description:

3-186 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

DRC.EXE IN|OUT USERNAME/PASSWORD /I:STEUERFILE [/S:SYST-ANL-ID]

[/D:DELIMITER] [/A:LOGFILE] [/L:O|A]

The parameters in detail:

N IN|OUT

import or export

N USERNAME/PASSWORD

TBII User and password

N /I

Csv File, for import and export. (description see above)

N /S

Systemtechnical plant for the AU's.

This parameter is optional. The default is the preset systemtechnical plant.

N /D

Seperator for the control file.

This parameter is optional. The default is ';'.

N /A

Logfile for import and export

This parameter is optional. The default is %TEMP%\DRCLOG.TXT.

N /L

O(verwrite) ... existing logfile will be overwritten

|A(ppend) ... new logfile will be appended.
This parameter is optional. The default is 'O'.

TOOLBOX II Users Manual D30-500-1.05 3-187

 OPM II

3.14.13. Definition of regions and automation units

In the system-technique of the OPM, regions and AU's can be defined. All necessary data are
interrogated with the help of a Wizard

Creating a Region

In the Pop Up Menu of the entry System-technique, via the menu item

CREATE REGION

The Wizard is started. The following entries are required:

N Number: Number of Region

N Name: Clear designation of the region

N Long text: optional long name of the region

N Short text CAEx II: Short text (max. 3 places) for the directory of the CAEx II File

By clicking the OK button, the new region is created.

Creating an AU

In the Pop Up Menu of the entry Region, via the menu item

CREATE AU

The Wizard is started. The following entries are required:

3-188 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

N Component number: Number of the component

N Short name : short name of the AU

N AU - Type: Type of this automation unit

N Further optional inputs

By clicking the OK button, the new AU is created.

TOOLBOX II Users Manual D30-500-1.05 3-189

 OPM II

3.14.14. Copy of automation units

It is possible to copy AU's into the system-technical tree of the OPM II via two different operating steps.

Cut and Paste

One marks an AU in the system-technique and copies this AU with the help of the menu item

COPY AU

of the Pop-Up menu into the Clipboard of the TOOLBOX II. Then either precisely one Danach können
entweder genau eine system-technical plant, precisely one region, or an optional number of AU's can
be marked and the parameters of the Clipboard inserted with the help of the menu item

PASTE AU

If pasting into a system-technical plant or a region takes place, justas with the creation of AU-objects, a
wizard appears. With the help of this, a new AU is created and then the parameters inserted.

Drag and Drop

With Drag and Drop, an AU can be dragged to a system-technical plant, a region or another AU of the
same Type. In the first of the two cases, a new AU is created with the help of a Wizard, which is
subsequently installed and the parameters copied.

The following is to be observed:

N Source and target AU-Type must be the same

N The target-AU must either have no parameters or it must have the parameter status Original (see
DDC). In the second case, the installing is deleted after interrogation and re-installed with the
help of the source AU and the parameters copied.

N The source-AU can be Original or read-only

N In the target-AU, an original state is always created.

3-190 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

N All 1703 and CAEx II respective CAEx plus parameters are copied and all necessary data, that
exist in the form of files. If the source-AU is CAEx-plus capable and linked signals exist on it,
before the copying process, a query to rename the signals appears. Ifthe user has selected
several automationunits as target-AU, this query appears for each individual AU.

TOOLBOX II Users Manual D30-500-1.05 3-191

 OPM II

3.14.15. Customer parameter sets

It is possible to define one or several customer parameters for each BSE or SIP. It is possible

N to create a cuustomer parameter record. The creation of a customer parameter record takes
place in OPM II. A customer parameter record contains thereby exactly as many parameter
blocks as the BSE or the SIP, from which the customer parameter record is created. The OPM II
thereby sees all parameter blocks as one unit. The saving of individual parameter blocks of a
BSE or a SIP is therefore not possible. The customer parameter records created in OPM II are
completely compatible with already existing customer parameter records.
During creation, a name must be assigned, and optionally a descriptional accompanying text
defined.

N Edit an already created customer parameter record.

With this function, it is possible to delete customer parameter records and modify accompanying
texts

In the tool Install, customer parameter records thus created are used for installing system elements.

The call up is carried out via the Pop-Up Menu items

CREATE CUSTOMER PARAMETER RECORDS

and

EDIT CUSTOMER PARAMETER RECORDS

of a system element.

3-192 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.14.16. Broadcast parametrizing

The system-technical Broadcast-parameterising for system elements with existing PD-Forms takes
place in principle by using the same operating steps as are currently necessary in the parameterising
tool PAR. In detail the following operating steps are required:

N in the system-technical overview, activation of the Pop-Up Menu in the PD-Form of a system
element.

N in activated Pop-Up Menu, selection of the menu item

N Broadcast-Parameterising

N in the dialogue window thatappears, selection of one or more system elements, for which the
Broadcast-parameterising is to be carried out

N in command-window of the PD-Form, parameterising of the desired parameters with

corresponding parameterising commands.

The OPM II thereby distributes at the end of each parameterising command, the parameter value to
those system elements, that the user selected in the previous operating step. The Broadcast-
parameterising is so long active, until the user has selected another PD-Form in the system-technical
overview.

TOOLBOX II Users Manual D30-500-1.05 3-193

 OPM II

3.14.17. Profibus parametrizing

For parameterising Profibus master, the external program from the company Hilscher is used. This
chapter describes the integration of this program in the TOOLBOX II.

The program from the company Hilscher for parameterising the Profibus isnotinstalled with TOOLBOX
II, but supplied on a separate CD.

Data storage of the Profibus parameters

The program of the company Hilscher stores the parameter data in files. The following two files are
thereby significant:
- Configuration file (Extension *.PB)
- Binary image with exported parameters (Extension *.DBM).
In the configuration file the installation of the Profibus with individual Slaves including their parameters
(with clear texts) are stored. From this file the parameters of all Slaves are then exported as binary
image to a file with the same name and extension *.DBM. This binary image is then transferred to the
destination system. Both files are located in the component path of the automation unit in which the SIP-
Profibus master is installed. The component path is composed the following way:

Customer drive:\sat\plants\TBI-customername\TBI-Region_short_text\Knnn

The individual pieces of information are derived from the system management of the TOOLBOX II for
the corresponding automation unit. nnn ... represents the component number (3-place decimal) Several
Profibus master SIPs can be installed in one automation unit. To establish an unambiguous Assignment
between the SIP and the configuration file, the filename is structured as follows:
- if the SIP is installed on the C-CPU: optional Text-Cxx-PREy
- if the SIP isinstalled on the M-CPU: optional Text-M-PREy
xx ... represents the number of the basic system element (2-place decimal), y ... represents the number
of the protocol element (1-place decimal)

Parameterising

The parameterising is started from the OPM in the system-technical overview via a context-menu of the
protocol element. First is checked, whether the program of the company Hirscher is installed. The
following Registry-entry must exist:

HKEY_LOCAL_MASCHINE\SOFTWARE\Hilscher GmbH\SyCon\Directory

If the program does not exist, the user is informed with a corresponding error information. Then the
configuration file belonging to the protocol element is sought in the component path. If the file is found,
then the program from the company Hirscher is started and this is given the filename of the
configuration file including path as transfer parameter. If the pertinent configuration file is not found, then
a default configuration file with the name

Cxx-PREy.PB

is stored in the component directory and the program is started with this file. As copy template for this
Default-file the file with the name

Profibus.PB

3-194 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

is used. This file is located in the same directory as the program from the company Hilscher and
iscreated during the installation of the program from the companyHilscher.
The user may rename the newly created file, whereby the name of the file must end with the text string
Cxx-PREy or M-PREy. When the user has finished pearameterising in the Hilscher-program, then he
must Export the file with the binary image (Extension *.DBM) from the Hilscher-program.
In a further step, the user must start the Ax1703-converter for the automatisionunit in OPM. The
converter then enters the binary image in the parameter block of the Profibus master-SIP. The
parameter block also contains 1703-parameters, that are parameterised with TOOLBOX II. These are
located at the records 0 to 0x1FF. The binary image is entered from the record 0x201 in the parameter
block. The actual length of the binary image is entered at record 0x200. During conversion, it is also
checked whether the length of the binary image does not exceed 16kB.

Laden

Loading the Profibus parameters takes place with the TOOLBOX II-tool Parameter Loader.

TOOLBOX II Users Manual D30-500-1.05 3-195

 OPM II

3.14.18. Documentation

The documentation of the parameters or their values is carried out by printing the Tree-part of the
system-technical parameterising. The printout takes the form of a Spreadsheet, i.e. the tree structure of
the system-technical parameterising is duplicated on a Spreadsheet. The documentation can be
selected via the Pop-Up Menu of an AU or a system element.

It is possible to output a preview before printing. In addition,itis possible to select several system
elements and print them out. In this case the preview is only available for the first entry, but all selected
system elements are printed.

PD-Forms or Spreadsheets can be printed individually. This takes place via the Pop-Up Menu at the
right of the Explorer window.

3-196 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.15. Transform and load

3.15.1. Overview

The converters in the OPM II converts parameter values from link images into a specific format for the
destination system. The method of imputing parameters in the OPM II is always the same for the user,
regardless of the destination system. During the conversion operation, the converter converts the data
into a specific format for the destination system.

For the conversion, the user can select various data quantities, depending on the destination system.
For example, with SAT 1703 one or several automaton units can be converted, for SAT 250 SCALA
one or several CAEs can be converted.

All link images are converted that are relevant for the selected destination system, and for which the link
address is completely filled out.

The conversion can be started by the user at any time by means of a menu entry in the OPM II. During
the conversion operation, information, warnings and errors are output in the output window of the OPM
II.

The following converters are available:

SAT 250
Link images : SAT 250/SK + Ax-Mode

SAT 230
Link images : SAT 230/Ax-Mode

SAT 1703
Link images : ACP and Ax 1703(IEC), SAT 1703/Ax Mode and SIP message address conversion

CAEx II
Link images : CAEx/ Ax Mode, ACP 1703 and Ax 1703(IEC) and SAT 1703/Ax Mode

TOOLBOX II Users Manual D30-500-1.05 3-197

 OPM II

CAEX plus
Link images : CAEx plus/ACP and ACP 1703 and Ax 1703(IEC)

For parameter changes in the system technique no conversion operation is necessary. Each change of
system-engineering parameters is immediately converted automatically in the background.

3.15.1.1. Loading

Once the parameters have been successfully converted, these generated destination-system-specific
data must be loaded into the corresponding destination system. Only after this are the changes
executed effective in the plant. The handling varies depending on the destination system used:

SAT 250

The loading operation can be started directly after the conversion. This option can be found in the
Converter SAT 250.

SAT 230

The loading of changed data is not part of the functionality of the TOOLBOX II. After the conversion
operation a loading file (PVL file) is created. This file can be read in by SAT 230.

SAT 1703

The loading of the data by SAT 1703 is carried out using its own tool. The Loading Parameters. In this
tool the loading operation can be started for every AU. Thereby, data from the following converters is
loaded:

N SAT 1703

N CAEx II
After the conversion, code must then be generated. This operation generates a working
application from the function diagram and the assignments. The generation of code is started in
the CAEx II converter or directly in the AK Postprocessor.

N CAEx plus
After the conversion, code must then be generated. This operation generates a working
application from the function diagram and the assignments. The generation of code is started in
the CAEx plus converter or directly in CAEx plus.

N System technique (The conversion operation runs automatically after parameter changes)

3-198 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.15.2. When must be converted and loaded?

Action Converter Load

Periphery Links ACP and Ax SAT 1703 intelligent

1703(IEC) as well as SAT 1703/Ax
Mode
parameter change

Periphery Links ACP and Ax SAT 1703 intelligent

1703(IEC)
Assignment of command and
feedback

Periphery Links ACP and Ax SAT 1703 intelligent

1703(IEC) CAEx II (Assignment and Code)
Changing the message address CAEx plus (Signal List and Code)

CAEx II Links CAEx II (Assignment and Code) intelligent

Change

CAEx plus Links CAEx plus (Signal List and Code) intelligent
Change

System technique none intelligent

System-engineering parameters
(e.g.: Baud rate)

System technique SAT 1703 intelligent

Picture parameterization

SAT 250 Links SAT 250 (Loading as option)

Change

SAT 230Links SAT 230 (Loading from SAT 230) intelligent

Change

TOOLBOX II Users Manual D30-500-1.05 3-199

 OPM II

3.15.3. SAT 250

The converter for SAT 250 uses values from the link images of the following OPM destination systems

SAT 250/SK + Ax-Mode

3.15.3.1. Link Images

The following attributes of a link image must be filled out, so that a link image can be converted by the
converter.

SAT 250/SK + Ax Mode

Lk_CaeId

Lk_TA

Lk_Prep
The entry Activated must be selected.

All attributes must contain valid values. An invalid value can occur as a result of a formula or reference.

3.15.3.2. Handling

DESTINATION SYSTEMS | SAT 250 | COMMUNICATION | OPM II TO CAE250

Note: Before the start of the conversion operation a PVL Revision must be selected.

DESTINATION SYSTEMS | SAT 250 | SETTINGS | SELECT REVISION

3-200 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.15.3.3. Functions

Selection options

One or several CAE 250's can be selected. The conversion operation is carried out in the sequence of
the selection.

Options

N Transmit PV
The transmission of the process variables from the OPM II to the CAE is carried out.

N Start consistency check

The consistency check is executed in the CAE. The result of this check is displayed in the error
output of the OPM II.

N Start loader
After the completed transmission of the PV's the SAT 250 loader is started. The result of this
check is displayed in the error output of the OPM II.

N Only changed or not converted PV

Only changed and new PV 's are transmitted to the CAE 250.
Note: Default handling for the transmission of PV's. Link images for the entire process-
engineering plant are taken into consideration for the conversion.

TOOLBOX II Users Manual D30-500-1.05 3-201

 OPM II

N All PV
All PV 's are transmitted, regardless of whether these are changed or not.
Note: Use only for test and error localization. Default handling for the transmission of PV's. Link
images for the entire process-engineering plant are taken into consideration for the conversion.

N All PV (initialize CAE)

An absolute comparison of all PV 's is carried out. Thereby, PV 's that exist in the CAE, but do not
exist in the OPM II, are deleted in the CAE 250.
Note: Use only for the very first initialization. Link images for the entire process-engineering plant
are taken into consideration for the conversion.

A check for duplicate text addresses is always carried out.

3-202 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.15.4. SAT 230

The converter for SAT 230 uses values from the link images of the following OPM destination systems

SAT 230/Ax-Mode

3.15.4.1. Link Images

The following attributes of a link image must be filled out, so that a link image can be converted by the
converter.

SAT 230/Ax Mode

Lk_WLSID

Lk_TTA

Lk_Prep
The entry Activated must be selected.

All attributes must contain valid values. An invalid value can occur as a result of a formula or reference.

3.15.4.2. Handling

DESTINATION SYSTEMS | SAT 230 | PVL FILES | GENERATE

Note: Before the start of the conversion operation a PVL Revision must be selected.

DESTINATION SYSTEMS | SAT 230 | SETTINGS | SELECT REVISION

TOOLBOX II Users Manual D30-500-1.05 3-203

 OPM II

3.15.4.3. Functions

Selection options

One or several control center systems can be selected. The conversion operation is carried out in the
sequence of the selection.

Destination directory

Directory in which the PVL Files are generated.

The name of the PVL File is comprised as follows:

<Name of the control center system> + <2 digit number>

The two-digit number is automatically incremented with each conversion operation.

Options

N only changed or not converted PV

Only changed and new PV 's are written in the PVL File.
Note: Default handling for the transmission of PV's. Link images for the entire process-
engineering plant are taken into consideration for the conversion.

3-204 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

N All PV
All PV 's are written in the PVL File
Note: Default handling for the transmission of PV's. Link images for the entire process-
engineering plant are taken into consideration for the conversion.

N Check for duplicate text addresses / duplicate peripheral addresses

With the conversion operation a check is carried out for duplicate text addresses and duplicate
peripheral addresses.

TOOLBOX II Users Manual D30-500-1.05 3-205

 OPM II

3.15.5. SAT 1703

The converter for SAT 1703 uses values from link images of the following OPM destination systems

ACP 1703 and Ax 1703(IEC)

SAT 1703/Ax Mode

SIP message address conversion

3.15.5.1. Link Images

The following attributes of a link image must be filled out so that a link image can be converted by the
converter.

ACP and Ax 1703(IEC) as well as SAT 1703/Ax Mode

Lk_Reg

Lk_Comp

Lk_BSE

Lk_SSE
The available entries are dependent on the selected category (Lk_Cat).

Lk_DP
The available entries are dependent on the selected category (Lk_Cat).

Lk_DS
must contain the OPM destination system ACP and Ax 1703(IEC) or SAT 1703/Ax Mode. The OPM
destination system is determined with the Type definition.

Lk_Cat
must contain a category that corresponds with the settings of Lk_BSE and Lk_SSE. If a part category
(e.g.: DI_EM single-point information) is selected, then the conversion operation produces an error.

Lk_Prep
must contain the value Activated.

All attributes must contain valid values. An invalid value can occur as a result of a formula or reference.

SIP message address conversion

N Lk_Reg

N Lk_Comp

N Lk_BSE

3-206 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

N Lk_SSE
The available entries are dependent on the selected category (Lk_Cat).

N Lk_DS
must contain the OPM destination system SIP message address conversion. The OPM
destination system is determined with the Type definition.

N Lk_Cat
must contain a category that corresponds with the settings of Lk_BSE and Lk_SSE.

N Lk_Prep
must contain the value Activated.

All attributes must contain valid values. An invalid value can occur as a result of a formula or reference.

3.15.5.2. Handling

DESTINATION SYSTEMS | SAT 1703

3.15.5.3. Functions

TOOLBOX II Users Manual D30-500-1.05 3-207

 OPM II

Selection options

One or several automation units can be selected. The conversion operation takes place in the sequence
of the selection.

Options

N Convert parameters
Parameters are converted for ACP and Ax 1703(IEC) and SAT 1703/Ax Mode and the Hardware
assignment is created new.
Note: Link images of the particular range are taken into account for the conversion.

N Create Hardware assignment

The Hardware assignment is created new for ACP and Ax 1703(IEC) and SAT 1703/Ax Mode.
(connection of link image to the Pin of the module).
Note: This function can be carried out at any time. Thereby no parameters are changed, rather
only the assignment between link address and Hardware Pin is updated. Link images of the
particular range are taken into account for the conversion.

N Generate message address conversion

All message address conversions of the selected automation units are generated.
Note: Link image of the entire process-engineering plant are taken into account for the
conversion.

N Generate Profibus Parameters

All Profibus parameters of the selected automation units are generated.
Note: Link image of the entire process-engineering plant are taken into account for the
conversion.

N Generate Elcad File

A file for the further processing in ELCAD is created in the specified path.
Note: Link images of the particular range are taken into account for the conversion.

3-208 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.15.6. CAEx II

3.15.6.1. OPM II Destination Systems

The converter for CAEx II uses values from link images of the following OPM destination systems

CAEx/ Ax Mode (spontaneous datapoints)

ACP 1703 and Ax 1703(IEC) as well as SAT 1703/Ax Mode (periodical datapoints)

3.15.6.2. Link Images

Only link images of the relevant range are taken into consideration for the conversion. The following
attributes of a link image must be filled out so that a link image can be converted by the converter.

CAEx/ Ax Mode (spontaneous datapoints)

N Lk_Reg

N Lk_Comp

N Lk_BSE

N Lk_Proj
must contain a project defined in the CAEx. The check is carried out during conversion.

N Lk_IOM
must contain a IOM defined in the CAEx. The check is carried out during conversion.

N Lk_DS
must contain the OPM destination system CAEx/ Ax Mode. The OPM destination system is
determined with the Type definition.

N Lk_Cat

N Lk_Prep
must contain the value Activated.

All attributes must contain valid values. An invalid value can occur as a result of a formula or reference.

ACP 1703 and Ax 1703(IEC) as well as SAT 1703/Ax Mode (periodical datapoints)

N Lk_Reg

N Lk_Comp

N Lk_BSE

TOOLBOX II Users Manual D30-500-1.05 3-209

 OPM II

N Lk_SSE
must contain a valid supplementary system element (Peripheral Element). An invalid value can
occur as a result of a formula or reference. The available entries are dependent on the selected
category (Lk_Cat).

N Lk_DP
must contain a valid periodical datapoint. An invalid value can occur as a result of a formula or
reference. The available entries are dependent on the selected category (Lk_Cat).

N Lk_DS
must contain the OPM destination system ACP and Ax 1703(IEC) or SAT 1703/Ax Mode. The
OPM destination system is determined with the Type definition.

N Lk_Cat
must contain a category that corresponds with the settings of Lk_BSE and Lk_SSE. If a part
category (e.g.: DI_EM single-point information) is selected, then the conversion operation
produces an error.

N Lk_Prep
must contain the value Activated.

N CAEx Project
must contain a project defined in the CAEx. The check takes place during conversion.

N CAEx IOM
must contain an IOM defined in the CAEx. The check takes place during conversion.

N CAEx IOM1
is optional. Is only used for the generation of the IOM File.

N CAEx Longtext
is optional. Is only used for the generation of the IOM File.

All attributes must contain valid values. An invalid value can occur as a result of a formula or reference.

3.15.6.3. Handling

DESTINATION SYSTEMS | CAEX II | AX 1703 .....

3-210 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.15.6.4. Functions - Generate assignment code

Selection options

One or several basis system elements of automation units can be selected. The conversion operation
is carried out in the sequence of the selection.

Options

Generate assignment
The assignment for the selected basis system element is generated. Optionally, Status Information can
also be selected. Only those datapoints are assigned that are defined in the CAEx II Project. Datapoints
that are defined in the OPM (or formed by means of Status Information) but do not exist in the CAEx II
Project, are ignored by the converter.
Note: Link images of the relevant range are taken into consideration for the conversion.

TOOLBOX II Users Manual D30-500-1.05 3-211

 OPM II

Generate Code
For the selected Basis System Element code is generated after completed conversion.

3.15.6.5. Functions - Generate IOM File

An IOM file is created in the components path. With the help of this IOM File IOM names and longtexts
can be imported in CAEx II and assigned in the function diagram.

Selection options

One or several Basis System Elements of automation units can be selected. The conversion operation
is carried out in the sequence of the selection.

Options

The Status Information, that is also to be generated in the IOM File, can be selected.

3-212 D30-500-1.05 TOOLBOX II Users Manual

 OPM II

3.15.7. CAEx plus

3.15.7.1. OPM II Destination Systems

The converter for CAEx plus uses values from link images of the following OPM destination systems

CAEx plus/ACP (spontaneous datapoints)

ACP 1703 and Ax 1703(IEC) (periodical datapoints)

3.15.7.2. Link Images

Link images of the process-engineering plant are taken into consideration for the conversion. If Link
images are defined directly in the level LNK, then these are not taken into account by the converter. The
following attributes of a link image must be filled out so that a link image can be converted by the
converter.

CAEx plus/ACP (spontaneous datapoints)

N Lk_TI

N Lk_DS

N Lk_Cat
must contain a category that corresponds with the settings of Lk_TI.

N Lk_Prep
must contain the value Activated.

All attributes must contain valid values. An invalid value can occur as a result of a formula or reference.

ACP 1703 and Ax 1703(IEC) (periodical datapoints)

N Lk_Reg

N Lk_Comp

N Lk_BSE

N Lk_SSE
must contain a valid supplementary system element (Peripheral Element). An invalid value can
occur as a result of a formula or reference. The available entries are dependent on the selected
category (Lk_Cat).

N Lk_DP
must contain a valid datapoint. An invalid value can occur as a result of a formula or reference.
The available entries are dependent on the selected category(Lk_Cat)

TOOLBOX II Users Manual D30-500-1.05 3-213

 OPM II

N Lk_DS
must contain the OPM destination system ACP and Ax 1703(IEC) or SAT 1703/Ax Mode. The
OPM destination system is determined with the Type definition.

N Lk_Cat
must contain a category that correspond with the settings of Lk_BSE and Lk_SSE. If a part
category (e.g.: DI_EM single-point information) is selected, then the conversion operation
produces an error.

N Lk_Prep
must contain the value Activated.

N Use CAEx plus

must contain the entry YES. An invalid value can occur as a result of a formula or reference.

All attributes must contain valid values. An invalid value can occur as a result of a formula or reference.

3.15.7.3. Handling

DESTINATION SYSTEMS | CAEX PLUS

3.15.7.4. Functions

Selection options

If no selection is made, then only the signal list is generated. This contains all signals of the entire
process-engineering plant. Link images that are not assigned to any signal are not taken into account.

If one or several automation units is selected, then the signal list for the entire process-engineering plant
is generated and subsequently code is generated for the selected automation units.

For further information see: CAEx plus

3-214 D30-500-1.05 TOOLBOX II Users Manual

 Assembly technique documentation

4. Assembly technique documentation

4.1. Overview

The assembly-technical documentation is needed in order to document the pin assignment for each
system element, i.e.

N The individual pins of a system element with the associated attributes (such as cable colour,
position on the marshalling rack)

N All relevant information of the system element (such as designation of pins and card points,
message address per signal)

In the forms of the assembly-technical documentation, the following information is shown:

N Physical structure of the system element (here each pin is shown, even those which cannot be
assigned, such as group inputs)

N The system-technical address which each pin has within a message

N The process-technical address which each pin has within a message

N General information of a pin (long text)

N Allocation of the pin to a link image in the OPM (process-technical address)

Free Columns

In the assembly-technical documentation, up to 30 free columns can be defined. These are defined via:

FREE COLUMNS | NEW CREATE

in the pin view.

When creating new, a distinction is made between the following functions:

N Free columns: These can be filled with values freely by the user.

N Infotypes: Here, all of the infotypes which are allocated to the process-technical plants are offered
for selection. The values of these infotypes can only be altered in the OPM and not in the ALW.

N OPM parameters: Here, all parameters are offered for selection. These can only be displayed in
the ALW and cannot be altered.

Columns are deleted via the menu item

NEW COLUMNS | DELETE OR DELETE ALL

TOOLBOX II Users Manual D30-500-1.05 4-1

 Assembly technique documentation

If columns are deleted which correspond to an infotype or a parameter in the OPM then only the display
is deleted from the assembly technical documentation tool and not the values.

Define Visible Columns

For the displaying of the documentation, it is possible to define the visible columns. These definitions
can be carried out via the popup menu of the window. The affected settings are saved with the data of
the process-technical plant.

Revision

The revision of the assembly technical documentation tool is shown:

N In the printout (or in the page view), and

N Under the menu item Options | Display revision

On every change and subsequent save, the revision is increased. In the assembly technical
documentation, the editor is fixed under:

OPTIONS | FIX EDITOR

In the menu item

OPTIONS | FIX LOGO

the logo for the printing out of the form is fixed. The logo is saved for each process-technical plant. *.jpg
and *.bmp files are supported.

Cable and Marshalling Rack

For the assigning of double-Euroformat modules, predefined cable connections and marshalling
terminal?? connections are done in advance.

The selection of the predefined cable connections and hedgehog connections can be done via the
menu item

EXTRAS | OPTIONS

4-2 D30-500-1.05 TOOLBOX II Users Manual

 Assembly technique documentation

The selection made is saved with the data of the process-technical plant.

TOOLBOX II Users Manual D30-500-1.05 4-3

 Assembly technique documentation

4.2. Handling

Tool start

SAT TOOLBOX II | TOOLBOX II SERVICE PROGRAMS | ASSEMBLY TECHNIQUE DOCUMENTATION

Selecting of AU for documentation

M-DCLICK-L

Selecting of slot to be documented.

M-DCLICK-L

4-4 D30-500-1.05 TOOLBOX II Users Manual

 Assembly technique documentation

4.3. Description of columns

The following columns are displayed in the assembly-technical documentation:

N BEZ
Designation of the HW pin

N I/O
Input or output of the data point

N W# (only for SAT1703/Ax-Mode destination system)

Value number of the message address

N BIT (only for SAT1703/Ax-Mode destination system)

Bit number of the message address

N SA (only for SAT1703/Ax-Mode destination system)

Subaddress of the message address

N CASDU1 (only for the OPM ACP1703 and 1703/ax(IEC) destination systems)

N CASDU2 (only for the OPM ACP1703 and 1703/ax(IEC) destination systems)

N IOA1 (only for the OPM ACP1703 and 1703/ax(IEC) destination systems)

N IOA2 (only for the OPM ACP1703 and 1703/ax(IEC) destination systems)

N IOA3 (only for the OPM ACP1703 and 1703/ax(IEC) destination systems)

N TI (only for the OPM ACP1703 and 1703/ax(IEC) destination systems)

N Process-technical address
Process-technical address of the 1703 Ax link image. For data points which occupy several HW
pins (e.g. double-point information items) the same process-technical address is entered.

N Pin_Longtext
The contents of the Pin_Longtext attribute are shown. (The value of this attribute is altered in the
OPM)

TOOLBOX II Users Manual D30-500-1.05 4-5

 Assembly technique documentation

N Label
In the 1703_Ax link, the attribute label can be used. In this attribute, state texts can be selected.
For data points which occupy several HW pins (e.g. double-point information items) this status
text is entered for each pin (e.g. in, out). If this status text is used for data points which occupy
only one pin then the first part of the status text is displayed.

N K.PKT
Module card point

N Cable
Name of the cable. The name is made up as follows: -W (fixed text) + Number of the mounting
rack designation (definition in assembly technology) + Number of the mounting rack position.
e.g. -W303

N Wire
Number and colour of the cable wire. The cable type can be selected via Extras-> Options.

N RVG
Name of the marshalling rack. The name is made up as follows: -X (fixed text) + Number of the
mounting rack designation (definition in assembly technology) + Number of the mounting rack
position.
e.g. -X303

N RVGP
Number of the marshalling rack. The marshalling rack type can be selected via
Extras-> Options.

4-6 D30-500-1.05 TOOLBOX II Users Manual

 Data Distribution Center

5. Data Distribution Center

5.1. Overview

The Data Distribution Center provides the possibility of exporting, importing or managing TOOLBOX II
data.

By means of the Export- Import function, data can be backed up and restored. Work can be carried out
in teamwork on several TOOLBOX II PC's without network connection, and these distributed data
stocks can be brought together again at a later time.

It is possible to display the current state of the default customer, to delete read-only parameters and to
change original identifiers of AU's and ranges with administrator authorizations.

Here are a few examples to facilitate fast entry in the tool:

Backup

By means of a Drag&Drop with the CTRL key a complete backup of a plant can be created. After
selecting the Export tab, a Drag&Drop of the customer (left window top node) into the right window
using the CTRL key is sufficient.

ACTION -> START EXPORT

After entering the filename the Backup is executed.

By means of selective selection of system components optional backups can be compiled. If e.g.: only
one region and the plant management is to be backed up, then these two nodes in the left window are
to be dragged by means of Drag&Drop (or Drag&Drop with CTRL key for Backups) into the right
window. The Backup is started as described above.

Exporting Originals

Drag&Drop the corresponding AU's and ranges. Thereby the data are transferred 1:1 into the Export
record.(i.e.: Original becomes Original, read-only parameter becomes read-only parameter, copy
becomes copy). In the database, for AU's the original identifier becomes a read-only parameter or for
ranges a copy.

Import

After switching to the tab Import the dialogue is displayed immediately, in which the filename of the
import record can be specified. After selecting the Import file the CAEx-drive is interrogated for the
CAExII data. After that the contents of the import record is visible in the left part of the window, in the
right part of the window the contents of the corresponding plant in the database (if this plant does not
yet exist in the database, the right part of the window is empty).

TOOLBOX II Users Manual D30-500-1.05 5-1

 Data Distribution Center

By means of Drag&Drop, from the import record it can be selectively chosen, which plant components
are to be imported. If e.g.: an AU that exists as original in the import record is to be transferred into the
database as an original, then this AU must be dragged from left to right by means of Drag&Drop.

The Import is started with

ACTION -> START IMPORT

Note: If the import record has been created with a version earlier than 3.0, then a selective AU selection
is not possible.

Presets after the Import

If the plant that is imported is not preset, then an interrogation of whether or not this is to be carried out
appears automatically.
Note: The preset plant is first accepted after the restart of all Toolbox II tools.

Cancellation of selection

By means of Drag&Drop from the right into the left window a selection can be canceled.

5-2 D30-500-1.05 TOOLBOX II Users Manual

 Data Distribution Center

5.2. Handling

Tool selection

SAT TOOLBOX II ->DATA DISTRIBUTION CENTER

Import of data

TAB IMPORT

A dialogue opens automatically in which the Import file can be selected. In addition, a drive for the
storage of the CAEx data (GPS Files) can be selected. Optionally, data of the assembly-engineering
documentation can be selected.

Drag&Drop the required data

Drag&Drop the data from the left window (Import record) into the right window (Database) selects the
data to be imported. The selected data are colored blue in the right window (Database).
For the selection of AU's, by pressing the CTRL key during the Drag&Drop a Backup is imported
(without CTRL key an original, but only if an original already exists in the file)
Drag&Drop the data from the right window (Database) into the left window (Import record), cancels the
selection.

ACTION -> START IMPORT

By means of this menu item the import operation is started. In the lower part of the window a logfile is
displayed. In this output window the error output can be displayed by selecting the tab Error.

Note: From Import records that have been created with a TOOLBOX II Version earlier than 3.0, it is not
possible to select individual AU's.

Export of data

TAB EXPORT/BACKUP

On the left is the window of the default customers in the TOOLBOX II Database, on the right the initially
blank window of the Export record.

Drag&Drop the required data.

Drag&Drop the data from the left window (Database) into the right window (Export record) selects the
data to be exported. The selected data are colored blue in the right window (Export record).
For the selection of AU's, by pressing the CTRL key during the Drag&Drop, a Backup of the AU is
created (in the database an original stand is retained, in the event that it was previously already an
original)
For the selection of ranges, by pressing the CTRL key during the Drag&Drop a copy stand can be
created in the export record.

Drag&Drop the data from the right window (Export record) into the left window (Database), cancels the
selection.

ACTION -> START EXPORT

TOOLBOX II Users Manual D30-500-1.05 5-3

 Data Distribution Center

By means of this menu item the export operation is started. In the lower part of the window a logfile is
displayed. In this output window the error output can be displayed by selecting the tab Error.

Deleting read-only parameters of AU's

TAB DEFAULT CUSTOMER/PLANT

In this window the default customer and his default system-engineering-, process-engineering plant is
displayed.

POP UP MENU -> DELETE READ-ONLY PARAMETERS

This function deletes AU's with the status read-only parameter from the database.

Delete copy of ranges

TAB DEFAULT CUSTOMER/PLANT

In this window the default customer and his default system-engineering-, process-engineering plant is
displayed.

POP UP MENU -> DELETE COPY

This function deletes ranges with the status Copy from the database.

Firmware updates

A part of the tree contains all firmware updates for SAT 1703 that are used in the displayed plant
(configured system elements).

With the import operation the user can perform the following actions:

5-4 D30-500-1.05 TOOLBOX II Users Manual

 Data Distribution Center

Import all or individual firmware updates

With the selection of the plant (or parts of it) all firmware updates in the right window are copied. The
entire tree of firmware updates or individual firmware updates can be moved from the right to the left
window.
Only the firmware updates visible in the right window are imported into the preset TOOLBOX II
database.

Import BETA versions of firmware updates

All BETA versions used are displayed in the tree. These firmware updates can be selected, as
described above. The import of BETA versions however always only takes place into the local
TOOLBOX II database, regardless of which database is preset.

With the export operation, the user can perform the following actions:

Transfer all or individual firmware updates into the export record

With the selection of the plant (or parts of it) all firmware updates in the right window are copied. The
entire tree of firmware updates or individual firmware updates can be moved from the right to the left
window.
Only the firmware updates visible in the right window are transferred in the export record.

Transfer BETA versions of firmware updates into the export record

BETA versions can be transferred in the export record as described above.

TOOLBOX II Users Manual D30-500-1.05 5-5

 Data Distribution Center

CAEx plus Project Library

The project library in CAEx plus represents a simple project-specific possibility for the
standardization of function modules. It is now possible to selectively import or export the
project library in the Data-Distribution-Center. The project library is now an independent node in
the data overview below the process-engineering plant and in addition has an identifier, whether
this is an original or read-only status.

In CAEx plus, with immediate effect it is now prevented that a read-only status of the project
library can be edited. A read-only status of the project library can of course be used in CAEx
plus.

5-6 D30-500-1.05 TOOLBOX II Users Manual

 Data Distribution Center

5.3. Automatic backup

In the TOOLBOX II the creation of Backups can be automated. For this, first a control file must be
created in the DDC. This Control File can be executed batch-controlled at a later time.

The Control File is created as follows:

N Open the DDC and switch to the tab Export

N Compile the Export record. (regardless of the selection, always only AU read-only parameters
and range copies are kept in the created Backup)

N By means of the menu item "Action -> Start Export Controlfile" a dialogue is opened

N Enter the path and filename

The Control File is executed as follows:

N Open a DOS window

N DDC .. Name of the program

controlfile .. Name and path of the control file
-B(BackupFilename) .. Option -B and name and path of the Backup file (without space)
-L(Logfilename) .. Option -L and name and path of the logfile (without space). This information is
optional.
-D ... automatic name generation. The name of the Backup file and the Logfile is composed as
follows: (Backupfilename)[current date]_[current hours and minutes] (Logfilename)[current
date]_[current hours and minutes]

Example:

DDC C:\TEMP\MYCTRL.SCD -BC:\BACKUP\Saving -D

RESULT: SAVING15072001_1735.001

The option -? displays Help.

The ComputerCode described above can also be executed in a Batch File (.CMD or .BAT).

TOOLBOX II Users Manual D30-500-1.05 5-7

 CAEx plus

6. CAEx plus

6.1. Overview

All external signals that are used in CAEx plus, are created and managed in the OPM II. The OPM II is
the source for these data .
The data created in the OPM II are made available for the CAEx plus by means of a conversion
operation, and are available in the signal list in the CAEx plus. This signal list contains all signals of a
process-engineering plant.
In CAEx plus these signals can be used directly with Drag&Drop.

Internal variables, that are required for the communication within a BSE, are created directly in the
CAEx plus. (comparable with local and global markers in CAEx II)

In OPM II 2 different Link types are defined for CAEx plus:

Link type CAExplus/ACP

In Link type CAExplus/ACP all signals are defined, except signals that are to be further processed
periodically by the locally connected periphery.
This link type does not contain any specific link address, but rather only the type identification (Lk_TI). In
the OPM II it is not determined, for which BSE this link is valid.
If the converter finds a link from the destination system CAEx plus/ACP, then the process-engineering
address of this image (up to signal level) is entered as signal name in the signal list. The process-
engineering address in the OPM II always corresponds with the designator of the signal in the CAEx
plus.
First when a signal in the CAEx plus is used on one or several BSE's is the input- and output routing
generated for the BSE(s) concerned when the code is generated.
i.e.: In the OPM II always only1 CAEx plus Link is to be created. Regardless of on which BSE this signal
is processed, and regardless of whether it is used as input or output.

TOOLBOX II Users Manual D30-500-1.05 6-1

 CAEx plus

Link type ACP 1703 and Ax 1703 (ACP)

In the Link type ACP 1703 and Ax 1703 (ACP) all signals are defined that are to be further processed
periodically by the locally connected periphery.
In the link it is defined by the attribute "Use_CAEx_plus", whether or not this link is to be taken into
account with the conversion of the CAEx plus.
The name of the signal corresponds with the process-engineering address in the OPM II (up to signal
level)
Since periodically transmitted data can only be further processed on the locally connected BSE, the link
address of the image determines, for which BSE the periodical further processing is possible.

6-2 D30-500-1.05 TOOLBOX II Users Manual

 CAEx plus

TOOLBOX II Users Manual D30-500-1.05 6-3

 CAEx plus

6.2. Periodical to spontaneous data

Periodical data from peripheral elements can only be further processed on the local BSE. To make
these data also available to other AU's or control systems, it is necessary to convert from a periodical
transmission to a spontaneous transmission. This conversion takes place in the function diagram of the
local BSE.

The following steps are necessary for this:

Create a signal in the OPM, that contains a link type ACP 1703 and Ax 1703 (ACP) (periodical data of
the peripheral element) and CAExplus/ACP (spontaneous message).

Create the link type ACP 1703 and Ax 1703 (ACP) on the periphery. As a result the link address is filled
out. Set parameter Use_CAEX_plus to "Yes".

Fill out the message address (CASDU1,CASDU2,IOA1,IOA2,IOA3) and the link address of the link type
CAExplus/ACP. Set parameter Make spontaneous to Yes.

Generation of the CAExplus

Use this signal in the local BSE. It is thereby sufficient to place this signal in the function diagram. The
input- and output routing is generated automatically.

6-4 D30-500-1.05 TOOLBOX II Users Manual

 CAEx plus

6.3. Update Signal List

Due to faulty input when copying function diagrams, by making link images ready or by setting the
parameter "Use in the CAEx plus" to NO, faulty or no longer needed entries can occur in the signal list.
Wrongly occurring entries in the CAEx plus signal list can be removed with the Update Signal List
function. This affects the following entries:

N Entries in the CAEx plus signal list which are not used in any function diagram and which are not
allocated to any corresponding signal in the OPM II. (can occur due to AU copying)

N Entries in the CAEx plus signal list which are not used in any function diagram and which are
allocated to a ready signal in the OPM II.(Can occur due to making link images ready or by
setting the parameter "Use in the CAEx plus" to NO)

In order to remove such entries from the CAEx plus signal list, the following steps are necessary.

N Close the OPM II

N Open a DOS input window and input the command

C:>siglistrepair
The OPM starts with the preset plant.

N Start the CAEx plus converter and generate the signal list by confirming the conversion dialog
with YES.
Destination systems | CAEx plus
A message box is opened in which it is pointed out that all signals of the signal list of the current
range will be deleted which have no reference to an image or a cross reference (use in function
diagram). If this dialog is confirmed with Yes, the corresponding entries will be removed from the
signal list.

N A second message box is automatically opened in which it is pointed out that all signals which are
ready in the OPM can be deleted. If this dialog is confirmed with YES then these signals will be
deleted.

N A third message box is automatically opened in which it is pointed out that the internal cross
references can be deleted. These internally cross references are used for navigation within a
CAEx plus project. If this dialog is confirmed with Yes then these internal cross references will be
deleted.

N Following this, CAEx plus must be started and the cross references and the internal cross
references recreated. This is done from the popup menu of the project node:
- Recreate signal list (the cross references are recreated, the allocation of the signals to the OPM
link images is done via the VTA names)
- Plug-ins | Recreate signal cross references (the internal cross references which are needed for
navigation within a project are recreated)

N If the corresponding functions are executed, the updating of the signal list is concluded and CAEx
plus and OPM II can be closed and restarted via the TOOLBOX II menu.

Note: All faulty entries of the signal list are output in the error output. Only by saving in the OPM II are
these deleted. If the OPM is closed without saving, all entries are retained in the signal list. The actual
conversion (generating of the signal list) is not carried out.

TOOLBOX II Users Manual D30-500-1.05 6-5

 CAEx II

7. CAEx II

7.1. Status bits

For the creation of IOM Files and generating assignment from the OPM the following abbreviations are
used:

N NonTopical: /N

N Spontaneous: /S

N GeneralInterrogation: /G

N Invalid: /I

N Substituted: /U

N Blocked: /K

N Overflow /O

N ElapsedTimeInvalid /W

N PositiveNegative /P

N CauseOfTransmission: /T

N OriginatorAddress /H

N CommandIdentifier: /Q

N Pin0: /0

N Pin0: /1

N Pin0: /1

N Falls: /F

N Runs: /L

TOOLBOX II Users Manual D30-500-1.05 7-1

 CAEx II

N TransparentPin0: /0
TransparentPin1: /1
TransparentPin2: /2
TransparentPin3: /3
TransparentPin4: /4
TransparentPin5: /5
TransparentPin6: /6
TransparentPin7: /7
TransparentPin8: /8
TransparentPin9: /9
TransparentPin10: /A
TransparentPin11: /B
TransparentPin12: /C
TransparentPin13: /D
TransparentPin14: /E
TransparentPin15: /F

7-2 D30-500-1.05 TOOLBOX II Users Manual

 CAEx II

7.2. Print

The status lines of the printer port are no longer interrogated by the CAEx II. As a result it is also
possible to print out over Network Printserver from CAEx II. In order to be able to print out under
Windows NT 4.0, the device LPT1 must be assigned a printer.

Open a DOS-Command prompt and:

NET USE LPT1: \\Servername\Printer

TOOLBOX II Users Manual D30-500-1.05 7-3

 CAEx II

7.3. MK and uK Support

The compilation of MK and uK is carried out by means of Batch Files from a DOS window. The following
Batch Files are supplied in the directory ..\SAT\CAEx:

Compiling LM1703 VSRE

N LM1703/BVSE - Binary ... c_lm_b.bat

N LM1703/AVSE - Analogue and binary ... c_lm_a.bat

Compiling uK1703 VSRE

N uK1703/U - Multi-Point Traffic... c_uk_g.bat

N uK1703/U - Repeater operation... c_uk_s.bat

N uK1703/U - Processing (VSR/RT/STA) .... c_uk_v.bat

After creating a function diagram in CAEx II the task must be compiled. A file is created in the system
path with the extension "SLS". Subsequently the corresponding batchfile is called up with the complete
path including the SLS file without extension. The Hex File is generated and can be transmitted to an
EPROM with a programming device.

Example

c_uk_v C:\SAT\ANLAGEN\KUNDE\ANL\Kxxx\TEST

Project-specific batchfiles can be created for automating these compiling operations.

7-4 D30-500-1.05 TOOLBOX II Users Manual

 Data flow test

8. Data flow test

8.1. Overview

The "Data Flow Test" function allows you to log and visualize data streams (message flow) in
automation units of the systems:

N TM 1703 ACP

N BC 1703 ACP

N AK 1703

N AM 1703, AME 1703, and AMC 1703, and

N SK 1703 / KSK 1703

For a later analysis - offline, even at another location - it is also possible to make a recording with the
interface recorder.

The data flow test comprises the following features

N Start/Stop option for simultaneous logging

N for TM 1703 ACP, BC 1703 ACP AX1703, AM/ AME1703, the option of simultaneous logging of
the startup procedure

Note! Possible only for system elements known to TOOLBOX II. If system elements are not known in an
AU, the data flow test will not be possible only for such system elements.

Test points for SK/KSK1703:

N from or to peripheral element, as the case may be

N from or to SIP, as the case may be (transmitted or received messages)

N from or to special function in a CPU, as the case may be

N from or to a CPU, as the case may be

test points for AM/AME 1703:

N from or to protocol element, as the case may be

N from or to intelligent peripheral element, as the case may be

TOOLBOX II Users Manual D30-500-1.05 8-1

 Data flow test

Destination system filters and TOOLBOX filters - General information

N Definition may be carried out in the online or offline modes

N It is possible to save filters and test points or save them with Import Export Backup

N A HW/FW configuration is not required, but the Plant Management

N It is possible to save filters and test points or save them with Import Export Backup

on this topic, also see:

Destination system filters and toolbox filters

Visualization of the messages

Message display in

N plaintext

N hexadecimal format

N plaintext and hexadecimal format

Message parts to be shown can be selected e.g.

N Source/Destination address

N Data processing Type (DPT)

N Data format identifier (DFI)

N Transmission identifier

TOOLBOX info

N Message number

N AU Type

N Time of arrival at the TOOLBOX

Browsing forward / backward through all read out messages

N during readout

N after having stopped

interface recorder

N optional recording, saving of the messages transferred into the TOOLBOX

N Saving in recorder file that can be named freely

8-2 D30-500-1.05 TOOLBOX II Users Manual

 Data flow test

N Import, Export, save recorder file by means of Import/Export/Backup tool

N Activating of interface recorder during, prior to, after message readout

N Recorder file can be visualized offline for any number of times

N Toolbox filters are effective in visualization e.g. for searching, counting a certain status bit or a
certain address

N Test points and destination system filters of the recording time are displayed

TOOLBOX II Users Manual D30-500-1.05 8-3

 Data flow test

8.2. Handling

Tool start

SAT TOOLBOX II | DATA FLOW TEST

SELECTING OF AU

Defining of test points (simultaneous logging points) in the destination system

FILTERS/ TEST POINTS | TEST POINTS (AU WINDOW)

Set possible filters in the destination system (AU window)

FILTERS/ TEST POINTS | DESTINATION SYSTEM FILTERS

DEFINE...

Defining of possible TOOLBOX filters (main window)

FILTERS/ TEST POINTS | DESTINATION SYSTEM FILTERS

TOOLBOX FILTERS (FINE FILTERS, TIME WINDOW ...)

Starting of simultaneous logging (AU window)

FILTERS/ TEST POINTS

SIMULTANEOUS LOGGING | START

or

SIMULTANEOUS LOGGING | DELETE MESSAGE BUFFER AND START

N Deleting of message buffer

N Starting of recorder Defining the name of the recorder file (existing ones cannot be used)

N Readout of message buffer stop: -> Stop continue: -> Continue show current (most recent)
message: -> END button

N Quitting of simultaneous logging and recording: -> Stop -> Close

Play recording (main window)

N Set possible TOOLBOX filters

N Recording | Play, Select Recorder File

8-4 D30-500-1.05 TOOLBOX II Users Manual

 Data flow test

8.3. RTU filter

N They are destination-system-dependent (AU-type-dependent)

N They are loaded into the AU automatically (upon starting the simultaneous logging function)

N They can be set/reset selectively

N They can be set/reset selectively

Filters Overview:

N Filters for time-section messages

(SK/ KSK1703, AM/AME1703): Suppressing or logging of the messages

N Filters for direct data to peripheral elements

SK/ KSK1703) Suppressing or logging of the messages

N Fine filters for messages

SK/ KSK1703) Logging of messages selected on the basis of C#, DT, BD#, V#;; wildcards; 5
message filters

N Filter for function code

AM/ AME1703) Logging of user data objects (with/without time stamp) and system objects of the
destination system selected on the basis of function code

TOOLBOX II Users Manual D30-500-1.05 8-5

 Data flow test

8.4. TBII filter

N They are effective in the TOOLBOX II

N They are destination-system-dependent

N They can be edited in the main window

N Filters Overview

Filters Overview

N Fine filters for messages

Logging of messages selected on the basis of C#, DT, BD#, V#; Wildcards; 20 message filters.
For every filter, an AU Type is specified to which it is to applied. For the selected AU, only
message filters of the suitable AU Type are activated.

N Time window for messages with time stamp

Definition through start and end times; 1 time window;

N Status filter
Message selection based on criteria such as "spontaneous", "GI", "cyclic", "faulty or NRT", "high-
priority", and freely definable combinations; 1 Status filter;

8-6 D30-500-1.05 TOOLBOX II Users Manual

 Data flow test

8.5. Blocked data formats

Previous simultaneous logging of block data formats

It is possible to simultaneously log blocked messages in the data flow text as plaintext. So far, it had
been possible, e.g., in the transmission of several measured values in a message, to display only the
first measured value as plaintext. The remaining measured values were only shown in the HEX mode

From TOOLBOXII, version 3.0

The message with the blocked data objects continues to be regarded as a message in simultaneous
logging (i.e., one line in the HEX mode and one message header as plain text), the individual data
objects being displayed as separate "sections" in the plain text. For each data object, all attributes are
displayed (to enhance readability), i.e., certain attributes that are the same for all data objects of a
message (e.g. reg# , comp#) are shown several times.

TOOLBOX II Users Manual D30-500-1.05 8-7

 Diagnostic

9. Diagnostic

9.1. Overview

The "Diagnostics" function can be used on automation units of the systems

N TM 1703 ACP

N BC 1703 ACP

N AK 1703

N AM 1703, AME 1703, and AMC 1703

N SK 1703 / KSK 1703 (with connected or built-in LM 1703)

N MK 1703

N uK 1703

For this purpose, the local error tables of the selected AU's and the global error table are read out and
checked for error entries. The result of this check is displayed in a readable form (plain text).

Setting of diagnostic depth

N Plain text: total information, short information

N Optional: with binary information

Execution of diagnosis

N Automatic diagnosis (main window)

For every AU marked as faulty in the global error table, an AU diagnosis will be carried out.

N Network overview diagnosis (main window)

The global error table is read out from the local AU, error entries are displayed.

N AU overview diagnosis (main window)

For every AU that is marked as faulty in the global error table an errors overview (central error
table) is displayed.

individual AU diagnosis (AU window)

For every CPU system element, the individual CPU diagnosis will be carried out.

individual CPU diagnosis (AU window)

TOOLBOX II Users Manual D30-500-1.05 9-1

 Diagnostic

Diagnostic classes

Grouping of the error entries in error classes in the error tables. For each error class, there is a
corresponding diagnostic class

Diagnostic class Meaning

A Failure

B Module failure

I Internal errors

E External errors

K Communication errors

W Warning

F Freely configurable user error

T Test

General

General Network (main window)

General AU (AU window)

9-2 D30-500-1.05 TOOLBOX II Users Manual

 Diagnostic

9.2. Handling

Requirements

Parameters of Plant Management (read-only or original) available on TOOLBOX II, the parameters of
the automation unit concerned are not required

Selection of tool

SAT TOOLBOX II | DIAGNOSTICS

Automatic diagnosis

N Possibly select AU in main window

N Possibly execute General

Acknowledgement | Network (main window)

N Possibly set form of representation

Diagnostic depth (main window)

N Starting of automatic diagnosis (processes selected AU's or the entire network sequentially)

Network overview diagnosis

N Possibly execute General

Acknowledgement | Network (main window)

N Starting of network overview diagnosis

individual AU diagnosis, individual CPU diagnosis

N Open AU window
M-D-CLick-L on desired AU (main window)

N Possibly execute General

Acknowledgement | Acknowledge AU

N Possibly set form of representation

Diagnostic depth (main window)

N Selecting of diagnostic function

prior to the CPU diagnosis, the slot needs to be selected (M-CPU, P-CPU as expanded display)

N Possibly output diagnostic information on printer

TOOLBOX II Users Manual D30-500-1.05 9-3

 Load firmware

10. Load firmware

10.1. Overview

In the systems TM 1703 ACP, BC 1703 ACP, AK1703, AM 1703, and AME 1703, the firmware of all
system elements with microprocessor support is kept in loadable memory elements (Flash-PROM). In
the system SK1703 / KSK 1703, this applies only to a few system elements.

The function described in this section - the Flash Loader- is used to load firmware in memory elements
of the systems

N TM 1703 ACP

N BC 1703 ACP

N AK 1703

N AM 1703, AME 1703, and AMC 1703

N SK 1703 / KSK 1703

The Firmware Loader covers the following functions

N Loading to SK/ KSK1703 DIREKT

N Loading to TM 1703 ACP, BC 1703 ACP, AX 1703 AM/ AME1703 DIRECTLY, or from a
REMOTE location, or via a telnet-client connection

N Loading of selected AU's (main window)

N Loading of the HW/FW configured system elements of an AU (AU window)

N Loading of selected system elements of an AU (AU window)

(The functions only relate to firmware-loadable system elements)

Note: In the HW/FW configuration tool, it is possible to define a nominal flash revision for every flash-
loadable system element. If a revision has been defined, it is always this defined nominal revision that
will be loaded.

Nominal flash revision Behavior during firmname loading process

No definition Loading of the last official revision

Revision defined Loading of the defined revision

TOOLBOX II Users Manual D30-500-1.05 10-1

 Load firmware

10.2. Handling

SAT TOOLBOX II | LOAD FIRMWARE

Selecting of desired AU
Selecting of system element

LOAD (AU WINDOW) | SELECTED SYSTEM ELEMENTS

or

LOAD (AU WINDOW) | ENTIRE AU

10-2 D30-500-1.05 TOOLBOX II Users Manual

 Plant management

11. Plant management

11.1. Overview

Plant management is a basic prerequisite for working with TOOLBOX II. In the plant management, the
customer and his plants are created.

Project-technique

In project-technical segment, customers and projects are defined. System-technique In the system-
technique, automation units and their addressing (region, component) are defined.

TOOLBOX II Users Manual D30-500-1.05 11-1

 Plant management

Process-technique

In the process-technique, on the other hand, process-technical objects and their characteristics are
defined (circuit breaker consists of commands and state information). Since the OPM operates in both
the process-technique and the system-technique segment, the plant management must provide for an
allocation of these two areas.

System-technique

A system-technical plant can be assigned several process-technical plants.

11-2 D30-500-1.05 TOOLBOX II Users Manual

 Plant management

11.2. Handling

The plant management is defined in the tool "Plant Management" definition of project-technique

Definition of Customers

PROJECT-TECHNIQUE | DEFINE CUSTOMER

EDIT | ADD LINES

And fill in the following values:

N ID
Is an ID that is unique worldwide and given out by the SAT Project Management.
Must always be entered

N Short designation
Is the short designation of the customer
Must always be entered

N Long designation
Is the long designation of the customer
Can be entered as an option

N TBI customer name

Is needed for the conversion of TBI and the customer name is used for the DOS-side storage of
the CAEx II files (as directory)
Must be entered if a CAEx II is used

N TBI customer drive

For conversion and for the storage of the CAEx II files
Must be entered if a CAEx II is used

Definition of the system-technique

SYSTEM-TECHNIQUE | DEFINE

EDIT | ADD LINES

And fill in the following values:

N ID
Is an ID that is unique worldwide and given out by the SAT Project Management
Must always be entered

N Short designation
Is the short designation of the system-technical plant
Must always be entered

N Long designation
Is the long designation of the system-technical plant
Can be entered as an option

TOOLBOX II Users Manual D30-500-1.05 11-3

 Plant management

Definition of process-technique

PROCESS-TECHNIQUE | DEFINE

EDIT -> ADD LINES

And fill in the following values:

N ID
Is an ID that is unique worldwide and given out by the SAT Project Management
Must always be entered

N Short designation
Is the short designation of the system-technical plant
Must always be entered

N System-technical segment
It is also necessary to Assign the system-technical plant from the drop-down listbox
This is absolutely necessary

N Range
Select the entire line of the process-technical plant and click "range"
This is absolutely necessary. At least one range must be created consisting of any given area
number and an range name

11-4 D30-500-1.05 TOOLBOX II Users Manual

 Plant management

11.3. Process-technical plants copy

The entire process-technical plant is copied into an already existing process-technical plant. The
destination plant can be assigned to any given customer. If the destination plant already contains data,
these will be deletec. Deleted are: all area data (incl. Types, images, default presets) all data of the
process-technical plant: formulas, Cae-Id, Wls-Id

Handling

Start the Plant Management tool of the TBII utilities

SAT TOOLBOX II | PLANT MANAGEMENT

Select the plant that is to be copied.

RIGHT MOUSE BUTTON | COPY PROCESS-TECHNICAL PLANT

Change the customer via the drop-down listbox

Create a new process-technical plant for the new customer, and

RIGHT MOUSE BUTTON | INSERT PROCESS-TECHNICAL PLANT

Note: It is also possible to copy to an already existing plant, however, the entire process-technical plant
is deleted prior to the copying procedure.

TOOLBOX II Users Manual D30-500-1.05 11-5

 Plant management

11.4. Range copy

The following data of the area are copied: Types, images, defaults, formulas In addition, the following
data of the process-technical plant are copied: CAE definitions, WLS definitions, table structure of mass
editing, options for typeless images, option for level separation characters in image name

The following information is to taken into consideration

N The destination plant can be assigned to any given customer.

N The existing areas of the destination plant are not deleted. If there already are areas having the
same name as the one to be copied, a suffix will be added to the area name.

N If levels have already been defined in the destination plant, they will not be renamed.

N If a name conflict arises when the data are copied, a suffix will be added to the respective name,
as well.

N All converted link images are set to non-converted.

Handling

Start the plant management tool

SAT TOOLBOX II | PLANT MANAGEMENT

Select the process-technical plant

Select the range source

In the range view, select a range

If copying to another customer is to be carried out, it is also possible to select another customer from
the drop-down listbox.

RIGHT MOUSE BUTTON | COPY AREA

Select the range destination

Click on Plants button

If copying to another customer is to be carried out, it is also possible to select another customer from
the drop-down listbox

11-6 D30-500-1.05 TOOLBOX II Users Manual

 Plant management

Select the process-technical plant into which the area is to be copied.

Double-click into the areas view

RIGHT MOUSE BUTTON | INSERT RANGE

If an area is copied within a process-technical plant, proceed as follows:

N Create a temporary process-technical plant

N Copy the source area into this temporary process-technical plant

N Adapt the copied area (change name of image)

N Copy the temporary area into the original process-technical plant

TOOLBOX II Users Manual D30-500-1.05 11-7

 HW-FW Configuration

12. HW-FW Configuration

12.1. Overview

Using the "HW/FW configuring" function, the various slots are filled with automation units (AU's) of the
systems

N TM 1703 ACP

N BC 1703 ACP

N AK 1703

N AM 1703, AME 1703, AMC 1703

N SK 1703 /KSK1703

N LM 1703

Modules of the LM 1703 system are fitted as supplementary modules of the pertinent process control
element LE, that is in SK 1703 / KSK 1703.

The following functions are possible

N Slot/ Fit system element in position

N Expanded view: Display of M-CPU, P-CPU, SIP configuration in the HW/FW configuration display

N A system element can be fitted in several AU's in just one procedure

N Installing of SAT default parameter or customized parameters;customized parameters can be

selected individually for each user

N In most cases, 2 slots are configured per combination system element (e.g. VSRE12+SMIM) at
the same time.

N Changing of the slot from configured to prepared and vice versa;deleting the HW/FW
configuration of a slot

N Definition of the task for each VSRE system element (SK 1703) and display in HW/FW
configuration display

A brief explanation of various terms

N System element (SE)

A unit consisting of HARDWARE + FIRMWARE - inseparably connected with the intended
functionality

TOOLBOX II Users Manual D30-500-1.05 12-1

 HW-FW Configuration

N Combination system element

A combination of system elements that can be fitted only in conjunction e.g. VSRE12 + SMIM
(SMI-Bus Master) for interfacing of AM/AME 1703

N Parameter block (PB)

(= virtual module) The parameters of a system element are organized in parameter blocks; to
change a parameter, select the associated parameter block

N Default parameters
SAT's set of preconfigured SE parameters (defaults)

N Customized parameters
Project-specific parameters can be stored as customized parameter unit and used in configuring
just like default parameters

12-2 D30-500-1.05 TOOLBOX II Users Manual

 HW-FW Configuration

12.2. Handling

Tool selection

SAT TOOLBOX II | HW/FW CONFIGURATION

Select AU for HW/FW configuration

M-DCLICK-L

Select slot on which something is to be configured

M-DCLICK-L

Select group (FW Type), i.e., preselection of the possible system elements. Open the drop-down listbox
and select the FW type. Select actual system element Mark a system element and

M-DCLICK-L

The system element is configured

TOOLBOX II Users Manual D30-500-1.05 12-3

 HW-FW Configuration

12.3. Grants for parametrization

In the HW/FW configuring tool, it is possible to distinguish for each Ax1703 peripheral element, whether
it can be parameter-configured in the OPM or in the PSRII

This distinction is indicated in each component in the HW/FW configuration window and this is where it
can also be changed.

Select in the Param. column whether this system element is parameter-configured in the OPM or in the
PSR.

Notes:

N If you set "PSR" in the Param. column, this system element can only be parameter-configured
from the PSRII (Parameter Setting). Should you attempt to configure this system element from
OPM, a related error alarm will appear in the OPM.

N If you set "OPM" in the Param. column, this system element can only be parameter-configured
from the OPMI. Should you attempt to configure this system element from the PSRII, a related
error alarm will appear in the Parameter Setting tool.

N If data are imported from a version lower than V.3.00, PSR will be set for each system element in
the Param. column. If a system element has already been parameter-configured in a version
lower than V3.00 in the OPM, this column must be set to OPM after the import.

N If a new system element is FW/HW configured in version V.3.00, the Param. column will always
be set to OPM. However, if this system element is still parameter-configured in the Parameter
Setting tool, this column must be set to PSR.

12-4 D30-500-1.05 TOOLBOX II Users Manual

 Master data update

13. Master data update

13.1. Overview

The tool "Updating of master data" allows you to swap in new versions of a system element

Starting of the tool

SAT TOOLBOX II | IMPORT MASTER DATA

A related dialog is opened.

This dialog shows where the system element files are that are to be swapped in.

Once this selection has been completed, the swap-in starts. The main window of "Master Data Swap-In"
displays an updated progress indicator

Command line mode

FWI [-D FW-UPDATE-DIRECTORY] [-L LOGFILE]

TOOLBOX II Users Manual D30-500-1.05 13-1

 Master data update

The parameter Fw-Update-Directory is the directory which includes the FW updates. This is a
mandatory parameter.
The option -L defines the logfile (Name and location). This is a mandatory parameter

13-2 D30-500-1.05 TOOLBOX II Users Manual

 ST emulation

14. ST emulation

14.1. Overview

The ST-Emulation function allows you to executed in-system functions.

This function can be operated only by users holding "ST-emulation authorized user" rights.

General handling

At first, a command entered by the user is check by the Online Service Window for its syntax. If its
syntax is correct, a related message will be sent to the destination system. Otherwise, an error
information will be output.

Every syntactically correct command input by the user prompts a reply from the destination system.
Based on this reply, the new state (the state changed by the command) becomes discernible.

All commands input by the user and the replies of the component to these commands are saved in a
scrollable list. In this way, the progress of the entire session can be analyzed. Also the negative replies
are saved in the list.

A command is input in a separate entry field. To permit the fast entry of commands, the last 100
transmitted commands are saved. By selecting them, the user can transfer them to the command line.
Such a command can be edited on demand, before it is transmitted again.

Supported systems

N TM 1703 ACP

N BC 1703 ACP

N AK 1703

N AM 1703, AME 1703, and AMC 1703

N SK 1703 / KSK 1703 (with connected or built-in LM 1703)

N MK 1703

Value range of entries

Designation Value range

Valid region numbers 0 to 254

Valid component numbers 0 to 254

Valid AM/AK supplementary module numbers: 0 to 254

TOOLBOX II Users Manual D30-500-1.05 14-1

 ST emulation

Valid addresses for access to bytes 0 to FFFF

Valid addresses for access to addresses (16-bit) 0 to FFFE

Valid addresses to bytes of a 32-bit CPU 0 to FFFFFFFF

Valid segments 0 to FFFF

Commands

N L
Logon direct
This command is used to set up the connection to the directly connected automation unit. For the
execution of other commands, it is usually necessary that you have logged on beforehand.
Following successful logon, the M-CPU will be selected automatically.
During a logon, the step 4 enable word will be sent automatically (see "Enable" command).

N LR
Logon remote
This command is used to set up the remote connection to the automation unit. The destination
automation unit is selected in the usual way via AU selection
During a logon, the step 4 enable word will be sent automatically (see "Enable" command).

N E
Enable
This command corresponds to the entry of a password. Depending on the entered enable word,
the user obtains the authorization for accessing different memory areas. After this command has
been entered, a dialog window will appear. This window contains a specific enable word entry
field whose content is not displayed while the word is being entered.
During a logon, the step 4 enable word will be sent automatically (see "Enable" command).
There are the following authorization levels:
Enableword 1: RAM write
Enableword 2: NV-RAM write (parameter setting)
Enableword 3: RAM and NV-RAM write (parameter setting)
Enablewort 4: RAM and NV-RAM (parameter setting and factory configuration)

N R
Reset
This command causes the restart of the automation unit

N RB BSE bit mask [/P]

Reset for base system elements (BSE)
BSE bit mask : bit mask for selection of the BSE¦s (Hex): Bit0-Bit19: BSE0-BSE19, Bit20: M-CPU,
Bit21: M-CPU (redundant), Bit22-31: unused
/P: Reset after parameter change

N RZ SBD no [/P]
Reset for supplementary modules (SBD) Reset for base system elements (BSE)
SBD no: number for selection of SBD¦s (dec): 0-127:PE0-PE127, 128-135:, SBD0-SBD7
/P: Reset after parameter change

N K
Kill
The selected BSE assumes the "Halt" state. A restart can only be triggered by means of a
hardware reset or via the "Reset" command.

14-2 D30-500-1.05 TOOLBOX II Users Manual

 ST emulation

N KB BSE bit mask

Kill for base system elements
This command shuts the transferred base system elements down
BSE bit mask:see "Reset for base system elements"

N KZ
Kill for supplementary modules Go to supplementary module
This command shuts the transferred supplementary modules of a BSE down.
SBD no: see "Reset for supplementary modules"

N Q
Quit
The connection to the directly connected automation unit is terminated.

N G BSE name
Go to BSE (CPU)
This command is used to select a BSE. This means that subsequent commands such as DB, DA,
WB, WA, K, etc. will be related to this BSE.
BSEname: M: M-CPU, P: P-CPU, C0: C-CPU0, ... ,C19: C-CPU19
The prompt will change depending on the selected BSE

N GZ SBDno.
Go to supplementary module
SBDno: the number of the supplementary module
The prompt will change depending on the selected BSE

N WS segment
Write selector Kill for supplementary modules
Selects the following display, write, and monitor commands for a memory element.
Segment: the segment address (Hex)
The memory segment remains set for subsequent display, write, and monitor commands.

N DB byteno [, byteno2][/format] or DB[segment:]offset[-granularity quantity][/format]

This command indicates the current memory contents of one or several (up to FFFF) bytes
starting from a given address. The memory contents can be output in decimal, hex or binary
format.
Parameters:
Byteno: first byte address whose contents are to be shown (Hex)
Byteno2: last byte address whose contents are to be shown (Hex)
Segment: segment of the memory address starting from which readout is executed (Hex)
Offset: offset of the memory address starting from which readout is executed (Hex)
Granularity: unit for reading, B ... byte, W ... word (2 bytes), D ... doubleword (4 bytes)
Quantity: number of units read (dec)
Format: mode of representation of the memory contents, B ... bin_r, D ... decimal, H ... hex, F ...
float (only for doubleword), A ... ASCII
Note: segment, granularity, number and format remain set for subsequent display, write, and
monitor commands.

N DBX[segment:] offset [-granularity quantity] [/format]

Display byte for 32-bit CPU
This command indicates the current memory contents of one or several (up to FFFFFFFF) bytes
starting from a given address. The memory contents can be output in decimal, hex, binary, or
float format.
Parameter: see "Display byte"
Note: Segment, granularity, quantity, and format remain set for subsequent display, write, and
monitor commands.

TOOLBOX II Users Manual D30-500-1.05 14-3

 ST emulation

N DA wordno [,wordno2] [/format]

Display Address
This command indicates the current memory contents of one or several (up to FFFF) words (16
bits) starting from a given address. The memory contents can be output in decimal, hex or binary
format.
Wordno: First memory address whose contents are to be shown (hex)
Wordno2: Last memory address whose contents is to be shown (hex)
Format: mode of representation of the memory contents: B ... binary, D ... decimal, H ... hex, A ...
ASCII
Note: The mode of representation remains globally set for further outputs.

N DA wordno [,wordno2] [/format]

Display byte for 32-bit CPU
This command indicates the current memory contents of one or several (up to FFFF) words (16
bits) starting from a given address. The memory contents can be output in decimal, hex or binary
format.
Wordno: First memory address whose contents are to be shown (hex)
Wordno2: Last memory address whose contents is to be shown (hex)
Format: mode of representation of the memory contents: B ... binary, D ... decimal, H ... hex, A ...
ASCII
Note: The mode of representation remains globally set for further outputs.

N MB byteno [, byteno2] [/format] or MB[segment:] offset [-granularity quantity] [/format]

Monitor byte
The memory contents of one or several (up to 256) bytes are displayed continuously. Output
takes place in a modal dialog.
Parameters: see "Display byte"

N MA wordno [,wortno2] [/format]

Monitor Address
The memory contents of one or several (up to 256) words (16 bits) are displayed continuously.
Output takes place in a modal dialog.
Parameters: see "Display address"

N MBX[segment:] offset [- granularity quantity] [/format]

Monitoring byte for 32-bit CPU
The memory contents of one or several (up to 256) bytes are displayed continuously. Output
takes place in a modal dialog.
Parameters: see "Display byte for 32-bit CPU"

N WB [segment:] offset [-granularity] [/format], const1[,const2,...,const16]

Write Byte
This command overwrites the current memory contents of one or several (up to 16) bytes starting
from a given address
Parameters: see "Display byte"
Const1 ... const16: the new memory contents

N WA offset, const1 [,const2,...,const8]

Write Address
This command overwrites the current memory contents of one or several (up to 8) words (16 bits)
starting from a given address.
Parameters:
Offset: the address where a byte is to be overwritten (hex)
Const1 ... const8: the new memory contents (hex)

14-4 D30-500-1.05 TOOLBOX II Users Manual

 ST emulation

N WBX [segment:] offset [-granularity] [/format],const1 [,const2,...,const16]

Write byte for 32-bit CPU
This command overwrites the current memory contents of one or several (up to 16) bytes starting
from a given address.
Parameters: see "Display byte for 32-bit CPU"

N MACRO [file name]

Loading of macro file
This functionality allows you to transmit several commands (each command in a line) defined in a
macro file, one by one to the destination system. Every macro is available as ASCII file and can
therefore be created with any given editor.
Parameter:
File name: name of the macro file including path
Limitation: the macros are supported only if the directly connected automation unit is of the AK
1703 Type.

N SET
Display presets

N SYMBOL
Loading of file with symbolic addresses

N D#
Display Symbol

N W#
Write Symbol

N X monitor command
Transparent monitor mode for ASCII message formats
A command is sent directly to the component without any check of its syntax by the Online
Service window. This function is used to send commands to the component that are not
supported by the Online Service window. This command supports the following destination
systems: SK 1703, MK 1703,uK 1703, AM(E) 1703/VB locally or via SMI-bus

N XX FC, KC [,D0,D1,...,Dn]
Transparent monitor mode for IEC 870-5 message formats
A command is sent directly to the component without any check of its syntax by the Online
Service window. This function is used to send commands to the component that are not
supported by the Online Service window. This command supports the following destination
systems: AK 1703, AM(E) 1703/VB via telecontrol connection
Parameters:
FC: function code hexadecimal
KC: command code hexadecimal
D0...Dn: function-group-specific data hexadecimal (byte)
Reply:
The reply data are displayed in the following format: RC: AC [DATA:D0,D1,...,Dn]
AC: reply code hexadecimal, D0...Dn: reply data hexadecimal

N CLEAR
Deleting of list box contents
All entries are eliminated from the list box.

TOOLBOX II Users Manual D30-500-1.05 14-5

 ST emulation

N SAVE [file name]

Save list box contents
All entries from the list box are saved line by line in a file. This file can be edited with any given
editor.
Parameters:
File name: name of file in which the contents of the list box are saved.

N ICR
Deleting of interface status

N IDE
Displaying of interface status

Note:for safety reasons (data consistency), SPx commands are not implemented. Therefore, commands
PIN, PON, and PEX do not apply, either.

14-6 D30-500-1.05 TOOLBOX II Users Manual

 ST emulation

14.2. Handling

Tool start

SAT TOOLBOX II | ST-EMULATION

TOOLBOX II Users Manual D30-500-1.05 14-7

 Service function online

15. Service function online

15.1. Overview

In a SAT 1703 automation network, there is always one AU that is responsible for time synchronization
throughout all AU's of the network: the so-called Time Master. Usually, the time master also comes
equipped with a DCF77 time signal receiver.

The function described in this section allows you to read out the time from a locally connected AU. If this
AU is the time master and not equipped with a time signal receiver, the time can also be set by the SAT
TOOLBOX II. For this purpose, the automation units of the system

N SK 1703 / KSK 1703

are supported.

If the time in the Time Master is updated, the time in every other AU of the network will automatically be
updated via the communication paths (time-setting procedure)

Description

Setting of the time in a locally connected AU

N if no DCF77 receiver is available or no reception is possible

N For test purposes

Readout of the time from a locally connected automation unit is possible.

TOOLBOX II Users Manual D30-500-1.05 15-1

 Service function online

15.2. Handling

Tool start

SAT TOOLBOX II | ONLINE SERVICE FUNCTIONS

Displaying of time

TIME | DISPLAY | DIGITAL OR | ANALOG

Setting of time

TIME | SET

Entering of hours/ minutes/ seconds

15-2 D30-500-1.05 TOOLBOX II Users Manual

 Service function online

15.3. Load the display for BC 1703 Ax

The Online Service Functions allow you to load the display catalog for the BC1703 hardware module.

The following procedure:

N Start tool "Online Service Functions"

N Services -> Load BC1703 Display

N Select the display catalog to be loaded

Loading will be followed by a reset.

TOOLBOX II Users Manual D30-500-1.05 15-3

 Parameterization

16. Parameterization

16.1. Overview

The "Parameterization" function allows you to edit the parameters of automation units of the systems

N SK 1703 / KSK 1703 (with connected or built-in LM 1703)

N AK 1703

N AM 1703, AME 1703, and AMC 1703

These systems can be also parametrized with the OPM II. All other systems must be parametrized with
the OPM II

Editing of parameters comprises:

N parameter blocks (PB's) of system elements

N the DT-DFI Assignment valid for the entire plant

N Topology

N Detailed routing

Parameter setting in parallel windows

For every selected parameter block (PB), a PB window is opened in which the associated parameter
documentation form is opened for editing

Protection of parameters against competing access

Only such parameters of CPU system elements can be parameter-configured which no other tool/tool
set is accessing at the moment. ("Locking" for CPU granularity). For copying processes write-protected
parameters can be read in.

Functions available in the main window act on all selected AU's

N Services
DT/DFI Assignment (for entire plant), plaintext designation of every data Type (DT) to be used,
Assignment of a data format identifier (DFI) to every data Type used

N Parameter setting
Load enable: the parameters of all selected AU's are copied into a parameter spooler (temporary
memory) from where they are loaded into the AU('s) in the "background", e.g., during the
continuous loading process. The load enable for the AU's concerned is carried out automatically
upon exit from the main window.

TOOLBOX II Users Manual D30-500-1.05 16-1

 Parameterization

Functions available in the AU window act on one AU or on selected system elements (SE)

N Parameter setting
Parameter setting for system elements No SPx command input is required because of the
selection of the parameter setting command in the PD form, possibility of splitting the PD form,
zoom function, modifiable font size, search function, selectable numerical format (Hex, Dec, Bin,
Signed Integer), automatic or manual updating of the PD form after changes

N Load enable
The changed parameters of the respective AU are loaded if the function -> Load -> Continuous
has been activated. Lade enable for the specific AU is carried out automatically upon exit from
the AU window.

N Creating/deleting/displaying directory of customer parameters

Customer parameters can be created for: peripheral and protocol elements, of the selected
parameter blocks (PB) of a CPU system element

N Saving is carried out in a user-related manner as customer parameter unit with accompanying
text and name of the user who is creating them. Listing, deleting of customer parameter units only
by the authorized user. Application of customer parameters of another user only through
export/import

N Services
Parameter configuring of the topology: i.e. accessibility of the components defined in the system-
technical segment (Plant Management) graphics editing by means of toggle function

N Parameter-configuring of detailed routing

Representation in tabular form: all detailed routing records of a parameter block are shown at the
same time, the simultaneous editing of several lines is possible

N Editing functions user to edit detailed routing tables

N Parameter setting for detailed routing

Cutting out of lines/columns and copying them to the clipboard, deleting of lines and overwriting
them with default values, inserting of lines and writing default values or values from the clipboard
into them, adding of lines and writing values from the clipboard into them, writing values from the
clipboard in cells/ lines/ columns, writing of a certain value into columns, Overwriting of
consecutive cells of a column with values automatically incremented/decremented by a
specifiable distance, functions for find/ replace, one-step/multi-step sorting

16-2 D30-500-1.05 TOOLBOX II Users Manual

 Parameterization

16.2. Handling

Selection of the tool

SAT TOOLBOX II | PARAMETRIZATION

Assigning of DT/ DFI

SELECTING OF FUNCTION (MAIN WINDOW) | SERVICES | DT-DFI | EDIT

Entering of desired data Type plain text for the respective data Type
For changing the DFI Assignment, M-DClick-L on DFI plaintext field and select new DFI

Creating/Editing of detailed routing

N Selecting of AU

N Selecting of system element for detailed routing

N Selecting of detailed routing function

Services | Detailed Routing

N Selecting of detailed routing Type (not chronologically correct, chronologically correct data)

N Filling in/Editing of table with detailed routing records

Defining of topology

N Selecting of slot

N Selecting of function
Services | Topology

N All AU's defined in the Plant Management can be selected by M-Click-L on AU numbers

Defining of AU parameters

N AU selection

N Selecting of system element (for peripheral elements, direct entry into parameter form; for CPU
system elements, selection of the parameter block and then entry into the parameter setting form)

N Editing of the parameter form: -> M-DClick-L on parameter setting command (SPx) -> Change the
parameter value

N Selecting of chapter in PD form (STRG+spacebar or M-Click-R)

N Search option for text portions in the PD form (M-Click-R)

N Divide PD form onto 2 windows (M-Click-R)

TOOLBOX II Users Manual D30-500-1.05 16-3

 Parameterization

N Change numerical format (M-Click-R)

N Enlarge window

Create customer parameters

N M-DClick-L on desired AU

N Select slot

N Select function
Customer parameters | Create

N for CPU system elements: Select parameter block/blocks (virt. module) and confirm with -> OK or
All

N Specify name of customer parameter unit

N optional: enter accompanying text

16-4 D30-500-1.05 TOOLBOX II Users Manual

 Parameterization

16.3. Redundant operation of base system elements

For the redundant operation of base system elements within an AU or in different AU's, it is necessary
to copy the parameters of the redundant base system elements.

In this connection, it is important that identical parameters (=mirror parameters) be copied automatically
but that parameters that differ in the various BSE's will not be overwritten (e.g., communication settings)

The function "Copy Mirror Parameters" covers this requirement. In the master data of each base system
element suited for redundancy, it is defined for each parameter block whether this block is a mirror
parameter block or not.

When copying from BSE by using the function Copy Mirror Parameters, only the parameter blocks
defined as mirror parameters in the destination BSE will be overwritten.

Starting of the function Copy Mirror Parameters

TOOLBOX II | PARAMETER SETTING | OPEN AU WINDOW

Starting of the function Insert Mirror Parameters. Select destination BSE.

PARAMETER SETTING | INSERT MIRROR PARAMETERS

TOOLBOX II Users Manual D30-500-1.05 16-5

 Parameter Loader

17. Parameter Loader

17.1. Overview

The Parameter Loader supports the following functions:

17.1.1. Load Parameters

Parameters and task parameters (CAEx II and CAEx plus) are loaded from the TOOLBOX II to the SAT
1703 destination system. The following destination systems are supported:

TM 1703 ACP

BC 1703 ACP

AK 1703

AM 1703, AME 1703 and AMC 1703

SK 1703 / KSK 1703 (with connected or integrated LM 1703)

MK1703 is loaded by means of its own tool, the MK-VSR Loader. The call takes place via:

SAT TOOLBOX II | SERVICE PROGRAM | MK-LOADER

The following different functions are available for loading:

Intelligent loading
With this function, only the changed parameters are transferred to the destination system. As a result
short loading times can be achieved. This function can be used locally or remotely.
Note: This function is used for the loading of parameter changes.

Initializing
With this function all parameters in the destination system are deleted and all parameters transferred
new. This function can only be carried out with the locally connected AU.
Note: This function is used for the first initialization of an AU or BSE.

Absolute loading
With this function all parameters are transferred without fail every time. This function can be used locally
or remotely.
Note: This function is only used for test purposes.

N In the main window the parameters can be loaded for one or several AU's by marking the
corresponding lines. In the AU window, the loading operation for one or several BSE's can be
started.

TOOLBOX II Users Manual D30-500-1.05 17-1

 Parameter Loader

17.1.2. Parameter comparison

With the parameter comparison function it can be ascertained whether the parameter status in the
destination system is current. In the main window, this comparison can be performed for one or several
AU's by marking the corresponding lines. For each selected AU it is output whether this is current or not
current. In the AU window, this function can be performed for each BSE. Thereby for each BSE it is
output whether this is current or not current.

17-2 D30-500-1.05 TOOLBOX II Users Manual

 Parameter Loader

17.2. Handling

Information on Connection Setup

N If is carried out automatically when an AU is selected in the AU window

N It remains intact as long as a tool of the TOOLBOX is active

N It can be terminated manually or upon exit from the last active tool

Tool selection

SAT TOOLBOX II | LOAD PARAMETERS (AUTOMATIC)

Functions

N Loading process (initial initialization)

select desired AU (M-DClick-L) (and connect connection cable to desired AU)

N Start loading process

N Initializing (AU window)

N Local AU | ...the entire AU is loaded!

all other loading processes of the AU, which has already undergone initial initialization, can be carried
out with:
Load (AU window) | Load AU (load entire AU)
Load (AU window) | selected system elements
Intelligent loading ... changes only
Unconditional loading ... load everything

If loading of several selected AU's is to be carried out spontaneously

Load (main window) | selected AU's

If several AU's are to be kept continuously updated

Load (main window) | continuous
A prerequisite for this is that loading is enabled in the Parameter Setting Tool after a parameter change

Loading of CAEx tasks

SK/ KSK1703, MK1703: locally connected AU
AM/ AME1703: locally connected AU or Remote connection
Notes: In loading to the not directly connected AU (online remote) longer loading times may result from
limited transmission capacities. A parameter loading process will always be followed by an AU reset. SK
1703-VSRE tasks must be assigned in the HW/FW Configuration tool.

Parameter comparison of destination system and TOOLBOX for several selected AU's
Parameters (main window) | Comparison of AU's and TOOLBOX for a specific AU:
Parameters (AU window) | Comparison of AU and TOOLBOX

TOOLBOX II Users Manual D30-500-1.05 17-3

 Revision interrogation and display

18. Revision interrogation and display

18.1. Overview

The "Interrogate and Display Revisions" function allows you, in the systems

N TM 1703 ACP

N BC 1703 ACP

N AK 1703

N AM 1703, AME 1703, and AMC 1703

N SK 1703 / KSK 1703

to interrogate the firmware revision of all configured system elements (CPU system elements, peripheral
elements, SBD system elements) from the destination system, to enter and display the result in the SAT
TOOLBOX II (HW/FW configuration). Naturally, an already entered result can also be displayed in the
offline mode from the SAT TOOLBOX II

The revision interrogation comprises

N Systemelement: Designation of the system element

N HW#: HW Type of the module

N FW#: Firmware number

N Rev: Revision of the flashcode (read from destination system)

N TOOLBOX II - Update: Revision of the masterdata in TOOLBOX II. In brackets you can find the
last firmwarecode displayed, which is installed in the TOOLBOX II

N P: Prepared system element

N SSE: Supplimentary System Element

TOOLBOX II Users Manual D30-500-1.05 18-1

 Revision interrogation and display

N Task: Indication if a CAEx Task is equipped

N Supported system element:Supported in TOOLBOX II

18-2 D30-500-1.05 TOOLBOX II Users Manual

 Revision interrogation and display

18.2. Handling

Selection of the tool

SAT TOOLBOX II | "INTERROGATE AND DISPLAY REVISIONS"

TOOLBOX II Users Manual D30-500-1.05 18-3

 Topology test

19. Topology test

19.1. Overview

The Topology Test function is used for the acquisition of all AU's in a SAT 1703 automation network that
are currently reachable or not reachable from the physically connected automation unit. AU's of the
systems

N TM 1703 ACP

N BC 1703 ACP

N AK 1703

N AM 1703, AME 1703, and AMC 1703

N SK 1703 / KSK 1703

N MK 1703

N uK 1703

are supported. Only such AU's can be tested that are located in the same region as the physically
connected AU and defined in the system-technical segment (Plant Management)

Requirements

N In the Topology Parameter Setting, the components to be reached per interface must be defined
in every AU.

N Automation units are located in the same region as the locally connected AU and are defined in
the Plant Management (system-technical segment)

N Predefinable number of repetitions of topology tests in order to observe non-reproducable errors

over a longer period of time

TOOLBOX II Users Manual D30-500-1.05 19-1

 Topology test

19.2. Handling

Tool start

SAT TOOLBOX II | TOPOLOGY TEST

Functions

Setting of number of cycles

NUMBER OF CYCLES

Starting of the topology test

EXECUTE

19-2 D30-500-1.05 TOOLBOX II Users Manual

 Message simulation

20. Message simulation

20.1. Overview

The "Message Simulation" function allows you to send messages from the SAT TOOLBOX II to
automation units of the systems:

N TM 1703 ACP

N BC 1703 ACP

N AK 1703

N SK 1703 / KSK 1703, and

It is possible to send one message on its own or up to 100 message in immediate succession;
sequential delay and message retries can be defined

TOOLBOX II Users Manual D30-500-1.05 20-1

 Toolbox II presets

21. Toolbox II presets

21.1. Overview

This function is used to make the global presets, that is, the ones that are valid for all tools of the SAT
TOOLBOX II, and the user-specific definitions:

N Presets effective within SAT TOOLBOX II

N Presets for the communication with destination systems

N User/Role management

This function can be executed with the operating authority "unskilled user". Excepted therefrom is the
user/role management which can only be handled by a user having "administrator" authority and by the
"SuperUser"

Concept

Consideration of different tasks of TOOLBOX user that need to be solved

SAT TOOLBOX protects the engineering data by:

N Definition of roles with different rights

N Definition of users through names and passwords

N Assignment of each user to a defined role

Functions

Login via user name and password The user is given the rights corresponding to the role (user
authorization) assigned to him.

Logout User logout; You can continue to operate tools that are still active. The activation of tools
requires another Login. If all tools are quit without logging out, the user will remain logged in.

Predefined roles

User name Password Assigned role corresponds to

STANDARD STANDARD SAT_STANDARD "unskilled user"

PRO PRO SAT_PROFESSIONAL "skilled user"

ADMIN ADMIN SAT_ADMINISTRATOR "user with administrator

rights"

TOOLBOX II Users Manual D30-500-1.05 21-1

 Toolbox II presets

The definition of new users/ roles/ passwords includes the steps

N Creating a user with user name and password

N Creating a role tailored to the scope of actitivities of the user

N Assignment of authorizations to this role for the use of certain tools

N Assignment of user to role

The user/role management can be defined only by a user having "administrator" or "SuperUser" rights.

Changing or deleting can be done only by the "SuperUser"

User-specific presets

N Customer and plant

N Preset AU list
Selection of automation units that can be accessed rapidly in the further work with the TOOLBOX

Workplace-specific settings

N Presets to the destination system

N Language switchover
becomes active upon restart of the TOOLBOX

21-2 D30-500-1.05 TOOLBOX II Users Manual

 Toolbox II presets

21.2. Handling

Starting of the tool

SAT TOOLBOX II | PRESETS TOOLBOX II

The definition of the user/role management is carried out through

AUTHORIZATION | USER/ROLE MANAGEMENT

Note: This is possible only with "Administrator" or "SuperUser" rights

N Defining of user...

N New User | Enter | Close

N Authorization | User Role Management

N Defining of roles...

N New Role | Enter Role Name

N Select desired functions

N Assign functions

N Authorization...| User Role Management

N Assignment of user to role

Presets for customer/ plant and preset AU list

SYSTEM | PRESETS TOOLBOX

PRESETTING OF CUSTOMER/PLANT

SELECTING OF CUSTOMER AND SYSTEM-TECHN./ASSEMBLY-TECHN. PLANT

AU | ADD

-DCLICK-L ON DESIRED AU(S)

CLOSE

AUTHORIZATION...| USER ROLE MANAGEMENT

AU | PRESET AU(S)

AU's are selected. The preset is effective for all tools that are opened from this time on.

Presets for operating mode, baud rate, loader configuration are defined through

SYSTEM | PRESETS TOOLBOX

TOOLBOX II Users Manual D30-500-1.05 21-3

 Workgroups (Teamwork)

22. Workgroups (Teamwork)

22.1. Overview

Extensive projects with increasing complexity and expanding volumes of data compel to an ever greater
degree the realization of these projects in teams, since at the same time less and less operating time is
available for the engineering.
With the implementation of Client/Server technology and Windows Telnet Server in the network as well
as with the distribution of project data without network, the TOOLBOX II provides extensive possibilities
for the sharing of the engineering in a team.

The following possibilities are available:

Multi-User Mode

If TOOLBOX II PC's are linked over a network, then work can take place in Multi-User mode. The
following solutions are possible:

Client Server Operation

A central Server which is accessed by the Client TOOLBOX II PC's. On the Client PC's a complete
TOOLBOX II installation is necessary.
Advantage: Possible for all TOOLBOX II tools
Disadvantage: Sufficient bandwidth of the network must be available (depending on application, greater
than 512 kB)

web.engineering
A central Windows Server with Terminalserver installation. The Clients only work via Web browser. On
the Clients a TOOLBOX II installation is not needed.
Advantage: less bandwidth of the network is required (64 kB)
Disadvantage: CAEx II cannot be used in this solution, and must be operated with a local installation.

For the simultaneous processing of the data by several project managers, the following conditions are
applicable.

Process-engineering:
If a link image is processed by one user, then this image is blocked for all other users. If stored in the
OPM II, then this image can be processed again by all users.
Images can only be deleted if no other user is present in the same process-engineering plant.
If a change is carried out and saved by one user, then the view of all users in Multi-User mode can be
updated with the F5 key.

System-engineering:
If a basis system element is processed by one user, then this is blocked for all other users. By saving
the changes, the block is canceled again.

TOOLBOX II Users Manual D30-500-1.05 22-1

 Workgroups (Teamwork)

Shared working

With the functionality of the shared working it is possible to process a project distributed over several
TOOLBOX II PC's without network connection and bring it together again later. With the bringing
together of shared projects, with the transfer it can be decided which parts of the project are to be
transferred.

For the processing of the data not all possibilities are available. The limitations of the processing
possibilities are dependent on the status of the data stock (original, read-only status, copy).

Ranges can be processed distributed. If different ranges are processed by two users, then after
processing, these can be brought together again in a process-engineering plant. If shared working takes
place within a range, then there are limitations for the processing of the engineering data (e.g.: Types
can only be changed at one place). With the bringing together the following data can be transferred
selectively:

All data of an automation unit (peripheral parameters, CAEx II data, SIP message address conversion)

CAEx plus

SAT 250 SCALA (per CAE)

SAT 230 (per WLS)

In the system-engineering an automation unit can be distributed as a complete unit.

In the Data Distribution Center as well as a project being distributed (Export function) part-projects are
also brought together (Import function).

22-2 D30-500-1.05 TOOLBOX II Users Manual

 Workgroups (Teamwork)

22.2. Distributed working

22.2.1. Overview

22.2.1.1. System technique (Automation Units)

Since the automation units of several users can be processed distributed, it is necessary that the
TOOLBOX II manages a status for automation units . It is thereby differentiated between Original- and
Read Status. Based on this status, all permitted handlings for an automation unit are determined.

Original Status

Is the default status after the creation of an AU.

There are no limitations when processing.

Read Status

If an AU is exported in the Data Distribution Center as Backup, then this AU is given the status Read
Status.

What is possible in a Read Status:

N Initialization of an AU.

N Loading parameters of an AU.

N Loading Firmware of an AU.

What is not possible in a Read Status:

N All data can only be read, but not changed. This concerns parameters, detailed routings, CAEx II
Data, CAEx plus Data etc.

N Values for peripheral elements can be changed in the OPM II, but cannot be converted.

TOOLBOX II Users Manual D30-500-1.05 22-3

 Workgroups (Teamwork)

22.2.1.2. Process-Engineering Plant (VAN)

Since some data of a process-engineering plant can only then be changed if all ranges exist in the
original, it is necessary that the TOOLBOX II manages a status for the process-engineering plant. It is
thereby differentiated between Original- and Copy Status.

Original Status

A process-engineering plant only then has Original Status, if all ranges of this process-engineering plant
have Original Status.
There are no limitations when processing.

Copy Status

If one or several ranges of a process-engineering plant have the status Copy or Exported, then the
entire process-engineering plant automatically has the Status Copy.

What is not possible in a VAN Copy:

N Defining or changing levels.

N Defining or changing CAE and WLS Id.

N Defining or changing ranges.

N Defining free columns in the Assembly-Engineering Documentation.

N Changing CAEx plus Project Library. (is read only)

22.2.1.3. Ranges of a Process-Engineering Plant

22-4 D30-500-1.05 TOOLBOX II Users Manual

 Workgroups (Teamwork)

Since ranges of several users can be processed distributed it is necessary that the TOOLBOX II
manages a status for ranges. It is thereby differentiated between Original- and Copy Status. Based on
this status the permitted handlings for a range are determined.

Original Status

Is the default status after the creation of a range.

There are no limitations when processing. (except the limitations, that result as a result of a Copy Status
of the process-engineering plant).

Copy Status

If a range is exported in the Data Distribution Center as Copy, then this range is given the status Copy.

What is possible in a range Copy

N Changing values in new or existing images or default values.

N Converting all destination systems

N Assigning Infotypes for SAT 250 SCALA

N Creating new typeless and typical root images or root default values. (These are images or
defaults that do not have any higher-level nodes).

N Optionally process newly created root images (Formulae, References, DV ..).

What is not possible in a range Copy:

N Defining or changing Types.

N Defining or changing Infotypes and access groups.

N Changing Names of existing images or defaults.

N Changing structures of existing images or defaults. (deleting or inserting in parts of the image)

N Create new formulae.

N Assigning formulae and references to existing images or defaults.

N In the OPM II only 100 new signals can be created for the CAEx plus signal list.

Example:

Existing images may not be changed (regardless of whether these are typical or typeless). New images
must be root images (Image UW New in Copy)

TOOLBOX II Users Manual D30-500-1.05 22-5

 Workgroups (Teamwork)

Exported Status

If a range with the status Copy is deleted in the Data Distribution Center, then this range is given the
status Exported.

22-6 D30-500-1.05 TOOLBOX II Users Manual

 Workgroups (Teamwork)

22.2.2. Handling

22.2.2.1. Export of OPM Data (process-engineering)

Each range can be exported separately. Thereby each range can be exported as original or copy.

Export from an Original

DATA DISTRIBUTION CENTER | TAB EXPORT

If the range is an Original, then one has the option, whether a copy or the original is to be exported. If an
Original is exported, then in the TOOLBOX the status is set to copy for this range.

Export from a Copy

DATA DISTRIBUTION CENTER | TAB EXPORT

If values have been changed in a range-copy or new Images and Default values created, then this
range can be sent back as a copy, to transfer these into the Original. The status of this range in the
TOOLBOX remains unchanged. This Export record always contains all changes. The user can first
select during Import, which data are to be transferred.

It is not possible, to import changes in a copy.

22.2.2.2. Import of OPM Data (process-engineering)

Import in an Original

DATA DISTRIBUTION CENTER | TAB IMPORT

If a copy of an Original is read in, then the Data Distribution Center detects that there are changes in the
copy, and reads in only these changes. An information appears for the user, that these changes are
transferred into the original, and a request, whether he wishes to continue the operation. If this request
is answered with "No", then the import operation is aborted.
If there are no changes in the copy, then an information appears that no data are imported.

During import, the user can select which data are to be transferred. The selection is carried out by
means of Drag & Drop of sub-nodes of a range.

The following process-engineering data of a range can be imported selectively:

TOOLBOX II Users Manual D30-500-1.05 22-7

 Workgroups (Teamwork)

N All data of an automation unit

Parameters, CAEx II, SIP message address conversion.

N All data of a CAE (CAE-Id from SAT 250)

Parameters, assignment of Infotypes

N All data of a WLS (WLS-Id from SAT 230)

Parameters

N All values of Infotypes of an access group.

It is therefore important when creating the access groups to take the distributability into account.

N All newly created root images in the copy

N All data of CAEx plus

N All data of SAT in general (general address link)

}}-- }}--Import a copy into a copy

DATA DISTRIBUTION CENTER | TAB IMPORT

When importing a copy into a copy, in the destination all changes are overwritten and the copy is
accepted 1:1. Before the import a warning appears.

Import an original into a copy

DATA DISTRIBUTION CENTER | TAB IMPORT

When importing an original into a copy, in the destination all changes are overwritten and the original is
accepted 1:1. Before the import a warning appears.

22.2.2.3. Export of AU Data (system-engineering)

Export from an Original

DATA DISTRIBUTION CENTER | TAB EXPORT

If the AU is an original, then one has the option, whether a Read Status or Original is to be exported. If
an original is exported, then in the TOOLBOX the status is set to Read Status for this AU.

Export from a Read Status

DATA DISTRIBUTION CENTER | TAB EXPORT

If the AU is a Read Status, then only a Read Status can be exported. The Status of this AU in the
TOOLBOX remains unchanged.

22-8 D30-500-1.05 TOOLBOX II Users Manual

 Workgroups (Teamwork)

22.2.2.4. Import of AU Data (system-engineering)

Import of Read Status in an Original

DATA DISTRIBUTION CENTER | TAB IMPORT

It is not possible to import an AU with the status Read Status by means of an AU with the status
Original.

Import of Original in a Read Status

DATA DISTRIBUTION CENTER | TAB IMPORT

When importing an AU with the status Original to an AU with the status Read Status, in the destination
all data are deleted and the Original Status of the imported AU are accepted. Before the import
operation a warning appears.

TOOLBOX II Users Manual D30-500-1.05 22-9

 Workgroups (Teamwork)

22.2.3. Examples

22.2.3.1. One Range, 2 Users working with SAT 1703 and SAT 200

The project is to be processed by 2 users at separate localities. The one user is to process the
SAT1703-Data, the other the SAT200-Data, whereby all OPM-Data (SAT1703 and SAT200) have been
defined in one range.

Example:

A project engineer sits in Vienna and processes the SAT1703-Data, the other project engineer is
however in China and processes the SAT200-Data.

User 1 receives by means of Export a copy of the range as well as both 1703-AUs as originals. The AU-
Original would not be absolutely necessary, since the user could also change values without the
original. The user however may wish to convert and for this he needs the original.

User 2 also receives by means of Export a copy of the range.

After receiving the ranges, now each of the two users has one copy of the range. User 1 now processes
the SAT1703-Data and User 2 processes the SAT200-Data. When they have finished, they then send
the changed values (the one the SAT200-Data, the other the SAT1703-Data) back to the master by
means of the Data Distribution Center.

Note:

Each of the 2 users can manipulate the data of the other in his copy. The TOOLBOX II does not prevent
the SAT2xx-User from also exporting the SAT1703-Data and sending them back to the master.

In order to solve this problem, during Import an option of which data are to be accepted appears
(Automation Unit, SAT 250 SCALA CAE, SAT 230 WLS ..).

22-10 D30-500-1.05 TOOLBOX II Users Manual

 Workgroups (Teamwork)

22.2.3.2. One Range, 2 Users working on different AU's

The project is to be processed by 2 users at separate localities. The one project engineer is to process
the data of AU 1, the other the data of AU 2, whereby the OPM-Data for these AUs have been defined
in one range.

Example:

Both AUs are located at two separate localities (In a tunnel e.g. the Cavern 1 and Cavern 2). For
commissioning, both project engineers must be able to process the respective data of the AU for which
they are responsible.

User 1 receives by means of Export a copy of the range as well as the original of the AU 1 as original.
The AU-Original would not be absolutely necessary, since the user would also be able to change values
without the original. The user however may wish to convert or load and for this he needs the original.

User 2 receives by means of Export a copy of the range as well as the original of the AU 2 as original.
The AU-Original would not be absolutely necessary, since the user would also be able to change values
without the original. The user however may wish to convert or load and for this he needs the original.

After receiving the ranges, now each of the two users has one copy of the range. User 1 now processes
the data for AU 1 and User 2 processes the data for AU 2. When they have finished, they then send the
changed values (the one the data of AU 1, the other the data of AU 2) back to the master in a copy by
means of the Data Distribution Center .

Note:

Each of the 2 users can manipulate the data of the other in his copy. The TOOLBOX II does not prevent
the SAT2xx-User from also exporting the SAT1703-Data and sending them back to the master.

In order to solve this problem, during Import an option of which data are to be accepted appears
(Automation Unit, SAT 250 SCALA CAE, SAT 230 WLS ..).

TOOLBOX II Users Manual D30-500-1.05 22-11

 Workgroups (Teamwork)

22.2.3.3. 2 Ranges with higher-level SAT 200

The project is to be processed by 2 users at separate localities in two different ranges. The one user is
to process the data in Range 1, the other the data in Range 2. In Range 1 there is a particular number
of 1703-AU’s and CAEs.
In Range 2 there is also a particular number of 1703-AU’s and CAEs. In addition there is a CAE (CAE 0)
to which OPM-Data of both ranges refer.

Example:

The plant consists of two voltage levels: 20kV and 110kV.

One project engineer sits in Vienna and processes the 110kV-Data. the other project engineer is
however located in China and processes the 20kV-Data.
User 1 receives by means of Export a copy of Range 1 and Range 2.
User 2 also receives by means of Export a copy of Range 1 and Range 2.

After the export from both users, the following state exists:

User 1 and User 2 now process the AUs in their respective range, or the common CAE and then send
the changed values back to the master in a copy by means of the Data Distribution Center.

22-12 D30-500-1.05 TOOLBOX II Users Manual

 Workgroups (Teamwork)

22.2.3.4. Creating New Images in a Range Copy

A project engineer who does not have a Range -Original, definitely needs several newly created images
(regardless of whether typical or typeless).

There are two possibilities of the project engineer obtaining the new images:

Solution 1

The project engineer send his currently executed changes back to the master, and then lets the master
create the new images in his Range-original and then again receives a copy from him which he then
coordinates. He then changes the values and sends the changed values back to the master in a copy
by means of the Data Distribution Center or by means of Source Data Management, which then imports
these by means of the Data Distribution Center or Source Data Management.

Solution 2

The user, per definition, may create new root images in his Range-copy (he must only not change any
existing structures). The user simply creates the new images and then manipulates the values.

To be able to send the newly created images back to the master, he sends a copy of the range back to
the master.

During Import, the Data Distribution Center detects that there are newly created images in the Export-
record and reads these in.

Solution 3

The project engineer sends his currently executed changes back to the master and then receives from
the master his Range-Original, in order to be able to create the new images. After completing all work,
he sends the range-original back to the master. This solution can also be used to create new types.

TOOLBOX II Users Manual D30-500-1.05 22-13

 Workgroups (Teamwork)

22.2.3.5. Function Diagrams in CAEx plus

Function diagrams can be processed in an AU Original. A direct exchange of data for function diagrams
or parts of function diagrams is not possible. The smallest unit for the exchange of data is an AU.
If function diagrams are to be exchanged between different VAN's or customers, then in this case a
temporary AU must be created. In this AU, optional function diagrams can be created and by means of
the function Copy AU, transferred to another customer or a process-engineering plant. The function
diagrams from this temporary AU can be copied to the appropriate libraries.

22-14 D30-500-1.05 TOOLBOX II Users Manual

 Parameter documentation

23. Parameter documentation

23.1. General parameters

23.1.1. Lk_Prep

Link address - Prepared

With this parameter a link image can be set to ready. Ready link images can be optionally suppressed
in the OPM (Suppress link images). By setting a link image to Ready, it is dealt with as follows in the
conversion process.

N SAT 250 Ax + SK Mode or SCADA Applications

The PVs which have already been transmitted in the CAE are deleted from the data store of the
CAE in the next conversion process. Newly created ready PVs are not transmitted to the CAE.
Note: If a link image is set to Ready then the CAE ID of images which have already been
converted can be changed. This only takes effect when loading this change into both CAEs (old
entry before the change, new entry after the change).

N SAT 1703 ACP and SAT 1703 Ax(IEC) or SAT 1703/Ax

Data points which have already been converted are deleted on the peripheral element after the
next conversion process. For this, the total peripheral element is initialized with default
parameters and all data points of this peripheral element are transmitted to the peripheral
element in the next conversion by the OPM.

N CAEx plus /ACP

Already converted links are not deleted from the signal list. Newly created links are not generated
in the signal list.

N CAEx II /Ax - Mode

The EAM file is always completely recreated and contains no ready links. Already converted links
are not deleted from the allocation. Newly created links are not allocated.

N SAT 230 Ax Mode

Already generated PVs are marked as deleted in the PVL file in the next conversion process.
Newly created, ready PVs are not generated in the PVL file.

N SAT Message Address Conversion

Already converted, fine-routing records are deleted from the parameter block in the next
conversion. Newly created, fine routing records are not transmitted in the conversion

N SAT General
No function

TOOLBOX II Users Manual D30-500-1.05 23-1