A method and system for identifying a machine tripping in a station

Abstract

The application relates to the technical field of substation monitoring, and discloses a method and system for identifying machine tripping of a remote machine in a station, which method executes a script for cyclically testing the IP address of a remote machine communicated and connected to a front-end machine of a dispatch automation system according to a preset test frequency, forms a test result containing the IP address and the corresponding test time, and accumulates into a test log, matches the IP address of the remote machine communicated and connected to the front-end machine of the dispatch automation system in each test time in the test log with a preset remote machine IP configuration table, determines the remote machine and the machine tripping time of the remote machine, records the IP address of the remote machine communicated and connected to the front-end machine each time the script runs, thereby judging the real-time corresponding communicated remote machine and the machine tripping time of the remote machine, and when a large number of false signals triggered by machine tripping of the remote machine occur, the remote machine and the machine tripping time of the remote machine which send the false signals can be effectively located.

Description

Technical Field

[0001] This invention relates to the field of substation monitoring technology, and in particular to a method and system for identifying remote motor tripping within a substation. Background Technology

[0002] The remote control unit is an automatic device used to collect and transmit and exchange various information between the dispatch center and the substation in real time. Its main functions are to realize four remote functions: remote measurement, remote signaling, remote control, and remote adjustment.

[0003] The remote control unit (RCU) is responsible for transmitting substation operating signals to the dispatch automation system in real time. Dispatchers need to monitor the entire power grid based on these substation operating signals. The accuracy and real-time performance of the signals transmitted by the RCU must meet the specifications. However, due to various reasons, erroneous signals occur frequently, and a large number of erroneous signals transmitted in a short period of time can affect the dispatcher's monitoring of the power grid.

[0004] Currently, the substation remote control units (RCUs) adopt a dual-redundant configuration. Both RTU A and RTU B independently collect signals from the equipment within the substation. Due to imperfections in the synchronization mechanism between the RTUs or incorrect configuration parameters, the following phenomenon may occur: After RTU A sends data, it does not promptly notify RTU B. RTU B stores the signal in its buffer. When the host switches from RTU A to RTU B, historical events that have not been confirmed in RTU B's buffer will be sent to the dispatch terminal in a short period of time. The dispatcher's interface will be instantly flooded with these erroneous signals, affecting the monitoring of the power grid and hindering its stable operation.

[0005] In dispatch automation systems, the front-end unit has difficulty distinguishing whether the data is provided by remote control unit A or remote control unit B. Therefore, when a large number of false signals are triggered due to remote control unit disconnection, it is difficult to effectively locate the remote control unit that sent the false signal. Summary of the Invention

[0006] This invention provides a method and system for identifying remote motor tripping within a station, which solves the technical problem of difficulty in effectively locating the remote motor that sent the false signal when a large number of false signals are triggered due to remote motor tripping.

[0007] In view of this, the first aspect of the present invention provides a method for identifying remote motor switching within a station, which uses two remote motors and a front-end machine of a dispatch automation system. The two remote motors are each configured with a unique IP address, and the front-end machine of the dispatch automation system initiates a communication connection with only one of the remote motors with a unique IP address at any given time.

[0008] This method includes the following steps:

[0009] In response to the pre-entered IP test request, the script performs a cyclic test on the IP address of the remote machine connected to the front-end machine of the scheduling automation system according to the preset test frequency, and generates test results containing the IP address and its corresponding test time, which are then accumulated in the test log.

[0010] The IP addresses of the remote motors that the front-end machine of the scheduling automation system communicates with at each test moment in the test log are matched with the preset remote motor IP configuration table to determine the remote motors that the front-end machine of the scheduling automation system communicates with at each test moment and the switching time of the remote motors.

[0011] Preferably, the method further includes:

[0012] Obtain the two remote motors and their respective configured IP addresses to form a remote motor IP configuration table, wherein the remote motor IP configuration table contains the mapping relationship between remote motors and IP addresses.

[0013] Preferably, the step of responding to a pre-inputted IP test request and executing a script to cyclically test the IP addresses of the remote machines connected to the front-end unit of the scheduling automation system according to a preset test frequency specifically includes:

[0014] In response to pre-entered IP test requests, the system performs cyclical tests on the IP addresses of remote machines connected to the front-end of the scheduling automation system, based on a preset test frequency and by calling the netstat command of the Linux system.

[0015] Preferably, before the step of matching the IP addresses of the remote machines that the front-end machine of the scheduling automation system communicates with at each test moment in the test log with a preset remote machine IP configuration table to determine the remote machines that the front-end machine of the scheduling automation system communicates with at each test moment and the remote machine switching time, the method further includes:

[0016] The test logs are compressed, and the compressed test logs are sent to the web server in the third security zone through forward isolation.

[0017] Secondly, the present invention also provides a station-based remote motor switching identification system, which uses two remote motors and a front-end machine of a dispatch automation system. The two remote motors are each configured with a unique IP address. The front-end machine of the dispatch automation system initiates a communication connection with only one of the remote motors with a unique IP address at any given time.

[0018] This system includes:

[0019] The script execution module is used to respond to the pre-input IP test request, execute the script to perform cyclic testing on the IP address of the remote machine connected to the front-end machine of the scheduling automation system according to the preset test frequency, generate test results containing the IP address and its corresponding test time, and accumulate them in the test log.

[0020] The machine switching identification module is used to match the IP addresses of the remote machines that the front-end machine of the scheduling automation system communicates with at each test moment in the test log with the preset remote machine IP configuration table, so as to determine the remote machines that the front-end machine of the scheduling automation system communicates with at each test moment and the machine switching time of the remote machines.

[0021] Preferably, the system further includes:

[0022] The IP configuration module is used to obtain the two remote motors and their respective configured IP addresses to form a remote motor IP configuration table, wherein the remote motor IP configuration table contains the mapping relationship between remote motors and IP addresses.

[0023] Preferably, the script execution module is specifically used to respond to a pre-inputted IP test request, and perform cyclic testing on the IP addresses of the remote machines connected to the front-end machine of the scheduling automation system by calling the netstat command of the Linux system according to a preset test frequency.

[0024] Preferably, the system further includes:

[0025] The compression module is used to compress the test logs and send the compressed test logs to the secure zone 3 web server through forward isolation.

[0026] Thirdly, the present invention also provides an electronic device, comprising:

[0027] processor;

[0028] Memory used to store the processor's executable instructions;

[0029] The processor is configured to execute the instructions to implement the method described above.

[0030] Fourthly, the present invention also provides a storage medium that, when instructions in the storage medium are executed by a processor of an electronic device, causes the electronic device to perform the method described above.

[0031] As can be seen from the above technical solutions, the present invention has the following advantages:

[0032] This invention executes a script that cyclically tests the IP addresses of remote actuators (TAAs) connected to the front-end of a scheduling automation system according to a preset test frequency. This generates test results containing the IP addresses and their corresponding test times, which are accumulated in a test log. The IP addresses of the TAs connected to the front-end of the scheduling automation system at each test time are matched with a preset TAs IP configuration table to determine the TAs connected to the front-end of the scheduling automation system at each test time and the TAs's switching time. By recording the IP addresses of the TAs connected to the front-end each time the script runs in the log, the real-time corresponding TAs and their switching times can be determined. When a large number of false signals are triggered due to TAs switching, the invention can effectively locate the TAs that sent the false signals and their switching times. Attached Figure Description

[0033] Figure 1 A flowchart of a method for identifying remote motor switching within a station, provided by an embodiment of the present invention;

[0034] Figure 2 This is a schematic diagram of a station remote motor switching identification system provided in an embodiment of the present invention. Detailed Implementation

[0035] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0036] The present invention provides a method for identifying remote motor switching within a station, which uses two remote motors and a front-end machine of a dispatch automation system. Each of the two remote motors is configured with a unique IP address. The front-end machine of the dispatch automation system initiates a communication connection with only one of the remote motors with a unique IP address at any given time.

