3S_V3 RDA type 3: wrong calculation of size

3S_V3 RDA type 3: wrong calculation of size

Summary

Processing of RDA Type 2 and RDA Type 3 does not work.

Log-Message: "RDA Count (X) x Datatype-Size (Y) doesn't match RDA Blocksize (Z)."

Description

Processing of RDA Type 2 and RDA Type 3 does not work.

Log-Message: "RDA Count (X) x Datatype-Size (Y) doesn't match RDA Blocksize (Z)."

Information

use RDA type 4 instead



Issue Number: 175960
Fixed on Date: 20.2.2019
Versions: 7.60 0 BUILD 55240 | 8.00 0 BUILD 55271

    • Related Articles

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

    • Cannot create a CTI variable using driver object type V Memory

      Summary In zenon 7.10 Editor (32 & 64 bit), if you have a pre-existing CTI variable, you cannot change its driver object type from K-memory to V-memory. Note: Even with creating a new variable based on CTI driver, V Memory object Type, REAL Datatype, ...

    • MdiElement.Type returns wrong element types

      Summary MdiElement.Type returns wrong element types - e.g. for a button, tpLine is returned. Description MdiElement.Type returns wrong element types - e.g. for a button, tpLine is returned. Solution An issue was addressed in the API - now the ...

    • IEC 60870 Slave: wrong APDU Length calculation for series of M_ME_TC_1 (T14) and M_ME_TF_1 (T36) data

      Summary issue in Stack for IEC60870 Slave - in zenon Process Gateway and in zenon Logic - when driver is used with reduced setting for 'ADPU/Data size': for IOs (variables) of Type IDs: - T14 - M_ME_TC_1 - measured value, short floating point number ...

    • Bandwidth Calculation

      Bandwidth calculation for network project (example with IEC61850 Drivers). the packet size depends on various parameters (communication protocol, lower communication layers, single or bulk transfers, network quality,...) and therefore no generic ...