Equipment debugging method and device, equipment, storage medium and program product

Abstract

The invention discloses an equipment debugging method and device, equipment, a storage medium and a program product. The method comprises the following steps: acquiring attribute information of to-be-debugged equipment; querying in the first file according to the attribute information of the to-be-debugged equipment, and determining debugging parameters of the to-be-debugged equipment and index information of each debugging parameter; the first file comprises equipment parameters of different function modules of different models in different application scenes and index information of the equipment parameters; reading attribute information of the debugging parameters from the second file according to the index information of the debugging parameters, and loading the attribute information of the debugging parameters into the debugging software to indicate the debugging software to debug the to-be-debugged equipment according to the attribute information of the debugging parameters; the second file comprises different equipment parameters and attribute information of each equipment parameter. By adopting the method, the updating complexity of the equipment parameters adapted to the debugging software can be effectively reduced.

Description

Technical Field

[0001] This application relates to the field of equipment commissioning, and in particular to a method, apparatus, device, storage medium, and program product for equipment commissioning. Background Technology

[0002] In the field of industrial equipment commissioning, such as frequency converters, commissioning software is often used to debug the equipment and ensure its normal operation. Currently, the software code of commissioning software is often coupled with the equipment parameters of the industrial equipment to make the commissioning software compatible with various equipment models.

[0003] However, when new industrial equipment is added for debugging, equipment is upgraded, or the same model of equipment is used in different fields, the equipment parameters that the debugging software needs to couple with often change, thus requiring modifications to the software code. Modifying the debugging software code to adapt to changes in the equipment parameters of the device under debugging results in low flexibility and low equipment debugging efficiency. Summary of the Invention

[0004] In view of the above-mentioned defects or deficiencies in the prior art, it is desirable to provide a device debugging method, apparatus, equipment, storage medium and program product that can effectively reduce the complexity of updating device parameters for debugging software adaptation.

[0005] Firstly, this application provides a device debugging method. The method includes: Obtain the attribute information of the device to be debugged; the attribute information includes at least one of the device model, test scenario, and functional module to be tested. The debugging parameters of the device to be debugged are determined by querying the first file based on the attribute information of the device to be debugged, as well as the index information of each debugging parameter. The first file includes the device parameters of different functional modules of different models in different application scenarios, as well as the index information of each device parameter. The attribute information of the debugging parameters is read from the second file according to the index information of each debugging parameter, and the attribute information of the debugging parameters is loaded into the debugging software to instruct the debugging software to debug the device to be debugged according to the attribute information of the debugging parameters; the second file includes different device parameters and the attribute information of each device parameter.

[0006] In conjunction with the first aspect, in one possible implementation, the process of constructing the second file includes: providing a parameter configuration interface to the user, instructing the user to configure the attribute information of different device parameters; in response to the user's configuration operation on the parameter configuration interface, obtaining a second initial file; and converting the data format of the second initial file to obtain the second file.

[0007] In conjunction with the first aspect, in one possible implementation, the process of constructing the first file includes: providing a directory configuration interface to the user, instructing the user to construct a device parameter directory with the device model as the root directory and functional modules and / or application scenarios as subdirectories; generating index information for each device parameter based on the address information of each device parameter in the second file; establishing the association between the index information and the corresponding device parameters in the device parameter directory to obtain the first initial file; and performing data format conversion on the first initial file to obtain the first file.

[0008] In conjunction with the first aspect, in one possible implementation, the second initial file is converted into a data format to obtain a second file, including: converting the attribute information of each device parameter in the second initial file into binary format data; determining the storage address of the attribute information of each device parameter for the attribute information of each device parameter; and storing the storage address and the attribute information converted from binary format in a key-value pair format as the second file.

[0009] In conjunction with the first aspect, in one possible implementation, the device debugging method further includes: updating the device parameter directory in the first initial file in response to the user's configuration operation in the directory configuration interface; updating the second file in response to the user's configuration operation in the parameter configuration interface; and updating the index information in the updated first initial file of the device parameter directory according to the updated second file to obtain the updated first file.

[0010] In conjunction with the first aspect, in one possible implementation, the debugging software is instructed to debug the device under test according to the attribute information of the debugging parameters, including: instructing the debugging software to control the operation of the device under test based on the debugging parameters and the corresponding attribute information, and testing the functional modules of the device under test according to the operating parameters of the device under test.

