A method for real-time monitoring of substation automation operation and non-operation communication channels

By real-time detection of the network connection status of the main and backup remote devices of the substation automation system in real-time, the problem that the dispatching automation system cannot automatically detect non-operating channel faults is solved, real-time monitoring and alarm of the substation communication channel is realized, ensuring the system stable operation and continuous monitoring function.

CN114744750BActive Publication Date: 2024-12-03GUANGXI POWER GRID CO LTD FANGCHENGGANG POWER SUPPLY BUREAU
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202111480981.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-12-07
Publication Date
2024-12-03
Estimated Expiration
2041-12-07

AI Technical Summary

Technical Problem

The existing scheduling automation system cannot automatically detect faults in non-operating communication channels, resulting in the failure of the remote driving device on duty to switch to the backup channel, losing the monitoring function of the substation, causing serious consequences.

Method used

In the PCS90000 scheduling automation system, the network connection status of the transmission channel of the main and backup remote devices and the main station is detected in real time, and the results are feedbacked in the form of light signs and alarms to ensure that the duty officer can understand the network status in a timely manner.

Benefits of technology

Real-time monitoring of the substation's automated operation and non-operation communication channels is realized, ensuring that the on-duty officers can quickly understand the network conditions, avoid monitoring loss caused by channel failure, and improve the reliability and security of the system.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

The present invention discloses a method for real-time monitoring of substation automation operation and non-operation communication channels. The method is based on the PCS90000 dispatching automation system, and detects the network connection status of the transmission channels of all substation main and standby telecontrol devices and the main station in real time by sending messages or data packets, and feeds back the results in the form of light-emitting signs and alarms. The present invention is developed based on the dispatching automation system and meets network security requirements; the duty officer can quickly and easily understand the status of all substation network channels during the daily inspection process, and the work efficiency is high, safe and reliable.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The invention belongs to the technical field of substation monitoring, and in particular relates to a method for real-time monitoring of automatic operation and non-operation communication channels of a substation. Background Art

[0002] The transmission channels of the dispatching automation system are connected to the two telecontrol devices A and B of the plant station (which are the main and standby devices for each other). When one of the telecontrol devices fails, the system can automatically switch the channel to the non-faulty telecontrol device on duty. At present, the dispatching automation system cannot automatically detect the failure of the non-operating channel. Once the on-duty telecontrol device fails, the channel cannot be switched to the non-operating channel of the telecontrol standby device, which will cause the dispatcher to lose the monitoring function of the substation, and the consequences are disastrous. Summary of the invention

[0003] The purpose of the present invention is to provide a method for real-time monitoring of substation automation operation and non-operation communication channels in view of the deficiencies in the prior art.

[0004] In order to achieve the above object, the present invention adopts the following technical solutions:

[0005] A method for real-time monitoring of substation automation operation and non-operation communication channels is based on the PCS90000 dispatching automation system, which detects the network connection status of the transmission channels of all substation main and standby telecontrol devices and the main station in real time by sending messages or data packets, and feeds back the results in the form of light signs and alarms; including:

[0006] Step 1: Back up and upload the update program through the bastion host; specifically:

[0007] 11) Back up the / users / ems / sophic / deployment / bin / fe / fe_ping program of the specified four servers (check first if there is no program, then do not back it up);

[0008] 12) Upload the / users / ems / sophic / deployment / bin / fe / fe_ping program from the operation and maintenance bastion machine to the specified directory of the specified node through the antivirus automated USB disk;

[0009] This deployment process only involves the newly added fe_ping program, not other programs, and does not change the underlying programs of the entire system;

[0010] Step 2: Main and standby remote motor status monitoring logic and engineering configuration; including:

[0011] (21) Dual IP monitoring logic for main and backup remote motors:

[0012] 211) If the channel status is disconnected, it means that both IPs of the channel are disconnected, and there is no need to test the status of the dual IPs through the ping command;

[0013] 212) If the channel status is connected, it means that the IP address that the channel is establishing a connection with is in a connected state, and the other IP address is detected by means of a regular ping packet to see if it is connected;

[0014] Since the ping packet method will also consume network resources, the period of sending ping packets regularly for each channel should not be too short. Set a ping packet detection every 30 seconds. If each ping packet returns a correct response, it means that the IP address is connected. If it returns an error, ping three times in a row. If an error is returned each time, it is considered that the IP address is disconnected. At the same time, the connection and disconnection status of the two IP addresses of the channel are written into the corresponding variables of the database.

[0015] (22) Engineering configuration:

[0016] 221) fe_ping is an independent process, configured under the relevant front-end application, responsible for testing whether the IP address of the 104 channel standby remote motor is connected through ping;

[0017] Assume that all 104 channels under the front application fe need to monitor the status function of the standby remote motor;

[0018] 222) Start the sm_cfg tool and add the process fe_ping under the fe application. Its task name and network registration name are both fe_ping. If the front application name is changed to fe1, it needs to be configured as fe1_ping.

[0019] Configure the monitoring process fe_ping in the task type domain; this process needs to be running on both the duty node and the standby node;

[0020] Command line parameter -app fe (prefix application name)

[0021] -period 300 (the interval between each ping command is 5 minutes by default. The interval should not be too long to prevent frequent ping commands from affecting normal network communication)

[0022] -thread 10 (start the number of ping command groups, that is, after the process is started, all 104 channels are divided into 10 groups, and the 10 groups execute the ping command in parallel at the same time).

[0023] (23) Program updates for each node; including:

[0024] (231) Update fcgfe1:

[0025] 2311) Check the / users / ems / sophic / deployment / bin / fe / fe_ping program on the backup server (first check if there is no program and do not back it up);

[0026] 2312) Update the program / users / ems / sophic / deployment / bin / fe / fe_ping;

[0027] 2313) Restart the fe_ping process under the fe application; if the standby node stops, restart the fe_ping of the duty node;

[0028] 2314) Observe whether there is any abnormality in the fe_ping process of node fcgfe1; if there is an abnormality, check the log to find the cause. If it cannot be solved in a short time, stop the fe_ping process first;

[0029] (232) Update fcgfe2:

[0030] 2321) Check the / users / ems / sophic / deployment / bin / fe / fe_ping program on the backup server (first check if there is no program and do not back it up);

[0031] 2322) Update the program / users / ems / sophic / deployment / bin / fe / fe_ping;

[0032] 2323) Restart the fe_ping process under the fe application; if the standby node stops, restart the fe_ping of the duty node;

[0033] 2324) Observe whether the fe_ping process of node fcgfe2 has any abnormality;

[0034] (233) Update fcgtx1:

[0035] 2331) Check the / users / ems / sophic / deployment / bin / fe / fe_ping program on the backup server (first check if there is no program and do not back it up);

[0036] 2332) Update the program / users / ems / sophic / deployment / bin / fe / fe_ping;

[0037] 2333) Restart the fe_ping process under the fe application; if the standby node stops, restart the fe_ping of the duty node;

[0038] 2334) Observe whether the fe_ping process of node fcgtx1 has any abnormality;

[0039] (234) Update fcgtx2:

[0040] 2341) Check the / users / ems / sophic / deployment / bin / fe / fe_ping program on the backup server (first check if there is no program and do not back it up);

[0041] 2342) Update the program / users / ems / sophic / deployment / bin / fe / fe_ping;

[0042] 2343) Restart the fe_ping process under the fe application; if the standby node stops, restart the fe_ping of the duty node;

[0043] 2344) Observe whether the fe_ping process of node fcgtx2 has any abnormality;

[0044] (24) After completing the engineering configuration and program update, you can start debugging. At the beginning of debugging, you can choose a station as a pilot to ensure that the ping function of the plant station is effective and will not affect the normal channel operation, and then gradually release the ping function of other plant station channels;

[0045] (25) Debug settings: In the channel group object, the attribute member12 is set to true, and the backup remote motor ping function is enabled for all channels under the channel group.

[0046] The ping function is specifically:

[0047] isFaultStatus indicates the status of the primary IP; bBak2 indicates the status of the backup IP; when channel group member12 is set to true, the ping function takes effect;

[0048] If the channel is disconnected, do not perform the ping function test, and directly set acquNet = 0, indicating that both the primary and backup IPs are disconnected. Do not use ping to detect the remote motor status, and directly check the cause of the channel interruption.

[0049] If the channel is connected:

[0050] Check the canDuty bit of the channel. canDuty indicates whether it is on duty. If canDuty=1, it means that the channel and the remote machine are connected to the first IP address in the tcp_client plug-in. First, set isFaultStatus to true, and then check whether the second IP address is connected by ping. If it is connected, set bBak2 to true. If ping fails, set bBak2 to false.

[0051] If the channel canDuty = 0, it means that the channel and the remote machine are connected to the second IP address in the tcp_client plug-in. Therefore, bBak2 is set to true first, and then the first IP address is checked for connectivity through ping. If it is connected, isFaultStatus is set to true. If ping fails, isFaultStatus is set to false.

