Log In
Home
04/21/2017
Offline
Hello Team,
Could anyone please confirm what is expected for below scenario:-
What should be the statuscode/result when %Good or %Bad exceeds 100. As per OPC UA Document, mantis issue 2503 states in such scenario the result will have a status code of Bad_AggregateInvalidInputs.
But what if i have some good values for a particular processing interval and computation result for a aggregate is having a statuscode as Good. So in that case too, do we have to change the statusCode to Bad_AggregateInvalidInputs.
- Abhijeet.
PS :- I have checked for same scenario in Aggregate Tester Application provided by OPC UA. In that application they are limiting the user to enter a value between 0 to 100 for %Good and %Bad. So got a bit confused.
Moderators-Specifications
Moderators-Companion
Moderators-Implementation
Moderators-Certification
Moderators-COM
02/24/2014
Offline
Abhijeet,
The Aggregate Tester application behaves as any good client should - it does not allow invalid parameters to be entered. The Server should always check the input parameters since it cannot be guaranteed a well behaving client. The Server would see that the %good or %bad are invalid (outside of 0-100) and never even look for historical values. The historical request for the given item would return a StatusCode of Bad_AggregateInvalidInputs (and no values).
If the aggregate was part of a monitored item, the item would not be added to a subscription - it would return an error on the add Monitored item.
Paul
Paul Hunkar - DSInteroperability
1 Guest(s)
Usage Policy