[0011] Secondly, this application also provides a device debugging apparatus. The apparatus includes: The acquisition module is used to acquire attribute information of the device to be debugged; the attribute information includes at least one of the device model, test scenario, and functional module to be tested. The query module is used to query the first file based on the attribute information of the device to be debugged, to determine the debugging parameters of the device to be debugged, as well as the index information of each debugging parameter; the first file includes the device parameters of different functional modules of different models in different application scenarios, as well as the index information of each device parameter; The debugging module is used to read the attribute information of the debugging parameters from the second file according to the index information of each debugging parameter, and load the attribute information of the debugging parameters into the debugging software so as to instruct the debugging software to debug the device to be debugged according to the attribute information of the debugging parameters; the second file includes different device parameters and the attribute information of each device parameter.

[0012] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the method described in the first aspect.

[0013] Fourthly, this application also provides a computer-readable storage medium. This computer-readable storage medium stores a computer program thereon, which, when executed by a processor, implements the method described in the first aspect.

[0014] Fifthly, this application also provides a computer program product. This computer program product includes a computer program that, when executed by a processor, implements the method described in the first aspect.

[0015] This application provides a device debugging method, apparatus, device, storage medium, and program product. When debugging a device needs to be debugged, the method obtains the device's attribute information, queries a first file based on the attribute information to determine the debugging parameters and index information of each parameter, reads the attribute information of the debugging parameters from a second file based on the index information, and loads the attribute information of the debugging parameters into the debugging software to instruct the software to debug the device according to the attribute information of the debugging parameters. In other words, this application can store device parameters and attribute information of different functional modules of different models in different scenarios in a file. When needed, the debugging parameters of the device to be debugged can be loaded into the debugging software without coupling the device parameter information into the debugging software code, which would make updating the device parameters difficult. Furthermore, this application separates the device parameter list and the attribute information of each device parameter and stores them in different files, thereby achieving flexible configuration of device parameters and efficient response of the debugging software. Attached Figure Description

[0016] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 This is a diagram illustrating the application environment of a device debugging method in one embodiment; Figure 2 This is a flowchart illustrating a device debugging method in one embodiment; Figure 3 This is a schematic diagram of the device parameter catalog in one embodiment; Figure 4 This is a schematic diagram illustrating the configuration of attribute information for device parameters in one embodiment; Figure 5 This is another flowchart illustrating the device debugging method in one embodiment; Figure 6 This is another flowchart illustrating the device debugging method in one embodiment; Figure 7 This is another flowchart illustrating the device debugging method in one embodiment; Figure 8 This is a structural block diagram of the device debugging apparatus in one embodiment; Figure 9 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0017] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings.

[0018] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. The present application will now be described in detail with reference to the accompanying drawings and embodiments. Furthermore, the term "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The terms "first" and "second," etc., in the specification and claims of the embodiments of this application are used to distinguish different objects, not to describe a specific order of objects.

[0019] In the field of industrial equipment commissioning, such as frequency converters, commissioning software is often used to debug the equipment and ensure its normal operation. Currently, the software code of commissioning software is often coupled with the equipment parameters of the industrial equipment to make the commissioning software compatible with various equipment models.

[0020] When adding new industrial equipment models for commissioning or upgrading existing equipment, it's often necessary to add or adjust the equipment parameters in the commissioning software to adapt to them, thus requiring modifications to the software code. Similarly, when applying industrial equipment to specialized fields, such as dedicated frequency converters for cranes, it's necessary to add specialized equipment parameters to the commissioning software code to ensure comprehensive and accurate commissioning. However, modifying the software code to adapt to changes in the equipment parameters of the equipment being commissioned results in low flexibility and low commissioning efficiency.

[0021] Based on this, embodiments of this application provide a device debugging method, apparatus, device, storage medium, and program product that can make the debugging software compatible with the device parameters of various models without coupling device parameter-related information into the debugging software code, effectively reducing the complexity of updating device parameters for debugging software adaptation.

[0022] The device debugging method provided in this application embodiment can be applied to, for example, Figure 1 In the application environment shown, server 10 can load locally stored device parameters into debugging software running on it, allowing the debugging software to debug the device 20 to be debugged based on the loaded device parameters. Server 10 can be implemented as a standalone server or a server cluster consisting of multiple servers.

[0023] In one embodiment, such as Figure 2 As shown, a device debugging method is provided, which can be applied to... Figure 1 Taking server 10 as an example, the following steps are included: Step 101: Obtain the attribute information of the device to be debugged.

