MATHDR32 formular - addition calculation results incorrect
Description
Formulas
with more than 40 variables are calculated incorrectly by MATHDR32
variables under certain circumstances. With zenon Logic the
formula is calculated correctly.
Cause:
Malfunction of the parser, which prepares the formula for the calculation.
This has been fixed. MATHDR32 now adds the values correctly.
To
benefit from this fix:
- Update your zenon Software Platform to the latest build of zenon 10
or higher.
Item ID: 257272
Version: 11.00 Build: 112904
Version: 10.00 Build: 113329
Related Articles
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 ...
Num_to_string function bad results
Description The NUM_TO_STRING function for float values returned incorrect results in certain cases. The issue has been addressed and the resulting string is filled with “*” now if the REAL/LREAL value is too big or too small. In these cases the ...
Expired/First-Login Users Can Trigger Password Reset with Incorrect Password During eSignature, Reuse Same Password Despite Password History Rules, and CEL Logs Incorrect Username
Description In the eSignature workflow, it was possible for users with expired passwords or newly created accounts to enter an incorrect password, triggering a prompt to reset the password within the signature screen. It was also possible to reset ...
Loadflow calculation: the LFR calculates a wrong path on writing the result to variables
Summary It was possible that loadflow calculation succeeded, but results were not distributed on some load paths with inactive branches, or from transformers connected directly to lines with impedance. Now all load paths will get valid load flow ...
CNet driver recording incorrect values
Description The CNetDrv driver recorded incorrect values (e.g. 0 instead of 1) because the receive buffers in the driver were not reset correctly when the connection was terminated. The issue has been addressed and the recording behavior is now as ...