Communication device for switchboard supporting high-speed modbus record query

The communication device addresses bottlenecks by asynchronously collecting and processing point and event data, enhancing responsiveness and data collection efficiency in switchboards.

KR103047798B1Active Publication Date: 2026-11-11LS ELECTRIC CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
KR1020240003504
Authority / Receiving Office
KR · KR
Patent Type
Patents
Current Assignee / Owner
Filing Date
2024-01-09
Publication Date
2026-11-11
Estimated Expiration
2044-01-09

AI Technical Summary

Technical Problem

Conventional communication devices in switchboards experience communication bottlenecks due to slow response times from lower power devices, limiting simultaneous accesses and restricting data processing to only point data, while event data remains unreadable.

Method used

A communication device with a gateway that collects and stores asynchronous point and event data, allowing synchronous or asynchronous transmission based on request type, and includes a control unit to manage data processing and conversion between Ethernet and serial protocols.

Benefits of technology

Enhances responsiveness by enabling asynchronous communication and processing of both point and event data, reducing bottlenecks and improving data collection performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 112024003039432-PAT00002_ABST
    Figure 112024003039432-PAT00002_ABST
Patent Text Reader

Abstract

The present invention relates to a communication device for a switchboard, and may include lower power devices of a power system, upper systems that receive information from the lower power devices and control the lower power devices, and a gateway that performs Ethernet communication with the plurality of upper systems and performs serial communication with the lower power devices, collects event data generated from the lower power devices asynchronously or synchronously, and transmits data synchronously or asynchronously depending on the type of request from the upper systems.
Need to check novelty before this filing date? Find Prior Art

Description

Technology Field

[0001] The present invention relates to a communication device for a switchboard that supports high-speed Modbus record queries, and more specifically, to a gateway device that supports communication between an upper system and a lower power device. Background Technology

[0002] Generally, as digitalization and interoperability with IT systems become increasingly important in the power distribution sector, the communication support methods for devices installed in distribution panels are shifting from serial-based low-speed communication to Ethernet-based high-speed communication.

[0003] However, for the sake of cost and application efficiency, communication protocol converters (hereinafter referred to as gateways) that convert low-speed serial communication, such as RS-485, into high-speed Ethernet-based communication are mainly used.

[0004] The gateway plays the role of converting data and transmitting it to lower-level power devices upon receiving a request from the upper-level system, and converting the responses from the lower-level power devices and transmitting them to the upper-level system.

[0005] Figure 1 is a block diagram of a conventional communication device for a switchboard.

[0006] Referring to FIG. 1, a conventional communication device for a switchboard includes lower power devices (300), such as a switchboard, a plurality of upper systems (100) that collect and control information of the lower power devices (300), and a gateway (200) that performs Ethernet communication with the plurality of upper systems (100) and performs serial communication with the lower power devices (300).

[0007] The above gateway (200) includes a transmitting / receiving unit (210) and a conversion unit (220).

[0008] The conversion unit (220) can convert specifications between communication protocols when there are various types of communication protocols, and the transmission / reception unit (210) performs actual communication with the upper system (100) and the lower power device (300).

[0009] Below, the configuration and operation of a conventional communication device for a switchboard with the above-mentioned structure will be explained in more detail.

[0010] First, the upper systems (100) can be understood as systems for collecting and controlling data of lower power devices (300), and the lower power devices (300) can be understood as power devices such as digital protection relays and digital power meters.

[0011] The gateway (200) relays communication between the upper system (100) and the lower power device (300), and enables connection of multiple upper systems (100) via Ethernet communication capable of high-speed communication of hundreds of Mbps with the upper system (100).

[0012] In addition, multiple connections can be made with the lower power device (300) at a low speed of tens of Kbps.

[0013] When multiple upper systems (100) make multiple requests, a communication bottleneck occurs because the connection speed with the lower power device (300) that must respond to the request is relatively slow.

[0014] Conventionally, in order to resolve communication bottlenecks, the number of accesses to the upper system (100) is limited.

[0015] That is, the upper system (100) limits the number of simultaneous accesses to the gateway (200) to prevent bottlenecks from occurring.

[0016] Additionally, the gateway (200) can provide a faster response to a request from the upper system (100).

[0017] That is, when the upper system (100) requests data, instead of using a method where the request is actually transmitted to the lower power device (300) to collect data and then transmitted back to the upper system (100), an asynchronous method is used where the data of the lower power device (300) is collected in advance and then the pre-collected data is provided when there is a request from the upper system (100).

[0018] In a conventional structure like this, when updating in an asynchronous manner, there is a limitation that it is possible to respond only to the specified data item of the specified lower power device (300), and there is a limitation that event data cannot be read and only point data can be read. The problem to be solved

