The SCL-file defines trigger options for each RCB; possible TrgOps are: dchg, dupd, qchg, period, gi. The IEC61850 Server (zenon Logic I/O driver) supports all TrgOps but only when configured by an IEC61850 client - when the client enables a Report, it can set TrgOp bit 'general interrogation' too. And then the IEC61850 Server reacts on */GI[BR|RP] correctly.
But the IEC61850 Server ignores trgOp 'gi=true' in the definition of RCB from SCL-file and uses as default value 'false'. Thus, when a client by enabling of RCB does not write TrgOps then the Server does not react on GI requests.
The SCL-file defines trigger options for each RCB; possible TrgOps are: dchg, dupd, qchg, period, gi. The IEC61850 Server (zenon Logic I/O driver) supports all TrgOps but only when configured by an IEC61850 client - when the client enables a Report, it can set TrgOp bit 'general interrogation' too. And then the IEC61850 Server reacts on */GI[BR|RP] correctly.
But the IEC61850 Server ignores trgOp 'gi=true' in the definition of RCB from SCL-file and uses as default value 'false'. Thus, when a client by enabling of RCB does not write TrgOps then the Server does not react on GI requests.
The IEC61850 Server reads now the trigger option setting from SCL file. When in SCL file there is no item 'gi' in TrgOps then the default value is TRUE anyway.
Note: in Edition 1 of IEC61850-6 has a mistake - does not list this trgOp at all and the part -7-2 has some mistake too. Thus in the Standard the issue was first partial corrected by Tissue 275 and next completed in Tissue 453. In praxis first the Edition 2 closes this gap.
Issue has impact on test case Rp1.