Retrieve data for support - Elios 3

When encountering unexpected behaviour, sharing the right data is important for fast and efficient solutions. This article can help identify what info is needed and how to share it.

All files sent must be zipped before upload.

Any data shared to the support are stored on strictly confidential folders and only used for support investigation purpose.

What data is needed for my issue?

It is important to share the right kind of information for the issue being reported. Depending where and when the error occurs there are different logs and files to share.

When the drone is armed and/or reviewing flights in Inspector

Inspector flight folder.
avdebug.LOG file.
Cockpit recording.

When the drone is disarmed/no flight

Idle files.

When there is issue with Cockpit app

Cockpit recording with STN files.
Cockpit logs.

Import a flight folder with debug file from Elios 3 with Inspector 5

Connect the Elios 3 to Inspector, then go to the Import tab.
Identify and select the flight/s concerned by the issue.
Select the checkbox to Import debug files.
Click Import.

After importing, and/or if the flight has previously been imported:

Open inspector, then go to the Export tab.
Create and select a destination folder.
Identify and select the flight/s concerned by the issue.
Select the checkbox to export debug files.
Click Export.
Zip the folder.

How to retrieve a avdebug.LOG if not selected during import

If the debug log checkbox was not selected during import, it is possible to retrieve this file with Windows File Explorer. The flight avdebug.LOG files are obtainable and stored on the AV SD card on the Elios 3.

How to identify the avdebug.LOG that correlates with the flight:

Navigate to the relevant flight in Inspector 5:

Click on the relevant flight. Click anywhere, but do not click Open.
Notate the Identifier numerals following the serial number.

Retrieve the file:

Connect the Elios 3 to the computer and power it on.
Identify and share the avdebug.LOG that concerns the flight/s at issue.

The AV SD card stores the last 40 files. An avdebug.LOG file will be created each time the Elios 3 is powered on.

Extract Inspector project folder with debug file Inspector 4

Connect the aircraft to Inspector, then go to the Import tab.

Identify and select the flight concerned by the issue

Select the option Import debug files

Choose the location of the project folder then click Import

Retrieving Tablet data

When retrieving data from the tablet it is necessary to have the Transferring files option selected in the Developer options settings.

Read more about the connection of the tablet to a computer here:

Extract Cockpit video recording with STN files

All the video recordings with their corresponding STN file are stored in this location:

In some case, the support team might ask a copy of the hidden STN files, they are stored in the following location:

All the Cockpit logs are stored in this location: Files > Internal Storage > Flyability > Cockpit > Logs.

Extract Idle files

Idle files are created and begin logging once the Elios 3 has been powered on. The Idle files are stored on the Elios 3 and can be found via the Debug files on the Import screen.

Connect the Elios 3 to Inspector, then go to the Import tab.
Click to expand the Debug files. Identify and select the flight/s concerned by the issue.
- Hover over files for more information to assist in locating the correct files.
Select the checkbox/es for the needed files.
Click Import. Files are saved in a flight folder in the Workspace.
- Navigate to the Workspace flight folder and sort by Date modified. The files can be verified by opening and seeing idle in the file naming.

Extract Idle files Inspector 4

Idle file can be shown in the Import tab when the option is selected, they can be downloaded directly from this tab by clicking on the download logo on the right side.

If the issue occurred after the flight, the corresponding idle file will be the one above the flight (e.g. for the flight 393-1 the idle file will be 394-1)

In case the issue occurred before the flight, the corresponding idle file will be the one below (e.g. for the flight 393-1 the idle file will be 393-undefined)

How to zip files

Select the folder/ flights that you want to zip

Right-click then select Send to, and then select Compressed (zipped) folder

Send the data to support

When a ticket is created, you will received an automatic reply including a link for sending data related to this ticket.

Data can be also shared via the platform of your choice but make sure the link allow the access to the support team.

Last updated 10 days ago

Was this helpful?

Retrieve data for support - Elios 3

When encountering unexpected behaviour, sharing the right data is important for fast and efficient solutions. This article can help identify what info is needed and how to share it.

All files sent must be zipped before upload.

Any data shared to the support are stored on strictly confidential folders and only used for support investigation purpose.

What data is needed for my issue?

It is important to share the right kind of information for the issue being reported. Depending where and when the error occurs there are different logs and files to share.

When the drone is armed and/or reviewing flights in Inspector

Inspector flight folder.
avdebug.LOG file.
Cockpit recording.

When the drone is disarmed/no flight

Idle files.

When there is issue with Cockpit app

Cockpit recording with STN files.
Cockpit logs.

Import a flight folder with debug file from Elios 3 with Inspector 5

Connect the Elios 3 to Inspector, then go to the Import tab.
Identify and select the flight/s concerned by the issue.
Select the checkbox to Import debug files.
Click Import.

After importing, and/or if the flight has previously been imported:

Open inspector, then go to the Export tab.
Create and select a destination folder.
Identify and select the flight/s concerned by the issue.
Select the checkbox to export debug files.
Click Export.
Zip the folder.

How to retrieve a avdebug.LOG if not selected during import

How to identify the avdebug.LOG that correlates with the flight:

Navigate to the relevant flight in Inspector 5:

Click on the relevant flight. Click anywhere, but do not click Open.
Notate the Identifier numerals following the serial number.

Retrieve the file:

Connect the Elios 3 to the computer and power it on.
Identify and share the avdebug.LOG that concerns the flight/s at issue.

The AV SD card stores the last 40 files. An avdebug.LOG file will be created each time the Elios 3 is powered on.

Extract Inspector project folder with debug file Inspector 4

Connect the aircraft to Inspector, then go to the Import tab.

Identify and select the flight concerned by the issue

Select the option Import debug files

Choose the location of the project folder then click Import

Retrieving Tablet data

When retrieving data from the tablet it is necessary to have the Transferring files option selected in the Developer options settings.

Connect the tablet to the computer and access the tablets internal storage using Windows explorer.

Read more about the connection of the tablet to a computer here:

Elios 3 How to connect the tablet on a computer

Extract Cockpit video recording with STN files

All the video recordings with their corresponding STN file are stored in this location:

In some case, the support team might ask a copy of the hidden STN files, they are stored in the following location:

All the Cockpit logs are stored in this location: Files > Internal Storage > Flyability > Cockpit > Logs.

Extract Idle files

Idle files are created and begin logging once the Elios 3 has been powered on. The Idle files are stored on the Elios 3 and can be found via the Debug files on the Import screen.

Connect the Elios 3 to Inspector, then go to the Import tab.
Click to expand the Debug files. Identify and select the flight/s concerned by the issue.
- Hover over files for more information to assist in locating the correct files.
Select the checkbox/es for the needed files.
Click Import. Files are saved in a flight folder in the Workspace.
- Navigate to the Workspace flight folder and sort by Date modified. The files can be verified by opening and seeing idle in the file naming.

Extract Idle files Inspector 4

Idle file can be shown in the Import tab when the option is selected, they can be downloaded directly from this tab by clicking on the download logo on the right side.

If the issue occurred after the flight, the corresponding idle file will be the one above the flight (e.g. for the flight 393-1 the idle file will be 394-1)

In case the issue occurred before the flight, the corresponding idle file will be the one below (e.g. for the flight 393-1 the idle file will be 393-undefined)