IEC104 power distribution automation terminal debugging system and method

Abstract

The invention provides a power distribution automation terminal debugging system and method based on an IEC104 protocol, and the method comprises the steps: inputting an IP address, a port number and a channel address of a device as parameters after a manufacturer selection module selects a manufacturer name, transmitting IEC104 message data information through a message communication module, a message sending module and a message receiving module, and transmitting the IEC104 message data information to a power distribution automation terminal. An IEC104 message is analyzed through a man-machine interaction interface, the original message and the message meaning represented by each byte of each original message are displayed through the man-machine interaction interface, finally, an information value in the analyzed IEC104 message corresponds to a substation point table, and real-time feedback and display of data are achieved. And meanwhile, a debugging log is recorded. And the method is adaptive to a plurality of manufacturers, so that the same software is used to debug terminal equipment of different manufacturers. The problem that multiple sets of software are used when a user debugs multiple manufacturer devices is solved, and the daily working efficiency is improved.

Description

Technical Field

[0001] The invention belongs to the technical field of IEC104 distribution automation terminals, and in particular relates to an IEC104 distribution automation terminal debugging system and method. Background Art

[0002] With the continuous development and growth of the power system, the power equipment market is becoming increasingly prosperous. Different manufacturers have developed a wide variety of IEC104 terminal devices based on their respective technical advantages and market positioning. These devices have certain differences in functions, performance, communication methods, etc., which brings challenges to the integration, commissioning and maintenance of the power system. In practical applications, a power system often uses IEC104 terminal devices from multiple manufacturers at the same time. For example, in a substation automation system, there may be relay protection devices, measurement and control devices, telecontrol communication devices, etc. from different manufacturers, all of which need to communicate with the dispatching center through the IEC104 protocol. Therefore, in order to ensure the stable operation of the entire power system, a terminal debugging system that can adapt to equipment from multiple manufacturers is required.

[0003] As an international standard telecontrol communication protocol, IEC104 protocol has clear provisions on the overall framework and basic functions, but allows a certain degree of flexibility in specific implementation details. Different manufacturers may make some personalized designs and extensions based on their own product characteristics and needs on the basis of following the protocol standards. For example, there may be some differences between different manufacturers in terms of message format, data encoding method, control domain definition, etc. In addition, some manufacturers may also add some customized functions and commands based on the protocol to meet specific application requirements. These differences and diversity make it difficult for traditional single-manufacturer dedicated debugging tools to meet actual needs, and there is an urgent need for a universal debugging system that is compatible with the implementation methods of different manufacturers.

[0004] In modern power systems, system integration and interoperability are emphasized. Equipment from different manufacturers needs to be able to work together on a unified platform to achieve data sharing and interaction. As a bridge connecting equipment from different manufacturers and commissioning personnel, the IEC104 terminal debugging system must have the ability to adapt to equipment from multiple manufacturers to ensure the smooth integration of the system. If there is no debugging system that can adapt to multiple manufacturers, then during the system integration process, the commissioning personnel will have to face various dedicated debugging tools provided by different manufacturers, which will not only increase the complexity and workload of debugging, but may also lead to problems such as low debugging efficiency and increased error rate due to incompatibility between tools.

[0005] Power equipment technology is constantly developing and updating, and new manufacturers and products are constantly emerging. In order to adapt to market changes and technological advances, the IEC104 terminal debugging system also needs to be continuously upgraded and improved to meet the adaptation requirements of new manufacturers' equipment. At the same time, with the development of smart grids, higher requirements are also put forward for the application of IEC104 protocols, such as the continuous improvement of requirements for real-time, reliability, security, etc. This also prompts the debugging system to continue to innovate and improve in order to better adapt to the new technical environment and application requirements. Summary of the invention

[0006] In view of this, the purpose of the present invention is to provide an IEC104 distribution automation terminal debugging system and method to solve the problem of users using multiple sets of software to debug equipment from multiple manufacturers, thereby improving daily work efficiency.

[0007] In a first aspect, an embodiment of the present invention provides an IEC104 distribution automation terminal debugging system, comprising:

