This section explains each option and parameter available in 4x PDI Builder.

Once the installation is finished, connect the Management Board of the 4x (using the Connector 4) with Veronte Link.

Then, open 4x PDI Builder and select the Arbiter to configure.


Arbiter ID

If the Veronte Autopilot 4x is correctly connected, 4x PDI Builder will display the mode in which the connected unit is. In addition, a PDI error button errors will appear:


4x PDI Builder

  • 4x mode: The 4x unit should appear in Normal mode, as shown in the figure above, or Maintenance mode.

    It can also appear as Maintenance mode (loaded with errors) or Normal mode - Disconnected.


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

  • errors PDI Errors button: The user can check if the connected unit has PDI Errors by simply clicking on it. If there are no errors, the following message is displayed:


    4x PDI Builder - PDI Errors message

The user can access now to three configuration options:


4x PDI Builder options

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


    When an offline configuration is opened, it is possible to select the hardware version to work with on the marked button. Versions 1.8 A and 1.8 B are arbiters A and B of version 1.8 respectively.

    It is recommended to select the same hardware version that the user’s Arbiter has, so that if the user wishes to load this configuration later to the Arbiter, there will be no compatibility problems.


    Hardware versions selector

    When switching between hardware versions, the following confirmation message appears:


    Hardware versions selector - Confirmation message

  • Upload PDI: A previously exported 4x PDI configuration can be imported to the linked Arbiter (PDI files are transferred from computer to Arbiter).


    When a configuration is loaded into Arbiter with a version older than the software version being used, an automatic migration from the configuration version to the software version being used will be performed.

    For more information on this, see Migrate configuration - Troubleshooting section of this manual.

  • Open 4x Veronte: It opens the configuration (the PDI files) loaded in the Arbiter (PDI files are transferred from Arbiter to computer). Then, the user can modify it online.


    PDI files are Arbiter configuration files. These PDI files are stored in the setup folder, holding several .xml files which contain all the control system and parameters.


    PDI files

Finally, click on ‘4xVeronte’ to edit a configuration offline or ‘Open 4xVeronte’ to open the current configuration and start editing it online.


The 4x unit must enter Maintenance mode for the user to start editing, so it is necessary to accept the confirmation panel below.


Open 4xVeronte

Once in Maintenance mode, the user can access the Initial menu. The different ‘buttons’ that can be seen in this menu of the 4x PDI Builder are explained below.


Initial menu

  1. Save and close: After changes are done, press here to apply changes.

    While saving, a percentage of saving process is displayed.


    Save and close

    In order to save the configuration in the 4x unit it is necessary to RESET, therefore the 4x PDI Builder software will close. For this reason, the user must accept the following panels:


    Save and close - Confirmation panels


    As the Arbiter is reset, it is not advisable to save changes during flight tests.


    This button will only appear if an Arbiter is connected. When working offline this button will not be available.

  2. Export PDI: After modifying a configuration, press here to save the configuration in the local storage (both folders with the PDI files are downloaded). 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.

  3. Import PDI from repository: The user can import a configuration file from the GitHub repository and modify it. After that, if the Save and close button (1) is pressed, this configuration will be uploaded to the connected arbiter.

  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 and close button (1) is pressed, this configuration will be loaded into the connected arbiter.

  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 arbiter configuration and more information needed for Embention to resolve the issue. It is advisable to attach this folder when creating the issue.


    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 or contact



  6. These are the different functions of the arbiter. They are explained in the following menus.