AccessDNP3_SG: non-standard dual event not generated under specific circumstances

• Related Articles

• Checklist: Process closes unexpectedly (***Non-reproducible***)

  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] ...

• AccessDNP3_SG: the DNP3 outstation does not re-order value changes based on the timestamp in the event buffer

  Summary The AccessDNP3_SG process gateway has been enhanced with an option to configure the event ordering. Either chronologic ordering or ordering in the order of observed occurrence (default) can be configured. The order of occurrence is in ...

• Azure Process Gateway is not responding under specific circumstances

  Summary The Azure Process Gateway changes from "OK" to "Not Responding" under specific circumstances. Observed with a zenon project exposing about 2700 variables to Event Hub via json format, and a 5[s] integrity period. This causes the user ...

• The OPC UA server sends non-empty keep-alive publish responses with all monitored items under specific circumstances

  Summary When a subscription is created by an OPC UA client with publishing disabled and monitored items are added and after that publishing is enabled, the OPC UA server returns all monitored items in publish responses in keep alive messages although ...

• It may happen that some standard recipes screen specific functions are not logged in the chronologic event list in the runtime.

  Summary Although the actions are executed correctly, the "new recipe"/"delete recipe"/"read recipe" standard recipes screen specific functions are not logged in the chronologic event list when executed from a client runtime. DescriptionAlthough the ...