[DKSF 54.1 IU] Page LOGIC web interface

A logic module is designed with the aim of a simple automation and can perform such tasks like maintaining a microclimate, managing an automated turning on/off a backup equipment, etc. Logic works on a basis of the rules, programmed by a user through a web interface.

This page describes a module operation algorithm and possibilities of its configuration.

List of Rules

Rules allow to set a flexible logic scheme of managing IO lines and relays of a device depending on variable external conditions.

Let us list the following principles of operation and configuration of Logic:

• The less is a line number, the higher is a rule priority;
• If two rules form a conflicting output command (turn on and turn off an output simultaneously), a rule with a higher priority will work;
• If rules do not conflict (they manage different outputs or form conflict free commands), then a correlation of their priorities is regardless;
• Rules of «While» type always have a higher priority than rules of «If» type, regardless their mutual arrangement in the list;
• A priority of a rule (its position in the list) can be changed using buttons “Move up” and “Move down”, located in the end of a line;
• A rule can be deactivated by unchecking a checkbox. Inactive rules are displayed in grey;
• Control buttons “Stop”/”Start” work right after you have clicked them. There is no need to click the button «Apply changes». Buttons manage starting and stopping of rules operation. This status is kept when a device is turned off. If operation of Logic was stopped by clicking the button “Stop”, a warning line appears “stopped (inactive)”;
• «Reset» button sets outputs that are used in rules into the initial status «Switched off». There is a need to take into account that when the rules are not stopped before clicking the button «Reset», a status of outputs can be immediately changed and a command will have no external effect;
• The button “Apply changes” saves the changes, added to the rules.

Each position of a rule line is described below.

Type of a rule (position 1 in a rule line). - Possible values: «While», «If».

«While» rules react on an input status immediately and run constantly. «If» rules react on changing an input status (the second position in a rule line).

«While» rule is designed to program conditions under which an output is constantly kept in a specified status, until a condition works. When a condition is not fulfilled, an output status can be changed by other rules.

«If» rule is designed to program a short-term reaction to a specified event, such as changing a logic level of an IO line or losing a response when a Pinger works.

Until an input of a rule remains unchanged, a rule «If» does not influence status of its output even if a condition of a rule is fulfilled. «While» rules always have a higher priority than «If» rules. For example, when one of «While» rules keeps an output in a status switched off, rules of «If» type that include an output on a specified event, will not work.

Input (position 2 in a rule line) - An input is a source of information for a rule operation. Possible values – RESET, TSTAT1, TSTAT2, PINGER1, PINGER2, AC PWR.

When configuring a logic input, there is a need to take into account the following peculiarities:

• One of the Thermostats (TSTAT1 or TSTAT2) must be previously set in a window for configuring thermostats; 
• One of the Pingers (PINGER1 or PINGER2) must be previously configured. 

Depending on the type of a chosen input, a set of conditions for a specific rule varies.

Condition (position 3 in a rule line) - is a condition within which a rule is applied and a command that changes an output status is issued. This value is changed depending on a type of a selected Input and represents a sense of an input status. Possible values for a Pinger are – “Silent”, “Responds”. For an IO line possible values are “log.1”, “log.0”. For a Thermostat possible values are “Below a specified T”, ”Above a specified Т”. ”. A rule of "If" type works only in the moment of fulfilling a condition. A rule of "While" type works all the time when a condition is fulfilled.

Command (position 4 in a rule line) - is a command, performed when a rule works (a condition is fulfilled). For an "If" rule possible values are – «Switch on», «Switch off». These commands work in the precise moment of fulfilling a condition. For a "While" rule possible values are «Keep Switched On», «Keep Switched Off». These commands work all the time when a condition is fulfilled.

Output (position 5 in a rule line) - is an output, which is managed by a rule. Possible values are – RELAY1, RELAY2, RELAY3, RELAY4, SNMP1, SNMP2 .

When configuring a logic output, there is a need to take into account the following peculiarities:

• A used relay (RELAY1-4) should be connected to a logic module by choosing an operation mode Logic on the page “RELAY MANAGEMENT”; 
• Used Setters must be programmed

Thermo (Hydro) stat

