Summary

The IEC61850 Server driver in zenon Logic (straton) should correctly handle all combinations of Trigger Options (TrgOps):

dchg, qchg and dupd based also on each Data Attribute definition in the SCL, not only on RCB setting.

In SCL-file there are definitions - pro each data attribute (e.g. for stVal) - if its DATrgOp.dchg, *.qchg and *.dupd are TRUE or FALSE.
No definition of DATrgOp means = FALSE.

The Report should include the attribute only when:
the RCB.TrgOps condition is fulfilled (such event happens)
AND
the responding DATrgOp of this attribute is true.

According the IEC61850 Standard a single data attribute should use either data-change (dchg) or data-update (dupd) trigger option, eventually combined with quality-change (qchg).
Also a single RCB should use either dchg or dupd, not both.
According the Standard only special Classes can use dupd.

Anyway, the driver should be able to handle dchg and dupd when set together in one DA or in one ReportControl and any combination of them; the TrgOp dchg as more important reason.

Description

The IEC61850 Server driver in zenon Logic (straton) should correctly handle all combinations of Trigger Options (TrgOps):

dchg, qchg and dupd based also on each Data Attribute definition in the SCL, not only on RCB setting.

In SCL-file there are definitions - pro each data attribute (e.g. for stVal) - if its DATrgOp.dchg, *.qchg and *.dupd are TRUE or FALSE.
No definition of DATrgOp means = FALSE.

The Report should include the attribute only when:
the RCB.TrgOps condition is fulfilled (such event happens)
AND
the responding DATrgOp of this attribute is true.

According the IEC61850 Standard a single data attribute should use either data-change (dchg) or data-update (dupd) trigger option, eventually combined with quality-change (qchg).
Also a single RCB should use either dchg or dupd, not both.
According the Standard only special Classes can use dupd.

Anyway, the driver should be able to handle dchg and dupd when set together in one DA or in one ReportControl and any combination of them; the TrgOp dchg as more important reason.

Solution

Now an eventual mismatch in SCL-file between the definition of DA and RCB the driver handles as following:

When the value of variable changes and this data attribute has one (or both) TrgOps - dchg or dupd - the driver creates new Report;
If only Report's TrgOps is dchg or dupd (or both); the TrgOps of DA and RCB do not need to match exactly.
In case of mismatch the Report's Optional Field has value of reason-for-inclusion (ReasonCode) according Report's TrgOps and not TrgOps of data attribute.
When Report's setting TrgOps includes both bits - dchg and dupd - then the reason-for-inclusion is dchg.

Information

Fixed in version 6600 of T5BusIec850s.dll