Configuration

Once the installation is finished, open 1x PDI Builder and select the unit.

1x autopilot ID

If it is correctly connected, it should appear in Normal mode as shown in the following figure.

1x PDI Builder

1x unit can also appears as: Maintenance mode, Maintenance mode (loaded with errors) or Normal mode - Disconnected.

Note

Maintenance mode (loaded with errors) appears when something is wrong in the configuration. For more information, see Troubleshooting section of this manual.

The user can access now to 3 configuration options:

• Veronte: It allows the user to work with offline configurations. A previously exported 1x PDI can be opened and modified or it is possible to build a new one from the default configuration.

  Note

  When an offline configuration is opened, it is possible to select the hardware version the user wants to work with:

  

  Hardware versions

• Upload PDI: A previously exported 1x PDI configuration can be imported to the linked 1x.

• Open Veronte: By clicking on this option, 1x PDI Builder configuration menu opens with the configuration (the PDI files) loaded in the 1x. Then, the user can modify it online.

Note

PDI files are 1x configuration files. These files allow for modular control with improved version management. These PDI files are split in 3 folders. Each folder hold several .xml files:

• Operation: This folder holds all the files related with the operations defined, such as waypoints, routes, operative parameters, runaways, etc.

• Setup: This contains the configuration of the vehicle. All the control loops and their parameters, the definition of the flight phases and guidance commands, and the automations defined are stored here.

• xsd: This folder holds .xsd files. An XSD file is a definition file specifying the elements and attributes that can be part of an XML document. This ensures that data is properly interpreted, and errors are caught, resulting in appropriate XML validation. Users should never delete, replace or modify it.

PDIs files

Finally, click on ‘Open Veronte’ to open the configuration and start editing. The different ‘buttons’ that can be seen in the initial menu of the 1x PDI builder are explained below.

Initial menu

1. Save PDI: After changes are done, press on the save button to apply the changes.

   While saving, a percentage of the progress of the saving process is displayed:

   

   Save PDI

   After saving any changes, Veronte Autopilot 1x will RESET and the 1x PDI Builder software will close.

   Danger

   As Veronte Autopilot 1x is reset, it is not advisable to save changes during flight tests.

   Note

   This button will only appear if an autopilot 1x is connected, i.e. when working offline this button will not be available.

2. Export PDI: After modifying a configuration, press the export button to store the configuration in the local storage. Users can store this configuration in an empty folder or in the folder where the previously imported configuration is stored. With the latter option, the “original” configuration will be overwritten by the one with the new changes. The user can choose between:

   • Download PDI: With this option the 3 folders with the PDI files are downloaded.

   • Download VER file: Download a .ver file with the configuration in binary. This option is only available ‘online’, otherwise it will be disabled.

Download option

3. Import PDI from repo: The user can import a configuration file from the repo and modify it. After that, if the save button is pressed, this configuration will be uploaded on the 1x.

4. Import PDI from local storage: The user can import a configuration file from the local storage and modify it. After that, if the save button is pressed, this configuration will be loaded into the 1x.

5. Feedback: Users can report a problem they have encountered by creating an issue in their own ‘Joint Collaboration Framework’. The ‘Download’ button downloads a zipped folder with the current 1x configuration and more information needed for Embention to resolve the issue. It is advisable to attach this folder when creating the issue.

   Note

   The user’s ‘Joint Collaboration Framework’ is simply a own Github repository for each customer.

   If the user has any questions about this Joint Collaboration Framework, please see Joint Collaboration Framework user manual.

   

   Feedback

6. These are the different functions of 1x autopilot. Each option will be explained in detail in the next sections.

Icon	Item	Description
	Veronte	Introduce 1x autopilot information
	Connections	Configure I/O connections on 1x autopilot
	Sensors	Configure parameter sensors
	Input/Output	Configure external sensors/devices and I/O signals
	Control	Introduce Phases, Envelopes, Modes and Arcade axis configuration
	Automations	Configure automatic actions on event detection (go home, change phase…)
	Communications	Configure alternative communication channels, statistics and routing
	Stick	Cusomize transmitter configuration
	Block Programs	Customize algorithms executed by 1x autopilot
	Devices	Configure any connected devices: servo, radio, camera…
	Telemetry	Customize traffic: log, telemetry…
	UI	Customize variable names
	HIL	Configure parameters for XPlane Simulator
	Safety	Customize checklist, block user control in PDI configuration and safety bits