[0024] The attribute information includes at least one of the following: the model of the device to be debugged, the test scenario, and the functional module to be tested.

[0025] In this embodiment of the application, before debugging the device to be debugged, it is necessary to first determine the relevant attribute information of the device to be debugged in order to determine the device parameters required for debugging the device to be debugged, that is, the debugging parameters corresponding to the device to be debugged.

[0026] After the server 10 and the device to be debugged 20 are connected, the server 10 can directly obtain the attribute information of the device to be debugged. Alternatively, it can obtain relevant parameters of the device to be debugged to determine its attribute information. For example, it can obtain the identifier of the device to be debugged to determine its model; or it can obtain the application scenario of the device to be debugged (lifting, medical, extreme scenarios, etc.) to determine the test scenario of the device to be debugged.

[0027] In one possible implementation, server 20 can also provide a configuration interface to the user via a client to instruct the user to configure the attribute information of the device to be debugged. For example, the user can directly select or enter the model of the device to be debugged 20 connected to server 10, the test scenario, and the functional module of the device currently being debugged (the functional module to be tested) in the configuration interface. Server 10 responds to the user's configuration operation in the configuration interface and determines the attribute information of the device to be debugged 20.

[0028] Step 102: Based on the attribute information of the device 20 to be debugged, query the first file to determine the debugging parameters of the device 20 to be debugged, as well as the index information of each debugging parameter.

[0029] In this embodiment, to avoid requiring corresponding modifications to the debugging software code when the debugging parameters of the device under debugging change, the device parameters required for device debugging are separated from the debugging software code and stored in an independent file. This allows for convenient addition or modification of the device parameters required by the debugging software by modifying this file. When debugging the device, the debugging software can be configured to directly load the corresponding device parameters from this file for debugging.

[0030] Furthermore, the file used to store device parameter information can be divided into a first file and a second file. The first file includes device parameters for different functional modules of different models in different application scenarios, as well as index information for each device parameter. That is, for example... Figure 3 As shown, the first file can display multiple device parameters in the form of a parameter list (directory only). This list can be categorized into three aspects: device model, functional module, and application scenario. Additionally, the first file includes index information for each device parameter, used to access its specific attribute information.

[0031] Among them, such as Figure 4 As shown, the second file includes specific attribute information for different device parameters. This attribute information can include the device parameter's communication address (e.g., Modbus address), function code, upper and lower limits, manufacturer's default values, read / write attributes, display radix, and decimal places. During actual debugging, the software code primarily controls device operation according to this attribute information to achieve device debugging.

[0032] In this embodiment, after determining the attribute information of the device to be debugged, the server 10 can obtain a first file locally and query the device parameters required for this debugging based on the attribute information of the device to be debugged 20 in the first file. Specifically, the attribute information of the device to be debugged 20 is matched against the parameter list in the first file to determine at least one device parameter in the parameter list corresponding to the model, test scenario, and functional module to be tested of the device to be debugged 20, thereby obtaining the debugging parameters corresponding to the device to be debugged 20 and the index information of each debugging parameter.

[0033] Step 103: Read the attribute information of the debugging parameters from the second file according to the index information of each debugging parameter, and load the attribute information of the debugging parameters into the debugging software to instruct the debugging software to debug the device 20 to be debugged according to the attribute information of the debugging parameters.

[0034] The second file includes different device parameters and attribute information for each device parameter.

[0035] In this embodiment, after determining the index information of the debugging parameters, the second file can be accessed based on the index information to obtain the specific attribute information of each debugging parameter. Then, the debugging software running on the server 10 can load this attribute information, thereby achieving coupling between the debugging software and the device parameters.

[0036] In other words, this application separates the device parameter list and the specific attribute information of each device parameter, storing them in different files (the first file and the second file). Firstly, considering that different models and functions may correspond to the same device parameters, storing the device parameter list and attribute information in the same file would result in the same device parameter's attribute information being configured multiple times in different positions within the list, leading to file redundancy. Therefore, separating the device parameter list and the attribute information of each device parameter avoids file redundancy and improves the orderliness of the content in each file. Secondly, it improves the configuration flexibility of the first and second files. For example, when adding a device parameter for a specific function of a certain model, only the first file needs to be modified, adding the new device parameter and its corresponding index information to the device parameter list under that function module for that model; when only the attribute information of a device parameter needs to be modified, only the second file needs to be modified. Furthermore, separating the two operations of "querying debugging parameters" and "reading the attribute information corresponding to debugging parameters" into two files avoids them being concentrated in the same file. This allows the debugging software to directly read the attribute information of the debugging parameters from the second file based on the index information, achieving efficient reading of attribute information and thus improving device debugging efficiency.