[0037] In one example, two remote controllers are defined as Remote Controller A and Remote Controller B. When the two remote controllers are configured in a master-slave mode, one remote controller acts as the master, responsible for providing data to the channel. The heartbeat line between the two remote controllers informs the standby controller which signals have been sent to the dispatch automation system. Upon receiving the acknowledgment signal, the standby controller clears the corresponding buffered signals. If the master controller malfunctions, the standby remote controller switches to the master and sends any unacknowledged signals in its buffer to the dispatch automation system.

[0038] The substation communicates with the dispatch automation system through two methods: a 2M dedicated line and a dispatch data network.

[0039] The substation adopts a redundant configuration of dual remote actuators, which are connected to the dispatch automation system in two forms: 2M channel and dispatch data network channel. Remote actuator A and remote actuator B elect a communication host based on their own communication status to provide data for the 2M channel. The front-end machine in the dispatch automation system cannot distinguish whether it is remote actuator A or remote actuator B that is providing data for the 2M channel.

[0040] The dispatch automation system adopts a dual-IP configuration mode for channels, filling the IP addresses of remote control unit A and remote control unit B into the channel configuration table simultaneously. The front-end unit will only initiate a connection to one of the IP addresses at any given time. When a remote control unit is disconnected, the IP address connected to the front-end unit of the dispatch data network will inevitably change. The network channel of the substation will only be interrupted when both remote control units experience network failures. The front-end unit in the dispatch automation system initiates a connection to all currently interrupted network channels via socket every 20ms.

[0041] This invention provides a method for identifying remote motor switching within a station, such as... Figure 1 As shown, Figure 1 This diagram illustrates a method for identifying remote motor switching within a station. The method includes the following steps:

[0042] Step 1: Respond to the pre-entered IP test request and execute a script to cyclically test the IP address of the remote machine connected to the front-end machine of the dispatch automation system according to the preset test frequency. Generate test results containing the IP address and its corresponding test time and accumulate them in the test log.

[0043] In one example, a timed task is created on the front-end machine of the scheduling automation system, and a script is written to perform cyclic testing on the IP address of the remote machine connected to the front-end machine of the scheduling automation system according to a preset test frequency. The test frequency can be set according to requirements, such as 1 / min, 1 / 30s, etc., and is not limited here.

[0044] In one feasible approach, in response to pre-entered IP test requests, the system uses the Linux system's netstat command to perform cyclical tests on the IP addresses of the remote machines connected to the front-end machine of the scheduling automation system, according to a preset test frequency. The netstat command displays network connections, routing tables, and network interface information, allowing users to see which network connections are active.

[0045] The `netstat` command is a console command and a very useful tool for monitoring TCP / IP networks. It can display routing tables, actual network connections, and status information for each network interface device. `netstat` is used to display statistics related to IP, TCP, UDP, and ICMP protocols, and is generally used to check the network connectivity of various ports on the local machine.

[0046] For example, the netstat command format is netstat -an|grep xxx.xxx.xxx.xxx (telematics unit IP address). The output of the command determines whether the telematics unit A or telematics unit B is communicating with the dispatch automation system in real time.

[0047] The front-end script executes once per minute, performing netstat tests on two IPs of the test station and accumulating the test results in the test log. The test log will accumulate a large number of test times and their corresponding IP addresses from the start to the end of the test. The test times are obtained based on the system's automatic clock. For example, if the output format is: 12:10 test station 192.168.1.1, this log records that at 12:10, the remote machine communicating with the front-end scheduling data network of the scheduling automation system is the remote machine at 192.168.1.1.

[0048] Step 2: Match the IP addresses of the remote motors that the front-end machine of the scheduling automation system communicates with at each test moment in the test log with the preset remote motor IP configuration table to determine the remote motors that the front-end machine of the scheduling automation system communicates with at each test moment and the switching time of the remote motors.

[0049] In one example, the remote motor IP configuration table is pre-generated. Specifically, two remote motors and their respective configured IP addresses are obtained to form the remote motor IP configuration table, which contains the mapping relationship between remote motors and IP addresses.

