KR100359845B1 - Relay Monitoring System using Ole for Process Contron - Google Patents

Abstract

The present invention relates to a relay monitoring device using an Ole for Process Control (OPC) interface, and in particular, to apply to each application with only one communication driver using the OPC interface that can easily acquire the data of the relay to configure the monitoring device It is to provide a relay monitoring device. The relay monitoring device using the OPC interface is a relay monitoring device, the relay from the relay through the communication with the plurality of office client and application unit for monitoring the relay, and the plurality of each of the office client and application program unit Receive data and transmit the data of the relay to the plurality of PC client and the application program to the PC server, interpreting the communication protocol of the relay and converts the data of the relay in accordance with the communication protocol and output to the PC server It is configured to include a conversion unit.

Description

Relay Monitoring System using OPC Interface {Relay Monitoring System using Ole for Process Contron}

The present invention relates to a relay monitoring device using an Ole for Process Control (OPC) interface, and in particular, to apply to each application with only one communication driver using the OPC interface that can easily acquire the data of the relay to configure the monitoring device It is to provide a relay monitoring device.

Hereinafter, a conventional relay monitoring apparatus will be described with reference to the accompanying drawings.

FIG. 1 is a diagram for describing a relationship between a general OPC server and an OPC client.

An OPC-based system is a device manufacturer that provides an OPC server in consideration of device communication and device characteristics, and each system manufacturer builds a system using this OPC server.

The advantage of this method is that the device manufacturer is responsible for the integrity of the communication and characteristics of a particular device and does not require duplicate work on the communication and characteristics of the same device.

Office servers (first, second and third OPC servers 14, 15, 16) are supported by other manufacturers. Manufacturer-supplied code determines each device, the approach each server has, the name of the data, and how the server physically accesses it.

At a higher level, the office server 14, 15, 16 includes several objects. For example, a server, a group, an item, and the like.

The Office Server object manages the server's information and provides a container for the Office Group objects.

The Office Group object manages its own information and provides a mechanism for logical office item george and content.

The Office Group provides clients with organizing data. For example, a group must represent an item within a specific action, such as display or report.

The data can be read or written. The exception based on the connection is that it is created between the client and the item in the group and may or may not be available as needed.

The OPC clients (first, second and third OPC clients 11, 12, 13) may reset the frequency with which the OPC server provides updates of the data to the OPC clients.

FIG. 2 is a diagram for describing a general OPC group 21 and an item (first, second, and third items 22a, 22b, and 22c).

The office items 22a, 22b, and 22c indicate that the data source is connected within the server.

From the custom interface point of view, the office items 22a, 22b, and 22c are not accessible in the form of objects by the office clients 11, 12, and 13, and thus for the office items 22a, 22b, and 22c. There is no external interface defined.

All accesses of the office item 22a, 22b, 22c determine through the office group object containing the office item 22a, 22b, 22c or simply where the office item 22a, 22b, 22c is defined.

Associated with each item 22a, 22b, 22c are, for example, Value, Quality and Time Stamp. Value takes the form of a variant, and quality is similar to that specified in the fieldbus.

Therefore, it is easy to modularize each process when writing a communication driver that connects to the monitoring device of the relay by using such an interface, thereby providing convenience that can easily cope with hardware changes.

3 is a view for explaining a conventional relay monitoring device.

On the system side, efforts were needed to analyze the communication method and communication protocol of the devices when connecting them and to write them as application programs (first and second applications 31 and 32). Had to be reflected in the application.

In addition, in the conventional system, a system driver generates a communication driver (first, second, and third communication drivers 33, 34, and 35) of the necessary devices and connects them to the system. The problem lies in the development of certain drivers.

And there are many client applications that have been developed that require data from the data source for their programs and access the data by independently developed drivers.

If there is a server (communication driver) in charge of communication for each device (first, second, and third devices 36, 37, 38), the upper-level application programs are placed in the device (36, 37, 38). According to the type of the device (36,37,38) to obtain the data of the device (36,37,38) by creating a communication driver (33,34,35) Is written independently, and even if a single device (for example, 36) changes its protocol, not only the communication driver (33, 34, 35) but also the application (31, 32) needs to be changed. Have

