Equipment debugging method and system

Abstract

The invention relates to an equipment debugging method and system. The method comprises the steps that under the condition that connection with an information board is established, protocol specification data, sent by the information board, of to-be-debugged equipment is received, the information board is connected with the to-be-debugged equipment, a debugging configuration file matched with the to-be-debugged equipment is searched in a preset configuration database based on the protocol specification data, and the to-be-debugged equipment is debugged according to the debugging configuration file. The debugging configuration file comprises a protocol content configuration file and a user interface configuration file, loading a debugging interface matched with the to-be-debugged device based on the user interface configuration file, obtaining debugging data input by a user through the debugging interface, coding the debugging data based on the protocol content configuration file, and sending the coded debugging data to the to-be-debugged device. And sending the coded debugging data to the to-be-debugged equipment through the information board. By adopting the method, the debugging efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the technical field of device debugging, and in particular to a device debugging method, system, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] With the continuous development of the intelligent manufacturing industry, during product engineering debugging, after-sales problem handling, or product development, operators often need to debug the system to help users view the product's operating status, operating parameter settings, etc.

[0003] In traditional debugging solutions, the debugging system is usually developed for the products or devices it serves, and only supports fixed protocol data for a few fixed types of products. When new types of devices or products need to be supported, the debugging system needs to be changed to meet the debugging requirements.

[0004] In the above-mentioned traditional solution, when the protocol data of the device or product that needs to be debugged changes, the debugging system itself needs to be modified and developed. Especially during the product development process, when the protocol data has not yet been determined, the debugging system needs to be frequently changed, which brings additional development workload and reduces debugging efficiency. Summary of the Invention

[0005] Based on this, it is necessary to provide a device debugging method, system, apparatus, computer equipment, computer-readable storage medium and computer program product that can improve debugging efficiency in response to the above technical problems.

[0006] In a first aspect, the present application provides a device debugging method, comprising:

[0007] When a connection is established with the information board, receiving protocol data of the device to be debugged sent by the information board, the information board being connected to the device to be debugged;

[0008] Based on the protocol specification data, searching a preset configuration database for a debugging configuration file that matches the device to be debugged, the debugging configuration file including a protocol content configuration file and a user interface configuration file;

[0009] Based on the user interface configuration file, loading a debugging interface that matches the device to be debugged, and acquiring debugging data input by a user through the debugging interface;

[0010] The debugging data is encoded based on the protocol content configuration file, and the encoded debugging data is sent to the device to be debugged through the information board.

[0011] In one embodiment, encoding the debugging data based on the protocol content configuration file and sending the encoded debugging data to the device to be debugged through the information board includes:

[0012] Based on the protocol content configuration file, construct a protocol data model that matches the device to be debugged;

[0013] Calling the protocol data model, encoding the debugging data, and obtaining encoded debugging data;

[0014] Encapsulating the encoded debugging data in a preset tunnel frame to form a data tunnel frame;

[0015] The data tunnel frame is sent to the information board, so that the information board extracts the encoded debugging data from the data tunnel frame and sends it to the device to be debugged.

[0016] In one embodiment, the method further comprises:

[0017] receiving debugging result data sent by the device to be debugged through the information board;

[0018] The protocol data model is called, the debugging result data is parsed, and the parsed debugging result data is displayed on the debugging interface.

[0019] In one embodiment, the configuration database includes a local configuration database and a remote configuration database, and the step of searching a preset configuration database based on the protocol specification data to obtain a debugging configuration file that matches the device to be debugged includes:

[0020] Based on the protocol data, preferentially searching the local configuration database for a debugging configuration file that matches the device to be debugged;

[0021] When no debugging configuration file matching the device to be debugged is found in the local configuration database, a debugging configuration file matching the device to be debugged is searched in the remote configuration database.

[0022] In one embodiment, the debugging configuration file is encrypted and stored in the local configuration database or the remote configuration database, and searching a preset configuration database for a debugging configuration file that matches the device to be debugged based on the protocol specification data includes:

[0023] Based on the protocol specification data, searching a preset configuration database for an encrypted debugging configuration file that matches the device to be debugged;

[0024] The encrypted debugging configuration file is decrypted to obtain a debugging configuration file that matches the device to be debugged.

[0025] In one embodiment, the method further includes: the protocol content configuration file and the user interface configuration file are described as XML configuration files, and different types of users have hierarchical access rights and modification rights for the protocol content configuration file and the user interface configuration file.

[0026] In a second aspect, the present application further provides a device debugging system, the device debugging system comprising a debugging device and an information board connected to each other, the information board being connected to the device to be debugged;

[0027] The information board is configured to read and send the protocol data of the device to be debugged to the debugging device, and receive the encoded debugging data sent by the debugging device, and send the encoded debugging data to the device to be debugged to debug the device;

[0028] The debugging device is configured to receive protocol specification data of the device to be debugged, and based on the protocol specification data, search a debugging configuration file matching the device to be debugged in a preset configuration database, wherein the debugging configuration file includes a protocol content configuration file and a user interface configuration file; based on the user interface configuration file, load a debugging interface matching the device to be debugged, and obtain debugging data input by a user through the debugging interface; based on the protocol content configuration file, encode the debugging data, and send the encoded debugging data to the information board.

[0029] In a third aspect, the present application further provides a device debugging apparatus, comprising: a data receiving module, a configuration search module, a debugging interface loading module, and a debugging module, wherein:

[0030] A data receiving module, configured to receive protocol data of a device to be debugged sent by an information board when a connection is established with the information board, the information board being connected to the device to be debugged;

[0031] A configuration search module is used to search for a debugging configuration file that matches the device to be debugged in a preset configuration database based on the protocol specification data. The debugging configuration file includes a protocol content configuration file and a user interface configuration file.