[0050] In one example, the test log shows that at 12:10, test station 192.168.1.1 communicated with the dispatch automation system's front-end dispatch data network via the remote control unit (RTU) at 192.168.1.1. The script executes every minute. If a RTU switchover occurs at 12:10:30, the log entry for 12:11, when the script runs, will show: 12:11, test station 192.168.1.2. By comparing this with the previous minute's log, we can see that the RTU switchover occurred between 12:10 and 12:11. Simultaneously, the RTU IP configuration table is used to match the IP address with the RTU, determining whether it was RTU A or RTU B. This allows for effective identification of the RTU that sent the erroneous signal and the switchover time when a large number of false signals are triggered by RTU switching. The switchover time can also help determine which information actually represents historical events, improving information accuracy.

[0051] In one specific embodiment, before step two, the method further includes:

[0052] The test logs are compressed, and the compressed test logs are sent to the web server in the third security zone through forward isolation.

[0053] Understandably, since the scheduling automation system is located in Security Zone 1, in order not to add computing tasks to the scheduling automation system in Zone 1, the test logs can be compressed and then sent to the web server in Security Zone 3 through forward isolation for subsequent machine switching analysis.

[0054] The test logs can be compressed using the gzip compression tool.

[0055] It should be noted that this invention executes a script to cyclically test the IP addresses of remote actuators (RAAs) connected to the front-end machine of the scheduling automation system according to a preset test frequency. This generates test results containing IP addresses and their corresponding test times, which are accumulated in the test log. The IP addresses of the RAAs connected to the front-end machine of the scheduling automation system at each test time in the test log are matched with a preset RAA IP configuration table to determine the RAAs connected to the front-end machine of the scheduling automation system at each test time and the RAA switchover time. By recording the RAA IP addresses connected to the front-end machine each time the script runs in the log, the real-time corresponding RAAs and the RAA switchover time can be determined. When a large number of false signals are triggered due to RAA switchover, the RAAs that sent the false signals and the switchover time can be effectively located.

[0056] The above is a detailed description of an embodiment of a remote-controlled motor (RTM) switching identification method provided by the present invention. The following is a detailed description of an embodiment of an RTM switching identification system provided by the present invention.

[0057] The present invention provides a station remote motor switching identification system, which uses two remote motors and a front-end machine of a dispatch automation system. The two remote motors are each configured with a unique IP address. The front-end machine of the dispatch automation system initiates a communication connection with only one of the remote motors with a unique IP address at any given time.

[0058] For easier understanding, please refer to Figure 2 This system includes:

[0059] The script execution module 100 is used to respond to the pre-input IP test request, execute the script to perform cyclic testing on the IP address of the remote machine connected to the front-end machine of the scheduling automation system according to the preset test frequency, generate test results containing the IP address and its corresponding test time, and accumulate them in the test log.

[0060] The machine switching identification module 200 is used to match the IP addresses of the remote machines that the front-end machine of the scheduling automation system communicates with at each test moment in the test log with the preset remote machine IP configuration table, so as to determine the remote machines that the front-end machine of the scheduling automation system communicates with at each test moment and the machine switching time of the remote machines.

[0061] In one specific embodiment, the system further includes:

[0062] The IP configuration module is used to obtain two remote motors and their respective configured IP addresses, forming a remote motor IP configuration table. The remote motor IP configuration table contains the mapping relationship between remote motors and IP addresses.

[0063] In one specific embodiment, the script execution module is specifically used to respond to a pre-inputted IP test request, and to perform cyclic testing on the IP addresses of the remote machines connected to the front-end machine of the scheduling automation system by calling the netstat command of the Linux system according to a preset test frequency.

[0064] In one specific embodiment, the system further includes:

[0065] The compression module is used to compress test logs and then send the compressed test logs to the web server in the third security zone through forward isolation.

[0066] The present invention also provides an electronic device, comprising:

[0067] processor;

[0068] Memory used to store processor-executable instructions;

[0069] The processor is configured to execute instructions to implement the method described above.

[0070] The present invention also provides a storage medium that, when the instructions in the storage medium are executed by the processor of an electronic device, causes the electronic device to perform the method described above.

