Remote Insulator Contamination Monitoring System
Chris Richards, J.D. Renowden · IEEE Power Engineering Review · 1997
erful features for the formulation of appropriate abstractions for the desired application. But programming is always easier if a specialized language is already available for the creation of similar applications. Specialized applications should use dedicated computational engines where the developer can build and compose with high level constructs. In addition to defining a new library of functions and overloading existing operators, such an engine must provide a minimal number of portable graphical data visualization and manipulation functions. It is obvious that programming a computational engine from scratch is a major effort. This paper proposes to use a widely used general purpose program available on most popular computer platforms as a computational engine: MATLAB. MATLAB has a large number of built-in functions and constructs covering a wide range of EMTP development needs and is expandable by means of optional toolboxes. The recent implementation of sparse matrix manipulation capabilities eliminates a major feasibility barrier. This paper presents the creation of MatEMTP: a transient analysis program in MATLAB M-files. It is based on a new formulation of the main system of network equations, designed to eliminate several topological data restrictions and capable of handling arbitrary switch interconnections. By programming through matrix and vector operations the MatEMTP code 1s naturally vectorized. To eliminate useless testing, initialization procedures and repetitive dead code executions, the readyto-run structure of Figure 1 is proposed. This data adaptable structure relies on the input processor to interconnect the M-files. The input processor is a separate program that decodes standard EMTP data files and creates the case.m file. This file is a processed file of network data created from the external case data format. The model selector is a set of M-files created by the inputprocessor for connecting required case.m models to the main program. All models are programmed in separate M-files that obey to a set of predefined core code requests. A typical request for a component model is “provide admittance matrix” or “update history”. The creation of any new model is as simple as programming a new M-file which is automatically recognized and inserted into the appropriate code location by the model selector. The organizer is another M-file created by the input processor that calls solution M-files according to selected options and overall solution needs. Thus, MatEMTP is based on a data dependent interconnection of individual code modules.