[0032] The debugging interface loading module is used to load the debugging interface that matches the device to be debugged based on the user interface configuration file, and obtain the debugging data entered by the user through the debugging interface;

[0033] The debugging module is used to encode the debugging data based on the protocol content configuration file, and send the encoded debugging data to the device to be debugged through the information board.

[0034] In a fourth aspect, the present application further provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps in the above-mentioned device debugging method embodiment when executing the computer program.

[0035] In a fifth aspect, the present application further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned device debugging method embodiment are implemented.

[0036] In a sixth aspect, the present application also provides a computer program product, including a computer program, which implements the steps in the above-mentioned device debugging method embodiment when executed by a processor.

[0037] The above-mentioned device debugging method, system, apparatus, computer equipment, computer-readable storage medium and computer program product are different from traditional debugging systems that need to be repeatedly modified when facing new equipment or protocol changes, resulting in low debugging efficiency. After establishing a connection with the information board, this solution obtains the protocol specification data of the device to be debugged through the information board, and can then search for the protocol content configuration file and user interface configuration file that match the device to be debugged in the preset configuration database. Based on the user interface configuration file, it can load the debugging interface that matches the device to be debugged, and obtain the debugging data entered by the user through the debugging interface, and encode the debugging data based on the protocol content configuration file, and send the encoded debugging data to the device to be debugged through the information board. This dynamic configuration mechanism for the device to be debugged can adapt to devices to be debugged with different protocols without modifying the core code, shortening the debugging cycle and improving debugging efficiency. In addition, by isolating the device to be debugged through the information board, it can reduce incompatibility problems caused by direct contact with the device to be debugged, further improving debugging efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following briefly introduces the drawings required for use in the embodiments of the present application or related technical descriptions. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying any creative work.

[0039] Figure 1 This is an application environment diagram of a device debugging method in one embodiment;

[0040] Figure 2Schematic diagram of a device debugging method according to an embodiment;

[0041] Figure 3 A schematic flow chart of a device debugging method according to another embodiment;

[0042] Figure 4 1 is a flow chart of a device debugging method in another embodiment;

[0043] Figure 5 A schematic diagram of a flow chart of a device debugging method in a detailed embodiment;

[0044] Figure 6 A structural block diagram of a device debugging system in one embodiment;

[0045] Figure 7 It is a structural block diagram of a device debugging system in another embodiment;

[0046] Figure 8 is a structural block diagram of a debugging device in one embodiment;

[0047] Figure 9 This is a structural block diagram of a device debugging apparatus in one embodiment;

[0048] Figure 10 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0049] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0050] The device debugging method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown, the information board 110 communicates with the debugging device 120 via a network, the information board 110 is connected to the device to be debugged, and the data storage system can be integrated on the debugging device 120 or placed on the cloud or other network servers.

[0051] Specifically, the information board 110 can be externally connected to the device to be debugged or embedded within it. The Modbus communication protocol can be used between the device to be debugged and the information board 110. The protocol data of the device to be debugged is provided in a Modbus protocol field, which the information board 110 can obtain through periodic polling. Then, when the information board 110 is connected to the debugging device 120, the information board 110 proactively sends the protocol data of the device to be debugged to the debugging device 120. Based on the protocol data, the debugging device 120 searches a preset configuration database for a debugging configuration file that matches the device to be debugged. The debugging configuration file includes a protocol content configuration file and a user interface configuration file. The preset configuration database can be stored locally on the debugging device 120 or on a remote server. Then, based on the user interface configuration file, the debugging device 120 loads a debugging interface that matches the device to be debugged, obtains debugging data entered by the user through the debugging interface, encodes the debugging data based on the protocol content configuration file, and sends the encoded debugging data to the device to be debugged via the information board 110.

[0052] The debugging device 120 may be an independent physical server or a physical terminal with debugging software installed.

[0053] In an exemplary embodiment, Figure 2 As shown, a device debugging method is provided, which is applied to Figure 1 The debugging device 120 in FIG. 1 is used as an example to illustrate the method, which includes the following steps:

[0054] S100 , when a connection is established with an information board, receiving protocol data of a device to be debugged sent by the information board.

[0055] The information board is a hardware module used to establish a physical connection and exchange data with the device to be debugged. It can be a microserver, used to collect data from the device to be debugged and exchange data with the debugging device. It is connected to the device to be debugged. The device to be debugged is an electronic device, instrument, or product that requires debugging, such as an air conditioner or inverter. Typically, different devices to be debugged use different protocol data. Protocol data characterizes the data encoding protocol used by the device to be debugged and includes the device's protocol identifier and protocol type. Protocol identifiers can be coded using a categorized encoding method, such as first major categories, then minor categories. Each category can be represented by two bytes, with the specific number of bytes depending on the number of product catalog types generated. This can result in the same protocol identifier for the same device to be debugged. Therefore, the protocol type can be used to distinguish different data encoding protocols used by the same device to be debugged. For example, all data items of a particular device to be debugged can be encoded according to the Modbus protocol or the CAN protocol. The protocol type can be used to distinguish different data encoding protocols used by the same device to be debugged.

[0056] For example, the information board can be external or embedded in the device to be debugged. After the information board establishes a connection with the device to be debugged via wired or wireless means, the information board begins to actively or passively receive the protocol data sent by the device to be debugged. For example, taking the debugging of a certain inverter product as an example, in this case, the information board is embedded inside the inverter, and the Modbus communication protocol is used between the inverter and the information board. The protocol data of the inverter is provided in a certain protocol field of Modbus, and the information board can obtain it in periodic polling. The information board is equivalent to the host computer of the inverter. The information board can first send a request frame, and the inverter will respond with a response frame. There is a dependency between the request frame and the response frame, so the information board can merge the request frame and the response frame into a tunnel data frame, which will be sent to the terminal or server where the debugging software is located. In addition, the information board can also perform preliminary processing on the received protocol data, such as format conversion and verification, and store it locally. Or when the information board is connected to the terminal or server where the debugging software is located (hereinafter referred to as the debugging device), the information board will actively upload the protocol data of the device to be debugged to the debugging device for further analysis and debugging operations.

