Table of Contents
Advertisement
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
Conjunction
Condition #1
OR
Condition #2
AND
Setpoint actions
Action type
Action #1
Set event flag
Setpoint #2
Conjunction
Condition #1
OR
Condition #2
AND
Setpoint actions
Action type
Action #1
Data logging
Action #2
Data logging
Action #3
Data logging
Action #4
Data logging
98
Trigger conditions
Trigger parameter
Pulse input #2
Event flag #5
Action target
#5
Trigger conditions
Trigger parameter
Event flag #5
Timer #1
Action target
#1
#2
#3
#4
Condi-
Operate
Release
tion
limit
limit
ON
OFF
Delays
Unit
Operate Release
0.1 s
0
0
Condi-
Operate
Release
tion
limit
limit
ON
ON
Delays
Unit
Operate Release
0.1 s
0
0
Operation Techniques
Advertisement
Table of Contents
