Application of Power Intelligence Component Technology in Power System Zhang Mingxia, Song Wei, Mi Zeng (Department of Power, North China Electric Power University, Baoding 071003, China) Solve the problems of repeated development and maintenance of power system application software. The basic idea of ​​component software technology and the superiority of code reuse and the flexibility of building large-scale applications are introduced, and the practical components of fault calculation are compiled. The component object model is the standardized direction of power system applications. The IEC (International Electrotechnical Commission) 61970 series of standards and the CIM (Common Information Model) CIS (Component Interface Specification) are based on the component object model to standardize the development of EMS applications.
With the wide application of computer technology, the safe and stable operation of power systems is increasingly dependent on hardware devices and software products based on microcomputer technology. Wiring analysis, power flow calculation, fault calculation, etc. are the basic contents of many power system analysis and calculation software. Through years of theoretical research and engineering practice, a set of mature theory and effective algorithms have been formed. As far as the theory itself is concerned, the algorithm can meet most of the engineering needs. That is to say, for many years, a considerable number of researchers and engineers have undeniably fallen into the quagmire of engineering, university master students, engaged in intelligent design and information management of power systems. Many people have repeated the same work many times. Different companies and work units cannot share code. Even if the same work unit or even the code written by the same person, in many cases, the application environment and customer needs have to be reinstated. The huge waste of resources has largely hindered the promotion of application software.
Today's component software technology is no stranger. From OLE to ActiveX, from COM to DCOM, Microsoft has turned its concept of language-independent binary code reuse into reality, providing a good solution to many of the shortcomings in the software development process. Fang also opened up broad prospects for the software industry.
1 Insufficient analysis of traditional software The reasons for the traditional application software architecture and design ideas of the power system mainly include the following problems, resulting in waste of resources in software production and application.
Software has poor adaptability to the application environment, it is difficult to share code between different application environments; as the environment changes, many codes lose their vitality and have to be repeatedly developed; software maintainability is poor, it is difficult to adapt to equipment configuration, grid structure and protection setting Differences in principles make it difficult to apply new theories and methods in time to meet the new requirements of production operations. This results in a vicious cycle of long software development cycles and high costs.
Software relies heavily on programming languages. Applications developed in different languages ​​are difficult to interact. Developers must make trade-offs between various programming languages. It is difficult to combine the excellent performance provided by various programming languages ​​in the same application, so software products cannot satisfy many. Aspect of the demand.
Closed application architecture lacks the necessary flexibility. The parts are frequently passed data. The relationship is intricate and does not form enough independent functional modules. Once the application is formed, it is difficult to change.
The code-oriented rather than service-oriented design framework lacks openness and is difficult to meet the needs of an increasingly wide range of distributed network applications.
2 Limitations of object-oriented code reuse Object-oriented programming is somewhat acceptable to the software industry. Simply put, the goal of object-oriented programming technology is not to use a program that mimics computer logic to facilitate programming, but to let developers write programs in the real world where people think about problems. Object-oriented programming has gained popularity on a large scale because it allows developers to share code between disparate projects, but this reuse is limited to languages ​​and application environments. That is, they generally require the original developer and the person who intends to reuse the code to use the same programming language. If a class library is written in C++, then the application written in other languages ​​can't basically reuse the code; similarly, the ava class can only be used in the ava program.
True code reuse means that code must be written in a way that is versatile enough to rebuild larger code, and can be customized to the way the code works. So, while using object-oriented programming can achieve relatively more software reuse than not using it, it faces these limitations. How to apply code sharing and reuse to practical, realistic programming, although object-oriented programming has long been the most direct solution to this problem, but it is clearly not satisfactory.
3 The superiority of component software technology Component technology can also be understood as "object-based" programming technology, which has deep roots in the object-oriented technology that the software industry has been optimistic for many years, but it has essential differences. As mentioned above, object-oriented technology is powerless for collaboration and code sharing among programmers using different languages. Faced with the new requirements put forward by customers, the new environment of application or the new development of R&D, many codes have become the embarrassment of “the taste is unsatisfactory, and they are not willing to give up.†Component technology came into being, and the separation of interfaces and implementations made the code completely In the market, programmers don't have to repeat the work that many people have done, concentrate on the implementation of new functions, or even assemble large-scale applications without any code, just as PC manufacturers can assemble by purchasing various components. PCs with excellent performance, without having to produce all the parts themselves, do not care about the internal details such as the material and structure of the parts, and the concentrated expression of language independence, reusability, interoperability and independent development.
3.1 Component Objects COM defines and implements the software component mechanisms, which can be collectively referred to as "objects". COM objects are very similar to C++ classes, and they all support encapsulation, polymorphism, and inheritance. However, COM objects as binary objects are different from C++ objects, and COM objects are only concerned with interfaces. The reason why a COM component can construct an application depends entirely on the interface supported by the component. The function of a COM object is also reflected through the interface. Combined with database and network technologies, a large distributed application can be built entirely from a range of functionally independent software components.
3.2 The implementation of the component is the interface that allows the component to communicate with the user and other applications. Without the interface, the COM component is useless; the interface definition software and the common functions that the component can utilize are the only window of the component to the outside world. The design of the interface depends on the function of the component itself and its communication with other applications or components. The rationality of the interface design is directly related to the effective implementation of the component function and its communication mechanism with other applications, thus affecting the reusability of the entire application. Sex and maintainability.
The implementation of the component starts from the design of the interface, and plans the interface according to the functions to be implemented by the component and its interaction with other related applications, and strives that the functional modules can interact with each other independently and flexibly, maintaining the independence of the component and the interaction between the components and the components. Flexibility; when a component needs to call the functions of other components or send information to other components, it also needs to properly handle the call and trigger relationships between components; in large distributed applications, the functional division of components is also cautious at the beginning of the design. Consider the issue.
4 Component software technology adaptability in the power system requires only components to wake up. This is also the group's bli. Scheduling load of the Gallo power system application software in the book1 power system, due to the differences in the structure of the power grid and different functional requirements such as planning and design, operation analysis, the application software development also has different Focus. Specific applications developed for a particular system are difficult to promote. And a large number of these applications (such as wiring analysis, power flow calculation, etc.) public, basic functions, which will inevitably lead to the re-development of these functions in the relevant applications; in addition, the object-oriented technology through the implementation of the implementation of the inheritance of the reuse of code However, it limits the independent development of the object; in addition, as the demand for technology in the production and operation of power systems increases with the scale of the power grid, the requirements for self-contained and closed-door applications are often stretched and difficult. all. The application component software technology encapsulates basic functions such as wiring analysis and power flow calculation into independent soft components, and provides external interfaces and function functions to explain its functions, without having to consider how the soft components will be useful. The customer calls the corresponding interface function to obtain the required functions; of course, it is also possible to select the required components as the PC manufacturer, construct their own harmonic analysis, relay protection and other applications in any way, without having to produce any source by themselves. The code does not have to be specific to the specific structure.
Such "takenism", which has learned from others, has broken through the limitations of "self-sufficiency", making the production and standardization of power system software production, which will certainly improve resource utilization, promote the application of new technologies and methods, and ensure the power system more effectively. Safe and stable operation.
5 Fault calculation component The author developed the fault calculation component based on the component software technology, which can be “plug and play†in different development environments and power system application software, avoiding repeated development and realizing the sharing of software resources.
Thanks to the realization of the soft parts, the past has been overcome.
The drawbacks are that the related software has good maintainability and scalability, and will greatly shorten the development cycle of other applications in the power system.
For the sake of simplicity, the component provides an external interface to encapsulate its fault calculation function. The definition is as follows: The fault calculation uses a compensation method based on the multi-port network theory, and the principle is as follows.
The fault calculation component implemented in this paper is a basic component, and no other components are reused. However, in actual use, the fault calculation depends to some extent on the power flow calculation to obtain the necessary data. The author developed the basic components of the trend calculation in the early stage, and provided the interface ILoad-6 test component technology. Its purpose is its independence of language and platform. The author uses Visual C+ Bu 6.0 to implement the components, and the commonly used Visual C++60 and VisualBasic6. Tested in 0; the component has good application performance in the graphical relay protection setting calculation software.
7 Conclusion COM is not a language, but a binary standard that allows soft components to interact with each other like objects. It provides a component object model that bridges the shortcomings of object-oriented programming. The application of component technology in the design of power system software is still in the trial stage. There are still many details that need to be studied in depth. Its wide application will promote the exchange and cooperation between R&D personnel, promote the standardization and standardization of software production; The application architecture will be the overall model of future software.
Men T Shirt,Sports T Shirts,T Shirts For Men,Short Sleeve T Shirt
Zedote SCM (Shanghai)Co., Ltd , https://www.zerodowntech.com