[0057] S200 , based on the protocol specification data, searching a preset configuration database for a debugging configuration file that matches the device to be debugged.

[0058] The configuration database is a database system used to store debugging configuration files for various devices to be debugged. It also stores relevant index information to facilitate quick search and call of debugging configuration files. The debugging configuration file is a set of configuration data tailored for the device to be debugged, including a protocol content configuration file and a user interface configuration file. The protocol content configuration file defines the protocol rules and data formats that must be followed when debugging the device to be debugged, including but not limited to data encoding methods, data decoding methods, instruction formats, and other content. It can also include definitions of all data items in the protocol, such as the data category (e.g., Modbus coils), the data address within the category, the data encoding data type (e.g., 16-bit integer, 32-bit integer, floating point, etc.), the scaling factor (e.g., data is encoded and transmitted after being magnified 10 times), the name, the unit, and so on. Encoding debugging data according to the protocol rules and data format defined in the protocol content configuration file ensures that the debugging data can be correctly received and processed by the device to be debugged. The user interface configuration file defines the display and interaction methods of the debugging interface, including but not limited to the layout, element display, interaction logic and other contents of the debugging interface that matches the device to be debugged. It can also include two parts. One part is a set of common display content items of the user interface. This part does not change with the switching of the form and is the content that will always be displayed; the other part is a set of display content items of each form. Each content item includes a 3-tuple of item element type and displayed data item. The 3-tuple includes device address, data type, and data address. The 3-tuple corresponds to the data item in the protocol content configuration file.

[0059] For example, after obtaining the protocol data of the device to be debugged, the debugging device uses it as a query condition to search a preset configuration database. The configuration database searches for a debugging configuration file that matches the protocol data based on a preset matching algorithm, such as the protocol identifier, device model, protocol type, and data characteristics. Once a matching debugging configuration file is found, the debugging device extracts the protocol content configuration file and user interface configuration file from the configuration file for subsequent loading of the debugging interface and encoding of the debugging data.

[0060] S300: Based on the user interface configuration file, a debugging interface matching the device to be debugged is loaded, and debugging data input by the user through the debugging interface is acquired.

[0061] The debugging interface is a visual operation interface for users to interact with the device to be debugged. It is loaded and displayed according to the content defined in the user interface configuration file, providing users with an intuitive debugging operation entry, and users can directly enter debugging data through the debugging interface.

[0062] For example, after locating a user interface configuration file, the debugging device loads and generates a debugging interface that matches the device being debugged onto the debugging device's display terminal, such as a computer screen or touch screen, according to the interface layout, element display, and interaction logic defined therein. The user operates through the debugging interface and enters debugging data, including but not limited to device parameter settings and function instructions. The debugging device can then capture the user-entered debugging data in real time and store it in a specific data cache area or send it to the device being debugged via a message board.

[0063] S400 , encoding the debugging data based on the protocol content configuration file, and sending the encoded debugging data to the device to be debugged through the information board.

[0064] Following the above steps, after receiving the debug data input by the user, the debugging device encodes the debug data according to the data encoding rules defined in the protocol content configuration file. Specifically, the debug data is converted to the data format and encoding rules specified in the protocol content configuration file so that it can be recognized and processed by the device being debugged. After encoding, the encoded debug data is transmitted to the information board, which then sends the encoded debug data to the device being debugged via a connection channel, thereby completing the debugging operation on the device being debugged.

[0065] The above-mentioned device debugging method is different from the traditional debugging system that needs to be repeatedly modified when facing new devices or protocol changes, resulting in low debugging efficiency. This solution, after establishing a connection with the information board, obtains the protocol specification data of the device to be debugged through the information board, and can then search for the protocol content configuration file and user interface configuration file that match the device to be debugged in the preset configuration database. Based on the user interface configuration file, it can load the debugging interface that matches the device to be debugged, and obtain the debugging data entered by the user through the debugging interface, and encode the debugging data based on the protocol content configuration file, and send the encoded debugging data to the device to be debugged through the information board. This dynamic configuration mechanism for the device to be debugged can adapt to devices to be debugged with different protocols without modifying the core code, shortening the debugging cycle and improving debugging efficiency. In addition, by isolating the device to be debugged through the information board, it can reduce incompatibility problems caused by direct contact with the device to be debugged, further improving debugging efficiency.

[0066] In an exemplary embodiment, Figure 3 As shown, S400 includes:

[0067] S410 , constructing a protocol data model that matches the device to be debugged based on the protocol content configuration file, calling the protocol data model, encoding the debugging data, and obtaining the encoded debugging data.

[0068] S420: Encapsulate the encoded debugging data in a preset tunnel frame to form a data tunnel frame, and send the data tunnel frame to the information board.

