View source for Partner Portal/Helpdesk Query Filling Recommendations

==Introduction==
Efficiency is the ability to avoid wasting materials, energy, efforts, money and time in doing something or in producing a desired result. Technical support department desired result is a qualitatively resolved query, which leads to Your satisfaction. 

This guide explains what information helps to answer queries more efficiently and how it accelerates the process of solving any questions you might have. Instead of spending time searching for the details required to solve a query we are able to jump straightly to identification of the issue. 

In the next page you can find a table with needed information in Query and instructions on how to gather that information.

==Main Information==
<br>
<div style="color: #0054A6;"><font size="3"><b>1. Gather information about the issue, what is the device model, configuration, firmware/configurator</b></font></div></font>
* '''Device:''' TMT250/TST100/GH5200/TAT100 etc.;
* '''Configuration:''' Attach configuration file
* '''Firmware version:''' 55.XX.YY.Rev.ZZ / 03.25.05.Rev.XX
* '''Status information:''' responses to relevant SMS/GPRS commands
'''NOTE:''' You may provide IMEI number of 1-3 devices with the issue.

<div style="color: #0054A6;"><font size="3"><b>2. Specify the number of devices and how often the issue repeats</b></font></div>
Repeating: Often/Randomly/Everyday/There is a pattern/Under certain conditions;
<br>
'''NOTE:''' If the Repeating is specified as “Under certain conditions”– describe the conditions.

<div style="color: #0054A6;"><font size="3"><b>3. Provide additional information</b></font></div>
* '''Log files''' - Provide live information when the issue is happening. Log files can be taken via configurator.
* '''Dump files''' - Provide files that the device logged automatically. You have to make sure to take them from FOTA WEB or configurator.

==Needed information in Query==
<br />
{| 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;" |'''How to get it'''
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |'''Why we need it'''
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |'''Example'''
|-
| style="vertical-align: middle; text-align: center;" |'''Device information'''
| style="vertical-align: middle; text-align: center;" |This information has to be gathered from your  platform or your system which monitors devices
| style="vertical-align: middle; text-align: center;" |It will help to understand the scale of the issue  and also find the cause more quickly by finding the connection between  affected devices.
| style="vertical-align: middle; text-align: center;" |Number and model of affected device:<br>2 devices of TFT100
|-
| style="vertical-align: middle; text-align: center;" |'''Firmware version'''
| style="vertical-align: middle; text-align: center;" |[[Command: getver|SMS command]]<br>[[TFT100 Status info|Configurator]]<br>[[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;" |Firmware: 55.00.07.Rev.02
|-
| style="vertical-align: middle; text-align: center;" |'''Configuration'''
| style="vertical-align: middle; text-align: center;" |Configuration can be downloaded directly from device through [[Devices|FOTA WEB]] or [[TFT100 Status info|Configurator]]
| style="vertical-align: middle; text-align: center;" |The configuration used on the device allows us to  analyze if the issue is not caused by improperly configured settings or  features.
| style="vertical-align: middle; text-align: center;" |Attach the device configuration to Query.
|-
| style="vertical-align: middle; text-align: center;" |'''How to repeat the issue'''
| style="vertical-align: middle; text-align: center;" |Monitor the devices on the server and provide  information, under which conditions issue occurs.
| style="vertical-align: middle; text-align: center;" |It will help the engineer better understand the  conditions and how to repeat it personally, which will lead to a faster  solution.
| style="vertical-align: middle; text-align: center;" |Device goes into Deep Sleep, when device wakes up  from Accelerometer, event (Movement AVL I/O ID 240) is not sent to server.
|-
| style="vertical-align: middle; text-align: center;" |<b>Log files</b>
| style="vertical-align: middle; text-align: center;" |It can be taken via Configurator's [[TFT100 Status info#Maintenance|Maintenance tab]] or via [[How_to_capture_log_and_dump_files#Log_capturing_using_terminal | Terminal]]
| style="vertical-align: middle; text-align: center;" |The logs allow  the engineers to provide you with initial insights into your issue with first  response.
| style="vertical-align: middle; text-align: center;" |Attach the taken Log file to Query.
|-
| style="vertical-align: middle; text-align: center;" |<b>Dump files</b>
| style="vertical-align: middle; text-align: center;" |You have to make sure to take them from [[TFT100 Status info#Maintenance|Configurator Maintenance tab]] or FOTA WEB after issue happened. '''Please take them  not more than 2 or 3 hours after the issue otherwise device overwrites those  files.'''
| style="vertical-align: middle; text-align: center;" |The dump files  allow the engineers to provide you with initial insights into your issue with  first response.
| style="vertical-align: middle; text-align: center;" |Attach the taken Dump files from FOTA WEB or  Configurator to Query.
|-
| style="vertical-align: middle; text-align: center;" |<b>Status information</b>
| style="vertical-align: middle; text-align: center;" |SMS/GPRS commands such as [[Command: getinfo|getinfo]], [[Command: getver|getver]], [[Command: getstatus|getstatus]] can be used to provide valuable information
| style="vertical-align: middle; text-align: center;" |Depending on the issue, Status information will allow us to analyze the issue more quickly and possibly provide a solution immediately.
| style="vertical-align: middle; text-align: center;" |SMS responses to [[Command: getver|getver]] from device:
Ver:55.00.07_02 GPS:AXN_5.10_3333<br>Hw:TMT250 Mod:2 IMEI:359632106584425<br>Init:2020-6-2 13:50 Uptime:3798<br>MAC:001E42B7C137 SPC:1(0) AXL:10<br>BL:1.7<br>BT:4
|}

'''If you cannot gather information from one of above steps, it can be skipped, however, please inform the engineer in the Query.<br />'''

==How to get LOG/DUMP files?==
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.

#<b>Open configurator debug window:</b> Open the configurator with the device connected to PC. Go to Status section -> Maintenance window.
#<b>Take log files that are already stored in the device:</b> 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.
#*<b>Note 2.1:</b> If the device is installed in a vehicle and deployed in the field you can use FOTA WEB to download these files remotely.
#<b>Make LOG file during/replicating the issue:</b> 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.
#* <b>Note 3.1:</b> For example, you should send SMS during the logging period if you claim that your device is not receiving SMS.
#* <b>Note 3.2:</b> For troubleshooting remote vehicles download DUMP files via FOTA and download them as soon as possible after replicating the issue.
#<b>Find DUMP/LOG files:</b> After the logging is done "Open directory" button in the configurator to find your DUMP, LOG, and CFG files.
#<b>Taking configuration file separately:</b> If you have not made a DUMP or log file in previous steps, export your configuration file by using the "Save to file" button.
#* <b>Note 5.1:</b> In the GIF file is saved to the Documents folder for quick access by pressing the "Open directory" button in the configurator. You may choose a different save location. 
<br>

[[File:How_to_get_log_dump_cfg_files.gif|center]]

[[Category: Frequently Asked Questions - FAQ]]