[0008] Manufacturer selection module: used to provide a list of multiple adapted device manufacturers for users to choose from;

[0009] Device connection module: used to read the parameters input by the user and connect the device to the IEC104 slave station;

[0010] Message communication module: used to establish TCP / IP connection and realize the reception and transmission of IEC104 messages;

[0011] IEC104 message sending module: used to construct IEC104 messages for time synchronization, general call, remote adjustment, and remote measurement, and control the message sending process;

[0012] IEC104 message receiving module: receives IEC104 messages sent by terminal equipment, classifies and stores the messages using corresponding data structures, and sends the IEC104 messages to the message parsing module or saves them in the message storage library;

[0013] IEC104 message parsing module: classifies and parses IEC104 messages through message parsing functions;

[0014] Human-computer interaction interface: used to display the functions of each module in a centralized manner. Testers can read the message information sent and received, as well as the remote signaling, telemetry, and remote adjustment data through the human-computer interaction interface, and modify the parameters through the write-set function;

[0015] After the manufacturer name is selected through the manufacturer selection module, the IP address, port number and channel address of the device are input as parameters, and the IEC104 message data information is transmitted through the message communication module, the message sending module and the message receiving module. Then, the original message and the message meaning represented by each byte of each original message are displayed through the human-computer interaction interface. Finally, the information value in the parsed IEC104 message can be matched with the substation table to realize real-time feedback and display of data.

[0016] Preferably, the device connection module initializes the relevant parameters of the IEC104 master station through the connection processing function, creates a connection object with the device terminal, and performs corresponding processing according to different connection events;

[0017] The device successfully establishes a connection with the IEC104 slave station, sends a signal to notify other modules of the current connection status, and records the log information of the successful connection. At this time, the log information includes the connection time, LED status and event type;

[0018] The device disconnects from the IEC104 slave station, sends a signal to notify other modules of the current connection status, and records the log information of the disconnection. The log information includes the disconnection time, LED status and event type.

[0019] Preferably, the message communication module realizes communication with the IEC104 slave device through an integrated library function, and processes received application layer messages through a callback function, wherein the callback function allows a user to pass application-specific context information by setting a universal reference parameter.

[0020] Preferably, the IEC104 message parsing module responds to the custom batch loading command through a message parsing function; wherein, by determining the payload size of the application service data unit and extracting data in the message according to a specific page type, during the data extraction process, the message parsing function combines the byte data into a complete value array in a specific order.

[0021] An IEC104 distribution automation terminal debugging method, comprising:

[0022] The user clicks the OK button, selects the manufacturer name, and sets the corresponding configuration file path according to the device manufacturer selected by the user;

[0023] Establish a TCP connection between the simulated IEC104 master station and the device terminal;

[0024] Ensure the establishment of TCP connection, and carry out message communication process through integrated library functions, including message generation, message sending, and message receiving, specifically generating IEC104 messages for time synchronization, general call, remote adjustment, and telemetry;

[0025] The received IEC104 message is parsed, and the corresponding entity is identified based on the address information in the message. After the entity is determined, the data is refreshed by calling the function, and the data information is actually fed back and displayed through the human-computer interaction interface.

[0026] Preferably, the message parsing process includes:

[0027] Identify the start character and determine the start position of the message;

[0028] Read the value of the two bytes following the start character to determine the length of the entire message;

[0029] Parse the control field according to the message type. The message types include U frame, S frame, and I frame. The control field contains the sending sequence number, receiving sequence number, transmission reason, and function type.

[0030] Analyze each byte of the control field and extract the corresponding control information;

[0031] Parse the application service data unit event, which includes a type identifier, a variable structure qualifier, and a transmission reason.

[0032] Preferably, the message sending process includes:

[0033] Use the network programming library to establish a TCP connection between the simulated master station and the device terminal;

[0034] After the TCP connection is successful, the user clicks the button or option to send the U frame start command through the human-computer interaction interface to generate a start U frame;

[0035] The simulated master station sends the generated startup U frame to the device terminal, and the user receives the startup command confirmation frame from the device terminal through the human-computer interaction interface;

[0036] After confirming receipt of the start command confirmation frame, the user sends a general call command, generating a general call command message I frame.