[0069] The protocol data model is a structured model for encoding debugging data and parsing debugging result data for the device to be debugged, constructed based on the data encoding method, data decoding method, and instruction format defined in the protocol content configuration file. It abstractly defines the data organization, field meanings, and data processing flow. A tunnel frame is a pre-defined data frame format used to encapsulate encoded debugging data. A tunnel frame typically includes a frame header, a data portion, and a frame trailer. Encoded debugging data can be encapsulated in the data portion, and the frame header can contain a variety of function codes to indicate different tunnel frame types (login frame, device information frame, data frame, etc.). This solution utilizes a tunnel protocol to encapsulate communication data (such as Modbus / RS485 data) between the information board and the device to be debugged in the data portion of the tunnel data frame and transmit it to the debugging device. Similarly, communication data between the debugging device and the device to be debugged can also be encapsulated in the data portion of the tunnel data frame and transmitted to the information board. After receiving the data, the information board removes the frame header and directly sends it to the device to be debugged.

[0070] Specifically, after obtaining the protocol content configuration file, the debugging device parses the data encoding method, data decoding method, instruction format, and other information contained therein. Based on this information, the debugging device constructs a corresponding protocol data model. The protocol data model defines the various fields required for debugging data, their types, the logical relationships between fields, and the data processing flow. Once the model is constructed, the debugging device invokes the protocol data model and processes the debugging data entered by the user according to the rules defined in the protocol data model. For example, the debugging data is filled into the corresponding fields and the data is formatted, filled with fields, and logically processed according to the specified format. Ultimately, the data is encoded and conforms to the protocol specifications of the device being debugged.

[0071] Furthermore, after obtaining the encoded debugging data, the debugging device encapsulates it as the data portion into a preset tunnel frame. During the encapsulation process, the debugging device can fill in the frame header and frame trailer of the tunnel frame according to the transmission requirements and protocol specifications. After encapsulation is completed, a complete data tunnel frame is formed. The data tunnel frame is then transmitted to the information board, which then sends it to the device to be debugged. It is understandable that the protocol used by the information board and the debugging device to establish the output transmission channel is a tunnel protocol, which defines the rules for data encapsulation, transmission, and parsing. Through the tunnel protocol, it can achieve effective transmission of debugging-related data between the debugging software and the product to be debugged, and also gives the information board a certain degree of intelligent expansion capability. Therefore, when uploading the protocol specification data of the device to be debugged, the information board can also encapsulate the protocol specification data in the tunnel frame and then upload it.

[0072] If the information board does not perform any processing during data transmission and directly forwards the received data to the debugging device through transparent transmission, that is, the information board only serves as a data transmission conduit. If the debugging device is not connected to the information board (usually the two are connected only when debugging is required, and the information board does not connect to the debugging device during the daily operation of the debugging device), the information board cannot process and store key information of the debugging device during the daily operation. As a result, the debugging software cannot obtain the debugging device's data during the non-debugging period, which is not conducive to comprehensive analysis of product operation status and troubleshooting. The tunneling protocol method, however, enables the information board to process and store data according to actual needs during the data transmission process. When the information board is not connected to the debugging device, it can actively collect key information of the debugging device during daily operation (such as operating status, fault data, key parameters, etc.) and store this information locally. When the debugging device is connected, the information board can encapsulate the stored key information into tunnel data frames according to the tunneling protocol and send them to the debugging device for analysis and debugging.

[0073] In addition, the tunnel protocol also has good scalability. It can adapt to changes in the protocol data of the device to be debugged. When the protocol of the device to be debugged is expanded, if a fixed protocol conversion method is adopted, the information board program needs to be modified to realize the conversion and transmission of the new protocol data. If the tunnel protocol is adopted, it is only necessary to adjust the data encapsulation and parsing rules within the framework of the tunnel protocol to realize the transmission and processing of the new protocol data.

[0074] In this embodiment, by constructing a protocol data model and encoding the debugging data based on it, this method enhances the adaptability of the debugging device to different protocol specifications. When faced with different devices to be debugged, it is only necessary to construct the corresponding protocol data model according to their protocol content configuration files to achieve correct encoding of the debugging data. The encoded debugging data is encapsulated in a tunnel frame to form a data tunnel frame for transmission, thereby improving the versatility and debugging efficiency of the debugging device.

[0075] In an exemplary embodiment, Figure 3 As shown, the method further includes:

[0076] S500: Receive debugging result data sent by the device to be debugged through the information board, call the protocol data model, parse the debugging result data, and display the parsed debugging result data on the debugging interface.

[0077] The debugging result data is a set of data that is fed back by the device to be debugged after receiving and executing the debugging data, including the current operating status of the device, parameter changes, and the execution effect of the debugging operation. It represents the impact of the debugging operation on the device to be debugged.

[0078] Continuing with the above embodiment, after the device to be debugged completes the debugging operation, it generates debugging result data according to its internal protocol specifications and transmits the debugging result data through a connection channel with the information board. After receiving the debugging result data, the information board transmits it to the debugging device. The debugging device can call upon the protocol data model previously constructed based on the protocol content configuration file and parse the debugging result data according to the data parsing rules preset in the model. For example, it can perform data format restoration, field extraction, logical judgment, etc. on the debugging result data to obtain the parsed debugging result data. Finally, the debugging device presents the parsed debugging result data to the user in an intuitive manner according to the layout and display rules of the debugging interface.

[0079] In this embodiment, the debugging result data is parsed by calling the protocol data model, thereby improving the accuracy of the debugging result analysis. The parsed debugging result data is displayed on the debugging interface so that the user can quickly and clearly understand the debugging effect of the device, facilitating the user to adjust the debugging strategy in a timely manner and improving the debugging efficiency and quality.

[0080] In an exemplary embodiment, the configuration database includes a local configuration database and a remote configuration database, such as Figure 4 As shown, S200 includes:

[0081] S210 , based on the protocol data, preferentially searching a local configuration database for a debugging configuration file that matches the device to be debugged.

[0082] S220 : When no debugging configuration file matching the device to be debugged is found in the local configuration database, a debugging configuration file matching the device to be debugged is searched in the remote configuration database.

