This section explains each option and parameter available in MEX PDI Builder.
Once the installation is finished, open MEX PDI Builder and select the unit.
MEX mode: The MEX 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 went wrong in the configuration. For more information, see Troubleshooting section of this manual.
The user can access now to 3 configuration options:
MEX: It allows the user to work with offline configurations. A previously exported MEX PDI configuration can be opened and modified or it is also possible to build a new one from the default configuration.
Upload PDI: A previously exported MEX PDI configuration can be imported to the linked MEX.
When a configuration is loaded into MEX 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 section Migrate configuration - Troubleshooting in this manual.
Open MEX: By clicking on this option, MEX PDI Builder configuration menu opens with the configuration (the PDI files) loaded in the MEX. Then, the user can modify it online.
PDI files are the files that contain the configuration of the MEX.
These files are located in a single folder, setup, which contains several .xml files, where all parameters and the control system are stored.
Finally, click on ‘MEX’ to edit a configuration offline or ‘Open MEX’ to open the configuration and start editing it online.
When MEX PDI is open, the unit changes to Maintenance mode. In order for this to be possible, the user must first accept the confirmation panel below.
The different ‘buttons’ that can be seen in the initial menu of the MEX PDI Builder are explained below.
Save and close: After changes are done, press on the save button to apply the changes. While saving, a percentage of saving process is displayed.
As after saving any changes, the MEX unit needs to RESET and the MEX PDI Builder software will consequently close, users must accept the following confirmation panels in order for this to be possible:
As MEX is reset, it is not advisable to save changes during flight tests.
This button will only appear if a MEX is connected, i.e. when working offline this button will not be available.
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.
Import PDI from repo: 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 MEX.
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 MEX.
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 MEX configuration and more information needed for Embention to resolve the issue. It is advisable to attach this folder when creating the issue.
These are the different functions of MEX. They are explained in the following menus.