Rules Complete Examples - Revision history

Tbezstarosta at 14:06, 26 May 2026

2026-05-26T14:06:54Z

2026-05-05T11:23:23Z

‎CR17 - Digital Inputs - Connection of NETIO T1 Sensor FW 5.0.3+

2024-07-29T07:18:33Z

‎Temperature out of limit - Output1 ON

2024-07-15T13:41:24Z

‎CR17 - Digital Inputs - Connection of NETIO T1 Sensor FW 5.0.3+

2024-07-15T13:34:18Z

2024-07-08T07:52:27Z

‎External Switch ON - All outputs ON with individual Power Up Sequence

2024-07-08T07:45:12Z

2023-11-29T21:35:07Z

‎3. Create RULE for output ON

2023-11-29T21:34:56Z

‎4. Create RULE for output OFF

2023-11-29T21:34:33Z

‎4. Create RULE for output OFF

@@ Line 604: / Line 604: @@
 NETIO T1 Sensor connected into INPUT n.2
-Rule name: '''CR17_TEMP'''
+PAB name: '''CR17_TEMP'''
   <nowiki>
@@ Line 637: / Line 637: @@
    "actions":{
      "OUTPUTS/1/ACTION":0
+   }
+}
 </nowiki>

@@ Line 598: / Line 598: @@
 == CR17 - Digital Inputs - Connection of NETIO T1 Sensor  <sup><code>FW 5.0.3+</code></sup>==
-Rule is used for managing outputs status in response to temperature metering connected into Digital Inputs (DI). Typical example of this solution is the temperature metering in server room. In case temperature hits specified temperature, the air-condition (AC) will turn ON.
+Rule is used for managing outputs status in response to temperature metering connected into Digital Inputs (DI). Typical example of this solution is the temperature metering [℃] in server room. In case temperature hits specified temperature, the air-condition (AC) will turn ON.
 === Temperature measurement - condition definition temperature range (15-45)℃ ===

@@ Line 615: / Line 615: @@
 </nowiki>
-===  Temperature out of limit  - Output1 ON ===
+===  Temperature out of spec  - Output1 ON===
-Rule name: '''CR17_RULE'''
+Rule name: '''CR17_RULE_1'''
   <nowiki>
+{
@@ Line 624: / Line 624: @@
    "actions":{
      "OUTPUTS/1/ACTION":1
+   }
+}
 </nowiki>

@@ Line 598: / Line 598: @@
 == CR17 - Digital Inputs - Connection of NETIO T1 Sensor  <sup><code>FW 5.0.3+</code></sup>==
-Rule is used for managing outputs status in response to temperature metering connected into Digital Inputs (DI). Typical example of this solution is the temperature metering of server room. In case temperature hit specify temperature, the air-condition (AC) will turn on. As temperature come back to define temperature range, the air-condition (AC) turn off.
+Rule is used for managing outputs status in response to temperature metering connected into Digital Inputs (DI). Typical example of this solution is the temperature metering in server room. In case temperature hits specified temperature, the air-condition (AC) will turn ON.
 === Temperature measurement - condition definition temperature range (15-45)℃ ===

← Older revision		Revision as of 13:34, 15 July 2024
Line 595:		Line 595:
	}		}

		+	</nowiki>
		+
		+	== CR17 - Digital Inputs - Connection of NETIO T1 Sensor <sup><code>FW 5.0.3+</code></sup>==
		+	Rule is used for managing outputs status in response to temperature metering connected into Digital Inputs (DI). Typical example of this solution is the temperature metering of server room. In case temperature hit specify temperature, the air-condition (AC) will turn on. As temperature come back to define temperature range, the air-condition (AC) turn off.
		+
		+	=== Temperature measurement - condition definition temperature range (15-45)℃ ===
		+	NETIO T1 Sensor connected into INPUT n.2
		+
		+	Rule name: '''CR17_TEMP'''
		+
		+	<nowiki>
		+	{
		+	"source":"INPUTS/2/TEMP",
		+	"type":"RANGE",
		+	"upperBound":45,
		+	"lowerBound":15,
		+	"timeHysteresis":1
		+	}
		+	</nowiki>
		+
		+	=== Temperature out of limit - Output1 ON ===
		+	Rule name: '''CR17_RULE'''
		+	<nowiki>
		+	{
		+	"conditions":{
		+	"PAB/CR15_TEMP/IN":false
		+	},
		+	"actions":{
		+	"OUTPUTS/1/ACTION":1
		+	}
		+	}
	</nowiki>		</nowiki>

@@ Line 569: / Line 569: @@
 </nowiki>
-=== External Switch ON  - All outputs ON with individual Power Up Sequence ===
+=== External Switch ON - All outputs ON with individual Power Up Sequence ===
 Rule name: '''CR16_RULE'''

@@ Line 497: / Line 497: @@
 In this rule is definition when the output 1 should be enabled (ON). It is combination of two conditions of PAB and scheduler.
-'''This code is saying:''' When is night ( day is false = <code>"PAB/daylight/DAY": false,</code>) and in paralel schedule is not active (set to be off = <code>"SCHEDULE/christmas_off/ACTIVE": false</code>) the result is <code>true</code> and following action (set output 1 to ON <code>"OUTPUTS/1/ACTION": 1</code>)is executed.
+'''This code is saying:''' When is night ( day is false = <code>"PAB/daylight/DAY": false,</code>) and in paralel schedule is not active (set to be off = <code>"SCHEDULE/christmas_off/ACTIVE": false</code>) the result is <code>true</code> and following action (set output 1 to ON <code>"OUTPUTS/1/ACTION": 1</code>) is executed.
 RULE name: '''outON'''

@@ Line 518: / Line 518: @@
 In this rule is definition when the output 1 should be disabled (OFF). It is again combination of two conditions of PAB and scheduler.
-'''This code is saying:''' When it is day now ( day is true = <code>"PAB/daylight/DAY": true,</code>) or the schedule is active (set to be on = <code>"SCHEDULE/christmas_off/ACTIVE": true</code>) the result is <code>true</code> and following action (set output 1 to OFF <code>"OUTPUTS/1/ACTION": 0</code>)is executed.
+'''This code is saying:''' When it is day now ( day is true = <code>"PAB/daylight/DAY": true,</code>) or the schedule is active (set to be on = <code>"SCHEDULE/christmas_off/ACTIVE": true</code>) the result is <code>true</code> and following action (set output 1 to OFF <code>"OUTPUTS/1/ACTION": 0</code>) is executed.
 RULE name: '''outOFF'''