[0083] Among them, the local configuration database is a database stored in the local storage medium of the debugging device (such as a hard disk, solid-state drive), and the remote configuration database is a database system deployed on a remote server or cloud.

[0084] Continuing with the above embodiment, after obtaining the protocol data for the device to be debugged, the debugging device preferentially accesses the local configuration database through the local database interface and searches the local configuration database for a matching debugging configuration file. If the local configuration database search results are empty, meaning no debugging configuration file matching the device to be debugged is found, the debugging device can access the remote configuration database through the network interface for a secondary search. For example, using a specific search engine to search and match the remote configuration database, the debugging device can obtain a debugging configuration file matching the device to be debugged.

[0085] In this embodiment, in the process of searching for a debugging configuration file that matches the device to be debugged, through the local priority and remote supplement retrieval strategy, a matching debugging configuration file can be quickly found in the local configuration database for commonly used devices to be debugged, and a matching debugging configuration file can be quickly found in the remote configuration database for infrequently used devices to be debugged, thereby improving the applicability and speed regulation efficiency of the debugging device.

[0086] In an exemplary embodiment, the debugging configuration file is encrypted and stored in a local configuration database or a remote configuration database. S200 includes: based on the protocol specification data, searching for an encrypted debugging configuration file that matches the device to be debugged in a preset configuration database, decrypting the encrypted debugging configuration file, and obtaining a debugging configuration file that matches the device to be debugged.

[0087] The encrypted debug configuration file is ciphertext data generated by encrypting the debug configuration file using an encryption algorithm. This encryption can be performed during transmission or after the debug configuration file is stored. The encryption algorithm can be asymmetric, symmetric, or other algorithms, which are not limited here. It is understood that the key required to decrypt the encrypted debug configuration file can be stored in a hierarchical management mechanism, with only designated users having access to the key, thereby enhancing the security of the debug configuration file.

[0088] For example, the debugging device can invoke an encryption algorithm to encrypt the debugging configuration file in real time before storing it in the local configuration database, or the remote server can invoke an encryption algorithm to encrypt the debugging configuration file in real time before storing it in the remote configuration database. Furthermore, the debugging device can match the protocol specification data with the index field (plaintext portion) of the encrypted debugging configuration file stored in the local / remote database. For example, the debugging device can preferentially search the local configuration database for the encrypted debugging configuration file. If the encrypted debugging configuration file is not found, the remote configuration database is accessed. Once the encrypted debugging configuration file is found, decryption is not performed during transmission, thus preventing the leakage of plaintext data.

[0089] In this embodiment, by encrypting and storing the debugging configuration file in the configuration database, the security of the debugging configuration file can be effectively improved, the tampering and leakage of the debugging configuration file can be reduced, and the security and reliability of the debugging process can be improved.

[0090] In an exemplary embodiment, the method further includes: describing the protocol content configuration file and the user interface configuration file in XML configuration files, and different types of users have hierarchical access rights and modification rights for the protocol content configuration file and the user interface configuration file.

[0091] Among them, the XML configuration file is an Extensible Markup Language configuration file, which is a text format for storing and transmitting data. It can describe data through custom tags and hierarchical structures. Hierarchical access rights are based on different types of users (such as ordinary users, developers, administrators, etc.) to set different levels of read permissions for protocol content configuration files and user interface configuration files. For example, administrators can read more sensitive or critical information, while ordinary users can only read some basic information. Hierarchical modification permissions are similar to hierarchical access permissions. They are different levels of modification rights set for configuration files based on user types. For example, only administrators and developers have modification permissions and can edit, update, and perform other operations on the debugging configuration files.

[0092] For example, the protocol content configuration file and the user interface configuration file are written in XML format, and XML's tag structure can be used to organize data. When reading the protocol content configuration file and the user interface configuration file, the debugging device can parse the XML-formatted debugging configuration file using an XML parser, converting the tag structure into recognizable data objects. When the debugging configuration file needs to be updated, the XML parser can also be used to modify and regenerate the XML-formatted debugging configuration file.

[0093] In addition, the debugging device can pre-define multiple user types, such as ordinary users, developers, administrators, etc., and assign different levels of access rights and modification rights to each user type. For example, ordinary users only have access rights to some basic protocol information in the protocol content configuration file, and read-only rights to the user interface configuration file, and cannot modify the debugging configuration file. In addition to being able to access all information in the protocol content configuration file, developers also have modification rights to configuration items, and have modification rights to the layout and element attributes of the user interface configuration file. Administrators have full access rights and full modification rights to the protocol content configuration file and the user interface configuration file. When a user uses the debugging device, the user identity can be verified by using an account and password to determine the user type. The user's access rights and modification rights are determined based on the user type, and it is determined whether the user's access and modification operations on the debugging configuration file are allowed. If the operation exceeds the scope of authority, the debugging device will reject the operation and prompt the user that the authority is insufficient.

[0094] In this embodiment, XML configuration files are used to describe the protocol content configuration file and the user interface configuration file. This makes it easier for developers to write and modify the configuration files, and also allows for easy parsing and use across different systems and platforms, improving the versatility and maintainability of the debug configuration files. By restricting access and modification permissions for different users, this reduces the risk of debugging device failures or debugging errors caused by misoperation or malicious modification by ordinary users, thereby improving the security and stability of the debug configuration files.

[0095] In order to make a clearer explanation of the equipment debugging provided by this application, the following Figure 5 and one The detailed embodiment includes the following steps:

[0096] S501 : When a connection is established with an information board, protocol data of a device to be debugged sent by the information board is received.

[0097] S502 : Based on the protocol specification data, preferentially search the local configuration database for an encrypted debugging configuration file that matches the device to be debugged.