Thermostat is used to maintain specific temperature. Besides a programmed thermostat, there is a need to set two rules minimum: one rule for switching on a heater or a cooler and another one for switching it off. It is possible to configure no more than two thermostat channels – TSTAT1, TSTAT2. A corresponding thermostat is chosen as a data source (input) in rules that manage a heater or a cooler. 

Configuration parameters and a thermostat status are described below.

Sensor N – is a number of a temperature sensor, with which a thermostat works. It is possible to plug up to 8 temperature sensors with an individual number from 1 to 8 to a device. On default: 1

A current temperature, degrees С or % relative humidity – Current readings of a temperature sensor or a humidity sensor.

Threshold, deg. С or % rel.hum. - is a temperature that will be maintained by a thermostat (whole degrees of Celsius, a value can be negative) On default: 20.

Hysteresis - Hysteresis sets a "corridor" close to a specified temperature, within its limits a thermostat does not react to temperature fluctuations. This function allows to avoid occasional frequent switching of a heater (cooler) caused by natural spontaneous fluctuations measured by a temperature sensor. If a current thermostat status is «temperature above a safe range», then a threshold for switching its status is a specified temperature minus a hysteresis value. And vice versa, if a current status is "temperature below a safe range", then a threshold is a specified temperature plus a hysteresis value. As soon as falling or rising temperature reaches the value of a threshold (taking into account a hysteresis) and thereby leaves the limits of a "corridor", a thermostat status is changed to an opposite one. On default: 2

Status – is a thermostat status. Its possible variants are: Sensor Failure, Above Specified Т, Below Specified Т.

After setting the values, there is a need to click the button «Apply changes».

Pinger

Pinger checks availability of a specified address through a network. A result of a test (a pinger status) can be selected as an «input» of a rule.It is possible to configure no more than two pingers – PINGER1, PINGER2. A typical use of a pinger is an automatic turning on of a backup equipment power supply if a connection line fails.

Parameters of a configuration and a pinger status are described below.

Requested address – is an address of a device, which is being checked for its availability. It is allowed to indicate IP address as well as a domain name. An empty page disables polling. On default: address is not specified 

Polling period, s (5-900) - is a period of repeating ping tests in seconds. A value is chosen depending on a necessary speed of discovering a failure and on the other hand a limit of a service traffic in a network. Also there is a need to take into account that too frequent power supply switching can decrease a wearout time of equipment. If there is no response, a ping is repeated after timeout is over, not when the next polling period starts. On default: 15

One ping timeout, ms (100-10000) - is time for ping to wait for a response. Timeout is chosen depending on a speed of a local network operation as well as a frequency of repeating pings that are not responded. If there is no response to ping after a specified timeout is over, ping sending is immediately repeated. If there is still no response after 5 repeated sending, a pinger status is changed to «does not respond», and repeats are stopped until the next polling period starts.On default: 1000

Status  – possible values «Responds», «Silent». If requesting is not completed, a status can be undefined. In this case the rules depending on a pinger status, do not form any commands, and their outputs are managed by other rules or keep a previous status. Pinger status is updated automatically nearly 4 times a minute.

After setting the values, there is a need to click the button «Apply changes».

SNMP SETTER

SNMP setter sends snmp set requests to an SNMP object. It is possible to configure no more than two setters - SNMP1, SNMP2

Configuration parameters and a status of a pinger are described below.

Memo (up to 30 characters) - is a field for an extra information. On default: empty.

Address - is an address of an SNMP object.  On default: address is not specified.

Icon

Port- port SNMP.  On default: 161

OID (.1.3.6...) - SNMP object identificators. On default: .1.3.6.1.4.1.25728.5800.3.1.3.1

Community - administrating groups' settings for SNMP.  On default: empty.

"On" value (type Integer32) - a value, which is transmitted to an SNMP object as an "On" signal.  On default: 1

"Off" value (type Integer32) - a value, which is transmitted to an SNMP object as an "Off" signal.  On default: 0

Test it - testing transmitting the signals

Status - is a status of an SNMP object. It can be "available", "timeout" or "waiting for a response"

After setting up the values there is a need to click the button «Apply changes».