[0020] The problem that the present invention aims to solve, taking into account the problems of the conventional technology described above, is to provide a communication device for a switchboard that provides asynchronous communication between an upper system and a lower power device, and can process event data, which is important data in power control, along with basic point data. means of solving the problem

[0022] The communication device for a switchboard according to the present invention may include lower power devices of a power system, upper systems that receive information from the lower power devices and control the lower power devices, and a gateway that performs Ethernet communication with the plurality of upper systems and performs serial communication with the lower power devices, collects point data and event data generated from the lower power devices asynchronously or synchronously, and transmits data synchronously or asynchronously according to the type of request from the upper systems.

[0023] In an embodiment of the present invention, the gateway collects and stores asynchronous point data and asynchronous event data from the lower power devices, and when the upper system requests asynchronous point data or asynchronous event data, it can transmit the stored asynchronous point data or asynchronous event data.

[0024] In an embodiment of the present invention, when the gateway receives a request for synchronization point data from the upper system, it may request point data from the lower power device and transmit the received point data and event data to the upper system.

[0025] In an embodiment of the present invention, the event data is stored in the gateway, and the stored event data can be transmitted asynchronously when the upper system requests event data thereafter.

[0026] In an embodiment of the present invention, the gateway checks for an event data request from the upper system, and if there is no stored event data corresponding to the index of the request, it can initialize the stored event data.

[0027] In an embodiment of the present invention, the initialization of stored event data can be performed by deleting the stored event data at the gateway, requesting event data from the lower power device, storing the received event data, and transmitting it to the upper system. Effects of the invention

[0029] The present invention provides asynchronous communication between an upper system and a lower power device, and by processing event data, which is important data in power control, along with basic point data, it has the effect of improving responsiveness. Brief explanation of the drawing

[0031] Figure 1 is a block diagram of a conventional communication device for a switchboard. FIG. 2 is a block diagram of a communication device for a switchboard according to a preferred embodiment of the present invention. FIGS. 3 to 5 are flowcharts illustrating embodiments of the present invention. Specific details for implementing the invention

[0032] To fully understand the structure and effects of the present invention, preferred embodiments of the present invention are described with reference to the attached drawings. However, the present invention is not limited to the embodiments disclosed below, but can be implemented in various forms and various modifications can be made. The description of the embodiments is provided merely to ensure that the disclosure of the present invention is complete and to fully inform those skilled in the art of the scope of the invention. In the attached drawings, components are depicted enlarged from their actual size for convenience of explanation, and the proportions of each component may be exaggerated or reduced.

[0033] Terms such as 'first' and 'second' may be used to describe various components, but said components should not be limited by said terms. These terms may be used solely for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, 'first component' may be named 'second component,' and similarly, 'second component' may be named 'first component.' Furthermore, singular expressions include plural expressions unless the context clearly indicates otherwise. Unless otherwise defined, terms used in the embodiments of the present invention may be interpreted in the sense commonly known to those skilled in the art.

[0034] Hereinafter, a communication device for a switchboard according to an embodiment of the present invention will be described in detail with reference to the drawings.

[0036] FIG. 2 is a block diagram of a communication device for a switchboard according to a preferred embodiment of the present invention.

[0037] Referring to FIG. 2, the present invention includes lower power devices (30), such as a distribution board, a plurality of upper systems (10) that collect and control information of the lower power devices (30), and a gateway (20) that performs Ethernet communication with the plurality of upper systems (10) and performs serial communication with the lower power devices (30), collects and stores point data and event data from the lower power devices (30) according to the conditions of point data and event data input from the upper systems (10), and transmits data synchronously or asynchronously according to the data processing method of the point data or event data input from the upper systems (10).

[0038] Hereinafter, the configuration and operation of a communication device for a switchboard according to a preferred embodiment of the present invention configured as described above will be explained in more detail.

[0039] First, the present invention provides a gateway (20) for communication between an upper system (10) and a lower power device (30), wherein the gateway (20) performs Ethernet communication, which is a relatively high-speed and wide-bandwidth communication method, with the upper system (10), and serial communication, which is a relatively low-speed and narrow-bandwidth method, with the lower power device (30).

[0040] The gateway (20) enables communication by connecting the upper system (10) and the lower power device (30), which have different communication methods.

[0041] The gateway (20) includes a transmitting / receiving unit (21), a control unit (22), a collection unit (23), a storage unit (24), a conversion unit (25), and a status unit (26).

[0042] The control unit (22) receives conditions for point data and event data and performs control according to a synchronous or asynchronous data processing method. The control unit (22) may be a processor.

[0043] When the gateway (20) is initially configured, conditions for point data and event data can be input into the control unit (22).

[0044] The conditions for point data and event data may be data regarding "ID of subordinate power device", "request code (Function code)", "address", "length", and "collection and initialization conditions".