[0098] S503 : When no encrypted debugging configuration file matching the device to be debugged is found in the local configuration database, an encrypted debugging configuration file matching the device to be debugged is searched in the remote configuration database.

[0099] S504: decrypt the encrypted debugging configuration file to obtain a debugging configuration file that matches the device to be debugged.

[0100] S505 , based on the user interface configuration file, loading a debugging interface that matches the device to be debugged, and acquiring debugging data input by the user through the debugging interface.

[0101] S506 , constructing a protocol data model that matches the device to be debugged based on the protocol content configuration file, calling the protocol data model, encoding the debugging data, and obtaining the encoded debugging data.

[0102] S507: Encapsulate the encoded debugging data in a preset tunnel frame to form a data tunnel frame, and send the data tunnel frame to the information board.

[0103] S508 , receiving debugging result data sent by the device to be debugged through the information board, calling the protocol data model, parsing the debugging result data, and displaying the parsed debugging result data on the debugging interface.

[0104] It should be understood that, although the steps in the flowcharts of the above embodiments are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a portion of the steps in the flowcharts of the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily to be performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0105] Based on the same inventive concept, embodiments of the present application also provide a device debugging system for implementing the aforementioned device debugging method. The implementation solution provided by this system is similar to the implementation solution described in the aforementioned method. Therefore, the specific limitations in one or more device debugging system embodiments provided below can be found in the limitations of the device debugging method above and will not be repeated here.

[0106] In an exemplary embodiment, Figure 6 As shown, a device debugging system 600 is provided. The device debugging system 600 includes an information board 110 and a debugging device 120 connected to each other. The information board 110 is connected to the device to be debugged.

[0107] The information board 110 is configured to read and send the protocol data of the device to be debugged to the debugging device 120, and receive the encoded debugging data sent by the debugging device 120, and send the encoded debugging data to the device to be debugged to debug the device;

[0108] The debugging device 120 is configured to receive protocol specification data of the device to be debugged, and based on the protocol specification data, search for a debugging configuration file that matches the device to be debugged in a preset configuration database, where the debugging configuration file includes a protocol content configuration file and a user interface configuration file. Based on the user interface configuration file, the debugging interface that matches the device to be debugged is loaded, and debugging data input by the user through the debugging interface is obtained. Based on the protocol content configuration file, the debugging data is encoded, and the encoded debugging data is sent to the information board 110.

[0109] In an exemplary embodiment, Figure 7 As shown, the information board 110 includes a protocol processing module 111, a protocol aggregation module 112 connected to the protocol processing module 111, and a first tunnel protocol module 113 connected to the protocol aggregation module 112. The debugging device 120 includes a second tunnel protocol module 121. The protocol processing module 111 is connected to the device to be debugged, and the first tunnel protocol module 113 is connected to the second tunnel protocol module 121.

[0110] The protocol processing module 111 is configured to poll and read the protocol data of the device to be debugged, and store the protocol data in the protocol aggregation module 112 .

[0111] The first tunnel protocol module 113 is configured to encapsulate the protocol data in the protocol aggregation module into a preset tunnel frame to form a protocol identification frame, and send the protocol identification frame to the second tunnel protocol module 121 .

[0112] The second tunnel protocol module 121 is configured to receive a protocol identification frame and extract protocol data of the device to be debugged from the protocol identification frame.

[0113] Specifically, the protocol processing module 111 is the data acquisition unit of the information board 110. It can establish a physical connection with the device to be debugged through a hardware interface to implement millisecond-level polling sampling of the device to be debugged, and collect the protocol protocol data of the device to be debugged. When there are multiple devices to be debugged, the protocol protocol data of each device to be debugged can be stored in the protocol aggregation module 112. The first tunnel protocol module 113 is the communication encapsulation unit of the information board 110. It can encapsulate the aggregated protocol data in a tunnel frame to form a protocol identification frame, and convert it into a tunnel frame format. The second tunnel protocol module 121 is the communication parsing unit of the debugging device 120. Corresponding to the first tunnel protocol module 113, it can receive and parse the protocol identification frame and extract the protocol protocol data of the device to be debugged for subsequent debugging.

[0114] In this embodiment, the protocol protocol data of the device to be debugged is polled and read by the protocol processing module, and the data is aggregated and encapsulated in the tunnel frame by the protocol aggregation module and the first tunnel protocol module, and finally parsed and obtained by the second tunnel protocol module 121 to form a complete data acquisition and transmission link, thereby improving data transmission efficiency and data transmission stability, and helping to improve subsequent debugging efficiency.

[0115] In an exemplary embodiment, Figure 7 As shown, the debugging device 120 includes a protocol management module 122 connected to the second tunnel protocol module 121 , and a protocol content configuration module 123 and a user interface configuration module 124 connected to the protocol management module 122 .

[0116] The protocol management module 122 is configured to store the mapping relationship between the protocol data of the device to be debugged and the debugging configuration file, and the mapping relationship is stored in the form of key-value pairs.

[0117] The protocol content configuration module 123 is configured to store the protocol content configuration file of the device to be debugged, and download the protocol content configuration file of the device to be debugged from a preset remote configuration database.

[0118] The user interface configuration module 124 is configured to store the user interface configuration file of the device to be debugged and download the user interface configuration file of the device to be debugged from a preset remote configuration database.

[0119] Specifically, the protocol management module 122 is the module in the debugging device 120 responsible for establishing the association between protocol protocol data and debugging configuration files. It can quickly establish a mapping relationship between protocol protocol data and debugging configuration files through key-value pairs to achieve subsequent rapid retrieval and matching. The protocol content configuration module 123 is used to store and manage protocol content configuration files. Its stored content includes but is not limited to information such as protocol encoding rules and data frame formats, and supports dynamic acquisition of protocol content configuration files from a remote configuration database. The user interface configuration module 124 is responsible for storing and managing user interface configuration files. Its content includes the location, style, operation response rules, etc. of interface elements (buttons, icons, etc.). It can also support multi-language interface switching and theme configuration.

