Substation one-key sequential control synchronous debugging method based on autonomous controllable CMS protocol

Abstract

The invention discloses a transformer substation one-key sequential control synchronous debugging method based on an autonomous controllable CMS protocol, and the method comprises the steps: configuring a CMS client which comprises a PER coding and decoding module based on an ASN.1 standard, and building communication with spacer layer equipment; analyzing the audited sequence control ticket, verifying the compliance through a rule engine, and if the compliance is not passed, marking an error and giving a suggestion; the edge computing host generates a synchronous debugging instruction in combination with the real-time remote signaling / telemetering data, and issues the synchronous debugging instruction through a LoRaWAN protocol; deploying a sensor to collect the state of target equipment, and giving an alarm in real time when abnormity occurs; and if the debugging accuracy is lower than a preset threshold value, analyzing the deviation and iteratively optimizing the model. The method is compatible with CMS and MMS protocols, and different substations can be adapted without the support of manufacturers; the problems of traditional debugging power failure, flow interference and the like are solved, multi-device synchronous debugging and fault self-repairing are achieved, and the intelligent operation and maintenance requirements of a transformer substation are met.

Description

Technical Field

[0001] This invention relates to the field of intelligent commissioning technology for substations, and in particular to a one-click sequential synchronous commissioning method and system for substations based on an autonomous and controllable CMS protocol. Background Technology

[0002] In the process of building intelligent substations, one-click sequential control, as a core technology for improving operation and maintenance efficiency and reducing the risk of misoperation, still faces significant bottlenecks in its commissioning phase. Currently, the commissioning of newly built intelligent substations mainly relies on simulated MMS clients to receive action information from primary equipment (referring to high-voltage equipment directly involved in power generation, transmission, distribution, and consumption, such as circuit breakers, disconnectors, and transformers). However, the IEC61850 protocol communication configuration is complex, making it difficult for operation and maintenance personnel to fully master. In the early stages of commissioning, a large amount of technical support from the manufacturer is required, resulting in low equipment operability. At the same time, with the advancement of the construction of domestically produced new-generation substations, the initial one-click sequential control technology only covers MMS communication substations and does not involve scenarios with independently controllable CMS communication protocols, failing to meet the commissioning needs of different types of substations. Grassroots operation and maintenance personnel urgently need a commissioning solution that covers all types of substations and offers high operability.

[0003] Traditional one-button sequential control commissioning has several problems: First, sequential control acceptance must be carried out under power outage conditions, and safety measures must be implemented by disabling remote control pressure plates for other operating bay switches and disconnectors, making the operation cumbersome and affecting the reliability of the power grid. Second, the on-site acceptance environment is complex, and remote control acceptance of other bays can easily interfere with the sequential control operation process. Alarm signals from link and protection device acceptance can cause sequential control operations to fail to meet the conditions, delaying the commissioning progress. Third, the sequential control operation ticket has many operating conditions and target status checks, and errors in remote signal correlation are prone to occur when the manufacturer creates it, resulting in long error correction times. Fourth, the equipment status required for sequential control operations conflicts with the equipment status of protection team acceptance and signal verification work, making it impossible to carry out in parallel, further reducing commissioning efficiency. In addition, existing commissioning technology lacks an effective synchronization mechanism, resulting in large deviations in actions when multiple devices are commissioned together, and the impact of environmental factors such as temperature and electromagnetic interference on commissioning accuracy is not considered, making it difficult to control commissioning errors.

[0004] From an industrial application perspective, current one-click sequential control commissioning technology still has significant shortcomings: On the one hand, the commissioning process relies on manual intervention. From sequential control ticket verification and commissioning command issuance to status acquisition, all operations require manual intervention, which is not only inefficient but also prone to commissioning failure due to human error. On the other hand, there is a lack of a unified commissioning host and data traceability mechanism. Commissioning data is stored in a scattered manner, making it impossible to achieve full-process visual monitoring and subsequent data analysis, which is not conducive to problem troubleshooting and technology iteration. At the same time, existing technologies do not incorporate functions such as energy consumption optimization and fault self-repair. Energy waste is serious during commissioning, and manual on-site handling is required after a fault occurs, prolonging the commissioning cycle and making it difficult to adapt to the operation and maintenance mode of unattended substations. There is an urgent need for a one-click sequential control synchronous commissioning solution based on an independently controllable CMS protocol, covering the entire process and highly intelligent, to solve the above-mentioned technical pain points and promote the large-scale application of one-click sequential control technology in substations. Summary of the Invention

[0005] The present invention proposes a one-click sequential control synchronous commissioning method and system for substations based on an autonomous and controllable CMS protocol, which can realize high-precision autonomous and controllable synchronous commissioning of multiple devices.

[0006] To achieve the above objectives, the present invention adopts the following technical solution:

[0007] Firstly, this application provides a one-click sequential control synchronous commissioning method for substations based on an independently controllable CMS protocol, implemented using a commissioning host, an edge computing host, and bay layer devices; the commissioning host is communicatively connected to the edge computing host; the edge computing host is equipped with a CMS client, and the bay layer devices are equipped with a CMS server, with the CMS client and the CMS server communicatively connected; both the CMS client and the CMS server integrate a PER codec module based on the ASN.1 standard; the method includes:

[0008] Sequential control ticket parsing and compliance verification steps: The debugging host obtains and parses the sequential control ticket, and verifies the parsing result; if the verification fails, the error location is marked and a correction suggestion is generated, and the verification log can be exported for review by operation and maintenance personnel. The sequential control ticket can be manually corrected later; the parsing result of the verified sequential control ticket is sent to the edge computing host.

[0009] Multi-device synchronous debugging instruction generation and distribution steps: The edge computing host collects remote signaling / telemetry data from each connected interval layer device, and generates synchronous debugging instructions by combining the parsing results of the verified sequential control tickets; the CMS client encodes the synchronous debugging instructions into debugging instruction CMS messages through the PER encoding and decoding module, and synchronously distributes the debugging instruction CMS messages to the CMS servers on multiple interval layer devices;

[0010] Debugging instruction receiving, decoding and execution steps: The CMS server on the interval layer device receives the debugging instruction CMS message, decodes it through the PER encoding and decoding module, and drives the controlled primary device to perform corresponding operations according to the decoded debugging instruction;

[0011] Real-time acquisition and feedback of debugging status steps: The CMS server on the interval layer device generates a response CMS message containing the device response status, which is encoded by the PER encoding and decoding module and sent back to the edge computing host; the sensor array deployed next to the primary device collects the execution status of the primary device at the first preset time period (e.g., 200ms) and transmits it to the edge computing host; the CMS client on the edge computing host decodes the collected data through the PER encoding and decoding module; the edge computing host uploads the decoded data to the debugging host; the debugging host receives the data uploaded by the edge computing host, determines whether there is an execution timeout or status abnormality, and if so, issues an alarm (e.g., through audible and visual alarms, alarm information generated by SMS push).

[0012] In this application, the PER codec module based on the ASN.1 standard is developed based on the mapping relationship between IEC61850 objects and CMS data structures, realizing independent and controllable CMS protocol configuration and communication adaptation.

[0013] In one possible implementation, the CMS client establishes a TCP / IP connection with the CMS server via Ethernet.

[0014] In one possible implementation, obtaining the sequential control ticket includes: obtaining a sequential control ticket that has undergone three levels of review from the substation operation and maintenance management platform.

[0015] In one possible implementation, parsing and verifying the sequential control ticket includes: parsing and verifying the sequential control ticket using a rule engine developed in Python.

[0016] In one possible implementation, generating synchronous debugging instructions includes: generating synchronous debugging instructions in the format of "target device ID-operation type-parameter value-execution time limit".

[0017] In one possible implementation, debugging command CMS messages are synchronously sent to CMS servers on multiple interval layer devices, including: synchronously sending debugging command CMS messages to CMS servers on multiple interval layer devices via the LoRaWAN protocol; and using time division multiplexing technology to divide the communication time slots of multiple interval layer devices.

[0018] In one possible implementation, the edge computing host is equipped with an ARM Cortex-A9 dual-core processor and 2GB DDR3 memory.

[0019] In one possible implementation, the edge computing host collects telemetry / telecommunication data from each connected interval layer device via an RS485 bus.

[0020] In one possible implementation, the sensor array includes current, voltage, and position sensors.

[0021] In one possible implementation, the sensor array connects to the CMS client via the Modbus-RTU protocol.

[0022] In one possible implementation, the edge computing host uploads the decoded data to the debugging host via Ethernet.

[0023] The debugging host is the hardware entity that carries the debugging platform.

[0024] The debugging host and the edge computing host have a hierarchical management relationship and support bidirectional data interaction (data upload + policy distribution).

[0025] The debugging host and the interval layer devices can interact indirectly through the edge computing host without a direct physical connection, forming an indirect control relationship (data is relayed through the edge computing host, and policies are implemented through the edge computing host).

[0026] In one possible implementation, the method further includes: debugging accuracy optimization and model iteration steps: after each debugging, the execution accuracy of the device is calculated once; if the execution accuracy is less than a preset accuracy threshold (such as 95%), the cause of the deviation is analyzed and classified statistically by the debugging host; the deviation data is accumulated, and the gradient descent algorithm is used to fine-tune the synchronous debugging model.

[0027] In one possible implementation, the execution accuracy of the primary device = (number of correctly executed steps / total number of steps) × 100%.

[0028] In one possible implementation, the method further includes: if there are multiple debugging tasks, then each is configured using a different formula. Calculate the priority of each debugging task, where Prioritize debugging tasks. The correlation weight between the control ticket corresponding to the commissioning task and the current power grid operating conditions. The correlation coefficient is... Weighting of wait time for debugging tasks. Waiting time for debugging tasks, The importance weight of the primary equipment corresponding to the debugging task. The importance coefficient of the primary equipment corresponding to the commissioning task;

[0029] The scheduling uses a priority queue algorithm, where high-priority debugging tasks are given priority to enter the execution queue.

[0030] In one possible implementation, the method further includes: using a formula Calculate the debugging error after dynamic correction, where This is the dynamically corrected debugging error. To account for actual debugging errors, Temperature affects weighting. To adjust the amount of change in ambient temperature, The weighting is affected by electromagnetic noise. Electromagnetic noise intensity;