In the case of monitoring the relay using the conventional monitoring device as described above, the conventional communication driver only plays a simple role of transmitting the relay's data to the application program, and thus the application program requires each independent communication driver.

Therefore, first of all, everybody has to write a driver for a specific manufacturer's hardware.

Second, inconsistencies between vendor drivers prevented hardware features from being supported by all driver developers.

Third, a driver that cannot be used may occur according to a change of hardware characteristics.

Fourth, two programs with independent drivers cannot access the same device at the same time.

SUMMARY OF THE INVENTION The present invention has been made in view of the above-mentioned problems of the prior art, and provides a communication device and a standard system interface software that can easily connect a relay to all monitoring devices from a large system such as DAS or SCADA to a simple single monitoring device. The purpose of the present invention is to provide a relay monitoring device using the PCC interface that can be easily changed by the driver according to the hardware change.

1 is a view for explaining the relationship between the general OPC server (OPC server) and the OPC client (Clint)

FIG. 2 is a diagram for explaining a general OPC Group and an Item.

3 is a view for explaining a conventional relay monitoring device

Figure 4 is a block diagram illustrating a relay monitoring apparatus using the PCC interface according to the present invention

FIG. 5 is a block diagram for explaining that the relay monitoring apparatus using the PCC interface shown in FIG. 4 monitors a plurality of relays.

* Description of the symbols for the main parts of the drawings *

40: relay monitoring device

41, 42: OPC client and application department

43: office server 44: conversion unit

45: relay

The present invention is characterized in that in the relay monitoring device, receiving a data from the relay through the communication between the plurality of PC client and application program unit for monitoring the relay, the relay and a plurality of each PC client and application program unit Each of the plurality of office clients and the application program to the PC server for transmitting the relay data of the relay, the communication protocol of the relay and the conversion unit for converting the relay data according to the communication protocol and outputs to the PC server .

Hereinafter, a relay monitoring apparatus using the PCC interface according to the present invention will be described with reference to the accompanying drawings.

4 is a block diagram illustrating the relay monitoring device 40 using the PCC interface according to the present invention, Figure 5 is a relay monitoring device 40 using the PCC interface shown in FIG. It is a block diagram for demonstrating this.

The relay monitoring device 40 according to the present invention monitors the relay 45 using the OPC server 43 serving as a driver in charge of communication with the OPC client and the application program, and the OPC server 43. The relay 45 which consists of the 1st-nth PCC client and application program parts 41 and 42 which have a program, and has data through the conversion part 44 which interprets a communication protocol is monitored.

Here, the relay monitoring device 40 and the conversion unit 44 are connected by an RS-232C cable, and the conversion unit 44 and the relay 45 are connected through a specific internal protocol (I-NET in the drawing).

Such a relay monitoring device can obtain the data of the relay 45 supported by the driver 43 in any application program even if there are several types of application programs. Can be. That is, one communication driver (office server 43) can support all the upper application programs.

In addition, even if the communication protocol of the relay 45 is changed, if only the communication driver (office server 43) is changed, the upper application can obtain data in the same manner.

The relay monitoring apparatus using the OPC interface monitors a plurality of relays as shown in FIG. 5, wherein the first, second and third devices 56, 57, and 58 of FIG. 5 are shown in FIG. 4. The conversion unit and the relay (44, 45), the first to third communication driver (53, 54, 55) is the office server 43, the first to n-th application (51, 52) is the first to n Office client and application program (41,42). Here, the first to third communication drivers 53, 54, and 55 and the office interfaces 51a and 52a of the first to nth applications 51 communicate through the common bus 59.

As described above, the present invention provides a circuit breaker for an upper wiring circuit in which a load side wiring circuit breaker having a lower priority is operated according to a priority when the electronic circuit breaker protects the lower load by blocking the line with an inverse time characteristic against an overload when an overload occurs. By reducing the current flowing, it protects critical loads and provides a safer switchboard for the user.

Claims (1)

In the relay monitor, A plurality of OPC client and application unit for monitoring the relay, An office server which receives data from the relay through communication with the relay and each of a plurality of office PC clients and an application program unit, and transmits data of the relay to the plurality of office PC clients and application programs; And a converter for interpreting the relay communication protocol and converting the relay data according to the communication protocol and outputting the relay data to the office server.