Section 5 Operator Interface National Language Support (NLS)
3BSE042835-600 75
National Language Support (NLS)
All texts in the faceplates shall be NLS-strings. The NLS-translator is common for
all standard libraries so that the total number of NLS-strings is limited. The NLS-
translator should further be placed outside the libraries since there is no easy way to
have version handled NLS-strings. Thus, since there is no version handling of NLS-
texts, it is not allowed to delete or change the meaning of a text once it has been
included in a release.
The alarm and event Message parameter and the initial value of the alarm
ConditionName parameter should also be NLS-treated via an Alarm and Event
translator. The Alarm and Event translator shall be common for all standard libraries
and placed outside the libraries.
Figure 22. Example of NLS treated default value
of Condition Name.
Interface between Control Builder and Operator Workplace
Control Builder parameters and variables are visible in the Operator Workplace via
the OPC server. Variables that are not used in the Workplace graphics should be
given the attribute hidden. Function block parameters should never be given the
attribute hidden even if they are not used in the graphics. The reason for this is to be
consistent with Control Module parameters, which cannot have any attributes.
Extensible parameters cannot be accessed via the OPC server.
Naming of any non-hidden variables should follow the same rules as parameters,
see Section 3, Parameter Interface (no restrictions on name length).
To Next Page
Loading...
Need help?
General
