DEVICE - POWER SAVING

Power consumption depends on the operating conditions and the activation of some functions, it is possible to predefine the operating mode with parameter D21.


The following table shows some indicative consumption data measured at 25 ° C with 4V battery voltage.


MODE

DESCRIPTION

POWER

[mW]

NO

Device is fully operational

80...4000

SLEEP1

Wake up occurs when:

• state changes for  din1 / din2 / din3 / din4

• threshold of active analog channels

• communication from cellular network

• wake-up time (D25)

30

HIBERNATE2

Wake up occurs when:

• an active digital input changes state

• wake-up time (D25)

0,8

THE LOW POWER MODE is SUSPENDED

WHEN THE AUXILIARY POWER IS CONNECTED

AFTER 30 MINUTES OF INACTIVITY

THE CONSOLE IS AUTOMATICALLY CLOSED (LOGOUT)

AND LOW POWER MODE IS RESTORED

TO REACTIVATE A DEVICE THAT IS PERMANENTLY ON

LOW CONSUMPTION MODE REMOVE THE POWER SUPPLIES (MAIN AND AUX) TO THEN CONNECT THE MobiLink.USB CABLE:

YOU WILL HAVE 60 seconds to log in to the console,

suspending low power mode


1 Triggers related to input status change are correctly executed (after the activation time). Values that require an acquisition time are available but contain the last value that the device acquired (when it could complete the acquisition).


2 Upon awakening the device is restarted, the values that require an acquisition time will be available only after this time has elapsed. The inputs can wake up the device but the change of state is not recognized. 


Consumption is reset to zero when AviorBox is turned off with the AT#OFF command.


Rules associated with power saving are stored in

specific unit R folders

DATA CONNECTION IN SLEEP MODE

Avior connects to internet (SMM server and MQTT broker) using Transmission Control Protocol (TCP). This protocol ensures that packets are transferred over the internet in a “reliable, ordered, and error-checked” way.

Nevertheless, from time to time, the transfer between communicating parties can get out of sync: in mobile cellular communication, the main reason is related to the carrier operator which unexpectedly closes the connection if there isn't data traffic for a certain period of time (the period varies from operator to operator).

In TCP, this state of incomplete connection is called a half-open connection. The important point to remember is that one side of the communication continues to function and is not notified about the failure of the other side.


In order to overcome such problem Avior allows to specify keepalive parameter for both SMM server (parameter S02) and MQTT broker connection (parameter Q02).


However, during low power consumption mode (in particular SLEEP mode) Avior is not able to send this keepalive to maintain the connection open and operator could close the connection, thus making Avior unreachable from the remote server (i.e. pushed command remains on cloud queue and Avior doesn't download it).


The good news is that as soon as Avior wakes-up from SLEEP mode (for example for "wake-up period" expiration or changes in digital inputs state or reception of SMS), it restores the connection to remote server.


Therefore, if you are planning to use Avior in SLEEP mode with long "sleep time" consider the upper situation and keep in mind that internet connection can be lost.