Найти в Дзене
Геннадий Антонов

Data extraction from Sepam files (continuation), or how to find needle in a haystack.

This is continuation my last column, about extraction data from configuration Sepam's files. Briefly remind key point of this development.
That was task to extract data protections settings from Sepam's configuration files, to readable table form Excel, where it could easy to find some aberrations, settings mistake, data analysis with help automation means.
Moreover quantity of the devices, with such approach, does not matter - there is 300 or 5000 files.
Manually to do that almost not realistically.
I had real practical example, when I observed when one of not very good managers, gave the task to engineer's group, manually to prepare data for several hundreds relay protection devices, mainly Sepam.
Result was disappointing.
Besides that engineers were not glad, of that task, and this data, what was obtained by that means, just was overloaded by mistakes, mismatches and another mishaps.
Moreover, this data was incomplete - for example one unit protection 50-51 on Sepam it has 19 para
Sepam settings for 67N
Sepam settings for 67N

This is continuation my last column, about extraction data from configuration Sepam's files.

Big data and parsing Sepam file settings
Геннадий Антонов3 апреля 2021

Briefly remind key point of this development.
That was task to extract data protections settings from Sepam's configuration files, to readable table form Excel, where it could easy to find some aberrations, settings mistake, data analysis with help automation means.
Moreover quantity of the devices, with such approach, does not matter - there is 300 or 5000 files.
Manually to do that almost not realistically.

I had real practical example, when I observed when one of not very good managers, gave the task to engineer's group, manually to prepare data for several hundreds relay protection devices, mainly Sepam.
Result was disappointing.
Besides that engineers were not glad, of that task, and this data, what was obtained by that means, just was overloaded by mistakes, mismatches and another mishaps.
Moreover, this data was incomplete - for example one unit protection 50-51 on Sepam it has 19 parameters, there is all 16 units (for group A and B), where we have 304 parameters.
In the manually obtained data there was mo more than several parameters!

In general, since that software for data extraction was improved.
Rewritten from ground zero on C++.
Added support all possible protections for Sepam 80 series.
And such types like:
B80, B83, C86, G82, G87, G88, M81, M87, M88, S80, S81, S82, S84, T81, T82, T87
As well extraction such data settings:
1) General characteristics
2) CT and VT
3) Control CT and VT
4) Predefined control logic
5) Disturbance recorder settings
6) ACE850 - IP, mask, type of port etc
7) Protections - action trip on disturbance recorder start

I have prepared video, where I will show on the contrived example in 300 Sepam's files, where I intentionally made changes in settings:
50BF, 50N-51N, disturbance recorder settings, extended memory, logical discrimination.
And how it could be easy to find in report, what was generated by the program.


For example, I put all configuration Sepam's files, and report generated by the program from the video.

You could download that by the link.

Sepam_80_data_report

As well, as a bonus I would be suggest for my readers free extract data from their configuration files Sepam 80 series.
I will wait in comments feedback from your side.
Send me your requests with queries to extract data from Sepam files.