FALCOM MAMBOII User Manual page 208

C C
ONFIGURATION OMMAND
used firmware version. In the greater firmware versions the index range can be
increased.
 Please note that alarms with lower index will be first executed, if they are
triggered at the same time upon a certain event.
<conditions>
It determines the list of condition(s) to be controlled. More specifically, it
determines when the MAMBOII should generate an action.
When specifying conditions for alarms (AL), use the logical operators such as "&"
or "?" to apply filtering of conditions. These logical operators enable an alarm to
be executed more precisely when the set conditions are met. It is possible to
specify up to 5 conditions separated either by ampersand "&" or "?" but without
spaces.
•
The ampersand character "&" represents the "AND" conjunction which it is
used to test whether all set events and/or states within the condition field are
evaluated to True,
•
While the question mark character "?" represents the "OR" conjunction, which
it may be used to test whether at least one of the set events and/or states
within the condition field is evaluated to True.
Hint: The conjunctions "&" and "?" could not be mixed/nested within a
condition field. Within a condition field the user is able to use either "&"
or "?".
The syntax to define several conditions is:
What do conditions mean?
Conditions are system events and/or states that rise when either a
command/action is manually or automatically executed during the system
runtime. Conditions are requirements for one or more alarms that will be
executed. As above, up to 5 conditions can be specified to execute up to 5
alarms. So, only when the events and states within this condition field are
evaluated True, then the user specified alarms get executed. Additionally,
the condition field <conditions> consists of one event and up to 4 states.
What are the differences between Events and States?
Events:
States:
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
S - F R
ET IRMWARE
Events are a link between occurrences in the system – e.g.
the device receives an incoming voice call or an input
changes or a lost GPS signal, etc. More specifically, an
event is a pointer that points to a process in a specific
case. All conditions that contain an event are checked
just when the event happens (making it possible to
release actions only one time) - so combining two or more
events within a condition field makes no sense (because
the alarm will never be executed). In chapter , page all
firmware-supported
category. All Events are represented with an "e"
character directly after the last dot-delimiter [.], for
example Sys.Device.eStart or Sys.Timer.e1 etc.
States are conditions, which are checked by system all
the time (every 1 second). Once they are True, the
specified actions will be permanently released, so please
2.4.0_ -
EVISION BETA
are
Events
V
ERSION
grouped by major
Page 208 of 271
1.0.0