[0037] The embodiments of the present invention bring the following beneficial effects:

[0038] The present invention can receive telemetry and telesignal messages sent by terminal equipment and record debugging logs at the same time. It is also compatible with multiple manufacturers, and can use the same software to debug terminal equipment from different manufacturers. The debugging systems adapted to multiple manufacturers can unify the debugging process and method, reduce duplication of work, and improve debugging efficiency.

[0039] In actual applications, when communication failures or equipment abnormalities occur, a debugging system that is compatible with multiple manufacturers can quickly diagnose and analyze equipment from different manufacturers, helping debugging personnel to quickly locate the problem and shorten troubleshooting time.

[0040] For users such as power system integrators and operation and maintenance units, there is no need to purchase dedicated debugging tools for each manufacturer's equipment. Only one debugging system that is compatible with multiple manufacturers can meet the debugging needs of different equipment, thereby reducing tool procurement costs;

[0041] A debugging system that is compatible with multiple manufacturers can help ensure that devices from different manufacturers can communicate and work together normally in the same system, enhancing the compatibility and interoperability of the system. And when new devices or manufacturers need to be added to the system, a debugging system that is compatible with multiple manufacturers can be more easily expanded and upgraded to accommodate new devices and needs without requiring large-scale modifications to the entire debugging system.

[0042] Other features and advantages of the present invention will be described in the following description, and some features will become apparent from the description or understood by practicing the present invention. The purpose and other advantages of the present invention are realized and obtained by the structures particularly pointed out in the description, claims and drawings.

[0043] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 Functional module diagram of the IEC104 distribution automation terminal debugging system provided by an embodiment of the present invention;

[0045] Figure 2 A flowchart of the IEC104 protocol provided for an embodiment of the present invention;

[0046] Figure 3 An I-frame ASDU structure diagram provided for an embodiment of the present invention;

[0047] Figure 4 A structural diagram of a U frame control domain provided by an embodiment of the present invention;

[0048] Figure 5 A structural diagram of an S frame control field provided by an embodiment of the present invention;

[0049] Figure 6 A structural diagram of an I frame control field provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0050] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0051] To facilitate understanding of this embodiment, firstly, a IEC104 distribution automation terminal debugging system disclosed in an embodiment of the present invention is described in detail. Figure 1 As shown, it includes a manufacturer selection module, a device connection module, a message communication module, a message receiving module, a message sending module, a message parsing module and a human-computer interaction interface.

[0052] Manufacturer selection module: used to provide a list of multiple adapted device manufacturers for users to choose from;

[0053] Device connection module: used to read the parameters input by the user and connect the device to the IEC104 slave station;

[0054] Message communication module: used to establish TCP / IP connection and realize the reception and transmission of IEC104 messages;

[0055] IEC104 message sending module: used to construct IEC104 messages for time synchronization, general call, remote adjustment, and remote measurement, and control the message sending process;

[0056] IEC104 message receiving module: receives IEC104 messages sent by terminal equipment, classifies and stores the messages using corresponding data structures, and sends the IEC104 messages to the message parsing module or saves them in the message storage library;

[0057] IEC104 message parsing module: classifies and parses IEC104 messages through message parsing functions;

[0058] Human-computer interaction interface: used to display the functions of each module in a centralized manner. Testers can read the message information sent and received, as well as the remote signaling, telemetry, and remote adjustment data through the human-computer interaction interface, and modify the parameters through the write-set function;

[0059] After the manufacturer name is selected through the manufacturer selection module, the IP address, port number and channel address of the device are input as parameters, and the IEC104 message data information is transmitted through the message communication module, the message sending module and the message receiving module. Then, the original message and the message meaning represented by each byte of each original message are displayed through the human-computer interaction interface. Finally, the information value in the parsed IEC104 message can be matched with the substation table to realize real-time feedback and display of data.