[0037] Taking Qt tools as an example, the process of loading the second file into the debugging software is explained as follows: First, the second file stored locally is read based on the index information using QFile. Then, QDataStream is used to parse the second file to obtain the attribute information of each debugging parameter. Next, the storage address of each debugging parameter's attribute information is mapped to a key, and the attribute information of the debugging parameters is mapped to a value, which is then populated into a pre-built QMap object, and finally loaded into the debugging software.

[0038] In this embodiment, after determining the debugging parameters and index information required for debugging the device 20 to be debugged, the server 10 instructs the debugging software to load the attribute information of each debugging parameter based on the index information. The debugging software then debugs the device 20 based on the loaded attribute information of at least one debugging parameter. This can be achieved through the following steps: The instruction debugging software controls the operation of the device under debugging 20 based on the debugging parameters and corresponding attribute information, and tests the functional modules of the device under debugging 20 according to the operating parameters of the device under debugging 20.

[0039] In this implementation, the debugging software modifies the device parameters of the device 20 that match the debugging parameters based on the attribute information of the debugging parameters. This ensures that the device 20 operates according to the attribute information in the scenario represented by the debugging parameters. Then, the debugging software can obtain the operating parameters of the device 20, analyze its operating status, and determine whether the functional modules of the device 20 are operating normally, thus achieving the debugging of the device 20.

[0040] The method provided in this application, when debugging a device needs to be debugged, obtains the attribute information of the device to be debugged, queries a first file based on the attribute information to determine the debugging parameters of the device to be debugged, as well as the index information of each debugging parameter, reads the attribute information of the debugging parameters from a second file based on the index information of each debugging parameter, and loads the attribute information of the debugging parameters into the debugging software to instruct the debugging software to debug the device to be debugged according to the attribute information of the debugging parameters. That is, this application embodiment can store the device parameters and attribute information of different functional modules of different models in different scenarios in a file. When needed, the debugging parameters of the device to be debugged can be loaded into the debugging software without coupling the device parameter information into the code of the debugging software, which would make updating the device parameters difficult. Furthermore, this application separates the device parameter list and the attribute information of each device parameter and stores them in different files, thereby achieving flexible configuration of device parameters and efficient response of the debugging software.

[0041] The foregoing embodiments described a scheme that separates the attribute information of device parameters from the code of the debugging software and stores them independently in a first file and a second file. In another embodiment of this application, a specific construction process for the first file and the second file is provided. The construction process for the second file may include, for example... Figure 5 The steps shown are as follows: Step 201: Provide the user with a parameter configuration interface, instructing the user to configure the attribute information of different device parameters.

[0042] Step 202: In response to the user's configuration operation on the parameter configuration interface, obtain the second initial file.

[0043] Step 203: Convert the data format of the second initial file to obtain the second file.

[0044] In this embodiment, both the first file and the second file are pre-configured by the user and stored locally on the server 10. Regarding the second file, the server 10 can provide a parameter configuration interface to the user through a client to instruct the user to configure device parameters and their corresponding attribute information.

[0045] After completing the configuration on the parameter configuration interface, the user can click "Submit". Upon confirming the user's configuration, server 10 responds to the user's configuration operation on the configuration interface by generating a second initial file based on the user-configured device parameters and corresponding attribute information. This second initial file is a text file, such as an Excel spreadsheet. Since the attribute information of the same device parameter often differs across different models, functional modules, or application scenarios, it is understandable that the second initial file may contain device parameters with the same name but different attribute information.

[0046] After the server 10 obtains the second initial file in response to the user's configuration operation in the parameter configuration interface, it needs to convert the second initial file into a file format (such as binary format) that can be recognized by the server (operating system) or debugging software, so as to obtain the second file. This allows the debugging software to access and load the attribute information of the debugging parameters in the second file when debugging the device 20 to be debugged.

[0047] In one embodiment, the process of building the first file may include, for example: Figure 6 The steps shown are as follows: Step 301: Provide the user with a directory configuration interface, instructing the user to build a device parameter directory with the device model as the root directory and functional modules and / or application scenarios as subdirectories.

