Hierarchy
⤷ PP-PI-PMA (Application Component) Process Management
⤷ COOPC (Package) OPC Interface (Open Process Control)
Basic Data
Data Element | COOPC_QUALITYSUB |
Short Description | OPC: Subquality of Item Value |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | INT1 | |
Data Type | INT1 | 1-byte integer, integer number <= 255 |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Subquality |
Medium | 15 | Subquality |
Long | 35 | Subquality of Value Read |
Heading | 30 | Value Subquality |
Documentation
Definition
The quality of an OPC value read comprises the following quality classes:
- Quality
- Quality substatus
- Value limit
This value specifies the value of the Quality Substatus class. The substatus describes the Quality value in more detail.
According to the OPC standard, OPC values can have the following substatuses:
Substatus for Quality "3 - Good"
Substatus Meaning
0 The value is accurate.
6 The value is accurate but was set manually.
Substatus for Quality "1 - Uncertain"
Substatus Meaning
0 The value is not accurate. However, the reasons are not known.
1 The data source no longer provides data but the reasons are unknown. The value may be obsolete.
4 The value is inaccurate since there's a sensor error.
5 The value read is outside the value limits.
6 The value is inaccurate since redundant data sources provide diverging values.
Substatus for Quality "0 - Bad"
Substatus Meaning
0 The value cannot be used. However, the reasons are not known.
1 There is a server configuration error.
2 The value cannot be determined since no logical data source is defined at present.
3 There is a device error.
4 There is a sensor error.
5 A connection problem occurred. The value last read exists but may be obsolete.
6 No value could be read since a connection problem occurred.
7 No value could be read since the data source is inactive or switched off.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20130529 |
SAP Release Created in | 46C |