[0060] Among them, the IEC 104 message consists of a fixed-length start character, a message length indicator, a control field, and an application service data unit ASDU. The start character is usually "68" and is used to mark the beginning of the message. The message length indicator occupies two bytes and indicates the length of the entire message, including the start character, length indicator, control field, and ASDU. The control field contains message control information, such as the sending sequence number, receiving sequence number, confirmation flag, etc. ASDU is an application service data unit, which contains actual application data, such as telemetry values, telesignaling status, remote control commands, etc.

[0061] Furthermore, the implementation method of the manufacturer selection module is as follows:

[0062] A dialog box is set up, which includes a label, a drop-down combo box and an OK button. The label prompts the user to "Please select the device manufacturer", and the drop-down combo box provides the manufacturer name options for the user to choose. The OK button is used to submit the user's selection;

[0063] After the user clicks the OK button, the dialog box will close and the corresponding configuration file path will be set according to the device manufacturer selected by the user. If the user selects the corresponding manufacturer name, the display and protocol variables will be set to the xml file path corresponding to the manufacturer. If the user does not select a device manufacturer and directly closes the dialog box, the program will return 1, indicating that the program has exited.

[0064] Furthermore, the device connection module is implemented based on the QT platform as follows:

[0065] In the connection processing function IEC104Master::cs104_connectionHandler, corresponding processing is performed according to different connection events, such as connection opening, connection closing, etc.

[0066] Specifically, when the connection event is CS104_CONNECTION_OPENED, it means that the device terminal has successfully established a connection with the IEC104 slave station. At this time, the device terminal will initialize relevant parameters, such as the read data counter, read data flag, etc., and set the connection status to IEC104_CONNECTED. At the same time, the device terminal sends a signal to notify other modules of the current connection status. If it is the first connection, the log information of successful connection is recorded; if it is a reconnection, the log information of successful reconnection is recorded. The log information includes the connection time, LED status and event type, where the green LED indicates normal, and the event type includes system operation alarm.

[0067] When the connection event is CS104_CONNECTION_CLOSED, it means that the device terminal is disconnected from the IEC104 slave station. At this time, the device terminal sets the connection state to IEC104_IDLE and sends a signal to notify other modules of the current connection state. At the same time, the device sets the active flag to false and records the log information of the disconnection, including the disconnection time, LED status and event type. The red LED light indicates an abnormality, and the event type includes system operation alarm.

[0068] It also defines two key member functions in the IEC104Master class: createMaster and connectSlave. The createMaster function is responsible for initializing the relevant parameters of the IEC104 master station and creating a connection object with the device terminal. Specifically,

[0069] Convert incoming IP addresses and port numbers into a format suitable for network communication;

[0070] Set the public address, device IP and port number of the IEC104 master station;

[0071] Initialize the connection status and retry flag;

[0072] Create a CS104_Connection object to manage the connection with the remote motor;

[0073] Enable debug output for easier problem tracking;

[0074] Obtain application layer parameters and link layer parameters, and configure link layer parameters, including connection establishment timeout, ASDU sending or test timeout, etc.;

[0075] Set the connection timeout and various event handling functions to handle the connection status changes accordingly. The connectSlave function is responsible for starting the asynchronous connection process with the remote machine and setting the connection status to connecting. This function attempts to establish a connection with the remote machine by calling the CS104_Connection_connectAsync method.

[0076] Through the above process, the device terminal can achieve a stable connection with the IEC104 slave station, and notify the relevant modules in time when the connection status changes to ensure the normal operation of the system.

[0077] Furthermore, the message communication module is implemented as follows: communication with the IEC104 slave device is realized through an integrated library function, and received application layer messages are processed through a callback function, wherein the callback function allows the user to pass application-specific context information by setting a universal reference parameter.

[0078] Specifically, in the process of sending requests and receiving responses, the module uses the CS101_Master_sendASDU and CS104_Connection_sendASDU functions to send application layer messages ASDU. These functions support sending system commands or process commands and help build data units that comply with IEC standards. The received ASDU is processed by the callback function asduReceivedHandler, which is triggered when the ASDU is received. In the callback function, the system will perform corresponding processing according to the type of ASDU. For example, for different types of data such as measurement values ​​and single-point information, the system will extract and print out relevant information, such as the object address (IOA) and data value.