[0052] Ping (Packet Internet Groper) is an Internet packet explorer, a program used to test network connections. Ping is a service command that works at the application layer in the TCP / IP network architecture. It mainly sends ICMP (Internet Control Message Protocol) Echo request messages to a specific destination host to test whether the destination station is reachable and understand its status.

[0053] Advantages of the present invention:

[0054] 1. The present invention detects the network connection status of the transmission channels of all main and standby telecontrol devices of all substations and the master station in real time by sending messages or data packets, and feeds back the results in the form of light signs and alarms. The duty personnel can quickly and easily understand the status of the network channels of all substations during the daily inspection process.

[0055] 2. The present invention is developed based on the dispatching automation system and meets network security requirements. DETAILED DESCRIPTION

[0056] The present invention is further described below in conjunction with embodiments.

[0057] Example:

[0058] A method for real-time monitoring of substation automation operation and non-operation communication channels is based on the PCS90000 dispatching automation system, which detects the network connection status of the transmission channels of all substation main and standby telecontrol devices and the main station in real time by sending messages or data packets, and feeds back the results in the form of light signs and alarms; including:

[0059] Step 1: Back up and upload the update program through the bastion host; specifically:

[0060] 11) Back up the / users / ems / sophic / deployment / bin / fe / fe_ping program of the specified four servers;

[0061] 12) Upload the / users / ems / sophic / deployment / bin / fe / fe_ping program from the operation and maintenance bastion machine to the specified directory of the specified node through the antivirus automated USB disk;

[0062] This deployment process only involves the newly added fe_ping program, not other programs, and does not change the underlying programs of the entire system;

[0063] Step 2: Main and standby remote motor status monitoring logic and engineering configuration; including:

[0064] (21) Dual IP monitoring logic for main and backup remote motors:

[0065] 211) If the channel status is disconnected, it means that both IPs of the channel are disconnected, and there is no need to test the status of the dual IPs through the ping command;

[0066] 212) If the channel status is connected, it means that the IP address that the channel is establishing a connection with is in a connected state, and the other IP address is detected by means of a regular ping packet to see if it is connected;

[0067] Since the ping packet method will also consume network resources, the period of sending ping packets regularly for each channel should not be too short. Set a ping packet detection every 30 seconds. If each ping packet returns a correct response, it means that the IP address is connected. If it returns an error, ping three times in a row. If an error is returned each time, it is considered that the IP address is disconnected. At the same time, the connection and disconnection status of the two IP addresses of the channel are written into the corresponding variables of the database.

[0068] (22) Engineering configuration:

[0069] 221) fe_ping is an independent process, configured under the relevant front-end application, responsible for testing whether the IP address of the 104 channel standby remote motor is connected through ping;

[0070] Assume that all 104 channels under the front application fe need to monitor the status function of the standby remote motor;

[0071] 222) Start the sm_cfg tool and add the process fe_ping under the fe application. Its task name and network registration name are both fe_ping. If the front application name is changed to fe1, it needs to be configured as fe1_ping.

[0072] Configure the monitoring process fe_ping in the task type domain; this process needs to be running on both the duty node and the standby node;

[0073] Command line parameter -app fe (prefix application name)

[0074] -period 300 (the interval between each ping command is 5 minutes by default. The interval should not be too long to prevent frequent ping commands from affecting normal network communication)

[0075] -thread 10 (start the number of ping command groups, that is, after the process is started, all 104 channels are divided into 10 groups, and the 10 groups execute the ping command in parallel at the same time).

[0076] (23) Program updates for each node; including:

[0077] (231) Update fcgfe1:

[0078] 2311) Check the / users / ems / sophic / deployment / bin / fe / fe_ping program of the backup server;

[0079] 2312) Update the program / users / ems / sophic / deployment / bin / fe / fe_ping;

[0080] 2313) Restart the fe_ping process under the fe application; if the standby node stops, restart the fe_ping of the duty node;

[0081] 2314) Observe whether there is any abnormality in the fe_ping process of node fcgfe1; if there is an abnormality, check the log to find the cause. If it cannot be solved in a short time, stop the fe_ping process first;

[0082] (232) Update fcgfe2:

[0083] 2321) Check the / users / ems / sophic / deployment / bin / fe / fe_ping program of the backup server;

[0084] 2322) Update the program / users / ems / sophic / deployment / bin / fe / fe_ping;

[0085] 2323) Restart the fe_ping process under the fe application; if the standby node stops, restart the fe_ping of the duty node;