[0071] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, electronic devices, and storage media described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0072] In the embodiments provided by this invention, it should be understood that the disclosed systems, electronic devices, storage media, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0073] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0074] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0075] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for executing all or part of the steps of the methods described in the various embodiments of the present invention through a computer device (which may be a personal computer, server, or network device, etc.). The aforementioned storage medium includes: USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, optical disks, and other media capable of storing program code.

[0076] The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for identifying remote motor switching within a station, comprising two remote motors and a front-end machine of a dispatch automation system, wherein the two remote motors are each configured with a unique IP address, and the front-end machine of the dispatch automation system initiates a communication connection with only one of the remote motors with a unique IP address at any given time. characterized in that This method includes the following steps: In response to the pre-entered IP test request, the script performs a cyclic test on the IP address of the remote machine connected to the front-end machine of the scheduling automation system according to the preset test frequency, and generates test results containing the IP address and its corresponding test time, which are then accumulated in the test log. The IP addresses of the remote motors that the front-end machine of the scheduling automation system communicates with at each test moment in the test log are matched with the preset remote motor IP configuration table to determine the remote motors that the front-end machine of the scheduling automation system communicates with at each test moment and the switching time of the remote motors.

2. The method of claim 1, wherein the method comprises: Also includes: Obtain the two remote motors and their respective configured IP addresses to form a remote motor IP configuration table, wherein the remote motor IP configuration table contains the mapping relationship between remote motors and IP addresses.

3. The method for identifying remote motor switching within a station according to claim 1, characterized in that, The steps of executing a script to cyclically test the IP addresses of remote machines connected to the front-end machine of the dispatch automation system in response to a pre-entered IP test request, according to a preset test frequency, specifically include: In response to a pre-entered IP test request, the system calls the netstat command of the Linux system to perform cyclic testing on the IP addresses of the remote machines connected to the front-end machine of the scheduling automation system, according to a preset test frequency.

4. The in-station remote motor switching identification method according to claim 1, characterized in that, Before the step of matching the IP addresses of the remote machines that the front-end machine of the scheduling automation system communicates with at each test moment in the test log with the preset remote machine IP configuration table to determine the remote machines that the front-end machine of the scheduling automation system communicates with at each test moment and the remote machine switching time, the method further includes: The test logs are compressed, and the compressed test logs are sent to the web server in the third security zone through forward isolation.

5. A station-based remote motor switching identification system, which uses two remote motors and a front-end machine of a dispatch automation system. The two remote motors are each configured with a unique IP address. The front-end machine of the dispatch automation system initiates a communication connection with only one of the remote motors with a unique IP address at any given time. Its features are, This system includes: The script execution module is used to respond to the pre-input IP test request, execute the script to perform cyclic testing on the IP address of the remote machine connected to the front-end machine of the scheduling automation system according to the preset test frequency, generate test results containing the IP address and its corresponding test time, and accumulate them in the test log. The machine switching identification module is used to match the IP addresses of the remote machines that the front-end machine of the scheduling automation system communicates with at each test moment in the test log with the preset remote machine IP configuration table, so as to determine the remote machines that the front-end machine of the scheduling automation system communicates with at each test moment and the machine switching time of the remote machines.

6. The in-station remote motor switching identification system according to claim 5, characterized in that, Also includes: The IP configuration module is used to obtain the two remote motors and their respective configured IP addresses to form a remote motor IP configuration table, wherein the remote motor IP configuration table contains the mapping relationship between remote motors and IP addresses.

7. The in-station remote motor switching identification system according to claim 5, characterized in that, The script execution module is specifically used to respond to pre-inputted IP test requests and, according to a preset test frequency, call the netstat command of the Linux system to perform cyclic testing on the IP addresses of the remote machines connected to the front-end machine of the scheduling automation system.

8. The in-station remote motor switching identification system according to claim 5, characterized in that, Also includes: The compression module is used to compress the test logs and send the compressed test logs to the secure zone 3 web server through forward isolation.

9. An electronic device, characterized in that, include: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the method as described in any one of claims 1 to 4.

10. A storage medium, characterized in that, When the instructions in the storage medium are executed by the processor of the electronic device, the electronic device performs the method as described in any one of claims 1 to 4.

Images