One click in Tekvel Magic software — and you have a MS Word protocol that covers every IED on the substation: a summary of all URCB/BRCB control blocks with their MMS reference, type, RptEna state, Owner client, triggers, optional fields, DataSet reference, BufTm and IntgPd; plus a detailed section decoding the bit fields and the element-by-element composition of every DataSet — with descriptions taken from the SCL file. The case closes the second half of the SCADA acceptance questions: «how it is configured» is now complemented by «how it is actually working right now», and you instantly see whether reports are sitting idle while SCADA collects data by periodic polling.
A contractor hands over an SCD file claiming it matches the actual device configuration. But how do you verify that quickly and provably when there are 76 IEDs on site and no permanent monitoring system? A field case from Tekvel: the verification module in the Tekvel Magic software automatically compared the device configurations against the SCD and produced an engineering deviation report covering DataSets, GOOSE, Sampled Values and MMS reports in 15 minutes.
There is quite a few projects we've met, where each IED publishes single GOOSE message with huge dataset instead of having several GOOSE. We decided to understand which solution is preferrable?
GOOSE-messaging has been covered a lot in many technical papers and to add anything valuable to the subject is rather difficult. But we will try. And functional constrained data will help us with that.
В предыдущей публикации [1] мы рассмотрели один из важных и наиболее обсуждаемых коммуникационных протоколов, описанных стандартом МЭК 61850 — протокол GOOSE, — предназначенный для передачи, в первую очередь, дискретных сигналов между устройствами релейной...
The GOOSE protocol, described in chapter International Electrotechnical Commission (IEC) 61850-8-1...
