Known Issues¶
The following are the known issues:
| Issue | Troubleshooting |
|---|---|
| When you change the user in the Management UI of the IEM, it is possible that you still see the Edge Devices from the previous user. | Clear the cache of your Internet browser and refresh the IEM. |
| It is possible that the error "Out of memory" occurs in the VM with the issue that the IEM is not accessible anymore. | Reboot the VM. |
| Edge Apps do not run due to app signing implementation. | Use the latest IE App Publisher version and create a new version of the Edge App in the IE App Publisher. Afterwards, upload the new version to the catalog of the IEM and install and run the Edge App. |
| In the SIMATIC S7 Connector Configurator, the delta download of S7+ connections for legitimization from "NoAccess" to "FullAccess" does not work. | - |
| In the SIMATIC S7 Connector Configurator, you will get no response from the UI after you click on "Deploy", "Start" and "Stop". In that case, the operation remains in progress state and buttons are disabled. | Close and reopen the SIMATIC S7 Connector Configurator. Perform again the required operation. |
| When you take a snapshot of the Industrial Edge Management OS (IEM‑OS) in the VM while the VM is running and you restore the snapshot, you will be signed out from the Industrial Edge Management when you open an app in the "Catalog" menu item in the Management UI. Also, when you restore the snapshot in this case, the time of the VM is not aligned with the current time. | To realign the time of the VM, reboot the VM or restart NTP services. When you take a snapshot of the Industrial Edge Management OS (IEM OS) in the VM while the VM is powered off, this issue will not occur and you do not have to reboot the VM or restart NTP services. |
| For Edge Devices, the IP range 172.17.0.0/16 is reserved for Docker. This IP range is not configurable and hence you must not use this IP range. Due to this, when you want to connect an Edge Device to the Industrial Edge Management and the Edge Device IP is in the same subnet as the reserved Docker IP range, the Edge Device is not able to connect to the Industrial Edge Management. For example, when the Edge Device IP is in subnet 172.17.24.XX, the Edge Device is not able to connect to the Industrial Edge Management. | To successfully connect an Edge Device to the Industrial Edge Management, ensure that the Edge Device IP is not in the same subnet as the Docker IP range. |
| In the SIMATIC S7 Connector Configurator, the delta download fails if there were already downloaded tags or newly added tags containing a tag name that includes a dot in its name. Delta download fails if there are any tags including a dot already downloaded in the runtime. | If you only want to start the runtime including all tags, stop the runtime and redeploy the tags (you can also select tags with a dot). If you want to perform a delta download, no tags including a dot are allowed. In this case, you must stop the project, select the tags without a dot in their tag names and deploy the project. Start the runtime and proceed with the delta configuration. |
| In the SIMATIC S7 Connector Configurator, several spaces in a row and the following characters are not supported for tag and connection names: # : > < [ ] „ " + / \ . $ | - |
| In the SIMATIC S7 Connector Configurator, browsing of S7+ and OPC-UA connections is not supported for S7‑1200 PLCs. | - |
In the SIMATIC S7 Connector Configurator, the following data types are not supported for the "TagWrite" operation:
|
- |
| In the SIMATIC S7 Connector Configurator, the "DateTime" data type is not supported for S7‑1200 PLCs. | - |
| In the SIMATIC S7 Connector Configurator, editing of "CHAR ARRAY" data types for S7 connections is not supported. | - |
The browse feature in the SIMATIC S7 Connector Configurator is provided as preview for ease of configuration, hence the following issues are known with regard to this feature:
|
Configure manually the tags or import the exported files from the TIA Portal. The browse feature is provided as beta functionality in V1.0.0, the complete feature will be available in V1.1.0. |
| If the browsing feature in the SIMATIC S7 Connector Configurator fails due to any reason after several attempts. | Configure manually the tags or import the exported files from the TIA Portal. |
| Browsing S7+ data sources is not supported for ET200 Open Control PLCs. | - |
| Manual adding of symbolic addresses for S7+ tags is not supported. | Symbolic addresses are only supported in browsing S7+ data sources. |
| In the SIMATIC S7 Connector Configurator, delta download of full text alarms is not supported. | Full text alarms are only supported in S7-300 and S7-400 PLCs in the full download configuration. To get full text alarms, stop the project and download the project with S7‑300 or S7‑400 PLCs. |
| When you update the configuration inside the IE Databus Configurator of an Edge Device, an according job is created in the IEM. If you delete this job while the job is in "pending" state, the IE Databus Configurator does not work anymore properly. | Delete and reinstall the IE Databus Configurator. The existing configurations will not be lost but you have to click "Deploy" inside the IE Databus Configurator to apply the configurations again onto the system app. |
| When you edit and update the default configuration file of the IE Cloud Connector system app of an Edge Device, an according job is created. This job cannot be tracked by the IE Cloud Connector Configurator. When you now create another job from the IE Cloud Connector Configurator, the existing job may be overwritten by the second created job since the jobs in the job queue are not executed in sequence. | - |
| After you unistall and reinstall the IE Cloud Connector system app onto an Edge Device, the connection still displays the previous status. | Click "Deploy". |
| When the UI of the IE Cloud Connector Configurator is already opened and if in that time the Edge Device is no longer available or not connected anymore to the IEM, the connection status will not be updated. The UI of the IE Cloud Connector Configurator does not contain a status indicator for Edge Devices. | - |
| If you corrupt respectively do wrong configurations in the configuration file of the IE Cloud Connector system app of an Edge Device and you then open the IE Cloud Connector Configurator, an according error message is displayed. In that case, the "Bus adaptor" in the IE Cloud Connector Configurator UI still displays a connected connection status although default values are loaded and displayed. | Click "Deploy". |
| After you close and relaunch the IE Cloud Connector Configurator, as well as for multiple user accesses, the IE Cloud Connector Configurator needs 10 seconds to open again. | - |
| No root CAs and no wildcard certificates are not supported in the IE Cloud Connector Configurator. | - |
| If the created subscription or metadata topics in the IE Cloud Connector Configurator are not listed and do not have permissions in the IE Databus Configurator, the IE Cloud Connector Configurator UI though displays a connected status, even if all of your provided data is entered correct in IE Cloud Connector Configurator and even if the clients are not subscribed. | Ensure that the created topics in the IE Cloud Connector Configurator are added to the IE Databus Configurator. |
| When you add a subscription or metadata topic for the first time in the IE Cloud Connector Configurator and if you enter wrong configuration data, an error message is displayed after you click on the "List Topics" button. When you correct the configuration data and click on the "List Topics" button once again, the same error message is displayed. | Ignore this error message and wait for some more time to see the topics displayed. |
| The IE Cloud Connector version 0.4.x has 1 single default template "CCConfig" that is an empty ".json" configuration file. The IE Cloud Connector version 1.0.x has 2 default templates; a "CCConfig" template that is a ".json" configuration file with some default values and another "CCS7Config" file. When you update the IE Cloud Connector to version 1.0.x, the "CCConfig" configuration file displays an empty ".json" file. The expected default values are not displayed. When you rollback the IE Cloud Connector to version 0.4.x, the "CCConfig" configuration file displays an empty ".json" file and the "CCS7Config" file that is not relevant in the IE Cloud Connector version 0.4.x. | In the update scenario, if you select the "CCConfig" configuration file and install the app, an error message is displayed on the first launch of the IE Cloud Connector Configurator prompting you to deploy the configurations to the runtime. If you have clicked the "Deploy" button in the UI, this error message does not appear again after relaunching the configurator. In the rollback scenario, ignore the unwanted "CCS7Config" file. The file does not have any impact on the functionality. |
| There is no retry concept in the IE Cloud Connector Configurator if any connection errors occur during the cloud connectivity. | You must manually save the configuration again. |
| There is no retry concept in the IE Cloud Connector Configurator if the broker is restarted. | You must manually save the configuration again. |
| When you browse an OPC-UA server in the SIMATIC S7 Connector Configurator from a project in the TIA Portal with 1 function block (FB) and several data block (DB) instances, only data of 1 DB instance is returned and thus results in false read data. | Configure manually the OPC-UA tags or use the exported "*.xml" file of the DB instances from the TIA Portal. |
| After you have installed an Edge App or updated an installed Edge App version, that are running behind a reverse proxy, on an Edge Device and you open the Edge App UI by clicking the tile of the Edge App in the Edge Device UI, a blank page opens. | Close the blank page, wait 1 minute and reopen the Edge App UI. |
| Deleting a configuration of the IE Databus and the SIMATIC S7 Connector by clicking the "Delete Configuration" button under the "My Installed Apps" menu entry starts a task on the according Edge Device but fails immediately. | - |
| If the IP address of the DNS server for Edge Devices has changed and you want to connect an Edge Device to the IEM, the "Please check Internet settings and retry" error message is displayed (as embedded DNS server is not updated) | Whenever the IP address of the DNS server has changed and you want to connect an Edge Device to the IEM, manually restart the Edge Device and perform again the onboarding process. |
| If you want to download the source components of an Industrial Edge Device firmware version by clicking the "Source Components" link in the "Firmware Catalog" menu entry in the admin panel, the operation either fails or does not respond. | Right click on the link and open the source components link in a new tab. The source components are being downloaded. |
| In the SIMATIC S7 Connector Configurator, a maximum array size of 999 is supported for the "CHAR ARRAY" data type in S7 connections. | - |
| If you import a configuration file, which was exported from the IEM through a SIMATIC S7 Connector Configurator version less than 1.0.6, into the SIMATIC S7 Connector Configurator, full downloads fail if there are S7+ tags with symbolic address. | Use imported files which are exported from a version ≥ 1.0.6. Browse all S7+ connections and then click "Deploy". |
| In the SIMATIC S7 Connector Configurator, connection names should be unique and names within a connection tag should also be unique. | - |
| If you import a configuration file, which was exported from the IEM through a SIMATIC S7 Connector Configurator version less than 1.0.9, into the SIMATIC S7 Connector Configurator, full and delta downloads fail if you use duplicate tag names in the same connection or if you use tag names with unsupported characters. | Use imported files which are exported from a version ≥ 1.0.9. |
Tags in the SIMATIC S7 Connector Configurator that are displayed in the invalid table after you click on the details link in the import or browse dialog window, follow the following priority:
|
- |
| If tag names, that you have browsed, contain a dot (".") in their names, the dot will be replaced by an underscore ("_"). This replacement is done to handle download failures, since dots are not supported. | - |
If column widths in the SIMATIC S7 Connector Configurator were resized previously, the column widths will be reset to default size due to the following scenarios:
|
Resize the column widths again. |
| If the number of tags in the SIMATIC S7 Connector Configurator is more than 4000 or if you import respectively browse tags, the response of resizing columns becomes slow and you may observe flickering of the UI. | - |
| If you have configured tags through the browsing functionality in the SIMATIC S7 Connector Configurator and you use the filter option, all browsed tags disappear. | If you use the filter option and browsed tags disappear, restart the configurator to retrieve the tags. Siemens recommends to not use the filter option when browsed tags are configured in the configurator. You can use column filters when you have either manually configured or imported tags in the configurator. |