47 | 50
Installation Manual LOGS50 EN_MI_090221
3.2.1. GUARD TIME FOR UNITARY EVENTS
Some of pre-determined events have a time of guard that prevents from the event to be re-triggered
continuously because of a fluctuation in its value.
Apertura
10 seconds
Connector
10 seconds
Low battery
1 day
HD overflow
1 hour
HA overflow
1 hour
Configuration update
2 minutes
Firmware upgrade
0 seconds
incidence event
0 seconds
3.2.2. INCIDENCES
Notifications of incidences are codified as follows:
0
: Overflow of data history
1
: Overflow of alarms history.
2
: One month of battery left
3
: Desynchronization of LOGS50.
The associated task to this action is predetermined in the configuration. The
user will have to enter the telephone number were incidents have to be notified.
The notification format will be similar to the sending of a variable, but the value
will be replaced by a text string composed dynamically to inform the user of the
ongoing incidences.
The cause of the sending a variable through SMS notifying a variable
“INCIDENCE” will be the step of any codified event indicated as active. It will
not be notified when it comes back to it is normal value 0.
When an incidence it is not produced it will appear a
‘.’
.
Example:
The value of a variable incidence will be the value of a binary add of each of the
bytes that are in
‘1’,
so if LOGS50 are desynchronized it will have a 4
th
bit of the
variable in 1 and the message received in the mobile will be:
“…..3…..”
while
the variable incidence will be
8
(1000b).