[0045] Collection and initialization conditions may be limited to event data.

[0046] When the gateway (20) operates with point data and event data input in this manner, the control unit (22) collects data from the lower power device (30) using the collection unit (23) and the transmission / reception unit (21).

[0048] The collected data is converted into a protocol through the conversion unit (25) and stored in the storage unit (24).

[0049] The conversion unit (25) serves to convert the communication protocol between the upper system (10) and the lower power device (30). That is, it converts the Ethernet communication protocol of the upper system (10) into a serial communication protocol that can be processed by the lower power device (30), and conversely, converts the serial communication protocol of the lower power device (30) into the Ethernet communication protocol of the upper system (10).

[0050] In this way, after collecting point data and event data, the protocol is converted and stored in the storage unit (24), thereby allowing the point data or event data stored in the storage unit (24) to be transmitted with minimal delay when the upper system (10) requests point data or event data.

[0051] When a request from the upper system (10) is received through the transmission / reception unit (21), the control unit (22) checks whether the data request from the upper system (10) is synchronous point data, asynchronous point data, or event data.

[0052] In the above description, point data is assumed to be general data, not event data such as overvoltage or overcurrent.

[0053] The gateway (20) performs different data processing according to the type of data request from the upper system (10), and this can be done by changing the state according to the conditions of the point data and event data collected from the state unit (26) and the sequence of data requested by the upper system (10), and by making the control unit (22) recognize it.

[0054] Specific examples of implementation are as follows.

[0056] Processing of Asynchronous Point Data

[0057] Figure 3 is a flowchart of the processing of asynchronous point data.

[0058] Referring to FIG. 3, when there is a request for asynchronous point data from the upper system (10) (S31), it is received through the transmission / reception unit (21) of the gateway (20) and provided to the control unit (22).

[0059] The control unit (22) checks if there is asynchronous point data requested by the upper system (10) in the data stored in the storage unit (24) (S32).

[0060] At this time, if there is asynchronous point data (if there is a buffer value), the control unit (22) generates a response packet containing the asynchronous point data (S33), and transmits the response packet to the upper system (10) that requested the asynchronous point data through the transmission and reception unit (21) (S35).

[0061] If, as a result of the verification in step S32 above, there is no asynchronous point data requested by the upper system (10) among the data stored in the storage unit (24) (there is no buffer value), the control unit (22) generates an error packet (S34) and transmits the error packet to the upper system (10).

[0062] The upper system (10) that receives the error packet recognizes that it failed to receive asynchronous point data and can request synchronous point data again.

[0064] Processing of Synchronous Point Data

[0065] Figure 4 is a processing flowchart of synchronization point data.

[0066] Referring to FIG. 4, the upper system (10) requests the collection of synchronous point data when the request for asynchronous point data fails as previously described, or when there is a need to collect synchronous point data.

[0067] A request for the collection of synchronous point data is received by the gateway (20) through the transmission / reception unit (21) (S41), and the state unit (26) changes the control state of the control unit (22) according to the data sequence of the received request for the collection of synchronous point data (S42).

[0068] The control unit (22) provides a request from the upper system (10) to the lower power device (30) via serial communication (S43) and checks if there is a response to the request (S44).

[0069] When there is a response value of synchronization point data from the lower power device (30), the control unit (22) converts the response synchronization point data into a response packet capable of Ethernet communication (S45) and transmits it to the upper system (10) through the transmission and reception unit (21) (S47).

[0070] At this time, if there is no synchronization point data response value from the lower power device (30) for a set period of time, the control unit (22) generates an error packet (S46) and transmits it to the upper system (10) through the transmission and reception unit (21) (S47).

[0071] Synchronization point data can be collected through this process.

[0072] If no synchronization point data response value is received from the lower power device (30) for a set period of time and an error packet is received by the upper system (10), the upper system (10) may request synchronization point data again or display a message confirming whether power is not being supplied to the lower power device (30). Such a status check request may also be performed by the gateway (20). To perform this processing, the gateway (20) may further include notification means such as a display unit.

[0073] In the above example, requests from upper systems (10) can be processed in the order in which they are requested, but the order can be determined and processed according to the importance of the synchronization point data.

[0074] In other words, priority synchronization point data, such as synchronization point data related to the operation of a circuit breaker, can be determined, and the priority synchronization point data can be processed first compared to general synchronization point data.

[0076] <Processing of Event Data>

[0077] Figure 5 is a flowchart of the event data processing process using the present invention.

[0078] Referring to FIG. 5, the event data of the present invention is basically processed asynchronously, and can be processed synchronously only when it is determined that an initialization request is included in the event data request received from the upper system (10).

[0079] First, the gateway (20) receives an event data request from the upper system (10) (S501) and checks whether the event data request includes an initialization request (S502).