[0120] In this embodiment, the mapping relationship between protocol data and debugging configuration files is stored in the form of key-value pairs, and debugging configuration files matching the diverse devices to be debugged are searched in a local database or a remote database, which can improve the adaptability of the debugging device to the diverse devices to be debugged and improve debugging efficiency.

[0121] In an exemplary embodiment, Figure 8As shown, the debugging device 120 further includes an encryption and decryption module 125 connected to the protocol content configuration module 123 and the user interface configuration module 124 , and a rights management module 126 connected to the encryption and decryption module 125 .

[0122] The encryption and decryption module 125 is configured to identify the user's location information. When it is determined based on the location information that the user is not in a preset location area, the protocol content configuration file in the protocol content configuration module 123 and the user interface configuration file in the user interface configuration module 124 are encrypted.

[0123] The rights management module 126 is used to provide different types of users with hierarchical access rights and modification rights for the protocol content configuration files and the user interface configuration files.

[0124] Specifically, the encryption and decryption module 125 is responsible for dynamically encrypting and protecting the configuration file based on the user's location information. For example, when the user uses the debugging device within the manufacturer's company for product development, the protocol content configuration file and the user interface configuration file do not need to be encrypted. If the user uses the debugging device outside the company for engineering debugging or after-sales maintenance, the protocol content configuration file and the user interface configuration file need to be encrypted. In addition, a special interface can be provided to allow users to modify the debugging configuration file, and the interface can be supplemented with permission management. At this time, the protocol content configuration file and the user interface configuration file can be encrypted, and the user can decrypt them through the interface. The permission management module 126 is the access control module of the debugging device 120, which is used to implement hierarchical permission management of the debugging configuration file. For example, the manufacturer can customize role creation, permission inheritance and dynamic permission adjustment through the permission management module 126 to meet the needs of hierarchical collaborative debugging.

[0125] In this embodiment, by judging the user's location, when the user exceeds the preset security area, the encryption of the protocol content configuration file and the user interface configuration file is triggered. Combined with the hierarchical permission management mechanism, the risk of configuration file leakage can be effectively reduced and the reliability and stability of the debugging device can be improved.

[0126] Based on the same inventive concept, the present application also provides an apparatus for implementing the aforementioned apparatus debugging method. The solution provided by this apparatus is similar to the solution described in the aforementioned method. Therefore, the specific limitations in one or more apparatus debugging apparatus embodiments provided below can be found in the aforementioned limitations on the apparatus debugging method and will not be further elaborated here.

[0127] In an exemplary embodiment, Figure 9As shown, a device debugging apparatus 600 is provided, comprising: a data receiving module 610, a configuration search module 620, a debugging interface loading module 630 and a debugging module 640, wherein:

[0128] The data receiving module 610 is used to receive the protocol data of the device to be debugged sent by the information board when the connection is established with the information board, and the information board is connected to the device to be debugged;

[0129] Configuration search module 620, for searching a preset configuration database for a debugging configuration file that matches the device to be debugged based on the protocol specification data, the debugging configuration file including a protocol content configuration file and a user interface configuration file;

[0130] The debugging interface loading module 630 is used to load the debugging interface that matches the device to be debugged based on the user interface configuration file, and obtain the debugging data input by the user through the debugging interface;

[0131] The debugging module 640 is configured to encode the debugging data based on the protocol content configuration file, and send the encoded debugging data to the device to be debugged via the information board.

[0132] In an exemplary embodiment, the debugging module 640 is also used to construct a protocol data model that matches the device to be debugged based on the protocol content configuration file, call the protocol data model, encode the debugging data, obtain the encoded debugging data, encapsulate the encoded debugging data in a preset tunnel frame to form a data tunnel frame, and send the data tunnel frame to the information board, so that the information board extracts the encoded debugging data from the data tunnel frame and sends it to the device to be debugged.

[0133] In an exemplary embodiment, the device debugging apparatus 600 is further configured to receive debugging result data sent by the device to be debugged via an information board, call a protocol data model, parse the debugging result data, and display the parsed debugging result data on a debugging interface.

[0134] In an exemplary embodiment, the configuration database includes a local configuration database and a remote configuration database. The configuration search module 620 is further used to preferentially search the local configuration database for a debugging configuration file that matches the device to be debugged based on the protocol specification data. If no debugging configuration file that matches the device to be debugged is found in the local configuration database, the remote configuration database is searched for a debugging configuration file that matches the device to be debugged.

[0135] In an exemplary embodiment, the debugging configuration file is encrypted and stored in a local configuration database or a remote configuration database. The configuration search module 620 is also used to search for an encrypted debugging configuration file that matches the device to be debugged in a preset configuration database based on the protocol specification data, decrypt the encrypted debugging configuration file, and obtain a debugging configuration file that matches the device to be debugged.

[0136] In an exemplary embodiment, the protocol content configuration file and the user interface configuration file are described in XML configuration files, and different types of users have hierarchical access rights and modification rights for the protocol content configuration file and the user interface configuration file.

[0137] Each module in the device debugging apparatus described above can be implemented in whole or in part through software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in hardware form, or can be stored in a computer device memory in software form, so that the processor can call and execute the corresponding operations of each module.

[0138] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 10 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O) and a communication interface. The processor, memory and input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store data such as protocol data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a device debugging method is implemented.

[0139] Those skilled in the art will understand that Figure 10 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0140] In an exemplary embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above-mentioned device debugging method embodiment when executing the computer program.

