SCL Editor [IEC61850-6]- the scl must not handle an error when checking a private types
Description
When importing an SCL file with Private tags
into the SCL Editor for IEC61850 in zenon Logic,
a syntax error is indicated. However, according to the standard, errors for Private tags should not be indicated during validation.
This behavior has been modified. Errors for Private tags are no longer indicated.
To benefit from this
fix:
- Update your zenon Software Platform to the latest build of zenon 14
or higher.
Item ID: 281751
Version: 14.00 Build: 239777
Related Articles
save after interlock assignment(change) in symbol visibility setting causes zenon editor crash
Description If a symbol whose visibility has been assigned an interlocking is saved while the Interlocking is still selected, may the Engineering Studio cause to crash. This error has been fixed. To benefit from this fix: Update your zenon Software ...
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 ...
iec870 driver does not transfer to SE new values of command variables if the old value had status bit OFF
Summary The IEC 870 driver does not update values of command variables in the Service Engine if old variable values have status bit OFF. This behavior has been modified. Description The IEC 870 driver does not update the values of the command ...
Filter Controls are missing in Manual Data Editor
Description The Manual Data Editor does not display any filter rows for the column headers. The same applies to the dialog for calculated archives in the Reporting Studio. This error occurs since build 171299 for versions 10, 11 and 12. This error ...