Troubleshooting

In case of any software error, it is possible to extract and analyze files from session folder.

Warning

Do not modify or delete manually any Veronte Link file. Copy them to a different path to send or analyze.

Veronte Link files are placed on the following paths:

  • C:\Users\USER NAME\AppData\Roaming\VeronteLink\configurables Device configurations.

  • C:\Users\USER NAME\AppData\Roaming\VeronteLink\sessions Session files, it includes flights information.

  • C:\Users\USER NAME\AppData\Roaming\VeronteLink\tracelogs Event logs, it includes flights information.

  • C:\Users\USER NAME\AppData\Roaming\VeronteLink \(\Rightarrow\) cfg.son Veronte Link connections configuration file. If deleted, the configuration will be lost.

  • C:\Users\USER NAME\AppData\Roaming\VeronteLink \(\Rightarrow\) vlink.lock Internal file that only appears if any instance of Veronte Link is open. If deleted, there will be instability in the system.

Comm Port error in Windows Device Manager

If the following Windows Comm Port error occurs:

../_images/device_manager_error.png

Windows Device Manager - Comm Port error

Users must extend the disconnection time to 5 seconds to fix it. To do this:

  1. Go to the Connection menu \(\rightarrow\) click on the gear icon to open the COM configuration.

  2. Open the Advanced parameters drop down menu \(\rightarrow\) modify the Disconnect time to 5 seconds.

    ../_images/disconnect_time.png

    Connection configuration - Disconnect time

If the user is still having problems with this, please contact the support team by creating a ticket in the customer’s Joint Collaboration Framework; for more information, see Tickets section of the JCF manual.

Error when replaying a session

If the following error message appears when attempting to replay a session:

../_images/error_replay_session.png

Error message

Important

As indicated in the Sessions section, users cannot replay a session from the currently connected device.

It is often due to users trying to replay a session from a disconnected device that still appears in the Devices list as disconnected. In this case, in order to play a session, it is first necessary to delete it from the this list.

../_images/error_replay_session_devices.png

Device disconnected in Devices list

The cause of this is that when replaying a session, a virtual device is created with the same address as the previous device and this can cause conflicts.

If the user is still having problems with this, please contact the support team by creating a ticket in the customer’s Joint Collaboration Framework; for more information, see Tickets section of the JCF manual.

Viewing UDP data

An application such as Wireshark can be used to visualize raw data sent from Autopilot 1x. Nonetheless, at the beginning, it may show characaters that do not come from 1x, because Wireshark reads all data from the connected port, including protocol information.

To distinguish 1x messages, the user has to search the matcher 0x0A 0xA0 for Veronte UDP Telemetry CLI. The matcher indicates the beginning of the data. In the following example, characters marked with blue correspond to 1x, while yellow characters are the UDP protocol structure.

../_images/wireshark.png

Distinguished data on Wireshark