[0048] Step 302: Generate index information for each device parameter based on the address information of each device parameter in the second file, establish the association between the index information and the corresponding device parameters in the device parameter directory, and obtain the first initial file.

[0049] Step 303: Convert the data format of the first initial file to obtain the first file.

[0050] In this embodiment of the application, for the first file, the server 10 can provide a directory configuration interface to the user through a client to instruct the user to configure a list of device parameters (i.e., a device parameter directory). The server 10 instructs the user to use the device model as the root directory when configuring the device parameter directory. Under each root directory, multiple subdirectories can be configured according to the functional modules of the device model, and at least one device parameter required for the device to implement that function can be configured in each subdirectory.

[0051] Alternatively, considering that different functions require different device parameter attribute information in different application scenarios, subdirectories can be configured under each function's subdirectory according to the application scenario of the device model. In each scenario's corresponding subdirectory, at least one device parameter required for the device to implement the function in that application scenario can be configured. This completes the construction of the device parameter directory.

[0052] In response to the device parameter directory constructed by the user in the directory configuration interface, server 10 needs to establish an association between the attribute information of each device parameter in the device parameter directory and the corresponding device parameter in the second file. This allows server 10 to determine the debugging parameters of the device 20 to be debugged in the device parameter directory and instruct the debugging software to access the second file based on this association to obtain the attribute information of the debugging parameters. Specifically, server 10 can generate corresponding index information based on the address information of each device parameter in the second file (which can be the communication address in the attribute information or the storage address of the attribute information of each device parameter). For example, the address information can be directly used as the index information. Then, the association between the index information and the corresponding device parameters in the device parameter directory is established to obtain the first initial file. For example, the index information is mapped to a key, and the corresponding device parameters in the device parameter directory are mapped to a value. The association between the index information and the corresponding device parameters in the device parameter directory is constructed through key-value pairs to obtain the first initial file. Next, the data format of the first initial file is converted into a data format that the server can recognize.

[0053] After converting the initial data format of the first file, it can be loaded into the global configuration manager of the debugging software using QT tools. This allows the debugging software to quickly retrieve the first file and query debugging parameters and their index information from the global configuration manager before debugging the device under test, based on the device's attribute information. Specifically, the first file can be parsed using QSettings to obtain the device parameters and their index information in the device parameter directory. Then, the device parameters and their index information in the device parameter directory are converted into QVariant type and stored in the global configuration manager of the debugging software.

[0054] The method provided in this application embodiment can generate a file in response to the user-configured device parameter directory and the attribute information corresponding to each device parameter, convert the file into a data format that the server can recognize and store it, so that when the debugging software is debugging the device to be debugged, it can effectively use the file to load the attribute information of the debugging parameters, thereby realizing a device debugging scheme decoupled from the software code.

[0055] As can be seen from the above embodiments, the first file and the second file used to store device parameter-related information are configured by the user. Therefore, when it is necessary to add new models to the debugging software or modify device parameters, the compatibility of the debugging software with the added or modified device parameters can be ensured by updating the first file and / or the second file. This embodiment may include, for example... Figure 7 The steps shown are as follows: Step 501: In response to the user's configuration operation in the directory configuration interface, update the device parameter directory in the first initial file.

[0056] Step 502: In response to the user's configuration operation in the parameter configuration interface, update the second file.

[0057] Step 503: Update the index information in the updated first initial file of the device parameter directory according to the updated second file to obtain the updated first file.

[0058] In this embodiment, if the server 10 detects a user's update operation on the device parameter directory in the directory configuration interface, and this update operation does not affect the content of the second file—for example, adding a device parameter already existing in the second file to a certain location in the device parameter directory, meaning the attribute information of the newly added device parameter already exists in the second file—then there is no need to update the second file again. In response to the user's configuration operation in the directory configuration interface, the server 10 obtains the updated first initial file, and performs data format conversion on the updated first initial file to obtain the updated first file.

[0059] If server 10 detects that a user has updated the attribute information of a device parameter in the parameter configuration interface without affecting the content of the first file, then in response to the user's configuration operation in the parameter configuration interface, an updated second initial file is obtained. The updated second initial file is then converted to its data format to obtain the updated second file.

