Log In
Home
06/28/2021
Offline
Hello,
In the OPC UA document Part 13 for aggregates:
5.4.3.3 Explains the Aggregate Table description under which I have certain doubts for Status Code Common Special Cases:
Status Code Common Special Cases
Before Start of Data: If the entire interval is before the start of data.
[Question]: What will be the effect of this on status code ? Not Clear
After End of Data:If the entire interval is after the end of data (as determined by the Historian).
[Question]: Same as above
Start Bound Not Found:If the starting bound is not found for the earliest interval and it is not partial, then what, if any, special processing should be done.
[Question]: What will be the effect of this on status code ? Not Clear
[Question]: What special processing?
[Question]: Examples?
End Bound Not Found:If the ending bound is not found for the latest interval and it is not partial, then what, if any, special processing should be done.
[Question]: Same as above
Bound Bad:If the Bounding value is Bad, then what, if any, special processing should be done.
[Question]: Same as above
Bound Uncertain: If the Bounding value is uncertain, then what, if any, special processing should be done.
[Question]: Same as above
thanks
jackyjoy
Moderators-Specifications
Moderators-Companion
Moderators-Implementation
Moderators-Certification
Moderators-COM
02/24/2014
Offline
The table in question is titled "Aggregate Table Description", it provides description of the rows that are found in each of the table in the following sections that describe specific aggregates (i.e. An Average, TimeAverage etc). For all of the item list it is just the definition of what each item means - i.e. "After End of Data" - that this is an interval after the end of data in the historian - the affect on the status code is describe for the given aggregate - i.e. Average has a row with "After End of Data" there it describes that "Bad_NoData" is to be returned. By special processing it is describe that sometime just a fixed status is to be return sometimes some other action is to be performed - say Total - "After End Of Data" says "Value extrapolated, Uncertain status" which mean extrapolate a value to the end and use it for the total calculation, but add setting the Uncertain Bit in the status. Every Aggregate has a copy of the table and is an example.
If there is a specific Aggregate that you have a question about please ask about it
Paul Hunkar - DSInteroperability
06/28/2021
Offline
jackyjoy jackyjoy said
Hello,
In the OPC UA document Part 13 for aggregates:
5.4.3.3 Explains the Aggregate Table description under which I have certain doubts for Status Code Common Special Cases:
Status Code Common Special Cases
Before Start of Data: If the entire interval is before the start of data.
[Question]: What will be the effect of this on status code ? Not Clear
After End of Data:If the entire interval is after the end of data (as determined by the Historian).
[Question]: Same as above
Start Bound Not Found:If the starting bound is not found for the earliest interval and it is not partial, then what, if any, special processing should be done.
[Question]: What will be the effect of this on status code ? Not Clear
[Question]: What special processing?
[Question]: Examples?
End Bound Not Found:If the ending bound is not found for the latest interval and it is not partial, then what, if any, special processing should be done.
[Question]: Same as above
Bound Bad:If the Bounding value is Bad, then what, if any, special processing should be done.
[Question]: Same as above
Bound Uncertain: If the Bounding value is uncertain, then what, if any, special processing should be done.
[Question]: Same as above
https://krogerfeedback.nl https://talktosonic.onl https://talktowendys.vip https://whataburgersurvey.onl
thanks
jackyjoy
thanks for the awesome information.
1 Guest(s)
Usage Policy