Quality codes
Quality Code entsprechend PROFIBUS PA bzw. OPC DA: Ergänzung der Quality Code-Tabellen für die Sub-Status
Sub-Status (Bit 5 bis Bit 2)
Sub-Status unterteilen die einzelnen Qualitäten.
-
Sub-Status "BAD"
BAD: Sub-Status
(Bits 5...2)
0000
Non-specific
There is no specific reason why the value is BAD.
0001
Configuration error
The value is not useful because of some inconsistency regarding the configuration.
0010
Not connected
The value is not reliable because the connection to the provider has been disconnected at consumer-side, e.g. a communication driver actively disconnects from a PLC on user request or by design.
0100
Sensor failure
The value is not useful because it cannot be converted, i.e. a value from the device (PLC) cannot be converted to the corresponding HMI tag.
0101
No communication, with last usable value
The value is not useful because communication to the data source failed, however a last known value is available.
0110
No communication, no usable value
The value is not useful because communication to the data source failed or has never been established since it was last out of service and a last known value is not available.
0111
Out of service
The value is not reliable because the provider side has been disabled or shutdown, e.g. a PLC is in stop mode, or a tag is disabled for maintenance purposes.
-
Sub-Status "UNCERTAIN"
UNCERTAIN: Sub-Status
(Bits 5...2)
0000
Non-specific
There is no specific reason why the value is UNCERTAIN.
0001
Last usable value
The connection to the data source is still established; however, the data source stopped updating the value for some reason.
0010
Substitute value
A predefined value is used in case of an invalid value due to communication issues with the data source or a range violation. The reason for providing substitute values is configurable.
0011
Initial value
A predefined value intended for the startup of the HMI system (or a sub-ordinate device) is used while not being able provide values from the data source.
0101
Range violation
The value lies outside the range defined by min value and max value. The Limits define which direction (min or max) has been exceeded.
0110
Sub-normal
A value derived from multiple values has less than the required number of good sources. This includes data aggregation by means of data compression algorithms.
-
Sub-Status "GOOD (cascade)"
GOOD (cascade): Sub-Status
(Bits 5...2)
0000
Non-specific
No error or special condition is associated with this value.
0110
Local override
The value has been overridden by the user or some logic in to continue operation. Typically, the input has been disconnected, and a manually entered value has been 'forced', or a value has been corrected.
Spezifische Informationen für WinCC Unified: Ergänzung der Quality Code-Tabellen für die Sub-Status
Erweiterter Sub-Status (Bit 11 bis Bit 8)
Der erweiterte Sub-Status gibt genauere Informationen über den Sub-Status. Der erweiterte Sub-Status ist für einige vom HMI-System gebildeten Quality Codes relevant.
-
Extended Sub-Status "BAD"
Extended Bad Sub-Status
(Bits 11...8)
0000
Non-specific
No HMI specific extended bad sub-status is associated with this value.
0001
Aggregated value
The value has been calculated out of multiple values with less than the required number of good sources. This includes data aggregation by means of data compression algorithms. The corresponding sub-status is set to 'non-specific'.
0011
Unusable value
A (logged) value has been identified to be incorrect, but a respective correction value is not available. The corresponding sub-status is set to 'non-specific'.
0111
Disabled
The provider of the value has been disabled and the previous value was BAD. The corresponding sub-status is taken from the last (previous) sub-status.
-
Extended Sub-Status "UNCERTAIN"
Extended UNCERTAIN Sub-Status
(Bits 11...8)
0000
Non-specific
No HMI specific extended uncertain sub-status is associated with this value.
0001
Aggregated value
The value has been calculated out of multiple values with less than the required number of good sources to be GOOD as well as less than required number of bad sources to be BAD. This includes data aggregation by means of data compression algorithms. The corresponding sub-status is set to 'sub-normal'.
0111
Disabled
The provider of the value (e.g. logging tag for logged value) has been disabled and the previous value was GOOD or UNCERTAIN. In case of GOOD the corresponding sub- status is set to 'last usable value'. In case of UNCERTAIN the corresponding sub-status is taken from the last (previous) sub-status.
-
Extended Sub-Status "GOOD (cascade)"
Extended GOOD Sub-Status
(Bits 11...8)
0000
Non-specific
No HMI specific extended good sub-status is associated with this value.
0001
Aggregated value
The value has been calculated out of multiple (good) values. This includes data aggregation by means of data compression algorithms. The corresponding sub-status is set to 'non-specific'.
0010
Manual input
A (logged) value has been created manually. The corresponding sub-status is set to 'non-specific'.
0011
Corrected value
A (logged) value has been corrected. The corresponding sub-status is set to 'non-specific'.
0110
Initial value
The local data source has been initialized with the configured initial value. The corresponding sub-status is set to ‘non-specific’.
HmiSimpleTag supports the definition of subsets for discrete values via class HmiEnumeration by optional Ref Attribute 'Enumeration'. Only values from the referenced HmiEnumeration are valid values for the HmiSimpleTag. The restriction applies to a single value, or all elements of a dynamic array of values.
The datatype of the HmiSimpleTag, or the base datatype in case of a DynArray, must match the datatype of the referenced HmiEnumeration.
In case that the value (received from external communications partners such as PLC's) does not match the valid enumeration values of the respective HmiSimpleTag, a configured substitute value is used and the quality code is set to "uncertain; substitute value", if configured; else the null value is used and the quality code is set to "uncertain; substitute value". Additionally, a corresponding trigger event is fired for tags.
Faceplates: Eigenschaft "Aussetzbar"
Die Eigenschaft "Aussetzbar" von Faceplate-Typen betrifft nur Skripte zur Dynamisierung. Ereignisse sind von der Aussetzbarkeit ausgeschlossen.
-
Das Aktivieren der Eigenschaft "Aussetzbar" kann in Runtime die Skripte zur Dynamisierung von nicht sichtbaren Faceplate-Instanzen aussetzen.
-
Welche Skripte ausgesetzt werden, steuert die Runtime-Umgebung und ist abhängig von der Performance in Runtime.
-
Es werden nur Skripte ausgesetzt, die zur Dynamisierung verwendet werden. Ereignisse sind nicht von der Eigenschaft "Aussetzbar" betroffen.
Systemfunktionen: Parameterbeschreibung von ÖffnePLCCodeAnzeigeVonFCAufruf geändert
Die Beschreibungen der zu übergebenden Parameter der Systemfunktion "ÖffnePLCCodeAnzeigeVonFCAufruf" für die Verwendung in der Funktionsliste und im WinCC Unified Objektmodell wurden angepasst:
|
Parameter |
Beschreibung |
|---|---|
|
Zeichenkettesuche |
Bei der Suche nach dem PIN-Namen wird nach einem Teilstring gesucht, d. h., der PIN-Name beginnt mit der in PIN übergebenen Zeichenkette. Ist dieses Bit nicht gesetzt, wird der vollständige PIN-Name mit PIN verglichen. |
|
PLC-Name |
Name der PLC. |
|
Enthaltener Block |
Name des Bausteins, der den Baustein "Aufgerufener Block" enthält. |
|
Aufgerufener Block |
Name der lokalen oder globalen Instanz einer Funktion, die im Code-Baustein aufgerufen wird, der zum Parameter "Enthaltener Block" gehört.
Wenn "Aufgerufener Block" innerhalb vom "Enthaltenen Block", bzw. dessen Funktionsbaustein (FB), mehrfach aufgerufen wird, dann wird immer zum ersten Aufruf von "Aufgerufenen Block" gesprungen. |
|
PIN |
Name des Input-PINs von "Aufgerufenen Block". Der Parameter dient dazu, in der PLC-Code-Anzeige das Netzwerk anzuzeigen, das mit dem Input-PIN verschaltet ist. |
|
Anwenderdatentyp-Instanz |
Name des an "PIN" verschalteten PLC Variablen oder Datenbautstein Variablen einer Anwenderdatentyp-Instanz. Der Parameter dient dazu, die Anzeige der Funktionen einzugrenzen, wenn die in "Aufgerufener Block" genannte Funktion mehrfach aufgerufen wird. Die Verwendung von Anwenderdatentyp-Instanzen setzt voraus, dass die Variablen der Anwenderdatentyp-Instanz vom gleichen Datenbaustein stammen wie auch die in "Aufgerufener Block" angegebene Funktion. |
|
Bildobjektpfad |
Pfad des Bildobjekts "PLC-Code-Anzeige". |