3S_v3: after a reconnect, RDA data could not be read

• Related Articles

• Checklist: Data Missing in Service Engine

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

• FAQ: How, where, why and when does zenon Service Engine save data?

  zenon Disk Space Handling: The zenon Service Engine, by default, stores process data on the hard disk. This is true for a standalone zenon project, as well as the zenon Service Engine server(s) in the zenon network topology. This data consists of ...

• 3S_V3 Driver - Real-time data acquisition (RDA) variables are not handled correctly for V2.3 connections.

  Summary Real-time data acquisition (RDA) variables are not handled correctly for V2.3 connections. RDA does however work correctly for V3 Connections. DescriptionReal-time data acquisition (RDA) variables are not handled correctly for V2.3 ...

• FAQ: How can I backup the Service Engine data, the data created during Service Engine?

  The path of the Service Engine folder can be amended in the project properties and it is set into zenon6.ini (VBF30=) when the start project is set in Engineering Studio or in zenon Startup Tool. In the Service Engine folder, there is the subfolder ...

• 3Sv3 Driver: RDA type 3 and 4 error when change rda array block size dynamically at runtime

  Summary No RDA data can be received from the driver. A log message states, that the RDA count is not equal to the size of the RDA array variable in the PLC. Description If the RDA count (count variable in the RDA header) is not equal to the size of ...