10. Troubleshooting

10.1. Essential information

It is strongly advised not to use external hardware devices (such as USB sticks or other removable storage media) to access or store flight plans during flight operations. In addition to the risk of disconnection or hardware failure, data stored on external devices is typically accessed more slowly than data stored locally. This can lead to performance issues or delays during critical mission tasks.

Important

To ensure reliability and optimal performance, the flight plan should always be copied to the local machine on which NAVIGATOR is running before the operation begins.

10.2. Errors

10.2.1. Socket error

Socket error #10053 Software caused connection abort

This error message pops up when an Ethernet hardware connection occurred. This usually is the case when the Ethernet cable from the flight computer (on which TOPOFLIGHT runs) to the RiACQUIRE computer has accidentally been removed or when the cable is damaged.

Important

Take good care of Ethernet cables! They are easily damaged if you stand on them.

10.2.2. SensorHandler blocks

SensorHandler blocks (the airplane is not moving on the map display of TOPOFLIGHT NAVIGATOR)

It may happen that the airplane symbol in NAVIGATOR software suddenly does not keep moving to the correct position.

Unblocking SensorHandler:

1. Open the Task-Manager.

2. Kill SensorHandler (you do not need to stop TOPOFLIGHT NAVIGATOR).

3. Start SensorHandler again.

10.3. Support

Users in need of support are urged to provide the NAVIGATOR log files.

Generating log files:

1. On your flight computer, start SensorHandler.

2. At the bottom of the main window, click Log Files.

3. Click Export Log Files.

4. Select the date of the flight you are referring to in your support request.

5. Click Export log file package.

Send the generated zip file to our .

Hint

The Log files chapter provides a comprehensive overview of all log files, including various export options.