[0031] when When the error exceeds the preset error threshold (e.g., 3), the debugging host automatically adjusts the debugging command parameters: if the error is due to excessively high temperature, i.e. If the error is caused by a temperature change exceeding the preset threshold (e.g., 20℃), the execution time limit of the spacer layer equipment will be extended; if the error is caused by excessive electromagnetic noise, i.e., N is greater than the first preset intensity threshold (e.g., 8V / m), the verification intensity of the debugging command will be increased.

[0032] In one possible implementation, the development steps of the independently controllable CMS client also include a communication fault tolerance mechanism: After the CMS client sends a request CMS message, it starts a software timeout timer. If no response is received from the CMS server within the timeout period, a retransmission mechanism is automatically triggered. The number of retransmissions is less than or equal to a preset number K (e.g., 3 times), and the retransmission interval adopts an exponential backoff algorithm. If all K retransmissions fail, the CMS client automatically reads the locally configured list of backup CMS servers, detects the online status of the backup CMS servers through the ICMP protocol, selects the backup CMS server with the least latency to establish a new connection, and the switching time is less than or equal to a preset time threshold (e.g., 200ms). At the same time, the CMS client records communication failure information to the local log. Every time a first preset number of failure data entries (e.g., 50 entries) are accumulated, the communication link selection model is updated using a decision tree algorithm.

[0033] In one possible implementation, fault statistics reports can be exported by debugging the host.

[0034] In one possible implementation, the multi-device synchronous commissioning step also includes multi-bay collaborative commissioning: for multiple (e.g., 3-5) adjacent bays within the substation, one Beidou dual-mode timing module is deployed in each bay, and time synchronization of each bay is achieved through the PTP protocol; before the commissioning command is issued, the edge computing host reads the bay association matrix, adds the bay collaborative identifier to the commissioning command, and calculates the bay order according to the logic defined in the association matrix; when the commissioning command is issued, the edge computing host schedules uniformly according to the collaborative logic: first, the first bay commissioning command is issued, and after receiving feedback that the first bay has completed execution, the second bay commissioning command is issued after a first preset time delay (e.g., 200ms), and so on.

[0035] In one possible implementation, after collaborative debugging is completed, the edge computing host generates an interval collaborative report, which can be pushed to the debugging host via the MQTT protocol.

[0036] In one possible implementation, the real-time acquisition and feedback of debugging status also includes adaptive adjustment of environmental parameters: multi-parameter environmental sensors are deployed in the debugging area, and the multi-parameter environmental sensors collect data and upload it to the debugging host according to a second preset time period (e.g., 500ms); the debugging host triggers an adaptive strategy based on the environmental parameters: when the temperature is greater than a preset temperature threshold (e.g., 40℃), the CPU frequency of the debugging host is automatically reduced, and the cooling fan of the debugging host is started at the same time; when the humidity is greater than a preset humidity threshold (e.g., 85%RH), the moisture-proof heating pad of the sensor is activated; when the electromagnetic noise is greater than a second preset intensity threshold (e.g., 10V / m), the CMS message verification strength is increased, and the CMS message transmission rate is reduced at the same time.

[0037] One possible implementation also includes a self-healing step for debugging faults: The debugging host is equipped with a fault diagnosis model to monitor the fault type of the target device in real time. For communication faults, the debugging host automatically restarts the CMS client communication module. If restarting is ineffective, it switches to a backup communication link. For execution faults, it first sends a target device status reset command through the CMS client. After resetting, it waits for a second preset time (e.g., 500ms) to re-execute the original debugging command. If it still fails, it generates a manual intervention prompt. For parameter faults, the debugging host automatically reads the target device's rated parameter library, reconfigures the control parameters according to a preset proportion of the rated values ​​(e.g., 90%), and marks the parameter correction record. After each fault repair, the repair process is recorded in the fault repair knowledge base. For every second preset number of fault records added (e.g., 100), the fault diagnosis model is updated using a random forest algorithm.

[0038] The target equipment includes spacer layer equipment and primary equipment.

[0039] The device hierarchy for one-click sequential control is "edge computing host (CMS client) → interval layer device (CMS server) → primary device". The fault self-repair covers "communication link (interval layer device) + execution terminal (primary device)" to achieve full-link, full-scenario fault coverage, including execution abnormalities of primary devices (such as reset requirements caused by mechanical jamming), parameter mismatch (incorrect rated parameters of primary devices), and communication interruption between interval layer devices and edge computing hosts (such as CMS server going offline).

[0040] One possible implementation also includes a step for optimizing energy consumption through a formula. Calculate the total energy consumption for debugging, of which To adjust the total energy consumption, The number of devices involved in the commissioning process. For the first The operating power of the primary equipment Let i be the running time of the i-th primary device. To debug the host's standby power, T is the total debugging time, according to The operation sequence of the primary equipment is adjusted based on the comparison result with the preset threshold: when When the threshold is ≤, execute according to the original timing sequence; when When the threshold is reached, optimize the startup time of non-critical primary equipment and reduce the simultaneous running time of primary equipment.

[0041] In one possible implementation, the method further includes: a visual interactive step for the debugging process: a web visualization interface is developed using the Vue.js framework, which is divided into three main modules: a debugging progress module, a target device status module, and a debugging instruction record module; manual intervention by maintenance personnel is supported, and all intervention instructions take effect after secondary permission verification; after debugging is completed, the system automatically generates a PDF format debugging report, which supports online preview, download, and printing, and is also pushed to the substation operation and maintenance management platform via the MQTT protocol and included in the target device operation and maintenance file.

[0042] In one possible implementation, the method further includes a dynamic compliance verification step: constructing a compliance verification library and defining the compliance indicators for each primary device, including: the main transformer's commissioning voltage deviation is within a preset voltage deviation range (e.g., within ±2%), the switch action time is less than or equal to a third preset time (e.g., 500ms), the disconnector action position deviation is less than or equal to a preset position deviation (e.g., 10mm), and the protection device alarm response time is less than or equal to a fourth preset time (e.g., 1s); during commissioning, the commissioning host compares the primary device execution data with the compliance indicators at a third preset time period (e.g., 100ms), and uses the difference calculation method to determine whether the standard is exceeded; when the data exceeds the indicator range, a compliance alarm window immediately pops up on the visualization interface; after commissioning, the compliance rate is calculated: compliance rate = (number of compliance indicators / total number of indicators) × 100%; if the compliance rate is greater than or equal to a preset compliance rate threshold (e.g., 95%), the commissioning is deemed qualified; otherwise, a rectification list is generated, and secondary verification is supported after rectification.

[0043] Secondly, this application provides a substation one-click sequential control synchronous commissioning system based on an independently controllable CMS protocol, including a commissioning host, an edge computing host, and a bay layer device; the commissioning host is communicatively connected to the edge computing host; the edge computing host is equipped with a CMS client, and the bay layer device is equipped with a CMS server, and the CMS client and the CMS server are communicatively connected; both the CMS client and the CMS server integrate a PER codec module based on the ASN.1 standard;

[0044] The system uses the above method to achieve one-click sequential control and synchronous commissioning of substations.

[0045] Compared with existing technologies, the beneficial effects of this invention are:

[0046] In terms of technical adaptability, this invention develops an independently controllable CMS client, which realizes accurate mapping between IEC61850 objects and CMS data structures, is compatible with both MMS and CMS protocol substations, solves the problem that traditional technologies only cover a single protocol, and can complete the commissioning of different types of substations without relying on manufacturer technical support, greatly improving equipment operability and solution versatility, and meeting the construction needs of the new generation of domestic substations.

[0047] In terms of debugging efficiency and reliability, this invention avoids the tediousness and errors of manual verification by automatically parsing and verifying sequential control tickets. At the same time, it realizes synchronous debugging of multiple devices and multi-interval collaboration, solving problems such as power outage operation, process interference, and state conflict in traditional debugging. Debugging can be carried out without power outages, supports parallel operation, and significantly shortens the debugging cycle. The fault self-healing mechanism and communication fault tolerance design can automatically deal with problems such as communication interruption and abnormal equipment execution, reduce the frequency of manual intervention, improve the stability and continuity of the debugging process, ensure the efficient progress of debugging tasks, and avoid schedule delays caused by faults.

[0048] In terms of accuracy and compliance, this invention introduces adaptive adjustment of environmental parameters and dynamic correction of debugging errors, effectively offsetting the impact of environmental factors such as temperature and electromagnetic interference on debugging accuracy, and ensuring that equipment operation deviations are controlled within a reasonable range. Dynamic verification of debugging compliance compares in real time with industry standards and specifications, automatically generating a rectification list to avoid the risk of debugging results not meeting safety standards. Visual interaction and data traceability functions enable transparent monitoring of the entire debugging process, facilitating subsequent problem investigation and data archiving. At the same time, energy-efficient design reduces energy consumption during the debugging process, balancing technical practicality and economy, providing strong support for the safe and stable operation of substations, and promoting the widespread application of one-click sequential control technology in power grid operation and maintenance. Attached Figure Description

[0049] Figure 1 This is a schematic block diagram of a substation one-click sequential control synchronous commissioning method based on an autonomous and controllable CMS protocol according to an embodiment of this application;

[0050] Figure 2 This is a bar chart comparing the one-click sequential control commissioning efficiency of substations with different protocols in the embodiments of this application;

[0051] Figure 3 This is a comparison chart of the transmission delay test accuracy of the longitudinal protection dual-channel in the embodiments of this application;

[0052] Figure 4 This is a comparison chart of the time delay stability of the longitudinal protection channel under different environments in the embodiments of this application. Detailed Implementation

[0053] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. 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.

[0054] In the description of this invention, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, features defined as "first" or "second" may explicitly or implicitly include one or more of the stated features. In the description of this invention, "a plurality of" means two or more, unless otherwise explicitly specified. Furthermore, the terms "installed," "connected," and "linked" should be interpreted broadly; for example, they may refer to a fixed connection, a detachable connection, or an integral connection; they may refer to a mechanical connection or an electrical connection; they may refer to a direct connection or an indirect connection through an intermediate medium; and they may refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0055] To better understand the technical solution of this application, the English abbreviations and terms involved in this application will be explained below.