[0141] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned device debugging method embodiment are implemented.

[0142] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above-mentioned device debugging method embodiment when executed by a processor.

[0143] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0144] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile memory and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processor involved in the various embodiments provided herein may be, but are not limited to, a general-purpose processor, a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), a programmable logic unit (PLC), a data processing logic unit based on quantum computing, an artificial intelligence (AI) processor, and the like.

[0145] The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0146] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A device debugging method, characterized in that: The method comprises: When a connection is established with the information board, receiving protocol data of the device to be debugged sent by the information board, the information board being connected to the device to be debugged; Based on the protocol specification data, searching a preset configuration database for a debugging configuration file that matches the device to be debugged, the debugging configuration file including a protocol content configuration file and a user interface configuration file; Based on the user interface configuration file, loading a debugging interface that matches the device to be debugged, and acquiring debugging data input by a user through the debugging interface; The debugging data is encoded based on the protocol content configuration file, and the encoded debugging data is sent to the device to be debugged through the information board.

2. The method according to claim 1, characterized in that The step of encoding the debugging data based on the protocol content configuration file and sending the encoded debugging data to the device to be debugged via the information board includes: Based on the protocol content configuration file, construct a protocol data model that matches the device to be debugged; Calling the protocol data model, encoding the debugging data, and obtaining encoded debugging data; Encapsulating the encoded debugging data in a preset tunnel frame to form a data tunnel frame; The data tunnel frame is sent to the information board, so that the information board extracts the encoded debugging data from the data tunnel frame and sends it to the device to be debugged.

3. The method according to claim 2, characterized in that The method further comprises: receiving debugging result data sent by the device to be debugged through the information board; The protocol data model is called, the debugging result data is parsed, and the parsed debugging result data is displayed on the debugging interface.

4. The method according to claim 1, wherein The configuration database includes a local configuration database and a remote configuration database. The method of searching for a debugging configuration file matching the device to be debugged in a preset configuration database based on the protocol specification data includes: Based on the protocol data, preferentially searching the local configuration database for a debugging configuration file that matches the device to be debugged; When no debugging configuration file matching the device to be debugged is found in the local configuration database, a debugging configuration file matching the device to be debugged is searched in the remote configuration database.

5. The method according to claim 4, characterized in that The debugging configuration file is encrypted and stored in the local configuration database or the remote configuration database, and searching a preset configuration database for a debugging configuration file that matches the device to be debugged based on the protocol specification data includes: Based on the protocol specification data, searching a preset configuration database for an encrypted debugging configuration file that matches the device to be debugged; The encrypted debugging configuration file is decrypted to obtain a debugging configuration file that matches the device to be debugged.

6. The method according to any one of claims 1 to 5, characterized in that The method further includes: the protocol content configuration file and the user interface configuration file are described as XML configuration files, and different types of users have hierarchical access rights and modification rights for the protocol content configuration file and the user interface configuration file.

7. A device debugging system, characterized in that: The equipment debugging system includes a debugging device and an information board connected to each other, and the information board is connected to the equipment to be debugged; The information board is configured to read and send the protocol data of the device to be debugged to the debugging device, and receive the encoded debugging data sent by the debugging device, and send the encoded debugging data to the device to be debugged to debug the device; The debugging device is configured to receive protocol specification data of the device to be debugged, and based on the protocol specification data, search a debugging configuration file matching the device to be debugged in a preset configuration database, wherein the debugging configuration file includes a protocol content configuration file and a user interface configuration file; based on the user interface configuration file, load a debugging interface matching the device to be debugged, and obtain debugging data input by a user through the debugging interface; based on the protocol content configuration file, encode the debugging data, and send the encoded debugging data to the information board.

8. The system according to claim 7, characterized in that The information board includes a protocol processing module, a protocol aggregation module connected to the protocol processing module, and a first tunnel protocol module connected to the protocol aggregation module. The debugging device includes a second tunnel protocol module. The protocol processing module is connected to the device to be debugged, and the first tunnel protocol module is connected to the second tunnel protocol module. The protocol processing module is configured to poll and read the protocol protocol data of the device to be debugged, and store the protocol protocol data in the protocol aggregation module; The first tunnel protocol module is configured to encapsulate the protocol data in the protocol aggregation module into a preset tunnel frame to form a protocol identification frame, and send the protocol identification frame to the second tunnel protocol module; The second tunnel protocol module is configured to receive the protocol identification frame and extract the protocol data of the device to be debugged from the protocol identification frame.

9. The system according to claim 8, characterized in that The debugging device includes a protocol management module connected to the second tunnel protocol module, and a protocol content configuration module and a user interface configuration module connected to the protocol management module; The protocol management module is configured to store a mapping relationship between the protocol data of the device to be debugged and the debugging configuration file, wherein the mapping relationship is stored in a key-value pair manner; The protocol content configuration module is configured to store the protocol content configuration file of the device to be debugged, and download the protocol content configuration file of the device to be debugged from a preset remote configuration database; The user interface configuration module is configured to store the user interface configuration file of the device to be debugged, and download the user interface configuration file of the device to be debugged from a preset remote configuration database.

10. The system according to claim 9, characterized in that The debugging device further includes an encryption and decryption module connected to the protocol content configuration module and the user interface configuration module, and a rights management module connected to the encryption and decryption module; The encryption / decryption module is configured to identify the location information of the user and, if it is determined based on the location information that the user is not in a preset location area, encrypt the protocol content configuration file in the protocol content configuration module and the user interface configuration file in the user interface configuration module; The rights management module is used to provide different types of users with hierarchical access rights and modification rights for the protocol content configuration file and the user interface configuration file.

Images