EVENTS


A rule is analyzed when the associated trigger event occurs.

The name of trigger event is the same used for the folder name.



I1...I6 DIGITAL INPUTS

When a status change occurs in an active digital input.

If the input remains stable during all the activation time required, will be analyzed all the rules stored in the folder: R:I1...I6

I7 MAIN POWER SUPPLY

If the channel is active, the presence of the main power is verified periodically and the event is detected if the status is different from the previous one for the entire activation time set, examining all the rules that may be stored in the folder: R:I7

I8 AUX POWER SUPPLY

If the channel is active and the main power supply is not detected, the auxiliary power supply (RJ45) is periodically verified. The event detected if the status is different from the previous one for the entire activation time, examining all the rules that may be stored in the folder: R:I8

P1...P6 PULSE COUNTER INPUTS

The digital inputs having pulse counter function enabled are sampled every 20ms: each change of status from open (0) to closed (1) produces a pulse, the counter advances by 1 each time the number of pulses required for feedrate is reached.The counter will restart from zero when the maximum number of counts is reached (0 ... 999999) and can be set to any value with a specific command.

At the end of the measurement period set for each input, will be analyzed all the rules stored in the folder: R:P1...P6

A1...A4 ANALOG INPUTS

For each analogue input, the average, minimum and maximum values during the last measurement period are available.

At the end of the measurement period set for each input, will be analyzed all the rules stored in the folder: R:A1...A4

A5 BATTERY

The battery charge level is available as a mean, minimum and maximum value measured during the last minute, at the end of which will be analyzed all the rules stored in the folder: R:A5

A6 TEMPERATURE

The temperature detected by the embedded sensor during the last measurement period is available as the average, minimum and maximum values.

At the end of the set measurement period, will be analyzed all the rules stored in the folder: R:A6

O1...O4 RELAY OUTPUTS

At any time the output changes status following a command, will be analyzed all the rules stored in the folder: R:O1...O6

M1...MF MEMORY BIT

At any time the memory bit status is modified, will be analyzed all the rules stored in the folder: R:M1...MF

V1...VF MEMORY VARIABLE

The value of the variables is calculated once a minute by processing the content of the expression. If the value obtained is different from the previous one, will be analyzed all the rules stored in the folder: R:V1...VF

PON POWER ON

Every time the device is switched on, will be analyzed all the rules stored in the folder: R:PON

RES RESET

At every device reset (excluding power-on), will be analyzed all the rules stored in the folder: R:RES

SSI SSID NETWORK

With WiFi enabled, at every log in, log out or change of the Service Set IDentifier (SSID), will be analyzed all the rules stored in the folder: R:SSI

NET CELLULAR NETWORK

With PLMN installed and enabled, at any disconnection or cell change will be analyzed all the rules stored in the folder: R:NET

CAE INCOMING CALL FROM ENABLED USER

At each incoming phone call from an active user will be analyzed all the rules stored in the folder: R:CAE

The phone number (N20), the group to which the user belongs  (N22) will eventually be evaluated as a condition within the rule.

CAD INCOMING CALL FROM DISABLED USER

At each incoming telephone call from an inactive user (out of validity period or without a ticket) will be analyzed all the rules stored in the folder: R:CAD

The phone number (N20), the group to which the user belongs  (N22) will eventually be evaluated as a condition within the rule.

CAU INCOMING CALL FROM UNKNOWN

At each incoming telephone call from unknown will be analyzed all the rules stored in the folder: R:CAU

The phone number (N20) will eventually be evaluated as a condition within the rule.

CAO ANSWER TO CURRENT ORIGINATED CALL

When the recipient answers to a device originated call will be analyzed all the rules stored in the folder: R:CAO

The phone number (N26) of the originated phone call will eventually be evaluated as a condition within the rule.

DTM DTMF CODE RECEIVED

During a voice phone call if a DTMF code is detected (the sequence code is accepted after * key is pressed) will be analyzed all the rules stored in the folder: R:DTM

The possible DTMF code detected (N21) will eventuallt be evaluated as a condition within the rule.

SME INCOMING SMS FROM ENABLED USER

At each SMS received from an active user will be analyzed all the rules stored in the folder: R:SME

