![Satec PM295 Скачать руководство пользователя страница 106](http://html1.mh-extra.com/html/satec/pm295/pm295_installation-and-operation-manual_1200390106.webp)
98
Operation Techniques
Here, two problems arise: The first is that a setpoint may not provide more than four
actions at once, and we need at least five to record data in five different data log
partitions. The second is that the trigger event is a pulse that will be cleared
immediately after we check it, and we need a trigger to operate a setpoint for more
long time.
The decision is to use a programmable event flag, for both goals.
Example 4-11
demonstrates the usage of the programmable event. The event flag #5 is used for this
purpose. It should be explicitly cleared before usage.
Four setpoints provide all operations. The first setpoint checks the pulse input to
hold a starting pulse when it comes, in the event flag, if the event has not yet
occurred. Two setpoints, #2 and #3, are triggered by the event flag and provide
continuous recording data using interval timer #1. Setpoint #4 disables recording
when the second pulse comes.
Example 4-11 Sample Of Binding The Setpoints
Setpoint #1
Trigger conditions
Conjunction
Trigger parameter
Condi-
tion
Operate
limit
Release
limit
Condition #1
OR
Pulse input #2
ON
Condition #2
AND
Event flag #5
OFF
Setpoint actions
Delays
Action type
Action target
Unit
Operate Release
Action #1
Set event flag
#5
0.1 s
0
0
Setpoint #2
Trigger conditions
Conjunction
Trigger parameter
Condi-
tion
Operate
limit
Release
limit
Condition #1
OR
Event flag #5
ON
Condition #2
AND
Timer #1
ON
Setpoint actions
Delays
Action type
Action target
Unit
Operate Release
Action #1
Data logging
#1
0.1 s
0
0
Action #2
Data logging
#2
Action #3
Data logging
#3
Action #4
Data logging
#4