[0086] 2324) Observe whether the fe_ping process of node fcgfe2 has any abnormality;

[0087] (233) Update fcgtx1:

[0088] 2331) Check the / users / ems / sophic / deployment / bin / fe / fe_ping program of the backup server;

[0089] 2332) Update the program / users / ems / sophic / deployment / bin / fe / fe_ping;

[0090] 2333) Restart the fe_ping process under the fe application; if the standby node stops, restart the fe_ping of the duty node;

[0091] 2334) Observe whether the fe_ping process of node fcgtx1 has any abnormality;

[0092] (234) Update fcgtx2:

[0093] 2341) Check the / users / ems / sophic / deployment / bin / fe / fe_ping program of the backup server;

[0094] 2342) Update the program / users / ems / sophic / deployment / bin / fe / fe_ping;

[0095] 2343) Restart the fe_ping process under the fe application; if the standby node stops, restart the fe_ping of the duty node;

[0096] 2344) Observe whether the fe_ping process of node fcgtx2 has any abnormality;

[0097] (24) After completing the engineering configuration and program update, you can start debugging. At the beginning of debugging, you can choose a station as a pilot to ensure that the ping function of the plant station is effective and will not affect the normal channel operation, and then gradually release the ping function of other plant station channels;

[0098] (25) Debug settings: In the channel group object, the attribute member12 is set to true, and the backup remote motor ping function is enabled for all channels under the channel group.

[0099] The ping function is specifically:

[0100] isFaultStatus indicates the status of the primary IP; bBak2 indicates the status of the backup IP; when channel group member12 is set to true, the ping function takes effect;

[0101] If the channel is disconnected, do not perform the ping function test, and directly set acquNet = 0, indicating that both the primary and backup IPs are disconnected. Do not use ping to detect the remote motor status, and directly check the cause of the channel interruption.

[0102] If the channel is connected:

[0103] Check the canDuty bit of the channel. canDuty indicates whether it is on duty. If canDuty=1, it means that the channel and the remote machine are connected to the first IP address in the tcp_client plug-in. First, set isFaultStatus to true, and then check whether the second IP address is connected by ping. If it is connected, set bBak2 to true. If ping fails, set bBak2 to false.

[0104] If the channel canDuty = 0, it means that the channel and the remote machine are connected to the second IP address in the tcp_client plug-in. Therefore, bBak2 is set to true first, and then the first IP address is checked for connectivity through ping. If it is connected, isFaultStatus is set to true. If ping fails, isFaultStatus is set to false.

[0105] Obviously, the above embodiments are only examples for clearly explaining the present invention, and are not intended to limit the implementation of the present invention. For ordinary technicians in the relevant technical field, other different forms of changes or modifications can be made based on the above description; it is not necessary and impossible to list all the implementation methods here; and the obvious changes or modifications derived from them are still within the protection scope of the present invention.

Claims

1. A method for real-time monitoring of substation automation operation and non-operation communication channels, based on the PCS90000 dispatching automation system, detects the network connection status of the transmission channels of all substation master and backup telecontrol devices and the master station in real time by sending messages or data packets, and feeds back the results in the form of light signs and alarms; it is characterized by include: Step 1: Back up and upload the update program through the bastion host; Specifically: 11) Back up the / users / ems / sophic / deployment / bin / fe / fe_ping program of the specified four servers; 12) Upload the / users / ems / sophic / deployment / bin / fe / fe_ping program from the operation and maintenance bastion machine to the specified directory of the specified node through the antivirus automated USB disk; This deployment process only involves the newly added fe_ping program, not other programs, and does not change the underlying programs of the entire system; Step 2: Main and standby remote motor status monitoring logic and engineering configuration; including: (21) Dual IP monitoring logic for main and backup remote motors: 211) If the channel status is disconnected, it means that both IPs of the channel are disconnected, and there is no need to test the status of the dual IPs through the ping command; 212) If the channel status is connected, it means that the IP address that the channel is establishing a connection with is in a connected state, and the other IP address is detected by means of a regular ping packet to see if it is connected; Since the ping packet method will also consume network resources, the period of sending ping packets regularly for each channel should not be too short. Set a ping packet detection every 30 seconds. If each ping packet returns a correct response, it means that the IP address is connected. If it returns an error, ping three times in a row. If an error is returned each time, it is considered that the IP address is disconnected. At the same time, the connection and disconnection status of the two IP addresses of the channel are written into the corresponding variables of the database. (22) Engineering configuration: 221) fe_ping is an independent process, configured under the relevant front-end application, responsible for testing whether the IP address of the 104 channel standby remote motor is connected through ping; Assume that all 104 channels under the front application fe need to monitor the status function of the standby remote motor; 222) Start the sm_cfg tool and add the process fe_ping under the fe application. Its task name and network registration name are both fe_ping. If the front application name is changed to fe1, it needs to be configured as fe1_ping. Configure the monitoring process fe_ping in the task type domain; this process needs to be running on both the duty node and the standby node; (23) Program updates for each node; including: (231) Update the fe_ping process of node fcgfe1; (232) Update the fe_ping process of node fcgfe2; (233) Update the fe_ping process of node fcgtx1; (234) Update the fe_ping process of node fcgtx2; (24) After completing the engineering configuration and program update, start debugging. At the beginning of debugging, select a plant station as a pilot to ensure that the ping function of the plant station is effective and will not affect the normal channel operation, and then gradually release the ping function of other plant station channels; (25) Debug settings: In the channel group object, the attribute member12 is set to true, and the backup remote motor ping function is enabled for all channels under the channel group.

