Variable xml export/import does not consider parameters BACnetPropertyID and BACnetWritePriority for variables created on BACnetNG driver

• Related Articles

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

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

• Checklist: Driver(s) cannot establish a reliable communication

  Time estimate: 60 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] ...

• After XML Export and Import the Filter Parameters not correct

  Summary If the filter "Linked screens" is used in a screen switch function for a screen of type Faceplate and a screen of a screen container is linked then this is not properly stored with XML expor. This issue has been fixed. Description During XML ...

• [SAP Interface] Values of export parameters of SAP function are not assigned to variables

  Summary Two bugs occur in the SAP Interface: In the Service Engine, zenon variables are not updated correctly. And in the Engineering Studio, import/export parameters are swapped when importing RFC function configurations. These two bugs occur ...