User's Manual
Table Of Contents
- 1 Product description
- 2 Integration with SKF @ptitude Observer
- 3 Installation and commissioning
- 4 Maintenance functions
- 5 Product specifications
- 6 Electrical waste
- Appendix A Limited Warranty
MAINTENANCE FUNCTIONS
Troubleshooting
62 (92)
SKF Enlight Collect IMx-1 System
User Manual
Revision C
The log will be created in the application folder for the monitor service and will be
named <MonitorName>IMx1SensorMeshInformation.log, i.e. prefixed by the actual
name of the monitor service. It is a human readable CSV format file that provides
information on sensor mesh, parent-child relationships and performance statistics
such as packet loss and transfer time:
• Log time
• Timestamp from sensor
• Sensor hardware ID
• The last 8-bytes of the sensor address
• The last 8-bytes of the sensor parent address
• Parent link metric
• Packets sent
• Packets lost
• Packets round trip minimum
• Packet round trip maximum
• Packets round trip average
• Network instability flag
• Watchdog reset flag
• Sensor self-diagnostic (see also Status, 2.3.2, for decoding information)
• Gateway Hardware ID
• The last 8-bytes of the gateway address
Such information can be invaluable when troubleshooting issues with the
performance or behaviour of the sensor mesh.
4.3.3 IMx-1 sensor troubleshooting
Possible causes for a ‘non-responsive’ sensor include:
• Sensor is in ‘flight mode’.
• Incorrect or incomplete configuration.
• Mechanical damage.
• Sensor fault including discharged battery.
• Loss of mesh communications – likely multiple sensors affected.
In working on IMx-1 systems the interaction between the various radio systems that
the sensor incorporates should be considered. Be aware that, as described below,
various timeouts apply to the sensor radios to avoid unnecessary battery drain.