In command group configured screen is not included in XML export and cannot be set via API

• Related Articles

• The number of alarm group / class / area is not included in the XML export file

  Summary It is possible to manually configure the alarm group / class / area number ("Id") in the Editor, however this number is not included in the XML-file when exporting alarm groups / classes / areas Description It is possible to manually ...

• It should be possible to access (get and set) specific driver properties of the drivers MODRTU32, MODBUS_ENERGY and BACnetNG via the API. Furthermore it should be possible to export and import the driver configuration in xml format of these drivers via the API.

  Summary Specific driver properties of the drivers MODRTU32, MODBUS_ENERGY and BACnetNG should be accessible (get and set) via the API. Additionally it should be possible to export and import the driver configuration of these drivers in xml format via ...

• XML Import/Export for drivers via GUI

  Summary Driver configurations can be exported and imported as an XML file from version 12 in Engineering Studio. Description For this purpose, in the driver configuration in the Engineering Studio we added the menu items Export selected as XML and ...

• FAQ: Where can I find the XML device profile for COPA-DATA DNP3 drivers?

  What is a DNP3 XML device profile? Where can I find the XML device profile for one of the following drivers? DNP3_TG - Subset Level 1,2,3 and 4 for both requests and responses, DNP3 Master driver for zenon Service Engine AccessDNP3_SG - Subset Level ...

• XML export and (re)import of command groups removes wildcard-based interlocking variable entries.

  Summary In Command Processing for all variables – response, command and interlocking – the wildcard '*' is allowed (and recommended). During XML-export and (re)import the entries about interlocking variables are removed if had the wildcard. ...