The content of the message (N24), the sender (N23) and the group to which belongs (N25) will eventually be evaluated as a condition within the rule.

SMD INCOMING SMS FROM DISABLED USER

At each SMS received from an inactive user (out of validity period or without a ticket) will be analyzed all the rules stored in the folder: R:SMD

The content of the message (N24), the sender (N23) and the group to which belongs (N25) will eventually be evaluated as a condition within the rule.

SMU INCOMING SMS FROM UNKNOWN

At each SMS received from unknown will be analyzed all the rules stored in the folder: R:SMU

The content of the message (N24) and the sender (N23) will eventually be evaluated as a condition within the rule.

APE INCOMING APP MESSAGE FROM ENABLED USER

At each message received from the SMM broker coming from an APP recognized as an active user, will be analyzed all the rules stored in the folder: R:APE

The content of the message (S10) and the sender (S09)  will eventually be evaluated as a condition within the rule.

APD INCOMING APP MESSAGE FROM DISABLED USER

At each message received from the SMM broker coming from an APP recognized as an inactive user (out of validity period or without a ticket) will be analyzed all the rules stored in the folder: R:APD

The content of the message (S10) and the sender (S09) will eventually be evaluated as a condition within the rule.

APU INCOMING APP MESSAGE FROM UNKNOWN

At each message received from the SMM broker coming from an unknown APP, will be analyzed all the rules stored in the folder: R:APU

The content of the message (S10) and the sender (S09) will eventually be evaluated as a condition within the rule.

DWE INCOMING WAN DEVICE MESSAGE FROM USER

At each message received by the SMM broker and coming from another device recognized as a user, will be analyzed all the rules stored in the folder: R:DWE

The content of the message (S07), the sender (S05)  and the group to which belongs (S06) will eventually be evaluated as a condition within the rule.

DWD INCOMING WAN DEVICE MESSAGE FROM DISABLED USER

At each message received from the SMM broker coming from another device recognized as an inactive user (out of validity period or without a ticket) will be analyzed all the rules stored in the folder: R:DWD

The content of the message (S07), the sender (S05) and the group to which belongs (S06) will eventually be evaluated as a condition within the rule..

DWU INCOMING LAN DEVICE MESSAGE FROM UNKNOWN

At each message received from the SMM broker coming from another unknown device, will be analyzed all the rules stored in the folder: R:DWU

The content of the message (S07) and the sender (S05) will eventually be evaluated as a condition within the rule.

DLN NEW LAN DEVICE DETECTED

Every 20 seconds the local network is scanned (if enabled), when a new device is detected will be analyzed all the rules stored in R:DLN 

The identifier of the connected devices (up to 6) are shown in the tags Y01 ... Y06. The content (Y09), the sender of the message (Y07) and the group to which belongs (Y08) will eventually be evaluated as a condition within the rule.

DLE INCOMING LAN DEVICE MESSAGE FROM USER

At each message received from another device belonging to the local network recognized as a user will be analyzed all the rules stored in the folder: R:DLE

The content of the message (Y09), the sender (Y07) and the group to which belongs (Y08) will eventually be evaluated as a condition within the rule.

DLD INCOMING LAN DEVICE MESSAGE FROM DISABLED USER

At each message received from another device belonging to the local network recognized as a an inactive user (out of validity period or without a ticket), will be analyzed all the rules stored in the folder: R:DLD

The content (Y09), the sender (Y07) of the message and the group to which belongs (Y08) will eventually be evaluated as a condition within the rule.

DLU INCOMING LAN DEVICE MESSAGE FROM UNKNOWN

At each message received from another unknown device belonging to the local network, will be analyzed all the rules stored in the folder: R:DLU

The content (Y09) and the sender of the message (Y07) will eventually be evaluated as a condition within the rule.

EME INCOMING EMAIL FROM ENABLED USER

At each email message routed by the SMM broker from an active user will be analyzed all the rules stored in the folder: R:EME

The subject of the message (S08), the sender address (S07) and the group to which belongs (S09) will eventually be evaluated as a condition within the rule.

EMD INCOMING EMAIL FROM DISABLED USER

At each email message routed by the SMM broker from an inactive user (out of validity period or without a ticket) will be analyzed all the rules stored in the folder: R:EMD