[0079] In addition, the message communication module also installs the asduReceivedHandler callback function into the system through the CS101_Master_setASDUReceivedHandler function to ensure that all received ASDUs are processed in a timely manner. The callback handler provides a universal reference parameter that allows the user to pass application-specific context information, enhancing the flexibility and scalability of the module. When data needs to be actively requested, the communication module is able to send a read request. Although the IEC 60870 document does not recommend the routine use of cyclic data requests or polling, this function provides an easy way to obtain specific data. By calling the CS104_Connection_sendReadCommand function, the system can send a non-blocking read command and handle the response in the asduReceivedHandler callback.

[0080] Furthermore, the IEC104 message parsing module responds to the custom batch loading command through a message parsing function; wherein, by determining the payload size of the application service data unit and extracting the data in the message according to the specific page type, during the data extraction process, the message parsing function combines the byte data into a complete value array in a specific order.

[0081] Specifically, the core of the message parsing module consists of the respondSetMassPointCmd function, which responds to the custom bulk load command. The function first determines the payload size of the ASDU application service data unit and extracts the data in the message according to the specific page type. During the data extraction process, the function combines the byte data into a complete value array in a specific order for subsequent processing.

[0082] During the parsing process, the module will locate the corresponding C_SE_NB object based on the address information in the message, which represents a specific monitoring or control point. Once the object is located, the module will call the updateData method to update the data. The updateData method formats the extracted data according to different data types, such as float, list, string, hexadecimal, bit, and integer, and converts it into a user-friendly display format.

[0083] In the updateData method, the identification of data types is implemented through a switch statement, and each data type has corresponding processing logic. For example, for floating-point data, the method converts the byte array into a floating-point number and formats it as a string; for list data, the method converts the byte array into an integer value and selects the corresponding list item to display based on the value; and for hexadecimal data, the method directly converts the byte array into a hexadecimal string. The updated data is displayed on the corresponding element of the interface, realizing real-time feedback and display of the data. The design of the entire message parsing module ensures that the system can accurately and efficiently process messages from remote motors, providing users with an intuitive and real-time monitoring interface.

[0084] A debugging method for IEC104 distribution automation terminal, combined with Figure 2 As shown, including,

[0085] The user clicks the OK button, selects the manufacturer name, and sets the corresponding configuration file path according to the device manufacturer selected by the user;

[0086] Establish a TCP connection between the simulated IEC104 master station and the device terminal;

[0087] Ensure the establishment of TCP connection, and carry out message communication process through integrated library functions, including message generation, message sending, and message receiving, specifically generating IEC104 messages for time synchronization, general call, remote adjustment, and telemetry;

[0088] The received IEC104 message is parsed, and the corresponding entity is identified based on the address information in the message. After the entity is determined, the data is refreshed by calling the function, and the data information is actually fed back and displayed through the human-computer interaction interface.

[0089] Specifically, the message sending process includes:

[0090] Use the network programming library to establish a TCP connection between the simulated master station and the device terminal;

[0091] After the TCP connection is successful, the user clicks the button or option to send the U frame start command through the human-computer interaction interface, and the IEC104 message simulation sending module is triggered. The IEC104 message sending module generates a start U frame and sets the first control field to 0x07. The value of this control field indicates the specific function of the start command.

[0092] The simulated master station sends the generated startup U frame to the device terminal, and the user observes whether the startup command confirmation frame of the device terminal is received through the human-computer interaction interface;

[0093] If yes, then judge that the startup is successful; if no, then need to carry out error handling or retry and send the startup command.At this moment, the operator is ready to send the general call command, and produces the general call command message I frame.

[0094] The operator generates a general call command message through the message simulation sending module. This message is an I frame, in which the ASDU type identifier is set to 0x64 and the transmission reason is set to 0x07. These specific values ​​are used to represent specific attributes of the general call command in the IEC104 protocol. If the confirmation command is not received within a certain period of time, retry sending or error handling can be considered.

[0095] Furthermore, the message parsing process includes:

[0096] Identify the start character and search for "68" in the received byte stream to determine the start position of the message;

[0097] Read the value of the two bytes following the start character to determine the length of the entire message;