2. The method for real-time monitoring of substation automation operation and non-operation communication channels according to claim 1 is characterized in that: The ping function is specifically: isFaultStatus indicates the status of the primary IP; bBak2 indicates the status of the backup IP; when channel group member12 is set to true, the ping function takes effect; If the channel is disconnected, do not perform the ping function test, and directly set acquNet = 0, indicating that both the primary and backup IPs are disconnected. Do not use ping to detect the remote motor status, and directly check the cause of the channel interruption. If the channel is connected: Check the canDuty bit of the channel. canDuty indicates whether it is on duty. If canDuty=1, it means that the channel and the remote machine are connected to the first IP address in the tcp_client plug-in. First, set isFaultStatus to true, and then check whether the second IP address is connected by ping. If it is connected, set bBak2 to true. If ping fails, set bBak2 to false. If the channel canDuty = 0, it means that the channel and the remote machine are connected to the second IP address in the tcp_client plug-in. Therefore, bBak2 is set to true first, and then the first IP address is checked for connectivity through ping. If it is connected, isFaultStatus is set to true. If ping fails, isFaultStatus is set to false.

3. The method for real-time monitoring of substation automation operation and non-operation communication channels according to claim 1 is characterized in that: The step (231) updates the fe_ping process of the node fcgfe1, specifically: 2311) Check the / users / ems / sophic / deployment / bin / fe / fe_ping program of the backup server; 2312) Update the program / users / ems / sophic / deployment / bin / fe / fe_ping; 2313) Restart the fe_ping process under the fe application; if the standby node stops, restart the fe_ping of the duty node; 2314) Observe whether there are any abnormalities in the fe_ping process of node fcgfe1; if there are any abnormalities, check the log to find the cause. If the cause cannot be resolved in a short time, stop the fe_ping process first.

4. The method for real-time monitoring of substation automation operation and non-operation communication channels according to claim 1 is characterized in that: The step (232) updates the fe_ping process of the node fcgfe2, specifically: 2321) Check the / users / ems / sophic / deployment / bin / fe / fe_ping program of the backup server; 2322) Update the program / users / ems / sophic / deployment / bin / fe / fe_ping; 2323) Restart the fe_ping process under the fe application; if the standby node stops, restart the fe_ping of the duty node; 2324) Observe whether there are any abnormalities in the fe_ping process of node fcgfe2.

5. The method for real-time monitoring of substation automation operation and non-operation communication channels according to claim 1 is characterized in that: The step (233) updates the fe_ping process of the node fcgtx1, specifically: 2331) Check the / users / ems / sophic / deployment / bin / fe / fe_ping program of the backup server; 2332) Update the program / users / ems / sophic / deployment / bin / fe / fe_ping; 2333) Restart the fe_ping process under the fe application; if the standby node stops, restart the fe_ping of the duty node; 2334) Observe whether there are any abnormalities in the fe_ping process of node fcgtx1.

6. The method for real-time monitoring of substation automation operation and non-operation communication channels according to claim 1 is characterized in that: The step (234) updates the fe_ping process of the node fcgtx2, specifically: 2341) Check the / users / ems / sophic / deployment / bin / fe / fe_ping program of the backup server; 2342) Update the program / users / ems / sophic / deployment / bin / fe / fe_ping; 2343) Restart the fe_ping process under the fe application; if the standby node stops, restart the fe_ping of the duty node; 2344) Observe whether there are any abnormalities in the fe_ping process of node fcgtx2.