C
ONFIGURATION
C
OMMAND
S
ET
- F
IRMWARE
R
EVISION
2.4.0_
BETA
-
V
ERSION
1.0.0
3.2.25 AL<index>
parameter (Alarm configuration)
Features of the alarm configuration
✔
Clearly arranged functional structured alarm conditions.
✔
Events can be combined to define very complex conditions.
✔
Several actions can be specified and will be executed when all conditions are
true.
✔
Alias names, which are defined for PFAL commands like IN/Output names, Timer,
Trigger or Counter names, can be used for conditions as well. This improves
clearly arranged easy to understand system configurations.
✔
Can be extended very flexible and easily.
Limitations
✔
Currently it is not possible to transmit various system states by using alarms (i.e.
sending
TCP
state periodically via SMS).
✔
It is not possible to evaluate the execution of alarm actions (whether they are
successfully executed or resulting errors). No conditions can be defined to react
on failed alarm actions before. (The only way is using i.e. state conditions, which
should be changed if the action was successfully executed).
✔
PFAL responses cannot be transmitted or displayed for executed alarm
commands.
✔
None of read commands cannot be efficiently used as alarm actions.
•
The purpose of read commands (i.e. all commands which retrieve a state or
other information) is to provide information on demand.
•
This information is returned only within the PFAL response, which is not
available for alarm commands
To sent information automatically use
“MSG.Send”
commands, see
, page
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 206 of 271