[0056] 1.CMS

[0057] The full English name is Common Message Specification. CMS is a protocol for substation communication, based on the ASN.1 encoding rules. It supports autonomous and controllable communication needs, enabling data exchange and status monitoring between bay-level devices.

[0058] 2.ASN.1

[0059] Full English name: Abstract Syntax Notation One. ASN.1 is an international standard for data representation, used to describe data structures and encoding rules. It is commonly used in communication protocols and supports efficient data serialization and deserialization.

[0060] 3.PER

[0061] The full English name is Packed Encoding Rules. PER is an encoding rule of ASN.1 that reduces the size of CMS messages and improves communication efficiency by optimizing the data encoding structure, making it particularly suitable for bandwidth-constrained environments.

[0062] 4. IEC61850

[0063] The full English name is International Electrotechnical Commission 61850, which is an international standard for substation automation systems. It defines the bay-level equipment model, communication services, and configuration procedures, supporting interoperability and intelligent operation and maintenance.

[0064] 5. TCP / IP

[0065] TCP / IP stands for Transmission Control Protocol / Internet Protocol. It is a fundamental suite of communication protocols for the Internet, providing reliable data transmission services and enabling stable connections between CMS clients and interval layer devices.

[0066] 6. LoRaWAN

[0067] LoRaWAN stands for Long Range Wide Area Network. It is a low-power, long-range wireless communication technology suitable for issuing commissioning commands to substation bay-level equipment and supports time-division multiplexing communication among multiple devices.

[0068] 7. RS485

[0069] The full English name is Recommended Standard 485. RS485 is a serial communication bus standard that supports multi-point communication and long-distance transmission. It can be used by edge computing hosts to acquire telemetry / telecommunication data from interval layer devices.

[0070] 8. Modbus-RTU

[0071] The full English name is Modbus Remote Terminal Unit. Modbus-RTU is a serial communication protocol used for data acquisition between sensors and CMS clients, supporting binary encoding and efficient data transmission.

[0072] 9. ICMP

[0073] The full English name is Internet Control Message Protocol (ICMP). ICMP is a protocol used to detect the reachability of network inter-layer devices and communication latency. In the fault tolerance mechanism of a CMS client, it is used for online status detection of the backup CMS server.

[0074] 10.PTP

[0075] The full English name is Precision Time Protocol, which is a high-precision time synchronization protocol (IEEE 1588 standard) used for time synchronization in multi-interval collaborative debugging to reduce the deviation of equipment actions.

[0076] 11. MQTT

[0077] MQTT stands for Message Queuing Telemetry Transport. It's a lightweight publish-subscribe messaging protocol used for pushing debug reports and alarms, supporting reliable communication in low-bandwidth environments.

[0078] 12. CRC16 / CRC32

[0079] The full English name is Cyclic Redundancy Check 16 / 32, which translates to Circular Redundancy Check 16 / 32-bit in Chinese. CRC16 / CRC32 is an error detection coding algorithm used to verify the integrity of communication CMS messages. CRC32 provides higher check strength than CRC16 and is suitable for high-interference environments.

[0080] 13. UUID

[0081] The full English name is Universally Unique Identifier (UUID). A UUID is a standardized unique identifier used to mark sequential control instructions, preventing duplicate or conflicting debugging commands.

[0082] 14. Vue.js

[0083] The full English name is Vue JavaScript Framework. Vue.js is a progressive JavaScript framework for building user interfaces, used for developing and debugging web-based visual interactive interfaces.

[0084] 15. SQLite is a lightweight relational database management system that can be used to store compliance verification databases and interval layer device parameter data.

[0085] 16. CNN

[0086] The full English name is Convolutional Neural Network, which is a type of deep learning model.

[0087] 17.B / S

[0088] The full English name is Browser / Server, which is a software architecture pattern.

[0089] 18. EtherNet / IP

[0090] The full English name is Ethernet Industrial Protocol. EtherNet / IP is a communication protocol used in industrial automation applications, supporting high-speed data acquisition between sensors and CMS clients (used in acceptance testing scenarios).

[0091] 19. EMI

[0092] The full English name is Electromagnetic Interference (EMI). EMI refers to electromagnetic noise interference that affects the operation of communication and spacer equipment. It is monitored by sensors and triggers adaptive strategies when interference is high.

[0093] The present invention will now be described in further detail with reference to the accompanying drawings.

[0094] Reference Figures 1 to 4 A method for one-click sequential control and synchronous commissioning of substations based on an independently controllable CMS protocol, comprising:

[0095] The configuration and communication adaptation steps for the independently controllable CMS protocol are as follows: Based on the mapping relationship between IEC61850 objects (Logical Nodes, Data Objects, and CMS data structures (Application Service Units, Data Frame Headers and Trailers), a PER encoding / decoding module based on the ASN.1 standard is developed. This module supports a 40%-60% reduction in data frame size after encoding compared to BER encoding, and can adapt to the independently controllable substation CMS communication protocol. The CMS client establishes a TCP / IP connection with the CMS server via a 1000Mbps full-duplex Ethernet connection. The connection request includes the CMS client ID and protocol version number V1.0. After successful verification by the CMS server, a connection confirmation CMS message is returned, which includes the CMS server ID and a maximum CMS message length of 1024 bytes. The terminal sends a request CMS message containing a service code at a third preset time period (e.g., 100ms). In the service code, 0x01 represents a debugging instruction request and 0x02 represents a status query. The CMS message carries a UUID-formatted sequential control instruction identifier and a 16-bit binary encoded target device ID. After receiving the message, the CMS server decodes it using PER (decoding time ≤ 10ms) and performs semantic verification (verifying the legality of the target device ID and the authorization of the debugging instruction). If the verification is successful, the corresponding service process is executed, generating a response CMS message containing the response status of the bay layer device. In the response status, 0x00 indicates success and 0x01 indicates failure. After being encoded by the PER encoding and decoding module, the message is sent back. The entire communication latency is ≤ 50ms, the data transmission accuracy is ≥ 99.9%, and it is compatible with the communication adaptation requirements of the previous MMS protocol substation.

[0096] Sequential control ticket parsing and compliance verification steps: Obtain the sequential control ticket from the substation operation and maintenance management platform, which has undergone three levels of review: initial review by the operation and maintenance team, secondary review by the technical department, and final review by the control center. The ticket is in XML format and contains 10-50 operation steps. Each step includes the operation type (e.g., "switch closing"), target equipment ID, control parameters (e.g., "closing voltage 110kV"), and execution time limit (e.g., "30s"). The sequential control ticket is parsed and verified using a rule engine developed in Python. The parsing process consists of three steps: The first step is to extract the primary equipment association relationship. For example, before the main transformer switch is operated, the disconnect switches on both sides need to be verified first. In the tripped state, the second step is to verify the range of control parameters. The voltage parameter must be within 90%-110% of the equipment's rated voltage, and the current parameter must be less than or equal to the equipment's rated current. The third step is to verify the operation timing logic to avoid conflicting steps where "switch closing" and "disconnector opening" are executed simultaneously. If the verification fails, the error location is marked, such as "Step 5: Disconnector not tripped before main transformer switch closing" and a correction suggestion is generated, such as "Execute step 3 disconnector opening first". The verification pass rate is ≥98%, and the verification log can be exported in TXT format, containing the verification time, error type, and correction suggestion.

[0097] Multi-device synchronous debugging instruction generation and issuance steps: An edge computing host equipped with an ARM Cortex-A9 dual-core processor with a main frequency of 1.2GHz and 2GB DDR3 memory is used. Its computing power is ≥6 TOPS, supporting multi-threaded parallel processing. Real-time acquisition of remote signaling / telemetry data from interval layer devices is achieved via an RS485 bus. This bus communication rate is 115200bps, with 8 data bits and 1 stop bit. The current data sampling frequency is 50Hz with an accuracy of ±0.5%, the voltage data sampling frequency is 50Hz with an accuracy of ±0.2%, and the device switch status sampling frequency is 10Hz with a response time ≤100ms. The edge computing host, combined with the sequential control ticket parsing results, generates and issues instructions according to "target device ID - operation type - parameter value". Synchronous debugging commands are generated in the format of "Execution Time Limit," carrying timestamps accurate to milliseconds to ensure timing consistency. Debugging commands are sent to bay-level equipment via the LoRaWAN protocol, which operates in the 470-510MHz frequency band with a spreading factor of SF=12 and a transmission rate of 1.2kbps. Time Division Multiplexing (TDMA) technology is used to divide the communication time slots of bay-level equipment, with each bay-level equipment having a 100ms time slot to avoid debugging command conflicts. It supports collaborative execution by 2-8 bay-level equipment, with a synchronization deviation ≤100ms and a debugging command issuance success rate ≥99.5%. Furthermore, when bay-level equipment is offline, debugging commands are automatically cached for ≤10 minutes and reissued upon the equipment's return to the network. Collaborative execution refers to controlling multiple bay-level equipment to drive their corresponding primary equipment, ensuring synchronous or sequential operation according to strict timing requirements. Bay-level equipment is the direct receiver and driving unit of control and debugging commands, such as line protection devices, transformer protection devices, and measurement and control units. Primary equipment is the final implementer of physical actions, such as circuit breakers (switches), disconnectors (knife switches), and transformers (main transformers).

[0098] Real-time acquisition and feedback of commissioning status: Deploy multiple types of sensors next to the target bay layer equipment: current sensor (model ACS712, range 0-50A, accuracy ±0.5%), voltage sensor (model ZMPT101B, range 0-220V, accuracy ±0.2%), and position sensor (model KTR-100, range 0-100mm, accuracy ±1mm). The sensors connect to the CMS client via the Modbus-RTU protocol (communication rate 9600bps) and acquire the equipment's execution status once every first preset time period (e.g., 200ms). The acquired data is encoded by the PER codec module of the CMS client and uploaded to the commissioning host (deployed in the substation monitoring center, using a B / S architecture, supporting multiple...) via Ethernet. Terminal access); the debugging host displays the execution progress of the bay layer equipment in real time in the form of an instrument panel (such as "Switch opening (50%)" "Knife switch in place (100%)"), and the status is indicated by color (green normal, yellow in execution, red abnormal); when an execution timeout is detected (exceeding the debugging instruction time limit by 1.2 times, such as the debugging instruction time limit of 30s and the timeout judgment threshold of 36s) or an abnormal status (such as the current exceeding the rated value of the bay layer equipment by 1.1 times), an alarm message is immediately generated through audible and visual alarm (buzzer frequency 1kHz, LED red light flashing) and SMS push (to the mobile phone of the operation and maintenance personnel). The alarm response time is less than or equal to the fourth preset time (such as 1s), and the alarm message includes the abnormal target equipment ID, abnormal type (timeout / overcurrent / overvoltage), current value, and historical comparison data.

[0099] Debugging accuracy optimization and model iteration steps: After each debugging session, calculate the execution accuracy of the equipment. The execution accuracy of the equipment is equal to (the number of correctly executed steps divided by the total number of steps) multiplied by 100%. The criterion for correct execution is that the deviation between the actual state and the target state of the bay layer equipment is ≤5%, such as voltage deviation ≤ ±0.5kV and position deviation ≤ 5mm. When the accuracy is less than the preset accuracy threshold (e.g., 95%), analyze the causes of the deviation through the debugging host and classify them statistically, including deviations in debugging command parameters, such as low control voltage causing delays in switching action, and delays in bay layer equipment response, such as mechanical jamming of old disconnectors, and environmental factors. Interference, such as electromagnetic noise, can cause errors in the transmission of debugging commands. Accumulated deviation data is used, with a dataset formed every 100 debugging cycles, including deviation type, deviation value, and environmental parameters. The gradient descent algorithm is used to fine-tune the synchronous debugging model, with a learning rate of 1e-5 and an iteration count of 1000. The timing of debugging command issuance is optimized, such as issuing the disconnector action debugging command 50ms earlier, and parameter configurations are improved, such as adjusting the switch closing voltage from 110kV to 112kV. After 5 iterations, the debugging accuracy is ≥98%, and the iteration log can be exported, containing the iteration count, accuracy change curve, and parameter adjustment records.

[0100] In some embodiments, a debug task priority scheduling step is also included, using a formula. Calculate the priority of the commissioning task, where P is the priority (value 0-10, the larger the value, the higher the priority), W1 is the correlation weight between the control ticket and the current power grid condition (fixed at 0.5, reflecting the urgency of the task), C is the correlation coefficient (value 0-1, calculated by comparing the correlation between the control ticket's bay layer equipment and the power grid load center, such as the main transformer bay layer equipment being directly related to the load center, receiving 1, and ordinary line switches not being directly related, receiving 0), W2 is the waiting time weight of the commissioning task (fixed at 0.3, to avoid long queues for tasks), T is the waiting time of the commissioning task (unit: s, value 1-300, starting from the time the task is submitted to the scheduling queue), W3 is the importance weight of the primary equipment corresponding to the commissioning task (fixed at 0.2, ensuring priority commissioning of key bay layer equipment), and U is the importance coefficient of the primary equipment corresponding to the commissioning task (value 0-1, divided according to the role of the bay layer equipment in the power grid, with main transformer and bus bay layer equipment receiving 1, and ordinary switches and disconnectors receiving 0.5). The scheduling process employs a priority queue algorithm, where high-priority commissioning tasks are given priority in entering the execution queue. For example, the commissioning task of the 220kV main transformer (U=1), with a waiting time of T=10s and a correlation with the current power grid load center of C=1, has a priority of P=0.5×1+0.3×(1 / 10)+0.2×1=0.73 (7.3 / 10 after normalization), which is higher than the 110kV ordinary line switching task (U=0.5, T=60s, C=0.6, P=0.5×0.6+0.3×(1 / 60)+0.2×0.5=0.355, 3.55 / 10 after normalization). Furthermore, the scheduling process supports real-time viewing of the task queue (including task ID, priority, and waiting time), avoiding the impact of commissioning delays on the power grid operation caused by delays in the commissioning of critical bay layer equipment.

[0101] In some embodiments, a dynamic error correction step for debugging is further included, using a formula. Calculate the debugging error after dynamic correction, where The debugging error after dynamic correction (unit: %, value 0-5, ≤3% is considered qualified). This refers to the measured debugging error (the percentage deviation between the actual state and the target state of the equipment in the bay layer, such as an actual switch closing time of 550ms and a target time of 500ms). W temp The influence of temperature is weighted (fixed at 0.4, as temperature changes have a significant impact on the mechanical action of the spacer layer equipment). To test the ambient temperature change (unit: °C, range: -10~40, acquired by DS18B20 temperature sensor, accuracy: ±0.5 °C). The electromagnetic noise influence weight is fixed at 0.3 (due to the complex electromagnetic environment of substations requiring noise compensation), and N is the electromagnetic noise intensity (unit: V / m, value 0~10, acquired by an EMI-100 sensor, frequency range 30MHz~1GHz, accuracy ±0.2V / m). When When the error exceeds the preset error threshold (e.g., 3), the debugging host automatically adjusts the debugging command parameters: if the error is due to excessively high temperature, i.e. An error occurred due to a temperature change exceeding the preset threshold (20℃). Therefore, the execution time of the interval layer equipment was extended (extension ratio = 0.02 × ... If the error is caused by excessive electromagnetic noise, i.e., N is greater than the first preset strength threshold (e.g., 8V / m), the verification strength of the debugging command is increased (upgraded from CRC16 to CRC32); for example, in the debugging of a switch, E meas =5、 =10℃, N=5V / m, then =5-(0.4×10+0.3×5)=5-5.5=-0.5, the error is within a reasonable range and no adjustment is needed, ensuring stable debugging accuracy under different environments.

[0102] Since high temperatures may cause reduced lubrication of the equipment's mechanical mechanisms, deviation in component performance, or increased communication delays, if errors are caused by excessively high temperatures, the system will automatically extend the equipment's execution time limit. Extending the execution time limit can provide more buffer time for equipment operation, ensuring that the action is completed in place.

[0103] Excessive electromagnetic noise can cause errors, so the system will automatically strengthen the verification of debugging commands (e.g., upgrading the verification algorithm from CRC16 to CRC32). A stronger verification code can effectively resist data packet errors caused by electromagnetic interference, ensuring the integrity of transmitted debugging commands and preventing execution deviations due to incorrect debugging commands.

[0104] In some embodiments, the self-controllable CMS client development steps also include a communication fault tolerance mechanism: after the CMS client sends a request CMS message, it starts a software timeout timer (the timeout time is set to twice the communication delay, i.e., 100ms, to avoid misjudging faults due to network fluctuations). If no response is received from the CMS server after the timeout, a retransmission mechanism is automatically triggered. The number of retransmissions is less than or equal to a preset number K (e.g., 3 times), and the retransmission interval adopts an exponential backoff algorithm (for example, the initial interval is 100ms, and the retransmission interval is...). The retransmission interval is , ≤K, where K=3, meaning the first retransmission interval is 100ms, the second is 200ms, and the third is 400ms, reducing network congestion and avoiding retransmission failures caused by network congestion; if all K retransmissions fail, the CMS client automatically reads the locally configured list of backup CMS servers (pre-configured with 2-3 backup interval layer devices, IP addresses 192.168.1.101-103, port 5000), checks the online status of the backup CMS servers via the ICMP protocol (ping command), selects the backup CMS server with the lowest latency (≤30ms) to establish a new connection, and the switching time is less than or equal to the preset time. Interval threshold (e.g., 200ms); simultaneously, the CMS client records communication failure information to the local log (CSV format, including failure time, failure type (timeout / retransmission failure / switchover), number of retransmissions, and CMS server IP before and after the switchover). For every first preset number of failure data entries accumulated (e.g., 50 entries), the communication link selection model is updated using a decision tree algorithm (increasing the avoidance weight of the faulty CMS server). Subsequent communication prioritizes links with a historical failure rate of <5%, and the failure recovery rate is ≥ a preset threshold (e.g., 95%). It also supports exporting failure statistics reports (including monthly failure count, failure type percentage, and recovery success rate) through the debugging host.

[0105] In some embodiments, the multi-device synchronous commissioning step further includes multi-bay collaborative commissioning: For multiple (e.g., 3-5) adjacent bays within the substation, such as 220kV line bays, 110kV line bays, and main transformer bays, with a bay spacing ≤50m, each bay is equipped with one Beidou dual-mode timing module, model UT300-Pro, with a timing accuracy ≤50ns and a capture sensitivity ≤-148dBm. Time synchronization of each bay is achieved through the PTP protocol, i.e., IEEE1588v2, with a synchronization error ≤10us. Before the commissioning command is issued, the edge computing host reads the bay association matrix, which is pre-configured, such as "the 110kV line bay disconnector can only be opened after the 220kV line bay switch is closed," and additional bays... The interval collaboration identifier, such as "Collaboration Group 1: Interval 1-3", is added to the debugging command. When the debugging command is issued, the edge computing host schedules the process uniformly according to the collaboration logic: the first interval debugging command is issued first, and after receiving the feedback of "execution completed" of the first interval with status code 0x00, the second interval debugging command is issued after a first preset time delay (such as 200ms), and so on, to avoid action conflicts between intervals, with a conflict occurrence rate of <1%. After the collaborative debugging is completed, an interval collaboration report is generated. The report is in PDF format and includes the execution time of each interval, the synchronization deviation accurate to milliseconds, the action results, and conflict avoidance measures. It also supports pushing messages to the debugging host (such as the provincial company's control platform) via the MQTT protocol, i.e., QoS level 2, to ensure that messages are not lost, facilitating global monitoring.

[0106] The bay is an independent unit of primary equipment in a substation, divided according to its electrical function; it is the physical object and boundary of operation. The bay-level equipment is a collection of intelligent electronic devices (IEDs) deployed within the bay, responsible for its monitoring, protection, control, and data acquisition. The bay-level equipment is a component of the bay and the foundation for its intelligent operation.

[0107] In some embodiments, the real-time acquisition and feedback step of the debugging status further includes adaptive adjustment of environmental parameters: A multi-parameter environmental sensor (model SHT30, measuring temperature -20~60℃, accuracy ±0.3℃; humidity 20%-90%RH, accuracy ±2%RH; model EMI-200, measuring electromagnetic noise 0~15V / m, accuracy ±0.1V / m) is deployed in the debugging area. The multi-parameter environmental sensor collects data at a second preset time period (e.g., 500ms) and uploads it to the debugging host. The debugging host triggers an adaptive strategy based on the environmental parameters: when the temperature exceeds a preset temperature threshold (e.g., 40℃), the CPU frequency of the debugging host is automatically reduced (from 1.2GHz to 0.8GHz to reduce heat generation and prevent hardware overheating and crashes), and the cooling fan of the debugging host is simultaneously activated (speed increased from 2000rpm). Up to 3000 rpm); when the humidity is greater than the preset humidity threshold (e.g., 85%RH), the sensor's moisture-proof heating element is activated (operating voltage 5V, power 2W, temperature controlled at 50℃±2℃ to prevent condensation on the sensor probe from affecting accuracy); when the electromagnetic noise is greater than the second preset intensity threshold (e.g., 10V / m), the CMS message verification strength is enhanced (upgraded from CRC16 to CRC32, and the verification coverage is expanded from the CMS message header to the entire CMS message), while the CMS message transmission rate is reduced (from 1.2kbps to 0.6kbps to improve anti-interference capability); after environmental adaptation and adjustment, the sensor data acquisition accuracy is ≥99%, the debugging edge computing host runs continuously and stably for ≥24 hours, and supports exporting environmental parameter adjustment logs (including adjustment time, trigger conditions, adjustment measures, and post-adjustment effects).

[0108] In some embodiments, a self-repair step for debugging faults is also included: the debugging host is equipped with a fault diagnosis model (a CNN neural network trained based on nearly 1000 sets of historical fault data, with a diagnostic accuracy of ≥92%), which monitors the fault types of the target equipment in real time: communication faults (such as CMS message loss, verification failure), execution faults (such as the interval layer equipment not acting according to the debugging instructions, or action timeout), and parameter faults (such as control parameters exceeding the rated values ​​of the interval layer equipment, or incorrect parameter format); for communication faults, the debugging host automatically restarts the CMS client communication module (the restart time is less than or equal to the fourth preset time (such as 1 second), and after restarting, a TCP connection is re-established and the debugging instructions are resent); if the restart is ineffective, it switches to the backup communication link (such as switching from Ethernet to a 4G module, with APN "cmnet" and a transmission rate of ≥1Mbps); for execution faults, it first sends a target equipment status reset instruction through the CMS client (such as a switch forced opening / closing instruction, carrying a strong After resetting (identified by 0xFF), wait for a second preset time (e.g., 500ms) to re-execute the original debugging command. If it still fails, generate a manual intervention prompt (including the location of the faulty equipment and suggested operation "check the mechanical jamming of the faulty equipment"). For parameter faults, the debugging host automatically reads the rated parameter library of the target equipment (e.g., rated voltage of the main transformer 110kV, rated current of the switch 100A), reconfigures the control parameters according to a preset proportion of the rated value (e.g., 90%) (e.g., adjust the original parameter 120kV to 99kV), and marks the parameter correction record. After each fault repair, the repair process is recorded in the fault repair knowledge base (MySQL database, including fault time, target equipment ID, fault type, repair measures, repair results, and time consumption). For every second preset number of fault records added (e.g., 100 records), the fault diagnosis model is updated using the random forest algorithm (adding feature weights for new fault types). The fault self-repair success rate is ≥90%, and the frequency of manual intervention is reduced by more than 60%.

[0109] In some embodiments, a debugging energy consumption optimization step is also included, using a formula. Calculate the total energy consumption for debugging, of which The total energy consumption during commissioning is expressed in kWh, reflecting the energy consumption during the commissioning process. n represents the number of primary equipment involved in the commissioning (such as main transformers, switches, disconnectors, etc., n≥2). The operating power of the i-th primary equipment (unit: kW, calibrated by the primary equipment nameplate parameters and actual measured data, such as main transformer operating power 0.8kW, line switch 0.5kW, protection device 0.2kW). The running time of the i-th primary device (unit: h, the time from the start-up and commissioning of the primary device to the completion of execution, accurate to 0.01h). To debug the host's standby power (unit: kW, fixed at 0.1kW, actual measured power consumption in standby mode), T is the total debugging time (unit: h, the time from the start of the task to the completion of all primary devices). Based on... Adjust the operating sequence of primary equipment based on the comparison results with preset thresholds (set according to substation energy consumption standards, such as 5kWh): When When the threshold is ≤, execute according to the original timing sequence; when When the threshold is reached, optimize the startup time of non-critical primary equipment (e.g., change the commissioning time of ordinary disconnectors from "starting synchronously with the main transformer" to "starting after the main transformer commissioning is completed") to reduce the simultaneous running time of primary equipment; for example, a commissioning task n=5 (1 main transformer, 2 switches, 2 disconnectors). The power outputs are 0.8kW, 0.5kW, 0.5kW, 0.3kW, and 0.3kW respectively. Both are 0.5h, T=1h, then =(0.8×0.5+0.5×0.5+0.5×0.5+0.3×0.5+0.3×0.5)+0.1×1=(0.4+0.25+0.25+0.15+0.15)+0.1=1.3+0.1=1.4kWh<5kWh, which meets the energy consumption requirements, and supports exporting energy consumption statistics reports (including the proportion of primary equipment energy consumption and the comparison of energy consumption before and after optimization).

[0110] In some embodiments, the debugging process also includes a visual interactive step: a web visualization interface is developed using the Vue.js framework, supporting Chrome 90+ and Edge 90+ browsers, with a page loading time ≤ 2s and a response time less than or equal to a third preset time (e.g., 500ms). The interface is divided into three main modules: a debugging progress module displays the overall progress with a horizontal progress bar, the color of which changes with the progress: gray for 0-30%, yellow for 31-70%, and green for 71-100%, with the progress updated in real time; a target device status module displays the status with a target device icon and color-coded indicators, green for "normal completion," yellow for "in execution," and red for "abnormal fault," and clicking the icon allows viewing detailed data such as current and voltage curves; and a debugging instruction record module displays the debugging instruction content, issuance time, execution result, and response time in a table format, supporting filtering by time or target device ID; and supports manual intervention by maintenance personnel, with intervention operations including pausing debugging, clicking... Clicking the "Pause" button immediately stops the current action of the target device and retains its current state. Modifying debugging command parameters requires entering new parameter values ​​and submitting them; the system will verify the validity of the parameters. Terminating debugging is only possible with administrator privileges and requires password confirmation. All intervention commands are subject to secondary permission verification, i.e., operator account login plus administrator password authorization, to take effect and avoid accidental operation. After debugging is completed, the system automatically generates a PDF debugging report. The report includes basic information such as the debugging task ID, substation name, and debugging time; execution data such as the execution steps, parameter values, and actual results of each primary device; error analysis such as measured error, corrective measures, and error causes; and compliance judgment such as determining whether it is qualified or unqualified according to the "Substation One-Click Sequential Control Technical Guidelines". The report supports online preview, download, and printing, and is also pushed to the substation operation and maintenance management platform via the MQTT protocol (broker address 192.168.1.200, port 1883) and included in the target device operation and maintenance file for easy subsequent traceability and auditing.

[0111] In some embodiments, the system also includes a dynamic compliance verification step: A compliance verification library is constructed (based on an SQLite database, regularly updated with industry standards and State Grid specifications), incorporating requirements from documents such as the "Technical Guidelines for One-Click Sequential Control in Substations (Trial)" (Equipment Substation

[2021] No. 28) and the "Opinions of State Grid Corporation of China on Promoting the Construction and Application of One-Click Sequential Control in Substations" (State Grid Equipment

[2022] No. 386), clarifying the compliance indicators for each primary device, including: the main transformer's commissioning voltage deviation is within a preset voltage deviation range (e.g., within ±2%), the switch action time is less than or equal to the third preset time (e.g., 500ms), the disconnector action position deviation is less than or equal to the preset position deviation (e.g., 10mm), and the protection device alarm response time is less than or equal to the fourth preset time (e.g., 1s); during commissioning, the commissioning host compares the primary device execution data with the compliance indicators at a third preset time period (e.g., 100ms), and uses the difference calculation method to determine whether the standards are exceeded (e.g., the actual voltage of the main transformer is 112kV, and the rated voltage is 110kV). Deviation = (112-110) / 110×100%≈1.8%≤2%, deemed compliant); When the data exceeds the indicator range, a compliance alarm window immediately pops up on the visualization interface (for example, including the out-of-standard indicator "switch action time 550ms", standard requirement "≤500ms", current value "550ms", and suggested measure "check switch mechanical lubrication"); at the same time, an alarm log is recorded (including alarm time, out-of-standard equipment, and out-of-standard item); after commissioning, the compliance rate is calculated: compliance rate = (number of compliant indicators / total number of indicators)×100%. If the compliance rate is greater than or equal to the preset compliance rate threshold (e.g., 95%), the commissioning is deemed qualified; otherwise, a rectification list is generated (Excel format, including rectification items, rectification basis, rectification suggestions, and rectification deadline). Secondary verification is supported after rectification is completed; the compliance verification accuracy rate is ≥99%, ensuring that the commissioning results fully comply with industry standards and power grid safety operation requirements, and supporting the export of a compliance verification report (including verification item details, out-of-standard records, and rectification status), which serves as an important basis for substation acceptance.

[0112] The following two implementation cases further illustrate the specific implementation methods of this system:

[0113] Example 1: One-click sequential control daily commissioning of a 220kV autonomous and controllable CMS protocol substation (Scenario of a 220kV Tianzhen substation of State Grid)

[0114] This embodiment focuses on a 220kV substation of the State Grid Corporation of China (which adopts the independently controllable CMS communication protocol, including 3 240MVA main transformers, 6 220kV line bays, 12 110kV line bays, and 42 10kV outgoing line bays, and requires one-click sequential control debugging of the main transformer bays and 10kV outgoing line bays in daily operations). It applies a one-click sequential control synchronous debugging method for substations based on the independently controllable CMS protocol, and focuses on verifying the CMS client communication adaptation, multi-device synchronous debugging, environmental adaptive adjustment, and fault self-repair functions, solving the problems of traditional debugging relying on manufacturers, low efficiency, and poor accuracy.

[0115] I. Hardware Deployment and Parameter Configuration

[0116] CMS Client and Communication Equipment: Three independently controllable CMS clients (based on ARM Cortex-A7 architecture, 1.0GHz main frequency, 1GB DDR3 memory, and 8GB eMMC storage) are deployed in the substation monitoring room. The CMS client is equipped with a PER codec module based on the ASN.1 standard (developed in C language, supporting a 45% improvement in data frame encoding efficiency and a decoding time of ≤8ms). It connects to the CMS server (NARI PCS-9700 bay layer device, supporting CMS protocol V1.0, with a maximum CMS message length of 1024 bytes) via a 1000Mbps Ethernet. The connection request includes the CMS client ID "CMS-220-TZ-01" and the protocol version number "V1.0". After the CMS server verifies the connection, it returns a confirmation CMS message (including the CMS server ID "SL-220-TZ-03" and a communication latency threshold of 50ms).

[0117] Edge computing and timing equipment: Deploy one edge computing host (equipped with an ARM Cortex-A9 dual-core processor, 1.2GHz clock speed, 2GB DDR3 memory, and 6.5TOPS computing power), which collects data from the interval layer devices via RS485 bus (communication rate 115200bps, 8 data bits, 1 stop bit, and no parity bit); The edge computing host is connected to the BDS-3 Beidou dual-mode timing module (model UT300-Pro, timing accuracy 45ns, acquisition sensitivity -149dBm), and achieves time synchronization with each interval through the PTP protocol (IEEE1588v2), with a synchronization error ≤8us.

[0118] Sensors and monitoring equipment: An ACS712 current sensor (range 0-100A, accuracy ±0.4%), a ZMPT101B voltage sensor (range 0-220V, accuracy ±0.15%), and a KTR-100 position sensor (range 0-150mm, accuracy ±0.8mm) are deployed in the main transformer bay. An EMI-200 electromagnetic noise sensor (range 0-15V / m, accuracy ±0.1V / m) and an SHT30 temperature and humidity sensor (temperature -20~60℃, accuracy ±0.3℃; humidity 20%-90%RH, accuracy ±2%RH) are deployed in the 10kV outgoing line bay. All sensors are connected to the CMS client via the Modbus-RTU protocol, with a communication rate of 9600bps and a data acquisition interval of 200ms.

[0119] II. Detailed Debugging Process and Technical Solution

[0120] Independent and controllable CMS client communication adaptation: The CMS client sends request CMS messages containing a service code at 100ms intervals. The service code "0x01" corresponds to a debug command request. The CMS message carries a sequential control command identifier and a target device ID. The sequential control command identifier is in UUID format and follows the 8-4-4-12 rule, for example, "550e8400-e29b-41d4-a716-446655440000". In the target device ID, the main transformer bay is "220-TZ-MT-01" and the 10kV outgoing line bay is "10-TZ-LN-05". After receiving the CMS message, the CMS server first performs PER decoding, which takes 6ms. Then, it verifies the validity of the target device ID and the debug command permission. Verifying the validity of the target device ID requires querying the local device list to confirm its validity. The verification command permission requires the debugging command to have "Operation and Maintenance Operation Permission". After the verification is successful, the service process is executed, such as executing the main transformer switch tripping command. Subsequently, a response CMS message with a response status of "0x00" is generated. The response status "0x00" represents success. After being encoded by the PER encoding and decoding module, it is sent back. The entire communication delay is 42ms, and the data transmission accuracy is 99.95%. When the communication is interrupted, the CMS client starts the fault tolerance mechanism: the timeout timer is set to 100ms, which is twice the communication delay. If no response is received, it will retransmit 3 times at intervals of 100ms, 200ms, and 300ms. After 3 retransmissions fail, it switches to the backup CMS server. The backup CMS server IP is 192.168.1.102, with a delay of 28ms, a switching time of 180ms, and a fault recovery rate of 96%.

[0121] Sequential control ticket parsing and compliance verification: Obtain the sequential control ticket (XML format, containing 25 operation steps, such as "Step 1: 10kVLN-05 bay disconnector tripping, control voltage 10.5kV, execution time limit 25s; Step 2: 220kVMT-01 bay switch tripping, control voltage 220kV, execution time limit 30s") from the substation operation and maintenance platform after three levels of review; Rule engine (developed in Python, based on the Drools rule framework) parsing process: ① Extract the primary equipment association relationship (before step 2 switch tripping, it is necessary to verify that step 1 disconnector tripping has been completed); ② Verify the parameter range ( For 10.5kV, the rated voltage of the equipment is 90%-110% of that of 10kV equipment; for 220kV, the rated voltage of the equipment is 90%-110% of that of 220kV equipment. ③ Verify the timing sequence (avoid simultaneous execution of "switch opening" and "disconnector closing"). The verification found that "Step 5: Before closing the 10kVLN-05 bay switch, the unverified current is 0", marked as an error and suggested "execute Step 4 current detection first". The verification pass rate was 98.2%. The verification log was exported (TXT format, including the verification time "2024-11-28 09:15:30" and the error type "parameter association missing").

[0122] Multi-device synchronous commissioning and priority scheduling: The edge computing host collects the main transformer interval current (e.g., 28.5A) and voltage (218.5kV) at a frequency of 50Hz, and collects the disconnector position (opening status) at a frequency of 10Hz. Combined with the sequential control ticket, it generates synchronous commissioning instructions (format: "Target device ID: 220-TZ-MT-01, Operation type: Switch opening, Parameter value: 220kV, Execution time limit: 30s, Timestamp: 2024-11-28 09:20:00.123"). Commissioning instructions are issued via the LoRaWAN protocol (operating frequency band 480MHz, spreading factor SF=12, transmission rate 1.2kbps), using TDMA technology to divide time slots (100ms per device), supporting coordinated execution of 6 devices (3 main transformers, 3 10kV outgoing lines); simultaneously, according to the formula... Priority calculation: Main transformer commissioning task (C=1, T=15s, U=1): P=0.5×1+0.3×(1 / 15)+0.2×1=0.72 (normalized 7.2 / 10), 10kV outgoing line task (C=0.7, T=40s, U=0.5): P=0.5×0.7+0.3×(1 / 40)+0.2×0.5=0.4275 (normalized 4.275 / 10). The main transformer task is executed first, with a synchronization deviation of 92ms.

[0123] It should be understood that the direct communication target of TDMA time slot allocation is the bay-level equipment (protection and control devices) that control the primary equipment. Commands are sent to these bay-level devices via the LoRaWAN protocol. The ultimate target of the operation is the primary equipment (main transformers, 10kV outgoing line switches). The purpose of synchronous communication is to synchronize the operation of these primary devices. The primary equipment and the bay-level equipment controlling it are considered as a single device or logical unit in communication scheduling. The aforementioned three main transformers refer to a combination of three sets of "main transformer protection and control devices + main transformer body". The three 10kV outgoing lines refer to a combination of three sets of "line protection and control devices + outgoing line circuit breakers".

[0124] Debugging error correction and environmental adaptation: During debugging, the ambient temperature was 38℃ (ΔT=38-25=13℃, 25℃ is the reference temperature), and the electromagnetic noise was 7.5V / m (N=7.5). The measured main transformer switch opening time was 320ms (target 280ms). Therefore, E meas =(320-280) / 280×100; according to the formula calculate: =14.29-(0.4×13+0.3×7.5)=14.29-7.45=6.84, triggering correction: extend execution time limit (extension ratio=0.02×13=26%, new time limit 35s), enhance CMS message verification (CRC16 upgraded to CRC32); at the same time, the ambient temperature is 38℃, close to the 40℃ threshold, the debugging edge computing host automatically reduces the CPU frequency to 0.9GHz and starts the cooling fan (speed 2800rpm); the humidity is 82%RH<85%RH, no moisture protection is required; the actual measured error after correction is 2.8%, which meets the requirements.

[0125] Fault self-repair and energy consumption optimization: During commissioning, communication with the 10kV LN-05 bay sensor was interrupted (fault type: communication failure). The commissioning host automatically restarted the sensor communication module (restart time 0.9s) and resent the data acquisition and commissioning commands; if the interruption still occurred after 5s, it switched to the backup sensor (IP: 192.168.1.205) with a switching time of 150ms, and data acquisition resumed; according to the formula... Energy consumption calculation: Main transformer equipment Edev=0.8kW×t=0.5h (3 units total 1.2kWh), 10kV equipment Edev=0.5kW×t=0.5h (3 units total 0.75kWh), Pidle=0.1kW×T=1.2h (0.12kWh), total energy consumption=1.2+0.75+0.12=2.07kWh<5kWh threshold, no timing optimization is required.

[0126] Visualized Interaction and Compliance Verification: The web-based visual interface (Chrome 95 browser, loading time 1.8s) displays the commissioning progress (4 out of 6 devices completed, progress 66.7%, yellow progress bar), device status (main transformer "normal tripping" green, 10kVLN-05 "communication restored" green), and commissioning command records (main transformer tripping command issuance time "09:20:00", execution result "success"); maintenance personnel modify the 10kV outgoing line closing voltage to 10.6kV (secondary permission verification: operator account + administrator password), and the system verifies compliance (10.6kV is within the 9-11kV range); after commissioning, the compliance verification database compares with the "Substation One-Click Sequential Control Technical Guidelines": main transformer voltage deviation 1.1% ≤ 2%, switch action time 290ms ≤ 500ms, compliance rate 98.5%, judged as qualified, and a PDF report (including commissioning data and error analysis) is generated.

[0127] III. Performance Verification

[0128]

[0129] Table 1 shows data based on statistics from five routine commissioning tests of the 220kV Tianzen substation. Traditional methods rely on manual configuration of control tickets and data recording, with a single-interval commissioning time of one hour, synchronization deviations exceeding 300ms across multiple devices, and no environmental correction; errors exceed 20% in high-temperature weather. This invention, through automatic communication via the CMS client, BeiDou synchronization, and dynamic error correction, reduces commissioning time to 15 minutes, controls synchronization deviations within 100ms, and lowers the error rate to below 3.5%. The self-repair success rate of faults is increased to 96%, manual intervention only requires permission verification, significantly reducing the workload of maintenance personnel. The CMS client can be adapted without manufacturer support, meeting the requirements for building independently controllable substations, and significantly improving commissioning efficiency and reliability.

[0130] Example 2: One-click sequential control acceptance and commissioning of a 110kV substation compatible with MMS / CMS protocol (Scenario of a 110kV Youmachong substation of State Grid)

[0131] This embodiment targets a 110kV Youmachong substation of the State Grid (originally using the MMS protocol, but after modification it is compatible with the independently controllable CMS protocol, including one 50MVA main transformer, two 110kV line bays, and 25 10kV outgoing line bays, which require one-click sequential control acceptance and commissioning after the modification). The method of this invention is applied to verify the dual protocol adaptation, multi-bay coordination, and compliance acceptance functions, solving the problems of protocol incompatibility, cumbersome acceptance process, and difficulty in ensuring compliance during the commissioning of modified substations.

[0132] I. Hardware Deployment and Parameter Configuration

[0133] Dual-protocol CMS client: Deploy 4 dual-protocol CMS clients (based on ARM Cortex-A53 quad-core processor, 1.5GHz clock speed, 2GB DDR4 memory, 16GB eMMC storage). The CMS client is equipped with both MMS and CMS protocol encoding and decoding modules (the CMS module improves PER encoding efficiency by 42%, and the MMS module is compatible with the IEC61850-8-1 standard); it is connected to the interval layer device (Beijing Sifang CSC-200 interval layer device, supporting MMS / CMS dual protocol switching) via 1000Mbps Ethernet. The CMS protocol connection parameters are the same as in Example 1. The MMS protocol connection uses IEC61850 standard port 102, and the maximum CMS message length is 2048 bytes.

[0134] Multi-bay collaborative equipment: Each of the three adjacent bays (110kV line bay A, 110kV line bay B, and main transformer bay) is equipped with one Beidou time synchronization module (UT300-Pro, time synchronization accuracy 48ns), which realizes time synchronization between bays through the PTP protocol (synchronization error ≤9us); one edge computing host (7TOPS computing power, supporting multi-threaded processing of bay collaborative logic) is deployed, which is connected to the local control host of each bay through fiber optic link (1000Mbps, latency ≤15ms).

[0135] The edge computing host (master clock) periodically sends synchronization messages. Each bay's local control host (slave clock) receives these messages, calculates network latency, and continuously adjusts its local clock to maintain microsecond-level consistency with the master clock. This achieves time synchronization between the local control hosts of each bay. Bay-level devices typically obtain time synchronization signals from their respective bay's local control host via hardwired methods such as IRIG-B codes or second pulses. Therefore, once the bay's local control host achieves time synchronization, it transmits its time base to all bay-level devices under its management, thus achieving synchronization across the entire bay.

[0136] The "master-slave synchronization + hierarchical collaboration" relationship between the local control host and the edge computing host in each bay, and the "time reference transmission + indirect control" relationship with the bay-level equipment, are all designed based on the technical specifications of the specified documents and the actual needs of the substation: the former solves the problems of "time unification for multi-bay collaborative debugging" and "functional division of labor" through fiber optic links and PTP protocol; the latter solves the problems of "high-precision synchronization of bay-level equipment" and "operation and maintenance complexity" through hard wiring and IRIG-B / second pulse; the two together support the core requirements of "accurate timing, coordinated action, and environmental adaptation" for one-click sequential control and synchronous debugging.

[0137] Acceptance testing sensors: High-precision current sensors (LA-500, range 0-500A, accuracy ±0.2%) and voltage sensors (PT-110, range 0-110kV, accuracy ±0.1%) are deployed in the main transformer bays; action time sensors (DT-100, range 0-1000ms, accuracy ±0.5ms) and electromagnetic noise sensors (EMI-300, range 0-20V / m, accuracy ±0.08V / m) are deployed in the line bays; all sensors are connected to the CMS client via EtherNet / IP protocol (communication rate 100Mbps), with a data acquisition interval of 100ms, meeting the high-precision requirements for acceptance testing and commissioning.

[0138] II. Detailed Debugging Process and Technical Solution

[0139] Dual-protocol communication adaptation and fault tolerance: Acceptance testing and commissioning require simultaneous verification of both MMS and CMS protocols: During CMS protocol commissioning, the CMS client sends a CMS message with service code "0x02" (status query), and the CMS server responds with the status "open" of the bay-level equipment, with a communication delay of 45ms; During MMS protocol commissioning, the CMS client sends a GetDataValues ​​request according to the IEC61850 standard to obtain the telemetry data of the bay-level equipment (main transformer current 32.8A), with a communication delay of 52ms; When the CMS protocol CMS server fails (no response), the CMS client automatically switches to the MMS protocol (switching time 220ms) and continues commissioning; The communication fault tolerance mechanism is the same as in Example 1, switching to the backup CMS server after 3 failed retransmissions, with a fault recovery rate of 95.5%, ensuring uninterrupted commissioning in dual-protocol scenarios.

[0140] Sequential control ticket acceptance analysis and multi-bay coordination: The sequential control ticket acceptance includes 32 operation steps, such as "Step 8: Close the 110kV line bay A disconnector, Step 9: Close the 110kV line bay B disconnector, Step 10: Close the main transformer switch". When the rule engine parses and verifies, it focuses on verifying the bay coordination logic. That is, before closing the main transformer in Step 10, the disconnectors in Steps 8 and 9 must be closed. The edge computing host reads the bay association matrix, which is the "Line A-Line B-Main Transformer" coordination group, and adds the coordination identifier "Group-01" to the debugging command. The debugging command issuance sequence is as follows: 09:30:00 issue the Line A debugging command, 09:30:00.2 issue the Line B debugging command with a delay of 200ms, and 09:30:00.5 issue the main transformer debugging command with a delay of 500ms. This avoids conflicts between bays. The coordination synchronization deviation is 48ms, and the conflict occurrence rate is 0%.

[0141] Acceptance error correction and environmental adaptation: During acceptance, the ambient temperature was 42℃ (ΔT=42-25=17℃), the electromagnetic noise was 9.2V / m (N=9.2), and the measured closing time of the main transformer switch was 520ms (target 500ms).meas =(520-500) / 500×100; According to the formula ΔE=4-(0.4×17+0.3×9.2)=4-9.56=-5.56, the error is qualified (ΔE≤3%); the temperature is 42℃>40℃, the host CPU frequency is reduced to 0.8GHz and the cooling fan speed is 3200rpm; the humidity is 86%RH>85%, the sensor moisture-proof heating plate is activated (temperature 50℃), and the sensor acquisition accuracy is 99.3%.

[0142] Fault self-repair and energy consumption optimization: During acceptance testing, the action time sensor of the 110kV line bay B malfunctioned (execution fault: no data returned). The commissioning host sent a reset commissioning command ("Target device ID: 110-YMC-LN-B, commissioning command: reset"), and re-collected data 500ms after reset. If the fault persisted, a manual intervention prompt ("Check sensor wiring") was generated. After maintenance personnel checked for loose wiring, the fault self-repair success rate was 90%. According to the energy consumption formula: the total Edev of 8 devices (2 110kV lines, 1 main transformer, and 5 10kV outgoing lines) is 2.1kW × 0.6h = 1.26kWh, Pidle = 0.1kW × 1.5h = 0.15kWh, and the total energy consumption = 1.26 + 0.15 = 1.41kWh < 5kWh, which meets the acceptance energy consumption requirements.

[0143] Acceptance visualization and compliance verification: The web interface displays the acceptance progress (28 out of 32 steps completed, progress 87.5%, green progress bar) and the status of bay-level equipment (green for line bay "closing completed", green for main transformer "normal operation"); verification indicators: main transformer voltage deviation 1.2% ≤ 2%, line bay action time 510ms ≤ 500ms (exceeding the standard, marked "mechanical lubrication needs to be checked"), 10kV outgoing line current deviation 0.8% ≤ 2%; compliance rate 93.75% (30 / 32 items compliant), generating a rectification list ("Line bay B action time exceeds the standard, it is recommended to lubricate the mechanical components of the disconnect switch"); after secondary commissioning, the compliance rate is 100%, generating an acceptance report (including data comparison before and after rectification), and pushing it to the provincial company's acceptance and commissioning host.

[0144] III. Performance Verification

[0145]

[0146] Table 2 data is based on statistics from three acceptance and commissioning tests of the 110kV Youmachong substation. Traditional acceptance testing required manual switching between MMS / CMS protocols, taking 4 hours for adaptation. Multi-interval coordination relied on walkie-talkies, resulting in deviations exceeding 200ms, an initial compliance rate of less than 80%, and a report generation time of 3 hours. This invention, through automatic dual-protocol adaptation, reduces the time to 0.5 hours. BeiDou synchronization and collaborative scheduling reduce deviations to within 50ms, increasing the initial compliance rate to 94%, and completing report generation in 5 minutes. During the rectification phase, based on accurate out-of-compliance alerts, the second acceptance pass rate reached 100%, solving the pain points of "difficult protocol adaptation and cumbersome compliance verification" in substation renovation acceptance. It meets the State Grid acceptance specifications and provides a reusable solution for similar renovation projects.

[0147] Reference Figure 2 This diagram visually demonstrates the efficiency improvement of this invention in commissioning substations with different protocols. Traditional commissioning relies on manual protocol configuration and verification of control tickets. Commissioning a single CMS / MMS interval takes 2-3 hours, while commissioning multiple intervals in a dual-protocol compatible substation takes over 4 hours, resulting in low efficiency. This invention, through its independently controllable CMS client automatically adapting to protocols, intelligently parsing control tickets, and synchronously scheduling multiple devices, reduces commissioning time in various scenarios to 1 / 5 of the traditional approach, improving efficiency by 80%. For example, comprehensive commissioning of a dual-protocol compatible substation, which traditionally takes 8 hours, takes only 1.6 hours with this invention, significantly reducing power outage time and maintenance costs.

[0148] Reference Figure 3 Traditional testing methods, lacking high-precision BeiDou timing and environmental error correction, result in errors of ±3.0µs for 2M multiplexed channel optical ports and over ±4.0µs for mixed channels, failing to meet the training document's accuracy requirement of "delay difference ≤15ms". This invention, through BeiDou dual-mode timing (synchronization error ≤10µs) and dynamic temperature / electromagnetic interference correction, controls the testing errors of each channel within ±0.6µs, improving accuracy by over 83%. For example, in the 220kV Fushuang line 2M multiplexed channel electrical port test, the traditional error is ±2.8µs, while this invention's is only ±0.4µs, ensuring that the delay data closely matches the actual channel condition and resolving the report's issue of "poor accuracy and high risk of misjudgment in traditional testing".

[0149] Reference Figure 4Traditional testing methods lack environmental compensation mechanisms. When the temperature rises from -10℃ to 40℃, the time delay fluctuation reaches 5.2µs, and when electromagnetic interference is 8V / m, the fluctuation exceeds 4.5µs, making them unsuitable for the complex environment of outdoor substations. This invention, through temperature drift compensation (dynamic drift is calculated using an integral formula), segmented optical power correction, and BeiDou signal enhancement, controls the time delay fluctuation caused by various environmental factors to within 0.8µs, achieving a fluctuation suppression effect of over 84%. For example, at 90%RH humidity, the traditional method results in a fluctuation of 2.3µs, while this invention results in only 0.3µs, ensuring stable and reliable time delay data even in rain, snow, and high-temperature scenarios, meeting the report's requirement for "all-weather testing of the longitudinal protection channel."

[0150] The above are merely preferred embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. Any equivalent substitutions or modifications made by those skilled in the art within the scope of the technology disclosed in the present invention, based on the technical solution and inventive concept of the present invention, should be covered within the scope of protection of the present invention.

Claims

1. A substation one-key sequential control synchronous debugging method based on an autonomous controllable CMS protocol, characterized in that, The method is realized based on a debugging host, an edge computing host and an interval layer device, the debugging host is in communication connection with the edge computing host, a CMS client is arranged on the edge computing host, a CMS server is arranged on the interval layer device, the CMS client is in communication connection with the CMS server, the CMS client and the CMS server are both integrated with a PER encoding and decoding module, and the method comprises the following steps: The debugging host acquires and analyzes the sequence control ticket, and checks the analysis result of the sequence control ticket, if the checking fails, the error position is marked and a correction suggestion is generated, and the checking log can be exported for the operation and maintenance personnel to check, and the sequence control ticket can be manually corrected in the subsequent step, and the sequence control ticket analysis result that passes the checking is sent to the edge computing host; The edge computing host collects the remote signaling / telemetry data of each interval layer device connected thereto, generates a synchronous debugging instruction in combination with the sequence control ticket analysis result that passes the checking, the CMS client encodes the synchronous debugging instruction into a debugging instruction CMS message through the PER encoding and decoding module, and the debugging instruction CMS message is synchronously sent to the CMS servers on the multiple interval layer devices; The CMS server on the interval layer device receives the debugging instruction CMS message, decodes the debugging instruction CMS message through the PER encoding and decoding module, and drives the primary device to perform the corresponding operation according to the decoded debugging instruction; The CMS server on the interval layer device generates a response CMS message containing the response state of the device, the response CMS message is encoded through the PER encoding and decoding module and then is sent back to the edge computing host, the sensor array arranged beside the primary device collects the execution state of the primary device at a first preset time period and sends the execution state to the edge computing host, the CMS client on the edge computing host decodes the collected data through the PER encoding and decoding module, the edge computing host uploads the decoded data to the debugging host, and the debugging host receives the data uploaded by the edge computing host and judges whether there is an execution timeout or a state abnormality, if there is, an alarm is given.

2. The substation one-key sequential control synchronous debugging method based on the autonomously controllable CMS protocol of claim 1, characterized in that, The method further comprises the following steps of debugging precision optimization and model iteration: the execution accuracy of the primary device is calculated after each debugging, if the execution accuracy is less than a preset accuracy threshold, the debugging host analyzes the deviation reasons and classifies and counts the deviation reasons, the deviation data is accumulated, and the synchronous debugging model is fine-tuned by using a gradient descent algorithm.

3. The substation one-key sequential control synchronous commissioning method based on the autonomously controllable CMS protocol of claim 1, characterized in that, The method further includes: if there are multiple debugging tasks, then using formulas respectively. Calculate the priority of each debugging task, where Prioritize debugging tasks. The correlation weight between the control ticket corresponding to the commissioning task and the current power grid operating conditions. The correlation coefficient is... Weighting of wait time for debugging tasks. Waiting time for debugging tasks, The importance weight of the primary equipment corresponding to the debugging task. The importance coefficient of the primary equipment corresponding to the commissioning task; The priority queue algorithm is adopted in the scheduling, and the debugging task with high priority is preferentially put into the execution queue.

4. The substation one-key sequential control synchronous commissioning method based on the autonomously controllable CMS protocol of claim 1, characterized in that, The method further comprises: calculating a dynamic corrected commissioning error by formula wherein is the dynamic corrected commissioning error, is the measured commissioning error, is a temperature influence weight, is a commissioning environment temperature change amount, is an electromagnetic noise influence weight, is an electromagnetic noise intensity; When When the error is greater than a preset error threshold, the debugging host automatically adjusts the debugging instruction parameters: if the error is caused by excessively high temperature, i.e. When the error is caused by excessively large electromagnetic noise, i.e. N is greater than a first preset intensity threshold, the debugging instruction verification intensity is enhanced.

5. The substation one-key sequential control synchronous commissioning method based on the autonomously controllable CMS protocol of claim 1, characterized in that, In the autonomous controllable CMS client development step, a communication fault tolerance mechanism is further included: after the CMS client sends a request CMS message, a software timeout timer is started, if no response is received from the CMS server within the timeout, a retransmission mechanism is automatically triggered, the number of retransmissions is less than or equal to a preset number K, and an exponential backoff algorithm is used for retransmission interval; if K times of retransmission all fail, the CMS client automatically reads the backup CMS server list configured locally, detects the online status of the backup CMS server through the ICMP protocol, selects the backup CMS server with the smallest delay to establish a new connection, and the switching time is less than or equal to a preset time threshold; at the same time, the CMS client records the communication failure information to the local log, and every time the first preset number of fault data is accumulated, the decision tree algorithm is used to update the communication link selection model.

6. The substation one-key sequential control synchronous commissioning method based on the autonomically controllable CMS protocol according to claim 1, characterized in that, In the multi-device synchronous debugging step, a multi-interval collaborative debugging is further included: for multiple adjacent intervals in the substation, one Beidou dual-mode time service module is deployed in each interval, and time synchronization of each interval is realized through the PTP protocol; before the debugging instruction is issued, the edge computing host reads the interval association matrix, appends the interval collaborative identifier to the debugging instruction, and calculates the interval order according to the logic defined by the association matrix; when the debugging instruction is issued, the edge computing host uniformly schedules according to the collaborative logic: the first interval debugging instruction is issued first, after receiving the feedback of the first interval execution completion, the second interval debugging instruction is issued after a first preset time delay, and the same is repeated.

7. The substation one-key sequential control synchronous commissioning method based on the autonomically controllable CMS protocol according to claim 1, characterized in that, In the real-time collection and feedback of the debugging state step, an environment parameter adaptive adjustment is further included: a multi-parameter environment sensor is deployed in the debugging area, and the multi-parameter environment sensor collects data at a second preset time period and uploads the data to the debugging host; the debugging host triggers an adaptive strategy according to the environment parameters: when the temperature is greater than a preset temperature threshold, the CPU main frequency of the debugging host is automatically reduced, and the debugging host cooling fan is started; when the humidity is greater than a preset humidity threshold, the sensor moisture-proof heating plate is started; when the electromagnetic noise is greater than a second preset intensity threshold, the CMS message verification strength is increased, and the CMS message transmission rate is reduced.

8. The substation one-key sequential control synchronous debugging method based on the autonomically controllable CMS protocol of claim 1, characterized in that, A debugging fault self-repairing step is further included: the debugging host carries a fault diagnosis model, which monitors the fault type of the target device in real time, for communication faults, the debugging host automatically restarts the CMS client communication module, if the restart is invalid, the backup communication link is switched to; for execution faults, the target device state reset instruction is first sent through the CMS client, after resetting, the original debugging instruction is re-executed after waiting for a second preset time, if it still fails, an artificial intervention prompt is generated; For parameter faults, the debugging host automatically reads the rated parameter library of the target device, reconfigures the control parameters according to a preset proportion of the rated value, and marks the parameter correction record; After each fault repair, the repair process is recorded to the fault repair knowledge base, and every time the second preset number of fault records is added, the fault diagnosis model is updated using the random forest algorithm.

9. The substation one-key sequential control synchronous commissioning method based on the autonomically controllable CMS protocol according to claim 1, characterized in that, Further comprising a debugging energy consumption optimization step, calculating debugging total energy consumption by formula , wherein is debugging total energy consumption, is the number of primary equipment participating in debugging, is the running power of the i-th primary equipment, is the running time of the i-th primary equipment, is the standby power of the debugging host, is the total debugging time, and according to , the running timing of the primary equipment is adjusted according to the comparison result with the preset threshold value: when ≤ threshold value, the original timing is executed; when > threshold value, the start time of non-critical primary equipment is optimized, and the simultaneous running time of the primary equipment is reduced.

10. A transformer substation one-key sequential control synchronous debugging system based on an autonomous controllable CMS protocol, characterized in that, The system comprises a debugging host, an edge computing host and an interval layer device; the debugging host is in communication connection with the edge computing host; a CMS client is arranged on the edge computing host, a CMS server is arranged on the interval layer device, and the CMS client and the CMS server are in communication connection; the CMS client and the CMS server are both integrated with a PER encoding and decoding module based on an ASN.1 standard. The system realizes the substation one-key sequential control synchronous debugging by using the method in any one of claims 1-9.

Images