Difference between revisions of "Terminal"
From Wiki Knowledge Base | Teltonika GPS
| (10 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
The Telematics Configuration Tool (TCT) introduces an easier way to '''debug''' '''FTx platform''' devices – '''Terminal tool'''. This new feature allows you to monitor their connected device actions and find possible issues related to the device’s functionality without using third-party tools. | The Telematics Configuration Tool (TCT) introduces an easier way to '''debug''' '''FTx platform''' devices – '''Terminal tool'''. This new feature allows you to monitor their connected device actions and find possible issues related to the device’s functionality without using third-party tools. | ||
| − | === Launching Terminal tool | + | === Launching Terminal tool and connecting FTx device === |
| − | + | ||
# To launch Terminal tool. At the top of the TCT window, click on “Settings” button and click then “Terminal”. | # To launch Terminal tool. At the top of the TCT window, click on “Settings” button and click then “Terminal”. | ||
# Terminal tool can be launched in TCT start-up window or after connecting to the FTx platform device. | # Terminal tool can be launched in TCT start-up window or after connecting to the FTx platform device. | ||
# To connect FTx platform device. Make sure that the device is connected to your computer and in Terminal tool press the “+” button on the left side of Terminal tool UI for a new connection, select the device from the dropdown list, and select the “Debug” port. | # To connect FTx platform device. Make sure that the device is connected to your computer and in Terminal tool press the “+” button on the left side of Terminal tool UI for a new connection, select the device from the dropdown list, and select the “Debug” port. | ||
| − | |||
<pre style="color: red">Note: Only one connection is available at the same time.</pre> | <pre style="color: red">Note: Only one connection is available at the same time.</pre> | ||
| − | + | # If everything is done correctly, you should see debug messages coming from the connected device. | |
| − | + | ||
| − | + | === Saving debug log into a file === | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | ===Saving debug log into a file=== | ||
| − | |||
Terminal tool holds about 500-1000 lines of debug messages in TCT UI, so if you want to gather more messages, we suggest saving debug messages into a file. | Terminal tool holds about 500-1000 lines of debug messages in TCT UI, so if you want to gather more messages, we suggest saving debug messages into a file. | ||
| − | #When the debug messages are coming from the connected device, press “Save” icon on the right side of Terminal tool UI. | + | |
| − | #Set a log file name and location where it should be saved. | + | # When the debug messages are coming from the connected device, press “Save” icon on the right side of Terminal tool UI. |
| + | # Set a log file name and location where it should be saved. | ||
# Debug messages will be saved into a file until the device is disconnected. For example, disconnecting the device using “Close” button next to the device connection. | # Debug messages will be saved into a file until the device is disconnected. For example, disconnecting the device using “Close” button next to the device connection. | ||
| − | ===Start/Pause log=== | + | === Start/Pause log === |
| − | |||
When the debug messages are coming from the connected device, you can pause and resume incoming messages whenever you like using “Start/Pause” button on the right side of Terminal tool UI. | When the debug messages are coming from the connected device, you can pause and resume incoming messages whenever you like using “Start/Pause” button on the right side of Terminal tool UI. | ||
<pre style="color: red">Note: If you are saving the debug log into a file, “Start/Pause” button doesn’t stop the log gathering in the file.</pre> | <pre style="color: red">Note: If you are saving the debug log into a file, “Start/Pause” button doesn’t stop the log gathering in the file.</pre> | ||
| − | ===Resizing Terminal tool=== | + | === Resizing Terminal tool === |
For your convenience, Terminal tool can be resized using a button in the middle of Terminal tool window. | For your convenience, Terminal tool can be resized using a button in the middle of Terminal tool window. | ||
| − | ===Minimizing Terminal tool=== | + | === Minimizing Terminal tool === |
If Terminal tool takes too much of your screen real estate, at any given time you can minimize it using “Minimize” button on the right side of Terminal tool UI. Minimizing Terminal tool doesn’t stop debug messages logging. | If Terminal tool takes too much of your screen real estate, at any given time you can minimize it using “Minimize” button on the right side of Terminal tool UI. Minimizing Terminal tool doesn’t stop debug messages logging. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 16:47, 27 February 2024
The Telematics Configuration Tool (TCT) introduces an easier way to debug FTx platform devices – Terminal tool. This new feature allows you to monitor their connected device actions and find possible issues related to the device’s functionality without using third-party tools.
Launching Terminal tool and connecting FTx device
- To launch Terminal tool. At the top of the TCT window, click on “Settings” button and click then “Terminal”.
- Terminal tool can be launched in TCT start-up window or after connecting to the FTx platform device.
- To connect FTx platform device. Make sure that the device is connected to your computer and in Terminal tool press the “+” button on the left side of Terminal tool UI for a new connection, select the device from the dropdown list, and select the “Debug” port.
Note: Only one connection is available at the same time.
- If everything is done correctly, you should see debug messages coming from the connected device.
Saving debug log into a file
Terminal tool holds about 500-1000 lines of debug messages in TCT UI, so if you want to gather more messages, we suggest saving debug messages into a file.
- When the debug messages are coming from the connected device, press “Save” icon on the right side of Terminal tool UI.
- Set a log file name and location where it should be saved.
- Debug messages will be saved into a file until the device is disconnected. For example, disconnecting the device using “Close” button next to the device connection.
Start/Pause log
When the debug messages are coming from the connected device, you can pause and resume incoming messages whenever you like using “Start/Pause” button on the right side of Terminal tool UI.
Note: If you are saving the debug log into a file, “Start/Pause” button doesn’t stop the log gathering in the file.
Resizing Terminal tool
For your convenience, Terminal tool can be resized using a button in the middle of Terminal tool window.
Minimizing Terminal tool
If Terminal tool takes too much of your screen real estate, at any given time you can minimize it using “Minimize” button on the right side of Terminal tool UI. Minimizing Terminal tool doesn’t stop debug messages logging.