[0060] If the second file needs to be updated in response to a user's configuration operation in the directory configuration interface (e.g., adding device parameters that are not present in the second file to the device parameter directory), or the first file needs to be updated in response to a user's configuration operation in the parameter configuration interface (e.g., adding device parameters and attribute information, requiring the device parameters to be added to the corresponding location in the device parameter directory), or if the user updates both the directory configuration interface and the parameter configuration interface simultaneously, then the device parameter directory needs to be updated based on the updated device parameters in the second file, the index information in the first file needs to be updated based on the address information of the device parameters in the updated second file, and / or the device parameters in the second file need to be updated based on the updated device parameter directory in the first file.

[0061] In other words, the device parameter directory in the updated first file needs to be matched with the device parameters in the updated second file, and the index information in the updated first file needs to be matched with the address information in the updated second file. This is to avoid data mismatches between the first and second files after the update.

[0062] The method provided in this application embodiment can update the device parameters and attribute information in the first file and / or the second file, which enables the debugging software to adapt to the device to be debugged when a new model is added, etc., without modifying the software code of the debugging software. This effectively reduces the complexity of updating the device parameters adapted by the debugging software and improves the flexibility of the debugging software.

[0063] It should be noted that although the operations of the method of the present invention are described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all of the operations shown must be performed to achieve the desired result. On the contrary, the steps depicted in the flowchart may be performed in a different order. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0064] In one embodiment, such as Figure 8 As shown, a device debugging apparatus is provided, comprising: an acquisition module 601, a query module 602, and a debugging module 603, wherein: The acquisition module 601 is used to acquire the attribute information of the device to be debugged; the attribute information includes at least one of the device model, test scenario, and functional module to be tested.

[0065] The query module 602 is used to query the first file based on the attribute information of the device to be debugged, to determine the debugging parameters of the device to be debugged, as well as the index information of each debugging parameter; the first file includes the device parameters of different functional modules of different models in different application scenarios, as well as the index information of each device parameter.

[0066] The debugging module 603 is used to read the attribute information of the debugging parameters from the second file according to the index information of each debugging parameter, and load the attribute information of the debugging parameters into the debugging software so as to instruct the debugging software to debug the device to be debugged according to the attribute information of the debugging parameters; the second file includes different device parameters and the attribute information of each device parameter.

[0067] In one embodiment, the device debugging apparatus further includes a first building module, configured to provide a parameter configuration interface to a user, instructing the user to configure attribute information of different device parameters; in response to the user's configuration operation on the parameter configuration interface, obtain a second initial file; and perform data format conversion on the second initial file to obtain a second file.

[0068] In one embodiment, the device debugging apparatus further includes a second construction module, which is used to provide a directory configuration interface to the user, instructing the user to construct a device parameter directory with the device model as the root directory and functional modules and / or application scenarios as subdirectories, generate index information for each device parameter according to the address information of each device parameter in the second file, establish the association between the index information and the corresponding device parameters in the device parameter directory, and obtain a first initial file; and perform data format conversion on the first initial file to obtain a first file.

[0069] In one embodiment, the first construction module is specifically used to convert the attribute information of each device parameter in the second initial file into binary format data; for the attribute information of each device parameter, determine the storage address of the attribute information of the device parameter, and store the storage address and the attribute information converted from binary format in a key-value pair format as the second file.

[0070] In one embodiment, the device debugging apparatus further includes an update module, configured to update the device parameter directory in the first initial file in response to a user's configuration operation in the directory configuration interface; update the second file in response to a user's configuration operation in the parameter configuration interface; and update the index information in the updated first initial file of the device parameter directory according to the updated second file to obtain the updated first file.

[0071] In one embodiment, the debugging module 603 is specifically used to instruct the debugging software to control the operation of the device under debugging based on the debugging parameters and corresponding attribute information, and to test the functional modules of the device under debugging according to the operating parameters of the device under debugging.

[0072] It should be understood that the units or modules described in the equipment commissioning device are consistent with the reference. Figure 2 The steps in the described method correspond to each other. Therefore, the operations and features described above for the method are also applicable to the device debugging apparatus and the units contained therein, and will not be repeated here. The device debugging apparatus can be pre-implemented in the browser or other security applications of the electronic device, or it can be loaded into the browser or other security applications of the electronic device through download or other means. The corresponding units in the device debugging apparatus can cooperate with the units in the electronic device to implement the solutions of the embodiments of this application.

[0073] The following is for reference. Figure 9It shows a schematic diagram of the structure of a computer system 700 suitable for implementing terminal devices or servers in the embodiments of this application.

