Articles
Turning a pcap into a technical report in one click: automated analysis of a digital substation's GOOSE traffic
On a digital substation, the end devices kept reporting a communication fault that just as suddenly cleared itself, and the cause stayed unclear — the alarm was a shared one. The only source of information was a pcap file about 11 minutes long — almost 186,000 GOOSE packets and more than 200 sources. A manual analysis in Wireshark at that scale would have taken hours. We show how, in a few minutes, the Tekvel Magic software turned the network capture into a structured Excel report of an unscheduled inspection.
Magical case #3: a documentation on IEC 61850 reporting — from an SCD or a set of CID files in one click
One run of Tekvel Magic software over SCL data — and you have a ready MS Word document - Signal list: a per-device summary, full detail of every URCB/BRCB control block and an element-by-element breakdown of every DataSet, with signal descriptions taken straight from the SCL. The module runs offline — from an SCD file or a folder of CID files, with no need to connect to the devices. The third case in the series closes the «how do you hand it over» task: handover documentation and as-built documentation in a single run, plus a separate «Configuration findings» document with a lightweight offline audit.
Magical case study #2: a report-control-block audit in IEDs — in one click
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.
Magical Case Study #1: How to Verify That an SCD File Matches the Actual Device Configuration at a Digital Substation
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.
Long-Term Traffic Capture with dumpcap
How to use the dumpcap command-line utility for stable long-term network traffic capture — without Wireshark freezes or crashes.
confRev: How Configuration Revisions Can Ruin Communications
8 out of 10 configurators fail to fully recognize SCD files. We analyze the confRev attribute in GOOSE and SV: what happens when the value does not match the expected one, and how this nearly derailed the commissioning of a real project with 43 IEDs.
Transmission of data structures in a GOOSE message
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.
MMS Protocol
В предыдущей публикации [1] мы рассмотрели один из важных и наиболее обсуждаемых коммуникационных протоколов, описанных стандартом МЭК 61850 — протокол GOOSE, — предназначенный для передачи, в первую очередь, дискретных сигналов между устройствами релейной...
GOOSE protocol
The GOOSE protocol, described in chapter International Electrotechnical Commission (IEC) 61850-8-1...