Troubleshooting¶
ARINC Communication not working¶
If ARINC communication does not work on the user’s CEX unit, it may be due to an incorrect configuration of the GPIOs in the GPIO panel. GPIOs configuration should be as shown below:
If users don’t have this panel configured this way and they don’t want to lose the CEX configuration they have already done, follow the next steps:
Open a configuration in CEX PDI Builder in offline mode by clicking on CEX option in the first window of the application:
Change the hardware version to
CEX 2.0 with GPIO
to be able to change the GPIOs configuration of the GPIO panel.Next, import the CEX configuration to be fixed.
To do this, click on the button and select the configuration from the local storage:
Go to Input/Output menu \(\rightarrow\) GPIO panel.
The configuration of this panel should be as shown below:
Once the changes have been made, export this configuration by clicking on the button and store it in the same folder from which it was previously imported to overwrite it with the correct settings.
Finally, upload the newly exported configuration to the CEX unit and check that the GPIO panel is correctly configured.
Maintenance mode (loaded with errors)¶
The following error message may appear when trying to save a change or import a configuration.
Therefore, CEX will be in ‘Maintenance mode (loaded with errors)’:
To check what the source of the problem is, the user can simply click on the PDI Error button , which will show what the PDI Error is:
PDI ID: ID of the PDI Error.
PDI Error Description: Description of this PDI Error. A list of all PDI Errors can also be accessed in the List of PDI Errors section of the 1x Software Manual.
Config ID: ID of the configurable (.xml file) containing the data in which the PDI Error has been caused.
Config Description: Description of the configurable (.xml file) containing the data in which the PDI Error has been caused.
Clicking the Export button will export a .csv
file with the same information shown in this PDI Errors panel.
Finally, it is possible to access the CEX configuration to fix this error.
Migrate configuration¶
Warning
When performing automatic migration from a previous version to the current version of the software, errors may occur.
It is then the responsibility of the user to check the subsequent result.