User`s guide

DEFAULT_DAYLIGHT_POLICY_IS_CALENDAR
In revision 8.4.4, the implementation of time handling was comprehensively
rewritten. Both local and UTC time as well as daylight saving time are fully
supported. There is a slight incompatibility between the new and old
implementation of the scheduling of time channels: The default behaviour of time
channels at daylight saving time / standard time transitions has been changed.
Prior to revision 8.4.4, the scheduling of time channels was synchronized to the
local time of the system. When the local time was moved backwards at daylight
saving to standard time transition, the time channels stopped for an hour.
Correspondingly, at standard to daylight saving time transition, the time channels
were excessively scheduled.
In revision 8.4.4, the default behaviour is that the time channels are scheduled
evenly (synchronized to UTC time) when the local time changes due to daylight
saving and there is a new attribute DP (Daylight Switch Policy) to specify the
behaviour, see the manual “Application Objects”.
When "DEFAULT_DAYLIGHT_POLICY_IS_CALENDAR" is set, the time
channels created with earlier program revisions keep behaving as before. Even
scheduling is the default behaviour of new time channels, however.
ALLOW_CONFLICTING_F_ATTRIBUTE_NAMES
When a pre-8.4.3 application is upgraded to 8.4.5 or later, the creation of F (Free
Type) objects fails by PROF_FREE_ATTRIBUTE_NAME_ALREADY_EXISTS
(2212), if the F object defines attribute names implemented as common process
attributes in the base system in revisions up to 8.4.4. Examples of such conflicting
attributes are RB, TI, TY, OI, BL, RB, OR and CT.
When "ALLOW_CONFLICTING_F_ATTRIBUTE_NAMES" is set, such
conflicting attribute names are accepted when an F object is created.
This switch should be used only when an old application is upgraded, because the
new base system functionality implemented by conflicting attributes will be lost
when the name is overloaded. In addition, some common SCIL tools (such as the
Object Navigator) and other SCIL software may be confused when the data type and
meaning of some common attributes are not that expected.
4.1.4. Upgrading from revision 8.4.2
NO_QUALITY_ATTRIBUTE_SEMANTICS
In revision 8.4.2 and earlier, the quality attributes SB (Substituted), BL (Blocked),
OR (Out of Range) and OF (Overflow) have been information-only attributes, i.e.
they have been stored in the process object to be available for SCIL but their values
have not affected the behavior of the process object in any way.
144
SYS 600 9.2SYS 600 9.2
MicroSCADA Pro
Installation and Administration Manual
1MRS756115