How to capture log and dump files

From Wiki Knowledge Base | Teltonika Mobility
Revision as of 12:57, 13 December 2021 by Veronika (talk | contribs)

(diff) ← Older revision | Approved revision (diff) | Latest revision (diff) | Newer revision → (diff)

Solution applies for these devices

TMT250 | GH5200 | TAT100 | TST100 | TFT100

Log capturing using Teltonika Configurator

To retrieve logs from device, connect it via USB to PC and open Teltonika Configurator software.

  • 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.

Follow these quick steps to get all the necessary debug information in just over 10 minutes.

  1. Open configurator debug window: Open the configurator with the device connected to PC. Go to Status section -> Maintenance window.
  2. Take log files that are already stored in the device: 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 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. Make LOG file during/replicating the issue: 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 1: For example, you should send SMS during the logging period if you claim that your device is not receiving SMS.
    • Note 2: For troubleshooting remote vehicles download DUMP files via FOTA and download them as soon as possible after replicating the issue.
  4. Find DUMP/LOG files: After the logging is done "Open directory" button in the configurator to find your DUMP, LOG, and CFG files.
  5. Taking configuration file separately: If you have not made a DUMP or log file in previous steps, export your configuration file by using the "Save to file" button.
    • Note 1: 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.


How to get log dump cfg files.gif

Log capturing using terminal

Devicemanager COM1.png

Our devices (TMT250, GH5200, TAT100, TST100, TFT100) are able to transmit their current state when they are connected to PC using USB cable.

Log file is used to detect errors and provide information when device is operating unexpectedly.

Required Terminal application for log capturing can be downloaded here: Terminal

After connecting device to PC, it creates two ports:


  • USB Debug Port - used for modem trace.
  • USB Modem Port - used for terminal log.




If connected device is not recognized by PC, please install appropriate drivers.
Download Teltonika COM port driver from the link: COM Port Driver

NOTE:
BaseCOM.png





  • Additionally, you can find your port when opening configurator.
  • Do not forget to leave configurator in first page as shown in the example, because while device configuration page is open, you will not be able to start your logging process.

Follow these steps to start log:

  • select COM port;
  • select the baud rate;
  • handshaking parameters;
  • click connect and "Start Log" button.

If log is not running, please send .log:1 command (see picture below). Now you are able to monitor all internal processes happening in the device. All logged process is saved in the txt file.
Note: Send command .log:0 to stop logging.

Terminal log.png

The most commonly used commands

  • .info - displays general device information, including how long the product has been running, etc.
  • factory:get_status:1 - displays the signal strength of the GSM antenna.
  • .shrec - sends an empty record to the server for the purpose of verifying that the record transfer is working
  • @sms_run:setparam <arg1>:<arg2> - Configure the device by sending a command to the terminal. Values arg1 = parameter ID, arg2 = parameter value. Parameter list can be reached depending on the device:
  • @sms_run:<command> - Configure the device by sending a command to the terminal. Use the selected commands to extract the required information from the product. SMS/GPRS Commands can be reached depending on the device: