When t-attribute of a data object is managed manually in the zenon Logic project, a report may have been generated with the previous timestamp of the value change.
When t-attribute of a data object is managed manually in the zenon Logic project, a report may have been generated with the previous timestamp of the value change.
No workaround.
Theoretically, would be possible to write program in logic which in separated cycles, first maps t-attribute from the timestamp of zenon variable, and in next cycle - its status bits and value. Maybe tolerable to do on few variables, but not on many. And there is then still risk of data inconsistency: that updated t-attribute would be sent in the report about data change in other DO, and the relevant value/quality change for this DO - in the next report.