Search

Scope: Core (OPC-10000-*) All specs

10 result(s) for Bad_NoData

OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.2.2 Operation level result codes

Table 25 - Bad operation level result codes Symbolic Id Description Bad_NoData No data exists for the requested time range or Event filter. Bad_BoundNotFound No data found to provide ... used for cases where no data was found when performing a simple 'Read' request. Bad_NoData i s used in cases where some action is requested on an interval
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.2.2 Read Event functionality

interval in which no data exists, the corresponding StatusCode shall be Good_NoData. The filter parameter is used to determine which historical Events and their corresponding fields are returned ... Event field that cannot be returned. The value of the StatusCode shall be Bad_NoData . When reading Events, TimestampsToReturn only applies to Event fields that are of type DataValue
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.2.4 Read modified functionality

interval in which no Events exists, the corresponding StatusCode shall be Good_NoData. The filter parameter is used to determine which historical Events and their corresponding fields are returned ... Event field that cannot be returned. The value of the StatusCode shall be Bad_NoData . When reading Events, TimestampsToReturn only applies to Event fields that are of type DataValue
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.4 Interpolative

Bad values skipped or if Uncertain values are used. If no starting value then Bad _ NoData . See description of Interpolated Bounds (see 3.1.8 ) for more details Partial ... Multi Value bit Not Set StatusCode Common Special Cases Before Start of Data Return Bad_NoData After End of Data Return extrapolated value (see 3.1.8 ) (sloped or stepped according
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.10 Minimum

only Bad quality values are available then the status is returned as Bad_NoData . The timestamp of the Aggregate will always be the start of the interval for every ProcessingInterval ... values exist with the Minimum value StatusCode Common Special Cases Before Start of Data Bad_NoData After End of Data Bad_NoData No Start Bound Not Applicable No End Bound
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.11 Maximum

only Bad quality values are available then the status is returned as Bad_NoData . The timestamp of the Aggregate will always be the start of the interval for every ProcessingInterval ... values exist with the Maximum value StatusCode Common Special Cases Before Start of Data Bad_NoData After End of Data Bad_NoData No Start Bound Not Applicable No End Bound
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.25 Start

that value occurs. If no values are in the interval then the StatusCode is Bad_NoData . Table 73 - Start Aggregate summary Start Aggregate Characteristics Type Calculated Data Type Same ... Always Multi Value Not Set StatusCode Common Special Cases Before Start of Data Bad_NoData After End of Data Bad_NoData No Start Bound Does not apply No End Bound
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.26 End

that value occurs. If no values are in the interval then the StatusCode is Bad_NoData . Table 74 - End Aggregate summary End Aggregate Characteristics Type Calculated Data Type Same ... Always Multi Value Not Set StatusCode Common Special Cases Before Start of Data Bad_NoData After End of Data Bad_NoData No Start Bound Does not apply No End Bound
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.27 Delta

first or last values. The status is Good otherwise. The status is Bad_NoData if no Good raw values exist. Table 75 - Delta Aggregate summary Delta Aggregate Characteristics Type Calculated ... Multi Value Not Set StatusCode Common Special Cases Before Start of Data Bad_NoData After End of Data Bad_NoData No Start Bound Does not apply No End Bound Does
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.30 DeltaBounds

positive. If one or both values are Bad the return status will be Bad_NoData . If one or both values are Uncertain the status will be Uncertain_DataSubNormal . Table ... Custom Good if both bounds are Good Uncertain_DataSubNormal if either bound is uncertain Bad_NoData if either bound is Bad Partial Set Sometimes If an interval