MAINTENANCE FUNCTIONS
Troubleshooting
SKF Enlight Collect IMx-1 System
User Manual
Revision F
Important note: Sensor power consumption in mesh active mode is of the order of
100x greater than the consumption when the mesh has been successfully joined.
Despite that the mesh radio will be deactivated if after 5-minutes the sensor hasn’t
successfully joined the mesh, there remains the possibility that in conditions of mesh
instability, the sensor may experience frequent but short duration disconnections that
will result in very high drain of the battery because the time-out mechanism is not
being triggered. If this were to be sustained and left uncorrected, battery lifetime
could be reduced to just a few weeks.
To detect this type of condition, the sensor self-monitoring will flag if three
disconnections have occurred within a 24-hour period. System users should
therefore be alert to:
• A system alarm in @ptitude Observer that flags that a sensor is reporting
disconnections and/or frequent resets: ‘Network Instability’. The state of the
network instability flag is also logged in the mesh network information log.
• Unexpectedly rapid loss of indicated, remaining battery life.
When either is apparent the user must take urgent action to stop the battery drain
and correct the sensor mesh issues. If the sensor mesh will take time to evaluate and
correct, to preserve remaining battery life, place the affected sensor in flight mode
until the underlying mesh, network issues can be properly investigated and
addressed.
4.3.4 Gateway troubleshooting
In the first instance, check the gateway status LED indication: for a gateway that is
powered and connected to @ptitude Observer both LEDs should be fixed green light.
If the gateway status LED indicator manifests anything other than fixed green light,
check for loss of system connectivity.
When the status LED indicator is flashing green, it may indicate that the system
connectivity is OK, but the GW has not managed to synchronize its time.
In addition, the app functionality can be utilised for basic gateway and system
troubleshooting, by observing whether the device is responsive in a scan of the area.
Possible causes for a ‘non-responsive’ or non-functioning gateway include:
• Incorrect or incomplete configuration.
• A defective or damaged gateway.
• Local hard wired or Wi-Fi network fault.
• Loss of power or internal fuse/circuit failure.
If the gateway is powered and believed functional but is not connecting to @ptitude
Observer, consult also the
System connectivity section.
To Next Page
Loading...