[0098] The control field is parsed according to the message type, which includes U frame, S frame, and I frame. For the I frame, the control field includes the sending sequence number, receiving sequence number, transmission reason, and function type.

[0099] Analyze each byte of the control field and extract the corresponding control information;

[0100] Parse the application service data unit event, which includes a type identifier, a variable structure qualifier, and a transmission reason.

[0101] Specifically, determine the type of data in the ASDU according to the type identifier, such as telemetry, telesignaling, and remote control. Parse the variable structure qualifier to understand the number and structure of the data objects. Read the transmission reason to understand the reason why the data is generated. According to the different data types, further parse the specific data content. For example, telemetry data may be a numerical value in a specific format, and telesignaling data may be a state represented by a Boolean value. If it is found during the parsing process that the message format does not comply with the IEC 104 standard, such as incorrect start characters, length indication mismatch, etc., record the error information and take corresponding processing measures, such as discarding the message and issuing an alarm. If there are errors in the parsed data, such as the value is out of range, the state is inconsistent, etc., record the error information and handle it according to the specific situation. It may be necessary to request to resend the data or perform troubleshooting.

[0102] Combination Figure 3-Figure 6 , introduce the composition of the application layer data unit APDU of IEC60870-5-104:

[0103] The data unit structure of the IEC60870-5-104 protocol is based on a simplified version of the ISO-OSI model, in which the data frame only contains three layers: physical layer, link layer and application layer. In IEC60870-5-104, the data unit of the application layer is called APDU, which consists of two parts: application protocol control information APCI and application service data unit ASDU.

[0104] The basic structure of APDU has two forms, one contains only APCI, and the other contains an APCI and at least one ASDU. The APCI part occupies 6 bytes, including the start byte 0x68 (decimal 104, indicating IEC104 message), the total length of APDU, and four control field bytes. The following is a restatement of the structure:

[0105] The structure of the application layer data unit APDU of IEC60870-5-104 is as follows:

[0106] The starting character is 0x68, which is 104 in decimal, indicating that the message complies with the IEC104 standard.

[0107] The second byte indicates the length of the APDU, which is the remainder after removing the first two bytes, including the total length of the control field and the ASDU. The maximum length of the APDU does not exceed 255 bytes, so its length should be between 4 and 253 bytes.

[0108] The control field consists of four bytes, which contain the message sending and receiving sequence information, ensure the reliable transmission of the message, and contain control information such as message start, stop and link test. According to the different control fields, the message is divided into three types: information transmission frame I frame, unnumbered control function frame U frame and numbered monitoring function frame S frame.

[0109] U frames are used to control the start and stop of message transmission and link testing.

[0110] The I frame carries ASDU information, and its control field includes the send and receive sequence numbers.

[0111] The S frame is used for monitoring functions, and its control field format determines its function.

[0112] ASDU only appears in I frame and consists of data unit identification and at least one information body. The data unit identification includes the following parts:

[0113] Type identifier: One byte used to identify the type of ASDU.

[0114] Variable structure qualifier: A byte that indicates the number and arrangement of information bodies.

[0115] Transmission reason: two bytes, the first byte identifies the transmission reason, and the second byte is usually set to 0.

[0116] Information public address: two bytes used to identify the public address of the information, ranging from 0 to 255.

[0117] In the I frame of the IEC60870-5-104 protocol, the information body of the application service data unit ASDU mainly includes three elements: information body address, information element and information body time stamp. The information body address usually occupies three bytes of space. When the number of information bodies exceeds one, there are two ways to organize the information body: the first way is that the information body address is continuous. In this case, only the first information body contains specific address information, and subsequent information bodies do not contain address information. Their addresses are inferred by adding 1 to the address of the previous information body. The second way is that the information body address is discontinuous, that is, the information body address is scattered. In this case, each information body needs to contain its address information independently.

[0118] It should be noted that, in this article, the terms "comprises", "includes" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or apparatus that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or apparatus.

[0119] While embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the invention, and that the scope of the invention is defined by the appended claims and their equivalents.

Claims