[0074] like Figure 9 As shown, the computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 702 or programs loaded from storage section 708 into random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the system 700. The CPU 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0075] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed.

[0076] In particular, according to embodiments of this disclosure, the above references Figure 2 The described process can be implemented as a computer software program. For example, embodiments of this disclosure include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program containing instructions for performing... Figure 2 The program code for the method. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 709, and / or installed from the removable medium 711.

[0077] It should be noted that the computer-readable medium shown in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0078] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0079] The units or modules described in the embodiments of this application can be implemented in software or hardware. The described units or modules can also be located in a processor. The names of these units or modules do not, in certain circumstances, constitute a limitation on the unit or module itself.

[0080] On the other hand, this application also provides a computer-readable storage medium, which may be included in the computer device described in the above embodiments, or may exist independently and not assembled into the computer device. The aforementioned computer-readable storage medium stores one or more programs that, when used by one or more processors, execute the methods described in this application. For example, it may execute... Figure 2 The steps of the method shown.

[0081] This application provides a computer program product including instructions that, when executed, cause the method described in this application to be performed. For example, it can execute... Figure 2 The steps of the method shown.

[0082] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can 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 can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0083] The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the inventive concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this application.

Claims

1. A method for debugging equipment, characterized in that, The method includes: Obtain the attribute information of the device to be debugged; the attribute information includes at least one of the device model, test scenario, and functional module to be tested. The debugging parameters of the device to be debugged are determined by querying the attribute information of the device to be debugged in the first file, as well as the index information of each debugging parameter; the first file includes device parameters of different functional modules of different models in different application scenarios, as well as the index information of each device parameter; The attribute information of the debugging parameters is read from the second file according to the index information of each debugging parameter, and the attribute information of the debugging parameters is loaded into the debugging software to instruct the debugging software to debug the device to be debugged according to the attribute information of the debugging parameters; the second file includes different device parameters and the attribute information of each device parameter.

2. The method according to claim 1, characterized in that, The process of building the second file includes: Provide users with a parameter configuration interface, instructing them to configure the attribute information of different device parameters; In response to the user's configuration operation in the parameter configuration interface, a second initial file is obtained; The second initial file is converted to a different data format to obtain the second file.

3. The method according to claim 2, characterized in that, The construction process of the first file includes: Provide users with a directory configuration interface, instructing them to build a device parameter directory with the device model as the root directory and functional modules and / or application scenarios as subdirectories. Based on the address information of each device parameter in the second file, generate index information for each device parameter, establish the association between the index information and the corresponding device parameters in the device parameter directory, and obtain the first initial file; The first initial file is converted to a different data format to obtain the first file.

4. The method according to claim 2, characterized in that, The step of converting the data format of the second initial file to obtain the second file includes: Convert the attribute information of each device parameter in the second initial file into binary format data; For each of the device parameters, determine the storage address of the attribute information of the device parameters, and store the storage address and the attribute information converted from binary format in a key-value pair format as a second file.

5. The method according to claim 3, characterized in that, The method further includes: In response to the user's configuration operation in the directory configuration interface, the device parameter directory in the first initial file is updated; In response to the user's configuration operation on the parameter configuration interface, the second file is updated; The index information in the updated first initial file of the device parameter directory is updated based on the updated second file to obtain the updated first file.

6. The method according to claim 1, characterized in that, The instruction to the debugging software to debug the device to be debugged according to the attribute information of the debugging parameters includes: The debugging software is instructed to control the operation of the device under debugging based on the debugging parameters and corresponding attribute information, and to test the functional modules of the device under debugging according to the operating parameters of the device under debugging.

7. A device for debugging equipment, characterized in that, The device includes: An acquisition module is used to acquire attribute information of the device to be debugged; the attribute information includes at least one of the device model, test scenario, and functional module to be tested. The query module is used to query the attribute information of the device to be debugged in a first file to determine the debugging parameters of the device to be debugged, as well as the index information of each debugging parameter; the first file includes device parameters of different functional modules of different models in different application scenarios, as well as the index information of each device parameter; The debugging module is used to read the attribute information of the debugging parameters from the second file according to the index information of each debugging parameter, and load the attribute information of the debugging parameters into the debugging software to instruct the debugging software to debug the device to be debugged according to the attribute information of the debugging parameters; the second file includes different device parameters and the attribute information of each device parameter.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images