Scannex ip.buffer, Manual

Page: 43 / 152

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
8.2.8. Alert List
Alert Tag Definition
Auth An authentication failure
Battery The ip.buffer is running on battery power
Comfort ip.buffer is still alive (sent at the interval specified in the alerts setting page)
Config The ip.buffer has been reconfigured 29
Connect1, etc A channel has connected
Disconnect1, etc A channel has disconnected
Full Global memory is full, as set in the alerts setting page (resent every 8 hours).
Full1, etc Channel has reached its full limit (resent every 8 hours)
Log The log area has become full, or the Log has been requested.
LowVolts The ip.buffer has started up running on a PSU that is too low
Mains The ip.buffer is running on mains power
Quiet1, etc Channel has had no data (resent periodically)
Reboot The ip.buffer has booted and started running code
TempHi The ip.buffer temperature is too high
TempLo The ip.buffer temperature is too low 30
User User triggered alert (i.e. clicked “Trigger User Alert!” on web page)
29 The config alert will be sent every 10 minutes while configurations are still in progress. It will
clear after 10 minutes of making no configuration changes.
30 Temperature alerts are only available on the ip.4 product
Page 39
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
8.2.8. Alert List
Alert Tag Definition
Auth An authentication failure
Battery The ip.buffer is running on battery power
Comfort ip.buffer is still alive (sent at the interval specified in the alerts setting page)
Config The ip.buffer has been reconfigured 29
Connect1, etc A channel has connected
Disconnect1, etc A channel has disconnected
Full Global memory is full, as set in the alerts setting page (resent every 8 hours).
Full1, etc Channel has reached its full limit (resent every 8 hours)
Log The log area has become full, or the Log has been requested.
LowVolts The ip.buffer has started up running on a PSU that is too low
Mains The ip.buffer is running on mains power
Quiet1, etc Channel has had no data (resent periodically)
Reboot The ip.buffer has booted and started running code
TempHi The ip.buffer temperature is too high
TempLo The ip.buffer temperature is too low 30
User User triggered alert (i.e. clicked “Trigger User Alert!” on web page)
29 The config alert will be sent every 10 minutes while configurations are still in progress. It will
clear after 10 minutes of making no configuration changes.
30 Temperature alerts are only available on the ip.4 product
Page 39