AN62 supported devices
- NETIO PowerBOX 4Kx
- NETIO PowerCable REST 101x
- NETIO PowerDIN 4PZ
- NETIO PowerPDU 8QS
- NETIO PowerPDU 4KS (TBA)
Note: Firmware version 3.2.0 or higher is required
NETIO Conditions & Actions
NETIO devices use a system of "Condition" & "Action" which have to be configured separately. To configure a Load WatchDog functionality you have to configure 2 tabs:
- PAB (Power Analysis Block) - real-time analysis of load [W] on output
- Rules - what to do if defined state happens
Detailed description and examples on the NETIO Wiki - Local device scripting
and in our glossary: Conditions & Actions
PAB (Condition)
The PAB functionality is used to analyze power consumption (load) of specified output. If load drops to a defined range, NETIO device detects this condition and can react to it with defined action(s).
More on PAB in our glossary: WatchDog - Power consumption (PAB)
The Rule (Action)
The Rule functionality generally define NETIO device's reaction to specific situation / event (condition).
Based on the conditions the NETIO device can process these actions:
-
ACTION on defined OUTPUT
- 0 = TURN OFF
- 1 = TURN ON
- 2 = SHORT OFF
- 3 = SHORT ON
-
4 = TOGGLE - Changes the status from ON to OFF and vice versa
- Send alarm to NETIO Cloud service (icloud service can inform account user by email for example)
Load Watchdog (Restart device if it's more than 5 minutes in IDLE mode)
a) PAB configuration
{ "type": "RANGE", "source": "OUTPUTS/1/LOAD", "lowerBound": 1, "upperBound": 20, "timeHysteresis": 120 }
Variables description:
Variable | Value | Description |
---|---|---|
type |
RANGE |
PAB type |
source |
OUTPUTS/x/(LOAD/CURRENT/POWER) |
The monitored variable. x indicates input / output number. |
timeHysteresis |
int |
[s] Monitored value must be present in defined interval for amount of time defined here. |
lowerBound |
int |
lower bound of the monitored value |
upperBound |
int |
upper bound of the monitored value |
Web administration window, PAB section:
b) Rule configuration
{ "conditions": { "PAB/NR04_PAB/IN": true } "actions": { "OUTPUTS/1/ACTION": 2, "CLOUD/OUTPUT/1/ALARM": "${COND_RESULT}" } }
3. Enable Rule and Save Changes
Variables description:
Variable | Value | Description |
---|---|---|
conditions |
Eg: `"PAB/PAB1_1/IN": true` |
Conditions definition. Relationship between conditions is defined by |
operator |
AND/OR |
Optional. Specifies relationship between conditions. |
filters |
Eg: |
Filter definition. For multiple filter conditions, the relationship between them is always |
actions |
Eg: |
Actions definition. All actions defined here will be triggered when conditions (and filters) are met |
Web administration window, Rules section:
c) Event activation
1. Check the device log. It should NOT contain any logs regarding PAB or Rules.
2. Make the monitored device go into IDLE mode (Wait or turn manually, specific for device).
3. Wait Output 1 should restart (switch OFF & ON) after 2 minutes. In the device log you will see entries similar to image below.
4. In case the device have NOT produced expected results, see the device log for hints.
Note: Names of configuration examples used in this Application Note (NR03_WDT for PAB configuration and NR03_RULE for Rule configuration) are based on
NRxx NETIO Rules - examples in NETIO Wiki.