Drivers cannot be exchanged using the API method ModifyVariable() when the source and the destination driver are using the same file name

• Related Articles

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

• Checklist: Communication to TwinCat via BeckhoffNG driver

  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. TwinCAT ADS communication library ...

• FAQ: How can I browse an OPC UA Server using the zenon OPC UA Client Driver?

  Go to Drivers > New Driver Create a Driver of Type "OPC UA Client Driver" Open the Driver Configuration Go to "Connections" Create a new Connection Enter your Discovery URL Enter your Server URL manually or click the 3 dots to browse the Discovery ...

• Exchanging a driver may result in an intermediate driver configuration file causing configured connections to be lost

  Summary When a driver is exchanged with a new driver, the driver configuration of the new driver is opened automatically. With some drivers that use TCP communication, the connections that are created in the driver configuration during the exchange ...

• A dot in the lot name leads to an incorrectly displayed file name when using the archive export function

  Summary File name for archive export does only contain lot name part before last contained dot Description File name for archive export does only contain lot name part before last contained dot Issue Number: 249934 Fixed on Date: 15.3.2022 Versions: ...