AN62 Power Consumption WatchDog - Restart na základě dlouhodobého pokledu spotřeby elektřiny (detekce klidového režimu)

AN62 Application Note describes Power consumption WatchDog function in the NETIO devices and how to configure it. This function is used to detect a power drop of a monitored device and react to it with device restart

Můžeme Vám nějak pomoci?

AN62 supported devices

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)

Rule monitors load (Watts) on Output 1. If the load is between 1-20W for at least 5 minutes, it restarts (ACTION 2 = SHORT OFF) the output. Example uses PAB (Power Analysis Block) functionality to determine if measured value (load in our case) lies in given range for a period of time. When it does, defined Rule triggers device restart.
 

a) PAB configuration

1. Navigate to the device's web administration -> PAB section
If this section is not available, ensure you have the latest Firmware version installed
 
2. Create new PAB definition with name: NR03_PAB (you can skip this and following step if already available by default)
 
3. Insert following configuration code. Edit lower- and upper- bounds to reflect your device IDLE mode load value and timeHysteresis (value in seconds) if necessary 
{
  "type": "RANGE",
  "source": "OUTPUTS/1/LOAD",
  "lowerBound": 1,
  "upperBound": 20,
  "timeHysteresis": 120
}
4. Enable PAB and Save Changes
 

Variables description:

Variable Value Description

type

RANGE

PAB type

source

OUTPUTS/x/(LOAD/CURRENT/POWER)
INPUTS/x/STATE

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.
Eg: If the time hysteresis is equal to 5, monitored value must be within a defined interval for at least 5s. Only then it will be evaluated.

lowerBound

int

lower bound of the monitored value

upperBound

int

upper bound of the monitored value

 

Web administration window, PAB section:

 

b) Rule configuration

1. Create new Rules definition with name: NR03_RULE (you can skip this and following step if already available by default)
 
2. Insert following configuration code:
{
  "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)

operator

AND/OR

Optional. Specifies relationship between conditions. AND = all conditions must apply at the same time. OR = at least one condition must apply. If missing, defaults to OR

filters

Eg: "SCHEDULE/MY_SCHEDULE/ACTIVE": true

Filter definition. For multiple filter conditions, the relationship between them is always AND

actions

Eg: "CLOUD/OUTPUT/1/ALARM": "${COND_RESULT}"

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.

 

Zeptejte se na cenu nebo technické parametry

Pro otestování zařízení použijte jméno/heslo demo/demo