[0080] Initialization means deleting event data of a specific lower power device (30) that was stored in the storage unit (24) and recollecting event data to transmit event data received from the specific lower power device (30) to the upper system (10), and is performed through the following process.

[0081] The event data request from the upper system (10) includes an index value, and if the index value is different from the index value of the event data of the lower power device (30) stored in the storage unit (24), the control unit (22) determines that the event data cannot be used and deletes the event data stored in the storage unit (24).

[0082] The above index value is data of a bit value set on the header side of the event data, and the index value may be a value set to distinguish event data updated in the lower power device (30). The index value may be a value updated in order or a value related to the time of creation of the event data.

[0083] In other words, if the index value included in the event data request is different from the index value of the event data stored in the storage unit (24), the control unit (22) determines that an initialization request has been made and deletes the event data stored in the storage unit (24).

[0084] As described later, after deleting the event data, an initialization operation is performed to re-collect the event data and store it in the storage unit (24) in order to provide the event data to the upper system (10).

[0085] If it is confirmed that there was an initialization request in step S502 above, the state unit (26) checks the event data request (S503), changes the settings of the control unit (22) according to the request (S504), and the control unit (22) requests event data from the lower power device (30) via serial communication (S505).

[0086] Next, the control unit (22) checks whether there is a response from the corresponding lower power device (30) (S506).

[0087] If there is a response, the event data of the lower power device (30) is stored in the storage unit (24) (S503), the event data is converted into a response packet (S508), and then transmitted to the upper system (10) through the transmission / reception unit (21) (S512) to provide a response to the event data request of the upper system (10).

[0088] If there is no event data response from the lower power device (30) for the time set in step S506, an error packet is generated (S501) and transmitted (S512).

[0089] The upper system (10) that receives the error packet confirms that there is an error in receiving the event data and requests the event data again or, if necessary, performs an error indication.

[0090] If it is confirmed that there was no initialization request in the previous S502 step, check whether the event data requested by the upper system (10) was stored in the storage unit (24) (S509).

[0091] If there is no stored event data, an error packet is generated and transmitted as in step S510 (S512). Upon receiving the error packet, the upper system (10) requests event data again, and at this time, requests to delete the stored event data by creating a difference in index value and to collect event data synchronously.

[0092] If there is a stored event, the control unit (22) generates a response packet (S511) and transmits it to the upper system (10) through the transmission / reception unit (21) (S512), thereby enabling the reception and processing of asynchronous event data.

[0094] As such, the present invention can process event data asynchronously, and by enabling initialization by considering the collection time for asynchronous processing of event data, it can be continuously updated and processed.

[0095] This means that a gateway (20) communicating with an upper system (10) via Ethernet must transmit event data to multiple upper systems (10). When providing event data synchronously, a large amount of event data is required to provide event data to the upper systems (10), and data collection performance may be degraded due to traffic. However, the present invention has the feature of providing event data asynchronously to reduce traffic and prevent the degradation of data collection performance.

[0097] Although embodiments according to the present invention have been described above, they are merely illustrative and those skilled in the art will understand that various modifications and equivalent embodiments are possible therefrom. Accordingly, the true technical scope of protection of the present invention should be determined by the following claims. Explanation of the symbols

[0099] 10: Upper System 20: Gateway 21: Transmitter / Receiver 22: Control Unit 23: Collection Section 24: Storage Section 25:Conversion section 26:State section 30: Sub-power unit

Claims

Claim 1 A communication device for a switchboard comprising: lower power devices of a power system; upper systems that receive information from the lower power devices and control the lower power devices; and a gateway that performs Ethernet communication with a plurality of upper systems and performs serial communication with the lower power devices, asynchronously collects and stores point data and event data generated from the lower power devices, transmits the stored point data and event data to the upper system when there is a request for asynchronous point data or asynchronous event data from the upper system, and requests point data from the lower power devices and transmits the received point data to the upper system when there is a request for synchronous point data from the upper system. Claim 2 delete Claim 3 delete Claim 4 A communication device for a switchboard according to claim 1, characterized in that the event data is stored in the gateway, and the stored event data is transmitted asynchronously upon a request for event data from a higher system. Claim 5 A communication device for a switchboard according to claim 1, wherein the gateway checks for an event data request from the upper system and, if there is no stored event data corresponding to the index of the request, performs initialization of the stored event data. Claim 6 A communication device for a switchboard according to claim 5, wherein the initialization of stored event data is characterized by deleting the stored event data at the gateway, requesting event data from a lower power device, storing the received event data, and transmitting it to the upper system.

Citation Information

Patent Citations

  • Management of equipment change events in enterprise systems

    JP2017528844A

  • System and Method for acquiring time synchronized electric power measurement data

    KR101891030B1

  • Smart power management apparatus in building

    KR102577917B1