When in Data Model of 850-Server the BRCB.rptID is empty then the IEC850 driver is not able to "Use Report-ID for RCB assignment" and is not storing EntryID to acquire buffered events after reconnect.

When in Data Model of 850-Server the BRCB.rptID is empty then the IEC850 driver is not able to "Use Report-ID for RCB assignment" and is not storing EntryID to acquire buffered events after reconnect.

Summary

According the IEC61850 Standard when RptID is empty then it means that it in Reports it will be the ObjectReference to RCB, e.g. "IEDNameLDInst/LLN0$BR$brcbST01". At the communication start or online browsing of available RCBs the IEC61850 Client driver reads (mms.read) RCBs from 850-Server. When in initial read response the RptID is empty then:

- you cannot configure the driver to "Use Report-ID for RCB assignment"; you must base configuration on RCB names.

- the driver is not able to store EntryID to acquire buffered events after reconnect. Even when the 850-Server sends Reports (mms.InformationReport) with object references in RptID field the driver does not remember EntryID received in the Report. As consequence the driver does not have any valid EntryID, so at restart /reconnect it always purges buffer - mms.write(PurgeBuf); even by active option 'do not purge buffer at start'.

Description

According the IEC61850 Standard when RptID is empty then it means that it in Reports it will be the ObjectReference to RCB, e.g. "IEDNameLDInst/LLN0$BR$brcbST01". At the communication start or online browsing of available RCBs the IEC61850 Client driver reads (mms.read) RCBs from 850-Server. When in initial read response the RptID is empty then:

- you cannot configure the driver to "Use Report-ID for RCB assignment"; you must base configuration on RCB names.

- the driver is not able to store EntryID to acquire buffered events after reconnect. Even when the 850-Server sends Reports (mms.InformationReport) with object references in RptID field the driver does not remember EntryID received in the Report. As consequence the driver does not have any valid EntryID, so at restart /reconnect it always purges buffer - mms.write(PurgeBuf); even by active option 'do not purge buffer at start'.

Solution

Now the IEC 61850 Client driver internally teats an empty RCB.RptID as equal ObjectReference to the RCB.

Workaround: update SCL-file on 850-Server to make it use non-empty RptID.

Information

According IEC61850 Standard the RptID field is optional in Report Control Block and mandatory in Reports.



Issue Number: 35349
Fixed on Date: 19.10.2015
Versions: 7.20 0 BUILD 23281

    • Related Articles

    • When IEC850 driver is configured to "Use Report-ID for RCB assignment" then it uses the globally configured TrgOps instead of the TrgOps per RCB

      Summary Issue when the option "Use Report-ID for RCB assignment" in IEC61850 Client driver is active: then to enable a RCB the driver uses the globally configured options (e.g. TrgOps) and not the options configured for this particular RCB. Affected ...

    • IEC61850 Server resets EntryID by any purge of BRCB

      Summary The IEC61850 Server - I/O driver in zenon Logic - resets EntryID to 0 when received purge for BRCB - when client writes */PurgeBuf[BR]=true in this BRCB. It causes that when client purges buffer frequently the Server uses for new Reports the ...

    • Checklist: Data Missing in Service Engine

      Time estimate: 60 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

    • Checklist: OPCDA Server

      Time estimate: 20 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Do NOT use DCOM in combination ...

    • Checklist: Driver(s) cannot establish a reliable communication

      Time estimate: 60 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...