Astos adapter - Troubleshooting
Table of Contents
- Help Method
- Screen Definitions and Operations
- Commands and Operations
- Error Messages
- Error Conditions
- Recover Runs
Help Method
In the adapter every button and dropdown control has a descriptive label and may be accompanied by an informative Tooltip; if you mouse over certain controls some text will pop up with details on their respective functionality. Additionally, the ASTOS main window provides an interactive help system that provides more information on the various settings and controls on the currently active main panel as well as background information.
Screen Definitions and Operations
The ASTOS dialog for COMET Adapter has to display a lot of information, so a minimum screen resolution of 1920 pixels by 1080 pixels is recommended (see 5.2). Defining mappings is achieved by multiple nested dialogs. This is mainly done to accommodate current project requirements while also not violating general ASTOS workflow guidelines. This may be improved on in the future.
Commands and Operations
Data transfer activity and creation of data export mapping is done form the COMET adapter dialog. Import mappings are integrated with the native way ASTOS creates and handles internal Variables for external database sources (see 5.4.2).
Error Messages
An error dialog is used for conditions requiring direct user interaction. Problems occurring during ASTOS Scenario loading are displayed in the log panel on the main ASTOS window (see Figure 6-1). Errors during simulation are shown in the “ASTOS Execution Log” (see ASTOS user manual).
Error Conditions
The only direct failure conditions of the COMET adapter happen when URL or credentials are missing (see Figure 6-6) or invalid (see Figure 6-7) while connecting to a COMET data hub.
When importing or exporting mapped data to or from the hub, the Adapter checks for new revisions on the remote side and aborts the transfer (see Figure 6-8: New revision detected on server) to avoid import of stale data or overwrite updates by another user without review of changed data.
Recover Runs
Authentication errors can be rectified by retrying with the correct credentials. On persisting connection problems please contact the operator of your E-TM-10-25 server for further advice. When a transfer is aborted due to a new Revision of data in the associated EngineeringModel on the server, the locally cached data is updated automatically. The user can (again) review up-to-date differences, adjust which mapped elements to transfer and retry to execute the import or export task for the selected data. If the E-TM-10-25 server is not responding, you will notice it when attempting to transfer data to the server or if you try to refresh the locally cached data. You might want to reconnect to the COMET® server (the way you connect the first time).