o Vibration circuit failure (2)
o Temperature circuit failure (4)
o Program ROM memory failure (8)
o External Flash memory failure (16)
o RAM memory failure (32)
o Configuration CRC failure (64)
o Firmware update error (128)
o Watchdog reset (256)
o Network instability (512)
Self-diagnostic errors may also raise a system or critical system alarm in @ptitude
Observer. Note that the network instability error can have significant ramifications for
sensor battery life and urgent action should be taken, refer 4.3.3.
Double clicking a sensor entry or selecting it and then choosing Edit, will launch the
sensor properties dialog where extended status information can be viewed on the
second tab, named Status.
Configuration:
• Not synchronized: the configuration held by @ptitude Monitor/Observer is
different to that in the sensor. This will not be corrected until/unless the user
initiates a synchronise action.
• Staged: a synchronise action has been initiated.
• Pending: Monitor has received the synchronisation request and is due to
send the sensor configuration to the gateway.
• Gateway – Notified: the gateway has received the new configuration.
• Synchronized: the configuration in @ptitude Monitor/Observer and in the
sensor are verified as being the same.
Connection: Current connection status for the sensor, may indicate OK, Temporarily
unreachable or Unreachable.
Hardware ID: The unique identifier for the sensor, if the sensor is commissioned and
has successfully connected via the gateway to @ptitude Observer, it will show a
MAC address in this field.
Sensor Mode: Mesh, Leaf or Relay. Refer description and notes on Sensor Mode
and 2.4.2.
Battery (%): A battery health indication of the estimated percentage battery life
remaining. Note that before a connection to the sensor has been established this
field will be empty.
Firmware Version: The firmware version that is installed in the sensor. Note that
before a connection to the sensor has been established this field will be empty.
To Next Page
Loading...
