AIR³ XCT Addon manual (3)

With Safe Landing Reporting, you can configure a task that launches a pop-up upon landing and requires you to confirm that you have landed safely.

If configured correctly, a task with the Safe Landing Reporting option will work as follows:

• Upon landing, a window and a notification will automatically open with the message: ‘Did you land safe? Click here”.
• If the pilot does not click on the window or the notification before the ‘Play reminder after’ timeout, the reminder sound will play according to the sound settings (volume, count).
• If the pilot clicks on the window or on the notification before the “DO NOT SEND” timeout ends, the Telegram message will not be sent to the selected Telegram group and/or the SMS message will not be sent to the selected contact(s).

To configure a Safe Landing Reporting, click on Safe Landing Reporting button in the Settings & Tasks setup.

First of all, click on Safe Landing Reporting Confirmation Process button to determine the process. By default, a message is sent after 60 seconds and a sound will be played as a reminder after 30 seconds. You can change these values, as well as the sound to play for the reminder.

Then, enable either Telegram Message & Position Sending and/or SMS Fallback.

To use the Telegram feature, you need to have installed and configured Telegram correctly. You will also need to have previously configured a ‘Telegram Message & Position’ task. To find out how to configure such a task,  click here.

Once you have enabled the ‘Telegram Message & Position Sending’ feature, the relevant button will become available. Click on it and select the previously configured Telegram task.

You can also decide to enable SMS and decide if the SMS is sent in parallel of the Telegram message or only if the sending of the Telegram message fails.

Once you have enabled the tickbox, click on the orange button “SMS Fallback Configuration”.

Make sure to have granted permission for SMS.

Then type the phone number to send the SMS to (or select a contact). Once typed or selected, click on the + sign to add the contact. You can add multiple phone numbers. Click on Test SMS to send a test message and make sure the SMS sending is working.

To tick the box “Only send SMS if Telegram fails, you need to have configured Telegram and a Telegram task. Otherwise, the box is not tickable.
Once, done, click on confirm.

Then select the message that you want to send through the SMS.

Once done, click on Confirm.

A Safe Landing Reporting task is created together with an automation rule that links the Landing XCTrack event to this newly created task.

As you can imagine, this security feature will only work if the device is correctly configured and has internet or mobile access when attempting to send the message.

Test it using the play button and/or by simulating a flight with XCTrack.

When using this feature, you can specify a server to which your tracklog will be sent automatically upon landing.

Click the ‘Export Tracklog’ button in the ‘Settings & Tasks’ setup.
First, select the XCTrack tracklogs folder. Click Select Folder. In the selection window, click on the three lines on the left to open the menu. Click on XCTrack, then Tracklogs and finally click on ‘Use this folder’. You will then be asked to allow the AIR³ XCT Addon to access your files. Click Allow.

Click on the + sign to set up a server configuration.

Select the server to which you want to send your tracklog.

Enter your username/email and password.
Depending on the selected server, you may also need to enter your glider and its type.

Depending on the server you select, you may also have the opportunity to test your credentials and ensure that you haven’t made a mistake.

The system will wait 15 seconds after landing by default before sending the tracklog to the server, but this can be changed in the Upload delay after landing field.

Once you have set up the details and clicked on ‘Add configuration’, a new task and an automation rule triggered by XCTrack landing are created.

You can manually upload a tracklog to the configured server by clicking on the arrow next to the bin icon. Click on the arrow and locate the tracklog you want to upload, then click on it.

This manual upload will not check for the latest tracklog created, nor if the date of the tracklog corresponds to the date of export.

To delete the server configuration, simply click on the trash icon.

Return to the main screen and click the ‘Export tracklog’ button to view the automation rules relating to the configured server(s). Click the play button to start the export process.

When triggered by the play button in the automation rule row, the exported tracklog is the latest one in the configured folder.

If the export is triggered by an XCTrack event, such as ‘Landing’, the export process will also check that the tracklog’s date corresponds to the export’s date.

If you have set up a safe landing reporting task, the system will wait until the end of the process before sending the tracklog.

Once you have started the tracklog process, a window will appear, giving you the option to stop the process. If you do not click on this window before the time runs out, the tracklog will be sent (provided that the configuration is correct and that you have an internet connection).

Depending on the server response, you may receive an indication about the failure if a problem occurs during upload.

Once you have set your tasks, you can manage them under ‘Configured tasks’.
To edit a task, click on it.