Transaction Groups: Add possibility to ensure Tag quality
R
Reto Kunz
Currently transactions are also completed when the quality of the tags / OPC items included in the transaction is bad. It is possible to write the aggregated quality value to a column in the database table.
However it would be really helpful for some applications to have better control over tag quality to ensure that only valid data ends up in the database.
A) Add the possibility to only execute a transaction when the tag quality of all items involved is "good".
B) Add a handshake signal to have a feedback when a transaction includes bad quality items. The information is already there, but it needs to be queried separately after the transaction has happened.
Log In
Z
Ziad Burjony
This would be really good. In particular for system of record applications. I have an instance where the transaction group errored due to DB connection, then came back healthy. However, it just kept picking up NULLs from the source tags (even though they were healthy). It was executing, putting NULL's in the DB with a bad quality code and reporting back to PLC (the handshake) that everything was just fine.