The value (%v) in the dynamic limit text is not converted into the secondary unit

• Related Articles

• "Export CEL" function cuts off the Limit Value Text (by using CSV Export)

  In some cases the "Export CEL" function will cut off the Limit Value Text (by using CSV Export) by projects converted from older versions. To fix this effect you need to create a new "Export CEL" function in actual version.

• The dynamic text element property "use limit value color" may not work as expected in the Runtime.

  Summary The dynamic text element property "use limit value color" from variable may not work in the Runtime when executing a unit switch and the displayed text is set as "variable value". DescriptionThe dynamic text element property "use limit value ...

• Dynamic limit text does not support japanese characters

  Summary Dynamic limit text only stores values of string variables as ANSI. Description Dynamic limit text only stores values of string variables as ANSI. Issue Number: 189397 Fixed on Date: 29.8.2019 Versions: 8.00 0 BUILD 60603 | 8.10 0 BUILD 60592

• AML and CEL continuous export write an empty text for dynamic limit texts that do not use other variables

  Description In a zenon project "Long dynamic limit texts" are disabled for AML or CEL. An entry for reaction matrix or a variable limit value uses dynamic content but does not refer to other variables. For example: " $The value is ;%v". The entry has ...

• Command Processing Screen doesn´t resolve Dynamic Limit Value Text

  Description Dynamic limit texts are displayed correctly in Dynamic Elements and CEL. But in Command Processing screens, Dynamic Limit Texts values are not resolved. This behavior has been changed: Placeholders for Dynamic Limit Texts are also ...