Difference between revisions of "What debug information should be collected?"
(→Steps) |
|||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
=='''<big>Introduction</big>'''== | =='''<big>Introduction</big>'''== | ||
| − | <big> | + | <big>This is a guide meant to understand what information helps engineers answer queries more quickly and hasten the process of solving any questions you might have.</big> |
| + | <big>Query solving can be compared to doing a jigsaw puzzle. The most important thing to complete a jigsaw puzzle is that all of the parts have to be present. Queries work in a similar way, if our technical support engineer receives all the parts of the puzzle – a solution or answer will be provided faster. This way you will save from 2 to 3 days of time when the engineer has to specify the details instead of analyzing it at once</big> | ||
| − | <big> | + | <big>Below you can find a table with information that is needed for a Query and why the information is needed for engineers. In the table there are specifications on how to gather those details from devices.</big> |
| − | |||
| − | |||
| − | |||
=Steps= | =Steps= | ||
'''1. Gather information about the issue, what is the Device model, Configuration, Firmware/Configurator''' | '''1. Gather information about the issue, what is the Device model, Configuration, Firmware/Configurator''' | ||
| Line 37: | Line 35: | ||
Dump files - Provide files that the device logged automatically. You have to make sure to take them from FOTA WEB or Configurator | Dump files - Provide files that the device logged automatically. You have to make sure to take them from FOTA WEB or Configurator | ||
| − | + | '''*If you cannot gather information from one of the steps, they can be skipped however inform the engineer in the query'''<br /> | |
| − | |||
| − | '''*If you cannot gather information from one of the steps, they can be skipped however inform the engineer in the query''' | ||
| − | |||
| − | <br /> | ||
{| class="nd-othertables_2" style="width:100%;" | {| class="nd-othertables_2" style="width:100%;" | ||
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |'''Information''' | ! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |'''Information''' | ||
| Line 55: | Line 49: | ||
| style="vertical-align: middle; text-align: center;" |'''Firmware version''' | | style="vertical-align: middle; text-align: center;" |'''Firmware version''' | ||
| style="vertical-align: middle; text-align: center;" |[[FMB getver|SMS command]] | | style="vertical-align: middle; text-align: center;" |[[FMB getver|SMS command]] | ||
| − | + | ||
| + | | style="vertical-align: middle; text-align: center;" |<nowiki>[FMB920 Status info|Configurator]]</nowiki> | ||
[[Devices|FOTA WEB]] | [[Devices|FOTA WEB]] | ||
| style="vertical-align: middle; text-align: center;" |The firmware version will allow us to analyze if the said issue was not already fixed in a newer firmware version, | | style="vertical-align: middle; text-align: center;" |The firmware version will allow us to analyze if the said issue was not already fixed in a newer firmware version, | ||
| − | + | Firmware: 03.25.15.Rev.05 | |
|- | |- | ||
| style="vertical-align: middle; text-align: center;" |'''Configuration''' | | style="vertical-align: middle; text-align: center;" |'''Configuration''' | ||
| Line 115: | Line 110: | ||
Note 5.1: In the GIF file is save to Documents folder for quick access by pressing the "Open directory" button in the configurator. | Note 5.1: In the GIF file is save to Documents folder for quick access by pressing the "Open directory" button in the configurator. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=='''Quick links'''== | =='''Quick links'''== | ||
| Line 166: | Line 115: | ||
[[FMB_SMS/GPRS_Commands|FMB SMS/GPRS command list]] | [[FMB_SMS/GPRS_Commands|FMB SMS/GPRS command list]] | ||
| + | |||
| + | [[FMB_AVL_ID|FMB parameter list]] | ||
[[Codec|Protocols]] | [[Codec|Protocols]] | ||
| + | |||
| + | |||
| + | |||
Revision as of 13:07, 8 May 2020
Introduction
This is a guide meant to understand what information helps engineers answer queries more quickly and hasten the process of solving any questions you might have.
Query solving can be compared to doing a jigsaw puzzle. The most important thing to complete a jigsaw puzzle is that all of the parts have to be present. Queries work in a similar way, if our technical support engineer receives all the parts of the puzzle – a solution or answer will be provided faster. This way you will save from 2 to 3 days of time when the engineer has to specify the details instead of analyzing it at once
Below you can find a table with information that is needed for a Query and why the information is needed for engineers. In the table there are specifications on how to gather those details from devices.
Steps
1. Gather information about the issue, what is the Device model, Configuration, Firmware/Configurator
Device: FMB0X0/FMB1XY/FMB920/FMB640 etc.;
Configuration: Attach configuration file
Firmware version: 03.XX.YY.Rev.ZZ
Status information: responses to relevant SMS/GPRS commands
Provide IMEI and GSM number of 1-3 devices with the issue
2. Specify the number of devices and how often the issue repeats
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
3. Provide additional information
Log files - Provide live information when the issue is happening. They can be taken via the Configurator.
Dump files - Provide files that the device logged automatically. You have to make sure to take them from FOTA WEB or Configurator
*If you cannot gather information from one of the steps, they can be skipped however inform the engineer in the query
| Information | How to get it | Why we need it | Example |
|---|---|---|---|
| Device information | This information has to be gathered from your platform or your system which monitors devices | It will help to understand the scale of the issue and also find the cause more quickly by finding the connection between affected devices. | Number and model of affected device: 2 devices of FMB001 |
| Firmware version | SMS command | [FMB920 Status info|Configurator]] | The firmware version will allow us to analyze if the said issue was not already fixed in a newer firmware version,
Firmware: 03.25.15.Rev.05 |
| Configuration | Configuration can be downloaded directly from device through FOTA WEB, FOTA or Configurator.
|
The configuration used on the device allows us to analyze if the issue is not caused by improperly configured settings or features. | Attach the device configuration to Query. |
| How to repeat | Monitor the devices on the server and provide information, under which conditions issue occurs. | It will help the engineer better understand the conditions and how to repeat it personally, which will lead to a faster solution. | 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. | The logs allow the engineers to provide you with initial insights into your issue with first response. | Attach the taken Log file to Query. |
| 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 otherwise device overwrites those files. | The dump files allow the engineers to provide you with initial insights into your issue with first response. | Attach the taken Dump files from FOTA WEB or Configurator to Query. |
| Status information | SMS/GPRS commands such as
getinfo getver getstatus getgps can be used to provide valuable information. |
Depending on the issue, Status information will allow us to analyze the issue more quickly and possibly provide a solution immediately. | SMS responses to getver from device:
Ver:02.00.01_06 GPS:AXN_3.80_3333_16070400,0000,, Hw:FMB120 Mod:4 IMEI:352094082042885 Init: 2017-6-16 5:54 Uptime: 16574 MAC:002E43912EF7 SPC:0(0) AXL:0 OBD:0 BL:1.6 BT:4
|
How to get Debug Information
Follow these quick steps to get all the necessary debug information in just over 10 minutes.
If you correctly perform all the steps and describe the issue clearly there is a high chance that we can solve it on our first reply.
1. Open up your device via configurator and go to Status -> Maintenance window
2. Click "Dump" to take the information from the device containing logs from the past that device made automatically. If the issue happened 2-3 hours ago we will see it in these files.
Note 2.1: If the device is installed in a vehicle and deployed in the field you can use FOTA WEB to download these files remotely.
3. If you want to repeat the issue now, you can use logging functionality accessed in the same window. Just start logging by clicking "Log" replicate the issue and when the log ends to attach it to the query. When logs are made they export your current configuration as well.
Note 3.1: For example, you should send SMS during the logging period if you claim that your device is not receiving SMS.
Note 3.2: For troubleshooting remote vehicles download DUMP files via FOTA and download them as soon as possible after replicating the issue.
4.After the logging is done "Open directory" button in the configurator to find your DUMP and LOG+CFG files.
5. If you have not made a log file in step 3, export your configuration file by using the "Save to file" button.
Note 5.1: In the GIF file is save to Documents folder for quick access by pressing the "Open directory" button in the configurator.
Quick links
