Why is AIR³ XCT Addon not working?

Here are a few tips to help you identify what was not set up correctly. Before proceeding, please read the AIR³ XCT Add-On instructions carefully.

• Are events being sent correctly from XCTrack to the AIR³ XCT add-on?
  • First, check that XCTrack is correctly sending events to the AIR³ XCT add-on. The simplest way to do this is to:
    • Create a new row in the AIR³ XCT add-on and select ‘Takeoff’ as the XCTrack event.
    • Click on ‘Select Task’ and then select ‘Sound’. Select a sound and click “Confirm”.
    • In the new row, click on the triangle to play the sound.
    • Open XCTrack and go to Menu > Preferences > Testing & Debug > Others. Click on ‘Manual takeoff’. You should immediately hear the sound you have just configured.
  • The simplest way to check whether you can catch a widget click event is to:
    • Open the AIR³ XCT Add-on menu (three dots), then go to Settings > Add a new trigger event > Add a new XCTrack event. Select the ‘Others’ category, then type ‘TEST’ (capital letters) in the ‘Event Name’ field and click ‘Confirm’.
    • Check that you have a ‘TEST (Others)’ event configured in the ‘Added XCTrack Events’ list.
    • Go back to the main AIR³ XCT add-on page, create a new row, select the ‘TEST’ event in the ‘Others’ category, select ‘Task’ and select a sound as you did to test the XCTrack take-off event.
    • Open XCTrack and go to Menu > Customise > Add widget > Intent launcher (in Action buttons). Open it to check that the event is ‘TEST’ (org.xcontest.XCTrack.Event.TEST).
    • Go back to the normal XCTrack interface. Long-press the widget. You should hear the sound. Note that you can deactivate “Long click to activate” in the widget configuration menu if you want to activate with a simple click.
  • To check whether you can catch a button click event, the simplest way is to:
    • Open the AIR³ XCT Add-on menu (three dots), then go to Settings > Add a new trigger event > Add a new XCTrack event. Type ‘KeyEvent’ (this is case sensitive) in the ‘Event Name’ field, then click ‘Confirm’.
    • Check that you have a ‘KeyEvent (Zello)’ event configured in the ‘Added XCTrack Events’ list. Note that creating a new “KeyEvent” event will go to the Zello category, as the main goal is to use a button with Zello. You can use a button for other reasons.
    • Go back to the main AIR³ XCT Add-on page, create a new row, select the ‘KeyEvent’ event in the Zello category, select ‘Task’ and select a sound as you did to test the XCTrack Take-off event.
    • Open XCTrack and go to Menu > Preferences > Key bindings. Click on Launch Android Intent and press the button you want to associate.
    • Go back to the normal XCTrack interface. Click on the button. You should hear the sound. Note that ‘long click’ and ‘short click’ are two different button codes for Android in most cases. If you configure the button to make a long click, You should only make a long click to trigger the event. If you are using a Bluetooth button, make sure you have paired it with the AIR³ correctly before proceeding.

These initial tests will enable you to verify that XCTrack can communicate with the XCT add-on via various methods, such as automatic events, widget events and button events.

• Is Zello correctly configured?
  • First of all, use the Echo to test your audio and make sure Zello is working correctly.
  • Ensure that you have configured the hardware button correctly, as indicated in the AIR³ XCT Add-on instructions (toggle mode).
  • Ensure that you have enabled Zello in the AIR³ XCT Add-on. Open the AIR³ XCT Add-on menu (three dots), then go to Settings > Zello Configuration and enable Zello triggered by the widget.
  • Go back to the main AIR³ XCT Add-on page, create a new row and select the ‘Zello’ event in the ‘Zello’ category. Then click on ‘Select task’ > select ‘Zello PTT’.
  • In the new row, click on the triangle to launch the Zello event and hear it. Click a second time to close the communication, as per the Zello hardware button configuration (toggle mode). You should hear your voice.
  • Using the previous instructions, you have checked that the link between the AIR³ XCT Add-on and XCTrack is working correctly. Create a new widget in XCTrack as indicated above, but enter ‘Zello’ as the event action name. Note that if you use the Expert-Zello profile with AIR³ Manager, this widget will be created automatically.
  • Click on the Zello widget in XCTrack to test Zello.
  • Once you have successfully completed the Echo tests, select the Zello group you want to use and make sure you set this group as the default.
  • If you encounter any issues, please refer to the manual for detailed instructions. For example, make sure that you have correctly defined the battery management on Unrestricted.

These tests should enable you to use Zello directly via XCTrack.

• Is the configuration of Telegram correct?
  • First of all, make sure it is working properly on your AIR³. Test by sending a message and your location to a group.
  • Ensure that you have correctly configured a task to send your position or location, as indicated in the instructions.
  • Create a new row in the AIR³ XCT add-on and select ‘Takeoff’ as the XCTrack event.
  • Click on ‘Select Task’ and select the Telegram task that you have configured.
  • In the new row, click on the triangle to check that the Telegram task has been executed.
  • Open XCTrack > Open Menu > Preferences > Testing & Debug > Others. Click on ‘Manual takeoff’. You should immediately see the Telegram task that you have just configured.