1. A distribution automation terminal debugging system based on IEC104 protocol, characterized in that: include: Manufacturer selection module: used to provide a list of multiple adapted device manufacturers for users to choose from; Device connection module: used to read the parameters input by the user and connect the device to the IEC104 slave station; Message communication module: used to establish TCP / IP connection and realize the reception and transmission of IEC104 messages; IEC104 message sending module: used to construct IEC104 messages for time synchronization, general call, remote adjustment, and remote measurement, and control the message sending process; IEC104 message receiving module: receives IEC104 messages sent by terminal equipment, classifies and stores the messages using corresponding data structures, and sends the IEC104 messages to the message parsing module or saves them in the message storage library; IEC104 message parsing module: classifies and parses IEC104 messages through message parsing functions; Human-computer interaction interface: used to display the functions of each module in a centralized manner. Testers can read the message information sent and received, as well as the remote signaling, telemetry, and remote adjustment data through the human-computer interaction interface, and modify the parameters through the write-set function; After the manufacturer name is selected through the manufacturer selection module, the IP address, port number and channel address of the device are input as parameters, and the IEC104 message data information is transmitted through the message communication module, the message sending module and the message receiving module. Then, the original message and the message meaning represented by each byte of each original message are displayed through the human-computer interaction interface. Finally, the information value in the parsed IEC104 message can be matched with the substation table to realize real-time feedback and display of data.

2. The distribution automation terminal debugging system according to claim 1, characterized in that: The device connection module initializes the relevant parameters of the IEC104 master station through the connection processing function, creates a connection object with the device terminal, and performs corresponding processing according to different connection events; The device successfully establishes a connection with the IEC104 slave station, sends a signal to notify other modules of the current connection status, and records the log information of the successful connection. At this time, the log information includes the connection time, LED status and event type; The device disconnects from the IEC104 slave station, sends a signal to notify other modules of the current connection status, and records the log information of the disconnection. The log information includes the disconnection time, LED status and event type.

3. The distribution automation terminal debugging system according to claim 1, characterized in that: The message communication module realizes communication with the IEC104 slave device through an integrated library function, and processes received application layer messages through a callback function. The callback function allows the user to pass application-specific context information by setting a universal reference parameter.

4. The distribution automation terminal debugging system according to claim 1, characterized in that: The IEC104 message parsing module responds to the custom batch loading command through the message parsing function; Among them, by determining the payload size of the application service data unit and extracting data in the message according to the specific page type, during the data extraction process, the message parsing function combines the byte data into a complete value array in a specific order.

5. A method for using the distribution automation terminal debugging system based on the IEC104 protocol according to claim 1, characterized in that: include: The user clicks the OK button, selects the manufacturer name, and sets the corresponding configuration file path according to the device manufacturer selected by the user; Establish a TCP connection between the simulated IEC104 master station and the device terminal; Ensure the establishment of TCP connection, and carry out message communication process through integrated library functions, including message generation, message sending, and message receiving, specifically generating IEC104 messages for time synchronization, general call, remote adjustment, and telemetry; The received IEC104 message is parsed, and the corresponding entity is identified based on the address information in the message. After the entity is determined, the data is refreshed by calling the function, and the data information is actually fed back and displayed through the human-computer interaction interface.

6. The distribution automation terminal debugging method according to claim 5, characterized in that: The message parsing process also includes: Identify the start character and determine the start position of the message; Read the value of the two bytes following the start character to determine the length of the entire message; Parse the control field according to the message type, which includes U frame, S frame, and I frame; Analyze each byte of the control field and extract the corresponding control information; Parse the application service data unit event, which includes a type identifier, a variable structure qualifier, and a transmission reason.

7. The distribution automation terminal debugging method according to claim 5, characterized in that: The message sending process also includes: Use the network programming library to establish a TCP connection between the simulated master station and the device terminal; After the TCP connection is successful, the user clicks the button or option to send the U frame start command through the human-computer interaction interface to generate a start U frame; The simulated master station sends the generated startup U frame to the device terminal, and the user receives the startup command confirmation frame from the device terminal through the human-computer interaction interface; After confirming receipt of the start command confirmation frame, the user sends a general call command, generating a general call command message I frame.

Images