The following are the known issues:
| Issue | Troubleshooting |
|---|---|
| The delta download of S7+ connections for legitimization from NoAccess to FullAccess does not work. | - |
| You get no response from the UI after you click on Deploy. In that case, the operation remains in progress state and buttons are disabled. | Close and reopen the SIMATIC S7 Connector. Perform again the required operation. |
The following data types are not supported for the TagWrite operation:
|
- |
| Editing of CHAR ARRAY data types for S7 connections is not supported. | - |
The browse feature 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.2.0, the complete feature is available in V1.3.0. |
| Sporadically, the browsing feature may fail due to any reason after several attempts. | Configure the tags manually 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. |
| Delta download of full text alarms for S7-300 and S7-400 PLCs 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. |
| Deleting a configuration of 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. | - |
| A maximum array size of 999 is supported for the CHAR ARRAY data type in S7 connections. | - |
| If you import a configuration file into the Common Connector Configurator, which was exported from the IEM using a version of the Common Connector Configurator earlier than 1.0.6, full downloads fail if there are S7+ tags with symbolic addresses. | Use imported files which are exported from a version ≥ 1.0.6. Browse all S7+ connections and then click Deploy. |
| If you import a configuration file into the Common Connector Configurator, which was exported from the IEM using a version of the Common Connector Configurator earlier than 1.0.9, full downloads fail if you have duplicate tag names within the same connection or if you use tag names with unsupported characters. | Use imported files which are exported from a version ≥ 1.0.9. Alternatively, you can check data sources again after importing and eliminate the duplicate tag names. |
If column widths were resized previously, the column widths are reset to default size due to the following scenarios:
|
Resize the column widths again. |
| If the number of tags 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 before completion of the mass deployment operation, you launch the UI in one of the selected Industrial Edge Devices, then new configuration is not reflected in the Industrial Edge Device. | You must wait for the completion of mass deployment operation before launching UI in other Industrial Edge Device which was selected as part of the mass deployment. |
| SIMATIC S7 Connector publishes tag data to broker using unreliable Qos policy -Qos0. This may result in some packet loss. | - |
S7+ browsing is not supported for following PLC type and FW version:
|
- |
| S7 Connector publishes multiple instances of same tag with different timestamp to broker when IED CPU is overloaded. This is done to ensure that no data loss happens even if there is data delay because of low CPU resources. | You must ensure S7 Connector gets enough CPU to process all the packets and send to broker. |
| In Optimized S7-Protocol (S7-1200/1500), filter is supported only for Datablocks. Tag filter based on M, Q, and I area is not yet supported. | - |
| The download fails for a project with 6000 tags if the tag name and connection name are long (200-254 bytes). | It is recommended to use smaller tag names and connection names, if you want to download large number of tags. |
| If legitimization is enabled in PLC and the full access is selected in the configurator, then you can browse PLC tags but not datablocks. There is no protection available for PLC tags regardless of the legitimization level. The PLC tags can always be browsed. | - |
| SIMATIC S7 Connector Configurator V1.3 is incompatible with previous versions of the run-time application. | You must update both SIMATIC S7 Connector Configurator and the run-time application to V1.3. |
| Total memory limit of SIMATIC S7 Connector Runtime is 920 MB. | - |
| Connection state of PLC and clients are displayed after 10seconds from the actual state. | - |
| If Tag XML import file is huge, then Import may fail. | You can increase the RAM (12GB) of IEM VM, to import Tag Files up to 110MB. |
| In S7 Connector, if runtime was running and IED restarts then S7 Connector tries to reconnect to Databus for 5 minutes. If within 5 minutes Databus Application is not up, no value is published to Mqtt broker. | You must redeploy the configuration. |
| When runtime is running, user is not allowed to deploy Optimized S7 Connection with TLS security enabled using certificates. | |
| The Configurator performance may degrade if there are more than 6k Tags present in the main configurator window or user had browsed connections containing more than 6k tags which are present as cached data. | If configurator runs slow, user should either delete the extra tags or clean the configuration by clicking My Installed Apps > Select S7 Connector App > Update Configuration > Select the configuration File > Update Now.User can then add and configure maximum of 6k Tags in the main configurator page. |
| If runtime is running and user performs deploy of more than 2k tags then it may fail. | User limit the Tag count to 2k when deploying in delta or user has to stop the runtime and select all Tags (Maximum 6k Tags) , deploy the project and then start the runtime. |
| When you use the application in Mozilla Firefox web browser and try to export the configuration using “Export” icon, the export configuration may not work. | You must use Google Chrome browser. |
| When user selects “Chinese” or “German” language from the browser settings, some of the text in the app is not translated correctly and displayed in English. | |
| Data stops publishing if 21 Optimized S7 Connection is kept for long run (More than 4 weeks). | You must redeploy the configuration. |
| If the user closes the S7 connector or user exports the configuration file, on browse Trust dialogue is prompted again. | |
| Tag write feature for PLC Simulator is not supported. | |
| The restoration process follows a specific order, where the connector is restored first, and then the Databus is restored next. If attempting to connect with the Databus before it is fully restored, the connection eventually fails. | You must re-deploy the configuration. |
| After a restore operation, Databus may require some time to become fully operational. During this period, attempting to connect the S7 Connector may result in failure. | You must re-deploy the configuration. |
| Updating the app without installing the Common Import Converter results in no configuration being shown in the Common Configurator, with zero data sources and zero tags. | Install the Common Import Converter.Navigate to getdata > Connector Configuration, and click Load Configuration. Upon reopening the Common Configurator, the migrated configuration is displayed. |
| If the Databus is stopped for a period exceeding 5 minutes, you may not receive metadata and data. | You must re-deploy the configuration. |
| If you deploy an empty configuration to the connector, the deployment process takes approximately 60 seconds. | |
| Consecutive empty deploy is not supported. | You must select at least one tag for downloading. |
| If the Optimized S7 Connection is browsed and user edits the Tag address in the Common Connector Configurator then Tag values will not be fetched | You must reinstall the App and ensure you do not edit the symbolic address of the Tag in the Common Connector Configurator. |