AccessIec870Sl: specific 870 master times out communicating to the 870 Process Gateway when a large number of variables are used in a sector

• Related Articles

• Checklist: Process Gateway cannot start

  Time estimate: 30 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

• Checklist: Process Gateway cannot establish a reliable communication

  Time estimate: 45 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

• Azure Process Gateway - Removing a large quantity of variables from the "Exported into MS Azure" column can take a long time or lead to unexpected behaviour.

  Summary In the Azure Process Gateway, removing a large quantity of variables (~1000) from the column "Exported into MS Azure" can take a long time or lead to unexpected behaviour. DescriptionIn the Azure Process Gateway, removing a large quantity of ...

• Process Gateway closes after acknowledging the error message "Memfile not large enough!" which appears immediately after startup of the Process Gateway.

  Summary When the zenProcGateway.INI file is empty the Process Gateway closes after acknowledging the error message "Memfile not large enough!" which appears immediately after startup of the Process Gateway. DescriptionWhen the zenProcGateway.INI file ...

• Command routing in the AccessDNP3 process gateway does not work correctly when the master issues trip or close commands and a boolean variable is used in zenon.

  Summary When using command routing in the AccessDNP3 process gateway with a boolean variable linked to a configured binary output in the DNP3 outstation, command routing does not work when a master issues a trip or a close command. The AccessDNP3 ...