The subject of the message (S08), the sender address (S07) and the group to which belongs (S09) will eventually be evaluated as a condition within the rule.

EMU INCOMING EMAIL FROM UNKNOWN

At each email message routed by the SMM broker from an active user will be analyzed all the rules stored in the folder: R:EMU

The subject of the message (S08), and the sender address (S07) will eventually be evaluated as a condition within the rule.

CHE INCOMING CHAT MESSAGE FROM ENABLED USER

At each Telegram chat message routed by the SMM broker from an active user will be analyzed all the rules stored in the folder: R:CHE

The content of the message (S16), the sender (S14) and the group to which belongs (S15) will eventually be evaluated as a condition within the rule.

CHD INCOMING CHAT MESSAGE FROM DISABLED USER

At each Telegram chat message routed by the SMM broker from an inactive user (out of validity period or without a ticket) will be analyzed all the rules stored in the folder: R:CHD

The content of the message (S16), the sender (S14) and the group to which belongs (S15) will eventually be evaluated as a condition within the rule.

CHU INCOMING CHAT MESSAGE FROM UNKNOWN

At each Telegram chat message routed by the SMM broker from unknown will be analyzed all the rules stored in the folder: R:CHU

The content of the message (S16) and the sender (S14) will eventually be evaluated as a condition within the rule.

API INCOMING API MESSAGE

Commands received from the SMM broker are examined and eventually executed. Anything that is not a recognized command triggers the verification of the rules that may be present in the folder: R:API

The content of the message (S13) will eventually be evaluated as a condition within the rule.

KWE INCOMING WIEGAND CODE FROM ENABLED USER

At each Wiegand code received from an active user, will be analyzed all the rules stored in the folder: R:KWE

The code received (K01), the group to which belongs (S15) and up to 5 previous codes received (K02...K06) will eventually be evaluated as a condition within the rule.

KWD INCOMING WIEGAND CODE FROM DISABLED USER

At each Wiegand code received from an inactive user (out of validity period or without a ticket) will be analyzed all the rules stored in the folder: R:KWD

The code received (K01), the group to which belongs (S15) and up to 5 previous codes received (K02...K06) will eventually be evaluated as a condition within the rule.

KWU INCOMING WIEGAND CODE FROM DISABLED USER

At each unknown Wiegand code received will be analyzed all the rules stored in the folder: R:KWU

The code received (K01) and up to 5 previous codes received (K02...K06) will eventually be evaluated as a condition within the rule.

COM INCOMING STRING FROM CLOSED CONSOLE

At each incoming ASCII string (terminated by Carriage Return) received from local COM port will be analyzed all the rules stored in: R:COM

This feature is suspended after console login and restored after logout.

An open console accepts commands only.

IR INFRARED CODE

At each infrared command is received (if receiver is enabled) will be analyzed all the rules stored in the folder: R:IR

The received code (F01) will be evaluated within the rule.

BLB BLE DETECTED

When BLE operates in OBSERVER mode, at any time a registered device (UID stored as user) enters or exits (1 minute timeout) the radio range (with a signal above the minimum detection threshold). will be analyzed all the rules stored in the folder: R:BLB

The identification of 4 detected devices is reported in tags B07...B10.

BLM BLE MESSAGE

When BLE operates in ADVERTISER mode, the device exposes the set UID (Eddystone beacon, Avior proprietary UID if not set). It can accept connections from APP that send commands and messages: the received commands are examined and eventually executed. Anything that is not a recognized command triggers the verification of any rules present in the folder: R:BLM

Identifier of connected devices are reported in the tags B07...B10.

SUN AT SUNRISE

At sunrise time at the installation site. (D17) will be analyzed all the rules stored in the folder: R:SUN

Sunrise time updated every Sunday at 3:05 with automatic clock and data connection available.

SUT AT SUNSET

At sunset time at the installation site. (D18) will be analyzed all the rules stored in the folder: R:SUT

Sunset time updated every Sunday at 3:05 with automatic clock and data connection available.

SCH SCHEDULED OPERATION

Once per minute the unit searches for a matching rule in the folder: R:SCH

The due time is the trailing part of the file name, after the progressive number.

MOD MODBUS TCP

If a client connects or it is disconnected to MODBUS TCP server, will be analyzed all the rules stored in folder R:MOD