Changes

no edit summary
Line 1: Line 1: −
'''1.Gather information amount the issue, what is the Device model, Configuration, Firmware/Configurator Versions:'''
+
== '''Introduction''' ==
 +
 
 +
=== This is a guide ment for saving your time. ===
 +
 
 +
=== Read it if you want to know what troubleshooting you should get before registering and issue with our technicians. ===
 +
<blockquote></blockquote>
 +
 
 +
=== '''1.Essiantial information''' ===
 +
 
 +
=== '''What is the Device model, Configuration, Firmware/Configurator Versions:''' ===
 +
''The following will provide us with the minimum information, needed to start solving the issue:''
 +
 
 +
 
 +
''Example''
    
'''Device:''' FMB0X0/FMB1XY/FMB920/FMB640 etc.;
 
'''Device:''' FMB0X0/FMB1XY/FMB920/FMB640 etc.;
Line 5: Line 18:  
'''Configuration:''' Attach configuration file
 
'''Configuration:''' Attach configuration file
   −
'''Firmware version:''' 03.XX.YY.Rev.ZZ
+
'''Firmware version:''' 03.XX.YY.Rev.ZZ,
    
'''Status information:''' responses to relevant SMS/GPRS commands
 
'''Status information:''' responses to relevant SMS/GPRS commands
   −
Provide IMEI and GSM number of 1-3 devices with the issue
+
'''IMEI and GSM numbers:''' See file attached
   −
''This will provide us with essential information, needed to start solving the issue''.  
+
 
 +
When dealing with issues inside the configurator software:
 +
 
 +
'''Configurator version:''' Teltonika.Configurator_1.XX.YY.ZZZZZ
 +
 
 +
=== '''2.Conditional information''' ===
 +
 
 +
=== '''Number of devices, How often the issue repeats:''' ===
 +
''The number of devices and type of the issue will help us to evaluate the priority and understand the situation better.''
      −
'''2.Specify the number of devices and how often the issue repeats:'''
      
'''Repeating:''' Often/Randomly/Everyday/There is a pattern/Under certain conditions;
 
'''Repeating:''' Often/Randomly/Everyday/There is a pattern/Under certain conditions;
If the Repeating is specified as “Under certain conditions”–write on how to repeat those conditions.
     −
''The number of devices and type of the issue will help us to evaluate the priority and understand the situation better.''
+
If the Repeating is specified as “There is a pattern/Under certain conditions” – write on how to repeat the pattern/conditions.
 +
 
 +
 
 +
''Example''
 +
 
 +
'''Number of devices:''' We have received new shipment of 1,000 pcs, and of them behaving strangely.
 +
 
 +
'''Type of issue:''' Repeats under certain conditions - device goes into Deep Sleep, when device wakes up from Accelerometer, event (Movement AVL I/O ID 240) is not sent to server.
    +
=== '''3.Provide additional information:''' ===
 +
''The logs allow the engineers to provide you with initial insights into your issue with the first response.''
   −
'''3.Provide additional information:'''
     −
'''Log files'''- Provide live information when the issue is happening.
+
'''Log files''' - Provide live information when the issue is happening.
    
'''Dump files''' - Provide files that the device logged automatically.
 
'''Dump files''' - Provide files that the device logged automatically.
Line 30: Line 57:  
'''Attach relevant server data''' (RAW data in Hex preferred), you should also specify the exact time when the issue in data can be seen (For example: 2020.02.24 10:00 AM GMT +0 until 2020.02.24 13:00 PM GMT +0).
 
'''Attach relevant server data''' (RAW data in Hex preferred), you should also specify the exact time when the issue in data can be seen (For example: 2020.02.24 10:00 AM GMT +0 until 2020.02.24 13:00 PM GMT +0).
   −
'''Specify what has been done to try and fix the issue''': e.g. static navigation was disabled via setparam command to see if the device filters out the positions.
+
'''Specify what has been done to try and fix the issue''':
 +
 
 +
 
 +
''Example''
 +
 
 +
Please find logs and server data attached. We have tried to disable static navigation via setparam command to see if the device filters out the positions due to incorrect ignition, we will investigate if it helped.  
   −
''The logs allow the engineers to provide you with initial insights into your issue with the first response.''
        −
How to get Debug Information
     −
Configuration Configuration can be downloaded directly from device through FOTA WEB, FOTA or Configurator).
+
== How to get Debug Information ==
 +
Configuration Configuration can be downloaded directly from device through FOTA WEB, FOTA or Configurator).
   −
Status information SMS/GPRS commands such as  
+
Status information SMS/GPRS commands such as ''getinfo getver getstatus getgps'' can be used to provide valuable information.
getinfo getver getstatus getgps can be used to provide valuable information.
     −
How to repeat conditions For example: Device goes into Deep Sleep, when device wakes up from Accelerometer, event (Movement AVL I/O ID 240) is not sent to server.
+
How to repeat conditions For example: Device goes into Deep Sleep, when device wakes up from Accelerometer, event (Movement AVL I/O ID 240) is not sent to server.
   −
Log files They can be taken via the Configurator Maintenance tab or via Terminal.
+
Log files They can be taken via the Configurator Maintenance tab or via Terminal.
   −
Dump files You have to make sure to take them from Configurator Maintenance tab or FOTA WEB after issue happened. And take them not more than 2 or 3 hours after the issue or device will log over them.  
+
Dump files You have to make sure to take them from Configurator Maintenance tab or FOTA WEB after issue happened. And take them not more than 2 or 3 hours after the issue or device will log over them.  
     

Navigation menu