LINT limits badly checked when forced
Description
The permitted values for LINT variables are
between -9 223 372 036 854 775 808 and 9 223 372 036 854 775 807. If an attempt is made
in zenon Logic to force the lower limit value -9223372036854775808
for a LINT variable, the error message "Invalid integer value"
is displayed. The value is not accepted as valid. However, 16#8000000000000000 can be used as a workaround.
This error has been fixed. -9223372036854775808
is accepted as a valid value for LINT.
To benefit from this
fix:
- Update your zenon Software Platform to the latest build of zenon 14
or higher.
Item ID: 274665
Version: 14.00 Build: 239777
Related Articles
Distributed Engineering: Changes in zenon Logic project cause all Services to be checked out
Description In the Distributed Engineering since zenon version 14 all services had to be checked out to make changes on an existing zenon logic project. The issue has been addressed and a check-out is not required anymore. To benefit from this fix: ...
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 ...
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 ...
straton strings with special characters are broken in force value dialog
Description In zenon Logic, strings with special characters are not displayed correctly in the Spy and in the Force value dialog. String values that are forced are not correctly written. This bug has been fixed. The value is displayed and written ...
AccessOPCUA: Takes very long time to start with Customer project
Description In the Process Gateway, AccessOPCUA takes a long time to start in some projects. This is due to the number of variables contained in the project. All variables have been checked to see if they have been configured in the Process Gateway. ...