Delphin Help

Delphin Manual
2003-2014 Delphin Technology AG
1
Delphin Online Hilfe

May 2011
Table of contents
Version history
ProfiSignal...........................................................................................
CD 4.1.1
2
ProfiSignal...........................................................................................
CD 4.1.0
3
ProfiSignal...........................................................................................
CD 4.0.3
5
ProfiSignal...........................................................................................
CD 4.0.2
8
ProfiSignal...........................................................................................
CD 4.0.1
9
ProfiSignal
...........................................................................................
CD 4.0.0
12
ProfiSignal
...........................................................................................
CD 3.2.5
15
ProfiSignal
...........................................................................................
CD 3.2.4
17
ProfiSignal
...........................................................................................
CD 3.2.3
18
10
ProfiSignal
...........................................................................................
CD 3.2.2
20
11
ProfiSignal
...........................................................................................
CD 3.2.1
22
12
ProfiSignal
...........................................................................................
CD 3.2.0
23
13
ProfiSignal
...........................................................................................
CD 3.1.7
27
14
ProfiSignal
...........................................................................................
CD 3.1.6
28
15
ProfiSignal
...........................................................................................
CD 3.1.5
31
16
ProfiSignal
...........................................................................................
CD 3.1.4
34
17
ProfiSignal
...........................................................................................
CD 3.1.3
36
18
ProfiSignal
...........................................................................................
CD 3.1.2
38
19
ProfiSignal
...........................................................................................
CD 3.1.1
41
20
ProfiSignal
...........................................................................................
CD 3.1.0
43
21
ProfiSignal
...........................................................................................
CD 3.0
46
22
To ProfiSignal
...........................................................................................
CD 2.2
58
ProfiSignal software
70
Installation
........................................................................................... 72
Introduction
........................................................................................... 75

May 2011
I
System requirements
..................................................................................... 77
Recommendations
.....................................................................................
for continuous operation
79
Multi-user mode
..................................................................................... 82
Safety Advice
..................................................................................... 84
Product information
..................................................................................... 85
Password protected
..................................................................................... 87
User..............................................................................................
login
87
Changing
..............................................................................................
passwords
90
Settings
..............................................................................................
for password protection
91
Windows
..............................................................................................
key combinations
93
User..............................................................................................
Rights
95
Licensing
..................................................................................... 98
Activate
..............................................................................................
and extend licence
102
Change
..............................................................................................
and deactivate licence
108
DataService
...........................................................................................
Configurator
110
DataService.....................................................................................
as a Windows service
112
Main menu ..................................................................................... 115
Connect
.............................................................................................. 115
Login
.............................................................................................. 120
View
.............................................................................................. 123
Options
.............................................................................................. 130
Help
.............................................................................................. 131
Connections
.....................................................................................
option
132
Main
..............................................................................................
settings
136
Connection
..............................................................................................
settings
144
TopMessage
..............................................................................................
connection
145
Log-/ProfiMessage
..............................................................................................
connection
150
Software
..............................................................................................
channels
153
DataService
..............................................................................................
connection
154
OPC
..............................................................................................
Client
158
Modbus-Client
.............................................................................................. 161
Firm
..............................................................................................
ware Update
163
Channels option
..................................................................................... 167
TopMessage
..............................................................................................
device configuration
169
Creating
..............................................................................................
software channels
172
Creating
..............................................................................................
variables
173
Calculation
..............................................................................................
channel
176
..............................................................................................
Formula functions
179
..............................................................................................
Load formula
182
II

May 2011
..............................................................................................
Save formula
183
Average
..............................................................................................
channel
184
Statistic
..............................................................................................
channel
186
Counter
..............................................................................................
channel
189
Creating
..............................................................................................
test channels
192
..............................................................................................
Parametrising signals
198
..............................................................................................
Modulating signals
200
..............................................................................................
Modulated frequency
201
..............................................................................................
Modulated amplitude
203
..............................................................................................
Modulated offset
204
..............................................................................................
Fourier series development
206
Advanced
..............................................................................................
settings
211
Form
..............................................................................................
ula editor
212
OPC
..............................................................................................
channel configuration
214
Configuring
..............................................................................................
Modbus channels
224
Dialogue functions/
.....................................................................................
General
237
Database option
..................................................................................... 241
Adding
..............................................................................................
a measurement database
243
Storing
..............................................................................................
channels to databases
250
Alarm manager
..................................................................................... 252
Alerting
..............................................................................................
settings
253
EMail
..............................................................................................
server set-up
259
Fax
..............................................................................................
server set-up
261
Actions
.............................................................................................. 261
Notification
..............................................................................................
set up
267
Storage
..............................................................................................
set up
270
Alarm
..............................................................................................
class settings
273
Alarm
..............................................................................................
rule settings
275
Scheduler option
..................................................................................... 282
General
..............................................................................................
settings
284
Mem
..............................................................................................
ory read-out
289
DB ..............................................................................................
backup
295
User management
..................................................................................... 296
Password
..............................................................................................
protection settings
296
Add..............................................................................................
groups
300
Add..............................................................................................
users
302
Lock
..............................................................................................
user
306
ProfiSignal
........................................................................................... 307
User interface
..................................................................................... 309

May 2011
III
Main
..............................................................................................
menu
310
File
.............................................................................................. 310
Search
.............................................................................................. 312
View
.............................................................................................. 313
Protection
.............................................................................................. 313
Settings
.............................................................................................. 314
..............................................................................................
Global settings
314
..............................................................................................
General tab
316
..............................................................................................
Timezone tab
318
..............................................................................................
Project options
318
..............................................................................................
VisuView tab
320
..............................................................................................
ParameterView tab
321
..............................................................................................
ModuleView tab
323
..............................................................................................
Script editor
325
..............................................................................................
ASCII Export tab
328
Window
.............................................................................................. 328
Help
.............................................................................................. 330
Toolbar
.............................................................................................. 331
Managem
..............................................................................................
ent tree
332
Project
..............................................................................................
context menu
334
Applications
..............................................................................................
context menu
337
VisuView
..............................................................................................
context menu
341
Param
..............................................................................................
eterView context menu
343
ModuleView
..............................................................................................
context menu
344
Report
..............................................................................................
context menu
347
Channels
..............................................................................................
context menu
348
Form
..............................................................................................
ulary context menu
348
Calculation
..............................................................................................
Channels context menu
349
Log..............................................................................................
window
349
Window
..............................................................................................
management
350
Tim..............................................................................................
e synchronization
351
Projects and
.....................................................................................
applications
353
Runtim
..............................................................................................
e and edit mode
353
Visualisation
.............................................................................................. 354
VisuView
..............................................................................................
properties
356
Multiple
..............................................................................................
VisuViews
360
VisuView
..............................................................................................
context menu
362
Visualisation
..............................................................................................
object context menu
363
Visualisation
..............................................................................................
objects overview
366
IV

May 2011
..............................................................................................
Script instructions
369
..............................................................................................
Visualisation object settings
378
..............................................................................................
General settings
379
..............................................................................................
Style
380
..............................................................................................
Protection
382
..............................................................................................
Event
383
..............................................................................................
References
386
..............................................................................................
Channel and tab order
387
Digital
..............................................................................................
meter
390
Round
..............................................................................................
analog meter
398
Lineal
..............................................................................................
analog meter
406
Bar
.............................................................................................. 416
Tank
.............................................................................................. 424
LED
.............................................................................................. 432
Signal
..............................................................................................
light
437
Rotary
..............................................................................................
knob
441
Slider
.............................................................................................. 451
Toggle
..............................................................................................
switch
459
Slide
..............................................................................................
switch
463
Button
.............................................................................................. 468
..............................................................................................
Button
468
..............................................................................................
Report Button
474
..............................................................................................
Project button
478
..............................................................................................
Application button
481
..............................................................................................
Exit button
484
..............................................................................................
Login button
487
Text
..............................................................................................
edit
491
Check
..............................................................................................
box
498
Radiobutton
.............................................................................................. 502
Drop
..............................................................................................
down and Channel drop down
509
..............................................................................................
Drop down
510
..............................................................................................
Channel drop down
517
Label
.............................................................................................. 523
Picture
.............................................................................................. 530
Table
.............................................................................................. 536
..............................................................................................
Standard configuration of tables
543
Tim
..............................................................................................
er
547
Date/Tim
..............................................................................................
e
548
Stop
..............................................................................................
watch
552

May 2011
V
..............................................................................................
Digital clock
553
..............................................................................................
Analog clock
558
..............................................................................................
Stop clock
561
Trend
.............................................................................................. 566
..............................................................................................
Trend settings
570
..............................................................................................
Trend colors
575
..............................................................................................
Using the trend chart
576
..............................................................................................
Channel table context menu
580
..............................................................................................
Graph toolbox
582
..............................................................................................
Script language
586
..............................................................................................
Yt-diagram
587
..............................................................................................
Yt-diagram settings dialog
589
..............................................................................................
Graph area functions
590
..............................................................................................
Graph toolbox
597
..............................................................................................
Logic diagram
600
..............................................................................................
Oscilloscope diagram
601
..............................................................................................
Oscilloscope diagram settings
602
..............................................................................................
Using the oscilloscope diagram
603
..............................................................................................
YX-diagram (table)
604
..............................................................................................
YX-diagram (table) settings dialog
606
..............................................................................................
YX-diagram (hardware channels)
608
..............................................................................................
YX-diagram settings dialog
610
..............................................................................................
Operating a YX diagram
611
..............................................................................................
YX-diagram color
612
..............................................................................................
FFT diagram
612
..............................................................................................
Orbit diagram
613
..............................................................................................
Orbit diagram settings dialog
615
Recorder
.............................................................................................. 616
..............................................................................................
Recorder properties
616
..............................................................................................
Using a recorder
630
..............................................................................................
Script language
632
..............................................................................................
Post time synchronization
635
Profile
.............................................................................................. 639
..............................................................................................
Profile settings
643
..............................................................................................
Table editor
648
..............................................................................................
Standard configuration
650
..............................................................................................
Profile runtime mode
652
..............................................................................................
Operating a profile
653
YX-table
.............................................................................................. 656
VI

May 2011
Turntable
.............................................................................................. 662
Alarm
..............................................................................................
list
668
..............................................................................................
View tab
675
..............................................................................................
Alarms tab
678
..............................................................................................
Analysis tab
680
..............................................................................................
Toolbar tab
684
..............................................................................................
Fault diagnostics
685
..............................................................................................
Acquisition of fault data
687
ODBC
..............................................................................................
visualisation object
688
..............................................................................................
ODBC connection
690
..............................................................................................
ODBC table
694
..............................................................................................
ODBC SQL
698
Param
..............................................................................................
eterView
702
Param
..............................................................................................
eterView context menu
704
Page
..............................................................................................
settings
705
Script
..............................................................................................
instructions
708
Param
..............................................................................................
eterView settings
710
..............................................................................................
Validation check
714
Overview
..............................................................................................
of parameter objects
717
..............................................................................................
Parameter object context menu
718
..............................................................................................
Button parameter object
721
..............................................................................................
Text edit parameter object
721
..............................................................................................
Check box parameter object
722
..............................................................................................
Radio button parameter object
723
..............................................................................................
Channel / dropdown box parameter object
723
..............................................................................................
Channel box parameter object
724
..............................................................................................
Label parameter object
725
..............................................................................................
Table parameter object
725
..............................................................................................
Date/Time parameter object
726
..............................................................................................
Profile parameter object
726
Report
..............................................................................................
Designer
728
Create
..............................................................................................
report
730
..............................................................................................
Report layout window
731
..............................................................................................
Generate report in runtime
736
..............................................................................................
Subreport
738
Overview
..............................................................................................
of report objects
740
..............................................................................................
Report objects - General Information
741
..............................................................................................
Adding a report object
741
..............................................................................................
Context menus for report objects
742

May 2011
VII
..............................................................................................
General settings
744
..............................................................................................
Frame and Group report objects
746
..............................................................................................
Label report object
749
..............................................................................................
Number band report object
752
..............................................................................................
Table report object
758
..............................................................................................
Page count / page number report object
763
..............................................................................................
Date / time / report filename report object
765
..............................................................................................
Picture report object
767
..............................................................................................
Alarm table report object
770
..............................................................................................
Creating an alarm table
775
..............................................................................................
Graph report object
777
..............................................................................................
Example of a graph/diagram
782
ModuleView
.............................................................................................. 784
Processing
..............................................................................................
tab
790
Events
..............................................................................................
tab
793
Subm
..............................................................................................
odule tab
798
Module
..............................................................................................
types
799
Channels/Variables
.............................................................................................. 813
Channels
.............................................................................................. 814
Application
..............................................................................................
variables
817
application
..............................................................................................
lists
821
application
..............................................................................................
fields
822
Application
..............................................................................................
arrays (3D)
823
Synchronization
..............................................................................................
variables
824
Form
..............................................................................................
ulary
824
..............................................................................................
Adding a formula to the formulary
834
Calculation
..............................................................................................
channels
842
..............................................................................................
Adding a calculation channel
843
Adapter
..............................................................................................
channels
846
The Klicks programming
.....................................................................................
language
849
Question
.............................................................................................. 860
Context
..............................................................................................
sensitive search
863
Search
..............................................................................................
dialogue
867
Context
..............................................................................................
menus
871
Variables
.............................................................................................. 883
Form
..............................................................................................
ula
888
Create
..............................................................................................
new variable (to the right)
890
Create
..............................................................................................
new variable (to the left)
891
Delete
..............................................................................................
Variable
892
VIII

May 2011
Add
..............................................................................................
brackets
892
Delete
..............................................................................................
brackets
892
Add
..............................................................................................
negation
893
Create
..............................................................................................
new variable (to the left of the bracket)
893
Create
..............................................................................................
new variable (to the right of the bracket)
894
More
..............................................................................................
operations
895
Assign
.............................................................................................. 900
Data
..............................................................................................
type
901
Form
..............................................................................................
at
906
String
.............................................................................................. 908
Data
..............................................................................................
flow
911
Control
.............................................................................................. 912
Initiate
.............................................................................................. 918
Visualization
.............................................................................................. 919
..............................................................................................
VisuView
920
..............................................................................................
Open VisuView in foreground (obsolete)
921
..............................................................................................
Dropdown box
922
..............................................................................................
Function obsolete
924
..............................................................................................
Table/YX-table
926
..............................................................................................
Function obsolete
930
..............................................................................................
Stop watch
932
..............................................................................................
Trends and Recorders
934
..............................................................................................
Functions for channel selection
936
..............................................................................................
Functions for configuration
938
..............................................................................................
Functions to display data
948
..............................................................................................
Functions for exporting
954
..............................................................................................
Functions for markers
958
..............................................................................................
Other functions
966
..............................................................................................
Recorder functions
966
..............................................................................................
Function obsolete
969
..............................................................................................
Profile
985
..............................................................................................
Alarm list
986
..............................................................................................
Function obsolete
989
..............................................................................................
ODBC
991
Param
..............................................................................................
eter input
996
..............................................................................................
Report
1000
..............................................................................................
Functions for report files
1001
..............................................................................................
Functions for generating reports
1003
..............................................................................................
Functions for report objects
1005

May 2011
IX
..............................................................................................
Functions obsolete
1006
..............................................................................................
Channel
1006
..............................................................................................
Application
1012
..............................................................................................
File
1018
..............................................................................................
Window
1024
..............................................................................................
DateTime
1025
..............................................................................................
Processing messfile (HDS)
1030
..............................................................................................
Configuration
1048
..............................................................................................
Directory
1065
..............................................................................................
ProfiSignal
1067
..............................................................................................
Project
1072
..............................................................................................
Calculation channels
1076
Configuration
.............................................................................................. 1077
Shortcut
..............................................................................................
lists
1089
Analysis ..................................................................................... 1091
Online
..............................................................................................
analysis
1092
..............................................................................................
Adding an online analysis
1093
..............................................................................................
Opening an online analysis
1095
..............................................................................................
Online analysis window
1096
..............................................................................................
Online analysis main menu
1097
..............................................................................................
Diagram settings dialog
1099
..............................................................................................
Recorder, online analysis
1101
..............................................................................................
Recorder settings
1103
..............................................................................................
Available diagram types
1114
Opening
..............................................................................................
measurement data file for analysis
1115
..............................................................................................
Measurement data preview
1116
..............................................................................................
Diagram type selection
1117
..............................................................................................
Analysis window
1119
..............................................................................................
Available diagram types
1120
Graphical
..............................................................................................
diagrams
1120
..............................................................................................
Diagram layout
1121
..............................................................................................
Taskbar functions
1122
..............................................................................................
General functions for the channel table
1122
..............................................................................................
Y-axis settings
1126
..............................................................................................
X-axis settings
1129
..............................................................................................
Sorting the channel table
1130
..............................................................................................
General functions for the graph area
1132
..............................................................................................
Graph toolbox functions
1136
..............................................................................................
Channel settings dialog
1141
X

May 2011
..............................................................................................
Diagram settings dialog
1143
..............................................................................................
Yt-diagram
1146
..............................................................................................
Channel table functions
1148
..............................................................................................
Functions for the graph area
1149
..............................................................................................
Graph toolbox
1156
..............................................................................................
Configure time axis
1160
..............................................................................................
Mouse cursor lines
1160
..............................................................................................
Settings dialog
1162
..............................................................................................
Logic diagram
1163
..............................................................................................
1164
..............................................................................................
Graph area
1166
..............................................................................................
Settings dialog
1167
..............................................................................................
1168
..............................................................................................
1168
..............................................................................................
1170
..............................................................................................
Graph toolbox
1170
..............................................................................................
Extended graph toolbox
1172
..............................................................................................
Configure time axis
1173
..............................................................................................
Settings dialog
1174
..............................................................................................
YX-diagram (hardware)
1175
..............................................................................................
Characteristic curve table, channel table
1177
..............................................................................................
Characteristic curve table
1178
..............................................................................................
Channel table
1183
..............................................................................................
Add characteristic curve
1185
..............................................................................................
1188
..............................................................................................
Graph toolbox
1191
..............................................................................................
1192
..............................................................................................
Settings dialog
1193
..............................................................................................
YX-diagram (color)
1194
..............................................................................................
FFT diagram
1195
..............................................................................................
1196
..............................................................................................
1198
..............................................................................................
Graph toolbox
1202
..............................................................................................
Order analysis portrayal
1204
..............................................................................................
1206
..............................................................................................
Status bar
1209
..............................................................................................
Settings dialog
1210
..............................................................................................
Orbit diagram
1211
..............................................................................................
Characteristic curve table, channel table
1212

May 2011
XI
..............................................................................................
1214
..............................................................................................
Graph toolbox
1216
..............................................................................................
1217
..............................................................................................
Settings dialog
1218
Analysis
..............................................................................................
functions
1218
..............................................................................................
Markers
1219
..............................................................................................
Add marker
1219
..............................................................................................
Marker layout
1221
..............................................................................................
Protection
1225
..............................................................................................
Marker overview
1227
..............................................................................................
Edit marker
1229
..............................................................................................
Text field
1230
..............................................................................................
Add a text field
1231
..............................................................................................
Text field layout
1233
..............................................................................................
Text field overview
1236
..............................................................................................
Edit text field
1237
..............................................................................................
Add line
1240
..............................................................................................
Examples of text fields in a diagram
1242
..............................................................................................
Print diagram
1242
..............................................................................................
Examples of a printed diagram
1246
..............................................................................................
Statistics
1250
..............................................................................................
Offline calculation channels
1254
..............................................................................................
Formulary
1257
Export
..............................................................................................
options for a trend
1258
..............................................................................................
Export ASCII file
1264
..............................................................................................
ASCII export settings
1268
..............................................................................................
Escape sequences
1273
..............................................................................................
Example of EMF exports
1273
File
..............................................................................................
factory
1276
..............................................................................................
File factory dialog
1278
..............................................................................................
Measurement file table
1281
..............................................................................................
Yt-diagram
1284
..............................................................................................
Concatenating measurement data files
1285
..............................................................................................
Concatenation examples
1286
..............................................................................................
Creating a relative file
1287
..............................................................................................
Relative file example
1289
Showing
..............................................................................................
a database in a trend
1291
Device
..............................................................................................
memory readout
1293
Saving
..............................................................................................
measurement data
1298
XII

May 2011
Global
..............................................................................................
alarm lists
1299
Report viewing
..................................................................................... 1301
Edit
..............................................................................................
report
1305
Im..............................................................................................
port report
1306
New
..............................................................................................
layout
1306
Layout
..............................................................................................
information
1308
Report
..............................................................................................
preview
1310
Appendix
........................................................................................... 1314
Software tools
..................................................................................... 1315
DataBase
..............................................................................................
check
1315
Convert2HDB
.............................................................................................. 1316
DelphinSupport
..............................................................................................
data
1317
Tables
..................................................................................... 1318
Measurem
..............................................................................................
ent data status
1318
Expert Key
1
1319
Different
...........................................................................................
devices
1320
Constructions
..................................................................................... 1321
Types
..................................................................................... 1324
First steps
........................................................................................... 1325
System requirements
..................................................................................... 1326
Software installation
..................................................................................... 1327
Power supply
.....................................................................................
/ Switching device on
1329
Connecting
..................................................................................... 1330
Construction
...........................................................................................
L
1335
Safety advice
..................................................................................... 1336
Displays /.....................................................................................
LEDs
1337
Connections
..................................................................................... 1338
Connection
.....................................................................................
schematic
1339
Construction
...........................................................................................
C
1341
Safety advice
..................................................................................... 1342
Displays /.....................................................................................
LEDs
1343
Connections
..................................................................................... 1344
Connection
.....................................................................................
schematic
1345
Construction
...........................................................................................
P
1347
Safety advice
..................................................................................... 1348
Connection
.....................................................................................
schematic
1349

May 2011
XIII
Construction
...........................................................................................
T
1351
Safety advice
..................................................................................... 1352
Connection
.....................................................................................
schematic
1353
Function
...........................................................................................
and Operation
1354
Dialogue option
.....................................................................................
/ General
1356
Device
..................................................................................... 1360
Analog input
..................................................................................... 1363
Dialogue
..............................................................................................
option / Voltage sensor type
1364
Dialogue
..............................................................................................
option / Current sensor type
1366
Dialogue
..............................................................................................
option / Resistor senor type
1370
Dialogue
..............................................................................................
option / Thermocouple sensor type
1372
Dialogue
..............................................................................................
option / RTD sensor type
1374
Sam
..............................................................................................
ple rates and measurement accuracy
1375
Digital input
.....................................................................................
with counter function
1377
Dialogue
..............................................................................................
option / Level detector
1378
Dialogue
..............................................................................................
option / Counter
1379
Dialogue
..............................................................................................
option / Frequency measurement
1381
Analog output
..................................................................................... 1383
Dialogue
..............................................................................................
option
1384
Digital output
..................................................................................... 1387
Dialogue
..............................................................................................
option
1388
Digital output
.....................................................................................
with PWM function
1390
Dialogue
..............................................................................................
option
1392
Device settings
.....................................................................................
save and load
1395
Configuration
.....................................................................................
reset
1397
Device information
..................................................................................... 1398
Device firmware
..................................................................................... 1400
Connection
...........................................................................................
information
1401
Connecting
.....................................................................................
sensors
1401
Connecting
.....................................................................................
actuators
1406
Measurement
...........................................................................................
technology
1409
Galvanic isolation
..................................................................................... 1409
Grounding..................................................................................... 1410
Ground Loop
..................................................................................... 1413
Shielding ..................................................................................... 1414
ESD-Protection
..................................................................................... 1416
Potential differences
..................................................................................... 1417
10
Device...........................................................................................
synchronization
1418
XIV

May 2011
11
Technical
...........................................................................................
specifications
1421
Analog input
..................................................................................... 1422
Digital input
.....................................................................................
with counter function up to 1 MHz
1427
Digital input
.....................................................................................
with counter function up to 10 kHz
1429
Analog output
..................................................................................... 1430
Digital output
..................................................................................... 1431
Digital output
.....................................................................................
with PWM function
1432
Synchronization
..................................................................................... 1434
Device specification
..................................................................................... 1435
12
FAQ
........................................................................................... 1438
13
EC declaration
...........................................................................................
of conformity
1439
14
Revision
...........................................................................................
history
1440
MetiOS-Devices
1
1440
Log-/ProfiMessage
........................................................................................... 1441
Safety Advice
..................................................................................... 1442
Introduction
..................................................................................... 1443
Included
..............................................................................................
in delivery
1443
System
..............................................................................................
requirements
1444
Sym
..............................................................................................
bols used in this documentation
1445
Getting started
..................................................................................... 1447
Starting
..............................................................................................
Log-/ProfiMessage
1447
Installing
..............................................................................................
programs
1448
PC..............................................................................................
connection
1448
Unknown
..............................................................................................
IP address?
1451
Basic
..............................................................................................
settings
1452
Log-/ProfiMessage
.....................................................................................
device and connections
1454
Device
..............................................................................................
types
1455
Power
..............................................................................................
supply
1456
LED
..............................................................................................
lamps, LAN, USB
1457
General
..............................................................................................
LEDs
1458
COM
..............................................................................................
interfaces, CAN
1459
I/O
..............................................................................................
module connections (terminal blocks)
1461
I/O
..............................................................................................
module installation and removal
1467
Internal
..............................................................................................
memory card installation and upgrade
1470
Internal
..............................................................................................
battery installation
1474
Configuration
.....................................................................................
and operation
1478
Overview
.............................................................................................. 1478

May 2011
XV
Configuring
..............................................................................................
a Log-/ProfiMessage device
1480
Connecting
..............................................................................................
slave devices
1481
Configuring
..............................................................................................
I/O module channels
1483
..............................................................................................
I/O module
1484
..............................................................................................
I/O module AMDT
1486
..............................................................................................
Analog input
1487
..............................................................................................
Resistor sensor type
1489
..............................................................................................
Voltage sensor type
1490
..............................................................................................
Current sensor type
1492
..............................................................................................
Current sensor type (0/4...20mA)
1493
..............................................................................................
Resistance thermometer sensor type
1494
..............................................................................................
Thermocouple sensor type
1496
..............................................................................................
Ph-probe sensor type
1497
..............................................................................................
Digital input with counter/frequency measurement
1498
..............................................................................................
Digital input
1500
..............................................................................................
Analog output
1501
..............................................................................................
Digital output
1502
Collective
..............................................................................................
device settings
1503
..............................................................................................
Configuration via an internet browser
1503
..............................................................................................
Settings
1504
..............................................................................................
Network
1504
..............................................................................................
Clock
1506
..............................................................................................
NTP status
1507
..............................................................................................
Configuration
1507
..............................................................................................
View channels
1508
..............................................................................................
Default channel configuration
1508
..............................................................................................
Service
1509
..............................................................................................
System report
1510
..............................................................................................
PROFIBUS GSD file
1510
..............................................................................................
XML template for network configuration
1511
..............................................................................................
System
1512
..............................................................................................
Update firmware
1512
..............................................................................................
Firmware changelog
1514
..............................................................................................
Restart main application
1514
..............................................................................................
Reboot
1515
..............................................................................................
Main menu device settings
1515
..............................................................................................
Device configuration (channel configuration)
1516
..............................................................................................
User management configuration
1517
..............................................................................................
Network settings (Main settings), NTP
1520
XVI

May 2011
..............................................................................................
Zeitzone/ Synchronisation
1521
..............................................................................................
Dienste
1521
..............................................................................................
Enabling user management
1522
..............................................................................................
Mailserver
1522
..............................................................................................
Saving and loading device configurations
1522
..............................................................................................
Tables
1524
..............................................................................................
Global linearisation tables
1525
..............................................................................................
Global setpoint tables
1527
..............................................................................................
Settings for all dialogs
1529
..............................................................................................
Advanced settings tab (software channels)
1532
..............................................................................................
Sensor compensation
1532
..............................................................................................
Information
1534
..............................................................................................
Basic channel selection
1535
..............................................................................................
Advanced channel selection
1535
..............................................................................................
Edge and level triggers
1536
..............................................................................................
Inherit status
1537
..............................................................................................
Configuring Software channels
1537
..............................................................................................
Accumulator
1538
..............................................................................................
Operating hours counter
1539
..............................................................................................
Differentiator
1539
..............................................................................................
Ereignis
1539
..............................................................................................
FlipFlop
1540
..............................................................................................
Limit
1542
..............................................................................................
Impulse generator
1543
..............................................................................................
Integrator
1554
..............................................................................................
Channelgroups
1554
..............................................................................................
Linearization
1554
..............................................................................................
Logic
1556
..............................................................................................
Variables
1559
..............................................................................................
Average
1560
..............................................................................................
PID-Regler
1561
..............................................................................................
Pulse width modulation (PWM)
1561
..............................................................................................
Calculation channel
1561
..............................................................................................
Collective fault
1565
..............................................................................................
Setpoint
1566
..............................................................................................
Statistics
1568
..............................................................................................
Status monitor
1569
..............................................................................................
Stopwatch
1570
..............................................................................................
System monitor
1575

May 2011
XVII
..............................................................................................
Trigger
1575
..............................................................................................
Uhr
1575
..............................................................................................
Alarmclock
1576
..............................................................................................
Counter
1576
..............................................................................................
Timer
1579
..............................................................................................
Configuring interfaces
1582
..............................................................................................
Ethernet connection
1583
..............................................................................................
CAN-Controller
1583
..............................................................................................
CAN-Driver
1584
..............................................................................................
CAN -Bus-Channel
1585
..............................................................................................
COM-Port
1589
..............................................................................................
PROFIBUS Protokoll
1590
..............................................................................................
PROFIBUS main settings, PROFIBUS-Driver
1590
..............................................................................................
PROFIBUS-Channel
1592
..............................................................................................
Modbus-RTU-Protokoll
1594
..............................................................................................
Modbus-RTU-Master
1594
..............................................................................................
Modbus-RTU-Slave
1595
..............................................................................................
Modbus-RTU-Kanal
1596
..............................................................................................
Benutzerdefiniertes Protokoll
1599
..............................................................................................
1599
..............................................................................................
Benutzerdefinierter Eingangskanal
1601
Benutzerdefinierter Eingangskanal, Register
..............................................................................................
Grundeinstellungen
1601
..............................................................................................
Eingabe
1603
..............................................................................................
Benutzerdefinierter Ausgangskanal
1604
..............................................................................................
Device memory
1608
..............................................................................................
Data transfer to USB memory stick
1611
Connection
.....................................................................................
examples
1614
Connecting
..............................................................................................
sensors
1614
Connecting
..............................................................................................
actuators
1617
Measurement
.....................................................................................
technology
1620
Galvanic
..............................................................................................
isolation
1620
Earthing
.............................................................................................. 1621
Earth
..............................................................................................
loops
1621
Shielding
.............................................................................................. 1622
ESD
..............................................................................................
protection
1623
Potential
..............................................................................................
differences
1624
Technical specifications
..................................................................................... 1626
Main
..............................................................................................
device
1626
XVIII

May 2011
I/O
..............................................................................................
modules (Device-dependent)
1630
..............................................................................................
I/O modules: AAST, ADGT, ADIT and ADVT
1630
..............................................................................................
I/O modules: DIOT, IOIT and OTPT
1633
..............................................................................................
I/O module: ADFT
1635
..............................................................................................
I/O module: AMDT
1637
I/O module
.....................................................................................
AMDT
1638
Safety
..............................................................................................
advice
1639
Introduction
.............................................................................................. 1639
..............................................................................................
Included in delivery
1640
..............................................................................................
Symbols used in this documentation
1641
Hardware
.............................................................................................. 1642
..............................................................................................
Project planning
1642
..............................................................................................
Connector panel (industrial)
1643
..............................................................................................
Connector panel (laboratory)
1644
..............................................................................................
Block circuit diagram
1646
..............................................................................................
1647
..............................................................................................
Galvanic isolation
1647
..............................................................................................
Analog inputs
1647
..............................................................................................
Analog outputs
1649
..............................................................................................
Digital inputs
1649
..............................................................................................
Counter
1650
..............................................................................................
Digital outputs
1650
..............................................................................................
Attachment
1651
..............................................................................................
AC-coupling for analog inputs
1651
..............................................................................................
External cicuits
1652
Functions
.............................................................................................. 1653
..............................................................................................
Operating mode
1653
..............................................................................................
Non-Continuous recording
1653
..............................................................................................
Continuous recording
1654
..............................................................................................
Signal simulation
1655
..............................................................................................
Synchronizing two AMDT modules
1659
..............................................................................................
Triggering and recording
1664
..............................................................................................
Redundant trigger source
1666
..............................................................................................
Time signal
1668
..............................................................................................
Digital filter
1668
..............................................................................................
Digital integrator
1669
..............................................................................................
FFT analysis / frequency spectrum
1670
..............................................................................................
Characteristics
1670
Characteristic "Maximum value", "minimum
..............................................................................................
value"
1672
May 2011
XIX
..............................................................................................
Characteristic "Peak-to-peak value"
1673
..............................................................................................
Characteristic "Mean value"
1674
..............................................................................................
Characteristic "True RMS value"
1675
..............................................................................................
Characteristic "Frequency of main amplitude"
1675
..............................................................................................
Characteristic "Main amplitude"
1676
..............................................................................................
Characteristic "Phase of main amplitude"
1676
Characteristic "Amplitude of 1X/2X/3X/xX
..............................................................................................
component"
1677
Characteristic "Phase of the 1X/2X/3X/xX
..............................................................................................
component"
1678
..............................................................................................
Characteristic "Rotation speed"
1680
..............................................................................................
Characteristic "Maximum of vector sum"
1681
..............................................................................................
Characteristic "Mean of product"
1682
Characteristic "Frequency of main amplitude,
..............................................................................................
band 1/2/3"
1683
..............................................................................................
Characteristic "Main amplitude, band 1/2/3"
1683
..............................................................................................
Characteristic "RMS value, band 1/2/3"
1685
..............................................................................................
Characteristic "Sum value"
1687
..............................................................................................
Characteristic "Remainder value"
1687
..............................................................................................
Measuring frequency or speed
1689
..............................................................................................
Measuring the phase angle
1691
..............................................................................................
Monitoring
1693
Configuration
..............................................................................................
and operation
1693
..............................................................................................
Configuration using the DataService Configurator
1693
..............................................................................................
Configuration/settings for I/O module
1696
..............................................................................................
I/O module / measurement block counter
1702
..............................................................................................
Configuration/settings for analog input
1702
..............................................................................................
Configuration/settings for FFT/spectrum
1707
..............................................................................................
Configuration/settings for characteristics
1708
..............................................................................................
Configuration/settings for analog output
1710
..............................................................................................
Configuration/settings for digital input
1711
..............................................................................................
Configuration/settings for counter
1712
..............................................................................................
Configuration/settings for digital output
1713
..............................................................................................
Visualization using ProfiSignal
1714
..............................................................................................
Firmware update
1715
Inform
..............................................................................................
ation on applications
1716
Appendix
..............................................................................................
to older AMDT hardware
1717
Appendix:..................................................................................... 1719
EC..............................................................................................
declaration on conformity ProfiMessage
1719
EC..............................................................................................
declaration on conformity LogMessage
1720
XX

May 2011
ISO
..............................................................................................
9001 certificate
1721
Expert...........................................................................................
Vibro
1722
Safety Advice
..................................................................................... 1723
Introduction
..................................................................................... 1724
Included
..............................................................................................
in delivery:
1724
System
..............................................................................................
requirements
1725
Sym
..............................................................................................
bols used in this documentation
1725
Getting started
..................................................................................... 1727
Getting
..............................................................................................
Expert Vibro operational
1727
Installing
..............................................................................................
programs
1727
Establishing
..............................................................................................
a PC connection
1728
Basic
..............................................................................................
settings
1734
Expert Vibro
.....................................................................................
displays and connections
1736
Power
..............................................................................................
supply
1736
Display,
..............................................................................................
LEDs
1737
COM
..............................................................................................
interfaces, CAN-Bus
1738
Sensor
..............................................................................................
connection (plugs)
1740
Configuration
.....................................................................................
and operation
1741
Overview
.............................................................................................. 1741
Network
..............................................................................................
configuration via the display
1743
Display
..............................................................................................
configuration and operation
1744
Expert
..............................................................................................
Vibro device configuration
1745
Configuring
..............................................................................................
channels (sensors)
1746
..............................................................................................
Trigger groups
1748
..............................................................................................
Configuring a rotation-speed channel
1749
..............................................................................................
Configuring analog inputs
1750
..............................................................................................
Track configuration
1753
..............................................................................................
FFT/Spectrum generation
1757
Creating characteristic values
..............................................................................................
(frequency/amplitude/phase) from FFT
1759
..............................................................................................
Creating Min/Max/Peak values
1761
..............................................................................................
Creating mean/true RMS
1762
..............................................................................................
Creating vector sums
1764
..............................................................................................
Digital input configuration
1765
..............................................................................................
Digital output configuration
1766
..............................................................................................
Analog output configuration
1767
Collective
..............................................................................................
device settings
1768
..............................................................................................
1769
..............................................................................................
Settings
1769

May 2011
XXI
..............................................................................................
Network
1769
..............................................................................................
Clock
1771
..............................................................................................
NTP status
1772
..............................................................................................
Configuration
1772
..............................................................................................
View channels
1773
..............................................................................................
1773
..............................................................................................
Service
1774
..............................................................................................
System report
1775
..............................................................................................
PROFIBUS GSD file
1775
..............................................................................................
1776
..............................................................................................
System
1777
..............................................................................................
Update firmware
1777
..............................................................................................
Firmware changelog
1779
..............................................................................................
1779
..............................................................................................
Reboot
1780
..............................................................................................
1780
..............................................................................................
Device configuration (channel configuration)
1781
..............................................................................................
User management configuration
1782
..............................................................................................
Network settings (Main settings), NTP
1785
..............................................................................................
1786
..............................................................................................
Dienste
1786
..............................................................................................
1787
..............................................................................................
Mailserver
1787
..............................................................................................
Saving and loading device configurations
1787
..............................................................................................
Tables
1789
..............................................................................................
1790
..............................................................................................
1792
..............................................................................................
1794
..............................................................................................
Advanced settings tab (software channels)
1797
..............................................................................................
Sensor compensation
1797
..............................................................................................
Information
1799
..............................................................................................
Basic channel selection
1800
..............................................................................................
Advanced channel selection
1800
..............................................................................................
Edge and level triggers
1801
..............................................................................................
Inherit status
1802
..............................................................................................
1802
..............................................................................................
Accumulator
1803
..............................................................................................
Operating hours counter
1804
..............................................................................................
Differentiator
1804
XXII

May 2011
..............................................................................................
Ereignis
1804
..............................................................................................
FlipFlop
1805
..............................................................................................
Limit
1807
..............................................................................................
Impulse generator
1808
..............................................................................................
Integrator
1819
..............................................................................................
Channelgroups
1819
..............................................................................................
Linearization
1819
..............................................................................................
Logic
1821
..............................................................................................
Variables
1824
..............................................................................................
Average
1825
..............................................................................................
PID-Regler
1826
..............................................................................................
Pulse width modulation (PWM)
1826
..............................................................................................
Calculation channel
1826
..............................................................................................
Collective fault
1830
..............................................................................................
Setpoint
1831
..............................................................................................
Statistics
1833
..............................................................................................
Status monitor
1834
..............................................................................................
Stopwatch
1835
..............................................................................................
System monitor
1840
..............................................................................................
Trigger
1840
..............................................................................................
Uhr
1840
..............................................................................................
Alarmclock
1841
..............................................................................................
Counter
1841
..............................................................................................
Timer
1844
..............................................................................................
1847
..............................................................................................
Ethernet connection
1848
..............................................................................................
CAN-Controller
1848
..............................................................................................
CAN-Driver
1849
..............................................................................................
CAN -Bus-Channel
1850
..............................................................................................
COM-Port
1854
..............................................................................................
PROFIBUS Protokoll
1855
..............................................................................................
1855
..............................................................................................
PROFIBUS-Channel
1857
..............................................................................................
1859
..............................................................................................
Modbus-RTU-Master
1859
..............................................................................................
Modbus-RTU-Slave
1860
..............................................................................................
Modbus-RTU-Kanal
1861
..............................................................................................
1864
..............................................................................................
1864

May 2011
XXIII
..............................................................................................
1866
..............................................................................................
Grundeinstellungen
1866
..............................................................................................
Eingabe
1868
..............................................................................................
1869
..............................................................................................
Device memory
1873
..............................................................................................
1876
Measurement
.....................................................................................
technology
1879
Galvanic
..............................................................................................
isolation
1879
Earthing
.............................................................................................. 1880
Earth
..............................................................................................
loops
1880
Shielding
.............................................................................................. 1881
ESD
..............................................................................................
protection
1882
Potential
..............................................................................................
differences
1882
Connection
.....................................................................................
examples
1885
Sensor
..............................................................................................
connection
1885
Actuator
..............................................................................................
connection
1886
..................................................................................... 1889
Appendix ..................................................................................... 1892
EC..............................................................................................
declaration on conformity
1892
ISO
..............................................................................................
9001 certificate
1893
Collective
...........................................................................................
device settings
1894
Configuration
.....................................................................................
via an internet browser
1895
Settings
.............................................................................................. 1895
..............................................................................................
Network
1895
..............................................................................................
Clock
1898
..............................................................................................
NTP status
1898
Configuration
.............................................................................................. 1899
..............................................................................................
View channels
1900
..............................................................................................
1900
Service
.............................................................................................. 1901
..............................................................................................
System report
1902
..............................................................................................
PROFIBUS GSD file
1902
..............................................................................................
1903
System
.............................................................................................. 1904
..............................................................................................
Update firmware
1904
..............................................................................................
Firmware changelog
1906
..............................................................................................
1907
..............................................................................................
Reboot
1907
XXIV

May 2011
Main menu
.....................................................................................
device settings
1908
Device
..............................................................................................
configuration (channel configuration)
1908
User
..............................................................................................
management configuration
1909
Network
..............................................................................................
settings (Main settings), NTP
1912
..............................................................................................
1914
..............................................................................................
Dienste
1914
..............................................................................................
1914
..............................................................................................
Mailserver
1915
Saving
..............................................................................................
and loading device configurations
1915
Tables
.............................................................................................. 1917
..............................................................................................
1918
..............................................................................................
1920
Settings for
.....................................................................................
all dialogs
1923
Advanced
..............................................................................................
settings tab (software channels)
1925
Sensor
..............................................................................................
compensation
1926
Inform
..............................................................................................
ation
1927
Basic
..............................................................................................
channel selection
1928
Advanced
..............................................................................................
channel selection
1928
Edge
..............................................................................................
and level triggers
1929
Inherit
..............................................................................................
status
1930
Configuring
.....................................................................................
Software channels
1931
Accum
..............................................................................................
ulator
1932
Operating
..............................................................................................
hours counter
1932
Differentiator
.............................................................................................. 1932
Ereignis
.............................................................................................. 1933
FlipFlop
.............................................................................................. 1933
Lim
..............................................................................................
it
1935
Im..............................................................................................
pulse generator
1936
Integrator
.............................................................................................. 1947
Channelgroups
.............................................................................................. 1947
Linearization
.............................................................................................. 1947
Logic
.............................................................................................. 1949
Variables
.............................................................................................. 1952
Average
.............................................................................................. 1953
PID-Regler
.............................................................................................. 1954
Pulse
..............................................................................................
width modulation (PWM)
1954
Calculation
..............................................................................................
channel
1954
Collective
..............................................................................................
fault
1958
Setpoint
.............................................................................................. 1959

May 2011
XXV
Statistics
.............................................................................................. 1961
Status
..............................................................................................
monitor
1962
Stopwatch
.............................................................................................. 1963
System
..............................................................................................
monitor
1968
Trigger
.............................................................................................. 1968
Uhr
.............................................................................................. 1968
Alarm
..............................................................................................
clock
1969
Counter
.............................................................................................. 1969
Tim
..............................................................................................
er
1972
Configuring
.....................................................................................
interfaces
1976
Ethernet
..............................................................................................
connection
1976
CAN-Controller
.............................................................................................. 1977
..............................................................................................
CAN-Driver
1978
..............................................................................................
CAN -Bus-Channel
1978
COM-Port
.............................................................................................. 1982
..............................................................................................
PROFIBUS Protokoll
1983
..............................................................................................
1983
..............................................................................................
PROFIBUS-Channel
1985
..............................................................................................
1987
..............................................................................................
Modbus-RTU-Master
1987
..............................................................................................
Modbus-RTU-Slave
1989
..............................................................................................
Modbus-RTU-Kanal
1989
..............................................................................................
1992
..............................................................................................
1992
..............................................................................................
1995
..............................................................................................
Grundeinstellungen
1995
..............................................................................................
Eingabe
1997
..............................................................................................
1998
Device memory
..................................................................................... 2002
Data transfer
.....................................................................................
to USB memory stick
2006
XXVI

May 2011
Version history

May 2011
1
1.1
ProfiSignal CD 4.1.1
Module ProfiSignal
Version 4.1.0.1
New functions
The axis label of some chart types can now be changed via script.
Errors rectified
Trend marker were not displayed in certain circumstances.
Module DataService and Configurator

Version 4.1.0.1
Amendments, additions
The treatment of initial values from time sychronized calculation channels has changed.
Constant initial values are now adopt better.
Errors rectified
Under certain circumstances, Expert Key analog inputs could not be switched to Pt xxx
measurement.
2

May 2011
1.2
Module ProfiSignal
Version 4.1.0.0
New functions
New diagram: double XY-chart
New vibration diagram: Bode diagram
New vibration diagram: Polar diagram
New vibration diagram: Shaft-Centerline diagram

Version 4.1.0.0
The language change is only possible if no channel dialog is opened.
Errors rectified
Expert Vibro characteristics channels could not be used in ProfiSignal adapter channels.
MetiOS
Firmware R243
New:
?
Expert Vibro Characteristcs channels: Limits for rotation speed

adaptive bands removed
Changed:
? Expert Vibro: Integral of window functions is now 1.0

May 2011
3
Fixed:
? Tolerance on Expert Vibro Characteristic channels was always
zero
4

May 2011
1.3
Module ProfiSignal
Version 4.0.0.7
New functions
Script functions for creating / deleting curves in XY charts.
Are the selected time range more alarms than can be displayed, the maximum possible
alarms are now shown in the table in addition to the error message.

Version 4.0.0.7
New functions
The readout of the memory (devices, databases) is directly in the Configurator possible
(as. HDS / ASCII /. TDM).
Changes / enhancements to configuration dialogs for Expert Vibro / Transient devices.
The list of checks in alarm rules are now sorted.
Expert Vibro
Firmware R242
New:
?
?
All persistent channels retain their values when reconfiguring

the channel
Expert Vibro:

May 2011
5
Major overhaul, sampling rate of tracks is rotational speed

adaptive, tracking filters, etc
? New time domain characteristics: RMS without DC
Web: New page Browser information for checking the
JavaScript and Websocket status of the browser
*iMP:
? <Req.GetPersistentData/> / <Req.SetPersistentData/>: Persistent
values of the channels, can be stored and restored e.g.
after loading a configuration
? <Req.MemEraseData/> / <Req.MemEraseData/>: Content of
storage groups can be deleted
?
?
?
Changed:
? Expert Vibro:
? Spectra show the technical useful double Amplitude by
default (compared to the mathematical correct half
amplitude)
? Stopwatch: Start / stop time is calculated from the time
stamps of the triggering sources. Frequency measurements are
more precise that way.
? Web: Firmware update and config load works without
JavaScript
? Collective Fault: Reset level mode now prevents setting of the
alarm state
? Impulse generator: Limited cycle time to min. 50 ms and pulse
width to min. 25 ms
? Timer channel: Limited response / release delay time to min.
10 ms
Fixed:
?
Expert Vibro:
? Raw tracks didn't output any data
? Track: At certain decimation ratios every 1 million samples
some samples were missing
? Coefficients for integrator changed (no ramp up)
? Characteristics in mode Harmonics didn't output any value
? Trigger groups: Inactive trigger sources caused parameter
error in other trigger groups
? Negative characteristic values at negative scaling of a track
? Analog / Digital Outputs didn't work
AMDT / ADFT:
? Fixed glitches on digital Inputs with certain hardware
revisions
? Inverting of digital outputs of AMDT / ADFT still not working
properly at certain conditions
? Sensor compensation didn't work properly
Setpoint channel did never start in free-running mode (was
over-fixed in R241)
6

May 2011
?
?
?
Timer channel: Output was stuck high if the response delay

time run out simultaneously with the falling edge of the source
In rare cases Analog outputs of AAST and ADIT could have a
full scale output value after system start
Modbus RTU master and Modbus TCP client doesn't start if the
channels are newly created. Works fine after restart or reboot
of the device (observed since R239)
Known issues:
? Modbus: Rare crash when deleting channels
? Changing configuration of Modbus device stops output
channels, changing configuration of Modbus channel restarts
? Expert Vibro: When configuring a track, Analog / Digital
outputs, Counters and Frequency inputs fall back to default
value

May 2011
7
1.4
ProfiMessage / LogMessage x000
Firmware R241-1
8

May 2011
1.5
Module ProfiSignal
Version 4.0.0.2
New functions
New script function to display a limited number of alarms / events.
Call of the measurement converter from within ProfiSignal ( entry in the file menu /
toolbar button ).
Errors rectified
Thread Sychronisierung improved in the script.
A Runtime-project creation error with activated audit-Trail was fixed.

Version 4.0.0.2
New functions
Optional (default) compression of spectra / fast time signals at Expert Vibro / AMDT /
ADFT in DataService.
Errors rectified
Error in the database backup function of the scheduler fixed.
Faulty storing of some control characters in XML fixed.
Error in the offline configuration of LogMessage devices fixed.
Create new Modbus channel failed fixed.
Unassigned modules receive appropriate identification in the channel tree.
Load / Save the user management now including audit classes.
. NET DLL: Some overloaded functions have been uniquely renamed for better
compatibility.

May 2011
9
ProfiMessage / LogMessage x000 / Expert Vibro
Firmware R241
New:
CAN: Bitrates 40 kbit/s, 20 kbit/s and 10 kbit/s supported
Upgraded NTP to 4.2.7p411 (Security Notice)
Orphaned channels (without Parent link) will be re-linked to a
channel group
Lost+Found so that this channels are editable and deletable
again
? Expert Vibro:
? Analog and Digital outputs working
? Progress of firmware update will be shown on display
? Integrator, Counter, A ccum ulator, Operating hours counter and all outputs have
a new source Preset (by default inactive) so that the persistent values
may be set by application or other channel
?
?
?
Changed:
? Default channel configuration does no longer create PROFIBUS
drivers, PROFIBUS Interfaces are inactive
? A forced / simulated default value of channels will set only the
Forced flag, all other status flags are cleared
? Web: Message in live channel list if browser doesn't support
JavaScript or WebSocket
? When loading large configuration files less likely a Timeout
will occur.
Fixed:
?
Wrong formatted timestamps if the device was set to

timezones with non-full hours, e.g. IST (UTC +05:30) (Also
backported to R228-1 and R118.1)
?
?
?
?
?
?
PWM Channel flags Configuration Error if lower limiter is

higher than upper limiter
Timer in mode release delay / retriggerable did ignore rising
level of trigger in the delay time
Storage groups: Calculation of available memory more
conservative
Stopwatch: Start/Stop source in edge trigger mode didn't work
Network configuration was corrupted if setting NTP server with
Allow large time differences
Operating hours counter didn't count anymore after edge of
10

May 2011
?
?
?
?
reset if trigger was still active

Counter channel did count up/ count down / reset on
configuration changes of sources
A forced / simulated default value wasn't always applied
Changed online tolerance didn't affect subscribed channels
Setpoint channel:
? Won't start immediately without trigger signal
? Edge trigger mode yielded in one repetition too less
? Active level trigger will repeat the sequence
Inverting of digital outputs of AMDT / ADFT didn't work
properly:
? All channels were inverted, one or more channels were set
to invert
? The channel value did reflect the electrical, but not the
logical state

May 2011
11
1.6
Module ProfiSignal
Version 4.0.0.0
New functions
Applications can optionally be provided with audit trail functions.
Audit Trail events can be displayed.
As part of the audit trail functions ProfiSignal projects has versioning function and projects are stored
encrypted.
For databases optionally no longer available channels can be displayed.
The trend channel list and the application channel selection can be filtered by channel name.
Multiple selection in the trend channel list.
Select printer with script function for report and trend.
The support for Windows XP is canceled.
Windows 8 is supported.

Version 4.0.0.0
New functions
Audit Trail functions
ASCII / XML / TDM Export within Scheduler
Support for Expert Vibro devices.
The support for Windows XP is canceled.
Windows 8 is supported.
12

May 2011
Expert Key
Device-Firmware V1.6.6
Firmware R240
New:
The firmware is no longer called Firmware - it's now called
MetiOS
First release for Expert Vibro
PTP Precision Time Protocol according IEEE 1588, will
synchronize the time within a few s
Calculation channels can handle string variables
WiMP (Websocket) server:
responds with HTTP error codes in case of handshaking
failure
Supports Websocket Version 0..13 (HyBi/RFC 6455 and Hixie
75 or 76)
PROFIBUS Protocol prevents having output channels on the
same byte / bit offset (Output channel will flag Configuration
error)
Web: Channel list with live values
LED channel for control of the front panel LED(s)
Services HTTP, Telnet, SSH, (S)FTP, NTP and the Delphin
services SFMP, XiMP and WiMP can be disabled
Telnet and FTP disabled by default
System user account root gets password root if no
password is set yet
Changed:
Poll string of COM Protocol can be max. 12 characters due to
Base64 encoding
The network interfaces will be brought up at boot time even if
some other host has the same IP address (up to now, the own
network interface was shut down)
Fixed:
COM Protocol added the string terminator to the poll string in
polled mode in every loop cycle
Block by block Average did calculate a NaN value if no source

May 2011
13
values were received in the trigger time. Now the current

source value is added to the average sum in the trigger
moment
Hang when changing the configuration of COM4 while set to
RTS/CTS handshake and no cable was connected
Limit channels will work with all-constant inputs
Analog Outputs: Zero value at output when switching off
<Req.GetChannelStatus> returned malformed XML in case of
erroneous request
PiMP / XiMP / WiMP: Restarting a datagroup with
<Req.StartStopData Command=Start/> after issuing
<Req.StartStopData Command=Stop/> didn't work
Storage group in mode level trigger didn't store while trigger
active without pre- or post trigger
14

May 2011
1.7
Module ProfiSignal
Version 3.2.0.4
New functions
Functions for printing trends and reports on a specific printer added.
Errors rectified
The settings of the EMF export were not stored properly.

Version 3.2.0.8
New functions
Real-time databases can either take the channel list from another storage source or filter
based on the channel name automatically from all channels.
The time of ProfiMessage devices can be manually set in the Configurator on the PC time.
Setup dialog for changing the network setting of ProfiMessage devices via USB added.
Setup dialog for the new channel type "User defined output" added.
The search for Delphin devices has been improved.
The adjustable sampling rate of ExpertKey were increased for current and temperature
measurements.
Setup dialog for channel type "User defined input" supplemented by additional encoding
types.
ProfiMessage

May 2011
15
Firmware R239
New:
FlipFlop: has new property Preset Priority
PROFIBUS: User-Watchdog can be disabled
CAN raw: Output channels with the same ID share the same message
NTP option Allow large time differences
Processing of data type String
Variable
o PROFIBUS Channel (input and output)
o FlipFlop (mode Latch)
o Clock (Timezone)
o System monitor (Firmware version)
COM Channels without polling can generate timeout if no data is received
COM Channel Output
While deactivating channels an invalid / config_error value is distributed to the
consumers so that dependent channels will also get that status.
New channel status flag Inactive, will be set if a channel is not active
Exporting network settings to USB stick exports also dynamic IP adresses
Importing network settings from USB stick imports DHCP setting
Calculation Channel can use the characteristic value of ADFT / AMDT analog inputs and
AMDT spectra
WiMP Web interchange Message Protocol on port 1036, a WebSocket wrapper for XiMP
Status led blinks green/orange while exporting storage data to USB stick
Changed
FlipFlop:
o Clear has priority over Preset, as long as Preset Priority (see above) is cleared
o Clear and Preset were handled as edge trigger in spite of being configured as level trigger
Integrator sends intermediate values if no reset source is configured, regardless of the
setting of Generate intermediate values
Updated time zones:
o Time zone database as of 05/2013
o World map image as of 10/2012
Updated PuTTY from 0.62 to 0.63
Fixed:
Differentiator: Trigger was ignored
Storage group:
o Level trigger with post trigger
o Erasing while active level trigger didn't store for current trigger
Inactive COM channels still sending poll strings
Exporting storage groups to USB stick was not working since R237
Persistence didn't work anymore after changing the data type of a channel
16

May 2011
1.8
Module ProfiSignal
Version 3.2.0.3
New functions
Script functions for reading strings out of measurement files were added.

Version 3.2.0.5
Errors rectified
The channels in the device memory read will no longer be read sequentially.
The dialog for reading the device memory, the time range is now updated.
ProfiMessage
Firmware R238
Fixed
Changed boot procedure to avoid rare hangs after firmware update
Reading Storage group hangs when starting several hundred reads in a very short time
(few minutes)
Updating Firmware uses less memory

May 2011
17
1.9

Version 3.2.0.4
New functions
Configuration stored on the website of ProfiMessage devices (*.tar.gz) can also be read
in the configurator.
Measurement files / databases without supply of online measurement data are stored only
with low I/O priority.
Circular links of several DataService connections are now possible.
Errors rectified
With very high load on the I/O system memory errors could occur within the measurement
database.
If the TCP/IP connection of the Modbus client was interrupted, it could lead to errors
when restoring the connection.
ProfiMessage
Firmware R237
New:
Storage group sets error flags in case of problem with the storage medium or file system
Channel configuration backup files can be erased by button on webpage
Fixed:
Modbus TCP:
Client reconnects to server in case of error
Better handling of error status
Integrator:
Correct handling of constant and/or non-changing signals
Correct handling of Reset in edge and level modes
XIMP:
High CPU load when terminating the connection
18

May 2011
Time stamp of values was always UTC and had an illegal time zone, now local time
PROFIBUS:
Output channels are resend when the connection to the master is re-established
(Constant output values remained on zero in the frame)
Constant output channels were always zero in the frame until a reconfiguration
Redundancy PNO 2.212 V1.2 with newer PROFIBUS controller
UART: Handling of buffers bigger than 256 bytes
CAN: Raw channel was always sending extended messages

May 2011
19
1.10
Module ProfiSignal
Version 3.2.0.1
New functions
The statistics function in the trend has been extended to the calculation of standard
deviation.
In the channel grid from the trend you can see the registered channels in the color of the
priotity from the alarm.
Errors rectified
Fixed an error while saving XML attributes with special characters.
The action about the events value chane, upper and lower limit by the visuobjects are
under examination. Bugs are eliminated.

Version 3.2.0.2
New functions
The selective protection for ProfiMessage / LogMessage x000 channels can be set for
more than one channel simultaneously.
Several individually selected channels can be copied and pasted as child channels.
All Channel have the tab permissons.
If moving / linking of channels is enabled insert partial / child configuration is possible in
more places.
Previously unmovable ProfiMessage / LogMessage x000 channels could now be moved in
'Custom View'.
The CPU channel of ProfiMessage devices is sorted as channel groups to the top.
Errors rectified
Fixed an error while saving XML attributes with special characters.
20

May 2011
Fixed an error when LogMessage x000 configuration should be edited offline.

By the dialog USB export configuration the save routine works correct.
Copy and past from channels.
Fehler bei der Auswahl der GPS Clock behoben.
ProfiMessage
Firmware R236
New
XiMP XML interchange Message Protocol on TCP port 1035.
RS-232 port COM4 is now usable for channels.
Support for PCPU V1.3.
Fixed
COM Channels did not send out pollstring.

May 2011
21
1.11 ProfiSignal CD 3.2.1

Modul Konfigurator
Version 3.2.0.1
Behobene Fehler
ProfiMessage network settings without DNS entry could not be saved.
22

May 2011
1.12
Module ProfiSignal
Version 3.2.0.0
New functions
New visualisation object Sequence-Editor, it show the current state of and edit an
Sequence channel (a new software channel in the DataService, created in the
Configurator).
The script language is enhanced with some shortcuts.
A part of the visuobjects and all diagrams make an color change if an activate alarm is
arrived.
New object functions
Errors rectified
-----------------------------------------------------------------------------------------------------

Version 3.2.0.0
New functions
Software sequence channel
Software limit channel with alarm database support
Store / load ProfiMessage / LogMessage x000 configurations
Offline configuration of ProfiMessage / LogMessage x000
Channel based security of ProfiMessage / LogMessage x000 channels
Support ProfiMessage / LogMessage x000 with enabled user access (login)
Copy / paste of many channels

May 2011
23
Support for new ProfiMessage / LogMessage x000 software channels

User management for ProfiMessage / LogMessage x000
Fixed
Fixed error with huge values in mean / statistics software channel
Sporadic not all data for requested channels were delivered and this may not be stored in
a database
-----------------------------------------------------------------------------------------------------
Expert Key
Device-Firmware V1.6.4
Optimization
The ARP protocol has been revised.
The network address entries of the IP-Stack will be automatically updated for the
existing connection.
This avoids "ARP FLOODING" packets during the data transfer.
New
Extensions of the Expert Key and Data Service Communication Protocol.
New commands for controlling the data flow on the existing IP connection.
System Watchdog: The Expert Key device will periodically execute (about 15 minutes) a
system initialization
if no data connection is established to the DataService.
-----------------------------------------------------------------------------------------------------
Firmware R235
New:
USB sticks with NTFS partitions are also supported (but only writable if
partition is free of any error)
Networks settings are always copied to USB stick
Channels reporting status to DataService:
24

May 2011
Firmware versions I/O-Modules

Free / allocated / available storage memory
NTP synchronization status
Error message of Calculation Channel
Modbus RTU Master and Slave
Userdefined UART Com Protocol on RS232 and RS485
DHCP client, static IP address will be used as alternate configuration
Support for loading and storing the configuration by DataService
Support for access restrictions on per channel basis
When shutting down the device, channels send a last invalid value.
User accounts
Password protection
Time synchronization by DataService - suitable for standalone applications
without real NTP server
Changing IP / Netmask by DataService from different network
Channel StatusGenerator and StatusFilter: Set or remove status flags of
values, either permanent or dependent on a trigger source
New firmware for AMDT: Dynamic adaptive sample rate dependent on rotation
speed for order tracking and phase measurement (Only for hardware version
AMDT 2.13 and newer)
Changed:
Default source for newly created Variables, Digital Outputs and Analog Outputs
is Application instead of Manual value
Avoided dead locks by recursions of channels by limiting the maximum
recursions to 20
Finding IP address of Message devices works too when Message device's
network address differs from PC's network address
New data transmission protocol for I/O modules AMDT/ADFT with less timing
constraints to ensure gapless data even at high / peaked CPU loads
Web pages are working now without having JavaScript enabled in the browser
(admittedly not so fancy...)
IP addresses with leading zeros are no longer accepted because were
interpreted as no-so-common octal notation
Fixed:
Limit Channel:
Latching was not working
Hysteresis at mode band monitoring was used incorrectly
Memory container showing sometimes zero or -1 when there were no storage
groups
PID Controller: the I-Member was 4 times too high
Setpoint:
Fixed triggers Start, Stop and Pause
Fixed variables in the table
Integrator: The timebase was interpreted as reciprocal value, existing
configurations are fixed automatically
Analog Input AMDT:
Filter type Highpass + Rectification + Lowpass could not be selected
Mean of Product, Maximum of Vector sum was calculated wrong
Compressed time signals and spectra signaled wrong compression method
Analog and digital outputs AMDT/ADFT: At watchdog timeout the default value
is set instead of holding the last value
Linearisation:
Flags for range check were not working as expected

May 2011
25
New created channels do not have a lower limit of 100 and upper limit of
500, the borders of the tables are used
Logic Channel: Fixed initial value when used with non-changing binary inputs
FlipFlop: Fixed analog latch updating output on change on input data status
26

May 2011
1.13

Firmware R234-01
Fixed
Rescuing the Message device by network configuration file on USB stick was not working
in R234
A nalog Outputs: When setting the output manually, the entered value was interpreted as
digits (= 2,44 mV ) and not as mV

May 2011
27
1.14
Module ProfiSignal
Version 3.1.0.16
Errors rectified
Visualisation - In the properties dialog was "arrange center" selected and you open the
visualisation with the object function "open visuView", the visualisation could not open in
full screen.
Trend - If you start an ASCII or an data export from the trend diagram, that use the
select data base as data source, the export didn't always use the selected data base.
YX-diagram (table) - You selected a YX-table in order to represented the characteristic
curves. The adjustment of the YX-table (e.g. color, unit and y-axis for column) didn't
assume.
Visualisation object digital meter - If the option "use sector colors" was selected, the
change of the text color didn't make directly.

Version 3.1.0.19
New functions
Support for LogMessage x000 devices
Configuration of ProfiMessage PID controller channel
Software channels are calculated in parallel with multiple threads.
ProfiMessage Dialogs channel can now be closed without a valid source channel selection.
For the analog input you can see beside the measurement period the sample rate.
The dialog of the channels can close even though no channel is select.
Errors rectified
Failed to create default paths in network user profiles fixed.
Paste for ProfiMessage PROFIBUS channel had no effect.
Sporadic error when sending rapid output values to TopMessage devices fixed.
28

May 2011
In sychronen data requests from multiple sinks sporadically, not all channels have been
requested.
In Alarmierung konnte 30min Verzgerung fr Aktionen nicht dauerhaft ausgewhlt
werden.
30min delay in alerting could be selected for actions not permanent.
In the accumulator group you can't close the dialog, if you use the channel more than
one.
The design of the following channel is changed, Impulse generator, Average and
Statistic.
The Profibus channel can copied about the menu.
The order of the software channels is everywhere the same.
At the analog input of the ADFT and AMDT the measurement range limit show right.
Expert Key
Gerte-Firmware V1.6.3
Optimierung
Optimierung der LAN-Kommunikation mittels TCP/IP-Protokoll
Datenbertragungsleistung verbessert. Puffer vergrert.
ProfiMessage
Firmware R234
New
PID Controller
Changed
Digital and Analog Outputs: The default value is applied as long as there is no other valid
value available (e.g. ProfiSignal application not yet running)
Memory management improved
Units of bytes now expressed correctly as KiB or MiB according to IEC 60027-2
Amendment 2
Fixed
Crash when deleting a dependent Calculation channel too early

May 2011
29
References (=Registers) of Modbus channels were too low by one, existing configurations
are fixed automatically
The byte stream of the Storage group was corrupted by wrongly decoded trigger marks
when using triggered Storage Groups
Analog Outputs: The default output value was 20 mA instead of 0 mA
Trigger Low Level for non-changing sources
Collective Fault
When changing the host name by DataService Konfigurator the device name will also
update
Firmware update shows decompression progress to prevent timeouts at high CPU loads
Analog Inputs didn't work with RTDs other than PT100
TopMessage
DelOS V2.52
Fixed
Fixed seldom and random hang at bootup stat "Scan Modules"
Increased Timeout while flashing AMDT / ADFT for new hardware V2.13
30

May 2011
1.15
Module ProfiSignal
Version 3.1.0.14
New functions
Online analysis: The dialog for recorder settings could not be opened when a recording
was already running. From this version, users are prompted to end a recording so that
the settings dialog can be opened.
Script: A setting to enable application variables to be selected from a dropdown box.
Script: A new command has been added to start a user process (Control->Call>Initprocedure )
Script: New object function TRMS computation to process HDS files. To calculate the
TRMS - True Root Mean Square.
Support for Expert Key T model
The trend statistic function can now compute TRMS (True Root Mean Square).
Measurement value status changed from "interrupted" to "no data".
Errors rectified
Statistic components: When the user opens statistic components in a trend that uses a
database as a data source , the selected database was not always being used to
calculate statistics. From this version, the selected database is now used to calculate
statistics. Statistics are no longer computed for trend channels that are not in the
selected database. The data source is now displayed for statistic components.
YX-diagram: Exceptions could occur when deleting a y-axis. The characteristic curve
table was then not being displayed correctly.
Alarm table/list report object: The ordering was lost for the visualisation-object alarm list
when being copied and pasted. This error occurred when copying/pasting an application
(which included the alarm list object in its report) or when copying the complete project.
Yt-diagram marker: Values for ADFT channels always appeared as 0. From this version,
the current values are displayed corresponding to the marker time-stamp.
Digital channels from Expert Key devices were being incorrectly portrayed in logic
diagrams at high frequencies.

May 2011
31

Version 3.1.0.16
New functions
Support for Expert Key with Firmware 1.6.x.x and Expert Key model T
Renaming of multiple channels.
Measurement value status changed from "interrupted" to "no data".
"Warnings" issued by the DataService are no longer recorded to system events.
ProfiMessage devices can be connected with a configuration totalling more than 1 MB.
Errors rectified
Measurement data blocks with negative scale factors.
Incorrect computation of moving averages.
Sporadic errors when saving data.
Measurement data from software channels now contain PC time zone.
Time synchronization error between Expert Key devices and PC time. This could result in
(minimal) overlapping measurement blocks.
Expert Key
Device firmware V1.6.0.10
New functions
Support for "Expert Key 100T" and "Expert Key 200T"
Console housing with thermo connectors (among others)
Optimization
Optimizing LAN communication via TCP/IP protocol
Maximum data transfer speed improved by approximately 50%
Reduction in the likelihood of transfer errors
32

May 2011
ProfiMessage
R233 / R133
New
Time synchronization by GPS clocks connected to COM3
Changed
Configuration files created by special build DataService Configurator with version
numbers e.g. 3.1.0.4.5 SB are accepted
AMDT calculation channels: Lower limit of bandwidth changed from 10 Hz to 0.1 Hz
The formula of Calculation channels additionally accepts the functions MIN and
MAX (besides the existing functions Min and Max) so that all functions are
consistently written with capital letters
In Storage Groups, the time stamp of all stored channels equals the time of the trigger
events
New version for AMDT/ADFT
Fixed
CAN Channel Raw did not update the time of its value
AMDT/ADFT in mode 0..20 / 4..20 mA miscalculated the shunt resistor values
In R132 PROFIBUS always reported Wire break to the application
PROFIBUS Interface and Protocol always displayed Wire break regardless of the bus
state when no PROFIBUS input channels existed
PROFIBUS output channels never displayed Wire break regardless of the bus state
PROFIBUS switchover redundancy to non-redundancy mode CAN kernel driver redesigned
(speed optimization)
Calculation channels:
Calculation channels: Sometimes the calculation functions were not compiled (Invalid
status)

May 2011
33
1.16
Module ProfiSignal
Version 3.1.0.6
New functions
New object functions for channel configuration in the Klicks programming language. Set
general channel configuration configures a channel's general settings. Set EK AIn config
configures an <%EK%> device's analog input.
ProfiSignal supports multiple users (multi-user mode)
Errors rectified
Trend - An error occurred in the Y-axis properties dialog when setting its color and then
its position. The Y-axis color was then incorrectly set.
Script - The relative time parameter was not always being correctly transmitted (e.g.
Trend - display time range, Stop watch - set time value).
Alarm list - An error occurred in the "Historical alarms" object function whereby the
function did not end when reaching the alarm request end time. The following script
instructions could not be performed.
Error rectified in the "Get substring" command.

Version 3.1.0.5
New functions
ProfiSignal supports multiple users (multi-user mode)
Errors rectified
Under certain circumstances empty files could be created when converting ProfiSignal
into MHouse measurement data files.
Error rectified in configuration dialogs.
Occasional error when saving compressed measurement data.
34

May 2011
Expert Key
ProfiMessage
R232
New
CAN bus channel with binary and word output
Differentiator with optional timeout
Analog outputs now scaling in mA / mV or customer units
Channel Clock - has date, time, hours etc as value
Full support for modules AMDT/ADFT (single module per bus)
Changed
Firmware for AMDT/ADFT: V3.58
DataService Configurator V3.1.3.8 Beta
Impulsegenerator works real time synchronized down to 50 ms
Basic settings (Network, Clock, etc) now working with DataService Konfigurator
Version numbers are unified now: A R232 is no longer shown as V2.3.2 at some places
Web:
o
o
Restart main application when synchronizing to NTP servers

Changed warning text when rebooting, restarting, setting the clock and synchronizing
to NTP servers
Updated PuTTY from 0.60 to 0.62
Fixed
Spectral Component was calculating always with 3 lines

May 2011
35
1.17
Module ProfiSignal
Version 3.1.0.3
Errors rectified
Visualization objects - From ProfiSignal Version 3.1.0.0, object borders were being
displayed at 1 pixel larger. This led to errors, e.g. text was no longer being displayed for
text input. This error has now been rectified.
Parameter view - When a channel selection box was being used to load a parameter file
in the parameter view, the value for the selected channel could change.
Oscilloscope diagram - The relative time axis was not being correctly portrayed for an
AMDT time signal as a trigger channel.

Version 3.1.0.3
Errors rectified
The configuration could not be read for an incomplete sensor-compensation configuration
for Expert Key channels.
Switching from Expert Key outputs to an 'Application' source functioned only after the
second save.
OPC inputs could nolonger be added.
Errors rectified in the ProfiMessage settings dialogs.
Outputs could not be assigned for ProfiSignal 3.1 Client and ProfiSignal 3.0 Server.
Expert Key
36

May 2011
ProfiMessage
R129/R229 (Build 7221) 17. November 2011
Web:
Fixed (again) manually setting the clock
Restart main application when setting the clock
The default hostname profimessage.example.com is changed to ProfiMessageSN<serialnumber>. Empty Domain name is allowed now.
PROFIBUS:
A DPV1 PRM is accepted even in case if an invalid USER_PRM is sent by master
New: Binary and word output channels (data direction ProfiMesage --> PROFIBUS
Master)
CAN-Bus will be restarted in case of BUS OFF
Hardware watchdog is allowed more time at boot up (no hard reset while file system
check)
New firmware for AMDT/ADFT V3.54
Transmission errors from AMDT/ADFT consuming all available memory are ignored
R229 may have spontaneously thrown kernel panics with a reboot
Fixed deadlock when configuring circular referenced channels
The full qualified domain name of the ProfiMessage will be automatically inserted in the
Device channel name (root node in channel tree) to reduce the confusion between host
name and device name.
Analog outputs of AMDT / ADFT now scaling correctly
Automatic firmware download AMDT / ADFT

May 2011
37
1.18
Module ProfiSignal
Version 3.1.0.2
Trend - The statistic is now able to call a single channel. The context menu in the
channel table has therefore been extended.
Trend - The filter function has been enhanced. Invalid measurement data can now be
filtered, i.e.not displayed in the diagram.
Errors rectified
Orbit diagram - Relative measurement data files would not run.
Trend - Time range information was missing in the channel table for relative
measurement data files. A number's sign can now be changed via a button for time range
settings.
ASCII-Export - When a trend is called, existing files are overwritten only following a
confirmation prompt.
YX-diagram (table) - Buttons for log axes were not being displayed.
Tables - Tables can now be saved following the input of values without having to wait for
at least one second.
Trend - When exporting measurement data files, not every channel was being exported.
Text input - Exiting text input with ENTER was not writing the value to the assigned
channel.
When opening a HDS file via the Windows Explorer, the dialog did not include the ASCII
export option.

Version 3.1.0.2
Amendments
From this version, DataService channels with a 0.0 tolerance transfer only changed
measurement data. A tolerance of -1.0 is required to transfer all values.
38

May 2011
Errors rectified
Errors have been rectified in computation and statistic channels.
Individual channels were being lost in exporting to .HDS files.
When adding measurement data to existing measurement data files of older formats (up
to DS 3.0), meant the files could then become unreadable.
Some license files were unreadable.
Rectifying errors in ProfiMessage dialogs.
Expert Key
ProfiMessage
R129/R229 (Build 7133) 17. November 2011
Web:
Fixed manually setting of the clock
Updated world map and time zone data to reflect recent time zone and border
changes
After successful firmware update reload of home page after 60 seconds

May 2011
39
New channel Spectral Component
40

May 2011
1.19
Modul ProfiSignal
Expert Key
ProfiMessage
-----------------------------------------------------------------------------------------------------
Modul ProfiSignal
Version 3.1.0.1
Errors rectified
Trend - Axis settings such as color and width were not being adopted when loading trend
configurations.
-----------------------------------------------------------------------------------------------------

Version 3.1.0.1
Amendments
Data type detection for TopMessage COM channels has been updated.
Errors rectified
ProfiMessage and TopMessage connection dialogs could not be opened on WLAN

May 2011
41
adapters.
Problem rectified concerning of AMDT / ADFT measurement data reception from
ProfiMessage devices.
-----------------------------------------------------------------------------------------------------
Expert Key
-----------------------------------------------------------------------------------------------------
ProfiMessage
42

May 2011
1.20
Module ProfiSignal
Expert Key
ProfiMessage
Module ProfiSignal
New functions
The Klicks programming language has a new Assign Data flow function. Assign Data flow
uses a script to assign a data source to an object. The object's value is then updated
every 100 msecs with the value from the data source.
The File factory enables complete or partial data files to be merged into a new or
relative file.
New visualization objects: The digital clock can be set to display data and/or time in a
digital format. An alaog clock face can be displayed using the analog clock object. The
stop clock object enables times to be measured. An event can then be triggered once a
specified time has been reached.
Diagrams can be labeled using text fields.
New diagrams: The oscilloscope diagram enables the display of medium to high-speed and
one-off, i.e. transient, processes. This diagram type is available in the online analysis and
as a visualization object.
Support for the current ProfiMessage device.
New object functions

Object functions can be used to determine ProfiSignal's standard directory and an
application's standard directory.

May 2011
43
Get number of values - This function determines, for a channel in a measurement file, the
number of values whose time-stamp is between the given start and end times.
Monitor Information - This function determines information about the selected monitor
(Monitor Index > 0) or desktop (entire virtual desktop).
Current time range - Determines the time range currently being displayed in a diagram.
Trend markers can now be processed using object functions. Refer here tofunctions for
markers.
Trend - The marker analysis function has been enhanced.
Trend - The load mesfile object function now has the option to display the configuration
that has been saved to the measurement data file.
Trend - The statistic function has been enhanced. Difference Min/Max and number of
measurement values can now be determined. Columns for statistics can be hidden/
displayed via the context menu. Values are then determined only for the displayed
columns.
Errors rectified
-----------------------------------------------------------------------------------------------------

Version 3.1.0.0
New functions
A saving tolerance can be given for each channel in a measurement databases.
The AlarmManager has been extended to include monitoring of a channel's rate of
change.
The AlarmManager has been extended to include monitoring measurement data inertia.
The AlarmManager has the option to reset the siren/horn via a channels (positive edge)
The AlarmManager's warning light mode now includes "active and unconfirmed alarms".
The scheduler has now includes the option with realtime measurement data.
The DataService's Data Server now has more settings.
44

May 2011
New software channels "average", "statistic", "edge counter" and "computation channel"
are now available.
A Modbus TCP Client driver is now available.
A DataSocket Client driver is now available.
Copy & Paste for channel configuration is available for some channels.
Support for the current ProfiMessage device.
Amendments
Saving of measurement data (.hds or database) has been internally optimized and the file
version increased.
Older program versions can not open files created under this version.
-----------------------------------------------------------------------------------------------------
Expert Key
-----------------------------------------------------------------------------------------------------
ProfiMessage

May 2011
45
1.21 ProfiSignal CD 3.0
ProfiSignal module
DataService and Configurator module
Expert Key
-----------------------------------------------------------------------------------------------------
ProfiSignal module
Version 3.0.0.10
Fixes
Digital display - Error in black font color settings in a newly created digital displays.
Table parameter view - Errors with the standard data type setting.
Parameter view - The settings dialog for groups was not being displayed.
Version 3.0.0.9
Amendments
VisuView - Amendments to how channel names are displayed in visualization objects:
when a channel name exists in multiple devices, then the device name is added to
channel name: "device name.channel name".
ModuleView - Improvements to the moving of block symbols. Block symbols can now be
positioned above other block symbols. A check is made on the validity of the block
symbol's positioning only at its end location.
Fixes
46

May 2011
YX-diagram(table) - The curve was not being correctly displayed when the first column
of the table was set as the row heading.
YX-diagram(table) - Curve settings made in standard configuration mode now remain
after switching to run time and edit mode.
Trend - When a measurement data file was being displayed in the diagram, the channel
was not being detected for the object functions Set channel color, Set channel Y-axis
and Channel visible.
Trend in a report - Legends were not always displayed uniformly for all reports.
Online analysis - When ending, and then aborting the ending of a recording session in a
ProfiSignal online analysis, the online analysis then failed to display new measurement
data.
ModuleView - Rectified various display errors, e.g. missing connectors between block
symbols.
ASCII export - The given time range is now correctly provided. For complex measurement
data (AMDT-time signals), the entire measurement data blocks were being exported.
Adapter channel - Amendments to the source channel configuration were not being made
when the use source channel settings option was enabled.
Alarmlist visualisation object - When a DataService interrupts a connection or an error
occurs when requesting alarms, the alarm list is deleted and the relevant error displayed.
If there is an interruption in the DataSe rv ice connection, the data request will repeat
after a short wait.
Version 3.0.0.8
Amendments
Script: Dividing one time by another time returns a double/floating-point number instead
of a time.
Script - The status query in the Check value state object function updates All errors.
Status queries for All errors in the script window of older ProfiSignal versions display the
integer 72057594037923840. The requested status is to be updated here.
Alarm lists - When password protection is enabled, event files for fault diagnostics can be
opened only by users with evaluator rights (refer to the section on users rights).
Fixes
ASCII export - In export settings, the equidistant mode had an erroneous time base
setting. The microsecond entry did not appear in any selection list. Milliseconds was the
first entry. The list was however internally processed as microseconds. When selecting
the millisecond time base, the microsecond time base was set (seconds-> milliseconds,
minutes -> seconds, hours -> minutes).
Channel box parameter object - The channel box did not always update when opening
the ParameterView (with a parameter file).
Date/time Visuobject - when a specific timezone (as opposed to the local timezone) was

May 2011
47
set in the application, it was changed to the local timezone when a time was entered
manually.
ParameterView - The Keep original proportion setting in the ParameterView page settings
were not being saved.
Script - The directory exists object function returns a correct result only when the
directory name is entered with a backslash.
Script - The load MesFile function (trend) did not test the configuration parameter. The
measurement data file was always loaded with the configuration.
Runtime project - A runtime project was generated erroneously when the source project
(dpa file) was located in a drive's root directory (e.g. F:\project.dpa).
Version 3.0.0.7
Fixes
ASCII export - An error occurred forASCII input for row/column separators . The error
occurred for the input of single character ASCII values, e.g. $9. On closing the dialog,
the string was not saved. On attempting to reopen the export settings dialog, an
exception occurred and the dialog failed to open. The general settings dialog could also
not be opened.
Version 3.0.0.6
Fixes
ASCII export - The input for row/column separators in the export settings was not being
correctly checked. Special characters such as TAB are input with the character's ASCII
value. For example, for TAB enter: $9 (9 = ASCII value for the tabulator). There was an
error in the Help's description for this input (input using the '#' character is incorrect).
ASCII export - For Adaptive Line By Line and Equidistant settings in ASCII export mode,
measurement data with status flags (e.g. range error detection) was not being exported.
Version 3.0.0.5
Alarm list - In the historical alarms function, only those alarms appeared that were
triggered in the selected time range. From this version, every active alarm from the
48

May 2011
selected time range is displayed (as long as no other filter is enabled).

Fixes
Measurement data export - When a measurement data export was performed in an
analysis following the adding of offline calculation channels, an error message appeared
stating that the export could not be started. From this version on the export is performed
correctly. The error occurred during ASCII export.
When selecting the export time range, the time range was always rounded up to seconds
even when the input time range remained unchanged. From this version, the time range is
rounded up only when the dialog's start and end times are amended.
Rounding errors when displaying the time-stamp - The seconds were being rounded up for
time-stamps within the range hh::mm:ss,9996 to hh::mm::ss,9999. For example, the
ASCII export time-stamp
04.02.2011;10:59:53,999600 was portrayed as 04.02.2011;10:59:54,999600.
Trend report object - Layout settings (from layout in the settings dialog) were not being
applied completely. The legends were then not always the same for the show legend only
setting. A further error occurred when the trend diagram was printed prior to the
generation of a report. The images in the report were then partially distorted.
Printing trends - When setting legends on own page, a new page was not generated and
the legend was printed over the diagram. When a report (with this diagram) was
generated following printing, or exported in EMF format, distorted images could occur.
Trend Visuobject - Setting the Y-axis range object function resulted in an error for
incorrect Y-axis input. The module with this object function then failed to end and could
not be re-started.
The Picture Visuobject - When a file name only (without folder) was entered in the
settings dialog for picture selection, it was not correctly saved. The picture was
displayed when closing the dialog, but then saved with the absolute path input. From this
version the file name (without folder) is saved using only the file name. Refer also to data
input without folder name.
Version 3.0.0.4
Fixes
ASCII export - For Adaptive Line by Line and Equidistant in export mode, ASCII export
ended only when a frequency spectrum was also exported. The progress dialog stated,
however, that the export had ended.
Trend report object - When generating a report with YX diagrams, FFT diagrams and
Orbit diagrams, the curves were not always updated (VisuView with background trend).
Yt diagram - When autoscaling Y-axes, slow channel curves (i.e. no changes within the
displayed time range) were not included.

May 2011
49
Version 3.0.0.3
New functions
Support for Expert Key 200 and P models
Fixes
Analysis, online analysis - Timezone settings for time-stamp portrayal can now take place
for any type of diagram via the context menu in the data area.
ASCII export - Exporting frequency spectra takes place only for Adaptive Block by Block
settings. Frequency spectra are now exported independently of the Adaptive Block by
Block setting.
Saving project files - Project files that were created using older ProfiSignal versions are
now saved using the original filename with projectname_OldVersion.dpa. The
projectname_OldVersion.dpa may still be loaded using the older ProfiSignal version.
VisuObject table - The standard datatype setting in the table settings dialog was not
being correctly saved to the project file. The standard data type is used when a table is
extended and the new table cells still have no clear data type. Check all applications
where scripts process cell content.
Version 3.0.0.2
New functions
FFT diagram - The frequency spectrum is portrayed as an order spectrum when the
"order analysis" is enabled. Refer to the AMDT I/O module configuration - FFT spectrum
settings.
The spectrum of an order spectrum is normalized to the measured rotations - normally
from a vibration measurement on rotating machinery. This enables the easy evaluation of
harmonized vibration components.
If users are assigned a Windows account when password protection is enabled, there is
an option to then use Windows to authenticate users.
Fixes
Trend Visuobject - The enable pause script function is now performed correctly for YX
(HW-channels), FFT and Orbit diagrams.
Yt diagram - When the number curve option was enabled, errors could occur when
printing (incomplete printing of curves).
The error could occur for small measurement data files for which no data was visible
when displaying the mouse cursor.
50

May 2011
Errors occurred when zooming.

FFT diagram - Minor errors were fixed in the zooming and navigating procedures in FFT
diagrams.
YX diagram (Tables) - Errors were fixed that occurred when updating the diagram.
Project files - When loading a project, errors could occur when country settings were
changed (decimal separator, digit group symbol).
Initialization via the script instruction failed. If, for example, the script instruction was
called from a button event, this event would not be completed.
Settings dialog for VisuObjects - When a channel in the channel tab no longer exists, it is
displayed with a message.
Alarm list report object - The Gone time column of a generated report shows a time only
when an alarm has gone.
Minor errors were fixed in the settings dialog.
Parameter object profile - It is again possible to select the set-point channel from the
channel tab.
When processing the profile the current input instead of the recipe data was being used.
Check your applications for possible errors.
The label parameter object - It is again possible to select a channel in the channel tab of
the settings dialog.
Version 3.0.0.1
New functions
Support for LogMessage devices.
Fixes
Trend Visuobject - The export functions for the diagram context menu were not enabled
when the trend was initially added in runtime via the script function Initiate: Add channel.
Yt diagram - The following settings can also now be performed in the configuration of
trends:
If the mouse cursor is visible, its position is saved and then displayed accordingly when
the configuration is loaded.
If markers are displayed, these are shown when loading the configuration.
FFT diagram - Rotations are not correctly shown in the FFT diagram's status bar.
ASCII export - Data loss could occur in equidistant export mode. This error has been
fixed.
Alarm list - User rights were not correctly queried for active authentication.

May 2011
51
Version 3.0
New functions
Windows 7 support
Expert Key support
Runtime information can be added via scripts and output to a special log window.
The conditional instructions in the Klicks programming language have been extended
with alternatives.
The Klicks programming language now has the option to insert blank lines in order to
group lines together.
Each application has a special initialization module added. This is always run first when
switching to runtime. The instruction can be called at any time using a script instruction.
In addition to the initialisation module, all visualization objects contain an initialisation
event.
A new color YX diagram offers the option to manage the color of characteristic curves
using a third channel.
New alarm list report object.
Fault data acquisition - Measurement files generated by an alarm can be displayed in the
fault diagnostics.
The module chart view has been updated. There is now a variable number of event tabs.
Connector lines, which were initially inserted automatically according to a system of
rules, can now be amended as required.
The search functions have been extended. There is now the option following print out to
search and to use placeholders.
The Recorder visualization object now contains the events Start recorder and Stop
recorder.
ProfiSignal has been extended with the ProfiSignal Go licence.
Functioning of the YX diagram has been changed. In earlier versions only characteristic
curves that used the same X channel could be displayed. The new version enables
separate channels (selected from X and Y channels) to be directly configured.
A range of diagram types are available in the online analysis.
ASCII export has been enhanced for frequency spectra.
The oscilloscope mode in Yt diagrams has been updated.
52

May 2011
Fixes
The table Visuobject - There were errors in the automatic data type detection. A
standard data type can now be input via the table's properties dialog. The standard data
type is used when a table is extended and the new table cells still have no clear data
type. Check all applications where scripts process cell content.
-----------------------------------------------------------------------------------------------------

Version 3.0.0.8
Fixes
Fehler in der Zeitsynchronisation mehrerer Expert Key Gerte behoben.
Version 3.0.0.7
Neue Funktionen
Untersttzung von Expert Key Gerten mit 12 Zhlern.
Amendments
Bei der ADFT werden jetzt fest bei Abtastraten < 100 Hz Einzelmesswerte verarbeitet,
unabhngig von der eingestellten Blockgre.
Fixes
Falsche Signalisierung von unterbrochenen Alarmanforderungen von einem anderen
DataService Server behoben.
In der Datenbank wurden Messwert Zeitstempel unter bestimmten Umstnden geringfgig
verndert.
Version 3.0.0.6
New functions
Support for Expert Key devices with digital debouncing on all digital inputs.
Support for resistance measurement with Expert Key devices.

May 2011
53
Fixes
An error was resolved in ProfiMessage's recording dialog concerning the conversion of
tolerance values.
Version 3.0.0.5
New functions
Support for Expert Key devices with the reference for differential inputs option.
Fixes
Switching from bipolar to unipolar current measurement in an Expert Key device could
result in damaging the channel configuration.
Version 3.0.0.4
New functions
Moving / linking of channels in the channel tree can be switched off under 'Extras'.
Fixes
Expert Key 100/200 P configurations can be saved and restored.
There could be data loss when reading measurement data from a measurement data file /
database while moving to realtime measurement data.
API: Under XP, the DLL for certain applications could not be loaded without version
identification.
Version 3.0.0.3
New functions
Support for Expert Key 200 and P models
Fixes
Error rectified in the computation of min/max time-stamp for statistics of measurement
data blocks.
The interruption has been rectified when reading TopMessage's "complex" data memory.
The ProfiMessage PROFIBUS channel configuration now correctly calculates the
54

May 2011
percentage tolerance following range changes.

Overall size of the database for separate files > 2GB was not correctly computed.
Version 3.0.0.2
New functions
If users are assigned a Windows account when password protection is enabled, there is
an option to then use Windows to authenticate users.
Amendments
Expert Key Upgrading, especially for TCP connections.
Fixes
AMDT spectrum: Some HW status bits were being incorrectly interpreted.
When assigning a fixed data source in Visu-Trend, only offline measurement data was
being requested from the DataService server.
Error rectified in displaying TopMessage / LogMessage names in the channel tree.
API: The extended error code was not being set for some functions.
Fault diagnostics: A file that is located on a different PC (server) now opens correctly.
Version 3.0.0.1
New functions
Support for LogMessage devices.
Fixes
Error rectified in the loading of certain Expert Key configurations.
In Expert Key devices, the first frequency measurement value could be incorrect following
a "0" frequency.
Under certain conditions, file / database read outs may omit the starting value.
Version 3.0
New functions

May 2011
55
Windows 7 support
Expert Key support
Back up function for the alarm database
Variable thresholds for monitoring alarms
New action 'saving' for alarms on the fault data acquisition of measurement data
Data reduction through averaging when saving measurement data to a global database
Software channels 'Variable channel' and 'test channel'
Amendments
FFT and block time signals (AMDT / ADFT) are stored in a different format. This is not
compatible to a older versions. Older versions can not portray these signals.
When password protection is enabled, a client DataService no longer needs to activate
password protection to establish a connection. Valid authentication by the client
DataService is sufficient.
Fixes
When password protection is set to the password server, authentication by any
administrator is sufficient to log in a client DataService.
-----------------------------------------------------------------------------------------------------
Expert Key
2011-06 / ProfiSignal-CD V3.0.9 / Firmware V1.5

Expert Key 100. Expansion from 2 to 12..8 digital inputs with counter function.
2011-03 / ProfiSignal-CD V3.0.8 / Firmware V1.4.6.2

Expert Key 100. New. Adjustable digital debounce for DIN3..12
Expert Key 100. New. Sensor type Resistor for resistance measurement.
2011-02 / ProfiSignal-CD V3.0.6 / Firmware V1.4.5

Expert Key 100. From circuit board V1.3.2. New. Higher channel-to-channel separation by
analog switch.
56

May 2011
analog switch.

May 2011
57
1.22
To ProfiSignal CD 2.2
ProfiSignal module
-----------------------------------------------------------------------------------------------------
ProfiSignal module
Version 2.2.0.34
New functions
Fixes
Visualisation - In Version 2.2.0.32, the visualization objects (e.g. digital displays)
were being updated only in active VisuViews.
Table Visuobject - A value change event within a table took place only when the
input focus changed to a different Visuobject. A value change event in a table is
now triggered by changes occurring via user input or script instructions.
Note: For a value change event via user input to be triggered, the table Visuobject
must be used in a script instruction. This applies also to the table Parameterobject.
ParameterView - The required options were not set for the script instructions for
radio button's Config Write: ... selected name for recipe and Assign Value: ...
Recipe value. Access was changed to selected recipe index and selected recipe
name. Access till now took place via configuration. From this version, access to
value assigning takes place via assign.
Report - When only a filename (without path) is entered in the properties dialog of
the picture report object, the picture is not included in the report.
58

May 2011
Version 2.2.0.32
New functions
Exporting diagram as EMF - The print function for trends has been upgraded.
Diagrams can be exported as an EMF file (Microsoft Windows meta file). The export
is run from the diagram context menu (Export -> Export trend as EMF or Export ->
Export trend and legends as EMF). The export can also be called via the object
functions Export trend as EMF and Export trend and legends as EMF. There is also
an option to copy the diagram area to the clipboard (diagram area context menu :
Export -> Export trend to clipboard).
Trend VisuObject - The Load MesFile object function now enables suppressing of
the configuration in the measurement data file to be loaded.
Fixes
Report - Errors have been rectified in the table report object. If the overall width of
all the columns of a table exceed the overall table width, a serious error then
occurred crashing ProfiSignal when opening a report with this table.
Version 2.2.0.30
New functions
Fixes
Online Analysis - When changes were made to the recorder trigger options, the new
settings were enabled only after the online analysis was restarted.
Recorder visualization object - A pretrigger time of 0 seconds can be set for the
pretrigger recording option (this rectifies the error in earlier versions that disabled
the pretrigger for inputs of 0 seconds).
Visualisation objects - When using general settings to change the font for
visualization object descriptions, the visualization object was not correctly scaled
(description was displayed incorrectly).
ParameterView - The setting is now correct for "active" settings on a tab in the
ParameterView (Instruction Configuration Write: ...). When a tab's active option is set
to off, the parameter objects on this tab are no longer available. The instruction
can also be performed when the ParameterView is closed.

May 2011
59
Alarm list visualisation object - Changes in the columns to be displayed settings

dialog are now correctly processed.
The output and export functions were not being performed as a block in earlier
versions. From this version, these object functions are closed only when the
function has been completely performed (e.g. all alarms for the requested time
range have been displayed).
Printing diagrams - Legends were written beyond the right margin in cases of long
channel names or multiple columns. From this version, the rows of every column are
restricted to the right margin (text is truncated).
Version 2.2.0.26
New functions
Klicks programming language - The <RETURN> placeholder can be used as line
breaks for the text input and labeling of visualisation objects per script.
Fixes
Report - ProfiSignal crashed when closing a report via the context menu in the
management tree.
Report - Reports could no longer be opened when generating reports without trend
output. An error message is displayed that a standard design can not be loaded.
From this version, the report opens with an error message that the picture could
not be found for the trend output.
Visualization objects - The value change event was not always triggered for
visualization object input such as check boxes. If, for example, a value was
assigned to a checkbox via a script instruction, the change would be shown in the
VisuView but the value change event would not be triggered.
Table Visuobject - Line breaks in table cells are now correctly saved and loaded for
the functions save to a CSV file and load from a CSV file.
Table Visuobject - Line breaks are now correctly inserted for the "Add from CVS"
function.
Visualisation objects - Display errors occurred for displaying titles on the left (from
the settings dialog option for visualization objects) when the text to displayed
required the entire visualisation object's space.
Version 2.2.0.22
New functions
60

May 2011
Fixes
Reports - Errors occurring for Report imports are now displayed in a dialog window.
Text input parameter object - Script errors could occur when the data type was
amended for text input (unknown ParameterObject).
YX table Visuobject - Settings for YX-table columns were not correctly loaded.
Presettings were improved for a new YX-table Visuobject.
Analysis: FFT diagram - Improvements have been made to the opening of a
measurement data file in a FFT diagram. After opening, the last spectrum is
displayed for each visible channel.
Version 2.2.0.20
New functions
Fixes
Report - Errors have been rectified in the table report object. Report tables with
multiple data records displayed every data record.
Errors were rectified in the import report function: the report table had not yet
implemented the import function; errors occurred when importing reports created
with pre-V2.2.0.0 versions.
Print diagram - When a picture file for the customer logo was input in the print
diagram dialog it was not always portrayed.
ASCII export - When selecting the date option from export settings, a column for
the date is now created. When the relative time input is set, the date column
remains empty.
Password protection - Several key combinations (e.g. ALT+F4) were not yet
blocked.
Version 2.2.0.14
New functions

May 2011
61
Fixes
Report - Errors when printing reports from Version 2.2.0.10. When printing reports,
diagrams were not printed despite being displayed in the preview.
ASCII export - Data loss occurred for ASCII exports that were run using the
database in trend function. The export did used the global database as a source
instead of the the open database. Lines were sometimes written twice for the
equidistant export mode.
Statistic components - The statistic component for YT-trends did not always use
the correct data source: if the YT-trend object was linked to a recorder, the
current recording was always used as the data source.
Alarm lists - The horn button was hidden when displaying historical alarms but the
sound file continued to play. The button remained hidden even when switching back
to the current alarm. From this version, the button remains displayed until the horn
has been confirmed.
Print diagram - When the title is changed in the print diagram dialog, the setting
would be used directly but only from the next printing.
Version 2.2.0.10
New functions
Klicks programming language - The initiate function open VisuView was amended.
The full screen mode for the VisuView is always borderless.
Fixes
Calculation channels - Conversion errors occurred in formulae when the the
Windows regional and language options used a decimal separator other than a
comma.
Klicks programming language - It was only partially possible to select ODBC
visualization objects in the script editor.
Reports - Errors occurred when a report table became full during runtime and was
extended by a column. The report then failed to generate. The error is rectified in
the current version and the report can be generated. New columns are not
incorporated into the report.
Report - Diagram legends were not always correctly portrayed in a report when
generated with multiple data records. The error occurred when there were changes
to the number of visible channels in a trend.
62

May 2011
Report Viewer - If a report, generated by an earlier version of Pro fiSig nal, is

amended it can no longer be displayed or it becomes hidden in the background
page. Saving was however successful.
Report Viewer - A diagram could no longer be operated when it was edited ("Edit
trend" mode enabled) and then had its design edited. In the current ProfiSignal
version only a diagram or a design can be amended.
Enabling password protection for projects - When enabling password protection for
a project, an error could occur whereby a visualization object receives an
unprotected setting that is not displayed in the settings dialog (user rights tab).
Password protection - Automatic log off - If a logged in user belonged to a user

group that had the automatic logout option enabled, input from this user was not
registered and the user was automatically logged out. Examples of non-registered
input are: operating of trends, development of an application.
The current version of registers all Pro fiSig nal keyboard input and mouse clicks and
resets the time for automatic logout.
-----------------------------------------------------------------------------------------------------
Updates in Version 2.2.0.0

New functions
Online analysis - Online analysis enables current measurement data to be simply
portrayed and recorded.
Application events for password protection.
New script instructions for TopMessage connections to the DataService:
Add TopMessage connection
Delete TopMessage connection
Fault diagnostics - An alarm event can now be displayed in a trend with the alarm
list visualisation object.
Context sensitive search - The search functions have been upgraded for the Klicks
programming language.

May 2011
63
Print diagram - The print function for the trend object has been upgraded.
Reports - The portrayal of a diagram in a report has been improved. In earlier
versions only a screenshot of the trend was record in the report as a bitmap. There
is now an improved portrayal of the diagram when printing the diagram from the
trend object, (refer to the YT diagram example). The diagram is saved in"Enhanced
Metafile" format (EMF).
Note: Reports generated from Version 2.2 can not be viewed in older
versions.
ASCII export - The export has been improved. Large data volumes can now be
exported quickly.
Recorder - Time synchronization, which was included for all device types, now has
a level trigger.
Offline calculation channels - Offline calculation channels can now process time
signals from AMDT or ADFT.
Text input - For double/floating-point number settings, a value format can be given.
This includes setting the number of decimal places to be displayed. Maximums and
minimums cab also be selected for whole and floating point numbers.
Fixes
ASCII export - Data loss could occur when exporting large volumes of data (e.g.
AMDT time signals), especially at high CPU loads.
YT diagram - Portrayal errors have been rectified for slow changing measurement
data.
YX diagram - The time range in the status area is now correctly displayed when
analysing a measurement data file with a YX diagram. Errors in the portrayal (such
as the omission of lines) has been rectified.
-----------------------------------------------------------------------------------------------------

Fixes
64

May 2011
Offline calculation channels - Omissions occurred in the computation of calculation

channels (computation cycles were omitted). Statistical functions (such as a
triggered mean value) failed to return a value or always returned a 0.
ParameterView - Parameter objects that were positioned in a group did not load or
save to a parameter file.
An error in ending Pro fiSig nal has been rectified - Various errors occurred when
ending Pro fiSig nal:
- A message that the user does not have the rights to end ProfiSignal ....,
- Pro fiSig nal can not be closed;
-----------------------------------------------------------------------------------------------------

New functions
Licensing
Alarm management
Search functions for the Klicks programming language
A search function was implemented for the Klicks programming language. The
function enables searches for terminology, visualization objects, etc. in a script.
Refer here to the search dialog section for the Klicks programming language.
Runtime project
Pro fiSig nal provides the option of creating a runtime project from a project. All the
project files required for a runtime project are packed into a DRT file. A runtime
project can not be amended.

May 2011
65
User management including password protection

Pro fiSig nal provides an access management system that requires user
authentication to operate the software. Refer to the section on password
protection.
Note: User management and password protection do not have backward
compatibility. Projects with password protection that were created up to Version
2.00b require updating for the new system of user management.
Changes to the VisuView toolbar
The Visuview's toolbar has been rearranged. The visualization objects have been
organized under different tabs to improve the overview.
The save project under ... function has been replaced.
The save project under ... function has been replaced with the copy project
function. Till now, the save project under ... function renamed only the project and
therefore the project files. The project created in this way could not be loaded in
parallel to the source project. The new copy project function creates a new project
that can be loaded at the same as the source project.
Trend - Channel table
The sort function for channels has been upgraded. It is now also possible to sort
channels using drag&drop and to save this setting to the configuration.
Recorder - Time synchronization included for all device types
Pro fiSig nal is now able to include time synchronization for fast time signals for any
device type. A digital reference signal now enables multiple modules to be
synchronized for recordings according to the time of a single module.
Fixes
ASCII export - Block exports could result in Pro fiSig nal crashing. This error has
been fixed.
Renaming projects - The rename project function (management tree_ project
context menu) is now correctly performed. The project files (.dpa) and associated
folders are renamed as well as the project name.
-----------------------------------------------------------------------------------------------------
66

May 2011
Upgrades in Version 2.00b

Upgraded functions
New object function in the YX diagram to assign the x axis. (Klicks)
Amendments:
Visualisation components - Titles and text input with line breaks.
Analysis dialog - An extra diagram-type dialog is now available when opening a
measurement data file for analysis.
ASCII export - A millisecond time range is now also available for equidistant exports.
A separate column can now be selected for the millisecond section of the timestamp.
Fixes:
Script converter: - Bug 801 - Commented lines remain commented following
conversion.
Script converter: - Bug 802 - The "Open VisuView in foreground" (from Pro fiSig nal
Version V1.50) is now correctly converted.
Trend: - YT diagram, logic diagram: Dialog to generate a time axis via a context
menu or double click on the axis.
Script: - Error rectified for running an external program.
-----------------------------------------------------------------------------------------------------
Updates in Version 2.00

Script language (for Pro fiSig nal Klicks only)
Complete revision of the script language with rearrangement of instructions.
New instructions to convert variable types (Script/Assign/Type/..).
New instruction to evaluate/inspect string variables(Script/Assign/String/..).
New instruction to start external applications (Script/Initiate/Pro fiSig nal/Run
external program)
New objects

May 2011
67
FFT diagram visualisation object (only for the optional vibration analysis module)
Orbit diagram visualisation object (only for the optional vibration analysis module)
Logic diagram visualisation object for analysing binary signals
Turntable visualisation object - Analog instrument with displayable limits.
Current file name report object.
3D tables in application data and as a local variable within a script (Pro fiSig nal
Klicks only)
Upgraded functioning:
Copy application - An entire application can now be copied in development mode.
Time zone settings - The timezone can be selected in the general settings. The
available zones are local (PC) and device or UTC time. The timezone setting may
also be amended in the trend analysis and ASCII export.
Report visualisation object - The object was upgraded to enable the report to be
printed or displayed without a script.
Picture visualisation object - A picture can now also be used as a borderless and
flat element.
Amendments:
Additional tabs in the VisuView toolbar - The Visuview toolbar has been extended
with a recorder tab and several types of diagram.
Analysis dialog - An extra diagram-type dialog is now available when opening a
measurement data file for analysis.
ASCII export - A millisecond time range is now also available for equidistant exports.
A separate column can now be selected for the millisecond section of the timestamp.
-----------------------------------------------------------------------------------------------------
Updates in Version 1.51

Windows file links
The following files types can be opened automatically in Pro fiSig nal by double clicking
them in the Windows file explorer:
*.dpa
Pro fiSig nal project file
*.drp
Pro fiSig nal report file
*.hds
Pro fiSig nal measurement data file
*.tcg
Pro fiSig nal trend configuration
*.mes
Delphin MHouse data file
68

May 2011
English help installed

Report file format revised
Report files (*.drp) no longer uses the 'Borland Database Engine (BDE)' database. The
files now use their own format.
The reason for this is that BDE is used in conjunction with other programs. Problems
occurred in the past when the other programs altered the BDE settings or when
deinstallation routines completely deleted the BDE. Report files that have been created
in Pro fiSig nal V.1.50 and older are automatically converted to a new format. This
requires the report converter to be installed. This is installed automatically when updating
older Pro fiSig nal versions providing the report feature was selected in the older versions.
Start menu entries
New sub menu Pro fiSig nal/Extras. This contains the existing program link 'HDB converter'
and a new link 'Report Converter'. The report converter converts report files from version
1.50 and earlier into the the new format and vice versa. Type *.rep report files require
renaming as *.drp files beforehand. Open an older *.drp or *.rep file directly in
A range of improvements to details in the trend visualisation object and the analysis
trend (open HDS files).
The omission of watch and size mode will be noticed by the user. The trend state that
was accessed in older versions via the watch mode context menu' is now accessed via
the standard configuration context menu.
New visualisation object YX graphic (measurement device)
-----------------------------------------------------------------------------------------------------

Version 2.2
New functions
Automatic backup function for online and scheduler databases
AlarmManager: Actions can be triggered during ongoing alarms and the confirmation
of alarms.
Improved recording of measurement data with high sampling rates.
Registering the DataService as a service
Error rectified

May 2011
69
Version 2.1
New functions
AlarmManager
User management
OPC server (robuster)
OPC Client - synchronized poll mode - browser filter added
ProfiMessage drivers extended
Improved cooperation with PowerManagment
Data folders from setup
Improved storage management
Error rectified
ProfiSignal software
Overview
The Delphin Manual is split into three main sections plus an appendix:
Section 1, Introduction, gives information on using this manual as well information on other
user tools.
There is also cross-module information on setting up user accounts, password protection
and licensing.
Section 2, DataService Configurator, concerns Delphin software that establishes links

between PCs and measurement hardware.
Section 3, ProfiSignal, contains information on Delphin's modular developmental system

for measurement data acquisition and evaluation.
70

May 2011

All content, in particular the text, images and graphics, are copyright protected.
Further information is available on the Product information page.

May 2011
71
2.1
Installation
Install the ProfiSignal CD.

Place the enclosed CD in your CD / DVD drive. Setup normally then runs automatically.
If this does not happen, run the Setup.exe file from the ProfiSignal CD.
Setup takes you step by step through the PC-software installation.
Following installation, these icons will appear on the screen:
The DataService Configurator is a device driver and tool for configuring the Delphin
devices (settings for sensor / actuator connections)
ProfiSignal is software for evaluating and visualizing measurement data.
Data folders/directories
During installation, setup requires input of the folder/directory for ProfiSignal data files.
For multi-user mode (license option), the "My documents" folder is required. ProfiSignal will
not run in multi-user mode if a different folder is selected (irrespective of license options).
72

May 2011
Note: The selected folder can not subsequently be altered!
System requirements
The following hardware requirements are the minimum requirements to ensure problem-free
operation of Delphin products.
Operating system
Microsoft Windows Vista, Windows 7, Windows 8 and Windows Server 2008 R2 the
the 32-bit or 64-bit versions
in either English or German. The 64-bit version is recommended.
Main memory
at least 2 GB*,
recommended: 3 GB for 32-bit systems, 8 GB for 64-bit-systems

May 2011
73
Monitor
a resolution of at least 1024 x 768 pixels, fixed font size at 96 dpi (100%)
CPU
PC with at least a dual-core 2 GHz* processor
recommended: 4-core processor from 3 GHz
Hard drive
forPro fiSig nal-Go at least 150 MB free space
forPro fiSig nal-Vie we r at least 150 MB free space
forPro fiSig nal-Klicks at least 1000 MB free space
for otherPro fiSig nal versions at least 500 MB free space
Info: Recommendations for continuous operation
74

May 2011
2.2
Introduction
The introduction section contains important information for users on operating Delphin
products and how users can access direct systems of help.
The following pages contain information that is applicable for all modules. This includes
system requirements as well as safety and product information.
There are two concluding sub-sections on password protection and licensing.
Documentation and online help

Delphin's hardware and software products combine optimally to meet requirements in
measurement data acquisition, visualization and analysis, or for control and test stand
systems.
The aim of this documentation and online help system is to enable users to quickly
commence working with the Delphin modules irrespective of prior knowledge, field of work
or industry.
The documentation and online help system is also intended to provide answers to specific
queries that may arise during operation of the Delphin hardware and software and also to
provide suggestions on extending and enhancing user systems.
Where can I find help and information?

There are several options for obtaining information:
1. Become familiar with this documentation. This does not require the user to read the
complete text from beginning to end
but can be achieved by using the sidebar, located on the left of the screen, that provides
a structure of the whole document. Select the required theme and follow the links.
2. Access the online help using the help menu option or press the F1 key within an
application to access context-sensitive help. This takes users the appropriate part of the
documentation from anywhere in the Pro fiSig nal or DataSe rv ice software.
The Help button on any user dialog gives direct access to the appropriate section of the
documentation.
3. There is a documentation folder located in the users ProfiSignal installation path (e.g.
C:\Programme\ProfiSignal). This contains a range of PDF files - irrespective of the modules
being used - that contain detailed information on each basis module.
Online help
There is a Help option on the main menu bar for DataSe rv ice Co nfig urato r or Pro fiSig nal
to access the online help system.

May 2011
75
The Help option in the DataSe rv ice Co nfig urato r contains the usual index and search
functions for online help.
For those users who are unfamiliar with online help systems, there is also an option to
access Windows general explanation of online help systems.
The Help option in Pro fiSig nal is similar.

In both cases, this options also gives access to the licensing settings which are explained
in the following section.
76

May 2011
2.2.1
System requirements
This page provides information on the minimum system requirements for write permissions
and hardware equipment to enable secure operation of Delphin's modules.
Rights and permissions

To run Pro fiSig nal, write permissions are required to the COMMON_APPDATA folder.
Depending on the installation options selected, write permissions may also be required to
COMMON_DOCUMENTS, APPDATA, PERSONAL as well as to the installation folder.
The exact location of the standard directory is system dependent. For the user group, the
required permissions are given in set up during installation.
Further information is available from your system administrator.
Hardware requirements
Operating system
Main memory
at least 2 GB*,
Monitor
CPU
Hard drive
Info:

May 2011
77
Be aware that additional storage memory is required for the measurement data. For a
measurement data server we recommend 200 GB of free storage space, but 10 GB is
sufficient.
* Minimum requirements can be greater depending on the operating system being used and
the number / resolution of data channels.
78

May 2011
2.2.2
Recommendations for continuous operation
This page provides recommendations on how to achieve as trouble-free operation as

possible for Delphin products even under continuous operation.
These recommendations are listed under the following packages of measures:
Extended hardware requirements
Measures to enhance system availability
Measures to enhance data security
Measures to enable the early detection of faults
Measures to optimize performance in reading out/ portraying data
Recommendations for the continuous operation of ProfiSignal

A normal Windows PC is in principle unable to provide 100% availability (fail safe
performance) - the Windows operating system does not provide redundant hardware
building blocks nor support for hardware redundancy.
One or more system failures per year are probably therefore unavoidable.
To minimize data loss due to system failure, and using the currently available technology,
we recommend the following.
Extended hardware requirements

ECC memory (Error Correction Code).
PC main memory is usually made up of DRAM memory. Statistically, bit errors can
occur in DRAM within days. Each bit error can distort data and over the long term
may result in unexpected and serious software or system errors.
ECC memories detect and correct bit errors.
Server / Workstation
System security and availability can be enhanced by using special server and
workstation hardware (e.g. Intel Xeon or AMD Opteron systems) instead of regular
desktop PC hardware.
Measures to enhance system availability

Ideally users should operate Delphin measurement software on a dedicated PC within
a separate and enclosed data network.
Do not use other applications (e.g. MS Office) on the PC running the measurement
data software.
Use UPS systems (uninterrupted power supply).
When the measurement software requires integration into a network, avoid using
automatic update features (e.g. Windows updates) and any other feature that runs

May 2011
79
as a hidden program. If the PC belongs to a domain, it is also subject to the update

of rules via the server (e.g. policies, firewall).
When updates are required, run these manually and perform a restart following the
update.
Check that the system runs error-free and monitor its performance over the following
days. If an error then occurs, the update associated with the error is then known.
Network connections are generally unable to guarantee 100% availability. Therefore
never store data directly to a network drive because even a brief interruption in the
network connection can lead to data loss.
Avoid using virus scanners and firewall software on the measurement software PC.
For security do the following instead:
o Limit users rights by permitting only those users who are absolutely necessary.
o When a Pro fiSig nal application is inactive, log out the current user and lock out
the PC once all the necessary tasks have been completed.
o Use hardware firewalls.
Info:
To enhance availability when the PC is being used as a measurement data server, it is
recommended to run the DataService as a Windows service (refer also to Installing the
DataService as a service). Consider setting up a redundant secondary system.
Measures to enhance data security

Copy measurement and project data to a file server on a cyclical basis.
For measurement databases, use the DataSe rv ice backup function. Information on
database backups is available under the sections Adding measurement database,
Backup tab as well as DB backup in the Delphin manual.
As an alternative regular backups can be made to volumes or other type of media.
Use at least 2 hard drives for storing data in RAID 1, 10 or 5 configurations.
RAID 0 decreases data security!
Use UPS (uninterrupted power supply).
Increase hard drive capacities before the drives are full.
Measures to enable the early detection of faults

Have the PC checked regularly for error-free functioning (important information here
includes alarm list analysis).
When using the Scheduler select an interval that gives enough time to rectify the
occurrence of a failure (installing a new PC in a worst case scenario).
There is a risk of data loss when a re-read of data from a Message device takes
80

May 2011
place only after the data has been overwritten in the ring memory.
Automate monitoring. The TopMessage(LogMessage) devices and ProfiSignal can be
configured so that emails can be sent automatically when a fault occurs.
Measures to optimize performance in reading out/ portraying data

Perform a regular manual defragmentation of the hard disk(s) (e.g. 1x per month) and
then check the system status.
The disk drive(s) should have at least 25% free capacity.
When using a data server:
o For Microsoft Windows Vista or Windows 7, use the 64bit version with 4 or 8 GB of
memory. Set the maximum possible cache size for the DataSe rv ice .
o The PC's maximum CPU load, when not performing read-outs, should not exceed
10%. If higher loads do occur when saving data, storage should be spread over
multiple servers.

May 2011
81
2.2.3
Multi-user mode
The multi-user mode (license option) enables Pro fiSig nal to be run in parallel (in different
sessions).
Requirements:
Pro fiSig nal installation with a Pro fiSig nal license that includes the multi-user option.
This option can not be added once Pro fiSig nal is installed.
Pro fiSig nal installation uses the "My Documents" folder.
The Pro fiSig nal system requirements apply for each session being run.
Features of multi-user mode:

If Pro fiSig nal is installed as a multi-user system, a centralized DataSe rv ice is installed as
a service. This service is required for operation and may not be deactivated.
Multi-user mode enables any number of users to run Pro fiSig nal. Parallel sessions of
Pro fiSig nal is restricted to the maximum number stated in the licence.
Expert Key devices that are connected via a USB are always assigned to the central
DataSe rv ice service. Measurement data can be transferred to individual sessions via a
DataService connection to a central service.
Recommended settings following installation

The default setting for the central DataSe rv ice is port 3636 and can be configured in any
session using the DataSe rv ice Co nfig urato r.
We recommend enabling the User management function in the central DataSe rv ice .
Configuring the central DataService

To configure the central DataSe rv ice , start the DataSe rv ice Co nfig urato r and use
Menu bar, Connect
Configure remote DataService
New connection
to establish a connection to the "Localhost" with the port "3636".
82

May 2011

May 2011
83
2.2.4
Safety Advice
Please take note of the following safety advice.

This will protect both yourself and your equipment:
1.Switch off the power supply before working on any electrical parts high voltages can
kill!
2.A maximum of 36V control voltage only should be attached to the Message device
input terminals.
Installation should only be carried out by trained personnel. Unintentional contact with
live components at voltages greater than 40 V can kill.
3.Transverse voltages, which occur between signal lines, can also endanger life.
4.Electronic components are sensitive to electrostatic charge. To prevent damage to the
devices, discharge any electrostatic before touching circuit boards or components.
We recommend the wearing of a static discharge wristband.
5.Ensure that signal lines are correctly connected to the screw terminals.
6.Use only appropriate tools for opening the device.
7.Switching off the power will interrupt data transmission this may lead to a loss of
data.
84

May 2011
2.2.5
Product information
Software:
Pro fiSig nal
Version:
3.0.0
Technical standpoint: January 2011
Copyright 2003-2014 Delphin Technology AG

All documentation, especially text, images and graphics, is copyright protected also when
used as part of the online help. The copyright belongs to (when not otherwise stated):
Delphin Technology AG
Lustheide 81
51427 Bergisch Gladbach (Refrath), Germany
Germany
Tel.: +49 2204 97685 -0
Fax: +49 2204 97685 -85
Email: info@delphin.de
Web: http://www.delphin.de/
Declaration of conformity
Compliance to EU directives
When used as intended, the product complies
to the declaration of conformity as set out in
European directives.
Certification
is certified according to ISO 9001.

May 2011
85
86

May 2011
2.2.6
Password protected
This section describes the general use of password protection to secure Pro fiSig nal
applications.
The following sections provide information on the system of password protection for
Pro fiSig nal- users:
User login
Changing passwords
Settings for password protection
General password protection

The general password protection for Pro fiSig nal provides an optimal access system
requiring user authentication to gain entry to the Pro fiSig nal software. In contrast to the
project specific password protection, general password protection applies to all licenced
Pro fiSig nal functions.
To use the password protection system firstly requires an Administrator to set up user
accounts in DataSe rv ice Co nfig urato r for all users required to provide authentication.
Setting up user accounts is described in the User management section under Add users.
General password protection is also set up in DataSe rv ice Co nfig urato r. This set up, and
the protection categories, is explained in the User management section under Password
protection settings.
2.2.6.1 User login

After general password protection has been enabled in DataSe rv ice Co nfig urato r, each
user must then log in prior to using the Pro fiSig nal or DataSe rv ice Co nfig urato r-software.
The Protection main menu option is visible only when password protection is enabled in
DataSe rv ice Co nfig urato r.
The various login procedures are described in the following:
Login to the ProfiSignal development mode
Login to the DataService Configurator
Auto login
Login to ProfiSignal's development mode

Menu bar, Protection
In edit mode, ProfiSignal's functionality is restricted to this option until the required login
has been successful. Only the options Protection and Help are enabled and only the Project

May 2011
87
and Application names available for login are visible in the management tree. In runtime
mode, the visualization views are also available.
Info:
When the Protection option is not displayed, the Pro fiSig nal application is operating without
password protection. In this event no login is required.
If, however, you require password protection, refer either to your system administrator or
section 2 ("DataService Configurator") under User management, on how to Set up password
protection.
In both runtime and edit modes, login takes place via the main menu Protection option.
Login may take place via the Login option from the submenu or by CTRL+ALT+L.
This opens a login dialog to enter username and password and then Login.
88

May 2011
The software functions are accessible once the system has accepted the password, with
the username then appearing in the program's title bar.
Login to DataService Configurator

In the DataSe rv ice Co nfig urato r, the login dialog appears at the first attempt at a
connection.
If you have set the DataSe rv ice Co nfig urato r to connect automatically, the login dialog
appears immediately following the start of the application.
To set the DataSe rv ice Co nfig urato r to automatically connect DataSe rv ice , refer to the
section on automatically connecting the DataService.
Auto login
The Auto login option is available under Protection (in Pro fiSig nal) or. Login (in
DataSe rv ice Co nfig urato r).
Enable this option for the system to automatically detect and login the current Windows
user (refer to add user in the DataSe rv ice Co nfig urato r documentation). Users may wish
to use Auto login when running Pro fiSig nal' or for manual user logouts.

May 2011
89
2.2.6.2 Changing passwords

When setting up a user in the DataSe rv ice Co nfig urato r, the Administrator determines the
first password to be used.
This password usually requires amending at the first login. To open the dialog for amending
the password:
Main menu option Login
Change password
or
Main menu option Protection
Change password
When the Administrator requests a compulsory password change or the user wishes to
amend a password, the dialog can be accessed in DataSe rv ice Co nfig urato r via Login |
Change password, and in Pro fiSig nal applications via Protection | Change password.
If the Change password option is grayed-out, refer to your system administrator who can
then give you the permissions required to change passwords.
When you have the permissions to make password changes, enter your current password
into the first line of the dialog. If you have been using the system without password
protection, leave this field empty.
Enter your new password in the second line and repeat its entry in the third line.
After clicking OK, the new password is first checked for validity (refer to the section on
password protection settings ) and then amend. Only then is the new password valid.
Your administrator can inform you of the requirements for a valid password, e.g. the
required and permitted length, letters, upper and lower case letters, numbers and symbols.
90

May 2011
2.2.6.3 Settings for password protection
In many cases password protection makes sense only when accompanied by other security
measures. These other measures prevent unauthorized users from evading the password
system.
main menu Protection
Settings
When you login as Administrator or as a Configurator user group member the Protection
settings dialog is accessible from the Pro fiSig nallProtection| Settings options. This dialog can
be used to disable Windows keys and key combinations that might interfere with the
Pro fiSig nal application.
Settings for password protection dialog

Key control (area)
o Hide Windows taskbar (checkbox)
This hides the Windows taskbar when Pro fiSig nal starts. When Pro fiSig nal is running
and no authorized user is logged in, the Windows taskbar is not accessible.

May 2011
91
o Lock windowskeys (checkbox)

This locks the Windows key combinations for non-authorized users. The keys
affected are listed in the Windows key combinations page.
o Lock Ctrl+ Alt + Del (checkbox)
This option is available only when the dwlGina3.dll file is installed. Installation of this
file is available under dwlGina3.dll installation.
When activated, the Ctrl+ Alt + Del combination is unavailable for non-authorized
users.
Info:
Disabling Ctrl + Alt + Del also locks running of the Windows task manager.
dwlGina3.dll installation (area)

To disable the Ctrl + Alt + Del combination requires installation of the dwlGina3.dll
file. Using this dll enables any key input to be detected and checked.
Info:
The dwlkbf.sys file is installed as an additional file under Windows XP and Windows Vista.
o Install dwlGina3.dll (button)

This starts the dwlGina3.dll installation. The installation requires confirmation. A
Windows restart is also required following installation. Users are informed of this via a
message window.
When dwlGina3.dll already exists, the dwlGina3.dll area appears with a deinstallation
button.
92

May 2011
2.2.6.3.1 Windows key combinations
Main menu Protection
Settings
The Lock windowskeys option disables all combinations using the CTRL, ALT, WINDOWS
keys.
Key combination
ALT + xxx
CTRL + xxx
WINDOWS + xxx
CTRL + ALT + xxx
CTRL + WINDOWS + xxx
CTRL + ALT + WINDOWS + xxx
ALT + Shift + xxx
CTRL + Shift + xxx
WINDOWS + Shift + xxx
CTRL + ALT + Shift + xxx
CTRL + WINDOWS + Shift + xxx
CTRL + ALT + WINDOWS + Shift + xxx
Key combinations in ProfiSignal

May 2011
93
Key combination
Purpose
1)
CTRL+ALT+L
Opens the ProfiSignal login dialog. This

combination is always available.
CTRL+Alt+E
End application runtime.
F12
Show/hide management tree
CTRL+F12
Show/hide Log window
CTRL+ALT+M
Switches between the ProfiSignal modes

standard and extended.
2)
3)
Key combinations in ModuleView

CTRL+ C,V,X
Copies, pastes, cuts selected modules
DEL
Deletes selected modules
Shift+DEL
Deletes connection
CTRL+DEL
Delete loop
F4
Open script window for the selected module
Key combinations for the Script window

CTRL+ C,V,X
Copies, pastes, cuts selected lines
DEL
Deletes selected lines
CTRL+Z
Undoes the previous script change
CTRL+Shift+Z
Restores the previous undone change
CTRL+F2
Activate/deactivate line
CTRL+ALT+H
Display hierarchy yes/no
Key combinations for the VisuView

CTRL+ C,V
Copy, paste selected visualization objects
DEL
Deletes selected objects
CTRL+G
Group selected visualization objects
CTRL+Shift+G
Undo group
ESC
Switches off full screen mode in VisuView
94

May 2011
Key combination
Purpose
1)
F11
Switches on/off full screen mode in VisuView
2)
3)
Key combinations for the ParameterView

CTRL+ C,V
Copy, paste selected parameter objects
DEL
Deletes selected parameter objects
Key combinations for Window management

CTRL+P
Switches between projects or to the project

area
CTRL+N
Switches to the last active VisuView
CTRL+W
Browses through windows
CTRL+R
Switches to report area
CTRL+T
Switches to analyse area
1)
When the Lock windowskeys option is enabled, these key combinations are available
only to users with administrator and configurator permissions.
2)
When the Lock windowskeys option is enabled, these key combinations are available
only to users with administrator and configurator permissions.
3)
This key combination is available in development mode only to users with
configurator permissions.
2.2.6.4 User Rights
User Rights
Administrators
DataProfiEvalService
Signal
Oper- Obser
uatConfigu- Configuator
v-er
or
rators
rators
ProfiSignal
Exit ProfiSignal
Main Menu File/Exit
Main window button
Windows taskbar

May 2011
95
Administrators
User Rights
Signal
Oper- Obser
v-er
or
rators
rators
Option to hide Windows taskbar is

enabled.
ProfiSignal keys for process
control
x
ProfiSignal keys for windows and

project management
Change rights/permissions Password protection settings
Change rights/permissions in
project
Option to lock Windows keys is

enabled.
Project options
Change general ProfiSignal
settings
Analysis
(Evaluate data, ASCII export)

Online analysis
Reading device memory
Report observing
Global alarm lists
Load project
Start application
End run
Development mode
Set up / amend project etc..

DataService Configurator
User management
Configure DataService
96

May 2011
User Rights

May 2011
Administrators
Signal
Oper- Obser
v-er
or
rators
rators
97
2.2.7
Licensing
This section informs you what to be aware of in licensing.

The section is divided as follows:
Licensing models
How do I find information about my licence
Activate and extend licence
Exchange and deactivate licence
Licensing models
Pro fiSig nal is offered in versions that differ according to functioning. The functions
available under Pro fiSig nal products can be extended by acquiring additional modules.
The following table shows the Pro fiSig nal versions and their extensions.
Module / Product
Report Viewer
Viewer
Basic1)
Klicks1)
Runtime
Basic
Runtime
Klicks
X
X
Report Designer
Analysis
Online analysis
Reading device memory
Run project/application
(without script language)
Run project/application
(with script language)
Develop project/application
(without script language)
Develop project/application
(with script language)
Vibration analysis 2)
Alarm management 2)
Audit trail 2)
ASCII import 2)
SQL-ODBC
2)
2)
1)
Extended module
98
Go
Channel restriction possible

May 2011
The DataSe rv ice , required for everyPro fiSig nal version, uses the same licence that you
receive for your Pro fiSig nal product.
The DataSe rv ice can also be extended with separate licence extensions. The following
modules are available:
o OCX device divers
o ProfiSignal-OCX (for 25 or 250 or unlimited numbers of channels)
o OPC server
o OPC client (for 25 or 250 or unlimited numbers of channels)
o Translation module
How do I find information about my licence

The licensing file is supplied together with the Delphin software modules. The licensing file
contains information on the product and extensions that you have purchased.
This information can be displayed by clicking Edit licence under the help option.
This opens the Edit licence dialog.

May 2011
99
The dialog displays the following information:

Manufacturer (text field)
Delphin Technology AG appears here as manufacturer of the Pro fiSig nalproduct.
Licenced for (text field)
The named person as licence holder for the Pro fiSig nal product.
Module (area)
There is a tree structure in the center showing the enabled products and extension
modules. Information about the licence is provide for each module, e.g. whether it
is a demo version or whether activation is required.
o Show activation keys (checkbox)
Whether the activation keys entered so far are to be shown. Enable Show
activation keys to display the activation keys.
Licence information area
The five rows on the upper right are text fields containing licence information.
These are:
100

May 2011
o Order No. (Delphin's order number for the licence file)

o Licence File ID(The unique ID for this licence file)
o Licence version (The licence file version number)
o Licence date (The date the licence file was created)
o Update until: The cut-off date for uploading free-of-charge for Pro fiSig nal.
Installationscodes (area)
The hexadecimal values in the text fields Code 01 to Code 12 are generated at
installation. They are dependent on the hardware parameters from the computer on
which the product is installed.
o Copy codes (button)
Copies the code text fields to the clipboard. This might be required, for example,
when amending licences.
The following values are copied:
Apply activation key (area)

The Enter Activation Code(s) button is enabled when a code is to be entered.
Enter the code/key and click the button. An window will appear indicating whether
the entered code/key is correct. The licenced product is then available following a
restart.
Further information on the different methods of activation is available under
Activate and extend licence.
Lower part of the Edit licence dialog
The lower part of the dialog contains activation buttons for the different methods
of activation
(Online activation, Telephone activation, Email activation and Fax
activation) as well as the Help and Close button.

May 2011
101
Once activated, these buttons disappear and are replaced by a Deactivate button.
This is required, for example, to change a licence.
2.2.7.1 Activate and extend licence

This section provides information on when and how to activate, extend or change a user
licence for Pro fiSig nal products.
The section is structured as follows:
Licence and activation key
Demo version
Activating ProfiSignal versions
o Online activation
o Telephone activation
o Fax activation
o Email activation
o Entering an activation key/code
Licence and activation key

A licence file is provided with the Delphin software. The licence is necessary to use the
required Pro fiSig nal functions.
The licence is made up of different types of information and is stored to a licence.lic file.
The licence comprises customer information (such as the licence holders order number) and
product information (such as product version and extensions).
Pro fiSig nal can be started without a licence but then only as a trial version without full
functionality.
The activation key is used to activate or amend an existing licence. The key is usually
needed following installation of a Pro fiSig nal product or when new functions are added.
Note:
It is not possible to use a key to amend a Pro fiSig nal version. A new licence is
required for a version change. If users attempt to enter a key for a different
Pro fiSig nal version, an error message will be displayed indicating that the key does
match the licence.
102

May 2011
Demo version
When users wish to test a Delphin's software using a Pro fiSig nal demo version, they
receive a licence file for a demo version. This file includes the modules required for testing
and stipulates a restricted runtime period.
A Pro fiSig nal demo version licence does not require activation.
It may be necessary though to request a new key from Delphin Technology AG, e.g. to
extend the test period. This key requires entering to enable further testing.
ProfiSignal version activation

ProfiSignal usually requires activating with a licence. Whether this is the case will become
apparent at program start. If the message Activation required appears in the title banner of
the main Pro fiSig nal menu, or the following message is displayed, an activation is
required.
An activation is required within 30 days from installation. If this time period is overrun,
Pro fiSig nal will not run but activation can still be performed.
Licence management is performed via the Mirage W e b A pplicatio n Se rv e r.
Delphin offers different methods for activating a Pro fiSig nal product:
Online activation
Telephone activation
Fax activation
Email activation
Online activation
Automatic online activation is the simplest method when the PC, on which Pro fiSig nal is
installed, has an internet connection. No further input is required for online activation.
To start online activation click online activation in the lower part of the Edit licence dialog.
When the Web Activation dialog appears, activation will then begin on clicking Activate
now! .

May 2011
103
The required data concerning Pro fiSig nal version, licence holder and hardware parameters
is transmitted to the server. An activation key is generated and transmitted to the PC.
The product then automatically activates.
When the Pro fiSig nal PC has no internet connection, activation can take place using
telephone, fax or email methods.
Telephone activation
To start activation click telephone activation in the lower part of the Edit licence dialog. An
info window appears with a telephone number with which to contact Delphin Technology
AG for activation.
To proceed with telephone activation you require information from the Edit licence dialog
window. You will then receive an activation key.
To enter the activation key, refer to Apply activation key .
Fax activation
To start activation click fax activation in the lower part of the Edit licence dialog. A window
appears to enter your name (as licence holder) and options for sending the activation key
(telephone number, fax number or email address).
104

May 2011
Confirm with a left click on the Confirm button.

A printer is then selected via the Windows printer dialog for printing the fax response
shown below.

May 2011
105
Send this fax to Delphin Technology AG using the number given. The user then receives
the activation key via the method requested.
Email activation
To start activation click email activation in the lower part of the Edit licence dialog. This
opens a window similar to that for fax activation. A window appears to enter your name (as
licence holder) and options for sending the activation key (telephone number, fax number
or email address). Confirm with a left click on the Confirm button.
106

May 2011
Depending on your email program settings, an automatic email connection then takes place
as shown here for Microsoft-Outlook.
Confirm with yes. You will then receive the activation key via the method requested.
Entering an activation key/code

You have received one or more activation keys via telephone, email or fax.
Enter the key - use copy&paste to avoid typing errors - in the input field of the the Apply
activation key area.
Separate multiple keys with a semi colon.
An activation key is made up of six 5-digit alphanumeric blocks separated by hyphens. Be

aware of upper and lower case letters.
After entering the activation key click apply activation key.
The following window appears when activation is successful:
End the Pro fiSig nal application. All licensed functions are then available following a restart
of Pro fiSig nal.

May 2011
107
Note:
ProfiSignal closes automatically on first activation when a restart has been
confirmed.
2.2.7.2 Change and deactivate licence

There are options to change or deactivate a licence.
Select Change licence from the Edit menu.
This opens the Change licence dialog that contains all the relevant information for changing
a licence file. Select the new licence.lic file using the browse button and click Change
licence.
Restart ProfiSignal to accept the new licence information.
Deactivate licence
As explained in Edit licence, the activate button changes to deactivate following
activation
Click deactivate to deactivate the licence without installing a new licence.
108

May 2011

May 2011
109
2.3
The DataService Configurator from Delphin functions as a link between the PC, e.g. on
which ProfiSignal is installed, and measurement hardware.
The DataSe rv ice transmits channel data from the connected measurement hardware to
Pro fiSig nal.
Delphin hardware is configured using DataService Configurator. This means the
configurator for the T o pMe ssag e devices can be run directly from the DataService
Configurator . Devices from the new Lo g -/ Pro fiMe ssag e generation are immediately
configured in the DataSe rv ice Co nfig urato r.
The DataService Configurator is also used to set up databases to enable permanent and
high resolution data storage over long time periods. The volume of stored data then
depends solely on the capacity of the hard drive.
Users have immediate access to databases once the measurement channels are being
displayed in trend (Yt) diagrams.
DataService Configurator sections:
Main menu
o Connect
o Login
o View
o Options
o Help
Connections option
o TopMessage connection
o Log-/ProfiMessage connection
o DataService connection
o OPC Client
o Other connections
Channels option
o Log-/ProfiMessage device configuration
o TopMessage device configuration
o OPC channels configuration
Database option
o Adding measurement database
110

May 2011
Scheduler option
o General tab
o Read memory tab
Alerting
o General settings
o Alarm class settings
o Alarm rule settings
o Action settings
User management
o Password protection settings
o Add users
o Add groups
o Lock user
Firmware update

May 2011
111
2.3.1
DataService as a Windows service
Set up
The DataService can be run as a Windows service. This enables the continuous recording
of measurement data without users having to login or ProfiSignal having to run.
Select
Install DataService as service
Permitting network shares

The DataService is run as a service after installation under the local system account user.
This account basically has permissions for shares within the network but does not normally
have specific permissions to specific network shares.
Every computer within a domain, as with every user within a domain, receives an account
within the domain. When the service starts under the local system account user, access
to the network takes place via the account of the active computer on which the service
is running.
112

May 2011
To enable the service to have permissions to network shares, it is necessary to add the
computer's account to the authorized user group on the server.
It is recommended to give access rights to the computer.
Alternatively, there is the option to run the service under a different authorized user
account.
Select Control panel
Administrative Tools
Services
Delphin DataService
Accessing local user files

Access to local files is with the permissions from the account being used. This means that
access to, for example, files under My files or those on the Desktop of the logged in user, is
only possible with the standard local system account.

May 2011
113
Info:
If you are unable to open data files within specific directories, check the service
permissions to these directories.
Further information on permissions can be obtained from your system administrator.
114

May 2011
2.3.2
Main menu
The DataService Configurator main menu has the following options:

o Connect
o Login (only with Password protection settings)
o View
o Options
o Help
Without password protection, the Login option does not appear in the DataService Configurator main
menu
2.3.2.1 Connect
Main menu
Connect
The Connect main menu contains:
Configure local DataService

Disconnect from DataService
Automatic connect DataService
Add driver (connection)
Start local DataService
Stop local DataService
This section describes the options under the main menu's Connect tab - with the exception
of Add driver (connection).
The Add driver (connection) is described for each device under the Connections option (for
a TopMessage connection, Log-/ProfiMessage connection, DataService connection, OPC
Client or a DataTranslation driver ).

May 2011
115
Info:
If you establish a connection via the main menu, it will be assigned to the local
DataSe rv ice . The connection will be assigned to the DataSe rv ice whose context menu
is being used.
The main menu option Connect enables management of the DataSe rv ice irrespective of
whether the DataService is running locally on a PC or on other equipment across a network.
When there are no connections to the DataSe rv ice , all devices are disabled and are
grayed-out. View and Options are then also disabled.
Configure local DataService

Left clicking the Configure local DataService establishes a DataSe rv ice connection and
enables the device entries for which a functioning connection exists.
116

May 2011
The connection process displays the message Wait... Connecting to DataService at....
WhichDataSe rv ice is being connected is also displayed. The IP address 127.0.0.1 stands
fro the local DataSe rv ice
Following successful connection, the accessible devices are portrayed in black type.
Portrayal in red type indicates a faulty or non connection.
If the connection process is taking too long, a time out will occur. Users can however
manually abort a connection process prior to an automatic time out by clicking Abort. In
any event, checking the network and device connections as well as the DataSe rv ice
software is recommended.
Disconnect from DataService

Existing DataSe rv ice connections can be disconnected by left clicking the Disconnect from
DataService option.

May 2011
117
Users can also stop or start a local DataService. One of the the two options will always
be disabled depending on the actual status of the DataService.
Automatic connect DataService

The Automatic connect DataService option enables a DataService Configurator
connection to take place immediately at the restart of a localDataService. A tick against
this option in the context menu shows that it has been selected.
If this option has not been selected, users must perform a manual DataSe rv ice co nne ctio n
e ach time the DataService Configurator starts.

The Configure remote DataService option enables users to select between previous
connections (in this example the local DataService, 127.0.0.1) and a connection to other
DataServices available within the network.
118

May 2011
To establish a new connection to a DataSe rv ice within the network, click New connection.
This opens the Connect DataService over network dialogue. Connections installed then
appear under the Configure remote DataService option.
The General tab
Host (text field)

May 2011
119
Enter the IP address of the equipment on which the DataService is running and to
which a connection is to be established.
Port (text field)
Enter the port over which the connection is to be established. The default is 3737.
Change this only when the port in your network is already being used by other
applications.
Connection (dropdown list)
Select the communication route over which the connection is to be established when
multiple network cards are available.
Username (text field)
When the DataService Configurator's password protection is activated, enter the
username from the user login.
Password (text field)
When the DataService Configurator's password protection is activated, enter the
password from the user login.
OK button
Clicking OK establishes the external DataSe rv ice connection.
2.3.2.2 Login
Main menu
Login
The main menu's Login has the following options:

Login
Logout
Change password
Auto login
To benefit from the login functions, users need to activate the password protection in the
User management. Setting up password protection is explained in the section Password
protection settings.
Enabling password protection then requires users to login prior to using the software. Login
takes place via the Login option in the main menu Login.
120

May 2011
Login
Left clicking Login displays the Login window.
Enter your user name and password and confirm by clicking the Login button.
Info:
When setting up a user, the administrator allocates the initial password (refer to the Add
users) section. The user must amend the initial password at the first login.
Logout
Left clicking Logout logs out the currently logged in user. The program is then locked until

May 2011
121
the user's next login.
Info:
When Auto login is enabled, an attempt will be made to login the current Windows user
on logout.
Change password
Left clicking the Change password option opens the Change password window.
To change the password, enter the currently valid (old) password and the new password.
To avoid erroneous input, a repeat entry of the new password is required (Confirm new
password).
Click OK to confirm the change.
The new password is then checked against the password requirements set by the
administrator (refer to the Password protection settings section). As long as this check is
successful, the new password then becomes active and the old invalid.
Auto login
122

May 2011
If the Auto login is enabled, an attempt will be made at each program start or current user
logout, to detect and automatically login the current Windows user (refer to the Add users,
section, Corresponding Windows user).
2.3.2.3 View
Main menu
View
The main menu's View has the following options:

Left panel - View settings for the DataService Configurator's left panel.
Right panel - View settings for the DataService Configurator's right panel.
The left and right panels then have the following options:
o Visible connection sheet columns
o Visible channel sheet columns
o Channel sheet options
o Visible database sheet columns
o The right panel has an extra option, Invisible. This enables the entire right side to
be hidden. All settings then take place on the Left panel.
Displaying both left and right panels is practical when configuring different modes,
e.g. using drag and drop to link a channel from the channel view to a database in
the database view.
Timezone - to set the time-stamp for data and events for the DataService
Configurator.
Visible connection sheet columns

The DataService Configurator's Connections option displays a separate entry for each
configured device.
A tree structure portrays the hierarchical relationships and dependencies of the devices.
Users can see which device is assigned to which server and which server, or individual
device, is assigned to which DataSe rv ice .
The Visible connection sheet columns option enables users to define the columns to be
displayed for the different items of equipment. Left clicking one of the options either
displays (when previously not displayed) or hides (when previously displayed) the column
on the panel display. Selected columns are ticked in the corresponding context menu.
The column menu is also displayed by right clicking a column heading in the Connections
view.

May 2011
123
The Name column may not be hidden and shows either the equipment's IP address or the
name to which it has been assigned. Assigning a name to a T o pMe ssag e device is
described in the T o pMe ssag e Co nfig urato r manual. Configuring a Lo g -/ Pro fiMe ssag e
device is described in the Log-/ProfiMessage device channel configuration.
The following columns can be displayed in the Connections view:
Host/IP: The Host/IP column displays the IP address or host name for the device
displayed under the Name column.
Connect: The Connect column displays the current status of the connection.
State: The State column displays the actual state of the connection.
Driver type: The Driver type column displays the device type name that corresponds to
the driver being used.
Version: The Version column displays the driver software version.
Object-ID: The Object-ID column displays a unique ID for the equipment (hexadecimal
number).
Further information on the column entries is available in the Connections option section.
Visible channel sheet columns

The Channels option within the DataService Configurator is for displaying and configuring
devices, modules and channels.
Users are able to arrange the panel to their own needs (with the exception of the Channel
column, which is always the first column and may not be hidden).
The basic display options are described at the beginning of the Connections option section.
The Visible channel sheet columns option enables users to define the columns to be
displayed for the different devices. Left clicking one of the options either displays (when
previously not displayed) or hides (when previously displayed) the column on the panel
display. Selected columns are ticked in the corresponding context menu.
The column menu is also displayed by right clicking a column heading in the Connections
view.
124

May 2011
Bilder berprfen und Log-/ProfiMessage-Hinweise durch TopMessage ersetzen
Compared to the Connections option, the Channels option provides users with much more
sophisticated display arrangements as long as the User defined view option is selected
under Channel sheet options.
Select the Hardware defined view option first to obtain a clear tree structure at Interface
| Protocol | Channels or Module levels (from top to bottom).
Interfaces differ according to the Me ssag e device. Containers (such as memory or
software channels) are also assigned to this level.
The protocol level is a sub-level of interfaces in the hardware defined view of the Channel
column. An example is the assignment of a PROFIBUS protocol and the various PROFIBUS
channels to a COM interface.
Below the Ext. Bus interface with DCP protocol are the master Me ssag e device modules
as well as the connected slave devices. The separate hardware channels are then found
at one level lower to each module.
The software channels container may have additional containers (channel groups) as well
as separate software channels.

May 2011
125
The Channel column may not be hidden and shows either the name of the device, the
container, or the name assigned to the device. Assigning a name to a T o pMe ssag e device
is described in the T o pMe ssag e Co nfig urato r manual, the configuration of a Lo g -/
Pro fiMe ssag e device is described in the Log-/ProfiMessage device channel configuration
section.
The following columns can be displayed Channels view:
Value: Displays the current channel value.

Date, Time: The Date and Time channels displays the time-stamp from the displayed
measurement value.
State: Displays the actual state of the connection. Possible states are described in the
Connections option (State) section.
In addition to the states described there are the states OK and Invalid.
o OK: Indicates that the channel configuration is error-free and the channel contains
measurement data. An incorrectly configured channel that contains no data will display
a red OK state.
o Invalid: Indicates that there is an error in the channel configuration. In addition to the
red typeface, an octagonal warning symbol
is also displayed.
Channel type: Displays the type name for the channel, device, connection or container.
Data type: The data type for displaying the measurement data.
Clamps: The connections (+ and -) of the sensors.
Channel number: Internal assignment of a channel number to the hardware channel.
Location: Contains the user-input text from the Location field in the configuration
dialogue.
Comment: Contains the user-input text in the Description field of the configuration
dialogue.
126

May 2011
Measurement range: The valid measurement range from the channel configuration. For
analog inputs this takes place following conversion. For software channels, the
measurement range is defined depending in the data type restrictions (Default: 0 - 100).
Storage: Indicates whether and in what way the measurement data is stored. No (no
storage), Device and Database entries may appear alternately or cumulatively. A Device
entry indicates that a channel's measurement data is being stored to a memory group
within a Me ssag e device. A Database entry is displayed when the user assigns a
channel to a database.
Storing measurement data to a memory group is described in the Memory groups
section. Information on storing measurement data to a database is available in the
Database option section.
Device: Informs users of the Me ssag e device to which a channel (i.e. an object in the
channel view) belongs. This is useful for long channel lists for one Me ssag e device.
Object-ID: Displays a unique ID for each device (hexadecimal number). Further
information on the object-ID is available under Connections option (Object-ID).
Channel sheet options

Select the Hardware defined view option from the Channel sheet options to obtain an
Explorer-type tree structure portrayal of the entries. The tree portrays the hierarchical
physical dependencies of the channels. Users can then see which devices are configured
and assigned to which DataSe rv ice .
For a Lo g -/ Pro fiMe ssag e -device, users see the various external and internal interfaces
(CAN and COM ports, Extension-Bus, USB etc.), an empty interface container, a memory
container for the memory groups, and a software channel container.
In the User defined view, users have the option to drag and drop channels to portray their
logical dependencies and groupings. This is an alternative to the physical dependencies
portrayed in the hardware defined view.
The User defined view is available as an option under Channel sheet options. The option
can also be accessed by right clicking any column heading.
For a Lo g -/ Pro fiMe ssag e device, the basic settings for the User defined view displays the
connected modules and three containers as sub-levels of the device: Interfaces, Memory
for memory groups and Software channels.
To reposition an element, left click the element and drag and drop it to the required
position. The element can be any channel, module or container.
Simple repositioning can be performed by creating a link at the destination position. During
this process a black arrow is displayed at the mouse-cursor.
Pressing CTRL + left-click copies the channel to the destination position (plus-symbol
displayed at the mouse cursor). Pressing SHIFT moves the channel from its original position
to the destination position (minus symbol at the mouse cursor). ALT + left-click moves the
channel along with its source (asterisk symbol at the mouse cursor).
Visible database sheet columns

May 2011
127
The DataService Configurator's database view displays information and configuration

options for internal and external measurement data storage to databases.
Users are able to arrange the panel to their own needs (with the exception of the Name
column, which is always the first column and may not be hidden). The basic display options
are described at the beginning of the Connections option section.
The Name column may not be hidden and contains the name of the database or the device
on which the database is running. Assigning a name to a T o pMe ssag e device is described
in the T o pMe ssag e Co nfig urato r manual, the configuration of a Lo g -/ Pro fiMe ssag e
database described in the Adding measurement database section.
The following columns can be displayed Database view:
Size/Value: The projected database size for measurement data from the channels to be
saved.
Timerange/Time: Displays the time-stamp for a measurement value, and acquisition timerange for a database.
State: Displays the actual state of the connection. Possible states are described in the
Connections option (State) section. In addition to the states described there are the
states OK and Invalid.
o OK: Indicates that the channel configuration is error-free and the channel contains
measurement data.
o Invalid: Indicates either there is an error in the channel configuration or the channel
has not received any measurement data.
Device: Displays the name of the device on which the channel is configured.
Comment: Contains the text input by the user in the Description field of the
configuration dialogue.
Object-ID: Displays the unique ID (hexadecimal number) for each device. Further
information on the object-ID is available under Connections option (Object-ID).
Timezone (display)
128

May 2011
Main menu
View
Timezone
Select the required timezone
Time synchronization is indispensable for the acquisition, recording, evaluation and

visualization of measurement data across multiple devices. To avoid time delays when data
streaming, enable the NTP client within the Me ssag e device.
Enter the network's internal NTP server IP address, when known, via the Me ssag e
device's configuration template. The configuration mask is accessed by entering the
Me ssag e device's IP address in the address line of any browser software. The Me ssag e
device needs to be accessible within the network. When necessary, obtain the NTP server
IP address from your system administrator.
The time to be displayed in the DataService Configurator is set using the Timezone
(display) option.
In cases where the PC and Me ssag e device are set to different timezones, users can then
switch the display between Local time (PC) and Source time (Me ssag e device). There is
also the option for UTC time or to set the time-stamp to another timezone.
Info:
All these settings refer only to the DataService Configurator time-stamp, not the
actual time-stamp.

May 2011
129
2.3.2.4 Options
Main menu
Options
The main menu's Options tab contains the following:

Language
Don't prompt for confirmation
Copy ID of selected element to Clipboard
Language
The Language option enables language settings for the DataService Configurator.
The language setting determines the user dialogue language as well as the Configurator
message language. The messages can be accessed via Events
Configurator messages
located at the bottom left of the DataService Configurator.
Setting the DataService language for messages is described in the Connections option
(General tab). Users can currently choose between English and German. Further localisation
is planned.
Don't prompt for confirmation

The Don't prompt for confirmation option enables configuration procedures that are
irreversible to be immediately implemented.
User systems generally have a security prompt for actions that are irreversible. This helps
prevent unintended actions from being performed. These prompts can however become
annoying for repeated actions by experienced users and can result in delaying work-flows.
But repeated actions do have a high error potential so this function should only be selected
with care.
The option should remain disabled until users are fully familiar with the DataService
Configurator.
Copy ID of selected element to Clipboard

This option is the simplest method for copying a selected channel's object-ID (16-digit
hexadecimal number) to the clipboard. Use this option when the CTRL + ALT + I short-cut
is unavailable.
130

May 2011
2.3.2.5 Help
Main menu
Help
The Help option provides links to the content and search options for the online help
system.
Content
Opens the DataSe rv ice Co nfig urato r help system with the Content option.
Search
Opens the DataSe rv ice Co nfig urato r help system with the Search option.
Edit licence
Opens the Edit licence dialogue. If the licence has not been activated this option will
appear as Activate licence.

May 2011
131
2.3.3
Connections option
Connections
The Connections tab in the DataSe rv ice Co nfig urato r displays all configured connections.
A connection is a communication path between a Me ssag e device and the DataSe rv ice
Co nfig urato r and Pro fiSig nal. Pro fiSig nal can display or process data from measurement
hardware only when a connection exists between the hardware andDataSe rv ice
Co nfig urato r and this connection is active (State: Connected).
The measurement data (channels) to be displayed in Pro fiSig nal is configured in the
Channels option of the DataSe rv ice Co nfig urato r (refer to the Channels option section).
The Connections' functions are accessed via the Connect option from the main menu and
via context menus from each connection under the Connections option.
Information on these context menus can be found in the section on context menus in the
Connections option.
The Connections tab

An entry is displayed for each connected device. A tree structure portrays the hierarchical
relationships and dependencies of the devices. Users can see which devices are assigned
to which server and which server, or individual device, is assigned to which DataSe rv ice .
Users can determine themselves the columns to be displayed. (With the exception of the
Name column, which is always the first column and may not be hidden). Displaying and
hiding columns is described in the View section. The simplest method is via context menus
that are accessed by right-clicking on a column heading.
The column order can then be changed by dragging the column heading to the required
position.
Double-clicking a column heading sorts the whole table in ascending or descending order of
the selected column. The column menu is also displayed by right clicking a column heading
in the Connections view.
The following columns are available:
Name: Displays either the device's IP address or its name (may not be hidden).
132

May 2011
Host/IP: Displays the IP address or the host name of the device listed in the Name
column.
Connect: Displays the expected state of the connection.
State: Displays the actual state of the connection.
Driver type: Displays the device type name that corresponds to the driver being used.
Version: Displays the driver software version.
Object-ID: Displays a unique ID (hexadecimal number) for each device.
Name
The default entry for the device name is the device's IP address. To simplify system
administration, users are recommended to provide a unique but descriptive name for the
device.
Assigning a device name to a Lo g -/ Pro fiMe ssag e device is described in the Log-/
ProfiMessage device channel configuration section.
Host/IP
After naming the device, its IP address can be displayed in the Host/IP column. For the
DataSe rv ice device type, the host name is the computer on which the DataSe rv ice is
installed.
Connect
The Connect column displays the state of the connection for the configured device. The
status in the Connect column corresponds to the settings options in the TopMessage
connection settings dialogue:
o Yes: A connection for the device was initiated with either the option Manually or
Always.
o No: The connection should be take place manually but has not been performed.
o Automatic: The connection should take place in special situations only; either by a
request from a Pro fiSig nal application (Automatic (all data)) or for memory read-out
only (Autom. (only stored data)).
Status

May 2011
133
The State column indicates whether the connection has been successful. Possible entries
under State:
Connected: A connection exists, Pro fiSig nal can access the channels.
Connecting: Connection is taking place, Pro fiSig nal can not yet access the channels
(may take up to one minute).
Offline: The user has disconnected the connection, Pro fiSig nal can not access the
channels.
Offline, Timeout: A connection could not be established or an existing connection has
been interrupted, Pro fiSig nal can not access the channels.
Dual connection/ identical device configuration: There is a connection to the
DataService with two devices with identical IDs, or two connections to the same
device.
Device time differs: The Me ssag e device time does not correspond to the time on
the computer on which the DataService is running; synchronize the times to avoid
delays or data loss. If possible use NTP for time synchronization.
Disconnected, Outdated firmware, update needed: The DataSe rv ice may be unable to
communicate with a Me ssag e device due to firmware (DelOS) incompatibility.
Pro fiSig nal is unable to access the channels. Update the Me ssag e device firmware.
Updating firmware is described in the Firmware update section.
To highlight absent or incorrect connections, all state's other than Connected have red
typeface.
Object-ID
For Lo g -/ Pro fiMe ssag e devices, the object-ID is made up of two blocks of 8-digit
hexadecimal numbers. The left block contains the device-ID and the left block the channelID.
The device-ID corresponds to the Lo g -/ Pro fiMe ssag e device's serial number at delivery
and should not be altered.
In rare cases a user-defined ID can be used instead of the serial number. Altering device
IDs is described in the Log-/ProfiMessage device channel configuration section. The system
issues Channel-IDs as part of channel configuration and can not be changed.
Connections option context menu

The context menu for the Connections option depends on the type of connection
(DataService or Me ssag e device).
134

May 2011
Except for a local DataService, whose connection options are managed via the main
menu's Connect option, the context menu options are Connect, Disconnect, Connect
automatically and Connect automatically (read device storage only). They correspond to
the settings made in Connection settings. The settings are made when setting up the
connection.
The selected connection is disconnected and removed from the list via the option Remove
driver (connection).
The Save connection settings option enables saving of the settings for the selected
connection to a bdc-file on the PC, and then to enable reloading of the settings (via Load
connection settings) from the bdc-file. For T o pMe ssag e and Expe rt Ke y hardware, there
is also the Update firmware option.
DataService connection options

The context menu for a local DataSe rv ice , or for a connection to a server which is running
a DataSe rv ice , includes the option Add driver (connection) .

May 2011
135
Add driver
To add a connection to a Me ssag e device or a server that is running a DataSe rv ice ,
select the corresponding option from Add driver (connection). Alternatively, users can add
a local DataService connection via the main menu's Connect option.
Users may also Load connection settings from previously saved settings. The procedure for
creating a new connection via the DataSe rv ice Co nfig urato r depends on the type of
connection and is explained in the following sub-sections:
TopMessage connection: Establishing a connection to a T o pMe ssag e - and T o pLab
device
Lo g -/ Pro fiMe ssag e connection: Establishing a connection to a Lo g -/ Pro fiMe ssag e
device
Expert Key connection (LAN): Establishing a LAN connection for Expert Key devices
Software channels: Creating a driver for software channels in the DataSe rv ice
DataService connection: Establishing a connection to use an additional DataSe rv ice on
another (server) PC
OPC-Client: Establishing a connection to an OPC-Server (depends on licensing)
Other connections: Depending on availability users can establish connections to other
devices for which user-specific drivers are created.
The Save connection settings option enables saving of the settings for the selected
connection to a bdc-file on the PC, and then to enable reloading of the settings (via Load
connection settings) from the bdc-file.
2.3.3.1 Main settings
Main settings
Connections
Service main settings
The Main settings option gives access to the DataService settings dialogue. The settings
options are available via four tabs:
General
136

May 2011
Data storage
Data Server
OPC / NTP Server
ProfiSignal Script
The General tab
Name (text field)

Enter the name of choice for the DataSe rv ice .
Timeout at startup... (radio buttons)
Set the timeout periods for establishing connections.
Language (logging messages) (radio buttons)
The language can be set - which is separate to the Configurator language (refer to the
Main menu Options section) - for DataSe rv ice messages accessed via the Events
DataService messages tabs (below left). Current options are English and German.

May 2011
137
The Data storage tab

The most important settings on the Data storage tab are the Measurement data cache
size numeric field and the Storage interval dropdown box. These are the decisive
parameters - along with the database settings in Trend optimization (measurement
database) - that will make subsequent processing easier.
138

May 2011
Data cache size:

Select or enter the cache size in MB for the selected DataSe rv ice . The larger the
cache, the more data DataService can store and display without having to access the
hard drive. The cache size may also be exceeded depending on the number of channels
to be stored and the data resolution of the channels. As a rule, as much memory as
possible should be made available for the cache.
Storage interval
The period of time until new measurement data is written to the hard drive. Data loss
may occur in the event of a system failure. A longer storage interval improves data
compression when saving.
The slide-controls in the middle section of the dialogue (For specialists) enables greater
precision for specific measurement scenarios. Using these settings depends heavily on the
experience of users and should therefore be used only by very practised users.
Cache optimisation
This slide-control correlates to the time range being used for Pro fiSig nal trend
portrayals and sets which portrayal requires a greater level of cache data. The
standard setting is normally sufficient.
Block size

May 2011
139
A larger block size increases access speed to stored measurement data and can
improve compression when recording the measurement data. A smaller block size
enables a better distribution of cache memory across the channels. A smaller block size
can therefore be beneficial for large numbers of channels. The standard setting is
normally sufficient.
Data Server tab

The Data Server tab enables settings to be made for the DataSe rv ice 's data server.
Server port
The TCP port that the server uses for connections. The default port of 3737 normally
remains unchanged.
Compress data transmission
Transmitted data will be compressed. The "enabled" default is the usual setting.
Only local connections
The server accepts no connections other than from the PC.
Allow all network connections
The server accepts all connections external to the PC.
Optimize for low bandwidth
To optimize the data package size for narrow-width connections, e.g. ADSL / UMTS.
Other options depend on the user's licence and are available only with the DataService
Server option.
Allow configuration
140

May 2011
Enables amendments to DataService or device configurations to be performed from

another PC.
Allow operations
Enables amendments to DataService or device operations to be performed from another
PC. e.g. amendments to outputs, activating triggers.
Allow read device memory
Enables another PC to read the device memory.
Allow read database
Enables another PC to read a database
No implicit reading
Enables explicit reading of a database, e.g. via the scheduler or a trend with a
predefined data source. Automatic reading of the measurement data via a standard
trend without a predefined data source is then not possible. Use this option to reduce
data volumes over a WAN connection.
Allow alerting
Enables another PC to read alerts.
Selective network connections
To specify in the connections dialog the available data for multiple clients.
The OPC / NTP Server tab

The OPC / NTP server tab enables settings to be made for the other servers belonging to
the DataSe rv ice .

May 2011
141
OPC Server
OPC Server settings (depending on licensing) first require checking of Server active. On
checking the OPC Server, the following settings are available under Options.
o Device timestamps
Enable this option when the server is to take on the device's original timestamp. The
server will otherwise use the current PC time.
o Replace special characters
Special characters may cause problems for some OPC Clients. Activating this option
replaces special characters with underlines.
o Writeable output channels
This option enables writing to output channels via the OPC interface. The channels also
require configuring in a way that they can be written to from the PC / ProfiSignal.
o Ignore value states
Enabling this option ignores the measurement data's original state and returns the state
QUALITY_GOOD.
o Update rate (maximum)
Sets the maximum speed at which the server updates measurement data. The actual
update rate depends on the measurement data source.
NTP Server
This section of the dialogue concerns time synchronization via an NTP Server.
When Local time server active is checked, a local NTP Server is enabled in DataSe rv ice .
This NTP Server may start only when no other NTP Server is running on the PC.
142

May 2011
Windows normally provides an NTP Server. This needs to be disabled prior to using the
DataService. The DataService NTP is to be used when the PC is not synchronized via a real
NTP Server (e.g. radio-controlled clock). In this event, the Windows NTP Server returns an
unsynchronized time to the Client. In contrast, the DataService NTP Server, as a local
time server, always returns a synchronized time-stamp to the Client.
Synchronized time-stamps are required because Lo g -/ Pro fiMe ssag e -devices accept only
synchronized time-stamps from the NTP Server.
Info:
Be aware that a local time server does not deliver official times and is subject to drift.
The ProfiSignal Script tab

The ProfiSignal Script tab provides three numeric fields for the framework ports for Java
VM. The input is required to enable use of the Klicks script language in ProfiSignal.
First port (TCP) (numeric field)

The first port for JavaVM.
Last port (TCP) (numeric field)

May 2011
143
The final port for JavaVM.

Java VM state port (UDP) (numeric field)
State port for JavaVM.
2.3.3.1.1 Connection settings
For setting the data for individual client devices.
IP Address / Mask
Enter the IP address range that is valid for the subsequent settings.
144

May 2011
Outgoing bandwidth
Enter the minimum available bandwidth to optimize the data-package size for narrowband connections.
Limit available channels
Enter the channels that are to be available / visible to the client.
Allow configuration
When checked, the client may amend configurations in the DataService or device.
Allow operations
When checked, the client may perform operations in the DataService or device, e.g. set
outputs and triggers.
Allow read device memory
When checked, the client may read a device's memory.
Allow read database
When checked, the client may read a measurement database.
No implicit reading
When checked, a measurement database can be read only explicitly, e.g. through a
scheduler or trend with a fixed data source. Automatic reading is no longer possible
through a standard trend without an assigned data source. Use this option to reduce
data volumes in a WAN connection.
Allow alerting
When checked, the client may read alerts/alarms.
Limit available memory / databases

Displays in the client only the selected memories / databases.
2.3.3.2 TopMessage connection
Requirements for establishing a (TopMessage) connection

For Pro fiSig nal to access the hardware and virtual channels of a T o pMe ssag e device, a
connection needs to be established to the device in the DataSe rv ice Co nfig urato r.
A successful connection between a PC and the T o pMe ssag e device requires an error-free
Ethernet connection and the correct TCP/IP settings for both PC and T o pMe ssag e
device. This means that the IP addresses of all network users are to be within the same
network - defined by subnet masks - and that the IP addresses for the devices differ to
each other.

May 2011
145
How to amend the IP address and subnet mask of a T o pMe ssag e device is described in
the Introduction to ProfiSignal manual.
Info
Establishing a connection to a Lo g Me ssag e d e v ice (T y pe LM100 - LM900) is
equvalent to T o pMe ssag e d e v ice .
Establishing a TopMessage connection

Main menu
Connect
TopMessage (LogMessage 100 - 900)
device
Alternatively, this option can be accessed via the context menu of a connection to a PC on
which a DataService is running.
Clicking TopMessage (LogMessage) device opens the Top-/LogMessage connection

settings dialogue. This lists all T o pMe ssag e devices connected to your network.
Found devices are listed under the Found devices tab (below left).
If the automatic search was unsuccessful because your network does not support
automatic searching, this activates the General tab (below right).
Technical info:
The automatic T o pMe ssag e device search takes place via a broadcast on port
number 16554.
146

May 2011

May 2011
147
When T o pMe ssag e devices have been found, double-click the device to which you
wish to make a connection. This opens the General tab which then already contains
the connection parameters for this device.
When there are no found devices, the connection parameters require manual input via
the General tab.
The General tab
148

May 2011
Host
Enter the IP address of the T o pMe ssag e device to which a connection is to be
established.
Port
Enter the port over which the connection is to be established. The default value is
"1029". Change this only when the port is already being used by other applications in
your network.
FTP mode
Select the FTP mode to be used for establishing FTP connections.
Connection
Select the communication route over which the connection is to be established when
multiple network cards are available.
Connect
o Manually
The connection is established and disconnected by the user in the DataSe rv ice
Co nfig urato r.

May 2011
149
o Always (default)
The DataSe rv ice will always attempt to establish a connection.
o Automatically (all data)
The connection is automatically established when a Pro fiSig nal application
requests one of the device's channels.
Info:
A connection to a TopMessage device must be established prior to assigning its
channels to an application, otherwise the channels will not be displayed.
o Autom. (only stored data)

The connection to the T o pMe ssag e device is automatically established when the
T o pMe ssag e device's internal memory is to be read out (either via the Pro fiSig nal
option File | Readout Device Storage or via the DataSe rv ice Co nfig urato r Scheduler
function). The connection automatically disconnects following memory read out.
Username
When the T o pMe ssag e device's password protection is activated, enter the username
from the user login.
Password
When the T o pMe ssag e device's password protection is activated, enter the password
from the user login.
OK button
Clicking OK establishes the T o pMe ssag e connection.
2.3.3.3 Log-/ProfiMessage connection
Requirements for establishing a (Log-/ProfiMessage) connection

For Pro fiSig nal to access the hardware and virtual channels of a Lo g -/ Pro fiMe ssag e
device, a connection needs to be established to the device in the DataSe rv ice
Co nfig urato r.
150

May 2011
A successful connection between a PC and the Lo g -/ Pro fiMe ssag e device requires an
error-free Ethernet connection and the correct TCP/IP settings for both PC and Log-/
ProfiMessage device. This means that the IP addresses of all network users are to be
within the same network - defined by subnet masks - and that the IP addresses for the
devices differ to each other.
Establishing a Log-/ProfiMessage connection

Main menu
Connect
ProfiMessage (LogMessage 1000 -
9000) device
The General tab

May 2011
151
Host
Enter the IP address of the Lo g -/ Pro fiMe ssag e device to which a connection is to be
established.
Port
Enter the port over which the connection is to be established. The default value is
1033. Change this only when the port is already being used by other applications in
your network.
Connect
o Manually
Co nfig urato r.
o Always (default)
The connection is automatically established when a Pro fiSig nal application requests
one of the device's channels.
Info:
152

May 2011
A connection to a Lo g -/ Pro fiMe ssag e device must be established prior assigning its

The connection to the Lo g -/ Pro fiMe ssag e device is automatically established when
the Lo g -/ Pro fiMe ssag e d e v ice 's inte rnal me mo ry is to be re ad o ut (e ithe r v ia the
Pro fiSig nal option File | Readout Device Storage or via the DataService Configurator
Scheduler function). The connections automatically disconnects following memory
read out.
OK button
Clicking OK establishes the Lo g -/ Pro fiMe ssag e connection.
2.3.3.4 Software channels
Creating a software channel

Software channels provide a range of different channels that do not require the connection
of hardware devices. These include basic variable channels to which users can assign a
set value and write to using Pro fiSig nal, and test channels that provide sine, square,
triangle and sawtooth signals with parameters.
The Pro fiSig nal demo version has a pre-installed software channel driver with several
software channels.
To use a software channel in another installation, the corresponding driver needs to be
added. This takes place in same way as adding a hardware device (e.g. a TopMessage
device ) in the DataSe rv ice Co nfig urato r:
1. Firstly, click the Connections tab to check whether the software channels driver has
already been added.

May 2011
153
2. If the software channels driver has not yet been added, select the main menu entry
Main menu
Connect
Software channels
3. The software channels driver is now added enabling users to create software
channels via the Channels tab.
2.3.3.5 DataService connection
Establishing a DataService connection
154

May 2011
A DataSe rv ice -connection indicates that the installed Delphin DataSe rv ice is accessing
connections that have already been configured on a different PC the network. This enables
users to configure a device connection from a central point.
To establish a DataSe rv ice -connection, do the following:
1. Main menu
Connect
DataService Client
2. Enter in the Host field either the TCP/IP network address or network name of the PC
whose connections / databases you wish to use.

May 2011
155
Host
Enter the IP address or name of the device on which the DataSe rv ice is running.
Port
Enter the port over which the connection is to be established.
Connect
o Manually
156

May 2011
Co nfig urato r.
o Always (default)
The connection is automatically established when an application requests one of
the device's channels.
Info:
A connection to the device must be established prior to assigning this connection's

The connection is automatically established when the device's internal memory is
to be read out (either via the Pro fiSig nal option File | Readout Device Storage or
via the DataService Configurator Scheduler function). The connections
automatically disconnects following memory read out.
Username
When the server's password protection is activated, enter the username from the user
login.
Password
When the server's password protection is activated, enter the password from the user
login.
OK button
Clicking OK establishes the connection.
3. Once a DataSe rv ice connection has been successfully established, it appears as a

line entry in the DataSe rv ice Co nfig urato r tre e structure alo ng with e ntrie s fo r all the
co nne ctio ns it co ntains. Users may have to click the tree structure's plus symbols in
order to get a complete overview.

May 2011
157
2.3.3.6 OPC Client
Installing an OPC Client

An OPC Client enables the DataSe rv ice to acquire data from an OPC Server and to then
make this data available to Pro fiSig nal.
Main menu
Connect
158
OPC Client

May 2011
The General tab
Drivername
Any name may be selected for this connection.
Connect
o Manually
Co nfig urato r.
o Always (default)
o Automatically
The connection is automatically established when Pro fiSig nal requests one of the
OPC channels.
Info:
A connection to an OPC Server must be established prior to assigning channels from
an OPC connection to an application, otherwise the channels will not be displayed.

May 2011
159
Measured value timestamp source

o OPC Server (default)
The time-stamp for a measurement value from an OPC Server is the one returned by
the server.
Info:
If the OPC Server and DataSe rv ice are not running on the same PC, time
synchronization must be performed using these PCs' clocks. Information on
synchronization using an NTP time server is available under the Server tab of the
connections option.
o DataService
Measurement data from the OPC Server is assigned a time-stamp from the
DataService.
OK button
Clicking OK installs the OPC Client.
Info:
This just activates the driver for OPC communications. Configuration of OPC
connections takes place via the DataSe rv ice Co nfig urato r Channels option and is
described in the OPC channels configuration section.
160

May 2011
2.3.3.7 Modbus-Client
Creating a connection to a Modbus device

For Pro fiSig nal to access the register of a device that supports the Modbus-TCP protocol,
a connection to the device needs to be established in the DataSe rv ice Co nfig urato r
program.
Main menu
Connect
Modbus-Client
The General tab

May 2011
161
Host
Enter the IP-address of the Modbus-client for which a connection is to be made.
Connect
o Manually
The connection (and disconnection) is manually made by the user in the DataSe rv ice
Co nfig urato r.
o Always (Default)
The DataSe rv ice always attempts to create the connection.
o Automatically
The connection is made automatically when Pro fiSig nal requests one of the Modbus
channels.
OK
Clicking OK creates the OPC-Client.
162

May 2011
Info:
This only activates the driver for Modbus communication. Configuration for Modbus
connections takes place under channels in the DataSe rv ice Co nfig urato r. This is
described in the section on configuring Modbus channels.
2.3.3.8 Firmware Update

New firmware is supplied with each software update for Me ssag e and Expe rt devices.
This section describes how to perform a
firmware update for a T o pMe ssag e d e v ice .
This chapter shows you how to perform an
update for a TopMessage device.
Run update
o Update TopMessage device
o Update ProfiMessage device
To ensure problem-free running of the complete

system, always update the device firmware
when requested by the Delphin hotline or by
the device's status information. Status
information is available under the Connections
tab.
Run update

May 2011
163
To update the firmware go to the Connections tab.

Open the device to be updated (right click).
Select Update firmware.
Update TopMessage device

To update a T o pMe ssag e device, open the T o pMe ssag e Co nfig urato r and the Update
firmware dialog.
When the new firmware files are available, they are selected directly. If the firmware files
are not in the standard folder, an alternative path can be selected via the Browse button.
164

May 2011
Double clicking Update installs the selected updates. The Update firmware dialog then
closes automatically.
The T o pMe ssag e Co nfig urato r can be used to check whether the update has been
successful.
Close the T o pMe ssag e Co nfig urato r, to return to the DataSe rv ice Co nfig urato r.
Update Log-/ProfiMessage device

May 2011
165
Firmware updates for Pro fiMe ssag e devices are not run from the Connections option in the
same way as for T o pMe ssag e updates. Instead updates are run from a browser-based
settings dialog (html).
Further information is available from the ProfiMessage device firmware update.
166

May 2011
2.3.4
Channels option
The Channels option within the DataSe rv ice Co nfig urato ris for displaying and configuring at
device, module and channel levels.
Info:
To fully understand the configuration options, it is important for users to be aware that
all configurations that take place in DataSe rv ice Co nfig urato r use the terminus channel
even when this doesn't concern a measurement data channel in its narrowest sense. A
"channel configuration" is also performed for device interfaces, protocols, memory groups
and modules.
There are also software channel containers and memory group containers in which nonhardware channels are gathered.
The first 'Channels' level displays all the devices that have been configured. How to
establish a connection to a T o pMe ssag e device is explained in the TopMessage
connection section. Information on establishing a connection a to Lo g -/ Pro fiMe ssag e
device is available in the Lo g -/ Pro fiMe ssag e connection section.
If a device has already had channels configured, these can be displayed in the tree
structure by clicking the
symbol. Shrinking the tree structure is achieved by clicking
the
symbol.
Devices with interrupted connections (Inactive state), are displayed as disabled but remain
listed until deleted.
Channels that have not received any measurement data are displayed in red typeface. The
typeface changes to black as soon as data is received.
Incorrectly configured channels (Invalid state) are also displayed in red typeface with an
additional octagonal warning symbol

May 2011
in the Channel column.
167
The first level of a displayed T o pMe ssag e -device shows the various modules, interfaces
and internal memory.
Expanding the tree structure displays a measurement module's input and output channels
and their current states. Further information is available from the corresponding
configuration sections (see below).
Configuring a Lo g -/ Pro fiMe ssag e device is described in the Lo g -/ Pro fiMe ssag e device
configuration section.
Configuring a T o pMe ssag e device is described in the TopMessage device configuration
section.
168

May 2011
Configuring an Expert Key device is described in the Functions and operation section of
the Expert Key.
Software channel set up is described in the Creating software channels section.
Configuring OPC connections is described in the OPC channels configuration section.
Die Konfiguration einer Modbus-Verbindung ist im Kapitel Modbus-Kanle konfigurieren
beschrieben.
2.3.4.1 TopMessage device configuration

TopMessage Configurator, the configuration software for T o pMe ssag e d e v ice s, is run
directly from the DataSe rv ice Co nfig urato r. This section describes how to configure the
TopMessage device and/or individual modules and channels.
Info
Configuring a Lo g Me ssag e d e v ice (T y pe LM100 - LM900) is equvalent to
T o pMe ssag e d e v ice .
TopMessage device configuration

To run the TopMessage Configurator , select the Channels option from the DataSe rv ice
Co nfig urato r by clicking Channels.
Left-clicking the T o pMe ssag e device that requires configuring, opens the following
context menu:

May 2011
169
This context menu enables users to select a database to which the channel data is to be
saved and the T o pMe ssag e device's time that is to be set to the local PC time.
Clicking Launch TopMessage Configurator opens the TopMessage Configurator for
configuring basic parameters and T o pMe ssag e channels.
Info:
The T o pMe ssag e Co nfig urato r is an independent program for T o pMe ssag e
configuration.
The T o pMe ssag e Co nfig urato r has its own documentation which is available via
Start
All Programms
ProfiSignal
Documentation Message Devices
or via the T o pMe ssag e Co nfig urato r's help menu.

The T o pMe ssag e Co nfig urato r is a simplified version of Delphin's Busmanag e r
software. All references in the documentation to Busmanag e r then also applies to the
T o pMe ssag e Co nfig urato r.
170

May 2011
T o pMe ssag e configuration is concluded on closing the T o pMe ssag e Co nfig urato r.
Configuring modules and channels
To run the TopMessage Configurator , first select the Channels tab from the Channels
option of the DataSe rv ice Co nfig urato r.
Enable the T o pMe ssag e device with the module or channel to be configured by leftclicking the +-symbol next to the T o pMe ssag e device name.

May 2011
171
Expanding the tree structure displays a measurement module's input and output channels
and their current states. Further information is available from the corresponding
configuration sections (see below). Left-clicking an element within the tree structure opens
a context from which the TopMessage Configurator can always be run. The options
contained within the context menu depend on the tree entry being clicked.
Store channel in
To select a database in which the data from a module's channel or channels is to be
stored.
Set value
To directly assign a value to a channel. The values 0.0 and 1.0 are available. When the
channels are non-digital, the option Value x is also available. Selecting this option opens
a dialogue to enable entry of any value that can then be assigned to a channel.
2.3.4.2 Creating software channels

To create a software channel requires the adding of a software channels driver.
Using the DataSe rv ice Co nfig urato r's Channels tab enables creation of the following
software channels:
Variable channels
Users may assign a set value or a Pro fiSig nal dynamic value to aVariable channel.
172

May 2011
Test channels
A test channel provides a signal with parameters, which can be fixed or dynamically set
using other channels (e.g. a variable channel). Other test channels may also be
selected as parameters therefore enabling signal modulation.
The following waveforms are available:
o Sine
o Square
o Triangle
o Sawtooth
2.3.4.2.1 Creating variables
To add variables, select the Channels tab from the DataSe rv ice Co nfig urato r and rightclick software channels. From the context menu, select Create channel and then Variable
channel.
A new dialogue now appears to configure the variable. Select an appropriate Name for the
variable. If the variable is to have a Unit enter it here. The Description field is optional. The
variable channel may be temporarily disabled, without having to delete it, by unchecking
the Active checkbox.

May 2011
173
The Main settings tab
Data source
Select the source from which the variable is to obtain its data. The following sources
are available:
o Application
The variable is writeable from Pro fiSig nal and a value can be assigned from an
application. The 'Initial value' is the value the variable has until it receives another
value. The context menu can also be used to set a variable value directly from the
o Channel
The variable receives varying values from the selected channel. The Initial value is the
variable's default value.
o Manual input
The variable is assigned a fixed value that can only be varied via this dialogue.
Attributes
174

May 2011
To select the variable channel's data type:

o Bool
For the values on and off.
o Integer
For whole numbers up to 64 bytes in size.
o Single
For floating point values with a 7-8 digit accuracy.
o Double
For floating point values with a 15-16 digit accuracy.
o String
For character strings.
A 'Valid value range' may also be entered for single and double data types.
The Advanced settings tab

Refer to Advanced settings
The Forwarding tab
Forwarding
Enable this option to forward changed values in the variable channel to the selected
channel. Only channels can be selected that have their Data source set to Application.
With Channel as Data source, the forwarding option can be used to copy parameters
between devices.
Clicking OK accepts the input and the variable channel will appear in the list.

May 2011
175
Users can amend a channel's settings by double-clicking its tree entry, or by right-clicking
and then selecting Properties. Right-clicking and Delete channel deletes the channel. Rightclicking and Store channel in saves the channel to an existing database. Channel settings
are also possible via the context menu when they have an application as a data source.
2.3.4.2.2 Calculation channel
A calculation channel enables computations between any channel(s) and number(s). As

well as basic calculations, many mathematical functions are also available such as sine,
root, logarithms, and minimum and maximum functions. The use of logical connectors and
conditions is also possible and a range of channel functions are available, e.g. to determine
a channel's state as well as its time and previous values. Calculation channels enable
integration and differentiation. There are also predefined constants to simplify usage.
Functions and keywords are described in formula functions.
Calculation channels are performed either at set times or via triggers.

Time settings can be made according to seconds, days, or even milliseconds along with a
mode for time-synchronization. Triggered calculations require a trigger channel to be
selected. Computation is then triggered at each rising edge (0/1-edge).
A formula is input directly into a field. Variables are added via the "Add variable" option. A
name can be given to a variable and then used in the formula. A variable can have a set
value or can assigned to a channel. Edited formulae can be saved and loaded. A collection
of formulae (a formulary) is available from the software channel context menu. Formulae
can be edited and added to the formulary as well as imported and exported. Formulae
edited in the formula editor do not affect existing calculation channels.
Create calculation channel
176

May 2011
To create a calculation channel, open the channel tab in DataSe rv ice Co nfig urato r and
right click software channels. Select Create channel and then Calculation channel.
The calculation channel can now be configured using the settings dialog. First select an
appropriate Name for the calculation channel. Unit is optional as is Description. The Active
checkbox enables a calculation channel to be temporarily disabled without having to delete
it.
The "Main settings" tab

May 2011
177
Type of calculation
Determines when a calculation channel is to compute and generate a value. The calculation
can be time-based, i.e. during a set time interval, or triggered by a channel (rising edge).
Formula
To input the calculation channel's formula Further information on formulae as well as a list
of functions and keywords is available under formula functions.
The input formula can besaved or a saved formula loaded.
Variable lists
The variable button enables additional variables to be used. These variables can be given a
name or assigned a channel or set value. If a channel is selected as a variable, there is an
"inherited state" option. The state of all channels that have"inherited state" enabled will be
output together as the calculation channel's state.
Time synchronized calculation
For time-synchronized calculations, the times from all source channels are checked and
synchronized. This enables data transfers from channels of different devices and avoids
runtime errors from occurring. Time-synchronized calculations also permit calculation
intervals at millisecond levels.
"Advanced settings" tab
178

May 2011
Refer to other settings
Confirming the settings dialog saves the changes and the calculation channel will now
appear in the list.
The configuration can be amended by double or right clicking settings from the channel
appearing in the list, The configuration can be deleted by right clicking Delete channel. The
channel can be saved to an existing database by right clicking and Save channel in.
2.3.4.2.2.1 Formula functions
Formulae are input via a text field. Any symbol or wording from the tables below can be
used as well as variable names. Incorrect words are underlined in red. Upper and lower case
are not differentiated.
Either German or English versions can be used!

English wording
German
wording
Symbol
Description
sin, cos, tan
Trigonometric Functions
asin, acos, atan
Inverse trigonometric functions
sinh, cosh, tanh
Hyperbolic functions
exp
Exponential functions (e-function)
ln
Natural logarithms (base e)
Log
Common logarithms (base 10)
sqrt
wurzel
The square root
pow
abs
A number's absolute value
mod
min, max

May 2011
Power of x^y or pow(x;y)
The modulo value of two

numbers, x%y or mod(x;y)
The minimum or maximum from a
list of any number of values, e.g.
min(x;y;z;...)
179
time
zeit
Returns a variable's time-stamp,

zeit(var)
state
status
Returns a variable's state, zeit

(var)
previous
vorher
Returns a variable's previous value

(n<=256), previous(var;5). Time
or state can also be determined
from here: time(previous(var;5))
or
oder
||
Logical or-operation
and
und
&&
Logical and-operation
not
nicht
Logical not-operation
xor
xoder
if
wenn
else
sonst
Logical exclusive-or-operation
(bitwise)
&, |
Bitwise and/or
Bitwise negation
==
Equals
!=, <>
Not equal to
>=, <=,
>, <
Greater than or equal to, less

than or equal to, greater, less
than
+, -, *, /
Basic mathematical operators
(, )
Brackets
Formula conditionals,
If(condition1) Statement1
Else If(condition2) Statement2
Else Statement3
"," (comma) and "." (Point) can be used for decimal numbers
";" (semicolon) must be used for listing/separating parameters
Constants
180

May 2011
English symbol/
wording
German wording
Description
ownChannel
eigenerKanal
Contains the calculation channel's

previous value. Can be used like a
variable, e.g. time(ownChannel)
now
jetzt
A constant for the current time.
Pi
Constant for Pi = 3.1415...
Euler
Constatnt for the Euler e number.
True
Wahr
Constant
False
Falsch
Constant
Predefined constants for the possible states of variables/channels

state_scaled
status_skaliert
The measurement data has been

converted into a unit of
measurement from binary A/D
converter code.
state_forced
status_erzwungen
The measurement data has been

forcibly replaced by a replacement
value or simulated measurement
data.
state_valid
status_gltig
The value is valid and no errors have

occurred.
state_invalid
status_ungltig
The data is invalid because of an

unspecified error.
state_offline
status_getrennt
Connection to data source/ device

has been interrupted.
state_type_changed
status_datentyp_gend
ert
The data type has changed.
state_config_error
status_konfig_fehler
The channel configuration contains

errors.
state_hw_failure
status_hw_defekt
The hardware contains errors.
state_wirebreak
status_drahtbruch
A wire break has been detected.
state_overrange
status_obere_grenze
The measurement data is at / above

the measurement range.

May 2011
181
state_underrange
status_untere_grenze
The measurement data is at /below

the measurement range.
state_value_invalid
status_wert_ungltig
state_infinite
status_unendlich
The data was infinite and has been

replaced by a valid value.
state_nan
status_keine_zahl
The data is non-numeric, e.g. by

being divided by 0 and has been
replaced by a valid value.
state_alarm
status_alarm
state_incomplete_cal
c
status_unvollstndige_b
erechnung
The value could not be completely/

correctly computed because of data
omission / altered time.
state_intermittent
status_unterbrochen
Recording has been interrupted /

paused.
state_time_sync_fail
ed
status_zeit_unsynchron
The value is incorrect because the

channel contains sources that are
non-synchronized (no current
measurement data).
A channel can have multiple states. The state must therefore be checked as follows:
state(var)==state_valid
flagging!
Checks whether the channel state is valid, i.e. no state
state(var) & state_XXX
Checks whether there is specific state flagging!
Multiple states can be checked as follows:

(state(var) & state_XXX) && (state(var) & state_YYY)
(state(var) & state_XXX) || (state(var) & state_YYY) or
state_YYY)
state(var) & (state_XXX |
2.3.4.2.2.2 Load formula
Formulae in the formulary can be loaded directly from a calculation channel dialog. Clicking
"Load formula" opens a dialog listing the available formulae. Selecting a name displays the
formula.
182

May 2011
Click "Load" to transfer the formula to the calculation channel. The "Create variables while
loading" inserts all existing variables into the formula within the calculation channel, but
only as empty channel sources and not with full settings.
2.3.4.2.2.3 Save formula
Edited formulae can be saved directly to the formulary using the "Save formula" dialog. The
formula is saved with a unique name that users must supply. The formula can be changed
when saving but will not be checked for correctness.
The formula is saved only to the formulary. There is no saving of any of the settings to
variables or assignments of channels.

May 2011
183
2.3.4.2.3 Average channel
An average channel enables other channels' arithmetical averages to be calculated. Moving

and block averaging functions are available.
Moving average
A moving average is based on a channel's previous n measurement values. n is userdefined.
Block average
A block average is based on a block of values. A block is determined either by a set
interval or the 1/0-edge of a trigger channel.
Creating an average channel

To create an average channel, open the channel tab in DataSe rv ice Co nfig urato r and right
click software channels. Select Create channel and then Average channel.
The average channel can now be configured using the settings dialog. First select an
appropriate Name for the average channel. Unit is optional as is Description. The Active
checkbox enables an average channel to be temporarily disabled without having to delete
it.
184

May 2011
Value source
To select the channel from which the average calculation is to be performed.
Type of average
To select the type of average. Selecting "Moving average" also requires input of the
number of measurement values from which the average is to be calculated. When selecting
"Average block by block", users also have to select either a time interval or trigger
channel.
"Generate interim values" outputs average values for the current measurement data
without affecting the overall average computations for the block (defined by time interval
or trigger).

May 2011
185
Refer to additional settings
Confirming the settings dialog saves the changes and the average channel will now appear
in the list.
2.3.4.2.4 Statistic channel
A statistic channel enables users to calculate statistics from other channels.

Moving calculations
This function determines, for each value from the source channel, the minimum or
maximum of the previous n values. n is user-defined.
Block calculations
Calculates statistics for a block. A block can be set as a fixed time period or triggered
by a channel's 0/1-edge. Calculations take into account both the source channel's
individual measurement data and its time interval. This enables correct results to be
delivered even for batch data. The exception is the geometric mean which does not use
the time interval.
Minimum
The smallest value in the source channel's block.
Maximum
The largest value in the source channel's block.
Variance
The variance is calculated using the following formula:
Standard deviation
The standard deviation is calculated from the square root of the variance:
Number of samples
The number of measurement values in the source channel's block.
Root mean square
186

May 2011
The root mean square is calculated using the following formula:
Geometric mean
The geometric mean is calculated using the following formula:
(The time interval is not taken into account)

Harmonic mean
The harmonic mean is calculated using the following formula:
Creating a statistic channel

o create a statistic channel, open the channel tab in DataSe rv ice Co nfig urato r and right
click software channels. Select Create channel and then Statistic channel.

May 2011
187
The statistic channel can now be configured using the settings dialog. First select an
appropriate Name for the statistic channel. Unit is optional as is Description. The Active
checkbox enables a statistic channel to be temporarily disabled without having to delete it.
Value source
To select the channel from which the statistics are to be performed.
Type of statistic
188

May 2011
To select the type of statistic. "Moving" enables users to select between minimum /
maximum and the number of measured values from which the minimum/maximum is to be
calculated. "Evaluation block by block" enables users to select between a range of statistic
types. A block can be defined either as a set time interval or a triggerable channel.
"Generate interim values" outputs statistical values for the current measurement data
without affecting the overall statistical computations for the block (defined by time interval
or trigger).

Refer to other settings
Confirming the settings dialog saves the changes and the statistic channel will now appear
in the list.
2.3.4.2.5 Counter channel
A counter channel counts a channels 0/1-edges. Each channel has the functions count
up, count down, reset and setting.
Creating a counter channel

To create a counter channel, open the channel tab in DataSe rv ice Co nfig urato r and right
click software channels. Select Create channel and then Counter.

May 2011
189
The counter channel can now be configured using the settings dialog. First select an
appropriate Name for the counter channel. Unit is optional as is Description. The Active
checkbox enables a counter channel to be temporarily disabled without having to delete it.
190

May 2011
Count up
Enable "Count up" and select a channel to count up a counter channel. The selected
channel's 0/1-edge is then used for counting up. Either count up or count down must be
enabled.
Count down
Enable "Count down" and select a channel to count down a counter channel. The selected
channel's 0/1-edge is then used for counting down. Either count up or count down must be
enabled.
Reset
Enable "Reset" to reset a counter channel. The channel can then be reset either externally,
by enabling "Application" or by using a selected channel's 0/1-edge.
Conversion
For entering conversions. A lineared and scaled value is output instead of a counter status.

May 2011
191

Refer to additional settings
"Additional settings" tab
Set
Enable the "Set" option to select a channel that sets the counter channel. When the
selected channel has a 0/1-edge, the counter is set to the "Set value".
Value trigger
This option enables users to decide when the channel's counter status is to be output.
Selecting "Value Trigger" and a trigger channel enables the channel status to be output via
a trigger. Selecting "Interim Value", the counter status is output at regular intervals. Not
selecting an option means the counter status is output only before a rest or set. The
previous value is output for reset and set.
Confirming the settings dialog saves the changes and the counter channel will now appear
in the list.
Resetting a channel via the Application option is also possible via a context menu.
2.3.4.2.6 Creating test channels
To add a test channel, select the Channels tab from the DataSe rv ice Co nfig urato r and
right-click software channels. From the context menu, select Create channel and then Test
channel.
192

May 2011
A new dialogue now appears for configuring the test channel. Select an appropriate Name
for the test channel. If the test channel is to have a Unit enter it here. The Description
field is optional.

May 2011
193
Waveform
Select the required waveform for your test channel. The following waveforms are
available:
o Sine
o Square
o Triangle
o Sawtooth
Signal parameters
For setting signal parameters. Each parameter has the option for either a fixed value or
variable value.
194

May 2011
o fixed value
The parameter is assigned a fixed value that may be changed only via the settings
dialogue.
o variable value
The parameter's value derives from the selected channel. It is possible here to give
signals parameters using variables from a ProfiSignal- application (refer to Parametrising
signals) or to modulate using different signals (refer to Signal modulation).
The following parameters can be set:

o Frequency
Frequency depicts the number of oscillations per second and is measured in hertz.
Negative frequencies are not permitted and the test channel will return a negative
value.
The sampling rate depicts the number of calculated values per second. This should be
at least ten times higher than the frequency (max. 200Hz).
o Amplitude
Amplitude depicts the maximum height of the oscillations in both positive and negative
directions. The unit of amplitude corresponds to the unit entered above.
o Phase
Phase depicts the oscillation shift along the time axis. Phase is given in degrees () with
360 corresponding to one oscillation.

May 2011
195
o Offset
Offset depicts the shift along the Y-axis beginning from zero. The unit corresponds to
the unit entered above.

Refer to Advanced settings
The Noise tab
Noise
Noise simulates signal noise via external influences. A random number is either added or
subtracted to the calculated signal value. Random numbers lie between the set range
(either a fixed value or a different channel).
196

May 2011
Clicking OK accepts the input and the test channel will appear in the list.
Users can amend a channel's settings by double-clicking its tree entry, or by right-clicking
and then selecting Properties. Right-clicking and Delete channel deletes the channel. Rightclicking and Store channel in saves the channel to an existing database.

May 2011
197
Info:
Frequency has a peculiarity. Switching the data source to variable value displays a
further settings option: synchronize Signal. All test signals are then automatically
synchronized. A change in frequency then creates a jump in the signal. This is required
for fixed frequencies (or those that are set via an application) so synchronize Signal
requires checking (refer to Parametrising signals). The signal may not be synchronized for
fast changing frequencies. In this case the field should remain unchecked (refer to Signal
modulation).
2.3.4.2.6.1 Parametrising signals
Values can be dynamically assigned as parameters to signals /test channels without users
having to do anything extra. However, when a signal requires parametrising via a
Pro fiSig nal application, the following procedure is required:
1. First create a variable in the DataService Configurator for each parameter that you
wish to change and give it a meaningful name. The data source for the variable must
set to the application (refer to Creating variables).
198

May 2011
2. Now create the test channel with the waveform that you wish to use. If this has
already been performed, right-click the test channel and select properties. Users then
enter the variable created in (1) above in the test channel as a variable value for each
parameter.
3. The values for the variables can then be amended in ProfiSignal and will in this way
influence the test channel.

May 2011
199
Info:
synchronized. A change in frequency then creates a jump in the signal. This is
required for fixed frequencies (or those that are set via an application) so synchronize
Signal requires checking. For fast changing frequencies the signal should not be
synchronized (refer to Modulating signals).
Further information on working with Pro fiSig nal is available in the ProfiSignal help.
2.3.4.2.6.2 Modulating signals
Additional signal types can be generated for test channels. This requires the modulating of
multiple signals.
200

May 2011
Signal modulation functions almost identically to signal parametrising within an application.

The parameters are then also set as a variable value but instead of selecting a variable as
channel, another test channel is selected.
For example, the following signals can be created:
o
Modulated frequency
Modulated amplitude
Modulated offset
Fourier series development
Info:
synchronized. A change in frequency then creates a jump in the signal. This is required
for fixed frequencies (or those that are set via an application) so synchronize Signal
requires checking. For fast changing frequencies the signal should not be synchronized
(refer to Modulating signals).
To create a modulated frequency signal, a signal for the frequency must first be created.
Remember that a frequency signal with a negative value will subsequently create an invalid
value in a modulated signal. The signal frequency should also be lower than the modulated
signal's frequency.
1. Create a test channel as a "frequency" signal with the following settings:

May 2011
201
Name:
Frequency-signal
Unit:
Hz
Waveform:
Sinus
Frequency:
fixed value, 0.1 Hz
Sampling
rate:
50 Hz
Amplitude:
fixed value, 0.4
Phase:
fixed value, 0 Degree
Offset:
fixed value, 0.6

Settings dialogue
This signal returns values of between 0.2 Hz and 1 Hz.
2. Then create the frequency-modulated signal. Remember that the signal is not
synchronized in order to obtain a continuous run!
Name:
Frequency-modulated signal
Waveform:
Sinus
Frequency:
variable value, Channel:

Frequency-signal
Sampling rate: 50 Hz
Amplitude:
fixed value, 1
Phase:
Offset:
fixed value, 0
Settings dialogue
3. The frequency-modulated signal can now be viewed in Pro fiSig nal (refer to the online
analysis).
202

May 2011
Create an amplitude signal to enable generation of an amplitude-modulated signal.
1. Create a test channel as an"amplitude" signal with the following settings:

Name:
Amplitude-signal
Waveform:
Sinus
Frequency:
fixed value, 0.1 Hz
Sampling rate:
50 Hz
Amplitude:
fixed value, 1
Phase:
Offset:
fixed value, 0
Settings dialogue
2. Then create the amplitude-modulated signal.

May 2011
203
Name:
Amplitude-modulated signal
Waveform:
Sinus
Frequency:
fixed value, 2 Hz
Sampling rate:
50 Hz
Amplitude:
variable value, Channel: Amplitude-signal
Phase:
Offset:
fixed value, 0
Settings dialogue
3. The amplitude-modulated signal can now be viewed in Pro fiSig nal (refer to the online
analysis).
Create a signal for the offset to enable generation of an offset-modulated signal.
1. Create a test channel as an"offset" signal with the following settings:
204

May 2011
Name:
Offset-signal
Waveform:
Sinus
Frequency:
fixed value, 0.1 Hz
Sampling rate:
50 Hz
Amplitude:
fixed value, 1
Phase:
Offset:
fixed value, 0
Settings dialogue
2. Then create the offset-modulated signal.
Name:
Offset-modulated signal
Waveform:
Sinus
Frequency:
fixed value, 2 Hz
Sampling rate:
50 Hz
Amplitude:
fixed value, 1
Phase:
Offset:
variable value, Channel: Offset-signal
Settings dialogue
3. The offset-modulated signal can now be viewed in Pro fiSig nal (refer to the online
analysis).

May 2011
205
In a Fourier series any signal can be generated through the sum of sine and cosine signals.
The precision of the generated signal depends on the number of individual sine and cosine
signals. The Fourier series is made up of a base wave and any number of upper waves. The
upper waves are entered as offsets of the base wave / previous upper wave.
Introduction: Fourier series for a square signal

Upper wave frequencies are odd multiples of the base wave frequency.
Example:
Base wave frequency: 1 Hz
Frequency of the 1st upper wave: 3 Hz
Frequency of the 2nd upper wave: 5 Hz
...
The upper wave amplitude is the corresponding factor of the base wave amplitude. The
Fourier series amplitudes must be multiplied by 4/Pi.
Example:
Base wave amplitude: 1*4/Pi
Amplitude of the 1st upper wave: 1/3*4/Pi
Amplitude of the 2nd upper wave: 1/5*4/Pi
...
Info:
For possible phase shifts, the same as for frequencies applies: upper wave phase shifts
are odd multiples of base wave phase shifts.
A required offset must be entered in the final upper wave.
Execution: Fourier series for a square signal

Create a test channel with the following settings:
206

May 2011
Name:
Base wave
Waveform:
Sine
Frequency:
fixed value, 1 Hz

Amplitude:
fixed value, 1.27324
Phase:
Offset:
fixed value, 0
(1*4/Pi)
Settings dialogue
(an offset is possible here)

Name:
1. Upper wave
Waveform:
Sine
Frequency:
fixed value, 3 Hz

Amplitude:
(1/3*4/Pi)
Phase:
Offset:
variable value, Channel: Base wave

Settings dialogue
Name:
2. Upper wave
Waveform:
Sine
Frequency:
fixed value, 5 Hz

Amplitude:
(1/5*4/Pi)
Phase:
Offset:
variable value, Channel: 1. Upper wave

Settings dialogue
Name:
3. Upper wave
Waveform:
Sine
Frequency:
fixed value, 7 Hz

Amplitude:
(1/7*4/Pi)
Phase:
Offset:
variable value, Channel: 2. Upper wave

Settings dialogue
The square signal created with the Fourier series can now be viewed in Pro fiSig nal (refer

May 2011
207
to the online analysis).
Values for other Fourier series:

Fourier series square signal
Amplitude
Base wave
1. Upper wave
2. Upper wave
3. Upper wave
4. Upper wave
5. Upper wave
6. Upper wave
7. Upper wave
8. Upper wave
9. Upper wave
10. Upper wave
1.27324
Frequenc
y
1 Hz
0.42441
3 Hz
0.25465
5 Hz
0.18189
7 Hz
0.14147
9 Hz
0.11575
11 Hz
0.09794
13 Hz
0.08488
15 Hz
0.07490
17 Hz
0.06701
19 Hz
0.06063
21 Hz
208
Fourier series for a square signal

with 3 upper waves

May 2011
Fourier series for a square signal

with 15 upper waves
Fourier series for a square signal with 5
upper waves
Fourier series triangle signal
Amplitude
Base wave
1. Upper wave
2. Upper wave
3. Upper wave
4. Upper wave
5. Upper wave
6. Upper wave
7. Upper wave
8. Upper wave
9. Upper wave
10. Upper wave

May 2011
0.81057
Frequenc
y
1 Hz
-0.09006
3 Hz
0.03242
5 Hz
-0.01654
7 Hz
0.01001
9 Hz
-0.00670
11 Hz
0.00480
13 Hz
-0.00360
15 Hz
0.00280
17 Hz
-0.00225
19 Hz
0.00184
21 Hz
209
Fourier series for a triangle signal

with 5 upper waves
Fourier series for a triangle signal
with 1 upper wave
Fourier series sawtooth signal
Amplitude
Base wave
1. Upper wave
2. Upper wave
3. Upper wave
4. Upper wave
5. Upper wave
6. Upper wave
7. Upper wave
8. Upper wave
9. Upper wave
10. Upper wave
0.63662
Frequenc
y
1 Hz
-0.31831
2 Hz
0.21221
3 Hz
-0.15915
4 Hz
0.12732
5 Hz
-0.10610
6 Hz
0.09095
7 Hz
-0.07958
8 Hz
0.07074
9 Hz
-0.06366
10 Hz
0.05787
11 Hz
210

May 2011
Fourier series for a sawtooth signal

with 5 upper waves
Fourier series for a sawtooth signal
with 10 upper waves
2.3.4.2.7 Advanced settings

May 2011
211
Info:
The options available will depend on the type of software channel selected.
Default value
In the event of an error, the channel returns the Default value and a state that
corresponds to the error.
To test or to overwrite incorrect values, there is an option to permanently force a
Default value.
Persistence
An enabled persistence saves the current value when ending the DataService and loads
this value on restart. A non-active persistence loads the initial value at a DataService
restart.
Formatting
For users to enter the channel's fractional digits (decimal places).
Data reduction
By entering a tolerance, a channel's value changes only when the change is at the
input value. This can significantly reduce data volumes for values that vary only
slightly. Users can select between absolute (Unit) and relative (%) tolerances.
2.3.4.2.8 Formula editor
The formula editor enables formulae for calculation channels to be added, edited, deleted,
imported and exported.
The editor is opened via the software channel context from the channel option.
212

May 2011
The editor's left column lists all existing formula. Clicking a formula from the list on the left
displays it on the right as a "selected formula".
The formula can then be edited using the symbols from the task bar.
Adding a new formula

Opens a window to add a new formula (refer to save formula).

May 2011
213
Edit selected formula

Opens a window to edit the selected formula (refer to save formula). Changes are
made only to the formulae held in the formulary and not to the existing calculation
channels!
Delete selected formula

Deletes the selected formula. This deletes only the formula from the formulary and
not from existing calculation channels!
Import formula
Opens a dialog to select a formula file. All formulae held in the file are then
imported into the formulary. If a formula already exists with the same name, it will
be replaced when confirmed by the user. Imports do not affect existing calculation
channels!
Export formula
Opens a dialog to select a formula file to be created. Clicking "save" saves all
existing formulae to the selected file.
2.3.4.3 OPC channel configuration

To access channels from an OPC Server, users must first create a DataSe rv ice
Co nfig urato r OPC Client connection (refer to the OPC Client section).
The following is required to set up an OPC channel:
1.Select the Channels tab from the DataSe rv ice Co nfig urato r
2.Create an OPC Server (refer also to Element filter).
3.Create an OPC group.
4.Create an OPC channel.
Creating an OPC Server

Select the Channels tab from the DataSe rv ice Co nfig urato r and open the OPC Client
context menu.
214

May 2011
Selecting OPC-Server opens the Channel settings (OPC server @ OPC Client) window. Users
enter here the OPC Server connection parameters.
The OPC server @ OPC Client window

Active
Whether the server is enabled or disabled.
Channel name
The name to be displayed in the DataSe rv ice Co nfig urato r and Pro fiSig nal.
Unit
Any text permitted. Enter the required unit for the measurement data channel.
Location
The location of the OPC Server
Description
Any text permitted.

May 2011
215

Host
Enter the IP address or PC network name on which the OPC Server starts. Enter local
host or 127.0.0.1 when the OPC Server is on the same computer.
Info:
An OPC connection with a second PC is not possible without substantial changes to
user permissions on both participating Windows PCs. These should be carried out only
by experienced administrators (DCOM settings).
In contrast, connecting to an OPC Server on the same PC is normally possible with
local administrator permissions. For further information on user permissions, refer to
your OPC Server documentation or visit the OPC-Foundation website (http://
www.opcfoundation.org).
Server
The dropdown box displays all OPC Servers for the PCs under host (when this function is
supported).
If the required entry is not found, the server name may be input as an alternative.
Options
- Disable load item list from OPC Server
When the channel list is not requested from the server, tag names are to be input
216

May 2011
manually.
- Disable determine additional item properties
When optional channel properties are not requested from the server, long channel
lists are then quicker to obtain.
- Synchronous data transmission
Measurement data update from the server is usually delivered per callback. When this
option is enabled, the measurement data is requested in cycles.
- Connect only with OPC 1.0
For compatibility reasons, only a DA 1.0 connection is established even when the OPC
Server can support later versions.
After clicking OK, and when the connection has been successful, it will be displayed under
Connections in the DataSe rv ice Co nfig urato r. Be aware that the OPC Server and its
channels do not return entries for 'state'. Users can navigate multiple OPC Servers by using
the Previous and Next buttons.
The Element filter

Select the Channels tab from the DataSe rv ice Co nfig urato r and open the OPC Client
context menu. Select Change browser filter. This opens the following dialogue.
The dialogue enables users to set OPC filters. When the filter is enabled, only a section of
the channel list is requested from the Server.
Further information is available from the OPC Server documentation.

May 2011
217
Creating/amending OPC-Groups
Common settings for OPC channels take place within an OPC-Group. To create an OPCGroup, open the OPC Server's context menu:
This menu enables users to open the OPC Server configuration dialogue, to delete an OPC
Server or to create an OPC-Group. Selecting OPC-Group opens the following Channel
settings (OPC channel group @ OPC Client).
Active
Whether the Group is enabled or disabled.
Channel name
The name to be displayed in the DataSe rv ice Co nfig urato r and Pro fiSig nal.
Unit
Enter the required unit for the measurement data channel.
Location
Enter the OPC-Group's location.
Description
Describes the group.
218

May 2011
Update interval
Sets the update interval for all channels included, or to be included, in this group.
Activate / deactivate group automatically if required
Users can navigate multiple OPC-Groups by using the Previous and Next buttons. Clicking
OK creates the OPC-Group.
Creating/amending OPC channels

Open the OPC-channel context menu to create OPC channels.
This menu enables users to open the OPC-Group settings dialogue, to delete an OPC-Group
and to simultaneously create input channels, output channels or multiple channels.
Creating an OPC input channel

Context menu OPC-Group
Create channel
Input channel
This opens the Channel settings 'OPC Input'.
Main settings tab

May 2011
219
Advanced settings tab
Active
Whether the channel is enabled or disabled.
Channel name
The name with which the tag is to be displayed in the DataSe rv ice Co nfig urato r and
Pro fiSig nal.
Unit
220

May 2011
Input field for the unit.

Location
Input the OPC-Group's location.
Description
Describes the group.
Formatting/ Fractional digits
Enter the number of fractional digits (decimal places).
Data reduction/ Tolerance
Sets the tolerance range for all channels included, or to be included, in this group.
Force default value
Select the OPC Server's channel to be used from the Tag name field. Select from the
dropdown box and then the tag name.
This then displays a tree structure with the OPC Server's available channels. Select the
channel you wish to use.

May 2011
221
Select the corresponding values from data type and Valid value range, checkbox Active and
save by clicking OK.
Use the Previous and Next buttons to navigate multiple OPC channels. Clicking OK creates
the OPC channel.
This completes the creation of the OPC channel and its measurement data can now be
displayed under the DataSe rv ice Co nfig urato r Channels option. Information is also
displayed on the channel's 'State'.
Left-clicking the input channel opens the following context menu:
222

May 2011
This menu enables users to open the Channel settings dialogue, to delete a channel and to
set the database to which the data from the channel is to be stored.
Creating an OPC output channel

Create channel
Output channel
Set the output in the same way as for input channels and ensure that the selected tag is
writeable.
Left-clicking the channel opens the following context menu:
This menu enables users to open the Channel settings dialogue, to delete a channel and to
set the database to which the data from the channel is to be stored. It is also possible to
set the output channel's value. Any value can be set using the Value x option. The output
is also writeable from Pro fiSig nal.
Creating multiple OPC channels

Create channel
Create several channels
This opens the Create several channels dialogue.

May 2011
223
Users can enter here the number of input / output channels required. Clicking OK sets up
the channels, which then require configuring. Users then need to open the appropriate
configuration dialogues for either input or output channels.
2.3.4.4 Configuring Modbus channels

To access the registers of a Modbus device, firstly create a connection to the device in
the DataSe rv ice Co nfig urato r (refer to the Modbus device section). Once a connection
has been made users can assign input channels, output channels or query channels. For
query channels there are also special types of input channels.
Click the Channels tab of the DataSe rv ice Co nfig urato r and open the Modbus context
menu for your connection.
Clicking Properties opens the Channel settings (Modbus TCP @ Modbus) window. This
enables input of the Modbus connection parameters.
224

May 2011
Input channel @ Modbus window

Active
Channel name
The name under which the connection is displayed in the DataSe rv ice Co nfig urato r and
Pro fiSig nal.
Location
The Modbus device's location.
Description
Text field.
Main settings
Update interval
To select the update interval for the Modbus connection.
Merge queries
To select whether the queries from individual input channels are to be merged. This can
reduce the number of queries sent to the Modbus device.
Creating a Modbus input channel

May 2011
225
Clicking Modbus-Input opens the Channel settings (Modbus input channel @ Modbus)
window. This enables input of the input connection parameters.
226

May 2011

Active
Channel name
Pro fiSig nal.
Unit
Text field. Enter the required unit of measurement for the data channel.
Location

May 2011
227
Description
Text field.
Main settings
Function name
To select a function for reading out data from the registers of the connected Modbus
device.
Device address
The slave's address to be accessed.
Reference
The starting register for the selected function
Number of Coils / Number of registers
The number of coils / registers to be read using the selected function. This entry
depends on the selected data type and can not be manually altered.
Datatype settings
To select how received data is to be interpreted. Not every setting is available for some
functions.
o Data type
The data type for received data. Depending on the function selected, bit, integer
and float are available.
o Signed
This sets whether the data type range is positive only or may include negative
values.
o Bit length
The bit length that the data type is to have
o Bit order
The bit order the received data is to have. For each register to be read, the Modbus
device returns two bytes. The byte
order determines whether the the high-value
byte (big endian) or low-value byte (little endian) is to be received first.
o Word order
The word order the received data is to have. When data is to be received from
multiple registers, this determines whether
the high-value register (big endian) or
low-value register (little endian) is to be received first.
Valid value range
Minimum and maximum values for the selected data type
Check timeout
This option can be selected for any number of channels. If the Modbus driver receives
no data over a long time period and this option has been selected for at least one
channel, then the connection will be interrupted through a timeout.
228

May 2011
Creating a Modbus output channel

Clicking Modbus-Output opens the Channel settings (Modbus output channel @ Modbus)
window. This enables input of the output connection parameters.

May 2011
229
Output channel @ Modbus window

Active
Channel name
Pro fiSig nal.
Unit
Location
230

May 2011

Description
Text field.
Main settings
Function name
device.
Device address
Reference
The number of coils / registers to be written to using the selected function. This entry
Data type settings
To select how data is to be sent. Not every setting is available for some functions.
o Data type
The data type for sent data. Bit, integer and float are available depending on the
selected function.
o Signed
values.
o Bit length
o Bit order
The bit order the sent data is to have. Two bytes are sent to the Modbus device for
each register to be written to. The
byte order determines whether the the highvalue byte (big endian) or low-value byte (little endian) is to be sent first.
o Word order
The word order the sent data is to have. When data is to be sent to multiple
registers, this determines whether
the high-value register (big endian) or low-value register (little endian) is to be sent
first.
Reference
To determine whether the data is to be manually input or sent from a channel.
Valid value range

May 2011
231
Creating a Modbus query channel

Clicking Modbus-Query opens the Channel settings (Query channel @ Modbus) window. This
enables input of the Modbus connection parameters.
232

May 2011

Active
Channel name
Pro fiSig nal.
Unit
Location

May 2011
233

Description
Text field.
Main settings
Function name
device.
Device address
Reference
The number of coils / registers to be read using the selected function.
Check timeout
This option can be selected for any number of channels. If the Modbus driver receives
no data over a long time period and this option has been selected for at least one
channel, then the connection will be interrupted through a timeout.
The data that is delivered from the Modbus device for this query is not directly displayed in
the relevant channel. Instead it is possible to assign to a query channel any number of
special input channels that extract information from the data that has been acquired from
the query.
Creating a Modbus input channel for queries

Select the Channels tab from the DataSe rv ice Co nfig urato r and open the context menu for
Modbus query channels.
Clicking Modbus-Input(Query) opens the Channel settings (Modbus-Input(Query) channel @

Modbus) window. This enables input of the input-query connection parameters.
234

May 2011

Active
Channel name
Pro fiSig nal.
Unit
Location

May 2011
235

Description
Text field.
Main settings
Function name
The function name for the relevant Modbus query.
Device address
The slave address for the relevant Modbus query.
Reference
The number of coils / registers to be read using the selected function. This entry
Datatype settings
To select how received data is to be interpreted. Not every setting is available for some
functions.
o Data type
The data type for received data. Bit, integer and float are available depending on the
selected function.
o Signed
values.
o Bit length
o Bit order
The bit order the received data is to have. For each register to be read, the Modbus
device returns two bytes. The byte
order determines whether the the high-value
byte (big endian) or low-value byte (little endian) is to be received first.
o Word order
The word order the received data is to have. When data is to be received from
multiple registers, this determines whether
the high-value register (big endian) or
low-value register (little endian) is to be received first.
Valid value range
236

May 2011
2.3.5
Dialogue functions/ General
The functioning is similar for all dialogue windows and is described here using the analog
input as an example.
Functions in the header section:
Enables the channel. Transfer of data from the device is now possible.

May 2011
237
For inputting the measurement point name, e.g. Power1.
For inputting the measurement point's measurement unit, e.g. N.
For inputting a description of (or comment on) the measuring point , e.g. B. Pump 3.
Functions in the footer section:
Switch to previous / next channel and display the corresponding dialogue. Determined by
the channel number.
Accepts all new settings and transmits these to the device.

Closes the dialogue.
Cancels the settings procedure. Closes the dialogue.
Accesses the electronic Help manual.
238

May 2011
Select the
Functions in Advanced settings:
For inputs:
In the event of an input channel failure, the Default value (instead of the measurement
value) is transmitted from the device to the PC.
For outputs:
In the event of an output channel failure, the Default value (instead of the output value) is
transmitted from the device to the PC.
For PC data recording, users can input here data reduction tolerances. In the example
shown, measurement data is stored only when the change is greater than 0.5 N.
Enter here the required accuracy for the measured or output value.

May 2011
239
Select the
Sensor correction tab
Functions in Sensor correction:
Enables sensor correction, i.e. a manual calibration.
Select whether one, two or three calibration points are available.
Enter the calibration points (with correct and measured values). The example shown is
from a temperature measurement with calibration at 0C and 100C.
240

May 2011
2.3.6
Database option
The DataSe rv ice Co nfig urato r database enables large volumes of measurement data to be
continuously recorded and/or trigger recording.
The amount of data that can be stored is restricted only by the amount of available
storage space.
Database functions
The primary aim of a database is to provide archived data for Yt (trend) diagrams in
addition to current data coming from the channel. This is best explained using an example.
Example:
Two analog channels are available for measuring temperatures. One channel is saved to a
database, the other not. The two channels are portrayed in a Pro fiSig nal trend diagram.
The difference between the channels is that one is portrayed from when the user assigned
the channel to the trend while the other is portrayed from when the channel was assigned
to the database. Furthermore, the channel not being stored to a database may only
portray data for a maximum period of 24 hours. Older data is then automatically deleted.

May 2011
241
Users can display the contents of a database via the Pro fiSig nal-main menu Show
database in Trend or via the ProfiSignal toolbar symbol.
Info:
When users require measurement data to be continuously saved to a database, it makes
sense to run the DataSe rv ice as a Windows service (Install DataService as a service
option on installation).
The measurement data is then saved as a background service without requiring
Pro fiSig nal to be started. The user is not even required to be logged into the Windows
system. Data is saved to the database as soon as Windows starts (i.e. from when the
log in screen is being displayed).
This function is not enabled during a standard Pro fiSig nal installation. To enable the
function following installation, do the following:
Re-run the Pro fiSig nal setup
Select Change program
Checkbox install as Service against the DataService option
Follow the installation instructions
When to use a database

1. Continuous measurement data recording
The DataSe rv ice Co nfig urato r database function should be used for continuous
measurement data recording (e.g. continuous operational data acquisition). The entire
recorded data from a channel can then be portrayed within a single diagram.
If measurement data needs recording only for a fixed time period it usually makes more
sense to use a Pro fiSig nal recorder object (refer to the Recorder visualization object).
Both recorder object and database functions can be combined. For example, data from a
channel can be recorded continuously to a database over periods of years with occasional
storage using recorders for specific time periods.
242

May 2011
2. Centralized data storage

For when measurement data requires centralized storage within a network (DataSe rv ice as
server). Other Pro fiSig nal-PCs within the network need to be able to access this data
when required. When measurement data is stored to a server database, any Pro fiSig nalPC then has access to the data. This requires that the client PCs are linked to the server
via a DataSe rv ice connection (refer to the DataService connection section).
2.3.6.1 Adding a measurement database

The DataSe rv ice Co nfig urato r enables data to be gathered in a database for: continuous
measurement data recording; the display of archived data in a single diagram; the running
of the DataSe rv ice as a centralized server.
Info:
When users require measurement data to be continuously saved to a database it makes
sense to run the DataSe rv ice as a Windows service (Install DataService as a service
option on installation). Refer to the Info in Database option section for information on
requirements and installation.
Adding a measurement database

Procedure
1. Select the Database tab.
2. Enable the context menu from the DataService entry and select Add measurement
database.

May 2011
243
3. This opens the Measurement database settings window for inputting the database's
basic settings.
The General tab
244

May 2011
Name (text field)

The database name that is displayed in the DataSe rv ice Co nfig urato r.
Enable storage
Sets whether measurement data can or can not be stored to the database.
Comment (text field)
Any text permitted.
Storage place (section)
Sets the database's file name and path.
o Path (text field)
Full path of the directory in which the database is to be stored.
o Filename (without extension) (text field)
File name for the database.
o Select (button)
Opens a file selection dialogue for users to select the required file path and name.
The Duration / Size tab

May 2011
245
The database size can be set via the Duration / Size tab. Each input field for this tab sets
the conditions for deleting the oldest stored data (ring storage). The different fields can be
used cumulatively. Users should in no event disable all three input fields.
Storage duration(numeric field)

Sets the number of days after which measurement data is deleted from the database.
A 0 value disables the function; daily deleting of measurement data is then dependent
on the Maximum database size and Minimum free drive space fields.
Maximum database size (numeric field)
Restricts the database to a set size. When the size has been reached, deletion of the
oldest data then takes place on a daily basis.
The ring memory is organized according to days and it is possible for the oldest day
value to be deleted before the maximum database size is reached. A value of 0 disables
this function.
Minimum free drive space (numeric field)
Sets the free space limit at which the oldest data is then deleted.
This value should be at least 100Mb to ensure functioning of the Windows system is not
impaired.
A value of 0 disables the function, but to then ensure a fully functioning operating
system requires a Maximum database size setting .
This restriction is recommended primarily when using one database per Windows drive.
For multiple databases on one Windows drive, the Minimum free drive space setting
should be the same for all databases otherwise only the database with the highest
value will be reduced.
It is however safer to use a Maximum database size setting as the main regulator.
246

May 2011
The Trend optimization tab
The slide-control in the Trend optimization tab corresponds to the Measurement data
cache size and Storage interval settings in the server main settings.
The slide-control is set according to whether a fast or slow update speed per channel is
required for the graphical portrayal of the trend Pro fiSig nal. This results in an average
data-resolution for all channel data within the selected database. The stored blocks, in
addition to the real time data, can then be optimized to enable high-speed trend portrayal.
The Backup tab

May 2011
247
This tab determines whether the database should be automatically backed up. When an
Automatic database backup is required, then a backup path must also be provided. This
can be input either manually or via the Select button.
A backup takes place daily at around 30 minutes following midnight (UTC time).
The Filter tab
The Filter settings determine when data is to be transmitted to the database.
Data reduction
Select here whether the data resolution is to be reduced through averaging prior to
storage. Data reduction is disabled as default (recommended).
Info:
Data reduction functions in relation to Trend optimization.
Storage mode (radio buttons)

o Always (radio button)
Data is continuously stored to the database at intervals set under the Data storage
tab.
248

May 2011
o Timerange (radio button and time range input fields)
When Timerange is enabled, the Starttime and Stoptime can be set during which
measurement data is stored. This can be useful, for example, in non-continuous but
repetitive machine run times.
o Level trigger (radio button / dropdown box)
When Level trigger is enabled, a channel can be selected from the Trigger dropdown
box.
Measurement data is then stored when this channel delivers a value greater than zero.
If the value is equal to or less than zero, storage is disabled.
o Edge trigger (dropdown box / radio buttons)
When Edge trigger is enabled, separate channels can be selected for starting and
ending storage to a database.
4. Closing the Measurement database settings window with OK sets up the database.

May 2011
249
Left-clicking a database opens the following context menu:
This enables you to temporarily disable/ enable storage to the database. Users may also
amend database settings or delete a database.
2.3.6.2 Storing channels to databases

After setting up a database, users must assign the channels that are to be saved to the
database. The assigning of channels takes place via the Channels option of the
A channel is assigned to a database by right-clicking the channel and selecting the
database from Context menu Store channel in DataBase
Database name.
Once the channel has been assigned to the database it appears as a sub-entry in the
database view.
Repeat the procedure to assign more channels to the database. An alternative method to
using the context menu is to display both panels of the DataSe rv ice Co nfig urato r and to
use the mouse to drag and drop the channel from the channels view to the database view.
250

May 2011
A saving tolerance is optional for any channel. This is set from the channel context menu
within a database. The tolerance can be selected as a percentage or as an absolute
corresponding to the measurement data's unit of measurement
Note: Saving and computation of the tolerance always takes place as an absolute in
measuring units. Changes to the measurement range does not affect the tolerances being
applied.

May 2011
251
2.3.7
Alarm manager
The Pro fiSig nal alarm manager is made up of the following components:
Alerting
Alerting is a part of the DataSe rv ice and is responsible for monitoring alarm sources,
recording alarms and performing actions in the event of an alarm. Configuration takes
place in the DataSe rv ice Co nfig urato r.
Alarm table
The alarm table is part of Pro fiSig nal and is required for portraying alarms. Configuration
takes place within a Pro fiSig nal-application (refer to the Pro fiSig nal Alarm table
documentation).
The alarm manager has the following functions:
Monitoring of threshold values

Monitoring status information
Monitoring connections (refer to the Connections option section)
Monitoring recording (refer to the Database option)
Monitoring read-out procedures (refer to the Scheduler option)
Sending of emails or faxes in the event of an alarm
Activation of sirens and warning lamps
Grouping alarms according to class
Prioritizing alarms
Alarm acknowledgement including confirmation input
The following sub-sections provide detailed information on alarms:

Alerting settings
Action settings
Alarm class settings
Alarm rule settings
252

May 2011
2.3.7.1 Alerting settings

To perform alarm settings, first select the DataSe rv ice Co nfig urato r Alerting option. Now
open the context menu for the DataService ID ...entry
Users now have the following options:

To save previously made Alarm settings. This opens a dialogue window.
To load previously made Alarm settings. This opens a dialogue window.
To make alarm settings.
Selecting Alerting settings opens the following dialogue.

May 2011
253
General tab
254

May 2011
Select the alarm database location using the Select button.

Horn channel
Select a writeable channel from a device. This channel is set to 1 when a new alarm
occurs. The channel is reset to 0 in ProfiSignal's alarm table by confirming the alarm or in
a ProfiSignal-Klicks script.
Reset alert horn channel

Select a channel from a device. A horn is confirmed when there is a rising edge for this
channel.
Warning light channel

Select a writeable channel from a device. When the conditions occur that were selected in
warning light mode, this channel is set to 1. When the conditions are no longer true, the
channel is reset to 0.
Warning light mode

May 2011
255
Input when the warning light is to be activated.
Retrigger alert horn

When the horn is to be retriggered (with the warning light enabled), then select the time
interval after which the horn is to sound from the dropdown list.
Info:
Alarm databases can be saved only to a local hard drive and not to a network resource.
Backup tab
Automatic backups can be made of alarm databases. Backups take place once a day.
Select the alarm database location using the Select button.
EMail server tab
256

May 2011
To be able to send emails, users require an accessible SMTP server within their network.
Enter the required information about the SMTP server in the following fields. The
information should be available from your network administrator.
SMTP server
Username
Password / Password rep.
Sender address
Sender domain

May 2011
257
When an SMTP server is not available via the LAN, emails can also be sent via an existing
dial-up (RAS) connection. Users then select RAS entry against Connection and enter the
following information:
RAS entry
Username
Alarm collecting
To avoid having to send emails for each alarm, there is an option to collect alarms and send
them as a batch in one email.
The message can be sent directly in the email's subject line, e.g. for sending to an SMS
Gateway.
For alarms that are to be sent to multiple email-recipients normally just one email is
generated for all recipients. If each recipient is required to receive a separate email, set
the option Create a separate email for each user. This option is useful for SMTP servers
that reject emails when the recipient address is invalid.
Send attempts
For setting the number of attempts at sending the email to the SMTP server. When the
email fails to send, an error message is generated and displayed in the Pro fiSig nal alarm
table.
Info:
Username / password entries are optional and depend on the SMTP server.
Domain input is also optional and dependent on the SMTP server.
Fax server tab
258

May 2011
Alarm collecting
To avoid having to send emails for each alarm there is an option to collect alarms and send
Gateway.
2.3.7.1.1 EMail server set-up
Email server tab

May 2011
259
To be able to send emails, users require an accessible SMTP server within their network.
Enter the required information about the SMTP server in the following fields. The
information should be available from the network administrator.
SMTP server
Username
Sender address
Sender domain
When an SMTP server is not available via the LAN, emails can also be sent via an existing
dial-up (RAS) connection. Users then select RAS entry against Connection and enter the
following information:
RAS entry
Username
Alarm collecting
Gateway.
For alarms that are to be sent to multiple email-recipients normally just one email is
generated for all recipients. If each recipient requires a separate email, set the option
'Create a separate email for each user'.
This option is useful for SMTP servers that reject emails when the recipient address is
invalid.
Send attempts
For setting the number of attempts at sending the email to the SMTP server. When the
email fails to send, an error message is generated and displayed in the Pro fiSig nal alarm
table.
Info:
Username / password entries are optional and depend on the SMTP server.
260

May 2011
Domain input is also optional and dependent on the SMTP server.
2.3.7.1.2 Fax server set-up
Fax server tab
Alarm collecting
Gateway.
2.3.7.2 Actions
When an alarm occurs as a result of a rule, assigned alarm actions are performed. The
following procedures are required to set up actions.
Notification
1. Select the Alerting tab in the DataSe rv ice Co nfig urato r.

May 2011
261
2. Open the Actions context menu and select Add notification action.
262

May 2011
3. This opens the Alarm action settings window that enables determining of alarm actions.
Active
Enables the action. When disabled, this action will not be performed when an alarm occurs.
Name
Enter a meaningful name for the action.
Comment
For additional information about the action.
Add notification action

May 2011
263
Select the type of notification (advice) and the recipient of the notification (advice). Other
fields will appear depending on the type of notification (advice). Enter the fields and add
the notification to the table by clicking the Add button.
Notification options:
Set output
Sets the selected channel to the entered value.
Send email
The selected user is notified of the alarm by email. By selecting a user group, all
members of the user group are notified.
Send fax
The selected user is notified of the alarm by fax. By selecting a user group, all members
of the user group are notified by fax.
Hold-up time
The time required from the alarm occurring up to notification being actioned. If the alarm is
confirmed before the hold-up time is reached, notification will not take place. The hold-up
time can be used to create a notification chain.
Deleting / amending a notification

From the table, select the notification that is to be deleted / amended and click the
Remove button. The selected line is then removed from the table and the contents are
placed into the notification settings fields. Users can then make amendments and then
reinsert the amended notification into the table by clicking Add.
Clicking OK will display the new action under the Alerting tab. Disabled actions are
portrayed as grayed-out. Left-clicking an action opens a context menu to either open the
settings dialogue or delete an action. Deleting an action is possible only when the action is
not being used by a rule.
Storage
In addition to the permanent recording of measurement data to a measurement database,
the alarm manager enables recording of pre and post data in an alarm event. Following the
post-trigger period of an alarm event, a measurement data file is generated for the given
time period, and linked to the alarm.
The measurement data file can then be displayed in the fault analysis of Pro fiSig nal's
alarm list .
1. Select the Alerting tab in theDataSe rv ice Co nfig urato r.
264

May 2011
2. Open the Actions context menu and select Add storage action.

May 2011
265
Active
Name
Comment
Storage
Enter the path of the measurement data file's location and how the file name is to be
constructed.
266

May 2011
Pretrigger / Posttrigger
Enter the period of time during which data is to be recorded before (pre) and after (post)
the alarm.
Source
Enter the source from which the measurement data is to be saved. The source can be an
existing database or a memory group within a Message device. Ensure that all selected
channels are being saved to the required source.
If an Automatic source is selected, the channels will be automatically and temporarily
saved. It is not necessary for channels to be recorded to either a database or Message
device memory group.
Channels
Select all the channels from which data is to be recorded in an alarm event. Use Add
channel to insert these into the list of channels to be recorded.
Import trend configuration
In addition to the option of manually selecting channels, users can also import a previously
set up trend configuration.
This will import trend settings as well as channels. If a measurement data file is to be
generated in the event of an alarm, the file will contain the trend settings and can be
displayed using these settings.
If a trend configuration is to be imported, the selected channels may not be manually
amended.
Info:
To avoid measurement data loss, ensure that the Message device and PC are time
synchronized.
2.3.7.2.1 Notification set up
Notification
1. Select the Alerting tab in the DataSe rv ice Co nfig urato r.

May 2011
267
2. Open the Actions context menu and select Add notification action.
268

May 2011
Active
Name
Comment
Add notification action

May 2011
269
Select the type of notification (advice) and the recipient of the notification (advice). Other
fields will appear depending on the type of notification (advice). Enter the fields and add
the notification to the table by clicking the Add button.
Notification options:
Set output
Sets the selected channel to the entered value.
Send email
The selected user is notified of the alarm by email. By selecting a user group, all
members of the user group are notified.
Send fax
The selected user is notified of the alarm by fax. By selecting a user group, all members
of the user group are notified by fax.
Hold-up time
The time required from the alarm occurring up to notification being actioned. If the alarm is
confirmed before the hold-up time is reached, notification will not take place. The hold-up
time can be used to create a notification chain.
Deleting / amending a notification

From the table, select the notification that is to be deleted / amended and click the
placed into the notification settings fields. Users can then make amendments and then
reinsert the amended notification into the table by clicking Add.
Clicking OK will display the new action under the Alerting tab. Disabled actions are
settings dialogue or delete an action. Deleting an action is possible only when the action is
not being used by a rule.
2.3.7.2.2 Storage set up
Storage
In addition to the permanent recording of measurement data to a measurement database,
the alarm manager enables recording of pre and post data in an alarm event. Following the
post-trigger period of an alarm event, a measurement data file is generated for the given
time period, and linked to the alarm.
The measurement data file can then be displayed in the fault analysis of Pro fiSig nal's
alarm list .
270

May 2011
2. Open the Actions context menu and select Add storage action.

May 2011
271
Active
Name
Comment
Storage
Enter the path of the measurement data file's location and how the file name is to be
constructed.
272

May 2011
Pretrigger / Posttrigger
Enter the period of time during which data is to be recorded before (pre) and after (post)
the alarm.
Source
Enter the source from which the measurement data is to be saved. The source can be an
existing database or a memory group within a Message device. Ensure that all selected
channels are being saved to the required source.
If an Automatic source is selected, the channels will be automatically and temporarily
saved. It is not necessary for channels to be recorded to either a database or Message
device memory group.
Channels
Select all the channels from which data is to be recorded in an alarm event. Use Add
channel to insert these into the list of channels to be recorded.
Import trend configuration
In addition to the option of manually selecting channels, users can also import a previously
set up trend configuration.
This will import trend settings as well as channels. If a measurement data file is to be
generated in the event of an alarm, the file will contain the trend settings and can be
displayed using these settings.
If a trend configuration is to be imported, the selected channels may not be manually
amended.
Info:
To avoid measurement data loss, ensure that the Message device and PC are time
synchronized.
2.3.7.3 Alarm class settings

When an alarm is triggered by a rule, the alarm will be assigned to up to three classes. Use
alarm class to group the alarms. Users can filter and sort alarms in Pro fiSig nal's alarm
table according to class.
Adding an alarm class


May 2011
273
2. Open the Classes context menu and select Add class.
3. This opens the Alarm class settings window that enables determining of classes.
Active
Enables the alarm class. When the class is disabled, no alarms are generated for this class.
Name
Enter a meaningful name for the alarm class.
Comment
For additional information about the alarm class.
Info:
Users can disable an alarm class when, for example, the equipment being monitored is not
running. There will then be no alarms occurring for this equipment.
274

May 2011
Clicking OK will display the alarm class under the Alerting tab. Disabled classes are
settings dialogue or delete a class. Deleting a class is possible only when the class is not
being used by a rule.
2.3.7.4 Alarm rule settings

An alarm rule determines the conditions under which an alarm is triggered. Examples of such
conditions are a threshold violation or a device network failure. The rule also contains the
priority at which the alarm is triggered and the class to which the alarm is assigned (refer
to the Alarm class settings section).
Adding a rule
2. Open the Rules context menu and select Add rule.
Note: In order for a rule can be created at least one class is required.

May 2011
275
3. This opens the Alarm rule settings window for determining the conditions under which
alarms are triggered.
The General tab

Active
Whether the rule is enabled or disabled. Only enabled rules can trigger alarms.
Name
Enter a meaningful name for the alarm rule.
Comment
For additional information about the alarm rule.
276

May 2011
Priority
An alarm is triggered with a priority of between 1 and 9 (1 = highest priority, 9 = lowest
priority). New alarms can be filtered in the Pro fiSig nal alarm table according to priority
(displays only alarms with a priority of up to x).
Confirmation needed
Determines whether confirmation of the alarm is required. The alarm then remains in the
Pro fiSig nal alarm table until it is confirmed. Confirmation of an alarm takes place in the
Pro fiSig nal alarm table.
Suppress alarms at restart
The conditions of the rule are tested for the first time once the rule is operational (i.e.
following the Okaying of this dialogue and restarting the DataSe rv ice ). This option
determines whether an alarm is triggered when the conditions are true at the first time of
testing. When enabled the alarm will not trigger at the first time of testing for the
conditions, only from the second time (rising edge).
Mode
Sets the mode on how the individual observations (on the Observations tab) function with
each other.
At least 1
The alarm is triggered as soon as the condition is true for one observation. The alarm is
marked as over when the observation condition is no longer true. A new alarm can only
be triggered once the previous alarm is over.
At least 2
The alarm is triggered as soon as the conditions are true for two observations. The
alarm is marked as over when the observation conditions are no longer true. A new
alarm can only be triggered once the previous alarm is over.
At least 3
The alarm is triggered as soon as the conditions are true for three observations. The
At least 3
The alarm is triggered as soon as the conditions are true for three observations. The
Each separate observation
Each observation triggers its own alarm independently from one another as soon as the
condition for the observation is true. The alarm is marked as over when the condition
for the triggering observation is no longer true.
Delay
Enter the length of time the conditions must remain true for the alarm to be triggered. Use
the delay option to allow tolerances for short-term anomalies.
Message

May 2011
277
Enter the message that is to be displayed for a triggered alarm. The message may use
placeholders. The placeholder will be processed at the time of the alarm being triggered.
%name%, %comment%, %location%

The placeholders are replaced by the name or channel name, description and location of
the triggering source, e.g. a channel or a connection.
%reason%
This placeholder is replaced by text giving the reason for the alarm.
For example, Exceeded 100C. In this case the value is taken from the monitoring threshold
value and the unit of measurement from the properties of the channel being monitored.
Assigned alarm classes

A triggered alarm can be assigned up to thee classes. Enter here the alarm classes that
are to be assigned to a new alarm. Only those classes that are enabled at the time of the
alarm can be assigned.
When there are no classes enabled at the time of the alarm, the alarm will be suppressed.
Info:
If only alarms up to priority 8 are being displayed in the Pro fiSig nal alarm table, a rule at
priority 9 then triggers alarms that are hidden to the user. Such alarms can then be
displayed , for example, in the global alarm table in Pro fiSig nal.
For the Each separate observation mode setting, the message placeholders are replaced
by the triggering observation.
Observations tab
278

May 2011
At least one observation per alarm rule requires defining. If Ignore value state is
unchecked, the rule will also be applied to the monitored channel when the value's state is
invalid. When checked, only valid values are considered.
Add observation
Select the Observation type and then the Observed channel. Other fields will appear
depending on the type of observation. Enter the fields and add the observation to the table
by clicking the Add button. If Ignore value state is checked, every measurement value is
observed whether invalid or not. When unchecked, only valid values are observed.
Observation types:
Value overrun check
Monitors the channel for overruns on preset thresholds. The hysteresis indicates the
extent of the underrun required to enable the observation to return a not true result

May 2011
279
following an overrun.
Value underrun check
Monitors the channel for underruns on preset thresholds. The hysteresis indicates the
extent of the overrun required to enable the observation to return a not true result
following an underrun.
Value band violation
Monitors the channel for underruns or overruns on preset thresholds. The hysteresis
indicates the extent of the underrun / overrun required to enable the observation to
return a not true result following a threshold violation.
Value high
Monitors a digital channel for an ON or HIGH status.
Value how
Monitors a digital channel for an OFF or LOW status.
Value state check
Monitors the channel for the occurrence of a selected state. The observation returns a
not true condition when neither of the selected states occur.
Value rate of change check
Monitors whether a channel's rate of change overruns the given limit. The hysteresis
input indicates how far, following an overrun, the limit has to underrun so that
monitoring again returns an unfulfilled status.
Value is frozen
Monitors a channel over a set time interval for values that fail to change (i.e. no new
values or values remain the same).
Device connection
Monitors whether a connection exists to the given device. An alarm is triggered when
the connection is interrupted or disabled.
DataService connection
Monitors whether a connection exists to the given DataSe rv ice . An alarm is triggered
when the connection is interrupted or disabled.
Measurement database error check
Monitors the recording of measurement data to the given measurement database (refer
to the Database option). An alarm is triggered when an error occurs during recording or
when a recording is disabled.
Scheduler error check
Monitors the running of the given scheduler (refer to the Scheduler option). An alarm is
triggered when an error occurs during the running of the scheduler or when the
scheduler is disabled.
Thresholds (limits) can be fixed or dynamic during monitoring. To use dynamic thresholds
switch Manual input to Channeland select the channel from which the threshold is to be
taken.
Deleting / amending an observation

From the table, select the observation that is to be deleted / amended and click the
placed into the Observation settings fields. Users can then make amendments and reinsert
the amended observation into the table by clicking Add.
280

May 2011
Actions tab
When an alarm is triggered it is entered into the alarm database and can be displayed in
the Pro fiSig nal alarm table.
Alarm actions may also be triggered (refer to Action settings). Users can select here the
actions to be triggered when a new alarm occurs for this rule.
Clicking OK will display the new rule under the Alerting tab. Disabled rules are grayed-out.
Left-clicking a rule opens a context menu to either open the settings dialogue or delete a
rule.

May 2011
281
2.3.8
Scheduler option
Every Me ssag e device is equipped with an internal data storage capability (T o pMe ssag e
up to 1GB, Lo g -/ Pro fiMe ssag e from 1GB) and is therefore able to function independently.
Data stored in the devices can then be transmitted to PCs via the DataSe rv ice and then
evaluated as required. The Scheduler (time planner) automates the reading out of data
from a Me ssag e device's internal memory.
Adding a scheduler event

1. Select the Scheduler tab in theDataSe rv ice Co nfig urato r.
2. Open the DataService context menu and select Add scheduler event.
3. This opens the Scheduler event settings window that enables configuring of
scheduler events.
282

May 2011
The following sub-sections provide detailed information on the scheduler function:

General settings
Memory read-out
Database backup
The event will appear in the tree structure when the dialogue is closed with OK.

May 2011
283
Left-clicking the event opens a context menu from which users can then open the settings
dialogue. The context menu also enables users to delete an event and to manually trigger
an event - for events that can be triggered manually (refer also to General settings). If an
event is currently running, it can be aborted via the context menu.
2.3.8.1 General settings
The General tab

The General tab determines when the scheduler event is to run.
284

May 2011
Active (checkbox)
The scheduler event runs only when enabled.
Name (text field)
The display name for the scheduler event.
Comment (text field)
For entering additional information.
Release and Schedule sections

These sections are used to determine the times at which scheduler events are triggered.
The options available in the Schedule section will depend on the radio button selections
made in Release.
When for example a delay is expected in updating the database, a Release delay can be
enabled and a time delay selected from the dropdown list.

May 2011
285
Once (radio button)

The scheduler event is performed once at the time given in Next event in the
Schedule section.
The Timerange field is used to determine the internal memory's time range from which
the data is to be read. When for example a delay is expected in updating the
database, a Release delay can be enabled and a time delay selected from the
dropdown list.
Cyclic (radio button)

The scheduler event is performed from the time given in the Schedule section and
repeated at the set Interval. When for example a delay is expected in updating the
database, a Release delay can be enabled and a time delay selected from the
dropdown list.
Day of week(radio button)

The scheduled event Day of week triggers recording on the day selected in the
Schedule section and at the given time. When for example a delay is expected in
updating the database, a Release delay can be enabled and a time delay selected
from the dropdown list.
286

May 2011
Day of month (radio button)

This scheduled event is performed on the day of the month selected in the Schedule
section. A Last day setting enables the scheduled event to take place on the last
day of each month. When for example a delay is expected in updating the database,
a Release delay can be enabled and a time delay selected from the dropdown list.
Ext. Trigger - Channel (radio button)

A positive edge (value change from less then equal to zero to greater than zero) from
the channel selected under Trigger, triggers the Ext. Trigger - Channel event.
The Timerange field is used to determine the time range that is to be read out.
Enabling the Since last event means that only the new data from the last scheduler
event is recorded.

May 2011
287
Ext. Trigger - Manually (radio button)

Enables the event to be performed manually. The Timerange field is used to
determine the time range that is to be read out.
Enabling the Since last event means that only the new data from the last scheduler
event is recorded.
The Ext. Trigger - Manually event is triggered ,by opening the scheduler option's
context menu and selecting the trigger manually option.
Sate signalisation
The channel selected here will be set to zero at the start of the scheduler event. At the
end of the event, the channel is then set to 1. It is -1 in the event of an error. A selection
of channels is available via the magnifying glass symbol.
288

May 2011
2.3.8.2 Memory read-out
Read memory tab

The read memory tab determines the Me ssag e -device memory groups to be read-out
and where the output is to be saved.
When a connection exists to another DataService (server), its measurement databases can
also be read-out.
Source section
The Source section lists in the left pane (Available memory) all the available Me ssag e
devices and their memory groups.
The Selected memory pane lists the memory groups that this scheduler event is to read.

May 2011
289
To amend the list, select the required memory groups and click Add. Alternatively, drag and
drop the required memory groups using the mouse from Available memory to Selected
memory.
Target & Options section

The Target section determines where the read memory data is to be saved. Radio buttons
provide the options Database and Single files.
Database (radio button)
The Database setting means this scheduler event will always save the data to the same
(.HDD) file.
Single files (radio button)
The Single files setting means the data is always saved to a new (.HDS) file.
Database storage mode

When the Database button is enabled, the following options are available:
290

May 2011
Path (text field)

Enter the database's location.
The following placeholders can be used:
%appl The installation directory for Pro fiSig nal (usually C:\Programme\ProfiSignal).
%data The data folder in the Pro fiSig nal installation directory (usually C:\Programme
\ProfiSignal\Data).
Filename (without extension) (text field)
Enter the database's name. Clicking Select opens a file selection dialogue.

May 2011
291
Timeout until abort ... (dropdown list)

When the read-out of the device memory exceeds the value set here, the attempt is
aborted.
Link with real-time data (checkbox)
When enabled, temporary real-time data is automatically saved from all channels of the
selected memory groups. Measurement curves with real times can then be displayed in
trends. If the connection temporarily fails, the gap that then results in the real-time
data storage, displays only for as long as it takes for the next read cycle to be
performed.
Info:
This option can be used as an alternative to the permanent saving of real-time data
to a database. This also avoids the gaps in measurement data that result from
connection failures or PC servicing work (e.g. updates).
Synchronise device time with local time after read (checkbox)

The Me ssag e device's internal clock is synchronised with the PC clock following data
read-out.
Delete device memory after read memory (checkbox)

When enabled, the device's memory is deleted following a successful read-out and
transmission of its data.
Settings to optimize the update time for trend graphs
The sampling rate being used is given here. This setting optimizes the trend graph
update time with the selected sampling rate.
Database limits (section)
o The fields Storage duration, Maximum size and Free space correspond to the entries
users can make in Database configuration (Duration / Size). Follow the information
provided there.
Single files storage mode

When the Single files button is enabled, the following options are available:
292

May 2011
Path (text field)

Enter the single file location.
The following placeholders can be used:
%appl
\ProfiSignal
The installation directory for Pro fiSig nal (usually C:\Programme

).
%data
The data folder in the Pro fiSig nal installation directory (usually
C:\Programme\ProfiSignal\Data).
%temp
The Windows temporary folder.
%user
The My Documents folder.

May 2011
293
Filename (without extension) (text field)

Enter the name for the single file. It is essential that the filename is unique by using
placeholders.
The following placeholders are available:
%DATETIME provides the full date and time (e.g. 2006-11-05_09-04-08)
%DATE
provides the full date (e.g. 2006-11-05)
%time
provides the full time (e.g. 09-04-08)
%YYYY
provides a long year (e.g. 2006)
%YYYY
provides a short year (e.g. 06)
%MM
provides the numerical month (e.g.11)
%DD
provides the numerical day (e.g. 05)
%hh
provides the hour (e.g. 09)
%mm
provides the minutes (e.g. 04)
%ss
provides the seconds (e.g. 08)
%n
1000 ...)
provides a running number beginning at 1 (e.g. 1, 2 ,3, ... 9, 10, ...
%nn
each n provides a a leading zero (%nnn => 001)
Examples:
Measurement_file%nnn => Measurement_file001.HDS, Measurement_file002.HDS,
Measurement_file003.HDS .....
File_from_%DD.%MM.%YY_%hh:%mm:%ss
=> File_from_05.11.06_09:04:08.HDS ...
Timeout until abort ... (dropdown list)

When the read-out of the device memory exceeds the value set here, the attempt is
aborted.
Delete device memory after read memory (checkbox)
When enabled, the device's memory is deleted following a successful read-out and
transmission of its data.
Synchronise device time with local time after read (checkbox)
The Me ssag e device's internal clock is synchronised with the PC clock following data
read-out.
Convert into old Basicpackage format (.mes) (checkbox)
The file is created in MHouse MES format Instead of Pro fiSig nal HDS format.
Settings to optimize the update time for trend graphs
The sampling rate being used is given here. This setting optimizes the trend graph
update time with the selected sampling rate.
294

May 2011
2.3.8.3 DB backup
The Backup tab
This tab determines whether the database should be automatically backed up. When an
Automatic database backup is required, then a backup path must also be provided. This
can be input either manually or via the Select button.
The backup takes place at the end of the memory read-out.

May 2011
295
2.3.9
User management
The users settings are made in the User management tab in the DataSe rv ice
Co nfig urato r. The user management settings are valid for the DataSe rv ice Co nfig urato r
and Pro fiSig nal.
Users are to be set up for the following cases:

When password protection is required for Delphin Software.
When email or faxes are to be sent from the alarm manager.
The following sub-sections provide detailed information on user management:

Password protection settings
Add users
Add groups
Lock user
2.3.9.1 Password protection settings

Password protection provides Pro fiSig nal with an option to regulate system access and
makes operating the software dependent on user authorisation.
To set up password protection, open the DataSe rv ice Co nfig urato r use r manag e me nt
sy ste m as fo llo ws:
296

May 2011
User management tab
Context menu from DataService ID entry
...
Users now have the following options:

To save previously made settings. This opens a dialogue window.
To load previously made settings. This opens a dialogue window.
To set up password protection settings
Selecting Password protection settings opens the following dialogue to set up password
protection.

May 2011
297
Protection mode
Unprotected
Password protection is disabled and users do not need to login.
Login required
Password protection is enabled. Users are required to login to the DataSe rv ice
Co nfig urato r and Pro fiSig nal. Protection is effective for the DataSe rv ice and
Pro fiSig nal only on the local PC. When access to the DataSe rv ice is from another PC
(refer to the DataService connection), the PC must login to the DataSe rv ice . However,
users on the other PC do not automatically have to login to the DataSe rv ice and
Pro fiSig nal. The other PC continues to run autonomously.
Password server
Password protection is enabled. Users are required to login to the DataSe rv ice
Co nfig urato r and Pro fiSig nal. Protection is effective for other PCs connected to the
local DataSe rv ice (refer to the DataService connection). Other PCs may now only
connect to the local DataSe rv ice with the Client of password server protection mode.
298

May 2011
Client of password server

Password protection is enabled and the full user management system from another
DataSe rv ice is being used. Select a server from the list of possible servers. Only one
DataSe rv ice may be selected to which a permanent connection already exists (refer to
the DataService connection) and which is using either the Login required or Password
server protections modes.
Info:
A change in protection mode requires an administrator login. Changing to or from Client of
password server requires a 'Password server' or 'Login' at the local DataSe rv ice .
Following installation the user Administrator has the password SUPERVISOR. The
password requires changing at the first login.
A permanent connection means selecting Always from Connect in the DataService
connection settings dialogue.
When adding a connection to a DataSe rv ice with the Password server protection mode,
the connection will take on the Client protection mode. Select this connection as
password server in the Client of password server protection mode.
Password restrictions
Enter the minimum requirements for user passwords in the Password restrictions section.
The following input is available:
Minimum password length
Whether the password must contain upper-case characters
Whether the password must contain lower-case characters

May 2011
299
Whether the password must contain numerics

Whether the password must contain symbols
The password lifetime begins from when the password was last amended. When the
password lifetime expires, users must amend the password at the next login. When the
administrator amends a password, the password lifetime expires immediately and requires
the user to amend it at the next login.
An internal password history is maintained of passwords set up by users. The Ban last used
passwords option determines the extent to which previous passwords can be reused. The
following options are available:
disabled: When amending a password any previous passwords may be reused.
letztes: When amending a password the current password may not be reused.
2/3/5/10 letzten: When amending a password the previous 2, 3, 5 or 10 passwords may
not be reused.
alle vorherigen: When amending a password none of the previous passwords may be
reused.
The number of invalid logins can be set after which the account becomes locked.
The administrator account can not be locked. The administrator should therefore
have an especially secure password.
Info:
These restrictions do not apply to passwords issued by the administrator. Symbols
include any character not belonging to another category.
2.3.9.2 Add groups
Standard user groups

At the first DataService start, the following standard groups are set up and may not be
deleted:
Configurator ProfiSignal
Members of this group may access ProfiSignal projects.
Configurator DataService
Members of this group may configure devices and the DataService.
Viewer
Members of this group may observe.
User
Members of this group may initiate actions.
Evaluator
300

May 2011
Members of this group may evaluate stored measurement data.

Administrator
Members of this group may act as administrators.
User groups
Other user groups may be set up in addition to the standard groups above.
These additional user groups can be assigned to specific visualization objects in
Pro fiSig nal-applications or prompted by a Pro fiSig nal Klicks script.
Adding user groups
1. Select the User management tab in theDataSe rv ice Co nfig urato r.

2. Open the User groups context menu and select Add group.
3. This opens the Group settings window that enables determining of groups.
Name / Comment
Enter a meaningful name for the user group. Additional information can be entered as
comments.
Automatic logout
Select a time after which inactive Pro fiSig nal and DataSe rv ice Co nfig urato r users are
automatically logged out.

May 2011
301
Info:
If the user is a member of multiple user groups with an enabled automatic logout, the
logout takes place at the first expired time.
Following an automatic logout an attempt will be made to re-login the current Windows
user.
Clicking OK will display the new user group under the User management tab. Disabled user
groups are grayed-out. Left-clicking a user group opens a context menu to either open the
settings dialogue or delete a user group.
2.3.9.3 Add users
Standard user
At the first DataService start the following standard users are set up:
Administrator
This is the main administrator for Delphin software. This account may not be deleted
nor disabled.
DataService
When creating a connection to another DataSe rv ice (re fe r to the DataService
connection), the DataSe rv ice uses this user provided no other login information is given.
Disable this user for security reasons when the password protection is set to Login
required.
Configurator
The DataSe rv ice Co nfig urato r uses this user when creating a connection to a
DataSe rv ice .
ProfiSignal
Pro fiSig nal uses this user when creating a connection to a (local) DataSe rv ice .
Info:
Because password protection for the DataSe rv ice Co nfig urato r and Pro fiSig nal takes
place at user group level, disabling the Configurator and ProfiSignal is not recommended.
The administrator should therefore have an especially secure password.
Add user account
302

May 2011

2. Open the Users context menu and select Add user.

May 2011
303
3. This opens the User settings window that enables determining of users.
Personal information
Enter here the name of the user. This is the user's login name.
Additional information on the user can be included under comments.
EMail address / Fax number: This information is required by the alarm manager (refer
to Alerting) for informing the user.
Password / Windows user

Enter a new password for each user. The user must amend this password at the next login.
Enable Users can not change password to prevent password amendment by the user.
304

May 2011
Corresponding Windows user

This links the user to a Windows user account. If automatic login is enabled in Pro fiSig nal
or theDataSe rv ice Co nfig urato r, this link is used when starting the software to detect the
Windows user and then automatically perform a login.
Authentication
When a link has been established to a Windows user account, the user authentication can
then be delegated to Windows. Once Windows has authenticated the user, the user name
and password can then only be amended within Windows.
Info:
Following logout of the current Pro fiSig nal or DataSe rv ice Co nfig urato r user, there will
be an automatic re-login of the current Windows user. This is available when password
protection is enabled (refer to Password protection settings).
Assigning user groups

Each user can be assigned a user group.
Within Delphin Software the following rule applies: When the user is a member of at least
one user group that has rights to perform actions, the user also receives rights to perform
these actions.
Standard user groups

Administrator
Members may manage users, set up password protection and carry out other
administrative settings.
Configurator DataService
Members may configure the DataSe rv ice and devices within the DataSe rv ice
Co nfig urato r.
Configurator ProfiSignal
Members may configure and generate Pro fiSig nal applications.
Evaluator
Members may analyze measurement data and evaluate reports in Pro fiSig nal.
User
Members may operate elements and, for example, activate device outputs in
Pro fiSig nal.
Viewer
Members may, for example, turn on/off displays in Pro fiSig nal and, for example, display
current measurement data in DataSe rv ice Co nfig urato r.
Clicking OK will display the new user under the User management tab. Disabled users are
grayed-out. Left-clicking a user opens a context menu to either open the settings dialogue
or delete a user.

May 2011
305
2.3.9.4 Lock user
Users are locked from the system after repeated invalid login attempts
2. Open the context menu for the locked user and select Properties.
3. This opens User settings where the user can be unlocked by clicking the Unlock
button. Save , any amendments by clicking OK.
306

May 2011
2.4
ProfiSignal
Information on the ProfiSignal modular development system to enable users to acquire and
evaluate their measurement data.
The ProfiSignal section is structured as follows:

User interface
o Main menu
o Toolbar
o Management tree
o Log window
o Window management
o Time synchronization
Projects and applications

o Runtime and edit mode
o Visualization/VisuView
o Parameterview
o Report Designer
o Moduleview
o Application data
The Klicks programming language

o Variables
o Formula
o Question
o Assign
o Control
o Initiate
o Configuration
o Context sensitive search
Analysis
o Online analysis
o Open measurement data file for analysis
o Analysis window
o Export ASCII file
o Display database in trend

May 2011
307
o Reading device memory

o Global alarm lists
Report viewing
o Edit report
o Import report
o New layout
o Layout information
o Report preview
308

May 2011
2.4.1
User interface
After starting Pro fiSig nal the following window appears.
The Pro fiSig nal window has four areas.
The area marked 1 in the image is the main ProfiSignal window with the main menu (also
for global settings) and toolbar.
The area marked 2 displays the management tree.
The area marked 3 displays the log window.
The area marked 4 displays the Pro fiSig nal project that is currently open.

May 2011
309
2.4.1.1 Main menu

The Pro fiSig nal main menu has the following menu items:
File
Search
View
Protection
This option is available only when password protection has been set up in the
DataService Configurator.
Settings
Window
Help
2.4.1.1.1 File
Menu file
The File option has the following submenu items.
310

May 2011
Submenu
Function
New Project
Sets up a new project. Pre-settings for new projects can be made in

project options.
New Project
(without script)
Sets up a new project without a script and therefore without a

module chart view/ModuleView. A script can be added later via the
project's context menu. Pre-settings for new projects can be made
in project options.
Open
Displays a dialog to open an existing project.
Open Global
Alerting
Opens the global alerting lists.
New Online
Analyse
Sets up a new online analysis.
Open Online
Analyse
Displays a dialog to select an online analysis.
File factory
Displays the file factory dialog. The File factoryenables complete or

partial data files to be merged into a new or relative file.
Open MesFile
Displays a dialog to open an existing measurement data file.

May 2011
311
Readout device
storage
Refer to readout device storage
Show DataBase in
Trend
Refer to Show DataBase in Trend
Open Report
Refer to report viewing
Save
Saves the project currently open in the management tree.
Save as
Saves the project currently open in the management tree to the

name given in the dialog.
Save all
Saves all the projects shown in the management tree.
Close Project
Closes the project currently open in the management tree.
Close all
Closes all the projects shown in the management tree.
Recent project
files
Opens a submenu that displays the last four project files which have
been open.
Recent
Opens a submenu that displays the last four measurement data files
measurement data which have been open.
files
Recent report files Opens a submenu that displays the last four report files which have
been open.
End
Closes Pro fiSig nal, with a prompt when an open project is currently
unsaved.
2.4.1.1.2 Search
Search menu
The Search option has the following submenu item.
Submen Function
u
Search
Displays a dialog that enables users to search for a script.
312

May 2011
2.4.1.1.3 View
View menu
The View option has the following submenu items.
Subme
nu
Function
Project
bar
Determines whether the management tree is to be displayed (shortcut F12).
Logging Determines whether the log window is to be displayed (shortcut CNTRL+F12).

window
2.4.1.1.4 Protection
Protection menu
The Protection option is available only when password protection has been set up in the
DataSe rv ice Co nfig urato r. The option has the following submenu items.
Submenu
Function
Login
Displays a dialog for user login.
Logout
Logs the user out.
Settings
Displays a dialog to enable users to set up password protection.

May 2011
313
Change password
Displays a dialog to enable users to change a password.
Auto login
Option for automatic login of the current Windows user (refer

also to user login).
2.4.1.1.5 Settings
Settings
Language
The Settings option has the following submenu items.
Submenu
Function
Language
Opens a submenu to enable users to select the required

language. There is a choice between the default language set
under global settings, English and German.
Global Settings
Opens a dialog to enter global settings.
2.4.1.1.5.1 Global settings
Settings
Global Settings
To make personalized settings on how Pro fiSig nal looks and functions.
This opens the following dialogue
314

May 2011
The following tabs are available:
General
Timezone
Project options
VisuView
ParameterView
ModuleView
Script editor
ASCII export

May 2011
315
Settings
Global Settings
General
For entering general settings.
ConfigTree
316

May 2011
Text color
Opens a color palette to select the color of the management tree's text.
Background color
Opens a color palette to select the color of the management tree's background.
Show tree icons
Uses icons when enabled and text only when disabled.
General
Default language
Sets the default language.
Log level
The log-level for messages. Depending on the setting, additional information can be
included in the log file. In the event of problems occurring, log files are sent to Delphin
Technology AG who may then request a specific log level depending on the type of
problem.
Start options
When Pro fiSig nal starts the following can be opened:

A specific project
The most recently opened project
No project
A new project
An online analysis is opened when selected as an autostart, irrespective of the settings

here. This takes place prior to the opening of a project.
Mode

May 2011
317
Pro fiSig nal Klicks can be run in standard or advanced modes. Standard mode is the
default setting.
Standard mode is recommended for inexperienced users of Pro fiSig nal Klicks. Switching to
Advanced mode (CNTRL + ALT + M) is possible at any time.
Advanced functions are available in advanced mode.
E.g. visualization objects can be moved, enlarged, reduced or hidden using programmable
procedures. This makes context menus more powerful.
In standard mode, users have access to the individual elements within the management
tree. In advanced mode, users have access to the individual visualization objects in the
VisuView. An extra level is therefore displayed within the management tree.
Settings
Global Settings
Timezone
For timezone settings.
The timezone setting is used for the application when setting up a new project. A specific
timezone can be selected from within the application.
Settings
Global Settings
Project options
For entering project settings.
318

May 2011
Create an application with
ParameterView
Includes a parameter view when setting up a new project.
Report
Includes a report when setting up a new project.
Runtime project options
Runtime projects needs application with autostart

When enabled, a runtime project can then be generated only when at least one
application is automatically started when opening a project (refer to the project context
menu).

May 2011
319
Show ModuleView
When enabled, the module chart view/ModuleView is displayed during runtime.
Show script
Enables the script window to be opened during runtime.
Show report window
Enables the report window to be opened during runtime.
Settings
Global Settings
VisuView
For entering general settings for VisuViews.
Grid
For gridline settings on the VisuView's background. Gridlines are shown only in development
mode to facilitate the positioning of visualization objects. Gridlines are always hidden in
runtime mode.
Enabled
When enabled, gridlines are displayed.
Snap to grid
When enabled, visualization objects can be positioned using the mouse only onto
gridlines. Changing the size of a visualization object is also dependent on the gridlines.
320

May 2011
dX: and dY:

These numeric fields set the distances between the gridlines in the X and Y directions.
The input is in pixels.
Process View Colors
Background
Opens a color palette to select the color of the VisuView's background.
Grid
Opens a color palette to select gridline colors.
Component colors
Background
Opens a color palette to select the background color for the visualization objects.
Text
Opens a color palette to select the text color for the visualization objects.
Settings
Global Settings
ParameterView
For entering general settings for ParameterViews.

May 2011
321
Grid
For gridline settings on the ParameterView's background. Gridlines are shown only in
development mode to facilitate the positioning of visualization objects. Gridlines are always
hidden in runtime mode.
Enabled
Snap to grid
When enabled, visualization objects can be positioned using the mouse only onto
gridlines. Changing the size of a visualization object is also dependent on the gridlines.
dX: and dY:
Colors
Background
Opens a color palette to select the color of the parameter view's background.
322

May 2011
Grid
Opens a color palette to select gridline colors.
Component colors
Background
Opens a color palette to select the color of the visualization object's background.
Text
Opens a color palette to select the text color of the visualization objects.
Settings
Global Settings
ModuleView
For entering general settings for module chart views/ModuleViews.
Background

May 2011
323
Background color
Opens a color palette to select the ModuleView's background color.
Background
Line color
Opens a color palette to select the line color of a new ModuleView.
Loop color
Opens a color palette to select the loop color of a new ModuleView.
Line width
To set the width of the lines.
Grid
For gridline settings on the ParameterView's background. Gridlines are shown only in
development mode to facilitate the positioning of visualization objects. Gridlines are always
hidden in runtime mode.
Grid visible
Grid color
Opens a color palette to select the grid color of a new ModuleView.
Grid width
Sets the width of the gridlines.
dX: and dY:
Module settings
324

May 2011
Modules can have various forms (e.g. a start module is circular). A module's color, border
color and border width are set here.
Background color
Opens a color palette to select the background color of a new module.
Component color
Opens a color palette to select the component color of a new module.
Script error color
Opens a color palette to select the color that a module is displayed in when its script
contains an error (refer to the Klicks programming language).
Active module (runtime)
Opens a color palette to select the module color when in runtime mode.
Border color
Opens a color palette to select the border color of a component.
Border width
Sets the width of the components' borders.
Show module type
When enabled, the module type is displayed
Automatic font size
When enabled, adapts long names to the component size.
Module type
Module font
To select the font for the module type.
Settings
Global Settings
Script editor
For entering script editor settings.

May 2011
325
Script font
Font
To select the font type for scripts.
Size
To select the font size for scripts.
Colors
326

May 2011
Script text
Opens a color palette to select the color of script texts.
Channel type
Opens a color palette to select the color of channel types.
Info-Text
Opens a color palette to select the color of info texts.
Keyword
Opens a color palette to select the color of keywords.
Channel name
Opens a color palette to select the color of channel names.
Background
Opens a color palette to select the script's background color.
Variables
Opens a color palette to select the color of variable names.
Script presentation
Action visible
When enabled, the relevant actions (Question, Assign, etc.) are displayed (refer to the
Klicks programming language).
Show hierarchy
When enabled, the script's hierarchy is also displayed.

May 2011
327
Settings
Global Settings
ASCII export
For entering ASCII export settings.
2.4.1.1.6 Window
Window menu
The Window option has the following submenu items.
328

May 2011
Submenu
Function
Maximize Windows
Maximizes all the windows that are currently open in

Pro fiSig nal.
Minimize Windows
Minimizes all the windows that are currently open in

Pro fiSig nal.
Analyse Windows\Maximize
Trend Windows
Maximizes all the trend windows that are currently open in

Pro fiSig nal.
Analyse Windows\Cascade
Trend Windows
Displays in cascade format all currently opened trend

windows in Pro fiSig nal.

May 2011
329
Analyse Windows\Minimize
Trend Windows
Minimizes all the trend windows that are currently open in

Pro fiSig nal.
Analyse Windows \Align

Trend Windows
automatically
Automatically aligns all the trend windows that are

currently open in Pro fiSig nal. Up to four windows can be
aligned next to one another. Five or more windows will
then be cascaded.
Close all analyse windows
Closes all the analysis windows that are currently open in

Pro fiSig nal.
Report Windows\Maximize
Report Windows
Maximizes all the report windows that are currently open

in Pro fiSig nal.
Report Windows\Cascade
Report Windows
Displays in cascade format all currently opened report

windows in Pro fiSig nal.
Report Windows\Minimize
Report Windows
Minimizes all the report windows that are currently open in

Pro fiSig nal.
Report Windows\Align Report

Windows automatically
Automatically aligns all the report windows that are

currently open in Pro fiSig nal. Up to four windows can be
aligned next to one another. Five or more windows will
then be cascaded.
Report Windows\Close all

report Windows
Closes all the report windows that are currently open in

Pro fiSig nal.
Script Windows\Close all

script windows
Closes all the script windows that are currently open in

Pro fiSig nal.
Close script windows with

start runtime
Determines whether open script windows should be closed

when switching to runtime.
Shortcut keys are available to switch between Pro fiSig nal application windows, analysis
windows and report windows.
2.4.1.1.7 Help
Help menu
The Help option has the following submenu items.
The Help option contains the usual index and search functions for online help.
For those users who are unfamiliar with online help systems, there is also an option to
access the Window's online help overview.
330

May 2011
Subm
enu
Function
Conte Opens Pro fiSig nal help and displays the "Content" tab.
nts
Searc
h
Opens Pro fiSig nal help and displays the "Search" tab.
Edit
licenc
e
Opens a dialog that enables the display and editing of licence details (refer also
to licensing)
About
Displays a dialog containing information on Pro fiSig nal.
2.4.1.2 Toolbar
The Pro fiSig nal toolbar appears as follows:
Sets up a new project. Pre-settings for new projects can be made in project
options.
Displays a dialog to open an existing project.
Displays a dialog to open an existing measurement data file.
Refer to readout device storage
Refer to Show DataBase in Trend
Refer to Report Viewer.
Saves the project currently open in the management tree.
Saves all the projects shown in the management tree.
Opens the global alerting lists.

May 2011
331
Sets up a new online analysis.

Displays a dialog to select an online analysis.
Displays the file factor dialog.
Shows/hides the management tree.
Shows/hides the log window.
Refer toruntime and edit modes.
Refer to runtime and edit modes.
2.4.1.3 Management tree

The management tree appears as follows:
332

May 2011
It provides the following information:

1.
An open alarm table (refer also to global alert table)
2.
Currently opened measurement data files (refer also to measurement data files)
3.
Currently opened reports (refer also to the report viewer)
4.
Currently opened projects and applications
The following additional information is available for applications:

1. The application's VisuViews
2. The application's ParameterViews
3. The application's ModuleViews

May 2011
333
4. The application's Reports

5. The application's data
Right-clicking an item in the management tree opens a context menu (when available).
2.4.1.3.1 Project context menu
Management tree
Proj ect
Right-clicking a project in the management tree opens the following context menu.
Submenu
Function
Rename
Renames the project selected from the management tree.
Close Project
Closes the project selected from the management tree.
Save project
Saves the project selected from the management tree.
Copy project
Copies the project selected from the management tree and

saves it under a new name. The copied project is displayed
only after being opened.
Project options
Opens the Project options submenu.
Autostart applications
Opens the Autostart applications submenu.
Create runtime project
Creates a runtime project.
Create application
Adds a new application to the project selected from the

management tree.
334

May 2011
Paste application
Adds a previously copied application to the project selected

from the management tree.
Add script to project
To add a script to a script-less project.
The "project options" submenu
Submenu
Function
Activate protection
Enables/disables password protection for the project.

Password protecting the project protects the project's
visualization objects. It is then possible to determine which
users are permitted to operate the visualization object (refer
to the user rights tab for visualization objects).
Activate key protection
Enables/disables key protection. Key protection can be

enabled/disabled only when password protection is enabled.
Project-specific password protection differs to global password protection by managing

user access only to specific ProfiSignal projects.
Project-specific password protection is enabled/disabled via the context menu Project
options | Activate protection.
Protection is disabled by default when setting up a new project.
The project therefore remains unprotected unless the user changes the setting. The

May 2011
335
project can then be accessed by anyone during runtime.

Project-specific password protection requires the setting up of global password
protection (refer to the user management section and setting up password protection).
The "Autostart application" submenu
This lists the project's applications. The applications can then be selected that are to
automatically start when the project is run. A multiple selection is possible.
Submenu
Function
None
No applications start automatically when the project is run.
The "Create runtime project" submenu

A runtime project can be generated from an existing project. The project requires the
following:
A project application has been selected for autostart
If images (.bmp, .jpg ) have been used for visualization objects or views, these must be
in the application's "Images" folder
A Klicks project must be compilable
336

May 2011
The following data files are added to the runtime project:

The project file from which the runtime project is generated
All the images (*.jpg, *.bmp and *.gif) used by the project
The parameter files (*.pmt) associated with the project
The export files (*.csv) associated with the project
The trend configuration files (*.tcg) associated with the project
The generated files are given the ".drt" file extension. If a file with the same name already
exists, ProfiSignal prompts whether the file is to be overwritten. A progress dialog is
displayed. The newly generated file (with full path details) is displayed when the runtime
project has been successfully created.
2.4.1.3.2 Applications context menu
Management tree
Application
Right-clicking an application in the management tree opens the following context menu.
Submenu

May 2011
Function
337
Rename
Renames the application selected from the management

tree.
Copy
Saves the application from the management tree.
Delete
Saves the application selected from the management tree.
Create VisuView
Adds a new VisuView to the application selected from the

management tree.
Create report
Adds a new Report to the application selected from the

management tree.
Create ParameterView
Only available when the project has no parameter view (refer

also to project options). A parameter view is then added to
the application selected from the management tree.
Paste
This option is enabled after copying of a VisuView or Report.

A VisuView or Report is then added to the application
selected from the management tree.
Timezone
Sets the timezone. The application uses the timezone for its
timestamp information.
Channel choice
Opens a channel selection dialog for adding channels to the

application selected from the management tree.
Calculation channel
properties
To set calculation channel properties for the calculation

channels of the application selected from the management
tree.
Application info
Opens a dialog with information on the application currently

Print application info
Prints the information on the application currently selected

Application Events
Opens a dialog to enable the configuration of application

events.
Default application
To select a default application for projects with multiple

applications.
The "Application info" submenu

Opens the following dialog.
338

May 2011
The dialog contains information on the modules that are assigned to the application. The
following information is displayed for each module:
The module's info lines

The module's (Hardware) channels, calculation channels or adapter channels
The module's variables or application variables
The module's sub procedures, parallel modules or sequence modules (includes
information on whether the script uses these module types or whether they are located
only in disabled lines)
Click "Print info" for a hard copy print of the information.
"Application Events"
Opens the following dialog.

May 2011
339
Checking the User-login Event automatically checks Enabled. The event programming code
is performed only when 'Enabled' is checked. Checking one of the events generates a tab in
the module chart view named "Application Events" and containing both events.
Unchecking Enabled prevents running of the event module's programming code but leaves
the module intact and available.
Unchecking an 'Event' removes the event from the module chart view and therefore also
any programming code it contains.
Possible events are:
User login
The event is triggered when a user logs in. It is also triggered when a user was
already logged in.
User logout
The event is triggered when a user logs out.
Application timezone
340

May 2011
If the PC and Me ssag e -device are operating under differing timezones, it is possible to
switch between displaying Local time (PC) and Source time (Me ssag e -device). UTC time
is also available.
Further information is available in the timezone settings section.
2.4.1.3.3 VisuView context menu
Management tree
VisuView
Right-clicking a VisuView in the management tree opens the following context menu.

May 2011
341
Submenu
Function
Rename
Renames the VisuView selected from the management tree.
Copy
Copies the VisuView selected from the management tree.
Paste
Available only when a Visualization object has been copied. The

visualization object is then copied into the VisuView that has been
Default
VisuView
Sets as default the VisuView currently selected from the management

tree. The default VisuView is then displayed when opening the project.
Delete
VisuView
Delete the VisuView currently selected from the management tree.
Management tree context menu, visualization components
Right-clicking a visualisation object in the management tree opens the following context
menu.
Submenu
Function
Rename
Renames the visualization object selected application from

the management tree.
342

May 2011
Properties
Opens the properties dialog for the visualization object

currently selected from the management tree.
2.4.1.3.4 ParameterView context menu
Management tree
ParameterView
Right-clicking a ParameterView in the management tree opens the following context menu.
Submenu
Function
Rename
Renames the ParameterView selected from the management tree.
Copy
Copies the ParameterView currently selected from the management

tree.
ParameterView page
Right-clicking the page of a ParameterView in the management tree opens the following
context menu.
Submenu
Function
Rename
Renames the ParameterView page selected from the management tree.

May 2011
343
New page
Adds a new page to the ParameterView selected from the management

tree.
Delete page
Deletes ParameterView page selected from the management tree.
ParameterView component
Right-clicking the component of a ParameterView in the management tree opens the
following context menu.
Submenu
Function
Rename
Renames the parameter object selected from the management tree.
Properties
Opens a properties dialog for the component selected from the

management tree.
2.4.1.3.5 ModuleView context menu
Management tree
ModuleView
Right-clicking a ModuleView in the management tree opens the following context menu.
This opens a ModuleView properties dialog.
Management tree context menu for modules

Right-clicking a module in a ModuleView selected from the management tree displays a
context menu for sequence modules, end modules, event-end modules, function modules
and sub modules.
344

May 2011
Submenu
Function
Rename
Renames the module selected from the management tree.
Show script
Opens the ModuleView for the module selected from the

management tree.
Module information
Opens a dialog with information for the module currently selected

Print module
information
Prints the information for the module currently selected from the
management tree.
Start modules and security modules can not usually be renamed. Renaming an event
module is possible only in the properties dialog (event tab) of the visualization object to
which the event is assigned. These three module types therefore have the following
context menu:
"Module information"
Opens the following dialog:

May 2011
345
The dialog displays information about the module selected from the management tree:

The module's (Hardware) channels, calculation channels or adapter channels
The module's sub procedures, function modules or sequence modules (includes
information on whether the script uses these module types or whether they are located
only in disabled lines)
Click "Print info" for a hard copy print of the information.
346

May 2011
2.4.1.3.6 Report context menu
Management tree
Report
Right-clicking a Report in the management tree opens the following context menu.
Submenu
Function
Rename
Renames the Report selected from the management tree.
Copy
Copies the Report currently selected from the management

tree.
Delete
Copies the Report currently selected from the management

tree.
Report page
Right-clicking the page of a Report in the management tree opens the following context
menu.
Submenu
Function
Rename
Renames the Report page selected from the management tree.
Report component
Right-clicking the component of a Report in the management tree opens the following
context menu.

May 2011
347
Submenu
Function
Rename
Renames the report object selected from the management tree.
Properties
Opens a properties dialog for the report component selected from the
management tree.
2.4.1.3.7 Channels context menu
Management tree
Channels
Right-clicking channels in the application data of the management tree opens the following
context menu.
Submenu
Function
Edit
Opens the channel selection dialog.
All channels
When enabled, adds all available channels to the application.
2.4.1.3.8 Formulary context menu
Management tree
Formulary
Right-clicking Formulary in the application data of the management tree opens the
following context menu.
348

May 2011
Submenu
Function
Copy
Copies the Formulary selected from the management tree.
Paste
Available only when the clipboard contains a copied Formulary. The

Formulary is then copied into the application selected in the management
tree.
2.4.1.3.9 Calculation Channels context menu
Management tree
Calculation Channels
Right-clicking Calculation channels in the application data of the management tree opens
the following context menu.
Submenu
Function
Calculation channel
properties
Opens the management tree.
2.4.1.4 Log window
The log windows documents information on the program run. The information is also saved
to a log file named Pro fiSig nal.000.log located in the "Log" subfolder of the Pro fiSig nal
directory.
Runtime information can be recorded via a script within an application. This is recorded to a
separate log window for each application. The log window is named Project name application name (runtime Log) . Log-info input is saved to a log file. If your project is

May 2011
349
named Project_1 and the application Application_1, the log-info input is saved to a file
named Project_1_Application_1.log. This file is then located in the ProfiSignal's Log
directory.
2.4.1.5 Window management

The following keyboard shortcuts are available in ProfiSignal for managing windows:
CTRL+P
Project area
Analyse area
Report area
(measurement data files)
Switches to the next

project in multiple
project systems.
Switches to the active

window of the current
application.

application.
Switches to the next

application for projects window of the current
with multiple
application.
applications.

application.
This shortcut is
ineffective for single
project systems.
CTRL+N
This shortcut is
ineffective for projects
with single
applications.
CTRL+W
Scrolls the windows of

the current
application.
Scrolls the analysis

windows.
CTRL+T
Switches to analyse
Has no function.
area when
measurement data files
and/or online analyses
are open.
350
Scrolls the opened reports.
Switches to analyse area

when measurement data
files and/or online analyses
are open.

May 2011
CTRL+R
Switches to report
area when reports are
open.
Switches to report area

when reports are open.
Has no function.
2.4.1.6 Time synchronization
Synchronization is essential when acquiring, saving, evaluating and visualizing

measurement data from multiple devices.
Enable the NTP client on the Message device to ensure synchronized data streaming.
ProfiSignal checks for time synchronization between all devices registered with the
DataService. ProfiSignal reports a warning when device times deviate by more than +/10 seconds or when an error is detected in NTP-synchronization.
The above message window lists several devices that have synchronization problems.
The window gives information on device name, IP address, time deviation between device
and PC and NTP message.
When NTP-synchronization is disabled in a device, an NTP deactivated message appears in
addition to the time difference for a deviation greater than + /- 10 seconds.
Timezone setting
If the PC and Me ssag e -device are operating under differing timezones, it is possible to
switch between displaying Local time (PC) and Source time (Me ssag e -device). UTC time
is also available.

May 2011
351
Timezone settings affect only the display of the timestamp in Pro fiSig nal, and not the
actual timestamp.
Settings for the default timezone in Pro fiSig nal takes place under Settings/Global Settings.
The timezone tab has options for local (PC) time, data source (device) time and UTC
time.
The timezone to be used by an application can also be set via the application's context
menu (application context menu). The application uses the timezone for displaying the
timestamp.
352

May 2011
2.4.2
Projects and applications
2.4.2.1 Runtime and edit mode
Users can switch at any time between edit and runtime modes.
Edit mode is for creating applications. The applications are then performed in runtime
mode.
This function can be password protected.
The above image shows the edit mode. Click the symbol shown by the arrow to switch the
selected application to runtime mode

May 2011
353
The above image shows the runtime mode. Clicking the symbol ends the runtime mode and
switches the application to edit mode.
2.4.2.2 Visualisation
The VisuView and ParameterView are used to configure the user interface.
The VisuView is a window on which various types of display and operating elements can be
positioned. ProfiSignal refers to these elements as visualisation objects.
The image below is a VisuView with four visualisation objects.
A new VisuView appears as a blank window with a grid.

The grid is just an aid to position visualisation objects in edit mode. Users can set the
appearance of a grid. Grids are displayed only in edit mode to aid the positioning of
visualisation objects. The grid is always hidden in runtime mode. Further information on using
the grid is available in the properties section.
Clicking the VisuView activates the toolbar.
354

May 2011
This contains various types of visualisation objects (analog and digital displays, switches,
lamps, etc.). Each symbol (apart from the Mouse Cursor) corresponds to a specific type of
visualisation objects that can be used within an application.
To add a visualisation object to the VisuView, click its symbol and place it onto to VisuView.
To position and adjust the size visualisation objects, click with the mouse to create a border
to enable drag&drop functions.
Symbols with a black arrowhead in the right-lower corner have subtypes. Subtypes can be
displayed by right-clicking the arrowhead. For example, the tank visualisation object has a
choice of six different subtypes.
The range of available tabs and visualisation objects shown on the toolbar depends on the
licence the user has acquired. For example, the ODBC tab is available only when this licence
has been purchased.
The visualisation objects are grouped according to function under different tabs. The
following tabs are available in addition to the standard tab.

May 2011
355
2.4.2.2.1 VisuView properties
VisuView edit mode
VisuView Properties
Background
Inedit mode, right-click the VisuView's background and to access the VisuView Properties
item from the VisuView context menu. Settings can be made here on how the VisuView
looks and operates during runtime.
356

May 2011
Info:
Many of the VisuView settings can also be made as global settings. All subsequent
VisuViews then take on these settings. Pro fiSig nal global settings are accessed via the
settings tab. Settings for VisuViews are then available under the VisuView tab.
General tab
Name

May 2011
357
Name
To rename the VisuView.
Visibility
Only for Runtime

Indicates whether the VisuView can be operated once runtime mode starts. This setting is
currently disabled. It may be available in subsequent versions.
Visible
Indicates whether the VisuView can be displayed once runtime mode starts. When the
VisuView is hidden (i.e. not visible), it can be displayed by double-clicking its entry in the
management tree.
A VisuView can also be displayed via the change screen event, available for the button
visualisation object.
Display View
in full screen mode:

VisuView is displayed as a full screen. The menu bar is then hidden.
Press F11 to exit full screen mode.
as dialog:
As dialog, a VisuView does not display the minimize, maximize, and close buttons in the
upper right corner.
Size and position
358

May 2011
X: and Y:
Visualisation object's position in pixels, corresponding to the object's upper left corner.
Width: and Height: Border:
When enabled, the object is displayed with a 3D border.
Visualisation object size in pixels.
arrange center
Positions the VisuView centrally.
Update Interval
Value update interval

The interval in milliseconds at which values are updated.
Background tab
Grid
For setting the background gridlines. Grids are displayed only in edit mode to aid the
positioning of visualisation objects. The grid is always hidden in runtime mode.
Enabled
Displays gridlines.
Snap to grid
When this option is checked, visualisation objects can be positioned, using the mouse,
only onto the gridlines. Changing the visualisation object size is also dependent on the
gridlines.
dX: and dY:

May 2011
359
These numeric fields set the distances between the gridlines in the X and Y directions. The
input is in pixels.
Color section
Background
Opens a color palette to select the background color for the VisuView.
Grid
Opens a color palette to select the gridline color.
Background picture
Users have the option of selecting any image as a background image for the VisuView.
Portrayal settings are made under Background picture.
Enable
Uses Filename: as the VisuView's background.
Centered
Displays the image file in middle of the VisuView's background.
Scaled
Displays the image file to the VisuView's scale.
Keep original proportion
Displays the image file to the VisuView's scale without distorting the image.
Filename:
Opens a file selection dialog to select the image file. The file path can be entered directly
into the text field.
2.4.2.2.2 Multiple VisuViews

A ProfiSignal application can have any number of VisuViews.
Adding a VisuView to an application
360

May 2011
Management tree
Application
Create VisuView
A new project initially has just one application and one VisuView. To add another VisuView,
right click the application in the management tree to open the applications context menu.
Select Create VisuView.
Default VisuView
Management tree
Default VisuView
Each ProfiSignal application must have a default VisuView. The default VisuView becomes
active when switching to runtime mode. If the ProfiSignal contains multiple VisuViews, the
default VisuView is set via the VisuView context menu and Default VisuView item.
Switching VisuViews during runtime

Management tree
VisuView (double-click)
When switching from edit to runtime mode, the default VisuView is displayed.
Several options are available to then access the other VisuViews:
Via the management tree. Double-click the VisuView to be displayed.
Via the visualisation object button. The default VisuView must then contain a
visualisation object button. Right-click the button, select properties and then event.
Use change screen to select the VisuView that is to be accessed when clicking the
button.

May 2011
361
Deleting a VisuView
Management tree
VisuView
Delete VisuView
An application must be assigned at least one VisuView. A VisuView can be deleted when an
application contains more than one VisuView. From the management tree, open the context
menu of the VisuView to be deleted and select Delete VisuView. If the default VisuView is
to be deleted, you are prompted to select another VisuView as default.
2.4.2.2.3 VisuView context menu
Right-clicking a free space on VisuView page opens the following context menu:
(Right-clicking a visualisation object opens a visualisation object context menu)
362

May 2011
Submenu
Function
Paste
Available when a visualisation object has been copied to the

clipboard. Inserts the clipboard contents onto the VisuView.
VisuView Properties
Opens a dialog showing the VisuView's properties.
Search
Refer to Context sensitive searches
2.4.2.2.4 Visualisation object context menu
Right-clicking a visualisation object opens the following context menu.
Submenu
Function
Copy
Copies the selected visualisation object to the clipboard

May 2011
363
Delete
Deletes the selected visualisation object.
Grouping
Available when multiple visualisation objects have been selected

(refer to grouping).
Align or distribute
Available when multiple visualisation objects have been selected

(refer to Align or distribute).
Order
Refer to order.
Event modules
Available when the visualisation object has been assigned

events. The event modules are then listed in the submenu. Leftclicking event modules opens a window with the programming
instructions for the module (refer also to the Klicks programming
language).
Properties
Opens a dialog showing the visualisation object properties.
Configuration of
standard
Available only for diagrams. Enables standard settings to be

made in edit mode.
Channel choice
Available only for diagrams and recorders. Opens a channel

selection dialog.
Search
Available when the selected visualisation object is being used in

a script (refer to Klicks programming language and context
sensitive searching).
Grouping
Available when multiple visualisation objects are selected. Enables these objects to be
grouped together. The group has a specific name and enables related objects to be
grouped and visualized together. A group can be moved as a single block.
Submenu
Function
Group
Creates a group for the selected visualisation objects.
364

May 2011
Ungroup
Deletes a previously created grouping.
Align or distribute
Available when multiple visualisation objects are selected. Enables these objects to be
aligned and distributed on the grid.
Submenu
Function
Align Left
Left aligns the selected visualisation objects.
Align center
Centers the selected visualisation objects.
Align Right
Right aligns the selected visualisation objects.
Align Top
Top aligns the selected visualisation objects.
Align Middle
Centers the selected visualisation objects.
Align Bottom
Bottom aligns the selected visualisation objects.
Order
To place visualisation objects in the fore or background. Users can set whether a
visualisation object is to be superimposed on other visualisation objects.

May 2011
365
Submenu
Function
Bring to the front
Places the selected visualisation objects in the

foreground.
Send to the back
Places the selected visualisation objects in the

background.
2.4.2.2.5 Visualisation objects overview
The following section provides information on the visualisation objects.

General
Visualisation object properties
Displays for binary inputs

LED
Symbol:
Signal light
Symbol:
Displays for analog inputs
366

May 2011
Label
Symbol:
Digital meter
Symbol:
Analog meter
Symbol:
Lineal analog meter

Symbol:
Bar point
Symbol:
Tank
Symbol:
Operating elements for binary outputs

Toggle switch
Symbol:
Slider
Button
Symbol:
Check box
Symbol:
Picture
Symbol:

May 2011
367
Operating objects for analog outputs

Slider
Symbol:
Rotary knob
Symbol:
Text edit
Symbol:
Special visualisation objects

Channel drop down
Symbol:
Radio button
Symbol:
Table/ YX table
Symbol:
Timer
Symbol:
Date/Time
Symbol:
Stop watch
Symbol:
368

May 2011
Diagrams
Symbol:
ODBC
Symbol:
Alarm list
Symbol
Turntable
Symbol
Analysis objects
Trend
Symbol:
Recorder
2.4.2.2.5.1 Script instructions
Script instructions are available in addition to the visualisation objects. These are accessed
via Assign Value, Configuration Read and Configuration Write. Selecting one of these
functions displays the following lines of script:
Assign Value: Object = Object
Config Read: Object = Object
Config Write: Object = Object
Left-clicking Object opens the following menu.

May 2011
369
The menu lists the visualisation objects that have been inserted onto the VisuView. Each
visualisation object has a submenu. Each submenu also has its own submenu. The menu
items differ according to visualisation object. If a visualisation object has a specific menu
item, this item is explained in the section describing that visualisation object. Menu items
that are common to all visualisation objects are explained here.
This applies also to parameter objects (refer to the following image).
The number of script instructions can vary in the submenus. It is dependent on the mode
setting. Extended mode lists all the available script instructions. The default setting lists
only a small number of script instructions.
A different menu is displayed for each of the objects in the functions Assign Value,
Configuration Read and Configuration Write. Only the script functions that are displayed for
the objects of Assign Value differ significantly from the other Configuration functions.
Descriptions for the functions therefore differentiate only between these two.
370

May 2011
Assign Value
Right-clicking the right or left objects in Assign Value, gives the value for the visualisation/
parameter object. This concerns the state of the visualisation/parameter object (when the
binary value is on or off). A signal light, for example, has either an on or off state. It is this
state and the outcome that is displayed. The state of a signal light can be displayed via the
right object of the Assign Value function. The state can be set via the left object.
The Label submenu item has a value. This can be an integer or a string.
Configuration Read and Write

The script functions called by the two Configuration functions (Configuration Read,
Configuration Write) concern settings that the user can also set via the properties dialog (in
edit mode) for the visualisation/parameter object. To explain the script functions, the
corresponding properties dialog is also portrayed below each menu.
Event

May 2011
371
Refer to the event properties.
Channel settings
372

May 2011
Refer to the channel settings.
Name settings
The Description script function displays a hint by clicking the visualisation object in runtime
mode. This contains the text that the user has assigned to the script function.

May 2011
373
Config Write: Visualisation\Visu-View\LED.LED_1.Name

settings.Description = 'This is a LED'
Refer to the name and title settings.
Size and Position
Refer to the size and position settings.
Border
374

May 2011
Select a fixed value from 0 to 2 to change the inner and outer bevelling and the border style.
A value of 0 does not create bevelling or or border style.
Refer to the size and position and border settings.
Label font settings

May 2011
375
Visibility
Either 2 or 3 submenu items are displayed depending on the type of visualisation/parameter
object. Visualisation/parameter objects that can be changed in runtime via the mouse also
have the submenu item Focus. These visualisation/parameter objects include buttons, text
edits, check boxes, Radiobuttons, dropdown boxes, channel boxes, labels, tables and dates/
times.
376

May 2011
When the submenu item Focus is enabled, the visualisation/parameter object can be
accessed via the keyboard. For example, text edit can be directly performed (refer to
visibility in the general settings section).
Scale settings
Refer to the scale options in the settings section.

May 2011
377
2.4.2.2.5.2 Visualisation object settings

The settings window for visualisation/parameter objects enables channels to be assigned as
well as many settings on how the visualisation/parameter object is to be displayed.
The settings window is accessed by double-clicking the visualisation/parameter object in
edit mode or via the visualisation/parameter object's Properties context menu.
Properties/settings are available in several tabs. Many of the settings for visualisation/
parameter objects are similar so are explained here together.
When a setting is available only for specific visualisation/parameter objects, this is
mentioned in the explanation.
The following tabs are explained here:

General
Style
Protection
Event
Channel and tab order
References
Other tabs may be available depending on the visualisation/parameter object
378

May 2011
General tab
Name and title
Name:
Each visualisation/parameter object must have a unique name within each application.
Description:
Optional text.

May 2011
379
User Defined Text

Also displays the text entered in the text field.
Name as Title
Also displays the visualisation/parameter object's name
Channel name
Also displays the name of the assigned channel. A channel can be assigned to the
visualisation/parameter object via the tabs Channel or Channel and table order.
Font
Opens a font dialog for selecting the font type.
Title on the left
Displays the description to the left instead of above. Effective only when "User Defined
Text", "Name as Title" or "Channel Name" have been enabled.
Visibility
Enabled
The visualisation/parameter object can be operated with the mouse in runtime. When
unchecked, the visualisation/parameter object is only displayed.
Visible
Displays the visualisation/parameter object during runtime. When unchecked, the
visualisation/parameter object remains hidden.
Style tab
380

May 2011
Size and position area
X: and Y:
Visualisation/parameter object position in pixels, corresponding to the object's upper left
corner.
Width: and Height:
Width and height of the visualisation/parameter object in pixels.
% Width and % Height
Size of the display area of visualisation/parameter object. This is given as a percentage
of the background to the visualisation/parameter object.
Border

May 2011
381
Border:
When enabled, the visualisation/parameter object is displayed with a 3D border.
Outer Bevel: and Inner Bevel:
Select between a "None", "Lowered" and "Raised" border.
Border style:
Select between "None" and "Single".
Bevel Width: and Border Width:
To set the width of the border and bevelling as a value in pixels.
Scale settings
Free Scalable
Width and height of the visualisation/parameter object can be selected independently of
one another.
Proportional
When changing width, height will be changed proportionally. When changing height, width
will be changed proportionally.
Square
When changing width, height will be changed to the same value. When changing height,
width will be changed to the same value.
The protection tab determines:
which users have access in runtime (link runtime) to the visualisation/parameter objects.
which user groups (link user groups, single user item) have access to visualisation/
parameter objects in runtime.
The protection tab is available only when protection is activated for the project. Protection
is activated by right-clicking the project in the management tree. Select Project options
from the menu. Activate protection (link to activate protection in management tree) must
be checked.
382

May 2011
Protection
To set access rights for individual users or user groups to visualisation/parameter objects.
Uncheck the boxes to allow unprotected access.
The event tab

ProfiSignal Klicks enables any visualisation/parameter object to react in runtime mode to
events. An event can, for example, be triggered by a user either clicking a visualisation/

May 2011
383
parameter object or making an input. An event can also be triggered by a channel assigned
to the visualisation/parameter object. For example, the underrun of a channel value or a
change in measurement data can trigger an event.
The event tab sets the type of event to which the visualisation/parameter object
responds. The tab can contain different areas depending on the visualisation/parameter
object.
Events
The events listed here are not available to all visualisation/parameter objects. For example,
the Date/Time object can only respond to the following three events.
Enable events
For a visualisation/parameter object to react to either single or multiple events, each event
needs to be check boxed.
This generate an event in the module chart view that enables users to input programming
code. This is then performed when the event is triggered.
Check boxing an 'Event' also check boxes Enabled. The event programming code is
performed only when 'Enabled' is check boxed.
When Enabled is unchecked, the programming code in the module view's event does not run
but the event remains available.
Event descriptions
Initialisation
384

May 2011
An initialisation is performed prior to the application switching to runtime. The instructions

in the Initprocedure are performed first. For each visualisation object, the instructions are
then performed that are contained in the (if any) user defined initialisation module. Only
then is the application in runtime mode.
Left click
This is triggered when left-clicking a visualisation/parameter object.
Right click
This is triggered when right-clicking a visualisation/parameter object.
Double click
This is triggered when double-clicking a visualisation/parameter object.
Value change
Is triggered when a visualisation/parameter object's status changes. The status
corresponds to the visualisation/parameter object's displayed value or its On or Off
status.
A "value change" is triggered when the input (via text input, dropdown box, and channel
box) is confirmed by Enter or the visualization object loses its input focus.
Upper limit
Is triggered when the visualisation/parameter object's status exceeds the given value.
The status corresponds to the visualisation/parameter object's displayed value or its On
or Off status.
Lower limit
Is triggered when the visualisation/parameter object's status under runs the given value.
or Off status.
Change screen
(Available only for Button and Picture obj ects)
To place a different VisuView in runtime mode. Button and Picture objects can use this
event.
Change Screen on Mouse Click
The VisuView listed under Change Screen to is placed in the foreground when the user
clicks the visualisation object.
Change Screen to:
This determines which VisuView is to be placed in the foreground.
Table options (Configuration Read)

VisuView
[name of VisuView]

May 2011
[type of visualisation obj ect]
[name of visualisation obj ect]
Event
385
Reference tab
The Reference tab lists the script modules which call this visualisation object. Deleting this
visualisation object then leaves these modules incomplete. Switching to runtime mode is
therefore only possible after deleting the corresponding instructions in the modules.
386

May 2011
The example above shows that this visualisation/parameter object is being used in the
event modules Tatser_1, Tank_1, and Digital meter_1.
Channel & tab order tab

To select channels and assign them values. Input values can be displayed and amended.
The functions here are not available to all visualisation/parameter objects.
Channel
Channel:
To select the channel that the visualisation/parameter object is to display/set. Only
channels are available that can also be set and displayed by the visualisation/parameter
object, i.e. those that have been assigned by the user to the object via channel
selection.
Show channel:
The visualisation/parameter object displays the value from the assigned channel. Ensure
that the channel value is not constantly changing.
Set channel:
If users change the displayed value for the visualisation/parameter object, the changed
value is written to the assigned channel. For data exchange between two visualisation/
parameter objects, we recommend the assigning of a marker channel(link to marker

May 2011
387
channel).
When a channel has been selected as a visualisation/parameter object's data

source, the value for this object can no longer be set within a script.
Tab order
Available for Text edit and Button objects.

Tab order
Tab order enables users to jump to the value of the visualisation/parameter object at the
required sequence.
Value settings
The number format for visualisation/parameter objects that display numerics.

Value format (hidden when not available)
If this field remains unchanged then the number is displayed with all leading and trailing
decimal places.
To display the number in the required format, the following format placeholders are
available: zero, hash, point and comma. The separator for decimals and thousands
depends on the country settings.
0 Number placeholder
# Number placeholder (without leading and trailing zeroes)
, Thousands separator. When the text contains a point, the thousands separator is
displayed.
, Decimal separator: The first point in the text is used as the decimal separator.
An example using a channel value of 1073,558
388

May 2011
Data format
##0.0
##.###0.0
000000.0000
############,##
Display format
73.6
1,073.6
001073.5580
1073.56
Selection button section

- Use Channel Range
The visualisation/parameter object's minimum and maximum values are assigned to the
channels measurement range.
- Use User Defined Range
Value from: and Value to: fields.
Value (Text edit)
The following window is displayed when integer or fractional number has been selected
for a Text edit object.
Value format:
The same applies here as for the other visualisation/parameter objects.
Minimum and Maximum settings
Permits input only in the given range.
- Minimum
The minimum value that can be entered as Text edit.
- Maximum
The maximum value that can be entered as Text edit.
Unit
To display the unit in visualisation/parameter objects that have numeric channel data.

May 2011
389
Unit
- Use channel unit
The unit is displayed in addition to the channel's value.
- Use user defined unit
The value unit is displayed next to the channel data.
2.4.2.2.6 Digital meter

The digital meter graphically displays analog values.
Digital meter settings

Open the settings dialog by double-clicking the visualisation object in edit mode.
Alternatively use the visualisation object's context menu (Properties option). In addition to
the Digital Display tab are other tabs that are described in the visualisation object
properties section.
Digital Display tab

The Digital Display enables specific settings to be made for the visualisation object.
390

May 2011
Display
Font
Opens a font selection dialog to select the font type for the visualisation object.
Background Color:
Opens a color palette to select the background color of the visualisation object.
Use sector colors
Uses the sector colors defined under Borders as the background color.
Use sector colors for font
Uses the sector colors defined under Borders as the font color.
Autosize on
The meter automatically adapts to the new digital meter size.
Limits

May 2011
391
Only effect when the following check boxes are enabled: User sector colors or
Use sector colors for font.
The digital meter can use up to three different colors dependent on measurement data.
The colors can be used for font or background colors (depending on the settings under
Digital Display).
1.
2.
3.
Sector 1 for values lower than lower limit.

Sector 2 for values between lower limit and upper limit.
Sector 3 for values greater than the upper limit.
Lower limit:
To set the lower limit value.
Upper limit:
To set the higher limit value.
Color - Sector 1:
Opens a color dialog for selecting sector 1 color.
Color - Sector 2:
Color - Sector 3:
Border
Show value from the digital meter border. means that the digital meter itself is bordered.
392

May 2011
Events tab
Events section
Enable events
Event descriptions
Initialisation
Left click
Right click
Double click
Value change
status.
Upper limit

May 2011
393
or Off status.
Lower limit
or Off status.
Channel tab
Channel section
Channel:
those channels are available that were previously added to the application via the
channel selection window.
Show channel:
394

May 2011
Set channel:
If the displayed value is changed using the visualisation/parameter object, the changed
value is written to the assigned channel. To exchange data between two visualisation/
parameter objects, assign them a maker channel (marker channel link).

Value settings section
To display the format the value display in visualisation/parameter objects that have
numeric channel data.
decimal places.
displayed.
Example: An example using a channel value of 1073.558
Data format
##0.0
##.###0.0
000000.0000

May 2011
Display format
73.6
1,073.6
001073.5580
395
############,##
1073.56

- Use Channel Range
Unit section
Unit section
- Use channel unit
The channel's unit is displayed next to the data.
Script
The common menu options for the Assign value, Config Read and Write script functions, and
which are similar for the majority of the visualisation/parameter objects, have already been
explained. This section explains only those script functions that apply to this visualisation
object. Open the following menu via the Config Read and Write script functions.
Digital meter settings (Configuration Write)

VisuView
[name of VisuView]
Digital meter
[Name of digital meter] u Digital meter settings
396

May 2011
Analog output component settings (Configuration Write)

VisuView
[name of VisuView]
Digital meter
[Name of digital meter] u Analog output component
options

May 2011
397
2.4.2.2.7 Round analog meter

The analog meter graphically displays analog values.
Analog meter settings

the Analog Display tab are other tabs that are described in the visualisation object
properties section.
Analogue display tab

The Analog Display enables specific settings to be made for the visualisation object.
398

May 2011
Display
Scale Font
Opens a font selection dialog to select the font type for the scale text.
Unit Font
Opens a font selection dialog to select the font type for the unit text. The type of unit

May 2011
399
is set under Unit in the Channel tab.

Show unit
Displays the unit set under Unit in the Channel tab.
Show Sectors
Displays the sectors defined under Borders.
Show Peaks
Shows pointers for maximum and minimum values. These are reset by left-clicking the
visualisation object in runtime mode.
Color Arrow
Opens a color palette to select the pointer color.
Scale Settings
The minimum and maximum values for the scale are set under Value in the
Channel tab.
The meter's labeling and portrayal settings are made here.

The scale is split into steps (primary scale with values) and sub steps (secondary scale
without values).
Scale format (Text field)
To format values for the gradations of the main scale.
decimal places.
available: zero, hash, point and comma.
#Number placeholder (without leading and trailing zeroes)
. Decimal separator. The first point in the text is used as the decimal separator.
, Thousands separator. When the text contains a comma, the thousands separator is
displayed.
An example using a value of 1073.558

Data format
##0.0
Display format
73.6
400

May 2011
1,073.6
##,###0.0
000000.0000
001073.5580
############.##
1073.56
Steps
Number of sections within the main scale (at
least one for minimum and maximum values)
(3 steps in the example on the right).
Substeps
Number of sections for the subscales between two main scales
(at least one) (4 substeps in the example on the right).
Limits
Settings here only effect how the visualisation object appears when Show
Sectors is enabled in Analog Meter.
The scale can be spilt according to three different colors.

1. Sector 1 for values lower than lower limit.
2. Sector 2 for values between lower limit and upper limit.
3. Sector 3 for values greater than the upper limit.
Lower limit:
Upper limit:
Color - Sector 1:
Color - Sector 2:
Color - Sector 3:

May 2011
401
Events tab
Events section
Enable events
Event descriptions
Initialisation
Left click
Right click
Double click
Value change
status.
402

May 2011
Upper limit
or Off status.
Lower limit
or Off status.
Channel tab
Channel section
Channel:

May 2011
403
Show channel:
Set channel:

Value Settings

- Use Channel Range
Unit section
Unit section
- Use channel unit
404

May 2011

Script
Analog meter settings (Configuration Write)

VisuView
[name of VisuView]
Analog meter
[Name of analog meter] u Analog meter settings

VisuView
[name of VisuView]
Analog meter
[Name of analog meter] u Analog output component
settings

May 2011
405
2.4.2.2.8 Lineal analog meter

The lineal analog meter graphically displays analog values.
406

May 2011
Lineal analog meter settings

the Analog Display tab are other tabs that are described in the visualisation object
properties section.
Analog Display (Vertical/Horizontal) tab

The Analog Display (Vertical/Horizontal) tab enables specific settings to be made for the

May 2011
407
Display section
Scale Font
Unit Font
is set using the Channel tab and Unit section.
Show Value
The value displayed on the scale is also shown in a separate display.
Show unit
Displays the value with a unit. The type of unit is set using the Channel tab and Unit
section.
Show Sectors
Displays the sectors defined under Borders.
Show Peaks
Color Arrow:
Opens a color palette to select the pointer color.
Scale Settings
The minimum and maximum values for the scale are set under Value in
the Channel tab.
408

May 2011

without values).
decimal places.
displayed.

Data format
##0.0
##,###0.0
000000.0000
############.##
Display format
73.6
1,073.6
001073.5580
1073.56
Steps
Number of sections within the main scale (at
least one for minimum and maximum values)
Substeps
Limits

May 2011
409
Settings here only effect how the visualisation object appears when
Show Sectors is enabled in Analog Meter.
1.
2.
3.

Lower limit:
Upper limit:
Color - Sector 1:
Color - Sector 2:
Color - Sector 3:
Events tab
Events section
Enable events
410

May 2011
Event descriptions
Initialisation
Left click
Right click
Double click
Value change
status.
Upper limit
or Off status.
Lower limit
or Off status.
Channel tab

May 2011
411
The analog meter tab concerns the analog display; Format in the channel tab concerns
how the value is displayed.
Channel section
Channel:
Show channel:
Set channel:
412

May 2011

decimal places.
displayed.
Data format
##0.0
##.###0.0
000000.0000
############,##
Display format
73.6
1,073.6
001073.5580
1073.56

- Use Channel Range

May 2011
413

Unit section
Unit section
- Use channel unit
Script
Vertical/ Horizontal meter settings (Configuration Write)

VisuView
[name of VisuView]
Analog meter
[Name of analog meter] u Vertical/Horizontal Analog
meter settings
414

May 2011

VisuView
[name of VisuView]
Analog meter
[Name of analog meter] u Analog output component
settings

May 2011
415
2.4.2.2.9 Bar
The Bar graphically displays analog values.
Bar (Vertical/Horizontal) settings

the Bar (Vertical/Horizontal) tab are other tabs that are described in the visualisation
object properties section.
416

May 2011
Bar (Vertical/Horizontal) settings

The Bar (Vertical/Horizontal) tab enables specific settings to be made for the visualisation
object.
Display
Font
Opens a font selection dialog on how the value is to be displayed.
Show Value
Displays the value in the upper part of the visualisation object.
Show unit

May 2011
417
section.
Use sector colors
Displays bar colors according to the sector colors defined under Borders.
Show Peaks
Color Bar
Opens a color palette to select the bar color. Only effective when Use sector colors is
disabled.
Background Color
Opens a color palette to select the bar's background color.
Type
To set how the display is to appear.
Limits
Use Sector Color is enabled in Display.
1.
2.
3.

Lower limit:
Upper limit:
Color - Sector 1:
418

May 2011

Color - Sector 2:
Color - Sector 3:
Events tab
Events section
Enable events
Event descriptions
Initialisation
Left click
Right click
Double click
Value change

May 2011
419

status.
Upper limit
or Off status.
Lower limit
or Off status.
Channel tab
Channel section
Channel:
420

May 2011
Show channel:
Set channel:

decimal places.
displayed.
Data format

May 2011
Display format
421
73.6
##0.0
##.###0.0
000000.0000
############,##
1,073.6
001073.5580
1073.56

- Use Channel Range
Unit section
Unit section
- Use channel unit
Script
Vertical/ Horizontal Bar settings (Configuration Write)

VisuView
[name of VisuView]
Bar meter
[Name of Bar] u Vertical/Horizontal Bar settings
422

May 2011

May 2011
423
2.4.2.2.10 Tank
The Tank graphically displays analog values.
Tank settings
the Tank tab are other tabs that are described in the visualisation object properties
section.
Tank tab
The Tank tab enables settings to be made for the Tank objects.
424

May 2011
Display
Font
Opens a font selection dialog to select the font type, size and color of the
measurement display.
Show Value
Displays the value on the visualisation object.
Show unit
Displays the unit set under Unit in the Channel tab.
Use Sector Colors
Displays fill-levels using colors set under Borders.
When not activated fill-level colors are used that are set under Color Tank.
Color Tank
Opens a color palette to select the fill-level color. Has no effect when Use Sector
Colors enabled.

May 2011
425
Background Color
Opens a color palette to select the background/empty tank color.
Type
This area is used to set the tank shape.
Limits
Use Sector Color is enabled in Display.
1.
2.
3.

Lower limit:
Upper limit:
Color - Sector 1:
426

May 2011
Color - Sector 2:
Color - Sector 3:
Events tab
Events section
Enable events
Event descriptions
Initialisation
Left click
Right click
Double click
Value change

May 2011
427

status.
Upper limit
or Off status.
Lower limit
or Off status.
Channel tab
Channel section
Channel:
428

May 2011

Show channel:
Set channel:

decimal places.
displayed.
Data format
##0.0

May 2011
Display format
73.6
429
##.###0.0
000000.0000
############,##
1,073.6
001073.5580
1073.56

- Use Channel Range
Unit section
Unit section
- Use channel unit
Script
Tank settings (Configuration Write)

VisuView
[name of VisuView]
Tank
[Name of Tank] u Tank settings
430

May 2011

May 2011
431
2.4.2.2.11 LED
The LED graphically displays binary values.
LED settings
the LED tab are other tabs that are described in the visualisation object properties
section.
LED tab
The LED tab enables settings to be made for the LED objects.
432

May 2011
Appearance
The following types of LED are available.
Border Width sets the object's thickness.
Colors
Color - Off
Opens a color palette to select the color for the Off-status.
Color - On
Opens a color palette to select the color for the On-status.
Events tab
Events section

May 2011
433
Enable events
Event descriptions
Initialisation
Left click
Right click
Double click
Value change
status.
Upper limit
or Off status.
Lower limit
434

May 2011
or Off status.
Channel tab
Channel section
Channel:
Show channel:
Set channel:

May 2011
435

Script
LED settings (Config Write)

VisuView
[name of VisuView]
Tank
[Name of Tank] u Tank settings
LED Appearance (Config Write)

Selecting the left side of the Config Write opens a menu for selecting the type of LED.
Open the menu by left-clicking.
436

May 2011
2.4.2.2.12 Signal light

The Signal light graphically displays binary values.
Signal light settings

the Signal Light tab are other tabs that are described in the visualisation object properties
section.
Signal light tab

The Signal light tab enables settings to be made for the signal light objects.

May 2011
437
Display
Show Cross if Disabled

Displays a cross on the visualisation object in the Off-status.
Border Width:
Width of border in pixels.
Cross Width:
Width of cross in pixels.
Colors
Color Off
Opens a color palette
Color On
Color Outline:
Color Cross
to select the color for the Off-status.

to select the color for the On-status.
to select the color for the object's border.
to select the color for the object's cross in the Off-status.
438

May 2011
Events tab
Events section
Enable events
Event descriptions
Initialisation
Left click
Right click
Double click
Value change
status.
Upper limit

May 2011
439
or Off status.
Lower limit
or Off status.
Channel tab
Channel section
Channel:
Show channel:
Set channel:

Script
440

May 2011
Signal Light settings (Configuration Write)

VisuView
[name of VisuView]
Signal Light
[Name of signal light] u Signal light settings
2.4.2.2.13 Rotary knob

The Rotary knob graphically displays analog values.

May 2011
441
Rotary knob settings

the Dial tab are other tabs that are described in the visualisation object properties
section.
Dial tab
The Dial tab enables settings to be made for the dial/rotary knob objects.
Display
442

May 2011
Scale Font
Unit Font
Opens a font selection dialog to select the font type for the unit text. The type of unit is
set using the Channel tab and Unit section.
Show Value
Show unit
section.
Show Scale
Displays the scale.
Show Scale Text
Displays the scale text.
Scale Settings
the Channel tab.

without values).

May 2011
443

decimal places.
displayed.

Data format
##0.0
##,###0.0
000000.0000
############.##
Display format
73.6
1,073.6
001073.5580
1073.56
Steps
Number of sections within the main scale (at least one for
minimum and maximum values)
Substeps
Color section
Color - Focus
Opens a color selection dialog to select the pointer color on a rotary control that has a
focus (marked element) status.
The focus status for a rotary control is enabled by mouse clicking or repeated pressing
of the tab key. Users can then operate the visualisation object via the keyboard. This
takes place using the cursor Pos1, End, Page Up and Page Down keys.
Color - Non-focus
Opens a color selection dialog to select the pointer color on a rotary control that does
444

May 2011
not have a focus (marked element) status.
Events tab
Events section
Enable events
Event descriptions
Initialisation
Left click
Right click
Double click
Value change
status.

May 2011
445
Upper limit
or Off status.
Lower limit
or Off status.
Channel tab
Channel section
Channel:
446

May 2011
Show channel:
Set channel:

decimal places.
displayed.
Data format
##0.0
##.###0.0

May 2011
Display format
73.6
1,073.6
447
000000.0000
############,##
001073.5580
1073.56

- Use Channel Range
Unit section
Unit section
- Use channel unit
Script
Rotary knob settings (Configuration Write)

VisuView
[name of VisuView]
Rotary knob
448
[Name of rotary knob] u Rotary knob settings

May 2011
Analog input component settings (Configuration Write)

VisuView
[name of VisuView]

May 2011
Rotary knob
[Name of rotary knob] u Analog input settings
449
450

May 2011
2.4.2.2.14 Slider
The Slider graphically displays analog values.
Slider settings
Alternatively use the visualisation object's context menu (Properties option).In addition to
the Slider (Vertical/Horizontal) tab are other tabs that are described in the visualisation
Slider (Vertical/Horizontal) settings

The Slider (Vertical/Horizontal) tab enables specific settings to be made for the

May 2011
451
Display
Scale Font
Unit Font
is set using the Channel tab and Unit section.
Show Value
Show unit
section.
Show Scale Text
Displays the scale text.
Color - Trench
Opens a color palette to select the bar color.
Scale Settings
the Channel tab.

452

May 2011
without values).

decimal places.
displayed.

Data format
##0.0
##,###0.0
000000.0000
############.##
Display format
73.6
1,073.6
001073.5580
1073.56
Steps
Number of sections within the main scale (at least one
for minimum and maximum values)
Substeps
Color section
Color - Focus
Opens a color selection dialog to select the pointer color on a rotary control that has a
focus (marked element) status.
The focus status for a rotary control is enabled by mouse clicking or repeated pressing
of the tab key. Users can then operate the visualisation object via the keyboard. This
takes place using the cursor Pos1, End, Page Up and Page Down keys.
Color - Non-focus
Opens a color selection dialog to select the pointer color on a rotary control that does
not have a focus (marked element) status.

May 2011
453
Events tab
Events section
Enable events
Event descriptions
Initialisation
Left click
Right click
Double click
Value change
status.
Upper limit
454

May 2011

or Off status.
Lower limit
or Off status.
Channel tab
Channel section
Channel:
Show channel:

May 2011
455
Set channel:

decimal places.
displayed.
Data format
##0.0
##.###0.0
000000.0000
############,##
Display format
73.6
1,073.6
001073.5580
1073.56
456

May 2011

- Use Channel Range
Unit section
Unit section
- Use channel unit
Script
Vertical/ Horizontal slider settings (Configuration Write)

VisuView
[name of VisuView]

May 2011
Slider
[Name of slider] u Vertical/Horizontal slider settings
457
Analog input component settings (Configuration Write)

VisuView
[name of VisuView]
slider
[Name of slider] u Analog input settings
458

May 2011
2.4.2.2.15 Toggle switch

The toggle switch graphically displays binary values.
Toggle switch settings

the toggle switch tab are other tabs that are described in the visualisation object
properties section.
Toggle switch tab

The Toggle switch tab enables settings to be made for the dial/rotary knob objects.

May 2011
459
Type
To set the switch's appearance and On position (right or left).
Colors
Color Off
Color On
Events tab
Events section
460

May 2011
Enable events
Event descriptions
Initialisation
Left click
Right click
Double click
Value change
status.
Upper limit
or Off status.
Lower limit

May 2011
461
or Off status.
Channel tab
Channel section
Channel:
Show channel:
Set channel:

Script
462

May 2011
Switch settings (Configuration Write)

VisuView
[name of VisuView]
Toggle switch
[Name of Toggle switch] u Switch settings
2.4.2.2.16 Slide switch

The slide switch graphically displays binary values.
Slide switch settings

the slide switch tab are other tabs that are described in the visualisation object properties
section.
Slide switch tab

The slide switch tab enables settings to be made for the slide switch objects.

May 2011
463
Font
Font
Opens a font selection dialog to select the font type for the object text.
Off Text (Text field)
The text to be displayed in the Off-status. The status normally shown here is not the
current status but rather the status that occurs when clicking the switch.
On Text (Text field)
The text to be displayed in the On-status. The status normally shown here is not the
current status but rather the status that occurs when clicking the switch.
Show Text (Text field)
Displays the text defined under Off/On Text.
Type section
464

May 2011
To set the switch's appearance and On position (right or left).
Color section
Color Off
Color On
Events tab
Events section
Enable events

May 2011
465
Event descriptions
Initialisation
Left click
Right click
Double click
Value change
status.
Upper limit
or Off status.
Lower limit
or Off status.
Channel tab
Channel section
Channel:
466

May 2011

Show channel:
Set channel:

Script
Slide switch settings (Configuration Write)

VisuView
[name of VisuView]

May 2011
Slide switch
[name of slide switch] u Switch settings
467
2.4.2.2.17 Button
ProfiSignal has different types of button. In addition to the general button are other
buttons with special functions.
Report button
Project button
Application button
Exit button
Login button
These special buttons enable users to implement, via Pro fiSig nal Basic, specific functions
for their applications. For Klicks users, buttons can be a simpler and quicker to use than
script commands.
2.4.2.2.17.1 Button
The Button visualisation object can be used to set binary values and to display VisuViews.
Button settings
the button tab are other tabs that are described in the visualisation object properties
section.
468

May 2011
Button tab
The button tab enables settings to be made for the button objects.
Label section
Label (text field)

The text to be displayed on the visualisation object.
Font section
Font
Opens a font dialog for selecting the label's font type.
Color settings section

May 2011
469
To select the visualization object color.

Default color
The color of the visualisation object when ready for use.
Disabled color
The color of the visualisation object when not ready for use.
Pressed color
The color of the visualisation object when being used.
Test Button Enabled and Test (check box and button)
To view the color settings.
When check-boxed, the Test button will appear in the default color settings. Pressing
the Test button displays the pressed color settings.
When unchecked, the Test button will appear in the disabled color settings.
Events tab
Events section
Enable events
470

May 2011
Event descriptions
Initialisation
Left click
The event is triggered when left-clicking the visualisation/parameter object.
Right click
The event is triggered when right-clicking the visualisation/parameter object.
Change screen section
A different VisuView can be placed in the foreground in runtime mode.

When enabled, the selected VisuView under Change Screen to: is placed in the
foreground.
Change Screen to:

May 2011
471
Channel section
Channel:
Show channel:
Set channel:

Tab order section
The tab order function is not available for all visualisation/parameter objects.
472

May 2011
Tab order
The tab keys can be used to move to those visualisation/parameter objects that require
input. This setting is used to define the order in which this takes place.
Script
Button settings (Configuration Write)

VisuView
[name of VisuView]
Button
[name of button] u Button settings
Change view enabled (Configuration Write)

VisuView
[name of VisuView]

May 2011
Button
[name of button] u Change view enabled
473
2.4.2.2.17.2 Report Button

The Report Button provides a simple method to produce a Report.
Report Button settings

the report button tab are other tabs that are described in the visualisation object
properties section.
The Button tab
This section describes the settings for the Report button.
474

May 2011
Label section
Label (text field)

Font section

May 2011
475
Font

Default color
Disabled color
Pressed color
Settings -Report button
Generated Report by Activity

Click the dropdown box to select the report to be generated.
Expand existing report
Expands the current report by one page.
476

May 2011
When disabled, the current report is deleted and a new report generated.
Report File Name
Name of the report file including path.
After Creating the Report
Three options are available: Do Nothing; Print the Report; or Open the Report.
Script
Button settings
VisuView
[name of VisuView]

May 2011
Report button
[name of report button] u Button settings
477
2.4.2.2.17.3 Project button

The Project button opens a project during runtime.
Project button settings

the project button tab are other tabs that are described in the visualisation object
properties section.
Button tab
This section describes the settings for the Project button.
Label section
478

May 2011
Label (text field)

Font section
Font

Default color
Disabled color
Pressed color
Proj ect file
Project file

May 2011
479
Name of the project file (with path) to be opened when clicking the Project button.
Script
Button settings
VisuView
[name of VisuView]
Proj ect button
480
[name of proj ect button] u Button settings

May 2011
2.4.2.2.17.4 Application button

The Application button enables runtime activation for a project application.
Application button settings

the application button tab are other tabs that are described in the visualisation object
properties section.
Button tab
This section describes the settings for the application button.
Label section

May 2011
481
Label (text field)

Font section
Font

Default color
Disabled color
Pressed color
Choose Application
Choose application
To select a project application. The selected application switches to run time on
clicking the button.
482

May 2011
Script
Button settings
VisuView
[name of VisuView]
Application button
[name of application button] u Button settings
Application ID
ProfiSignal has the following initiate function to obtain an application's ID.
Script u Initiate u Application u Get application ID

May 2011
483
Right clicking the "Application name" opens a menu showing all the applications for the
project. The application ID is written to the output variable.
2.4.2.2.17.5 Exit button

The Exit button enables users to switch from runtime to edit mode. It can also be used to
end ProfiSignal.
the exit button tab are other tabs that are described in the visualisation object properties
section.
Exit button settings
Button tab
This section describes the settings for the Exit button.
484

May 2011
Label section
Label (text field)

Font section
Font

May 2011
485

Default color
Disabled color
Pressed color
Choose Application
Choose application
Select the application within this project. The application switches from runtime mode
to edit mode. Close ProfiSignal ends the ProfiSignal session.
Script
Button settings
VisuView
[name of VisuView]
Exit button
[name of exit button] u Button settings
486

May 2011
Stop ID
ProfiSignal has the following initiate function to obtain an application's ID.
Script u Initiate u Application u Get application ID
Right clicking the "Application name" opens a menu showing all the applications for the
project. The application ID is written to the output variable.
2.4.2.2.17.6 Login button

The Login button opens the user login dialog.

May 2011
487
To enable the menu requires the following conditions in runtime mode:

Activate protection in the management tree. Protection is activated by right-clicking the
project in the management tree. Click Project options and enable Activate protection.
Password protection was also e enabled in the DataService. Click User management. Right
click LocalDataService and select Password protection settings. From the dialog select
Login required.
Login button settings

section.
Button tab
This section describes the settings for the login button.
488

May 2011
Label section
Label (text field)

Font section
Font

May 2011
489

Default color
Disabled color
Pressed color
Script
Button settings
VisuView
[name of VisuView]
Login button
490
[name of login button] u Button settings

May 2011
2.4.2.2.18 Text edit

Text edit is used to set analog values and to input text.
Text edit settings

section.
Edit tab
The edit tab enables settings to be made for the edit objects.

May 2011
491
Display section
Background color
Opens a colour palette to select the background colour for the visualisation/parameter
object.
Font
Opens a font selection dialog to select the font type, size and color for the
visualisation/parameter object.
Key Check
One Line Text

Only single line text may be input.
Multiline Text
492

May 2011
Multiple lines of text may be input.

Integer
Only numerics may be input.
Fractional Number
Only numerics and decimal points may be input.
Max Chars per Line: (check box and numeric field)
The maximum number of characters that may be input. In the above image, this would
be 10 characters per line. The checkbox is available only when One Line Text or
Multiline Text has been selected.
Max Lines: (check box and numeric field)
The maximum number of lines that may be input. In the above image, this would be 2
lines. The checkbox is available only when Multiline Text has been selected.
If Fractional Number has been selected, value settings will be available in the
Channel and Tab order tab. Settings can then be made for fractional number: its
format, maximum and minimum settings.
Scroll bars
Horizontal
The text edit area is displayed with a horizontal scroll bar. Available only for multiple
lines of text.
Vertical
The text edit area is displayed with a vertical scroll bar. Available only for multiple lines
of text.
Events tab
Events section

May 2011
493
Enable events
Event descriptions
Initialisation
Left click
Right click
Double click
Value change
status.
Upper limit
or Off status.
Lower limit
494

May 2011
or Off status.
Channel section
Channel:
Show channel:
Set channel:

May 2011
495

Tab order section
Tab order
Value settings
Value settings are displayed only when a fractional number has been selected in
the Edit tab (Key Check).
Value format (Text field)

To format the display of a visualization object.
decimal places.
496

May 2011
displayed.
An example using a value of 1073,558

Data format
##0.0
##,###0.0
000000.0000
############.##
Display format
73.6
1,073.6
001073.5580
1073.56
Minimum and Maximum

Enabling Establish minimum and maximum requires text edit input to be within the given
range. The input value is replaced with the minimum value when below the minimum. The
input value is replaced with the maximum value when above the maximum.
Minimum and maximum values are selected here. If a minimum is selected that is greater
than the maximum, the values will exchanged.
Script
Text edit settings (Configuration Write)

VisuView
[name of VisuView]

May 2011
Text edit
[name of text edit] u Edit settings
497
2.4.2.2.19 Check box

The Check box sets binary values.
Check box settings

the check box tab are other tabs that are described in the visualisation object properties
section.
Check Box tab

The check box tab enables setting of the check box object.
498

May 2011
Display section
Background color
object.
Font
Description
Description (Text field)

The text that is displayed next to the check box.
Events tab
Events section

May 2011
499
Enable events
Event descriptions
Initialisation
Left click
Right click
Double click
Value change
status.
Upper limit
or Off status.
Lower limit
500

May 2011
or Off status.
Channel section
Channel:
Show channel:
Set channel:

Displays/marks the entry that has the channel's value. If neither entry has a value, nothing
is displayed/marked.
Tab order section

May 2011
501
Tab order
Script
Check box settings (Configuration Write)

VisuView
[name of VisuView]
Check box
[name of check box] u Checkbox settings
2.4.2.2.20 Radiobutton
The radio button sets binary and analog values. A range of option fields are available. Not
all of these option fields can be enabled at the same time. Clicking a new option fields
disables previous clicked option fields.
502

May 2011
Radio button settings

the radio button tab are other tabs that are described in the visualisation object
properties section.
Radio button tab

The radio button tab enables settings to be made for the radio button objects.

May 2011
503
Display section
Background color
object.
Font
Orientation
Vertical
The option fields for the radio button are positioned vertically.
Horizontal
The option fields are positioned horizontally.
2 Columns
The option fields are positioned as two columns.
Names and Values
504

May 2011
To manage the option fields to be displayed as radio buttons.

Each entry corresponds to one option field.
The upper table is for managing the list.
Each table entry can be selected in runtime mode.
A table entry is made up of an index, a name and a value.
The index indicates the sequence in which the radio button option fields are to be
displayed.
Name is the text to be displayed alongside the radio button option field.
The value is the value to be used when the option field is selected during runtime
mode.
When a channel is assigned to the visualisation object, the channel will then take the
value of the selected option field. This value can also be set in Pro fiSig nal Klicks via
a script.
There are three text fields below a table. Following the selection of an entry, the index,
name and corresponding value is displayed. A selected entry can be deleted or replaced
from the list using the appropriate buttons. To add an entry, enter a name, that has not
yet been used, and a value. The new entry will be added to the list by then clicking the
add button. The order of displayed list can be amended using the up-and-down button.
Default index
This section enables setting of the default option fields. "No selection" means that no
option fields are pre-selected.
Events tab
Events section

May 2011
505
Enable events
Event descriptions
Initialisation
Left click
Right click
Double click
Value change
status.
Upper limit
or Off status.
506

May 2011
Lower limit
or Off status.
Channel section
Channel:
Show channel:
Set channel:

Tab order section

May 2011
507
Tab order
Script
The radio button 's Assign Value script instruction differs to other visualisation object/
parameter objects. In addition to Value are other additional menu items.
Assign Value
VisuView
[name of VisuView]
Radiobutton
[name of radio button]
In addition to Value are the items selected index and selected name. All three items
concern radio button settings. The example show a radio button set as Two. The index
provides the position of the radio button (index 2). Name is the radio button's label (Two).
The value is the radio button's enabled value (20).
Radio button settings (Configuration Write)
508

May 2011
VisuView
[name of VisuView]
Radiobutton
Count indicates the number of entries/indexes a radio button has.
The Orientation setting enables orientation to be changed during runtime. 0 = vertically

positioned option fields; 1 = horizontally positioned option fields; 2 = option fields displayed
in 2 columns.
2.4.2.2.21 Drop down and Channel drop down

The drop down boxes set binary and analog values. The Channel drop down is for channel
selection.
Drop down
Channel drop down

May 2011
509
2.4.2.2.21.1 Drop down

The drop down boxes set binary and analog values. The drop down is an input field with a
scrollable dropdown list. Users can either select a list item or perform direct input.
Drop down settings

the drop down tab are other tabs that are described in the visualisation object properties
section.
Drop Down tab

The drop down tab enables settings to be made for the drop down objects.
510

May 2011
Display section
Background color
object.
Font
Drop Down Box

May 2011
511
Sort by Name
Displays the dropdown list alphabetically.
Sort by Value
Displays the dropdown list according to value.
Auto Complete
In runtime, text input is automatically completed.
Auto Drop Down
For text input during runtime, the dropdown list opens automatically.
Name and Value
To manage the dropdown list items to be displayed with the drop down.
The upper table is for managing the list.
Each table entry can be selected in runtime mode.
A table entry is made up of n index, a name and a value.
The index indicates the sequence in which the dropdown list items fields are to be
displayed.
Name is the name of the item to be displayed in the dropdown list.
The value is the value to be used when the item is selected during runtime mode.
512

May 2011
When a channel is assigned to the visualisation object, the channel will then take the
value of the selected option field. This value can also be set in Pro fiSig nal Klicks via
a script.
There are three text fields below a table. Following the selection of an entry, the index,
name and corresponding value is displayed. A selected entry can be deleted or replaced
from the list using the appropriate buttons. To add an entry, enter a name, that has not
yet been used, and a value. The new entry will be added to the list by then clicking the
add button. The order of displayed list can be amended using the up-and-down button.
Default index
This section enables setting of the default option fields. "No selection" means that no
option fields are pre-selected.
Events tab
Enable events

May 2011
513

Event descriptions
Initialisation
Double click
This is triggered when double left-clicking a visualisation/parameter object.
Value change
status.
Upper limit
or Off status.
Lower limit
or Off status.
Channel section
Channel:
Show channel:
514

May 2011
Set channel:

Tab order section
Tab order
Script
The drop down box menu differs to other visualisation/parameter objects. In addition to
Value are other additional menu items.
Assign Value
VisuView
[name of VisuView]

May 2011
Drop down box
[name of drop down box]
515
In addition to Value are the items selected index and selected name. All three items
concern drop down box items. The example show a radio entry set as Two. The index
provides the position of the radio button (index 2). Name is the radio button's label (Two).
The value is the radio button's enabled value (20).
Drop down box settings (Configuration Write)

VisuView
[name of VisuView]
Drop down box
[name of drop down box]
Drop down box
settings
Default value
The default value for the drop down box.
Initiate function
Script
Initiate
Visualisation
[VisuView name]
516
Dropdown box

May 2011
Initiate Visualisation\VisuView_1\Drop D.Drop down box_1:: Add item(In: Name\Object,

Value\Object)
Add item adds an item to the dropdown list during runtime. The item has a name and
value.
Initiate Visualisation\VisuView_1\Drop D.Drop down box_1:: Remove item(In: ItemIndex

\Object Out: LVResult)
Remove item deletes an item from the dropdown list. The index is required of the item to
be deleted.
Initiate Visualisation\VisuView_1\Drop D.Drop down box_1:: Clear box()

Clear box deletes all the items from a dropdown list.
2.4.2.2.21.2 Channel drop down
Channel drop down is used to select channels. The channel drop down is an input field with
a scrollable dropdown list. Users can either select a channel or directly input a channel.
Channel drop down settings

the channel drop down tab are other tabs that are described in the visualisation object
properties section.
Channel drop down tab

The channel drop down tab enables settings to be made for the channel drop down
objects.

May 2011
517
Display section
Background color
object.
Font
Channel drop down box
518

May 2011
Sort by Name
Displays the dropdown list alphabetically.
Auto Complete
In runtime, text input is automatically completed.
Auto Drop Down
For text input during runtime, the dropdown list opens automatically.
Channel filter
To manage the channel items to be displayed with the drop down in runtime mode.
Channels can be selected according to different filters. Only those channels with the
selected type are then added to the list. It is also possible to add channels and delete
individual channels. Users can manipulate the list to get the required channels.
Only writeable channels

Only writeable channels are added to the list/ are available during runtime mode.
Also Show Inactive Channel
Non-active channels are also available during runtime.

May 2011
519
Mark the channel types that are to be displayed during runtime.

Select All check boxes all channel types.
Only channels are available that have been selected in hardware channels. If "All
Channels" is enabled in the "Choose Channels" dialog, all channels will be available
from the connected hardware devices. The channels will also be listed for devices
that are attached during runtime, as long as the channels are of the filtered
channel type.
Enabling for example Analog input and Analog output then lists in runtime mode all the
analog channels. Refer to the example for a better understanding of the channel selection
process.
520

May 2011
Advanced
The "Advanced" button enables individual channels to be added to the list even though
their channel types have not been selected. Individual channels can also be deleted even
though their channel type has been enabled.
Events tab
Enable events
Event descriptions

May 2011
521
Initialisation
Double click
Value change
status.
Upper limit
or Off status.
Lower limit
or Off status.
Script
The channel drop down menu differs to other visualisation/parameter objects. In addition
to Assign Value are other additional menu items.
Assign Value
Channel ID provides in runtime mode the channel ID of the selected channel in the channel
drop down. In addition are the items selected index and selected name. These concern the
selected channel in the channel drop down. The index provides the position of the selected
channel. Name is the channel name selected in the channel drop down.
VisuView
[name of VisuView]
Channel drop down
[name of channel drop down]
Channel drop down box settings (Configuration Write)
522

May 2011
VisuView
[name of VisuView]
Channel drop down
Channel drop
Channel filter
down settings
Channel filter (Configuration Write)

VisuView
[name of VisuView]
Channel drop down
To make channel filter settings during runtime mode.
more Values (Configuration Write)

VisuView
[name of VisuView]
Channel drop down
more Values
2.4.2.2.22 Label
The Label object is used to portray analog values and text.

May 2011
523
Label settings
the label tab are other tabs that are described in the visualisation object properties
section.
Label tab
The label tab enables setting of the object's specific properties.
Display section
524

May 2011
Background color
object.
Font
Label
In the Label area, the text to be displayed is defined. The text is made up of a Prefix, a
Value and a Suffix.
Prefix: (Text field)
Text, that is positioned before Value .
Value: (Text field)
When the object has a channel assigned to it, this field is then reserved for the
channel's numerical value. The field is then disabled and any input deleted.
When the object has no channel assigned to it, users can input here any numeric or
text string. Input can also be made via a script in Pro fiSig nal Klicks.
Suffix: (Text field)
Text, that is positioned after Value .
Automatic Number Detection
Enables formatting for a numeric value.

May 2011
525
decimal places.
displayed.

Data format
##0.0
##,###0.0
000000.0000
############.##
Display format
73.6
1,073.6
001073.5580
1073.56
Direction
Left
The text is left-aligned.
Center
The text is centered.
Right
The text is right-aligned.
Events tab
Events section
526

May 2011
Enable events
Event descriptions
Initialisation
Left click
Right click
Double click
Value change
status.
Upper limit
or Off status.
Lower limit

May 2011
527
or Off status.
Channel & Tab Order tab
Channel section
Channel:
Show channel:
Set channel:

Tab order section
528

May 2011
Tab order
Script
Label settings (Configuration Write)

VisuView
[name of VisuView]

May 2011
Label
[name of label]
Label settings
529
The direction setting enables alignment to be changed during runtime. 0 = left-aligned; 1 =

centered; 2 = right-aligned.
2.4.2.2.23 Picture
The Picture visualisation object can be used to set binary values and to display image/
graphics files.
530

May 2011
Picture settings
the picture tab are other tabs that are described in the visualisation object properties
section.
Picture tab
The picture tab enables setting of the object's specific properties.
Picture
The picture object is a button which, depending on its switch settings, can have various
graphics displayed on the button surface.
To display a graphic/image without the button function, enter the graphic/image to be
displayed under Picture On: and uncheck Enabled in the General tab.
The following file types can be displayed:
GIF Image File (*.gif),
JPEG graphics file (*.jpg) or (*. jpeg)
Bitmaps (*.bmp)
Icons (*.ico)
Enhanced meta file (*.emf)

May 2011
531
Windows meta file (*.wmf)

Picture On:
The graphics to be displayed when the object is in the On-position. The button opens a
file selection dialog to select the image file.
Picture Off:
The graphics to be displayed when the object is in the Off-position. The button opens
a file selection dialog to select the image file.
Proportional
Displays the image in proportion to the size of the object (proportionally to the width
and height of the original file).
Stretch
Displays the image file according to the object's scale.
Picture only
Image is enclosed within a frame.
File input without path

If a filename is input without a path it will be searched for in the following:
"Images" folder in the applications folder
Application folder
Project folder
Function
Switch/button (optional button)

Clicking the image changes the button-status and therefore the image. Status false
displays the Picture Off, status true displays the Picture On.
Button
Displays the Picture Off. Clicking and holding the button displays the Picture On. Picture
status is then true. Releasing the button displays Picture Off and Picture status is then
false.
Inverted
Available only for buttons. Clicking and holding the object displays Picture Off; releasing
displays Picture On.
View
If the image has been assigned a non-writeable, the object can then only be displayed.
Because values may not be written to the channel, clicking the object can not change
the picture status.
Change screen section
532

May 2011
A different VisuView can be placed in the foreground in runtime mode.

When enabled, the selected VisuView under Change Screen to: is placed in the
foreground.
Change Screen to:
Events tab
Events section
Enable events
Event descriptions
Initialisation

May 2011
533

Left click
Right click
Double click
Value change
status.
Upper limit
or Off status.
Lower limit
or Off status.
Channel tab
Channel section
Channel:
Show channel:
Set channel:
534

May 2011

Script
Change view (Configuration Write)

VisuView
[name of VisuView]
Picture
[name of picture] u Change view
Picture settings (Configuration Write)

VisuView
[name of VisuView]

May 2011
Picture
[name of picture] u Picture settings
535
Config Write
Clicking the left object opens a menu with the functions Switch, Button and View.
2.4.2.2.24 Table
A Table displays measurement data in table format. The measurement data is added to the
table via script commands (Pro fiSig nal Klicks only). Table objects can display text and
numerics that can then also be displayed within reports.
Table settings
A table's basic settings such as number of rows/columns is set in the table settings dialog.
The dialog is opened by double-clicking the object in edit mode. It can also be opened via
the object's Context menu/Properties. In addition to the table tab are other tabs that are
536

May 2011
described in the visualisation object properties section. The settings dialog can not be
opened when the object is in configuration of standard (i.e. table is displayed with a red
border). To access settings, close the configuration of standard mode.
The Table tab
Display section
Background color
object.
Font

May 2011
537
General
Fixed rows
No further rows can be added in runtime mode.
Rows:
Number of rows in the table.
Fixed Columns
No further columns can be added in runtime mode.
Columns:
Number of columns in the table.
Row Header
Displays row headings in the first column. The text for row headings is entered in edit
mode via the context menu item Title properties. Alternatively, row headings can be
automatically numbered via Automatic counter.
Prefix and Suffix:
Row headings can also be given prefixes and suffixes. Prefix comes before and suffix
following each heading.
Column Header
Displays headings in the first row. The text for headings is entered in edit mode via the
context menu item Title properties. Alternatively, row headings can be automatically
numbered via Automatic counter.
Automatic Counter
Available only when Row Header or Column Header is enabled.
538

May 2011
Heading cells are then automatically numbered. Prefix and Suffix enables text to be
displayed before and after the number.
Prefix and Suffix:
Column headings can also be given prefixes and suffixes. Prefix comes before and suffix
following each heading.
Negative Values Red
Displays negative numerics in red (cells must then gave integer or floating point data
type settings).
Data Type Settings
Cell
Enables each cell to have a different data type.
Row
All rows take the first row's data type.
Column
All columns take the first column's data type.
Default data type
The default data type for new cells.
CSV Settings
CSV Delimiter (Text field)

When using a CSV-file (comma separated values) to load a table or when a table is to
be saved as a CSV-file.
The delimiter to be used to separate the CSV records.
Events tab
Enable events

May 2011
539

Event descriptions
Initialisation
Value change
status.
Tab order section
Tab order
Script
Assign Value
540

May 2011
VisuView
[name of VisuView]
Table
[name of table]
This script function gives access to individual table cells during runtime. Data can then
either be added to or read from the cells.
Assign Value: Visualisation\VisuView_1\Tab.Table_1[column\Object, row\Object] = Object

Left-clicking one of the two variables, column or row, opens the following menu.
Selecting Complete List/Table enables data to be added to complete tables and not just
to individual cells.
Assign Value: Visualisation\VisuView_1\Tab.Table_1[] = Object

Table settings (Configuration Write)
VisuView
[name of VisuView]

May 2011
Table
[name of table]
Table settings
541
Table settings (Configuration Read)

VisuView
[name of VisuView]
Table
[name of table]
Get column count returns the table's number of columns. Get row count returns the table's
number of rows. Get row for title returns the rows that contain headings. Get column for
title returns the columns that contain headings.
Initiate function
Script
Initiate
Visualisation
[VisuView name]
Table
[Name of table]
The Initiate function is described in the Klicks programming language under Initiate.
542

May 2011
2.4.2.2.24.1 Standard configuration of tables

In edit mode, the Table object can be placed into the "configuration of standard" mode.
The configuration of standard mode sets the row height and column width for each row/
column and the number/text format for each cell. The Configuration of standard mode is
accessed via Configuration of standard context menu item.
The table is displayed with a red border to indicate that it is in Configuration of standard
mode.

May 2011
543
Configuration of standard menu

Right-clicking the table in configuration of standard mode displays the following menu.
Right-clicking on row or columns that are defined as header cells displays title properties.
Right-clicking other cells displays column, row or cell properties.
Title, column, row, or cell properties

'Title properties' is displayed when right-clicking row/column header cells. This opens the
title properties settings dialog.
Right-clicking other cells displays 'column, row or cell properties'. Which of the three
settings (column, row or cell) is displayed depends on the Data Type Setting in the table
settings dialog. Clicking the menu item displays a dialog for column, row or cell properties.
Load from CSV
Opens a file selection dialog to select a *.csv file (comma separated values).
The dialog is for reading in previously saved table data.
CSV is the international format for importing and exporting table data. CSV created in
other programs, e.g. Microsoft Excel, can therefore also be loaded.
Save to CSV
Opens a save-file dialog, to enter a *.csv (comma separated values) export file. Header
and cell data from the table object is then saved in ASCII format. The data can be reimported via Load from CSV. A CSV file may also be opened by other programs, e.g.
Microsoft Excel.
cell data type
To directly set the data type for the cell, row or column. Clicking show data types (next
544

May 2011
menu item) displays each cell in the corresponding data type color. The data type
settings in table properties determines whether a single cell or complete row or column
has been assigned a specific data type.
show data type
Displays each cell according to a data type color.
save changes
Exits the configuration of standard mode and saves all the changes that have been
made.
Abort changes
Exits the configuration of standard mode without saving any changes that have been
made.
Title properties dialog

Header cells for columns or rows can be changed via the context menu items in
configuration of standard mode.
Title
The heading for the row or column.
Height & Width
To set a cell's height and width.
Title, column, row, or cell properties

May 2011
545
Cell, column or row properties

The data type drop down box is used to select the data type for the cell, row or column.
The data type determines the type of data that can be entered or assigned to a cell. If
data is entered during runtime that does not correspond to the set data type, the cell
displays a red background.
Selecting a 'floating point' data type enables a format to be entered for the cell,row or
column.
decimal places.
displayed.
546

May 2011
Data format
##0.0
Display format
73.6
1,073.6
##,###0.0
000000.0000
001073.5580
############.##
1073.56
Height & Width

To set a cell's height and width.
2.4.2.2.25 Timer
The Timer is used to cyclically perform program code. The timer can trigger an event after
a specific time period. This can be a one-off or repeated event. The timer has no display or
operating properties so remains hidden during runtime mode.
Timer settings
Alternatively use the visualisation object's context menu (Properties option). The dialog
tabs are explained under visualisation object settings.
Events tab
Enable events

May 2011
547
Event descriptions
Initialisation
Timer
When checkboxed, an event symbol appears in the ModuleView. Unchecking an 'Event'
removes the event from the module chart view and therefore also any programming
code it contains.
Interval
The Interval determines the frequency at which the timer event is performed. The
shortest interval possible is 50 msec. If the interval is set lower than the time required
for the event code to be performed, the code is then performed completely before
being re-triggered.
2.4.2.2.26 Date/Time
Date/Time sets dates and times.
Settings dialog
Alternatively use the visualisation object's context menu (Properties option).In addition to
the date/time tab are other tabs that are described in the visualisation object properties
section.
Display tab
The display tab enables setting of the object's specific properties.
548

May 2011
Display section
Background color
object.
Font
Date/Time Settings

May 2011
549
Date display
To hide or show the date field. When enabled, users can input a date during runtime.
Time display
To hide or show the time field. When enabled, users can input a time during runtime.
Milliseconds display
To hide or show milliseconds. When enabled, users can input milliseconds during runtime.
Available only with enabled Time display.
Auto Description
Automatically supplies descriptions for date and time input.
Align vertical
Vertically aligns data and time fields.
Events tab
Enable events
Event descriptions
Left click
The event is triggered when left-clicking a visualisation/parameter object.
Right click
Value change
status.
550

May 2011
Tab order section
Tab order
Script
Assign Value
VisuView
[name of VisuView]
Date time
[name of date time]
Time value
Date time settings (Configuration Write)

VisuView
[name of VisuView]
Date time
[name of date time]
Date time settings
Value (Read only)

May 2011
551
VisuView
[name of VisuView]
Date time
[name of date time]
Time value
The Config Write function enables the full range of time values to be displayed. It can also
display partial elements of the date fields.
2.4.2.2.27 Stop watch
The digital clock can be set to display data and/or time in a digital format. An analog clock
face can be displayed using the analog clock object. The stop clock object enables times
to be measured. An event can then be triggered once a specified time has been reached.
Digital clock
Analog clock
Stopwatch
552

May 2011
2.4.2.2.27.1 Digital clock
The digital clock displays the current time and/or date. A timezone can be set with options
to manually switch between 24-hour (0 to 24) and am and pm settings. Times are updated
both in runtime and edit modes.
Digital clock settings

the digital tab are other tabs that are described in the visualisation object properties
section.
Digital clock tab

To make specific settings for the digital clock object.

May 2011
553
Display section
Background color
object.
Font
554

May 2011
Date/Time
Options for predefined formats or a user-defined format.
Pre-defined formats
Time
Displays the time.
Date
Displays the date.
Week day
Displays the day of the week.
12-hour clock (am and pm)
Displays the time along with pm or am. When disabled, the clock display is in 24-hour
format.
Long date format
Displays month and day in long format and time information separated by a comma.
User-defined format
c
d
Displays the day of the month without a leading zero (1 - 31).
dd
Displays the day of the month with a leading zero (01 - 31).
ddd
Short week day (Mo - Su)
dddd
Long week day (Monday- Sunday)

May 2011
555
ddddd
Full date in short format.
dddddd
Full date in long format.
Displays month without a leading zero (1 - 12). When followed by h, minutes

in place of months are displayed.
mm
Displays month with a leading zero (01 - 12). When followed by h, minutes in
place of months are displayed.
mmm
Short month (Jan- Dec)
mmmm
Long month (January- February)
yy
Displays year as 2-digit number (00 - 99).
yyyy
Displays year as 4-digit number (0000 - 9999).
Displays hours without a leading zero (0 - 23).
hh
Displays hours with a leading zero (00 - 23).
Displays minutes without a leading zero (0 - 59).
nn
Displays minutes with a leading zero (00 - 59).
Displays seconds without a leading zero (0 - 59).
ss
Displays seconds with a leading zero (00 - 59).
Full time in short format.
tt
Full time in long format.
am / pm
Uses 12-hour clock. Displays am for each hour before midday and pm for
each hour after midday.
a/ p
Uses 12-hour clock. Displays a for each hour before midday and p for each
hour after midday.
Use date separator according to country settings.
Use time separator according to country settings.
Timezone section
556

May 2011
The application's time zone is used as default. Users can however enter a time zone of their
choice.
Initialisation
Script
The clock menu differs to other visualisation/parameter objects. In addition to Value are
other additional menu items.
Assign Value
Returns the time displayed by the digital clock, taking into account the timezone settings.
VisuView
[name of VisuView]
Digital clock
[name of digital clock]
Time value

VisuView
[name of VisuView]
Digital clock
[name of digital clock]
Digital clock settings
Digital clock
[name of digital clock] u Time value
Value (Read only)

VisuView
[name of VisuView]

May 2011
557
2.4.2.2.27.2 Analog clock
The analog clock displays the current time. The timezone can be set. Times are updated
both in runtime and edit modes.
Analog clock settings

the analog clock tab are other tabs that are described in the visualisation object properties
section.
Analog clock tab

To make specific settings for the analog clock object.
558

May 2011
Display
Opens a color palette to select the background color of the visualisation object.
Font
Dropdown box to select the font for the analog display.
Numeric color
A color palette to select the color for the analog display.

May 2011
559
Color matching
Color hour and minute hand
To select the color of the hour and minute hands.
Color second hand
To select the color of the seconds hand.
Color Outline
To select the color of the outline and scale lines.
Timezone section
The application's time zone is used as default. Users can however enter a time zone of their
choice.
Initialisation
Script
The analog clock menu is the same as for the clock object.
Assign Value
Returns the time displayed by the analog clock, taking into account the timezone settings.
560

May 2011
VisuView
[name of VisuView]
Analog clock
[name of analog clock]
Time value
Analog clock settings (Configuration Write)

VisuView
[name of VisuView]
Analog clock
[name of analog clock] u Analog clock settings
Analog clock
[name of analog clock]
Value (Read only)

VisuView
[name of VisuView]
Time value
Assign Value
- Time value
Returns the time being displayed by the clock. Takes into account timezone settings.
2.4.2.2.27.3 Stop clock
The stop clock object enables times to be measured. Options are available to perform
either a count-down or a count-up from a specified start time. An event can be triggered
once a value has been reached. The stop clock's appearance is similar to a button.

May 2011
561
It has the following four buttons that can be hidden/shown in the settings dialog.
Start
Starts time measurement. The time will be set to the start time provided by the user.
The stop clock can be started only when no other time measurements are being
performed.
Stop
Stops time measurement.
Pause
Pauses time measurement. Re-clicking restarts the time measurement.
Reset
Returns the stop clock to the start time.
Stop clock settings

the stop clock/watch tab are other tabs that are described in the visualisation object
properties section.
Stop watch tab

To make specific settings for the stop clock object.
562

May 2011
Display section
Background color
object.
Font
Only the background color changes, not the button colors.
Status Colors
The stop clock can be displayed in different colors according to status.
Use status colors
Status color changes the background color
Use status colors for font
Changes the font colors.
Color - Go
Color for the running status
Color - Stop
Color for the stop status
Color - Break
Color for the pause status

May 2011
563
Toolbar button
Start, stop, pause and reset buttons may be hidden with the stop clock being controlled
via script instructions.
Unit of Time
only hours
Displays hours only.
hours and minutes
Displays hours and minutes.
hours, minutes and seconds
Displays all time data (hours,minutes, seconds).
Show day overlap
Displays the day when the time extends beyond 24 hours.
Clock mode
The stop clock begins at the given start time. The default start time is zero. Count-up
means the start time is added to. Count-down means the start time is counted down to
zero. Selecting countdown automatically sets the start time to 5 minutes unless a start
time has already been entered by the user.
Event settings
Different settings appear here depending on whether the stop clock has been set to countup or count-down.
The event tab contains the event Time arrived. The time for 'time arrived' is set here.
Once this time has been reached, the stop clock will act depending on whether it has been
set for count-up or for count-down.
Count-up:
If countdown is disabled, the following appears here.
If event time is reached: keep running (default)
On reaching the event time, the stop clock continues running.
If event time is reached: stop
On reaching the event time, the stop clock stops.
If event time is reached: restart
On reaching the event time, the stop clock restarts from the start time.
Count-down:
If countdown is enabled, the following appears here.
If countdown is arrived: stop
The stop clock stops when reaching 0.
If countdown is arrived: restart
When the stop clock reaches 0, it restarts at the start time.
564

May 2011
Events tab
The stop clock is triggered by the following events.
Event descriptions
Initialisation
Right click
Stop watch/clock started
Triggered when the user clicks the start button. Triggered only when the stop clock is
not currently performing a time measurement.
Stop watch stopped
Triggered when the user clicks the stop button. Triggered only when the stop clock is
currently performing a time measurement.
Stop watch break
Triggered when the user clicks the pause button. Triggered only when the stop clock is
currently performing a time measurement.
Time arrived
Triggered when the event time has been reached. The event time is set under the stop
clock tab.
Null arrived
Triggered when the stop clock reaches 0. Triggered only when countdown is enabled.
Script
Assign Value

May 2011
565
VisuView
[name of VisuView]
Stop watch
[name of stop watch]
State
Returns the stop clock's current state.
State 1 = stop clock running.
State 2 = stop clock stopped.
State 3 = stop clock paused.
Time
Returns the time being displayed by the clock.
LED settings (Configuration Write)

VisuView
[name of VisuView]
Stop watch
[name of stop watch]
Stop watch settings
Initiate function
The following object functions are available for the stop watch/clock.
Start
Stop
Break
Set start value
2.4.2.2.28 Trend
The Trend (or trend graph) is a sophisticated tool for measurement data visualisation and
analysis. The following diagram types are available.
Yt-diagram
Logic diagram
YX-diagram (table)
YX-diagram (hardware channels)
FFT diagram
Orbit diagram
566

May 2011
A trend is structured into five areas. These areas are not always shown:
Tool bar
Graph area (chart)
Channel table
Graphics tool box
Status bar
Trend default view

A trend can be operated when an application is in runtime mode. When the application is in
edit mode, trend objects can have two possible states. The operation of the objects differs
depending on state.
In the normal state, the trend chart behaves in edit mode like any other visualisation
object. This means that the trend chart can be moved within the VisuView using the
mouse, its size can be altered and its settings window can be opened by double clicking.
Right-clicking the trend chart will open a context menu with the menu item Configuration of
standard. Selecting this option switches to another state. In this state the trend is
operational and the trend's default appearance can be set.

May 2011
567
The trend is displayed with a red border to indicate that it is in the Configuration of
standard state.
568

May 2011
The trend chart can now be used as if in runtime mode. Settings made here (e.g. axes
scaling, selection of channels to be portrayed, type of curve etc.) can be saved; these
saved settings will then become the default settings for the trend chart when switching
from edit mode to runtime mode. The settings may be changed during a runtime mode
session but the trend chart will always revert to the default settings with each new switch
into runtime mode.
Exit the state by clicking commit changes or discard changes. These menu items can be
called from any area within the trend object.

May 2011
569
The
symbol also exits the configuration state. The user will be promoted to commit or
discard the changes.
Linking trends and recorders

The trend has only a limited area for storing measurement data. When this storage area is
full, the oldest measurement data is overwritten and can therefore no longer be displayed.
By linking trend and recorder objects enables all data to be displayed that has been
recorded.
When a trend is linked to a recorder, it displays the stop and start recording times (see
example below of the start/stop times for a Yt diagram).
To link a trend with a recorder, go to the trend settings and click on the trend settings
tab.
2.4.2.2.28.1 Trend settings

Trend settings are set using the trend settings window. This window is used to select the
channels to be portrayed in the trend. It is also used to generate a link between the trend
and a recorder object.
Alternatively use the visualisation object's context menu (Properties option). The window
can only be opened in edit mode but not when in the configuration state (i.e. the trend
chart is surrounded with a red border line). Exit the configuration state before opening the
trend settings window. Tabs that are not described here are explained under visualisation
object settings
570

May 2011
Events tab
Initialisation
Channel selection tab
Assigned channels
The table shows the measurement channels currently assigned to the trend. The table

May 2011
571
displays the channel name and comments which have been set in the T o pMe ssag e
Configurator.
Choose channels
This button opens the Channel selection window.
The channels assigned to the application are displayed on the left of this window (refer
also to selecting application channels). Any of these channels can be portrayed in the
trend. The channels listed on the right are the channels which are currently assigned to
the trend chart.
To select a group of consecutive channels, click the first channel in the group, press
SHIFT and click the final channel in the group. When the channels are not consecutive,
press CNTRL and click on each required channel. Click Add or move the channels to the
right using drag&drop.
To delete a channel from the trend chart, mark the channel in the list on the right and
click Delete.
Confirm changes with OK or ignore with Cancel.
Note:
The channel selection dialog can also be opened via the visualisation object's context
menu from the VisuView.
Trend Settings tab
572

May 2011
Grid(check box and dropdown list)

Displays a grid behind the measurement curves. The dropdown list sets the appearance
of the grid.
Grid (color field)
Opens a color palette to select the raster color.
Trend background (color field)
Opens a color palette to select the background color for the trend chart axes (refer to
the example in trend color settings).
Chart background color (color field)
Opens a color palette to select the background color for the trend (refer to the example
in trend color settings).
Trend Text Color (color field)
Opens a color palette to select the trend's text color (refer to the example in trend color
settings).
Trend Scale Color
Opens a color palette to select the trend's grid color (refer to the example in trend color

May 2011
573
settings).
Trend Background Color(color field)
Opens a color palette to select colors for the toolbar, status bar and toolbox areas (refer
to the example in trend color settings).
Allow open mesfile
Activates a button in runtime mode which allows the opening of measurement files.
Mesfile time range
When check boxed, the time axis for the opened measurement file can not exceed the
saved time scale.
Show selected channel
When checked, those channels are which have been selected in the channel table are
highlighted in the diagram.
Enable button 'Standard'
Displays a restore default settings button in runtime mode.
Enable button 'trend settings'
Displays a settings dialog button in runtime mode.
Mouse Cursor section
Determines the information to be displayed when using the cursor. This section is
available only for Yt and logic diagrams.
Marker section
Determines the information to be displayed when using markers.
Data source tab

To set the data source for saved data. The data source will be accessed to display
archived data.
Automatic (best data source)

Recommended and necessary when there is only one or no database available. Selecting
channels that are not in a database will automatically save the channel data for a
specific time period.
Recorder
One or more recorders can be selected when these have been installed onto the
VisuView. Recording limits will be automatically incorporated into the trend. Refer also to
linking trends and recorders.
574

May 2011
Special database
The trend uses the selected database as its data source.
Refer also to the section on saving measurement data
The trend's status bar shows the data source currently being displayed.
Print Layout tab
Use individual print layout

When enabled, users can use the print layout settings button to open the printer
settings dialog. Individual printer settings can be given for each trend object. The printer
settings will be saved as start settings and used for subsequent output.
The following shows the effect of color selections on a trend object.
View of the trend:

May 2011
575
2.4.2.2.28.2 Using the trend chart
This section describes how to use a trend. Trends can only be used and operated directly
within runtime mode.
If the application is in edit mode, a trend can also be operated by switching to standard
configuration.
Tool bar functions
The taskbar provides hide/show functions for the various display elements within a diagram.
The diagram name is also displayed.
Hides/shows the diagram's graphical portrayal.

If only the graphical part is being shown, the channel table will then display on
hiding the graphical part. Graphic and table can not be hidden at the same time.
Hides/shows the channel table.
Hides/shows the Graphics toolbox.
Hides/shows the diagram's taskbar.
For some types of diagram, this symbol can hide/show an extended graphics
toolbox.
576

May 2011
Activates the properties dialog.

Displays a trend in full screen mode. This is available only in runtime mode.
If the trend is in standard configuration the tool bar appears as follows:
Exits the standard configuration state. Users will be prompted to commit (save)
or discard (abort) any changes made.
Trend graph functions
The trend graph portrays measurement data channels. Measurement curves and axes are
displayed. Display settings are mainly made using the graph toolbox. The channel table
determines which measurement curves are to be displayed as well as how measurement
curves are assigned to y-axes.
The settings made using the graph toolbox determines how the graph area operates. The
graph toolbox functions are described for each graph/diagram type.

May 2011
577
Channel table functions are available in runtime mode and in standard

configuration. This section describes only those functions that are common to
all graph/diagram types.
The channel table lists the measurement channels assigned to a diagram. If a diagram has
more than one Y-axis, every Y-axis is included with its name. The measurement channels
are listed under the Y-axes to which they are assigned.
The majority of information within the table is taken from the channel properties defined
within the TopMessage Configurator.
Name
Value
Unit
State
Scale min / Scale max
Tolerance
Comment
Channel type
Channel ID
Module type
Device time difference
Time
Timezone
Data type
Device name
The values in the colour and show columns can be amended with the channel table.
578

May 2011
The Colour column determines the colour of the measurement curve within the graphical
section. The colour can be changed by double clicking the colour field. This will display a
colour palette from which the curve colour can be selected.
Unchecking the Show hides the curve in the graphical section.
The Show and Hide buttons hide or show all the curves assigned to the diagram. The
channel filter button hides the channels in the channel table which are also hidden in the
diagram.
Selecting (by marking) a channel or axis within the channel table will highlight the
measurement curve within the diagram (curve and y-axis with bolder display).
Mark a channel or axis by left clicking. Clicking an already selected channel or axis then
deselects it. Deselection can also be made by clicking on an empty area within the channel
table.
Graph / channel table split

The graph and table are separated by a thin blue line. The line can be moved by positioning
the mouse cursor above it. Left-click the line to move it to the required position.

The channel table can be amended via a context menu. Amendments can be made only in
runtime mode or in standard configuration. The section on channel table context menu
describes the menus that are common to all (or the majority of) graph/diagram types.

May 2011
579
Graph toolbox functions

Toolbox functions differ for different types of diagram. The graph toolbox explains only
those functions that are common to all or the majority of graph/diagram types.
Status bar functions

The status bar displays trend information such as the current mouse position. The status
bar is explained for each graph/diagram type.
The channel table's context menu differs according to whether the item selected is a
measurement channel, a Y-axis, a point on a specific diagram (e.g. the X-axis in a YXdiagram) or a column heading.
In standard configuration, the context menu also contains the items commit changes and
discard changes.
Commit changes
Saves the changes for the trend currently being displayed.
Discard changes
Discards the changes made to the current trend.
Context menus for measurement channels and points on specific diagrams

Measurement channel context menus differ according to graph/diagram type and are
explained for each graph/diagram type, as are the points on specific graph/diagram types.
580

May 2011
Y-axis context menu
Add y-axis
Adds a y-axis. The number of Y-axes is limited to four.
Remove y-axis
Deletes selected y-axis. Only y-axes not assigned to channels can be deleted.
Y-axes settings
Opens the Y-axis settings dialog. This dialog is used to configure Y-axes.
Column header context menu
Sorting
To sort the channel table. The channel ID is the default sorting parameter. The sort
mode is set to Automatic. In Custom sort, mode, users can use the mouse
(drag&drop) to set the channel order (refer to sorting the channel table).
Columns
To select the columns to be displayed in the channel table. Left-clicking a menu
option adds (by checking) or removes (by unchecking) the column to/from the table.
Columns to be shown appear as checked.
Channel filter
This refers to the channel filter button.

May 2011
581
Add Y-axis
Adds a Y-axis. The number of Y-axes is limited to four. This option is available only
for diagrams that support multiple Y-axes.
Set y-axes
Opens the Y-axis settings dialog. This dialog is used to configure Y-axes. This option
is available when only one Y-axis has been set up and therefore has no entry for the
Y-axis in the channel table.
Toolbox functions differ for different types of diagram. This section explains only those
functions that are common to all or the majority of graph/diagram types. For clarity, the
functions are sorted in function blocks according to settings.
1.Navigation in the toolbox
To navigate within the graph toolbox. The symbols are displayed only when
the diagram is too narrow to allow the display of all symbols.
2.Navigating/moving the graph area

To navigate around the graphical area. The scale remains the same.
This symbol moves the current section of the graph area to the left.
This symbol moves the current section of the graph area to the right.
3.Trend graph zoom functions

Compresses the trend graph's scales (zooming with set zoom factor).
582

May 2011
Extends the trend graph's scales (zooming with set zoom factor).
Adapts the scales automatically to the measurement curve to be displayed
(automatic scaling). FFT-diagrams display the complete range of frequencies
(on the x-axis) and/or the complete range of amplitudes (on the y-axis).
4.Selecting mouse mode in graph area
Provides the mouse with a cropping function (expands a variable section). Creates
a "moused" rectangle of the section to be expanded by left clicking and releasing
the mouse.
The cropping function can also be enabled/disabled by double-clicking in the data
area.

May 2011
583
The mouse moves along the scale within the graph area. Left click the trend
chart, and drag&drop at the required position.
The mouse cursor in the data area then appears as

action is performed on all y-axes.
. For multiple y-axes, the
The direction of movement is also displayed in the y- and x-axis areas. For
multiple y-axes, a single axis can be moved.
Provides the mouse with a zoom function (to enable zooming in and out). Zoom in
by left clicking and moving the mouse upwards and/or to the right and releasing.
Zoom out by left clicking and moving left / downwards.

the action is performed on all y-axes.
. For multiple y-axes,
multiple y-axes, a single axis can be stretched/compressed. Switching between
pan and zoom is possible by double clicking.
The pause key enables users to switch between online and offline data. Clicking
the pause key switches to analysis mode (offline). If the pause key remains
unclicked, online data is displayed. The pause key is unavailable for analysis
diagrams.
5.Undo function
Undoes the last zoom operation (performed via either the graphic toolbox or
mouse). More than one operation can be undone, i.e. pressing undo twice will
undo the last 2 operations, pressing undo 3 times will undo the last 3 operations
etc...
To redo an undone operation.
To undo all saved operations.
6.Analysis functions
Markers, text fields, and cursors are important tools in the analysis of measurement
curves.
584

May 2011
Enables Assigning text to a marker. Available only for Yt-diagrams.

To hide/show current markers
Opens the marker T text field overview with marker and text field tabs.
Enables add a text field .
To hide/show current text fields
To hide/show current alarm events. Available only when alarms are displayed
(refer to Fault diagnostics und Acquisition of fault data)
To select a priority for displaying a marker. Only those markers are displayed
that have a priority equal to or greater than the set priority.
Update graph
Forces the measurement curves to be redrawn (necessary only when the graph
has errors).
Open measurement data file

Opens the analyse measurement file dialog.
Print
Opens the Print diagram dialog to print the currently displayed graph.
Configure diagram

May 2011
585
Configurations can be saved to a TrendConfig (*.tcg) file and later reloaded. The trend
chart configuration only is saved to this file and not the measurement data. The
configuration that is saved differs according to the type of diagram.
To load a *.tcg file.
To save the current trend chart configuration to a *.tcg file.
To save the current trend chart configuration to a *.tcg file. If an HDS file is
being used, the configuration is saved to this file. If a database is being used, the
configuration is saved in ProfiSignal and is available in the dialog showing a
database in a trend dialog.
Resets the trend object to its default values. The section on standard
configuration describes the default view. Available only for trend objects .
2.4.2.2.28.3 Script language
The common menu items for the Assign value, Config Read and Write script functions, and
explained.
This section describes the specific script functions for trend objects.
Functions for channel selection
Clear channel group
Deletes all channels in the trend's channel list.
Add channel
Adds a channel to the list.
Delete channel
Deletes a channel from the channel list.
Functions for configuration

All channels visible
All the diagram's channels are shown.
Channel visible
A single channel is shown.
Load config
Loads a configuration file.
Save config
Saves the current configuration to a file.
Save config to MesFile

measurement data file.
Saves the current configuration to the displayed
Load standard configuration
Restores the default view.
Set X-axis range
Sets the X-axis range.
Set Y-axis range
Sets the Y-axis range.
586

May 2011
Suppress update
Switches on/off suppress update.
Clear drawing area
Clears the graph area.
Set channel color
Sets channel color.
Set channel Y-axis
Assigns a Y-axis to the channel.
Functions for displaying data

back to online Trend
Switches to the trend's online mode
Freeze diagram
Pauses the diagram
Show timerange
Sets the time range to be displayed.
Show last recording
Shows the last/current recording.
Set online timerange

displayed in online mode.
Sets the time window in which the trend is
Load MesFile
Loads a measurement data file.
Other functions
Export to MesFile
Starts data export for the trend's channels.
ASCII export
Starts ASCII export of the trend's channels.
print Trend
Prints the current trend using the default printer.
2.4.2.2.28.4 Yt-diagram
The Yt-diagram portrays measurement data over time periods. A Yt-diagram can
simultaneously display multiple channels. Further information on operating the Yt-diagram is
available under operating a trend.

May 2011
587
The trend here is displaying a total of three measurement channels (in the graph area).
The channels are shown with 2 Y-axes with their own scales.
Channel table
The channel table lists the measurement channels assigned to a diagram.
Graph/diagram area (chart)

The graph area portrays measurement data channels. Measurement curves and axes are
displayed. Display settings are mainly made using the graph toolbox. Mouse operations in
the graph area take place according to settings in the graph toolbox. Further details are
available in the graph toolbox.
Graph toolbox
The graph toolbox provides a range of functions for graphical analysis.
Status bar
588

May 2011
The mouse position (portrayed as a cross) in the graph area returns the values for time
and Y. In this example, the X-axis is time and the Y-axis the amount of degrees. By using
the mouse, users can therefore obtain an exact reading for a specific point in the graph
area.
For multiple Y-axes, the status bar reading is always for the selected Y-axis. The status
bar gives the Y-axis description (in this example: Y2 [C]).
The data source is always the currently open measurement data file.
Yt-diagram analysis functions

Marker, text field and cursor provides the Yt-diagram with important aids for analyzing
measurement curves.
Markers, set time markers at any point. Text can then be assigned to each time marker.
Markers can be saved so that they can be used again a later evaluation of the
measurement files.
Mouse cursor limits, evaluates and documents the time ranges for measurement curves.
The Yt-diagram settings dialog enables the generation of individual settings and
measurement data.

May 2011
589
The Genera, Style, and References tabs are common for all visualisation objects and are
described in visualisation object settings.
The tabs Channel Selection, Events,Trend Settings, (for making general settings to the
diagram), Data Source and the Print Layout tab are described in trend settings.
Graph area layout for a Yt-diagram
590

May 2011
Data area
Context menu
The following context menu can be opened in the data area:
Show timerange
Opens a dialog to select the time range that is to be displayed.

May 2011
591
Export
A variety of export options are available for trends. Refer to the section export options for
trends.
Configuration
The configuration option in the context menu enables setting of the time zone for the
display as well as permanent saving and the loading of trend configurations. For an
explanation of this option, an option which is also available for all diagram types, refer to
the section on general functions for the graphical areas.
If the mouse cursor is shown, the context menu includes:
Maus Cursor bewegen

This option appears only when the Cursor is being displayed. The mouse modus can be
amended using the buttons in the graphics toolbox that enable zooming functions with a
displayed cursor. This option can be used to re-activate the Move mouse cursor mode.
The Move mouse cursor mode is enabled when checkboxed.
MouseCursor Ansicht
For setting the appearance of the mouse cursor. The default information that is displayed
per channel is the channel measurement data, channel name and unit of measurement. For
Cursor 2, the difference between Cursor 1 and Cursor 2 is also displayed.
592

May 2011
The channel name, unit and difference can be hidden (unchecked) and re-displayed
(checked).
Statistics
This option appears only when the Cursor is being displayed. A statistic table is opened
with a table of additional information such as the channels' minimums and maximums
between the cursors on the time scale. The statistics are generated for all displayed
channels.
If markers or text labels or being shown, the context menu includes:
Edit marker/textlabel
A range of functions are available in the graphical part of a diagram. To enable problemfree operation and to avoid unintended amendments, users can switch, e.g. when working
in mouse mode, to the mode for edit markers and text fields. This menu option enables
users to switch to the mode for editing markers and text fields and displays whether a user
is in this mode (checked) or not (unchecked). Enables text fields and markers to be
changed.
Textlabel ...
Enables access to the edit functions for a selected, single text field. This option is available
only when markers are being shown and a text field has been marked. Marked text fields
have a dashed border and non-marked fields a solid border. Text fields can be marked only
in the edit marker / text field mode. Click the text field to be edited. The border then
appears as dashed and the "text field"context menu opens.

May 2011
593
Marker ...
To select what information is to be displayed (checked) or hidden (unchecked) for all
markers. The channel information option applies to all channels that are assigned a marker
and includes the channel name and unit options. This means that when channel information
is hidden, then the channel name and unit is also hidden.
Open marker/ text field overview

Opens the marker / text field overview to enables the management of markers and text
fields (hidden). Further information is available under marker overview and text field
overview.
Zoom functions
Zoom functions (also referred to as mouse modes) are enabled via the graph toolbox. They
are described under graph toolbox functions.
Double-clicking the data area enables the zoomed area to be changed. The mouse cursor
changes its appearance:
Mouse cursor with
disabled
zoom function
Mouse cursor with enabled

zoom function
594

May 2011
Y-axes
A Yt-diagram can portray up to 4 y-axes. Y-axes are added via the channel table. Y-axes
can be positioned to the left or right of the data area. Refer here to y-axis settings dialog.
Context menu
The following context menu can be opened in the y-axes area:
Y-axis settings
Opens the Y-axis settings dialog.
Show timerange
Export
trends.
Configuration
Zoom functions

May 2011
595
If the zoom function is enabled in the graph area, the mouse cursor at the y-axes changes
as follows:
Pan - Left-clicking and moving the mouse pans along the y-axis.
Zoom - Left-clicking and moving the mouse stretches/contracts the y-axis.
Info:
Switching between pan and zoom is possible by double clicking.
Time axis
Context menu
The following context menu can be opened in the time axis area:
Configure time axis

Opens the time axis configuration dialog to set the display settings for the time axis.
Show timerange
596

May 2011
Export
trends.
Configuration
The Toolbox object is used to make settings for the different types of graphs/diagrams.
The toolbox differs for different types of diagram. This section explains only those functions
that are common to all or the majority of graph/diagram types. For clarity, the functions
are sorted in function blocks according to settings.
Display options
Hides/shows a background grid for the graphical area
Enables/disables the filter function for measurement data.
Changes the measurement curve line-type. A stepped curve is the default setting.
The symbol shows the type of curve that is displayed after clicking:
Enables the points to be joined as a line.
Enables the points to be joined as steps. This setting also displays curves for
slow channels.
Enables the curve type settings made by the user for each channel. Refer to

May 2011
597
channel settings dialog.

This symbol is shown only when users have amended a channel's curve type.
Sets the type of measurement curve to be displayed (hides/shows measurement points). A line is
the default setting. The symbol shows the type of curve that is displayed after clicking:
Enables the symbol and line type of portrayal. Measurement points are marked and joined.
Enables the symbol portrayal. Only the measurement points are displayed.
Enables the line portrayal.
Relative axes
Enables relative scaling of the time axis (available only when one measurement file is
being portrayed or when the trend is connected only to one recorder). Recording begins at
a zero value.
Enables relative scaling of the y-axis. The values for 0 and 100% correspond to the
scaling values set for each channel within the TopMessage Configurator as well as in the
channel table's Scale min and Scale max columns.
Moving along the axes
(Available only with an open measurement data file or trend linked to a recorder
object). The graph area displays from the beginning of measurement file/recording. The
scale remains the same.
The graph area displays the end of a measurement data file/ near the current time.
Trend graph Zoom functions
The graph area is compressed (zoom function with set zoom factor).
The graph area is extended (zoom function with set zoom factor).
(automatic scaling).
598

May 2011
Select mouse mode
In the graph area the mouse has a cropping function (expands a variable section).
Create a "moused" rectangle of the section to be expanded by left clicking and releasing
the mouse. Create a "moused" rectangle of the section to be expanded by left clicking
and releasing the mouse.
The mouse moves along the scale within the graph area. (i.e. left click on trend
chart, hold down and move (drag) then release (drop) at the required position).
Provides the mouse with a cropping function (zooms in and out of a variable
section). Zoom in by left clicking and moving the mouse upwards / to the right and
releasing. Zoom out by left clicking and moving left / downwards.
Example: channel's current value at the cross-hairs
Pause mode within the trend graph
Enters pause mode (only for online portrayal of measurement data) This means that
the scale range for y and time axes become static. The pause mode can be automatically
activated and deactivated by other symbols within the graph toolbox.
Analysis functions
Assigning text to a marker

May 2011
599
Display marker
Enable cursor
Text field
Other functions
These are described in functions of the graphics toolbox.
Undo function
Update graph
Configure diagram
2.4.2.2.28.5 Logic diagram
The logic diagram is a Yt-diagram for analog signals (upper diagram) combined with a logic
section (lower diagram) for evaluating the edges of digital signals.
600

May 2011
Channel table
The channel table lists all the measurement channels assigned to a diagram. In logic
diagrams, the channel table is split into analog and digital channels.

The graph area displays the channel data. Measurement curves and axes are portrayed.
Display settings are mainly made using the graph toolbox. Mouse operations in the graph
area take place according to settings in the graph toolbox.
Graph toolbox
The graph toolbox provides a range of functions for graphical analysis. They are the same
as for the Yt-diagram's graph toolbox and are therefore not explained here.
The magnifier function is unavailable for logic diagrams. The magnifier button is therefore
replaced with a hide/show button for the data area.
The button is on (default) when the data area is displayed.
Status bar
The status bar is the same as the Yt-diagram status bar.
2.4.2.2.28.6 Oscilloscope diagram
The oscilloscope diagram enables the display of medium to high-speed and one-off, i.e.
transient, processes.
The oscilloscope portrayal is a snapshot of a longer curve portrayal. The oscilloscope
portrayal requires triggering. The oscilloscope portrayal remains until re-triggered and
sufficient measurement data is available.

May 2011
601
The tabs Channel Selection, Trend Settings, (for making general settings to the diagram),
Data Source and the Print Layout tab are described in trend settings.
602

May 2011
Oscilloscope mode tab

Time range
To select the required time range.
Pretrigger
To observe signal activity prior to the trigger time. Pretriggers can be set in the 0% to
100% range at 5% intervals.
Trigger source
To select the trigger channel. Available channels include all diagram channels (for online
analysis) and/or application channels (for visualization objects).
Analog channel
Triggering requires users to select both the edge and threshold

value.
Digital channel
Triggering requires users to select the edge.
Time signal for AMDT

and/or ExpertVib
Additional settings are not possible. Trigger time, time range, and
pretrigger are already set by the time signal.
Edge
Positive edge
Negative edge
Threshold value
The threshold/limit value for analog trigger channels. The signal triggers when the
threshold/limit value is either overrun (positive edge) or underrun (negative edge).
Channel table

Display settings are mainly made using the graph toolbox and the extended graph toolbox.
Mouse operations in the graph area take place according to settings in the graph toolbox.

May 2011
603
Graph toolbox

The extended graph toolbox is hidden/shown using the
button.
The extended graph toolbox facilitates operation in the oscilloscope mode.
Status bar
2.4.2.2.28.7 YX-diagram (table)

The Visuobjekt YX-Diagramm (Tabelle) portrays characteristic curves.
604

May 2011
Channel table / characteristic curve table

In YX-diagrams, a characteristic curve table is displayed as well as a channel table. Further
details are available in the characteristic curve tables/ channel tables.

The graph area portrays characteristic curves. Display settings are mainly made using the
graph toolbox and the extended graph toolbox. Mouse operations in the graph area take
place according to settings in the graph toolbox. Further details are available in the graph
toolbox.
Graph toolbox
The graph toolbox and the extended graph toolbox provide a range of functions for
graphical analysis.

May 2011
605
Status bar
The status bar shows information about the trend, e.g. current mouse position.
606

May 2011

Der Reiter Kanalauswahl ist im YX-Diagramm (Tabelle) durch den Reiter Tabellenauswahl
ersetzt.
Reiter Tabellenauswahl
Mit dem Button Tabellenauswahl bearbeiten ffnen Sie den Tabellen Auswahldialog .
In der Auswahlbox Tabelle auswhlen whlen Sie eine zuvor angelegte Tabelle.
Nach der Auswahl einer YX-Tabelle sind an dieser Stelle keine Einstellungen mehr mglich.

May 2011
607
Nach der Auswahl einer Tabelle werden links alle Spalten der Tabelle aufgelistet. Whlen Sie
hier die Spalten aus, die im Diagramm verwendet werden sollen.
Hinweis:
Die Spalte 1 der Tabelle ist festgelegt fr den X-Wert der Kennlinien.
Reiter YX-Diagramm
Koordinatenkreuz anzeigen
Logarithmische X-Achse
Logarithmische Y-Achse
2.4.2.2.28.8 YX-diagram (hardware channels)
The YX-diagram (hardware channels) portrays characteristic curves.
608

May 2011


toolbox.
Graph toolbox
graphical analysis.

May 2011
609
Status bar
The status bar shows information about the trend, e.g. current mouse position.
The YX-diagram (table) is used to make settings for different types of graphs/diagrams.
610

May 2011

YX Diagram tab
Show coordinate plane
Logarithmic X-axis
Logarithmic Y-axis
Trigger tab
Refer to the YX diagram description in the analysis section.

May 2011
611
2.4.2.2.28.9 YX-diagram color
2.4.2.2.28.10 FFT diagram
Refer to FFT-diagram (analysis)
612

May 2011
2.4.2.2.28.11 Orbit diagram
The orbit diagram is a YX-diagram for two time signals. It is tailored to the "Non-contact
distance measurement" or "shaft vibration measurement on turbines/compressors"
applications.
The kinetic shaft orbit (shaft center line of movement) is portrayed. Required is a rounded
shaft surface, homogeneous materials and 90 order sensors.

May 2011
613
Refer also to orbit diagram (analysis)
614

May 2011
Orbit settings
Show max Displacement

May 2011
615
2.4.2.2.29 Recorder
The recorder saves measurement data to files. The channels from which measurement data
is to be saved are firstly assigned to the recorder. If the recording function is activated in
runtime mode, then all incoming measurement values from this point in time will be saved to
a measurement data file (*.hds).
Recorder settings
The recorder settings dialog is used to select the channels to be recorded, measurement
data file names and saving options.
Alternatively use the visualisation object's context menu.
The recorder can be linked to one or more trend objects. Refer to linking trends and
recorders.
Recorders can only be used and operated directly within runtime mode.
2.4.2.2.29.1 Recorder properties
These settings can be made to a recorder.

In addition to the tabs explained here are other tabs that are described in the visualisation
Events tab
616

May 2011
Enable events
Events

May 2011
617
Initialisation
Recorder started
Triggered when the recorder has begun to record.
Recorder stopped
Triggered when the recorder has been ended.
Channel selection tab
618

May 2011
Assigned channels
The table shows the measurement channels currently assigned to the recorder. The table
displays the channel name and comments which have been set in the T o pMe ssag e
Configurator.
Choose channels
This button opens the Channel selection window.
The channels assigned to this application are displayed on the left of this window. Any of
these channels can be portrayed using the recorder.
The channels listed on the right are the channels which are currently assigned to the
recorder.
To assign a further channel, select the channel in the list on the left and press Add.
To delete a channel from the recorder, select the channel in the list on the right and
press Delete.
Confirm changes with OK or ignore with Cancel.
The File name tab

Sets the name of the file for the measurement data.

May 2011
619
The file name and the location of saved data files (*.hds) are set here.
The file location is determined by the path entered in the Directory text field. The default
path is a sub-directory of the project folder which has the same name as the recorder. To
change the file location firstly uncheck Default directory. A new directory can be selected
by using Search and the Open file dialogue.
If the path is invalid, ProfiSignal will automatically save the data in the folder
...ProfiSignal/Project/[Name of project]/[name of application].
The file name is made up of the entry in the File name text field and/or an automatic
naming procedure plus the .hds file ending.
The automatic naming procedure follows the options selected under data file name.
620

May 2011
If the options are selected as above the file name would appear as follows:
Messdatei_2011-07-18_001
with the date and consecutive numbering being automatically set.
The following are examples of the file names when selecting different
options:
Filename (placeholder)
Messdatei.hds
File name + consecutive numbering
Messdatei_1.hds
Messdatei_2.hds
Messdatei_3.hds
File name + date + time
Messdatei_24-09-2005_18-18-52.hds
Messdatei_24-09-2005_18-19-32.hds
Messdatei_24-09-2005_18-20-23.hds
file name + Date + consecutive number
Messdatei_24-09-2005_001.hds
Placeholders are also available which provide the user with further possibilities in creating
personalised file names. To use placeholders, select File name only (overwrites data) and
combine text and placeholders in the text field File name. The actual file name will be
displayed under Preview.

May 2011
621
Trigger tab
Recording takes place by the user manually operating a recorder object's controls or by
automated triggering. The Trigger tab sets the parameters for automatic triggering to take
place.
622

May 2011
Manual start and stop only

Recording takes place only by the user operating a recorder object's controls or by a
script instruction.
Allow manual start and stop
Recording can be performed by operating a recorder object's controls as well as
automated triggered recording.
Automated triggering
Activates the trigger settings under Start and Stop when the application is in runtime
mode.
Start section
Time
Recording will begin at the entered start time.

May 2011
623
Start once
Recording starts at the set start time.
Start daily
Recording records every 24 hours from the set start time.
Start repeatedly
The recording restarts if it is stopped at a point in time that follows the start time. This
will continue until the recording is ended by the user operating a recorder object's
controls or by a script instruction.
(Note: measurement data occurring between end and restart times will not be saved. This
interruption in saving measurement data lasts just a few seconds.)
Info:
The Start daily and Start repeatedly options are useful in combination time-dependent
stop. A new file will then be opened at the end of the set measurement duration.
Triggered
Recording will be triggered by a channel status.
624

May 2011
Level trigger High

Recording will start with each rising edge detected within the trigger channel and end
with each trailing edge. The Stop section then becomes active.
Level trigger Low
Recording will start with each trailing edge detected within the trigger channel and
end with each rising edge. The Stop section then becomes active.
Rising edge trigger
Recording will start with a rising edge detected within the trigger channel. Stop
settings must be entered separately.
Trailing edge trigger
Recording will start with a trailing edge detected within the trigger channel. Stop
Trigger channel
Selects the trigger channel.
Trigger value:
A threshold value can be entered here if the trigger channel is analog. Recording will
then begin when this value is exceeded and end when below the threshold value.
Manual
script instruction.

May 2011
625
Stop section
Time related
Sets the duration of the recording.
Measurement period
Sets the duration of the recording in hours, minutes and seconds.
Triggered
626

May 2011
Rising edge trigger

Recording will start with a rising edge detected within the trigger channel .
Recording will start with a trailing edge detected within the trigger channel .
Trigger channel
Trigger value:
Save options tab

Sets specific properties for the recorder object. Changes are not usually required here.

May 2011
627
Saving options section

Optimizes the amount of measurement data to be saved.
628

May 2011
All values
This is the default setting. All measurement data will be saved.
Tolerance in %
A measurement value will be saved only if it differs from the previous saved value by
the percentage given here. The 100% value for a channel is determined by the
TopMessage Configurator and corresponds to the set scaling.
Pretrigger
When checkboxed, additional data for the specified time is recorded prior to the start
of the recording.
Time synchronization
When checkboxed, a dialog will open on clicking Trigger configuration: This dialog
enables settings for amending time synchronization.
Equidistant Storage
A measurement value will be saved after each number of seconds entered here.
Single step via trigger source

Checkboxing this option enables an additional button.

May 2011
629
When a trigger channel is selected, a measurement value will be saved for each
positive edge of the selected channel.
When no trigger channel is selected, manual saving of one measurement value per
channel can be initiated via the
trigger channel is selected.
button. This button may also be used when a
Trend optimization section

Sets the speed of the graph portrayal when the recording is to be displayed within a
trend chart.
Set to slow for slow sample rates and very long time periods.
Set to quick for short sample rates and short time periods.
2.4.2.2.29.2 Using a recorder
Recorders can only be used and operated directly within runtime mode.
Recorder, a recording has not been started
Recorder, recorder started, single step save option
Start /stop recording
630

May 2011
Users can permit/block manual start/stop recording. If a manual start/stop is permitted,

the following buttons are enabled:
Start recording
Starts the recording. A file name is updated (depending on the settings) and a
measurement data file created and opened.
Stop recording
The recording is stopped and the measurement data file closed.
Pause recording
Pauses the recording. The measurement data file's channels are given an interrupted status
but the files remain open.
Single step measurement

If a recording has been started, this button adds one data record (one measurement value
per channel) to the measurement data file. This button appears only when the option single
step via trigger source is enabled.

This button opens the dialog open measurement data file for analysis with the recorder's
directory/folder. A measurement data file can also be opened during recording. The data
recorded is the data that has been displayed up to the opening of the measurement data
file. there is no updating.
Table data file details

File name
File name of the measurement data file currently recording or previously recorded.
State
Recording status

May 2011
Comment
631
Initialisation
Recorder has been started. A measurement data file has

been created and opened but no recording has taken place.
Recording ongoing
The recording is taking place.
Recording paused
The recording has been paused.
Recording stopped
The recording has been stopped and the measurement data

file closed.
Recording stopped

file closed by the recorder.
Time
How long the recording has been running.
Data
The amount of recorded data.
2.4.2.2.29.3 Script language
Initiate
This section describes the specific script functions for the recorder object.
Recording
Starts or ends a recording.
Pause
enables a recording to be paused or continued.
Cancel last recording
Deletes the last recording (measurement data file).
Note: The following functions are available only in extended mode.

Clear channel group
Deletes all selected channels from the recorder's channel list.
Add channel
Adds a channel to the recorder's channel list.
Delete channel
Deletes a channel from the recorder's channel list.
Configuration
632

May 2011
The common menu items for the Assign value, Config Read and Write script functions, and
explained. This section explains only those script functions that apply to the recorder.
During runtime mode, trend settings can be changed using the following script instructions
Config Read and Config Write:
Available in Extended ProfiSignal mode:
Recording
ON
Recording is taking place
OFF
Recording ends
File name

May 2011
633
File name complete
Individual file name
Start trigger channel ID
Stop trigger channel ID
Paused
Pretrigger time
Pretrigger enabled
Precision
File name options

Value
Description
Relevant settings for file name

options
Individual
Individual + consecutive
numbering
Date + time
Date
Individual + date + time
Individual + Date + consecutive

number
Placeholder
634

May 2011
Saving option
Value
Description
Relevant settings for save options
All values
Tolerance
Tolerance
Tolerance
Cycle
Cycle time
Single step
Single step trigger ID
Pretrigger
Pretrigger time
Tolerance
Pretrigger enabled is to ON
Post device-time synchronization
This option should not be configured via

a script
Post device-time synchronization

with pretrigger
This option should not be configured via

a script
Tolerance
Trigger
Trigger channel for single step recording
Directory
Cycle
2.4.2.2.29.4 Post time synchronization
Post device-time synchronization enables the time-stamp to be synchronized for all

channels being recorded.

May 2011
635
Hardware settings
A trigger channel is connected to an external trigger source for each Me ssag e d e v ice (or
each module for the IO-mo d ule s A MDT and A DFT .
The Me ssag e d e v ice 's NTP synchronization must be set as follows (General settings
dialog, tab 1):
All other settings concerning time synchronization are optional.
Please check the devices' firmware. A version from DelOS V2.19a is required.
Settings in ProfiSignal
Application channel selection
In edit mode in selecting channels for an application, trigger channels for the devices/
modules are selected in addition to the recording channels.
Recorder settings dialog

Channels are selected via the Channel selection tab.
'Time synchronization' in the saving options tab must be selected. Clicking Trigger
Configuration opens the Settings - Post Time Synchronization dialog.
Settings - Post time synchronization
636

May 2011
Displays the devices/modules corresponding to the channels selected for the recorder.
The Trigger mode indicates how the start stop signal is to be identified.
Level - Recording takes place for the state ON/HIGH.
High Edge - The start signal is generated by the first high/positive edge, the stop
signal by the next high/positive edge.
Low Edge - The start signal is generated by the first low/negative edge, the stop
signal by the next low/negative edge.
The connected trigger channel must be selected for each module/device. First select the
module and then the trigger channel from the dropdown list. Only the available channels for
the selected module are displayed.

May 2011
637
Recording
The recorder must be started before the start trigger is switched. Measurement data is
recorded only between the start and stop triggers. If the recorder is stopped between the
start and stop triggers, the data will not be synchronized and discarded.
The recorder displays the status of recording:
Recording status
Comment
Initialisation
Recorder has been started. The trigger channels are firstly

checked. If they are all possess an output state, the
recorder is then ready for recording and is on standby for a
start trigger.
Async pause
Recorder has been started, all trigger channels in output

state, no measurement data being recorded.
Async recording
Recording is taking place. A stop trigger is awaited.
638

May 2011
Recording stopped
The recorder has been stopped and the data, which has not
yet been synchronized, is saved to a measurement data
file.
Stopped

file closed by the recorder.
Portraying measurement data in a trend

Current measurement data is displayed directly in a trend in online mode. The time-stamp is
non-synchronized.
If the synchronized data is to be displayed directly during or after a recording, the zoom
needs initializing with the "Show last recording" button. The data source in the status field
will then show as the measurement data file.
Only synchronized data is displayed, i.e. data recorded up to the last stop
trigger.
2.4.2.2.30 Profile
The Profile generates setpoint curves. A setpoint curve can be generated in runtime mode,
e.g. to control an analog output. The Profile can also output setpoints to a dedicated
channel. Profile data can then be displayed using other visualisation objects. This feature is
especially useful to simulate a process during development when a connection is
unavailable to a Me ssag e device.

May 2011
639
The Profile is described in several sections. This section gives a brief overview of the
Profile.
Profile settings
The Profile dialog is opened by double-clicking the object in edit mode or clicking the
Properties menu item in the object's context menu. When the profile object is bordered in
red, it is in the configuration state. This state must be exited before the Profile settings
window can be opened.
The Profile settings window is described in Profile settings.
In edit mode, the profile object can be placed into a standard configuration state.
Standard configuration enables the object to be operated with the mouse and therefore
simulates the runtime mode.
640

May 2011
Profile operation in runtime mode

In runtime mode the Profile's upper and lower buttons can be operated. Grid points are
added or amended by clicking the curve area.
Script
The common menu items for the Config Read and Write script functions, and which are
similar for the majority of the visualisation/parameter objects, have already been explained.
This section explains only those script functions that apply to the Profile object. The menu
is accessed via Config Write or Config Read. A Profile has no script function for Assign
Value.
Other settings (Configuration Write)

VisuView
[name of VisuView]
Profile
[name of profile]
Other settings
Range settings (Configuration Write)

VisuView
[name of VisuView]
Profile
[name of profile]
Range settings
Profile settings (Configuration Write)

VisuView
[name of VisuView]

May 2011
Profile
[name of profile]
Profile settings
641
The points script function enables either the points to be given that are to be displayed
within the profile or to have the points output that are displayed by the profile. Take care
when entering multiple points. The x,y coordinates are each separated by a horizontal line.
Each point is enclosed within brackets.
Visual settings (Configuration Write)

VisuView
[name of VisuView]
Profile
[name of profile]
Visual settings
Point style determines how the points appear. For example, instead of crosses, small or
large dots can be displayed.
Initiate function
Script
Initiate
Visualisation
[VisuView name]
642
Profile
[name of profile]

May 2011
Running a profile displays the current setpoint curve position as a black line. This script
function ensures that the black line jumps to the beginning at a start.
2.4.2.2.30.1 Profile settings

The Profile dialog is opened by double-clicking the object in edit mode or clicking the
properties menu item in the object's context menu. When the profile object is bordered in
red, it is in the configuration state. This state must be exited before the Profile settings
window can be opened. In addition to the profile tab are other tabs that are described in
the visualisation object properties section.
Profile tab
The profile tab enables setting of the report objects specific properties.

May 2011
643
Profile settings
Repeat
This property determines what a Profile does after processing a curve.
644

May 2011
When unchecked, the Profile stops after processing.

When checked, the Profile repeats after processing.
Mirrored
When enabled, the Profile is performed in the reverse direction on reaching the final point.
This option can be combined with Repeat. The repeat is then performed only after the
mirror function has completed.
Interpolation with Splines
How the values between two points are to be computed (interpoled).
When unchecked, neighboring points are connected with a straight line (2nd degree
interpolation).
When checked, neighboring points are connected with a curve (3rd degree interpolation).
Configure points
Opens the table editor to edit the profile's grid points.
A description of the editor is available in the table editor section.
Standard
Sets the profile object's value when the object has been stopped.
Link between profiles
Multiple profiles can be linked to enable synchronization. When a profile is linked with
another profile, it cannot be directly started by the user. The profile instead starts
automatically when the master profile is started. When the master profile is stopped, the
linked profile also stops.
Master profile:
Selects the master profile. When a profile is selected here, the profile object can no
longer be directly started by the user.
Master of:
Lists all the profiles that can be controlled by the master profile.
Scale Settings

May 2011
645
Y Upper Range:
Upper limit of the Y-axes scale.
Y Lower Range:
Lower limit of the Y-axes scale.
T Upper Range (numeric field and dropdown list)
Maximum value for the time-axis scale according to the selected unit of time.
T Lower Range (numeric field and dropdown list)
Lower limit for the time-axis scale according to the selected unit of time
View
Color lines
Opens a color dialog for selecting the curve's color.
Color points
Opens a color dialog for selecting the profile's point color.
Line Width
The line width in pixels.
Point Style
To select a symbol for how points are displayed in the curve.
Events tab
Enable events
646

May 2011

Event descriptions
Initialisation
Left click
Right click
Value change
status.
Channel section
Channel:

May 2011
647

Show channel:
Set channel:

Tab order section
Tab order
2.4.2.2.30.2 Table editor

The table editor enables settings of the grid points for a setpoint curve. Settings are also
made here on how the profile functions in runtime mode.
648

May 2011
Table editor settings

Profile table
This table lists all the grid points for the setpoint curve of a profile. A table item has two
entries: Time and Value(the coordinates for the profile grid points). The grid points can be
edited within the table.
Row Count
The number of grid points and therefore the number of rows in the table.
Time
Absolute selects the absolute time, following the profile start, as the grid point Time. In

May 2011
649
the table above, the setpoint value for #5 is then reached after 40 seconds.
Relative selects as the grid point Time, the relative time from when the previous
setpoint value was reached. In the table above, the setpoint value for #5 is then
reached after 100 seconds (0+10+20+30+40).
Scale
Scale indicates the unit of time for the Time column (milliseconds ms, seconds s, minutes
min or hours h).
Export
Opens a save-file dialog to enable the setpoint curve to be saved to a file.
Import
Opens a save-file dialog to enable the setpoint curve to be imported from a file.
Repeat
This property determines what a Profile does after processing a curve.
When unchecked, the Profile stops after processing.
When checked, the Profile repeats after processing.
Mirrored
When enabled, the Profile is performed in the reverse direction on reaching the final point.
This option can be combined with Repeat. The repeat is then performed only after the
mirror function has completed.
Spline interpolation
How the values between two points are to be computed (interpoled).
When unchecked, neighboring points are connected with a straight line (2nd degree
interpolation).
When checked, neighboring points are connected with a curve (3rd degree interpolation).
Default Value
Sets the profile object's value when the object has been stopped.
2.4.2.2.30.3 Standard configuration

In edit mode, the profile object can be placed into a state of standard configuration.
Standard configuration enables the object to be operated with the mouse and therefore
simulates the runtime mode. Standard configuration is accessed by right-clicking the
profile object and selecting configuration of standard from the context menu.
650

May 2011
The table is displayed with a red border to indicate that it is in a state of standard
configuration.
The setting options available for profiles are explained separately. These settings can also
be amended in runtime mode.
Standard configuration edit mode

The following menu items are available in standard configuration. The menu is displayed by
right-clicking the profile object.

May 2011
651
Delete point
Deletes the point that has been marked using the mouse (the marked point is displayed
as a point instead of a cross).
Delete all points
Deletes all points.
Enter point in table
This opens the table editor. This enables the editing of the points in a curve. A
description of the editor is available in the table editor section.
save changes
Exits standard configuration and saves any changes made.
abort changes
Exits standard configuration and ignores any changes made.
2.4.2.2.30.4 Profile runtime mode

Operating the profile takes place in runtime and/or edit mode.
The profile is operated with buttons in the upper and lower sections of the object.
Grid points are added or amended by clicking the curve area.
Upper button functions
652

May 2011
Starts the setpoint curve. Available only in runtime mode and is hidden while the profile is
running. When running, the current position is marked as a black line in the setpoint
curve.
Pauses the setpoint curve. Running of the profile continues from this point using the start
button. Available only in runtime mode and is shown only while the profile is running.
Ends the setpoint curve. Available only in runtime mode and is shown while the profile is
running.
The setting options available for profiles are explained separately.
2.4.2.2.30.5 Operating a profile
Mouse position input
Positioning the mouse cursor in the graph area of the profile displays the X and Y
coordinates in the lower box (circled red in the above image).
Amending grid points using the mouse

Adding grid points

May 2011
653
Grid points for the setpoint curve can be added in standard configuration or runtime mode.
Left-click a point in the profile where a grid point is to be added.
Moving an existing grid point
Existing grid points can be moved using the mouse in standard configuration or runtime
mode. Click on the grid point to be moved. The marked grid point changes from a cross to
a point. Left-click and move the grid point.
Alternatively, use the table editor to move an existing grid point. To open the table editor,
right-click the profile. This opens a context menu . Click the item "Change points in table".
The table editor enables X- (time) and Y-(value) coordinates to be changed. Time (Xcoordinates) may not be arbitrarily changed. They must be higher than the table's
preceding times and lower than the table's succeeding times.
654

May 2011
Deleting existing grid points

Right-click the grid point to be deleted. Select "Remove point" from the menu displayed.
This deletes a single grid point. Select "Remove all points" to delete all the grid points in a
profile.
The following menu items are available in standard configuration or runtime mode . The
menu is displayed by right-clicking the profile object.
Delete point
Deletes the point that has been marked using the mouse (the marked point is displayed
as a point instead of a cross).
Delete all points
Deletes all points.
Enter point in table
This opens the table editor. This enables the editing of the points in a curve. A
description of the editor is available in the table editor section.
Lower button functions

In standard configuration or runtime mode the following symbols (located in the lower part
of the window) are available to change the displayed scale.
Moves the setpoint curve's display area.
Automatically rescales to display all grid points.
Extends (zooms out) the setpoint curve's display area.
Compresses (zooms in) the setpoint curve's display area.

May 2011
655
2.4.2.2.31 YX-table
The YX-table has been developed to facilitate use of the YX-diagram (table). It is similar to
the table object, apart from specific functions for YX-diagrams. A full explanation of the
table is therefore unnecessary.
This section explains only the differences between YX-tables and regular tables. Also
explained here are the effects amendments to a YX-table have on a YX-diagram (table).
Differences in the title properties dialogs

To open these dialogs, switch to standard configuration for YX-tables. Select title
properties. This dialog differs to the regular table title properties by having the area
Settings for YX diagram.
656

May 2011

May 2011
657
Title
Sets the column title. When this YX-table is assigned to a YX-diagram (table), the column
title appears as a channel name in the diagram.
Settings for YX diagram
Y-axis
A choice of 4 y-axes can be selected from the dropdown list. The channel will be displayed
on the y-axes of the diagram to which the table is assigned. In the above example,
Channel 2 will be portrayed on the Y-axis.
Unit
Unit enables allocations to be made to a channel (e.g. Unit).
Color
Opens a color dialog for selecting the diagram's channel color.
Visible
Hides/shows the channel in the diagram.
658

May 2011
Channel selection for a YX-diagram (table)

Open a table-selection dialog via the YX-diagram (table) settings dialog / Choose table
tab/ edit chosen table. Select a table that has been previously set up.
Once a YX-table has been selected, further settings are not possible here. Settings are
then only possible via the YX-table's title properties dialog.
The table button in the table selection dialog enables the display of individual columns from
the YX-diagram (table). Channels or columns that are to be displayed in the diagram are
moved from the right to the left sides of the table using the mouse or the Add button.
Portraying a YX-table in a YX diagram (trend)

By assigning a YX-table to a YX-diagram, automatically sets the YX-diagram's X-axis to
the table's first column.

May 2011
659
The other table columns are portrayed in the YX-diagram as channels only when they have
been assigned column names.
660

May 2011
Script
YX-tables differ only to other tables in the script functions Config Write / Read. These
functions then include the menu item: Configuration table.
Configuration table (Configuration Write)

VisuView
[name of VisuView]

May 2011
YX-table
[name of YX-table]
661
The configuration table enables cells to be written to or read from.
2.4.2.2.32 Turntable
The turntable can show three values simultaneously. Upper and lower limits are indicated as
marked-off areas, with the current value indicated by an arrow.
Turntable settings
Open the settings dialog by double-clicking the object in edit mode. Alternatively use the
visualisation object's context menu (Properties option). In addition to the turntable tab
are other tabs that are described in the visualisation object properties section.
662

May 2011
Turntable tab
Color section
Arrow - Color
Opens a color dialog to set the arrow color.

May 2011
663
Scale - Color
Sets the turntable's background color.
Steps Color
Sets the color for the scale.
Color Min / Max Sector
Sets the displayed color below the minimum-settings and above the maximum-setting.
Display
Lower Bound
The minimum value to be displayed. When the value to be displayed is lower than the
Lower Bound, the arrow will point to the Lower Bound (i.e. 10 in the example). The scale
begins from the Lower Bound.
Upper Bound
Upper Bound is the highest value to be displayed. When the value to be displayed is
greater than the Upper Bound, the arrow will point to the Upper Bound (i.e. 100 in the
example). The scale ends at the Upper Bound.
Scale Position
Sets where the scale is displayed. On either the left or the right. The scale is then
positioned either on the left or the right of the turntable.
Show Min / Max Values
Shows the turntable's Upper and Lower limits/bounds as colored areas. These Lower and
Upper Bounds are different to the Lower and Upper Bound settings for scale settings.
Font
Opens a dialog to select the font, color and size of the scale numbers.
Do not Show Leading Sign
Omits the minus signs for negative number scales.
Step settings
664

May 2011
Steps
The steps on the scale that are numbered.
Sub Steps
The number of steps between each numbered step.
Events tab
Events section
Enable events
Event descriptions
Initialisation
Left click

May 2011
665

Right click
Double click
Value change
status.
Upper limit
or Off status.
Lower limit
or Off status.
Channel tab
Channel section
Three channels can be entered for a turntable. The first channel delivers the value to
which the turntable's arrow points. The other two channels deliver values for the colored
areas marking the Upper and Lower areas.
666

May 2011
Only channels are available that can also be set and displayed by the visualisation/
parameter object, i.e. those that have been assigned by the user to the object via channel
selection.
The turntable only displays the channels; there are no write functions.
When channels are used to obtain values, these values can no longer be set
within a script. A script will allow value setting instructions, but these will have
no effect on the value.
Script
Turntable settings (Configuration Write)

VisuView
[name of VisuView]

May 2011
Turntable
[name of turntable]
Turntable settings
667
2.4.2.2.33 Alarm list
The alarm list visualizes alarms.
668

May 2011
In edit mode the alarm list displays four dummy-alarms, each showing a different state.
This enables a preview of color combinations when selecting alarm colors. Columns contain
data. Column widths can be set.
Local filters, located in the alarm list's toolbar, has pre-set priorities and states. For current
alarms to occur when switching to runtime mode requires thatthe classes are selected in
the settings dialog, whose alarms may then be displayed.
Alarm states
The following example explains the different states an alarm can take.
Alarms can take an Active state. This means that the alarm's conditions have been met.
For example, a threshold value has been exceeded. An alarm can also take a Gone state.
This means the alarm's conditions were met, but are no longer being met. For example, a
threshold value was exceeded but the value is currently under the threshold. An alarm can
also take a Error state. This means that an action to be performed has caused an error,
e.g. an email was unable to be sent successfully. An alarm can also take a Interrupted
state. This means an imminent alarm was interrupted, e.g. a rule was changed while the
alarm was still active.
When setting up alarms in the DataService users can use alarm classes to set whether the
alarm class requires confirmation. A confirmed alarm can take the states: Active/Confirmed,
Gone/Confirmed, Interrupted/Confirmed or Error/Confirmed.
Confirmed (menu item)
Confirming alarms
Only those alarms can be confirmed that have been given the appropriate settings in the
DataService. Right-clicking an alarm displays a menu with Confirm as an item. If the alarm is
non-confirmable, the menu item appears grayed-out. Clicking "Confirm" opens a dialog to
enter the confirmation text that can be confirmed with OK. Multiple alarms can be
confirmed simultaneously by marking the alarms to be confirmed and then following the
above procedures. A dialog then appears prompting the user to confirm that multiple alarms
are intended - the same confirmation text is assigned to all alarms. If one alarm among the
multiple alarms is non-confirmable, the Confirm menu item will be grayed-out.
Horn confirmation

May 2011
669
Right-clicking the alarm list's table displays a 'confirm horn' menu item. This enables the
horn to be confirmed in the event of a hidden toolbar. The time-point at which the horn
becomes active, and how the wave file is entered, is described below.
Alarm table layout

The information that makes up an alarm is spread over eleven columns. Users decide on the
columns to be shown (Selecting columns). The non-selected columns are then hidden. The
columns concern the following:
Alarm Time
The time that the alarm occurred. The alarm time includes date and time.
Alarm Gone Time
The time at which the alarm switched from active to gone states. This means that the
alarm conditions are no longer being fulfilled.
Priority
Determines the alarm ranking.
Alarm Classes
Displays the classes to which the alarm is assigned.
Alarm Text
Explanatory Text that has been previously set within the DataService.
Alarm Source
Channel name and source of alarm.
State
An alarm can take the following states: Active, Gone, Interrupted, Error, Active/
Confirmed, Gone/Confirmed, Interrupted/Confirmed and Error/Confirmed.
Confirmation required
An X indicates that the alarm requires confirmation.
Confirmation time
The time that the alarm was confirmed.
Confirmation user
The user who confirmed the alarm.
Confirmation reason
Reason for the confirmation
Event file
The name of the event file that has been generated by the alarm.
Settings dialog
670

May 2011
The settings dialog has eight tabs. The General, Style, Events and Reference tabs are
identical for all visualisation objects.
The View tab enables the table to be amended according to user requirements. Possible
amendments include color, font,headings, widths and the columns to be displayed.
The Alarms tab concerns the alarms themselves: e.g. which alarms from which classes; the
minimum priorities that the alarms should possess etc.
The Analysis tab enables settings for fault diagnostics, e.g. assigning a trend to an alarm.
The Toolbar tab concerns the settings that can be made in the toolbar.
Alarm list toolbar
The toolbar enables local settings to be to display the required alarms. The toolbar is
available only in standard configuration and runtime mode. Options are available to filter out
alarms. The toolbar also enables viewing of either current or historical alarms. Current
alarms can also be cleaned (more to follow). Settings may be saved/loaded. The Properties
button enables the alarm list's appearance to be changed during runtime mode. The alarm
table can also be exported as a CSV file. It is also possible to halt alarms.
Filter

May 2011
671
This filter enables specific alarms to be omitted from the alarm list. Various selection criteria
are available. To be displayed in the list an alarm must have a specific priority, state, or
alarm class. The filter is set using the settings dialog. Pre-settings are: all priorities; all
states; no alarm classes. This must be selected in the settings dialog in order for them to
displayed in the filter.
Priority enables all or only specific alarm priorities to be displayed.
State enables one of four states to be selected. A state with all priorities can be selected
or just a single priority.
Alarm classes enables single or multiple classes and their alarms to be displayed.
Buttons for historical alarms, current alarms and clean-up
The system is pre-set to display all current alarms.
Historical alarms can be displayed by clicking the button and entering the required start
and end times for the required alarms. Confirm with OK. The same applies for Current
alarms. If "Automatic change from the historical to the current alarms" has been enabled in
the settings dialog, the mode may change when switching to historical alarms. Current
alarms may also undergo a clean-up. This means that all alarms are deleted from the list
that are either non-confirmable or have been confirmed.
Exporting alarms
The alarm list can be converted to a CSV file so that alarms can be viewed, for example,
using Excel. The file contains all the existing columns within the alarm list. Each alarm is
listed with its associated column information.
672

May 2011
Horn button
The horn appears when an alarm sounds. Click the horn to stop it sounding. The signal
restarts with a new alarm.
Properties button
Opens the settings dialog to enable changes to be made during runtime mode. The settings
that can be changed are: alarm color selections; and the hiding/showing of columns.
The buttons Configuration Load and Save, Standard

The option is available to save configurations of settings and to load these when switching
again into runtime mode. The following can be saved:
Alarm list columns
Which columns are to be displayed. The sequence, size and sorting of the columns.
Alarm colors
The colors the alarms are to take.
Filter settings
Settings for priority, state and alarm class.
Standard enables the configuration to be loaded before switching to runtime mode.
In edit mode, right-click the alarm list to display the menu item Configuration of standard.
Amendments similar to runtime mode amendments can be made to the alarm list. The
amendments are saved by right-clicking the alarm list and selecting commit changes.
Script
Initiate
Script
Initiate
Visualisation

May 2011
[VisuView name]
Alarm list
[name of alarm list]
673
674

May 2011
2.4.2.2.33.1 View tab
Columns and Color refer to the portrayal of alarms. Within the alarm list's toolbar area,
individual buttons,or even the entire toolbar, can be hidden/shown. The Sound Playback
section enables settings to be made for the horn.
Columns

May 2011
675
The table list all the columns available to the alarm list. 'Visible' indicates the columns to be
displayed in the alarm list. 'Caption Column' enables changes to be made to the column
headings in the alarm list. The 'Default' button returns column headings to their original
settings.
Color
To select the colors for the different alarm types and whether the alarm is to portrayed as
blinking. An alarm blinks in two different colors (color and blinking color). 'Active, Required
Confirmation', 'Active Alarm', and 'Gone, Required Confirmation' can be portrayed as blinking.
The 'Blinking' checkbox then requires checking. When checked, a color option appears on
the right.
View
676

May 2011
To select the colors for the alarm list: background color for column titles; background color
for the alarm list; grid color (red in the example below). Table and heading fonts can also
be changed. Click the corresponding button to open a font dialog. The alarm list can then
appear as in the following example:

May 2011
677
2.4.2.2.33.2 Alarms tab
'Alarm classes' and 'Priority' determine what alarms are required. Users can then display in
runtime mode only those alarms with the priority and class settings made here.
Alarm Classes
678

May 2011
Select (left click) an alarm class to include it in the alarm list filter.
New alarms set in the DataService are then displayed here.
If an alarm class is deleted and then selected it will be marked here as unknown along with
the subsequent class names. If it has not been selected, the deleted class will be omitted
from the list.
Priority
Select the priority of the alarms to be displayed.

Priorities from 1 to 9 can be given. All displays alarms with any priority. Selecting a number
displays alarms with the same or lower priority number. For example, selecting a priority of
4 displays alarms with the priorities 1, 2, 3 or 4.
Priority numbers up to the selected number are included in the alarm list filter.
Authentication
Is relevant when password protection has been enabled in ProfiSignal and DataService.
When 'Authentication necessary" is checkboxed, alarms can be confirmed only when the
user has the appropriate rights. A password dialog will therefore appear prior to the
confirmation dialog. The user must enter a valid name and password to be able to confirm
the alarm.
Automatic Change form the Historic to the Current alarms

May 2011
679
Displays historic alarms within the given time period. This option automatically re-displays
the current alarms. The automatic change from historic to current alarms can be
triggered by two events. These events can be selected separately or in combination.
One event concerns the exceeding of the given time.
The other concerns activation of a new alarm. In this event, all three toolbar filters
(priority, state, and class) are set to the values made in edit mode prior to switching to
runtime mode.
2.4.2.2.33.3 Analysis tab
This tab enables alarm channels to be easily displayed in trends. This feature is also known
as fault diagnostics. This section describes the part of a trend that is necessary for fault
diagnostics. For a better understanding, refer also to the basics in trends.
Show alarm in trend
680

May 2011
This tables assigns a trend and a time to the alarm. This section first describes the reasons
for these entries and the effect they have. The settings are then explained afterwards.
Dedicated trend
The trend here appears in a pop-up as follows. During runtime mode, the alarms are
displayed in the alarm list/table. Right-clicking an alarm opens the following menu. Show in
diagram lists the trends that have been assigned to this alarm class. In this example, the
alarm has two classes: Class 3 and Class 4. Two trends can therefore be selected. In this
example, Yt-Diagram_2 is assigned to Class 3 and Yt-Diagram_3 to Class 4.
Clicking a trend in the list displays the VisuView for that trend. This displays the alarm's
state. In this example, the alarm was triggered at 10:51:17,774, stopped at 10:51:32,633,
and confirmed at 10:51:40,028. Also displayed is the name of the DataService rule.

May 2011
681
Time range
Each alarm class can be given a time range. This refers to the time that is to be displayed
in the trend pre and post alarm.
Alarm state
Given time
range
Time range displayed in trend
Active
Fixed time range
Time range: the time the alarm triggers minus the

selected time range. Following the alarm, the trend will
be displayed at the current time. This means the trend
zooms to the entire time range: the time the alarm
triggers minus the selected time range through to the
current time.
Gone
Fixed time range
Time range: the time the alarm triggers through to the

gone time, plus the selected time range, before and
after.
Active
15 % of the time
range
15% of the time range: the time the alarm triggers

through to the current time.
Gone
15 % of the time
range
15% of the time range: time the alarm triggers through

to time of alarm deactivation.
The above example uses a time range of 15 seconds. This means that 15 seconds are
displayed prior to the alarm triggering, and 15 seconds following the gone state.
Entering data into the table
682

May 2011
The above describes the functioning and assigning of trends and time ranges. This section
deals briefly with the setting of parameters. The classes listed as alarm classes in the alarm
list are automatically added/deleted. Selecting alarm classes under the 'Alarms' tab/ alarm
classes adds the selected class to the table. If a class is disabled in the 'Alarms' tab, the
class is then deleted from the table. Right-clicking a trend lists all the trends being used by
the application. The same applies to 'Time domain'. The default setting is 15%. The
dropdown box lists time ranges between 5 seconds, 15 seconds, 1 minute, 5 minutes, 15
minutes and 1 hour.
Automatic display
If the alarm channel has a 'hidden' trend setting, the setting can be overidden here and the
trend displayed.
Limit trend choice
The table lists all trends that have been assigned to alarm classes. This occurs whether or
not the trend contains a channel from the alarm. If checkboxed here only those trends are
displayed that use the alarm's channel.

May 2011
683
2.4.2.2.33.4 Toolbar tab
Toolbar
The alarm list can be set to display only the list without the toolbar. Only when the Toolbar
is visible can specific buttons be hidden: Either the Properties and/or Configuration buttons
(to load and save configurations).
Sound Playback
To select a *.wav file that is played when a horn-alarm is to sound. For a New Alarm Play
Sound File must also be enabled. This possible only when a *.wav file has already been
selected.
CSV Settings
684

May 2011
The toolbar contains an export-file button

to export alarms as CSV files (comma
separated values). The saved CSV files can be opened using programs such as Microsoft
Excel.
CSV Delimiter (Text field)
The delimiter to be used to separate the CSV records.
Always use quotes
When enabled, all data records between delimiters is placed within quotes.
. When disabled, quotes are used only for empty data records or data records that
contain only a delimiter
.
2.4.2.2.33.5 Fault diagnostics
The fault diagnostics object enables the channel of an incoming alarm to be quickly and
simply displayed as a trend object. Clicking an alarm in the alarm list displays a menu from
which a trend can be selected. The trend then opens in the foreground and displays the
alarm's channel at the point of activation. This enables the alarm's channel to be quickly
displayed and responded to.
To use fault diagnostics requires settings to be made in the alarm list. These settings are
explained in the alarm list object.
Appearance of alarms in the alarm table
The example shows four alarms in the alarm list. Two alarms are active, one is in a 'gone'
state, and one is 'gone' and confirmed. Right click an alarm to display the menu with Show
in diagram. The trends are listed that can be displayed. The examples list the
Trend_Class1 object.

May 2011
685
Showing an alarm in a trend

Clicking (in this example) Trend_Class1 opens in the foreground the trend object.
The alarm's channel is then displayed within the trend. The times at which the trend was
triggered, stopped, and confirmed are portrayed in different colors. The red line shows: the
time that the active alarm was triggered; the green line shows: the time the alarm entered
the gone state; and the blue line shows: when the alarm was confirmed. The lines of the
graph also contain additional information: The name of the rule that triggered the alarm;
the time points; the alarm state; and confirmation text, for those alarms requiring
confirmation.
The trend shows a threshold line (in the example, as a broken red line). The user sets the
over-run/under-run threshold that triggers the alarm. In the example, the threshold was
over-run at 15:18:54 hours and went under-run again at 15:19:08.
The time range displayed in the trend, as well as the channel's trend, can be set in the
alarm list settings dialog.
686

May 2011
2.4.2.2.33.6 Acquisition of fault data
Setting alarms in the DataService enables the display of the event files that are generated
when an alarm occurs. An event file, like a measurement data file, shows one or more
channels for a set time range. It differs from a measurement data file in that it contains a
time range that spans the pre and post periods of the alarm. The relevant settings are
made by the user in the DataService.
Event file menu item

To display an event file for an alarm, right click the alarm to open a menu with the item
Show event file. Right-clicking the item displays the event file in a separate window as a
Yt-diagram.
The menu item is available only when the alarm has been assigned an event file. The Event
file column in the alarm list indicates whether an event file has been assigned to the alarm.
Analysis window displaying event file

Opens an analysis window with the event file that was generated by the alarm. The name
of the event file is displayed in the window header.

May 2011
687
2.4.2.2.34 ODBC visualisation object
Enables the linking of databases via a standardized ODBC interface. The following three
ODBC objects are available:
ODBC connection
ODBC table
ODBC SQL
Setting up databases in Microsoft Windows

Use the ODBC Data Source Administrator to convert your database into an ODBC database
that can be used in ProfiSignal.
Click Control Panel and Additional Options. Click Data Sources (ODBC). This opens the ODBC
Data Source Administrator.
688

May 2011
Click Add to create your ODBC database.
Select the required driver from the list displayed. The example creates a database with
Microsoft Access and selects the Microsoft Access driver. The click Finish.

May 2011
689
Enter the name of your ODBC database in Data Source Name. Click Select to select your
database. Confirm input with OK. The created database now appears under the ODBC name
in ODBC connection.
2.4.2.2.34.1 ODBC connection
The ODBC connection object creates a database connection via ODBC.

the ODBC connection tab are other tabs that are described in the visualisation object
properties section.
ODBC connection tab

Sets up a connection to a database.
690

May 2011
ODBC Name
Selects the database to be connected. To list your database under ODBC Name requires
you to perform an ODBC database conversion in Microsoft Windows. The example selects
the TestDatenbank database.
Login settings

May 2011
691
If the database has access right, User Name and Password enables the input to be made
that is required to access the database selected under ODBC Name.
Check connection
Left click Start to test the connection to the database selected under ODBC Name. The
window below Start displays the connection protocol, with an error message for a failed
connection. The error message is generated by the operating system and not by
ProfiSignal.
An error message that occurs frequently is as follows:
The ODBC connection object requires the universal interface Borland Database Engine
(abbreviated to BDE) to access a database. The BDE can be installed from the ProfiSignal
CD.
Script
Assign Value
VisuView
[name of VisuView]
ODBC connection
[name of ODBC connection]
Connection
settings
Assign Value: Visualisation\VisuView_1\ODBC.ODBC connection_1.Connection

settings.Active = on
692

May 2011
The ODBC connection must be active to access the database in runtime mode.
Connection settings (Configuration Read)
VisuView
[name of VisuView]
ODBC connection
[name of ODBC connection]
Connection
settings
The Last error script function displays the last error that occurred.
Initiate function
Script
Initiate
Visualisation

May 2011
[VisuView name]
ODBC connection
[ODBC connection name]
693
2.4.2.2.34.2 ODBC table
The ODBC table object enables database tables to be read and written.
Label settings
the ODBC table are other tabs that are described in the visualisation object properties
section.
ODBC Table tab

Sets up a connection to a database table.
694

May 2011
Available ODBC connections area
For mark one of the available ODBC connections that is to be used for accessing. All ODBC
connections in the application are listed.
Table Name
To input the name of table to be read. The example uses a database named TestDatenbank
and a table named FruitStorage.

May 2011
695
Check connection
Check connection tests the connection to a table when left clicking the start button. The
connection protocol is displayed in the window. A failed connection will display an error
message. The error message is generated by the operating system. The error message is
not generated by ProfiSignal.
Note:
As the name suggests, this concerns a connection test. The input table cannot always be
listed, as in the example below, even though the user has input everything correctly.
Script

VisuView
[name of VisuView]
ODBC Table
696
[name of ODBC table]
Connection settings

May 2011
The marked name also represents the name of the ODBC-connection.
Config Read
VisuView
[name of VisuView]
ODBC Table
[name of ODBC table]
The column name script function returns the column heading for the given column number.
The table's separate values can be displayed using the script instructions below. Users can
select the data type for a cell's value. An example is used here to clarify the script function.
It deals with the article table that was used already at the beginning.
The example below uses the Field as double script function. Ensure the ODBC connection is
enabled beforehand otherwise no data will be received.
The application variable LVVariable1 will be set to the value of 3.4. The first value in the
price column.
Initiate function
Script
Initiate
Visualisation

May 2011
[VisuView name]
ODBC table
[ODBC table name]
697
The script function update table renews the table. Users can rename a table using Change
table name .
The First record, script function positions the pointer at the table's first record.
Information can then be obtained from the first record's columns. The Next record, script
function positions the pointer at the table's next record. The following example shows a
function that processes all the data for a column.
2.4.2.2.34.3 ODBC SQL
The ODBC SQL object enables access to an SQL database.
Label settings
the ODBC tab are other tabs that are described in the visualisation object properties
section.
ODBC SQL Query tab

Enables a database query to be performed.
698

May 2011
Available ODBC connections area
For mark one of the available ODBC connections that is to be used for accessing. All ODBC
connections in the application are listed.
SQL Query

May 2011
699
Enter the SQL instruction concerning the query.
Check connection
Left-click Start to test the connection to the database selected under ODBC Name. The
window displays the connection protocol and/or SQL query.
Script

VisuView
[name of VisuView]
ODBC SQL
[name of ODBC SQL]
Connection settings
700

May 2011
The marked name also represents the name of the ODBC-connection.
Config Read
VisuView
[name of VisuView]
ODBC SQL
[name of ODBC SQL]
The column name script function returns the column heading for the given column number.
The table's separate values can be displayed using the script instructions below. Users can
select the data type for a cell's value. An example is used here to clarify the script function.
It deals with the article table that was used already at the beginning.
The example below uses the Field as double script function. Ensure the ODBC connection is
enabled beforehand otherwise no data will be received.
The SQL query in the above example was: SELECT Artikelname, Einzelpreis FROM Artikel
WHERE ArtikelNr < 4. The variable LVVariable_4 has a value here of 0.5.

May 2011
701
Initiate function
Script
Initiate
Visualisation
[VisuView name]
ODBC SQL
[ODBC SQL name]
update SQL Query renews the SQL query.
'execute SQL Query' starts a new SQL query.

The First record, script function positions the pointer at the table's first record.
Information can then be obtained from the first record's columns. The Next record, script
function positions the pointer at the table's next record. The following example shows a
function that processes all the data for a column.
Only the table rows are used that are given in the SQL instruction.
2.4.2.3 ParameterView
ParameterViews and VisuViews are required to configure the user interface.
A ParameterView is a special type of VisuView and enables the input and management of
parameter sets and/or recipes.
ParameterViews use only those visualisation objects that are suitable for parameter input.
Visualisation objects for ParameterViews are referred to as parameter objects.
702

May 2011
Differences between ParameterViews and VisuViews

An application may have only one ParameterView. The view may have several tabs
(pages).
Only certain objects (parameter objects) can be added.
ParameterViews can save input to a file. the file can then be used to reload previous
input. use the buttons Save and Load,. These buttons are available as default in
ParameterViews and can also be used in runtime mode.
ParameterViews enable the management of recipes for industrial processes and/or
parameter sets for test bench applications.
Cancel and OK are used for validity tests. Validity tests check the parameter object data
before making it available to the application. Validity tests are explained in the validity
check section.
Various parameter objects are available that are identical (except for recipe values) to
visualisation objects.
The following tools appear in ProfiSignal after opening (clicking) a ParameterView.
Creating a ParameterView
In Global settings/project options (ProfiSignal main menu/Settings) checkbox
ParameterView to automatically create a ParameterView each time a new application is
created.

May 2011
703
A ParameterView can also be added later to an application. However, this is possible only
when the application has no ParameterView assigned to it an application may have only
one ParameterView. To add a ParameterView to an application, right-click the application in
the management tree and select the Create ParameterView item from the context menu.
To delete a ParameterView
Right-click the ParameterView in the management tree and select Delete.
2.4.2.3.1 ParameterView context menu
The following context menu opens by right-clicking a ParameterView's page. If a parameter

object is active, the parameter-object context menu opens.
704

May 2011
Menu item
Description
Paste
Enabled only when a parameter object has been copied to the

clipboard. Inserts the clipboard contents onto the
ParameterView's page.
New Page
Adds a page to the ParameterView
Delete Page
Deletes the current ParameterView page
Rename Page
Renames the current ParameterView page.
Page move left
Enabled only when the current ParameterView page is not the

first tab of the ParameterView. The page is then moved one
position to the left.
Page move right
Enabled only when the current ParameterView page is not the

last tab of the ParameterView. The page is then moved one
position to the right.
Page settings
Opens a dialog showing the ParameterView page properties.
ParameterView
Settings
Opens a dialog showing the ParameterView's properties.
Search
Refer to Context sensitive searches
2.4.2.3.2 Page settings

In edit mode, the settings window is opened via the Page Settings item of the
ParameterView's context menu. Settings can be made here on how the ParameterView
looks and operates during runtime.

May 2011
705
Background tab
Grid
For setting the background gridlines. Grids are displayed only in edit mode to aid the
positioning of parameter objects. The grid is always hidden in runtime mode.
Enabled
Displays gridlines.
Snap to grid
When this option is checked, parameter objects are positioned only on gridlines. Changing
the visualisation object size also takes place according to the gridlines.
dX: and dY:
Color section
706

May 2011
Background
Opens a color palette to select the background color of the ParameterView.
Grid
Background picture
A graphics file can be used as a background image for the ParameterView. This section sets
how the graphic file is to be displayed.
Enable
Uses Filename: as the ParameterView's background.
Centered
Displays the image file in middle of the ParameterView's background.
Scaled
Displays the image file to the ParameterView's scale.
Keep original proportion
Displays the image file to the ParameterView's scale without distorting the image.
Filename:
The button opens a file selection dialog to select the image file. The file path can be
entered directly into the text field.
General tab
Visibility
Visible
Indicates whether the ParameterView can be displayed once runtime mode starts. When
the ParameterView is hidden (i.e. not visible), it can be displayed by double-clicking its
entry in the management tree.
This is possible also via the change screen event (Button object).

May 2011
707
2.4.2.3.3 Script instructions
Object functions are available to open and close ParameterViews and to load and save
parameters. The object functions are explained under script instructions.***
Script
Initiate Input Parameter
Users can themselves read values or assign new values to a VisuView or ParameterView.
This occurs via Assign Value.
Assign Value: Parameter\Page_1.RadioB.Radiobutton_1. Recip e Value = Object

Buttons in the ParameterView
Differences exist between the script instructions used to open ParameterViews. Either the
buttons OK and Cancel or Close are displayed depending on how the ParameterView is
opened. When and which button is displayed is explained in each script instruction
description.
Value and recipe value

Two values are recorded for each parameter object in runtime mode. The current
parameter value and the ParameterView Recipe Value. A radio button example is used to
explain this.
708

May 2011
The radio button object is added to a ParameterView. Add three items (Value One, Value
Two, Value Three) via the button's settings dialog. The default index is set to Value 1.
Two data sets exist: Value and Recipe Value, , with Value being the data set that is
displayed by the parameter object.
The default index in the radio button's settings dialog is assigned the entry "Value One".The
entry is given a value of 1. (Value: 1 Recipe Value: 1)
Open the ParameterView with either the script instructions Load parameter without file,
Open ParameterView or double-clicking the ParameterView in the management tree.
Change the "Value One" to "Value Two" (Value: 2 Recipe Value: 1) Value changes to 2.
The Load parameter without file displays the ParameterView with the OK and Cancel
buttons. Clicking OK accepts the Recipe Value as the contents from Value (Value: 2
Recipe Value: 2) Clicking Cancel leaves Recipe Value unchanged (Value: 2 Recipe Value:
1)
The script instruction Open ParameterView displays the ParameterView with a 'Close'
button. The ParameterView cannot be confirmed with OK. The 'Close' button functions like
'Cancel' and the Recipe Value remains unchanged (Value: 2 Recipe Value: 1)
Opening the ParameterView other than with the script instruction Load parameter from
file, sets Value to the contents of Recipe Value. If this value is 1, this is the value that is
set (Value: 1 RecipeValue1).
Loading a recipe file (*.pmt) into a ParameterView, sets the Value accordingly. In the
example, the recipe file has the entry "Value Three" for the radio button (Value: 3 Recipe
Value: 1) The contents of Value are accepted by Recipe Value only by clicking OK.
Opening the ParameterView with the script instruction Load parameter from file sets Value
to the loaded recipe file (Value: 3 Recipe Value: 1)
Object functions for the ParameterView

Load parameter from file
Load parameter without file
Load parameter
Save parameter
Open ParameterView
Close ParameterView
Recipe value to value
Value to recipe value

May 2011
709
2.4.2.3.4 ParameterView settings

In edit mode, the settings window is opened via the ParameterView Settings item from the
ParameterView's context menu. Various settings can then be made to the ParameterView.
710

May 2011
General tab
Caption
Caption
The ParameterView title.
Button Settings

May 2011
711
OK-Button Visible
Displays the OK button in the lower part of the ParameterView.
OK-Button enabled
When checked, the OK button can be used in runtime mode. When unchecked, the OK
button is grayed-out in runtime mode.
Cancel-Button Visible
Displays the Cancel button in the lower part of the ParameterView.
Cancel-Button enabled
When checked, the Cancel button can be used in runtime mode. When unchecked, the
Cancel button is grayed-out in runtime mode.
Cancel-Button Visible
Displays the Save button in the lower part of the ParameterView.
Save-Button Enabled
When checked, the Save button can be used in runtime mode. When unchecked, the
Save button is grayed-out in runtime mode.
Load-Button Visible
Displays the Load button in the lower part of the ParameterView.
Load-Button Enabled
When checked, the Load button can be used in runtime mode. When unchecked, the
Load button is grayed-out in runtime mode.
Events
Validate Event
When checked, the ParameterView validate event module is available in the module view.
The validate event is fully explained in the subsection.
If Enabled is also checked, the program code in the ParameterView validate event
module is performed in runtime mode on clicking the ParameterView's OK button.
712

May 2011
Init Event
When checked, the ParameterView Initevent module is available in the module view.
When Enabled is checked, the module's program code is performed when the
ParameterView is opened via the script instructions Load parameter without file() or Load
parameter from file.
After Load-Click Event
When checked, the ParameterView after LoadClick Event module is available in the
module view. When enabled is checked, the module's program code is performed on
clicking the ParameterView's Load button.
after Save-Click Event
When checked, the ParameterView after SaveClick Event module is available in the
module view. When enabled is checked, the module's program code is performed on
clicking the ParameterView's Save button.
Load Settings tab

Load Property Groups
Change View
Change view loaded only when checked here.
Visibility
Visibility settings loaded only when checked here.
Position
Position settings loaded only when checked here.
Percentual Bounds
Percentual bound settings loaded only when checked here.
Label Font Settings
Label font settings loaded only when checked here.
Name settings
Name settings loaded only when checked here.
Scale settings
Scale settings loaded only when checked here.
Channel settings
Channel settings loaded only when checked here.

May 2011
713
2.4.2.3.4.1 Validation check
The ParameterView validate event has a special feature. When activated, only parameters
can be input that meet certain criteria. This criteria is defined by the user when setting up
the application.
For example: input of all the ParameterView's fields is required prior to the application
accepting any of the parameters. Another example: a parameter must be within a given
range.
To use the validate event, the following conditions must be met:
Validate Event and Enabled must be checked in the ParameterView settings . An event
module (ParameterView validate event) is then generated in the ModuleView.
The ParameterView must be opened via on the of the following script instructions: Load
parameter from file or Load parameter without file. The OK and Cancel buttons are
available in the ParameterView only when it has been opened in this way. These buttons
are essential for the validate event and are the only options that enable the
ParameterView to be closed.
The validation checks are defined in the ParameterView validate event module . When all
the checks (conditions) are fulfilled, Parameter Valid is set to ON (refer also to the
Configuration Write section in Klicks programming language).
After successful validation, the validated values are available in the parameter object as
recipe values . The recipe values remain available until the next successful validation.
Whenever the application needs to access validated values, it must access the recipe
value and not the value (refer also to Assign Value in the Klicks programming language
section).
Validate operation
Clicking the ParameterView's OK button performs the program code in the ParameterView
validate event module.
The module checks single/multiple parameter object Values (not Recipe Values) by
querying. When all the validation conditions have been fulfilled, Parameter Valid for the
ParameterView is set to ON via a script instruction.
When 'Parameter Valid' equals ON on reaching the end of the module, Recipe Values for all
parameter objects are set to Value. The ParameterView is then closed.
When Parameter Valid equals OFF on reaching the end of the module, Recipe Values are
not accepted (the previous value is retained) and the ParameterView remains open.
Validation example
This example is of a validation that checks that text only is input for a text edit parameter
object.
Open Parameter settings by right clicking a free area in the ParameterView and selecting
ParameterView Settings. Check Validate Event and Enabled.
714

May 2011
To prompt parameter input, add one of the following script instructions (Load parameter
from file or Load parameter without file) to your script (the start module in the example).
Script/Initiate/Parameter Input/Load parameter from file or
Script/Initiate/Parameter Input/Load parameter without file
Open the script editor for the ParameterView validate event.

Insert here an If...then question to check the Value of a text edit parameter object is
not empty (the text input parameter object must already have been added to the
ParameterView).
Set The ParameterView's Parameter Valid to ON when the question is fulfilled.

May 2011
715
This completes the operation.

When the application starts, the ParameterView opens. Clicking OK checks whether text
has been input into the text edit parameter object. If true, Recipe Value is set the
parameter object's Value. In his case, the parameter object's value equals the input text.
The ParameterView is closed and the module's program code (which opened the
ParameterView) continues to run.
If no text has been entered in the parameter object Recipe Value is assigned no new value.
The ParameterView remains open and awaits input.
Unsuccessful validation should issue a message indicating why the

validation failed. This can take place via an information window that
opens when the question in the event module is not fulfilled.
When multiple parameter objects are to be validated, it is simpler to set

Parameter Valid to ON at the beginning of the script. Users can then
define the conditions under which the input parameters are invalid and
then set Parameter Valid to OFF.
716

May 2011
This can be written more briefly.
2.4.2.3.5 Overview of parameter objects
This overview shows the following objects that are available for a ParameterView.
Button parameter object

Symbol:
Text edit parameter object

Symbol:
Check box parameter object

Symbol:
Radio button parameter object

Symbol:
Channel / drop down parameter object

Symbol:

May 2011
717
Label parameter object

Symbol:
Table parameter object

Symbol:
Date/Time parameter object

Symbol:
Profile parameter object

Symbol:
2.4.2.3.5.1 Parameter object context menu
The following context menu opens by right-clicking a parameter object.
Menu item
Description
Copy
Enabled when selecting parameter object in a ParameterView.

The object is then copied to the clipboard
Delete
Deletes the selected parameter object from the ParameterView.
718

May 2011
Grouping
Refer to groupings
Alignment
Refer to alignment
Event modules
Refer to event modules
Properties
Opens a dialog with the parameter object settings.
Configuration of
standard
To edit as in runtime mode (refer to tables and profiles for

parameter objects)
Grouping
This item is available when more than one object has been selected (left-click + shift).
Menu item
Description
Create group
Groups together selected parameter objects to make a single

object group. Each component of the group is accessible only
via the management tree. The function is to optically mark
parameter objects that belong together.
Release group
Deletes a previously created grouping.
Alignment
Aligns the selected (left-click + shift) parameter object.

May 2011
719
Menu item
Description
Align Left
Left aligns the selected parameter object
Align center
Centers the selected parameter object
Align Right
Right aligns the selected parameter object
Align Top
Aligns the selected parameter object to the top
Align Middle
Vertically centers the selected parameter object
Align Bottom
Aligns the selected parameter object to the bottom
Event modules
Contains the events assigned to the parameter object. Selecting an event opens the
corresponding script window.
720

May 2011
2.4.2.3.5.2 Button parameter object

The Button parameter object is used to set binary values and to display VisuViews.
The parameter object button differs to visualisation object button by the inclusion of a
Recipe Status. Therefore, only the Recipe Status is explained here.
Script
Assign Value
Input Parameter
ParameterView
[name of page]
Button
[name of button]
2.4.2.3.5.3 Text edit parameter object

Text edit is used to set analog values and to input text.

May 2011
721
This parameter object differs to the visualisation object text edit by the inclusion of a
Script
Assign Value
Input Parameter
ParameterView
[name of page]
Text edit
[name of text edit]
2.4.2.3.5.4 Check box parameter object

The Check box sets binary values.
This parameter object differs to the visualisation object check box by the inclusion of a
Script
Assign Value
Input Parameter
ParameterView
[name of page]
722
Check box
[name of check box]

May 2011
2.4.2.3.5.5 Radio button parameter object

The radio button sets binary and analog values.
This parameter object differs to the visualisation object radio button only by Recipe value,
Recipe selected name and Recipe selected index. Therefore, only these items are explained
here.
Script
Assign Value
Input Parameter
ParameterView
[name of page]
Radio button
2.4.2.3.5.6 Channel / dropdown box parameter object

The drop down boxes set binary and analog values.

May 2011
723
This parameter object differs to the visualisation object dropdown box only by Recipe
value, Recipe selected name and Recipe selected index. Therefore, only these items are
explained here.
Script
Assign Value
Input Parameter
ParameterView
[name of page]
Dropdown box
[name of dropdown box]
2.4.2.3.5.7 Channel box parameter object

The Channel box is used to select channels.
This parameter object differs to the visualisation object channel box only by Recipe value,
Recipe selected name and Recipe selected index. Therefore, only these items are explained
here.
724

May 2011
Script
Assign Value
Input Parameter
ParameterView
[name of page]
Channel dropdown
[name of channel
dropdown]
2.4.2.3.5.8 Label parameter object

The Label object is used to portray analog values and text.
This parameter object does not differ from the visualisation object label.
2.4.2.3.5.9 Table parameter object

The Table parameter object portrays measurement data within a table. The measurement
data is added to the table via script commands (Pro fiSig nal Klicks only). The table object
can also be used to portray text and numbers.
This parameter object differs to the visualisation object table only by the Recipe Status.
Therefore, only the Recipe Status is explained here.

May 2011
725
Script
Assign Value
Input Parameter
ParameterView
[name of page]
Table
[name of table]
2.4.2.3.5.10 Date/Time parameter object

Date/Time sets dates and times.
This parameter object differs to the visualisation object date/time by the inclusion of a
Recipe value. Therefore, only the Recipe value is explained here.
Script
Assign Value
Input Parameter
ParameterView
[name of page]
Date/Time
[name of date/time]
2.4.2.3.5.11 Profile parameter object

The Profile parameter object is used to generate setpoint curves. A setpoint curve can be
generated in runtime mode, e.g. to control an analog output. The Profile can also output
set points to a dedicated channel. Profile data can then be displayed using other parameter
objects. This feature is especially useful to simulate a process during development when no
connection exists to a Message device.
726

May 2011
Using a profile in the ParameterView

Confirm ParameterView with OK
The ParameterView's profile uses the amended points. The amended points are displayed
when re-opening the ParameterView.
Discard the ParameterView values using cancel

The ParameterView's profile uses the points from the previously opened ParameterView.
The previous points are displayed when re-opening the ParameterView.
ParameterView is closed when

Values are written to the channel when the profile is running. Closing the profile interrupts
the writing of values and the profile is set to its default value.

May 2011
727
2.4.2.4 Report Designer

ProfiSignal reports are printable pages that can be individually configured. Report objects
can be positioned as required on a page to provide specific information for evaluation
purposes.
Depending on the report object category, data is then delivered from a range of different
sources. Some report objects extract data using a background script from ProfiSignal. An
example here is a visualisation object portrayed within an image with measurement data.
Some report objects require manual input, e.g. the label report object.
A report configured in development mode is started in runtime mode via the report button
728

May 2011

May 2011
729
2.4.2.4.1 Create report
Create report
A report is automatically created for a new application if the following settings have been
made in the general settings. Open the Settings dialog from the Settings and Global
settings options on the main toolbar. Checkbox Report in the Project options tab.
To create a report that has not been automatically created in an application, use the
application menu from the management tree. This option also enables the creation of
multiple reports. Right click applications in the management tree. Select Create report
from the submenu.
Open report
730

May 2011
To open a report, double click the report displayed in the management tree. This opens a
report view that enables the insertion of report objects.
2.4.2.4.1.1 Report layout window

Main menu
The main menu in a report contains only the ReportView option. Left clicking ReportView
displays a submenu with the familiar Windows options of cut, copy, paste and delete and
also the option Report settings.
The Report settings dialog has the settings Name for the report name and Resolution
settings for the required (print) resolution in DPI.

May 2011
731
Toolbar
The report toolbar is located between the ReportView option and the tab for individual
pages. The following functions are available: print, zoom, text alignment, typeface and font
attributes.
The four symbols from left to right are: Print, print settings, print preview and export
report as PDF. These functions are enabled only when viewing a created report.
The dropdown list next to the print function (100% in the example) enables the view to be
enlarged (with a value less than 100%) or reduced (with a value greater than 100%).
On the right are functions for aligning the text. The symbols, from left to right, have the
following meanings: left aligned, center aligned, right aligned and justified.
To the right of the alignment symbols are dropdown lists to set font and font size.
The symbols on the far right are for setting font style and font color.
Page overview
732

May 2011
Between the toolbar and the actual page is an area showing the report pages and
subreports. The upper row lists the report pages and the lower row the sub-reports for the
selected report pages.
Right clicking a report page opens a context menu for the report page. This enables pages
to be added, deleted or rearranged.
The paste option enables the report object in the clipboard to be inserted onto the report
page.
The options new page, delete page and rename page add, delete or rename report pages.
The options insert or delete subreports enables subreport pages, which belong to specific
report pages, to be added or deleted.
The move left and move right functions enable changes to be made to the ordering of
pages on the tab.

May 2011
733
The page settings option opens a two-tab settings dialog to enable settings to be made
that are independent of the type of measurement data. The settings dialog is described in
the following section.
Page settings dialog
Page settings enables pages to be named and dimensions / alignment to be set.
The General tab

The name field enables input of the name to appear on the tab in the report view.
The paper properties section sets the formatting for the report page. The paper type
dropdown list enables a standard paper size to be selected. The figures in the height and
width numeric fields are then automatically updated. Non-standard sizes can be entered
using these fields. The portrait and landscape radio buttons sets the page orientation.
The margin section has numeric fields for the input of minimum margins for the report page
layout.
More settings tab

This tab contains settings not covered by general settings.
734

May 2011
Page settings
The page settings section has background page and printable page radio buttons to set
the page's category:
If the page is to be used as a standard page that is not dependent on measurement data,
e.g. a letter that is output in combination with other pages, then enable the background
page button. All other page settings are then disabled.
If the page is to be used as part of a report, for example, to output measurement data as
a trend, then enable the printable option. This report page is a part of a report. Cross
checking print page ensures that the report page is printed when printing the report. The
printable page can also be assigned to a background page. Cross check background page
and select a background page from the dropdown list.
The category and status of a page is displayed on the report page's tab. The following
screenshot shows the different types of symbols:
a printable page that is printed when the report is output; a printable page that is not
printed when the report is output; a background page.

May 2011
735
Background links
When a page is to be used as a background, the report pages are listed for which the
background page is to be used.
Grid
For setting the type of background gridlines.
Snap to grid
When this option is checked, report objects can only be positioned, using the mouse, onto
the gridlines.
dX: and dY:
Input is in millimeters.
2.4.2.4.1.2 Generate report in runtime
There are two methods to generate a report in runtime mode:

1. Via the report button specially developed for this purpose
2. Via a script
Report button
A report button is set up in a VisuView. The button is available under the standard tab for
visualization objects. The following describes only the important aspects of the report
button functions. A more detailed explanation is available elsewhere.
To generate a report with the VisuView report button, open the settings dialog that is
accessed via the Visuview button tab.
736

May 2011
The dropdown box entitled generated report by activity enables selection of the report to
be generated. This lists all the reports that are available to this application.
If expand existing report is enabled, the the generated report pages are added to current
report. If disabled, a new report is generated using the same name plus a consecutive
number.
The name and associated path is entered under report file name. If no settings are made
here a file selection dialog will appear on activating the report button in runtime mode.
The radio buttons to the right of after creating the report provide three options for post
report-generation. Either nothing happens, or the report is printed, or the report is opened.
Generate a report via a script

A report may also be generated in runtime via a script. The script instruction is available
under Script -> Initiate -> Report.
Skript
Initiate Report [Name Report]
Start a report
First, start the report: enable either of the script instructions: start report or start
report with default name. The "start report" script function requires the generated
report's filename to be input as well as input on whether the existing report is to be
appended/ added to. If the existing report is not to be appended, a new report will be
generated with a new consecutive number. The "start report with default name" script
function automatically generates a name using the report name and date/time.
Initiate Report\Rep ort_1: Start report(In: Report file name\Object, append existing report file

May 2011
737
Initiate Report\Rep ort_1: Start report with default name(Out: LVResult)

DataCommit
Data then requires transferring. The report is extended by one page / one record each
time this function is performed.
Initiate Report\Rep ort_1: Commit data()

Stop report
The report requires stopping before it can be opened.
Initiate Report\Rep ort_1: Stop report(Out: LVResult)

Open report file
A report can be opened after it has been stopped. The report name requires inputting
as well as input on whether the report is to be displayed in full screen mode.
Initiate Open report file(In: Report file\Report\ Rep ort_1.Rep ortName, Front\Object, Full
screen\Object Out: LVResult)
2.4.2.4.1.3 Subreport
It is possible to assign multiple subreports to a report.
Assigning a subreport to a report
738

May 2011
Right click the report page that is to be assigned a subreport. Then select the insert
subreport option. The option is available only when the report page is empty and has no
report objects. If this is not the case the option is grayed out and a subreport may not be
added.
In the above screenshot the report Unnamed_1 has the subreport Unnamed_3 assigned to
it. This can then have as many report objects assigned to it as required. If you require a
subreport to have another subreport assigned to it, the assigning subreport may not
contain any report objects.
Inputting data to a subreport

May 2011
739
Skript
Initiate
Report
[Name Report]
[Name ReportPage]
[Name SubReport]
Inputting data to the subreport is possible only via a script and not via the report button.
The subreport is included in the script function initiate report. It has an extra object
function called DataCommit. This is set up just as a generated report without a subreport.
The procedure is as follows:
Start the report
Start with either the start report or start report with default name script instructions.
DataCommit for subreport
For each run, the report has a subreport page added (in this case "Report_1") by using
the DataCommit object function. If you perform this object function four times before
you commit the data to the report (Report_1 DataCommit), the report has four
subreport pages added to it.
Initiate Report\Unnamed_1.Rep ort_Unnamed_1_1: Commit data()

DataCommit
When committing data to the report, the subreports that have been generated up to
this point are added. In the event that the report includes other pages (Unnamed_2 in
the example), these will also be committed.
Stop report
This script instruction needs to be performed before the report can be opened.
2.4.2.4.2 Overview of report objects

Overview
Frame and Group report objects
Symbol:
Label report object

Symbol:
Number band report object

Symbol:
Table report object

Symbol:
Page count / page number report object

Symbol:
Date / time / report filename report object
740

May 2011
Symbol:
Picture report object

Symbol:
Graph/diagram report object

Symbol:
Alarm table/list report object

Symbol:
2.4.2.4.2.1 Report objects - General Information
Report objects are graphical elements that portray categories of information in the
reporting of measurement data. The information to be portrayed is obtained from different
sources depending on the report object.
Some information can be obtained using ProfiSignal's programming scripts, e.g. when
measurement data is displayed via a visualisation object.
If the current date is to be included in the report, this is taken from the PC.
Some report objects require manual input, e.g. the label report object.
All reports objects are added to the report in the same way. Right clicking a report objects
opens a context menu. Each report object has a properties dialog that includes a tab
specific to each object and a general tab that is identical for all report objects.
Adding a report object to a report

May 2011
741
A report object is selected by left clicking. Left clicking and holding the object (keeping the
left button pressed) enables it to be dragged to the required position within the report.
On releasing the object, opens the New Component window. A predefined object name
(Pagecount_1 in the example here) can be amended as required and confirmed with OK.
The toolbar icons with a black triangle in the lower left corner have submenus with
additional objects available for selection. Right clicking an icon opens the submenu. Left
clicking then selects the required object.
Right clicking an object opens a context menu:
742

May 2011
Copy, paste and delete

The copy and/or delete options enables the report object in the clipboard to be copied or
deleted. The paste option enables the clipboard to be copied at the required location.
Grouping
Left clicking the Grouping option opens a submenu to create report-object groups or to
delete existing groups.
Report objects are grouped by selecting multiple objects while pressing the shift key. Left
clicking the Grouping option then enables grouping of the selected objects. The grouped
objects can then be processed within the report as a single object.
A selected group can be deleted by left clicking Grouping and then Ungroup .
Order

May 2011
743
The "order" option determines whether the object is to be in the fore- or background in
relation to other report objects.
A report object's settings are managed via its settings window.
The settings window can be opened in development mode by double clicking the report
object or via the properties context menu option.
A report object's settings are accessed via two tabs.
The general settings are identical for all report objects and are described here.
The General tab
744

May 2011
Name section
This area is used for inputting the report object name.
Size and position section

May 2011
745
This sets the report object's size and position.

The X and Y fields set the upper left positioning. The numerical fields indicate the distance
of this point from the upper left corner of the report page. Input is ignored that exceeds
the margin settings and is replaced with the maximum permissible values.
This also applies to the width and height settings for the report object.
Color & border section
This sets how the report object appears on the report page.
The left, right, top, bottom checkboxes set the extent of bordering. Checkboxing opens
the numeric field for setting the width of the border line.
The report object's background color on the report page can be selected by checking
background color. A button will then appear next to the checkbox to open a color palette.
2.4.2.4.2.2 Frame and Group report objects

The two report objects, Group and Frame are used to group together multiple report
objects.
The Frame report object can also be used to portray multiple measurements on one report
page.
Positioning a report object

Place the report object on the report page at the required position and size. Report objects
can then be assigned to the group by selecting the required object from the toolbar and
746

May 2011
positioning it within the group. It is also possible to incorporate subgroups to groups at the
required level of nesting.
Unlike frames, it is possible to generate groups via menus. Select the report objects to be
grouped together and right click one of the report objects. Select Grouping from the menu.
To ungroup an existing group click Ungroup.
Grouping overview in the management tree

The management tree visually portrays the nesting of groups. This is however visible only
when extended mode is selected in the general tab of the general settings dialog.
Usage
Amendments to a single report object belonging to a group changes all the report objects
within that group. This applies to enlargement, reduction and repositioning.
If a report object is selected within a group, the object can be amended as required but
can not be moved beyond the borders of the group.
Frame and Group settings

May 2011
747
Open the group / frames settings window by double clicking the report object in
development mode or via the report object's properties context menu.
The General tab

The properties in the general tab sets the visualization object's runtime display and
operational properties. The properties are described in the General properties section.
The frame control tab (for frames only)

The frame control tab enables setting of the report object's specific properties.
Frame control section
If enable frame control is checked the start data number numeric field is also then
748

May 2011
active. This selects the number of the data record from which the portrayal is to begin.
The interval control is also enabled. Checkboxing 'interval control' then enables interval
step. This numeric field sets the number of data records to be portrayed on a report
page.
This is explained using the following example:
A frame that contains multiple report objects is generated in a report. The frame includes
multiple labels, one date, one time and one number. The report objects are partially linked
to visualization objects; in this example to a digital display and a date.
The frame is now positioned three times next to each other by copying. The interval
control for all three frames is given as 3 because the data record is to be portrayed
exactly three times. The "start data number" in the first frame is 0, in the second, 1, and
in the third, 2. The first frame then receives data at the first report generation, and the
second frame at the second time. At the third report generation, all three frames have
data. In this example, the first frame receives data at 12:32 hours with the digital
displays showing a value of 15.9. The second frame receives data at 12:33 and so on.
2.4.2.4.2.3 Label report object

The label report object is used to portray a set text on the report page.

May 2011
749
Label settings/ properties
Open the label settings window by double clicking the report object in development mode or
via the report object's properties context menu.
The General tab

The settings in the general tab sets the visualization object's runtime display and
The label tab

The label tab enables setting of the report object's specific properties.
750

May 2011
Label section
The label section has a text field to enter the label text including line breaks.
Font, Pre- & Suffix section

May 2011
751
The prefix and suffix input fields enable input that will appear before or after the label
respectively.
Left clicking the font button opens a dialog window that enables a font to be selected.
The radio buttons 0, 90, 180, 270, which are located to the right of the font button,
determine text rotation. The angles refer to the degree of rotation from the text's base
line in an anti-clockwise direction.
Alignment section
The left, right, center and justify buttons set the text alignment within the report object
area.
2.4.2.4.2.4 Number band report object

The string, text and number band report objects are used to display, on the report page,
the current value of a visualisation / parameter object.
The string report object is used to display single-line text.
The text report object is used to display multiple lines of text.
The number report object is used to display formatted numerical values.
752

May 2011
A text object, unlike a string object, may use line breaks and is therefore able to fully
display assigned text.
Settings for string/text/number
Open the string/ text/ number settings window by double clicking the report object in
development mode or via the properties option in the report object's context menu (right
click report object).
The General tab

The string/ text/ number tab

The label tab enables setting of the report objects specific properties.

May 2011
753
754

May 2011

May 2011
755
Value Source section
This determines where the data is to be obtained for the report object variable. Selection
is made via the radio buttons value from script or value direct from a property. In the
former, the data is assigned directly from a script (this option is unavailable in
Pro fiSig nal Basic). The data can alternatively be taken from an object's properties. The
objects that are available for selection are shown in lists. Left or right clicking the input
field opens a submenu with the lists of available objects.
The following is an example of assigning data to a report object. The number report
object is assigned the value shown in a digital display located in a VisuView. The first
example illustrates assigning of the value via a script. The second example illustrates a
direct assignment.
Assign Value: Report\Rep ort_1.Page 1.Numberband.Numberband_1 = Visualisation

\VisuView_1\DigMet.Digitalmeter_1
[Name Application]
[Name VisuView]
[Name VisuView Obj ect]
Properties
Values
Font, Pre- & Suffix section (for string and number report obj ects only)
756

May 2011
respectively.
Alignment section
area.
Length control section (string report object only)
For setting the permitted length of text. A maximum of 255 characters is possible.
Checkboxing limited text length enables input to be made via the lower numeric field.
The required maximum permissible characters can then be input, either directly via the
keyboard or by clicking the arrow buttons.
Number format section (number report object only)

May 2011
757
To format the number to be displayed in the report.

decimal places.
0 Numeric placeholder
# Numeric placeholder (without leading and trailing zeroes)
,
Thousands separator. When the text contains a comma, the thousands separator is
displayed.
An example using a channel value of 1073,558

Data format
##0.0
##,###0.0
000000.0000
############.##
Display format
73.6
1,073.6
001073.5580
1073.56
2.4.2.4.2.5 Table report object

The table report object is used to portray a table on the report page.
Table settings
758

May 2011
Open the table settings window by double clicking the report object in development mode
or via the report object's properties context menu.
The General tab

The table tab

The label tab enables setting of the report object's specific properties.

May 2011
759
Style section
This section enables font settings for the header and body of the table. Unchecking
"Header Row" means the table will have no column headings.
Columns section
760

May 2011
The columns section enables each column to be separately set. Select a column from the
list and enter the settings via the corresponding input and selection fields. The add and
delete columns enable columns to be added or deleted.
The following input and selection fields are available:
Label
The heading for the selected column.
Width
Column width.
Data type
The column's data type. This can be text, an integer or number.
Format
A format can be selected only for a number. The format is entered in the field next
to the data type field.
Header align
To input the required alignment for column headings. Options are: left, center, right,
and block.
Text align
Sets the alignment for text within a column.
Prefix
This prefix will appear before the content in the selected column.
Suffix
The suffix will appear after the content in the selected column.
Use own font
The user's own font and color can be applied to the text in the selected column.

May 2011
761
The following is an example to illustrate the table settings.
The Border tab

The Border tab sets the color and width of the table's lines/borders.
762

May 2011
2.4.2.4.2.6 Page count / page number report object

The page count and page number report objects show the current page and total number
of pages within a printed report.
These objects are usually used in combination to get a count of the number of pages.
The actual page numbering is then automatically input into these fields when outputting
the report.
Example: Page 3 / 5 => Page page number/ page count
Page number/page count settings

May 2011
763
Open the page number / page count settings window by double clicking the report object
in development mode or via the report object's properties context menu.
The General tab

The text tab

The text tab enables setting of the report object's specific properties.
respectively.
764

May 2011
Alignment section
area.
2.4.2.4.2.7 Date / time / report filename report object

The report objects short date, date, short time, time are used to portray the time and
date in a report.
The report object "report file name" gives the name, including full path, of the generated
report file.
Date / time settings

May 2011
765
Open the text settings window by double clicking the report object in development mode or
via the report object's properties context menu.
The General tab

The text tab

The text tab enables setting of the report object's specific properties.
766

May 2011
respectively.
Alignment section
area.
2.4.2.4.2.8 Picture report object

The picture report object is used to portray, on a report page, picture files (e.g. logos) and
illustrations from visualisation and parameter objects.

May 2011
767
Picture settings
Open the picture settings window by double clicking the report object in development mode
The General tab

The picture tab

The label tab enables setting of the report objects specific properties.
768

May 2011
Picture location section
Sets the source from which the picture is to be taken.

Crosschecking "get picture directly" enables a picture to be loaded directly via the "load
bitmap" key. Left clicking the the "load bitmap" key opens a dialog to enable the required
file to be loaded.
Crosschecking the "get picture directly" additionally opens a third tab (auto picture). All
visualization object for this application are listed under the picture from component field.
Left clicking the required visualisation object portrays the object in the report object.

May 2011
769
Align section
This section is relevant only when Proportional is crosschecked. If "proportional" is not

crosschecked, the picture and report object occupy an identical area.
If proportional is crosschecked, the six available keys can be used to align the picture
within the report object area.
2.4.2.4.2.9 Alarm table report object
The alarm table report object puts alarms into a printable format. There are two options to
access the alarms. The report object can be linked to an alarm table in a VisuView. The
alarm content displayed in the VisuView is also delivered to the report object. Alternatively,
the alarm class/category of the alarms to be reported on are set directly within the report
object.
Alarm table/list settings
Open the alarm table settings window by double clicking the report object in development
mode or via the report object's properties context menu.
The General tab
770

May 2011
The "alarm table choice" tab

The alarm table choice set tab enables setting of the content of the alarm table report
object. There are two options. The report alarm table can be linked to a VisuView alarm
table. The report table then displays the alarms displayed by the VisuView table.
Alternatively, selection is made of the alarm class for the alarms to be reported in the
table. Further information on how content can be generated for the alarm table is available
in this sub-section.
Linking a report alarm table to a VisuView alarm table

The dropdown box in the allowed alarm tables in the report section lists all the
application's VisuView alarm tables. Select the alarm table to be used in the report.
Selecting an alarm table then hides the alarm class section below. The report alarm table
then uses the column settings from the selected VisuView alarm table. This means that the
report alarm table displays only those columns that are also displayed in the VisuView table.
Column width is also used. These settings can be changed in the table tab. Linking another
VisuView alarm table to the report table overwrites the report table's settings from any
previously selected VisuView alarm table.
Self-selection of alarm class
The alarm class section lists all the classes that the DataService has made available.
Select the class of the alarms to be displayed. The alarm class section is visible only when
an alarm object has not been selected from the VisuView alarm table list in the "allowed
alarm tables" section.
The table tab

May 2011
771
Style section
This section enables font settings for the header and body of the table. Unchecking
"Header Row" means the table will have no column headings.
Columns section
772

May 2011
For column settings. If the report alarm table has been linked to a VisuView table, the
settings shown here are those from the VisuView table. These can be amended here if
required. If, however, alarm classes have been selected, the settings here will be blank and
will require input.
Add/ Del button
Clicking this key opens the following dialog that lists the available columns . The column is
displayed when checkboxed and hidden when not checkboxed.
Up/down keys
These keys enable changing of the order in which the columns are displayed. Position the
columns in the order to be displayed.
Column settings
Each column can be individually set. Select the column to be set. The settings can then be
made/amended in the column setting section.

May 2011
773
Label:
The column heading/title.
Width:
Column width.
Header align:
The heading alignment within the column: left, right or center.
Text align:
Alignment of the entire column excluding the heading/title.
Use own font:
When checkboxed, the user's own font can be used for this column. When
unchecked, the font used is that selected in the style section.
The Border tab
The Border tab sets the color and width of the table's lines/borders.
774

May 2011
That are two methods for inserting alarm content into a report object. The report alarm
table can be linked to a VisuView alarm table. The report table then displays the alarms
displayed by the VisuView table. The report table can be either a current or archived alarm.
Alternatively, selection can be made of the alarm class for the alarms to be reported.
Linking a report alarm table to a VisuView alarm table

The VisuView alarm table content to be used in the report is selected in the settings dialog
of the report alarm table object. The report alarm table also uses the VisuView alarm
table's column settings which can be subsequently amended via the table tab.
This method enables the report to be created via both the report key and a script

May 2011
775
instruction.
When a report is created during runtime, all alarms that have been displayed in the
VisuView alarm table will also be included in the report alarm table.
Self-selection of alarm class

The alarm class section lists all the classes that the DataService has made available.
Select the class of the alarms to be displayed. The alarm class section is visible only when
an alarm object has not been selected from the VisuView alarm table list in the "allowed
alarm tables" section.
This method creates a report via script instruction. To enable alarms to be portrayed firstly
requires a time range to be set from which the alarms are to be portrayed. For this purpose
the initiate instruction has a start and end time.
Script
Initiate
Report
[Name of report]
[Name of page]
776
Alarmlist
[Name of alarm table]

May 2011
Initiate Report\Rep ort_1.Page.Unnamed_1.Rep ort alarm table_1:: Start and end time(In:
Start time\Object, End time\Object Out: LVResult)
The start and end times must be run before running the DataCommit function. The
following example shows how to create a report, with a fixed time period, using a script.

Initiate Report\Rep ort_1.Page.Unnamed_1.Rep ort alarm table_1:: Start and end time(In:
Start time\17/08/2011 14:00:00, End time\17/08/2011 15:00:00 Out: LVResult)
Config Read: LVRep ortName = Report\Rep ort_1.Rep ortName
Initiate Report: Open report file(In: Report file\Report\Rep ort_1.ReportName, Front\yes Full
screen\no Out: LVResult)
When a report is created in runtime, the alarms that will be displayed in the report alarm
table are those within the given time period and of the class/classes that is/are
checkboxed in the settings dialog.
When creating a report in this way, do not forget to select the columns, that are to be
displayed in the created table. The list of displayed columns is initially empty.
2.4.2.4.2.10 Graph report object

The graph report object is used to portray diagrams/graphs (YT, logic, YX(HW), YX(Tab),
FFT and orbit) on a report page. This object differs to a picture report object in that a
graph / diagram is not just a static portrayal of a trend visualisation object but can be
changed in the finished report file. In this way, the axis scale and curve color may be
changed prior to print out. It is also possible to hide specific measurement curves.
This requires that the trend visualisation object is linked to a recorder object (refer also
to the trend settings section) and that a recording has been created prior to data commit.
The data from the recording is then automatically inserted into the graph report object.

May 2011
777
Trend settings
Open the trend settings window by double clicking the report object in development mode
The General tab

The trend selection tab

The trend selection tab enables setting of the report object's specific properties.
778

May 2011
"Available visutrends for the report" section
This section enables trend content to be included in a report graph/diagram.

The dropdown box lists the available trend objects. Selecting a trend inserts its content
into the report graph/diagram.
Rotation section
The radio buttons0, 90, 180, 270 set the portrayals rotation. The angles refer to the
degree of rotation from the base line in an anti-clockwise direction.
The quality of the portrayal may diminish when rotating the graph/diagram.
Type section

May 2011
779
Sets whether only the graph/diagram is to portrayed, or only its legend, or the graph/
diagram plus legend. A legend lists all the visible channels of a graph/diagram.
The layout tab

The layout tab enables setting of the report object's specific properties.
780

May 2011
Diagram section
MouseCursor transparent - when checkboxed, visible cursors or markers do not obscure

the measurement curves.
With channel index - channel measurement curves are indexed and the index is included
in the legend.
Index above curves - the indexing of the measurement curve is located above the curve.
Index count - the number of indexes per measurement curve.
Black/white print - optimizes the portrayal for black/white output.
Legend section

May 2011
781
Columns - the number of columns over which channel information is to be divided. The
division into columns takes place only when the legend is printed below the diagram.
Align - the position of the legend: below the diagram (bottom), or to the left or to the
right of the diagram. This setting is effective only when the diagram and legend is output
to one page.
Channel information - the legend can be portrayed with information additional to the
index and channel name.
The portrayal of a graph/diagram in a report is described in the graph/diagram example

subsection. Refer also to the information in the print diagram section for trend objects.
Example screenshot of a YT-diagram.
This screenshot was used for reports that were generated with Pro fiSig nal versions up to
and including V2.1.
From version 2.2, the diagram is saved in "Enhanced Metafile"-Format (EMF). This
optimizes its portrayal in a report:
782

May 2011
The diagram within a report: the legend is on the right and there is no indexing of the
channels.

May 2011
783
The diagram within a report: the legend is below and there the channels are indexed.
2.4.2.5 ModuleView
The ModuleView structures processes by using special modules. To create a ModuleView,
modules are placed onto the ModuleView page. Connector lines for modules are
automatically inserted according to fixed rules, but the lines can subsequently be moved
and amended.
The ModuleView can have a range of tabs. In Pro fiSig nal Klicks, tabs are always available
for processing and modules. Event tabs appear automatically when events are added for
visualisation objects, parameter objects or for ParameterViews.
784

May 2011
ModuleView menu
Left-click ModuleView in edit mode to open the following menu.
"Zoom" and "Modules" have submenu items.

May 2011
785
Menu item
Description
Zoom
To set the zoom factor, i.e. the size that the module is
displayed.
Properties
Opens the ModuleView properties dialog
Modules
Refer to module context menu and submodule context menus
Close
Closes the ModuleView
ModuleView context menu

Right-clicking a free space in a ModuleView while in edit mode opens the following context
menu (right-clicking a module opens either a module context menu or submodule context
menu):
786

May 2011
Menu item
Description
Zoom
To set the zoom factor, i.e. the size that the module is
displayed.
ModuleView properties
Opens the ModuleView properties dialog
Help
Displays either the processing, submodule or event tabs

depending on the tab that has been selected.
ModuleView properties
The ModuleView properties dialog is available in edit mode and contains the following tabs.
General tab

May 2011
787
Grid
For setting the ModuleView's background grid lines. Grids are displayed only in edit mode to
aid the positioning of parameter objects. The grid is always hidden in runtime mode.
Overview of functions:
Enabled
Displays gridlines.
dX: and dY:
The input is in pixels. Note that the input is independent of the selected zoom factor and
always relates to the default zoom factor of 100%. If a zoom factor other than 100% is
selected, then the display values are converted. Possible values range from 2 to 100.
Grid line width
Sets the width of the grid lines. The input is in pixels. Note that the input is independent
of the selected zoom and always relates to the default zoom factor of 100%. If a zoom
factor other than 100% is selected, then the display values are converted. Possible
values range from 1 to 20.
Color section
788

May 2011
Background
Opens a color palette to select the background color of the ModuleView.
Grid
Module tab
Extension line
Extension line sets the ModuleView's connector lines.

Extension line width:
The width of the ModuleView's connector lines
Line color

May 2011
789
Connector line color

Loop color
Color of the loops between modules
Design
Background color:
The background color for modules
Component color
The background color of the rectangles that surround a module
Incomplete script color
The color given to a module whose script contains errors
Line color
Connector line color
Active Module (runtime):
The color given to a module in runtime, i.e. when this module is being performed
Frame color
The module's border/frame color
Frame width:
The width of the module's border/frame
Module font
Opens a dialog to select the module font
2.4.2.5.1 Processing tab

The first tab contains the process flow. The following toolbar is available when selecting
this tab in edit mode.
This toolbar is used to add modules to the process flow. Applications can become very
complex. It is therefore important to work in a structured way and to give the modules
meaningful names. Note: The toolbar is hidden in runtime mode.
790

May 2011
Sequence module
Module Properties
Module name
OK
Sequence
module
This button inserts a sequence module into the process flow. The
sequence module must be inserted between two existing modules in the
ModuleView. Select these two modules using the mouse (+ SHIFT). Then
click the sequence module button. Left-click the location in the process
flow at which the sequence module is to be added. This opens the
module properties dialog. Enter a name for the sequence module and
confirm with OK. The module is now included in the process flow.
Function module Module Properties
Module name
OK
Function
module
This button inserts a function module into the process flow. Use the
mouse to select a module in the process flow to which the function
module is to be added. Then click the function module button. Left-click
the location in the process flow at which the function module is to be
added. This opens the module properties dialog. Enter a name for the
function module and confirm with OK. The module is now included in the
process flow.
Security module Module Properties
Module name
OK
Security
module
End module
This button inserts a security module into the process flow. Then click
the security module button. Left-click the location in the process flow at
which the security moduleis to be added. This opens the module
properties dialog. Enter a name for the security module and confirm with
OK. The module is now included in the process flow.
End module Module Properties
Module name
OK
This button inserts an end module into the process flow. Use the mouse
to select a module in the process flow to which the end module is to be
added. Then click the end module button. Left-click the location in the
process flow at which the end module is to be added. This opens the
module properties dialog. Enter a name for the end module and confirm
with OK. The module is now included in the process flow.
A process flow may appear as follows.

May 2011
791
Modules can be connected via the module context menu.

The modules in a ModuleView represent containers for programming code. To enter the code (refer
also to the Klicks programming language), open the script editor. Opening takes place in
edit mode as follows:
Double-click a module
Click the module and press F4.
Right-click the module. From the context menu select Show script.
Click the module and select Modules>Show script from the ModuleView menu.
The ModuleView provides a unique overview of a process flow, its events and submodules.
This makes programming maintenance easy, even after many years of use. An overview is
792

May 2011
maintained even for complex processes.

A benefit of the ModuleView is that it requires a minimum of module types.
Further information on modules is available under module types.
2.4.2.5.2 Events tab

It is possible to assign program code to visualisation objects, parameter objects and to
ParameterViews. The code is then performed when specific events occur. Such an event
might be the left-clicking of a button, or a change in a table value.
Events for visualisation objects

To add an event, double-click a visualisation object in edit mode. This opens a settings
dialog that contains an event tab (but only when the visualisation object is an object that
can be assigned an event). The settings dialog can also be opened by right-clicking the
object and selecting properties from the context menu.
When an event is assigned to a visualisation object that is located on a VisuView, an event
tab will appear in the VisuView with the corresponding event module. The name of the
event tab corresponds to the name of the VisuView. If the VisuView contains only
visualisation objects that cannot be assigned events, an event tab will not be displayed.
ProfiSignal l provides the following events for visualisation objects. Not every event is
available for every visualisation object. Further information on events is available under
visualisation objects.
Left click
Right click
Double click
Value change
status.
Upper limit
or Off status.
Lower limit

May 2011
793
or Off status.
Timer
The Timer event is used to perform program code cyclically. It is available only for the
Timer visualisation object
Change View
Places a different VisuView in the foreground during runtime mode. The event is available
for the visualisation objects: Picture and Button.
Events for parameter objects

To set up an event, double-click the parameter object in edit mode. This opens a settings
dialog that contains an event tab (but only when the parameter object is an object that
can be assigned an event). The settings dialog can also be opened by right-clicking the
object and selecting properties from the context menu.
When an event is assigned to a parameter object that is located on a ParameterView page,
an event tab will appear on the page with the corresponding event module. The name of
the event tab is made up of the ParameterView text and the name of the ParameterView
page. If the ParameterView page contains only parameter objects that cannot be assigned
events, an event tab will not be displayed.
ProfiSignal l provides the following events for parameter objects. Not every event is
available for every parameter object. Further information on events is available under
parameter objects.
Left click
Right click
Double click
Value change
status.
Upper limit
or Off status.
Lower limit
or Off status.
Change View
Places a different VisuView in the foreground during runtime mode. The event is available
for the visualisation objects: Picture and Button.
Events for ParameterViews
794

May 2011
To add an event, right-click a free space (not a parameter object) on the ParameterView in
edit mode. This opens the context menu for the ParameterView. Select ParameterView
Settings, to open the settings dialog. This dialog contains an events section under the
general tab.
When an event is assigned to a ParameterView, an event tab will appear with the
corresponding event module. The name of the event tab is the ParameterView. If the
ParameterView has no events assigned to it, an event tab will not be displayed.
The following events can be assigned to a ParameterView (further information is available
under ParameterView settings).
Validation check
A validation check is performed.
Initialisation
To run program code when the ParameterView is opened via the script instructions: Load
parameter without file() or Load parameter from file() .
After Load-Click Event
Runs program code on clicking the Load button in a ParameterView.
after Save-Click Event
Runs program code on clicking the Save button in a ParameterView.
Events for an application

An application can be assigned events via its context menu. The events are portrayed in a
tab with the name:"application events".
Assigning an event
At the start of a process, edit mode can be called by simply enabling an event tab. The
following toolbar provides all the elements required to program a ParameterView. Unavailable
items are grayed-out.
This toolbar is used to add modules to the process flow. An application may have any
number of events which can then be assigned modules. It is therefore essential to work in a
structured way and to give each module a meaningful name. The toolbar is hidden in runtime
mode.
Sequence module
Module Properties
Module name
OK
This button inserts a sequence module into the event.

Sequence
module
Use the mouse (+SHIFT) to select two modules in the event between
which the sequence module is to be inserted. Click the sequence module

May 2011
795
button and position the module. This opens the module properties dialog.
Enter a name for the sequence module and confirm with OK. The module
is now included in the process flow.
Function module Module Properties Sequence module name
OK
This button inserts a function module into an event.
Parallel
symbol:
Use the mouse to select a module in the event to which the function
module is to be added. Click the function module button and position the
module. This opens the module properties dialog. Enter a name for the
function module and confirm with OK. The module is now included in the
event.
Event module Module Properties Event module name
OK
This button inserts an event module into the event.
Event module
Use the mouse to select a module in the event to which the event
module is to be added. Left-click the location in the event at which the
event moduleis to be added. This opens the module properties dialog.
Enter a name for the event module and confirm with OK. The module is
now included in the event.
For example, the following ModuleView is for the VisuView named VisuView_1, with a button
named Start motor, that has a Left click event assigned to it.
It is possible to define a process flow within events.
796

May 2011
Modules can be connected via the module context menu.
The modules in a ModuleView represent containers for programming code. Open the script editor to
enter the code (refer also to the Klicks programming language).
Open script editor
Select the module and press F4
Right-click a module. Select 'Show script' from the context menu
Select the module and click 'Show module/script' in the ModuleView menu
The ModuleView gives an overview of process flows, events, and submodules. Long term
program maintenance is therefore possible even for inexperienced users. An overview is
available, even for complex projects, enabling them to be easily managed.
An advantage of a ModuleView is that it requires only a few different types of module.
Further information is available under module types.

May 2011
797
2.4.2.5.3 Submodule tab

Pro fiSig nal Klicks enables the set-up of submodules that can be called from other modules
(refer also to the Klicks programming language).
The following toolbar appears when selecting the tab in edit mode. Non-available items are
grayed-out. The toolbar is hidden in runtime mode.
The toolbar can be used to add new submodules. Applications can become very complex. It
is therefore important to work in a structured way and to give the modules meaningful
names.
Submodule
This button inserts a submodule. Click the submodule button. Left-click a

location at which the submodule is to be inserted to open a module
properties dialog. A name can then be entered for the submodule. Click
OK to add the module.
New submodules can be added in this way.
The modules in a ModuleView represent containers for programming code. Open the script editor to
enter the programming code (refer also to the Klicks programming language). Open the
script editor as follows:
798

May 2011
The ModuleView gives an overview of process flows, events, and submodules. Long term
program maintenance is therefore possible even for inexperienced users. An overview is
available, even for complex projects, enabling them to be easily managed.
An advantage of a ModuleView is that it requires only a few different types of module.
Further information on modules is available under module types.
2.4.2.5.4 Module types
The following modules types are available.
Start module
End module
Sequence module
Function module
Security module
Event symbol:
End event module
Submodule
Init module
The modules in a ModuleView represent containers for program code. Open the script editor
to enter the code (refer also to the Klicks programming language). Open the script editor as
follows:
Double-click a module in the ModuleView.
Right-click the module name in the management tree. From the context menu select
Show script.
Start module
A start module occurs only in a process flow and is represented as:

May 2011
799
A process flow can have only one beginning point and therefore only one start module. The
name of the beginning point can not be changed (refer also to security modules).
When a new application is set up, start and end modules are automatically added. The
processing tab's toolbar therefore contains no start or end modules.
End module
An end module occurs only in a process flow and is represented as:
(End_1 is an amendable name). An end module is added using the following symbol:
from the processing tab's toolbar.
A process may have only one start module but may have any number of end modules. For
example, for a successful or failed process.
When a new application is set up, start and end modules are automatically added.
Sequence module
A sequence module occurs in a process flow and is represented as:
(Standby is an amendable name). A sequence module is added using the following symbol:
800

May 2011
from the processing tab toolbar or from the event tab toolbar.
Sequence modules are processed sequentially. A module can have several sequence
modules assigned to it.
Only one module is actually processed (refer to the Klicks programming language and calling
sequence modules).
A loop enables a process flow to be diverted to another sequence module. This enables a
sequence module to be performed repeatedly. It is possible to set up loops that start and
end within the same sequence module.

May 2011
801
To set up a loop, select one or two sequence modules, open the module context menu and
select Create loop.
To reposition a loop, move the mouse cursor to the loop's vertical connector line. The
cursor changes its appearance to indicate that the loop can now be moved.
Security module
Process flows can have secure as well as normal processes. The secure process ensures
the application closes down correctly in the event that a normal process failing.
802

May 2011
The security module is the start module for a secure process and is represented by the
symbol:
A secure process can have only one beginning point and therefore only one security
module. The name of the beginning point can not be changed (refer also to start module).
A security module is added using the following symbol:
from the processing tab's toolbar.
A secure process can contain sequence modules, function modules and several end
modules.

May 2011
803
Event modules
It is possible to assign program code to visualisation objects and parameter objects. The
code is then performed when specific events occur. Such an event might be the leftclicking of a button, or a change in a table value. When an event is set up, it appears in
the event tab by the symbol:
The name of the event can be amended via its visualisation object or parameter object.
Initially, only an end event module can be connected to an event module. Sequence
804

May 2011
modules can subsequently be inserted between the event and end event modules. Function
modules can be connected to sequence modules.
End event module

An end event module appears only in an event tab and is represented as:
(End_1 is an amendable name). An end module is added using the following symbol:

May 2011
805
from the event tab's toolbar.
An event has only one event module but any number of end event modules that can end
the event and the program procedure behind the event.
Function module
A function module occurs in a process flow and is represented as:
(Substance A is an amendable name). A function module is added using the following

symbol:
Function modules can be connected to any sequence module and are performed using
program instructions (refer to the Klicks programming language and performing function
modules).
Processing of the function module begins automatically when the associated sequence
module has been performed.
Submodule
A submodule appears only in the submodule tab and is represented as:
(Calibrate cooling is an amendable name). A submodule is added using the following

symbol:
806

May 2011
Submodules are not connected to other modules. Submodules are run from program
instructions (refer to the Klicks programming language and performing submodules).
Init module
An Init module is automatically inserted into a process flow and is represented as:
It is performed when switching to runtime mode. When an application is switched to

runtime mode, the Init module can, for example, set application variables to their start
values. Scripts can re-perform this module from within the program procedure. A number of
lines of code are automatically created when adding this module. These lines may not be
deleted!
Module context menu (excludes submodules)

Right clicking a module (not a submodule) in the ModuleView opens the following context
menu:

May 2011
807
Menu item
Description
Cut
Enabled when a sequence or function module has been selected.

Clicking this option retains the selected module. There are now 2
possibilities:
1.) A cut sequence module is deleted from its current position
and inserted into its new position using Paste. The new position
is defined by selecting two other modules after cutting. The
sequence module's name does not change. This method can also
be used to move sequence modules between the processing tab
and event tabs.
2.) A cut function module is deleted from its current position and
inserted to its new position using Paste. The new position is
defined by selecting a sequence module after cutting. The
function module's name does not change. This method can also
be used to move function modules between the processing tab
and event tabs.
Copy
Enabled when a module has been selected that can be copied.

Modules that can be copies are sequence, function, and
submodules.
Paste
Enabled when a module has been copied or cut and one of the
three following cases apply:
1.) A sequence module has been copied/cut and two modules
have been selected. The sequence module is then pasted
between the two selected modules.
808

May 2011
2.) A function module has been copied/cut and a sequence

module has been selected.
3.) A submodule has been copied/cut
Paste inserts the module.
Create extension line
Enabled when two modules (start, end or sequence modules

only) have been selected (left-click + SHIFT) that are not yet
connected. A connection between the modules is then
generated.
Create Loop

only) have been selected (left-click + SHIFT). A loop is then
created between the two modules.
Delete connection
Deletes a connection that has been generated by Create

Extension Line. Two modules must be selected (left-click +
SHIFT).
Delete loop
Deletes a loop that has been generated by Create Loop. Two

modules must be selected (left-click + SHIFT).
Delete Module
Deletes the selected module. A start module may not be

deleted. An end module can be deleted only when an end still
remains.
Create Loop
Enabled when the selected module contains loops. In this case,

a submenu lists the target module for loops. Selecting such a
target module opens a color dialog to select the color of the
loop. Reset sets the loop color to the default.
Show script
Opens a script editor (refer also to the Klicks programming

language).
Module properties
Opens a dialog with the module's properties.
Search
Provides context sensitive searching
Help
Displays help for either the processing, submodule or event tabs

Submodule context menu

The following context menu opens by right-clicking submodule in the ModuleView:

May 2011
809
Menu item
Description
Cut
Enabled when a sequence or function module has been selected.

Clicking this option retains the selected module. There are now 2
possibilities:
1.) A cut sequence module is deleted from its current position
and inserted into its new position using Paste. The new position
is defined by selecting two other modules after cutting. The
sequence module's name does not change. This method can also
be used to move sequence modules between the processing tab
and event tabs.
2.) A cut function module is deleted from its current position and
inserted to its new position using Paste. The new position is
defined by selecting a sequence module after cutting. The
function module's name does not change. This method can also
be used to move function modules between the processing tab
and event tabs.
Copy
Enabled when a module has been selected that can be copied.

Modules that can be copies are sequence, function, and
submodules.
Paste
Enabled when a module has been copied or cut and one of the
three following cases apply:
1.) A sequence module has been copied/cut and two modules
810

May 2011
have been selected. The sequence module is then pasted

between the two selected modules.
2.) A function module has been copied/cut and a sequence
module has been selected.
3.) A submodule has been copied/cut
Paste inserts the module.
Create extension line

only) have been selected (left-click + SHIFT) that are not yet
connected. A connection between the modules is then
generated.
Create Loop

only) have been selected (left-click + SHIFT). A loop is then
created between the two modules.
Deletes connection
Deletes a connection that has been generated by Create

Extension Line. Two modules must be selected (left-click +
SHIFT).
Delete loop
Deletes a loop that has been generated by Create Loop. Two

modules must be selected (left-click + SHIFT).
Delete Module
Deletes the selected module. A start module may not be

deleted. An end module can be deleted only when an end still
remains.
Create Loop
Enabled when the selected module contains loops. In this case,

a submenu lists the module that has loops. Selecting such a
target module opens a color dialog to select the color of the
loop. Reset sets the loop color to the default.
Show script
Opens a script editor (refer also to the Klicks programming

language).
Module properties
Opens a dialog with the module's properties.
Search
Provides context sensitive searching
Help
Displays help for either the processing, submodule or event tabs

Called by
Opens a dialog that shows where the submodule is used (i.e.

called) in the application.
Module properties
The following dialog

May 2011
811
can be opened in two ways.
Select a module and click module properties from either the module context menu or
the submodule context menu.
Select a module and click Module/Module properties from the ModuleView's main menu.
General tab
To change the module name. Module names can not be changed for start modules, security
modules or event modules.
812

May 2011
Module information
Displays information about the module that has been selected in the management tree.

The module's (hardware) channels, calculation channels or adapter channels
The module's assigned submodules, function modules or successor modules (includes
information on whether these modules are used within the script, or whether they are in
disabled lines only)
Click Print Info to print out this information.
Position
To position the module within the corresponding tab.
2.4.2.6 Channels/Variables
The management tree in edit mode contains the item Channels/Variables. This gives an
overview of the data being used by the application. Information of the data is accessed by
double-clicking an item in the management tree's Channels/Variables.

May 2011
813
The following links provide further information on the individual management tree items:
Channels
Application variables (can become channel variables)
Application lists
Application arrays
Application arrays (3D)
Synchronization variables
Formulary
Adapter channels
2.4.2.6.1 Channels
Channels are available from the hardware connecting processes. Channels are available as
analog, digital and virtual input/output channels.
Open the channel selection dialog by double-clicking the Channels item in the management
tree when in edit mode. The dialog is unavailable in runtime mode.
814

May 2011
All device channels are now accessible that are available within the network. The devices
must be enabled in the DataService. The channel selection dialog lists all the devices
that are enabled in the DataService.
To add a channel, select the channel from the list on the left and either drag&drop it onto
the right list using the mouse or click Add. Select multiple channels clicking channels while
pressing CNTRL+SHIFT.
Select all available channels by enabling the All channels checkbox. To delete channels from
the right list, select the channel from the right list. Then click Remove.
The maximum number of channels that can be processed under your ProfiSignal licence is
displayed at the bottom of the dialog. Only active channels are included in the maximum of
channels. The maximum number of channels also indicates the number of currently active
channels within the application. Once the limit has been reached, the maximum number is
displayed in red.

May 2011
815
No further channels can then be added to the right list via drag&drop or Add. The limit can
however be exceeded by activating a channel that has been inactive during runtime mode.
In this event, the application will end immediately (displaying a message) and will not be
able to be restarted.
The channel limit can also be exceeded by clicking All channels. This also prevents the
application from being started!
Channel selection can also take place within the trend settings dialog. Channels that are
selected here can be displayed in a trend.
The channels that can be assigned to trends are limited to the channels that are
compatible with the trend type. If an incompatible trend is selected, the following message
816

May 2011
appears: Not all selected channels will be added (channel type not allowed or channel has
no value).
2.4.2.6.2 Application variables

Application variables differ to local variables by being valid and available to the whole
application. How variables are organized and accessed is described in Klicks under variables.
Open the applications variable dialog by double-clicking the Application Variables item in
the management tree when in edit mode. The dialog is unavailable in runtime mode.
The following tabs are available: Variables, Lists, Arrays,CubeTabSheet, Sync variables,
Calculation channels, Formulary and Adapter channels. These enable the set up of basic
variables and variables for Lists, Tables/arrays, 3D-tables/3D-arrays, Synchronization
variables, Calculation Channels, Formulas and Adapter Channels.
Setting up basic variables

Click the Variables tab and the Add button. A new line is added with a new variable called
Variable_1.
Left-click the name to enable it to be changed.

May 2011
817
Double-clicking a line opens the following dialog:
The following options are available:
818

May 2011
To change the variable name

To set the variable's starting value when switching to runtime mode
To enter a comment text for the variable
To declare the variable to be a channel variable (which enables further options)
The dialog has the following buttons:

Previous
Available when more than one variable exists on the list in the variable tab, and this
variable is not the first on the list. When clicked, changes will be accepted (when
required) for the current variable and the previous variable on the list will be displayed.
The button is grayed-out when it is the first on the list (variables tab).
Next
Available when more than one variable exists on the list in the variable tab, and this
variable is not the last on the list. When clicked, changes will be accepted (when
required) for the current variable and the next variable on the list will be displayed. The
button is grayed-out when it is the last on the list (variables tab).
OK
Accepts all the changes and closes the dialog.
Abort
Discards all the changes and closes the dialog.
Help
Displays help information for application variables.
Channel variable and settings tab

When as channel variable available is cross-checked, the application variable becomes a
channel variable.
This is an extension to application variables. Application variables are available only within a
script (refer to the Klicks programming language). Channel variables are available also in
visualisation objects, parameter objects and calculation channels. Their values can be
amended within a program. This enables, for example, the output from a calculation channel
to be processed within a script. Channel variables are always basic variables, i.e. not list or
table/array variables.

May 2011
819
A channel variable enables the settings tab. Further settings can then be performed for
the channel variable:
Data type (binary, integer, floating point). The data type remains value unless it is
overwritten by script instruction.
Unit (optional). A unit is useful when the channel variable is to be used in a
visualisation object and the visualisation object has the option channel name
enabled.
Set area of validity, to enter a valid range, i.e. minimum and maximum values.
The Reference tab

The Reference tab lists the modules in which the application variables are used.
820

May 2011
Deleting a basic variable

Select the variable to be deleted (multiple selection possible) and click Delete.
2.4.2.6.3 application lists

Application lists differ to local lists by being valid and available to the whole application.
How lists are organized and accessed is described in Klicks under variables.
Open the application lists dialog by double-clicking the Application lists item in the
management tree when in edit mode. The dialog is unavailable in runtime mode.

May 2011
821
The following tabs are available: Variables, Lists, Arrays,CubeTabSheet , Sync variables,
Calculation channels, Formulary and Adapter channels. These enable the set up of
application variables, list variables, Tables/arrays, 3D-tables/3D-arrays, Synchronization
Adding a list variable

Click the Lists tab and the Add button. A new line is added with a new variable. Left-click
the name to enable it to be changed.
Deleting a list variable

Select the list variable to be deleted (multiple selection is possible) and click Delete.
2.4.2.6.4 application fields

Application arrays/tables differ to local arrays by being valid and available to the whole
application. How arrays/tables are organized and accessed is described in Klicks under
variables.
Open the application lists dialog by double-clicking the Application arrays item in the
The following tabs are available: Variables, Lists, Arrays,CubeTabSheet, Sync variables,
Calculation channels, Formulary and Adapter channels. These enable the set up of
application variables, List variables, array/table variables, 3D-tables/3D-arrays,
Synchronization variables, Calculation Channels, Formulas and Adapter Channels.
822

May 2011
Adding an array/table variable

Click the Lists tab and the Add button. A new line is added with a new variable. Left-click
the name to enable it to be changed.
Deleting an array/table variable

Select the array variable to be deleted (multiple selection is possible) and click Delete.
2.4.2.6.5 Application arrays (3D)

Application arrays/tables (3D) differ to local arrays by being valid and available to the
whole application. How arrays/tables (3D) are organized and accessed is described in Klicks
under variables.
Open the application lists dialog by double-clicking the Application arrays (3D) item in the
The following tabs are available: Variables, Lists, Arrays,CubeTabSheet, Sync variables, Calculation
channels, Formulary and Adapter channels. These enable the set up of application
variables, List variables Tables/arrays, 3D-tables/3D-arrays, Synchronization variables,
Calculation Channels, Formulas and Adapter Channels.
Adding an array/table (3D) variable

Click the CubeTabSheet tab and the Add button. A new line is added with a new variable.
Deleting an array/table (3D) variable

Select the array (3D) variable to be deleted (multiple selection is possible) and click Delete.

May 2011
823
2.4.2.6.6 Synchronization variables

How synchronization variables are organized and accessed is described in Klicks under
variables.
Open the application lists dialog by double-clicking the Synchronization variables item in
the management tree when in edit mode. The dialog is unavailable in runtime mode.
The following tabs are available: Variables, Lists, Arrays,CubeTabSheet, Sync variables, Calculation
channels, Formulary and Adapter channels. These enable the set up of application
variables, List variables, array/table variables, 3D-tables/3D-arrays, Synchronization
Adding a synchronization variable

Click the Sync variables tab and the Add button. A new line is added with a new variable.
Deleting a synchronization variable

Select the synchronization variable to be deleted (multiple selection is possible) and click
Delete.
2.4.2.6.7 Formulary
Formulas are stored within a formulary. Formulas are the computation rules that users can
assign to calculation channels. A formula contains placeholders for variables and channels.
In calculation channels, the placeholders are replaced by actual channels and channel
variables.
Open the application lists dialog by double-clicking the Formulary item in the management
tree when in edit mode. This dialog is unavailable in runtime mode.
How users set a formula is explained using an example.
824

May 2011
Adding a formula
Click the Formulary tab and the Add button. The following dialog opens:

OK
Cancel
Help
When this dialog is closed and reopened later by double-clicking a line in the formulary tab, two
further buttons are available:
Previous
Available when more than one formula exists on the list in the formulary tab, and this
formula is not the first on the list. When clicked, changes will be accepted (when
required) for the current formula and the previous formula on the list will be displayed.
The button is grayed-out when it is the first on the list (formulary tab).
Next
Available when more than one formula exists on the list in the formulary tab, and this
formula is not the last on the list. When clicked, changes will be accepted (when
required) for the current formula and the next formula on the list will be displayed. The

May 2011
825
button is grayed-out when the formula is the last on the list (formulary tab).
Adding an operand
This dialog enables a formula to be assigned. Left click Operand. This opens the following
dialogue:
Click assign new operand name to open a window to enter the name of the operand.
Clicking OK replaces the Operand keyword with a placeholder.
Changing an operand
Left click Operand_1 to open the menu.
826

May 2011
Left click Operand to display a menu with assign new operand name and previously set up operand
names. To change the operand name, either add another operand name or select a
previously set up operand.
Adding a fixed value or file

A fixed value and file name (including path) can be added. Select Constant or File.
Selecting File opens a file selection dialogue.
Creating a formula
To create a formula select Formula.
This menu enables an operand to be added or deleted, and brackets to be added. A

detailed example of adding a formula is available here.
Further operations can also be added. This takes place via the following submenus:

May 2011
827
The following explanations assume that the operand has been assigned x as the operand name.
The natural logarithm ln()

Selecting this option returns an entry in the form of
The natural log ln(x) corresponds to the loge(x), i.e. the logarithm of base e ( Euler's number
2.7182818284590452 ) and is the inverse to the power function of ex . loge(x). It answers the query, how
often must the base e be multiplied by itself to achieve x.
The absolute value abs()
If x is negative, it converts the x sign to +. The function has no effect for positive values above 0.
Differentiation
Formulas are used in calculation channels. This calculation channel assigns a channel to
the x operand. The differentiation function calculates the increase between the previous
computed channel value and the current channel value.
Linearization
Logical operation, not

A 0 value returns a logical false and all other values a logical true. True and false are also
referred to as boolean values. When a logical operation is not assigned a value not equal to
0( i.e. true), the function returns the value 0 (i.e. false). Inversely, an input of 0
(i.e.false ) returns the value 1 (i.e.true). The aim of the function is invert a boolean value's
operands.
828

May 2011
Cube functions
The following functions are available:

The following example assumes that the operand has been assigned x as the operand name.
sqrt (x)
For non-negative values of x, the functions computes the value that returns x when multiplied by itself.
The power function yx

Multiplies base y x-times by itself.
The power function ex

This is the inverse function to natural logarithms. Multiplies base e ( Euler number 2.7182818284590452
) x-times by itself.

May 2011
829
Statistic function
The following statistical functions are available.

Time difference
Counted mean value

Triggered mean value

830

May 2011
Reset mean value

Counted min value

Triggered min value

Reset min value

Counted max value

Triggered max value

Reset max value

May 2011
831
Trigonometric functions
The following trigonometric functions are available:

The angles for all trigonometric functions are given in radians. Angle size is measured by the length of its
arc.
Instead of giving the angel a in degrees, the length of the blue arc serves as the measurement for its size.
The complete angle is given in radians by the circumference of the unit circle, i.e. by 2* pi ( pi equals
832

May 2011
3.1415926535897932384626433832795....),
Conversion between degrees and radians is as follows: If a is an angle measured in degrees, its value in
radians is 2pi a/360. Vice versa, a value in radians requires multiplying by 360/(2Pi) to return an angle
in degrees.
The sin() function
Computes the sine value for the angle x, with the angle being given in radians.
The cos() function

Computes the cosine value for the angle x, with the angle being given in radians.
The tan() function

In a right-angled triangle, the tangent of angle x is the relationship between the "opposite/adjacent" sides.
As a formula: tan(x) = sin(x)/cos(x). The angle x is given in radians.
The asin() function

Arcus sinus is the inverse of sine. asin x is the angle a, for which sin a = x. The angle is given in radians.
The acos() function

Arcus cosinus is the inverse of cosine. acos x is the angle a, for which cos a = x. The angle is given in

May 2011
833
radians.
The atan() function

Arcus tangens is the inverse of tangent. atan x is the angle a, for which tan a = x. The angle is given in
radians.
Functions from DLL

Delphin Technology AG provides a 32-bit DLL enables the input of formulas that utilize user-defined
functions. The DLL is then included in the formulary. For example, using a MyCFunctions DLL (which has
the functions MyAdd and MySub ), these submenu items appear under Functions from DLL.
If these two functions each have two parameters, they will appear as follows:
2.4.2.6.7.1 Adding a formula to the formulary

The method is explained using an example.
The example formula computes the temperature difference, as a percentage, between
internal and outside temperatures.
(Outside Temperature Internal Temperature)
%Temp.difference = -------------------------------------------- * 100
(Outside temperature + Internal temperature)/2
Method:
Double-click formulary, from the management tree.
834

May 2011
The Formulary tab is enabled.

Left-click Add.
Now enter a name for the formula and begin to form it.
This is best done in the following order:
Add all the operands and constants required by the formula
Select the required arithmetic operators and connections
Select placeholder names for the operators
Add brackets
(Outside Temperature Internal Temperature)
%Temp.difference = --------------------------------------------- * 100
(Outside temperature + Internal temperature)/2
Adding operands and constants

May 2011
835
Operands are added using the menu above.
The number of required operands have been added.

The two last operands are now replaced by constants. Left-click an operand that is to be
replaced by a constant.
836

May 2011
The two last operands have been replaced by the constants 2 and 100.
Adding operators

May 2011
837
The
+/- keywords are replaced with operators by left-clicking on a +/-. From the menu
select the required operator. This produces the following dialog:
Adding brackets
The left bracket is positioned first by selecting the operand that is to follow the left
bracket.
838

May 2011
Left click opens the menu:
Select Add brackets to give the following entry:
The bracket is displayed in bold because it has not yet been closed with a right bracket.
The right bracket is now positioned by selecting the operand that comes before the right
bracket. Left click opens the menu: Select Add brackets to give the following entry:
The bracket pair is closed by selecting the variable that follows the right bracket and
selecting Add brackets. Brackets are also inserted from the third operand to the constant

May 2011
839
2.
Finally, the third and fourth operands are bracketed.
The
operands are now replaced by placeholders.
Left click each operand to display the following menu:
Select assign new operand name. An input dialog opens to enable the input of an operand
name. For the first operand, select a name for the outside temperature
840

May 2011
This produces the following entry:
Operand names used in the formula are listed in the menu and can be selected for other
operands.
The other placeholders are similarly added.
The formula for the formulary is then complete.

May 2011
841
User friendly and in just a few mouse clicks.
2.4.2.6.8 Calculation channels

Calculation channels provide functions and/or mathematical and logical operations.
Calculation channels enable the mathematical linking of channels, constants, channel
variables and other calculation channels. A calculation channel outputs a calculated
channel which can be processed like a hardware channel with analog and digital data.
Calculation channels can then be used in ProfiSignal function blocks (e,g, scripts,
visualisation objects, trends etc.) .
Open the calculation channels dialog by double-clicking the Calculation channels item in
the management tree when in edit mode. This dialog is unavailable in runtime mode.
Calculation channel properties
Open an application context menu in the management tree and select Calculation channel
properties. This opens the following dialog.
842

May 2011
auto calculation
Automatically computes the calculation channels.
calculation interval
Only available when auto calculation is cross-checked. The interval is the time between
two calculations. For example, a calculation channel can be re-computed every 1000
milliseconds.
max. digits
The number of digits following a decimal point (i.e. decimal places).
Adding a calculation channel

Click the Calculation channel tab and the Add button. This opens the calculation channel
dialog.
Script
2.4.2.6.8.1 Adding a calculation channel

Open the calculation channels dialog by double-clicking the Calculation channels item in
the management tree when in edit mode. This dialog is unavailable in runtime mode.

May 2011
843
The following settings can then be made.

Enable/disable calculation channel. A disabled calculation channel will not perform any
calculations.
Naming a calculation channel.
Setting the type of calculation channel (binary, integer or floating point). The data
type remains unless it is overwritten by a script instruction.
Inputting a unit (optional). A unit is useful when the channel variable is to be used in
844

May 2011
a visualisation object and the visualisation object has the option channel name
enabled.
Entering a valid range, i.e. minimum and maximum values.
Entering a comments text.
Entering a tolerance. When a calculation channel has computed a new value the
Da ta Se rv ice saves the new value only when it deviates from the previous value by the
tolerance entered here. A value of 0 is recommended.
OK
Cancel
Help
When this dialog is closed and reopened later by double-clicking a line in the formulary tab, two
further buttons are available:
Previous
Available when more than one channel exists on the list in the calculation channel tab,
and this channel is not the first on the list. When clicked, changes will be accepted
(when required) for the current channel and the previous channel on the list will be
displayed. The button is grayed-out when the channel is the first on the list (Calculation
channels tab).
Next
Available when more than one channel exists on the list in the calculation channel tab,
and this channel is not the last on the list. When clicked, changes will be accepted
(when required) for the current channel and the next channel on the list will be displayed.
The button is grayed-out when the channel is the last on the list (Calculation channels
tab).
To create a channel select either an existing formula from the formulary or click New to
create a new formula.

May 2011
845
The formula contains placeholders for the channels and variables. These are available under
a variable list. Placeholders in calculation channels are replaced by actual channels and
channel variables (click no channel or a previously selected channel).
The Reference tab contains all the channels that can be used by this calculation channel.
Also listed are all the ProfiSignal elements such as trends, adapter channels or modules in
which the calculation channel is used.
2.4.2.6.9 Adapter channels

Adapter channels enable independence to be established between the measurement
hardware and ProfiSignal software.
This happens by using adapter channels to adapt connections between the hardware
channels and applications without having to make any amendments to the application
software. This adaptation takes place via configuration of adapter channels (refer also the
Klicks programming language).
Open the Adapter channel dialog by double-clicking the Adapter channels item in the
management tree when in edit mode. This dialog is unavailable in runtime mode.
846

May 2011
Adding an adapter channel

Click the Adapter Channels tab and the Add button. The following dialog opens:
The following settings can then be made:

May 2011
847
Name change.
Default value input. The default value the adapter channel is given when being
switched to runtime mode.
Comment text input.
Source channel selection.
If use source channel settings is enabled, the settings are used from the source
channel's settings tab. Otherwise settings can be made for type, unit, valid range
and writeability.
Previous
Available when more than one channel exists on the list in the adapter channel tab, and
this channel is not the first on the list. When clicked, changes will be accepted (when
required) for the current channel and the previous channel on the list will be displayed.
The button is grayed-out when the channel is the first on the list (adapter channels
tab).
Next
Available when more than one channel exists on the list in the adapter channel tab, and
this channel is not the last on the list. When clicked, changes will be accepted (when
required) for the current channel and the next channel on the list will be displayed. The
button is grayed-out when the channel is the last on the list (adapter channels tab).
OK
Cancel
Help
The data type remains unless it is overwritten by a script instruction. Unit (optional) A unit
is useful when the channel variable is to be used in a visualisation object and the
visualisation object has the option channel name enabled.
The Reference tab lists the modules, adapter channels and trends in which the adapter
channels are used.
Script
848

May 2011
2.4.3
The Klicks programming language
Pro fiSig nal includes the Klicks automation language. It does not require users to learn an
instruction set or to input instruction code. This avoids syntax errors occurring and enables
users to convert complex procedures into clear structure charts at just a few clicks of the
mouse. The integrated script language and its components are described step-by-step in
the following sections.
The automation language is available only with Pro fiSig nal Klicks.
This section contains information on the following:
Script window
Main menu
Creating and editing script code
Key words
Normal and extended modes
Object hierarchy
Script action
Context menus for script objects
Script search
Detailed information on the script language's components are available under:

Variables
Formula
Question
Assign
Control
Initiate
Configurate
The script window

A Module View's modules represent containers for the programming code. To enter Klicks
instructions requires opening of the script window. Opening can take place in the edit mode
as follows:
Double-click a module in the ModuleView.

May 2011
849
Right-click the module name in the management tree. From the context menu select
Show script.
In runtime mode the script window can be opened only by double-clicking the module.
A module with no programming code appears as follows:
The window shows:

A title line in which the user may enter the names of the project, application and
module.
A main menu.
The editing area for entering the programming instructions.
Scrollbars.
A status bar giving the total number of program lines.
Two lines of script. The first contains the the type of module (in the example a start
module) and its name. The second line ends the script and is identified as Module
End. These two lines may not be deleted from the script!
The main menu.

In edit mode the main menu has three options. Help opens the Klicks help function, and
Print opens the printer dialogue. Clicking Edit opens the following menu.
850

May 2011
In runtime mode the script may not be edited so only the options Help and Print are
available.
Info:
1. The first line of a script contain the module type (e.g. start module) and its name.
The final line ends the script and is identified as Module End. Users may neither delete
nor copy these two lines!
2. The majority of instructions are associated with multiple selections. There are
several methods for selecting multiple lines of script:
To select a group of associated lines of script, first click on the group's opening line.
Then, while holding down the SHIFT key, click on the group's closing line.
To select lines that are not associated with each other, hold down the CTRL key and
click each line to be selected one after the other.
Name
Keyboard
short-cut
Description
Undo
Ctrl+Z
Redo
Shift+Ctrl+Z
Cut
Ctrl+X
Copies the selected lines to the clipboard and

deletes them from the script
Copy
Ctrl+C
Copies the selected lines to the clipboard
Paste
Ctrl+V
Inserts clipboard content into the script
Delete
Del
Deletes the selected lines from the script
Print

May 2011
Prints out the script window
851
Creating and editing lines of script

Lines of script can be generated in edit mode. Right-click the line above which the new
line is to be inserted. The following context menu appears.
The Script option

Selecting this option opens a submenu.
This submenu is used to create lines of script. Script lines are categorized under the
following:
Variables
Formula
Question
Assign
852

May 2011
Control
Initiate
Configuration
The Edit option

Selecting this option opens a submenu.
Info:
1. The first line of a script contain the module type (e.g. start module) and its name.
The final line ends the script and is identified as Module End. Users may neither delete
nor copy these two lines!
2. The majority of instructions are associated with multiple selections. There are
several methods for selecting multiple lines of script:
To select associated lines of script click on the first line. Then, while holding down the
Shift key, click on the group's closing line.
To select lines that are not associated with each other, hold down the CTRL key and
click each line to be selected one after the other.
3. Lines can be moved by marking the lines to be moved and dragging using the mouse
them to the required location.
4. Lines can be copied and inserted at the required position by selecting the lines to be
copied, holding down the Ctrl key and then dragging them to the required position.
Name

May 2011
Keyboard
short-cut
Description
853
Activate Line
Ctrl+F2
Activates or deactivates the selected lines.
Undo
Ctrl+Z
Redo
Shift+Ctrl+Z
Cut
Ctrl+X
Copies the selected lines to the clipboard and

deletes them from the script
Copy
Ctrl+C
Copies the selected lines to the clipboard
Paste
Ctrl+V
Inserts clipboard content into the script
Delete
Del
Deletes the selected lines from the script
Print
Prints out the script window
A line is considered active when it can be performed during runtime. For example, in runtime
the following Assign would assign a fixed value of 1 to a Local Variable.
A line is considered deactivated when it is ignored during runtime. These lines are struckthrough as in the following example.
The Info option

There is an option to insert information lines into the script to provide in-script
documentation. To set up such a line, select Info from the context menu. This opens the
following input dialogue.
854

May 2011
Users can now enter the required information. Clicking OK ends the dialogue and the info
line is entered as shown in the following example. Clicking Cancel closes the dialogue with
no info line being added.
To amend an infotext, left-click the line to re-open the dialogue and display the line.
The Log-Info option
To enable the output of information to a runtime log window, select Log-Info from the
context menu. This provides the following line:
Log-Info: Object
Object is a placeholder or key word. Key words are always displayed as red underlined. A
script line displaying such a key word is then incomplete. The application to which it
belongs can not then be run. To complete a line, all key words need to be replaced with
real content.
Log-info input is saved to a log file. If your project is named Project_1 and the application
Application_1, the log-info input is saved to a file named Project_1_Application_1.log. This
file is then located in the ProfiSignal's Log directory.

May 2011
855
The Empty line option
This enables the insertion of blank lines into the script. This helps to group lines together
making them easier to read.
The Help option
This displays help for the context menu currently open.
Key words
Adding a line of script generates an instruction core that contains placeholders. If, for
example, you wish to assign a value via Script>Assign>Value, you get the following line:

Object is a placeholder or key word. Key words are always displayed as red underlined. A
script line displaying such a key word is then incomplete. The application to which it
belongs can not then be run. To complete a line, all key words need to be replaced with
real content. For example, the line could be completed by assigning a Local Variable called
Variable_1 with a value of 1.
Assign Value: LVVariable_1 = 1
Normal and extended modes
The script uses two modes: a normal mode and an extended mode. The extended mode
provides an added set of object functions. The extended mode is intended for experienced
users. The programming options in the extended mode may confuse beginners.
Switching between normal and extended modes takes place via the script editor's context
menu. This context menu has the option Extend Menu. The option is enabled when it is
displayed as checked.
856

May 2011
Alternatively, users can click the options Settings/Global settings to open a settings
dialogue. The required settings can then be taken via the Script editor tab.
Object hierarchy
A line of script contains not only the name of the actual object (Drop down box_1in the
following example), but also the type and components that belong to the object. If there
are groupings, these will also be shown. In such an event, we say that the object
hierarchy is displayed.
Example of a shown hierarchy:
Initiate Visualisation\VisusView_1\Drop D.Drop down box_1: Add item(In: Name\Objekt, Value

\Objekt Out: LVResult)
This display method has the advantage of describing exactly how a line of script has been
generated. The menu structure is clearly portrayed within the line of script.

May 2011
857
If a compact form is required, the object hierarchy can be hidden.
Example of a hidden hierarchy:
Initiate Drop down box_1: Add item(In: Name\Objekt, Value\Objekt Out: LVResult)
Users can switch between the two display methods. This is possible via the keyboard
shortcut Ctrl + Alt + H, or by opening the settings dialogue via Extras/Global settings /
Show hierarchy. The Script Editor tag then enables users to show/hide the hierarchy.
Line actions
A line of script normally contains the type of instruction to which the line is classified. For
example, when a line involves assigning a value to a variable, the action Assign Value
appears at the beginning of the instruction.
Example of a shown action:
Assign Value: LVVariable_1 = 1

This display method has the advantage of clearly showing what action is being performed in
the line. If a compact form is required, the action can be hidden.
Example of a hidden action:
LVVariable_1 = 1
858

May 2011
Users can switch between the two display methods. Open the settings dialogue via
Settings/Global settings /Action visible. The Script Editor tag then enables users to show/
hide the action.
Context menus for script objects

When adding a new line of script in edit mode, an instruction core is provided. For example,
selecting Script>Question>If...then generates the following instruction core.
Left-clicking different sections within the instruction core opens context menus. The click
can be on a bracket, an arithmetic operator or a keyword (red underlined). Sections that
appear bold blue are assigned context menus (excluding the first and last lines of a script).
These provide just the types and names of modules or ends them.
Script lines can be generated using the context menus as well as being subsequently
altered. There are context menus that are assigned to just one, or very few, actions.
These context menus are opened when requiring help for the corresponding action.
Information on context menus is available (here).
Script search
There are two methods in ProfiSignal to search a script. First, by using a search dialogue.
Second, in edit mode there is a search option in the context menus for
constants (fixed values, dates, text, color),
variables
VisuView, ParameterView or Report objects and for
a ModuleView's modules.
The context menu search starts a context sensitive search.

May 2011
859
2.4.3.1 Question
Questions provide Klicks with conditional instructions. These are instructions that are run
only under specific conditions. This enables the program flow to be controlled so that
different actions can be programmed for different conditions and/or data input. Questions
can be entered or amended only in edit mode.
If...then
else if...then
If not then
If the first time then
If not the first time then
If...then Repeat
If...then
Selecting Script
Question
If...then generates the following instruction core:
Question: If (Object <>= Object) then

Question End
If the condition within the brackets is true then all the instructions within the If then and
Question End are performed.
The most basic condition is made up of two operands and one comparison operation. Leftclicking the key words opens context menus with options for replacing the key word.
Question: If (LVVariable <> 111) then

Question End
Left-clicking
then
then opens a context menu that enables the adding of further conditions.
Add condition
Question: If (LVVariable <> 111) logic (Object <>= Object) then

Question End
Left-clicking the logic key word displays a context menu that enables selection of a logical
connection (and / or / xor) or the deletion of a left or right subcondition.
Left-click logic
and
or
xor
Delete right condition
Delete left condition
Left-clicking and opening bracket displays the following menu to
860

May 2011
delete the brackets around a subcondition (the outermost pair of brackets remain),
negate the subcondition.
Left-click opening bracket
Add negation
Delete Brackets
Adding formulae and other brackets provides additional options in the bracket context
menu.
Left-clicking an opening bracket displays the following menu to
negate the subcondition,
add a new variable to the left of the bracket.
Add negation
Delete Brackets
Create new variable (to the left)
Left-clicking a closing bracket displays the following menu to

add a new variable to the right of the bracket.
Create new variable (to the right)
else if...then
This instruction is available only at a Question End line. Selecting Script>Question>else
if...then generates the following instruction core:
Question: If(Object <>= Object) then

Question: else if(Object <>= Object) then
Question End
The condition in the else if then line will then be performed only when the condition in
the If then is false. If the bracketed condition in the else if then is true, then every
instruction between else if then and Question End is performed.
If not then
This instruction is available only at a Question End line. Selecting Script>Question>If not
then generates the following instruction core:

Question: If not then
Question End

May 2011
861
If the condition is true then the instructions between If then and If not then are
performed. If the condition is false then the instructions between If not then and Question
End are performed.
If the first time

It is available only at a Question End or If not then line. Selecting Script>Question>If the
first time generates the following instruction core:

Question: If the first time then
Question End
Question End
If the condition is true for the first time, the instructions between If the first time then and
its corresponding Question End are performed.

Question: If the first time then
Question End
Question End
If the condition is false for the first time, the instructions between If the first time then
and its corresponding Question End are performed.
If not the first time then

It is available only at a Question End or If not then line. Selecting Script>Question>If not
the first time generates the following instruction core:

Question: If not the first time then
Question End
Question End
If the condition is true more than once, the instructions between If not the first time then

Question: If not the first time then
Question End
Question End
862

May 2011
If the condition is false more than once, the instructions between If not the first time then
If...then Repeat
Selecting Script>Question>else if...then generates the following instruction core:
Question: If(Object <>= Object) then Repeat

Question End
If the condition within the brackets is true then all the instructions within the If then
Repeat and Question End are performed.
2.4.3.2 Context sensitive search

Left-clicking an object mode in a script edit mode or in one of the four views (VisuView,
ParameterView, ModuleView or Report) opens a context menu for performing a search for
other occurrences of the object.
Context sensitive searching in scripts

Left-clicking a constant value (fixed value, date, text, color) in edit mode opens a
context menu which contains a Search option. This opens the following menus.

May 2011
863
The Search option pop-up window lists all the values in the project. Each entry is made
up of three elements separated by a slash. The first element names the application, the
second the module and the third the script's line number.
Clicking an entry opens the corresponding script window and selects the line of script.
A local variable search searches only the script from which the context menu was
opened.
Left-clicking an object assigned to one of the four views opens a context menu with a
Search option. This opens the following menus.
The Search option pop-up window lists all the values in the project. Each entry is made
There is also a Go to option. Clicking this option opens the corresponding view and
selects the object.
Context sensitive searching in views

Right-clicking an object in a view in edit mode opens a context menu which contains a
Search option. Clicking this option opens the following menus.
The Search options pop-up window lists all the objects in the project. Each entry is made
864

May 2011
Right-clicking the background of a view opens a context menu with a Search option. This
opens the following menus.
The Search option pop-up window lists all the occurrences of the view within the project.
Each entry is made up of three elements separated by a slash. The first element names
the application, the second the module and the third the script's line number.
Context sensitive searching in ParameterView

Right-clicking a parameter-object in a ParameterView in edit mode opens a context menu
which contains a Search option. This opens the following menus.
The Search option pop-up window lists all the occurrences of the parameter object in the
project. Each entry is made up of three elements separated by a slash. The first element
names the application, the second the module and the third the script's line number.
Context sensitive searching in ModuleView

May 2011
865
Right-clicking a module in a ModuleView in edit mode opens a context menu which

contains a Search option. This opens the following menus.
The Search option pop-up window lists all the occurrences of the module in the project.
Each entry is made up of three elements separated by a slash. The first element names
the application, the second the module and the third the script's line number.
Context sensitive searching in Report

Right-clicking a report-object in Report in edit mode opens a context menu which contains
a Search option. This opens the following menus.
The Search option pop-up window lists all the occurrences of the report object in the
project. Each entry is made up of three elements separated by a slash. The first element
names the application, the second the module and the third the script's line number.
866

May 2011
2.4.3.3 Search dialogue

Select Search>Search in Script ... from the main menu. This opens the following dialogue:
Enter your search term in the Search for field. The systems remembers the previous 20
search terms and can be re-selected from the dropdown list.
The following entries can be made for the Search.
The Search scope
Determines the scripts that are to be searched.

May 2011
867
Project
Determines whether the search is performed on all open projects or just one specific
project. Select All Projects to search all project module scripts (e.g. Start and End).
Further search limitations within the search scope are then not possible.
Application
If a specific project is selected under Project, then either all applications or a specific
application can be selected here.
Module
If a specific application is selected under Application, then either all modules or a specific
module can be selected here.
Options
Match case
When checked the search will take account of the search term's upper and lower case.
Whole words
When checked only complete matches of the the search term will be returned. When
unchecked even partial matches of the the search term will be returned.
Use Wild Cards
When checked the search will take account of wild cards ( *, ^ and $ ). The ^ symbol
can be placed only at the beginning of the search term and indicates that search results
must begin with the character/symbol that directly follows the ^ symbol. To return
searches that end in a specific character/symbol, place a $ directly following the required
character/symbol. The * symbol stands for any number of any character.
Example: The user is searching variables and there are the local variables Row and
Column.
Using the search term * returns both variables.
Using the search term R* returns only Row.
Using the search term ^R returns only Row.
Using the search term n$ returns only Column.
Extended Options
868

May 2011
Extended Options enables even greater accuracy for search results. The following options
are available:
Variables
Searches only local variables, application variables and synchron variables but does not
distinguish between simple variables, list variables, tables and 3-D tables.
Channels
Searches channels.
Components and Properties
Searches the component name (e.g. LED_1) of a VisuView, ParameterView or Report.
Component properties are then also searched (e.g. visible).
Constant values
Searches for the entered constant values.
Module, project, application call
Searches the names of modules, applications or projects.
Object Function
Searches the names of object functions.
Expressions
Searches lines of script that contain the input search text. For example, to search for
lines that assign a value to the application variable start_runtime, enter the search text
AVstart_runtime =.
After entering the above, users can start the search by clicking Search. Search results are
output as a list with each item on the list representing one search hit. Double-clicking a line
or selecting a list line and clicking Open Script opens the script in which the search term
has been found with the relevant line being marked.
Each item in the list contains the following information:
Project
Application
Module
Object-Name/ Value
Type

May 2011
The project in which the search term has been found.

The application (in the project) in which the search term has
been found.
The module (in the application) in which the search term has
been found.
Name of the found object/value. This need not be the same as
the search term when match case and whole words have not
been checked.
The type of found object:
- local variable
- local list
- local table
- local 3D-table
- application variable
869
Line
- application list
- application field
- application 3D table
- synchron variable
- analog input
- analog output
- digital input
- digital output
- counter
- calculation channel
- adapter channel
- com
- channel variable
- visu component
- visu property
- param. component
- param. property
- report component
- report property
- constant
- info
- object function
- subsequent module
- implied subsequent (automatic subsequent that does not
appear in the script! )
- function module
- submodule
- Project
- Application
- VisuView
- ParameterView
- Report
- Object type
The module line in which the search term has been found.
Info:
The search is for objects whose names match - partially or completely - the search
term. Search terms are not evaluated. An example: If a script contains the line Assign
Value: LVVariable1 = 1, a search on "Variable1 = 1" will not return a hit because the
search term refers to an expression (an assign) and not to a local variable.
Refer also to Context sensitive searches
870

May 2011
2.4.3.4 Context menus

Context menus appear when users left-click elements within a line of script while in edit
mode. The menu depends on the clicked object. The menus are therefore known as
context-dependent menus, or context menus for short. The content of these menus not
only depends on the clicked object but also on the position of the object within the line of
script. The following Assign line is provided as an example.
Assign Value: LVObject = Object

Left-click the left
Object key word to open the following context menu.
Left-click the right key word to open a more extensive context menu.
The reason for the difference in menus is that there must be something to the left of an
Assign to which something can be assigned. It makes no sense, for example, to enter a
constant of 1 on the left of the Assign because it is not possible to assign anything to the
value of 1.
This section explains the following context menu options:
Variable

May 2011
871
Boolean value
Channel
Visualisation
Parameter input
Report
Formula
Constant
Date / Time
Colour
File
Search
Variable
In extended mode the following context menu is displayed.
It enables user to add, rename or select local variables. Previously added application
variables can also be selected via a dropdown list. In normal mode the four application
variable types are directly integrated into the context menu.
872

May 2011
This is not so in the extended mode because this mode is intended for advanced users who
develop more complex applications with many more application variables. Selecting from a
dropdown list is therefore much easier because it has
a scrollbar for quick navigation through the list
an input dialogue to enter variable names. The first entry in the list is automatically
selected that matches the input.
Boolean value
If an Assign or Question instruction contains a left Object that is assignable to a boolean
value (e.g. a digital output), the context menu then has two special options for On and
Off.

May 2011
873
Channel
Select Channel in extended mode to display the following context menu.
In normal mode the Calculation channel and Channel variable options are hidden.
874

May 2011
Not every channel type is always available. For example, opening the context menu for the
left Object in the line
Assign Value: LVObject = Object

displays only the following channel types:
This is because it is not possible to assign a value to a calculation channel, which

calculates values, or to digital or analog input.
Left-click a channel type to open a dropdown list to select the channel/channel properties
matching the type. There are more options in extended mode.
C
Mode
h
a
n
n
e
l
n
a
m
e
o

May 2011
Description
875
r
c
h
a
n
n
e
l
p
r
o
p
e
r
t
i
e
s
C
Normal/extended
h
a
n
n
e
l
n
a
m
e
Access to the ChannelName value.
C
Extended
h
a
n
n
e
l
n
a
m
e
.
C
h
a
n
n
e
l
I
D
Access to the ID of the Channel name value.
C
Extended
h
a
Access to the Active property of the calculation channel named

ChannelName.
876

May 2011
n
n
e
l
N
a
m
e
.
A
c
t
i
v
e
C
Extended
h
a
n
n
e
l
N
a
m
e
.
A
d
a
p
t
e
r
c
h
a
n
n
e
l
I
D
Accesses the ID that is assigned to the channel which refers to the

adapter channel named ChannelName.
C
Normal/extended
h
a
n
n
e
l
N
a
m
Access to the IsWriteable property of the adapter channel named

ChannelName.

May 2011
877
e
.
I
s
W
r
i
t
e
a
b
l
e
C
Normal/extended
h
a
n
n
e
l
N
a
m
e
.
U
n
i
t
Access to the Unit property of the adapter channel named

ChannelName.
C
Normal/extended
h
a
n
n
e
l
N
a
m
e
.
N
a
m
e
Access to the Name property of the adapter channel named

ChannelName.
Visualisation
Select this option to display context menus that enable access to VisuView and/or VisuObject properties. More information on properties can be found in Visu-Object.
878

May 2011
Parameter input
Select this option to display context menus that enable access to ParameterView and/or
Parameter-Object properties. More information on properties can be found in ParameterObject.
Report
Select this option to display context menus that enable access to Report and/or ReportObject properties. More information on properties can be found in Report-Object.
Formula
Select this option to display context menus that enable the creation of formulae.
Constant
Click the Constant option for key words (displayed as red underlined)
or for a constant value
to open the following empty dialogue:
This dialogue may contain an initial value when the context menu has been opened for a
constant value.

May 2011
879
The dialogue then appears as:
Any constant may be entered.
The As Text button

Click this button to treat the input as text. The input will then appear within quotes in the
line of script.
Assign Value: Object = '122'

The OK button
Click this button to treat the input as numerical and to write the input to the script as
numeric. Inputting 11,3456 returns the line
Assign Value: Object = 11,3456

Prefix the input with 0x to enter hexadecimal values. For example, an input of oxABC writes
the corresponding decimal value to the script.
Assign Value: Object = 2748

If the input can not be recognized as being numeric, it will be portrayed in quotes.
Assign Value: Object = '122 mV'

The Cancel button
Click this button to close the dialogue and ignore any changes. The line of script then
remains unchanged.
Date / Time
Click this option to open a dialogue to enter date and time information.
880

May 2011
The Absolute tab
This tab enables direct selection from a calender of date and time information. The
following applies:
Click > to display the next month.
Click < to display the previous month.
Click on a day to select the day.
A time can be entered at the lower part of the calender. Mark by left-clicking the hour/
month/second areas.
The time can be altered using the keyboard or
symbol.
Click OK to accept the date /time into the line of script.
Assign Value: Visualisation\VisuView_1\TextIn.Date = 19.05.2011 10:50:16

The Now button inserts a placeholder named NOW in the script.
Assign Value: Visualisation\VisuView_1\TextIn.Date = NOW

The NOW placeholder is then replaced by the current time each time the script runs.

May 2011
881
The Relative tab
Use this tab to adjust a date by a specific time interval.

Example: A script requires the date from five days ago.
First generate the following line of script:
Assign Value: Visualisation\VisuView_1\TextIn.Date = NOW - Object

Left-click Object and select Date / Time from the context menu and then the Relative tab.
Enter 5 against the date and click OK. This returns the following line:
Assign Value: Visualisation\VisuView_1\TextIn.Date = NOW - 5 00:00:00,000

that will determine the required data.
Colour
Click this option to open a dialogue to select a colour.
882

May 2011
Click OK to enter the colour into the script as a whole number value.
File
Click this option to open a file selection dialogue. Select a file and click Open to write the
file name and path to the line of script.
Search
To perform a context sensitive search.
2.4.3.5 Variables
Three different types of variables are used in Pro fiSig nal's Klicks script language. Adding
and selecting variables is possible only in edit mode.
Local variables
Local variables are those variables that can be used only in the scripts in which they are

May 2011
883
added. There are four types of local variable:

basic local variables
local lists
local tables
local 3D tables
The variables can be added via a range of context menus. Select Script>Assign>Value to
generate the following instruction core:

Left-click the Object key word to open the following menu. Previously added variables of
the same type are also displayed here with unused variables listed in the Not used variables
submenu.
Select Add new variable from the Local variable submenu to display an input dialogue for
assigning a name to the new basic local variable. Enter Variable and click OK to return the
following instruction core.
Assign Value: LVVariable = Object

In the same way users can add local lists,
Assign Value: LVLists[Index\Object] = Object

local tables
Assign Value: LV7[column\Object, row\Object] = Object

or 3D tables
884

May 2011
Assign Value: LV3D table[X\Object, Y\Object, Z\Object] = Object

Left-click the local variable of a script line to display a context menu with options to
rename or delete the variable. Application variables may also be selected.
Application variables
Application variables are those variables that are valid for the application in which they
were added. There are four types of application variable:
application variables
application lists
application fields
application 3D tables
These variables are added via application data. Application variables are selected via a
range of context menus. Select Script>Assign>Value to generate the following instruction
core:

Left-click the Object key word to open the following menu. The menu displays previously
added variables of the same type, up to a maximum of 15 application variables.

May 2011
885
When there are more than 15 application variables available, the following menu is
displayed.
Click the Application variable option to open the following dropdown list.
This method of selection provides a clearer overview when there are multiple application
variables available. There is also an input field for entering names that enables fast
selection of the required variable. However, this method does not allow opening of the
context menu for adding variables. The method is then the same as described for
application data.
Select an application variable to return the following instruction core.
886

May 2011
Assign Value: AVVariable1 = Object

In the same way, users can add application lists,
Assign Value: AVLists[Index\Object] = Object

application fields
Assign Value: LVtable[column\Object, row\Object] = Object

or 3D application tables.
Assign Value: AV3D table[X\Object, Y\Object, Z\Object] = Object

Local variables may also be selected via this menu.
Synchron variables
Synchron variables are required when calling a function module. Select
Script>Control>Call>Functionprocedure>[name of function procedure] to generate the
following instruction core with Name being replaced by the name of the function .
Control Call: Module\Parallelmodule.Name(Sync)

To select a synchron variable left click the Sync key word and select the Sync. Variable
option from the context menu. A dropdown list of the available synchron variables will
appear. Adding synchron variables takes place via application data (synchron variables).

May 2011
887
2.4.3.6 Formula
Pro fiSig nal has an option in edit mode to generate mathematical formulae. Many of the
context menus contain the Formula submenu option.
The above menus appear when left-clicking the right Object key word in the following line
of script

and then clicking the Formula submenu. The examples in this section use the following line
of script:
Assign Value: LVResult = LVValue1
Info:
1.) Left-clicking the left Object of an Assign does not provide the Formula option. This is
because it is not possible to assign a value to a formula!
2.) In Pro fiSig nal the result of a computation is affected by the types of operands.
An example using the computation 25/100*2: All operands are whole numbers (also
referred to as integer values). The result of this computation may appear to be 0.5 . In
fact, the result is 0. The reason for this is that the result of a computation is always a
888

May 2011
whole number when all operands are whole numbers. The result from25/100 is therefore
rounded up to the a whole number. 0.25 to the next whole number is therefore 0. A
result with floating-point decimals would be returned by writing the computation as
25.0/100*2. The same effect may take place when using variables. To avoid the
problem, assign a data type to the variable.
A range of procedures can be performed via the menu:

create new variable (to the right)
create new variable (to the left)
delete Variable
add brackets
delete brackets
more operations
Adding brackets returns, for example, the following line of script:
Assign Value: LVResult = (LVValue1 + LVValue2)

Left-click the opening bracket to display the following context menu:
A range of procedures can be performed via the menu:

Add negation
Removes previous added brackets
create new variable (to the left)
Left-click the closing bracket to display the following context menu:
Via this menu, the following function can be performed.

create new variable (to the right)

May 2011
889
2.4.3.6.1 Create new variable (to the right)
Adds a new variable to the right of a variable . For example, in the line

clicking Value1 and create new variable (to the right) generates the following line of script.
Assign Value: LVResult = LVValue1 +/- Object

Adding a new variable also adds a
following menu,
+/- key word next to it. Clicking this key word opens the
for selecting an operation.
Info:
1. Operations can give unexpected results when variables contain strings. This is
because not all operations are definable for strings. The + operation on two strings joins
them together. Multiplying two strings is not possible and returns only the left variable
as a result.
2. Numerics that require, for example, to be multiplied but have been entered as strings
via input fields firstly require writing as variables. These variables are then assigned data
types that are valid for the required operation. The variables can then used in the
required formula.
890

May 2011
2.4.3.6.2 Create new variable (to the left)
Adds a new variable to the left of a variable . For example, in the line

clicking Value1 and create new variable (to the left) generates the following line of script.
Assign Value: LVResult = Object +/- LVValue1

following menu,
Info:
as a result.
via input fields firstly require writing as variables. These variables are then assigned data
types that are valid for the required operation. The variables can then used in the
required formula.

May 2011
891
2.4.3.6.3 Delete Variable
Deletes a variable provided it is not the final variable . In a line of script such as

this instruction therefore has no effect.
2.4.3.6.4 Add brackets
Enables the addition of valid and logically correct pairs of brackets . Brackets can not be
added, for example, when the left and right brackets of the bracket pair are on differing
sides of a comparison operation (e.g. >, <).
Using the following line of script as a basis:
Assign Value: LVResult = LVValue1 + LVValue2

To add brackets select Add brackets for Value1 to position an opening bracket immediately
before it. This returns the following line:
Assign Value: LVResult = (>LVValue1 + LVValue2

The (> symbol indicates that a closing bracket is missing. To add the closing bracket
select Add brackets for Value2 to position an opening bracket immediately after it. This
returns the following line:
2.4.3.6.5 Delete brackets
Deletes a previously inserted pair of brackets .
892

May 2011
2.4.3.6.6 Add negation
Click an opening bracket and select Add negation to negate the contents of a bracket pair
. However the option has an effect only for brackets that contain a comparison
operation. This is because the bracket expressions in such cases are either true or false
enabling them to be negated (or reversed). The negation results in true becoming false and
vice versa.
In a line of script such as

the instruction has no effect. For a Repeat instruction (refer to Control)
Control: Repeat while (LVValue1 > LVValue2)

it is possible to apply the option.
Control: Repeat while not (LVWert1 > LVWert2)

Click not to open a submenu to remove the negation.
2.4.3.6.7 Create new variable (to the left of the bracket)
Adds a new variable to the left of the opening bracket . For example, in the line

clicking the opening bracket and create new variable (to the left) returns the following line.
Assign Value: LVResult = Object +/- (LVValue1 + LVValue2)

following menu,

May 2011
893
Info:
as a result.
via input fields, firstly require writing as variables. These variables are then assigned
data types that are valid for the required operation. The variables can then used in the
required formula.
2.4.3.6.8 Create new variable (to the right of the bracket)
Adds a new variable to the right of the closing bracket . For example, in the line

clicking the closing bracket bracket and create new variable (to the right) returns the
following line.
Assign Value: LVResult = (LVValue1 + LVValue2) +/- Object

following menu,
894

May 2011
Info:
as a result.
via input fields, firstly require writing as variables. These variables are then assigned
data types that are valid for the required operation. The variables can then used in the
required formula.
2.4.3.6.9 More operations
Gives access to additional mathematical functions .
The natural logarithm ln()

ln(x)
May 2011
895
The natural logarithm ln() corresponds to log(x) or the logarithm to the base of e ( Euler
number 2.7182818284590452 ) and is the inverse of the cube function ex. Log(x) returns
a result to the question of how many times you have to multiply base e with itself to return
x.
The absolute value abs()
abs(x)
Cube functions
The following functions are available:

The following explanations assume that the operand has been assigned x as the operand
name.
sqrt ()
sqrt(x)
For non-negative values of x, the functions computes the value that returns x when
multiplied by itself.
The cube function yx

yx
Multiplies base y x-times by itself.
896

May 2011
The cube function ex

ex
This is the inverse function to natural logarithms. Multiplies base e ( Euler number
2.7182818284590452 ) x-times by itself.
Trigonometric functions
The following trigonometric functions are available:

For all trigonometric functions the arguments are angles. The size of the angle is given in
radians. The size of an angle is measured by the length of the arc against a unit circle.

May 2011
897
Instead of giving the angel a in degrees, the length of the blue arc serves as the
measurement for its size. The complete angle is given in radians by the circumference of
then unit circle, i.e. by 2* pi ( pi equals 3.1415926535897932384626433832795.... );
Conversion between degrees and radians is as follows: If a is an angle measured in

degrees, its value in radians is 2pi a/360. Vice versa, a value in radians requires
multiplying by 360/(2Pi) to return an angle in degrees.
The sin() function

sin(x)
Computes the sine value for the angle x, with the angle being given in radians.
The cos() function

cos(x)
Computes the cosine value for the angle x, with the angle being given in radians.
The tan() function

tan(x)
898

May 2011
In a right-angled triangle, the tangent of angle x is the relationship between the "opposite/
adjacent" sides. As a formula: tan(x) = sin(x)/cos(x). The angle x is given in radians.
The asin() function
asin(x)
Arcus sinus is the inverse of sine. asin x is the angle a, for which sin a = x. The angle is
given in radians.
The acos() function

acos(x)
Arcus cosinus is the inverse of cosine. acos x is the angle a, for which cos a = x. The
angle is given in radians.
The atan() function

atan(x)
Arcus tangens is the inverse of tangent. atan x is the angle a, for which tan a = x. The
angle is given in radians.
Select the tangent function for the type of line
Assign Value: LVResult = tan(Object)
Click the bold-type function name to open a menu via which the function may be deleted.

May 2011
899
2.4.3.7 Assign
Klicks provides different types of Assign. They can be added or amended only in edit mode.
Assign Value
Script
Assign
Value
First, there is the normal assigning of a value which assigns a new value to a variable or
property. To add this type of assign, select Script>Assign>Value. This generates the
following instruction core:

This assigns to the left Object the value given by the right object. For objects from a
Visualisation, Parameter or Report, only those properties are available that are not used for
object-configuration purposes. Configuration properties are accessed via Configuration
Read or Configuration Write.
Other Assign operations

The data types of Klicks variables are not fixed (e.g. as integers) and can be assigned. This
can affect the result of a computation. Example: Assigning Variable1 with a value of 3 and
then dividing by 4, you would expect a result of 1.33333. But the division is on two whole
numbers (integers) for which the result must also be a whole number. The result is then
simply truncated from the decimal point. This gives a result of 1. The problem can be
resolved by assigning a float data type to Variable1 prior to the division. Data type settings
can be amended through other operations.
Data type
Format
String
Data flow
There are object functions that return a value rather than notification of success
(operation call successful or not successful). Belonging to these are objects that function
on the basis of strings and are therefore available under the Assign context menu. There
are other object functions available under Configuration.
900

May 2011
2.4.3.7.1 Data type
Data types for variables are not fixed. The following commands assign, or determine,
variable data types.
ToBool
ToDouble
ToFloat
ToInteger
ToLong
ToString
ToTime
ToChar
Get variable type
ToBool
Script
Assign
Type
ToBool
This generates the following instruction core:
Assign Type: LVResult = ToBool( InOut: Variable\Object )

This instruction assigns a variable a boolean data type. An attempt is made to convert the
variable to a boolean data type. The data type may be amended by other instructions.
Arguments:
Name
Variable
Type
Input / output
value
Description
Variable to be assigned a boolean data type
Return code:
Result
1, when the variable has successfully been converted to a boolean data

type.
0, when the variable has not successfully been converted to a boolean
data type. The variable is then assigned the value of 0 (for false).
ToDouble
Script
Assign
Type

May 2011
ToDouble
901
Assign Type: LVResult = ToDouble( InOut: Variable\Object )

This instruction assigns a variable a double data type (double the accuracy of a floating
point). An attempt is made to convert the variable to a double data type. The data type
may be amended by other instructions.
Arguments:
Name
Variable
Type
Input / output
value
Description
Variable to be assigned a double data type
Return code:
Result
1, when the variable has successfully been converted to a double data

type.
0, when the variable has not successfully been converted to a double
data type. The variable is then assigned the value of 0.
ToFloat
Script
Assign
Type
ToFloat
Assign Type: LVResult = ToFloat( InOut: Variable\Object )

This instruction assigns a variable a floating point data type (double the accuracy of a
floating point). An attempt is made to convert the variable to a floating point data type.
The data type may be amended by other instructions.
Arguments:
Name
Variable
Type
Input / output
value
Description
Variable to be assigned a floating point data type
Return code:
Result
1, when the variable has successfully been converted to a floating

point data type.
0, when the variable has not successfully been converted to a floating
point data type. The variable is then assigned the value of 0.
902

May 2011
ToInteger
Script
Assign
Type
ToInteger
Assign Type: LVResult = ToInteger( InOut: Variable\Object )

This instruction assigns a variable an integer data type (32-bit and therefore half the size
of a long data type). An attempt is made to convert the variable to an integer data type.
The data type may be amended by other instructions.
Arguments:
Name
Variable
Type
Input / output
value
Description
Variable to be assigned an integer data type
Return code:
Result
1, when the variable has successfully been converted to an integer data

type.
0, when the variable has not successfully been converted to an integer
ToLong
Script
Assign
Type
ToLong
Assign Type: LVResult = ToLong( InOut: Variable\Object )

This instruction assigns a variable a long data type (64-bit and therefore double the size of
an integer data type). An attempt is made to convert the variable to a long data type. The
data type may be amended by other instructions.
Arguments:
Name
Variable
Type
Input / output
value

May 2011
Description
Variable to be assigned a long data type
903
Return code:
Result
1, when the variable has successfully been converted to a long data

type.
0, when the variable has not successfully been converted to a long
ToString
Script
Assign
Type
ToString
Assign Type: LVResult = ToString( InOut: Variable\Object )

This instruction assigns a variable a string data type. An attempt is made to convert the
variable to a string data type. The data type may be amended by other instructions.
Arguments:
Name
Variable
Type
Input / output
value
Description
Variable to be assigned a string data type
Return code:
Result
1, when the variable has successfully been converted to a string data

type.
0, when the variable has not successfully been converted to a string
data type. The variable is then assigned a "" (no text) value.
ToTime
Script
Assign
Type
ToTime
Assign Type: LVResult = ToTime( InOut: Variable\Object )

This instruction assigns a variable a time data type. An attempt is made to convert the
variable to a time data type. The data type may be amended by other instructions.
904

May 2011
Arguments:
Name
Variable
Type
Input / output
value
Description
Variable to be assigned a time data type
Return code:
Result
1, when the variable has successfully been converted to a time data

type.
0, when the variable has not successfully been converted to a time
data type. The variable is then assigned the current time.
ToChar
Script
Assign
Type
ToChar
Assign Type: LVResult = ToChar( InOut: Variable\Object )

This instruction assigns a variable a char data type. An attempt is made to convert the
variable to a char data type. The data type may be amended by other instructions.
Arguments:
Name
Variable
Type
Input / output
value
Description
Variable to be assigned a char data type
Return code:
Result
1, when the variable has successfully been converted to a char data

type.
0, when the variable has not successfully been converted to a char
data type. The variable is then assigned a value of ".
Get variable type

Script
Assign
Type
Get variable type
Assign Type: Object = Get variable type(In:Variable\Object)

May 2011
905
This instruction determines a variable's data type.
Arguments:
Name
Variable
Type
Input value
Description
Variable for which a data type is to be
determined
Return code:
Object 1: Boolean data type

2: Integer data type
3: Long data type
4: Floating point data
type
5: Double data type
6: String data type
7: Time data type
8: Char data type
2.4.3.7.2 Format
The following describes the instructions that sets the formats for dates, times, timezones
and numbers.
Dateformat
Timeformat
Timezone
Numberformat
Date format
Script
Assign
Format
Dateformat
Assign Format: Date = Type

This instruction sets the date format. Left-click the
date formats:
Short
Medium
Long
Type key word to display a choice of
(08.11.07)
(08.11.2007)
(08 November 2007)
906

May 2011
(Thursday, 08 November 2007)
Full
Timeformat
Script
Assign
Format
Timeformat
Assign Format: Time = Type

This instruction sets the time format. Left-click the
time formats:
Short
Medium
Long
(13:46)
(13:46:10)
(13:46:10:345)
Type key word to display a choice of
Hours and minutes

Hours, minutes, seconds
Hours, minutes, seconds, milliseconds
Timezone
Script
Assign
Format
Timezone
Assign Format: Timezone = Type

This instruction sets the timezone format. Left-click the
of timezone formats:
Type key word to display a choice
UTC time
Local time (PC)
Source time (PC, device)
-12 hours
-11 hours
-10 hours (HST)
-9 hours (AKST, HDT)
-8 hours (PST / AKDT)
-7 hours (MST / PDT)
-6 hours (CST / MDT)
-5 hours (EST / CDT)
-4 hours (AST / EDT)
-3 hours
-2 hours
-1 hours
+0 UTC (GMT /WET)
+1 hour (CET / WEST / BST / IST)
+2 hours (CEST Summertime)
+3 hours (MSK / EEST)
+4 hours
+5 hours
+6 hours
+7 hours
+8 hours
+9 hours

May 2011
907
+10 hours
+11 hours
+12 hours
Numberformat
Script
Assign
Format
Numberformat
Assign Format: Object = Numberformat(In: '#0,0', Object )

Formats the input object value (Object on the right of the Assign), with the input object
remaining unchanged. The format is given through #0,0 and can be changed by leftclicking. The result from formatting takes place on the left of the Assign with the input
object's value being rounded.
Arguments:
Name
'#0,0'
Object
Type
Input value
Description
Input format
Input value
Input object
Return code:
Object Formatted output
2.4.3.7.3 String
In the following, object functions are described based on strings that return a value rather
than notification of success (operation call successful or not successful).
Get string length
Find substring
Get substring
Extract substring
Replace substring
Get string length

Script
Assign
String
Get string length
908

May 2011
Assign String: Object = Get string length(In: String\Object)

Determines and returns the length of the string.
Arguments:
Name
String
Type
Input value
Description
Input string whose length is to be determined
Return code:
Length of input string
Object
Find substring
Script
Assign
String
Find substring
Assign String: Object = Find substring(In:String\Object, Search string\Object, Start position

\Object)
Determines whether a the string contains a specific substring.
Arguments:
Name
String
Search string
Start position
Type
Input value
Input value
Input value
Description
String to be searched
String to be searched for
Position from where the search is to start (commencing
at 1 )
Return code:
0, when the substring has been found

Otherwise the position of the search string in the string to be searched
Object
Get substring
Script
Assign
String

May 2011
Get substring
909
Assign String: Object = Get substring(In:String\Object, Start position\Object, Number of

characters\Object)
Determines and returns a substring.
Arguments:
Name
String
Start
position
Number of
characters
Type
Description
Input value String from which a substring is determined,
Input value Position where the substring to be determined starts
( commencing at 1 )
Input value Number of characters to be returned
Return code:
A substring. This is empty when the "Number of characters" equals 0 or
when the start position is greater than the "String" argument.
Object
Extract substring
Script
Assign
String
Extract substring
Assign String: Object = Extract substring(In:String\Object, Prefix\Object, Suffix\Object

InOut:Start position\Object)
Extracts and returns a substring.
Arguments:
Name
String
Prefix
Suffix
Start
position
Type
Input value
Input value
Description
String from which a substring is to extracted,
A string that must go before the string to be extracted. This
may not be empty.
Input value
A string that must go after the string to be extracted. This
may not be empty.
Input /
Input: Position from where the extraction should happen
output value (commencing at 1 )
Output: Start position of the extracted string in the input
string ( 0, when nothing is to be extracted)
910

May 2011
Return code:
A substring that can be empty.
Object
Replace substring
Script
Assign
String
Replace substring
Assign String: Object = Replace substring(In: Search string\Object, Replace string\Object,

Replace all\Object InOut: String\Object, Start position\Object)
Replaces one or more occurrences of the search string with the replacement string.
Arguments:
Name
Search
string
Replace
string
Replace all
Type
Input value
Description
String to be replaced
Input value
The replacement string
Input value
String
Input /
output
value
Input /
output
value
Whether all occurrences of the search string are to be

replaced (yes) or (no)
Input: String before the replacement of a substring
Output: String after the replacement of a substring
Start
position
Input: Position from where the replacement should happen

(commencing at 1 )
Output: Position from where the replacement happened ( 0,
when no replacement has happened)
Return code:
The number of times the search string
was replaced.
Object
2.4.3.7.4 Data flow
Klicks enables, via a script, the assigning of a data source to an object. The object's value
is then updated every 100 msecs with the data from the data source.
Script
Assign
Data flow

May 2011
911
Assign Data flow: Object << Object

This assigns the right object as a data source to the left object. Left clicking the left
Object (the target for the data flow instruction) displays the following window:
Left clicking the right

following window:
Object (the source for the data flow instruction) displays the
2.4.3.8 Control
The Control option in Klicks provides three different types of control. These are added or
amended only in edit mode.
First, there are repeats that run an instruction block until a condition is true. Then there
are instructions for waiting.
Repeat / Loop
Repeat x times
Repeat while case
Break Repeat
Wait x msec
Wait while case
Select Next Procedure
912

May 2011
Call sub module

Call function module
Call Initprocedure
Call Startprocedure
Repeat / Loop
Script
Control
Repeat / Loop
Control: Repeat for Object = Object to Object Step Object

Repeat End
The instruction corresponds to a for-loop. The code between Control: Repeat.... and
Repeat End is repeated until the variable exceeds the maximum value.
The following applies:
The
The
The
The
first object defines the variable

second object sets the variable's initial value
third object sets the variable's maximum value
fourth object sets the amount the variable increases at each repeat
Repeat x times
Script
Control
Repeat x times
Control: Repeat Object times

Repeat End
Var sets how often the code is repeated between Control: Repeat Object
End.
times and Repeat
Repeat while case

Script
Control
Repeat while case
Control: Repeat while (Object <>= Object)

Repeat End

May 2011
913
The code between Control: Repeat.... and

false!
Repeat End is repeated until, the given condition is
The most basic condition is made up of two operands and one comparison operation. Leftclicking the key words opens context menus with options for replacing the key word. Leftclicking while opens a context menu that enables the adding of further conditions.
Control: Repeat while (Object <>= Object) logic (Object <>= Object)
Repeat End
Left-clicking the logic key word displays a context menu that enables selection of a logical
connection (and / or / xor) or the deletion of a left or right subcondition.

menu.

914

May 2011
Break Repeat
Script
Control
Break Repeat
This instruction is available only within a Question block and generates the following
instruction core:
Control: Break Repeat

It enables an immediate exit from a repeat instruction.
Wait while case

Script
Control
Wait while case
Control: Wait while (Object <>= Object)

End Control
The lines of script following Question End are not when the condition is false. The most
basic condition is made up of two operands and one comparison operation. Left-clicking the
key words opens context menus with options for replacing the key word. Left-clicking
while opens a context menu that enables the adding of further conditions.
Control: Wait while (Object <>= Object) logic (Object <>= Object)
Repeat End
Left-clicking the logic key word displays a context menu that enables selection of a
logical connection (and / or / xor) or the deletion of a left or right subcondition.


May 2011
915
menu.

Wait x msec
Script
Control
Wait x msec
Control: Wait Object msec

This enables a waiting period, of the number of msecs given, until the following lines of
script are performed.
Select Next Procedure

Script
Control
Call Functionprocedure
[function module name]
If there are sequence modules, the menu option is available within a Question instruction.
This generates the following instruction core with Name being replaced by the name of the
sequence module.
Control select next procedure: Module\sequence.Name

The instruction selects the successor module to be processed following processing of the
current module.
916

May 2011
Info:
The instruction does not lead to direct calling of the successor. This takes place only
after processing of the current module. The successor can therefore be run multiple
times, i.e. repeatedly overwritten, within this module. The final Control Select Next
Procedure instruction therefore sets the actual successor. If there is a successor for a
module but not explicitly selected, the called successor is the one that was added first
to the module chart view!
Call function module

Script
Control
Call
Functionprocedure
[function procedure name]
function module.
Control Call: Module\Parallelmodule.Name(SVSync)

A function module can contain arguments. An argument can be added by left-clicking the
closing bracket in the first line of a function module. This displays the relevant context
menu. Left-clicking an existing argument displays a context menu to rename or delete the
argument. Arguments can be added or deleted until the function module is called!
The instruction core to call a function module with an argument appears as follows:
Control Call: Module\Parallel.Name(Object, SVSync)

This calls the given function module.
Info:
SVSync is a variable that is required for synchronizing function modules. Its functioning
has not yet been implemented. Although a sync variable then requires inputting, it has no
effect.

May 2011
917
Call sub module

Script
Control
Call
Subprocedure
[sub module name]
submodule.
Control Call: Module\Submodule.Name

A submodule can contain arguments. An argument can be added by left-clicking the closing
bracket in the first line of a submodule. This displays the relevant context menu. Leftclicking an existing argument displays a context menu to rename or delete the argument.
Arguments can be added or deleted until the submodule is called!
The instruction core to call a submodule with an argument appears as follows:
Control Call: Module\Sub.Name(Object)

This calls the given submodule.
Call Initprocedure
Script
Control
Call
Initprocedureu [init module name]
Control Call: Module\Initmodule

This calls the given init module.
Call Startprocedure
2.4.3.9 Initiate
Klicks provides object functions for extended operability. These concern either global object
functions that are available in addition to set objects (e.g. object functions for files) or
object specific functions. Some functions are available only after an object has been added
to a VisuView, ParameterView or Report or when the user is in extended mode.
Visualization
Parameter input
918

May 2011
Report
Channel
Application
File
Window
DateTime
Configuration
Directory
Pro fiSig nal
Project
(operation call successful or not successful).
Included here are objects that function on the basis of strings and are therefore available
under the Assign string context menu. Other object functions are available under readable
object functions and writeable object functions.
2.4.3.9.1 Visualization
This section contains object functions associated with the VisuView or elelments of the
Visuview.
Object functions for VisuView:

Open VisuView
Close
Objec functions for VisuView components:

Dropdown box
Table/YX-table
Stoppuhr
Diagrams
Recorder
Profile
Alarm list
ODBC

May 2011
919
2.4.3.9.1.1 VisuView
Open VisuView
Close
Open VisuView
Script
Initiate
Visualisation
Open VisuView
Initiate Visualization: Open VisuView (In: VisuView\Name, Front\Var, Full screen\Var, Border\Var)
This function opens the VisuView.
Arguments:
Name
Name
Front
Type
Input value
Input value
Description
Name of VisuView
Whether the VisuView is to be in the foreground (yes/no).
This value should be set to Yes when users wish to open a
VisuView that requires closing with Close Visuview or
moving to the background. An example of such a VisuView
is one requiring user input.
Full screen
Border
Input value
Input value
Whether the VisuView is to be portrayed in full screen

mode (yes/no).
When the VisuView is to be portrayed in full screen mode,
it is then not possible to add a border. Any Border input is
then ignored.
Whether the VisuView is to be portrayed with a border
(yes/no).
Input for Border is ignored when Full screen has been set
to Yes.
Close
Script
Initiate
Visualisation
Close
Initiate Visualization: Close(In: VisuView\Name)
920

May 2011
This function closes the VisuView.
Arguments:
Name
Name
Type
Input value
Description
Name of VisuView
Info:
This instructions can no longer be selected and exists only for reasons of backwards
compatibility to older project files. Use instead the instruction Open VisuView
Open VisuView
Close
Open VisuView
Script
Initiate
Visualisation
Open VisuView
Initiate Visualization: Open VisuView (In: VisuView\Name, Full screen\Var, Border\Var)

This function opens the VisuView.
Arguments:
Name
Name
Full screen
Type
Input value
Input value
Border
Input value

May 2011
Description
Name of VisuView
Should the VisuView be portrayed in full screen mode (Yes/
No)?
Should the VisuView be portrayed with a border (Yes/No)?
921
Open VisuView in foreground (obsolete)

Script
Initiate
Visualisation
Open VisuView in foreground
Initiate Visualization: Open VisuView in foreground(In: VisuView\Name)

This function opens the VisuView in the foreground.
Arguments:
Name
Name
Type
Input value
Description
Name of VisuView
2.4.3.9.1.2 Dropdown box
The following object functions are available for the dropdown box (refer also to Visuobject
dropdown box/channel dropdown box and ParameterView dropdown box/channel dropdown
box):
Add item
Remove item
Clear box
Add item
These functions are available only in extended mode.
Script
Initiate
Visualisation
[VisuView name]
dropdown box/[dropdown box name]
Add item
This generates the following instruction core with the VisuView name and dropdown box
name serving as placeholders for an actual VisuView and/or dropdown box:

\Objekt Out: LVResult)
Script
Initiate
Input Parameter
[page name]
Dropdown box
[Dropdown box name]
Add
item
This generates the following instruction core with the Page name and dropdown box name
serving as placeholders for an actual ParameterView and/or dropdown box:
Initiate Parameter\Page_1\Drop D.Drop down box_1: Add item(In: Name\Object, Value\Object

Out: LVResult)
922

May 2011
The function adds an item to the dropdown box.
Arguments:
Name
Name
Value
Type
Input value
Input value
Description
Name of the item in the dropdown box
Internal value of the item which is not visible
Return code:
0: Function failed
1: Function succeeded
Result
Remove item
This function is available only in extended mode.

Script
Initiate
Visualisation
[VisuView name]
Dropdown box
[Dropdown box name]
Remove item
Initiate Visualisation\Visuschaubild_1\Drop D.Drop down box_1: Remove item(In: ItemIndex

Script
Initiate
Input Parameter
[Page name]
Dropdown box
[Dropdown box name]
Remove item
This generates the following instruction core with the page name and dropdown box name
Initiate Parameter\Page_1\Drop D.Drop down box_1: Remove item(In: ItemIndex\Object Out:

LVResult)
This function removes an item from the dropdown box.

May 2011
923
Arguments:
Name
ItemIndex
Type
Input value
Description
Index of the item to be removed
Return code:
0: Function failed
Result
Clear box

Script
Initiate
Visualisation
[VisuView name]
Dropdown box
[Dropdown box name]
Clear
box
Initiate Visualisation\Visuschaubild_1\Drop D.Drop down box_1: Clear box()

Script
Initiate
Input Parameter
[Page name]
Dropdown box
[Dropdown box name]
Clear
box
Initiate Parameter\Page_1\Drop D.Drop down box_1: Clear box()

This function removes all items from the dropdown box.
Info:
These instructions can no longer be selected and exist only for reasons of backwards
compatibility to older project files.
924

May 2011
Add item
Remove item
Add item
These functions are available only in extended mode.
Script
Initiate
Visualisation
[VisuView name]
dropdown box/[dropdown box name]
Add item

\Objekt)
Script
Initiate
Input Parameter
[page name]
Dropdown box
[Dropdown box name]
Add
item
This generates the following instruction core with the Page name and dropdown box name
Initiate Parameter\Page_1\Drop D.Drop down box_1: Add item(In: Name\Object, Value\Object)
The function adds an item to the dropdown box.
Arguments:
Name
Name
Value
Type
Input value
Input value
Description
Name of the item in the dropdown box
Internal value of the item which is not visible
Remove item

May 2011
925
Script
Initiate
Visualisation
[VisuView name]
Dropdown box
[Dropdown box name]
Remove item
Initiate Visualisation\VisusView_1\Drop D.Drop down box_1: Remove item(In: ItemIndex

\Objekt)
Script
Initiate
Input Parameter
[Page name]
Dropdown box
[Dropdown box name]
Remove item
Initiate Parameter\Page_1\Drop D.Drop down box_1: Remove item(In: ItemIndex\Object)

This function removes an item from the dropdown box.
Arguments:
Name
ItemIndex
Type
Input value
Description
Index of the item to be removed
2.4.3.9.1.3 Table/YX-table
The following functions are available for table (refer also to Visuobject table and Parameter
object table) and YX-table:
Reset table
Save to CSV
Load from CSV
Insert from CSV
(operation call successful or not successful). These include the following object functions
for tables / YX-tables and are assigned under configuration.
Get column count
Get column for title
Get row count
926

May 2011
Get row for title
These include the following object functions for tables / YX-tables and are assigned under
configuration.
Set name of column

Set y-axis of column
Set color of column
Set unit of column
Set visibility of column
Reset table
Script
Initiate
Visualisation
[VisuView name]
Table
[Table name]
Reset table
This generates the following instruction core with the VisuView name and table name
serving as placeholders for an actual VisuView and/or table:
Initiate Visualisation\VisuView_1\Tab.Table_1: Reset table()

Script
Initiate
Visualisation
[VisuView name]
YX-Table
[YX-table name]
Reset table
serving as placeholders for an actual VisuView and/or YX-table:
Initiate Visualisation\VisuView_1\YX-Tab.YX-Table_1: Reset table()

Script
Initiate
Input Parameter
[Page name]
Table
[Table name]
Reset table
This generates the following instruction core with the page name and table name serving
as placeholders for an actual ParameterView and/or table:
Initiate Parameter\Page_1\Tab.Table_1: Reset table()

This function resets and clears the table.
Save to CSV
Script
Initiate
Visualisation
[VisuView name]
Table
[Table name]
Save to CSV
Initiate Visualisation\VisuView_1\Tab.Table_1: Save to CSV (In: CSV-File\Object Out:

May 2011
927
LVResult)
Script
Initiate
Visualisation
[VisuView name]
YX-Table
[YX-Table name]
Save to CSV
Initiate Visualisation\VisuView_1\YX-Tab.YX-Table_1: Save to CSV (In: CSV-File\Object Out:

LVResult)
Script
Initiate
Input Parameter
[page name]
Table
[table name]
Save to CSV
Initiate Parameter\Page_1\Tab.Table_1: Save to CSV (In: CSV-File\Object Out: LVResult)

This function saves the contents of a table to a CSV file.
Arguments:
Name
CSV-File
Type
Input value
Description
Name of the CSV file (including path) to which the table
is to be saved
Return code:
0: Function failed
Result
Load from CSV

Script
Initiate
Visualisation
[VisuView name]
Table
[Table name]
Load from CSV
Initiate Visualisation\VisuView_1\Tab.Table_1: Load from CSV(In: CSV-File\Object Out:

LVResult)
Script
Initiate
Visualisation
[VisuView name]
928
YX-Table
[YX-Table name]
Load from CSV

May 2011
Initiate Visualisation\VisuView_1\YX-Tab.YX-Table_1: Load from CSV(In: CSV-File\Object

Out: LVResult)
Script
Initiate
Input Parameter
[page name]
Table
[table name]
Load from CSV
Initiate Parameter\Page_1\Tab.Table_1: Load from CSV(In: CSV-File\Object Out: LVResult)
This function loads the contents of the given CSV file into the table/YX-table. Existing
table content is deleted.
Arguments:
Name
CSV-File
Type
Input value
Description
Name of the CSV file (including path) to be loaded.
Return code:
0: Function failed
Result
Insert from CSV

Script
Initiate
Visualisation
[VisuView name]
Table
[Table name]
Insert from CSV
Initiate Visualisation\VisuView_1\Tab.Table_1: Insert from CSV(In: CSV-File\Object Out:

LVResult)
Script
Initiate
Visualisation
[VisuView name]
YX-Table
[YX-Table name]
Insert from
CSV

May 2011
929
Initiate Visualisation\VisuView_1\YX-Tab.YX-Table_1 : Insert from CSV(In: CSV-File\Object

Out: LVResult)
Script
Initiate
Input Parameter
[page name]
Table
[table name]
Insert from CSV
Initiate Parameter\Page_1\Tab.Table_1 : Insert from CSV(In: CSV-File\Object Out:

LVResult)
This function loads the contents of the given CSV file into the table/YX-table. This inserts
new content to the existing content.
Arguments:
Name
CSV-File
Type
Input value
Description
Return code:
Result
0: Function failed
Info:
Save to CSV
Load from CSV
Insert from CSV
Save to CSV
930

May 2011
Initiate Visualisation\VisuView_1\Tab.Table_1: Save to CSV (In: CSV-File\Object)

This function saves the contents of a table to a CSV file.
Arguments:
Name
CSV-File
Type
Input value
Description
Name of the CSV file (including path) to which the table
is to be saved
Load from CSV

Initiate Visualisation\VisuView_1\Tab.Table_1: Load from CSV(In: CSV-File\Object)
This function loads the contents of the given CSV file into the table/YX-table. Existing
table content is deleted.
Arguments:
Name
CSV-File
Type
Input value
Description
Insert from CSV

Initiate Visualisation\VisuView_1\Tab.Table_1: Insert from CSV(In: CSV-File\Object)
This function loads the contents of the given CSV file into the table/YX-table. This inserts
new content to the existing content.
Arguments:
Name
CSV-File
Type
Input value

May 2011
Description
931
2.4.3.9.1.4 Stop watch
The following functions are available for the stop watch (refer also to stop watch
visuobject).
Start
Stop
Break
Set start value
Start
Script
Initiate
Visualisation
[VisuView name]
Stop watch
[Stop watch name]
Start
Initiate Visualisation\VisuView_1\Stop p .Stop watch_1: Start(Out: LVResult)

Starts timing with the stop watch.
Return code:
0: Function failed
Result
Stop
Script
Initiate
Visualisation
[VisuView name]
Stop watch
[Stop watch name]
Stop
Initiate Visualisation\VisuView_1\Stop p .Stop watch_1: Stop(Out: LVResult)
932

May 2011
Ends timing with the stop watch.
Return code:
0: Function failed
Result
Break
Script
Initiate
Visualisation
[VisuView name]
Stop watch
[Stop watch name]
Break
Initiate Visualisation\VisuView_1\Stop p .Stop watch_1: Break(In: Break\Object Out:

LVResult)
Pauses or continues timing depending on the input parameter.
Arguments:
Name
Pause
Type
Input value
Description
yes: Pause timing.
no: Continue timing.
Return code:
Result
0: Function failed
Set start value

May 2011
933
Script
Initiate
Visualisation
[VisuView name]
Stop watch
[Stop watch name]
Set start
value
Initiate Visualisation\VisuView_1\Stop p .Stop watch_1: Set start value(In: Startvalue\Object

Out: LVResult)
Set start value. When counting forward, timing begins from this start value. When counting
back, timing counts back from this start value and ends at zero.
Arguments:
Name
Start value
Type
Input value
Description
Value in nano seconds.
Return code:
Result
0: Function failed
2.4.3.9.1.5 Trends and Recorders
There are a multitude of object functions for Trends/Recorders but not every function can
be used for every trend/recorder.
Functions for channel selection (Trends and recorders)
Clear channel group
Add channel
Delete channel
Functions for configuration (Trends)

Channel visible
934

May 2011
Set channel color

Set channel Y-axis
Set X-axis range
Set Y-axis range
Suppress update
Clear drawing area
Load config
Save config
Functions for displaying data (Trends)

Freeze diagram
Show timerange
Show last recording
Load MesFile
Functions for exporting (Trends)

Export to MesFile
ASCII export
export trend as EMF
export trend and legend as EMF
Functions for markers (Trends)

Create marker
Delete marker
Copy marker
Show marker
Load marker

May 2011
935
Read marker
Actual marker
Next marker
Show textlabel
Other functions
print Trend
Recorder functions
Pause
Recording
Take single step
Functions for channel selection (Trends and recorders)

Clear channel group
Add channel
Delete channel
These functions are available for the following Visu-Objects:

Yt-diagram
YX-diagram (HW channels)
Logic diagram
Orbit diagram
FFT diagram
Recorder
The following placeholders are used in this section:

[VisuView name] is the name of an actual VisuView.
[Visu-Object name] is the name of an actual VisuView object for which the function is
available.
[Visu-Object type] is the type for the selected VisuView object.
936

May 2011
Clear channel group
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Clear channel group

This generates the following instruction core (with Yt-Diagram_1 as object).
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Clear channel group(Out:

LVResult)
This function deletes all the channels from the channel list of a diagram or recorder.
Return code:
0: Function failed
Result
Add channel
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Add
channel
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Add channel(In: Channel ID

This function adds a channel to the channel list of a diagram or recorder.
Arguments:
Name
Channel ID
Type
Input value
Description
ID of the channel to be added to the channel list
Return code:
Result
0: Function failed

May 2011
937
Delete channel
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Delete channel
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Delete channel(In: Channel ID

This function deletes a channel from the channel list of a diagram or recorder.
Arguments:
Name
Channel ID
Type
Input value
Description
ID of the channel to be deleted from the channel list
Return code:
Result
0: Function failed
Functions for configuration (Trend)

Channel visible
Set channel color
Set channel Y-axis
Set X-axis range
Set Y-axis range
Suppress update
Clear drawing area
Load config
Save config
938

May 2011

This function is available for the following Visu-Objects:
Yt-diagram
Logic diagram
Orbit diagram
FFT diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
All
channels visible
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: All channels visible(In: visible

This function sets the visibility for all channels of a diagram.
Arguments:
Name
visible
Type
Input value
Description
Show or hide channels (Yes/No)
Return code:
Result
0: Function failed
Channel visible
Yt-diagram

May 2011
939
YX-diagram (channels)
Logic diagram
Orbit diagram
FFT diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Channel visible
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Channel visible(In: Channel ID

\Object, visible\Object Out: LVResult)
This function sets visibility for the channel of a diagram.
Arguments:
Name
Type
Channel ID Input value
visible
Input value
Description
ID of the channel that is to have its visibility set
Show or hide channel (Yes/No)
Return code:
Result
0: Function failed
Set channel color

Yt-diagram
YX-diagram (table)
Logic diagram
Orbit diagram
FFT diagram
940

May 2011
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Set
channel color
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Set channel color(In: Channel ID

\Object, Color\Object Out: LVResult)
This function sets the color of the channel to be displayed within the diagram.
Arguments:
Name
Channel ID
Color
Type
Input value
Input value
Description
ID of the channel that is to have its color set
The color in which the channel is to be displayed within
the diagram
Return code:
0: Function failed
Result
Set channel Y-axis

Yt-diagram
YX-diagram (table)
Logic diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Set
channel Y-axis
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Set channel Y-axis(In: Channel

ID\Object, Y-axis (number)\Object Out: LVResult)

May 2011
941
Determines the Y-axis on which the given channel is to be displayed. Up to four Y-axes can
be given. A Y-axis number that is less than 1 or greater than 4 generates a Log-Message.
A false value is then also returned. If there is no Y-axis for the given number, the axis is
then automatically created. Example: If just one Y-axis exists and you set a channel to a
fourth Y-axis, Y-axes numbered two to four will be set up.
Arguments:
Name
Channel ID
Y-axis number
Type
Input value
Input value
Description
ID of the channel which is assigned to the Y-axis.
Number for the Y-axis ( from 1 to 4), to which the
channel is to be set
Return code:
0: Function failed (e.g. because the Y-axis number was less than 1 or
greater than 4; detailed information on errors is available in the log file)
Result
Set X-axis range

This function is available only in extended mode for the following objects:
YX-diagram (table)
FFT diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Set
X-axis range
This generates the following instruction core (with YX-diagram (channel)_1 as object).
Initiate Visualisation\VisuView_1\YX-diagram (channel).YX-diagram (channel)_1: Set X-axis

range(In: Range low\Object, Range high\Object Out: LVResult)
This function sets the X-axis range.
942

May 2011
Arguments:
Name
Range low
Range high
Type
Input value
Input value
Description
Lowest value on the X-axis.
Highest value on the X-axis.
Return code:
0: Function failed
Result
Set Y-axis range

Yt-diagram
YX-diagram (table)
Logic diagram
FFT diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Set
Y-axis range
Initiate Visualisation\VisuView_1\YX-diagram (channel).YX-diagram (channel)_1: Set Y-axis

range(In: Axis\Object, Range low\Object, range high\Object Out: LVResult)
This function sets the Y-axis range.
Arguments:
Name
Axis
Range low
Range high

May 2011
Type
Input value
Input value
Input value
Description
The Y-axis for which the range is to be set.
Lowest value on the Y-axis.
Highest value on the Y-axis.
943
Return code:
0: Function failed
Result
Suppress update
YX-diagram (table)
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Suppress update
This generates the following instruction core (with YX-diagram (table)_1 as object).
Initiate Visualisation\VisuView_1\YX-diagram (table).YX-diagram (table)_1: Suppress

update(In: suppress\Object Out: LVResult)
This function determines whether updating of the portrayal is to be suppressed.
Arguments:
Name
Suppress
Type
Input value
Description
Whether the update is to be suppressed (Yes/No)
Return code:
Result
0: Function failed
Clear drawing area

944

May 2011
Orbit diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Clear drawing area

Initiate Visualisation\VisuView_1\Yt-diagram (channel).Yt-diagram_1 (channel): Clear

drawing area()
This function clears a diagram's graphical portrayal.
Load config
Yt-diagram
YX-diagram (table)
Logic diagram
Orbit diagram
FFT diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Load config
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Load config(In: File name\Object

Out: LVResult)
This function loads a diagrams configuration settings from a configuration file.
Arguments:
Name
File name
Type
Description
Input value Name of the configuration file (including path) to be
loaded.

May 2011
945
Return code:
0: Function failed
Result
Save config
Yt-diagram
YX-diagram (table)
Logic diagram
Orbit diagram
FFT diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Save config
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Save config(In: File name\Object

Out: LVResult)
This function saves a diagrams configuration settings to a configuration file.
Arguments:
Name
File name
Type
Input value
Description
Name of the file (including path) to which the
configuration is to be saved
Return code:
Result
0: Function failed
946

May 2011

Yt-diagram
Logic diagram
Orbit diagram
FFT diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]

Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Save config to MesFile(Out:

LVResult)
This function saves a diagrams configuration settings directly to the measurement data file
being displayed.
Return code:
Result
0: Function failed

Yt-diagram
YX-diagram (table)
Logic diagram
Orbit diagram
FFT diagram

May 2011
947
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]

Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Load standard configuration

(Out: LVResult)
This function is available for every type of diagram and restores a diagram's standard
configuration.
Return code:
Result
0: Function failed
Functions to display data (Trends)

Freeze diagram
Show timerange
Get timerange
Show last recording
Load MesFile

Yt-diagram
Logic diagram
Orbit diagram
FFT diagram
948

May 2011
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]

Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: back to online Trend(Out:

LVResult)
This function overrides the freeze mode in a diagram's graphical portrayal. For a detailed
explanation refer to Trend operation.
Return code:
0: Function failed
Result
Freeze diagram
Yt-diagram
Logic diagram
Orbit diagram
FFT diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Freeze diagram
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Freeze diagram(Out:LVResult)

This function activates the freeze mode for a diagram's graphic portrayal. For a detailed

May 2011
949
Return code:
0: Function failed
Result
Show timerange
Yt-diagram
Logic diagram
Orbit diagram
FFT diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Show timerange
This generates the following instruction core (using Yt-Diagram_1 as object).
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Show timerange(In: start time/

end time\Object, timerange\Object Out:LVResult)
This function sets the timerange to be shown in the diagram. When the range is negative it
is assumed an end time has been given. Refer also to Trend operation.
Arguments:
Name
Start time/ end
time
Timerange
Type
Input value
Description
Start time or end times of the portrayal (UTC time)
Input value
Timerange for the portrayal (UTC time). Negative for

end time.
Return code:
Result
0: Function failed
950

May 2011
Get timerange
Yt-diagram
Logic diagram
Orbit diagram
FFT diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Get
timerange
This generates the following instruction core (using Yt-Diagram_1 as object).
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Show timerange(Out: Start time

\Object, End time\Object, Online\Object Out:LVResult)
This function returns the timerange shown in the diagram.
Argumente:
Name
Start time
Typ
Output
value
Output
value
Output
value
End time
Online
Beschreibung
Startzeit der Darstellung (UTC-Zeit)
Endzeit der Darstellung (UTC-Zeit)
false: diagram is in Zoom modus
true: diagram is online
Return code:
Result
0: Function failed
Show last recording

May 2011
951
Yt-diagram
Logic diagram
Orbit diagram
FFT diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Show last recording

Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Show last recording(Out:

LVResult)
This function is used when the diagram is linked to a recorder. When the recorder is
stopped, this instruction enables the display of the last recorded measurement file. Refer
also to Trend operation.
Return code:
0: Function failed
Result

Yt-diagram
Logic diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Set
online timerange
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Set online timerange(In:

timerange\Object Out: LVResult)
952

May 2011
This function sets the timerange to be displayed in a diagram's graphical portrayal prior to
scrolling the window's content. Refer also to Trend operation.
Arguments:
Name
Timerange
Type
Input value
Description
Timerange to be displayed in graphical portrayal (UTC
time)
Return code:
0: Function failed
Result
Load MesFile
Yt-diagram
Logic diagram
Orbit diagram
FFT diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Load MesFile
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Load MesFile(In: File name

\Object, with configuration\Object Out: LVResult)
This function loads a measurement data file into the diagram.

May 2011
953
Arguments:
Name
File name
Type
Input
value
Input
value
With
configuration
Description
Name of the measurement data file (including path) to be
loaded.
yes: also loads the configuration contained in the
measurement data file and overwrites the trend's
configuration settings.
no: does not change the trend's configuration settings.
Return code:
0: Function failed
Result
Functions for exporting (Trends)

Export to MesFile
ASCII export
export trend as EMF
Export to MesFile
Yt-diagram
Logic diagram
Orbit diagram
FFT diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Export to MesFile
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Export to MesFile(In: File name
954

May 2011
\Object, Start time\Object, End time\Object, Only visible channel\Object, Progress

dialog\Object Out: LVResult)
This function exports a diagram's data.
Arguments:
Name
File name
Type
Description
Input value File name (including path) to which data is to be
exported.
Input value Start time for the export time range (UTC time)
Input value End time for the export time range (UTC time)
Input value Export only from displayed channels? ( Yes/No )
Start time
End time
Only visible
channel
Progress dialog
Input value Display a progress dialog? ( Yes/No )
Return code:
0: Export failed
1: Export succeeded
Result
ASCII export
Yt-diagram
Logic diagram
Orbit diagram
FFT diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
ASCII export
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: ASCII export(In: File name

\Object, Start time\Object, End time\Object, Only visible channel\Object, Progress dialog

May 2011
955
This function exports a diagram's data in ASCII format. Ensure that the start time is earlier
than the end time and that the end time does not lie in the future.
Arguments:
Name
File name
Start time
End time
Only visible
channel
Progress dialog
Type
Description
exported.
Input value Export only from displayed channels? ( Yes/No )
Input value Display a progress dialog? ( Yes/No )
Return code:
0: Export failed
1: Export succeeded
Result
export trend as EMF

Yt-diagram
YX-diagram (table)
Logic diagram
Orbit diagram
FFT diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
export trend as EMF

Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: export trend as EMF(In: Width

\Object, height\Object InOut: File name\Object Out: LVResult)
The diagram's graphical portrayal is exported to an EMF file. Refer also to Trend export
options.
956

May 2011
Arguments:
Name
Width
Height
File name
Type
Input value
Input value
Input / output value
Description
Width in mm
Height in mm
Name of the EMF file
Return code:
0: Function failed
Result

Yt-diagram
YX-diagram (table)
Logic diagram
Orbit diagram
FFT diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]

Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: export trend and legend as

EMF(In: Width\Object, Height\Object, position legend\Object InOut: File name\Object
Out: LVResult)
The diagram's graphical portrayal and legend/key is exported to an EMF file. Refer also to
Trend export options.
Arguments:
Name
Width
Height
Type
Input value
Input value

May 2011
Description
Width in mm
Height in mm
957
Position
Input value
File name
Position legend
1: Legend/key is not shown
2: below
3: right
4: left
x: Legend/key is shown on the right when the
trend is displaying a channel table
Name of the EMF file
Return code:
0: Function failed
Result
Functions for markers (Trends)

Create marker
Delete marker
Copy marker
Show marker
Load marker
Read marker
Actual marker
Next marker
Show textlabel

Yt-diagram
Logic diagram
Orbit diagram
FFT diagram
Create marker
Script
Initiate
Visualisation
[VisuView name]
958
[Visu-Obj ect type]
[Visu-Obj ect name]

May 2011
Create marker
This generates the following instruction core that uses the Yt-Diagram_1 object.
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Create marker(In: Name\Object,

Text\Object, Time\Object, Channel ID\Object, priority\Object Out: marker ID
\Object, LVResult)
This function creates a new marker.
Arguments:
Name
Name
Text
Time
Channel ID
Priority
Type
Input
Input
Input
Input
Input
Marker ID
Output value
value
value
value
value
value
Description
Name of marker
Text
Timestamp for the marker (UTC time)
The channel ID for which the marker is to be set
Marker priority
0:
No priority
1-9: Priority (1 = highest priority,
9 = lowest priority)
ID for the created marker.
Return code:
0: Function failed
Result
Delete marker
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Delete marker
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Delete marker(In: Marker ID

\Object, Channel ID\Object Out: LV Result)
This function deletes the given marker. When a channel ID is given, the marker is deleted
only from this channel. If no channel ID is given (channel ID = 0), the marker is deleted
completely.

May 2011
959
Arguments:
Name
Marker ID
Channel ID
Type
Input value
Input value
Description
ID of the marker to be deleted
Channel ID
0: Completely delete marker (from all channels)
ID:ID of the channel from which the marker is to be
deleted
Return code:
0: Function failed
Result
Copy marker
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Copy marker
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Copy marker(In: Marker ID

\Object, Channel ID\Object Out: LV Result)
This function copies the marker to the given channel. If no channel ID is given (channel ID
= 0), the marker is copied to all the trend's channels.
Arguments:
Name
Marker ID
Channel ID
Type
Input value
Input value
Description
ID of the marker to be copied
Channel ID
0:
Marker is copied to all the trend's channels.
ID:
ID of the channel to which the marker is to be
copied
Return code:
Result
0: Function failed
960

May 2011
Show marker
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Show marker
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Show marker(In: visible\Object,

Priority\Object, Start time\Object, End time\Object Out: marker count\Object,
LVResult)
This function loads all the markers for the given time range and displays them in a trend
diagram. If a priority is given (priority input value : 1-9), only those markers are displayed
whose priority is greater or equal to the given priority (1 = highest priority, 9 = lowest
priority).
Arguments:
Name
visible
Type
Input value
Priority
Input value
Start time
End time
Marker count
Input value
Input value
Output value
Description
Show or hide marker
Yes: Show marker
No: Hide marker
Marker priority
0:
No priority
Start time for the time range (UTC time)
End time for the time range (UTC time)
Number of displayed markers
Return code:
Result
0: Function failed
Load marker

May 2011
961
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Load marker
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1:Load marker(In: Priority\Object,

Start time\Object, End time\Object Out: marker count\Object, LVResult)
This function loads all the markers for the given time range. The markers are not
automatically displayed in a trend diagram. The marker count returns the number of markers
with markers that have equal or higher priorities.
Arguments:
Name
Priority
Type
Input value
Start time
End time
Marker count
Input value
Input value
Output value
Description
Marker priority
0:
No priority
Start time for the time range (UTC time)
End time for the time range (UTC time)
Number of loaded markers
Return code:
0: Function failed
Result
Read marker
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Read marker
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1:Create marker(In: Marker ID

\Object Out: Name\Object, Text\Object, Time\Object, channel count\Object, Priority
\Object, OFT UserID\Object, LVResult)
This function determines information for the given markers.
962

May 2011
Arguments:
Name
Marker ID
Name
Text
Time
channel count
Type
Input value
Output value
Output value
Output value
Output value
Priority
Output value
OFT UserID
Output value
Description
ID of the markers whose information is to be read
Name of marker
Text
Timestamp for the marker (UTC time)
The number of channels to which the marker is
assigned
Marker priority
0:
No priority
ID of the user that created the marker
Return code:
0: Function failed
Result
Actual marker
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Actual marker
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Actual marker(In: Channel ID

\Object InOut: Time\Object, priority\Object, Out: marker ID\Object, LVResult)
This function determines the current marker for the given channel. The time-stamp of the
search marker may not be greater than the given time (i.e. less than or equal to).
If a priority is given (input > 0), the current marker will be determined with this priority.
Note: The "Read marker" function can then determine further information about the marker.
Arguments:
Name
Channel ID
Type
Input value

May 2011
Description
ID of the channel whose current marker is to
963
Time
Priority
Marker ID
Output value
be determined
Input: The time-stamp of the determined
marker may not be greater than this time (i.e.
less than or equal to)
Output: Time-stamp of the determined marker
Input: Marker priority
0:
No priority
Output: Priority of the determined marker
ID of the determined marker
Return code:
0: Function failed
Result
Next marker
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Next
marker
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Next marker(In: Channel ID

\Object InOut: Time\Object, priority\Object, Out: marker ID\Object, LVResult)
This function determines the next marker for the given channel. The time-stamp of the
search marker must be greater than the given time.
If a priority is given (input > 0), the next marker will be determined with this priority.
Note: The "Read marker" function can then determine further information about the marker.
Arguments:
Name
Channel ID
Type
Input value
Time
Description
ID of the channel whose next marker is to be
determined
Input: The time-stamp of the determined
marker must be greater than this time-stamp
Output: Time-stamp of the determined marker
964

May 2011
Priority
Marker ID
Output value
Input: Marker priority

0:
No priority
Output: Priority of the determined marker
ID of the determined marker
Return code:
0: Function failed
Result
Show textlabel
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Show textlabel
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Show textlabel (In: visible\Object,

Name\Object, Out: textlabel count\Object, LVResult)
This function shows or hides an existing text label in a trend diagram. If no name is given
(Name = ""), then all text labels are shown / hidden.
Arguments:
Name
visible
Type
Input value
Name
Text label
count
Input value
Output value
Description
Yes. name text label
No: Hide text label
Name of text field to be shown/hidden
Number of text labels
Return code:
Result
0: Function failed

May 2011
965
Other functions
print Trend
print Trend
Yt-diagram
YX-diagram (table)
Logic diagram
Orbit diagram
FFT diagram
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
print
Trend
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: print Trend(In: with dialog\Var

Out: LVResult)
This function prints out the trend.
Arguments:
Name
With dialog
Type
Input value
Description
Display a print dialog? ( Yes/No )
Return code:
Result
0: Function failed
Recorder functions
Pause
Recording
966

May 2011

Take single step
Refer also to the channel selection functions:

Clear channel group
Add channel
Delete channel
Pause
Script
Initiate
Visualisation
[VisuView name]
Recorder
[Recorder name]
Pause
This generates the following instruction core with VisuView name and recorder name being
placeholders for actual names:
Initiate Visualisation\VisuView_1\Rec.Recorder_1: Pause(In: Pause\Object Out: LVResult)

This function enables an active recording to be paused or continued.
Arguments:
Name Type
Pause Input value
Description
Whether the recording is to be paused or continued (Yes/No)
Return code:
0: Function failed
Result
Recording
Script
Initiate
Visualisation
[VisuView name]
Recorder
[Recorder name]
Recording
Initiate Visualisation\VisuView_1\Rec.Recorder_1: Recording(In: start\Object Out: LVResult)

May 2011
967
This function starts or ends a recording.
Arguments:
Name
Start
Type
Input value
Description
Whether the recording is to be started or ended (Yes/No)
Return code:
0: Function failed
Result

Script
Initiate
Visualisation
[VisuView name]
Recorder
[Recorder name]
Cancel last
recording
placeholders for actual names.
Initiate Visualisation\VisuView_1\Rec.Recorder_1: Cancel last recording (LVResult)

This function cancels the last recording.
Return code:
0: Function failed
Result
Take single step

Script
Initiate
Visualisation
[VisuView name]
Recorder
[Recorder name]
Take single step
Initiate Visualisation\VisuView_1\Rec.Recorder_1: Cancel last recording (LVResult)

The function saves a data record to the measurement data file (corresponding to the single
step key on the recorder).
968

May 2011
Return code:
Result
0: Function failed
Info:
Clear channel group (obsolete)

Add channel (obsolete)
Delete channel (obsolete)
back to online Trend (obsolete)
Freeze diagram (obsolete)
Show timerange (obsolete)
Show last recording (obsolete)
Set online timerange (obsolete)
Export to MesFile (obsolete)
ASCII export (obsolete)
Load MesFile (obsolete)
print Trend (obsolete)
Load config (obsolete)
Save config (obsolete)
Save config to MesFile (obsolete)
Suppress update (obsolete)
Clear drawing area (obsolete)
Clear channel group (obsolete)


May 2011
969
Yt-diagram
Recorder
Logic diagram
Orbit diagram
FFT diagram

available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Clear channel group

Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Clear channel group()

This function deletes all the channels from the channel list of a diagram or recorder.

Yt-diagram
Recorder
Logic diagram
Orbit diagram
FFT diagram

available.
Script
Initiate
Visualisation
[VisuView name]
970
[Visu-Obj ect type]
[Visu-Obj ect name]
Add

May 2011
channel
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Add channel(In: Channel ID

\Object)
This function adds a channel to the channel list of a diagram or recorder.
Arguments:
Name
Channel ID
Type
Input value
Description
ID of the channel to be added to the channel list

Yt-diagram
Recorder
Logic diagram
Orbit diagram
FFT diagram

available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Delete channel
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Delete channel(In: Channel ID

\Object)
This function deletes a channel from the channel list of a diagram or recorder.
Arguments:

May 2011
971
Name
Channel ID
Type
Input value
Description
ID of the channel to be deleted from the channel list
back to online Trend (obsolete)

Yt-diagram
Recorder
Logic diagram
Orbit diagram
FFT diagram

available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]

Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: back to online Trend()

This function overrides the freeze mode in a diagram's graphical portrayal. For a detailed
Freeze diagram (obsolete)

Yt-diagram
Recorder
Logic diagram
Orbit diagram
FFT diagram
972

May 2011

available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Freeze diagram
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Freeze diagram()

This function activates the freeze mode for a diagram's graphic portrayal. For a detailed
Show timerange (obsolete)

Yt-diagram
Recorder
Logic diagram
Orbit diagram
FFT diagram

available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Show timerange
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Show timerange(In: start time/

end time\Object, timerange\Object)

May 2011
973
This function sets the timerange to be shown in the diagram. When the range is negative it
is assumed an end time has been given. Refer also to Trend operation.
Arguments:
Name
Start time/ end
time
Timerange
Type
Input value
Description
Start time or end times of the portrayal (UTC time)
Input value
Timerange for the portrayal (UTC time). Negative for

end time.
Show last recording (obsolete)

Yt-diagram
Recorder
Logic diagram
Orbit diagram
FFT diagram

available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Show last recording

Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Show last recording()

This function is used when the diagram is linked to a recorder. When the recorder is
stopped, this instruction enables the display of the last recorded value. Refer also to Trend
operation.
974

May 2011
Set online timerange (obsolete)

Yt-diagram
Logic diagram

available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Set
online timerange
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Set online timerange(In:

timerange\Object)
This functions sets the timerange to be displayed in a diagram's graphical portrayal prior
to scrolling the window's content. Refer also to Trend operation.
Arguments:
Name
Timerange
Type
Input value
Description
Timerange to be displayed in graphical portrayal (UTC
time)
Export to MesFile (obsolete)

Yt-diagram
YX-diagram (table)

May 2011
975
Logic diagram
Orbit diagram
available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Export to MesFile
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Export to MesFile(In: File name

\Object, Start time\Object, End time\Object Out: LVResult)
This function exports a diagram's data.
Arguments:
Name
File name
Type
Description
exported.
Start time
End time
Return code:
Result
0: Export failed
1: Export succeeded
ASCII export (obsolete)

Yt-diagram
YX-diagram (table)
Logic diagram
Orbit diagram
976

May 2011

available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
ASCII export
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: ASCII export(In: File name

\Object, Start time\Object, End time\Object Out: LVResult)
This function exports a diagram's data in ASCII format. Ensure that the start time is earlier
than the end time and that the end time does not lie in the future.
Arguments:
Name
File name
Type
Description
exported.
Start time
End time
Return code:
Result
0: Export failed
1: Export succeeded
Load MesFile (obsolete)

Yt-diagram
YX-diagram (table)
Logic diagram
Orbit diagram
FFT diagram

May 2011
977

available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Load MesFile
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Load MesFile(In: File name

\Object)
This function loads a measurement data file into the diagram.
Arguments:
Name
File name
Type
Input
value
Description
Name of the measurement data file (including path) to be
loaded.
print Trend (obsolete)

Yt-diagram
YX-diagram (table)
Logic diagram
Orbit diagram
FFT diagram
available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
print
Trend
978

May 2011
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: print Trend(In: with dialog

\Object)
This function prints out the trend.
Arguments:
Name
With dialog
Type
Input value
Description
Display a print dialog? ( Yes/No )
Load config (obsolete)

Yt-diagram
YX-diagram (table)
Logic diagram
Orbit diagram
FFT diagram
available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Load config
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Load config(In: File name

\Object)
This function loads a diagrams configuration settings from a configuration file.

May 2011
979
Arguments:
Name
File name
Type
Description
Input value Name of the configuration file (including path) to be
loaded.
Save config (obsolete)

Yt-diagram
YX-diagram (table)
Logic diagram
Orbit diagram
FFT diagram
available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Save config
Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Save config(In: File name

\Object)
This function saves a diagrams configuration settings to a configuration file.
Arguments:
Name
File name
Type
Input value
Description
Name of the file (including path) to which the
configuration is to be saved
980

May 2011
Save config to MesFile (obsolete)

Yt-diagram
YX-diagram (table)
Logic diagram
Orbit diagram
FFT diagram
available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]

Initiate Visualisation\VisuView_1\Yt-diagram.Yt-Diagram_1: Save config to MesFile()

This function saves a diagrams configuration settings directly to the measurement data file
being displayed.
Set X-axis range (obsolete)

YX-diagram (table)
Orbit diagram

May 2011
981

available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Set
X-axis range
Initiate Visualisation\VisuView_1\YX-diagram (channel).YX-diagram (channel)_1: Set X-axis

range(In: Range low\Object, Range high\Object)
This functions sets the X-axis range.
Arguments:
Name
Range low
Range high
Type
Input value
Input value
Description
Set Y-axis range (obsolete)

YX-diagram (table)
Orbit diagram

available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Set
Y-axis range
982

May 2011
Initiate Visualisation\VisuView_1\YX-diagram (channel).YX-diagram (channel)_1: Set Y-axis

range(In: Axis\Object, Range low\Object, range high\Object)
This functions sets the Y-axis range.
Arguments:
Name
Axis
Range low
Range high
Type
Input value
Input value
Input value
Description
The Y-axis for which the range is to be set.
Set X-axis channel (obsolete)

YX-diagram (table)
Orbit diagram

available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Set
X-axis
Initiate Visualisation\VisuView_1\YX-diagram (table).YX-diagram (table)_1: Set X-axis

channel(In: Channel ID\ObjectOut: LVResult)
This function assigns a channel to an X-axis.

May 2011
983
Arguments:
Name
Channel ID
Type
Input value
Description
The channel that is to be assigned to the
X-axis.
Return code:
0: Function failed
Result
Suppress update (obsolete)

YX-diagram (table)

available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Suppress update
Initiate Visualisation\VisuView_1\YX-diagram (table).YX-diagram (table)_1: Suppress

update(In: suppress\Object)
This function determines whether updating of the portrayal is to be suppressed.
Arguments:
Name
Suppress
Type
Input value
Description
Whether the update is to be suppressed (Yes/No)
984

May 2011
Clear drawing area (obsolete)

Orbit diagram

available.
Script
Initiate
Visualisation
[VisuView name]
[Visu-Obj ect type]
[Visu-Obj ect name]
Clear drawing area

Initiate Visualisation\VisuView_1\Yt-diagram (channel).Yt-diagram_1 (channel): Clear

drawing area()
This functions clears a diagram's graphical portrayal.
2.4.3.9.1.6 Profile
The following functions are available for profiles (refer also to Profile visuobject).
Reset profile
Script
Initiate
Visualisation
[VisuView name]
Profile
[Profile name]
Reset profile
This generates the following instruction core with VisuView name and profile name being
Initiate Visualisation\VisuView_1\Prof ile.Prof ile_1: Reset profile()

Script
Initiate
Input parameter

May 2011
[Page name]
Profile
[Profile name]
Reset profile
985
This generates the following instruction core with page name and profile name being
Initiate Parameter\Page_1\Prof ile.Prof ile_1: Reset profile()

This function resets the profile (refer also to Profile visuobject).
2.4.3.9.1.7 Alarm list
The following functions are available for alarm lists (refer also to Alarm list visuobject).
Historical alarms
Clean up
Online
Load configuration
Save configuration
Export
Confirm horn
Historical alarms
Script
Initiate
Visualisation
[VisuView name]
Alarmlist
[Alarm list name]
Historical
alarms
This generates the following instruction core with VisuView name and alarm list name being
Initiate Visualisation\VisuView_1\Alarm.Alarmlist_1: Historical alarms(In: Start time\Object,

End time\Object Out: LVResult)
This function outputs archived alarms that have time-stamps between the start and end
times. Users are then in offline mode.
Arguments:
Name
Start time
End time
Type
Input value
Input value
Description
Time-stamp of the first alarm to be displayed
Time-stamp of the last alarm to be displayed
Return code:
986

May 2011
0: Function failed
Result
Clean up
Script
Initiate
Visualisation
[VisuView name]
Alarmlist
[Alarm list name]
Clean up
Initiate Visualisation\VisuView_1\Alarm.Alarmlist_1: Clean up()

This function deletes from the alarm list (ongoing alarms) confirmed alarms and those
alarms that are not to be confirmed.
Online
Script
Initiate
Visualisation
[VisuView name]
Alarmlist
[Alarm list name]
Online
Initiate Visualisation\VisuView_1\Alarm.Alarmlist_1: Online()

This function switches between archived/historical alarms and current alarms.
Load configuration
Script
Initiate
Visualisation
[VisuView name]
Alarmlist
[Alarm list name]
Load
configuration
Initiate Visualisation\VisuView_1\Alarm.Alarmlist_1: Load configuration(In: File name\Object

Out: LVResult)
This function loads configuration settings for the alarm list from the given file.

May 2011
987
Arguments:
Name
File name
Type
Input value
Description
Name of the configuration file
Return code:
0: Function failed
Result
Save configuration
Script
Initiate
Visualisation
[VisuView name]
Alarmlist
[Alarm list name]
Save
configuration
Initiate Visualisation\VisuView_1\Alarm.Alarmlist_1: Save configuration(In: File name\Object

Out: LVResult)
This function saves configuration settings for the alarm list to the given file.
Arguments:
Name
File name
Type
Input value
Description
Return code:
0: Function failed
Result
Export
Script
Initiate
Visualisation
[VisuView name]
988
Alarmlist
[Alarm list name]
Export

May 2011
Initiate Visualisation\VisuView_1\Alarm.Alarmlist_1: Export(In: File name\Object Out:

LVResult)
This function exports the entire alarm list to the given file. Its is saved as a CSV file that
can be opened in Excel.
Arguments:
Name
File name
Type
Input value
Description
Name of the export file
Return code:
0: Function failed
Result
Confirm horn
Script
Initiate
Visualisation
[VisuView name]
Alarmlist
[Alarm list name]
Confirm horn
Initiate Visualisation\VisuView_1\Alarm.Alarmlist_1: Confirm horn()

This function prevents horn/siren output when a new alarm is triggered that has triggered
the alarm.
Info:
Historical alarms
Load configuration

May 2011
989
Save configuration
Export
Historical alarms
Script
Initiate
Visualisation
[VisuView name]
Alarmlist
[Alarm list name]
Historical
alarms
Initiate Visualisation\VisuView_1\Alarm.Alarmlist_1: Historical alarms(In: Start time\Object,

End time\Object)
This function outputs archived alarms that have time-stamps between the start and end
times. Users are then in offline mode.
Arguments:
Name
Start time
End time
Type
Input value
Input value
Description
Time-stamp of the first alarm to be displayed
Time-stamp of the last alarm to be displayed
Load configuration
Script
Initiate
Visualisation
[VisuView name]
Alarmlist
[Alarm list name]
Load
configuration
Initiate Visualisation\VisuView_1\Alarm.Alarmlist_1: Load configuration(In: File name\Object)

This function loads configuration settings for the alarm list from the given file.
Arguments:
Name
File name
Type
Input value
Description
Save configuration
Script
Initiate
Visualisation
[VisuView name]
990
Alarmlist
[Alarm list name]
Save

May 2011
configuration
Initiate Visualisation\VisuView_1\Alarm.Alarmlist_1: Save configuration(In: File name\Object)

This function saves configuration settings for the alarm list to the given file.
Arguments:
Name
File name
Type
Input value
Description
Export
Script
Initiate
Visualisation
[VisuView name]
Alarmlist
[Alarm list name]
Export
Initiate Visualisation\VisuView_1\Alarm.Alarmlist_1: Export(In: File name\Object)

This function exports the entire alarm list to the given file. Its is saved as a CSV file that
can be opened in Excel.
Arguments:
Name
File name
Type
Input value
Description
Name of the export file
2.4.3.9.1.8 ODBC
ODBC includes the Visu-Objects ODBC connection, ODBC table and ODBC SQL. The following
object functions are available:
Connection ( ODBC connection)
Update table ( ODBC table)
Change table name ( ODBC table)

May 2011
991
First record ( ODBC table)

Next record ( ODBC table)
Update SQL query ( ODBC SQL )
Execute query ( ODBC SQL )
First record ( ODBC SQL)
Next record ( ODBC SQL)
(operation call successful or not successful). These include the ODBC table and ODBC SQL
functions and are assigned under configuration.
Column name
Field as string
Field as integer
Field as boolean
Field as double
Connect
Script
Initiate
Visualisation
[VisuView name]
ODBC connection
[ODBC connection name]
Connect
This generates the following instruction core with VisuView name and ODBC connection
name being placeholders for actual names.
Initiate Visualisation\VisuView_1\ODBC.ODBC connection 1: Connect(In: ODBC connection

name\Object, User name\Object, Password\Object Out: LVResult)
This function connects to an ODBC data source added under Windows. This function must
be performed prior to the object functions for ODBC table and ODBC SQL.
Arguments:
Name
ODBC connection
name
User name
Password
Type
Input value
Input value
Input value
Description
Name of the ODBC data source added under
Windows ( user DSN )
User name for the ODBC connection
Password for the ODBC connection
992

May 2011
Return code:
0: Connection failed
1: Connection succeeded
Result
Update table
Script
Initiate
Visualisation
[VisuView name]
ODBC table
[ODBC table name]
update
table
This generates the following instruction core with VisuView name and ODBC table name
being placeholders for actual names.
Initiate Visualisation\VisuView_1\ODBC table.ODBC table_1: update table(Out: LVResult)

This function updates the contents of the table in respect of the assigned ODBC
connection and database table (refer to ODBC table).
Return code:
0: Table successfully updated
1: Update failed
Result
Change table name

Script
Initiate
Visualisation
[VisuView name]
ODBC table
[ODBC table name]
Change
table name
Initiate Visualisation\VisuView_1\ODBC table.ODBC table_1: Change table name(In: table

name\Object Out: LVResult)
This functions changes the database table to which the table is assigned (refer also to
ODBC table).
Arguments:
Name
Table name
Type
Input value

May 2011
Description
Name of the assigned database table
993
Return code:
1: Table name successfully changed.
0: Table name change failed. In this event the old name remains
unchanged.
Result
First record ( ODBC table)

Script
Initiate
Visualisation
[VisuView name]
ODBC table
[ODBC table name]
first
record
Initiate Visualisation\VisuView_1\ODBC table.ODBC table_1: first record(Out: LVResult)

This function extracts the first record from the database table (refer also to ODBC table).
Access to the data is via Configuration Field as string, Field as integer, Field as boolean or
Field as double.
Return code:
1: First record accessed successfully

0: Table contains no data
Result
Next record ( ODBC table)

Script
Initiate
Visualisation
[VisuView name]
ODBC table
[ODBC table name]
next
record
Initiate Visualisation\VisuView_1\ODBC table.ODBC table_1: next record(Out: LVResult)

This function extracts the next record from the database table (refer also to ODBC table).
Access to the data is via Configuration Field as string, Field as integer, Field as boolean or
Field as double.
Return code:
Result
1: Next record accessed successfully

0: There is no next record
994

May 2011
Update SQL query

Script
Initiate
Visualisation
[VisuView name]
ODBC SQL
[ODBC SQL name]
Update
SQL query
This generates the following instruction core with VisuView name and ODBC SQL name
Initiate Visualisation\VisuView_1\ODBC SQL.ODBC SQL_1: update SQL query(Out:

LVResult)
This function updates the contents of an SQL query's result set (refer also to ODBC SQL).
Return code:
0: SQL query successfully updated
1: Update failed
Result
Execute query
Script
Initiate
Visualisation
[VisuView name]
ODBC SQL
[ODBC SQL name]
execute
query
Initiate Visualisation\VisuView_1\ODBC SQL.ODBC SQL_1: execute query(In: Query\Object

Out: LVResult)
This function assigns a new SQL query to the SQL query and then carries it out (refer also
to ODBC SQL).
Arguments:
Name
Query
Type
Input value
Description
New SQL query
Return code:
1: Instruction successful
0: Execute failed
Result
First record ( SQL Query )

Script
Initiate
Visualisation

May 2011
[VisuView name]
ODBC SQL
[ODBC SQL name]
first record
995
Initiate Visualisation\VisuView_1\ODBC SQL.ODBC SQL_1: first record(Out: LVResult)

This function extracts the first record from the SQL query's result set (refer also to ODBC
table). Access to the data is via Configuration Field as string, Field as integer, Field as
boolean or Field as double.
Return code:
1: First record accessed successfully

0: No data returned from the SQL query
Result
Next record ( SQL Query )

Script
Initiate
Visualisation
[VisuView name]
ODBC SQL
[ODBC SQL name]
next record
Initiate Visualisation\VisuView_1\ODBC SQL.ODBC SQL_1: next record(Out: LVResult)

This function extracts the next record from the SQL query's result set (refer also to ODBC
table). Access to the data is via Configuration Field as string, Field as integer, Field as
boolean or Field as double.
Return code:
Result
1: Next record accessed successfully

0: There is no next record
2.4.3.9.2 Parameter input
This section contains object functions associated with the ParameterView or elements of
the parameter view. Object
functions for the ParameterView

Load parameter
Save parameter
Open ParameterView
Close ParameterView
996

May 2011


Script
Initiate
Input Parameter
Initiate Parameter: Load parameter from file(In: File name\Object Out: LVResult)
This function enables parameter input. Parameter data is read in from a file. Input can be
confirmed (with OK) or cancelled.
Arguments:
Name
File name
Type
Input value
Description
File (including path) from which the parameter data
is to be read
Return code:
0: Connection failed
1: File successfully opened
Result

Script
Initiate
Input Parameter
Initiate Parameter: Load parameter without file(Out: LVResult)

This function enables parameter input without a file being used to read in data. Input can
be confirmed (with OK) or cancelled.
Return code:
Result
0: Parameter input failed

1: Parameter input succeeded
Load parameter

May 2011
997
Script
Initiate
Input Parameter
Load parameter
Initiate Parameter: Load parameter(Out: File name\Object Out: LVResult)

This function loads parameter input from the given file name.
Arguments:
Name
File name
Type
Input value
Description
File (including path) from which the parameter
data is to be loaded
Return code:
0: Data failed to load
Result
1: Data loaded successfully
Save parameter
Script
Initiate
Input Parameter
save parameter
Initiate Parameter: save parameter(In: File name\Object, Overwrite\Object Out: LVResult)

This function saves parameter input to the given file name and indicates whether or not an
existing file is to be over-written.
Arguments:
Name
File name
Type
Input value
Overwrite
Input value
Description
File (including path) from which the parameter
data is to be loaded
Should an existing file be overwritten ( Yes/No)
Return code:
Result
0: Data failed to save

1: Data saved successfully
998

May 2011
Open ParameterView
Script
Initiate
Input Parameter
Open ParameterView
Initiate Parameter: Open ParameterView()

This function opens a parameter view. Parameter input is not possible!
Close ParameterView
Script
Initiate
Input Parameter
Close ParameterView
Initiate Parameter: Close ParameterView()

This function closes a parameter view.

Script
Initiate
Input Parameter
Initiate Parameter: Recipe value to value()

So-called "recipes" can be input via a ParameterView. A recipe is made up of the individual
values portrayed in a parameter view. These values are saved when a recipe is required.
The saved data can then be processed while a new recipe is being set up in the parameter
view.
This function reads saved recipe data and writes it to a parameter view.

Script
Initiate
Input Parameter
Initiate Parameter: Value to recipe value()

May 2011
999
So-called "recipes" can be input via a ParameterView. A recipe is made up of the individual
values portrayed in a parameter view. These values are saved when a recipe is required.
The saved data can then be processed while a new recipe is being set up in the parameter
view.
This function saves the data from a parameter view as a recipe.
Object functions for ParameterView objects

Dropdown box
Table
Profile
2.4.3.9.3 Report
The following object functions are available for reports.

Functions for report files:
Open report file
Print report to default printer
Close report
Close all reports
Functions for generating reports:

Start report
Start report with default name
Stop report
DataCommit
Functions for report objects:
Daten bernehmen (Unterreport)

Start- und Endzeit (Alarmliste)
1000

May 2011
2.4.3.9.3.1 Functions for report files
Open report file

Close report
Close all reports
Open report file

Script
Initiate
Report
Open report file
Initiate Report: Open report file(In: Report file\Object, Front\Object, Full screen\Object Out:
LVResult)
This function opens a report file with the option to open in full screen mode.
Arguments:
Name
Report file
Front
Full screen
Type
Input value
Input value
Input value
Description
File (including path) to be opened
Whether or not the file is to be placed in the foreground
Should the report start in full screen mode?
Return code:
0: Function failed
Result

Script
Initiate
Report
Initiate Report: Print report to default printer (Report file\Object)

This function prints the report file to the default printer.

May 2011
1001
Arguments:
Name
Report file
Type
Input value
Description
File (including path) to be printed
Close report
Script
Initiate
Report
Close report
Initiate Report: Close report(In: Report file\Object Out: LVResult)

This function closes a report file.
Arguments:
Name
Report file
Type
Input value
Description
File (including path) to be closed
Return code:
<0: Function failed
Result
Close all reports

Script
Initiate
Report
Close all reports
Initiate Report: Close all reports(Out: LVResult)

This function closes all open report files.
Return code:
Result
<0: Function failed

1002

May 2011
2.4.3.9.3.2 Functions for generating reports
Start report
Stop report
DataCommit
Start report
Script
Initiate
Report
[Report name]
Start report
This function generates the following instruction core with Report name being a placeholder
for an actual report:
Initiate Report\Rep ort_1: Start report(In: Report file name\Object, append existing report file
This function starts a report and requires the report's file name. It also determines
whether the report is new or is to be appended to an existing report.
To append to an existing report enter yes. The report with the given file name is opened
and a record is added for each DataCommit function. If the report file does not already
exist, a new report with the given name is created.
To append to an existing report enter no. This creates a report with the given file name.
If a file with this name already exists, a new report name will be generated from the given
file name plus a sequential number.
Arguments:
Name
File name of the report
append existing report file
Type
Input value
Input value
Description
File (including path) to be started
Should the existing report be appended?
Return code:
Result
<0: Function failed


May 2011
1003
Script
Initiate
Report
[Report name]

This function starts the report with the file name automatically generated from the report
object name, date and time.
Return code:
0: Function failed
Result
Stop report
Script
Initiate
Report
[Report name]
Stop report

This function stops the report.
Return code:
0: Function failed
Result
Commit data
Script
Initiate
Report
[Report name]
Commit data

Once a report has been started, this function saves report data to the report file.
1004

May 2011
2.4.3.9.3.3 Functions for report objects
Some report objects provide extra functions for creating a report.
Commit data (subreport)

Start- and endtime (alarmlist)
Commit data (subreport)

Script
Initiate
Report
[Report name]
[Name page]
[Name subreport]
Commit data
Initiate Report\Rep ort_1.Subrep ort: Commit data()

For each run, the report has a subreport page added (in this case "Report_1") by using the
DataCommit object function.
If you perform this object function four times before you commit the data to the report
(Report_1 DataCommit), the report has four subreport pages added to it.
Start- and endtime (alarmlist)

Script
Initiate
Report
[Report name]
[Name page]
Alarmlist
[Name alarmlist]
Commit
data
Initiate Report\Rep ort_1.Page.Rep ortp age_1.Alarmlist.Rep ort Alarmlist_1: Start- and

endtime(In: Start time\Object, End time\Object Out: LVResult)
This function sets the time range from which the alarms are to be portrayed.
The start and end times must be run before running the DataCommit function.
Arguments:
Name
Start time
End time

May 2011
Type
Description
Input value Start time
Input value End time for the time range from which the alarms are to
be portrayed
1005
Return code:
Result
0: Function failed
2.4.3.9.3.4 Functions obsolete
Info:
Open report file (old)
Open report file (old)
Initiate Report: Open report file (old)(In: Report file\Object, Full screen\Object)
This function opens a report file with the option to open in full screen mode.
Arguments:
Name
Report file
Full screen
Type
Input value
Input value
Description
Should the report start in full screen mode?
2.4.3.9.4 Channel
The following object functions for channels are available in extended mode.
Check value state
Get actual value
1006

May 2011
Get channel ID
Get channel ID from device
Get channel name
Get device activ
Get extended channel info
Get device number
Check value state

Script
Initiate
Channel
Check value state
Initiate Channel: Check value state(In: State variable\Object, State\Object Out:LVResult)

This function tests whether the state variable corresponds to the given state.
Further information on value state is available in the Value state section.
Arguments:
Name
State variable
State
Type
Input value
Input value
Description
Variable state to be tested
State to be tested:
Scaled Value
Forced Value
Invalid
Connection Offline
Changed datatyp
Wrong configuration
Defect hardware
Wire Break
Upper range
Lower range
Invalid value
Infinite value
No number
Alarm
Incomplete calculation
No data
All errors
Return code:
Result
0: Variable state does not equal given state

May 2011
1007
1: Variable state equals given state
Get actual value

Script
Initiate
Channel
Get actual value
Initiate Channel: Get actual value(In: Channel ID\Object Out: Time\Object, Value\Object, State
\Object, LVResult)
This function determines the following information for the channel with the given Channel
ID: the current value; the time when the value was acquired; the state (value state).
Arguments:
Name
Channel ID
Time
Value
State
Type
Input value
Output value
Output value
Output value
Description
Channel whose value is to be determined
Time stamp from the acquired channel value
Channel value
State:
Scaled Value
Forced Value
Invalid
Connection Offline
Changed datatyp
Wrong configuration
Defect hardware
Wire Break
Upper range
Lower range
Invalid value
Infinite value
No number
Alarm
No data
The value state can be checked with the
function Check value state.
Return code:
Result
0: Function failed
1008

May 2011
Get channel ID
Script
Initiate
Channel
Get channel ID
Initiate Channel: Get channel ID(In: Channel name\Object Out: Channel ID\Object, LVResult)
This function determines the channel ID for the given channel.
Arguments:
Name
Type
Channel name Input value
Channel ID
Output value
Description
Channel whose ID is to be determined
Channel ID for channel
Return code:
0: Function failed
Result

Script
Initiate
Channel
Initiate Channel: Get channel ID from device(In: Channel name\Object, Device name\Object
Out: Channel ID\Object, LVResult)
This function determines the channel ID for the given channel name of a specific device.
Arguments:
Name
Channel name
Device name
Channel ID
Type
Input value
Input value
Output value
Description
Channel whose ID is to be determined
Device on which channel is located
Channel ID for channel
Return code:

May 2011
1009
0: Function failed
Result
Get channel name

Script
Initiate
Channel
Get channel name
Initiate Channel: Get channel name(In: Channel ID\Object Out: Channel ID\Object, LVResult)
This function determines the channel name for the given channel ID.
Arguments:
Name
Channel ID
Type
Input value
Channel name Output value
Description
Channel ID of the channel whose name is to be
determined
Name of channel
Return code:
0: Function failed
Result
Get device activ

Script
Initiate
Channel
Get device activ
Initiate Channel: Get device activ(In: Channel ID\Object Out: Active\Object, LVResult)
This function determines whether the channel with the given channel ID is active.
Arguments:
Name
Channel ID
Active
Type
Input value
Output value
Description
Channel ID of the channel to be tested
Is the channel active ( 1) or inactive ( 0 )
Return code:
1010

May 2011
0: Function failed
Result

Script
Initiate
Channel
Initiate Channel: Get extended channel info(In: Channel ID\Object Out: Unit\Object, Min
\Object, Max\Object, Decimal places\Object,Channel type\Object, Comment\Object,
Location\Object, LVResult)
This function determines channel information for the given channel ID.
Arguments:
Name
Channel ID
Unit
Min
Max
Decimal places
Channel type
Comment
Location
Type
Input value
Output
value
Output
value
Output
value
Output
value
Output
value
Output
value
Output
value
Description
ID of the channel whose information is to be determined
Channel unit
Minimum value for the channel
Maximum value for the channel
Number of decimal places
Channel type
Comment
Channel location
Return code:
0: Function failed
Result
Get device number

Script
Initiate
Channel
Get device number

May 2011
1011
Initiate Channel: Get device number(Out: Number\Object, LVResult)

This function determines the number of devices connected to the DataService.
Arguments:
Name
Number
Type
Output value
Description
Number of devices in DataService
Return code:
0: Function failed
Result
2.4.3.9.5 Application
The following object functions are available for applications.

Open
Close
Get application ID
Get application directory
Get default image directory
Get default config directory
Get default measurement directory
Get default report directory
Get default parameter directory
Get project directory
Open
Script
Initiate
Application
Open
Initiate Application: Open application(In: Application name\Application name(Out: LVResult)

This function opens the given application.
1012

May 2011
Arguments:
Name
Application name
Type
Input value
Description
Name of the application (including path) to be opened
Return code:
0: Open failed
1: Open succeeded
Result
Close
Script
Initiate
Application
Close
Initiate Application: Stop application(In: Application name\Application name)

This function closes the given application.
Arguments:
Name
Type
Description
Application name
Input value Name of the application (including path) to be closed
Get application ID
Script
Initiate
Application
Get application ID
Initiate Application: Get application ID(In: Application name\Application name Out: Application
ID\Object, LVResult)
This function determines the ID of the given application.
Arguments:
Name
Application name

May 2011
Type
Input value
Description
Name of the application whose ID is to be
determined
1013
Application ID
Output value
Application ID
Return code:
0: Function failed
Result

Script
Initiate
Application
Initiate Application: Get application directory(Out: Directory\Object LVResult)

This function determines the directory in which the application is located.
Arguments:
Name
Directory
Type
Output
value
Description
The variable to which the directory is returned.
Return code:
1: The directory could be determined
0: The directory could not be determined
Result

Script
Initiate
Application
Initiate Application: Get default image directory(Out: Directory\Object LVResult)

This function determines the default directory in which the application's images are located.
1014

May 2011
Arguments:
Name
Directory
Type
Output
value
Description
Return code:
Result

Script
Initiate
Application
Initiate Application: Get default config directory(Out: Directory\Object LVResult)

This function determines the default directory in which the application's configuration
information is located.
Arguments:
Name
Directory
Type
Output
value
Description
Return code:
Result

Script
Initiate
Application

May 2011
1015
Initiate Application: Get default measurement directory(Out: Directory\Object LVResult)

This function determines the default directory in which the application's measurement data
files are located.
Arguments:
Name
Directory
Type
Output
value
Description
Return code:
Result

Script
Initiate
Application
Initiate Application: Get default report directory(Out: Directory\Object LVResult)

This function determines the default directory in which the application's reports are
located.
Arguments:
Name
Directory
Type
Output
value
Description
Return code:
Result

1016

May 2011

Script
Initiate
Application
Initiate Application: Get default parameter directory(Out: Directory\Object LVResult)

This function determines the default directory in which the application's parameter files are
located.
Arguments:
Name
Directory
Type
Output
value
Description
Return code:
Result

Script
Initiate
Application
Get proj ect directory
Initiate Application: Get project directory(Out: Directory\Object LVResult)

This function determines the project directory to which the application belongs.
Arguments:
Name
Directory
Type
Output
value
Description
Return code:
Result


May 2011
1017
2.4.3.9.6 File
The following object functions are available for files.

Copy file
Delete file
File exists
Show file dialog
Show file dialog with Path
Open MesFile in analyse view
Open MesFile dialog
Copy file
Script
Initiate
File
Copy file
Initiate File: Copy file(In: Source file\Object, Destination file\Object, Override\Object

Out:LVResult)
This function copies the source file to the target/destination file.
Arguments:
Name
Source file
Destination file
Override
Type
Input value
Input value
Input value
Description
File (including path) to be copied
Target/destination file (including path)
Should an existing file be overwritten (Yes/No)
Return code:
-2: Copying failed because the file to be copied does not
exist
-3:Copying failed because target/destination file is write
protected.
0: Copy failed
1: Copy succeeded
Result
Delete file
Script
Initiate
File
Delete file
1018

May 2011
Initiate File: Delete file(In: File name\Object Out: LVResult)

This function deletes the given file.
Arguments:
Name
File name
Type
Input value
Description
File (including path) to be deleted
Return code:
0: Delete failed
1: Delete succeeded
Result
File exists
Script
Initiate
File
File exists
Initiate File: File exists(In: File name\Object Out: LVResult)

This function tests whether the given file exists.
Arguments:
Name
File name
Type
Input value
Description
File (including path) whose existence is to be tested.
Return code:
0: File does not exist
1: File exists
Result
Show file dialog

Script
Initiate
File
Show file dialog
This generates the following instruction core.
Initiate File: Show file dialog(In: Title\Object, Filter\Object Out: LVResult)

May 2011
1019
This function opens the file dialog with the given title and filter. The default directory,
in which the dialog is opened depends on the filter that specifies the file type to be
displayed.
Arguments:
Nam
e
Title
Filter
Type
Description
Input
value
Input
value
Title of dialog
The file filter for the dialog. This determines what is to be shown as
entries in the "File type" dropdown box of the file dialog. For example,
to display project files( *.dpa ) and runtime project files (*.drt ), the
following filters can be used
1.) ProfiSignal project (*.dpa,*.drt)|*.dpa;*.drt
2.) ProfiSignal project(*.dpa)|*.dpa|ProfiSignal runtime project
(*.drt)|*.drt
3.) *.dpa;*.drt
In the first case, the "File type" dropdown box contains the entry
"ProfiSignal project (*.dpa,*.drt)" and all files with dpa and drt
extensions are displayed. The entry name and associated file
extensions are separated in the filter by the | symbol. When, as in
this example, there is more than one extension, they are separated
by a ";"
In the second case, the "File type" dropdown box contains
both"ProfiSignal project (*.dpa)" and "ProfiSignal runtime project
(*.drt)" entries. Selecting the first entry displays all files with the dpa
extension, and selecting the second entry displays files with the drt
extension. The different entries are separated in the dialog through
the | symbol!
In the third case, only the file extensions to be displayed are given
with multiple entries being separated by a ";".
Return code:
Result
If a file is selected within the dialog and the dialog is closed with OK, the
return code is the file name including path. Otherwise, the return code is
text at the length of 0 (i.e. '' ).

Script
Initiate
File
1020

May 2011
Initiate File: Show file dialog with Path(In: Title\Object, Filter\Object, Path\Object Out:
LVResult)
This function opens the file dialog in the given directory with the given title and filter.
Arguments:
Name
Path
Title
Filter
Type
Input value
Input value
Input value
Description
Directory in which the dialog is to be displayed
Title of dialog
The file filter for the dialog. This determines what is to be shown
as entries in the "File type" dropdown box of the file dialog. For
example, to display project files( *.dpa ) abd runtime project files
(*.drt ), the following filters can be used
1.) ProfiSignal project (*.dpa,*.drt)|*.dpa;*.drt
2.) ProfiSignal project(*.dpa)|*.dpa|ProfiSignal runtime project
(*.drt)|*.drt
3.) *.dpa;*.drt
In the first case, the "File type" dropdown box contains the entry
"ProfiSignal project (*.dpa,*.drt)" and all files with dpa and drt
extensions are displayed. The entry name and associated file
extensions are separated in the filter by the | symbol. When, as in
this example, there is more than one extension, they are separated
by a ";"
In the second case, the "File type" dropdown box contains
both"ProfiSignal project (*.dpa)" and "ProfiSignal runtime project
(*.drt)" entries. Selecting the first entry displays all files with the
dpa extension, and selecting the second entry displays files with
the drt extension. The different entries are separated in the dialog
through the | symbol!
In the third case, only the file extensions to be displayed are given
with multiple entries being separated by a ";".
Return code:
Result
If a file is selected within the dialog and the dialog is closed with OK, the
return code is the file name including path. Otherwise, the return code is
text at the length of 0 (i.e. '' ).

Script
Initiate
File

May 2011
1021
Initiate File: Open MesFile in analyse view(In: File name\Object, Front\Object Out: LVResult)
This function opens the given measurement file in an analysis window.
Arguments:
Name
File name
Front
Type
Input value
Input value
Description
Whether or not the analyse view is to be
placed in the foreground
Return code:
0: File failed to open.
1: File opened.
Result
Open MesFile in analyse view (obsolete)

Script
Initiate
File
Initiate File: Open MesFile in analyse view(In: File name\Object)

This function opens the given file.
Arguments:
Name
File name
Type
Input value
Description
Open MesFile dialog

Script
Initiate
File
Open MesFile dialog
Initiate File: Open MesFile dialog(In: Analyse view in front\Object Out: LVResult)
This function opens a measurement file dialog. The selected measurement file is then
opened in an analyse view.
1022

May 2011
Arguments:
Name
Analyse view in front
Type
Input value
Description
Whether or not the analyse view is to be placed
in the foreground
Return code:
0: File failed to open.
1: File opened.
Result
Open MesFile dialog in analyse view (obsolete)

Script
Initiate
File
Open MesFile dialog
Initiate File: Open MesFile dialog()

This function opens a measurement file dialog.
Close all analyse views

Script
Initiate
Report
Close all analyse views
Initiate File: Close all analyse views(Out: LVResult)

This function closes all open analysis windows.
Return code:
Result
0: Failed to close all analysis windows.

1: Closed all analysis windows.

May 2011
1023
2.4.3.9.7 Window
The following object functions are available for windows.

Show message dialog
Show MessageBox
Show color dialog
Show message dialog

Script
Initiate
Window
Show message dialog
Initiate Window: Show message dialog(In: Title\Object, Message\Object Out: LVResult)

This function opens a message dialog that prompts a user response.
Arguments:
Name
Title
Message
Type
Input value
Input value
Description
Title of message dialog to be opened
Message for the dialog
Return code:
0: Dialog ended with "No"
1: Dialog ended with "Yes"
Result
Show MessageBox
Script
Initiate
Window
Show MessageBox
Initiate Window: Show MessageBox(In: Title\Object, Message\Object )

This function opens a message box.
Arguments:
1024

May 2011
Name
Message
Type
Input value
Description
Message for the dialog
Show color dialog

Script
Initiate
Window
Show color dialog
Initiate Window: Show color dialog(Out: LVResult)

This function opens a message box.
Return code:
-1 : Dialog ended with "Cancel"
> -1: selected color value
Result
2.4.3.9.8 DateTime
The following object functions are available for DateTime.

Decode date
Decode time
Decode full time
Encode date and time
Encode date
Encode time
Encode full time
Convert Double into timestamp
Convert timestamp into Double
Decode date
Script
Initiate
DateTime
Decode date
Initiate DateTime: Decode date(In: Timestamp\Object Out: Year\Object, Month\Object, Day

\Object)
This function separates the given date into its separate elements.

May 2011
1025
Arguments:
Name
Date
Year
Month
Day
Type
Input value
Output value
Output value
Output value
Description
Date to be separated
Year value in date
Month value in date
Day value in date
Decode time
Script
Initiate
DateTime
Decode time
Initiate DateTime: Decode time(In: Timestamp\Object Out: Hours\Object, Minutes\Object,

Seconds\Object, Milliseconds\Object)
This function separates the given time into its separate elements.
Arguments:
Name
Time
Hours
Minutes
Seconds
Milliseconds
Type
Input value
Output value
Output value
Output value
Output value
Description
Time to be screened
Hour value in given time
Minute value in given time
Seconds value in given time
Milliseconds value in given time
Decode full time

Script
Initiate
DateTime
Decode full time
Initiate DateTime: Decode full time(In: Timestamp\Object Out: Hours\Object, Minutes\Object,

Seconds\Object, Milliseconds\Object, Microseconds\Object, Nanoseconds\Object)
This function separates the given time into its separate elements.
Arguments:
Name
Time
Hours
Type
Input value
Output value
Description
Time to be separateed
Hour value in given time
1026

May 2011
Minutes
Seconds
Milliseconds
Microseconds
Nanoseconds
Output
Output
Output
Output
Output
value
value
value
value
value
Minute value in given time

Seconds value in given time
Milliseconds value in given time
Microseconds value in given time
Nanoseconds value in given time

Script
Initiate
DateTime
Initiate DateTime: Encode date and time(In: Year\Object, Month\Object, Day\Object, Hours
\Object, Minutes\Object, Seconds\Object Out: DateTime\Object)
This function generates a date/time object from the given input.
Arguments:
Name
DateTime
Year
Month
Day
Hours
Minutes
Seconds
Type
Output value
Input value
Input value
Input value
Input value
Input value
Input value
Description
Generated date/time object
Year input
Month input
Day input
Hour input
Minute input
Seconds input
Encode date
Script
Initiate
DateTime
Encode date
Initiate DateTime: Encode date(In: Year\Object, Month\Object, Day\Object Out: Date\Object)

This function generates a date object from the given input.
Arguments:
Name
DateTime
Year
Month
Day
Type
Output value
Input value
Input value
Input value

May 2011
Description
Generated date/time object
Year input
Month input
Day input
1027
Encode time
Script
Initiate
DateTime
Encode time
Initiate DateTime: Encode time(In: Hours\Object, Minutes\Object, Seconds\Object, Milliseconds

\ObjectOut: Time\Object)
This function generates a time object (without micro and nano seconds) from the given
input.
Arguments:
Name
Time
Hours
Minutes
Seconds
Milliseconds
Type
Output value
Input value
Input value
Input value
Input value
Description
Time object
Hour input
Minute input
Seconds input
Millisecond input
Encode full time

Script
Initiate
DateTime
Encode full time
Initiate DateTime: Encode full time(In: Hours\Object, Minutes\Object, Seconds\Object,

Milliseconds\Object, Microseconds\Object, Nanoseconds\ObjectOut: Time\Object)
This function generates a time object (with micro and nano seconds) from the given input.
Arguments:
Name
Time
Hours
Minutes
Seconds
Milliseconds
Microseconds
Nanoseconds
Type
Output value
Input value
Input value
Input value
Input value
Input value
Input value
Description
Time object
Hour input
Minute input
Seconds input
Millisecond input
Microseconds input
Nanosecond input
1028

May 2011
Script
Initiate
DateTime
Initiate DateTime: Convert Double into timestamp(In: Double Date/Time\Object Out:

Timestamp\Object, LVResult)
This functions converts the double value into a timestamp.
Arguments:
Name
Double Date/Time
Timestamp
Type
Input value
Output
value
Description
Double value to be converted into a timestamp
Generated timestamp
Return code:
0: Conversion failed
1: Conversion succeeded
Result

Script
Initiate
DateTime
Initiate DateTime: Convert timestamp into Double(In: Timestamp\Object Out: Double Date/
Time\Object, LVResult)
This function converts the timestamp into a double.
Arguments:
Name
Timestamp
Double Date/Time
Type
Input value
Output
value
Description
Timestamp to be converted into a double
Generated double value
Return code:
Result
0: Conversion failed
1: Conversion succeeded

May 2011
1029
2.4.3.9.9 Processing messfile (HDS)
The following object functions for HDS measurement files are available in extended mode.
Open MesFile
Close MesFile
Get start time
Get end time
Get channel count
Get channel info
Get expanded channel info
Get channel Id
Get first value
Get next value
Get actual value
Get last value
Get mean value
Get minimum value
Get maximum value
Get sum
Get integral
Get TRMS
Get value count
Export HDS file
Export ASCII file
Open MesFile
Script
Initiate
Open MesFile
Initiate HDS: Open MesFile(In: File name\Object Out: Handle\Object, Start time\Object, End
time\Object LVResult)
This function opens the given measurement file and gives it a "handle". The file can then be
communicated with via its handle.
1030

May 2011
Arguments:
Name
File name
Handle
Start time
End time
Type
Input value
Output value
Output value
Output value
Description
Measurement file (including path) to be opened
Handle for file
Measurement file start time
Measurement file end time
Return code:
-2: The file could not be opened.
0: Opening measurement data file failed
1: Opening measurement data file
succeeded
Result
Close MesFile
Script
Initiate
Close MesFile
Initiate HDS: Close MesFile(In: Handle\Object Out: LVResult)

This function closes the measurement data file that has the given handle.
Arguments:
Name
Handle
Type
Input value
Description
Handle for file
Return code:
0: Closing measurement data file failed
1: Closing measurement data file
succeeded
Result
Get start time

Script
Initiate

May 2011
Get start time
1031
Initiate HDS: Get start time(In: Handle\Object Out: Start time\Object, LVResult)
This function acquires the start time for the measurement data file that has the given
handle.
Arguments:
Name
Handle
Start time
Type
Input value
Output value
Description
Handle for file
The start time for the measurement data file
that has the given handle
Return code:
0: Function failed
Result
Get end time

Script
Initiate
Get end time
Initiate HDS: Get end time(In: Handle\Object Out: End time\Object, LVResult)
This function acquires the end time for the measurement data file that has the given
handle.
Arguments:
Name
Handle
Start time
Type
Input value
Output value
Description
Handle for file
The end time for the measurement data file
that has the given handle.
Return code:
Result
0: Function failed
1032

May 2011
Get channel count

Script
Initiate
Get channel count
Initiate HDS: Get channel count(In: Handle\Object Out: Number\Object, LVResult)

This function acquires the number of channels for the measurement data file that has the
given handle.
Arguments:
Name
Handle
Number
Type
Input value
Output value
Description
Handle for file
The number of channels for the measurement
data file that has the given handle.
Return code:
0: Function failed
Result
Get channel info

Script
Initiate
Get channel info
Initiate HDS: Get channel info(In: Handle\Object, Index\Object Out: Name\Object, Channel ID
\Object, LVResult)
This function acquires information on a channel from the measurement data file that has
the given handle.
Arguments:
Name
Handle
Index
Type
Input value
Input value
Name
Channel ID
Output value
Output value

May 2011
Description
Handle for file
Channel index for which information is to be
acquired
Name of channel
Channel ID
1033
Return code:
0: Function failed
Result

Script
Initiate
Initiate HDS: Get extended channel info(In: Handle\Object, Channel ID\Object Out: Unit
\Object, Min\Object, Max\Object, Decimal places\Object,Channel type\Object, Comment
\Object, Location\Object, LVResult)
This function acquires information on a channel from the measurement data file that has
the given handle.
Arguments:
Name
Channel ID
Unit
Min
Max
Decimal places
Channel type
Comment
Location
Type
Input value
Output value
Output value
Output value
Output value
Output value
Output value
Output value
Description
Channel ID
Unit
Minimum value
Maximum value
Number of decimal places
Channel type
Comment
Location
Return code:
0: Function failed
Result
Get channel Id
Script
Initiate
Get mean value
1034

May 2011
Initiate HDS: Get channel Id(In: Handle\Object, Name\Object Out: Channel ID\Object,
LVResult)
This function acquiers the channel Id of the channel from the measurement data file that
has the given handle.
Arguments:
Name
Handle
Name
Type
Input value
Input value
Channel ID
Output value
Description
Handle for file
Name of channel for which information is to be
acquired
Channel ID
Return code:
-2: Incorrect Handle
0: Function failed
Result
Get first value

Script
Initiate
Get first value
Initiate HDS: Get first value(In: Handle\Object, Channel ID\Object Out: Time\Object, Value
\Object, State\Object, LVResult)
This function acquires the first value from a channel from the measurement data file that
Arguments:
Name
Channel ID
Time
Value
State
Type
Input value
Output value
Output value
Output value
Description
Channel ID
Measurement value timestamp
Channel value
Value status:
Scaled Value
Forced Value
Invalid
Connection Offline

May 2011
1035
Changed datatyp
Wrong configuration
Defect hardware
Wire Break
Upper range
Lower range
Invalid value
Infinite value
No number
Alarm
No data
The value state can be checked with
the function Check value state.
Return code:
0: Function failed
Result
Get next value

Note: This function is available only in extended mode.
Script
Initiate
Get next value
Initiate HDS: Get next value(In: Handle\Object, Channel ID\Object InOut: Time\Object Out
Value\Object, State\Object, LVResult)
This function acquires the next value from a channel from the measurement data file that
has the given handle. The timestamp for the required value must be greater than the given
time.
Arguments:
Name
Channel ID
Time
Type
Input value
Input / output
value
Description
Channel ID
Input: The timestamp for the acquired value must
be greater than this timestamp
Value
State
Output value
Output value
Output: Timestamp from the acquired value

Channel value
Value status:
Scaled Value
Forced Value
Invalid
1036

May 2011
Connection Offline
Changed datatyp
Wrong configuration
Defect hardware
Wire Break
Upper range
Lower range
Invalid value
Infinite value
No number
Alarm
No data
The value state can be checked with the function
Check value state.
Return code:
0: Function failed
Result
Get actual value

Script
Initiate
Get actual value
Initiate HDS: Get actual value(In: Handle\Object, Channel ID\Object InOut: Time\Object Out
Value\Object, State\Object, LVResult)
This function acquires the current value from a channel from the measurement data file
that has the given handle. The timestamp for the required value must not be greater than
the given time (i.e. the timestamp must be less than or equal to).
Arguments:
Name
Channel ID
Time
Type
Input value
Input / output
value
Value
State
Output value
Output value
Description
Channel ID
Input: The timestamp for the acquired value may
not be greater than this timestamp (i.e. the time
stamp must be less than or equal to).
Output: Timestamp from the acquired value
Channel value
Value status:
Scaled Value

May 2011
1037
Forced Value
Invalid
Connection Offline
Changed datatyp
Wrong configuration
Defect hardware
Wire Break
Upper range
Lower range
Invalid value
Infinite value
No number
Alarm
No data
Check value state.
Return code:
0: Function failed
Result
Get last value

Script
Initiate
Get last value
Initiate HDS: Get last value(In: Handle\Object, Channel ID\Object Out: Time\Object, Value
\Object, State\Object, LVResult)
This function acquires the last value from a channel from the measurement data file that
Arguments:
Name
Channel ID
Time
Value
State
Type
Input value
Output value
Output value
Output value
Description
Channel ID
Measurement value timestamp
Channel value
Value status:
Scaled Value
Forced Value
Invalid
Connection Offline
1038

May 2011
Changed datatyp
Wrong configuration
Defect hardware
Wire Break
Upper range
Lower range
Invalid value
Infinite value
No number
Alarm
No data
Check value state.
Return code:
0: Function failed
Result
Get mean value

Script
Initiate
Get mean value
Initiate HDS: Get mean value(In: Handle\Object, Channel ID\Object, Start time\Object, End
time\Object Out: Value\Object, State\Object, LVResult)
This function acquires the average value for the values between the start and end times of
a channel from the measurement data file that has the given handle.
Arguments:
Name
Channel ID
Start time
Type
Input value
Input value
End time
Input value
Value
State
Output value
Output value
Description
Channel ID
Timestamp of the first measurement value to be
included in the average calculation
Timestamp of the last measurement value to be
included in the average calculation
Calculated average
Value status:
Scaled Value
Forced Value
Invalid

May 2011
1039
Connection Offline
Changed datatyp
Wrong configuration
Defect hardware
Wire Break
Upper range
Lower range
Invalid value
Infinite value
No number
Alarm
No data
Check value state.
Return code:
0: Function failed
Result
Get minimum value

Script
Initiate
Get minimum value
Initiate HDS: Get minimum value(In: Handle\Object, Channel ID\Object, Start time\Object, End
time\Object Out: Value\Object, Time\Object, State\Object, LVResult)
This function acquires the minimum value for the values between the start and end times of
a channel from the measurement data file that has the given handle.
Arguments:
Name
Channel ID
Start time
Type
Input value
Input value
End time
Input value
Value
Time
State
Output value
Output value
Output value
Description
Channel ID
included in the minimum value calculation
included in the minimum value calculation
Calculated minimum value
Timestamp from the acquired value
Value status:
Scaled Value
Forced Value
1040

May 2011
Invalid
Connection Offline
Changed datatyp
Wrong configuration
Defect hardware
Wire Break
Upper range
Lower range
Invalid value
Infinite value
No number
Alarm
No data
Check value state.
Return code:
0: Function failed
Result
Get maximum value

Script
Initiate
Get maximum value
Initiate HDS: Get maximum value(In: Handle\Object, Channel ID\Object, Start time\Object, End
time\Object Out: Value\Object, Time\Object, State\Object, LVResult)
This function acquires the maximum value for the values between the start and end times
of a channel from the measurement data file that has the given handle.
Arguments:
Name
Channel ID
Start time
Type
Input value
Input value
End time
Input value
Value
Time
State
Output value
Output value
Output value

May 2011
Description
Channel ID
included in the maximum value calculation
included in the maximum value calculation
Calculated maximum value
Timestamp from the acquired value
Value status:
1041
Scaled Value
Forced Value
Invalid
Connection Offline
Changed datatyp
Wrong configuration
Defect hardware
Wire Break
Upper range
Lower range
Invalid value
Infinite value
No number
Alarm
No data
Check value state.
Return code:
0: Function failed
Result
Get sum
Script
Initiate
Get sum
Initiate HDS: Get sum(In: Handle\Object, Channel ID\Object, Start time\Object, End time\Object
Out: Value\Object, State\Object, LVResult)
This function acquires the sum value for the values between the start and end times of a
channel from the measurement data file that has the given handle.
Arguments:
Name
Channel ID
Start time
Type
Input value
Input value
End time
Input value
Value
State
Output value
Output value
Description
Channel ID
included in the sum value calculation
included in the sum value calculation
Calculated sum
Value status:
1042

May 2011
Scaled Value
Forced Value
Invalid
Connection Offline
Changed datatyp
Wrong configuration
Defect hardware
Wire Break
Upper range
Lower range
Invalid value
Infinite value
No number
Alarm
No data
Check value state.
Return code:
0: Function failed
Result
Get integral
Script
Initiate
Get integral
Initiate HDS: Get integral(In: Handle\Object, Channel ID\Object, Start time\Object, End time
\Object Out: Value\Object, State\Object, LVResult)
This function acquires the integral for the values between the start and end times of a
channel from the measurement data file that has the given handle.
Arguments:
Name
Channel ID
Start time
Type
Input value
Input value
End time
Input value
Value
State
Output value
Output value

May 2011
Description
Channel ID
included in the integral calculation
Calculated integral
Value status:
1043
Scaled Value
Forced Value
Invalid
Connection Offline
Changed datatyp
Wrong configuration
Defect hardware
Wire Break
Upper range
Lower range
Invalid value
Infinite value
No number
Alarm
No data
Check value state.
Return code:
0: Function failed
Result
Get TRMS
Script
Initiate
Get TRMS
Initiate HDS: Get TRMS(In: Handle\Object, Channel ID\Object, Start time\Object, End time
\Object Out: Value\Object, State\Object, LVResult)
This function acquires the TRMS (true root mean square) for the values between the start
and end times of a channel from the measurement data file that has the given handle.
Arguments:
Name
Channel ID
Start time
Type
Input value
Input value
End time
Input value
Value
Output value
Description
Channel ID
Calculated TRMS
1044

May 2011
State
Output value
Value status:
Scaled Value
Forced Value
Invalid
Connection Offline
Changed datatyp
Wrong configuration
Defect hardware
Wire Break
Upper range
Lower range
Invalid value
Infinite value
No number
Alarm
No data
Check value state.
Return code:
0: Function failed
Result
Get value count

Script
Initiate
Get value count
Initiate HDS: Get value count(In: Handle\Object, Channel ID\Object, Start time\Object, End
time\Object Out: Number of values\Object, LVResult)
This function acquires the number of values between the start and end times of a channel
from the measurement data file that has the given handle.
Arguments:
Name
Type
Description
Channel ID
Start time
Input value
Input value
End time
Input value
Channel ID

May 2011
1045
Value

Calculated integral
Output value
Return code:
- 9 : Server is offline.
- 8 : Unknown channel ID.
-7 : Incorrect start or end time
-6 : No unique data source found
0: Function failed
Result
Export HDS file

Script
Initiate
Export HDS file
Initiate HDS: Export HDS file(In: Handle\Object, Export file name\Object, Channel ID\Object,
Start time\Object, End time\Object, Append\Object Out: LVResult)
This function exports values, from the measurement data file, whose timestamps are
between the given start and end times.
Arguments:
Name
Handle
Export filename
Type
Input value
Input value
Channel ID
Input value
Start time
End time
Append
Input value
Input value
Input value
Description
Handle for file
File name (including path) to which data is to be
exported.
0: All channels of the source file should be exported.
ID: Only the channel with ID should be exported.
Timestamp of the first value to be exported
Timestamp of the last value to be exported
If the destination file exists already:
Yes: add the measurement data to the file
No: overwrite the existing file
Return code:
Result
0: Function failed
1046

May 2011
Export ASCII file

Script
Initiate
Export ASCII file
Initiate HDS: ASCII-Export(In: Handle\Object, Export file name\Object, Start time\Object, End
time\Object Out: LVResult)
This function exports, in ASCII format, values from the measurement data file whose
timestamps are between the given start and end times.
Arguments:
Name
Export filename
Type
Input value
Start time
End time
Input value
Input value
Description
exported.
Return code:
Result
0: Function failed
Function obsolete
Info:
Export HDS file (old)
Initiate HDS: Export HDS file(In: Handle\Object, Export file name\Object, Start time\Object,
End time\Object Out: LVResult)
This function exports values, from the measurement data file, whose timestamps are
between the given start and end times.

May 2011
1047
Arguments:
Name
Export filename
Type
Input value
Start time
End time
Input value
Input value
Description
exported.
Return code:
0: Function failed
Result
2.4.3.9.10 Configuration
The object functions in this section are available for channel configuration only in extended
mode.
Set TM channel Config 1
Set TM AIn Config 1
Set TM AIn Config 2
Set TM AIn Config 3
Set TM ADFT-AIn Config 3
Set common channel config
Set EK AIn config
Add TM Connection to Dataservice
Delete TM Connection from Dataservice

Script
Initiate
Configuration
Initiate Configuration: Set TM channel Config 1(In: Channel ID\Object, Active\Object, Name
\Object, Unit\Object, Comment\Object Out: LVResult)
This function configures aT o pMe ssag e (Lo g Me ssag e ) channel.
1048

May 2011
Arguments:
Name
Channel ID
Active
Name
Unit
Comment
Type
Input
Input
Input
Input
Input
value
value
value
value
value
Description
ID of the channel which is to be configured
Set channel to active (Yes) or inactive (No)
New name of channel
New channel unit
New comment/long text for channel
Return code:
Result
0: Configuration failed
1: Configuration succeeded
Refer also to TopMessage device configuration. If you open the T o pMe ssag e -Co nfig urato r
and double-click a channel, the channel configuration dialogue opens.

May 2011
1049
Set TM AIn Config 1

Script
Initiate
Configuration
Set TM AIn Config 1
Initiate Configuration:Set TM AIn Config 1(In: Channel ID\Object, Sensor type\Object, Mode
\Object, Physical range\Object, Min\Object, Max\Object, Scaled min\Object, Scaled max
\Object, Decimal places\Object, Unit\Object Out: LVResult)
This function configures an analog input of a T o pMe ssag e (Lo g Me ssag e ) device.
1050

May 2011
Arguments:
Name
Channel ID
Sensor type
Type
Input value
Input value
Scaled min
Description
0: Voltage
1: Pt xxx
(RTD)
2: NiCr-NiAl (K)
3: NiCr-CuNi (E)
4: Fe-CuNi (L)
5: Fe-CuNi (J)
6: Pt10Rh-Pt (S)
7: Cu-CuNi (U)
8: Pt13Rh-Pt (R)
9: Cu-CuNi (T)
10: NiCr Si-Ni Si(N)
11: Ni xxx
(RTD)
12: 0..20 mA
13: 4..20 mA
14: Resistance
15: W5Re-W26Re (C)
16: Pt30Rh-Pt6Rh(B)
17: pH
0: unipolar
1: bipolar
Index
Burden
Maximum value of physical range
Minimum measurement range - value not equal to 0 only
for a voltage sensor
Maximum measurement range - value not equal to 0
only for a voltage sensor
Minimum for scaling
Mode
Input value
Physical range
Input value
Min
Input value
Scaled max
Maximum for scaling
Decimal places
Number of portrayed decimal places for real-time data
Unit
0: C
1: K
2: F
3: R
4: R
Max
Return code:
Result
and double-click a channel, the channel configuration dialogue opens. This function's

May 2011
1051
arguments refer to the tab settings and options of this dialogue.
Set TM AIn Config 2

Script
Initiate
Configuration
Set TM AIn Config 2
Initiate Configuration: Set TM AIn Config 2(In: Channel ID\Object, Compensation active
\Object, Set min\Object, Actual min\Object,Set max\Object, Actual max\Object Out:
1052

May 2011
LVResult)
Arguments:
Name
Channel ID
Compensation
active
Set min
Set max
Actual min
Actual max
Type
Input value
Input value
Description
Is sensor compensation active (Yes) or not (No)
Input
Input
Input
Input
Minimum set-point
Minimum set-point
Minimum actual value
Maximum actual value
value
value
value
value
Return code:
Result
arguments refer to the sensor compensation tab settings.

May 2011
1053
Set TM AIn Config 3

Script
Initiate
Configuration
Set TM AIn Config 3
Initiate Config:Set TM AIn Config 3(In: Channel ID\Object, A/D Measuring time\Object,
Tolerance\Object, Tolerance scaled\Object, Wire Break\Object, Range error detection
\Object,Measurement interval\Object, Calibration interval\Object,Reference junction\Object
Out: LVResult)
1054

May 2011
Arguments:
Name
Channel ID
A/D Measuring time
Tolerance
Tolerance scaled
Range error detection
Type
Input
Input
Input
Input
Input
Measurement interval
Calibration interval
Reference junction
Input value
Input value
Input value
value
value
value
value
value
Description
Power supply rejection (in milliseconds)
Tolerance in percent
Tolerance scaled (Yes/No)
Range error detection active (Yes) or inactive
(No)
Value x; measured at x cycles
Value x: Calibrate every 2^x cycles
Reference junction
Return code:
Result
arguments refer to the options tab.

May 2011
1055

Script
Initiate
Configuration
Initiate Config:Setze TM ADFT-AIn Config 3(In: Channel ID\Object, Sample rate\Object,

AAFilter\Object, Wire Break\Object, Range error detection\Object, lover limit\Object,
upper limit\Object, Characteristic\Object Out: LVResult)
1056

May 2011
This function configures an analog input from a T o pMe ssag e (Lo g Me ssag e ) device of
the ADFT type.
Arguments:
Name
Channel ID
Sample rate
AAFilter
Wire Break
Range error detection
lower limit
upper limit
Characteristic
Type
Input
Input
Input
Input
Input
Description
ID of the channel to be configured
Sampling frequency in Hz
Anti-Alias-Filter (Yes/No)
Wire break (Yes/No)
Range error detection enabled (Yes) or disabled
(No)
Input value Lower limit
Input value Upper limit
Input value TRMS (0) or arithmetical average(1)
value
value
value
value
value
Return code:
Result
-2: An incorrect parameter was provided
arguments refer to the options tab.

May 2011
1057

Script
Initiate
Configuration
Initiate Config: Set common channel config(In: Channel ID\Object, Active\Object, Name
\Object, Unit\Object, Comment\Object Out: LVResult)
This function configures a channel's general settings.
1058

May 2011
Arguments:
Name
Channel-ID
Active
Name
Unit
Type
Input
Input
Input
Input
Comment
Input value
value
value
value
value
Description
Channel active (Yes) or inactive (No)
New channel name
New channel unit Input must be blank for an Expert Key
channel with a thermocouple/RTD sensor type.
New comment/long text for the channel
Return code:
-7: An error occurred when writing to the channel configuration.
-6: No comment was found in the channel configuration.
-5: The channel is an Expert Key analog input channel with a
thermocouple/RTD sensor type and was given a unit.
-4: An error occurred when reading the channel configuration.
-3: The channel belongs to a device that does not allow general setting.
The following device types are supported: ProfiMessage, OPC-Client, Expert
Key, software channels, DataSocket and Modbus
-2: No channel was found with the given ID.
Result
Set EK AIn config

Script
Initiate
Configuration
Set EK Ain config
Initiate Config: Set EK AIn config(In: Channel ID\Object, Sensor type\Object, MR-Min\Object,
MR-Max\Object, Shunt resistor\Object, Unit\Object, Min\Object, Max\Object, Scaled min
\Object, Scaled max\Object, Decimal places\Object, Sample rate\Object Out: LVResult)
This function configures the analog input of an <%EK%> device.
Arguments:
Name
Channel-ID
Sensor type

May 2011
Type
Input value
Input value
Description
0: Voltage
1: Current
2: Resistance
3: Thermocouple type B / P730Rh-Pt6Rh
1059
MR-Min
Input value
4: Thermocouple type C / W5Re-W26Re

5: Thermocouple type E / NiCr-CuNi
6: Thermocouple type J / Fe-CuNi
7: Thermocouple type K / NiCr-NiAl
8: Thermocouple type L / Fe-CuNi
9: Thermocouple type N / NiCrSi-NiSi
10: Thermocouple type R / Pt13Rh-Pt
11: Thermocouple type S / Pt10Rh-Pt
12: Thermocouple type T / Cu-CuNi
13: Thermocouple type U/ Cu-CuNi
14: RTD Pt100
15: RTD Pt200
16: RTD Pt500
17: RTD Pt1000
18: RTD Ni100
19: RTD Ni1000
Lower limit of measurement range
Valid values for voltage sensor type (when MR-Min is
not equal to 0, MR-Min and MR-Max must be
symmetrical, e.g. +/-10000)
-10000, -5000, -2000, -1000, -500,- 200, - 100 and 0
Valid values for current sensor type
Any value can be entered that is greater than or equal
to 0; on condition that it is not greater than 10000mv
when multiplied by the load resistance. MR_Min must
also be less than MR_Max. An error will otherwise be
returned.
Only a 0 value is valid for a resistance sensor type
Only a 0 value is valid for a thermocouple sensor
type The actual value is automatically replaced
according to the selected unit.
The following are valid values for RTD sensor types.
MR-Max values are in brackets
Pt100
-260(849)
-436(1560.2)
13.15(1122.15)
Pt200
-260(849)
-436(1560.2)
13.15(1122.15)
-260(408)
-436(766.4)
13.15(681.15)
-260(849)
-436(1560.2)
13.15(1122.15)
-260(266)
-436(510.8)
13.15(539.15)
-436(1560.2)
13.15(1122.15)
-436(766.4)
13.15(681.15)
Pt500
Pt1000 -260(849)
-260(408)
1060

May 2011
MR-Max
Input value
Ni100
-60(249)
-76(480.2)
213.15(522.15)
Ni1000
-60(249)
-76(480.2)
213.15(522.15)
-60(210)
-76(410)
213.15(482.15)
Upper limit of measurement range

Valid values for voltage sensor type (when MR-Min is
not equal to 0, MR-Min and MR-Max must be
symmetrical, e.g. +/-10000)
100, 200, 500, 1000, 2000, 5000 and 10000
Valid values for current sensor type
Any value greater than 0; on condition that it is not
greater than 10000mv when multiplied by the load
resistance. MR_Min must also be less than MR_Max. An
error will otherwise be returned.
Valid values for resistance sensor type
500, 1000, 2500, 5000 and 10000
Only a 0 value is valid for a thermocouple sensor
type The actual value is automatically replaced
according to the selected unit.
The following are valid values for RTD sensor types.
MR-Min values are in brackets
C
RTD
849(-260)
1560.2(-436)
1122.15(13.15)
Pt200
849(-260)
1560.2(-436)
1122.15(13.15)
408(-260)
766.4(-436)
681.15(13.15)
849(-260)
1560.2(-436)
1122.15(13.15)
266(-260)
510.8(-436)
539.15(13.15)
1560.2(-436)
1122.15(13.15)
408(-260)
766.4(-436)
681.15(13.15)
Ni100
249(-60)
480.2(-76)
522.15(213.15)
Ni1000
249(-60)
480.2(-76)
522.15(213.15)
210(-60)
410(-76)
482.15(213.15)
Pt500
Pt1000 849(-260)
Load

May 2011
Input value
For a current sensor type, values are not equal to 0.

Values must be equal to 0 for all other sensor types.
1061
Ensure that 10000mV is not exceeded when multiplying

by the load and measurement range. An error will
otherwise be returned.
Unit
Input value
Min
Input value
Unit. Input for thermocouple and RTDs can be 0( C ), 1

(F) and 2 (K). This value is 0 for all other sensor
types.
Minimum measurement value to be scaled
Any value can be input here for sensor
types:voltage, current and resistance. Max must
be greater than Min.
For thermocouples and RTDs, values are always
equal to 0 because minimum values are automatically
applied.
Max
Input value
Maximum measurement value to be scaled

types:voltage, current and resistance. Max must
be greater than Min.
equal to 0 because maximum values are automatically
applied.
Scaled min
Input value
Minimum, scaled output value

types:voltage, current and resistance. Scaled max
must be greater than Scaled min.
equal to 0 because minimum values are automatically
applied.
Scaled max
Input value
Maximum, scaled output value

types:voltage, current and resistance. Scaled max
must be greater than Scaled min.
equal to 0 because maximum values are automatically
applied.
Decimal places
Input value
Number of decimals places for real time data. Values are

in the 09 range.
1062

May 2011
Sample rate
Input value
Values for sensor types voltage, current and

resistance, are as follows:.
0.2; 0.5; 1; 2; 5; 10; 20; 50; 100; 200; 500; 1000;
2000;
5000 and 10000
The following values are available for the
thermocouple sensor type.
0.2; 0.5; 1; 2; 5; 10; 20; 50; 100;
The following values are available for the RTD sensor
type.
0.2; 0.5; 1; 2; 5; 10
Return code:
Result
-16: Invalid input for Min, Max, Scaled min or Scaled max
-15: Load resistance multiplied by MR-Max exceeds 10000mv.
-14: A value pair has been input whose Scaled max value is not greater than
the Scaled min.
-13: Invalid Unit
-12: Invalid load resistance
-11: Invalid MR-Min and/or MR-Max
-10: Invalid Sampling rate
-9: Invalid Decimal places
-8: Invalid Sensor type
-7: An error occurred when writing to the channel's configuration.
-6: No comment was found in the channel configuration.
-5: The channel is an Expert Key analog input channel with a thermocouple/
resistance-probe sensor type and was given a unit.
-4: An error occurred when reading the channel configuration.
-3: The channel belongs to a device that can not undergo general setting.
-2: No channel found for the given Channel ID or ID is not an analog Expert
Key input.
Add Top Message Connection to Dataservice

Script
Initiate
Configuration
Add Top Message Connection to Dataservice
Initiate Configuration: Add TM Connection to DataService(In: Host\Object, User\Object,

Password\Object Out: LVResult)
This function adds the given T o pMe ssag e (Lo g Me ssag e ) device toDataSe rv ice .

May 2011
1063
Arguments:
Name
Host
Type
Input value
User
Input value
Password
Input value
Description
Name or IP-address of the T o pMe ssag e (Lo g Me ssag e )
device to be added to DataSe rv ice
When the connection is password protected the user name
is entered here (can be spaces)
When the connection is password protected the password is
entered here (can be spaces)
Return code:
0: Function failed
2: Function succeeded but the T o pMe ssag e (Lo g Me ssag e ) device
already exists in DataSe rv ice
Result
Delete Top Message Connection from Dataservice

Script
Initiate
Configuration
Delete Top Message Connection from Dataservice
Initiate Configuration: Delete TM Connection from DataService(In: Host\Object Out:

LVResult)
This function deletes the given T o pMe ssag e (Lo g Me ssag e ) device from the DataSe rv ice .
Arguments:
Name
Host
Type
Input value
Description
Name or IP-address of the T o pMe ssag e (Lo g Me ssag e )
device to be deleted from DataSe rv ice
Return code:
Result
0: Function failed
1064

May 2011
2.4.3.9.11 Directory
The following object functions are available for directories.

Directory exists
Create directory
Show directory dialog
Directory exists
Script
Initiate
Directory
Directory exists
Initiate Directory: Directory exists(In: Directory name\Object Out: LVResult)

This function tests whether the given directory exists.
Arguments:
Name
Directory
name
Type
Input value
Description
Name and path of directory whose existence is to be
checked
Return code:
0: Directory does not exist
1: Directory does exist
Result
Create directory
Script
Initiate
Directory
Create directory
Initiate Directory: Create directory(In: Directory name\Object Out: LVResult)

This function generates a directory.

May 2011
1065
Arguments:
Name
Directory
name
Type
Input value
Description
Name and path of directory to be created
Return code:
0: Directory could not be created
1: Directory was created
Result

Script
Initiate
Directory
Initiate Directory: Show directory dialog(In: Title\Object Out: LVResult)

This function opens the directory dialogue
Arguments:
Name
Title
Type
Input value
Description
Name in directory dialogue
Return code:
Result
The selected directory or empty string when the

dialogue is cancelled

Script
Initiate
File
Show directory dialog with Path
Initiate Directory: Show directory dialog with Path(In: Title\Object, Path\Object Out:
LVResult)
This function opens the directory dialogue
Arguments:
1066

May 2011
Name
Title
Path
Type
Input value
Input value
Description
Name in directory dialogue
The path with which the directory dialogue is to be
opened
Return code:
The selected directory or empty string when the
dialogue is cancelled
Result
2.4.3.9.12 ProfiSignal
The following object functions are available for ProfiSignal.
Clo se Pro fiSig nal

Run external program

Get monitor info
Close ProfiSignal
Script
Initiate
ProfiSignal
Close ProfiSignal
Initiate ProfiSignal: Close ProfiSignal()

This function ends ProfiSignal.

Script
Initiate
ProfiSignal

May 2011
1067
Initiate ProfiSignal: Run external program(In: Program file(.exe)\Object, Call parameter\Object,

Window State\Object,Wait until program exits\Object Out: return code\Object, LVResult)
This function runs the given program file using the given call parameter. The working
directory of the external program is the Pro fiSig nal project directory.
Arguments:
Name
Program file(.exe)
Call parameter
Type
Input value
Input value
Window State
Input value
Wait until program

exits
Input value
Description
External program to be run
Call parameter for the program to be run. Multiple
parameters are separated using a space.
How the DOS window is to be displayed that is
opened when calling the external program (normal,
minimized, maximized or hidden)?
Is the next line of code to be processed when the
external program ends?
Return code:
Return code
Result
When the "Wait until program exits" is set to No then this

code is always 0. When not, the return code corresponds to
the the return code of the external program.
1: Program could be run
0: Program could not be run

Script
Initiate
ProfiSignal
Initiate ProfiSignal: Get default config directory(Out: Directory\Object, LVResult)

This function determines the default directory in which the application's configuration
information is located.
Arguments:
Name
Directory
Type
Output
value
Description
Return code:
1068

May 2011

Result

Script
Initiate
ProfiSignal
Initiate ProfiSignal: Get default measurement directory(Out: Directory\Object, LVResult)

This function determines the default directory in which the measurement data files are
located.
Arguments:
Name
Directory
Type
Output
value
Description
Return code:
Result

Script
Initiate
ProfiSignal
Initiate ProfiSignal: Get default report directory(Out: Directory\Object, LVResult)

This function determines the default directory in which reports are located.
Arguments:
Name
Directory

May 2011
Type
Output
value
Description
1069
Return code:
Result

Script
Initiate
ProfiSignal
Initiate ProfiSignal: Get default parameter directory(Out: Directory\Object LVResult)

This function determines the default directory in which the parameter files are located.
Arguments:
Name
Directory
Type
Output
value
Description
Return code:
Result

Script
Initiate
ProfiSignal
Get proj ect directory
Initiate ProfiSignal: Get project directory(Out: Directory\Object, LVResult)

This function determines the default directory in which the projects are located.
Arguments:
1070

May 2011
Name
Directory
Type
Output
value
Description
Return code:
Result
Get monitor info

Script
Initiate
ProfiSignal
Get monitor info
Initiate ProfiSignal: Get monitor info(In: Monitor index\Object Out: Top\Object, Left\Object,
Height\Object, Width\Object, Primary\Object, LVResult)
This function determines information about the monitor (Monitor Index > 0) or about the
Desktop (entire virtual desktop).
For single monitor systems the desktop settings (Monitor Index = 0) correspond to the main
monitor settings (Monitor Index = 1)
Arguments:
Name
Monitor index
Top
Left
Height
Width
Primary

May 2011
Type
Description
Input /
Input:
output value Monitor number
0:
Desktop
> 0: Monitor number.
Output:
For decktop, the number of monitors are returned.
Output
Returns the location of the monitor's upper border.
value
The value is given in pixels relative to the upper
border of the primary monitor.
Output
Returns the location of the monitor's left border.
value
The value is given in pixels relative to the left
border of the primary monitor.
Output
Returns the monitor's height (in pixels).
value
Output
Returns the monitor's width (in pixels).
value
Output
Yes. The data derives from the primary monitor
value
1071
Return code:
0: Function failed
Result
2.4.3.9.13 Project
The following object functions are available for projects.

Open project file
Close project file
Open login
Logout user
Check user rights
Get actual user name
Authenticate user
Password change
Open project file

Script
Initiate
Proj ect
Open proj ect file
Initiate Project: Open project file(In: File name\Object Out: LVResult)

This function opens the given project file.
Arguments:
Name
File name
Type
Input value
Description
Project (including path) to be opened
Return code:
Result
0: Project could not be opened

1: Project could be opened
1072

May 2011
Close project file

Script
Initiate
Proj ect
Close proj ect file
Initiate Project: Close project file(In: File name\Object)

This function closes the given project.
Arguments:
Name
File name
Type
Input value
Description
Project (including path) to be closed
Open login
Script
Initiate
Proj ect
Open login
Initiate Project: Open login(Out: LVResult)

This function opens the login dialogue
Return code:
-5: The dialogue is write protected
-4: An exception has occurred
0: No user is logged in
1: Login succeeded
2: Password protection is not enabled
3: The dialogue was cancelled
Result
Logout user
Script
Initiate
Proj ect
Logout user
Initiate Project:Logout user(Out: LVResult)

This function logs out logged in users.
Return code:

May 2011
1073
-5: The dialogue is write protected

-4: An exception has occurred
0: No user is registered
1: Logout succeeded
Result
Check user rights

Script
Initiate
Proj ect
Check user rights
Initiate Project: Check user rights(In: User Right\Object Out: LVResult)

This function checks whether the active user has the selected user rights.
Arguments:
Name
User Right
Type
Input value
Description
The user right for which an existence check is to be made.
Return code:
1: The active user has the user right
Result

Script
Initiate
Proj ect
Initiate Project: Get actual user name(Out: Name\Object, LVResult)

This function acquires the user name of the active user.
Arguments:
Name
Name
Type
Return code
Description
Name of active user
Return code:
1074

May 2011
1: Name could be acquired
Result
Authenticate user
Script
Initiate
Proj ect
Authenticate user
Initiate Project: Authenticate user( In: User Right\Object Out: User Name\Object Out:
LVResult)
This function opens a dialogue that requires user authentication to perform a specific task.
The user must have the required user rights. Authentication depends on the active user!
Arguments:
Name
User Right
User Name
Type
Input value
Return code
Description
User right required for authentication
Name of active user
Return code:
Result
-1: The authentication dialogue was cancelled

1: The authenticated user user has the user right
Authenticated user (obsolete)

This instruction can no longer be selected and exists only for reasons of backwards
Initiate Project: Authenticate user( In: User Right\Object Out: LVResult)

This function opens a dialogue that requires user authentication to perform a specific task.
The user must have the required user rights. Authentication depends on the active user!
Arguments:
Name
User Right
Type
Input value

May 2011
Description
User right required for authentication
1075
Return code:
0: No user authentication
1: The authenticated user user has the user right
Result
Password change
Script
Initiate
Proj ect
Password change
Initiate Project: Password change(Out: LVResult)

This function opens a dialogue enabling the logged in user to change his/her password. The
dialogue opens only when a user is logged in.
Return code:
-5: Password could not be changed (write protected )
-1: Der Dialog wurde abgebrochen
-1: The dialogue was cancelled
1: The dialogue was successfully closed
Result
2.4.3.9.14 Calculation channels
The following object functions are available for calculation channels (refer to Formulator /
calculation channels).
Start
Stop
Start
Script
Initiate
Start
Initiate Calculation Channels: Start(In: Cycle\Object)
1076

May 2011
This function starts the calculation for calculation channels.
Arguments:
Name
Cycle
Type
Input value
Description
The frequency at which the calculations are to be
performed ( in milliseconds ).
Stop
Script
Initiate
Stop
Initiate Calculation Channels: Stop()

This function stops the calculation for calculation channels.
2.4.3.10 Configuration
As well as assigning values under Assign, there are also assign options when configuring
object properties. This section describes these options. For read and write configurations
there are object functions that set or read out a value rather than notify success
(operation call successful or not successful). These object functions are also described.
Configurations can be added or amended only in edit mode.
Read
Read object functions
Write
Write object functions
Read
Script
Configuration
Read

This instruction enables the reading out of configuration properties of Visu-Objects,
Parameter-Objects or Report-Objects. Further information about these properties can be
found in the help information on the specific objects. To read out or amend the value of an
object, use the Assign Value command.

May 2011
1077
Read object functions

(operation call successful or not successful).
These include the following object functions and are assigned under Configuration/Read.
Get column count
Get row count
Get row for title
Column name
Field as string
Field as integer
Field as boolean
Field as double
Get column count

In the following,VisuView name, Table name and YX table name are placeholders for an
actual VisuView,table or YX table.
Selecting Script
Configuration
Read generates the following instruction core:

Open the context menu for Object and select
VisuView [Visuview name]
name]
Get column count to generate the following line of script:
Table
[table
Config Read: Object = Visualisation\VisuView_1\Tab.Table_1.Get column count

[YX table name]
Get column count to generate the following line of script:
YX-Table
Config Read: Object = Visualisation\VisuView_1\YX-Tab.Table_1.Get column count

This function determines the number of columns for a table/YX-table.

1078

May 2011
Selecting Script
Configuration

name]
Get column for title to generate the following line of script:
Table
[table
Config Read: Object = Visualisation\VisuView_1\Tab.Table_1.Get column for title(In: Title

\Object)
[YX table name]
Get column for title to generate the following line of script:
YX-Table
Config Read: Object = Visualisation\VisuView_1\YX-Tab.Table_1.Get column for title(In: Title

\Object)
This function returns the number of the table/YX-table column that has the given title.
Arguments:
Title
Title to be searched for
Return code:
Object
The column that has the given title. If no column is found, a value of 2
is returned
Get row count

Selecting Script
Configuration

name]
Get row count to generate the following line of script:
Table
[table
Config Read: Object = Visualisation\VisuView_1\Tab.Table_1.Get row count

May 2011
1079

[YX table name]
Get row count to generate the following line of script:
YX-Table
Config Read: Object = Visualisation\VisuView_1\YX-Tab.Table_1.Get row count

This function determines the number of rows for a table/YX-table.
Get row for title

Selecting Script
Configuration

name]
Get row for title to generate the following line of script:
Table
[table
Config Read: Object = Visualisation\VisuView_1\Tab.Table_1.Get row f or title(In: Title

\Object)
[YX table name]
Get row for title to generate the following line of script:
YX-Table
Config Read: Object = Visualisation\VisuView_1\YX-Tab.Table_1.Get row f or title(In: Title

\Object)
This function returns the number of the table/YX-table row that has the given title.
Arguments:
Title
Title to be searched for
Return code:
Object
The row that has the given title. If no row is found, a value of 2 is
returned
1080

May 2011
Column name
In the following,VisuView name, Table name and ODBC table name and ODBC SQL name
are placeholders for an actual VisuView,table or ODBCSQL Visu-Object.
Selecting Script
Configuration

ODBC-Table
[ODBC table name]
Column name count to generate the following line of script:
Config Read: Object = Visualisation\VisuView_1\ODBC table.ODBC table_1.column name

(In: column number\Object)

ODBC SQL
[ODBC SQL name]
Column name count to generate the following line of script:
Config Read: Object = Visualisation\VisuView_1\ODBC SQL.ODBC SQL_1.column name

(In: column number\Object)
This function returns a column name for the given column number.
Arguments:
Column number
Number of the column whose name is to be determined
Return code:
Var
Column name for the given number. A 0 is returned when no column

exists for the given number
Field as string

May 2011
1081
are placeholders for an actual VisuView,ODBC table or ODBC SQL Visu-Object.
Selecting Script
Configuration

[ODBC table name]
Field as string to generate the following line of script:
ODBC-Table
Config Read: Object = Visualisation\VisuView_1\ODBC table.ODBC table_1.f ield as string

(In: column name\Object)

[ODBC SQL name]
Field as string to generate the following line of script:
ODBC SQL
Config Read: Object = Visualisation\VisuView_1\ODBC table.ODBC table_1.f ield as string

This function returns the column value as a string for the given column name of the
currently observed row of an OBDC table or SQL query.
Arguments:
Column number Column number whose value is to returned as a string
Return code:
Object
The value for the given column is returned as a string. A 0 is returned

when there is no column with the given name or when an error occurs
when converting to a string
Field as integer
1082

May 2011
Selecting Script
Configuration

[ODBC table name]
Field as integer to generate the following line of script:
ODBC-Table
Config Read: Object = Visualisation\VisuView_1\ODBC table.ODBC table_1.f ield as integer


[ODBC SQL name]
Field as integer
VisuView
[Visuview name]
ODBC SQL
to generate the following line of script:
Config Read: Object = Visualisation\VisuView_1\ODBC table.ODBC table_1.f ield as integer

This function returns the column value as an integer for the given column name of the
currently observed row of an OBDC table or SQL query.
Arguments:
Column number Column number whose value is to returned as an integer
Return code:
Object
The value for the given column is returned as an integer. A 0 is returned

when converting to an integer

May 2011
1083
Field as boolean
Selecting Script
Configuration

[ODBC table name]
Field as boolean to generate the following line of script:
ODBC-Table
Config Read: Object = Visualisation\VisuView_1\ODBC table.ODBC table_1.f ield as boolean


[ODBC SQL name]
Field as boolean
VisuView
[Visuview name]
ODBC SQL
to generate the following line of script:
Config Read: Object = Visualisation\VisuView_1\ODBC table.ODBC table_1.f ield as boolean

This function returns the column value as a boolean value (true or false) for the given
column name of the currently observed row of an OBDC table or SQL query.
Arguments:
Column number Column number whose value is to returned as a boolean value (true or
false)
Return code:
Object
The value for the given column is returned as a boolean value. A 0 is
1084

May 2011
returned when there is no column with the given name or when an error
occurs when converting to a boolean value (true or false)
Field as double
Selecting Script
Configuration

[ODBC table name]
Field as double to generate the following line of script:
ODBC-Table
Config Read: Object = Visualisation\VisuView_1\ODBC table.ODBC table_1.f ield as double


[ODBC SQL name]
Field as double to generate the following line of script:
ODBC SQL
Config Read: Object = Visualisation\VisuView_1\ODBC table.ODBC table_1.f ield as double

This function returns the column value a double for the given column name of the currently
observed row of an OBDC table or SQL query.
Arguments:
Column number Column number whose value is to returned as a double
Return code:
Object
The value for the given column is returned as a double. A 0 is returned

when converting to a doubler

May 2011
1085
Write
Selecting Script
Configuration
Write generates the following instruction core:

This instruction enables the setting of configuration properties for Visu-Objects, ParameterObjects or Report-Objects. Further information about these properties can be found in the
help information on the specific objects. To read out or amend the value of an object, use
the Assign Value command.
Write object functions

There are object functions that only assign a value. These include the following object
functions and are assigned under Configuration/Write.
Set name of column
Set color of column
Set unit of column
Set name of column

In the following, VisuView name and YX-table name are placeholders for actual Visuviews
or YX tables.
Selecting Script
Configuration
Open the context menu for the left Object and select
YXTable
[YX table name]
Set name of column to generate the following line of script:
Config Write: Visualisation\VisuView_1\YX-Tab.YX-Table_1.Set name of column(In: column

number\ Object) = Object
The YX-table will be used only for the YX-diagram (table) and configures this diagram. This
function sets the name for the channel corresponding to the column number.
1086

May 2011
Arguments:
Column number
Number of the column (a channel in the YX diagram) to be given a

name

or YX tables.
Selecting Script
Configuration
YXTable
[YX table name]
Set name of column to generate the following line of script:
Config Write: Visualisation\VisuView_1\YX-Tab.YX-Table_1.Set Y-axis of column(In: column

The YX-table will be used only for the YX-diagram (table) and configures this diagram. A
column in the YX table corresponds to a channel in the YX diagram. This function sets the
Y-axis for the channel corresponding to the column number.
Arguments:
Column number
Number of the column (a channel in the YX diagram) to be given a Yaxis
Set color of column

or YX tables.
Selecting Script
Configuration

May 2011
1087
YXTable
[YX table name]
Set colour of column to generate the following line of script:
Config Write: Visualisation\VisuView_1\YX-Tab.YX-Table_1.Set colour of column(In: column

display color for the channel corresponding to the column number.
Arguments:
Column number Number of the column (a channel in the YX diagram) to be given a colour
Set unit of column

or YX tables.
Selecting Script
Configuration
Table
[YX table name]
Set unit of column to generate the following line of script:
YX-
Config Write: Visualisation\VisuView_1\YX-Tab.YX-Table_1.Set unit of column(In: column

display unit for the channel corresponding to the column number.
Arguments:
Column
number
Number of the column (a channel in the YX diagram) to be given a unit
1088

May 2011

or YX tables.
Selecting Script
Configuration
YXTable
[YX table name]
Set visibility of column to generate the following line of script:
Config Write: Visualisation\VisuView_1\YX-Tab.YX-Table_1.Set visibility of column(In:

column number\ Object) = Object
column in the YX table corresponds to a channel in the YX diagram. This function is for the
visibility settings of the channel corresponding to the column number.
Arguments:
Column number Number of the column (a channel in the YX diagram) to be given visibility
2.4.3.11 Shortcut lists
This section lists the shortcuts that are available within a script.
Shortcut
Action
F1
Opens the Delphin online help. When pressed within a dialog or selected
line of script, the corresponding help window opens.
CTRL+D+click
on an object
Clicking a numeric opens the color selection dialog.

Clicking a path opens the file selection dialog.

May 2011
1089
Clicking a fixed value opens a dialog to enable input of a fixed value.

CTRL+click on Opens the date dialog
a date
CTRL+click on Opens a dialog to enable input of a fixed value.
a fixed value
CTRL+click on Opens a menu containing entries corresponding to the object type and an object
for visualisation, parameter and report objects - to the same grouping.
CTRL+A+click
on an object
Opens a menu (when possible) that enables the entry of new variables
(simple, lists, tables,3D-tables).
CTRL+move
line
Copies the line to the new location in script.
1090

May 2011
2.4.4
Analysis
ProfiSignal provides a range of tools for measurement data analysis.
File
Open Mesfile...
This dialog enables users to display and analyse their saved measurement data files. A
range of diagrams are available. An ASCII export can also be performed for selected files.
File
Readout device storage...
Readout device storage reads the data memories from Me ssag e devices. Users can access
the full contents of the memory, display the data directly in an analysis window, or perform
an ASCII export.
File
Display database in trend...
The Display database in trend enables a DataSe rv ice database to be displayed in an

analysis window. The dialog can be used for any database registered in the DataSe rv ice .
File
Open Global Alerting...
Global alerting facilitates the visualisation of alarms. No application needs to be created.

May 2011
1091
File
New Online Analyse...
File
Open Online Analyse...
Online analyse enables users to perform the basic portrayal and recording of current
measurement data. No application needs to be created.
Settings
Global Settings
The time-stamp in an analysis is displayed according to the settings in Global Settings. In

ProfiSignal select either Local, Source or UTC from the timezone tab under Settings/
Global Settings.
2.4.4.1 Online analysis

Online analyse enables users to perform the basic portrayal and recording of current
measurement data. An application is not required. The features of an online analysis
include:
Choice of diagram type

Choice of channels from all available devices within the network
Recorder ready for immediate use
Diagram and recorder configuration saved in default.xml
The selected online analysis opens automatically when ProfiSignal starts
File
New Online Analyse / Open Online Analyse
A new online analysis is opened via either the

analysis).
symbol or File (refer to adding an online
The
symbol or File opens a dialog showing the existing online analysis configurations.
Users can open an existing online analysis.
Further details on configuring/operating an online analysis window are available under online
analysis window.
1092

May 2011
2.4.4.1.1 Adding an online analysis
Opens a dialog to select a diagram type.
Once a diagram type has been selected, a dialog opens to select channels:

May 2011
1093
All device channels are now accessible that are available within the network. The devices
must be enabled in the DataSe rv ice . The channel selection dialog lists all the devices that
are enabled in the DataService.
To add channels to an online analysis, select the channels on the left and either drag&drop
them onto the right or click Add. Select multiple channels by clicking channels while
pressing CNTRL+SHIFT.
The maximum number of channels that can be processed under your Pro fiSig nal licence is
displayed at the bottom of the dialog. Only active channels are included in the channel
limit. The channel limit message also indicates the number of active channels currently
assigned to the online analysis.
1094

May 2011
Once the limit has been reached, the maximum number is displayed in red.
No further channels can then be assigned to the online analysis via drag&drop or Add.
End the dialog with OK. This opens the online analysis window. The channels are then
displayed with their current data. Users can start recording without having to perform any
additional configurations.
The online analysis window is explained in the online analysis window section.
2.4.4.1.2 Opening an online analysis
Pro fiSig nal has three ways to configure an online analysis. The
dialog showing the existing online analysis configurations.
symbol or File opens a
The table lists all the available online analysis configurations. The Autostart column lists
the configurations that automatically start when ProfiSignal runs.
Select a configuration and click Open to access the configuration. Delete deletes the
configuration from the list (and also from Default.xml).

May 2011
1095
A configuration can also be opened by double-clicking an entry.
2.4.4.1.3 Online analysis window
1 This area of the window includes the title bar and the main menu.
The title is made up of the text Online Analyse - ... and the name of the online analysis
("Online Analyse_1" in the example).
Configuration of the online analysis, as well as trend and recorder configuration, is
performed via online analysis main menu.
The diagram and channel table is displayed in this area. Setting up a diagram explains
this area.
3 This area includes the online analysis recorder. The recorder can be used immediately.
1096

May 2011
The channels that are recorded are those listed in the channel table.
The status bar in this area displays the timezone used for displaying times.
2.4.4.1.3.1 Online analysis main menu

Online Analyse
The online analysis's main menu has the following items:
Save
Saves the current online analysis's settings. When auto save is enabled, the current
settings overwrite the existing settings when closing the online analysis.
Rename
Changes the online analysis name.
Settings
The online analysis's Settings has the following items:
Channel choice
Opens a channel selection dialog. To add and delete channels. This item is disabled when a
recorder is running.

May 2011
1097
Trend
Opens the diagram settings dialog.
Recorder
Opens the recorder settings dialog. This item is disabled when a recorder is running.
Auto save
Saves the current configuration when closing the online analysis.
Auto start
This option selects the online analysis that automatically opens when ProfiSignal starts.
Window
The online analysis's Window has the following items:
Minimize Windows
Minimizes the display of all analysis windows including measurement data files.
Maximize Windows
Maximizes the display of all analysis windows including measurement data files.
Cascade windows
Displays all analysis windows and measurement data files as overlapping.
Auto align windows

Automatically aligns all analysis windows and measurement data files.
1098

May 2011
2.4.4.1.3.2 Diagram settings dialog
Diagram settings can be made for the online analysis. The available settings depend on the
type of diagram selected.
The settings dialog is accessed via the

Settings
symbol or
Trend
Settings Trend tab


May 2011
1099
of the grid.
Grid
Opens a colour palette to select the raster colour.
Chart background
Opens a colour palette to select the background colour for the trend chart curves.
Trend background
Opens a colour palette to select the background colour for the trend chart axes.
Label
Opens a colour palette to select the trend chart's display colour.
Scale
Opens a colour palette to select the colour for the scale lines.
Background components
Opens a colour palette to select colours for the toolbar, status bar and toolbox areas.
(Refer to trend colour settings).
Mesfile time range

saved time scale.
Show selected

Marker section
Print Layout tab
1100

May 2011

Use individual EMF layout
When enabled, users can use the EMF layout settings button to open the EMF-export
settings dialog. An individual setting can be input. This setting will be saved as the start
setting and used for subsequent output.
2.4.4.1.3.3 Recorder, online analysis
Recorder: a recording has not been started
Recorder: recorder started, single step save option
Start /stop recording

Manual stop / start of a recorder can be permitted or blocked. If a manual start/stop is
permitted, the following buttons are enabled:

May 2011
1101
Start recording
Starts the recording. A file name is updated (depending on the settings) and a
measurement data file created and opened.
Stop recording
The recording is stopped and the measurement data file closed.
Pause recording
Pauses the recording. The measurement data file's channels are given a interrupted status
but the files remain open.
Single step measurement
If a recording has been started, this button adds a data record (one measurement value
per channel) to the measurement data file. This button appears only when the option single
step via trigger source is enabled.

This button opens the dialog open measurement data file for analysis using the recorder's
directory/folder. A measurement data file can also be open during a recording. The data
recorded is the data that has been displayed up to the opening of the measurement data
file. An update does not take place.
Table with information on the data file

File name
File name of the measurement data file currently recording or previously recorded.
State
Recording status
Comment
Initialisation
Recorder has been started. A measurement data file has

been created and opened but no recording has taken place.
Recording ongoing
The recording is taking place.
Recording paused
The recording has been paused.
Recording being stopped
The recording is being stopped and the measurement data

file closed.
Recording stopped

file has been closed by the recorder.
Time
How long the recording has been running.
1102

May 2011
Data
The amount of recorded data.
Recorder settings tab

File
New Online Analyse / Open Online Analyse
Settings
Recorder
The File name tab

Sets the name of the file for the measurement data.

May 2011
1103
The file name and the location of saved data files (*.hds) are set here.
The file location is determined by the path entered in the Directory text field. The default
path is a sub-directory of the project folder which has the same name as the recorder. To
change the file location firstly uncheck Default directory. A new directory can be selected
by using Search and the Open file dialogue.
If the path is invalid, ProfiSignal will automatically save the data in the folder
...ProfiSignal/Project/[Name of project]/[name of application].
The file name is made up of the entry in the File name text field and/or an automatic
naming procedure plus the .hds file ending.
The automatic naming procedure follows the options selected under data file name.
1104

May 2011
If the options are selected as above the file name would appear as follows:
Messdatei_2011-07-18_001
with the date and consecutive numbering being automatically set.
The following are examples of the file names when selecting different
options:
Filename (placeholder)
Messdatei.hds
File name + consecutive numbering
Messdatei_1.hds
Messdatei_2.hds
Messdatei_3.hds
File name + date + time
Messdatei_24-09-2005_18-18-52.hds
Messdatei_24-09-2005_18-19-32.hds
Messdatei_24-09-2005_18-20-23.hds
file name + Date + consecutive number
Placeholders are also available which provide the user with further possibilities in creating
personalised file names. To use placeholders, select File name only (overwrites data) and
combine text and placeholders in the text field File name. The actual file name will be
displayed under Preview.

May 2011
1105
Trigger tab
Recording takes place by the user manually operating a recorder object's controls or by
automated triggering. The Trigger tab sets the parameters for automatic triggering to take
place.
1106

May 2011
Manual start and stop only

script instruction.
Allow manual start and stop
Recording can be performed by operating a recorder object's controls as well as
automated triggered recording.
Automated triggering
Activates the trigger settings under Start and Stop when the application is in runtime
mode.
Start section
Time
Recording will begin at the entered start time.

May 2011
1107
Start once
Recording starts at the set start time.
Start daily
Recording records every 24 hours from the set start time.
Start repeatedly
The recording restarts if it is stopped at a point in time that follows the start time. This
will continue until the recording is ended by the user operating a recorder object's
controls or by a script instruction.
(Note: measurement data occurring between end and restart times will not be saved. This
interruption in saving measurement data lasts just a few seconds.)
Info:
The Start daily and Start repeatedly options are useful in combination time-dependent
stop. A new file will then be opened at the end of the set measurement duration.
Triggered
1108

May 2011
Level trigger High

Recording will start with each rising edge detected within the trigger channel and end
with each trailing edge. The Stop section then becomes active.
Level trigger Low
Recording will start with each trailing edge detected within the trigger channel and
end with each rising edge. The Stop section then becomes active.
Rising edge trigger
Recording will start with a rising edge detected within the trigger channel. Stop
Recording will start with a trailing edge detected within the trigger channel. Stop
Trigger channel
Trigger value:
Manual
script instruction.

May 2011
1109
Stop section
Time related
Sets the duration of the recording.
Measurement period
Sets the duration of the recording in hours, minutes and seconds.
Triggered
1110

May 2011
Rising edge trigger

Recording will start with a rising edge detected within the trigger channel .
Recording will start with a trailing edge detected within the trigger channel .
Trigger channel
Trigger value:
Save options tab
Sets specific properties for the recorder object. Changes are not usually required here.

May 2011
1111
Saving options section

Optimizes the amount of measurement data to be saved.
1112

May 2011
All values
This is the default setting. All measurement data will be saved.
Tolerance in %
A measurement value will be saved only if it differs from the previous saved value by
the percentage given here. The 100% value for a channel corresponds to the scaling
setting in the TopMessage Configurator.
Pretrigger
When checkboxed, additional data for the specified time is recorded prior to the start
of the recording.
Time synchronization
When checkboxed, a dialog will open on clicking Trigger configuration: This dialog
enables settings for amending time synchronization.
Equidistant Storage
A measurement value will be saved after each number of seconds entered here.
Single step via trigger source

Checkboxing this option enables the following button.
When a trigger channel is selected, a measurement value will be saved for each
positive edge of the selected channel.
When no trigger channel is selected, manual saving of one measurement value per

May 2011
1113
channel can be initiated via the

trigger channel is selected.
button. This button can also be used when a
Trend optimization section

Sets the speed of the graph portrayal when the recording is to be displayed within a
trend chart.
Set to slow for slow sample rates and very long time periods.
Set to quick for short sample rates and short time periods.
2.4.4.1.4 Available diagram types
The following diagrams are available for online analysis:
Yt-diagram
Logic diagram
YX-diagram
YX-diagram color
Orbit diagram
FFT diagram
1114

May 2011
2.4.4.2 Opening measurement data file for analysis
Open this tool by clicking

in the main menu. This enables recorded measurement data
files to be viewed/analysed.
The window lists the available ProfiSignal measurement data files (hds files). If Show File
information is enabled and a data file is selected, information on the measurement data file
is displayed in the preview window.
Once a measurement data file has been selected (double-clicking or clicking OK), a
selection dialog opens to select the diagram type that is to display the measurement data.
This dialog also enables users to start an ASCII export.
The following data types can be opened in addition to ProfiSignal measurement data files:
DataSe rv ice database (*.hdd) - a DataSe rv ice database can be opened only when it is
no longer registered within the DataSe rv ice . In other cases, use the display database in
trend dialog.
ProfiSignal Trend configuration (*.tcg) - if a configuration file is generated from an open
measurement data file and/or DataSe rv ice database, the configuration file has the same
path as the measurement file/database. If the configuration file selected from the dialog
has a valid path, the measurement data file/database with the configuration is opened.
MHouse measurement data file (*.mes) - the selected MHouse file is converted to a
ProfiSignal file (*.hds) before being opened. The converted file is retained and is not
automatically deleted when the analysis window is closed.

May 2011
1115
Info:
If a ProfiSignal file with the same name already exists (in the same directory), this file
will be opened without conversion.
2.4.4.2.1 Measurement data preview
If Show file information is enabled and a data file is selected, the following information is
displayed.
Information on the measurement data file (Preview)

The preview displays the name of the measurement data file and the time (start and end
times) that data has been recorded from the channels. The timezone is also given for the
time-stamp. The timezone is taken from the timezone information of all the channels in the
measurement data file. The number of channels in the measurement data file is also given.
Warnings and comments
The preview window also displays comments/errors:
1116

May 2011
Comment: channels have different timezones!

The measurement data file contains channels with differing timezones. The local (PC)
timezone is used for the time-stamp.
Medana file (Basic package) cannot be opened!
This message can appear when a Medana file ending (*.mes) has been manually changed
to a Pro fiSig nal file ending.
Unknown data type!
This message can appear when a file has been manually changed to have a Pro fiSig nal
file ending.
Measurement data file cannot be opened!
If an error occurs when opening a measurement data file, users can check and repair the
file using the DataBaseCheck tool.
Measurement file has no channels!
The selected measurement data file contains no channels. Check the measurement data
file.
Open failed because opened as a database!
The selected DataSe rv ice database is still assigned in the DataSe rv ice . Either: delete
the database in the DataSe rv ice configuration (refer to theDataSe rv ice Co nfig urato r
database view); or open the database with the display database in trend dialog.
Comment: relative measurement data file!
The file is a relative file that has been created with the file factory.
Information on the channels in a measurement data file

This area displays all the channels contained within a measurement data file. Also displayed
are the channel's comments and units from the DataService Configurator.
2.4.4.2.2 Diagram type selection
The following dialog appears once a measurement data file has been selected. This dialog
enables users to select a diagram type that is to display the selected measurement data
file. An ASCII export can also be performed.

May 2011
1117
The different diagram types can display only certain channels. The following message
appears when a diagram has been selected that is incapable of displaying the channels
belonging to the selected measurement data file:
Refer to the manual to find out which diagram is capable of displaying which channel type.
If ASCII export is selected, another dialog opens.
1118

May 2011
Cancel closes the diagram type dialog and returns to the measurement file dialog.
2.4.4.2.3 Analysis window
1 This area of the contains the window's title bar.

The title is made up of the text "Analyse -" and the name of the measurement data file
(e.g. "2009-05-29_001.hds").
The diagram and channel table is displayed in this area. Setting up a diagram explains
this area.
3 The status bar in this area displays the timezone used for displaying times.
The following diagrams are available for measurement data file analysis:

May 2011
1119
Yt-diagram
Logic diagram
YX-diagram (measurement device)
YX-diagram color
Orbit diagram
FFT diagram
2.4.4.2.4 Available diagram types
The following diagrams are available for analysing measurement data files:
Yt-diagram
Logic diagram
YX-diagram
YX-diagram color
Orbit diagram
FFT diagram
2.4.4.3 Graphical diagrams

The following diagrams are available for online analysis:
Yt-diagram
Logic diagram
YX-diagram
YX-diagram color
Orbit diagram
1120

May 2011
FFT diagram
2.4.4.3.1 Diagram layout
This section describes the layout and operation that are common to all diagram types.
Layout and operations that are specific to a diagram are explained in the section for that
diagram type.
The diagram is structured according to five areas. These areas can be hidden:
Toolbar - The toolbar can be used to hide/show different areas of the diagram.
The graph area portrays the measurement data channels. The trend chart displays
measurement curves and measurement axes.
Display settings are mainly made using the graph toolbox. Operating the graph area
with the mouse takes place according to settings made in the graph toolbox. These
are explained in the Graph toolbox functions section.
The graph area is explained further in the sections for each diagram type.
Channel table - The channel table lists the measurement channels assigned to the
trend chart. For example, settings can be made here on what measurement curve is
to be displayed, or on how portrayal of the measurement curve is to proceed.
Graph toolbox - Gives access to a range of analysis functions.
Status bar - Displays information on the diagram, e.g. the current mouse position.
The status bar is described for each diagram type.

May 2011
1121
2.4.4.3.1.1 Taskbar functions

toolbox.
2.4.4.3.1.2 General functions for the channel table
The channel table lists the measurement channels assigned to a diagram. If a diagram has
more than one Y-axis, every Y-axis is included with its name. The measurement channels
are listed under the Y-axes to which they are assigned.
within the TopMessage Configurator.
Name
Value
1122

May 2011
Unit
State
Tolerance
Comment
Channel type
Channel ID
Module type
Time
Timezone
Data type
Device name
The values in the colour and show columns can be amended with the channel table.
The Colour column determines the colour of the measurement curve within the graphical
section. The colour can be changed by double clicking the colour field. This will display a
colour palette from which the curve colour can be selected.
Unchecking the Show hides the curve in the graphical section.
channel filter button hides the channels in the channel table which are also hidden in the
diagram.

May 2011
1123
measurement curve within the diagram (curve and y-axis with bolder display).
Mark a channel or axis by left clicking. Clicking an already selected channel or axis then
deselects it. Deselection can also be made by clicking on an empty area within the channel
table.
Graph / channel table split

The graph and table are separated by a thin blue line. The line can be moved by positioning
the mouse cursor on it. Left-click the line to move it to the required position.

The channel table's context menu depends on whether the entry selected is a
measurement channel, a Y axis , a point specific to a diagram (e.g. digital for logic
diagrams) or a column header. Context menus for a measurement channel/ diagram-specific
point is explained for the diagram type.
Y-axis context menu
Add y-axis
Remove y-axis
Y-axes settings
1124

May 2011
Sorting
To sort the channel table. The channel ID is the default sorting parameter. The sort
mode is set to Automatic. In Custom sort, mode, users can use the mouse
(drag&drop) to set the channel order (refer to sorting the channel table).
Columns
To select the columns to be displayed in the channel table. Left-clicking a menu
option adds (by checking) or removes (by unchecking) the column to/from the table.
Channel filter
This corresonds to the channel filter button.
Add y-axis
Adds a y-axis. The number of Y-axes is limited to four. This option is available only for
diagrams that support multiple y-axes.
Y-axes settings
Opens the Y-axis settings dialog. This dialog is used to configure Y-axes. This option
is available only when one Y-axis has been set up and therefore has no entry in the
channel table.
Changing column size/position in a table's header section

The positioning and width of the columns can be altered except for the columns color and
visibility (V..).
Column position
A column can be moved using the mouse (drag&drop). The new position is indicated
with a green-colored pointer.

May 2011
1125
Column width
Click on the separating lines between columns to alter a column width.
This dialog enables the following settings to be made:

Changes to the y-axis scale caption.
Short ticks adds detail to the scale (additional markings/ticks). The background scale
changes correspondingly.
Scale color opens a color palette to select the color of the scale.
Position enables users to change the position of the y-axis. A new y-axis is always
'Left'-positioned (aligned).
Ticks determines the minimum number of scale markings/ticks.
Width determines the y-axis width. Input is in pixels.
Range low and Range high sets the scale's range.
Current sets the scale for an optimal portrayal of the measurement curve currently
displayed.
Autoscale enables automatic scaling of all y-axes in online portrayals. This button is
available only for trend objects in standard configuration mode. The setting here applies
to all y-axes.
OK and Cancel closes the window. OK saves any changes made.
1126

May 2011
Info:
The Y-axis settings window can be opened either by double-clicking a y-axis in the
graph area or via a context menu.
Example:

May 2011
1127
1128

May 2011
This dialog enables the following settings to be made:

Changes to the x-axis scale caption.
Short ticks adds detail to the scale (additional markings/ticks). The background scale
changes correspondingly.
Range low and Range high sets the scale's range.
Current sets the scale for an optimal portrayal of the measurement curve currently
displayed.
Autoscale enables automatic scaling of all x-axes in online portrayals. This button is
available only for trend objects in standard configuration mode.
Info:
The x-axis settings window can be opened either by double-clicking a x-axis in the graph
area or via a context menu.

May 2011
1129
The channel ID is the default sorting parameter. The sort mode is set to Automatic.
Automatic sorting
Sorting takes place according to selected columns. A column is selected by clicking its
header. For example, sorting according to Value alters the channel table with each new
measurement data.
For multiple Y-axes, sorting takes place for each Y-axis.
With the first click, sorting takes place in ascending (A-Z) order. A subsequent click
switches to a descending order. A small triangle appears in the column header to show the
order of sorting:
1130

May 2011
Custom sort
Sorting ends following automatic sorting of one column. No further sorting takes place when
clicking a column header. The Custom sort is set via the context menu.
Channel table sorting in this mode can take place with the mouse. Any channel can be repositioned using the mouse (drag&drop). Left-click, hold and move the required channel.
The cursor symbol changes and indicates whether the channel may be dropped at the
current mouse position.
If the channel is moved to a Y-axis, it will be positioned at the end of the Y-axis channels.
If the channel is moved to another channel, it will be positioned before this channel.

May 2011
1131
Info:
If channels (rows in the table) are moved with the mouse, the mode will be switched to
"custom sort".
2.4.4.3.1.3 General functions for the graph area
Graph area layout for a YX-diagram
1132

May 2011
Data area
Context menu

May 2011
1133
Show timerange
Export
trends.
Configuration
The configuration option in the context menu enables: setting of the time zone; saving
trend configurations; loading trend configurations. The configuration that is saved differs
according to the type of diagram.
The menu contains the following items.
Online time range ...

Opens a dialog to configurate the online time range.
1134

May 2011
Timezone (display)
To set the timezone that is to appear in the time-stamp.
If channels from multiple devices are being saved to the measurement data file and these
devices have differing timezone settings, these timezones are then also available for
selection:
Load configuration
Loads a trend configuration from a TrendConfig file (*.tcg).
Save configuration
Saves the current trend chart configuration to a *.tcg file.

Saves the current trend chart configuration to the current measurement data file.
Y-axes
Yt, logic and YX diagrams can portray up to 4 y-axes. Y-axes are added via the channel
table. Y-axes can be positioned to the left or right of the data area. Refer here to y-axis
settings dialog. Refer also to the explanations for each diagram type.
Context menu
The y-axes context menu also has an item to configure the y-axis.
Y-axis settings

May 2011
1135
X-axis
A diagram can portray one x-axis.
Context menu
The x-axis context menu also has an item to configure the x-axis.
X-axis settings
Opens the X-axis settings dialog.
2.4.4.3.1.4 Graph toolbox functions
Toolbox functions differ for different types of diagram. This section explains only those
functions that are common to all or the majority of graph/diagram types. For clarity, the
functions are sorted in function blocks according to settings.
1.Navigation in the toolbox
To navigate within the graph toolbox. The symbols are displayed only when
the diagram is too narrow to allow the display of all symbols.
2.Navigating/moving the graph area

This symbol moves the current section of the graph area to the left.
1136

May 2011
This symbol moves the current section of the graph area to the right.
3.Trend graph zoom functions

(automatic scaling). FFT-diagrams display the complete range of frequencies
(on the x-axis) and/or the complete range of amplitudes (on the y-axis).
4.Selecting mouse mode in graph area

May 2011
1137
Provides the mouse with a cropping function (expands a variable section). Creates
a "moused" rectangle of the section to be expanded by left clicking and releasing
the mouse.
The cropping function can also be enabled/disabled by double-clicking in the data
area.
The mouse moves along the scale within the graph area. Left click the trend
chart, and drag&drop at the required position.

action is performed on all y-axes.
. For multiple y-axes, the
multiple y-axes, a single axis can be moved.
Provides the mouse with a zoom function (to enable zooming in and out). Zoom in
by left clicking and moving the mouse upwards and/or to the right and releasing.
Zoom out by left clicking and moving left / downwards.

the action is performed on all y-axes.
. For multiple y-axes,
multiple y-axes, a single axis can be stretched/compressed. Switching between
pan and zoom is possible by double clicking.
The pause key enables users to switch between online and offline data. Clicking
the pause key switches to analysis mode (offline). If the pause key remains
unclicked, online data is displayed. The pause key is unavailable for analysis
diagrams.
5.Undo function
Undoes the last zoom operation (performed via either the graphic toolbox or
mouse). More than one operation can be undone, i.e. pressing undo twice will
undo the last 2 operations, pressing undo 3 times will undo the last 3 operations
etc...
To redo an undone operation.
To undo all saved operations.
1138

May 2011
6.Analysis functions
Markers, text fields, and cursors are important tools in the analysis of measurement
curves.
Enables Assigning text to a marker. Available only for Yt-diagrams.
To hide/show current markers
Opens the marker T text field overview with marker and text field tabs.
Enables add a text field .
To hide/show current text fields
To hide/show current alarm events. Available only when alarms are displayed
(refer to Fault diagnostics und Acquisition of fault data)
To select a priority for displaying a marker. Only those markers are displayed
that have a priority equal to or greater than the set priority.
Update graph
Forces the measurement curves to be redrawn (necessary only when the graph
has errors).

Opens the analyse measurement file dialog.
Print
Opens the Print diagram dialog to print the currently displayed graph.

May 2011
1139
Configure diagram
Configurations can be saved to a TrendConfig (*.tcg) file and later reloaded. The trend
chart configuration only is saved to this file and not the measurement data. The
configuration that is saved differs according to the type of diagram.
To load a *.tcg file.
To save the current trend chart configuration to a *.tcg file.
To save the current trend chart configuration to a *.tcg file. If an HDS file is
being used, the configuration is saved to this file. If a database is being used, the
configuration is saved in ProfiSignal and is available in the dialog showing a
database in a trend dialog.
Resets the trend object to its default values. The section on standard
configuration describes the default view. Available only for trend objects .
1140

May 2011
2.4.4.3.1.5 Channel settings dialog
Settings
Displays the channel settings. These settings can not be changed. Further channel
information is available in the Channel Info tab.
Diagram settings
Color

May 2011
1141
Determines the color of the measurement curve within the graph area. The color can be
changed by double clicking the color field. This will display a color palette from which the
curve color can be selected.
Line style
Sets the line style for connector lines. The line style types are described under the
individual diagram types.
Line width
The default line width is 1 (connector line between the measurement points). A channel
can be highlighted via its line width.
If Highlight selected channel is enabled in the settings dialog, the line width for the
selected channel is increased by 1.
Symbol
The symbol used for each measurement point.
Filter functions for measurement data

Each channel has a filter function to limit the data to be displayed.
Set the value range that the data must have to be displayed. Lower (minimum active) and
upper (maximum active) values can be set. The value range is preset (scale min/scale max
in the channel table) when minimum active and maximum active are enabled;
Filter activation
Filters are enabled/disabled using the buttons in the graph toolbox. Click the following
button:
Channel information
1142

May 2011
Lists information about the channel.
When a relative measurement data file is used in the analysis, the channel information also
includes information on the measurement data source and channel ID:
References
The References tab lists the objects used by the channel.
2.4.4.3.1.6 Diagram settings dialog
Diagram settings can be made for the online analysis. The available settings depend on the
type of diagram selected.
The settings dialog is accessed via the

May 2011
symbol
1143
Image: Settings dialog for a Yt-diagram (analysis and online analysis)
The Settings Trend and Print layout tabs are identical to virtually all diagram types and are
described in this section. Diagram-specific tabs are described under each separate diagram
type.
The following include functions that may not be available for all diagram types.
Settings Trend tab

of the grid.
Grid
Opens a colour palette to select the raster colour.
1144

May 2011
Chart background
Opens a colour palette to select the background colour for the trend chart curves.
Trend background
Opens a colour palette to select the background colour for the trend chart axes.
Label
Opens a colour palette to select the trend chart's display colour.
Scale
Opens a colour palette to select the colour for the scale lines.
Background components
Opens a colour palette to select colours for the toolbar, status bar and toolbox areas.
(Refer to trend colour settings).
Mesfile time range

saved time scale.
Show selected

Marker section
Print Layout tab

May 2011
1145

Use individual EMF layout
When enabled, users can use the EMF layout settings button to open the EMF-export
settings dialog. An individual setting can be input. This setting will be saved as the start
setting and used for subsequent output.
2.4.4.3.2 Yt-diagram
A Yt-diagram portrays measurement data over a time period. A Yt-diagram can

simultaneously display multiple channels. Up to 4 y-axes can be portrayed and positioned to
the left and right of the diagram area.
1146

May 2011
Tool bar
The taskbar provides hide/show functions for the various elements within a diagram. The
diagram name is also displayed.

Activates the open-file dialog.
Channel table

The graph area portrays measurement data channels. Measurement curves and axes are
displayed. Display settings are mainly made using the graph toolbox. Operating the graph
area with the mouse takes place according to settings made in the graph toolbox. Further
details are available in the graph toolbox.
Graph toolbox
The graph toolbox provides a range of functions for graphical analysis.
Status bar
The mouse position (portrayed as a cross) in the graph area returns the values for time
and Y. In this example, the X-axis is time and the Y-axis the amount of degrees. By using
the mouse, users can therefore obtain an exact reading for a specific point in the graph
area.
For multiple Y-axes, the status bar reading is always for the selected Y-axis. The status
bar gives the Y-axis description (in this example: Y2 [C]).

May 2011
1147
The data source is always the currently open measurement data file.
Yt-diagram analysis functions

Marker, text field and cursor provides the Yt-diagram with important aids for analysing
measurement curves.
With Markers, you can set time markers at any point required. Text can then be assigned
to each time marker. Markers can be saved so that they can be used again a later
evaluation of the measurement files.
Mouse cursor limits, evaluates and documents the time ranges for measurement curves.
2.4.4.3.2.1 Channel table functions

The channel table lists the measurement channels assigned to a diagram. The section on
general functions in the channel table describes their settings and operation.
This section explains only those settings and functions specific to Yt-diagram channel
table.

The channel table's context menu depends on whether the entry selected is a
measurement channel, a Y axis , a feature specific to a diagram (e.g. x-axis for yxdiagrams) or a column header.
Measurement channel context menu
linear / steps
Changes the type of portrayal for the measurement curve.
1148

May 2011
Steps is the default setting. Measurement points are joined in steps.

Channel settings
Opens the channel settings dialog. This dialog enables changes to be made to the channel's
portrayal.
Move to y-axis
To assign the channel to an existing y-axis. A new y-axis can be set up using the submenu entry add new y-axis.
2.4.4.3.2.2 Functions for the graph area
Graph area layout for a Yt-diagram

May 2011
1149
Data area
Context menu
Show timerange
1150

May 2011
Export
trends.
Configuration
Move mouse cursor

Mouse cursor settings

May 2011
1151
(checked).
Statistics
This option appears only when the Cursor is being displayed. A statistic table is opened
with a table of additional information such as the channels' minimums and maximums
between the cursors on the time scale. The statistics are generated for all displayed
channels.
If markers or text labels or being shown, the context menu includes:
Edit marker / text label

changed.
Text label...
Marker...
1152

May 2011
To select what information is to be displayed (checked) or hidden (unchecked) for all

markers. The channel information option applies to all channels that are assigned a marker
and includes the channel name and unit options. This means that when channel information
is hidden, then the channel name and unit is also hidden.

overview.
Zoom functions
Mouse cursor with
disabled
zoom function

zoom function
Y-axes

May 2011
1153
A Yt-diagram can portray up to 4 y-axes. Y-axes are added via the channel table. Y-axes
Context menu
The following context menu can be opened in the y-axes area:
Y-axis settings
Show timerange
Export
trends.
Configuration
Zoom functions
If the zoom function is enabled in the graph area, the mouse cursor at the y-axes changes
as follows:
1154

May 2011
Pan - Left-clicking and moving the mouse pans along the y-axis.
Zoom - Left-clicking and moving the mouse stretches/contracts the y-axis.
Info:
Switching between pan and zoom is possible by double clicking.
Time axis
Context menu
The following context menu can be opened in the time axis area:
Configure time axis

Opens the time axis configuration dialog to set the display settings for the time axis.
Show timerange

May 2011
1155
Export
trends.
Configuration
2.4.4.3.2.3 Graph toolbox
The graphics toolbox offers a multitude of tools for working with diagrams. This section
explains only the functions that apply specifically to diagrams. The remaining functions are
described in the general functions of the graphics toolbox.
Display options

slow channels.
1156

May 2011

Hide/show the trend's magnifier function (only available when one measurement file is
being portrayed).
The graphical section of a trend is then split in two:
The upper part portrays an overview of all the measurement values and can not be
altered.
The lower part can be altered using the graph toolbox. The section being displayed in
the lower part can be identified in the upper part by 2 vertical lines.
Relative axes

May 2011
1157
being portrayed or when the trend is connected only to one recorder). Recording begins at a
zero value.
The graph area moves to the beginning of the measurement data file.
The graph area moves to the end of the measurement data file.
Displays the entire measurement data file's time scale.
Automatically scales the y-axes to the measurement curves being displayed.
Select zoom/mouse mode for the graph area

Enables the mouse mode (zoom functions in data section). These are
described in functions of the graphics toolbox.
The channel table displays the channel values corresponding to the

mouse position in the zoomed area.
Double-clicking the data area enables it to be zoomed.
1158

May 2011
Example: channel's current value at the cross-hairs
Analysis functions

Display marker
Enable cursor
Text field
Other functions
Undo function
Update graph
Configure diagram

May 2011
1159
2.4.4.3.2.4 Configure time axis
This dialog enables the following time axis settings to be made:

Scale caption can be entered for the time axis.
Online time range can be changed.
2.4.4.3.2.5 Mouse cursor lines
Left-click the
symbol to activate the mouse cursor. This displays 2 cursor lines within the graph
area showing time and measurement values for the measurement curves being portrayed.
The move mouse cursor is enabled and the cursor changes its appearance
1160

May 2011
Cursor 1 displays the channel name, value and unit, and Cursor 2 displays the value and
(in brackets) the time and value differences between the cursor positions. Displaying the
channel name, unit and difference is optional and can be set in the graph area context
menu.
Move mouse cursor

The cursor lines can be moved by left-clicking the mouse for as long as move mouse
cursor is enabled. The cursor line nearest the mouse position is moved.
The zoom/mouse mode can be changed using the buttons in the graph toolbox to enable
zooming while the cursor lines are being displayed. The data area's context menu can be
used to enable move mouse cursor.
If zooming results in the cursor lines disappearing, they can be re-displayed by doubleclicking the data area.
Channel information using the mouse

If a channel has been selected (clicked) in the channel table, only this channel's values
will be displayed. The exact position of the measuring points will be shown as black
squares. These squares will also move with the movement of the cursor lines using the
mouse.

May 2011
1161
De-selecting a channel (by clicking the selected channel in the channel table), redisplays all measurement data.
Export using cursors
Info:
The time range within the cursor lines can be exported (measurement data file and ASCII
export). The user is then prompted only to enter an output file; a time range is not
required.
Statistics
If the mouse cursors are being shown, the data area context menu can be used to display
the statistical evaluation table.
2.4.4.3.2.6 Settings dialog
The Trend settings tab for a diagram's general settings and the print layout tab are
explained in trend settings.
1162

May 2011
2.4.4.3.3 Logic diagram
The logic diagram is a Yt-diagram for analog signals (upper diagram) combined with a logic
section (lower diagram) for evaluating the edges of digital signals.
Channel table

Display settings are mainly made using the graph toolbox. Operating the graph area with
the mouse takes place according to settings made in the graph toolbox.
Graph toolbox

May 2011
1163
Status bar

This section explains only those settings and functions specific to the logic diagram
channel table.

The channel table's context menu differs according to whether the selected entry is an
measurement channel in the analog area , a measurement channel in the digital area, a Yaxis or a column header. The context menu for analog and digital areas are the same as
the column header menu.
Context menu for channels in the analog area
1164

May 2011
linear / steps
Channel settings
Refer to the Yt diagram description
Change y-axis
To assign the channel to an existing y-axis. A new y-axis can be set up using the submenu entry 'Set new y-axis'. The channel can also be moved to the digital area.
Context menu for channels in the digital area
Change y-axis
To assign the channel to an existing y-axis in the analog area. The 'set new y-axis' menu
item adds a new y-axis to which the digital channel can be assigned.

Channels in the digital area can be sorted in the same way as channels in the analog area.
Refer here to sorting a channel table.

May 2011
1165
2.4.4.3.3.2 Graph area
Graph area layout
Analog data area

The analog data area corresponds to the Yt-diagram data area and is not further explained
here.
Digital data area
1166

May 2011
Lists all digital channels. The channels are sorted according to the sorting in the channel
table.
Visible channels are displayed in an equal way. The y-axis area is used to display the name
of the digital channel. If analog channels are to be displayed in the digital area, the analog
values are interpreted as follows:
Value > 0
-->
True (On)
Value > 0
-->
False (Off)
Split between analog and digital areas

The size of the digital and analog areas can be changed using the mouse. The mouse
cursor changes its appearance when positioned between the two areas:
Left-click and move to the required size.
Hide analog area

The magnifier function for the Yt-diagram is not available for logic diagrams. The magnifier
button is therefore replaced with a hide/show button for the data area.

May 2011
1167
2.4.4.3.4 Oscilloscope diagram
The oscilloscope diagram enables the display of medium to high-speed and one-off, i.e.
transient, processes.
The oscilloscope portrayal is a snapshot of a longer curve portrayal. The oscilloscope
portrayal requires triggering. The oscilloscope portrayal remains until re-triggered and
sufficient measurement data is available.

This section explains only those settings and functions specific to the oscilloscope diagram
channel table.
1168

May 2011

The channel table's context menu differs according to whether the selected entry is an
analog measurement channel, a digital measurement channel, a Y-axis or a column header.
The context menu for analog and digital channels are the same as the column header
menu.
Context menu for channels in the analog area
linear / steps
Channel settings
Refer to the Yt diagram description

May 2011
1169
Change y-axis
To assign the channel to an existing y-axis. A new y-axis can be set up using the submenu entry 'Set new y-axis'. The channel can also be moved to the digital area.
Context menu for channels in the digital area
Change y-axis
To assign the channel to an existing y-axis in the analog area. The 'set new y-axis' menu
item adds a new y-axis to which the digital channel can be assigned.

Channels in the digital area can be sorted in the same way as channels in the analog area.
Refer here to sorting a channel table.
Enter the text here.
Display options
1170

May 2011

slow channels.
Shows/hides the analog and logic areas. The symbol shows the curve type that is
displayed after clicking:
Analog and logic areas are displayed.
Only the analog area is displayed.
Only the logic area is displayed.
Relative axes
being portrayed or when the trend is connected only to one recorder). Recording begins at a
zero value.

May 2011
1171
The graph area moves to the beginning of the measurement data file.
The graph area moves to the end of the measurement data file.
Automatically scales the y-axes to the measurement curves being displayed.
2.4.4.3.4.4 Extended graph toolbox
The extended graph toolbox facilitates oscilloscope mode operation.
Time range
Pretrigger
Trigger source
1172

May 2011
Analog channel

value.
Digital channel

and/or ExpertVib
Edge
Positive edge
Negative edge
Threshold value
Standard
This button is available only for the oscilloscope diagram. In runtime mode.
2.4.4.3.4.5 Configure time axis
This dialog enables the following time axis settings to be made:

Scale caption can be entered for the time axis.

May 2011
1173
Online time range can be changed.
Oscilloscope mode tab

Time range
Pretrigger
Trigger source
Analog channel

value.
1174

May 2011
Digital channel

and/or ExpertVib
Edge
Positive edge
Negative edge
Threshold value
2.4.4.3.5 YX-diagram (hardware)
The YX-diagram portrays characteristic curves. YX-diagrams can portray multiple

characteristic curves and up to four y-axes. The characteristic curves can be positioned to
the left or right of the diagram area.

May 2011
1175
Tool bar

toolbox.

1176

May 2011

toolbox.
Graph toolbox
graphical analysis.
Status bar
The status bar shows information about the trend chart, such as the current mouse
position.
2.4.4.3.5.1 Characteristic curve table, channel table
The channel table in a YX-diagram also has a characteristic curve table.

May 2011
1177

The characteristic curve table lists the characteristic curves set up in a diagram. The
characteristic curves are displayed in the graph area.
Channel table
Split between characteristic curve table and channel table

Characteristic curve tables and channel tables are separated by a narrow blue line. The line
can be moved by positioning the mouse cursor on it. Left-click and move to the required
sizes.
The characteristic curve table lists the characteristic curves set up in a diagram. If a
diagram has more than one Y-axis, every Y-axis is included with its name. The
characteristic curves are listed under the Y-axes to which they are assigned.
1178

May 2011
The Color and Show columns can be amended.

The Color column determines the color of the measurement curve within the graphical
section. The color can be changed by double clicking the color field. This will display a color
palette from which the curve color can be selected.
Unchecking Show hides the curve in the graphical section.
channel filterbutton hides the channels in the channel table which are also hidden in the
diagram.

May 2011
1179
characteristic curve within the graph area (curve and y-axis with bolder display).
Mark a characteristic curve or axis by left clicking. Clicking an already selected
characteristic curve or axis deselects it. Deselection can also be made by clicking on an
empty area within the characteristic curve table.
Context menu for characteristic curve tables

Context menus for characteristic curves differ depending on whether the selected entry is
a characteristic curve, a y-axis, or a column heading.
Context menu for a characteristic curve
1180

May 2011
Characteristic curve settings

Opens the characteristic curve settings dialog. This dialog enables changes to be made to
the channel's portrayal.
Add characteristic
To add new characteristic curves. Refer also to adding characteristic curves.
Delete characteristic
To assign the characteristic curve to an existing y-axis. A new y-axis can be set up using
the sub-menu entry Set new y-axis. Deleting a characteristic curve requires confirmation.
Change y-axis
To assign the characteristic curve to an existing y-axis. A new y-axis can be set up using
the sub-menu entry Set new y-axis.
Y-axis context menu
Add y-axis
Delete y-axis
Set y-axes
X-axes settings

May 2011
1181
Opens the X-axis settings dialog. This dialog is used to configure the X-axis.
Add characteristic
To add new characteristic curves. Refer also to adding characteristic curves.
Sorting
To sort the characteristic curve table. The characteristic curve ID is the default sorting
parameter. The sort mode is set to Automatic. In Custom sort, mode, users can use the
mouse (drag&drop) to set the curve order (refer to sorting the channel table).
Columns
To select the columns to be displayed in the characteristic curve table. Left-clicking a
menu option adds (by checking) or removes (by unchecking) the column to/from the table.
Channel filter
This corresponds to the channel filter button.
Add y-axis
Set y-axes
Opens the Y-axis settings dialog. This dialog is used to configure Y-axes. This option is
available only when one Y-axis has been set up and therefore has no entry in the
characteristic curve table.
X-axes settings
1182

May 2011
Opens the X-axis settings dialog. This dialog is used to configure the X-axis.

visibility (V..). (Refer to channel table)
This section explains only those settings and functions specific to YX-diagram channel
table.
within theT o pMe ssag e Co nfig urato r.
Name
Value
Unit
State
Tolerance
Comment
Channel type
Channel ID
Module type

May 2011
1183
Time
Timezone

Channel table context menus differ depending on whether the selected entry is a
measurement channel or a column heading.
Channel settings
Opens the channel settings dialog.
Add characteristic
To add new characteristic curves. Refer also to adding characteristic curves. The selected
channel is set to the Y-channel.
Sorting
To sort the channel table. The channel ID is the default sorting parameter. The sort mode
is set to Automatic. In Custom sort, mode, users can use the mouse (drag&drop) to set
the channel order (refer to sorting the channel table).
Columns
To select the columns to be displayed in the channel table. Left-clicking a menu option
adds (by checking) or removes (by unchecking) the column to/from the table. Columns to
be shown appear as checked.
1184

May 2011

visibility (V..).
(Refer to channel table)
Context menu for characteristic curve tables
The Add characteristic item in the context menu for characteristic curve tables, adds a
new characteristic curve.
It opens a characteristic curve settings dialog. This dialog configures a characteristic
curve.
The Add characteristic item in the context menu for channel tables, adds a new
characteristic curve.
It opens a characteristic curve settings dialog. This dialog configures a characteristic
curve. The selected channel is set to the Y-channel.
Drag&drop a channel from the channel table

May 2011
1185
A new characteristic curve can be added using drag&drop. Select a channel from the
channel table and drag&drop it in the characteristic curve table.
This opens a characteristic curve settings dialog. The selected channel is then used as the
Y-channel.
1186

May 2011
General
Displays the curve's general settings. These settings can also be changed later.
Characteristic
X:
Channel settings for X values. The dropdown box lists all channels in the diagram's channel
table.
Y:

May 2011
1187
Channel settings for Y values. The dropdown box lists all channels in the diagram's channel
table.
Diagram settings
Color
Determines the color of the measurement curve within the graph area. The color can be
changed by double clicking the color field. This will display a color palette from which the
curve color can be selected.
Line style
Sets the line style for connector lines. The line style types are described under the
individual diagram types.
Line width
The default line width is 1 (connector line between the measurement points). A channel
can be highlighted via its line width.
If Highlight selected channel is enabled in the settings dialog, the line width for the
selected channel is increased by 1.
Symbol
The symbol used for each measurement point.
1188

May 2011
Data area
Context menu

May 2011
1189
Export
trends.
Configuration
If markers or text labels or being shown, the context menu includes::

changed.
Enables text fields and markers to be changed.
Text label...

overview.
1190

May 2011
Y-axes
A YX-diagram can portray up to 4 y-axes. Y-axes are added via the channel table. Y-axes
Refer also to the explanations for each diagram type.
Context menu
Y-axis settings
X-axis
A YX-diagram (hardware) can portray one x-axis.
Context menu
X-axis settings
Display options

May 2011
1191
Hides/shows measurement curves.
Hides/shows measurement points.
Clear drawing area
Logarithmic axes
Logarithmic scaling of the x-axis
Logarithmic scaling of the y-axis
These buttons select either 'normal' (default) or 'logarithmic scalings for the amplitude or
frequency axes.
The remaining functions are described in the general functions of the graphics toolbox.
1192

May 2011
YX diagram
Users can select between linear and logarithmic axes.
Linear axes
Show coordinate plane
Isometric axes

May 2011
1193
Logarithmic axes
Logarithmic X axis
Logarithmic Y axis
Data
Original data
Compressed data
Special compression
2.4.4.3.6 YX-diagram (color)
The YX-diagram (color) functions are identical to the YX-diagram (hardware). The following
therefore concern only the specific aspects for the YX-diagram (color).
1194

May 2011
2.4.4.3.7 FFT diagram
Tool bar

toolbox.

May 2011
1195
Channel table

The graph area portrays the measurement data channels. The display is primarily set using
the graph toolbox and the extended graph toolbox.
Operating the graph area with the mouse takes place according to settings made in the
graph toolbox. These are explained in the 'graph toolbox' functions section.
Graph toolbox
graphical analysis.
Status bar
The status bar provides information on the current mouse position. When a channel has been selected
from the channel table, information is also available on the channel's current data.

This section explains only those settings and functions specific to the FFT diagram channel
table.

Channel table context menus differ depending on whether the selected entry is a
measurement channel or a column heading.
1196

May 2011
Channel settings
Opens the channel settings dialog. This dialog enables changes to be made to the channel's
portrayal.
Note:
Only y-axes are available in the FFT diagram.

May 2011
1197
Data area
Context menu
Show timerange
1198

May 2011
Export
trends.
Configuration

Move mouse cursor
(checked).

May 2011
1199
If markers or text labels or being shown, the context menu includes::

changed.
Text label...

overview.
Zoom functions
Mouse cursor with
disabled
zoom function

zoom function
1200

May 2011
Y-axis
An FFT diagram can portray one y-axis. The y-axis can be positioned to the left or right of
the data area. Refer here to y-axis settings dialog.
Context menu
The following context menu opens in the y-axis area:
Y-axis settings
Export
trends.
Configuration
X-axis
An FFT diagram can portray one x-axis.
Context menu

May 2011
1201
The following context menu opens in the x-axis area:
X-axis settings
Export
trends.
Configuration
FFT spectrum / FFT cascade

This button enables switching between FFT-spectrum and FFT-cascade portrayals. The
button indicates the current portrayal mode.
FFT-cascade portrayal - An FFT-spectrum is displayed for a selected time range
(total cascade time). The time range is set in the extended FFT toolbox.
FFT-spectrum portrayal - Only one spectrum per channel is displayed.
1202

May 2011
FFT with line spectrum / envelope curve

This button enables switching between line-spectrum and envelope curve portrayals.
The button indicates the current portrayal mode.
Envelope curve portrayal - The frequency spectrum is displayed as an envelope
curve.
Line-spectrum portrayal - The frequency spectrum is displayed as vertical lines.
This is the normal mode of portrayal.
Normalised portrayal
The frequency spectrum is normalised to 100.
Logarithmic axes
Logarithmic scaling of the frequency axis (x-axis)
Logarithmic scaling of the amplitude axis (y-axis)
This button switches between 'normal' (default) or 'logarithmic' scaling of the amplitude or
frequency axis.
When at least one logarithmic axis is selected, no order analysis can take place.
Navigating data
To switch to the next/previous frequency spectrum. The status bar
(below) indicates the corresponding trigger times. The buttons become
disabled when the oldest/newest data has been reached.
To switch to the next/previous cascade.
Analysis functions
Evaluation cursor

May 2011
1203
Shows four cursor lines to evaluate characteristic frequencies.

Cursor mode options.
Four modes are available:

Mode
Cursor position
Single, hand
All cursor lines are positioned using the mouse
Harm., hand
The first cursor line can be positioned using the mouse.

The other three cursor lines are positioned according to
first cursor line and following harmonic rulings.
Harm., amplitude
The first cursor line is positioned according to the highest

amplitude. The other three cursor lines are positioned
according to the first cursor line and following harmonic
rulings
Harm., speed
The first cursor line is positioned according to the

measured speed of rotation. The other three cursor lines
are positioned according to the first cursor line and
following harmonic rulings.
Other functions
Undo function
Update graph
Configure diagram
A frequency spectrum is automatically displayed as an order analysis when "order analysis"

is enabled in the AMDT I/O module.
The spectrum is normalized to the measured rotation speeds - usually vibration
measurement on rotating machinery. The order analysis evaluates harmonic vibrating
components.
1204

May 2011
"Order analysis" is enabled within the device. The information exists within the
measurement data.
Refer also to configuring the AMDT I/O module - settings for FFT spectrum.

May 2011
1205
The extended graph toolbox enables users to make settings for the spectrums to be
displayed. Users can set the time range to be displayed. In cascade mode, this effects the
number of spectrums that can be displayed simultaneously. In the portrayal of FFT
spectrums, users can select a specific spectrum via time input.
1206

May 2011
Extended graph toolbox for online analysis
Extended graph toolbox for measurement data file analysis (for cascade portrayal)
Extended graph toolbox for measurement data file analysis (spectrum portrayal)
Total time for cascade diagram
To select the required range for the time axis. In cascade mode, this effects the number of
spectrums that can be displayed simultaneously. The default settings correspond to the
FFT diagram settings dialog.
Navigating a measurement data file

The MultiSlider navigation tool enables users to change the spectrum or time range being
displayed.
FFT spectrum portrayal
For FFT spectrum portrayals, only one slider exists for time point selection. The diagram
displays the FFT spectrum for the selected time point. Move the slider to the required time
point by left clicking and dragging.

May 2011
1207
FFT cascade portrayal

Activate the FFT cascade mode via the graph toolbox. This automatically displays on the
slider the time range for the current cascade.
Move the slider to set the required time range for the cascade.
1208

May 2011
Info:
The MultiSlider navigation tool can be used to set the cascade time range. The individual
spectrums can then clicked using the navigation buttons in the graph toolbox.
2.4.4.3.7.5 Status bar
Amplitude / Frequency
The current amplitude and frequency values for the cursor position on the graph area.
Trigger time / Speed frequency

When a channel is selected in the channel table, the time-stamp (trigger time) is shown for
the spectrum being displayed.

May 2011
1209
Frequency speeds (in rotating machinery) can also be shown via the AMDT I/O module.
Refer also to the "AMDT I/O module".
Status
When a channel is selected in the channel table, the status (trigger time) is shown for the
spectrum being displayed.
Graphic-puffer, occupied
Depending on the computer set-up, only a limited number of data points (typically 100 000
to 250 000) can be comfortably processed within the graphic. If this limit is exceeded, a
100% graphic-puffer occupied will be displayed under the graphic. Therefore, select only
'short' time intervals.
Logarithmic axes
Amplitude minimal value
Frequency minimal value
Total time for cascade diagram

Select here the required range for the time axis. In cascade mode, this effects the number
of spectrums that can be displayed simultaneously.
1210

May 2011
2.4.4.3.8 Orbit diagram
The orbit diagram is a YX-diagram for two time signals. The diagram is intended for the
applications non-contact distance measurement and/or shaft vibration measurement on
turbines/compressors.
The kinetic shaft orbit (shaft center line of movement) is portrayed. Required is a rounded
shaft surface, homogeneous materials and 90 order sensors.
Tool bar
The tool bar provides hide/show functions for the various display elements within a
diagram. The diagram name is also displayed.

May 2011
1211
Hides/shows the extended graph toolbox.

Hides/shows the diagram's status bar.

The characteristic curve table lists all configured characteristic curves.
Channel table

The graph area portrays measurement data channels. Display settings are mainly made
using the graph toolbox and the extended graph toolbox.
Mouse operations in the graph area take place according to settings in the graph toolbox.
Further details are available in the graph toolbox.
Graph toolbox
graphical analysis.
Status bar
Status information - Amplitude / Phase
Displays the amplitude and phase information for the mouse position in the graph area.
Status information - Maximal amplitude

Displays amplitude and phase information for the largest amplitude. The information is also
displayed as a line in the graph area.
2.4.4.3.8.1 Characteristic curve table, channel table
The channel table in an Orbit-diagram also has a characteristic curve table. Refer here to
YX-diagram (hardware)
1212

May 2011

The characteristic curve table lists the characteristic curves set up in a diagram. The
characteristic curves are displayed in the graph area.
Channel table
Split between characteristic curve table and channel table

Characteristic curve tables and channel tables are separated by a narrow blue line. The line
can be moved by positioning the mouse cursor on it. Left-click and move to the required
sizes.

May 2011
1213
Data area
Context menu
Export
1214

May 2011
trends.
Configuration
If markers or text labels are being shown, the context menu includes::

changed.
Text label...

overview.
Y-axes
An orbit diagram can portray one y-axis. The y-axis can be positioned to the left or right of
the data area. Refer here to y-axis settings dialog.

May 2011
1215
Context menu
Y-axis settings
X-axis
An orbit diagram can portray one x-axis.
Context menu
X-axis settings
Display options
Clear drawing area
1216

May 2011
A range from 10 - 1000 m can be selected here. A range should be selected that is able
to fully display the maximum amplitude within the diagram
Navigating data
To switch to the next/previous measurement value. The buttons become disabled when
the oldest/newest data has been reached.
Select mouse mode

Provides the mouse with a cropping function (expands a variable section). Create a
"moused" rectangle of the section to be expanded by left clicking and releasing the mouse.
Create a "moused" rectangle of the section to be expanded by left clicking and releasing
the mouse.
The cropping function can also be enabled/disabled by double-clicking in the data area.
The remaining functions are described in the general functions of the graphics toolbox.
The extended graph toolbox enables users to navigate a measurement data file using a
slider tool. The slider can be used to select specific points in time. A measurement data file
can also be 'run'; i.e. measurement data can be monitored over a time period.
Run measurement data file

A measurement data file can also be 'run'; i.e. measurement data can be monitored over a
time period. Position the slider at the starting point and click the green start button. The
green start button changes to a pause symbol. Click the pause button to halt the

May 2011
1217
measurement data file play back.
Orbit settings
Show max Displacement
2.4.4.4 Analysis functions

Markers, text labels and cursor lines gives users important tools to analyse measurement
curves.
With markers, you can set time markers at any point required. Each time marker can then
be assigned text. Markers can be saved and then re-displayed in later evaluations.
Mouse cursor lines enable users to highlight a time range in a measurement curve (for Ytdiagrams), to evaluate it and to document it. The functioning of mouse cursors depends on
the type of diagram and is explained under each diagram type.
1218

May 2011
2.4.4.4.1 Markers
Set time markers at any point required. Each time marker can then be assigned text.
Markers are saved to a database and/or measurement data file (depending on the trend's
data source) so that they can be re-displayed in a later evaluation.

Click
to add text to a marker. The mouse cursor in the data area then changes its
appearance
Position the vertical cross-hair at the time value where the marker is to be displayed.
Confirm by left clicking. The following dialogue is displayed to configure the marker.
Show/hide marker
To hide/show markers in the graph area.
Marker overview
Opens the marker window. Refer here to marker overview.
2.4.4.4.1.1 Add marker
MarkerClick
to add a marker with text. The mouse cursor in the data area then
changes its appearance to

Position the vertical cross-hair at the time value where the marker is to be displayed.
Confirm by left clicking. The following dialogue is displayed to configure the marker.

May 2011
1219
Marker tab
Name - The name of the marker can have up to 15 characters.
Text - Additional text information. The text can be made up of several lines of text.
Time-stamp - Displays the time-stamp under which the marker is saved. Change
time enables the time-stamp to be amended.
Change time - Opens a dialog to change the marker's time-stamp.
All channels - The marker is saved for all channels.
1220

May 2011
Selected channels - The marker is saved for selected channels. This option is
available only when a channel is selected in the trend's channel table.
Visible channels - The marker is saved for all visible channels.
Priority - To enter a priority for the marker.
OK - Saves the marker and its settings to the database/measurement data file.
Cancel - Closes the dialog without adding a marker.
Layout tab
Protection tab
2.4.4.4.1.2 Marker layout
The layout tab is used to configure the appearance of the marker.

May 2011
1221
Border
Border - The marker text is given a border.

Color- The border color.
Line width - The width of the border (in pixels).
1222

May 2011
Background
Transparent - Transparent background. The measurement curves are visible. Text

background must be set to 'Text transparent'.
Text transparent - Text is by default not transparent and uses the background color
of the diagram area. This option enables users to also set the text background to
transparent. The option is used only when the 'Transparent' option is enabled.
Chart background color - The marker background is not transparent. The
measurement curves are not visible. The background color for the diagram area is
used.
Special color - The marker background is not transparent. The color setting for the
background is used.
Text Alignment
Vertical - The marker text is aligned vertically.

Horizontal - The marker text is aligned horizontally.
Font Text - The font type used for the marker text.
Font name - The font type used for the marker name.
Position

May 2011
1223
Diagram - The position of the text field in the diagram area (the anchor point is the
upper left corner) is fixed. If the area being displayed is changed, the position of the
text field remains.
Attach to data - The position of the text field in the diagram area (the anchor point
is the upper left corner) corresponds to the coordinates. If the area being displayed is
changed, the position of the text field also changes.
Attach X to data Attach Y to data -
Additional line
No line - Only the marker text field is displayed.

Time line - This option is relevant only to Yt-diagrams. A vertical (time) line is
displayed at the marker's time-stamp.
Line to point - This option is unavailable for markers.
Line to data - Automatically connects the marker text field with the measurement
data from the selected channel.
Color- The color of the connector line.
Line width - The width of the connector line (in pixels).
Other
1224

May 2011
Keep settings - Saves the settings temporarily and uses them by the next new
marker. Available only when a new marker is added.
Commit - The layout settings are saved.
Standard - Loads the default layout settings for markers.
2.4.4.4.1.3 Protection

May 2011
1225
The protection tab is used to limit the display of markers. This function is available only
when password protection has been enabled.
Protection
The markers are displayed only for users selected here.
Deactivate protection
A protection check is not performed. Markers are always displayed.
1226

May 2011
2.4.4.4.1.4 Marker overview
Opens the marker window.

This lists all the markers and text fields in a diagram. This section explains the marker tab.
The text label tab is explained under text fields.
Marker table
Table columns
Name
Name of the marker and channel names (under the + sign).
Timestamp
The marker's timestamp
Description
For markers, the text entered in marker settings/Text .
For channels (under the + sign), the channel's current value for the time-stamp, its unit
and status.

May 2011
1227
Priority
The priority entered under marker settings.
Stored
To indicate whether the marker has been saved. When not cross-checked, an error
occurred when attempting to save the marker. The error message is shown under
Comment.
Comment
Displays the error message when saving the marker.
User
If password protection is enabled, this column then displays the user who added the
marker.
Table context menu

Marker
Copy to all channels - The marker is copied to all the channels in a diagram.
Copy to visible channels - The marker is copied to all visible channels in a diagram.
Copy to channels... - The marker is copied to the selected channel. A list of
available channels is displayed to select a channel.
Channels
Delete from channel - Deletes the marker from this channel.
Other functions
Filter
The filter function restricts the markers to be listed in the table.
Save
Saves the flag to the measurement data.
The following rules apply when saving flags:
When using an open measurement data file (*.hds), the flag will be saved directly to this
file.
When portraying online data, the flag will be saved only for those channels which are
assigned to a recorder object linked to the trend chart or assigned to a database in the
DataSe rv ice .
1228

May 2011
Copy
Copies the values for the selected marker to the Windows clipboard. The values are then
available as text for other Windows applications.
Export
Saves the selected flags to a CSV file (ASCII).
Delete
Deletes the selected marker (from all channels). If only one channel is selected, the marker
is then deleted only from this channel.
Done
Closes the dialog.
Info:
Double-clicking a row (marker) opens the marker settings dialog.
2.4.4.4.1.5 Edit marker
An existing marker can be amended. Open the marker settings dialog.
Changes under the marker tab

Change name and text

May 2011
1229
Amend time-stamp
Change time enables the time-stamp to be amended. This opens the following dialog:
Change priority
Changes under the layout tab

Any setting in layout can be amended.
Commit changes
Closing the dialog with OK requires the user to confirm that the changes are to be saved.
Changes are not saved, for example, when closing the analysis window or ending the
application.
2.4.4.4.2 Text field
Users can place text fields in their analyses in addition to the markers that can be
positioned at a set time point. Text fields enable users to insert comments about their
diagrams and to connect these comments to specific points using connector lines.
The appearance of the comments can be configured via their layout settings. The examples
of text fields in a diagram show the different layout settings.
When the marker line option is enabled, a marker line can be added to the text field. The
marker line runs from one corner of the text field (the anchor point) and points to a fixed
point within the graphic, i.e. if you wish to move/zoom the text field or graphic, you can
then track where the text field belongs.
A text field can be edited after it has been assigned to a diagram. Text fields can be
deleted, have their settings amended(name, text, layout), and changes made to their
appearance. Multiple text fields can be superimposed. Marker lines can be added, amended
or deleted, and text fields converted into markers.
There are various ways in which to access these functions. One way is to call the text field
overview from the graphics toolbox or from the context menu for the diagram-data.
1230

May 2011
Another way is direct editing from the diagram via the marker / text field edit mode. The
latter offers functions that are available only in the diagram.
2.4.4.4.2.1 Add a text field
A text field is added to a diagram via the graph toolbox.

Click
to add a text field. The mouse cursor in the data area then changes its
appearance
The text field is positioned, and its size amended, by clicking and moving the text field's
border. The following dialogue is displayed to configure the text field.

May 2011
1231
Text label tab

Name - The name of the text field can have up to 15 characters. Input is optional. The
name in the text field overview enables it to be processed.
Text - The text to be displayed in the text field. The text can be made up of several
lines of text.
OK - The text field is added to the diagram.
Cancel - Closes the dialog without adding a text field.
1232

May 2011
Layout tab
2.4.4.4.2.2 Text field layout
The layout tab is used to configure the appearance of the text field.
Border

May 2011
1233
Border - The text field text is given a border.

Color- The border color.
Line width - The width of the border (in pixels).
Background
Transparent - Transparent background. The measurement curves are visible. Text

background must be set to 'Text transparent'.
Text transparent - Text is by default not transparent and uses the background color
of the diagram area. This option enables users to also set the text background to
transparent. The option is used only when the 'Transparent' option is enabled.
Chart background color - The text field background is not transparent. The
measurement curves are not visible. The background color for the diagram area is
used.
Special color - The text field background is not transparent. The color setting for
the background is used.
Text Alignment
Vertical - The text field's text is aligned vertically.

Horizontal - The text field's text is aligned horizontally.
Font Text - The font type used for the text.
1234

May 2011
Position
Diagram - The position of the text field in the diagram area (the anchor point is the
upper left corner) is fixed. If the area being displayed is changed, the position of the
text field remains.
Attach to data - The position of the text field in the diagram area (the anchor point
is the upper left corner) corresponds to the coordinates. If the area being displayed is
changed, the position of the text field also changes.
Attach X to data Attach Y to data -
Additional line
No line - Only the text field is displayed.

Line to point - Connects a line from the text field to a data point. The connecting
line is added after closing the dialog. Refer here to adding a connector line.
Color- The color of the connector line.
Line width - The width of the connector line (in pixels).
Add the line with mouse - This text is displayed only when 'line to point' is enabled.
Clicking ? opens a help dialog on adding a marker line.
Other

May 2011
1235
Keep settings - Saves the settings temporarily and uses them for the next new text
field. Available only when a new text field is added.
Commit - The layout settings are saved.
Standard - Loads the default layout settings for text fields.
2.4.4.4.2.3 Text field overview
Text fields that have been added to a diagram are listed under the 'Text label' tab in the
'Marker / Text field overview'. The text field overview enables users to access text field
settings, to show/hide text fields, to convert text fields into markers and to delete text
fields.
The text field overview is accessed via the corresponding symbol in the graph toolbox:
Table columns
Name Text field name as given in the dialog for text field settings.
Text
The text displayed in the diagram as given in the dialog for text field settings.
Visibl
e
When text fields are enabled, indicates whether the text field is hidden
(unchecked) or shown (checked).
1236

May 2011
Buttons
Delet
e
Deletes single or multiple text fields
Done
Closes the text field overview
Context menu
The following text field opens for a selected text field:
Visible
Text fields are visible in a diagram only when they are shown via the
corresponding button in the diagram's graph toolbox. The menu item
indicates whether the text field is explicitly hidden (unchecked) or shown
(checked). Refer also to edit text field.
Convert into
marker
Text fields can be converted into markers. This function cannot, however,
be undone. The option opens the set a marker dialog. The text field's
information is transferred to the dialog. The conversion takes place after
clicking OK.
Delete text
label
Deletes the text field from the overview and diagram.
2.4.4.4.2.4 Edit text field
A text field can be edited after it has been assigned to a diagram. Text fields can be
deleted, have their settings amended(name, text, layout), and changes made to their
appearance. Multiple text fields can be superimposed. Marker lines can be added, amended
or deleted, and text fields converted into markers.
There are various ways in which to access these functions. One way is to call the text field
overview from the graphics toolbox or from the context menu for the diagram-data.
Another way is direct editing from the diagram via the marker / text field edit mode. The
latter offers functions that are available only in the diagram.
Delete text label

A text field is deleted in the text field overview.
1. Open the text field overview
2. Select the text field to be deleted

May 2011
1237
3. Click Delete
Info:
Instead of deleting, users can hide/show individual or all text fields.
To select multiple text fields, click each text field while pressing CNTRL.
Hide/show text field

All text fields
Hides/shows text fields in the graph area.
Single text fields

Individual text fields can be hidden.
Open the text field's context menu from the marker/text field edit mode and uncheck Text
label
hide text label. The text field remains hidden until the user re-checks 'Visible'. This
applies even when all the text fields have been switched to show via the button for
analysis functions in the graph toolbox.
A hidden text field can be re-shown via the text field overview by open the context menu
and checking the "Visible" menu item.
Dialog for text field settings

The dialog for text field settings appears when adding or editing a text field. The dialog
enables users to amend the name, text (that appears in the diagram) and the layout of the
text field.
The dialog can be accessed by opening the text field overview or by enabling the marker/
text field edit mode and double-clicking the text field to be changed.
The dialog for text field settings opens with the text label tab. The dialog also contains a
Layout tab.
Data area context menu
1238

May 2011
If text fields are being displayed, the context menu for the graph area includes the
following menu items:
Context menu for the data area of the Yt-diagram

changed.
Text label...

overview.
Context menu items for a text field

Right-click a selected text field

May 2011
context menu item text label
1239
Properties
Opens the dialog for text field settings to enable users to change the name, text and
layout of a text field.
Hide text label

Hides the text field. The text field remains hidden until the user re-shows it. A hidden text
field can be re-shown and amended via the marker/text field overview. An analysis
function from the graph toolbox can also be used to hide/show text fields.
Add line
Switches to a special mode that enables users to add a marker line. This menu item is
available only when the marker line option has been enabled.
Convert into marker

Text fields can be converted into markers. This function cannot, however, be undone. The
option opens the set a marker dialog. The text field's information is transferred to the
dialog. The conversion takes place after clicking OK.
Bring to the front / Send to the back

Multiple text fields can overlap. These functions place a specific text field in the foreground
or background. The functions remain available even when text fields seem currently not to
overlap.
2.4.4.4.2.5 Add line
When the marker line option is enabled, a marker line can be added to the text field. The
marker line runs from one corner of the text field (the anchor point) and points to a fixed
point within the graphic, i.e. if you wish to move/zoom the text field or graphic, you can
then track where the text field belongs.
1. Selecting a text field
1240

May 2011
To select a text field, users must enable the Edit marker/text label (from the diagram area
context menu).
The mouse cursor then changes its appearance. Click a text field to select it. The text field
is then selected and placed in the foreground.
2. Enable Add line

Open the context menu for the text field and select Add line (this menu item is available
only when the user has enabled the line option).
3. Set anchor point

A corner of a text field can be selected as an anchor point. The mouse cursor changes its
appearance at the text field corners.
Clicking a corner selects the corner as an anchor point.

May 2011
1241
4. Set end point

Now position the mouse at the required end point and click. A line is now drawn from the
anchor point to the end point.
Info:
A line can be amended by following the above procedures.
To delete a line, disable the line option in the text field settings.
2.4.4.4.2.6 Examples of text fields in a diagram
Enter the text here.
2.4.4.4.3 Print diagram
This symbol from the graph toolbox opens a print dialog to print the graph currently
displayed in the graph area.
1242

May 2011
The dialog enables the following settings to be made:
Document tab
Caption - This text is used as a header.
Diagram - Prints the diagram area. Further settings can be made under the layout
tab.
Legend - Prints the legend. Further settings can be made under the layout tab.
Header - Prints the header. The header size is set under the Format/printer tab.
Logo - Prints the company logo in the left of the header. The default file is
Kundenlogo.jpg or Logo.jpg in the installations folder (when available).

May 2011
1243
Footer (File name) - The name of the measurement data file can be printed in the
footer. The size of the footer is set under the Format/Printer tab.
Comment - Prints the text entered in the 'Comment' field.
Format/ Printer field
Printer - To select a printer and settings.

Bounds - To set margins
Header / Footer - To set the size of the header / footer. Available only when
Header or Footer has been selected under the Document tab.
Copies - The number of copies to be printed
Orientation - For portrait or landscape settings.
1244

May 2011
Layout tab
Diagram section
Scale factor - alters the scaling for the diagram section (refer to the example in scaling
the diagram section).
Black White Print - the graphic is exported as black and white only. Colour settings for
channels, scales, labels and backgrounds are ignored. A black and white printer may be
unable, depending on the printer model, to print out all colour settings. The black/white
should therefore be used.
The following options are available only for Yt-diagrams and/or logic diagrams (refer also
to scaling the diagram area):
MouseCursor transparent - determines whether the label background is white or
transparent when the cursor/marker is shown. Labelling is normally white to distinguish it
from the curves.
in the legend.

May 2011
1245
Index above curves - the numbering of the measurement curve is located above the
curve.
Legend section
Automatic - Legends and comments are printed with the diagram or on an extra
page depending on the number of channels and the length of the comments. Page
breaks can be determined by Maximum rows.
One page with diagram - The legend is printed on one side with the diagram. The
diagram area is then dependent on the length of the legend.
Separate page - The legend is printed on a separate page. Any comments are
printed with the legend.
Maximum rows - If Automatic is enabled, this field sets the number of lines/rows
(for the legend plus comments) that are to be printed on the separate page.
division into columns takes place only when the legend is printed the diagram.
Align - To set the position of the legend. Below the diagram (bottom), or to the left
or to the right of the diagram. This setting is effective only when the diagram and
legend is output to a single page (refer to the legend alignment example).
Channel information
The information selected here will be added to the legends for each channel. It is shown
only when the legend is "bottom" aligned.
Scale min/max - Minimum and maximum data values for the curve.
Unit - The channel's unit.
2.4.4.4.3.1 Examples of a printed diagram

Diagram printout:
1246

May 2011
1 Header with title and company logo (5)

2 Diagram (trend)
3 Legend, in two columns with the additional information of min / max scale.
4 Comment
Example of different scaling and the setting MouseCursor transparent

May 2011
1247
Scaling at a factor of 1.2

MouseCursor transparent: yes
Numbering above the curve
Scaling at a factor of 1.0 (default)

No numbering
1248

May 2011

Numbering in curve

May 2011
1249
Example of legend alignment

No numbering
Landscape
Legend alignment: right
2.4.4.4.4 Statistics
If Yt-diagram cursor lines have been set, a statistic table can be generated for the
measurement data within the cursor lines. Hidden channels within the diagram are not
included. Table columns can be sorted according to user requirements and hidden/shown.
The table content can be copied to the Windows clipboard for further processing by other
Windows programs. The table content can also be exported into a data file.
1250

May 2011
When cursor lines have been set, select "Statistics" from the context menu for the graph
area.
Description of table columns

Color
The channel color according to the trend's channel table
Name
Channel name
Unit
Channel unit
Cursor1
(+Status)
The value for the channel at cursor position 1. The next column shows
the status of the value
Cursor2
(+Status)
The value for the channel at cursor position 2. The next column shows
the status of the value
Difference
Difference between values Formula: (Value for Cursor2 - Value for

Cursor1)
Minimum
The minimum in the statistic time range
Time (minimum)
Timestamp for the minimum
Maximum
The maximum in the statistic time range
Time (maximum) Timestamp for the maximum

Min/Max
difference
The difference between the values in the minimum/maximum columns

according to the formula (Max - Min)
Average
The channel's average for the statistic time range. The integral is
calculated from this average
Formula: Integral / time-range in seconds
Integral
Integral for the channel's measurement data according to the statistic

time range on a seconds basis
Increase
Increase for the channel over the statistic time range

Formula: (Value for Cursor1 - Value for Cursor1) / time-range

May 2011
1251
Also displayed is the unit (e.g. mV / sec)

The time basis depends on the selected time range:
Time-range up to 5 seconds: milliseconds
Time-range up to 30 minutes: seconds
Time-range > 30 minutes: Minutes
Number of
values
Number of measurement values within the statistic's time range. For

high data resolutions and/or times, computing Number of values can
require a noticeably high level of computing resources. By default, this
column is therefore not used.
Comment
Comments on the channel according to the trend's channel table
Hide/show columns
Users can hid/show individual columns. Values are not computed for hidden columns.
Open the context menu from the table header and select 'columns'. This opens a dialog
listing all the available columns.
Select the columns to be shown (checked).
Sort columns
1252

May 2011
A column can be moved using the mouse (drag&drop). The new position is indicated with a
green-colored pointer.
Status information
The statistic time-range is displayed in the lower section of the table. The time range can
be adjusted by moving the cursors in the diagram.
The timezone is also given in the table's status information.
Export functions
Copy
Copies the table to the clipboard. The columns are separated by tabs. One row is
generated for each channel.
Export

May 2011
1253
Exports the table to a file according to the ASCII export settings.
2.4.4.4.5 Offline calculation channels
An HDS file can be added to offline calculation channels using this button in the header of
a diagram's (Yt-diagram, logic diagram) channel table. An offline calculation channel is an
extra channel which can be used to perform calculations on measurement data within the
measurement data file.
Clicking the button opens the calculation channel window. Operation is identical to online
calculation channels and is explained in adding a calculation channel.
A calculation channel can also be added using drag&drop. Select an analysis formula from
the formulary in the management tree and drag&drop it in the channel table. For diagrams
with multiple y-axes, the new calculation channel can be dragged directly onto the y-axis
under which the calculation channel is to be added. After dropping, a settings dialog
opens with the selected formula.
1254

May 2011
An offline calculation channel contains all the formulas already being used in the
measurement data file as well as the formulas in the analysis formulary. The formulas are
identified in the list by the prefix "FormelPool - ...".

May 2011
1255
After users have made the required entries within the calculation channel window and
clicked OK, the offline channel appears in the trend's channel table.
Checkboxing Show performs the calculation and the channel is saved to the HDS file.
1256

May 2011
The settings dialog for the calculation channel can be opened using the channel's context
menu via the channel table. The settings for a calculation channel can not be changed.
Info:
A calculation channel can not be directly deleted from a measurement data file. A
calculation channel can be removed from a measurement data file via a data export. The
following method is recommended:
Display the complete measurement data file, without cursor.

Hide all channels that are not to be exported (i.e. removed/deleted).
Start a measurement data file export (for displayed channels only) via the context
menu in the data area.
2.4.4.4.6 Formulary
Formulas for analysing measurement data files can be created and stored centrally within
the formulary.
The formulary is displayed in the management tree after opening the measurement data
file:

May 2011
1257
Double-clicking the formulary in the management tree opens a window listing all the
available formulas.
The name of the formula and the formula itself is displayed.
A new formula is created. This opens the formula editor which can be used to enter new
formulas.
The selected formula is deleted from the formulary.
2.4.4.5 Export options for a trend

A range of export functions are available in a diagram's data area. The options available
are: measurement data file export; ASCII export; EMF export.
Diagram data area context menu
Export
1258

May 2011
ASCII export (all channels) ...

ASCII export (visible only) ...
Users can select an ASCII export for all channels in a trend or for the trend's visible
channels only.
Once an ASCII export has been started, a time-range dialog opens. This dialog is used to
set the required time range. A dialog then opens to select a file for the output.
If a file is selected that already exists, the user is asked whether this file is to be
overwritten. If 'Yes', then the ASCII export overwrites the existing file. If 'No', the ASCII
export is aborted.
The settings for the ASCII export are taken from the ProfiSignal general settings (ASCII
export tab ).

Before starting an ASCII export, users can open the dialog for ASCII export settings and
make the required export configuration.
Info:
Changes made here also change ProfiSignal's main settings.

May 2011
1259
Data export (all channels) ...

Data export (visible only) ...
Users can select an data export for all channels in a trend or for the trend's visible
channels only.
Once an data export has been started, a time-range dialog opens. This dialog is used to
set the required time range. A dialog then opens to select a file for the output.
If a file is selected that already exists, the user is asked:
Overwrite
The existing data file is overwritten
Attach
The exported data will be added to the existing data in the

measurement data file
Cancel
Aborts the data export
Info:
This function enables multiple data files to be copied to a single file.
export trend as EMF

The diagram's graphical portrayal is exported to an EMF file.
Windows Enhanced Metafile (EMF) is an enhanced version of the Windows graphics file
format (WMF). The format has been developed to facilitate the exchange of graphic files
between different programs and is included in the Windows clipboard function.
In contrast to WMF, EMF uses a 32-bit format for defining image coordinates. EMF can also
be used as a printer language.
1260

May 2011
Once an EMF export has been started, a dialog opens to select an output file.
Users can export either a diagram only or a diagram with legend ( examples of EMF export).
Export trend to clipboard (EMF)

Export trend and legend to clipboard (EMF)
The diagram's graphical portrayal is copied to the clipboard. Graphics in the clipboard can
then be copied into other Windows programs.
EMF export settings

May 2011
1261
Size
To set the size of the graphic to be exported. This is useful when the graphic is to be
processed with report tools that require a specific size of graphic.
The default setting (Height and Width = 0), the graphic is exported at a 1:1 ratio of the
current measurements of the graph in the graph area.
Diagram section
Scale factor - alters the scaling for the diagram section (refer to the example in scaling
the diagram section).
MouseCursor transparent - determines whether the label background is white or
transparent when the cursor/marker is shown. Labelling is normally white to distinguish it
from the curves.
in the legend.
Index above curves - the numbering of the measurement curve is located above the
1262

May 2011
curve.
Black White Print - the graphic is exported as black and white only. Colour settings for
channels, scales, labels and backgrounds are ignored. A black and white printer may be
unable, depending on the printer model, to print out all colour settings. The black/white
should therefore be used.
Legend section
Without legend - Legend is not exported.
With legend - The legend is output at the page margin and then aligned according to
the other settings. The area for the diagram is dependent on the size of the legend.
With legend on chart - The legend is output in the diagram.
Maximum rows - Unavailable for EMF exports.
division into columns takes place only when the legend is printed the diagram.
Align - the position of the legend: below the diagram (bottom), or to the left or to the
right of the diagram.
Channel information
The information selected here will be added to the legends for each channel. It is shown
only when the legend is "bottom" aligned.
Scale min/max - Minimum and maximum data values for the curve.
Unit - The channel's unit.
Diagram in clipboard
The diagram's graphical portrayal is copied to the clipboard. Graphics in the clipboard can
then be copied into other Windows programs. EMF-export settings are not taken into
consideration.
Dialog for export time range

When a trend or data export is started from the graph area, the following dialog appears.
Select the time range to be exported.

May 2011
1263
When the trend's source is a measurement data file, information about the file is also
displayed.
Info:
If the file's complete time range is to be exported, click OK.
If the user changes the time range, the time range is then rounded to the nearest
second.
2.4.4.5.1 Export ASCII file
To use data in other programs requires that the data is converted into a format that can
be import by the target software. Most target software, e.g. Excel, can import the ASCII
1264

May 2011
format. Export data therefore requires conversion into ASCII format.

Open measurement data file for analysis
select diagram type
ASCII export
ASCII export is initialized via the dialog Open measurement data file for analysis. The ASCII
export button in diagram type selection opens the following dialog.
Measurement data file information

May 2011
1265
Displays the Start and End times for the measurement data file. The time-stamp is
portrayed as the given timezone.
The timezone is determined from the measurement data file. If all channels use the same
timezone, this timezone is then used in the dialog. If different timezones are used, a
message is displayed and the local (PC) timezone is used for the time-stamp.
Channel table
The channel table lists all the channels in a file. It displays the channel name, Unit and
Comments for the channels. When a file's channels have differing timezones, the table also
displays the timezone information for a channel.
If only specific channels are to be exported, these can be selected from the channel table.
To select a series of channels, click the first channel of the series + SHIFT + click on the
last channel of the series. To select multiple channels that are not in a series, press CNTRL
and click each required channel.
To de-select and already selected channel, re-click it.
Status
Displays the export's progress. For Adaptive Block by Block mode, the currently active
channel is displayed.
1266

May 2011
Time range
The default setting is the time range for the whole measurement data file. A specific time
range can also be exported.
The timezone for the time-stamp to be portrayed can also be amended here. The timezone
can be the channel's timezone, the local (PC) timezone and the UTC time.
Data resolution
The original data (all values) is the default setting for ASCII exports but compressed data can also be used.
Block values are then computed for the required data resolution - the average, minimum and maximum
values for a time range.
The Adaptive Line By Line export mode uses the channel's average value. This corresponds to the with the
time scale determining data resolution.
The export mode Adaptive Block By Block exports minimum and maximum values as well as averages.
Opens the dialog for ASCII export settings. The settings here can then be checked and
amended if required.
Start ASCII export

May 2011
1267
Starts an ASCII export. Th progress of the ASCII export is displayed in the status line. The
Close button is replaced by the Cancel which ends the ASCII export.
Cancelling an ASCII export retains the data in the export file that has been exported up to
clicking cancel. The file is not deleted.
Close dialog
Closes the dialog. Any changes made to the ASCII export settings are also made to the
main settings.
2.4.4.5.1.1 ASCII export settings
Some target software require separators between the data.

ASCII export dialog
ASCII settings
Use the ASCII export settings dialog to configure the ASCII-export output file.
1268

May 2011
ASCII settings
Header
The following data is included in the header:
ASCII file name
Data source
Number of channels
Data resolution and export mode
ASCII export time range and timezone
Information about the channels to be exported
Channel ID
Measurement unit
Comments (long)
The header data can be hidden/shown.

May 2011
1269
File name;
C:\Software\exe\Data\Online Analyse_1\AsciiExportNeu.csv
Measurement data file;
Automatic
Number of channels;
Data resolution;
All values;
Start time;
30.06.2009 08:22:40,353
End time;
30.06.2009 08:27:27,763
Timezone;
Local timezone (PC)
Channel name;
Speichertemp3;
Spannung 1;
Spannung 3;
Unit;
C;
mV;
mV;
Adaptive line by line
Comment
Analog input #02, Module ADIT #01
Export comments
Comments (long text from channel information) can be separately hidden/shown.
Date and time

Date and time columns can also be hidden/shown. Date and time (one column) uses a
single column for date and time. A space character separates date and time.
The timestamp can be generated relative to the starting time.
The timestamp precision can be set. Milliseconds are possible that can then be recorded to
a separate column.
Dec. separator
Decimal point or comma depending on target software requirements.
Line separation / column separation
1270

May 2011
Select the character for line and column separation. The default for line separatorsis 'LF'
and for columns ';'.
Select the character that is required by the target software. Special characters such as
TAB are to be in put as their ASCII code. For example, for TAB enter: $09 (09 = ASCIICode for TAB). An ASCII code always has 2 digits. If the '$' character is given for text, it
must be input with the ASCII code.
Refer here to escape sequences for tables.
From Excel version 5.0, an assistant is available to facilitate data import.
Number prefix and number suffix

These limiters have spaces as default values. Some programs require limiters for numerics.
The limiter characters can be entered here. Special characters (non-printable characters)
are entered using an ASCII code (see above).
Decimal places
The number of decimal places (default = 2). This setting is used for the data type 'double/
floating-point number'.
Export modus
Adaptive block by block

Saves measurement data only when a value changes. For each channel a data block is set
up which contains all measurement value changes in sequential order with date/time. This
is the default setting for export modus.
Adaptive line by line

Saves measurement data only when a value changes. For each change in measurement
data, a new line is generated for any selected channel.
Equidistant line by line

May 2011
1271
Saves measurement data according to a set time period. The data is then easy to insert
into an Excel table.
ASCII settings templates
The settings can be saved as a template. Save opens a dialog window that enables users
to enter a name for the template:
To use an existing template, select it from the dropdown list and click Load.
A template can be deleted from the list.
Standard resets the current settings to the default settings.
Default settings for ASCII export:
1272

May 2011
Characters
Description
ASCII characters
ASCII code
\a
Alarm
BEL
07
\b
Backspace
BS
08
\t
Horizontal tab
HT
09
\n
Line feed
LF
0A
\v
Vertical tab
VT
0B
\f
Form feed
FF
0C
\r
Carriage return
CR
0D
2.4.4.5.2 Example of EMF exports
This example shows how a trend diagram appears in ProfiSignal. It then shows how it
appears as an exported graphic without a legend.
Trend diagram in ProfiSignal:

May 2011
1273
Export trend as EMF:
1274

May 2011
Y1
25.0
20.0
15.0
10.0
04-01-2008
07-01-2008
10-01-2008
13-01-2008
Export trend and legend as EMF:

Y1
Legende
Aussentemperatur
25.0
20.0
15.0
10.0
04-01-2008

May 2011
07-01-2008
10-01-2008
13-01-2008
1275
2.4.4.6 File factory

The File factory enables users to concatenate whole or partial data files into a new or
relative file.
Concatenated data file

Selected measurement data files or sections of measurement data files are exported to a
new or existing measurement data file. Channel IDs and time-stamps remain unchanged.
Refer also to concatenating measurement data files.
Relative data file

All the channels from a source data file/ selected channels from a source data file are given
new channel IDs in the relative data file (when a source channel ID exists). Refer also to
creating a relative measurement data file.
The time-stamps are amended according to the relative time-stamp settings.
Source file data and channel ID assignment are determined in the trend configuration and
are saved to the relative measurement data file
Relative measurement data files enable users to compare measurement curves and/or
characteristic curves with absolute time-stamps.
The File Factory is opened either via the

Main menu File
symbol or File in the main menu.
File Factory
1276

May 2011

May 2011
1277
2.4.4.6.1 File factory dialog
1 - Yt-diagram
Source files are loaded into the Yt-diagram. Cursor lines can be used to select the channels
and time range to be exported.
2 - Measurement data file table

The table lists all the selected source files (including partial files). The table shows source
file names and start/end times. When a relative file is has been selected, a column for
trigger times is also shown.
The table's source files can be edited.
1278

May 2011
3 - Operation
Load mesfile
Loads the required source file into the Yt-diagram. This opens a dialog to open a
measurement data file for analysis. Select the source files and close the dialog with OK.
The selected source data is loaded into the Yt-diagram. The cursor lines appear
immediately to select start/end time. A trigger time cursor line is also shown for relative
files.
Add
Once the source has been loaded into the Yt-diagram, and once channels have been
selected and settings made for the time range and trigger time, the source file is then
included in the table.
Delete
Delete removes the selected entry from the table.
Edit
To re-load a source file into the Yt-diagram and to amend its settings.
Concatenate mesfiles / Create relative mesfile

To set whether a concatenate or relative file is to be created.
Load destination
Available when Create relative mesfile is enabled. An existing relative file can be loaded as
a destination file.
This opens a dialog to open a measurement data file for analysis. Select the destination
files and close the dialog with OK.
The table now displays the destination file with information on the source files.

May 2011
1279
Start
Either starts concatenation or creates a relative file (depending on setting).
Concatenate mesfiles
Opens a dialog for users to select either an existing file or create a new file.
An existing file can either be overwritten or added to. The following window opens:
Override
The existing data is deleted and replaced by the new data.
Attach
Existing data is retained and the selected data is added to it.
Cancel
The procedure is aborted and no concatenated file is created.
Create relative mesfile

If a destination file has been loaded, it will be added to with the new source data.
If no destination file has been selected, a dialog opens to input the name of either a new or
existing relative file.
An existing file can either be overwritten or added to. This opens a dialog (see above)
Override
The existing relative file is deleted and replaced by the new data.
1280

May 2011
Attach
The existing relative data file is retained and the selected data is added to it.
To add to a relative file, it is recommended that users first load a destination file.
Cancel
The procedure is aborted and no relative file is created.
4 - Progress display
Displays the progress in creating a concatenated or relative file.
5 - Close dialog
Delete
Deletes all entries from the table.
Close
Closes the file factory dialog.
2.4.4.6.1.1 Measurement file table
Concatenated measurement data file

file names, and the start/end times.
Relative measurement data file

May 2011
1281
file names, start/end times and trigger times.
When a destination file has been loaded, information is also displayed on this relative file.
Edit source data

Re-load source data into Yt-diagram
Select the required source data from the table. Edit
re-loads
the source data into the Yt-diagram. The cursor lines are set to the time-stamp settings
and the channels are shown that are to be exported. The Add button is replaced by
Commit.
The Yt-diagram's time range and export channels can now be changed (the shown
channels are the export channels).
The Commit button becomes available once changes have been made
. This button accepts the new settings for the selected source
data.
Source data can also be edited by double-clicking its entry in the table.
Amending the time-stamp in a table

The time-stamp for start/end/trigger times can be amended via the context menu for a
table entry.
This opens a dialog to change time settings.
1282

May 2011
Amend channel selection

The context menu can be used to amend the export channels.
The context menu displays the current settings.
All channels
All source file channels are exported.
Visible channels
Only the source file's visible channels are exported (the channels that are visible when
adding the source file).
Select channels ...

Opens a dialog for channel selection.
The dialog enables users to select the channels for export.

May 2011
1283
Delete source files

Select the source file to be deleted from the table. Delete
deletes the entry from the table.
2.4.4.6.1.2 Yt-diagram
Users can configure the source files for the file factory's Yt-diagram:
Export time range

Start and end times are set using the cursor lines.
A trigger time for relative files is also set using cursor lines.
Cursor lines offer an An Attach to data option to enable users to precisely select start/
end/trigger times. The option is accessed via the context menu in the graph area.
Select the channel for the cursor line. Moving the mouse automatically positions the cursor
line at the value before the mouse cursor. The measurement value's time-stamp is now
used.
Mouse cursor is moved
After moving mouse cursor
1284

May 2011
Channel selection
When the source data is added to the table using Add
channels visible in the Yt-diagram are used as the export channels.
, the
Loading new source data

The
file.
symbol in the graph toolbox's Yt-diagram enables users to directly load a source
Using a Yt-diagram
A Yt-diagram in a file factory does not have all the functions of a normal Yt-diagram. Some
buttons are disabled or hidden.
2.4.4.6.2 Concatenating measurement data files

Concatenated data file
Selected measurement data files or sections of measurement data files are exported to a
new or existing measurement data file. Channel IDs and time-stamps remain unchanged.
Enable the option Concatenate mesfiles.

May 2011
1285
Load the required source data, using Load mesfile,

into the
diagram. This opens a dialog to open a measurement data file for analysis. Select the
source files and close the dialog with OK.
Use cursor lines to set the start/end times for the export time range.
Use Add
to include the source file in the table.
Now select other source files. Different time ranges from a single file can also be selected.
Concatenation takes place by clicking Start
shows which source file is currently being exported.
. The progress bar
2.4.4.6.2.1 Concatenation examples
This example briefly shows how concatenated files are created.
Source files
File_001
File_002
1286

May 2011
Concatenated file
2.4.4.6.3 Creating a relative file
Relative data file

May 2011
1287
All the channels from a source data file/ selected channels from a source data file are given
new channel IDs in the relative data file (when a source channel ID exists).
The time-stamps are amended according to the relative time-stamp settings.
Source file data and channel ID assignment are determined in the trend configuration and
are saved to the relative measurement data file
Relative measurement data files enable users to compare measurement curves and/or
characteristic curves with absolute time-stamps.
Creating a relative file

Enable the option Create relative mesfile
1288

May 2011
Load the required source data, using Load mesfile,

into the
diagram. This opens a dialog to open a measurement data file for analysis. Select the
source file and close the dialog with OK.
Use cursor lines to set the start/end times for the export time range. A trigger time is also
required to convert the time-stamp.
Use Add
to include the source file in the table.
Now select other source files. Different time ranges from a single file can also be selected.
'Start'
creates the relative file. The progress bar shows the
source file currently being exported.
2.4.4.6.3.1 Relative file example
This example briefly shows how a relative file is created.
Source files
Two sections of a source file are to be exported.
Section 1
Section 2

May 2011
1289
Relative data file

The measurement curves are now displayed together in a relative file.
The trigger time in the source file has been set to 00:00:00 in the relative file.
The Yt-diagram channel table for a relative file shows the source file as well as the channel
ID. These columns are shown in the following example. The source file name is prefixed with
an index.
1290

May 2011
Further information on the source file, such as time range, is available from the channel
settings dialog. The context menu is opened by double-clicking a channel in the channel
table.
2.4.4.7 Showing a database in a trend

Pro fiSig nal enables users to display a database in an analysis window.
File
Show database in trend...
The
symbol in the main menu opens the following dialog.
Server / Database
Lists all the available databases. All measurement databases and scheduler databases are
listed.

May 2011
1291
Info:
Inactive/disabled databases are also shown.
Stored configurations
Once a database has been selected, a list is displayed here of the trend configurations
previously stored in ProfiSignal.
Properties
Displays the storage properties for the selected device storage. If the storage device is
active, the current Start- and End times are updated. If the device's timezone is available,
it is then used as the time-stamp.
Show in trend
Opens the analysis window.
If a database only is selected, without a trend configuration, a diagram type must then be
selected. This opens the following dialog:
1292

May 2011
The Orbit and FFT diagrams are available only with the vibration analysis licence.
Close dialog
The dialog for Showing a database in a trend requires the user to close it (no automatic
closing).
2.4.4.8 Device memory readout

Pro fiSig nal enables users to readout the internal memory in Me ssag e devices.
File
Readout device storage...
The
symbol in the main menu opens the following dialog.

May 2011
1293
Users are able to:

- Readout a complete device storage
- Readout a device storage for a specific time range
- Display the readout data in a diagram
- Perform an ASCII export of the readout data
- Configure a filename and path for the measurement data file
Device / Storage group

Lists all the available Me ssag e devices and their and storage groups. Only one storage
group can be selected for readout. Once a group has been selected, information on the
group is displayed under Stored channels in storage group and Properties.
Stored channels in storage group

Lists the channels for the selected storage group. Individual channels can be selected for
the readout Select multiple channels clicking channels while pressing CNTRL+SHIFT.
1294

May 2011
Info:
Readout all the channels for a T o pMe ssag e storage group. Specific channels can
then be processed at the PC.
Properties
Displays the storage properties for the selected device storage. If the storage device is
active, the current Start- and End times are updated. If the device's timezone is available,
it is then used as the time-stamp.
If only a part of the storage device is to be readout, the required time range is set here.
Otherwise the complete device storage is readout.
Info:
It may take a number of seconds (especially for large storage partitions) before the
readout to a PC begins. This is because the required data first needs to be
"searched".
Storage contents

May 2011
1295
Show in trend
The selected storage data is displayed in a diagram. When the readout has been
completed, a dialog opens to select the required diagram type.
If Save to HDS-File has not been selected, a temporary file is set up and displayed.
The temporary file is deleted when the analysis window is closed.
Export ASCII file

The readout data is converted into ASCII format according to the export settings.
If Save to HDS-File has not been selected, a temporary file is set up. The temporary
file is deleted after the ASCII export.
Settings
This button opens a dialog for export settings. Users can then make the required
export settings. The settings are saved and re-used for the next export.
(Refer also to general settings)
Data density
The original data (all values) is the default setting for ASCII exports but compressed data can also be used.
Block values are then computed for the required data resolution - the average, minimum and maximum
values for a time range.
The Adaptive Line By Line export mode uses the channel's average value. This corresponds to the with the
time scale determining data resolution.
The export mode Adaptive Block By Block exports minimum and maximum values as well as averages.
Filename
The name and destination directory for the converted data.
1296

May 2011
Save to HDS file

If users select an existing file, they will be asked whether the file is to be overwritten
or added to .
This makes it possible to read multiple storage groups into a single file.
Other sections
Start / Close
Start
Starts the readout. The progress is displayed in the progress bar. Close aborts the
readout (button name changes to Cancel).
Close
Closes the dialog.
Progress bar
Displays the current readout progress and the number of copied measurement values.

May 2011
1297
2.4.4.9 Saving measurement data

Pro fiSig nal enables continuous and batch data recording.
Measurement data files can be set up with start/stop settings at the same time as data is
being permanently recorded as a background service. Data records can also be set up with
manual start/stop settings.
Continuous data recording

In continuous data recording, data is recorded to the DataSe rv ice on a channel basis.
Measurement databases can be set up. Measurement data can be portrayed in the required
trend diagram.
The data can be accessed by any application connected to the DataService. Measurement
data is recorded independently from applications. Data is therefore acquired and recorded
even when there are no applications running.
This recording method means that movement can be made along trend diagram time axes
from the current measurement value back to anywhere in the past. Data is displayed
immediately without any delay.
This is important for the monitoring of plant and machinery, for continuous production
processes, for the acquisition of quantities, endurance testing etc..
Database set up in DataService
For continuous data recording, a measurement database must be set up in the
DataSe rv ice . Measurement data within the database is then available to any online
analyse.
In continuous data recording, data is recorded to the databases so that historical data is
available to online analyse.
Benefits
A special feature of the DataService is that large masses of data can be processed at a
high level of data resolution. The data can then be displayed at high-speed on the screen.
Batch data recording (recorder files)

Batch processes are distinguished by a finite duration with start /stop conditions. Manual
start / stops are also a feature.
The recorder is the ProfiSignal component that is responsible for storage. The data is
stored to a recorder file.
Important application areas for batch recording are experimental trials, fault data
acquisition, fault detection, the monitoring of plant and machinery, production processes
etc..
1298

May 2011
Info:
A combination of recording methods can be used. Batch recording can be performed at
the same time as continuous data is being recorded.
No data recording
If no database has been set up and no batch file is currently being processed, the
historical data for a channel is available only once a channel has been assigned to a
diagram.
2.4.4.10 Global alarm lists

Global alerting facilitates the visualisation of alarms.
Global alerting is similar to the alarm list object. This chapter here therefore explains only
the differences to the alarm list. It would be useful for you to familiarize yourself with the
alarm list chapter.
Open global alerting
To open global alerting click the symbol in the main menu (circled in red). This symbol is
not available under the symbols for visualisation objects.
Direct access to alarm classes

May 2011
1299
Existing alarm classes from the DataService are used in the list's local filter. To display the
alarms for a class, the class must be checked in the local filter. The method using the
settings dialog, as used for alarm lists, is not necessary.
Available only in runtime mode
Global alerting is always in runtime mode. Switching to edit mode is not possible.
'Configuration of standard' is therefore unavailable.
No settings dialog
Global alerting has no settings dialog. Some settings are therefore unavailable. This
includes fault diagnostics, sound playback, the hide/show tool bar functions as well as
others.
settings for alarm colors and the hiding/showing of columns can be made using the
properties button.
1300

May 2011
2.4.5
Report viewing
This section describes how to view a previously created report. Creating reports is
described in the report designer section. Previously created reports are portrayed by report
viewing. In the following, a short description is given of the various methods of opening a
report file.
Methods for opening a report file

Via the toolbar
The report can be opened via the open report option in the toolbar.
Via the menu

The report can be opened via the option File|Open Report in the main menu.
Via a script
Object function: Script
Initiate
Report
Open report file
A created file can be opened during runtime via a script. Refer here to the open report file
object function.
Report button
The VisuView has a report button that can create a report during runtime. This report can
also be viewed immediately after it has been created. From the report button's properties/
settings dialog select open the report from the button tab.
Once the report has been opened it can then be viewed. The following describes the
different functions for report viewing.

May 2011
1301
The ReportView menu
The report settings option opens a settings dialog. This dialog enables the following
settings to be made: Name enables input of a specific name for the report and resolution
settings sets the report's resolution (for printing) in DPI.
Toolbar to open, save and import a report
1302

May 2011
The first button enables a report to be opened or saved. An additional report may also be
imported. This means that the selected report in the open-dialog will be inserted into the
report already opened. The pages of the selected report are attached to the end.
Toolbar for printing, print settings, preview and PDF-export
These enable the report to be printed, to change print settings, to export the report in
PDF-format and to display a preview of the report. Preview opens a window to portray the
print.
Formatting report object text
These buttons enable changes to be made to the font and alignment of text. In the above
example, changes are being made to the label report object. Such changes can not be
made for picture and graph/diagram report objects.
Report layout save, open, new, edit, and information
Save layout

May 2011
1303
To save the new/amended report layout. Further amendments can be made by clicking the
new layout button. Click edit layout to save an amended design. Clicking the save layout
button opens the layout information dialog to enable input of a new layout name. Any
changes require saving under a new report name because it is not possible to overwrite an
existing report.
Open layout
The dropdown box lists all the available layouts.

Delete layout
Clicking this icon deletes a report layout. This button is active only after selecting a layout
and clicking edit. The standard layout can not be deleted and the button remains inactive
for this layout.
New layout
Opens an empty page. This enables a new layout to be created using the previous report
object settings.
Edit layout
To make changes to the layout. This mode disables the functions print, preview and PDFexport. Changes can also be made to a report object via the menu and corresponding
settings dialog. This can happen only when this button is enabled.
Layout information
This opens a corresponding dialog. This lists all the information on changes made to the
report.
First, previous, next and last record
These functions enable the browsing of report pages. The outer buttons enable jumping to
the first and last pages respectively. The inner buttons enable page-by-page browsing.
Status bar
The first six values provide the cursor's position on the report page. The final field indicates
the report object on which the cursor is positioned. This can be seen in the above example.
1304

May 2011
2.4.5.1 Edit report

A previously created report can be edited. Open the report and activate the edit mode
using the pointer key.
Then select the report object to be edited.
Report object menu

Open the report object menu by right clicking the report object.
Grouping
The group submenu option enables the selected report object to be include within a group
and ungroup deletes it from an existing group.
Order
The submenu option bring to the front places the report object in the foreground and send

May 2011
1305
to the back places it in the background.

Properties
Opens the properties/settings dialog for a report object.
Edit DB value
Database values can be edited for the following report objects: string, text, number and
picture. Selecting this option opens a dialog (whose appearance differs depending on the
type of report object). Current values are on the left and these can be edited on the right.
Note: Changes are recorded and listed in layout information.
Search
Lists the locations where the report object is accessed from within Pro fiSig nal. Refer also
to the search dialog section
Other options
Shift, enlarge and shrink
These enable report objects to be moved, enlarged and shrunk using the mouse.
Report viewing menu
The report viewing menu also enables a report object to be cut, copied, pasted and
deleted.
2.4.5.2 Import report
The import report

button in the report window can be used to extend the current
report with a previously created report.
A report file is selected for import. This file's records are then appended to the records of
the currently opened report.
The import function is a method to extend a report.
Only reports from the same application can be imported.
2.4.5.3 New layout
The new layout

function in the report window enables the layout of previously created
reports to be fully amended but for the report object content to remain unchanged.
Creating a new layout

Click new layout in the report window to open the following dialog. This lists all the
available reports and their subreports. The example shows Report_1 as a report with the
following two entries being subreports. Select the report whose data is required. Selecting
a report and confirming the dialog with OK opens a blank report.
1306

May 2011
Inserting report objects and linking them to previously created

objects
A dialog opens which lists all the report objects that can be used. These objects stem from
the selected report. The example below lists five report objects (Picture_1 to Picture_5)
that can be found in Report_1.
Note:
The new layout can not be saved under the same report name. A previously created report
is always write protected. The new layout can only be saved using a new name.

May 2011
1307
2.4.5.4 Layout information

The layout information provides information on a created report. Click the layout
information button in the report window
The following example is used to explain some of the information that can be found in the
log table.
The first line of the log table shows the data and time of when the report was created,
then the date and time an object was created and then the date and time a value, in this
case 182.29, was assigned. The lower lines show when the created report was reopened.
The value of the report object was then amended from 182.29 to 150.
1308

May 2011
Header information
The title shows the currently selected layout. This is followed by the names of the author
and company. A text field for entering a description then follows.
Log table
The table has three columns:
LogTime: Displays the date and time.
LogType: Displays the type of information.
LogMessage: Displays text information.
There are seven log types:

Info (information)
The information for which the user is responsible. An example of this is creating a report
object and assigning data to it. The user has first set up the object and then set the type
of data to be assigned to it.
Warning
Warnings that have occurred when creating or editing the report.
Error
Errors that have occurred when creating or editing the report.
System
Information that has been generated by the system.
VChanged
A value under this data type has been amend. An example of this is the amendment of a
number in a created report.
UserMsg
Is not yet used in the current Pro fiSig nal version.
Unknown
Any information that does not correspond to any of the above data types.
Filtering data type

Right clicking the table opens the menu below. This menu is used to select the information
that is to be displayed.

May 2011
1309
2.4.5.5 Report preview

Selecting the preview option in the report window opens the following dialog. It portrays
the report in the format in which it will be printed. Depending on the printer, the report will
be displayed either in color or black and white.
A 2-page report displayed in the report window. Page 1 is on the left and page 2 on the
right. Both pages are numbered 1 and both tables are identical.
1310

May 2011
The same report in preview. The correct page numbers are displayed and the page 2 table
is a continuation of the page 1 table. The page 2 table displays the lines that could not be
displayed on page 1.

May 2011
1311
Print and print settings
These buttons print the report and enable users to make printer settings. If a black and
white printer is selected, the preview will be in black and white.
Browse pages
These buttons enable users to easily browse through the pages of a report. The buttons on
the far left and right display the first and last pages respectively. The buttons immediately
preceding these move you one page forwards or backwards. The central dropdown box
enables selection of the required page to be displayed.
Page view
1312

May 2011
The first three buttons are for autoscaling the report page. The first button shows the
page width. The second button shows the page length. The third button shows the
complete page in its entire length and width.
The dropdown box enables the page scaling to be set from at least 10% through to a
maximum of 400%.
Left clicking the magnifier (button on the far right) enlarges the display. Right clicking the
report page displays the whole page.
Mouse function
If this button is activated, the complete page can be moved in any direction by left clicking
and holding at any point on the page.
The mouse's middle wheel enables, depending on the toolbar mode, either page-by-page
browsing or scaling changes.

May 2011
1313
2.5
Appendix
Software tools
Tables
Version history
1314

May 2011
2.5.1
Software tools
DataBaseCheck
Convert2HDB
DelphinSupportData
2.5.1.1 DataBase check

Das Tool DataBaseCheck berprft ProfiSignal Messdateien und Datenbanken auf Fehler.
Untersttze Dateitypen:
.hds
.hdd
.hdl
.hdi

May 2011
1315
2.5.1.2 Convert2HDB
1316

May 2011
2.5.1.3 DelphinSupport data

May 2011
1317
2.5.2
Tables
Measurement data status
2.5.2.1 Measurement data status
Text in channel table

---
Forced
Invalid
Disconnected
--Wrong configuration
Defect hardware
Wire Break
Upper range
Lower range
Invalid value
INFINIT
NAN
--Block incomplete
No data
Description in
Description
Klicks programming language
Scaled Value
The measurement data has been converted into a
unit of measurement from binary A/D converter
code.
Forced Value
The measurement data has been forcibly replaced
by a replacement value or simulated measurement
data.
Invalid measurement data
The data is invalid because of an unspecified error.
Connection interrupted
The connection to the data source / device has
been interrupted.
Changed datatyp
The type has altered within a min/max/average
block.
Error in configuration
The channel configuration contains errors.
Hardware error
The hardware contains errors.
Wire Break
A wire break has been detected.
Upper range
The measurement data is at / above the
measurement range.
Lower range
The measurement data is at /below the
measurement range.
Invalid value
Currently not used.
Infinite value
The data was infinite and has been replaced by a
valid value.
No number
The data was divided by 0 and has been replaced
by a valid value.
Alarm
Currently not used.
The min/max/average block could not be
completely/correctly computed because of data
omission / altered time.
No data
Recording has been interrupted / paused.
1318

May 2011
Expert Key
Expert Key is Delphin's product series for PC-supported measurement technology and test
stand automation.
The entire functioning of an Expert device is incorporated onto a single circuit board, giving
it an extremely compact format. Expert Key devices are equipped with both USB and
network interfaces that can be used as required.
The devices are available in different constructions and types.
The devices are supplied with ProfiSignal Go software for the quick-start of measurement
and automation procedures. Functions range form data storage, both in record and
continuous database format, right through to online and offline analyses and monitoring in
trends. There are also functions for monitoring, alarm-management and data-export.

May 2011
1319
3.1
Different devices
The devices are available in different construction forms and types.
This construction forms are available :

Expert Key L the pop-up table-top device
Expert Key C for installation in control cabinets
Expert Key P the laboratory device with 4 mm plugs
Expert Key M the mobile case
Expert Key T - for multi-channel temperature measurement and more
See description in the next section.
This types are available :

Type 100 - with 14 analog inputs
Typ 200 - with 28 analog inputs
See description in the next section.
1320

May 2011
3.1.1
Constructions
Overview concerning the different constructions :
Expert Key L the pop-up table-top device

Expert Key 100L and 200L are designed for table-top and wall-mounted usage. Mounting
brackets are included in the delivery. A pop-up detachable lid enables a clear overview of
connections. Sensors and actuators are connected via plugs located on the sides. The L
model has universal capability and is particularly suited to laboratory, servicing and testing
environments
Expert Key C for installation in control cabinets

Expert Key 100C and 200C are designed to be installed in cabinets or 19 rack systems.
Several devices can be mounted by the narrow construction form simply side by side.

May 2011
1321
Expert Key P the laboratory device with 4 mm plugs

The Expert Key 100P and 200P have a console design that uses plugs. They are intended
for use in testing and laboratory environments. Signals are connected to 4 mm safety lab
plugs. Measurement data from sensors can be transmitted to a PC via USB or LAN
interfaces. RTD sensors, voltage and current signals can be directly connected to any of
the analog inputs.
Expert Key M the mobile case

The Expert Key 100M and 200M are data acquisition systems in robust mobile cases for use
in tough environments. Measurement cables are fed through brush strips incorporated into
the case lid. Signal lines can be connected via 4 mm safety lab plugs or any other type of
plug or connector. Mobile measurement cases are available as either standard or custommade versions.
Expert Key T for multi-channel temperature measurement and more

Expert Key 100T and Expert Key 200T devices have console-type housings. They are
1322

May 2011
intended for use in laboratories and test stands as tabletop or wall-mounted devices. The
analog and digital inputs and outputs are easy to access and signals and actuators are
quick to connect requiring no tools. Universal analog inputs permit the direct connection of
RTDs, thermocouples and mVolt/mA signals. Each analog input is equipped with BNC and
thermo mini connectors to connect any type of thermocouple.

May 2011
1323
3.1.2
Types
Overview concerning number of inputs/outputs of the two device types :
Expert Key 100L

Expert Key 100C
Expert Key 100P
Expert Key 100M
Expert Key 100T
Expert Key 200L

Expert Key 200C
Expert Key 200P
Expert Key 200M
Expert Key 200T
Analog inputs
Number of
14
28
Power supply for RTD / Number
Yes / 4
Yes / 8
Temperature Reference Junction / Number of
Yes / 1
Yes / 2
12 to 8
Analog outputs
Number of
Digital inputs
Number of
thereof with counter function up to 1 MHz
thereof with counter function up to 10 kHz
10 to 6
1)
--
Digital outputs
Number of
thereof with PWM function
4 to 8
1) from Firmware V1.5 of June 2011
1324

May 2011
3.2
First steps
The First steps section provides information on start-up of device and PC software.
Standard delivery
Please check that the delivery is complete:
Construction L :
Device. Wall bracket. Power supply. USB cable. Shunt resistors 50
. Thermocouple.
Screwdriver. Introduction manuals (hard copy).
Construction C :
Device. USB cable. Shunt resistors 50
. Thermocouple. Screwdriver. Introduction manuals
(hard copy).
Construction P and T :
Device. Power cable. USB cable.
Bauform M :
Device. Wall bracket. Power supply. USB cable. Shunt resistors 50
. Thermocouple.
Screwdriver. Introduction manuals (hard copy).

Tablet computer - dependent on order and agreement.
Additional - for all constructions :

CD with program DataService and ProfiSignal, also driver for LabView(TM), DasyLab(TM),
Modbus TCP, OPC server, also all electronic manuals.

May 2011
1325
3.2.1
System requirements
operation of the Delphin products.
Operating System
Microsoft Windows XP 32-bit, Windows Vista and Windows 7 in the 32-bit- or 64-bit
versions,
either the English or German versions.
Main memory
At least 1024 MB*
Recommended: 2 ... 3 GB for 32-bit systems, 4 ... 8 GB for 64-bit-systems
Monitor
At least 1024 x 768 pixel, 96 dpi resolution
CPU
A PC with at least 1.6-GHz*
Recommended: Systems with dual or 4-core processors from 2.5 GHz or greater
Hard disk
for Pro fiSig nal-Go at least 70 MB of free hard disk space
for Pro fiSig nal-Vie we r at least 70 MB of free hard disk space
for Pro fiSig nal-Klicks at least 500 MB of free hard disk space
for other Pro fiSig nal-- versions at least 200 MB of free hard disk space
1326

May 2011
3.2.2
Software installation
Install the CD ProfiSignal Go. Please ensure that the DataService Configurator is installed
as a Program (and not as a Service).
Following installation from the CD of the program ProfiSignal Go the following icons will be
displayed:
The DataService Configurator is a device driver and tool for configuring the Expert device
(settings for sensor / actuator connections).
The ProfiSignal program provides evaluation and visualisation functions for measurement
data.
USB connection
To connect the Expert Key via the USB, the USB driver needs to be installed via Setup.
Select Setup USB driver for Expert devices. Connect the Expert Key device only after USB
driver installation has been performed at a PC.

May 2011
1327
1328

May 2011
3.2.3
Power supply / Switching device on
Construction L and M :
The device operates with an external supply voltage in the range of 9...24 VDC.
Use the AC/DC power supply as delivered!
Construction C :
The device operates with an external supply voltage in the range of 9...24 VDC.
Use an external AC/DC power supply or the supply voltage of cabinet (typ. 24 VDC).
The device operates with an external supply voltage of 230 VAC or 110 VAC.
Use the power line cable as diliverd.
The device is now ON. The blue Power LED lights.

After a few seconds the blue Run LED also lights.
Pulsation of one second the LED indicates that the device is operating normally.

May 2011
1329
3.2.4
Connecting
Cable connections to PC
Connecting device to PC.
Use either the supplied USB cable or network cable.
Create data link to device

Use the DataService Configurator program to create a data link to the device. Select
Connections.
1330

May 2011
1. USB connection
Info:
Ensure that the USB driver is installed before connecting device for the first time with a
USB cable. The USB driver is installed during installation from the ProfiSignal CD.
Connect the device to the PC using the USB cable.

Data connection now takes place automatically.
A successful USB connection will then appear as follows:
Tipp:
If the measurement values will further processed in software channels (with timesynchronized calculations), it is recommended to connect the device via USB to the PC.

May 2011
1331
2. LAN connection
The device is supplied ex-works with the fixed IP address of 192.168.251.252.
The service is also DHCP activated.
Info:
DHCP enables the automatic set up for a network participant. The new participant is then
automatically assigned an available IP address.
Connect the device to the PC using a network cable (crossover cable) or via a network hub
/ switch (1:1 cable).
Select the Connections tab in the DataService Configurator
Context menu
Add driver
(connection)
An available valid IP address is now assigned to the device by the (customer's) DHCPserver.
1332

May 2011
Select the device from
Found devices
The IP address can be input manually.

May 2011
1333
A successful LAN connection will then appear as follows:
1334

May 2011
3.3
Construction L
Handling
The use of this device is easy. All connections for the power supply , for interface to the
computer and for the sensors and actuator are directly accessible and marked. These
connections are described further below.
Power supply unit

The device operates with an external power supply with a voltage range of 9...24 VDC . A
reverse voltage protection is included. Maximum power dissipation is 6 W.
This power supply unit is suitable for power lines of either 230V/50Hz or 110V/60Hz.
The standard unit covers the European region. Versions are also available for other regions
with different connecting plugs.

May 2011
1335
3.3.1
Safety advice
The device's connections (also internal) are operated at a voltage of 50 VDC. This voltage
is categorized as safe for human handling.
Only the external power supply has a 230 VAC or 110 VAC connection. Use only the delivered
power supply connector with protective insulation.
The protective insulation is labelled as
1336

May 2011
3.3.2
Displays / LEDs
At the front:
Blue LED: Power

Permanently ON during normal operation. Indicates that the power supply (external supply)
is ON.
Blue LED: Run

ON in normal operation and pulsates at a rate of 1 s. Indicates that the processor is
operating normally.
Special situations:
The LED flashes at ca. 5 Hz during a firmware download / update.
Red LED: Error

Is OFF during normal operation. A short flash indicates a tolerable error has occurred. The
LED lights permanently when a serious error has occurred.

May 2011
1337
3.3.3
Connections
When the lid is opened, the following screw terminals are then accessible:
1338

May 2011
3.3.4
Connection schematic
Expert Key 100L

May 2011
1339
Expert Key 200L
1340

May 2011
3.4
Construction C
Handling
Power supply connector

The device operates with an external power supply with a voltage range of 9...24 VDC .
Usually here the cabinet supply voltage (typ. 24 VDC ) is connected.

May 2011
1341
3.4.1
Safety advice
The device's connections (also internal) are operated at a voltage of 50 VDC. This voltage
is categorized as safe for human handling.
Only the external power supply has a 230 VAC or 110 VAC connection.
Guide lines for grounding of device and power supply you will find here : Grounding
1342

May 2011
3.4.2
Displays / LEDs
Blue LED: Power

Permanently ON during normal operation. Indicates that the powers supply (via external
supply) is ON.
Blue LED: Run

ON in normal operation and gently pulsates at a rate of 1 s. Indicates that the processor is
operating normally.
Special situations:
The LED flashes at ca. 5 Hz during a firmware download / update.
Red LED: Error

Is OFF during normal operation. A short flash indicates a tolerable error has occurred. The
LED lights permanently when a serious error has occurred.

May 2011
1343
3.4.3
Connections
Front/Top/Bottom connections
1344

May 2011
3.4.4
Expert Key 100C

May 2011
1345
Expert Key 200C
1346

May 2011
3.5
Construction P
Handling
The handling is supported by the unique inscription. The naming of all inputs/outputs
corresponds to the construction form L and C. See previous sections.

May 2011
1347
3.5.1
Safety advice
Attention:
The device has front-sided a direct connection to the power line 230 VA C (or 110 VA C ).
Use the power line cable as delivered. The connector includes an ON/OFF switch. A safety
fuse is integrated and accessible.
1348

May 2011
3.5.2
Expert Key 100P

May 2011
1349
Expert Key 200P
1350

May 2011
3.6
Construction T
Handling
The handling is supported by the unique inscription. The naming of all inputs/outputs
corresponds to the construction form L and C. See previous sections.

May 2011
1351
3.6.1
Safety advice
Attention:
The device has front-sided a direct connection to the power line 230 VA C (or 110 VA C ).
Use the power line cable as delivered. The connector includes an ON/OFF switch. A safety
fuse is integrated and accessible.
1352

May 2011
3.6.2
Expert Key 200T

May 2011
1353
3.7
Function and Operation
Operating, general
Configuration of all connections and sensors takes place via the program DataService
Configurator.
Select the tab
Channels
1354

May 2011
View of all channels

May 2011
1355
3.7.1
Dialogue option / General
The operating elements are the same for all dialogues and are described here using Analog
Input as an example.
Select the tab
Main settings
1356

May 2011
Operating elements from the upper dialogue area:
Activates this channel. Transmission of measurement data from the device is now possible.
Enter a name here for the measuring point, e.g. Power1.
Enter the physical unit for this measuring point, e.g. N.
Enter a description (or commentary) of the measuring point, e.g. Pump 3.
Operating elements from the lower dialogue area:
Switches between previous / next channels, determined by channel number, and displays
the relevant dialogue.
Accepts all the new settings and transmits these to the device.
Closes the dialogue.
Ends the procedure. Closes the dialogue.
Runs Help i.e opens the electronic manual.

May 2011
1357
Select the tab
Advanced settings
Elements from the Advanced settings tab:
For inputs:
In the event of an input failure, the default value (instead of the measured value) is
For outputs:
In the event of an output failure, the default value (instead of the measured value) is
For PC-based data recording, this element is used for setting tolerance levels for recording.
In the example shown, a new measurement value is recorded only when there is a change
of more than 0.5 N over the previously recorded value.
For setting the required accuracy for the measurement or output value.
1358

May 2011
Select the tab
Sensor compensation
Elements from the Sensor compensation tab:
Activates sensor compensation, i.e. manual adjustment.
Select whether there are 1,2 or 3 calibration points.
Enter the calibration point (with Correct value and Measured value. The example shown
concerns temperature measurement with calibration at 0C and 100C.

May 2011
1359
3.7.2
Device
Properties
Select Properties from the device's context menu.
This opens the following window.
1360

May 2011
This dialogue enables users to make the required network settings. The default setting is
DHCP. The Expert Key connection then takes place automatically. If a DHCP server is not
being used, it is possible to manually input the IP address, net mask, gateway, host name
and domain settings.
Info:
When possible, use a fixed IP address for the device because, depending on the DHCP
being used, the IP address is only assigned for limited time periods.
This dialogue enables users to make the required settings to filter noise. Enter the network
frequency to activate the filter. The signals being measured by the analog inputs are
filtered by various methods depending on the sampling rate. Filtering is automatically
deactivated when dynamic signals (e.g. jump or fast oscillating sine) are detected at the
analog input.
Set filtering to Off for unfiltered signals.

May 2011
1361
This dialogue enables users to set the reference potential for differential inputs. This is
required when multiple sensors are connected and there is the possibility of significant
potential differences occurring between the reference masses of the sensor signals. Refer
also to the section on Measurement Technology\Potential differences.
"Off" setting
This is the recommended, factory setting. Select this option when there are no or very low
potential differences. This setting still has benefits for measurement. Low noise and low
crosstalk.
"On" setting
For significant potential differences that are known to occur or that are expected to occur.
Compensation then takes place for such potential differences. This applies to all analog
inputs.
Refer also to the section on Technical specifications\Analog inputs\Channel-to-channel
separation.
"Channel selectively" setting

For significant potential differences that are known to occur or that are expected to occur.
Compensation then takes place for such potential differences. This applies only to those
analog inputs that have been cross-checked.
Refer also to the section on Technical specifications\Analog inputs\Channel-to-channel

separation.
1362

May 2011
3.7.3
Analog input
Block diagram
The analog inputs are galvanically isolated as a group from the rest of the system as well
as from the PC.
Four dialogue options are available for the sensor type or electrical interface:
Voltage, e.g. 0...10 V
Current, e.g. 4...20 mA
Thermocouple, e.g. type K, NiCr-NiAl
Resistive probe, e.g. RTD Pt100
Info:
For information on connections refer to Connecting sensors.
Technical data is available under Analog inputs.

May 2011
1363
3.7.3.1 Dialogue option / Voltage sensor type
Descriptions for the general elements are available in the previous section.
The dialogue for the Voltage sensor type contains the following fields:
1364

May 2011
Select the sensor type or the relevant electrical interface as well as the subtype. The
options here are:
unipolar, i.e. positive signal only
bipolar, i. e. positive or negative signal
Select here the smallest (most negative) and largest (most positive) measurement range
appropriate to the sensor signal.
The options here are:
Measurement range 100 mV, 200 mV, 500 mV, ... up to 10,000 mV
Enter here the lower and upper reference points for the sensor's linear characteristics.
The example shown means that 0 mV corresponds to 0 N, and 1000 mV to 50 N.
The output range (in the example 0 to 50 N) serves also as the default settings for graphic
portrayals in ProfiSignal.
Select the sampling rate for this measuring point.

sampling frequency 0.2 Hz, 0.5 Hz, 1 Hz, ... up to 100,000 Hz
For slow-changing sensor signals, a low sample rate should be selected. This enhances
evening-out/filtering.
For periodic sensor signals that change very frequently, the sample rate should be 10 times
higher than the sensor signals. This enhances signal form and signal fidelity.
For all active analog inputs, it is recommended that you select sampling rates that do not
differ by more than 100:1 from one another. This will give consistent measurement
accuracy.

May 2011
1365
The sample rate shown here is the product of the highest sample rate set and the number
of active analog inputs.
3.7.3.2 Dialogue option / Current sensor type
1366

May 2011
The dialogue for the Current sensor type contains the following fields:
Select the sensor type or the relevant electrical interface.

Select also the subtype. The options here are:
unipolar, i.e. positive signal only
bipolar, i. e. positive or negative signal
Select here the smallest (most negative) and largest (most positive) measurement range
appropriate to the sensor signal. The options here are:
For unipolar: 0...20 mA, 4...20 mA, or an available range
For bipolar: 20 mA, or an available range
The example shown means that 4 mA corresponds to 0 N, and 20 mA to 50 N.
The output range (in the example 0 to 50 N) serves also as the default settings for graphic


May 2011
1367
accuracy.
The sum of set sample rates for all active analog inputs is shown here as a guide.
Function: Measuring current in any range

Current measurement is often required where any measurement range and any load
resistance can be set.
Example:
The motor current of a DC motor is to be measured in the 0...5 A range. A shunt resistor of
0.2 W is available.
1368

May 2011

May 2011
1369
3.7.3.3 Dialogue option / Resistor senor type
The dialogue for the Resistor sensor type contains the following fields:
Select the sensor type or the relevant electrical interface.
1370

May 2011
Select here the magnitude of resistance.

Info: The resistance to be measured should be greater than 10
k .
an must be less than 10
The example shown means that 0
sorresponds to 0 grad, and 1000
to 360 grad.
The output range (in the example 0...360 grad) serves also as the default settings for
graphic portrayals in ProfiSignal.

accuracy.
The sum of set sample rates for all active analog inputs is shown here as a guide.

May 2011
1371
3.7.3.4 Dialogue option / Thermocouple sensor type
The dialogue for the Thermocouple sensor type contains the following fields:
Select the sensor type or the relevant electrical interface. Select also the subtype. The
options here are:
Thermocouple type: B, C, E, J, K, L, N, R, S, T, U.
1372

May 2011
By selecting the thermocouple type, the measurement range is set. Only the physical
temperature unit can be selected here. The options are:
Celsius (C), Fahrenheit (F) or Kelvin (K)

Sampling frequency 0.2 Hz, 0.5 Hz, 1 Hz, ... up to 1000 Hz
accuracy.
The Total sample rate displayed here is the product of the highest set sample rate and the
number of active analog inputs.
Select the sensor compensationtab to achieve improved precision.

This concerns adjustment using 1 ... 3 calibration points.

May 2011
1373
3.7.3.5 Dialogue option / RTD sensor type
The dialogue for the resistance sensor contains the following fields:
Select the sensor type or the relevant electrical interface. Select also the subtype.
The options are:
Sensor types: Pt100, Pt200, Pt500, Pt1000
1374

May 2011
Selecting the type of sensor sets the measurement range. Only the physical temperature
unit can be selected here. The options here are:
Celsius (C), Fahrenheit (F) or Kelvin (K)

sampling frequency 0.2 Hz, 0.5 Hz, 1 Hz, ... up to 100 Hz
accuracy.
The Total sample rate displayed here is the product of the highest set sample rate and the
number of active analog inputs.
3.7.3.6 Sample rates and measurement accuracy

Due to the Expert Key having a common A/D converter, the sampling rate for all analog
inputs is therefore the analog input with highest sample rate setting.
The total sample rate is the product of the highest set sample rate and the number of
active analog inputs. Increasing sampling rate increases signal interference with
measurements becoming less accurate.
As a guide to the level of accuracy to be expected, sample rates are color classified:
Green. The sample rate is low enough to synchronize the measurement

with the network frequency. Signal interference will be kept to a minimum
and documented measurement accuracy will be maintained. This range is
especially suited to temperature measurements.

May 2011
1375
In highly electromagnetic environments, shielding of the connecting

cables is strongly recommended
Yellow. Connection cable shielding is generally recommended. The
documented measurement accuracy is maintained as far as possible.
For a higher accuracy, reduce the sample rate.
Red. Connection cable shielding is essential. Signal interference increases
and there are restrictions of the accuracy of measurement.
For a higher accuracy, reduce the sample rate.
Info:
Set the network frequency in your device's settings.
1376

May 2011
3.7.4
Digital input with counter function
Block diagram
The digital inputs are galvanically isolated, individually or in pairs, from the rest of the
system as well as from the PC. Frequency measuring, as well as counting, can also be
achieved. The counter (1 MHz type, DIN1 and DIN2) is resetable to real time accuracy.
The digital input with counter function provides the following three measurement channels:
Important hint:
Non-required measurement information should be deactivated. For example, when the
required measurement function is frequency measurement, then the two other channels
should be deactivated.
Info:
For information on connections refer to Connecting sensors.
Technical data is available under Digital input with counter function.

May 2011
1377
3.7.4.1 Dialogue option / Level detector
An explanation for Main settings is available in the previous section.
This option enables input signal inverting, i.e. High-level and Low-level are interchanged.
This option enables setting of the minimum pulse length (or maximum frequency) that can
be processed from the digital input.
Settings can range from 500 ns to 5 ms. This corresponds to frequencies from 1 MHz to
100 Hz.
Or settings can range from 50 s to 50 ms. This corresponds to frequencies from 10 kHz to
10 Hz.
1378

May 2011
The setting then prevents the registering or counting of the very short pulses or noise that
are not required.
3.7.4.2 Dialogue option / Counter
Enter here the lower and upper reference points for the sensor's linear characteristics. The

May 2011
1379
example shown is for the acquisition from an energy meter. The 0 impulse setting
corresponds to 0 kWh, and 1000 impulses corresponds to 100 kWh.
The output range (in the example 0 to 100 kWh) serves also as the default settings for
This sets a signal source for resetting the counter. The options here are:
None
Application: The source is a channel that is administered by the ProfiSignal software.
Channel: The source is a channel that is administered by the DataService software.
Channel (real time): The source is a set digital input from the device.
Only the selection of Channel (real-time) offers non-delayed resetting of the counter.
1380

May 2011
3.7.4.3 Dialogue option / Frequency measurement
Enter here the lower and upper reference points for the sensor's linear characteristics. The
example shown is for rotation acquisition. The 0 Hz setting corresponds to 0 U/min, and 50
Hz to 3000 U/min.
The output range (in the example 0...3000 U/min) serves also as the default settings for

May 2011
1381
1382

May 2011
3.7.5
Analog output
Block diagram
The analog outputs are galvanically isolated as a group from the rest of the system as well
as from the PC.
The signal driver has the following output range options:

Voltage: 0...10V or 10V
Current: 0...20mA, 4...20mA or 20mA
Info:
For information on connections refer to Connecting actuators.
Technical data is available under Analog outputs.

May 2011
1383
3.7.5.1 Dialogue option
Select the electrical signal:

Voltage
1384

May 2011
Current
For voltage: 0...10V or 10V

For current: 0...20mA, 4...20mA or 20mA
Select here the signal source that controls the output. The options here are:
Application
It is a channel that is administered by the ProfiSignal software.
Channel
It is a channel that is administered by the DataService software.
Manual value
It is a set value (manual value).
The Initial value is output as long as no valid output value is available (after switching on
the device).
Enter here the lower and upper reference points for the linear output characteristics.
The example shown is for monitor output at 4...20 mA. The settings have the following
meaning:
0 % corresponds to 4 mA, and 100 % to 20 mA.
The input range (in the example 0...100 %) serves also as the default settings for graphic
Info:
The displayed value in the DataService Configurator and ProfiSignal is the conversion
input range! The output range is measurable only at the terminals.

May 2011
1385
1386

May 2011
3.7.6
Digital output
Block diagram
The digital outputs are galvanically isolated, individually or in pairs, from the rest of the
system as well as from the PC.
Info:
Technical data is available under Digital outputs.

May 2011
1387
This option enables output signal inverting, i.e. High-level and Low-level are interchanged.
1388

May 2011
Select here the signal source that controls the output. The options here are:
Application
The source is a channel that is administered by the ProfiSignal software.
Channel
The source is a channel that is administered by the DataService software.
Manual value
The source is a set value (manual value).
The Initial value is output as long as no valid output value is available (after switching on
the device).

May 2011
1389
3.7.7
Digital output with PWM function
Block diagram
The digital outputs are galvanically isolated, individually or in pairs, from the rest of the
PWM signal generation functions with a preset base frequency. The duty cycle is
controlled.
1390

May 2011
Info:
Technical data is available under Digital output with PWM function.

May 2011
1391
A description for the general elements are available in the previous section.
Select the base frequency for the PWM signal.
1392

May 2011

Base frequency: 5 Hz, 10 Hz, 20 Hz, ...10,000 Hz
Select here the signal source that controls the output.

None
Application. The source is a channel that is administered by the ProfiSignal software.
Channel. The source is a channel that is administered by the DataService software.
Manual value. The source is a set value (manual value).
The Initial value is output as long as (after switching on the device) no valid output value
is available.
Enter here the lower and upper reference points for the linear output characteristics.
The example shown is for the activation of a required luminous power.
The settings have the following meaning:
0 lm corresponds to 0 %, and 500 lm to 100 %.
The input range (in the example 0...500 lm) is also the setting for the graphical portrayal in
ProfiSignal.
Info:
The display value in ProfiSignal and the DataService Configurator is the conversion
input range!

May 2011
1393
1394

May 2011
3.7.8
Device settings save and load
Saving a configuration
Select Save device settings from the device's context menu and save the entire settings
for the Expert Key device.
Loading a configuration
Select Load device settings from the device's context menu and load previously saved
channel settings for the Expert Key device.
The separate channels of the Expert device are identified in ProfiSignal by way of the
unique ID. If you load a saved configuration from device A into device B on the same PC,
the unique IDs will be automatically replaced.
Possible conflicts
If the same configuration is loaded from different PCs into multiple devices, the channels of
the multiple devices will have the same IDs. When you connect the devices to the same
PC, the channels of the last connected devices will not be displayed. When connecting
additional devices, you will receive a corresponding message in the Configurator.
To resolve this conflict, do the following:

With more than 2 devices, connect only 1 device at first and then carry out the
following steps per extra device.
If you have no saved configuration data on hand for the second device, firstly
connect the second device to the PC and save the configuration data from this
device.
Reset the second device's configuration.
Now connect both devices to the PC. Both devices are now connected, error-free, to
the PC.
Load the saved configuration into the second device. Unique IDs will then be assigned
automatically.

May 2011
1395
Info:
Note that only one configuration can be loaded from the same device type (100 or 200).
The construction (L, C P, M or T) is irrelevant.
1396

May 2011
3.7.9
Configuration reset
Resetting a configuration
Select Reset configuration from the connection's context menu to reset the current
settings. The configuration for all channels will then be reset to the settings as at
delivery.
The separate Expert device channels are identified in ProfiSignal by a unique ID. These IDs
are renamed during resetting.

May 2011
1397
3.7.10 Device information
Displaying
Select Show device informations from the device's context menu.
This opens the following window.
This provides an overview of useful information concerning your device. When you have
technical queries concerning your device, you should access this window to acquire
important information, e.g. the serial number or the firmware version.
1398

May 2011

May 2011
1399
3.7.11 Device firmware

Updating firmware
Select the tab
Connections
The following dialogue appears after clicking Update firmware from the context menu:
Click Select to select the file containing the new firmware. Commence update by clicking
Start update.
Important:
The device must NOT be switched off during the update (requires approx. 2 minutes)!
1400

May 2011
3.8
Connection information
3.8.1
Connecting sensors
This section uses examples to give advice on connections.
1. Sensor at the analog input / Voltage

Sensors with voltage signals can be connected directly.
Info:
The largest measurement range is 10 V.
The smallest measuring range is 100 mV.
2. Sensor at the analog input / Current, 20 mA

For sensors with current signals, a load resistor is intended for the input terminals. The
appropriate resistors can be supplied as accessories.

May 2011
1401
Info:
Load resistance must be in the range 10
to 500
3. Sensor at the analog input / Temperature, thermocouple

Thermocouple-temperature sensors can be connected directly.
Any normal type of thermocouple can be used.
Info:
The required reference junction is integrated in the device. Refer to TRJ measuring point.
4. Sensor at the analog input / Temperature, RTD

4-wire type RTD temperature sensors are recommended for connection.
The device offers several sources for constant current.
1402

May 2011
Info:
Constant current is at 0.2 mA.
The IREF1...4 constant current sources are assigned to the AIN1...4 analog inputs.
By series connecting 2...4 sensors enables users to connect a greater number of sensors
than available constant current sources. Sources IREF1...4 and IREF15...18 are then
assigned as follows to the analog inputs.
For types 100 and 200 :
Source
Analog input
IREF1
AIN1
AIN5
AIN9
AIN13
IREF2
AIN2
AIN6
AIN10
AIN14
IREF3
AIN3
AIN7
AIN11
IREF4
AIN4
AIN8
AIN12

May 2011
1403
For type 200:

Source
Analog input
IREF15
AIN15
AIN19
AIN23
AIN27
IREF16
AIN16
AIN20
AIN24
AIN28
IREF17
AIN17
AIN21
AIN25
IREF18
AIN18
AIN22
AIN26
5. Sensor at the digital input

The digital inputs offer beside the function "level-dectection" also the function "frequency
measurement" and "counting".
a) Level detection
1404

May 2011
Info:
The input signal should be a square signal.
The input signal must have an High-level in the range 5...50 V.
Maximum frequency is 10 kHz or 1 MHz.
b) Frequency measuring / counting
Info:
The input signal should be a right-angle signal.
The input signal must have an High-level in the 5...50 V range.
Maximum frequency is 10 kHz or 1 MHz.

May 2011
1405
3.8.2
Connecting actuators
This section uses examples to provide information on connections.
1. Actuator at the analog output

As an output signal, either a voltage signal (0...10 V or 10 V) or a current signal (0...20
mA, 4...20 mA or 20 mA) can be used.
Info:
For a voltage signal, the maximum current is 20 mA.
The output is controlled using an interconnected PC.
2. Actuator at the digital output / Resistive (ohmic) load

The digital output requires an external feed in the 5...50 VDC range.
The device contains an electronic switch (FET). There is a defined current flow direction
from terminal "++" to terminal "+".
a. 2-wire connection
b. 3-wire connection
1406

May 2011
Info:
For the 100 model, the 3-wire connection must be used for the DOUT5...8 outputs.
Maximum switching capacity is 30W. Maximum switching current is 1 A.
3. Actuator at the digital output / Inductive load

The digital output requires an external feed in the 5...50 VDC range.
The device contains an electronic switch (FET). There is a defined current flow direction
from terminal "++" to terminal "+".
a. 2-wire connection
Info:
An integrated inverse diode, external to the actuator (e.g. relay), is intended here.
b. 3-wire connection

May 2011
1407
Info:
An integrated inverse diode is used here (not shown in illustration).
A 3-wire connection is now also required.
1408

May 2011
3.9
Measurement technology
3.9.1
Galvanic isolation
All inputs/outputs are organized into groups. The groups are galvanically isolated from each
other, from the system and from the PC.
The table below shows which inputs/outputs are galvanically isolated from each other :
Each line of the Table marks a galvanic isolated area.
Typ 100
Typ 200
AIN 1..14
AIN 15..28
IREF 1..4
IREF 15..18
Analog inputs +
Constant current sources
AIN 1..14
IREF 1..4
Analog outputs
AOUT 1..2
AOUT 1..2
Digital inputs
DIN 1..2
DIN 1
DIN 3
DIN 4
DIN 5
DIN 6
DIN 7
DIN 8
DIN 9..10 /
DOUT 8..7
Digital inputs or outputs
DIN 11..12 /
DOUT 6..5
Digital outputs
DOUT 4..3
DOUT 1
DOUT 2..1

May 2011
1409
3.9.2
Grounding
Construction L :
The device is equipped with an earth clamp, labelled as PE, and has contact to the
aluminium cover plate.
This connector has no direct link to the 0VDC of the voltage supply.
The supplied power supply connector has protective insulation and therefore no earthing.
The device is equipped with an earth plug, labelled with a earthing smbol, and has contact
to the aluminium front panel.
This connector has no direct link to the 0VDC of the voltage supply. An earth connection
(2.5 mm) is required to create protective earthing (PE)
1410

May 2011

May 2011
1411
Construction form C :
The device is equipped with a dedicated earth connection in the form of a threaded pin on
the lower mounting tab. An earth connection (2.5 mm) is required to create protective
earthing (PE). There is also an earthing terminal, labelled PE, on the front of the device.
This is connected to the steel housing. This connector has no direct link to the 0V DC of
the voltage supply.
1412

May 2011
3.9.3
Ground Loop
Unwanted equalising currents occur when there are differing earth potentials in the cable
connections between sensor, measurement device and computer. These are known as earth
(or ground) loops and are shown as red in the graphic below.
Info: Avoid earth loops whenever possible!
Sensor-to-device earth loops

Galvanic isolation of the "anlog input" part of the circuit prevents earth loops occurring in
Expert Key devices as long as no additional earth connection has been made at the device.
Refer to the section: ESD protection
To prevent sensor-to-device earth loops, the use of potential-free sensors or potential-free
sensor signals is strongly recommended.
Device-to-computer earth loops
Shielded cabling is always used for USB connections. This is the default for the standard
high-speed USB 2.0.
The use of shielded cabling is required for LAN connections.
To avoid earth loops, only one of the two cable connections are permitted. The LAN
connection is recommended in environments where there is interference.

May 2011
1413
3.9.4
Shielding
The local environment may cause interference to measurement signals (e.g. through
electromagnetic fields, radio waves, etc.).
In such environments, shielded cabling should be used between the sensor and measurement
device. This is necessary to improve measurement precision and to obtain low-noise signals.
The shielding should have single-sided earthing to prevent equalising currents from occurring.
a) Sensors with no earth

Normal cases: The shielding has single-sided earthing directly prior the device.
Special cases: Single-sided earthing at the device via the "IREF-" terminal.
1414

May 2011
b) Sensors with earth

Use of potential-free sensors or potential-free sensor signals is strongly recommended. Even
when an earthed sensor is used, the shielding is still to be earthed as shown:

May 2011
1415
3.9.5
ESD-Protection
To obtain ESD protection for the analog inputs, earth the "IREF-" terminal. This terminal is
connected to the internal analog earth point.
Note:
With construction form L earthing is performed with
2 terminals (35/38) for device type 100, or with
4 terminals (35/38/75/78) for device type 200.
1416

May 2011
3.9.6
Potential differences may occur between multiple sensors or between sensor-signal

reference masses. The image below shows these as VPD.
All analog inputs (differential inputs) have a common but floating analog mass. In this way,
the device can adjust to differing sensor-signal reference masses (when changing
channels).
Limits are to be adhered to for the permitted potential difference.

Refer to the section on Technical specifications\Analog inputs\Channel-to-channel
separation.
If potential differences occur, or are expected to occur, options are available to make the
necessary settings. Refer to the Function and Operation\Device section.

May 2011
1417
3.10
Device synchronization
Multiple devices can be time-synchronized for the transmission of measurement data. Also
devices of different type (100 or 200).
A digital reference signal is output from one of the devices and simultaneously received by
all participating devices. The time-synchronization of the measurement data then takes
place at a PC.
Wiring
Wiring example for two devices Expert Key 100L :
Wiring example for two devices Expert Key 200L :
1418

May 2011
Configuration
For device-to-device synchronization, one digital output and one digital input are used.
These connections are then no longer available for general use.
Configuration example with Expert Key 100L :

May 2011
1419
Refer also to the Synchronization section under technical data.
Info:
It is recommended that the device is connected to the PC with a highspeed USB. Avoid
running other hardware (e.g. hard disk) from the same USB host controller. Because of
possible delays within the network, LAN synchronization can not be guaranteed.
1420

May 2011
3.11 Technical specifications

Power supply
Voltage range:
9...24 VDC +-15%
Max. power dissipation of the device:

6W
Reverse polarity protection:

Yes

May 2011
1421
3.11.1 Analog input
Sampling rate (throughput)

Max. 100,000 Hz, when all analog inputs are set to "Voltage" or "Current" sensor type.
Max 10,000 Hz, when at least one analog input is set to "Resistor" or "Thermocouple" or
"RTD" sensor type.
Max. 1000 Hz, when at least one analog input is set to the option "Reference for
differential inputs".
Total sampling rate

Settings range from 0.2 Hz to 100,000 Hz for "Voltage" sensor type.
Settings range from 0.2 Hz to 100,000 Hz for "Current" sensor type.
Settings range from 0.2 Hz to 1000 Hz for "Thermocouple" sensor type.
Reduces by a max. of 100 Hz when the option "Reference for differential inputs" is enabled.
Settings range from 0.2 Hz to 100 Hz, for "RTD" sensor type.
Measurement range, voltage:

10 V
or
0...10 V
5 V
or
0...5 V
2 V
or
0...2 V
1 V
or
0...1 V
500 mV
or
0...500 mV
200 mV
or
0...200 mV
100 mV
or
0...100 mV
Measurement range, current:

0...20 mA or 4...20 mA or available value
Possible load resistance:
10/20/50...500
or available value
A/D converter resolution:

18 bit
1422

May 2011
Measurement
range
Resolution
10 V
76 V
5 V
38 V
2 V
19 V
1 V
9.5 V
500 mV
4.7 V
200 mV
2.4 V
100 mV
1.2 V
Input impedance:
2M
Input protection against permanent voltage surge:

40 V
Channel-to-channel separation
Permitted potential differences between the reference masses of different sensors for total
sampling rate < 1000 Hz
Standard :
3...30 V, depending on the sampling rate
Extended:
40 V, if option "Reference for differential inputs" is activated
ESD-input protection:
Yes
Max. sensor-impedance:
1k
Galvanic isolation:
All analog inputs (including constant current sources) are galvanically isolated as group.
To the rest of the system as well as to the PC.
With an isolation voltage of up to 1,000 VDC .
Operating type/ sampling procedure:

May 2011
1423
Each individual analog input can be active or inactive.

All active analog inputs are sequentially and continuously sampled.
An automatic oversampling averages / evens-out the measurement values.
Measurement accuracy, voltage:

Measurement range
Measurement accuracy
10 V
0.02 %
2 mV
5 V
0.05 %
2.5 mV
2 V
0.05 %
1 mV
1 V
0.1 %
1 mV
500 mV
0.1 %
0.5 mV
200 mV
0.2 %
0.4 mV
100 mV
0.2 %
0.2 mV
Table applies to 14/28 active analog-inputs each with a sample rate of 1Hz/2Hz.
DC-signal. 25C ambient temperature.
Measurement accuracy in % of positive end value of the measurement range.
Measurement accuracy, current:

Measurement range
0...20 mA
0.05 %
0.01 mA
4...20 mA
0.05 %
0.01 mA
DC signal. Load resistance with 0,05% tolerance. 25C ambient temperature.
Measurement accuracy in % of the positive end value of measurement range.
Measurement accuracy, Resistant:

Measurement
range
10
0,05 %
0,25
1K
0,1 %
to 2,5 K
0,1 %
500
to
1424

May 2011
5K
0,2 %
to 10 K
0,5 %
10
to
DC-signal. 25C ambient temperature.
Measurement accuracy in % of positive end value of the measurement range.
Measurement accuracy, temperature, RTD:

Type
Measurement
range
Pt100
-260...849 C
0,03 %
0,25 C
Pt1000
-260...400 C
0,15 %
1,3 C
...550 C
0,25 %
2,1 C
...850 C
0,5 %
4,3 C
Table applies to 14/28 active analog inputs each with a sampling rate of 1Hz/2Hz.
4-wire connection. 25C ambient temperature.
Measurement accuracy in % of the positive end value.
Measurement accuracy, temperature, thermocouple:

Type
Measurement range
R / Pt13Rh-Pt
- 50...1.767 C
0.2 %
3.5 C
K / NiCr-NiAl
-270...1.372 C
0.2 %
2.7 C
J / Fe-CuNi
-210...1.200 C
0.2 %
2.4 C
E / NiCr-CuNi
-270...1.000 C
0.2 %
2.0 C
Internal compensation measuring point. 25C ambient temperature. Warm-up time > 45 min.
Measurement accuracy in % of the positive end value of the measurement range - following sensor
compensation procedure.
Power supply for RTD:

Constant 0.2 mA.

May 2011
1425
Compensation measuring point for thermocouple:

An additional sensor (RTD type PT100 using 4-wire-technology) is internally attached at
the screw terminals.
1426

May 2011
3.11.2 Digital input with counter function up to 1 MHz

Max. input frequency for the counter:
1 MHz
Time resolution:
1 s
Counter width, hardware / software:
32 bit / 64 bit
Reset function for counter:

Yes
Low level:
0 1,5V / 0 1,5mA
High level:
5 90V / 3,5mA
Measurement range of frequency measurement:

0.1 Hz to 1 MHz
Accuracy of frequency measurement:

max. 0.01 % of input frequency
Digital debouncing
Range of settings for the minimum pulse length: 500 ns to 5 ms (1 MHz to 100 Hz)
All level changes (according to High or Low) are transferred as measurement values.
The counter status is updated at 10 measurement values/s.
Frequency measurement is performed via a PC.
Sum of input frequency for transmitted level-change for all active digital inputs:
10 kHz

May 2011
1427
Galvanic isolation:
All digital inputs with counter function are galvanically isolated in pairs - to the rest of the
system and to the PC.
With an isolation voltage of up to 1000 VDC .
1428

May 2011
3.11.3 Digital input with counter function up to 10 kHz

Max. input frequency:
10 kHz
Time resolution:
100 s
Counter width, hardware / software:
32 bit / 64 bit
Reset function for counter:

No
Low level:
0 1,5V / 0 1,5mA
High level:
3,5 90V / 2mA (typ. 2,7mA @ 5V)
Digital debouncing
Range of settings for the minimum pulse length: 50 s to 50 ms (10 kHz to 10 Hz)

All level changes (according to High or Low) are transferred as measurement values.
Sum of input frequency for transmitted level-change for all active digital inputs:
10 kHz
Galvanic isolation:
All digital inputs have separate galvanic isolation - from the rest of the system as well as
from the PC.

May 2011
1429
3.11.4 Analog output

D/A converter resolution:
16 bit
Output type and range:

Voltage:
0...10 V or 10 V
Current:
0...20 mA or 4...20 mA or 20 mA
Switching:
Software/automated selection of voltage/current mode
Mode of operation:
Output values are always managed from the PC. The output returns to ca. 0 V and 0 mA
when disconnecting the USB or LAN. The output is undefined for a period of 20s when
restarting the device.
Possible load resistance:

50 ... 500
Max. output rate per analog output :

50 Hz
Galvanic isolation:
All analog inputs have galvanic isolation to the rest of the system and to the PC.
Accuracy:
Range
Accuracy
0...10 V, 10 V
0.05 %
5 mV
0/4...20 mA, 10 mA
0.05 %
0.01 mA
Table applies to a 25 C ambient temperature.

Accuracy in % of unipolar measurement range.
1430

May 2011
3.11.5 Digital output

Max. switching delay:
0.5 ms
Max. permanent switching frequency:

10 Hz
Max. switching capacity:

30 W
Max. switching voltage and current:

30 V / 1 A
40 V / 0.75 A
50 V / 0.6 A
Mode of operation:
Output values are always managed from the PC. The output switches to OFF (open
contact) when disconnecting the USB or LAN.
Inverse diode:
Integrated, max. 2 A
Galvanic isolation:
All digital outputs have separate galvanic isolation - from the rest of the system as well as
from the PC.

May 2011
1431
3.11.6 Digital output with PWM function

PWM-basic frequency and duty cycle resolution:
10,000Hz / 1:100
5,000Hz / 1:200
2,000 Hz / 1:500
1,000 Hz / 1:500
...
10 Hz / 1:500
5 Hz / 1:500
Max. switching capacity:

30 W
Max. switching voltage and current:

30 V / 1 A
40 V / 0.75 A
50 V / 0.6 A
Inverse diode:
Integrated, max. 2 A
Max. output rate per digital output :

10 Hz
Mode of operation:
Output values are always managed from the PC. The output switches to OFF (open
contact) when disconnecting the USB or LAN.
Galvanic isolation:
All digital outputs with PWM function are galvanically isolated in pairs - from the rest of the
1432

May 2011

May 2011
1433
3.11.7 Synchronization
Synchronizing multiple devices
Max. number of devices:

4
Synchronization signal:
Right-angle, 2 Hz
Synchronization accuracy:
10 s
1434

May 2011
3.11.8 Device specification
Microprocessor, FPGA, Memory

Microprocessor:
50..80 MHz, 32 bit
FPGA:
Xilinx, Spartan family
Memory:
Volatile: SDRAM, 32 MByte
Non-volatile: Flash-EPROM, 2...8 MByte
USB port
Standard:
USB 2.0
Transmission speed:
High Speed, up to 480MBit/s,
or Full Speed, 12MBit/s, with limited functionality
Max. cable length:

5m
Driver type and operation:

Transmission mode is Bulk
USB-port:
Typ B, standard

May 2011
1435
LAN/Network interface
Transmission standard:
10Base-T
Transmission speed:
10 or 100 MBit/s
Max. cable length:

100 m
Sensor / actuator connection

Max. cable length to sensors and actuators:
5m
Physical
Device dimensions:
Construction L : 50 x 185 x 215 mm
Construction C : 280 x 57 x 208 mm
Construction P and T : 307 x 495 x 138 mm
Device weight:
Construction L : 750 g
Construction C : 1.5 kg
Signal cable diameter for connecting terminals:

0.14 to 2.5 mm
1436

May 2011
Environment
Environmental compatibility:
Electronics conform to RoHS directives.
Environmental conditions
Permitted humidity
10 .. 80 % relative humidity, not to precipitated
Permissible ambient temperature:
-20 .. 60 C

May 2011
1437
3.12
FAQ
USB connection
Several connected devices appear in the DataService Configurator. How do I know which
device is mine?
Open the device's context menu and click on "Device information". This displays the serial
number of the device. This number is also on the device.
Analog inputs
Why does a measurement value appear in the DataService Configurator even when no
sensor is connected?.
Ignore the measurement value or disable the unused analog input.
The DataService Configurator displays a clearly erroneous measurement value.What could

be causing this?
Check the connection between the sensor and device. If necessary, test the sensor's
voltage supply.
There may be a significant potential difference between the reference masses of multiple
sensors. In this event, enable the option "Reference for differential inputs" in the device's
main settings.
1438

May 2011
3.13
EC declaration of conformity

May 2011
1439
3.14
Revision history

Expert Key 100/200.
Optimization and error correction concerning LAN communication and TCP/IP protocol.
Support for the construction form "Expert Key 200T".

Expert Key 100. Expansion from 2 to 12..8 digital inputs with counter function.
2011-03 / ProfiSignal-CD V3.0.8 / Firmware V1.4.6.2

Expert Key 100. New. Adjustable digital debounce for DIN3..12
Expert Key 100. New. Sensor type Resistor for resistance measurement.
2011-02 / ProfiSignal-CD V3.0.6 / Firmware V1.4.5

analog switch.
analog switch.
MetiOS-Devices
1440

May 2011
4.1
Log-/ProfiMessage
Log-/ProfiMessage devices are designed for use as modular measurement, control, and
monitoring devices and are equipped with many settings and connection options. They are
also equipped with a range of I/O modules, field bus interfaces, and software channels to
enable the performance of monitoring, control, and regulation tasks. Log-/ProfiMessage
devices have 16GB internal memories and can function as stand alone, independent units.
Acquired data can be transferred via interfaces in runtime mode, via time-controlled
events, or via the device's USB ports.
Copyright 2003-2013 Delphin Technology AG. All rights reserved.

This document's content, especially text, images, and graphics are protected by copyright.
When not otherwise stated, the copyright belongs to Delphin Technology AG, Lustheide 81,
in 51427 Bergisch Gladbach, Germany.
All the trademarks and brands used in this manual refer only to the respective product or
trademark holder. Delphin Technology claims no rights other than those to its own
trademarks and brands.

May 2011
1441
4.1.1
Safety Advice
WARNING!
Connector terminals on I/O modules carry electrical potential from the attached
sensors/actuators.
Before coming into contact with the connectors, ensure the power is off. There
should be no voltage at the connector terminals when the attached sensors
have varying potentials or earthed high potentials, e.g. when measuring the
electrical current of a mains voltage phase.
Differences in electrical potential between two channels of a module can not be
determined from the Measurement data.
Refer to Potential differences.
I/O module, memory card, battery installation installation/replacement
Electronic components are sensitive to ESD (Electro-Static Discharge). Therefore,

discharge any electrostatic energy before opening the device for I/O module or memory
card installation/replacement. We recommend wearing a wrist band (static discharge wrist
band) and to carry out the work on a conductive surface.
ESD damage can have varying consequences from minor deviations in data recording
through to full system failure.
1442

May 2011
4.1.2
Introduction
Dear User,
Thank you for purchasing a device from the Log-/ProfiMessage series. You have acquired a
high quality product with extensive options for data acquisition and processing.
This manual is included in the delivery. Always keep the manual available for reference. To
avoid any damage occurring to yourself or your equipment, carefully follow the guidance
and safety precautions given in this manual. If your equipment has a problem that this
manual does not address, please contact us.
This manual is intended for technicians and engineers or similarly qualified persons wishing
to use the device. If you find errors in the product or in this documentation, or if you have
any suggestions for its improvement, we welcome your feedback.
Contact:
Lustheide 81
Telephone: +49 2204 97685-0
Telefax: +49 2204 97685 -85
Internet: www.delphin.de
Contact USA:
Delphin Technology Corp.
4860 Cox Road, Suite 2000
Glen Allen, VA 23660
Virginia, USA
Telephone: +1 804 217 8391
Telefax: +1 804 747 6182
Email: info@delphin.com
Internet: www.delphin.com
4.1.2.1 Included in delivery

Included in delivery:
Log-/ProfiMessage device
Three-pin connector with 120-ohm resistor (for connection of slave devices via Ext.
BUS. Only available in ProfiMessage devices!)
Brackets for rail mountings
Ethernet cross-cable
RS-232 connection cable with D-SUB DB9 connectors

May 2011
1443
CD containing ProfiSignal software

Documentation
The devices can be equipped with various I / O modules.
For measurement systems with high channel numbers, a ProfiMessage master device can be
extended using slave devices.A LogMessage device cannot be extended.
Available I / O modules:
ADFT:
8 analog inputs for V, mV, 20mA
2 frequency or counter inputs
2 digital inputs
2 analog outputs 10V
4 digital outputs
ADGT V2.0:
8 analog inputs for V, mV, 20mA, Pt100, thermocouples
ADGT V3.0:
ADIT:
1 analog output 20mA
1 digital output
ADVT:
15 analog inputs for V, mV, 20mA, thermocouples
DIOT:
11 frequency or counter inputs
1 digital input
16 digital outputs
IOIT:
24 digital inputs
1 digital output
4.1.2.2 System requirements

Operating system
Main memory
at least 2 GB*,
Monitor
CPU
1444

May 2011
Hard drive
4.1.2.3 Symbols used in this documentation

To make reading of this manual easier, we have used the following symbols:
WARNING!
This symbol warns of a potential hazard which - if the safety requirements are
not followed - may be fatal or cause serious physical injury.
Indicates important information.
Info
Refers to a special option or explains a special feature.
We use italics to highlight individual words within the text. Keyboard input is highlighted in
this way. Program menus have a grey background with arrows indicating the respective
sub-menus which need to be accessed: Connect
Add driver (connection) Log-/ProfiMessage
device. Also highlighted in grey and displayed in italics are the dialog headings, buttons,
check boxes, input field names, etc. Display status.
This should help you to find the relevant fields and buttons or menus within the
corresponding software.
Symbols on the device
Symbol

May 2011
1445
CE symbol:The CE symbol guarantees that our products meet the requirements of relevant
EU directives. Refer also to the EC Declaration of Conformity section.
1446

May 2011
4.1.3
Getting started
This section explains:

The important device connections to commence work.
The software that needs to be installed on your PC.
How to establish a connection between a PC and the device.
The settings required to acquire measurement signals from the device.
For detailed information refer to these sections:
The section Display devices and connections gives an overview of all the interfaces/
connections/ports and LEDs.
The section Configuration and operation explains the different options for setting up
the device for measurement tasks.
The section on Examples of connections shows the options for connecting standard
sensors and actuators and how to configure them.
The section on Measurement technology contains general information and
recommendations on using measurement technology.
Technical data is available in the Technical specifications section.
4.1.3.1 Starting Log-/ProfiMessage

Just a few steps are required to start using the Log-/ProfiMessage device:
Unpack the device.
Plug the three-pinned, grey plug from the supplied AC adapter into the socket marked
"Power" on the device.
Refer also to Display devices and connections. The plug is polarity-protected can be
inserted into the socket in only one way.
Plug the supplied three-pinned grey connector for the external bus terminal in the
socket marked " Ext. BUS.
The terminal possesses a resistor that is necessary for the proper functioning of the
bus system. The resistor is required even when a bus (cable) is not connected.
Connect the power adapter into the mains socket.
The next steps are:

Installing programs
PC connection
Basic settings

May 2011
1447
4.1.3.2 Installing programs
Administrator rights are required to install the programs.
Install the CD ProfiSignal Go. Please ensure that the DataService Configurator is installed
as a Program (and not as a Service).
Following installation, these two desktop icons should appear:
The DataService Configurator from Delphin functions as a link between the PC and
measurement hardware.
Delphin hardware is configured using DataService Configurator. Lo g -/ Pro fiMe ssag e
devices are immediately configured in the DataSe rv ice Co nfig urato r.
The ProfiSignal program provides evaluation and visualisation functions for measurement
data.
4.1.3.3 PC connection
Preparing the PC
The factory setting of the IP address is printed on a sticker on the device. If the sticker is
lost, the please try the IP address 192.168.251.252 (Net mask: 255.255.240.0)
To be able to establish a connection using this address, the PC must be temporarily set to
a different address within the same IP segment:
1.Run the network connection dialog.
2.Depending on the operating system being used, the the dialog can be accessed from
either the Windows Start button and Network settings or via the Control Panel,
Network and Sharing Center.
3.Display the Properties of the connection to which the device is to connect (usually
labelled Local Area Connection). In Windows Vista, click Status , then Properties .
4.Display the Properties for the internet protocol.
1448

May 2011
5.In the next dialog you can set either a fixed address for your PC, or - if the PC is set
to DHCP and used in the LAN - use the option of an alternative configuration to
prepare for cases where no network (server) is available (recommended).
6.Enter an address that falls within the same segment as the address of the device
(refer to above example). Windows automatically adds the subnet mask.
7.Close all dialogs by clicking OK .
Establishing a cable connection
Connect the PC and the device using the supplied Ethernet cable.

May 2011
1449
The connection between the device and PC can also be made via a network hub or
switch.
Establishing a device connection and setting an alternative network address
If a different IP address is required, e.g. to operate the device within a LAN, this can be
performed using any internet browser. Go to the next section if a change of IP address is
not required.
1.Open the internet browser and enter the address http://192.168.251.252 .
A connection is established to the device and the start page is displayed.
2.In the Settings section, click Network .
This displays the network settings page.
3.Enter the address required for your network at IP Address. The subnet mask and
gateway, or DNS and NTP server can also be entered (refer to web browser
configuration)
4.Click Save when finished to store the settings.
The Log-/ProfiMessage device can now be connected to your network. If the PC again
requires reconnecting to the device, you may need to set it to the new IP Segment (the
first group of three digits).
Establishing a connection to the device
1.Start the DataService Configurator to establish a connection and to carry out
configuration.
The DataService is starts and the Connections tab is displayed on the left of the
2.Select Connect
Add driver (connection) Log-/ProfiMessage device. Alternatively, a Log-/
ProfiMessage device driver can be added by right-clicking DataService ... .
3.A device search is performed and a dialog displayed with the found device or devices.
4.Double-click the the address of the required device. If no device is found, use the
General tab to manually enter the address.
Change the port only when the Windows firewall is not being used and/or other ports
have been configured within the firewall.
5.Confirm the settings with Connect: Always (default). Connection is then automatic
when starting the DataService Configurator.
1450

May 2011
A successful connection is then displayed with an IP address and a status. The

DataService record displays the host name or the address of the PC.
4.1.3.4 Unknown IP address?

If an IP address has been amended and then forgotten, the new address can be
determined via a connection to the serial interface. Requirements:
A Null modem cable (crossover serial cable, D-SUB DB9 connector coupling to D-SUB
DB9 connector coupling that is included the delivery).
A terminal program such as Windows HyperTerminal or PuTTY.
Info
Putty can be downloaded using the device's Service option and via the web
interface (when connected).
Method
1.Connect the RS-232 port of your PC to the COM4 port of the device using the null
modem cable.
2.Set your terminal program to 115200 baud transmission speed , 8 data bits , no parity and 1
stop bit (8N1), and No handshake.
3.Enter the user name root .
4.Enter ifconfig .
The current IP address and subnet mask settings for the device are then shown in the
second line of the output (underlined in red in the following example):

May 2011
1451
To change the IP address or subnet mask, you must first set your PC address to an
address in the same segment and then connect the PC to the device via Ethernet. Refer
to PC Connection. This section also explains how to amend the device's IP address.
4.1.3.5 Basic settings

The DataService Configurator dialog is split enabling a device to be selected on the left
under Connections and settings to be made on the right under Channels .
Displaying measurement data

Once a connection has been established (refer to the previous section ) current
measurement data can then be displayed. Double-click on an I/O module to displays its
channels. The Value column continuously updates with new measurement data.
Displaying scaled measurement data
To convert data from the sensor into the required measurement unit requires configuration
of the channel. Right click a channel to display the Properties dialog. A general explanation
of dialogs is available under settings for all dialogs section. Special settings for different
channel types (analog input, analog output) can be found in subsections of the configuring
module channels section. The dialog also displays connection diagrams (refer to I/O module
connections ).
1452

May 2011
Other settings
Setting digital I/O
Scaling can also be made for counter inputs. Set which signal (channel) requires
output of a constant level.
Settings for data reduction, A/D measurement duration, etc.
A number of options are available other than basic scaling, e.g. duration of an A/D
conversion, the change required for a new measured value to be stored (data
reduction), or how the channel is to be monitored.
Specific settings for a device
Options are available for system monitoring, e.g. CPU utilization or the available
memory, and interface configurations.
Calculation channels (subordinate channels)
ProfiSignal devices are capable of processing data before it is saved and output. The
corresponding settings are described in configuring software channels.

May 2011
1453
4.1.4
Log-/ProfiMessage device and connections
ProfiMessage device:
LogMessage device:
Function keys are not currently enabled.

Connections are described in the following sections:
Power supply
LEDs, LAN, USB
General LEDs
COM interfaces
I/O module connections (terminal blocks)
Connecting slave devices
Also in this section:
I/O module installation and removal
Internal memory card installation and upgrade
Internal battery installation
Refer also to Device restart (reboot)
1454

May 2011
4.1.4.1 Device types

The various devices types are equipped with one or two I/O modules. The connection
diagrams are in the following chapters.
Types
LM
LM
LM
LM
LM
1000
2000
3000
4000
5000
Analog inputs (mV, mA)

Analog inputs (mV, mA,
Thermocouples)
8
15
15

Thermocouples, Pt100(0))
10
16
Analog outputs (mV, mA)
Digital inputs (frequency

measurements)
12
(11)
24
28 (2)
Digital inputs (mV)
17
Sampling rate in measurements per

second
600
600
600
10000
80
Galvanic isolation AI to AI ( V DC)
110
110
110
100
650
Module 1
ADVT
DIOT
ADVT
ADFT
ADGT
ADIT
IOIT
IOIT
ADGT
Module 2
Types
LM 6000
LM
LM
LM
7000
8000
9000
30
15
Analog inputs (mV, mA)

Thermocouples)
15

Thermocouples, Pt100(0))
10
20
Analog outputs (mV, mA)
2
12 (11)
Digital inputs (frequency

measurements)
Digital inputs (mV)
Sampling rate in measurements per

second
1200
Galvanic isolation AI to AI ( V DC)
110

May 2011
16
1200
600
1200
110
110
110
1455
Types
LM 6000
LM
LM
LM
7000
8000
9000
Module 1
ADVT
ADVT
ADVT
ADIT
Module 2
ADIT
ADVT
DIOT
ADIT
4.1.4.2 Power supply
Input voltage: 12 ... 28 VAC 10% / 12 ... 36 V DC 10%
Info
If the device is equipped with the I/O module AMDT or ADFT the minimum
input voltage is 18 VA C / DC
Power input Pmax : 10 W

Pin assignment
Pin
Label
Description
Left
24V
Power supply
Middle
0V
Neutral
Right
PE
Protective Earth , refer to

earthing
1456

May 2011
4.1.4.3 LED lamps, LAN, USB
LED
Right
Left
Status
Description
Off
Not connected
Green, non-flashing
Connected, data not being

transferred
Green, flashing
Data transfer
Off
Half duplex
Orange, non-flashing
Full duplex
Orange, flashing
Collision

May 2011
1457
4.1.4.4 General LEDs
LED descriptions
Compon
Number
ents
of LEDs
Power
Status
Mod. 1
Status
Description
green
Hardware failure, e.g. the device connected to the

USB port requires too much power
orange
Power supply OK
red /
green
Multifunctional display
green
Status of I/O module
Flashing green: Module OK

Flashing orange: Main program has ended (no data
acquisition / processing)
Permanent: normal functioning

Slow flashing: BUS identification
For ADFT / AMDT:
Slow flashing: new firmware being saved
Fast flashing: firmware being downloaded
Mod. 2
Ext. BUS
CAN
Battery
green
Status of I/O module
green
RxD
orange
TxD
green
RxD
orange
TxD
red
Battery failure / battery low
The battery for the clock and emergency data

backup is flat and must be replaced. Refer to
Internal battery replacement
MEM
COM1
green
Access to the internal memory
green
RxD
orange
TxD
1458

May 2011
Compon
Number
ents
of LEDs
COM2
COM3
COM4
Status
Description
green
RxD
orange
TxD
green
RxD
orange
TxD
green
RxD
orange
TxD
4.1.4.5 COM interfaces, CAN
COM1/CAN
Pin assignment 9-pin D-SUB connector

Pin
Signal
Description CAN (CiA
(IEC 61158)
DS102-1)
Housi
ng
Shield
Shield
Shield / protective ground, refer

to earthing
CANL
CAN-Bus Low
RxD/TxDP/B
Receive/transmit data-Plus (RS485)
RTS
Control signal for repeaters (TTL)
GND / C
Data reference potential /

neutral

May 2011
Description COM1 RS-485
Shield / protective ground, refer to earthing
1459
VP
Supply voltage / Plus (5V)
CANH
CAN-Bus High
RxD/TxDN/ A
Receive/transmit data-Negative
(RS-485)
Not connected
Info
Galvanic isolation does not exist between CAN and COM1.
COM2/COM3

Pin
Signal
Description COM2 RS-485 (IEC
Description COM3 RS-
61158)
232
Housi
ng
Shield
Shield
RxD
Receive data (RS-232)
RxD/TxDP/B
Receive/transmit data-Plus (RS485)
RTS
Control signal for repeaters (TTL)
GND / C
VP
RTS
RxD/TxDN/ A
Receive/transmit data-Negative
(RS-485)
Data reference potential / neutral

Supply voltage / Plus (5V)
Request to Send (RS232)
1460

May 2011
TxD
Transmit data (RS-232)
Info
Galvanic isolation does not exist between COM2 and COM3.
COM4

Pin
Signal
Description DIN 41 652, Teil 1 (ISO 4902)
Housing
Shield
DCD
Data Carrier Detect (RS-232)
RxD
Receive Data (RS-232)
TxD
Transmit Data (RS-232)
DTR
Data terminal ready (RS-232)
GND
Signal ground
Not connected
RTS
Request to Send (RS-232)
CTS
Clear to Send (RS-232)
Not connected
4.1.4.6 I/O module connections (terminal blocks)

Devices can be equipped with different modules. Below are the the wiring diagrams/terminal
assignments for the various I/O modules (in alphabetical order).

May 2011
1461
AAST
ADFT
For technical reasons, only one ADFT module per system can be used.
1462

May 2011
ADGT
Info
Versions 1.0 and 2.0 of the ADGT modules have mechanical switches
that enable cyclical selection of individual channels. A light ticking is
therefore audible during operation.

May 2011
1463
ADIT
ADVT
AMDT
1464

May 2011
DIOT

May 2011
1465
IOIT
OTPT
1466

May 2011
4.1.4.7 I/O module installation and removal
Electronic components are sensitive to ESD (Electro-Static

Discharge). Therefore, discharge any electrostatic energy
before opening the device to install an I/O module or
memory card. We recommend wearing a wrist band (static
discharge wrist band) and to carry out the work on a
conductive surface.
Removal
1.Disconnect the unit from the mains voltage supply.
2.Remove all plug-in connectors from the device front.
When replacing one module with a similar module, leave the cables attached to the
terminal blocks.
3.Unscrew the four locking screws at the ends of the two terminal blocks until a
distinct cracking sound is heard.
The screws have retaining rings to prevent their complete removal.
4.Pull the two terminal blocks towards the front. Prise off if necessary using a flat
screw at the sides between the terminal block and housing front (see image).

May 2011
1467
5.Use a screwdriver to lightly press the two retaining lugs at the housing sides and
lever towards the front.
6.Carefully pull the module circuit board from the slots in the board. Be careful not to
bend any pins.
1468

May 2011
Installation
Follow the above procedures in reverse order but taking the following into account:
The side of the I/O module with components must point towards the internal circuit
board.
Check that all connector pins fit into the sockets of the inner board and that the
boards are aligned in parallel.
Make sure that the boards keep within the side slots when installing them onto the
base board.

May 2011
1469
Note that the front fits only in one direction to the bottom part. It may be necessary
to rotate the module through 180 degrees.
Do not fully tighten each screw one after the other. Lightly tighten one screw then
move to the next, repeating the procedure until all screws are fully tightened.
4.1.4.8 Internal memory card installation and upgrade
Electronic components are sensitive to ESD (Electro-Static

Discharge). Therefore, discharge any electrostatic energy
before opening the device to install a memory card. We
recommend wearing a wrist band (static discharge wrist
band) and to carry out the work on a conductive surface.
Removing and replacing the memory card

2.Remove all plug-in connectors from the device front. Leave the cables that are
attached to the terminals of the terminal blocks.
1470

May 2011
4.Pull the two terminal blocks towards the front. If necessary prise off using a flat
screwdriver between the side of the terminal block and housing.

May 2011
1471
6.Remove the memory card from its slot using long-nose pliers or a similar tool.
7.Push in the new memory card, with its "handle" pointing towards the board, until it
stops. Use only gentle pressure and do not force. The card fits in one direction only.
Installation
boards are in parallel alignment.
1472

May 2011
Make sure that the boards keep within the side slots when installing them into the
base board.

May 2011
1473
4.1.4.9 Internal battery installation
Electronic components are sensitive to electrostatic charge.

Therefore, discharge any electrostatic before opening the
device to replace the battery. We recommend wearing a
wrist band (static discharge wrist band) and to carry out
the work on a conductive surface.
A lithium coin cell battery CR2450 with 3V/575 mAh is used. The battery has a lifespan of
at least 10 years.
Removal
2.Remove all connectors from the device front. Leave the cables that are attached to
the terminals of the terminal blocks.
4.Pull the two terminal blocks towards the front. If necessary prise off using a flat
screwdriver between the side of the terminal block and housing.
1474

May 2011
6.Remove the battery from its holder using long-nose pliers or a similar tool.
Installation
When inserting the new battery ensure that the negative pole is towards the board
and the plus-pole to the holding bracket.

May 2011
1475
boards are in parallel alignment.
Make sure that the boards keep within the side slots when installing them into the
base board.
1476

May 2011

May 2011
1477
4.1.5
Configuration and operation
The following sections are covered here:

The Configuration via web browser explains how to make (device) settings via an
internet browser.
The following functions are possible via the device's web interface: saving and
loading device configurations; resetting to factory settings; firmware updating. Some
basic settings are also possible, e.g. Ethernet interface or device-clock.
Basic device settings, such as the network settings or the device ID, is described in
the Device configuration section.
The Connecting slave devices section explains the configuration process when
multiple devices are being used.
Devices are equipped with internal memories to enable configurations to be saved.
The Memory section explains how this storage space can be used the space, e.g. for
partitioning across different channel groups.
The Data transfer to USB memory stick section explains how to externally back up
internally stored data.
Configuring the various I/O module-channels is described in detail in the section on
Configuring module channels.
Read the Configuring interfaces section on how to use the various interfaces for
connecting or exchanging data with external devices.
The Configuring software channels section describes the various ways in which to
perform calculations on the measurement data or between channels.
See also Getting Started , Settings for all dialogs.
4.1.5.1 Overview
See also Getting started

Configuration of the most important parameters, such as network settings, can be
performed using either the Web Interface from the device or the DataService Configurator.
Settings via the web interface are described in the Configuration via an internet browser
section. The configuration of sensor and actuator connections, and the definition of
calculation (software channels) takes place via the DataService Configurator and is
explained in the following sections. A detailed description of DataService Configurator is
available in the DataService Configurator manual.
Clicking DataService Configurator starts the DataService background program and
establishes a connection to the devices (the default for the first installation is explained in
the Getting started section). The DataService Configurator dialog is split enabling a device
to be selected on the left under Connections and settings to be made on the right under
Channels . The device itself is considered a "channel" and in the example is listed as "Log-/
ProfiMessage '192 .168.100.116 ', PoND 2.2 ...".
1478

May 2011
Channel configuration
Any configuration performed in the DataService Configurator is considered a channel
configuration even when not strictly concerning a measurement channel, i.e. a device
interface, memory group or module.
Amendments to configurations take immediate effect with the previous settings being
overwritten. The new settings are saved to the Log-/ProfiMessage device's non-volatile
memory and remain there even following a device reset.
Open the configuration dialog for a channel by double-clicking the channel name or rightclicking and selecting Properties from the context menu. Objects that do not have this entry
in their context menus are not configurable via the DataService Configurator but act as
containers, i.e. as channel groups for (more) sub-channels such as the "software channels"
group.
Channels from a channel group are displayed by clicking the corresponding plus sign ( ).
DataService Configurator options
Hide or show columns for the different tabs on or off: View
... or View
Right panel Visible columns ...
Set the DataService Configurator time zone: View
Left panel
Timezone .
Change the DataService Configurator's display language via Options

Suppress confirmation requests: Options
Change channel order via Options
User-defined view ).
Visible columns
Language .
Don't prompt for confirmation.
Activate channel move / link (Only available in the
Further information is available in the manual for the DataService Configurator.

May 2011
1479
4.1.5.2 Configuring a Log-/ProfiMessage device

The Channels tab's top level DataService Configurator is the device level. The next level is
the user-defined view (left panel) and displays the I/O modules, the interfaces, memory
and the software channels. The hardware view (right panel), displays the various system
interfaces, memory and software channels. The I/O modules are located in the "Ext. BUS"
group.
This section explains the settings that users can make themselves. This takes place via "
Log-/ProfiMessage '192 .168.100.116'..." in the Channels tab in the DataService
Configurator (see example). Use the Properties context menu to amend a device name and
ID or to enter a description for the device. Use Main settings context menu to amend
network and NTP settings.
1480

May 2011
Refer to Configuring main unit, Network settings, NTP.

The explanations of other settings, refer to:
Memory for internal memory
Configuring module channels for I / O modules
Configuring interfaces for CAN, COM and PROFIBUS interfaces
Configuring software channels for system monitoring and calculations
Info
For general information on configuration dialogs (including header and
footer), refer to Settings for all dialogs.
4.1.5.3 Connecting slave devices

Slave devices can be connected only to ProfiMessage devices.
The ProfiMessage system uses the CAN-bus and Delphin-CAN Protocol (DCP) to connect to
I/O modules. A ProfiMessage device can be equipped with two I/O modules. The CANconnection is established internally.
The DCP-CAN-Bus for I/O extensions uses the "Ext. BUS" port. If a ProfiMessage device has
an insufficient number or type of channels a slave can then be attached this port. (Refer
to Device connections).
Connecting the extension bus
Use twisted pair, shielded cable (e.g. braided LiYCY 2 x 0.14 mm 2 TP). Ensure that the
start and end connections (i.e. at the master and at the final slave device) use the 120ohm resistors included in delivery. These generate the bus signal level and prevent
interference from signal reflection. The Hi (CAN High) designated ports must be connected
to other devices via Hi, and Lo (CAN Low) with Lo.

May 2011
1481
Display in the DataService Configurator

The Channels tab lists the modules currently connected according to the type of view
selected ( hardware view or user-defined) in the group "Extension (CAN) bus" group or as I/
O modules from the (master) device.
I/O module configuration is explained in configuring module channels.

Configuring the extension bus
The extension bus protocol can not be changed and is set at DCP (Delphin-CAN Protocol).
Baudrate
The baud rate states the number of characters transferred per second via the interface.
Selection depends on the properties of the connected devices and the cable length
between the devices. For longer lines a lower baud rate should be selected to achieve
error-free communication.
The following rates can serve as a guide:
from 15 m :1000 kBaud (factory default)
up to 30 m: 500 kBaud
up to 45 m: 333.3 kBaud
1482

May 2011
4.1.5.4 Configuring I/O module channels

I/O module channels refer to the channels of the of the I/O modules. The configuration for
software channels , interfaces and device memory is described in separate sections.
Refer also to the overview , galvanic isolation, specifications.

May 2011
1483
4.1.5.4.1 I/O module
This section describes configurations at the I/O module level and how to delete a module
entry.
An I / O module appears in the Channels tab as a
symbol. The I / O modules are
available in the hardware view below the "Ext BUS
DCP " entry. The user-defined view
lists all the I/O modules directly below the device - as long as the user has not already
moved the modules or channels.
Double-click an I/O module or select Properties from the context menu to display the
configuration dialog. Use the dialog to change the module name or set the module number
(bus address) in the Main settings tab.
Main settings tab

Module information
This area shows the module's type, version and unique CAN-ID.
1484

May 2011
Module number
After loading the factory settings the modules have no number. The number is important
because a module can be active only when it has been assigned a unique number. Modules
are displayed in numerical order in the channel view.
Give each connected module a unique number between 1 and 99. Numbers that have
already been allocated are marked with the
symbol. When a number has been
allocated, the module symbol is displayed next to the number.
Module settings (for I/O modules DIOT and ADFT only)
These modules have the option to use the counter inputs either as pulse counters or
frequency measurements. For frequency measurements, set the period over which incoming
pulses are totalled to enable the frequency to be determined. Low frequencies require a
correspondingly longer time to acquire multiple vibrations, but measurement is then slow for
long time periods. For short times measurement is dynamic but less vibrations are detected
and measurement data fluctuates strongly. Make sure the gate time is small enough at
higher frequencies because the maximum number of impulses is 65535.
Deleting module entries

Modules can also be displayed that are currently inactive but had been previously
connected or configured. As long as they have not been deleted they are appear with the
symbols
or
before the module symbol. The configuration is retained and reloaded as
soon as the module is reconnected.
Deleting a module entry permanently deletes the entire module

configuration including all hardware channels. Therefore, prior to deleting,
back up the current configuration via the web interface. Refer to save/
load configuration.

May 2011
1485
Delete the entire module entry when the module configuration is no longer required. Click
Delete channel along with subchannels / links from the module's context menu.
4.1.5.4.2 I/O module AMDT
The AMDT I/O module on vibration measurement is dealt with in a separate chapter.
Refer to E/A-Modul AMDT.
Channel configuration/settings are described here: I/O module AMDT, Configuration and
operation.
1486

May 2011
4.1.5.4.3 Analog input
Configuration options in the Main settings tab depend on the sensor type:
Voltage, e.g. 0 10V
Resistor
Current, e.g. 4 20mA
Resistance thermometer, e.g. Pt 100
Thermocouple, e.g. type K NiCr-NiAl
pH probe
The Additional settings tab is identical for all analog input sensors but not every setting is
accessible from every type of sensor.
Monitoring
Measuring range monitoring: When data is not in the Measuring range specified in the Main settings
tab, the channel status is set to "measurement range overrun/underrun". The status
otherwise displays "OK". The output value of the channel is set to the maximum or minimum
value of the Scaling value (in the Main settings tab). Channel status values are available in
the status monitoring table.
Wire break monitoring : The option is useful for monitoring sensor failure in, for example,
thermocouples or sensors with 4 ... 20 mA output. In the event of a failure, channel status
is set to "wire-break". Channel status values are available in the status monitoring table.

May 2011
1487
Cycle times
Calibration every 2^ x cycles : Offset errors require correcting from ambient temperature
fluctuations in long term measurement procedures This setting determines how often this
happens. A cycle is made up of the measurement of all active channels in the module (refer
to Overall module measuretime in the Measuring time tab). The default is every 1024 cycles
(210 ). For an A/D measurement time of 100 ms for 8 active channels, any offset errors are
then corrected approximately every 14 minutes.
Measurement every x cycles: To specify that a measurement from a channel is acquired at, for
example, every 10th cycle. A cycle is made up of the measurement of all active channels in
the module (refer to Module's overall measurement time in the Measurement cycle settings tab).
Compensation
The setting is available for thermocouple sensor types and pH probes. Enter the Channel
that is to be used for the thermocouple's cold junction measurement (junction between
thermocouple and copper wire/connector) or the temperature compensation for the pH
probe. The default Reference Junction uses the measurement from the Pt100 temperature
sensor at the I/O module's terminal and is practical only for the thermocouple sensor type.
A different channel may also be used. When the temperature at the thermocouple to
copper wire junction remains constant, this temperature can be entered as a Manual value.
Inherite status means that the compensation status is applied also to the current
measuring point.
Info
Refer also to Examples of connections for information on the connection of
sensors and Measurement technology for background information on
measurement technology in practice .
1488

May 2011
4.1.5.4.3.1 Resistor sensor type
The example means: 0 degrees corresponds to 0 ohms, 4000 ohms corresponds to 270
degrees .
Measuring range
Select a measuring range that is equal to or greater than the resistance from the sensor to
prevent A/D converter overload. The channel receives the status "measurement range
overrun/underrun" for measurements not within the range. Channel status values are
available in the status monitoring table.
Scaling
Enter two points from the sensor's characteristic curve, if possible, the lower and upper
vertexes. For a linear characteristic, measured values are then converted into the unit of
measurement (scaling) from the sensor. For non-linear characteristics use Sensor
correction. The specified range (in the example 0 to 270 bar) is used as the default for the
display area for graphics in ProfiSignal. The channel receives the status "scale range
overrun" or "scale range underrun" when not within the range. Channel status values are

May 2011
1489
Connection
Indicate here how the sensor has been connected (the diagram displays the selected
wiring):
2 Wire : The sensor is connected with only two wires. This is recommended only for very
short lines and high impedance sensors otherwise the resulting voltage drop on the line
feeds can lead to measurement errors.
3 Wire : The sensor is connected with three wires. Since loss occurs only on one line, a
measurement error is only half as large as in two-wire connections.
4 Wire : The recommended connection method for low impedance sensors and / or longer
supply lines. The loss of feed lines does not matter because the device has a high-ohm
input resistance (no voltage drop on the line feed) and the voltage drop (the unit of
measurement) can be measured directly at the sensor.
4.1.5.4.3.2 Voltage sensor type
The example means: 0 mV corresponds to 0 bar, 5 V corresponds to 10 bar.

Mode
unipolar : Measuring positive signals only.
bipolar : Measuring positive and / or negative signals.
1490

May 2011
Measuring range
Select a measuring range that is equal to or greater than the signal from the sensor or
signal source to prevent A / D converter overload. The channel receives the status
"measurement range overrun/underrun" for measurements not within the range. Channel
status values are available in the status monitoring table.
Scaling
vertexes. For a linear characteristic, measurement values are then converted into the unit
of measurement (scaling) from the sensor. For non-linear characteristics use Sensor
correction. The specified range (in the example 0 to 10 bar) is used as the default for the
display area for graphics in ProfiSignal. The channel receives the status "scale range

May 2011
1491
4.1.5.4.3.3 Current sensor type
Mode
unipolar : Measuring positive currents only.
bipolar : Measuring positive and / or negative currents.
Measuring range
Select a measuring range that is equal to or greater than the current at the load resistor to
prevent A/D converter overload. The channel receives the status "measurement range
overrun/underrun" for measurements not within the range. Channel status values are
Current measurement is not possible without a load resistance.
Scaling
Enter the lower and upper vertexes of the sensor's characteristic curve. For non-linear
characteristics use Sensor correction. The specified range (in the example -2000mA to
2000mA) is used as the default for the display area for graphics in ProfiSignal. The channel
receives the status "scale range overrun" or "scale range underrun" when not within the
range. Channel status values are available in the status monitoring table.
1492

May 2011
4.1.5.4.3.4 Current sensor type (0/4...20mA)
The example means: 0 mA corresponds to 0 l / h (liters per hour), 20 mA corresponds to

1000 l / h.
Mode
This setting is available only for sensor type 0 ... 20 mA available. For sensor type 4 ... 20 mA
the measuring range is always unipolar.
unipolar :
Measuring positive signals only.
bipolar :
Measuring positive and / or negative signals.
Shunt
Enter the load resistance being used. Delphin offers various load resistances for measuring
currents. Contact us to obtain a suitable resistance.
Current measurement is not possible without a load resistance.

May 2011
1493
Scaling
correction. The specified range (in the example 0l/h to 1000 l/h) is used as the default for
the display area for graphics in ProfiSignal. The channel receives the status "scale range
4.1.5.4.3.5 Resistance thermometer sensor type
The example shows the settings for a Pt100 sensor. The sensors or settings for Nixxx
sensors or PT1000 etc. are however similar.
Pt xxx or Ni xxx or YSI400
Select the the type of resistance thermometer being used: Pt100 , Pt1000 or Ni500 etc. The
numerical values for the platinum and nickel thermometers correspond to their resistance at
0C.
YSI400 is a special NTC resistor mainly used in the medical field (temperature range -80 to
250 C, resistance of 1660 ... 6400
Measuring range
Select the measurement range being used. Depending on the version of the sensor only a
limited range may be permissible. Refer to the sensor's technical data. The default is always
the sensor's maximum possible measuring range. The channel receives the status
"measurement range overrun/underrun" for measurements not within the range. Channel
status values are available in the status monitoring table.
1494

May 2011
Temp. Format
Select the unit of measurement in which the temperature is to be displayed. Conversion is
performed automatically within the device.
C : Degrees Celsius
K: Kelvin
F: Degrees Fahrenheit
R: Rankine
R: Degrees Raumur
Scaling
Enter the range for valid sensor signals. The specified range (in the example -260C to
+850C) is used as the default for the display area for graphics in ProfiSignal. The channel
range. Channel status values are available in the status monitoring table.
Connection
Indicate here how the sensor has been connected (the diagram displays the selected
wiring):
2 Wire : The sensor is connected with only two wires. This is recommended only for very
short lines and high impedance sensors otherwise the resulting voltage drop across the
circuits can lead to measurement errors.
3 Wire : The sensor is connected with three wires. Since loss occurs only on one line, the
measurement error is only half as large as in two-wire connections.
4 Wire : The recommended connection method for low impedance sensors and / or longer
supply lines. The loss of feed lines does not matter because the device has a high-ohm
input resistance (no voltage drop on the line feed) and the voltage drop (the unit of
measurement) can be measured directly at the sensor.
Info
No choice of wiring is available for YSI400 sensors.

May 2011
1495
4.1.5.4.3.6 Thermocouple sensor type
The example shows the settings for a thermocouple type K (NiCr-NiAl, nickel-chrome and
nickel-aluminum alloy).
Sensor type
select your type of thermocouple. The letter type and material type of the thermocouple
wires are given.
Measuring range
The maximum possible sensor measuring range is pre-selected. The channel receives the
status "measurement range overrun/underrun" for measurements not within the range.
Channel status values are available in the status monitoring table.
Temp. Format
Select the unit of measurement in which the temperature is to be displayed. Conversion is
performed automatically within the device.
C : Degrees Celsius
K: Kelvin
F: Degrees Fahrenheit
R: Rankine
R: Degrees Raumur
1496

May 2011
Scaling
Enter the range for valid sensor signals. The specified range (in the example -270C to
+1372C) is used as the default for the display area for graphics in ProfiSignal. The
channel receives the status "scale range overrun" or "scale range underrun" when not
within the range. Channel status values are available in the status monitoring table.
Info
Enter the compensation to be used in the Extended settings tab (refer to
Settings for all dialogs).
4.1.5.4.3.7 Ph-probe sensor type
This sensor type determines the pH value from the voltage of the pH probe in mV and the
temperature in C of the reference junction via the Nernst factor.
Nernst factor = ln10 * molar gas constant * absolute temperature / Faraday constant
with molar gas constant = 8.314472 in J/(mol*K), absolute temperature = temperature of
the reference junction + 273.15 in K, Faraday constant = 96.4851534 in J/(mV*mol)
Sensor type
Select pH .

May 2011
1497
Measuring range
A range of 625 mV is sufficient for this type of sensor.
Temp. compensation
Temperature compensation is determined by measuring the temperature at the
measurement point in the solution to be determined. Activate compensation and configure
the channel using the Additional settings dialog (refer to Settings for all dialogs).
Scaling
The default scaling uses the standard measurement methods and should
not be altered.
4.1.5.4.4 Digital input with counter/frequency measurement
Use the Main settings (for DIOT and ADFT modules) or Speed measurement(AMDT module) tabs
to select whether the digital inputs are to be used for counting (Pulse count) or Frequency
measurement. Pulse counting occurs according to a signal's falling edge. For frequency
measurement, pulses are counted that occur within the gate time. The result is then
converted into a frequency
(refer also to the module tab in the Module settings area of the Main settings tab.
Pulse counting or frequency measurement settings apply to all digital

inputs of an I/O module.
1498

May 2011
This example means: 0 pulses correspond to 0 degrees, 7200 pulses correspond to 3600
degrees (10 rotations).
This example means: 0 pulses correspond to 0 kHz, 5000 pulses correspond (with a gate
time of 100 ms) to 50 kHz.
Scaling
correction. The specified range(0 to 3600 degrees in the upper example, i.e. 10 rotations;
in the lower example 0 to 50 kHz ) is the default for displaying graphics in ProfiSignal. The
channel receives the status "scale range overrun" or "scale range underrun" when not
within the range. Channel status values are available in the status monitoring table.

May 2011
1499
4.1.5.4.5 Digital input
Invert : This option inverts a "High" level at the input to a "Low" level at the output
(measurement signal in device) and vice versa.
1500

May 2011
4.1.5.4.6 Analog output
Depending on the module, either currents or voltages can be output. The Output range in the
configuration dialog indicates whether currents can be output in the range 0 ... 20 mA or 4
... 20 mA or voltages in the range 0 ... 10 V or 10 V.
The example means: 0 bar corresponds to 4 mA, 0.5 bar corresponds to 20 mA.

May 2011
1501
The example means: 0 bar corresponds to 0V, 0.5 bar corresponds to 10V.
Source
Enter either a constant value ( Manual value ) or use Channel to select an existing channel
whose value is then output. Selecting Application enables the output value to be manually
set via the DataService Configurator or automatically set via a ProfiSignal application.
Scaling
vertexes. Values from the source are then linearly converted into the output range. For
non-linear characteristics use Sensor correction. The specified range (in the example 0 to
0.5 bar) is used as the default for the display area for graphics in ProfiSignal. The channel
range. Channel status values are available in the status monitoring table. The Output range
defines the limits of the current or voltage output.
4.1.5.4.7 Digital output
The digital output corresponds to a switch that is either ON (the two output terminals are
connected, the input is "High" ) or OFF (no current flow between the two output terminals,
the input is "Low" ). An external voltage source may be necessary (see wiring diagram in
the dialog). Be aware of the maximum permitted currents and voltages for the digital
output, (refer to the Technical specifications).
1502

May 2011
Source
Enter either a constant value (Manual value) or use Channel to select an existing channel
whose value is then output. Selecting Application enables the output value to be manually
set via the DataService Configuratoror automatically set via a ProfiSignal application.
Invert: This option inverts the "High" level for the channel in the OFF state (No current flow
between the two output terminals) at the output and vice versa.
4.1.5.5 Collective device settings
4.1.5.5.1 Configuration via an internet browser
A web configuration is performed by entering the IP address (or the DNS name known by
the network) in the browser's address bar. Any current browser can be used. Cookies are
not required and JavaScript is used only for date and time settings.
Info
Click Save after entering the settings otherwise they will not be amended
within the device.
To return to the main menu either click the Back button on your browser or
click Back at the bottom of the screen.

May 2011
1503
Settings via the web interface are made in the the following four areas: Settings ,
Configuration , Service and System . To display the current status of the NTP client, click
NTP status or Clock. Many of the settings available via the web interface are also available
via the DataService Configurator.
The browser display for a device with the address 192.168.100.28; the host name is
"Expert-Vibro-SN41080240", the domain "TID.local".
4.1.5.5.1.1 Settings
This section enables network and timezone settings. The NTP status is obtained by
clicking NTP status above.
This window enables network data to be input or amended. Settings are made only after
clicking Save .
After changing the IP address or subnet mask the device is then only
accessible via the new address. You may need to change your PC's IP
address (and possibly the subnet mask) in order to re-establish a
connection.
1504

May 2011
The hostname (network name for the device), domain and DNS server are used to convert
network names into the corresponding IP address. Leave the DNS server field empty when
a DNS server is unavailable on the network. Do not use invalid characters for network host
and domain names (no underscores or special characters and only ASCII characters, i.e. no
German umlauts, etc., but hyphens are allowed)
Ask your network administrator whether your network requires MTU and gateway
information. Otherwise leave the default setting of 1500 for MTU. A gateway address is
required only if connections are to be established to other networks.
In the NTP server field, enter the IP address of one or more available NTP time servers (NTP:
Network Time Protocol) to enable the device to acquire the correct time. The NTP time
server can be any other network device such as a PC or another Expert Vibro device. The
integrated Windows time server SNTP (Simple Network Time Protocol) is however not
recommended due to it having insufficient information on synchronization status. The
device accepts NTP times but only when the NTP is synchronized to an internet time server
or to DCF77 or GPS and is able to provide information on the quality of synchronization. If
necessary, download an NTP time server from http://www.meinberg.de/german/sw/
ntp.htm .
The installation CD contains a subfolder (NTP) with a recommended NTP server.

May 2011
1505
Info
The device requires requires up to 5 minutes from switching on to
synchronize with the NTP time. During this time, NTP-Status displays an
invalid value and the message "synchronised to unspecified at stratum 13".
Using a GPS clock

To connect a GPS clock, e.g the Holux GR-213, enter the "pseudo IP address" 127.127.20.3 in
the NTP server field to connect to COM3. The corresponding channel (Device Interfaces
COM3 RS-232) must be disabled to enable reception.
Once the GPS signal has been received, NTP-Status displays "synchronized to UHF
radio at stratum 1".
Enter the timezone in which the device is operating. Store the selection by clicking Save.
When a time server is unavailable, the date and time can be manually set. The device's
internal clock then continues to operate without synchronizing with a time server.
1506

May 2011
Click Synchronize with NTP servers now to commence synchronization with the NTP time server
specified under Network.
This window displays detailed information about the NTP time server, e.g. about server-IP,
signal delay and jitter (variations). The information is for users who are familiar with NTP
protocols and who wish to identify errors in timestamp transfers or time server responses.
Info
The following is an example of the NTP-status (only the beginning is shown):
4.1.5.5.1.2 Configuration
This section describes:

Default channel configuration resets all channel settings to the factory settings.
Refer also to Default configuration.
View channels to display the current channel Settings .

May 2011
1507
This window displays the configurations for all device channels as a table. Each column
contains detailed information such as channel name, type of module, physical unit,
measurement range, or whether an invalid channel configuration exists, etc. The object ID
in the penultimate column enables users to display the channel configuration as an XML file
(potentially important for support purposes).
The data can only be displayed. Changing settings is not possible. Use the DataService
Configurator for configuration.
The following image gives an example of the channel overview:
Resetting to the factory settings (Default channel configuration) can not

be undone. Therefore save the current configuration beforehand. Refer to
Saving and loading device configurations.
Clicking Default channel configuration resets all channel settings to the factory settings. The
process is displayed in a window.
The process ends when Back is displayed in the window's footer.
1508

May 2011
Following a reset (default channel configuration) the channels are disabled

so you need to re-enable them.
Info
Resetting the configuration to the factory setting can only be done via the
web interface.
4.1.5.5.1.3 Service

How to generate a System report.
The report is important only for Delphin's service and support team in the event that
your device is malfunctioning.
How to display the PROFIBUS GSD file for integrating the Expert Vibro device into a
PROFIBUS network (clicking), or how to save it to a PC (Save as context menu).
How to download bitmaps from a device.
Bitmaps are used for the graphical representation of the device in your PROFIBUS
project program.
How to copy an XML template for network configuration to the PC.
Make new settings in the template and transfer these to the device via a USB stick.
How to download the PuTTY terminal program ( PuTTY ).

May 2011
1509
Provides a detailed overview of the system for fault diagnosis by the Delphin support
team. Send the file to the support team. The system report can be generated only through
the web interface.
When you click System report, the device needs approximately 10 seconds to acquire all the
information and save it to a ZIP file. The following dialog is then displayed to select the
location of the saved the file. The file name contains the date and time of the request as
well as the device's network identifier.
The PROFIBUS GSD file is required to configure the Expert Vibro device into the PROFIBUS
project software of the PROFIBUS master.
Click PROFIBUS GSD to view the GSD file in an internet browser. Right click and select Save
as from the context menu to save the file and to enable it to be copied to a PC containing
the PROFIBUS configuration program.
The saved bitmaps are optional for correctly displaying the Expert Vibro device in the
PROFIBUS project software.
Info
Download the GSD file via the web interface or copy it from the /firmware
directory on the installation CD.
The following is an example of a GSD file (only the beginning is shown):
1510

May 2011
The XML template enables you to set a device's network configuration without having to
connect a PC to the device. This is especially useful when you have to configure multiple
devices. You then amend the file for each device and save it to a USB stick. When you
insert the USB stick into a device, the device reads it and uses the settings from the file.
Method
1.Save the file to your PC (right click the link).
2.Open the file with an editing program.
3.Change DefaultGateway="192.168.0.254", IPV 4_ A ddress="192.168.0.1" and
IPV 4_ NetMask="255.255.255.0" to the required values or change DHCP_ activ e="false" to
DHCP_ activ e="true".
4.Save the amended file to a USB stick.
5.Insert the USB stick in the Expert Vibro device.
6.Switch on the Expert Vibro device.

May 2011
1511
4.1.5.5.1.4 System

Update firmware that updates the device's firmware (the software within the device).
Refer also to Update firmware.
Firmware changelog that enables you to view the changes made to the firmware
compared to previous versions.
Viewing requires the Adobe Acrobat Reader. The Acrobat Reader can be downloaded
cost-free from Adobe.
Refer to Updating firmware.
Reboot that starts the device anew.
The procedure functions the same as switching the device off and then switching it
back on again.
Refer to Reboot device.
Restart main application that restarts only the device software for data acquisition,
recording and/or transfer.
Refer to Restart main application.
This is faster than rebooting the device.
Info
Update firmware can be performed only via the device's web interface:
The latest firmware for your device is delivered with each software update. Perform both
updates to ensure software and hardware are being used with their latest versions. Errors
may otherwise occur in data acquisition or configuration. The device's current firmware
version is also displayed in this window.
Do not disconnect the power during an update. This can damage the
device, requiring repair by Delphin.
1512

May 2011
Enter the file with the new firmware in the New firmware file field (click Search to find the file
on your PC) and then click Start firmware update . The firmware update takes approximately 4
to 6 minutes.

May 2011
1513
Click Firmware changelog to display a PDF file containing information on how the current
firmware differs to previous versions. The Adobe Acrobat Reader is required. The Acrobat
Reader can be downloaded cost-free from Adobe.
Example of a firmware changelog:
Clicking Restart main application restarts the main program. This is faster than fully rebooting
the device.
During the restart, data is neither acquired nor stored. The device
disconnects from the network and the connection is re-established only
after a restart.
1514

May 2011
Info
A restart can be performed only via the web interface.
The process is displayed in a window.
The process ends when the "Done" message is displayed.

Restarting the device anew. The process takes approximately 2 minutes. Then click Back .
The device's power LED (system LED) indicates when the device is ready for operation.
The action is equivalent to pressing the (countersunk) reset button on the front of the
device or switching it off and then on again.
Info
A restart can also be performed via the display.
4.1.5.5.2 Main menu device settings

May 2011
1515
4.1.5.5.2.1 Device configuration (channel configuration)
Open the configuration dialog by double clicking the line containing the device or via
Properties in the context menu.
This dialog enables users to:

Enter details on Location and device function (Description).
Enter, for example, the location of the device or measurement object that is to
acquire data.
Amending Device ID .
Device ID
The DataService uses the device ID to uniquely identify a device and its channels. The
factory setting for the device ID is its serial number.
The device ID is displayed as the main part of the Obj ect ID under the DataService's column
of the same name. The column can be displayed via View
Right panel Visible channel sheet
columns.
The user-defined device ID needs to be changed if you have transferred the configuration
from another device and are then operating both of them from the same DataService. Both
devices would then have identical device IDs and the DataService would not be able to
distinguish between them.
1516

May 2011
Method
1.Open the Device configuration dialog.
2.Enable Device ID given by user.
3.Enter a new ID (e.g. the device's " old " serial number).
The device ID is in hexadecimal format. Valid input includes numbers from 0 to 9 and letters
from 'af' or 'AF' (no distinction is made between upper case and lower case letters). A
zero may not be entered as the first character.
A valid input changes the input field's background color to bright green. It remains red as
long as the input is invalid or incomplete.
When you change a device ID, it disconnects for a short period before then reconnecting.
Refer also to Settings for all dialogs
4.1.5.5.2.2 User management configuration
User manager enables you to regulate which users may access your Expert Vibro- device.
The dialog contains a table with all users that have been given access to your Expert Vibro
device. On the left of the table is the user name and on the right the user right. The users
Administrator, Guest and root are already set and can not be deleted. Changes to these
are also restricted. The grayed out entries in the table mean the option Active is disabled.
Guest
The Guest user is used for anonymous logins. To enable anonymous logins, you need to
activate this user as well as activating anonymous logins in Main settings
User manager.
Set the user rights to the required level.

May 2011
1517
Administrator
The Administrator has the rights to change any setting within the device. The factory
setting password is SUPERVISOR.
root
Has the the same rights as the Administrator but also has the right to login at the
operating system's console. There is no factory-set password for root.
Important
After enabling user management, we recommend for security reasons, that
you change the Administrator and root password in the device's user
management.
Adding a user
Click New user.
Deleting a user
Selected the user to be deleted and click Delete. Administrator, Guest and root can not be
deleted.
Amending a user
Select the user to be amended. The user's current details are shown on the right.
1518

May 2011
Activating a user
Only users that have Active enabled can login to a device.

User rights
Select one of the five user levels: Viewer, Evaluator, Operator, Configurator or an additional
Administrator. Rights for the user groups are explained in the user rights of the DataService
Configurator.
Phone numbers and email addresses

You can enter up to three phone numbers and email addresses per user.

May 2011
1519
4.1.5.5.2.3 Network settings (Main settings), NTP
Open the dialog via Main settings in the context menu from the line containing the device.
If you make changes to IP address, Net mask or DHCP, the device is then
accessible only via the new address. You may need to change your PC's IP
connection. (Delete the "old" driver using the the context menu of the
device on the left side of the DataService Configurator).
The hostname (network name for the device), Domain and DNS server are used to convert
1520

May 2011
If you enable Use DHCP, the device attempts to automatically retrieve an IP address from
the DHCP server. Even if you enable it you should still enter an (alternative) IP address:
this will be used by the device in the event that no address is provided by the DHCP
server.
or to DCF77 or GPS and is able to provide information on the quality of synchronization.
Download an NTP server from http://www.meinberg.de/german/sw/ntp.htm if necessary.
Info
Using the DataService

You can also achieve direct synchronization with a connected DataService without using
the NTP protocol. The current time of a PC connected to the device is used as the
reference time and the Expert Vibro device commences to set itself according to this time.
The procedure can take longer than one hour. In the NTP server field, select the setting
DataServ ice. Use this setting only when your network has no NTP server. The time setting is
only as good as the time setting in the connected PC.
Using a GPS clock
To connect a GPS clock, e.g. the Holux GR-213, set the NTP-Server field to GPS-Clock @
COM3. The corresponding channel (Device Interfaces
COM3 RS-232) must be disabled to
enable reception.
Incorrect time synchronization
Example of absent or incorrect time synchronization DataService Configurator:
Enter topic text here.


May 2011
1521
You can enable the device's user management from the User manager tab.
Anonymous login
This option enables users to login to the device using the user name of "Guest". To enable
anonymous login, you need to activate the "Guest" user account and set the account's
rights. Anonymous login via the DataService then takes place either when the user has not
entered any login data when connecting to a device or the data entered is invalid.
Once user management has been enabled, a connection to device is

established only with the input of a valid user name /password. Before you
activate user management, ensure that you have the required login
information. Otherwise you will be unable to connect to the device!
Factory settings of login data

User: Administrator
Password: SUPERVISOR
Important
management.
4.1.5.5.2.4 Saving and loading device configurations
Save settings
1522

May 2011
Open the dialog via the context menu for the line in which the device is displayed.
Enter the destination file. You also then have the option of entering comments for the
saved configuration. These are displayed when loading the file.
Load settings
Select the configuration file to be loaded. Only files can be loaded that have be generated
via Save settings. Configuration files that have been saved via the web interface can not be
loaded via this menu. The comments for the saved file are displayed and the user then has
the following options:
Restore channels
This loads into the device all the channels from the configuration file. Any existing channel
configurations within the device may be deleted.
Restore global tables
This loads into the device all set-point and linearization tables from the configuration file.
Any existing tables within the device may be deleted.

May 2011
1523
Restore users
This loads into the device all user settings (including passwords) from the configuration file.
Any existing user data within the device may be deleted.
Only the data is loaded. Activating user management is performed via the following option:
Restore system settings
This loads into the device all system settings (network settings, activated user
management) from the configuration file.
If user management has been enabled, the password (from the

configuration file) must be known for the next login otherwise it will no
longer be possible to connect to the device!
Keep current device IP address/ mask / gateway

When enabled, the main network settings are not loaded. If not enabled (i.e. not crosschecked), the network settings loaded into the device may make your device inaccessible
from your IP range, or the device acquires an IP address that is already being used thereby
resulting in a network conflict.
Restore unique device ID
The device ID generally corresponds to the device's serial number. This ensures that the
device's channel IDs are globally unique. Select this option to use a previous configuration,
e.g. from a spare device, without you having to change the channel ordering in other
applications or trends. The option is automatically selected when the saved device ID is
the same as the current device ID. The option is unavailable when the device ID Option in
the configuration file is currently being used by a device connected to the DataService
Configurator.
The device ID from the configuration file is loaded into the device.
Devices with the same device IDs cannot be used in the same DataService Configurator
environment.
4.1.5.5.2.5 Tables
Set point tables can be created in the device for software and channel linearization tables.
The tables can have two different applications:
Global application for multiple channels (external table)
Global tables can be used for multi-channel data not assigned to a specific channel.
They are valid only after Global settings have been made for Table type in the Main
settings tab for this channel's software channel setpoints or linearization.
A global linearization table is created using the Global linearization table context menu
of the device.
Local
The validity of a local setpoint or linearization table is limited to the channel in which
1524

May 2011
it is configured.
From the Main settings tab select the Local for the software channel setpoint or
linearization Table type . Create the table in the Table tab that then appears.
An external linearization table that can be used as a global table for multiple channels is
created via the Global linearisation tables context menu of device. Refer also to
Linearization.
Linearization table created using the device's context menu.

Method
1.Click New to create a table.
2.Change the Table name if required.
3.Select the required mode.
4.Enter the point values.
The number of values to be entered will depend on the type of linearization required
(Mode ).
5.Click Save.
A table can be imported as well as created: Import.

May 2011
1525
Mode
There is a choice of modes
Offset
An offset shifts the curve by a fixed value, i.e. the given value is added to the
measurement value.
Offset and Gradient
Allows a shifting of the curve and an increase in its gradient. The example above
shows the values for a temperature measurement with calibration at 0 C and 100
C.
Squarely
Generates a quadratic curve through the given points to linearize the measured
values.
Linear interpolation
Enter a table for the conversion of measured values into display values. Linear
interpolation takes place between the given points.
An optimal fitting polynomial 3rd degree (cubic spline) is determined using spline
interpolation for the given values. This is then used to to convert the measured
values.
Info
You can use copy and paste to transfer data from an Excel table into the
dialog's table. Position the cursor in the table's top left field. Extra rows are
created automatically when this is permitted by the selected mode.
Click on a row and use the Del key to delete unwanted rows. Insert extra
rows in a linear interpolation using the Return key .
A created table can be exported and then re-imported later: Export and
Import .
Info
Import .
1526

May 2011
An external setpoint table that can be used as a global table for multiple channels is
created via the Global setpoint table context menu of device.
The setpoint table creates a conditional procedure whose points are set by value pairs
made up from a period and a value. Each row of the table describes a program step for time
t (fixed or variable) and value y (fixed or variable). Based on the previous value of yi-1 ,
the ti value indicates how long will it take to achieve the yi value. The first row defines the
starting point of the track, so at least two pairs of values require entering. One variable is
defined via the setpoint channel that uses the table.
Setpoint table created using the device's context menu.

May 2011
1527
Method
3.For each table row (program step) enter the time value ( Time ) with the unit of time
and to be used and the value to be output.
4.Click Add.
5.Enter the required Global Settings .
6.Click Save.
Numbers (constants) or variables can be used for times and values. The variables used in
the tables are defined under setpoint channel(software channels). For time input, the
variable may be used as a value or as a trigger:
Variable (value) means that the value of the variable is used as time value. Variable (trigger)
means that the channel set for the variable is used as a trigger channel. A trigger event is
a rising edge. If this trigger occurs, the value that is programmed into the program step for
the trigger is applied as a setpoint and the next program step is then performed. This
method enables the upgrade of a basic time-controlled program to an event controlled
system.
Global settings
Relative time : When enabled, input times are calculated as a difference to previous time
points. When disabled, time values are taken from the start (first value).
Example of absolute and relative time input
The numerical values are fixed values and in this case refer to identical time points.
The final time is 7 (the unit is not stated but might, for example, be minutes).
Point no.
Absolute
Relative
1528

May 2011
Example of a table
In the table in the example, the value 22.5 is held for the first 15 minutes. Then, after
each 6 minutes (Relative time setting ) the value increases to 35, then lowers to 10 via
22.5, and then increases again to 22.5. A change and therefore output of the new
value takes place every 10 seconds. The change over the previous value is therefore
around 0.35 for every 10 seconds.
Cycle time : The cycle time for values to be output between two program steps.
Intermediate values are linearly interpolated, i.e. calculated using a linear equation. The
intervals used in the table between each program step should be multiples of the cycle
time.
4.1.5.5.3 Settings for all dialogs
A configuration dialog opens after double-clicking one of the channels, e.g. from an I/O
module, an interface or an interface protocol. Different tabs are displayed depending on the
channel type. The data in the tabs also depends on the channel type. Many settings are
similar, especially in the upper and lower sections, and can therefore be explained generally
for any type of channel.

May 2011
1529
Upper section
Active: Enables or disables the channel.

Channel name: Enter a meaningful and unique name to identify the channel.
Unit: Enter the unit of measurement.
1530

May 2011
Info
The unit for memory groups should be left at % (default). Storage
capacity is always shown as a percentage.
Location: Information on the location of the sensor or signal source can be entered
here.
Description: For entering a description or comment. After creating a function (software
channel), a description of the function (in English) appears here.
Lower section
Previous or Next : Changes to the configuration dialog of the previous or next channel in
the channel view. The dialog's current settings are applied before the dialog changes
(the equivalent of clicking on OK ).
OK: Applies all the settings and closes the dialog.
Cancel: Cancels the configuration and closes the dialog. The settings are ignored and
no changes are made within the device.
Help: Opens the online help. The appropriate topic is displayed whenever possible.
The lower left displays the date and time of the last change made to a setting for this
channel (8.8.2013 in the image).
Tabs in the dialog's main section

Depending on the type of channel, different tabs are available. Not every channel type has
the following tabs:
Main settings
Advanced settings
Sensor compensation
Information
The Main settings tab is always for a specific channel. There are also other tabs that relate
to specific channels and are therefore described under these channels. The other tabs
share common settings and can be explained here.

May 2011
1531
4.1.5.5.3.1 Advanced settings tab (software channels)
Default value: This is used in the event of a input or output failure ( refer also to status
monitor ). The settings depend on channel type. For example, digital inputs only have the
options Off and On.
Force default value (simulation) Sets the channel's output value. This setting is is useful during
installation to simulate certain conditions or activate system responses.
Do not forget to disable the option for normal operation!
Data reduction (Not available for all channel types): A signal is fed through the channel input,
processed within the channel and then released at the channel output. The tolerance
specifies the extent of change a signal must undergo following processing before being
output. In the example the processed input value is output only when it differs by more
than 0.1 mA to the preceding value. The Data reduction function enables prevents the device
from having to process/store superfluous data.
The tolerance value can be expressed as an absolute measurement unit or as a relative
value. Refer also to the Scaling section of the Main settings tab.
Format: For setting data resolution.
Persistence (not available for all channel types): The currently valid output value (refer to
data reduction) is stored to a non-volatile memory. The channel uses this value following a
restart or reboot. This feature is particularly important for outputs to establish a predefined
state following a power failure.
4.1.5.5.3.2 Sensor compensation
To specify correction values for sensors with non-linear characteristics or to specify the
correct direction for sensors with different characteristic values for positive and negative
measurement directions. Conversion takes place according to scaling settings in the Main
settings tab for the signal delivered by the sensor.
1532

May 2011
Active: Enables sensor compensation.

Mode There is a choice of modes
Offset
measurement value.
Offset and slope
Allows a shifting of the curve and an increase in its slope/gradient. The example in
the above image shows the values for a temperature measurement with calibration at
0 C and 100 C.
Squarely
values.
values.
Info
Import .

May 2011
1533
4.1.5.5.3.3 Information
This tab displays the dependent channels of a channel or track.
1534

May 2011
4.1.5.5.3.4 Basic channel selection
Many dialog require a channel to be selected as a source or a target. A basic or advanced

channel selection is available.
Basic channel selection is accessed directly from the configuration dialog. All configured
channels are listed by clicking the arrow on the dropdown list:
Click the required channel.

If the channel name is known it can be input from the keyboard. The list then filters
according to each letter typed.
4.1.5.5.3.5 Advanced channel selection
Info
The advanced channel selection is not yet available for Windows Vista and
Windows.
This method of display and selection is more convenient for large numbers of configured
channels because the advanced filtering function enables only specific channels to be
displayed.

May 2011
1535
Open the dialogue box by clicking

and channel ID.
. The channels are displayed by name, description
Enter filter criteria in the Advanced search area. The filtered channels are then displayed.
Selected the required channel and click OK.
Info
The separate settings (trigger groups, analog/digital input/output, track,
characteristic values etc.) can be saved in a file and re-loaded or copied
and pasted by using Partial configuration.
4.1.5.5.3.6 Edge and level triggers
Many dialogs have input fields with options for different trigger functions according to edge
or level states. The following variations and combinations are available:
Edge and level
Level
Edge (full)
1536
Edge (basic)

May 2011
Explanation of options
Setting
Description
Rising edge
The event is triggered when changing from "Low" to "High"
Falling edge
The event is triggered when changing from "High" to "Low"
Edge (both)
The event is triggered at every change
High level
The event is triggered when (and for as long as) the level is "High"
Low Level
The event is triggered when (and for as long as) the level is "Low"
4.1.5.5.3.7 Inherit status
This option sets whether the source's status as well as its value is to be used. This can be
used, for example, to prevent invalid input values from entering the process. Channel
status values are available in status monitoring.
An example of inheriting: A thermocouple wire-break is also displayed in the software
channel as a wire break.
4.1.5.5.4 Configuring Software channels

Software channels are calculations or functions that are performed within the device. In
previous device families from Delphin, such channels were also called virtual channels. Any
number of channels can be created. This is a standard feature of the device.
Display the Software channels context menu (DataServiceChannels tab). You can then either
create a Channel group (e.g. Analog channels in the example) to group together created
channels, or select one of the available channel operations. The context menu contains all
available calculations and functions.

May 2011
1537
Alternatively software channels can be created via the context menu of a hardware
channel as Create dependent channel. In contrast to creation via Software channel, the source
channel is already selected within the dialog and the channel is (initially ) located directly
under the hardware channel. Following creation, the User defined view enables channels to
be moved and grouped differently.
Another option enables the linking of a channel. The original channel remains at the original
position, but creates at another location an entry that is linked to this channel.
Linking channels
From the Options in tab in the DataService Configurator select Activate channel move / link. In
the User defined view (View
Right / left panel Channel sheet options) move or link a channel
by left-clicking and holding. Further information is available in the DataService Configurator
manual.
The rest of the configuration is similar to module channels. Specific settings for each
function are explained in the sections here.
General information on dialogs is available in Settings for all dialogs and General settings for
Software channels.
4.1.5.5.4.1 Accumulator
This Software channel adds together all values from the specified source channel:
Adder = adder + new value
Reset: When enabled, the calculated sum is output only in a reset event and then reset
internally to zero. When not enabled, the sum is output for each each new value from the
source channel.
(Refer also to Trigger options ).
Generate intermediate values: When enabled, results are also output (without resetting to
zero) between reset events immediately after their calculation.
1538

May 2011
4.1.5.5.4.2 Operating hours counter
This software channel acquires the time the source has an active level. When the level
becomes inactive, the time period is added to the cumulative time period.
High level / Low level: Sets the active level of the source.
Info
The operating hours counter retains its value even when the scale is
amended.
Enable Reset and configure a channel and the trigger ( Edge, Level ) to reset the hour
counter.
Refer also to Trigger options.

If the source has an active level when the reset signal occurs, the operating hours counter
is reset to zero only after the source becomes inactive again.
4.1.5.5.4.3 Differentiator
This Software channel calculates the relationship of the difference between two values
from the source channel to the difference between their time stamps based on the time
base:
Differential = (
Value / timestamp) * time base
Refer also to the Advanced settings tab

Time base : Enter the time base for the calculation. The default is 1 ms.
Enable Trigger when the calculation is to be triggered by specific events. The differential
between successive trigger events is then calculated.
4.1.5.5.4.4 Ereignis

May 2011
1539
4.1.5.5.4.5 FlipFlop
This software channel functions like a hardware flip-flop.

Select the type of flip-flop from Mode. A diagram is displayed depending on the selection.
Various inputs are available. Disable any unnecessary inputs.
The mode "Latch" will store any data types, for example if the D-Source is an analog
channel, the FlipFlop stores the value.
The following tables show the possible states.
X = any level, = edge, H = "High" level, L = "Low" level.
Refer also to trigger options.
JK Flip-Flop
Status
Clr
Pre
(clock)
(clear)
(preset
)
1
Previous status
Toggle
1540

May 2011
RS-Flip-Flop
Status
S+
Clr
Pre
set
(clock
(clear
(pres
priorit
et)
y
1
Previous
state
In RS flip-flop, there is the additional option of Set priority , i.e. the value at set input
(S) has priority when R = H.
D-Flip-Flop
Status
C (clock)
Clr
Pre
(clear)
(preset)
Previous state

May 2011
1541
Latch
Status
C (clock)
Clr (clear)
D (transparent)
Previous state
4.1.5.5.4.6 Limit
This Software channel monitors the specified source channel. The result, i.e. the output
signal of the limit channel, is "High" when the specified alarm conditions are true.
The following forms of monitoring are available:
Mode
Alert when
Overrun
the value is above the specified range or above the limit/threshold
Underrun
the value is below the specified range or below the limit/threshold
Band monitoring
the value is outside the specified range (threshold bandwidth)
Band violation
the value is within the specified range (threshold bandwidth)
Steady condition
values change by more than the bandwidth during hold-up times
In addition, no triggering for wire-breaks at the source can also be entered. The setting is
only for sources (sensors) which can have wire-break monitoring.
For all input, either enter a fixed value (Manual value) or specify a channel that delivers the
value. It is possible to change the limit value during measurement.
Threshold is the decisive value in monitoring.
Hysteresis : Hysteresis prevents the alarm being repeatedly activated for small fluctuations
around the threshold value in the monitored signal. Depending on switch direction, the
hysteresis lies below the threshold (for overruns) or above the threshold (for underruns).
Refer to the images. The hysteresis is especially beneficial for small (noise) signals. The
Delay option offers an alternative.
1542

May 2011
Bandwidth : Sets the "monitoring window" for Band violation and Steady condition monitoring. In
Band monitoring and Band violation the "monitoring window" is symmetrical to the threshold.
The value entered acts for Band monitoring in positive and negative directions as a
subtraction to the window and as an addition for Band violation.
Example: Threshold = 50, bandwidth = 3
means the 47 to 53 range is monitored.
Hold-up: The alarm condition must remain true during the specified time to trigger an alarm.
The option is an alternative to Hysteresis and is especially suitable to suppress alarms for
brief signal distortions with high amplitudes. Both options can be combined.
Latching: The alarm is latched (continues to alarm) even when the alarm condition is no
longer true. Enabling Latching changes Reset trigger for latching. The alarm resets when a
reset event occurs, e.g. a Rising edge, in the given channel. The Reset priority option causes
an alarm to reset when the alarm condition is still true.
4.1.5.5.4.7 Impulse generator
The software channel can be used in two different modes:

Free running: Free running pulses are generated at a fixed repetition rate (Cycle time)
and at a set Pulse width.

May 2011
1543
Synchronic to real time: Pulses are generated at a repetition rate according to time. For
example, a Cycle time set at 15 minutes generates pulses at 00, 15, 30 and 45
minutes of each hour. Only discrete values can be entered here because impulses are
generated only at whole number ratios.
Pulse width: sets the pulse duration, i.e. how long the pulse maintains a "High" level.
Cycle time: sets the pulse repetition rate.
In Synchronic to real time mode, only specific times can be selected from the list because the
cycles must be at whole number ratios.
After closing the dialogue with OK a check for validity is performed. If the input is invalid,
e.g. the pulse width is greater than the cycle time, an error message is displayed and the
previous valid configuration is retained.
1544

May 2011
Source: The Level trigger option means that the pulse generator functions only during the
source's active time, The Edge trigger option means that the pulse generator starts with
the source's edge and runs continuously until stopped with Reset
The diagram shows the release of the pulse ( red curve) by the source ( blue curve).
Reset: when the event occurs, immediately resets the pulse generator output to
(asynchronous) "Low" level. If the Level trigger setting is selected, this signal permanently
suppresses further pulses occurring at the pulse generator output.

May 2011
1545
Examples
The following are examples of possible uses for the pulse generator.
Example 1
In this example the pulse generator runs in continuous mode. Cycle time = 5 seconds.
A channel has been selected for the pulse width that initially outputs the value 1 and
then the value 2. The channel is not permitted to output a negative value (no negative
times)nor a value greater than the cycle time, i.e. 5 in this example. Another channel is
given for the reset.
1546

May 2011
Once the pulse generator starts ( red curve) with a pulse duration of 1 second, the
pulse duration sets to 2 seconds ( green curve). After three pulses, the reset channel
( purple curve) gives the reset signal and the pulse generator issues no more pulses
(the next pulse would be due at 8:49:30). Pulses begin again only after deleting the
reset signal (level = "Low"). The cycle time indicates that the next pulse will be output
at 08:49:50.

May 2011
1547
Example 2
In this example the pulse generator runs in controlled mode. The trigger is enabled by
setting High level ("High"). The pulse width and cycle time are set by other channels.
Note that these channels may not issue negative values (no negative times) nor
conflicting values such as a pulse width greater than the cycle time. Another channel
is given for the reset.
1548

May 2011
The pulse generator (red curve) is started by the trigger channel (blue curve) with a
2-second pulse duration (green curve) of and a 6-second cycle time (black curve).
After three pulses, the pulse duration is increased to 3 seconds (green curve). After
another two pulses, the cycle time (black curve) is reduced to 5 seconds. Just before
9:13:00 a reset takes place at the rising edge of the reset channel. Because the
trigger source has a "High" level, the pulse duration re-starts even though a pulse had
already begun.

May 2011
1549
Example 3
The following examples illustrates the relationship between trigger signal and reset
signal.
a)
Trigger and reset are triggered by channels and are set to Edge (both) . Then both the
signal's rising and falling edges trigger the event.
The trigger (blue curve) starts the pulse generator (red Curve) with a rising edge.
Then the reset (purple curve) is triggered with a rising edge triggered and the pulse
generator stopped. Pulses are generated again only after the trigger emits a new start
signal with a falling edge. A falling edge from the reset channel re-stops the pulse
generator. Pulses re-start only with a rising edge from the trigger channel.
1550

May 2011
b)
The trigger is triggered by a channel and has been set to Edge (both) . The reset is also
triggered by a channel, but has been set to High level.
The trigger (blue curve) starts the pulse generator (red curve) with a rising edge.
Then comes the reset (purple curve). Because the high level ("high") remains, no
further pulses are generated (Reset = High level ). Meanwhile the trigger channel
switches to a low level ("Low"). However, because the reset channel remains at a high
level, the trigger channel's edge has no effect. The pulse generator does not re-start
even when the reset channel reverts to a low level; a re-start takes place only with a
rising edge in the trigger channel.

May 2011
1551
c)
Trigger and reset are triggered by channels and are set to High level.
The pulse generator (red curve) is started by the trigger channel (blue curve). When a
reset signal (purple curve) is received the output is set to "low" and no further pulses
are generated. When the reset signal resets to "Low", the pulse generator re-starts
(10:25:25) because the trigger channel remains at a high level. In the second example,
no further pulses are generated because the trigger channel has meanwhile gone to
"low".
1552

May 2011
d)
The trigger is triggered by a channel and has been set to High level. The reset is also
triggered by a channel, but has been set to Edge (both).
reset signal (purple curve) is received the pulse counter is set to "low", but begins
immediately to generate new pulses because the trigger signal remains "High" and the
reset signal is generated only by the edge. The pulse generator stops only after the
trigger signal also goes to "Low". The falling edge of the reset signal has no influence
here as no pulses are being generated at the time.

May 2011
1553
4.1.5.5.4.8 Integrator
This software channel calculates the area below a curve ( Source ).

Integral = (((previous value + current value) / 2) *
time-stamp * time-base)
Cyclic : New values are repeatedly obtained from the source for the Period input and the
integral calculated between the current and previous values. A new value is calculated for
each interval and added to the running total.
Adaptive: When the source delivers a new value, the integral is calculated between this
value and the previous value. The result is added to running total.
Time unit for source: The calculated values are scaled to the source's time unit, e.g. in l/min
(for liters per minute, enter 60 seconds).
Reset: The calculated integral is output only in a reset event and then reset internally to
zero.
Generate intermediate values: When enabled, totals are also output between reset events
directly following their calculation, (without being reset to zero).
4.1.5.5.4.9 Channelgroups
Use channel groups to group related or interdependent channels. Any number of channel
groups may be created. If required a channel can be linked to more than one group (linked
channels: refer to Configuring Software channels).
4.1.5.5.4.10 Linearization
Linearization enables an additional conversion to be performed on a channel's values. An

advantage of this feature is that the channel's original values remain available with the
conversion being performed in a "new" channel.
The available options are identical to those for sensor compensation, which can also be
performed here in addition to the required linearization. This dialog enables either the
setting of only a conversion function for the channel ( Table type: Local table ) or the use of
a global linearization function ( Global table ) which has been set up via the Global linearisation
table option in the device's context menu.
See also Tables , Global linearisation tables, Settings for all dialogs: sensor compensation
tab
1554

May 2011
Method
1.Select a table type.
For external tables then select a table; for an internal table, set up a table via the
Table tab that is then displayed.
2.Select a source.
3.Set up a table if necessary (Table tab).
There is a choice of modes:

Offset
measurement value.
Offset and Gradient
Allows a shifting of the curve and an increase in its gradient.
Squarely
values.
values.
Info
Import .

May 2011
1555
4.1.5.5.4.11 Logic
This software channel enables the logical linking of digital signals. Various boolean functions
are available: AND, OR, NAND, NOR, NOT, XOR and XNOR as well as Antivalence (XOR with
more than two inputs) and Equivalence (XNOR with more than two inputs).
Add input generates additional inputs. All inputs are linked according to the selected logic.
Info
NOT, XOR and XNOR functions can link only one or two inputs.
Only this number of inputs can then be created.
Click
to delete an input.
Function table NOT
Input value
Output value
Function table AND

Input value A
Input value B
Output value
1556

May 2011
Function table OR
Input value A
Input value B
Output value
Input value A
Input value B
Output value
Input value A
Input value B
Output value
Input value A
Input value B
Output value
Function table NAND
Function table NOR
Functiontable XOR (exclusive OR)

May 2011
1557
Function table XNOR

Input value A
Input value B
Output value
Function table Antivalence

The output for Antivalence is then "High" if an odd number of inputs are "High" and the
remaining inputs are "Low".
Input value A
Input value B
Input value C
Output value
1558

May 2011
Function table Equivalence
Input value A
Input value B
Input value C
Output value
4.1.5.5.4.12 Variables
This software channel provides a control option that enables either manual control over the
processes in a device via the DataService Configurator or automated control via a
ProfiSignal application.
Signal flow is via a variable channel from the DataService Configurator or a ProfiSignal
application in the direction of the device. Using channel variables differs to analog or digital
outputs or COM channels set to outputs, in that access is to the device itself and not just
to the connected process.
The generated variable is configured as a source for the controlling channel, e.g. as a reset
trigger for a counter channel.

May 2011
1559
Application: This option enables variable control via the DataService Configurator or
ProfiSignal. Set the variable to a constant value via the Variable's context menu in the
DataService Configuratoror automatically control the value via ProfiSignal.
Manual value: This option sets a constant value for the variable. This setting is useful during
installation to test specific devices or activate system responses.
4.1.5.5.4.13 Average
This software channel calculates averages from the source values.

Simple moving average: This average is calculated from a configured series of values
numbering from 2 to 1000 values.
Moving indicates that each new value from the source is stored to the data series
triggering calculation of the average from the accumulated values and outputting the
result. If the number of values reaches the specified maximum, the data series is then full
and a new value from the source then overwrites the oldest value.
A device reboot or a configuration change deletes all the accumulated values.
Block averaging : This option provides two methods of averaging:
Arithmetic mean: The arithmetic mean, also called the average, is the sum of all values
of a data series divided by the number of values.
Vector average: A vector average is the average for a unit circle. The method is used,
for example, for mass flow rates in air conditioning engineering.
Edge triggering : The configured average type is calculated at the time of the trigger event
for the data series that has accumulated between two trigger events. The result is output
following calculation.
Level triggering : When a level moves from an active to inactive state, the average is
calculated from the values accumulated during the active level period.
Generate intermediate values: When enabled, the averages between trigger events are output
immediately after calculation (after each new source value).
1560

May 2011
4.1.5.5.4.14 PID-Regler
4.1.5.5.4.15 Pulse width modulation (PWM)
This software channel generates a square signal with a variable frequency and variable
pulse-pause ratio. The pulse-pause ratio is determined by the source.
Frequency / period : Enter either a fixed frequency/ time for the period of the base wave or
name a channel that provides the appropriate value.
Lower / Upper limit : Set here the minimum and maximum values for the pulse-pause ratio.
A pulse-pause ratio of 0% means that the PWM output is permanently switched off. A
pulse-pause ratio of 100% means that the PWM output is permanently switched on. The
range of source values is limited to the specified range.
4.1.5.5.4.16 Calculation channel
This software performs the mathematical formula that has been input. Any number of
sources can be linked within the formula. Each source is represented by a variable that can
assume either a constant value or the value from the specified channel.
Method
1.Set the required variables with Add Variable.
A variable named Var0 is created by default but its name can be changed.
2.Set whether the variable is to have a constant value (Manual input) or whether the
value is to be obtained from a channel (Channel).
3.Enter the formula expression in the Formula field.
Restrictions on variable names
1.The first character must be alphabetic.
The digits 0-9 are permitted within or at the end of the name.
2.Variable names must be unique (no repeat names in different channels).
3.A distinction is made between upper and lower case letters.
Input in the formula field must use the same variable names otherwise the formula is
invalid.

May 2011
1561
Example
The example calculates the difference between two channels, divides the result by 100
and adds an offset.
Input for the formula field
Operand1 operator operand2, e.g. pressure 1 - pressure2
Operator operand, e.g. !DigIO1
Function (operand), e.g. sin (pressure)
Function (operand1 , operand2), e.g. pow (pressure, 2)
1562

May 2011
Available calculation functions

Type of
Function
calculation
Basic
calculations
Logical
operations
Binary
operations
Data types
Syntax
Operand1
Operand2
Addition
bool, int, float
bool, int, float
Operand1 +
Operand2
Subtraction
bool, int, float
bool, int, float
Operand1 Operand2
Multiplication
bool, int, float
bool, int, float
Operand1 *
Operand2
Division
bool, int, float
bool, int, float
Operand1 /
Operand2
AND
bool, int, float
bool, int, float
Operand1 &&
Operand2
OR
bool, int, float
bool, int, float
Operand1 ||
Operand2
NOT
bool, int, float
! Operand1
AND
bool, int
bool, int
Operand1 &
Operand2
OR
bool, int
bool, int
Operand1 |
Operand2
XOR
bool, int
bool, int
Operand1 ^
Operand2
Negation
bool, int
bool, int
~Operand1
Left-shift
bool, int
bool, int
Operand1 <<
Operand2
bool, int
bool, int
Operand1 >>
Operand2
Minimum
bool, int, float
bool, int, float
MIN
(operand1,
operand2)
Maximum
bool, int, float
bool, int, float
MAX
(operand1,
(Move
operand1 to
the left by the
number of
places in
operand2)
Right-shift
(Move
operand1 to
the right by
the number of
places in
operand2)
Operations
with sets

May 2011
1563
Type of
Function
calculation
Data types
Operand1
Syntax
Operand2
operand2)
Matching
operations
Trig functions
Reverse trig.
Functions
Other
operations or
functions
Less than
bool, int, float,

string
bool, int, float,

string
Operand1 <
Operand2
Less than or
equal
bool, int, float,

string
bool, int, float,

string
Operand1 <=
Operand2
Greater than
bool, int, float,

string
bool, int, float,

string
Operand1 >
Operand2
Greater than
or equal
bool, int, float,

string
bool, int, float,

string
Operand1 >=
Operand2
Equals
bool, int, float,

string
bool, int, float,

string
Operand1 ==
Operand2
Not equal to
bool, int, float,

string
bool, int, float,

string
Operand1 !=
Operand2
Tangent
bool, int, float
TAN
(Operand1)
Cosine
bool, int, float
COS
(Operand1)
Sine
bool, int, float
SIN
(Operand1)
Arctangent
bool, int, float
ATAN
(Operand1)
Arccosine
bool, int, float
ACOS
(Operand1)
Arcsine
bool, int, float
ASIN
(Operand1)
Exponential
bool, int, float
EXP
(Operand1)
Power
bool, int, float
bool, int, float
POW(basis,
factor)
POW
(Operand1,
Operand2)
Square
bool, int, float
SQRT
(Operand1)
Modulo
bool, int, float
bool, int, float
Operand1 %
Operand2
Absolute
bool, int, float
ABS
(Operand1)
1564

May 2011
Type of
Function
calculation
Data types
Syntax
Operand1
Operand2
Natural
logarithm
bool, int, float
LN(Operand1)
Logarithms
(base 10)
bool, int, float
LOG
(Operand1)
Pi
PI
Euler's
number e
EX
Constants
Data types
bool: True or false
float: a floating point number or a fraction
int: an integer
4.1.5.5.4.17 Collective fault
This software channel monitors channels with boolean output signals to generate a common
alarm. Its output has an ON state when one of sources (Monitored channels) has an ON-state
(logical OR operation).
longer true. A reset event is then required to reset the alarm. If the Latching option is not
selected, the output for the batch alarm channel takes the state of the linked source.
Enabling Latching changes Reset trigger for latching. The alarm resets when a reset event
occurs, e.g. a Rising edge, in the given channel. The Reset priority option causes an alarm to
reset when the alarm condition is still true.
Method
Select one or more channels to trigger a batch alarm from the Available channels field
and click
to accept the selection.
Select one or more channels from Monitored channels and click

selection.

May 2011
to remove the
1565
4.1.5.5.4.18 Setpoint
This software channel enables the device to be used as a programmer. The setpoint table
enables the conditional procedures to be programmed that can be repeated as often as
required.
Table type: Use a global Global table (Global table setting) that has been created for the
device (refer to Global setpoint tables) or define a table for a specific channel (Local table
setting). In the latter case, a Table tab will appear.
Number of repeats: To determine whether and how often the program sequence will be
repeated automatically. After the last repeat the final setpoint remains in the table.
Start: The state (Level ) or edge ( Edge) of the specified channel starts the program at the
specified number of repetitions. Once the repetitions have been completed, a new or active
start event then sets the programmer to the beginning and restarts the program sequence.
Break: Pauses the program's execution, i.e. the current setpoint is retained for as long as
the specified channel has the set Level. The break pause channel has a higher priority than
the start channel, i.e. the start channel does not start the programmer while pause state is
active.
For Edge settings, the setpoint is retained from the arrival of the edge until the next edge.
An event here is also unable to give priority to a start channel over a pause status.
Reset: A reset event from the specified channel, sets the program to the beginning but
does not start it. The reset channel has the highest priority, i.e. the reset condition
prevents starting by a start event and can override up a pause status.
1566

May 2011
Table tab
t (fixed or variable) and value y (fixed or variable). Based on the previous value of yi-1 , the
t i value indicates how long will it take to achieve the yi value. The first line defines the
starting point of the procedure, so at least two pairs of values need to be entered. If a
variable is used it requires configuring via the Variables tab. This applies even when using a
global (external) setpoint table for the selected channel for
Method
1.For each table row (program step) enter the time value (Time) with the unit of time
2.Click Add.
3.Enter the required Global Settings.
Select a row to change the specified values. Then click Change. Delete removes the
selected row.
Numbers (constants) or variables can be used for times and values. The variables are then
defined via the Variables tab. For time input, the variable may be used as a value or as a
trigger:
system.

May 2011
1567
Global settings
Relative time: When enabled, input times are calculated as a difference to previous time
Point no.
Absolute
Relative
Example
In the table in the example, the value for var1 is held for the first 15 minutes. Then, after
each 6 minutes (Relative time setting ) the value increases to var2, then lowers to var3 via
var1, and then increases again to var1. A change and therefore output of the new value
takes place every second.
Cycle time: The cycle time for values to be output between two program steps.
intervals used in the table should be as integral multiples of the cycle time.
4.1.5.5.4.19 Statistics
This software channel enables a source to be evaluated with a range of statistical

functions.
Moving minimum / maximum : This minimum or maximum is calculated from a configured series
of values numbering from 2 to 1000 values.
triggering calculation of the minimum or maximum from the accumulated values and
outputting the result. If the number of values reaches the specified maximum, the data
series is then full and a new value from the source then overwrites the oldest value.
Block calculations: The number of values in the data series is determined by the frequency of
new source values within an interval set by trigger events. A change in the specified
channel creates the trigger event. Several statistical functions are available in this mode.
Edge triggering : The selected function is calculated at the time of the trigger event from the
data series that has accumulated between two trigger events. After calculation, the result
is output and all the accumulated valuesare deleted.
1568

May 2011
Level triggering : When a level moves from an active to inactive state, the selected function
is applied to the values accumulated during the active level period. The result is output and
the accumulated values then deleted.
Generate intermediate values: When enabled, the results between the trigger events are
immediately output after calculation (with each new source value).
Refer also to Trigger options .
Definitions
The minimum is the smallest value within the data series.
The maximum is the greatest value within the data series.
The variance is the mean square error relative to the mean.
The standard deviation is the square root of the variance (not the average deviation!).
The True RMS is the root from the sum of the squares of the values by the number of
values.
The arithmetic mean, also called the average, is the sum of all values of a data series
divided by the number of values.
The geometric mean is the Nth root from the product of n values.
The harmonic mean is the reciprocal from an average of reciprocals.
4.1.5.5.4.20 Status monitor
This software channel monitors the source and becomes active (switches to " On" ) when
the source contains the specified state.
Potential alarm functions and their meaning
Selection
Description
Alarm
Alarm, range error
Wire break
Wire breakage in monitored channel
Configuration error
Error in configuring the monitored channel
Invalid
Invalid value in the monitored channel
Measuring range
overrun
The measured value is above the range for the A / D converter
Measuring range
underrange
The measured value is below the range for the A / D converter
Hardware failure
Error in the hardware
Simulated value
An internally generated value for testing, e.g. from PROFIBUS
Not A Number
(NAN)
The result of a calculation is not a valid number,e.g. a root from a

negative number
Infinite value (INF)
The result of a calculation is infinity (infinity), e.g. division by zero
Default value
Default value for the monitored channel

May 2011
1569
Selection
Description
Forced value
The Forced value is a default value, e.g. in the event that a sensor is
defective at an analog channel
Scale range
overrun
The scale range has been exceeded
Scale range
underrun
The scale range has underrun
General warning
An error has occurred while transferring data, e.g. during a

PROFIBUS transmission
End of a trigger
block
End of a trigger block (data storage)
Input value out of

range
The value of the source channel can not be processed. There exists
a parameter error
4.1.5.5.4.21 Stopwatch
This software channel records the time between a start and a stop event. There are two
methods of starting and stopping the stopwatch:
1.Starting and stopping by means of an Edge or Level.
2.Starting from one channel (Edge only ) and stopping from another channel (Edge
only).
In the second example, the stopwatch can be restarted (Retriggerable) via a stop (Reset).
Enabling Reset at start resets the stopwatch to 0 at a start (Example 1, Case 1). When not
enabled the last value is retained and is added to the new interval (Example 1, Case 2).
1570

May 2011
Example 1
Case 1
Setting: Start / Stop at High level, Reset at start is enabled.
The stopwatch starts (red curve) at a high level in the start / stop channel (green
curve). Once the level reverts to low, recording stops. The recording time is the high
level time.

May 2011
1571
Case 2
Setting: Start / Stop at High level, Reset at start is disabled.
curve). The last measured value was 1.5478 seconds. Once the level reverts to low
(8.8582 seconds, calculated from the beginning of the high level), recording stops. The
last measured value is added to the the current "runtime". The stopwatch thus
contains the value of 10.4060 seconds.
1572

May 2011
Example 2
Case 1
Setting: Start at Rising edge, Reset at Rising edge, Reset at start is enabled.
With a rising edge in the start-channel (green curve) the stopwatch starts (red
curve). Because Reset at start is enabled, the stopwatch begins at 0. The rising edge of
the reset channel (blue curve) stops the stopwatch. The recording time is the time
between the two edges (6.2821 seconds).

May 2011
1573
Case 2
Setting: Start at Rising edge, Reset at Rising edge, Reset at start is enabled and
Retriggerable is enabled.
With the first rising edge of the start channel (green curve) the stopwatch starts (red
curve). Because Reset at start is enabled, the stopwatch begins at 0. The second rising
edge of the start channel resets the timer back to 0. The rising edge of the reset
channel (blue curve) stops the stopwatch. The recording time is the time between the
the start channel's final edge and the edge of the reset channel (2.2234 seconds).
1574

May 2011
4.1.5.5.4.22 System monitor
This software channel displays system information such as CPU load or memory usage.
Some of the system monitoring functions are already created in the

"System Monitoring" group.
Optional system information

Selection
Description
Unit
CPU usage
Displays the overall CPU usage.
CPU usage
application
Displays the main program's CPU usage (data

acquisition and calculation).
CPU Usage system
Displays the (operating) system's CPU usage.
Free memory
Displays the amount of free memory available.
MB
Used memory
Displays the amount of used memory.
MB
Up time system
Displays how long the operating system has been

working, i.e. the time that the device has been on
since the last reset.
Days
Up time application
Displays the time that the main program has been

running, i.e. the period following a Reset main
application or from a switching on of the device or
from a Reboot of the device.
Days
4.1.5.5.4.23 Trigger
This software channel uses the signal source to generate a logic signal for further
processing. Its output is active ("On") after a trigger event (trigger High level, Low level,
Rising edge, Falling edge or Edge (both)).
A trigger channel can be used for edge detection or recognition of a non-zero numeric
value.
4.1.5.5.4.24 Uhr

May 2011
1575
4.1.5.5.4.25 Alarmclock
This software channel allows the triggering of specific events at specified times. Depending
on the configuration, an alarm clock channel can generate one-off or repeat alarms for the
specified duration.
Active fields for Alarm settings depend on the repetition settings (Once, Hourly, Daily, Weekly,
Monthly or Yearly). Enter in the times in each active field. The alarm clock response is then
described in the text box above these fields. In an alarm, the alarm clock's output channel
switches to an active state ("On").
Alarm duration (s): Enter either a constant value (Manual value) or use Channel to select a
channel whose value determines the alarm duration as a time in seconds.
Reset: A reset event (a trigger via Level or Edge) ends the alarm duration and sets the alarm
clock output in a non-active state ("Off"). Alarm clock settings are not changed by a reset,
i.e. a follow-up alarm may trigger during the configured time.
4.1.5.5.4.26 Counter
This software channel counts events.

Count up trigger: The channel's counter is increased by one at the selected edge (Rising edge,
Falling edge or Edge (both)).
Count down trigger: The channel's counter is decreased by one at the selected edge (Rising
edge, Falling edge or Edge (both)).
Reset trigger: The channel's counter is output and reset internally to zero at the selected
edge (Rising edge, Falling edge or Edge (both)). When enabled Reset trigger the counter is
displayed only at a reset event unless the Generate intermediate values option has been
enabled.
Generate intermediate values: When enabled, the results are also output between Reset
events immediately after their calculation (at every counter change).
Output update trigger: The channel's counter is output at the selected edge (Rising edge,
1576

May 2011
Example of counting up
The counter (green curve) increases by one for each edge from the source channel
(orange curve) until the reset trigger becomes active. The Generate intermediate
values option is enabled so all new counter states are output immediately.

May 2011
1577
Example of counting down
The counter (green curve) decreases by one for each edge from the source channel
(orange curve) until the reset trigger becomes active. The Generate intermediate values
option is enabled so all new counter states are output immediately.
1578

May 2011
Example of outputting a value
At the time of value output (light blue curve) the counter is output. The option
Generate intermediate values is disabled so no intermediate values are output.
4.1.5.5.4.27 Timer
This software channel enables the changing of source signal times. This permits, for
example, new trigger times to be created for a subsequent channel or defined signals to be
generated for outputting to the process. A Response delay mode temporally compresses the
signal source and a Release delay temporally expands a signal.
Response delay: The timer channel starts the delay at the source's change to an active
state (High level or Low level trigger). After the delay. the timer output switches into an
active state ("On") for as long as the source retains an active state. If source's active
state is shorter than the delay, no reaction takes place at the timer output.

May 2011
1579
Release delay: The output of the timer channel becomes active ("On") when the source
switches to an active state (High level or Low level Trigger ) or edge triggering (Rising edge,
Falling edge or Edge (both) triggers). The same edge or a source change from active to
inactive starts the delay. After the delay, the timer's output becomes active ("Off").
The image shows the signal of a dropout delay with level triggering.
Retriggerable: This option enables a restart of the delay via other source trigger events
during the delay.
Delay (s): Enter either a constant value (Manual value) or use Channel to select an existing
channel whose value determines the delay as a time in seconds.
Reset: A reset event (a trigger via Level or Edge) ends the delay time and sets the timer
output in a non-active state ("Off"). The reset channel has a higher priority than the
source. This enables a reset state to block the timer function.
1580

May 2011
Example of a dropout delay
The source (purple curve) triggers with a rising edge. The delay is 2 seconds,
Retriggerable is not enabled.
The source (purple curve) triggers with a falling edge. The delay is 7 seconds,

May 2011
1581
Example of a reset
The source ( purple curve) triggers with a rising edge, The delay is controlled via a
channel, Retriggerable is not enabled, reset (green curve) is performed at Rising edge.
The source ( purple Triggers curve) with Rising edge, The delay time is controlled via a
channel, Retriggerable is not active, reset ( green Curve) is performed at a High level.
The timer (black curve) is then blocked for the duration of the reset signal.
4.1.5.5.5 Configuring interfaces
The device is equipped with multiple interfaces to enable communication with external
devices. These interfaces enable connection for data import or export to other PCs, PLCs,
and other third party equipment as well as for sensors using CAN bus.
Configuration of the Ethernet CAN-bus and COM interfaces takes place as for channels
directly from the channel view of the DataService Configurator and is described in this
section.
Configuring the Ethernet interface
Ethernet for Modbus configuration
Configuring the CAN bus
CAN connection
CAN protocol
1582

May 2011
CAN bus channel

Configuring the COM interfaces
COM port
PROFIBUS protocol
PROFIBUS channel
Modbus-RTU protocol (master/slave/channel)
User defined protocol
User defined input channel
User defined output channel
4.1.5.5.5.1 Ethernet connection
You can configure the lower of the two Ethernet connections in the channels tab (LAN2) to
enable you to connect the Expert Vibro device to a Modbus system.
Method for TCP client
1.From the interfaces context menu, select Create channel
Modbus TCP client protocol.
2.From the Modbus TCP client context menu, select Create channel
device.
3.From the Modus device context menu, select Create channel
Modbus output.
Modbus internal
Modbus input and/or
4.Double click the generated entry and make the settings for your data.
Method for TCP server
Modbus TCP server protocol.
2.From the Modbus TCP server context menu, select Create channel
device.
Modbus output.
Modbus internal
Modbus input and/or
4.1.5.5.5.2 CAN-Controller
Follow these steps to run a device via the CAN interface:

1.Configuring the basic settings of the CAN-Controller (this section)
2.Creating a CAN-Driver: CAN-Driver
3.Create one (or more) CAN-Bus-Channels
The CAN interface is displayed in the Channels tab with the CAN-symbol
. The CAN
interfaces are available in the Hardware defined view under the interface entry. The User
defined view lists all CAN interfaces directly below the device - as long as the user has not
already moved the modules or channels.

May 2011
1583
Double-click a CAN entry or select Properties from the context menu to display the
configuration dialog. Set the baud rate and the length of the identifier in the Main settings
tab. We recommend a unique Channelname. If required, amend Description and enter a
Location.
Main settings tab
Baudrate
between the devices:
For longer lines a lower baud rate should be selected to achieve error-free
communication.
The following are guidelines for CAN interfaces:
from 15 m: 1000 kBaud (factory device)
up to 30 m: 500kBaud
up to 45 m: 333.3kBaud
up to 60m: 250kBaud
up to 150m: 100kBaud
The baud rate must be the same for transmission and reception. Therefore, first determine
the baud rate for the equipment to be communicated to and use this value to set the CAN
interface's baud rate.
In brackets are noted the procotols, which implement that baud rate (CiA = CAN in
Automation, DCP = Delphin CAN Protocol)
Extended ID
A CAN system identifies data not by device addresses but by identifiers within a message.
The CAN specification defines identifiers at either 11 or 29 bits in length. The setting
determines which identifier length is being used.
When enabled this interface can be used with either an 11-bit or 29-bit (CAN 2.0B)
identifier. When not enabled, data transmission on the CAN bus is limited to an 11-bit
identifier (CAN 2.0A) and no other amendments can be made via CAN-Bus-Channels.
Create a CAN-Driver via the CAN-Controller context menu: Create channel
1584
CAN-Driver (RAW).

May 2011
The symbol
is then displayed for the CAN driver.
Double-click the CAN driver or select Properties from the context menu to display the
configuration dialog. Use the dialog to enter a name, location and description for the CANDriver.
A CAN-Bus-Channel is displayed with the symbol

. CAN-Bus-Channels are available
only when a CAN interface and CAN-Driver have been configured. To create additional
channels, select Create channel
CAN Protocol RAW).
CAN-Bus-Channel from the CAN-Driver context menu (
Double-click a CAN-Bus-Channel entry or select Properties from the context menu to display
the configuration dialog. The data to be entered depends on the type signal that is to be
sent to or received from the CAN-Bus-User. Therefore, obtain information on the format
and settings of the signal before entering data here.

May 2011
1585
Main settings tab

Data type settings
Data type
Specifies the data type for interpreting the payload data. Bit length, Byte order and
Word order are set and adjusted depending on the data type input. Startposition
within reference data , Scaling and Use channel as output are also set
according to data type.
Signed
Sets whether the integer data type is to be interpreted as signed or unsigned.
An 8-bit value would then be in the range -128 to 127 (2's complement) or 0 to
255. Floating values are always interpreted as signed. Bit-values make no
distinction between signed and unsigned.
Bit length
Sets the bit lengths for integer and floating data types. Byte order and Word order
are adjusted according to length value. This also applies to the numeric fields in
Startposition within reference data.
1586

May 2011
Encoding type
Specifies the encoding type for interpreting the transmitted/received data.
Byte order
The byte order (byte sequence) is a number, made up of several bytes, how
bytes are ordered to the address. BigEndian, also known as Motorola-format,
orders the most significant byte to the lowest address. LittleEndian, also known
as Intel-format, orders the least significant byte to the lowest address. Refer
also to http://de.wikipedia.org/wiki/Byte-Reihenfolge.
Word order
Like the byte order, word order orders Word data (1word = 2bytes = 16bits) to
addresses. In addition to determining byte order, a different word ordering may
be necessary.
Byte pattern
To display the different byte and word order combinations, a hex value (a
random number in the example) is shown with the resulting byte pattern of a
CAN message.
Startposition within reference data
Byte offset
The length of the payload data, i.e. the size of the data field (DATA) of a CAN
message, is limited to a maximum of 8 bytes. This allows multiple signals to be
transmitted within a CAN message as long as not all the 8 bytes per signal are
being used (this would only be the case with a binary-coded 64-bit floating
value). Enter the starting byte for this signal's payload data. In the example the
value of 4 means that, for example, two signals each with 2 bytes (binary-coded
16-bit integer value) would fit before the current signal and one signal behind it.
The maximum possible value of the offset is derived from the bit length of the
data type and is displayed to the right of the numeric field. Input is restricted to
the valid values, and the default is 0
Bit offset
This field is available only for the bit data type and binary encoding. The payload
bit in this data type can be between the 0 and seventh bytes. The byte offset is
also available for this data type. Input is restricted to the valid values, and the
default is 0
CAN ID
Extended ID
To set whether the CAN message uses 11 bit or 29 bit for the identifier. The
setting in this dialog is available only when Extended ID has been selected in the
CAN controller dialog.
ID
Enter a hexadecimal value for an ID either with 11bit (hex value of between 1
and 7FF) or 29bit (between 1 and 1FFFFFFF). Input is restricted to the valid
values.
The entry directly sets the identifier for CAN message to be received (or sent,
see Use channel as output) when 7FF or 1FFFFFFF is selected for Mask.

May 2011
1587
Mask
The filter provides the option to set the CAN bus channel to a whole group of
IDs. The range of input depends on the setting in Extended ID . The Mask value is
linked with the configured and received ID bit by bit AND. The CAN message will
be evaluated when the configured and received ID have the same value,
otherwise it will be ignored. An identifier group is established when the bits that
are to be ignored during evaluation are set to 0. Enter 7FF or 1FFFFFFF when a
Mask is not to be used.
Example of mask settings
ID 0x027 = 100111 = binary, Mask = 0x24 = 100100 binary (numbers with 0x are in
hexadecimal format); bit by bit AND operation results in 100100 in binary. The first four
digits of the link and ID are identical; last two digits only are 0 and 1. CAN messages
are then received with IDs that begin with 1001 (binary) and end with either two
zeroes or two ones, i.e. all messages with the (binary) IDs 100100, 100101, 100 110
and 100111.
Scaling
If CAN users send values that require conversion, enable Scaling and enter Min / Max
values to convert from the Input value into the Scale value .
If the Use channel as output option is used, scaling takes place in the opposite
direction: Enter the range from the source data in Scale value and the range for the
output signal in Output value.
Info
Without scaling, the channel's data type is that entered under Data
type. When scaling is enabled the floating data type is always used for
the channel.
This also applies when the channel is used as an output. When scaling
is enabled the channel must have the floating data type, otherwise the
type under Data type is used.
Scaling example
In the above image, a conversion from 4800 (pulses) to 300 (km / h) is performed.
1588

May 2011
Use channel as output

CAN-bus channels are configured by default as input channels, i.e. they receive data
via the CAN bus. This option enables the device to send data to other CAN bus users.
Enter either a constant (Manual value) or select an existing channel from Channel whose
value can be output. Selecting Application enables the output value to be manually set
via the DataService Configuratoror automatically set via a ProfiSignal application. The
source value is converted to the type given in Data type.
Inherite status (for Channel settings only): The status of the input channel is used but
not output to the CAN-Bus.
4.1.5.5.5.3 COM-Port
Follow these steps to run a device via the COM interface:

1.Select the interface mode for the COM-Ports (this section).
2.Set the communication parameters for the selected COM-Port.
To use the PROFIBUS interface, the following settings are also required:
3.Configure the PROFIBUS-Driver .
4.Create one (or more) channels: PROFIBUS-Channel.
The COM interface is displayed in the Channels tab with the COM-symbol
. The COM
defined view lists all COM interfaces directly below the device - as long as the user has not
Double-click a COM entry or select Properties from the context menu to display the
configuration dialog. We recommend entering a unique Channelname, amending Description
and entering a Location if required.
Main settings tab
Interface Mode
Select whether the connection is for PROFIBUS devices (selection PROFIBUS) or for other
protocols (select UART). Additional fields are displayed depending on selection, e.g. to set
interface parameters such as baud rate, data bits, or parity.

May 2011
1589
COM1 and COM2 are available for PROFIBUS devices as well as for UART (RS-485). COM3
and COM4 are exclusively for UART devices (RS-232).
Info
PROFIBUS communication is limited to fixed communication parameters. The
interface mode can therefore not be changed after a driver has been
created, i.e. a PROFIBUS-Driver functions only in the PROFIBUS interface
mode, other drivers in the UART mode.
The interface mode can be changed only after deletion of the driver.
Other settings are described in the following sections:

PROFIBUS-Driver
PROFIBUS-Channel
Create the PROFIBUS driver via the COM interface's context menu: Create channel
PROFIBUS-Driver .
We recommend entering a unique Channelname, amending Description and entering a Location

if required.
Select the PROFIBUS interface mode from the Main settings tab of the COM-Port. Set the
PROFIBUS address from which the Expert Vibro device is to be addressed by the PROFIBUS
master.
Info
Expert Vibro devices can only be operated as slaves to the PROFIBUS.
Only COM1 and COM2 can be used as PROFIBUS interfaces.
Expert Vibro devices have the address 126 as factory settings or after
Resetting the configuration (default configuration) via the web interface.
This address is a placeholder and does not exist in the PROFIBUS network.
PROFIBUS main settings (Main settings tab for the COM interface)
1590

May 2011
Slave address : Enter the address configured in the PROFIBUS master for the Expert
Vibro device (1 to 125).
Displayed information
IDENT , next to the slave address field, shows the identification number of the
PROFIBUS device's manufacturer. The PROFIBUS User Organization (PNO) has assigned
the identification number 0x09B8 to the Expert Vibro device.
The connection properties (Hardware and Port ) are displayed below the PROFIBUS
settings.
Main settings tab (PROFIBUS driver)

Use Slave redundancy to set up a redundant PROFIBUS interface. The interface is used
only when the intended interface (COM1) fails.
Select None when redundancy is not required.
Select PNO_2212_V1.2 to set up a redundant PROFIBUS interface.
The PROFIBUS User Organization (PNO), in its PNO Paper No. 2212 V1.2 from
November 2004, describes the setting up of a redundant PROFIBUS interface.
The Custom option is reserved for customer enhancements.
After selecting Slave redundancy, Backup COM-Port shows that the COM2 interface is to
be used for backups.
Info
Slave redundancy can be selected only when COM2 is available for
backup operations. This requires that the COM2-Port, like COM1,
functions in the PROFIBUS interface mode and no PROFIBUS-Driver has
been configured to the COM2-Port. The dialog displays any incorrect
settings.
As soon as Slave redundancy is configured for the PROFIBUS-Driver to
COM1, a PROFIBUS-Driver can no longer be created on COM2.
The symbol
is then displayed for the driver channel following configuration. Then create
and configure the required PROFIBUS-Channels (Signals).

May 2011
1591
To create PROFIBUS-Channels requires configuration of a COM-Port in the PROFIBUS

interface mode and a PROFIBUS-Driver. Select Create channel PROFIBUS-Channel from the
PROFIBUS-Driver context menu (
, PROFIBUS Protocol) to create channels for PROFIBUS
signals. A PROFIBUS-Channel is displayed with the symbol
Double-click a PROFIBUS-Channel entry or select Properties from the context menu to

display the configuration dialog. The data to be entered depends on the signal to be
received from the PROFIBUS-User. Therefore, obtain information on the format and settings
of the PROFIBUS signal before entering data here.
Main settings tab
Data type settings

Data type
Specifies the data type for interpreting the transmitted data. Bit length, Byte order
and Word order are set and adjusted depending on the data type input.
Startposition within reference data and Scaling are set according to data type.
Signed
Bit length
1592

May 2011
Encoding type
Specifies the encoding type for interpreting the transmitted data.
Byte order
The byte order (byte sequence) is a number, made up of several bytes, that
sets allocates byte-mapping to address. BigEndian, also known as Motorolaformat, orders the most significant byte to the lowest address. LittleEndian, also
known as Intel-format, orders the least significant byte to the lowest address.
Refer also to http://de.wikipedia.org/wiki/Byte-Reihenfolge.
Word order
be necessary.
Byte pattern
random number in the example) is shown with at the resulting byte pattern.
Byte offset
The length of the payload data, i.e. the size of the data field (DU) of a
PROFIBUS message, is limited to a maximum of 244 bytes. This enables multiple
signals to be transmitted within a message. Enter the starting byte for this
signal's payload data. The maximum possible value of the offset is derived from
the bit length of the data type and is displayed to the right of the numeric field.
Input is restricted to the valid values, and the default is 0
Info
When configuring, the Profibus master receives information on the
number of I/O channels of its slave, i.e. including the Expert Vibro
PROFIBUS slave. At run time, i.e. when data exchange is taking place,
the master sends the I/O configuration to the slave. If the configured
byte offset in the Expert Vibro device greater than the I/O addresses of
the transmitted master configuration, the Expert Vibro device displays a
configuration error in the channel status.
Bit offset
default is 0.

May 2011
1593
Scaling
If the PROFIBUS master sends values that require conversion, enable Scaling and enter
Min / Max values to convert from the Input value into the Scale value.
Info
the channel.
Use the Main settings tab to enter the general settings for the interface (Baud rate, number
of data bits etc.) for the relevant COM interface.
Create the Modbus protocol driver via the COM interface's context menu: Create channel
Modbus-RTU master/slave protocol.
We recommend you assign a unique channel name, amend the description, and enter, if
required, a location.
Following configuration, the
symbol is displayed for a Modbus-RTU master and
for
a Modbus-RTU slave. Then create and configure the required channels for the Modbus
master and/or Modbus slave.
Use the context menu from the Modbus protocol (
, Modbus RTU Master) to create a
Modbus device: Modbus external device. To call up the configurations dialog, double click the
Modbus Device menu item or select Properties from the context menu. Use the dialog to enter
a name, location and description for the external device. Settings are also made here for
the device's (own) address in the Modbus network and the parameters for querying Modbus
users.
Main settings tab
1594

May 2011
Device name
Device address
Sets the address for the master device.
Settings for Host name and Port can not be changed.
Time settings
Poll cycle
Sets the the time for cyclical data querying. Existing Modbus users are (re)-queried
after the set time. The time must be long enough in relation to the Pause time and
the number of channels (users) otherwise you will receive an error message when
closing the dialog. The values entered will then not be saved.
Timeout
Sets the maximum permissible time between a request and a response before and
error status occurs. In the event of an error, a "wire-break" status is displayed (refer
also to the table in status monitoring). The time must be short enough in relation to
the Poll cycle otherwise you will receive an error message when closing the dialog.
The values entered will then not be saved.
Pause
Sets the waiting time for a query from more than one channel within a poll cycle. The
time must be short enough for all channels to be queried within the time entered
under Poll cycle otherwise you will receive an error message when closing the dialog.
Sequential query
If you enable this option, only one request telegram will be generated for sequential
Modbus addresses instead of a separate request telegram for each address.
The
symbol is displayed following configuration. Then create and configure the
required Modbus channels (signals).
To create a Modbus channel, use the context menu for the Modbus protocol (
, Modbus
RTU Slave): Modbus internal device. To call up the configurations dialog, double click the
Modbus Device menu item or select Properties from the context menu. You can use the dialog
to set the name, location and description under which the Expert Vibro device is to
function in the Modbus network. You also make the Expert Vibro device's address settings
here for the Modbus network.

May 2011
1595
Main settings tab
Device name
Device address
Sets the address for the Expert Vibro device (slave).
The Port setting can not be changed.
The
Depending on whether you wish to read in or output a signal, select Create channel
output or Modbus input. A Modbus input channel is displayed with the
Modbus
symbol, a Modbus
output channel with

.
Refer also to Settings for all dialogs.
Main settings
1596

May 2011
Function code: Select what is to be read in (input) or written to (output). Only permissible
data is provided, e.g. FC01 to FC04 for inputs and FC05/06 as well as FC15/16 for outputs.
This setting has an effect on the data type settings.
Reference: The number before the input field indicates the storage side and therefore the
type of register.
Input is as a preset decimal format and is limited to the values that are available. You can
use Description as, to set whether the input is to be used as Address or Register and whether
the format is decimal or hexadecimal (Hex).
Data type settings
The settings are dependent on the Functions code input and whether the channel is an
input or output.
Data type
Specifies the data type for interpreting the data. Bit length, Byte order and Word
order are set and adjusted depending on the data type. Start position in payload
data, Scaling and Use channel as output are also set according to data type.
Signed
Bit length
Start position in data.
Encoding type
Displays the encoding type used for interpreting the transmitted/received data.
Byte order
sets how bytes are ordered to the address. BigEndian, also known as Motorolaformat, orders the most significant byte to the lowest address. LittleEndian, also
Refer also to http://en.wikipedia.org/wiki/Endianness.
Word order
be necessary.
Byte pattern (for input channels only)
message.
Scaling
If a Modbus user sends values that require conversion, enable Scaling and enter Min /
Max values to convert from the Measurement value into the Scale value .

May 2011
1597
Info
Without scaling, the channel's Data type is used When scaling is enabled,
the floating data type is always used for the channel.
is enabled, the channel must have the floating data type, otherwise
you have to use the type under Data type.
Scaling example
In the above image a conversion takes place from 2000 (integer value) to 200 (C), i.e.
it returns a decimal point despite transmission of an integer (whole number).
Using the channel as an output
If you create a Modbus output channel, you can send data from the Expert Vibro
device to other Modbus users.
You enter the data for the message to be sent in a similar way to a Modbus input. You
must also enter the Source (of the signal).
Enter either a constant for the Source (Manual value) or select Channel and an existing
channel in the device whose value is to be output. Selecting Application enables the
output value to be manually set via the DataService Configurator or automatically set
via a ProfiSignal application. The source type is converted to the type given in Data type
(refer also to Scaling).
Inherit status (for Channel settings only): The status of the input channel is used but not
output to the CAN bus.
Asynchronous set: When enabled, the output value is transmitted as soon as the value
changes, i.e. without delay. Otherwise a new value is transmitted at the next cycle.
1598

May 2011
Enter the general settings for the interface (Baud rate, number of data bits etc.) under
the Main settings tab for the relevant COM interface.
User defined protocol.
We recommend a unique Channel name, amendment to the Description and, if necessary,

entry of a Location.
of data bits etc.) for the relevant COM interface. The Main settings tab is described in the
following and then how input and output channels are created.
Main settings
This tab is enables you to make settings that apply to all channels (inputs and outputs) of
the interface. But it is also possible to make individual settings for each channel for
pollstring and poll cycle and/or output time. Termination settings apply for all input and
output channels.

May 2011
1599
Cyclic query: General settings on whether data is to be cyclically queried for all input
channels and/or sent for all output channels. Do not enable the option if you wish to make
the settings per channel.
Time settings
Poll cycle
Sets the the time for the cyclical data query. The current user is (re)-queried
after this time has elapsed. The time must be long enough in relation to the
Pause time and the number of channels (participants) otherwise you will receive
an error message when closing the dialog. The values entered will then not be
saved.
Timeout
Sets the maximum permissible time between a request and a response before an
error status occurs. In the event of an error, a "wire break" status is displayed
after the number of timeouts given under Wire break create after. Refer also to the
table in status monitoring. The time must be short enough in relation to the time
in Poll cycle otherwise you will receive an error message when closing the dialog.
Pause
Sets the waiting time for a request from more than one channel within a poll
cycle. The time must be short enough for all channels to be queried within the
time entered under Poll cycle otherwise you will receive an error message when
Pollstring
Enter here a character string for all output channels that is to be output which
prompts the user to send its data in the event that this is required. If you require data
from several channels with different pollstrings, do not enable the option here but enter
instead the pollstring separately for each the relevant input channel.
Enter the string as text. ASCII characters that can not be entered directly, e.g.
carriage return (CR) or line feed (LF), can be entered using % and the ASCII value in
hexadecimal format: Enter CR as %0D and LF as %0A.
Termination
This setting applies to input and output channels for the interface and can not be
changed for a specific channel. Input for Termination symbol and Bus idle characters are
however used alternately. For example, an input message is considered ended
according either to the Termination symbol or the number of characters.
Termination symbol
One or more ASCII characters that indicate the end of a message. If the
characters can not be sent, or if you do not enter any characters, the Bus idle
characters will be used for identification.
Enter the characters as text. ASCII characters that can not be entered directly,
e.g. carriage return (CR) or line feed (LF), can be entered using % and the ASCII
value in hexadecimal format: Enter CR as %0D and LF as %0A.
You can enter only one end sequence. Multiple end sequences are not possible.
1600

May 2011
Bus idle characters

Enter the time of the pause after which a message should be considered as
ended when no termination symbol has been sent. Do not enter a time value.
Enter instead the number of characters that can be transmitted in this time, e.g.
3.5 characters. A conversion according to the interface's baud rate is then not
required.
Decimal separator
Enter the decimal separator for the transmission of numerics. The character will
be used for all channels which transmit numerics.
Settings for user defined input channels take place mainly via two tabs:
1.Main settings tab
Contains settings for the data type and scaling of the received data.
2.Input tab
Contains settings for the frequency of receiving messages , Pollstring and the
decoding (filtering) of received data.
The other tabs contain standard settings (refer also to Settings for all dialogs).
Use this tab to set how received (user) data is to be converted into a measurement value.
Use the Input tab for preventing conversion for all the characters/bytes that are being sent
(by using the Filter and Offset fields).
Data type settings

Data type
Specifies the data type for interpreting the transmitted user data. Bit length, Byte
order and Word order are set and adjusted depending on the data type.

May 2011
1601
Signed
Bit length
Encoding type
Displays the encoding type used for interpreting the transmitted data. Binary
(the received bytes are interpreted as binary data). ASCII (ASCII characters,
i.e. text) or ASCIIHex (the received ASCII characters are interpreted as
hexadecimals pairs). The data is converted into the given data type after being
received.
Byte order
sets how bytes are ordered for the address. BigEndian, also known as Motorolaformat, orders the most significant byte to the lowest address. LittleEndian, also
Word order
be necessary.
Byte pattern
message.
Scaling
If the sent values require conversion, enable Scaling and enter Min / Max values to
convert from the Measurement value into the Scale value .
Info
Without scaling, the channel's data type is used that you entered
under Data type. When scaling is enabled, the floating data type is
always used for the channel.
Scaling example
1602

May 2011
Use this tab to set the frequency at which data should/must be received, whether data
output needs to be "prompted" and, if required, how data is to be extracted from a string.
Time settings
Timeout
Sets the maximum permissible time that may elapse between a query (Pollstring)
and its answer, or between two sequential answers (without Pollstring) before an
error status is registered. In the event of an error, a "wire-break" status is
displayed (refer also to the table in status monitoring).
Pause
Sets the waiting time between two queries using a Pollstring. The Pollstring is
resent once this time has elapsed.
Polled
Pollstring
The string entered here will be sent to the user according to the time frame
defined using Pause. This is required when a user sends an answer (a value) only
after the user has been "queried". Leave the field empty if the user doesn't
require prompting to send.
carriage return (CR) or line feed (LF), can be entered using % and the ASCII
Filter
If the user sends multiple answers (messages or comments), you can use a filter
to filter the answers you require from this user/channel. Enter the message's
beginning, e.g. $GPGGA.
Delimiter
If the filtered message contains multiple elements, use this field to determine the
character that separates the elements and which element (umpteenth Element) is
to be used for this channel.

May 2011
1603
Decoding
Offset
Truncates the first character of the message set under Polled. This means the
message is evaluated from this offset. You can set the offset from the absolute
beginning of the message (default) or relative to the first character in Filter
(Offset relative to filter).
Maximum length
Evaluates the message only up to the character given here. All other characters
are ignored.
Set how a value is to be output in the Main settings tab. Use the Timing tab if you need to
use extra pauses for a message, e.g. to send an initialization to a device that then needs
time to perform the initialization.
Main settings tab
Data type settings
Output is always as an ASCII string. However, you can set the format of the value to
be output using the data type setting.
Data type
Sets the data type for the signal that is to be used. The value for other entries
depends on the settings here, e.g. an Integer data type has no post decimals
places but can be output with post decimal places, which are then always
zeroes.
For a String data type, enter its Length.
1604

May 2011
Pre decimal place

Sets the number of decimal places before the decimal point/separator. The
decimal separator is output only when at least one post decimal place is output.
Leading zeroes
Sets whether the pre decimal places are to include leading zeroes when the
number is less than the given decimal places. This means that the same number
of characters are always sent.
Post decimal place
Sets the number of decimal places to be output.
Always sign
Sets that positive as well as negative signs can be sent. The sign does not
count as a pre decimal place.
Example
Displays the formatting of an imaginary number according to the settings made.
Format
Sets what is to be sent, e.g. value and unit for the channel. Don't delete the required
placeholders including % signs. You can send only one channel (value) but any number
of placeholders for other information, e.g. for outputting the current date and time.
You can also enter text instead of placeholders, e.g. text to be sent for initialization.
For example, by using the initialization string "Measure:Volt:DC" you can switch a
multimeter to DC measurement.
To send output channel data, use the following placeholders:
%VALUE%: Channel value.
%STATUS%: Channel status.
%UNIT%: Channel unit.
%NAME%: Output channel name.
%DESCRIPTION%: Output channel description.
%LOCATION%: Output channel location.
%ID%: Output channel ID.
To send source channel data, use the following placeholders:
%UNITSOURCE%: Source channel unit.
%NAMESOURCE%: Source channel name.
%DESCRIPTIONSOURCE%: Source channel description.
%LOCATIONSOURCE%: Source channel location.
%IDSOURCE%: Channel ID for the source channel.
The following general placeholders are available for you to use:
%DATETIME%: Current date and time.
%HOUR%: Current time.
%MINUTE%: Current minute.
%SECOND%: Current seconds.
%YEAR2%: Current year as 2 digits.
%MONTH%: Current month.
%DAY%: Current day.

May 2011
1605
To output ASCII special characters, the following placeholders are also available:
%NUL%: 00 in hexadecimal format.
%SOH%: 01 in hexadecimal format.
%STX%: 02 in hexadecimal format.
%ETX%: 03 in hexadecimal format.
%EOT%: 04 in hexadecimal format.
%ENQ%:05 in hexadecimal format.
%ACK%:06 in hexadecimal format.
%BEL%:07 in hexadecimal format.
%BS%: 08 in hexadecimal format.
%TAB%: 09 in hexadecimal format.
%LF%: 0A in hexadecimal format.
%VT%: 0B in hexadecimal format.
%FF%: 0C in hexadecimal format.
%CR%: 0D in hexadecimal format.
%SO%: 0E in hexadecimal format.
%SI%: 0F in hexadecimal format.
%DLE%: 10 in hexadecimal format.
%DC1%: 11 in hexadecimal format.
%NAK%: 15 in hexadecimal format.
%SYN%: 16 in hexadecimal format.
%ETB%: 17 in hexadecimal format.
%CAN%: 18 in hexadecimal format.
%EM%: 19 in hexadecimal format.
%SUB%: 1A in hexadecimal format.
%ESC%: 1B in hexadecimal format.
%FS%: 1C in hexadecimal format.
%GS%: 1D in hexadecimal format.
%RS%: 1E in hexadecimal format.
%US%: 1F in hexadecimal format.
Source
Select a channel whose value is to be output. Enter the %STATUS% placeholder in
the Format field so that you can inherit and therefore output the source channel's
status.
Output
Cyclic
Sets the frequency of sending. The next value is sent after the time given here
has elapsed.
Adaptive
This option means that a new value is sent only when the value to be sent has
changed.
Never
This option is intended for the sending of an initialization (next option). The
string entered in the Format field is then sent only once for initialization and
never cyclically or adaptively.
1606

May 2011
Initialization
This option enables you to set initialization strings, e.g. "Measure:Volt:DC" to
switch a multimeter to DC measurement. If you have to send more than one
sequence , enter a number under Sequence on whether the string entered under
Format is to be sent first (Sequence = 1) or second (Sequence = 2) and so on. Use
the Timing tab to set a pause following the sending of the initialization string in
order to give the device time to process the instruction.
Response expected
Enable this option so that the next output takes place only when the user has answered
the previous sending with a string. The answer string itself is only expected and therefore
not evaluated. If the answer contains relevant information, you must define an input
channel and then have the answer evaluated.
Timing
Enable Use individual time settings and enter the required pause times, e.g. for when an
initialization string is sent (refer to output: Never). Pause times are unnecessary for all other
cases because sending then takes place either cyclically or adaptively.

May 2011
1607
4.1.5.5.6 Device memory
Setting subgroups within the "Memory" enables a more efficient partitioning of the memory.
From the "Memory" context menu select Create channel Storage group. Divide the available
memory among these groups and use the Channel list tab to set how often the groups
channels are to be saved.
Refer also to Settings for all dialogs , Data transfer to USB memory stick.
Memory group settings, Main settings tab
Use this tab to set the Size of the memory that this group may use. The memory can
either be written until full (End storage process when memory full) or configured as a ring
buffer. As a ring buffer, the current value overwrites the oldest value when the
memory is full.
An alternative to the ring buffer is the Erase trigger function. Enter a (digital) channel as
the trigger for the deletion. A calculation channel can be used that monitors memory
capacity and then deletes the memory when a specified capacity has been reached.
Store time change : When enabled, time changes, such as synchronizing using NTP time,
triggers extra saving to the memory group from the channels in the channel list. The
data can then be used to identify the cause of any "time mismatches".
Store config change: When enabled, saves changes to channel configurations in this
memory group along with the time of change, version number and configuration file
history in the device (.. / pm / config / channels / backup / directory).
1608

May 2011
Memory group settings, Storage mode tab

Save initial values: When enabled, the current values from all channels in the
channel list are saved when the memory group starts. The storage group starts
via activation in this dialogue or following the switching on / rebooting of the
device and active storage group.
Cycle store value: When enabled, saving takes place at the given interval
irrespective of any trigger or tolerance settings.
Continuous: The current value is saved when a tolerance is exceeded depending
on the tolerance settings for the channel in the channel list.
Single step : Functions as for the edge trigger but without pre-or post-trigger
times.
Edge trigger: Saving takes places with a change (edge) in a (digital) signal.
Level trigger: Measurement data is saved as long as the given level remains active.
For Edge trigger and Level trigger options, an additional Pre-trigger time and Post-trigger time
can be assigned to the trigger event. Data is then stored within these times when a
value exceeds the tolerance settings for the respective channel.

May 2011
1609
Storage group settings, Channellist tab
Select the channels from which data is to be stored: Mark channel and click
How often measurement data is saved depends on different settings (refer also to
Storage mode) and may also be influenced by the Tolerance for newly added channels:
Online: The tolerances given in the Advanced settings tab (Data reduction) will also
be saved. The measurement data is saved when it deviates from the previously
saved data by more than the value given here. The valid value for the channel is
displayed - after acquisition - in the field Stored Channels.
Default value: The value specified here is used for the channel that is to be
assigned to the group. The tolerance is valid only for saving to this memory
group. For everything else, such as a calculation using this channel, the valid
tolerance is the one assigned to this channel. The valid value for the channel is
1610

May 2011
If Relative tolerance is enabled, data is not displayed according to the channel's

unit but as a percentage based on Conversion in the Main settings tab.
Info
Make the Tolerance for channels being saved settings before clicking
. A subsequent change to the settings will be ineffective. For the
change to be effective, the channel first needs to be deleted and then
reinstated.
Settings for USB export
Activate this option to export data from a memory group to a USB memory stick:
Allowed .
Refer also to Data transfer to USB memory stick.
4.1.5.5.7 Data transfer to USB memory stick
Acquired data can be copied to a USB memory stick without the device having to be
connected to a PC. There are two options for the transfer of data:
1.Data transfer without configuration
2.Data transfer with the type of transfer configured into device
The prerequisite for both options is the capability of transferring data to a USB memory
stick. Refer to device memory.

May 2011
1611
Info
Use a FAT32-formatted USB flash drive with an LED that blinks during the
data transfer.
Data transfer without configuration

1.Insert the USB memory stick.
2.After detection of the USB memory stick, data is transferred to the USB stick from
the enabled storage groups. The transfer is complete when the USB stick's LED stops
blinking.
The data is only copied. It is not deleted from the device!
3.Remove the USB memory stick.
Configuring data transfer
1.Insert the USB memory stick into a PC running the DataService Configurator.
2.Open the configuration dialog from the "memory" group's Save USB export Configuration
option.
3.Select the required (memory) mode:

One-off: Data is saved fro the specified period.
Incrementally : Data is saved that has been acquired since the last save. Saving takes
place after removal and reinsertion of the USB memory stick.
4.Enter the USB memory stick's drive (in the dialog's lower left corner).
5.Click Save.
The configuration file is saved in XML format to the USB memory stick.
1612

May 2011
As soon as you insert the USB stick in the device, the XML configuration file is read out and
the corresponding data transferred to the USB stick. The data is only copied. It is not
deleted from the device!
Saving ends when either:
All data from the selected memory group(s) for the set time periods has been saved
or
The date has been saved with a time-stamp for the current time.
The transfer is complete when the USB stick's LED stops blinking. A new saving process
begins only by the removal and reinsertion of the stick.

May 2011
1613
4.1.6
Connection examples
This section gives examples of typical sensor and actuator connections. It explains the
available connection options that exist and how sensors and actuators are configured.
4.1.6.1 Connecting sensors
Measuring voltages at an analog input

Info
The largest measurement range is 10 V bipolar or 10 V unipolar.
The smallest range is 156 mV bipolar and 156 mV unipolar.
20 mA current measurement at an analog input

Sensors with current signals require connection of a load resistor at the device's input
terminals. Resistors are available as accessories.
Info
The load resistance must be between 10
1614
and 500

May 2011
Measuring temperatures with a thermocouple at an analog input

Thermocouples can be directly connected. Use the configuration dialog to set the type
(J, K, T, R, etc.).
Info
The compensation required for the thermocouple is integrated into the
device. Enter the compensation channel as the Reference Junction in
the Extended settings tab (for the same I / O module).
Measuring temperatures / resistances at an analog input

Connect resistor or temperature probes with 4-wire technology when possible. This
connection method provides the best results since current path and measuring circuit
are separate. Measurement current in 2- or 3-wire connectors flows through both, or
one, measurement lines. Voltage drops on the measuring line can therefore distort
readings.
Several constant-power sources are available within the device to supply power.
Info
These sources deliver 1 mA.
they can measure resistance values ofup to 10k .

May 2011
1615
Sensor at a digital input

Digital inputs have two variants:
Input for level (recognition)
Inputs for frequency measurement or counting
Not every input is usable for both functions.
Level detection
Info
The I / O modules AAST, ADFT, AMDT, DIOT, and IOIT OTPT have
digital inputs for level detection.
For reliable detection the input signal must have a "low" level ranging
from 0 ... 1.5 V, a "high" level ranging from 3.5 ... 90 V and a minimum
pulse width of 1 ms. A maximum of 50 signal changes per second
(maximum signal frequency) can be recorded.
1616

May 2011
Frequency measurement/ pulse counting
Info
The I / O modules ADFT, and AMDT DIOT have digital inputs for
frequency measurement / pulse counting.
For reliable detection the input signal must have a "low" level ranging
from 0 ... 1.5V and a "high" level ranging from 3.5 ... 90V. The maximum
measurable signal frequencies are 50 kHz for the ADFT and AMDT
module and 30 kHz for the DIOT module.
4.1.6.2 Connecting actuators
Actuator at an analog output
Info
The I / O modules AAST and ADIT have current sources as analog
outputs.
The maximum permissible shunt resistance of the actuator is 650 .

May 2011
1617
Info
The I / O modules ADFT and AMDT have voltage sources as analog
outputs.
The minimum permissible load resistance of the actuator is 2.5k .
Actuator at a digital output, resistive load

To connect an actuator at a digital output requires an external supply voltage of
between 5 and 50V DC (24 V in the examples).
Info
The maximum switching voltage is 50V and a maximum switching
current of 2.5A.
1618

May 2011
Actuator at a digital output, inductive load

between 5 and 50VDC (24 V in the examples).
Info
The maximum switching voltage is 50 V, and a maximum switching
current of 2.5 A.
To protect the output's electronic switches we recommend switching to
recovery diodes in parallel with inductive loads.

May 2011
1619
4.1.7
The section contains general information and recommendations on using measurement

technology.
4.1.7.1 Galvanic isolation

A device's I/O modules, interfaces, Ethernet, Ext. BUS, CAN, COM1, COM2, COM3 and
COM4 are all galvanically isolated from the central unit (CPU and power) as well as from
each other. The CAN ports and COM1 are not isolated from each other and nor is COM2 to
COM3. For system reasons, the USB interface is not isolated.
The diagram shows the individual galvanic isolating properties of the device.
Refer also to shielding.
1620

May 2011
4.1.7.2 Earthing
The PE terminal for the power supply is the ground terminal for the device. This terminal is
internally connected to the metal housings of the USB-/LAN and COM ports but has no
connection to the 0 V terminal(s).
Connect the PE terminal with a 2.5 mm2 cable to the protective earth of your power
supply.
Refer also to Shielding , Galvanic isolation.
4.1.7.3 Earth loops

When linking a sensor, measurement device, and computer together then establishes
connections between different ground points. Unless the individual devices are connected
to protective earth, this electro conductive connection creates an electrical circuit
between the devices. The result is a so called earth or ground loop (shown red in the
example).
This can have the following effects:
In practice the earthing points U1 ... U3 shown in the example do not necessarily
possess equal potential. Constant or changing potential differences can occur
between the earthing points due to the earthing plan and wiring. Compensating
currents then occur in the sensor and communication circuits.
Interference in the sensor or communication circuits, e.g. through electromagnetic
fields, enable parasitic currents to occur within the circuit.
Compensation and parasitic currents lead to interference or noise voltage at the input of
the measuring instrument and thus creating constant or fluctuating measurement errors.

May 2011
1621
Prevent earth loops!
Earth loop between sensormeasurement device

Galvanic isolation of the I / O modules to the central device means earth loops via the
sensor circuit, as shown in the example, can not occur within the device. Earth loops can
however occur between the sensors of different channels of a module.
To avoid such loops, we recommend the use of earth-free sensors or signal sources.
Refer also to potential differences.

Earth loop between measuring devicecomputer
Most of the device's interfaces are galvanically isolated to each other and to the central
device. The earth loop in the communication circuit, as shown in the example, does not
occur with the device.
Use these interfaces to connect the device to PCs, PLCs or to the equipment from other
manufacturers.
Refer also galvanic isolation.
4.1.7.4 Shielding
Measurement signals can be disrupted by the occurrence of magnetic and electric fields
across the measuring circuits, e.g. generated by neighbouring current-carrying circuits.
Shielded cables should therefore always be used for sensor circuitry and kept at least 50
cm away from other current-carrying circuits.
The smaller the sensor signal and/or the higher the sensor impedance, the more important
is good shielding for low noise, accurate readings.
To prevent earth loops, earth the shield on one side of the circuit only (see example).
1622

May 2011
a) Sensors without earth

Earthing of the shield is in this case one-sided and directly at the device (PE connection on
the power supply).
Refer also to earthing.
b) Sensors with earthing

When the use of earth-free sensors is not possible, earth the shield only or attach it to the
sensor's earth potential (see example).
4.1.7.5 ESD protection

The ADGT 3.0 module has an earth terminal specifically for ESD protection (ESD, E lectro- S
tatic D ischarge ) of the inputs.
Connect this with the PE labelled terminal (33) via a 2.5 mm2 cable to the protective
earth of your power supply.

May 2011
1623
The other modules do not have ESD protection. Therefore, discharge

static before coming into contact with the I / O modules. Simply touch a
housing with protective earth, the earth contact of the mains socket, or a
radiator or water pipe. Modules can be damaged if static is not discharged.
4.1.7.6 Potential differences

Potential differences can, in principle, always occur between reference potentials of
multiple-sensor signals that are connected to the analog inputs of a I/O module. The
following figure shows the sensor signals as green arrows and Umess , and the potential
difference between the two sensor signals as an orange arrow and UDifference.
The reference potential of a measurement circuit of an analog input for a device occurs by
a change of channel of the sensors' different reference potentials. Depending on the input
circuit of the various I / O modules of a device, the difference voltage U Difference between
certain channels, may not exceed specified maximum values. These are the "Permissible
differential voltages from channel to channel" specified in the Technical specifications.
1624

May 2011
WARNING!
Connector terminals on I/O modules carry electrical potential from the attached
sensors/actuators.
Before coming into contact with the connectors, ensure the power is off. There
should be no voltage at the connector terminals when the attached sensors
have varying potentials or earthed high potentials, e.g. when measuring the
electrical current of a mains voltage phase.
determined from the Measurement data.
Info
If the connected sensors have different potentials and high currents are
expected in the event of a short circuit between the sensor potentials,
take measures to protect the device and the measurement installation from
subsequent damage.

May 2011
1625
4.1.8
Main device
AAST, ADGT, ADIT and ADVTADGT, ADIT and ADVT
ADFT
DIOT, IOIT and OTPTDIOT and IOIT
4.1.8.1 Main device
Weight, approx.
1kg
Dimensions
200 x 73 x 120mm
Material
Plastic housing
Humidity
20 ... 80%, non-condensing
Temperature range
-20 ... 60 C
Supply 1)
1)
12 ... 28 V
AC
10% or 12 ... 36 V
DC
10%
Power input, approx.
10 W
Mounting
Rail 35 mm according to DIN EN 60715 or screw fixing
Processor
400 MHz PowerPC with integrated FPU
ROM
8 MB of solid state FlashROM
SRAM
0.5 MB, battery-backed
DRAM
128 MB of DDR
Real-time clock
Resolution of 100 ms, battery-backed
Backup battery
CR2450 lithium battery, backup time of at least 10 years
Web Server
Basic configuration, firmware upgrade, loading and saving

configuration
The modules AMDT and ADFT require a supply of at least 18 V
A C / DC
Ethernet interface
Ethernet standards
10/100Base-T (half and full duplex), autonegotiation
Protocols
TCP/IP, UDP, ICMP, HTTP, SMTP, NTP Modbus TCP

Client/Server
Connector
RJ45 (8-pin connector TP)
1626

May 2011
Galvanic isolation

May 2011
1.5 kV
eff
1627
USB interface
Interface Type
USB master
Transmission speed
USB 1.0 Full Speed (USB 1.1 compatible)
Power for external devices
5 V max. 500 mA (High Power)
Connector
USB type A
External bus (Ext. Bus)
Interface Type
CAN 2.0B, ISO 11898-1, ISO 11898-2
Baudrate
max. 1Mbaud
Connector
LP-3-pin terminal block (e.g. Wieland type 8113B/3VL)
Galvanic isolation
1kV
COM1
Interface Type
RS-485 interface
Baudrate
max. 12Mbaud
Connector
9-pin D-SUB connector, pin assignment to IEC 61158
Galvanic isolation
1 kV (no isolation to CAN)
Features
PROFIBUS built-in hardware controller 1) DP V1 slave,
redundant according to PNO Paper No. 2212 V1.2

1)
The Ident no. for ProfiMessage is 0x09B8 as allocated by the PROFIBUS User
Organization (PNO) . Further information can be found in the GSD file, refer to
PROFIBUS GSD file and PROFIBUS driver .
CAN (CAN bus)
Interface Type
CAN 2.0B, ISO 11898-1, ISO 11898-2
Baudrate
max. 1Mbaud
Connector
9-pin D-SUB connector, pin assignment according to CiA
DS102-1 (pin 2 and pin 7)

Galvanic isolation
1 kV (no isolation to COM1)
1628

May 2011
COM2
Interface Type
RS-485 interface
Baudrate
max. 12Mbaud
Connector
9-pin D-SUB connector, pin assignment to IEC 61158
Galvanic isolation
Features
PROFIBUS built-in hardware controller 1) DP V1 slave,
redundant according to PNO Paper No. 2212 V1.2

1)
The Ident no. for ProfiMessage is 0x09B8 as allocated by the PROFIBUS User
Organization (PNO) . Further information can be found in the GSD file, refer to
PROFIBUS GSD file and PROFIBUS driver .
COM3
Interface Type
RS-232 interface
Baudrate
max. 5Mbaud
Connector
9-pin D-SUB connector, 3 pins used
Galvanic isolation
COM4
Interface Type
RS-232 interface
Baudrate
max. 5Mbaud
Connector
9-pin D-SUB connector, pin assignment according to DIN 41
652, part 1 (ISO 4902) (such as PC connector

assignment)
Galvanic isolation

May 2011
1kV
1629
4.1.8.2 I/O modules (Device-dependent)
4.1.8.2.1 I/O modules: AAST, ADGT, ADIT and ADVT
Analog inputs
Number of inputs
AAST: 4
ADGT: 8
ADIT: 10
ADVT: 15
Connections
Terminals, max. diameter 2.5 mm 2
Voltage measuring ranges
156 mV to 10V (bipolar) and +156 mV to

+10 V (unipolar)
Current range
20 mA, 0 ... 20 mA and 4 ... 20 mA

Current measurement requires a load
resistance of 10 ... 500
Sampling rate
AAST, ADIT and ADVT: Max. of 600

measurements / s
ADGT: Max. 60 measurements / s
Sequential sampling, A / D measurement time
for each channel individually adjustable
Resolution
24 bits (about 7 decimal digits)
Input impedance
> 1 G at ADGT> 10 M
Measurement error (DC)
Thermocouples
Voltage /
current:
0.01% of measurement range /

end value
Pt100:
0.1K
Pt1000:
0.1K
Thermoc
ouples:
0.1% of end value following

compensation
Built in cold junction built-in, external optional

NiCr-NiAl (K), NiCr-CuNi (E), NiCrSi-NiSi (N), FeCuNi (L), Fe-CuNi (J), Pt10Rh-Pt (S), Cu-CuNi
(U), Pt13Rh-Pt (R), Cu-CuNi (T), Pt30Rh-Pt6Rh
(B), W5Re-W26Re (C)
Measuring range -270 C ... 2320 C
depending on thermocouple
1630

May 2011
Resistance probe / thermometer
Pt50 to Pt5000, Ni50 to Ni5000, YSI400

2-wire, 3-wire and 4-wire
1 mA reference current
Measuring range -270 C ... 850 C
Resistance measurement
0 10k
pH measurement
Integrated temperature compensation
Self-calibration
DC offset, cyclical, frequency adjustable
Digital filter
Low pass 6 1000Hz. The cut-off frequency is

automatically adjusted to the sampling rate.
Potential isolation of main device
750V DC.
Dielectric withstand voltage of the

channel
110V
Permissible differential voltages

from channel to channel
ADGT V2.0: 400 V DC

ADGT V3.0: 650 V DC
AAST, ADIT and ADVT: 110V
Analog outputs
Number of outputs
AAST: 4
ADIT: 1
Output signal:
0 / 4 ... 20 mA, maximum load resistance 650
Resolution
16 bit
Signal error
0.05%
Potential isolation
750 V from channel to channel and main device
Digital inputs for level detection

May 2011
1631
Number of inputs
AAST: 2
High level
3.5 ... 90 V / 2 mA (typ. 2.7 mA at 5 V)
Low level
0 1.5V / 0 1.5mA
Refresh rate
1kHz (1ms)
Minimum pulse width that can be

evaluated
1 ms
Maximum signal frequency
50Hz
Potential isolation
2.5kV
Reverse polarity protection
1kV
Digital outputs
Number of outputs
AAST: 2
ADIT: 1
Switching voltage
max. 50VDC
Switching current
max. 2.5ADC
Inverse diode
Integrated
Potential isolation
2.5kV
1632

May 2011
4.1.8.2.2 I/O modules: DIOT, IOIT and OTPT
Number of inputs
DIOT: 12, including 11 for frequency

measurement / pulse counting
IOIT: 24
OTPT: 1
High level
3.5 ... 90 V / 2 mA (typ. 2.7 mA at 5 V)
Low level
0 1.5V / 0 1.5mA
Refresh rate
1kHz (1ms)

evaluated
1 ms
50Hz
Potential isolation
2.5kV
1kV
Digital inputs for frequency measurement / pulse counting
Number of inputs
DIOT: 11
High level
3.5 ... 90 V / 2 mA (typ. 2.7 mA at 5 V)
Low level
0 1.5V / 0 1.5mA
Gate time
1 ms ... 6000 ms, adjustable in increments of 1
Frequency measurement
0 30kHz.
Measurement error
0 1kHz. 1Hz
>1 10kHz: 5Hz
>10 30kHz: 10Hz
Counter width
16 bit
Potential isolation
2.5kV
1kV
Digital outputs

May 2011
1633
Number of outputs
DIOT: 16
IOIT: 1
OTPT: 24
Switching voltage
max. 50VDC
Switching current
max. 2.5ADC
Inverse diode
Integrated
Potential isolation
2.5kV
1634

May 2011
4.1.8.2.3 I/O module: ADFT
Analog inputs
Number of inputs
Connections
Terminals, max. diameter 2.5 mm 2
Voltage measuring
ranges
156mV to 10V
Current range
20 mA, 0 ... 20 mA and 4 ... 20 mA

Current measurement requires a load resistance of 10 ...
500
Input signal frequency

range (-3 dB)
0 4000Hz.
Sampling rate
10 ... 5000 Hz, in 10 stages, individually adjustable for

each channel.
Channels with the same sampling rate will be sampled
simultaneously
Total sampling rate
10 ... 8000 samples/s
Resolution
14 bits (approx. 1.2 mV in the 10V range)
AC / DC coupling
DC coupling preset, switching via DIP switch on the device.
Input impedance
0.8M
Measurement error (DC)
Measurement range
1.25V to 10V
0.1% from unipolar

measurement range
Measuring range
0.625 V:
0.2% from unipolar

measurement range
Measuring range
0.312V:
0.2% from unipolar

measurement range
Measuring range
0.156V:
0.4% from unipolar

measurement range
Anti-aliasing filter
Optional digital low-pass filter 6. Order for sampling rates

100 to 5000 Hz.
The cut-off frequency is automatically adjusted to the
sampling rate.
Dielectric withstand
voltage of the channel
250VDC
Permissible differential
voltages from channel to
channel
100V DC.
Analog outputs

May 2011
1635
Number of outputs
Output signal
0 10V / 0 4mA
Resolution
12 bits (approx. 2.4mV)
Signal error
0.25% of output range or 25 mV
Earth reference
Terminals "" are connected with 1 kOhm to the

internal analog ground
Number of inputs
4, including 2 for frequency measurement /

pulse counting
High level
3.5 ... 90 V / 2 mA (typ. 2.7 mA at 5 V)
Low level
0 1.5V / 0 1.5mA
Refresh rate
1kHz (1ms)

evaluated
2.5 ms
50Hz
Potential isolation
2.5kV
1kV
Digital inputs for frequency measurement / pulse counting
Number of inputs
High level
3.5 ... 90 V / 2 mA (typ. 2.7 mA at 5 V)
Low level
0 1.5V / 0 1.5mA
Gate time
250 ms ... 5000 ms, adjustable in increments of

250
0.2Hz 50kHz
Measurement error
0.2Hz 100Hz 1% of the input frequency

>100Hz: 1Hz
Potential isolation
2.5kV
1kV
Digital outputs
1636

May 2011
Number of outputs
Switching voltage
max. 50VDC
Switching current
max. 2.5ADC
Inverse diode
Integrated
Potential isolation
2.5kV
4.1.8.2.4 I/O module: AMDT
The AMDT I/O module on vibration measurement is dealt with in a separate chapter.
Refer to E/A-Modul AMDT.
Technical data is available in the I/O module AMDT, Technical specifications section.

May 2011
1637
4.1.9
I/O module AMDT
This section of the documentation describes using and configuring the I/O module AMDT.
The I/O module AMDT has been designed for vibration measurement technology. The
efficiency is reached by a DSP (Digital Signal Processor). The processor's firmware (i.e.
software within the I/O module) provides many signal processing functions.
The documentation is provided under the following headings:
Hardware
Functions
Each section can be read independently. Just select the section you require.
The content is based on this consistent state-of-the-art :
ProfiSignal-CD: V3.1.4
Device firmware: V232
AMDT board: V2.0x
AMDT firmware: 3.58

1638

May 2011
4.1.9.1 Safety advice

Use only the power supply connector delivered, or a power supply with protective
insulation, to power the Log-/ProfiMessage device.
WARNING!
Sensors / signals without potential isolation and which have a high-voltage

potential, e.g. current measurement in the phase instead of neutral conductor of
the mains voltage, produce voltage also at the device's connectors.
In such cases, check for voltage at the connectors before coming into contact
with them.
The device's I/O modules are potentially isolated to each other and to other
components within the device. Potential differences greater that 750V can
therefore not occur (potential difference cannot be detected from measurement
data).
Replacing/exchanging I/O modules
Electronic components are sensitive to ESD (Electro-Static Discharge). Therefore,

discharge any electrostatic energy before opening the device to install/replace an I/O
module. We recommend wearing a wrist band (static discharge wrist band) and to carry out
the work on a conductive surface.
4.1.9.2 Introduction
Dear User,
Thank you for purchasing the I/O module AMDT. With this module you have acquired a high
quality product with extensive options for data acquisition and processing.

May 2011
1639
This manual is intended for technicians, engineers or similarly qualified persons wishing to
install the I/O module AMDT into a device. If you find errors in the product or in this
documentation, or if you have any suggestions for its improvement, we welcome your
feedback.
Contact:
Lustheide 81
Telephone: +49 2204 97685-0
Telefax: +49 2204 97685 -85
Contact USA:
Virginia, USA
Telephone: +1 804 217 8391
Telefax: +1 804 747 6182
4.1.9.2.1 Included in delivery
The I/O module AMDT is usually pre-installed with delivery of the Log-/ProfiMessage device.
Devices can be equipped with various I/O modules. An existing I/O module my therefore be
exchanged for an I/O module AMDT.
A device configured to individual customer requirements with pre-installed or separate
I/O module AMDT
CD containing software
Documentation
1640

May 2011
4.1.9.2.2 Symbols used in this documentation
WARNING!
This symbol warns of a potential hazard which - if the safety requirements are
not followed - may be fatal or cause serious physical injury.
Info
Refers to a special option or explains a special feature.
We use italics to highlight individual words within the text. Keyboard input is highlighted in
Add driver (connection) Log-/ProfiMessage
device . Also highlighted in grey and displayed in italics are the dialog headings, buttons,
check boxes, input field names, etc. Display status.
The CE symbol guarantees that products meet the requirements of relevant EU directives.

May 2011
1641
4.1.9.3 Hardware
4.1.9.3.1 Project planning
Log-/ProfiMessage systems are made up of a base device and optional extension devices
(the graphic shows a Log-/ProfiMessage system).
Each installed I/O module communicates with a CPU via an expansion bus. The I/O module
AMDT is equipped with the fastest sampling and transfer rates. Specific conditions need to
be taken into account when planning a system.
Regulations according hardware set up
One I/O module AMDT can be installed in any one slot. Full functioning is then
available. When setting parameters, take into account the maximum transfer rate of
10,000 samples/s.
Two I/O modules AMDT can be installed in any of the available slots.
Ensure adequate ventilation when both I/O module AMDTs are installed in the base
device. Full functioning capability is however no longer available. Both AMDT modules
can continuously transmit characteristic values but only one AMDT can continuously
transmit time signals or frequency spectrums or both.
Two synchronized I/O modules AMDTs can be installed in any of the available slots.
Synchronization requires additional wiring and occupies digital input 4 and digital
output 4. Ensure adequate ventilation when both I/O modules AMDT are installed in
the base device. Synchronization is available only in the "non-continuous recoding"
operating mode. Both AMDT modules can transfer time signals, frequency spectrums
and characteristic values continuously and synchronized. Refer here to the section
on synchronizing two AMDT modules.
Three or more I/O modules AMDT can not be installed.
1642

May 2011
Regulations according number of usable analog inputs

Using a digital high pass filter or band pass filter can be limited to 1..4 analog inputs depending on board revision. An overview is available in the section digital filters.
Using a digital integrator can be limited to 1..4 analog inputs - depending on board
revision. An overview is available in the section Integrator.
The application "Vibration severity measurement with acceleration sensors" (using a
digital band pass filter and an integrator) can be limited to 1..4 analog inputs depending on board revision. Details on this application are described in the manual
"Applications with AMDT".
The application "Bearing diagnostics with envelope spectrum" (using a digital
demodulation filter) can be limited to 1..4 analog inputs - depending on board
revision. Details on this application are described in the manual "Applications with
AMDT".
Regulations according phase measurement
Be aware of the following when using phase characteristic in rotating machinery: Phase
measurement can be used only for low rotation speed (typ. < 500 RPM). Acquisition of 1 to
10 signal periods within a time signal block is significant. Refer here to the sections on
characteristic phase of main amplitude and characteristic phase of 1X/2X/3X/xX
component.
4.1.9.3.2 Connector panel (industrial)
Information on connections
Refer to the technical specifications.

May 2011
1643
Analog inputs
Voltage signals with range of max. 10V in a frequency range DC 8000Hz can be
connected. Input impedance equals 0,8M . Current signals with range of 0/4 to 20mA are
processed using terminating resistors (to be wired between the '+' and '-' connectors).
DC-coupling is factory set. Switching is possible using a DIP switch within the module.
The permitted total voltage difference between channels is 100VDC .
Analog outputs
Output range is 0 to 10V, max. load is 4mA (min. 2.5k ).
The '-' connector is connected at 1k
to the internal analog ground point.
Digital inputs / counters

Square signals/pulses from 5V / 12V or 24V can be connected.
Low-level is <1.5V; high-level is >3.5V; common '-' connector, potential isolation.
Frequency measurement for signals from 0.2Hz to 30kHz.
Digital outputs
Switching voltage at a max. of 50VDC . Switching current at a max.: 2.5ADC .
Common '+' connector. Potential isolation.
Shielded cabling
The I/O module enables measurement in the signal range DC to 8kHz. This requires the use
of shielded (single-sided shielding connected to protective earth) or twisted pair cables.
Sensors
Information on connecting special sensors are available in the manual "Applications with
AMDT"l.
4.1.9.3.3 Connector panel (laboratory)
1644

May 2011
Information on connections
Refer to connector panel (industry).

May 2011
1645
4.1.9.3.4 Block circuit diagram
Block circuit diagram for hardware
Block circuit diagram for an analog input signal
1646

May 2011
4.1.9.3.5 Technical specifications
Specifications may change as part of ongoing technical developments.
4.1.9.3.5.1 Galvanic isolation
The complete analog set up (analog inputs 1 8 and analog outputs 1 2) is galvanically
isolated to the rest of the system.
Each digital input/output is galvanically isolated to the rest of the system.
The CAN-Bus interface (Ext. BUS, communication with base device or main CPU) is likewise
galvanically isolated.
4.1.9.3.5.2 Analog inputs
Properties
8 Analog inputs. 14-bit resolution. Differential inputs. 0,8M impedance.
A potential difference totalling 100V is permitted between the differential inputs ('-'
connector). Input protection to 250V.
Sampling frequency
Real synchronous/parallel sampling.
Non-continuous sampling: A max. sampling frequency of 20480Hz for 8 channels gives a
total sampling rate of about 160000samples/s.
Continuous sampling: A max. sampling frequency of 1024/2048/4096Hz for 8/4/2
channels gives a total sampling rate of about 8000samples/s.
Signal bandwidth / Anti-Alias-Filter (HW)
Signal bandwidth is : DC to 8kHz 0,8kHz.
Transfer rate for measurement data
A max. 10000samples/s

May 2011
1647
Measurement range
Seven voltage measurement ranges are available:
Measurement
range
10
2.5
1.25
0.625
0.312
0.156
Resolution
mV
1.2
0.6
0.3
0.15
0.08
0.04
0.02
0/4 20mA signals can be converted to voltage signals using terminating resistors of, for
example, 50/100/250 . Resistors are to be externally attached between the '+' and '-'
connectors.
Accuracy
DC-accuracy is factory set using calibration and adjustment. Basic accuracyn is 0.1 to
0.4% of the (unipolar) measurement range.
Measurement
range
10
2.5
1.25
0.625
0.312
0.156
DC accuracy
mV
10
2.5
1.3
1.3
0.9
0.6
0.1
0.1
0.1
0.1
0.2
0.3
0.4
For 0/4 20mA signals, terminating resistors need to be used that have an accuracy
greater than 0.1%.
AC-coupling
The differential input is factory set as DC-coupled. Switching to AC-coupling is possible
using a DIP switch on the signal conditioning board. The DC part of a signal is eliminated
through a HW-filter. Cut-off frequency is around 4Hz.
The DC part of a signal can also be eliminated through a SW-filter (i.e. through a DSP).
Scaling / sensor compensation
Channels can be individually scaled. Scaling takes place in the required unit (e.g. 100m
for displacment sensors or 50g for acceleration sensors). Zero offset correction and
amplification correction can be performed using sensor correction.
Anti-Alias-Filter (SW)
The (SW) Anti-Alias-Filter's frequency limit is set automatically at 40% of the sampling
frequency setting. This filter is optional. It is a digital deep pass of the 8th to 4th order
with Butterworth characteristic.
Application
Analog inputs deliver continuous or event-triggered recording of vibration/wave signals or
of signals requiring rapid sampling.
1648

May 2011
4.1.9.3.5.3 Analog outputs
Properties
2 analog outputs. Voltage range of 0 to 10V. Resolution of 12bit and/or 2.4mV.
Board V2.0x : Output range restricted to 0.3V to 9.7V.
Board V2.1x : Output range is 0 to 10V.
Max. load of 4mA at min. 2.5k .
Refresh rate
Determined by source channel (e.g. set-point channel).
Typical rates are 0 10Hz. Dependent on DSP load.
Accuracy
DC-accuracy is factory set using calibration and adjustment.
Basic precision is 0,25% of the output range, i.e. 25mV.
Scaling
Channels can be individually scaled. Scaling takes place in the required unit (e.g. 0 to
100m for distance/clearance sensors or 0 to 50g for velocity sensors)
Application
Analog outputs are used as monitors for specific measurement data (e.g. speed or vibration
amplitude). Also as signal generators (z.B. set-point ramp).
4.1.9.3.5.4 Digital inputs
Properties
4 digital inputs. Galvanic isolation up to 2.5kV. Reverse polarity protection up to 1kV.
Low-level 0 1.5V / 0 1.5mA. High-level 3.5 90V / 3mA.
Refresh rate
Digital inputs are sampled at 1kHz (1ms). The minimum signal pulse width is 1ms.
Recommended pulse width is >2.5 ms.
Maximum continuous signal frequency is 50Hz.
Application
Digital inputs are used as trigger sources with simultaneous frequency or rotation speed
measurement and phase measurement.

May 2011
1649
4.1.9.3.5.5 Counter
Properties
2 or 4 digital inputs (see above) are each equipped with 16-bit counters. Choice of pulse
counting in the 0 to 65535 range, or frequency measurement in the 0.2Hz to 30kHz range.
Automatic switching of measurement mode at 100Hz
Refresh rate
Counters are sampled at 4Hz (250ms). The minimum evaluable pulse width of a signal is
0.02ms. Recommended pulse width is >0.1 ms.
Frequency measurement precision
Basic accuracy is 1 % of the input frequency up to 100Hz and 1Hz above 100Hz.
Application
Digital inputs are used as trigger sources with simultaneous rotation speed measurement
and phase measurement.
4.1.9.3.5.6 Digital outputs
Properties
4 digital outputs. Galvanic isolation up to 2.5kV. Switching voltage max. 50VDC . Switching
current max. 2.5ADC . Integrated protection diode. Recovery diode external.
Refresh rate
Determined by source channel (e.g. timer channel). Typical range 0 10Hz; dependent on
DSP load.
Application
The digital outputs report warnings or alarms (e.g. generated by limits on vibration
characteristics). Signals are also delivered for process control.
1650

May 2011
4.1.9.3.6 Attachment
Setting AC-coupling for analog inputs
External switching
4.1.9.3.6.1 AC-coupling for analog inputs
An analog input's DC-coupling can be switched to AC-coupling via two DIP switches on the
signal conditioning board.
Two switches require activating. Analog input 1 is located on the right.
Switch position
Function
OFF (up)
AC-coupling
ON (down)
DC-coupling
AC-coupling is based on 0.1F (50V) serial capacitors these provide a high-pass cut-off
frequency of 4Hz.

May 2011
1651
4.1.9.3.6.2 External cicuits
The following includes examples of external cicuits.
External divider for analog inputs and measurement range 25V or 20V
An extended measurement range of 25V or 20V can be achieved with a symmetrical
external resistor divider. The recommended wiring appears as follows:
The resistor accuracy class should be (depending on requirements) 0.1% to 1%. Input
impedance reduces here to 25 or 20k . Measuring point scaling must be performed using
the DataService Configurator program to raise the factor to 2.5 or 2.0.
External AC-coupling
AC-coupling can be achieved with symmetrical capacitors. The recommended wiring
appears as follows:
Non-polarized capacitors must be used. The input high-pass has a cut-off frequency of 4
0.4Hz.
External AC-coupling is useful for mobile systems. For fixed installations, refer to ACcoupling for analog inputs.
1652

May 2011
External supply for ICP / IEPE acceleration sensors

Basic supply and coupling of measurement signals can be achieved with three components.
The recommended wiring appears as follows:
The sensor is supplied through a constant current diode. An external source of 24VDC is
required. The dynamic signal undergoes capacitive separation from the static DC operating
point voltage. The capacitors and the AMDT input resistors form a symmetrical high-pass
with a Cut-off frequency of 0.4Hz.
4.1.9.4 Functions
4.1.9.4.1 Operating mode
4.1.9.4.1.1 Non-Continuous recording
This is the preset operating mode for the I/O module. Recording, evaluation and
measurement data transfer takes place in sequence, one after the other. The DSP is then
on standby for the next trigger event.
Signal sampling can take place at up to 20.48kHz, parallel across 8 channels.

May 2011
1653
The above graphic represents the generation of measurement data associated with
common triggers. The transmission of the measurement data is time delayed.
The timing of the entire cycle depends primarily on the user configuration. The main factors
here are:
Recording time
Determined by the quotient of the "number of samples" and the "sampling frequency".
Example: 1024 / 2560Hz = 400ms.
Evaluation time
Determined by the number of active channels "analog input" and the computation
time required for digital filtering, for FFT analysis, and for calculation of
characteristic. Example: about 10ms/channel for a 1024-point FFT.
Measurement data transmission time
Determined by the number of selected 'active' channels specifically for channels
"analog input" and "FFT/spectrum". Transmission rate is about 10000 samples/s. Or
about 100 ms for any 1024 samples.
4.1.9.4.1.2 Continuous recording
The the I/O module runs continuously in this operating mode. Recording, evaluation and
measurement data transmission take place by the DSP continuously and simultaneously.
The max. sampling frequency depends on the amount of measurement data that is to be
simultaneously transmitted. The sampling frequency is typically 1kHz parallel on 8 analog
inputs with simultaneous transmission of time signals and some characteristic values.
1654

May 2011
The above graphic represents the generation of measurement data associated with
common triggers. The transmission of the measurement data is time delayed.
The maximum sampling frequency is limited to max. 10000samples/s of continuous
measurement data transmission, and to the performance of the DSP. Depending on the user
configuration, the following rates can be achieved:
Transmitted measurement data

Time
signal1)
FFT/Spectrum2)
X
X
No. of parallel or active channels
Characteristic
values3)
1024Hz
2048Hz
4096Hz
2560Hz
5120Hz
10240Hz
5120Hz
10240Hz
20480kHz
1)
Time signal block, each with 1024 samples
2)
FFT with 1024 samples or 400 lines
3)
3 characteristic values from the time range and 3 characteristic values from the frequency
range
4.1.9.4.1.3 Signal simulation
In signal simulation, the signals measured by analog-input 1 8 are discarded and replaced
by demo signals computed by the DSP. This operating mode enables users to perform test
runs without having to actually connect signals. A choice of signals and modulation types

May 2011
1655
are available.
Signal 1
Description: Harmonic signal
Channel 1 8: Sinus, 1000mVpp, 50Hz
Time signal and frequency spectrum :
Signal 2
Description: Signal with three frequency components
Channel 1: Sinus with 3 components, 1000mVpp, 100Hz / 200mVpp, 200Hz / 40mVpp,
300Hz
Channel 2 8 with 2 8-times amplitude
Time signal and frequency spectrum :
Signal 3
Description: Signals with paired phase shifts
Channel 1/3/5/7: Sinus, 1000mVpp, 50Hz, 0
Channel 2/4/6/8: Sinus, 500mVpp, 50Hz, -90
Time signal:
1656

May 2011
Signal 4
Description: Signal with transient progression
Channel 1 8: Sinus, emerging/fading, 1000mVpp, 50 Hz
Time signal:
Signal 5
Description: Signals with increasing phase shift
Channel 1: Sinus, 1000mVpp, 10 Hz, 45
Channel 2 8 with phase 90 360 and 2 8-times amplitude
Time signal:

May 2011
1657
Signal 6
Description: Signals with frequency components and paired phase shifts appropriate to the
"shaft vibration" application
Channel 1/3/5/7: Sinus with 3 components, 320mVpp, 40Hz, 30 / 80mVpp, 80Hz, 40 /
16mVpp, 120Hz, 50
Channel 2/4/6/8: Sinus with 3 components, 240mVpp, 40Hz, 300 / 60mVpp, 80Hz, 220
/ 12mVpp, 120Hz, 140
Each channel with an amplitude-offset of -7000mV
Time signal, frequency spectrum and orbit :
Signal 7
Description: Signals with low frequency
Channel 1: Sinus, 1000mVpp, 1.25Hz
Channel 2 8: same signal with 2- to 8-times amplitude
Time signal:
Modulation
Optional modulation varies the demo signal from measurement to measurement.
Modulation 1
Modulation of amplitude, +50% to -50%, for 32 measurements
Modulation 2
Modulation of frequency , +50% to -50%, for 32 measurements
1658

May 2011
Modulation 3
Modulation of phase, +45 to -45, for 32 measurements
Modulation 4
Modulation of offset , +1000mV to -1000mV, for 32 measurements
Modulation 5
Noise in the range of 5% of amplitude
Example:
Modulation 6
Two anomalies of 20% of amplitude at position 3/16 and 11/16 of signal duration.
Example:
4.1.9.4.1.4 Synchronizing two AMDT modules
Synchronization enables 8 + 8 = 16 analog signals to be simultaneously triggered and

sampled. Synchronization is available only in the "non-continous recoding" operating mode.
Application example as here described:
Synchronization of vibration measurement from 8 + 4 = 12 analog signals. 8 analog inputs
are assigned to a master and 4 analog inputs to a slave. Periodic external trigger pulses
(form a rotating shaft). Connected to digital input 1 on master and slave.

May 2011
1659
Additional wiring
Synchronization requires additional wiring. Digital input 4 and digital output 4 is connected
diagonally. Feed voltage and reference mass are also to be connected.
Wiring for the application example:
The connections in blue are always essential.
1660

May 2011
Configuration/Settings
Settings for the operating mode is as follows:
One I/O module AMDT is configured as "Master", the other as "Slave".
Overview of possible trigger settings:

External trigger signal
Master,
Slave,
Trigger source
Trigger source
None
Time period
Master
Analog signal, wired only at master
Analog input
Master
Digital signal, wired at master and slave
Digital input
Digital input
Digital signal, wired only at master
Digital input
Master

May 2011
1661
Settings for triggering is as follows:
Master and slave settings are identical.
1662

May 2011
Rules for settings

1. Digital input 4 and digital output 4 are used internally for synchronization. Both channels
should be set to inactive. Set Value source to Manual value for digital output 4.
2. Manual configuration amendments to a "slave" require subsequent amendments to the

"master" to avoid the handshake becoming incompatible.
3. If no external Trigger signal is used, the time period (of "master") must be set higher
than the natural cycle (Recording time + Calculation time + 2 x Measured data transmit
time) to avoid the handshake becoming incompatible. See timing diagram.
Procedure
The outcome of synchronization: Triggering takes place (almost) simultaneously.
Measurement data (time signal / frequency spectrum) are transmitted one after the other
Timing diagram for the application example:

May 2011
1663
4.1.9.4.2 Triggering and recording
Properties
Software-trigger vie time interval, periodic within the range 1ms .. 60s
Hardware trigger via analog input or digital input
Trigger threshold, edge, polarization adjustable
Non-continuous recording at a sampling frequency in the range 256 Hz .. 20480 Hz
(for 1 to 8 channels)
Continuous recording at a sampling frequency in the range 256 Hz ..1024 / 2048 /
4096 Hz (for 8 / 4 / 2 channels)
Recording depth of max. 8192 or 4096 samples for each channel, max. 8 synchronous
channels
Pre-trigger in the range 0..100% of recording depth
Start stop trigger function for externally determined recording depth
Hardware trigger operating mode
The trigger signal is preferably received from one of the four digital inputs. One of the eight
analog channels may alternatively be used with a preset threshold.
1664

May 2011
Comment to illustration above:

In example a) the trigger signal starts recording. Recording stops when the recording-time
parameter for has been reached (refer to the next section).
In Examples b) and (c) the trigger controls starting and stopping of the recording
irrespective of the trigger-pulse parameter. In the event that the stop trigger does not
occur, recording is limited to the recording-time parameter (refer to next section).
Recording parameters
A vibration/wave signal, associated with a time signal, is recorded according to three
parameters: sampling frequency, number of samples, and recording time. A frequency
spectrum is determined according to the parameters: frequency range, number of lines,
frequency resolution.
Parameters are related to each other and their settings therefore influence one another.
The following table provides an overview:

May 2011
1665
Parameter
Symbol
Calculation
Example
Sample rate
fs
2560Hz
Number of samples
ns
2048
Recording time
tr
tr = ns / fs
2048 / 2560Hz = 800ms
Frequency range
fra
fra = fs / 2.56
2560 / 2.56 = 1000Hz
Number of lines
nli
nli = ns / 2.56
2048 / 2.56 = 800
Frequency resolution
fre
fre = fs / ns
2560Hz / 2048 = 1.25Hz
4.1.9.4.2.1 Redundant trigger source
When triggering takes place via an external digital signal, the trigger source can be
automatically switched in the event of a trigger signal failure. There are two variants:
Single-stage redundancy
The failure of a trigger signal on digital-input 1 switches to the time-period trigger.
Double-stage redundancy
The failure of a trigger signal on digital-input 1 switches to the trigger signal on
digital-input 2. If digital-input 2 also fails, the signal is switched to the time-period
signal.
1666

May 2011
Configuration example:

May 2011
1667
Function and visualisation example:
Comment to illustration above:

A frequency spectrum is measured here every 3 seconds. If the external trigger signal fails,
measurement is triggered at a time period of 6s. Event 1 marks the Failure of trigger signal
of Digital input 1. Event 2 marks the recovery of the trigger signal.
4.1.9.4.3 Time signal
Any acquired vibration signal is initially saved to a buffer within the I/O module. The "analog
input" channel delivers a block of measured data (e.g. 2048 amplitude values over time).
This block is referred to as a "time signal".
Properties
128 to 8192 samples, synchronous/parallel sampled at 256to 20480Hz
Variable pre/post history and/or triggers
Digital filters, integrators etc. can be used
Data compression can be used for transmission
4.1.9.4.3.1 Digital filter
Properties
Choice of filter type: low-pass, band-pass, high-pass or demodulation filter
Filter order of 2 8, preset Butterworth characteristic
Adjustable cut-off frequency in the range 1Hz 10kHz
Adjustable filters for each channel
1668

May 2011
Application
High-frequency distortions are filtered out of the signal to be recorded; the signal is filtered
for only the frequency range required.
Restrictions
The digital filter is defeated if necessary by this limitations:
Board V2.00 to V2.12 :
With 1..4 used analog inputs : All filters available. Max. order is 8.
With 5..8 used analog inputs : Only Low-pass filter available. Max. order is 4.
From board V2.13 :
With 1..8 used analog inputs : All filters available. Max order is 6.
4.1.9.4.3.2 Digital integrator
Properties
Numerical integration of the acquired vibration signal
Fixed scaling factor preset at 1000.
Application
For measurements using acceleration sensors, a signal (m/s2 unit) is converted into a
velecity signal (mm/s unit). Refer to the "Applications with AMDT" manual.
Restrictions
The integrator is defeated if necessary by this limitations:
Board V2.00 to V2.12 :

With 1..4 used analog inputs : Integrator available
With 5..8 used analog inputs : Integrator not available
From board V2.13 :

With 1..8 used analog inputs : Integrator available
Info
When digital integration is enabled, measurement range checking or wirebreak monitoring will not take place.

May 2011
1669
4.1.9.4.4 FFT analysis / frequency spectrum
Any acquired vibration signal is initially saved to a buffer within the I/O module. Options are
available to then perform an FFT-analysis or to compute a frequency spectrum. Each
analog-input channel is provided with an additional FFT/spectrum channel. That delivers a
block measured data (e.g. 800 amplitude values concerning frequency).
Properties
An FFT/spectrum channel can be separately set up/created (for each analog input)
FFT algorithms for 1024, 2048, or 4096 points or with 400, 800, or 1600 lines
Frequency range, number of lines and frequency resolution can be set
Standard window functions 'Hanning', 'Flat Top', etc. optional
Data compression available for for data recording and transmission
Scaling
Each FFT/spectrum channel can be individually scaled. Scaling takes place in the required
unit (e.g. 100 m for displacement sensors or 50g for acceleration sensors)
Application
Analysis of characteristic frequencies and their amplitudes for a measured vibration signal.
4.1.9.4.5 Characteristics
Any acquired vibration signal is initially saved to a buffer within the I/O module. Options are
available to then perform an FFT-analysis or to compute a frequency spectrum. It is then
possible to calculate various characteristic from the vibration signal and/or the frequency
spectrum.
One or more additional characteristic channels are available for each analog-input channel.
These then deliver characteristic values (e.g. root mean square, a spectrum's peak
amplitude etc.).
Properties
1 to 30 characteristic-value channels can be separately set up/created (for each
analog input)
Simple configuration using selection lists
Automatic assigning to source channel
Characteristic values
No.
Characteristic value
Typ
Note
e
1
Peak-to-peak value
Difference between maximum and minimum
Mean value
or DC component
True RMS value
1670

May 2011
No.
Typ
Note
e
4
Frequency of the main amplitude
Frequency of the main amplitude within

spectrum
Main amplitude
Main amplitude within spectrum
Rotation speed
Frequency/Rotational speed
Phase of main amplitude
T, F
Amplitude of 1X component
Amplitude of the speed synchronous vibration

component
Phase of 1X component
T, F
Phase of the speed synchronous vibration

component
10
Amplitude of the double speed synchronous

vibration component
11
T, F
Phase of the double speed synchronous

vibration component
12
Maximum of vector sum
T, 2
Maximum of vector sum of two signals (at an

order of 90)
13
Mean of product
T, 2
Mean of product of two signals
14
Frequency of main amplitude,

band 1
Frequency of main amplitude for preset

frequency band 1
15
Main amplitude, band 1
Main amplitude for preset frequency band 1
16
RMS value, band 1
RMS value for preset frequency band 1
17

band 2
Frequency of main amplitude in preset

frequency band 2
18
19
RMS value, band 2
20

band 3
Frequency of main amplitude in preset

frequency band 3
21
22
RMS value, band 3
23
Maximum value
Most positive value
24
Minimum value
Most negative value
25
Amplitude of triple speed synchronous vibration

component
26
T, F
Phase of triple speed synchronous vibration

component
27
Amplitude of xX component
Amplitude of multiple-x speed synchronous

vibration component
28
Phase of xX component
T, F
Phase of multiple-x speed synchronous

vibration component
29
Sum value
Weighted sum of all lines of frequency

spectrum

May 2011
1671
No.
Typ
Note
e
30
Remainder value
Weighted sum of all lines of frequency

spectrum minus the lines of the harmonic
components
Type: T = determined from time signal, F = determined from frequency spectrum, 2 = determined from 2
source channels
Scaling
Scaling is automatically taken from source channel (in case of amplitude) or appropriate
preset (in case of frequency or phase angle)
Application
Analysis of characteristic values for a vibration signal for time domain and for frequency
domain. For example, determining the root mean square of a vibration signal or the peak
amplitude of a spectrum.
Mathematical definition
Mathematical definitions for all the available characteristic values are listed in the following
sections.
4.1.9.4.5.1 Characteristic "Maximum value", "minimum value"
Maximum value
The DSP determines (finds) the maximum value (or most positive value) of the time signal.
And then delivers the amplitude value.
Minimum value
The DSP determines (finds) the minimum value (or most nagative value) of the time signal.
And then delivers the amplitude value.
Smooth curve / Eliminate glitches

It might be necessary to smooth curves prior to determining characteristic values when
noise or distortions occur within the periodic signals The appropriate settings are available
in the Options tab:
1672

May 2011
4.1.9.4.5.2 Characteristic "Peak-to-peak value"
The DSP calculates the peak-to-peak value of the time signal, i.e. the difference between
the most positive and most negative amplitude values.
OptionsSmooth curve / Eliminate glitches

It might be necessary to smooth curves prior to determining characteristic values when
noise or distortions occur within the periodic signals. The appropriate settings are available
in the Options tab:

May 2011
1673
4.1.9.4.5.3 Characteristic "Mean value"
The DSP calculates the arithmetical average of the time signal.
The arithmetical average is also referred to as a signal's steady or DC component. This

characteristic value is available even when the option "Without DC-part" is enabled for an
analog input (see configuration/settings for an analog input).
Apply window function option
Select this option to calm measurement data for a static vibration/wave. A weighting is
then applied prior to the arithmetic average being calculated. A low weighting is given to
the signal's periphery and a higher weighting to its middle.
1674

May 2011
4.1.9.4.5.4 Characteristic "True RMS value"
The DSP calculates the root mean square of the time signal.
Discretization enables a good approximation to the above exact formula.
Info
The accuracy of TRMS calculations on sine signals depends on the number
of signal periods acquired. The rule of thumb: Errors are <3% for more than
2 periods; Errors are <1% for more than 4 periods.
4.1.9.4.5.5 Characteristic "Frequency of main amplitude"
The DSP determines (finds) largest amplitude within the frequency spectrum and delivers
the frequency of this line.

May 2011
1675
4.1.9.4.5.6 Characteristic "Main amplitude"
The DSP determines (finds) the highest amplitude in the frequency spectrum and delivers of
the amplitude for this line.
4.1.9.4.5.7 Characteristic "Phase of main amplitude"
Phase angle measurement is useful only for low frequencies/rotations. The

computation procedure (see below) shows why. Further information on
phase angle definition and on measurement precision etc. is available
under measuring the phase angle.
This characteristic value can be determined only when a cyclical digital

pulse is connected to a digital input/counter (e.g. the square wave pulse
of a rotating shaft). This signal delivers a stable base frequency fn as well
as a phase reference or trigger signal.
The DSP normalizes the time signal (internally, hidden) to an integral multiple of the basic
frequency fn.
1676

May 2011
Using the frequency spectrum associated with the line index fn, the DSP determines the
line/vibration component's phase angle 0 360.
4.1.9.4.5.8 Characteristic "Amplitude of 1X/2X/3X/xX component"

of a rotating shaft). This signal delivers a stable base frequency fn as well
as a phase reference or trigger signal.
Using the frequency spectrum for the line index fn / 2fn / 3fn / xfn, the DSP determines the
amplitude of this line/vibration component.
Info
Acquisition of an accurate fn via the frequency input is essential, as is the
highest possible resolution for the frequency spectrum. In the event of
deviations between the measured frequency and frequency spectrum's line
index, evaluation then takes place of the next line.

May 2011
1677
Only the free-definable component (Amplitude of xX component) can be set in the range 0
100 x fn. See Below the corresponding configuration dialog (Tab Main settings) with the
field "Speed factor":
4.1.9.4.5.9 Characteristic "Phase of the 1X/2X/3X/xX component"
Phase angle measurement is useful only for low frequencies/rotations. The

computation procedure (see below) shows why. Further information on
phase angle definition and on measurement precision etc. is available
under measuring the phase angle.

of a rotating shaft). This signal delivers a stable base frequency fn.
1678

May 2011
The DSP normalizes the time signal (internally, hidden) to an integral multiple of the basic
frequency fn.
Using the frequency spectrum for the line index fn / 2fn / 3fn / xfn, the DSP determines the
0 ... 360phasing for this line/vibration component.
Only the free-definable component (Phase of xX component) can be set in the range 0
100 x fn. See Below is the corresponding configuration dialog (Tab Main settings) with the
field "Speed factor":

May 2011
1679
4.1.9.4.5.10 Characteristic "Rotation speed"
The DSP determines (finds and counts) the number of signal periods in the time signal. From
this, the DSP determines the signal frequency (f = 1 / T) or rotation (n = 60 * f). Edge and
threshold values can be set.
A frequency measurement has upper and lower frequency limits frequencies outside this
range can are not conclusive (i.e. have insufficient accuracy). The following table provides
an overview:
Sampling frequency
Number of samples
Lower limit
Upper limit
fs
ns
10240Hz
2048
10Hz
1024Hz
2560Hz
2048
2.5Hz
256Hz
512Hz
2048
0.5Hz
51Hz
Frequencies can be measured between the lower limit at 2*fs/ns and the upper limit at
fs/10 for selected parameters (recording parameters). The measurement value equals 0
beyond these limits.
Below is the corresponding configuration dialog (Main settings) tab:
1680

May 2011
4.1.9.4.5.11 Characteristic "Maximum of vector sum"
The DSP performs vectoral addition of all amplitude values from the time signals of two
channels following on each other. (e.g. analog inputs 1 and 2) and then determines the
maximum value. The characteristic must be put on with the first one of two channels
following on each other.
OptionsSmooth curve / Eliminate glitches

Smooth curves prior to determining characteristic values may be applicable to periodic
signals that have noise or distortions. These two settings are available in the Options tab:

May 2011
1681
4.1.9.4.5.12 Characteristic "Mean of product"
The DSP multiplies all amplitude values from two time signals of two channels following on
each other (e.g. analog inputs 1 and 2) and then determines the mean value. The
characteristic must be put on with the first one of two channels following on each other.
Info
For the "Electrical power measuring" application, this characteristic value
corresponds to the P unit of measurement (= active power) for current and
voltage input values.
1682

May 2011
4.1.9.4.5.13 Characteristic "Frequency of main amplitude, band 1/2/3"
The DSP determines (finds) main amplitude, within a small frequency band, from the
frequency spectrum, and delivers the frequency of this line. The frequency band is
determined by middle of band fm and band width fw. The frequency band can be fixed or
adapted to speed.
Refer also to amplitude of maximum line, band1/2/3
4.1.9.4.5.14 Characteristic "Main amplitude, band 1/2/3"
The DSP determines (finds) the main amplitude, within a small frequency band, from the
frequency spectrum, and delivers the amplitude of this line. The frequency band is
determined by band middle fm and band width fw. The frequency band can be fixed or
adapted to rotations.


May 2011
1683

Example 1: Fixed frequency band. The characteristic value delivers the frequency spectrum's
largest amplitude within the band 1005Hz or 95 to 105Hz
Example 2: Frequency band adapted to rotation. Monitoring of the dual synchronous shaft
vibration in a machine with a rotating shaft. The frequency band midpoint is shifted
proportionally and automatically from 20 to 100 Hz for operating rotations from 600 to
3000rev/min (10 to 50Hz). The width of the frequency band is 5Hz.
1684

May 2011
4.1.9.4.5.15 Characteristic "RMS value, band 1/2/3"
The DSP determines (calculates) the RMS value (root mean square) using all the lines
within a specific frequency band of the frequency spectrum. The frequency band is
determined via the fm middle and fw width. The frequency band can be fixed or adapted to
rotations.

May 2011
1685
The following formula is also available (Alternative formula ):
Refer also to "Amplitude of maximum line, band 1/2/3" characteristic value

Hint
It is recommended that the frequency band is set so that the left and right limits are
located between the spectral lines. Each spectral line will then clearly lie within or without.
Example
A sampling frequency of 2560 Hz and 4096 samples delivers a frequency spectrum with
1600 lines and a frequency resolution of 0.625 Hz. A frequency band midpoint of 100 Hz
and a width of 6 Hz. This results in values for k, m and n of:
1686

May 2011
4.1.9.4.5.16 Characteristic "Sum value"
The DSP determines (calculates) a weighted sum for all lines of a frequency spectrum.
Info
For a single ideal line (sine wave), there is agreement between Sum value
and True RMS value.
4.1.9.4.5.17 Characteristic "Remainder value"
The DSP determines (calculates) a weighted sum of all quadratic lines of the a frequency
spectrum excluding the three harmonic components and, when applicable, a component of
choice.


May 2011
1687
Info
Acquisition of an accurate fn via the frequency input is essential, as is the
highest possible resolution for the frequency spectrum. In the event of
deviations between the measured frequency and frequency spectrum's line
index, evaluation then takes place of the next line.
The three harmonic components and the components of choice can be processed as
required. These components are each calculated using three lines in the above formula.
Settings are 1/3/5 lines.
1688

May 2011
The characteristic value can not be generated without an rotation pulse. The DataServiceConfigurator then displays an error:
4.1.9.4.6 Measuring frequency or speed
Measuring of frequency or rotation speed of rotating equipment provides the determining of

speed as additional information for the frequency spectrum.
Properties
Frequency measurement via 2 free running counters (16-bit)
Connected to digital-input 1/2
Signal frequency of 0.2Hz to 30kHz
Frequency measurement or pulse counting operating modes
Frequency measurement gate time within the 250
5000ms range
Operating mode
Settings are made jointly for both counter channels for operating mode (frequency
measurement mode or pulse counting) and gate time.
The appropriate measuring process is automatically selected. The interval of registered
pulses are measured in the 0.2 to 100Hz (or 12
6000rev/min) range. In the >100 Hz to
30kHz range, the number of pulses are measured per gate time.

May 2011
1689
A gate time setting of 1000ms is recommended. The table shows the values for 1 pulse/
rotation, a gate time of 1000ms and a sampling frequency of 1000Hz:
Frequency
in Hz
Rotation
Pulse
in rev/min
interval
Evaluated periods
in ms
0.2
12
5000
0.5
30
2000
60
1000
120
500
300
200
10
600
100
10
20
1200
50
20
50
3000
20
50
100
6000
10
100
200
12000
200
500
30000
500
1000
60000
1000
2000
0.5
2000
5000
0.2
5000
10000
0.1
10000
20000
0.05
20000
30000
0.033
30000
The following applies to the >100 to 30kHz range: Lower gate times enable faster
measurement data updates. Higher gate times provide higher resolution/measurement
precision.
Gate time
Resolution
in ms
in Hz
5000
0.2
2000
0.5
1000
500
250
1690

May 2011
4.1.9.4.7 Measuring the phase angle
Phase angle measurement is useable only for machinery with low

frequency/speed. The evaluation procedure shows why. Refer also to
characteristics phase for the main amplitude or phase for the 1X/2X/3X/xX
component.
Defining the phase angle

The phase angle definition corresponds to a sine definition associated with a trigger point.
Conversion to a cosine definition is explained below.
The following example has two signals. Two signal periods are acquired. Signal 1 has a
phase angle of 0 deg. Signal 2 has a phase ange of 90 deg. Mark 3 shows the trigger point.
Measurement accuracy is determined by acquisition of the fn basic frequency via the digital
frequency input.
Select the settings Sampling frequency and Number of samples, to enable acquisition of more
than one but less than ten signal periods in a time signal block. This achieves an accuracy
of 1
5degrees for the phase angle.
The following table is for a frequency spectrum with 2048 and 4096 lines.
Acquired signal periods
>1
10
20
Measurement deviation phase angle
1deg.
2deg.
3deg.
5deg.
10deg
.

May 2011
1691
The rule of thumb for a measurement deviation of 5degrees:
Examples
Sample rate
2560Hz
2560Hz
1280Hz
Number of samples
2048
4096
4096
Input signal range for a

measurement accuracy of
5degrees
1.25 to 25Hz
0.625 to 12.5Hz
0.3125 to 6.25Hz
Converting a sine definition to a cosine definition

The phase angle is given in the range 0
360degrees. The following table shows a
comparison between sine and cosine definitions:
Sinus
30
60
90
120
150
180
Cosinus
270
300
330
360/
0
30
60
90
Sinus
210
240
270
300
330
360
deg.
Cosinus
120
150
180
210
240
270
deg.
Conversion takes place via a calculation channel using the formula "PhaseOut = (PhaseIn +
270) MOD 360".
1692

May 2011
4.1.9.4.8 Monitoring
The "Limit" software channel monitors characteristic values against threshold values. Limit
channels can be logically linked and given to digital outputs. In the same way, functions
can be integrated into the monitoring such as averaging, computations or time procedures.
Refer to the sections on software channels in the device manual.
4.1.9.5 Configuration and operation

Configuration using the DataService Configurator
Visualisation using ProfiSignal
Firmware update
4.1.9.5.1 Configuration using the DataService Configurator
The DataService Configurator gives a hierarchical portrayal of a system's connected

components. The following image shows 8 "analog input" channels. Analog input 1 has
additional derived channels.

May 2011
1693
The "Analog Input x" channel deliver the time signal (as block of measured data). The value
shown here is the maximum value of the time signal.
The "Analog Input x FftSpectrum" channel delivers a frequency spectrum (as a block of
measured data). The value shown here corresponds to the spectrum's peak amplitude.
The following image shows the other channels from the I/O module AMDT: 2 analog
outputs, 2 counters, 4 digital inputs and 4 digital outputs. The two counters belong to the
first two digital inputs.
Overall functioning is organized according to channels. As a rule, each channel delivers one
measurement value. Channels can be added or deleted.
1694

May 2011
Configuring/setting the entire I/O module

Open the configuration dialog via the context menu (right-click) or double-clicking an I/O
module.
The dialog is described in configuring/setting the I/O module.

Configuring/setting single channels
Open the configuration dialog via the context menu (right-click) or double-clicking a
channel.
The dialog is described in configuring/setting an analog input.

Adding/deleting an FFT/spectrum or characteristic value channel
Add channels using the analog input's context menu (right-click). Delete a channel using
that channel's context menu
The dialog is described in configuring/setting an FFT/spectrum.

May 2011
1695
4.1.9.5.1.1 Configuration/settings for I/O module
I/O module settings take place for all analog inputs. The most important settings are on the
tabs: Operating mode, Triggering and Recording.
Operating mode tab
Recording
To set the main mode of operating:
Non-continuous: Recording, evaluation and measurement data transfer takes place in
chronological sequence. Refer to Non-continuous recording.
Continuous: Recording, evaluation and measurement data transfer takes place in
parallel. Refer to Continuous recording.
FFT analysis
To enable/disable internal FFT analysis. This setting affects the settings options
available on the Recording tab.
Transmitted measurement data
To globally set which of the three measurement data types are to be transmitted,
irrespective of whether the corresponding channels have been created and are active.
Simulation
To enable signal simulation. Refer also to signal simulation.
1696

May 2011
Triggering tab
Trigger source
A trigger event starts recording (i.e. signal acquisition). Select from four trigger-source
options:
Time period
The I/O module's internal time counter is used to generate periodical trigger
events.
Analog input
The trigger source is one of the I/O module's eight analog inputs.
Digital input
The trigger source is one of the module's four digital inputs.
Master
The trigger source is a second I/O module AMDT. Refer to synchronizing a
second AMDT.
Trigger channel
Selects the triggering channel. This is always one of the I/O module's own channels.
Trigger period
To set a time period, between two trigger events, in the 1ms
60s range.
Note: A short time period can extend the actual period when the total time is greater
for recording, evaluation and data transmission.
Trigger threshold
For analog-input triggering, sets the threshold value at 0
measuring range.

May 2011
100% of the input
1697
Pre-Trigger
This option is available only for the Non-continuous operating mode.
For triggering via analog input or digital input, sets the amount of signal pre-history as
0..100% of recording depth (i.e. signal length).
Mode and polarity
Sets the type of triggering. Analog input: With over-run or under-run of the threshold/
limit value. Digital input: With logical 1 or logical 0.
Start-Stop trigger and number of trigger pulses
This option is available only for the Non-continuous operating mode.
This option dynamically controls the recording signal length for analog or digital input
triggering. Refer to triggering and recording.
Recording tab
Used analog inputs

Operation can reduce the number of analog inputs from 8 to 4 / 2 / 1. This reduces the
time for evaluation and for measurement data transmission, or increases the trigger
rate. Some functions are available only for settings of 4 channels. Refer also to
project planning.
This is setting takes priority over the analog inputs marked as Active.
1698

May 2011
Sample rate
Sets the sampling frequency in the 256Hz to 20480Hz range. The setting is applied to
all selected analog inputs. The Operating mode affects the options that are available
here.
Number of samples
The number of samples (i.e. measurement values) in the 128 to 8192 range for a time
signal. The setting is applied to all selected analog inputs. The Operating mode affects
the options that are available here.
Recording time
Information about the time signal. It is determined from the sampling frequency and
number of samples and then displayed here.
Frequency range/ number of lines / frequency resolution
Information about the frequency spectrum. It is determined from the sampling
frequency and number of samples and then displayed here.
Time signal tab
Compression
Time signals can be compressed prior to transmission. This can reduce transmission
speed and increase storage capacity in the data logger memory. Select the required
Method:
None
The time signal is transmitted without compression
Log. compression (-Law)
Amplitude values undergo logarithmic compression; the compression fact equals
2:1. Amplitude error following decompression is 2 % max.

May 2011
1699
Delta coding
Amplitude values are transmitted as absolute (for minor changes) or relative (as
differences). The compression factor ranges between 2:1 and 1:1. No
compression/decompression loss.
Minimum-/Maximum values
The time signal is reduced to the local maximum or minimum. More information is
available in the "Applications with AMDT" manual (in the generator/air-gap
section).
FFT/Spectrum tab
Window function
Enables a weighting function for the time signal The weighting is applied prior to
running the FFT analysis. Options are "Hanning" (recommended for high frequency
precision) or "Flat Top"(recommended for amplitude precision).
Compression
Frequency spectrums can be compressed prior to transmission. This can reduce
transmission speed and increase storage capacity in the data logger memory. Select
the required Method:
None
The frequency spectrum is transmitted without compression
Log. compression (-Law)
Amplitude values undergo logarithmic compression; the compression fact equals
2:1. Amplitude error following decompression is 2 % max.
1700

May 2011
Averaging
A frequency spectrum can be averaged within the device via measurement cycles n =
2
32.
The Intermediate block values transmits a frequency spectrum corresponding at averaging
level (1, 2, 3, , n) for each measurement.
The End block value transmits a frequency spectrum at a corresponding averaging level
only after n measurements.
Order analysis
When order analysis is enabled, the evaluation software (e.g. ProfiSignal) will be
informed that the measured frequency spectrum is to be portrayed as an order
spectrum. The spectrum is then normalized to the measured rotation. This requires that
a rotation-pulse is connected and a frequency measurement is activated.
Speed measurement tab
Counter mode
Both counters are assigned directly to first two digital inputs.
Two modes are possible:
Pulse counting
Settings are made simultaneously to both counters. Pulse counting is consecutive (16bit = 65536) and reset is not possible. Frequency measurement takes place automatically
in Hz. More information is available in measuring frequency or speed.

May 2011
1701
Speed measurement, Source

Sets one of the digital or analog inputs as source for measuring speed to which the
FFT analysis is assigned. Key word: Rotation speed stamp to frequency spectrum and
order analysis.
Set to digital-input 1 or 2 when the frequency measurement is taking place via one of
these inputs.
Redundancy mode
Two speed pulse sensors and two digital inputs can be operated creating the possibility
of redundancy. Refer here to redundant trigger source.
4.1.9.5.1.2 I/O module / measurement block counter
Measurement data undergoes evaluation and transmission depending on I/O module settings
and trigger events.
The DataService Configurator displays a counter for the number of recorded measurementdata blocks, as status information for the I/O module AMDT.
4.1.9.5.1.3 Configuration/settings for analog input
Refer also to the technical specifications for analog inputs.

Active
Activating this channel transmits the time signal as a measurement data block following
each triggering. Non-required channels should be deactivated.
Info
The Time signal tab of the I/O module includes more settings with affects to
all analog-input channels. See section Configuring/setting an I/O module.
1702

May 2011
Main settings tab
Sensor type / Mode / Measuring range

Defining the input measuring range. Sensor type enables selection between a volt and
current interface. Mode enables selection between a bipolar and unipolar measuring
range. Measuring range selects one of 7 possible measuring ranges from 10000mV to
156mV.
Scaling / Unit
The four Scaling fields contain scaling as a choice of two points of a linear ordering.
Example: Enter the unit g and the following Scaling values for a velocity sensor with
a sensitivity of 100 mV/g:
Inversion
Activates signal inversion. Takes place following recording and prior to evaluation.
Without DC part
Eliminates a signal's DC part. Takes place following recording and prior to evaluation.
The DC part is still made available as a measurement value (arithmetical average
characteristic value).

May 2011
1703
Apply window function

Select this option to calm measurement data for a static vibration. A weighting is then
applied prior to the arithmetic average being calculated. The signal's periphery is
weighted lower and its middle higher.
Rectification
Activates signal rectification. Takes place following recording and prior to evaluation.
Default value
The value set here is transmitted as a measurement value when a normal measurement
value is missing.
Formatting
The required number of decimal places for the measurement value is set, e.g. for
display in the DataService Configurator.
1704

May 2011
Additional settings tab
Measuring range check

Monitors whether the input signal remains within the physicl voltage range (e.g. 10
V).
Wire break monitoring
Monitors whether the arithmetical average (DC component) of the input signal remains
within the preset voltage range.
Anti-Alias-Filter (SW)
The software-Anti-Alias-Filter is a digital low-pass whose cut-off frequency is around
40% of the set sampling frequency. Select the Automatic, to work with the FFT
analysis.
Compression
The I/O module can be set to compress measurement data for transmission of all active
analog inputs. Refer to the time signal tab in configuring/setting an I/O module. This
option enables individual analog inputs to be excluded from such compression.

May 2011
1705
Filter settings tab
Filter
Activates digital filtering of the time signal. Options are low-pass, band-pass or highpass filters. A Butterworth characteristic is preset. Filter order is automatically set
internally. Cut-off frequencies can be set at the 1Hz to 10000 Hz range.
Using a digital high pass filter or band pass filter can be limited to 1..4
analog inputs - depending on board revision. An overview is available
in the section digital filters.
Integrator
Activates numerical integration of the time signal. The scaling factor is fixed at a
preset value of 1000.
Example: For measurements using velocity sensors, a vibration/wave velocity signal (m/
s2 unit) is converted into a vibration speed signal (mm/s unit). Refer to the
"Applications with AMDT" manual.
Using a digital integrator can be limited to 1..4 analog inputs depending on board revision. An overview is available in the section
Integrator.
1706

May 2011
Sensor correction tab
Mode / Calibration points

Performs correction for offset and gain. A simple variance analysis is used. Input is
required of two points from the linear characteristic curve.
4.1.9.5.1.4 Configuration/settings for FFT/spectrum
Main settings tab
Active
Activating this channel transmits a frequency spectrum as measurement data following
each triggering. Unrequired channels should be deactivated.

May 2011
1707
Scaling
The "FFT/spectrum" channel is derived from one of the analog-input channels and therefore
inherits its scaling. The effective scaling is grayed-out here.
4.1.9.5.1.5 Configuration/settings for characteristics
To add a characteristic-value, click on the source analog-input and right-click to display

the required context menu refer to image below. To delete, use the channel's context
menu.
Technical specifications for each characteristic : see section characteristics
1708

May 2011
Main settings tab

Here characteristic "Peak-to-peak value" as example:
Active
Activating this channel transmits the selected vibration/wave characteristic value as
measurement data following each triggering.
Measurement range /Scaling / Unit
The "Characteristic value" channel is derived from one of the analog-input channels and
therefore inherits its scaling. The effective scaling is grayed-out here. Exceptions are those
characteristic values that deliver frequency or phase measurements. Scaling is then preset
to Hz or (degrees).
More setting options : see section characteristics.

May 2011
1709
4.1.9.5.1.6 Configuration/settings for analog output
Refer also to the technical specifications for analog outputs.

Output is always in the range 0
10V.
Main settings tab
Source
Source selects from various signal sources:
Application: Output data is controlled via a ProfiSignal application.
Channel: Output data is controlled via a DataService channel.
Manual value: Output is set manually.
Scaling
Defines the physical basis for the output unit of measurement. In the example 0
100% is assigned the output value 0
10V.
1710

May 2011
4.1.9.5.1.7 Configuration/settings for digital input
Refer also to the technical specifications for digital outputs.

Main settings tab
Inversion
Activates logical inversion.

May 2011
1711
4.1.9.5.1.8 Configuration/settings for counter
Refer also to the technical specifications for the counter and the section on measuring
frequency and rotation.
The (measuring frequency or counting pulses) mode is set under the Measuring rotation tab.
Refer to configuring/setting an I/O module.
Unit
The preselected unit for frequency measurement is Hz . Enter here the desired unit.
Main settings tab
Scaling
Sets conversion factor for the measurement. As a choice of two points of a linear
ordering.
1712

May 2011
4.1.9.5.1.9 Configuration/settings for digital output
Refer also to the technical specifications for digital outputs.

Main settings tab
Source
Source selects from various signal sources:
Application: Output data is controlled via a ProfiSignal application.
Channel: Output data is controlled via a DataService channel.
Manual value: Output is set manually.
Inverted
Activates logical inversion.

May 2011
1713
4.1.9.5.2 Visualization using ProfiSignal
ProfiSignal is a complete system for applications for measurement data acquisition, analysis
and visualization. It replaces former products,e.g. VibroLab, BasisPaket or Process
visualisation.
The following images show examples of a diagram with some time signals and a diagram
with a frequency spektrum :
1714

May 2011
4.1.9.5.3 Firmware update
Firmware for the I/O module AMDT is included in the device firmware. Firmware updates
take place via the device's Ethernet interface and any internet browser. Refer to the
sections on firmware update in the device manual.
The device's power supply must not be interrupted during firmware

updating otherwise damage may occur to the equipment that will require
repairing.
Method
Open your internet browser
Enter the IP address of your device (example):
Click Update firmware.

Enter the file with the new firmware in the New firmware file field on (click Search to find
the file on your PC).
The click Start firmware update.
The firmware upgrade takes 4 to 6 minutes.

May 2011
1715
The device will reboot after the update (reboot). A message is displayed during loading and
when a restart has been completed:
The process finishes about one minute later. Then return to the home page ( Back ).
4.1.9.6 Information on applications

The "Applications with AMDT" manual contains information on typical industrial applications.
It includes information on the fundamentals of applications, advice on connections,
examples of configurations, and much more.
The main section are :
Measurement of absolute bearing vibration
Measurement of relative shaft vibration
Air gap monitoring
1716

May 2011
4.1.9.7 Appendix to older AMDT hardware

This appendix explains features and differences to older hardware. AMDT boards V1.0 to
V1.2 were manufactured and supplied from 2000 to 2005.
AMDT V1.0 to 1.2
AMDT V2.0
Measurement range
10V, alternatively 25V or

2,5V adjustable via jumpers
10V, 5V, 2,5V, 1,25V, 625

mV, 312mV, 156mV, adjustable
via software
Coupling
DC-coupling
Preset DC-coupling, choice of ACcoupling via DIP switch
Max. sampling
frequency
25kHz
20.48kHz
Oversampling
No
Yes
Anti-aliasing filter
Set by hardware (SMDs),

possible to replace the signal
conditioning board
Automatically adapts, with digital

filter (DSP)
Potential isolation
A potential difference totalling

2.5V is permitted between the
differential inputs ('-'
connector).
A potential difference totalling 100V

is permitted between the differential
inputs ('-' connector).
Input protection
to 25V
to 250V
Input hysteresis
No
Yes
Input current, type
8mA
3mA
Updating
Coupled to analog inputs

(trigger)
Independent
Frequency
measurement
0.1Hz to 100kHz
0.2Hz to 30kHz
Measurement procedure
Pre-parameterized
automatic
Updating

(trigger)
Independent
Output range
10V
0 ... 10V
Updating

(trigger)
Independent

(trigger)
Independent
Analog inputs
Digital inputs
Counter
Analog outputs
Digital outputs
Updating
Other

May 2011
1717
Power supply
24V
12 or 24V
Availability
Low-pass/high-pass/band-pass
for analog-input 1 ... 8
Low-pass for analog-input 1 ... 8,

high-pass/band-pass for analog-input
1 ... 4
Filter order
Adjustable, 2/4/6/8
Automatically optimized , 4 or 8
Filter procedure
Non-continuous or continuous
Always continuous
Availability
basic integrator for analog-input

1 ... 8
Basic integrator for analog-input 1

4
Integrator procedure
Non-continuous or continuous
Always continuous
No
Yes for low rotations, via time-zoom

procedure
Digital filter
Digital integrator
Measuring phase
Availability
Envelope spectrum (for roller-bearing diagnostics)

Availability
Yes, via sequential mode
1718
Yes, for analog-input 1 4

May 2011
4.1.10 Appendix:
4.1.10.1 EC declaration on conformity ProfiMessage

May 2011
1719
4.1.10.2 EC declaration on conformity LogMessage
1720

May 2011
4.1.10.3 ISO 9001 certificate

May 2011
1721
4.2
Expert Vibro
The devices are designed for use as modular measurement, control, and monitoring devices
and are equipped with many settings and connection options. They are also equipped with
a range of field bus interfaces and software channels to enable the performance of
monitoring, control, and regulation tasks. The devices are equipped with internal storage
capacities of 116GB and can function as stand alone units. Acquired data can be
transferred via interfaces in runtime mode, via time-controlled events, or via the device's
USB ports.

1722

May 2011
4.2.1
Safety Advice
WARNING!
The connecting terminals carry electrical potential from the attached sensors/
actuators.
Before coming into contact with the connections, ensure the power is off. Check
for any voltages at the connecting terminals when the attached sensors have
varying degrees of electrical potential or when they have high electrical
potentials with earthing, e.g. when measuring electrical current for a mains
voltage phase.
Differences in electrical potential between two channels can not be detrmine
from the measurement data.
Refer to Potential differences.

May 2011
1723
4.2.2
Introduction
Dear User,
Thank you for purchasing a device from the Expert Vibroseries. We are sure that by
purchasing this device you have acquired a top class product to offer you a multitude of
options for data acquisition and processing.
This manual is intended for technicians and engineers or similarly qualified persons wishing
to user the device.
If you find errors in the product or in this documentation, or if you have any suggestions
for its improvement, we welcome your feedback.
Contact:
Lustheide 81
Phone: +49 2204 97685 -0
Telefax: +49 2204 97685 -85
Contact USA:
Virginia, USA
Telephone: +1 804 217 8391
Telefax: +1 804 747 6182
4.2.2.1 Included in delivery:

Expert Vibro device
Plug(s) for inputs and outputs and power supply
Brackets for rail mountings
1724

May 2011
Ethernet crossover cable

Software CD ProfiSignal
Documentation
4.2.2.2 System requirements

Operating system
Main memory
at least 2 GB*,
Monitor
CPU
Hard drive
4.2.2.3 Symbols used in this documentation

WARNING!
This symbol warns of a potential hazard which if the safety requirements are
not followed may be fatal or cause serious physical injury.

May 2011
1725
Info
Refers to a special option or explains an interesting feature.
We use italics to highlight individual terms within the text. Keyboard input is highlighted in
device. Also
highlighted in grey and displayed in italics are the dialog headings, buttons, check boxes,
input field names, etc. Display status.
Symbol
CE symbol The CE symbol guarantees that our products meet the requirements of relevant
EU directives. refer also to the EC Declaration of Conformity section.
1726

May 2011
4.2.3
Getting started
This section explains:

What you have to connect to your device before commencing work.
The software that needs to be installed on your PC.
How to establish a connection between a PC and the device.
The settings required to get the first measurement signals from your device.
For detailed information refer to these sections:
The section Expert Vibro displays and connections gives an overview of all the
connections, the display and LEDs.
The section Configuration and operation explains the different options for setting up
the device for measurement tasks.
The section on Examples of connections shows the options for connecting standardtype sensors and actuators and how to configure them.
The section on Measurement technology contains general information and
recommendations on applying measurement technology.
Technical data is available in the section on Technical specifications.
4.2.3.1 Getting Expert Vibro operational

Just a few steps are required to start using the Expert Vibro device:
Unpack the device.
Connect a power supply of 12..24 VDC to the 3-pin, black connector and insert it into
"Power" socket on the device.
Refer also to Expert Vibro displays and connections
The plug is polarity-protected and can be inserted into the socket in only one way.
Connect the power adapter into the mains socket.
The next steps are:
Installing programs
Establishing a PC connection
Basic settings
4.2.3.2 Installing programs
Administrator rights are required to install the programs.
Install the ProfiSignal CD. Ensure that the DataService software is installed as a program
(and not as a Service).

May 2011
1727
Following installation, these two desktop icons should appear:
Delphin's DataService Configurator software operates as a connection bewteen the PC

and the measurement hardware. The Expe rt Vibro devices are configured in DataSe rv ice
Co nfig urato r.
ProfiSignal is software for evaluating and visualizing measurement data.
Information for administrators

To establish a connection between a PC and an Expert Vibro device, ports
80 and 1033 need to be enabled.
4.2.3.3 Establishing a PC connection

To establish a connection between a PC and a Expert Vibro device, ports 80 and 1033 need
to be enabled. If you use the Windows-Firewall you may receive a warning when
attempting to establish a connection. A user with administrator rights may need to permit
the connection.
Info
As an alternative to the method described here, you can also set the IP
address and subnet mask via the Expert Vibro device's display. Refer to
Network configuration via the display.
Establishing a direct connection between a PC and device

Connect the PC and the device using the supplied Ethernet crossover cable.
The connection between the device and PC can also be made via a network hub
or switch.
Establishing a connection to the device
1.Start the DataService Configurator to establish a connection and to carry out
configuration.
The DataService starts and a Connections tab is displayed on the left of the
2.Select Connect
Add driver (connection) Search Delphin devices in LAN. Alternatively
you can use the DataService... context menu as shown here in the in image.
1728

May 2011
3.A device search is performed and a dialog displayed with the found device or
devices.
4.In the column Add, click the device(s) to which you wish to establish a
connection. Then click Add.
If the device's IP address does not correspond to the IP address of your PC, you
will need to set a different network address. If a device is not found, e.g.
because the UDP scan (port 16555) required for finding devices is not permitted
in your network, you can either directly connect the device to your PC (without
a network) or use the method described under Direct connection to a PC and
fixed address.
5.If the device's User management is enabled, you will receive an additional dialog.
Enter your login data under user name and password.
A successful connection is then displayed with an IP address and a status. The
information in the line called DataService and under the column Host/IP is your
PC's host name and IP address.

May 2011
1729
Setting a different network address
If the current IP address does not correspond to your PC's IP address, you will be given
the opportunity to change it following the device search and before connecting the
device:
Enter an appropriate IP address corresponding to your PC's IP address (similar but not
the same) and subnet mask. For a new device, enter root as user; the user name and
password are relevant only if you have enabled User management in the device. Enter
the information required and click OK. The settings will be made. You now need to
perform a new search (click Update).
Alternatively you can change the IP address via the touch display: Click Network and
then on the number to be changed. User the keys above and below the numbers to
increase or lower the number being displayed.
A third option is to change the setting via an internet browser:
1.Open the browser and enter the address http:// plus the current address of the
device, e.g. http://192.168.251.252.
A connection will be made to the device and the start page is displayed.
2.Click on Network under Settings.
A page with the network settings is displayed.
3.Enter the address required for your network at IP Address. The subnet mask and
gateway, or DNS and NTP server can also be entered (refer to web browser
configuration)
4.Click Save when finished to store the settings.
Refer also to Network settings (Main settings), NTP
Direct connection to a PC and fixed address
If the UDP scan is not permitted in your network, (port 16555 not enabled for UDP),
the DataService Configurator will not be able to find the device. You will then have to
establish a direct connection between the PC and device and then set the PC to the
device's address to establish a connection. Once you have established a connection,
you can change the device's address (as descibed above) for it to function in your
network. The ports 80 (connection via a web browser) and/or 1033 (connection via the
DataService Configurator) have to be enabled for the TCP protocol.
1730

May 2011
The factory-setting IP address for the Expert Vibro device is shown on a label on the
device. If the label has been lost during transport, try using the IP address
192.168.251.252 (network mask: 255.255.240.0).
Set (temporarily) your PC's IP address to a different address within the same IP
segment:
1.Run the network connection dialog.
2.Depending on the operating system being used, the dialog can be accessed from
either the Windows Start button and Network settings or via the Control Panel,
Network and Sharing Center.
3.Display the Properties of the connection (interface) to which the device is to
connect (usually labelled Local Area Connection). In Windows Vista and Windows
7, click Status , then Properties .
4.Display the Properties for the internet protocol.

May 2011
1731
5.In the next dialog you can set either a fixed address for your PC, or if the PC is
set to DHCP and used in the LAN use the option of an alternative configuration if
no network (server) is available (this is the recommended approach).
6.Enter an address that falls within the same segment as the address of the device
(refer to above example). Also set the subnet mask.
7.Close all dialogs by clicking OK .
Retry connecting to the device but use the menu Connect
Vibro.
Add Delphin device
Expert
1.Enter in the dialog the device's IP address, e.g. 192.168.251.252.
2.If User management is enabled in the device, enter your login data under User
Name and Password.
3.Click OK to establish a connection.
1732

May 2011
4.Once you have established a connection, set the device to an address (as
described above) that functions in your network. Don't forget to reset your PC to
its original address if this is required.
Offline configuration
If you wish to use an already saved configuration, select Connect

Expert Vibro.
Add Delphin device
Enable Offline configuration and enter the path and file name or click on Select to search
for the file.
The configuration file is then loaded. The device contained in the configuration file
appears in the channel tree structure as if it physically exists.
Any changes you make to the configuration are saved directly to the
configuration file.
Info
To establish a connection via XML, port 1035 for TCP must be enabled. For
a connection via Websocket, port 1036 for TCP must be enabled.

May 2011
1733
4.2.3.4 Basic settings

The DataService Configurator dialog is split enabling a device to be selected on the left
under Connections and settings to be made on the right under Channels .
Displaying measurement data

Once a connection has been established (refer to the previous section ) current
measurement data can then be displayed. Double click your device in the right window,
(Expert Vibro in the example), then on I/O Channels to open the item and all the current
channels and channel groups. If applicable, click on a channel group and then on an input
or output to display a sub-item(s). The Value column is continuously updated with new
measurement data.
Displaying scaled measurement data
To convert data from the sensor into the required measurement unit requires configuration
of the channel. Right click a channel to display the Properties dialog. A general explanation
of dialogs is available under the settings for all dialogs section. Special settings for
different channel types (analog input, analog output) can be found in subsections of the
configuring channels (sensors) section. The dialog also displays an overview of
connections.
Other settings
Setting digital-I/O
You can also set the scaling for inputs with counter functions. Set which signal
(channel) requires output at a constant level.
Specific settings for a device
Options are available for system monitoring e.g. CPU utilization or available memory
as well as configuring interfaces for your applications.
1734

May 2011
Creating calculation channels (independent channels)

Your Expert Vibro device is capable of processing data before its is saved or output.
The corresponding settings are described in configuring software channels.

May 2011
1735
4.2.4
Expert Vibro displays and connections
Connections are described in the following sections:

Power supply
Display, LEDs
COM interfaces, CAN-Bus
Sensor connection (plugs)
4.2.4.1 Power supply
Input voltage: 12 24VDC 10%

Power input P max : 10 W
Pin assignment
Pin
Label
Description
Upper
PE
Protective Earth , refer to

earthing
Middle
0V
Neutral
Lower
24V
Power supply
1736

May 2011
4.2.4.2 Display, LEDs
Display
The display is touch sensitive. You can therefore display the relevant menu item by tapping
the display. You can also connect a mouse to the USB port and click the menus via a
mouse cursor.
The settings for the port are explained in Network configuration via the display. The menus
and symbols are described in Configuring and operating the display..
LED lamps
System LED
Die Power-LED blinks at around 1Hz as soon as a functioning power supply is attached. In
standby, the LED blinks every 5 seconds for around 0.1 seconds.
LEDs next to the display
In the alarm status factory setting, The LEDs next to the display show whether any
messages are available or whether emails have been sent. Configure the LED display
DataService Configurator via System
LED.
LEDs LAN1 (interface to PC)

LED
Status
Description
Left
Off
No connection
Green, nonflashing
Connected, data not being transferred
Green, flashing
Data transfer
Off
Half duplex
Orange, nonflashing
Full duplex
Orange, flashing
Collision
Right

May 2011
1737
LEDs LAN2 (interface for expansion bus)

LED
Status
Description
Right
Off
No connection
Green, nonflashing
Connected, data not being transferred
Green, flashing
Data transfer
Off
Half duplex
Orange, nonflashing
Full duplex
Orange, flashing
Collision
Left
4.2.4.3 COM interfaces, CAN-Bus
COM1/2 and CAN1/2
Pin wiring 9-pin D-SUB connector

Pin
Signal
COM1/2 RS-485
CAN1/2 (CiA
(IEC 61158)
DS102-1)
Housing
Shield
Shield
Shield / protective
ground, refer to
earthing
CANL
CAN-Bus Low
RxD/TxD-P / B
Receive/transmit
data plus (RS-485)
RTS
Control signal for

repeater (TTL)
1738

May 2011
GND / C
Data reference
potetnial / neutral
VP
Power supply / Plus

(5V)
CANH
CAN-Bus High
RxD/TxD-N / A
Receive/transmit
data minus (RS485)
Not connected
Info
No galvanic isolation between CAN1 and COM1 and/or CAN2 and COM2.
COM3
Pin wiring 9-pin D-SUB plug

Pin
Signal
COM3 DIN 41 652, Teil 1
(ISO 4902)
Housing
Shield
Shield / protective ground,

refer to earthing
DCD
Received signal level, Data

Carrier Detect (RS-232)
RxD
Receive Data (RS-232)
TxD
Transmit Data (RS-232)
DTR
Data Carrier Detect (RS232)
GND
Signal ground

May 2011
1739
Not connected
RTS
Request to Send (RS-232)
CTS
Clear to Send (RS-232)
Not connected
4.2.4.4 Sensor connection (plugs)
Terminals 1 to 48)
Terminals 49 to 96)
1740

May 2011
4.2.5
The following sections are covered here:

The device's main settings, e.g. network settings or device ID, are explained under
Device configuration.
Configuration of the display, as well as an explanation of the display's symbols and
menus are available under Configuring and operating the display.
Channel configuration is explained in detail under Channel (sensor) configuration.
Settings and operation, which are the same for all MetiOS devices, are available under common
device settings. These include:
The Configuration via web browser section explains the (device) settings that you
can make via an internet browser.
The following functions are available only via the device's weeb interface: Resetting
to factory settings and updating the device's firmware. Some basic settings are also
possible, e.g. to the Ethernet interface or device-clock.
Devices are equipped with internal memories to enable configurations to be saved.
The ***Memory section explains how this storage space can be used, e.g. for
partitioning across different channel groups.
The Data transfer to USB memory stick section explains how to externally back up
internally stored data.
Read the Configuring interfaces for external devices section on how to use the
various interfaces for connecting or exchanging data with external devices.
The Configuring software channels section describes the various ways in which to
perform calculations on the measurement data or between channels.
See also Getting Started , Settings for all dialogs .
4.2.5.1 Overview
See also Getting Started
Configuration of the most important parameters, e.g. network settings, can be performed
either via the device's web interface or the DataService Configurator. Settings via the web
interface are described in the Configuration via web browser section. The configuration of
any sensor and actuator connections, and the definition of calculation (software channels)
takes place via the DataService Configurator and is explained in the sections that follow. A
detailed description of the DataService Configurator is available in the manual on the

May 2011
1741
Clicking the DataService Configurator starts the DataService background program and
establishes a connection to the devices (the default for the first installation is explained in
the Getting Started section). The DataService Configurator dialog is split enabling a device
to be selected on the left under Connections and settings to be made on the right under
Channels . The device itself is then portrayed as a "channel" and is listed as "Expert Vibro
'ExpVib-SN4108...'" in the example.
Channel configuration
Every configuration that you make in the DataService Configurator is referred to as a
channel configuration even when this concerns a device interface or memory group and not
a specific channel.
Amendments to configurations take immediate effect and the previous settings are
overwritten. The new settings are saved to the Expert Vibro device's non-volatile memory
and remain there even following a device reset.
Open the configuration dialog for a channel by double-clicking the channel name or rightclicking and selecting Properties from the context menu. Objects that do not have this entry
in their context menus are not configurable via the DataService Configurator but act as
containers, i.e. as channel groups for (more) child channels such as the "software
channels" group.
Channels from a channel group are displayed by clicking the corresponding plus sign (
1742
).

May 2011
DataService Configurator options

Hide or show columns for the different tabs:
View
Left panel Visible columns ... or View
Right panel
Set the DataService Configurator time zone: View
Visible columns ...
Timezone .
Change the DataService Configurator's display language via Options
Language .
Suppress confirmation requests:

Options Don't prompt for confirmation.
Change channel order via Options
User-defined view ).
Activate channel move / link (Only available in the
Further information is available in the manual for the DataService Configurator .
4.2.5.2 Network configuration via the display

The settings that you can perform via the display concern the main settings to enable
communication via the Ethernet interface. Further settings are required to operate the
device. Refer to Settings for configuring via an internet browser, and Network settings
(Main settings) for configuring via the DataService Configurator.
After changing the IP address or subnet mask, the device is then only
connection.
Tap
on the upper right of the start display to get to the main menu. Settings for
connecting to a PC are available via
(Settings)
(Lan 2).
Settings
If you enable Automatically (DHCP) (by tapping the right field), the device attempts to
automatically retrieve an IP address from the DHCP server. Even in this case, enter an
(alternative) IP address: this will be used by the device in the event that no address is
provided by the DHCP server.
Enter the IP address, Subnet mask and Default-Gateway, digit-group by digit-group: tap the
number-group to to display the digits; you can change them using the + and - symbols.
Input is restricted to numbers between 0 and 255 (the display makes adjustments if
necessary). Ask your administrator whether input for Gateway and MTU is required for your
network. Otherwise leave the default setting of 1500 for MTU. A gateway address is
If the address is already being used, you will receive an error message and the option to
change it. Delete erroneous input using .
Amendments to settings become active by tapping Save. Tap Cancel for the device to
ignore your input.

May 2011
1743
4.2.5.3 Display configuration and operation

Configure the data displayed on the start page via the DataService Configurator (System
Display). Up to 7 lines can be displayed.
Refer also to Network configuration via the display.
Menu
Tap
on the upper right of to get to the main menu.
Meaning of display symbols
Back to start
Switch to channel view
Make settings
Close menu
Quick tap: Switches off the display illumination. Longer tap: Displays a menu to
reboot or shutdown the device.
Channel view
Use the display to make additional settings to the channel list:

(Settings)
(Channel list). You can select between displaying only active channels(Empty value filter is
enabled) and displaying by ascending/descending alphabetical name (Sort by name enabled).
Different pages can be displayed via the channel view (opened with
). Move to the
next/previous using the up/down arrows. The current page and the number of available
pages are displayed between the arrows:
1744

May 2011
Tap a channel to maximize the display: The channel name and current measurement value
is then displayed. Tap the white part of this display to re-display the channel view. Tap
to open the Main menu.
Info
Open the information display via

(Settings)
(Information). This displays the
hardware and software versions and the device's serial number.
Tap
to open the main menu.
4.2.5.4 Expert Vibro device configuration

The top level of the Channel in the DataService Configurator is the device level. The userdefined view (image above) shows the software channels, system monitor, I/O channels,
interfaces and the memory. The hardware view (lower image) shows the software
channels, system monitor, the different interfaces, the I/O channels, the memory and the
USB ports.

May 2011
1745
This section concerns the devices settings that you have to perform yourself. In the
example, this takes place via the Expert Vibro-SN41080240.TI... in the Channel tab of the
DataService Configurator. Use the Properties context menu to amend a device name and ID
or to enter a description for the device. Use Main settings context menu to amend network
and NTP settings.
Refer to Configuring main unit, Network settings, NTP
For explanations of other settings, refer to:
Software channel configuration for software channels
Channel (sensor) configuration for I/O channels
Interface configuration for the interfaces CAN, COM and PROFIBUS
Memory for internal memory
Info
For general information on configuration dialogs (including header and
footer), refer to Settings for all dialogs.
4.2.5.5 Configuring channels (sensors)

How to configure software channels, interfaces (for external devices) and memory is
explained in the corresponding sections.
Refer also toOverview, Galvanic isolation, Specifications
The I/O channels are grouped together to give an optimal overview:
Analog outputs
Digital inputs
Digital outputs
1746

May 2011
Trigger groups with analog input 1, the input for rotation speed and the three other
analog inputs
Additional digital outputs 5 to 8 are shown below trigger group 4. The trigger groups show
you which analog inputs can be synchronized with which rotation speed channels.
Trigger groups
Before configuring the analog inputs, configure the trigger groups. This is
because the functioning of the analog inputs in the the group depend on
the trigger group settings.
The trigger configurations set how the signals from the analog channels,
and any calculations dependent on them, are processed, e.g. whether
measurement is to take place over a period of time or over a specific
number of rotations.
Method for analog inputs

1.Make settings for the sensor type and sensor measurement range via the Properties
context menu for each input.
2.Set how the sensor signal is to be used. Each input delivers a signal that is pre-set
as track. You can however define other tracks (Track context menu). Each track can
be given different properties such as scaling, sampling frequency and filtering, i.e.
you can have a sensor's signals simultaneously evaluated in different ways.
3.Set what characteristic value is to be determined for a track or whether a spectrum
(for example) is to be calculated for this track (optional setting).
4.If you want to have either characteristic values or a spectrum calculated, you can
still create dependent channels that enable further evaluation.
Info
You can evaluate each input via multiple tracks. This enables the use of
different filters, the determination of multiple characteristic values
(spectrum, min/max values) or different storage variants. The configuration
of a channel with different tracks can be saved (Child channels
Add to
library) or copied and then transferred to other channels.
Method for digital inputs

1.Set the logical level for the input signal (normal or inverted).
2.State the default value to be used in the event that an input fails.
3.Indicate whether you require dependent channels that will enable further evaluation.
The majority of calculations are available that are also available for software
channels.
Methods for analog and digital outputs
1.Set the output source (signal, channel, manually input value etc.).

May 2011
1747
2.State the default value to be used in the event that an input signal fails.
3.Set whether the last output value is to be saved so that this value can be re-output
in the event of a network failure.
4.2.5.5.1 Trigger groups
The settings fro a trigger group has a major influence on the way the dependent channels
and tracks acquire and process data.
Triggering: Set whether triggering of evaluation is to take place after a specific Time
(periodic) or is dependent on a Channel, i.e. synchronous with a channel. The calculations
for a track then take place for the given time or for the period between the trigger pulses
of the given channel. You can also set multiple periods(Number of trigger pulses) .
Refer also to Edge trigger option
When selecting an Analog input under Channel, further options are available:
Threshold is the decisive value for monitoring.
Hysteresis : Hysteresis prevents the trigger being repeatedly activated for small fluctuations
Refer to the images. The hysteresis is especially beneficial for small (noise) signals.
1748

May 2011
Debounce: Enable this option, in addition to hysteresis, when your signal has short peak
levels with high amplitudes. In this event you need to select a relatively high hysteresis to
prevent the trigger activating. Enter the maximum length of time that the pulse can have
to be suppressed.
4.2.5.5.2 Configuring a rotation-speed channel
Indicate under Scaling whether a conversion should take place into another unit.

May 2011
1749
Set the edge and level (Threshold) at which the amplitude of the signal is valid. If you do
not enable Positive edge, the negative edge is used.
The channel is required for various calculations, e.g. for all calculations dependent on
rotation speed.
4.2.5.5.3 Configuring analog inputs
Before you configure the analog inputs, configure the trigger group. This is
because the functioning of the analog inputs depend on the trigger group.
The trigger configurations set how the signals from the analog channels,
and the calculations dependent on them, are processed, e.g. whether
measurement is to take place over a period of time or over a specific
number of rotations.
If you wish to use functions dependent on rotations, configure also the
rotation channel.
Voltage sensor type
1750

May 2011
IEPE feeding
For ICP - and IEPE sensors, activate IEPE feeding. Please note the additional
connections to be undertaken that are given under Connection. The sensor is then
supplied with voltage and the signal decouples.
Refer also to sensor connection, IEPE and ICP sensors
AC coupling
Select AC coupling if you want to exclude DC components. In this case, only the AC
current component of your signal is acquired.
DC components (DC offset) can also be suppressed via a track.

May 2011
1751
Current sensor type
Measurement range
Enter the current according to sensor type. For sensors with 0 to 20 or 4 to 20mA
output, you can directly select the measurement range via Sensor type. In all other
cases, select Current and enter the measuring range 0 100mA .
Shunt resistor
Enter the shunt resistance being used. Depending on the shunt resistance, an
extended current range is available in the measuring range for Current. Delphin offers
various shunt resistances for measuring currents. Contact us to obtain a suitable
resistance.
Current measurement is not possible without a shunt resistance.
AC coupling
Select AC coupling if you want to exclude DC components (DC-offset). In this case, only
the AC current element of your signal is acquired.
DC components (DC offset) can also be suppressed via a track.
1752

May 2011
4.2.5.5.4 Track configuration
Create one or multiple tracks via the context menu of an analog input.
A track limits an A/D conversion rate of 50kHz to a reasonable value for evaluation. You
can also do this in several steps, e.g. by calculating a spectrum for high measurement
rates, then using this to determine the main frequency for averaging over multiple
measurements.
Info
You can save the configuration for track via the Partial configuration menu
item. The file can then be opened and copied and transferred to another
track using Replace.

May 2011
1753
Main settings
Sampling frequency
Manual: Set the data rate at which the measurements are to be acquired. The band
width deriving from the sampling rate is displayed.
Rotation speed controlled: For rotation speed measurements, you can use the group's
rotation speed channel as a trigger channel for all the group's channels and adapt the
sampling frequency to the rotation speed. This ensures that the same number of
measurements are acquired per rotation for both high and low rotation speeds. After
enabling, enter the number of rotations for measurement data acquisition in Periods.
Refer also to the rotation speed amendment in the Filter tab and trigger group.
1754

May 2011
Scaling
Enter two points from the sensor's characteristic curve, if possible the lower and upper
vertexes. For linear characteristic curves, the measurement values are then converted
to the unit of measurement measured by the sensor. For non-linear characteristic
curves, use also a linearization (refer to software channel linearization. The specified
range (in the example 0 to 500 bar) is used as the default for the display area for
graphics in ProfiSignal. The channel receives the status "scale range overrun" for "scale
range underrun" when not within the range. Channel status values are available in the
status monitoring table.
Create measuring: When enabled, all measurement values are transferred despite, for
example, only one measurement value being displayed in the DataService Configurator
under the Channels tab. If you need only characteristic values, you don't need "raw
data" being written to the database. The displaying of single measurement values in
the DataService Configurator functions even when the option is not enabled. You only
need to enable this option when you wish to graphically view the overall results.
Without steady component: Removes the steady component (DC offset) in the signal, i.e.
only the AC component is output.
Refer also to AC coupling input
Filter
Select the required filter or calculation functions by clicking the symbol. Double clicking
integrator enables you to set a double integration. If you select the wrong filter or
calculation, click it again to disable it (grayed out). You can also select a function
using Preset.

May 2011
1755
The example shows that high pass, band stop (at 300 Hz) and low pass have been
selected.
Enter the cut off (or frequency for band stop) according to the filter. A band width
also needs to be entered for a band stop. The ordering depends on the steepness of
the filter's slope/gradient but a higher ordering requires more processing time. Select
the your filter's characteristics. The ripple resulting from the settings can be changed
for some filters but otherwise is only displayed (grayed out).
If you selected sampling frequency via rotation speed in the Main settings tab, you
should enable Rotation speed tracking so that the filter adapts to the rotation speed
frequency.
Info
If you select integrator, high pass is automatically enabled.
Bode plot
Select Bode plot to open a window that displays the amplitudes and phases for the
selected settings.
hides/shows the grid.
switches the frequency axes between a linear and logarithmic portrayal.
hides/shows a red cursor (line) with information on amplitude, frequency and phase.
Move the cursor to the required position to display the information.
enables you to shift the displayed curves within the windows.
hides the red cursor.
Reset sets the display to the default settings.
1756

May 2011
The example shows the amplitude and phase progressions for the settings above. The
cursor is positioned on the band stop's frequency.
4.2.5.5.4.1 FFT/Spectrum generation
If you are creating a spectrum (via a Fast-Fourier-Transformation, i.e. a FFT) for a track,
enter how the calculation is to be performed via the Main settings tab.

May 2011
1757
Window function: Sets which window function is to be used. Hamming or Hanning are well
suited for signals that do not begin or end at zero over the time range of a single FFT.
Number of samples: Determines the number of measurement values to be used for a
calculation.
Data type: :Sets the calculation to be performed: Magnitude or Phase.
Averaging: Averages the results from multiple FFTs.
Suppress DC line: Removes the DC component (amplitude of 0Hz).
Overlapping: If the number of measurement values exceeds the number of samples, multiple
FFTs are calculated. To avoid edge effects, the FFTs should not be calculated from
sequential sections. The sections from which calculations are performed should overlap.
Values between 33% and 66% are usually sufficient in practice.
under the Channels tab. If you need only characteristic values, you don't need "raw data"
being written to the database. The displaying of single measurement values in the
DataService Configurator functions even when the option is not enabled. You only need to
enable this option when you wish to graphically view the overall results.
1758

May 2011
4.2.5.5.4.2 Creating characteristic values (frequency/amplitude/phase) from FFT
This function enables you to extract additional characteristic values from a spectrum. The
functions available are frequency (determines characteristic values based on frequency)
and amplitude (determines characteristic values based on amplitude) .
Frequency
Use the Main settings tab to set the frequency of the system's main oscillation or to set
the range/band in which the characteristic values are to be determined. Enter either a
Fixed frequency band or band dependent on rotation speed (Rotation speed adapted frequency
band).
Main oscillation of the complete spectrum: The largest amplitude is searched and its
frequency output.
Fixed frequency band/Rotation speed adapted frequency band: The largest amplitude in a
specific frequency band is searched and its frequency output. The frequency band is
determined via the Median and Width and/or the Min/Max of the rotation speed.

May 2011
1759
Info
The Rotation speed adapted frequency band requires a configured rotation
speed channel.
Amplitude
1760

May 2011
In the Main settings tab, set which characteristic values are to be determined: Maximum
value, RMS, Sum or Remainder and via which harmonic band this is to take place.
If the calculation is not to be performed for the complete spectrum, you can select
partial bands via Range. Enter a Fixed frequency band, a band for a harmonic frequency
(Harmonic Band) or a band dependent on rotation speed (Rotation speed adapted frequency
band) an.
Fixed frequency band/Rotation speed adapted frequency band: The largest amplitude in a
specific frequency band is searched and its frequency output. The frequency band is
determined via the Median and Width and/or the Min/Max of the rotation speed.
Harmonic band: Determines the amplitude via a band that extends from the 1st harmonic
(frequency) to the given harmonic, e.g. up to the 5th harmonic. The following image
shows the 1st and 2nd harmonic.
Info
The Harmonic band and Rotation speed adapted frequency band require a
configured rotation speed channel.
4.2.5.5.4.3 Creating Min/Max/Peak values
This function enables you to determine a signal's minimum value (lower value in the
diagram), maximum value (upper value in the diagram) or the peak-to-peak value
(difference between minimum and maximum values). The time period in which the
characteristic values are calculated is determined from the settings for the trigger group.

May 2011
1761
Select the required function via the Main settings tab.
Smooth curve, Eliminate glitches: You can smooth the curves or remove the brief peaks of
periodic signals that have overlapping noise or overlapping short but high interference levels
before determining the characteristic values.
4.2.5.5.4.4 Creating mean/true RMS
This function enables you to determine the mean average or true root mean square
(TRMS). The arithmetical average is also referred to as a signal's steady or DC component.
The characteristic value is also available by activating the "AC coupling" option (refer to
analog input configuration). The time period in which the characteristic values are
calculated is determined from the settings for the trigger group.
The average is calculated using the following formula:
1762

May 2011
The TRMS is calculated using the following formula:
Info
The accuracy for TRMS calculations on sine signals depends on the number
of signal periods acquired. The rule of thumb: the probability for errors is
less than 3% for more than 2 periods and less than 1% for more than 4
periods. You enter the periods via the settings for the trigger group.
Apply window function: Select this option to calm measurement data for a static vibration.
This applies a weighting before the mean or TRMS is determined. The signal's boundaries
are given less weight and more weight is given to the signal's middle.

May 2011
1763
4.2.5.5.4.5 Creating vector sums
This function performs a vectorial addition of all amplitude values from the time signals of
two channels and then determines the average (Mean), Minimum or Maximum. The time
period in which the characteristic values are calculated is determined from the settings for
the trigger group.
Smooth curve, Eliminate glitches: You can smooth the curves or remove the brief peaks of
periodic signals with overlapping noise or overlapping short but high interference levels
before determining the characteristic values.
1764

May 2011
4.2.5.5.5 Digital input configuration
Debounce: To hide short interference pulses, enter here a time period that should pass
before a signal is evaluated.
Invert : This option inverts a "High" level at input to a "Low" level at output (measurement
signal in device) and vice versa.
under the Channels tab. The displaying of single measurement values in the DataService
Configurator functions even when the option is not enabled. You only need to enable this
option when you wish to graphically view the overall results.

May 2011
1765
4.2.5.5.6 Digital output configuration
Value source
Use Channel to select an existing channel whose value is to be output or enter a constant
value manually (Manual value) via the DataService Configurator or automatically via a
ProfiSignal application (Application).
Invert: When enabled, inverts a "High" level to a "Low" at the output and vice versa.
1766

May 2011
4.2.5.5.7 Analog output configuration
You can output either currents or voltages.

Main settings
Enter here the scaling for the output.

Sensor compensation
For setting corrections to the output characteristic curve.

May 2011
1767

Offset
measurement value.
Offset and gradient
Allows a shifting of the cure and an increase in its slope. The example in the
above image shows the values for a measurement with calibration at 0N and
100N.
Square
values.
Spline Interpolation
A spline interpolation determines the best possible ploynomial of the 3rd grade
(cubic spline) for the given values and converts the measured values.
Info
You can use copy and paste to transfer data from an Excel table into
the dialog's table. Position the cursor in the table's top left field left
field. Extra rows are created automatically when this is permitted by
the selected mode.
Click on a row and use the Del key to delete unwanted rows. Insert
extra rows in a linear interpolation using the Return key .
Import.
4.2.5.6 Collective device settings
1768

May 2011
4.2.5.6.1 Configuration via an internet browser
Info
within the device.
4.2.5.6.1.1 Settings
clicking Save .
connection.

May 2011
1769
ntp.htm .
1770

May 2011
Info
Using a GPS clock


May 2011
1771
Info
4.2.5.6.1.2 Configuration

1772

May 2011


May 2011
1773

Info
web interface.
4.2.5.6.1.3 Service

project program.
1774

May 2011
the web interface.
Info

May 2011
1775
Method
1776

May 2011
4.2.5.6.1.4 System

back on again.
Info

May 2011
1777
to 6 minutes.
1778

May 2011
the device.
after a restart.

May 2011
1779
Info

Info
4.2.5.6.2 Main menu device settings
1780

May 2011
4.2.5.6.2.1 Device configuration (channel configuration)

acquire data.
Device ID
columns.

May 2011
1781
Method
4.2.5.6.2.2 User management configuration
Guest
User manager.
1782

May 2011
Administrator
root
Important
management.
Adding a user
Click New user.
Deleting a user
deleted.
Amending a user

May 2011
1783
Activating a user

User rights
Configurator.

1784

May 2011
4.2.5.6.2.3 Network settings (Main settings), NTP

May 2011
1785
server.
Info

Using a GPS clock
enable reception.

1786

May 2011
Anonymous login


User: Administrator
Important
management.
4.2.5.6.2.4 Saving and loading device configurations
Save settings

May 2011
1787
Load settings
Restore channels
1788

May 2011
Restore users


Configurator.
environment.
4.2.5.6.2.5 Tables
of the device.
Local

May 2011
1789
it is configured.
Linearization.

Method
(Mode ).
5.Click Save.
1790

May 2011
Mode
Offset
measurement value.
Offset and Gradient
C.
Squarely
values.
values.
Info
Import .
Info
Import .

May 2011
1791
1792

May 2011
Method
4.Click Add.
6.Click Save.
system.
Global settings
Point no.
Absolute
Relative

May 2011
1793
Example of a table
time.
4.2.5.6.3 Settings for all dialogs
1794

May 2011
Upper section


May 2011
1795
Info
here.
Lower section

the following tabs:
Main settings
Advanced settings
Sensor compensation
Information
1796

May 2011
4.2.5.6.3.1 Advanced settings tab (software channels)
options Off and On.
4.2.5.6.3.2 Sensor compensation

May 2011
1797

Offset
measurement value.
Offset and slope
0 C and 100 C.
Squarely
values.
values.
Info
Import .
1798

May 2011
4.2.5.6.3.3 Information

May 2011
1799
4.2.5.6.3.4 Basic channel selection


4.2.5.6.3.5 Advanced channel selection
Info
Windows.
displayed.
1800

May 2011

and channel ID.
Info
4.2.5.6.3.6 Edge and level triggers
Edge and level

May 2011
Level
Edge (full)
Edge (basic)
1801
Setting
Description
Rising edge
Falling edge
Edge (both)
High level
Low Level
4.2.5.6.3.7 Inherit status
4.2.5.6.4 Configuring Software channels

1802

May 2011
Linking channels
manual.
Software channels.
4.2.5.6.4.1 Accumulator
source channel.

May 2011
1803
4.2.5.6.4.2 Operating hours counter
Info
amended.
counter.

4.2.5.6.4.3 Differentiator
base:
Differential = (

4.2.5.6.4.4 Ereignis
1804

May 2011
4.2.5.6.4.5 FlipFlop

JK Flip-Flop
Status
Clr
Pre
(clock)
(clear)
(preset
)
1
Previous status
Toggle

May 2011
1805
RS-Flip-Flop
Status
S+
Clr
Pre
set
(clock
(clear
(pres
priorit
et)
y
1
Previous
state
D-Flip-Flop
Status
C (clock)
Clr
Pre
(clear)
(preset)
Previous state
1806

May 2011
Latch
Status
C (clock)
Clr (clear)
D (transparent)
Previous state
4.2.5.6.4.6 Limit
Mode
Alert when
Overrun
Underrun
Band monitoring
Band violation
Steady condition

May 2011
1807
4.2.5.6.4.7 Impulse generator

1808

May 2011

May 2011
1809
1810

May 2011
Examples
Example 1

May 2011
1811
at 08:49:50.
1812

May 2011
Example 2

May 2011
1813
already begun.
1814

May 2011
Example 3
signal.
a)

May 2011
1815
b)
1816

May 2011
c)
"low".

May 2011
1817
d)
1818

May 2011
4.2.5.6.4.8 Integrator

zero.
4.2.5.6.4.9 Channelgroups
4.2.5.6.4.10 Linearization

tab

May 2011
1819
Method
2.Select a source.

Offset
measurement value.
Offset and Gradient
Squarely
values.
values.
Info
Import .
1820

May 2011
4.2.5.6.4.11 Logic
Info
Click
to delete an input.
Function table NOT
Input value
Output value
Function table AND

Input value A
Input value B
Output value

May 2011
1821
Function table OR
Input value A
Input value B
Output value
Input value A
Input value B
Output value
Input value A
Input value B
Output value
Input value A
Input value B
Output value
Function table NAND
Function table NOR
1822

May 2011
Function table XNOR

Input value A
Input value B
Output value

Input value A
Input value B
Input value C
Output value

May 2011
1823
Input value A
Input value B
Input value C
Output value
4.2.5.6.4.12 Variables
1824

May 2011
4.2.5.6.4.13 Average


May 2011
1825
4.2.5.6.4.14 PID-Regler
4.2.5.6.4.15 Pulse width modulation (PWM)
4.2.5.6.4.16 Calculation channel
Method
invalid.
1826

May 2011
Example
and adds an offset.

May 2011
1827

Type of
Function
calculation
Basic
calculations
Data types
Syntax
Operand1
Operand2
Addition
bool, int, float
bool, int, float
Operand1 +
Operand2
Subtraction
bool, int, float
bool, int, float
Operand1 Operand2
Multiplication
bool, int, float
bool, int, float
Operand1 *
Operand2
Division
bool, int, float
bool, int, float
Operand1 /
Operand2
AND
bool, int, float
bool, int, float
Operand1 &&
Operand2
OR
bool, int, float
bool, int, float
Operand1 ||
Operand2
NOT
bool, int, float
! Operand1
AND
bool, int
bool, int
Operand1 &
Operand2
OR
bool, int
bool, int
Operand1 |
Operand2
XOR
bool, int
bool, int
Operand1 ^
Operand2
Negation
bool, int
bool, int
~Operand1
Left-shift
bool, int
bool, int
Operand1 <<
Operand2
bool, int
bool, int
Operand1 >>
Operand2
Minimum
bool, int, float
bool, int, float
MIN
(operand1,
operand2)
Maximum
bool, int, float
bool, int, float
MAX
(operand1,
Logical
operations
Binary
operations
(Move
operand1 to
the left by the
number of
places in
operand2)
Right-shift
(Move
operand1 to
the right by
the number of
places in
operand2)
Operations
with sets
1828

May 2011
Type of
Function
calculation
Data types
Operand1
Syntax
Operand2
operand2)
Matching
operations
Trig functions
Reverse trig.
Functions
Other
operations or
functions
Less than
bool, int, float,

string
bool, int, float,

string
Operand1 <
Operand2
Less than or
equal
bool, int, float,

string
bool, int, float,

string
Operand1 <=
Operand2
Greater than
bool, int, float,

string
bool, int, float,

string
Operand1 >
Operand2
Greater than
or equal
bool, int, float,

string
bool, int, float,

string
Operand1 >=
Operand2
Equals
bool, int, float,

string
bool, int, float,

string
Operand1 ==
Operand2
Not equal to
bool, int, float,

string
bool, int, float,

string
Operand1 !=
Operand2
Tangent
bool, int, float
TAN
(Operand1)
Cosine
bool, int, float
COS
(Operand1)
Sine
bool, int, float
SIN
(Operand1)
Arctangent
bool, int, float
ATAN
(Operand1)
Arccosine
bool, int, float
ACOS
(Operand1)
Arcsine
bool, int, float
ASIN
(Operand1)
Exponential
bool, int, float
EXP
(Operand1)
Power
bool, int, float
bool, int, float
POW(basis,
factor)
POW
(Operand1,
Operand2)

May 2011
Square
bool, int, float
SQRT
(Operand1)
Modulo
bool, int, float
bool, int, float
Operand1 %
Operand2
Absolute
bool, int, float
ABS
(Operand1)
1829
Type of
Function
calculation
Data types
Syntax
Operand1
Operand2
Natural
logarithm
bool, int, float
LN(Operand1)
Logarithms
(base 10)
bool, int, float
LOG
(Operand1)
Pi
PI
Euler's
number e
EX
Constants
Data types
bool: True or false
int: an integer
4.2.5.6.4.17 Collective fault
Method
and click

selection.
1830
to remove the

May 2011
4.2.5.6.4.18 Setpoint
required.
active.

May 2011
1831
Table tab
Method
2.Click Add.
selected row.
trigger:
system.
1832

May 2011
Global settings
Point no.
Absolute
Relative
Example
4.2.5.6.4.19 Statistics

functions.

May 2011
1833
Definitions
values.
4.2.5.6.4.20 Status monitor
Selection
Description
Alarm
Alarm, range error
Wire break
Configuration error
Invalid
Measuring range
overrun
Measuring range
underrange
Hardware failure
Simulated value
Not A Number
(NAN)

negative number
Default value
1834

May 2011
Selection
Description
Forced value
Scale range
overrun
Scale range
underrun
General warning

End of a trigger
block
Input value out of

range
a parameter error
4.2.5.6.4.21 Stopwatch
only).

May 2011
1835
Example 1
Case 1
level time.
1836

May 2011
Case 2

May 2011
1837
Example 2
Case 1
1838

May 2011
Case 2

May 2011
1839
4.2.5.6.4.22 System monitor


Selection
Description
Unit
CPU usage
CPU usage
application

CPU Usage system
Free memory
MB
Used memory
MB
Up time system

Days
Up time application

Days
4.2.5.6.4.23 Trigger
value.
4.2.5.6.4.24 Uhr
1840

May 2011
4.2.5.6.4.25 Alarmclock
specified duration.
4.2.5.6.4.26 Counter

enabled.

May 2011
1841
1842

May 2011

May 2011
1843
4.2.5.6.4.27 Timer
1844

May 2011
during the delay.

May 2011
1845
1846

May 2011
Example of a reset
4.2.5.6.5 Configuring interfaces
section.
CAN connection
CAN protocol

May 2011
1847
CAN bus channel

COM port
PROFIBUS protocol
PROFIBUS channel
4.2.5.6.5.1 Ethernet connection
device.
Modbus output.
Modbus internal
Modbus input and/or
device.
Modbus output.
Modbus internal
Modbus input and/or
4.2.5.6.5.2 CAN-Controller

. The CAN
1848

May 2011
Location.
Main settings tab
Baudrate
communication.
up to 60m: 250kBaud
Extended ID

May 2011
CAN-Driver (RAW).
1849
The symbol

CAN Protocol RAW).
1850

May 2011
Main settings tab

Data type settings
Data type
Signed
Bit length

May 2011
1851
Encoding type
Byte order
Word order
be necessary.
Byte pattern
CAN message.
Byte offset
Bit offset
default is 0
CAN ID
Extended ID
ID
values.
1852

May 2011
Mask
and 100111.
Scaling
Info
the channel.
Scaling example

May 2011
1853

4.2.5.6.5.3 COM-Port

. The COM
Main settings tab
Interface Mode
1854

May 2011
Info

PROFIBUS-Driver
PROFIBUS-Channel
PROFIBUS-Driver .

if required.
master.
Info

May 2011
1855
settings.

Info
settings.
The symbol
1856

May 2011


Main settings tab
Data type settings

Data type
Signed
Bit length

May 2011
1857
Encoding type
Byte order
Word order
be necessary.
Byte pattern
Byte offset
Info
Bit offset
default is 0.
1858

May 2011
Scaling
Info
the channel.
for
users.
Main settings tab

May 2011
1859
Device name
Device address
Time settings
Poll cycle
Timeout
Pause
Sequential query
The
, Modbus
1860

May 2011
Main settings tab
Device name
Device address
The
Modbus
symbol, a Modbus
output channel with

.
Main settings

May 2011
1861
type of register.
Data type settings
input or output.
Data type
Signed
Bit length
Encoding type
Byte order
Word order
be necessary.
message.
Scaling
1862

May 2011
Info
Scaling example

May 2011
1863

Main settings
output channels.
1864

May 2011
Time settings
Poll cycle
saved.
Timeout
Pause
Pollstring
Termination
Termination symbol

May 2011
1865
Bus idle characters

required.
Decimal separator
1.Main settings tab
2.Input tab
Data type settings

Data type
1866

May 2011
Signed
Bit length
Encoding type
received.
Byte order
Word order
be necessary.
Byte pattern
message.
Scaling
Info
Scaling example

May 2011
1867
Time settings
Timeout
Pause
Polled
Pollstring
Filter
Delimiter
1868

May 2011
Decoding
Offset
Maximum length
are ignored.
Main settings tab
Data type settings
Data type
zeroes.

May 2011
1869
Pre decimal place

Leading zeroes
Post decimal place
Always sign
Example
Format
%DAY%: Current day.
1870

May 2011
Source
status.
Output
Cyclic
has elapsed.
Adaptive
changed.
Never

May 2011
1871
Initialization
Response expected
Timing
1872

May 2011
4.2.5.6.6 Device memory
memory is full.

May 2011
1873

times.
1874

May 2011

May 2011
1875

Info
reinstated.
Allowed .
4.2.5.6.7 Data transfer to USB memory stick
1876

May 2011
Info
data transfer.

blinking.
option.

5.Click Save.

May 2011
1877
or
1878

May 2011
4.2.6
The section contains general information and recommendations on using measurement

technology.
4.2.6.1 Galvanic isolation

Within a single device, all I/O modules and interfaces, Ethernet, CAN1, CAN2, COM1, COM2
and COM3 are galvanically isolated from the main unit (CPU and power) as well as from
each other. The CAN1 and COM1 interfaces are not isolated from each other. The same
applies to COM2 and CAN2. system requirements mean the USB ports are also not
galvanically isolated.
The diagram shows the the individual galvanic isolation for the device.
Refer also to shielding.

May 2011
1879
4.2.6.2 Earthing
The PE terminal for the power supply is the device's ground. This terminal is internally
connected to the metal housings of the USB-/LAN and COM ports but has no connection to
the 0 V terminal(s).
Connect the PE terminal with a 2.5 mm 2 cable to the protective earth of your power
supply.
Refer also to Shielding , Galvanic isolation.
4.2.6.3 Earth loops

By linking sensors, measurement devices and PCs creates connections between different
ground points. Unless the individual devices are connected to protective earth, this electro
conductive connection creates an electrical circuit between the devices. The result is a
so-called ground loop (shown as red in the diagram).
This can have the following effects:
In practice, the earthing points U1 U3 shown in the diagram do not necessarily
possess equal potential. Constant or changing potential differences can occur
between the earthing points due to the earthing plan and wiring. Compensating
currents then occur in the sensor and communication circuits.
Interference in the sensor or communication circuits, e.g. through electromagnetic
fields, enable parasitic currents to occur within the circuit.
Compensation and parasitic currents lead to interference or noise voltage at the input of
the measuring instrument and thus constant or shifting errors in measurement.
1880

May 2011
Prevent earth loops!
Earth loop between sensormeasurement device

Galvanic isolation to the central unit means earth loops cannot occur in the device via the
sensor circuit as shown in the diagram . However, earth loops can occur between the
sensors of different channels of a module.
To avoid such loops, we recommend the use of earth-free sensors or signal sources.
Earth loop between measuring devicecomputer
Most of the device's interfaces are galvanically isolated from each other and from the
central unit. The earth loop via the communication circuit as shown in the diagram can not
occur with the device.
Use these interfaces to connect the device to PCs, PLCs or to equipment from other
manufacturers.
Refer also to galvanic isolation.
4.2.6.4 Shielding
Measurement signals can be disrupted by the occurrence of magnetic and electric fields in
the measuring circuits, e.g. generated by neighbouring current-carrying circuits. Shielded
cables should therefore always be used for sensor circuitry and kept at least 50 cm away
from other current-carrying circuits.
The smaller the sensor signal and / or the higher the sensor impedance, the more important
good shielding is for a low-noise, accurate readings.
To prevent earth loops, earth the shield on one side of the circuit only (see example).
a) Sensors without earth
Earthing of the shield is in this case one-sided and directly at the device (PE
connection on the power supply).
b) Sensors with earthing

When the use of earth-free sensors is not possible, earth the shield only or attach it
to the sensor's earth potential (see example).

May 2011
1881
4.2.6.5 ESD protection

The device has an earth terminal specifically for ESD protection of the inputs (ESD,ElectroStatic Discharge): 50 to 55, 58 to 63, 66 to 71 and 74 to 78.
Connect this with a PE-labelled terminal via a cable of 2,5mm2 to the protective earth.
Discharge static before coming into contact with the I/O modules. Just
place your hand on an earth protected housing or PE terminal. If you don't
do this, the inputs could become damaged.
4.2.6.6 Potential differences

Potential differences can, in principle, always occur between reference potentials of
multiple-sensor signals that are connected to the analog inputs of an I / O module. The
following figure shows the sensor signals as green arrows and U mess , and the potential
difference between the two sensor signals as an orange arrow and U Difference.
1882

May 2011
The reference potential of a measurement circuit for a device's analog input occurs by a
change of channel of the sensors' different reference potentials. Depending on the input
circuit of a device's different inputs, the differential-voltage U between the channels may
not exceed the specified maximum values. These are the "Permissible differential voltages
from channel to channel" specified in the Technical specifications.
WARNING!
The connecting terminals carry electrical potential from the attached sensors/
actuators.
Before coming into contact with the connections, ensure the power is off. Check
for any voltages at the connecting terminals when the attached sensors have
varying degrees of electrical potential or when they have high electrical
potentials with earthing, e.g. when measuring electrical current for a mains
voltage phase.
determined from the measurement data.

May 2011
1883
Info
If the connected sensors have different potentials and high currents are
expected in the event of a short circuit between the sensor potentials,
take measures to protect the device and the measurement installation from
subsequent damage.
1884

May 2011
4.2.7
Connection examples
This section gives examples of typical sensor and actuator connections. It explains the
available connection options exist and how sensors and actuators are configured.
4.2.7.1 Sensor connection
Measuring voltages at an analog input

Info
The measurement range is 25V bipolar.
20 mA current measurement at an analog input

Sensors with current signals require connection of a load resistor at the device's input
terminals. Resistors are available as accessories.
Info
The load resistance must be between 10
and 500
Sensor at a digital input

Level detection

May 2011
1885
Info
To ensure detection, the input signal must have a "low" level in the range
from 0 2,5V, a "high" level in the range from 3.1 50V and a minimum
pulse width of 1ms. A maximum of 50 signal changes per second (maximum
signal frequency) can be recorded.
IEPE/ICP sensor
For an IEPE and/or ICP sensor feed, connect terminals 49 (or 57, 65 or 73 depending
on the input) with +24V and terminal 56 (or 64, 72 or 80) with 0V or the negative
pole of the supply voltage. The power supply from the Expert Vibro device is sufficient.
A separate supply is unnecessary.
For potential earth use the terminals between 49 and 56 (or between the other
connections).
4.2.7.2 Actuator connection
Actuator at an analog output
1886

May 2011
Info
The maximum shunt resistance of an actuator is 650 .
Info
The minimum load resistance of an actuator is 2.5 .

May 2011
1887
Actuator at a digital output, resistive load

Info
The maximum switching voltage is 50V and a maximum switching
current of 1A.
Actuator at a digital output, inductive load

Info
The maximum switching voltage is 50 V, and a maximum switching
current of 1A.
To protect the output's electronic switches, we recommend switching
to recovery diodes in parallel with inductive loads.
1888

May 2011
4.2.8
Inputs/outputs
Analog inputs
8 or 16
Sampling rate, adjustable per channel
1Hz to 50,000Hz
Voltage range
25V
Current range
0 to 20mA, 4 to 20mA, optional
Signal conditioning, adjustable via

software
DC coupling, AC coupling, IEPE/ICP
Resolution
24 bit
Input impedance
1M
Dielectric withstand voltage/ galvanic

isolation channel to channel
100VDC / 500VDC
Band width of the primary signal:
DC 20kHz
Digital frequency inputs, galvanically
isolated
High level
5 50VDC / 3.5mA
Low level
0 2V / 3.5mA
Measurement range, frequency
0.2Hz 1MHz
Analog outputs, galvanically isolated
Resolution
16bit
Output range
0 10V / 10V / 0 20mA / 4 20mA
Maximum shunt resistance
500
Digital outputs, galvanically isolated
Switching voltage/ current
50V / 0.6A
Frequency range
5Hz 10kHz
PWM
up to 1:500
Data storage
Maximum size

May 2011
16GB
1889
Maximum measurement values
1billion
Signal processing functions

High pass filter
Cut-off frequency
0.5Hz 20,000Hz
Filter ordering
4, 6, 8, 10
Filter characteristic
Bessel, Butterworth, Chebyshev
Low pass filter

Cut-off frequency
0.5Hz 20,000Hz
Filter ordering
4, 6, 8, 10
Filter characteristic
Bessel, Butterworth, Chebyshev
Integrator / Differentiation
Single or double integrator, differentiation
FFT
Line numbers
Maximum 12,800
Window function
Hanning, Hamming, Flat-Top
Averaging
2 32-times
FFT types
Narrow and wide band, envelope curve,

demodulation, amplitude and phase
spectrum
Characteristic values from time signals

Min-/Max value, peak-to-peak value, arithmetic average, TRMS, maximum of vectorial
sums, arithmetic average of the product
Characteristic values from a frequency
spectrum
Frequency, main oscillation phase, any harmonic amplitude phase, frequency of any
harmonic amplitude, sum value including quadratic mean (in any frequency band), sum
or remainder
Interfaces
LAN
2 x 1000Base-TX
1890

May 2011
WLAN / WWAN
802.11b/g/n, GPRS, UMTS, LTE
USB
USB 2.0 full speed (USB 1.1 compatible)

for device and host interface, USB ports
type A and B
PROFIBUS
2 x PROFIBUS DPV1, Slave max. 12 MB
CAN
2 x CAN 2.0B, ISO 11898-1, ISO 11898-2
RS-232
9-pin D-SUB connector, 3 pins used
RS-485
9-pin D-SUB connector, pins assigned

according to IEC 61158; Modbus RTU,
SCPI, ASCII protocols
General technical information

Dimensions
210mm x 80mm x 125mm
Mounting
Rail according to DIN EN 60715
Weight
ca. 750g
Signal connections
96 terminals in 2 rows, max. 1.5mm2
Temperature range
-20 ... 60 C
Power supply
12 24VDC 10%
Power input
ca. 10W

May 2011
1891
4.2.9
Appendix
4.2.9.1 EC declaration on conformity

??
1892

May 2011
4.2.9.2 ISO 9001 certificate

May 2011
1893
4.3
Collective device settings
1894

May 2011
4.3.1
Info
within the device.
4.3.1.1 Settings
4.3.1.1.1 Network
clicking Save .
connection.

May 2011
1895
ntp.htm .
1896

May 2011
Info
Using a GPS clock


May 2011
1897
4.3.1.1.2 Clock
4.3.1.1.3 NTP status
1898

May 2011
Info
4.3.1.2 Configuration

May 2011
1899
4.3.1.2.1 View channels
4.3.1.2.2 Default channel configuration

1900

May 2011

Info
web interface.
4.3.1.3 Service
project program.

May 2011
1901
4.3.1.3.1 System report
the web interface.
4.3.1.3.2 PROFIBUS GSD file
Info
1902

May 2011
4.3.1.3.3 XML template for network configuration
Method

May 2011
1903
4.3.1.4 System
back on again.
4.3.1.4.1 Update firmware
Info
1904

May 2011
to 6 minutes.

May 2011
1905
4.3.1.4.2 Firmware changelog
1906

May 2011
4.3.1.4.3 Restart main application
the device.
after a restart.
Info
4.3.1.4.4 Reboot
Info

May 2011
1907
4.3.2
4.3.2.1 Device configuration (channel configuration)


acquire data.
Device ID
1908

May 2011
columns.
Method
4.3.2.2 User management configuration


May 2011
1909
Guest
User manager.
Administrator
root
Important
management.
Adding a user
Click New user.
Deleting a user
deleted.
Amending a user
1910

May 2011
Activating a user

User rights
Configurator.


May 2011
1911
4.3.2.3 Network settings (Main settings), NTP

1912

May 2011
server.
Info

Using a GPS clock
enable reception.

May 2011
1913
4.3.2.3.1 Zeitzone/ Synchronisation
4.3.2.3.2 Dienste
4.3.2.3.3 Enabling user management
Anonymous login

1914

May 2011

User: Administrator
Important
management.
4.3.2.3.4 Mailserver
4.3.2.4 Saving and loading device configurations
Save settings
Load settings

May 2011
1915
Restore channels
Restore users

1916

May 2011

Configurator.
environment.
4.3.2.5 Tables
of the device.
Local
it is configured.

May 2011
1917
4.3.2.5.1 Global linearisation tables
Linearization.

Method
(Mode ).
5.Click Save.
1918

May 2011
Mode
Offset
measurement value.
Offset and Gradient
C.
Squarely
values.
values.
Info
Import .
Info
Import .

May 2011
1919
4.3.2.5.2 Global setpoint tables
1920

May 2011
Method
4.Click Add.
6.Click Save.
system.
Global settings
Point no.
Absolute
Relative

May 2011
1921
Example of a table
time.
1922

May 2011
4.3.3

May 2011
1923
Upper section

Info
here.
Lower section
1924

May 2011

the following tabs:
Main settings
Advanced settings
Sensor compensation
Information
4.3.3.1 Advanced settings tab (software channels)
options Off and On.

May 2011
1925
4.3.3.2 Sensor compensation


Offset
measurement value.
Offset and slope
0 C and 100 C.
Squarely
values.
1926

May 2011
values.
Info
Import .
4.3.3.3 Information

May 2011
1927
4.3.3.4 Basic channel selection


4.3.3.5 Advanced channel selection
Info
Windows.
displayed.
1928

May 2011

and channel ID.
Info
4.3.3.6 Edge and level triggers

Edge and level

May 2011
Level
Edge (full)
Edge (basic)
1929
Setting
Description
Rising edge
Falling edge
Edge (both)
High level
Low Level
4.3.3.7 Inherit status

1930

May 2011
4.3.4

Linking channels
manual.
Software channels.

May 2011
1931
4.3.4.1 Accumulator
source channel.
4.3.4.2 Operating hours counter

Info
amended.
counter.

4.3.4.3 Differentiator
base:
Differential = (

1932

May 2011
4.3.4.4 Ereignis
4.3.4.5 FlipFlop
JK Flip-Flop
Status
Clr
Pre
(clock)
(clear)
(preset
)
1
Previous status
Toggle

May 2011
1933
RS-Flip-Flop
Status
S+
Clr
Pre
set
(clock
(clear
(pres
priorit
et)
y
1
Previous
state
D-Flip-Flop
Status
C (clock)
Clr
Pre
(clear)
(preset)
Previous state
1934

May 2011
Latch
Status
C (clock)
Clr (clear)
D (transparent)
Previous state
4.3.4.6 Limit
Mode
Alert when
Overrun
Underrun
Band monitoring
Band violation
Steady condition

May 2011
1935
4.3.4.7 Impulse generator

1936

May 2011

May 2011
1937
1938

May 2011
Examples
Example 1

May 2011
1939
at 08:49:50.
1940

May 2011
Example 2

May 2011
1941
already begun.
1942

May 2011
Example 3
signal.
a)

May 2011
1943
b)
1944

May 2011
c)
"low".

May 2011
1945
d)
1946

May 2011
4.3.4.8 Integrator
zero.
4.3.4.9 Channelgroups
4.3.4.10 Linearization
tab

May 2011
1947
Method
2.Select a source.

Offset
measurement value.
Offset and Gradient
Squarely
values.
values.
Info
Import .
1948

May 2011
4.3.4.11 Logic
Info
Click
to delete an input.
Function table NOT
Input value
Output value
Function table AND

Input value A
Input value B
Output value

May 2011
1949
Function table OR
Input value A
Input value B
Output value
Input value A
Input value B
Output value
Input value A
Input value B
Output value
Input value A
Input value B
Output value
Function table NAND
Function table NOR
1950

May 2011
Function table XNOR

Input value A
Input value B
Output value

Input value A
Input value B
Input value C
Output value

May 2011
1951
Input value A
Input value B
Input value C
Output value
4.3.4.12 Variables
1952

May 2011
4.3.4.13 Average

May 2011
1953
4.3.4.14 PID-Regler
4.3.4.15 Pulse width modulation (PWM)

4.3.4.16 Calculation channel

Method
invalid.
1954

May 2011
Example
and adds an offset.

May 2011
1955

Type of
Function
calculation
Basic
calculations
Data types
Syntax
Operand1
Operand2
Addition
bool, int, float
bool, int, float
Operand1 +
Operand2
Subtraction
bool, int, float
bool, int, float
Operand1 Operand2
Multiplication
bool, int, float
bool, int, float
Operand1 *
Operand2
Division
bool, int, float
bool, int, float
Operand1 /
Operand2
AND
bool, int, float
bool, int, float
Operand1 &&
Operand2
OR
bool, int, float
bool, int, float
Operand1 ||
Operand2
NOT
bool, int, float
! Operand1
AND
bool, int
bool, int
Operand1 &
Operand2
OR
bool, int
bool, int
Operand1 |
Operand2
XOR
bool, int
bool, int
Operand1 ^
Operand2
Negation
bool, int
bool, int
~Operand1
Left-shift
bool, int
bool, int
Operand1 <<
Operand2
bool, int
bool, int
Operand1 >>
Operand2
Minimum
bool, int, float
bool, int, float
MIN
(operand1,
operand2)
Maximum
bool, int, float
bool, int, float
MAX
(operand1,
Logical
operations
Binary
operations
(Move
operand1 to
the left by the
number of
places in
operand2)
Right-shift
(Move
operand1 to
the right by
the number of
places in
operand2)
Operations
with sets
1956

May 2011
Type of
Function
calculation
Data types
Operand1
Syntax
Operand2
operand2)
Matching
operations
Trig functions
Reverse trig.
Functions
Other
operations or
functions
Less than
bool, int, float,

string
bool, int, float,

string
Operand1 <
Operand2
Less than or
equal
bool, int, float,

string
bool, int, float,

string
Operand1 <=
Operand2
Greater than
bool, int, float,

string
bool, int, float,

string
Operand1 >
Operand2
Greater than
or equal
bool, int, float,

string
bool, int, float,

string
Operand1 >=
Operand2
Equals
bool, int, float,

string
bool, int, float,

string
Operand1 ==
Operand2
Not equal to
bool, int, float,

string
bool, int, float,

string
Operand1 !=
Operand2
Tangent
bool, int, float
TAN
(Operand1)
Cosine
bool, int, float
COS
(Operand1)
Sine
bool, int, float
SIN
(Operand1)
Arctangent
bool, int, float
ATAN
(Operand1)
Arccosine
bool, int, float
ACOS
(Operand1)
Arcsine
bool, int, float
ASIN
(Operand1)
Exponential
bool, int, float
EXP
(Operand1)
Power
bool, int, float
bool, int, float
POW(basis,
factor)
POW
(Operand1,
Operand2)

May 2011
Square
bool, int, float
SQRT
(Operand1)
Modulo
bool, int, float
bool, int, float
Operand1 %
Operand2
Absolute
bool, int, float
ABS
(Operand1)
1957
Type of
Function
calculation
Data types
Syntax
Operand1
Operand2
Natural
logarithm
bool, int, float
LN(Operand1)
Logarithms
(base 10)
bool, int, float
LOG
(Operand1)
Pi
PI
Euler's
number e
EX
Constants
Data types
bool: True or false
int: an integer
4.3.4.17 Collective fault

Method
and click

selection.
1958
to remove the

May 2011
4.3.4.18 Setpoint
required.
active.

May 2011
1959
Table tab
Method
2.Click Add.
selected row.
trigger:
system.
1960

May 2011
Global settings
Point no.
Absolute
Relative
Example
4.3.4.19 Statistics
functions.

May 2011
1961
Definitions
values.
4.3.4.20 Status monitor

Selection
Description
Alarm
Alarm, range error
Wire break
Configuration error
Invalid
Measuring range
overrun
Measuring range
underrange
Hardware failure
Simulated value
Not A Number
(NAN)

negative number
Default value
1962

May 2011
Selection
Description
Forced value
Scale range
overrun
Scale range
underrun
General warning

End of a trigger
block
Input value out of

range
a parameter error
4.3.4.21 Stopwatch
only).

May 2011
1963
Example 1
Case 1
level time.
1964

May 2011
Case 2

May 2011
1965
Example 2
Case 1
1966

May 2011
Case 2

May 2011
1967
4.3.4.22 System monitor



Selection
Description
Unit
CPU usage
CPU usage
application

CPU Usage system
Free memory
MB
Used memory
MB
Up time system

Days
Up time application

Days
4.3.4.23 Trigger
value.
4.3.4.24 Uhr
1968

May 2011
4.3.4.25 Alarmclock
specified duration.
4.3.4.26 Counter
enabled.

May 2011
1969
1970

May 2011

May 2011
1971
4.3.4.27 Timer
1972

May 2011
during the delay.

May 2011
1973
1974

May 2011
Example of a reset

May 2011
1975
4.3.5
section.
CAN connection
CAN protocol
CAN bus channel
COM port
PROFIBUS protocol
PROFIBUS channel
4.3.5.1 Ethernet connection

device.
Modbus output.
Modbus internal
Modbus input and/or
device.
1976
Modbus internal

May 2011

Modbus output.
Modbus input and/or
4.3.5.2 CAN-Controller
. The CAN
Location.
Main settings tab
Baudrate
communication.
up to 60m: 250kBaud

May 2011
1977
Extended ID
4.3.5.2.1 CAN-Driver
The symbol
CAN-Driver (RAW).
4.3.5.2.2 CAN -Bus-Channel

CAN Protocol RAW).
1978

May 2011
Main settings tab

Data type settings
Data type

May 2011
1979
Signed
Bit length
Encoding type
Byte order
Word order
be necessary.
Byte pattern
CAN message.
Byte offset
Bit offset
default is 0
CAN ID
Extended ID
1980

May 2011
ID
values.
Mask
and 100111.
Scaling
Info
the channel.
Scaling example

May 2011
1981

4.3.5.3 COM-Port
. The COM
Main settings tab
Interface Mode
1982

May 2011
Info

PROFIBUS-Driver
PROFIBUS-Channel
4.3.5.3.1 PROFIBUS Protokoll
PROFIBUS-Driver .

if required.
4.3.5.3.1.1 PROFIBUS main settings, PROFIBUS-Driver
master.
Info

May 2011
1983
settings.

Info
settings.
The symbol
1984

May 2011
4.3.5.3.1.2 PROFIBUS-Channel


Main settings tab
Data type settings

Data type
Signed

May 2011
1985

Bit length
Encoding type
Byte order
Word order
be necessary.
Byte pattern
Byte offset
Info
Bit offset
default is 0.
1986

May 2011
Scaling
Info
the channel.
4.3.5.3.2 Modbus-RTU-Protokoll
for
4.3.5.3.2.1 Modbus-RTU-Master

users.

May 2011
1987
Main settings tab
Device name
Device address
Time settings
Poll cycle
Timeout
Pause
Sequential query
The
1988

May 2011
4.3.5.3.2.2 Modbus-RTU-Slave
, Modbus
Main settings tab
Device name
Device address
The
4.3.5.3.2.3 Modbus-RTU-Kanal
Modbus
symbol, a Modbus
output channel with

.
Main settings

May 2011
1989
type of register.
Data type settings
input or output.
Data type
Signed
Bit length
Encoding type
1990

May 2011
Byte order
Word order
be necessary.
message.
Scaling
Info
Scaling example

May 2011
1991

4.3.5.3.3 Benutzerdefiniertes Protokoll

4.3.5.3.3.1 Benutzerdefiniertes Protokoll
Main settings
1992

May 2011
output channels.

May 2011
1993
Time settings
Poll cycle
saved.
Timeout
Pause
Pollstring
Termination
Termination symbol
Bus idle characters
1994

May 2011
required.
Decimal separator
4.3.5.3.3.2 Benutzerdefinierter Eingangskanal
1.Main settings tab
2.Input tab
Data type settings

Data type

May 2011
1995
Signed
Bit length
Encoding type
received.
Byte order
Word order
be necessary.
Byte pattern
message.
Scaling
Info
Scaling example
1996

May 2011
Time settings
Timeout
Pause
Polled
Pollstring
Filter
Delimiter

May 2011
1997
Decoding
Offset
Maximum length
are ignored.
4.3.5.3.3.3 Benutzerdefinierter Ausgangskanal
Main settings tab
Data type settings
Data type
1998

May 2011
zeroes.
Pre decimal place
Leading zeroes
Post decimal place
Always sign
Example
Format

May 2011
1999

%DAY%: Current day.
Source
status.
Output
Cyclic
2000

May 2011
has elapsed.
Adaptive
changed.
Never
Initialization
Response expected
Timing

May 2011
2001
4.3.6
Device memory
memory is full.
2002

May 2011

times.

May 2011
2003
2004

May 2011

Info
reinstated.
Allowed .

May 2011
2005
4.3.7
Info
data transfer.

blinking.
option.
2006

May 2011

5.Click Save.
or

May 2011
2007
Average 1560, 1825, 1953

Averaging (FFT) 1757
Index
- B-
-[[PICTURE Analoganzeige Einstellung Skala.png]

398
[PICTURE ISO9001.png]
85
Band stop 1753

Basic channel selection 1535, 1800, 1928
Basic Settings
1452, 1734
Batch alarms
1565, 1830, 1958
-1-
-C-
150 Hz
206
-22. Upper wave
206
-AAC-coupling 1750
Activation
Email activation 102
Fax activation 102
Online activation 102
Telephone activation 102
activation key
102
Add connection 161
Adder 1538, 1803, 1932
Adding an online analysis
1093
Advanced channel selection 1535, 1800, 1928
Advanced settings (software channels) 1532,
1797, 1925
Alarm clock
1576, 1841, 1969
Amplitude of a spectrum 1759
Amplitude:
(1/5*4/Pi) 206
Analog input
1487, 1750
Analog output
1501, 1767
Analysis
1250, 1254, 1257
Analysis functions, FFT diagram 1202
Analysis functions,Yt-diagram 1218
Analysis window
1119
Ansicht Merker 592
Ansicht MouseCursor 592
ASCII export (obsolete) 976
1268
ASCII export, column separation 1270
ASCII export, line separation 1270
Available diagrams, onlien analysis
1114
2008
Calculation channel 1561, 1826, 1954

CAN interface
Configuration 1583, 1848, 1977
CE symbol 1445, 1725
Change licence 108
Change marker time-stamp 1230
Channel configuration 1745
Channel configuration (Log-/ProfiMessage) 1480
Channel configuration (overview) 1478, 1741
Channel selection
Advanced 1535, 1800, 1928
Basic
1535, 1800, 1928
Channel settings dialog 1141, 1142
Channel settings, diagram 1141
Channel table 577, 1121
577
Channel table, diagram 1122
Channel table, FFT diagram 1196
Channel table, logic diagram 1164
Channel table, Yt-diagram 1148
Channel, 3. Upper wave 206
1186
Clock settings
1506, 1771, 1898
Color, channel 1141
COM interfaces
1738
Wiring 1459
Compensation 1487
Configuration 1134, 1516, 1781, 1908
via an internet browser 1503, 1769, 1895
Configure time axis, Yt-diagram 1160
Configuring main unit
1516, 1781, 1908
Connection
DataService (local) 115
DataService (via network) 115
Connections option
Main settings Data storage 138
Main settings General 137
Main settings Script
143
Connections options
May 2011
with counter function 1498

with frequency measurement
Digital output
1502, 1766
Display
1737
Display marker 1219
Display symbols
1744
Documentation 75
Connections options
Server main settings
141
Counter 1576, 1841, 1969
Current Measurement
1750
Current sensor type 1492
Current sensor type (0/4..20mA) 1493
Cursor, Auswertung Yt-Diagramm 590
Cursor, Yt-diagram 1160
Cursor, Yt-diagram evaluation 1149
-E-
-DData reduction 1532, 1797, 1925

Data transfer to USB 1611, 1876, 2006
Database 110, 241, 1291
saving 243
setup 243
Storing channels
250
Database option 241, 243, 250
DataService 110
Add connections
154
as Windows service 243
Establishing a connection 155
Network addresses
154
Network names
154
DataService Configurator 110
Add connections
132
Connections option 132
Service settings
132
DCP 1481
Debounce 1748
Default configuration 567, 1508, 1773, 1900
Default value 1532, 1797, 1925
Deleting module entries
1484
Delphin-CAN-Protocol 1481
Device 1454, 1736
Device configuration 1745
Device Configuration (Log-/ProfiMessage) 1480
Device connections
1454, 1736
Device ID 1516, 1781, 1908
Device memory
1608, 1873, 2002
Diagram layout
1121
Diagram layout, analysis
1121
Diagram type selection, analysis
1117
Dialog footer (explanation) 1529, 1794, 1923
Dialog for characteristic curve settings
1186
Dialog for export time range 1263
Dialog header (explanation) 1529, 1794, 1923
Dialogs in general, sensor compensation tab
1532, 1797, 1926
Differentiator 1539, 1753, 1804, 1932
Digital input
1500, 1765
May 2011
1498
Earth loops
1621, 1880
Earthing 1621, 1880
EC declaration on conformity
1719, 1892
Edge trigger 1536, 1801, 1929
Envelope curve, FFT diagram 1202
Ermittle Kanal-Id 1034
Escape sequences
1273
ESD protection 1623, 1882
Establishing a connection to the device 1448,
1728
Ethernet connection (for Modbus) 1583, 1848,
1976
Examples
Actuator connection 1886
Connecting actuators
1617
Connecting sensors
1614
Sensor connection 1885
Expansion Bus
maximum total length 1481
Expansion device 1481
Explorer view
1480, 1745
Export ASCII file 1264, 1268, 1273, 1293
Export to MesFile 975
Extended graph toolbox, FFT diagram 1206
Extension Bus
maximum total length 1481
External linearization tables
1525, 1790, 1918
External setpoint tables
1527, 1792, 1920
-FFFT cascade 1202

FFT diagram status bar 1209
FFT diagram, analysis
1195
FFT diagram, analysis functions
1202
FFT diagram, channel table 1196
FFT diagram, extended graph toolbox
1206
FFT diagram, graph area 1198
FFT diagram, graph toolbox
1202
FFT diagram, navigating data 1203
FFT diagram, order analysis
1204
2009
FFT diagram, settings dialog, analysis

1210
FFT spectrum 1202
File 310
File menu 310
Filter 1142, 1753
Filter activation 1141
Filter functions for measurement data 1141
Firmware changelog 1514, 1779, 1906
FlipFlop 1540, 1805, 1933
Format
1532, 1797, 1925
Formulary
1254
Formulary, analysis
1257
Frequency of a spectrum 1759
Frequency: 206
Included in delivery: 1443, 1724

Inherit status
1537, 1802, 1930
Initiate "Add channel"
937
Initiate "All channels visible"
939
Initiate "back to online Trend"
948
Initiate "Channel visible"
939
Initiate "Clear channel group"
937
Initiate "Delete channel"
938
Initiate "Freeze diagram"
949
Initiate "Show last recording"
951
Initiate "Show timerange"
950
Initiate, Actual marker 963
Initiate, Copy marker 960
Initiate, Create marker 958
Initiate, Delete marker 959
Initiate, Load marker 961
Initiate, Next marker 964
Initiate, Read marker 962
Initiate, Show marker 961
Initiate, Show textlabel 965
Install programs
1448, 1727
Integrated resistance 1481
Integrator 1554, 1753, 1819, 1947
Interface 309
Interfaces
1582, 1847, 1976
Internal battery replacement
1474
IP address
1504, 1520, 1769, 1785, 1895, 1912
ISO 9001 certificate 1721, 1893
-GGalvanic isolation 1620, 1879

Gateway
1504, 1520, 1769, 1785, 1895, 1912
General functions for the channel table, diagram
1122
Getting started 1447, 1727
Global alarm lists
1299
Grafischer Bereich, Yt-Diagramm 590
Graph area 1121, 1134
Graph area, FFT diagram 1198
Graph area, logic diagram 1166
Graph area, Yt-diagram 1149
Graph toolbox
1121
Graph toolbox functions, diagram 1136
Graph toolbox, diagram 1136
Graph toolbox, FFT diagram 1202
Graph toolbox, Yt-diagram 1156
Grid 1156
GSD file 1510, 1775, 1902
-KKeys
-LLamps
1457, 1737
LAN LEDs
1457, 1737
Language settings
130
LED lamps
1457, 1737
LEDs
1458
Level trigger 1536, 1801, 1929
License 102
Limit value 1542, 1807, 1935
Line spectrum, FFT diagram 1202
Line style 1141, 1156
Line width 1141
Linearization 1554, 1819, 1947
Linearization tables
1524, 1789, 1917
Linking trends and recorders
570
Load configuration 1522, 1787, 1915
Load resistor 1493, 1750
- HHigh pass
1753
Highlight selected channel
Hysteresis
1748
1141
-II/O module replacement

1467
I/O modules
Terminal assignment
1461
ICP sensor 1750
Identify an unknown IP address
1451
IEPE sensor 1750
If...then 860
2010
1454, 1736

May 2011
Load, save trend configuration 585, 1140

Logic
1556, 1821, 1949
Logic diagram, analysis
1163
Logic diagram, channel table 1164
Logic diagram, graph area 1166
Login 1517, 1522, 1782, 1787, 1909, 1914
Low pass
1753
Modbus
161
Master 1594, 1859, 1987
Protocols
1594, 1859, 1987
Slave 1595, 1860, 1989
Module information 1484
Module layout
1461
Module number 1484
Module replacement
1467
Module settings
1484
Module synchronization 1481
1151
Mouse mode within the trend graph 583, 1137
Mouse mode, diagram 1153
Mouse mode, move mouse cursor 1149
-MMain menu 115, 310

Connect
115
Login 120
Options
130
View
123
Manual sampling frequency
1753
Manual value, 0 Degree 206
Manual value, 5 Hz
206
Marker lines
1239
Marker View
1149, 1151
Markers
1218, 1559, 1824, 1952
Markers, Yt-diagram 1219
Master/Slave 1481
Mausmodus Diagramm 594
Mausmodus Maus Cursor bewegen 590
Maximum 1761
Mean 1762
Meaning of display symbols
1737
Measurement curve line style 1156
Measurement curve lines
1156
Measurement curve portrayal 1156
Measurement data analysis
1091
Measurement data preview
1116
Measurement data storage 110
Measurement database 1291
Add 243
Backup 247
Filter 248
Settings
244
Storage duration 245
Storage size 245
Trend optimization 247
Measurement range monitoring 1487
Memory
1608, 1873, 2002
Memory card installation and upgrade 1470
Memory groups
1293
Menu 310
Menu symbols in the display
1744
Merker Ansicht
590
Message devices
1293
Minimum 1761
May 2011
- NName: 206
Navigating data , FFT diagram 1203
Network
1504, 1520, 1769, 1785, 1895, 1912
Network settings
1448, 1504, 1520, 1728, 1769,
1785, 1895, 1912
Ni xxx
1494
NTP 1506, 1520, 1771, 1785, 1898, 1912
NTP status
1507, 1772, 1898
Number of samples (FFT) 1757
Number of trigger impulses fro a period 1748
-OOffline calculation channels

1254, 1257
Offset: 206
Onilne Analyse 1101
Online analysis
1092, 1093, 1095, 1096, 1097,
1099, 1103, 1114
1096
OPC Client
Add connections
158
Main settings
159, 161
Settings
158
OPC Server 158
OPC-Server 140, 141
Open measurement data file for analysis
1115
Opening an online analysis
1095
Operating hours counter 1539, 1804, 1932
Options
Copy ID 130
Language settings
130
Switch off security prompt
130
Orbit diagram, analysis
1211
Order analysis
1204
2011
Order analysis (FFT) 1757

Order analysis, FFT diagram
Order spectrum 1204
Overlapping (FFT) 1757
Readout device storage 1293

Reboot
1515, 1744, 1780, 1907
Reboot device 1515, 1737, 1780, 1907
Recorder save options
627
Recorder, online analysis
1101, 1103
Replacement
Battery
1474
I/O module 1467
Memory card 1470
Reset
1454
Resistance sensor type 1489
Resistance thermometer sensor type 1494
Restart main application 1514, 1779, 1907
RMS
1762
Rotation 1749
Rotation Speed 1749
1204
- PParameterView, Page settings

707
Password protected
general 87
Password protection
General 87
Project specific
87
Peak value 1761
Peak-To-Peak value 1761
Period duration 1748
Persistence 1532, 1797, 1925
Phase of a spectrum 1759
Phase: 206
Ports (TCP, UDP) 1728
Ports used (TCP, UDP) 1728
Post time synchronization 636
1624, 1882
Power input
1456, 1736
Power supply
1456, 1736
Power supply: 1456
Print diagram 1242, 1246
Print diagram, layout
1245
Print trend 1242
PROFIBUS
1510, 1775, 1902
Channel 1592, 1857, 1985
Drivers
1590, 1855, 1983
Main settings
1590, 1855, 1983
ProfiMessage
Add connections
150
Connect
151
ProfiSignal 110, 132
Pt xxx
1494
Pulse generator 1543, 1808, 1936
Pulse width modulation (PWM) 1561, 1826, 1954
PWM 1561, 1826, 1954
-S-
-QQuick Start
1447, 1727
- RReading out the memory of a Message device

1293
2012
Safety Advice 1442, 1723

Sampling frequency via rotation speed 1753
Sampling rate: 206
Save configuration 1522, 1787, 1915
Scaling 1753
Scheduler
Add event
282
Event
284
Read memory tab 289
Settings
284
Scheduler database 1291
Search 312
Search channel (explanation) 1529, 1794, 1923
Search dialog channel (explanation) 1529, 1794,
1923
Searching scripts
867
Select channel (explanation) 1529, 1794, 1923
Selecting channels for the trend 571
Sensor connection 1740
Set point tables
1524, 1789, 1917
Setpoint (software channel) 1566, 1831, 1959
Setting network address
1448, 1728
Setting up an application variable 818
Settings
161
Settings dialog, FFT diagram, analysis
1210
1529, 1794, 1923
1611, 1876, 2005
Shielding 1622, 1881
Show in trend 1292
Show text field 1238
Showing a database in a trend 1291
Shutdown 1744
Sine 206
May 2011
Slave device 1481

Software 1448, 1727
Software channels
1537, 1802, 1931
Sorting the channel table, diagram 1130
Start/stop settings
622
Statistic components
1250
Statistic components, analysis
1250
Statistics
1250, 1568, 1833, 1961
Status bar 1121
Status bar FFT diagram 1209
Status monitoring 1569, 1834, 1962
Stopwatch 1570, 1835, 1963
Stored configurations
1292
Subnet mask
1504, 1520, 1769, 1785, 1895, 1912
Switch off (device) 1737
Switch off device 1737
Switch off the display illumination 1744
Symbol, channel 1141
Symbols in the display
1744
Symbols in this document
1445, 1725
Symbols used in this documentation 1445, 1725
System monitoring 1575, 1840, 1968
System report
1510, 1775, 1902
System requirements
1444, 1725
Trend, Zeitbereich anzeigen 1133

Trigger (software channel) 1575, 1840, 1968
Trigger conditions
622
Trigger groups
1748
Trigger variants
1536, 1801, 1929
Triggering 1748
True RMS
1762
- UUDP scan 1728

Unknown IP address? 1451
Update Firmware 1512, 1777, 1904
Updating firmware 1514, 1779, 1906
USB 1457, 1737
USB Memory Stick
1611, 1876, 2006
User 1517, 1522, 1782, 1787, 1909, 1914
User interface 309
User management
1517, 1522, 1782, 1787, 1909,
1914
Using multiple devices
1481
-VVector sums
1764
Veranlasse "Pause Stoppuhr"
933
Veranlasse "Setze Startwert"
933
Veranlasse "Starte Stoppuhr"
932
Veranlasse "Stoppe Stoppuhr"
932
Veranlasse, Aktueller Zeitbereich 951
Verbindungsansicht
Grundeinstellungen Server 140
Vibration analysis
1195, 1211
View channels
1508, 1773, 1900
Voltage Measurement
1750
Voltage sensor type 1490
-TTabellenauswahl, YX-Diagramm (Tabelle) 607

Tables
1524, 1789, 1917
TCG 1134
1626, 1889
Main device 1626
Temperature formats
1494, 1496
Terminal 1451
Terminal block configuration 1461, 1740
Text field 1239
Thermocouple sensor type 1496
Threshold 1748
Time planner (refer to scheduler) 282
Timer 1579, 1844, 1972
Timezone 351, 1134
Timezone setting 351
Tool bar functions, diagram 1122
TopMessage 146
Add connections
145
Connect
148
Track
1753
Trend configuration 1134
Trend default view
567
Trend, Online-Zeitbereich einstellen 1134
May 2011
-WWaveform: 206
Web configuration 1503, 1769, 1895
Window function (FFT) 1757
Wire break monitoring 1487
Wiring 1738, 1740
-XX-axis settings, diagram
1129
2013
-YY-axis settings, diagram 1126

Yt-diagram, analysis
1146
Yt-diagram, analysis functions
1218
Yt-diagram, channel table 1148
Yt-diagram, configure time axis
1160
Yt-diagram, graph area 1149
Yt-diagram, graph toolbox
1156
Yt-diagram, markers
1219
Yt-Diagramm, Cursor 1160
Yt-Diagramm, Grafischer Bereich 590
YX-diagram 1175
YX-diagram (hardware), analysis
1175
YX-diagram color, analysis
1194
-ZZoom functions
Zoomfunktionen
1153
594
2014

May 2011

Delphin Help

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Delphin Help

Caricato da

Copyright:

Formati disponibili

Delphin Manual

2003-2014 Delphin Technology AG

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

2003-2014 Delphin Technology AG

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

2003-2014 Delphin Technology AG

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Delphin Online Hilfe

Module DataService and Configurator

Delphin Online Hilfe

Module DataService and Configurator

Expert Vibro Characteristcs channels: Limits for rotation speed

Delphin Online Hilfe

Delphin Online Hilfe

Module DataService and Configurator

All persistent channels retain their values when reconfiguring

Delphin Online Hilfe

Major overhaul, sampling rate of tracks is rotational speed

Delphin Online Hilfe

Timer channel: Output was stuck high if the response delay

Delphin Online Hilfe

ProfiMessage / LogMessage x000

Delphin Online Hilfe

Module DataService and Configurator

Delphin Online Hilfe

ProfiMessage / LogMessage x000 / Expert Vibro

Wrong formatted timestamps if the device was set to

PWM Channel flags Configuration Error if lower limiter is

Delphin Online Hilfe

reset if trigger was still active

Delphin Online Hilfe

Module DataService and Configurator

Delphin Online Hilfe

ProfiMessage / LogMessage x000

Delphin Online Hilfe

values were received in the trigger time. Now the current

Delphin Online Hilfe

Module DataService and Configurator

Delphin Online Hilfe

Delphin Online Hilfe

Module DataService and Configurator