
Abhijeet Paunikar
Member
Members
Forum Posts: 9
Member Since:
04/21/2017
04/21/2017

Hello Team,
There seems to be some mismatch in setting Calculated Bit. Please have a look at below scenario :-
Table 18 it is mentioned that for TimeAverage2, Calculated Bit as Set Always
Similarly in Table 32, for Count, Calculated Bit as Set Always.
But in A.5.2, Historian3/TimeAverage2 at timestamp 12:00:40.000 Status Code is Bad, CalculatedÂ
and in A.19.2, Historian1/Count at timestamp 12:00:32.000 Status Code is Bad.
Calculated bit is not set in case of Count Aggregates.
Please can someone confirm the correct behavior.
Regards, Abhijeet
Forum Timezone: America/Phoenix
Most Users Ever Online: 510
Currently Online:
Guest(s) 23
Currently Browsing this Page:
1 Guest(s)
1 Guest(s)
Top Posters:
Forum Stats:
Groups: 2
Forums: 10
Topics: 1456
Posts: 4932