IEC61850 Server - valKind RO (Read Only) must also be taken in account for DA with FC = SP and SE

IEC61850 Server - valKind RO (Read Only) must also be taken in account for DA with FC = SP and SE

Description

The IEC61850 Server did not refuse written values on valKind RO (Read Only) for DA with FC = SP and FC = SE. 

The issue has been addressed. Now the IEC61850 Server refuses written values on valKind RO (Read Only) for DA with FC = SP and FC = SE. 

 

To benefit from this fix: 

  • Update your zenon Software Platform to the latest build of zenon 11 or higher. 



Item ID: 248296
Version: 14.00 Build: 293273
Version: 12.00 Build: 301428
Version: 11.00 Build: 314353

    • Related Articles

    • Checklist: OPCDA Server

      Time estimate: 20 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. Do NOT use DCOM in combination ...

    • zenon Changesets CSV

      Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in as Excel ...

    • zenon Changesets Excel

      Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in CSV format ...

    • FAQ: What are Installation and Security considerations of the zenon Smart Server and Smart Client?

      The attached document (English only) describes in some detail the specifics of the zenon Smart Server Application and the zenon Smart Client Application. Also a short explanation of security features and components is given. More information about ...

    • IEC61850 Server - TrgOps is out of range when writing bitstring on server with Padding =0

      Description Issue when an 850-client emulated with LibIEC850 stack writes bitstring size 6 value encoded as 8 bits - with padding=0 (MMS encoding) - to the TrgOps attribute of a Report Control Block in the data model of the IEC61850 Server. The ...