User Documentation
Table Of Contents
- Table of contents
- 1 Introduction
- 2 Safety instructions
- 3 System overview
- 4 Operating behavior
- 5 Software installation
- 6 Configuration
- 7 Program development
- 8 Licensing
- 9 Device Administration (DevAdmin)
- 10 Software units
- 11 OPC UA Server
- 12 Node-RED
- 13 LongtermDiagnosticMonitor
- 14 Data recorder
- 15 Diagnostics
- 16 Maintenance
- 17 Technical data
- 18 Directives and standards
- 19 Appendix: Tutorial - creating an IEC project
- 20 Appendix: Addressing in the Ethernet (basics)
- 21 Appendix: Tutorial FoE
- 22 Appendix: Tutorial - call C function from IEC
- Index

Data recorder
System manual
2696790000/02/04.2020
80
Start and stop trigger
Triggers are conditions, which can cause a recording of a profile to be
started or stopped in an event-driven manner. A trigger condition always
refers to a certain variable. This does not have to be registered in the profile,
but rather is specified via its complete path in the variable tree. The same
limits apply for the data type as for registered variables. The following types
of conditions can be specified with these variables:
● Exceeding of a constant threshold value t: The condition occurs when
the variable value t is exceeded, while upon the previous call, this was
not yet the case.
● Falling short of a constant threshold value t: The condition occurs if the
variable value t is fallen short of, while upon the previous call, this was
not yet the case.
● Exceeding or falling short of a constant threshold value t: OR a combina-
tion of both of the above conditions
● Any change of the value of the variable: The condition occurs if the vari-
able value has changed with respect to the last call
Upon the occurrence of the start trigger condition, the recording begins cor-
responding to the configuration (in other words, either endless or until the
end of the buffer is reached). If a stop trigger condition has been configured,
the recording is stopped upon the occurrence of this condition.
A start trigger condition can also be set without an associated stop trigger
condition. The converse is not possible.
Furthermore, there is the option to define a stop time condition (post-start
trigger). This defines a number of recordings. Afterwards, the recording is
stopped automatically.
Example
Total capacity: 32 samples, stop time condition: 25 % (= 8 samples)
1 ... Recording start 2 ... Start trigger
3 ... Recording stop 4 ... Stop time