A device parameter changing method, a terminal device, and a storage medium

Abstract

This application relates to the field of data processing technology and provides a method for changing device parameters, a terminal device, and a storage medium. The method includes: obtaining a user request; obtaining parameter information of the target device based on the user request; performing a feasibility analysis on the user request based on the parameter information to obtain a parameter description of the target parameter to be modified, including a functional explanation of the target parameter and a recommended modification value; processing the target parameter according to the recommended modification value, including at least one of parameter verification and normalization processing, to obtain updated data corresponding to the target parameter; and sending a change instruction to the target device to instruct the target device to update the stored data of the target parameter according to the changed data. The user only needs to input a user request, and the terminal device automatically completes the change of device parameters, enabling faster and more accurate parameter changes.

Description

Technical Field

[0001] This application belongs to the field of data processing technology, and in particular relates to a method for changing device parameters, a terminal device, and a storage medium. Background Technology

[0002] In equipment management scenarios such as the Internet of Things for Energy, industrial control, new energy storage, and photovoltaic power plants, equipment parameter configuration is a core aspect of equipment commissioning, operation control, and strategy optimization.

[0003] With the increasing intelligence of equipment and the growing demand for on-site operation and maintenance, users are increasingly modifying equipment parameters remotely or locally through terminal applications and management platforms. The traditional method for changing parameters involves users locating the target parameter item on the configuration page, manually entering the target value, and then saving the change. However, due to users' lack of understanding of the parameter's meaning or uncertainty about its value range, errors in parameter modification often occur, affecting equipment operation. Summary of the Invention

[0004] This application provides a method for changing device parameters, a terminal device, and a storage medium, which can solve the problem that users often make mistakes when manually modifying device parameters, affecting device operation.

[0005] In a first aspect, embodiments of this application provide a method for changing device parameters, including: Receive a user request, wherein the user request is a request to change the target parameter in the target device to the first data; In response to the user request, a first interface is displayed, the first interface including a first control; Receive a first operation applied to the first control, the first operation being used to determine a change to the target parameter; In response to the first operation, a change instruction for the target parameter is sent to the target device, the change instruction including updated data for the target parameter.

[0006] In this application, upon receiving a user request, a first interface is displayed. After receiving a first operation applied to a first control, a change instruction for the target parameter is sent to the target device. Users of this application do not need to manually search for parameter items, calculate values, or understand complex communication protocols; they can complete parameter changes simply through request and confirmation operations. This significantly simplifies the parameter configuration process in scenarios such as industrial equipment and energy storage / photovoltaic power stations, reducing manual operation steps. It also solves the problem of users making modification errors due to unclear parameter meanings or unknown value ranges, avoiding parameter configuration errors from the interaction source and preventing risks such as abnormal equipment operation and malfunctioning protection systems.

[0007] In one possible implementation of the first aspect, after sending a change instruction for the target parameter to the target device in response to the first operation, the method further includes: The second interface is displayed, which includes the instruction execution result of the target device executing the change instruction. The instruction execution result includes whether the parameter change was successful or failed. If the instruction execution result includes the parameter change failed, the instruction execution result also includes the reason for failure and processing suggestions.

[0008] In this application, the execution result of the command is displayed after the parameter is changed, so that the user can clearly understand the final status of the change operation. When the change fails, the reason for the failure is automatically displayed, so that the user does not need to check the log or contact technical support, directly identify the root cause of the fault, and significantly improve the efficiency of fault location.

[0009] In one possible implementation of the first aspect, receiving the user request includes: The user request is received through a first application, which is an artificial intelligence application, and the first interface is the interface of the first application.

[0010] In this application, user requests are received by relying on artificial intelligence applications, and more flexible interaction methods such as natural language and voice are supported, eliminating the need for users to manually search for parameter items and greatly reducing the operational threshold.

[0011] In one possible implementation of the first aspect, displaying the first interface in response to the user request includes: In response to the user request, the first application sends a data acquisition instruction to the data processing module; After receiving the data acquisition instruction, the data processing module acquires the initial parameter information of the target device, wherein the initial parameter information includes a signal configuration table and the current signal value; The data processing module performs structured processing on the initial parameter information to obtain structured target parameter information; The data processing module sends the target parameter information to the first application; The first application performs a feasibility analysis on the user request based on the target parameter information to obtain a parameter description of the target parameter. The parameter description includes a functional explanation of the target parameter and a recommended modification value for the target parameter. The parameter description is used to instruct the user to determine whether to change the target parameter according to the recommended modification value. The first application displays the first interface, and the first interface also includes a parameter description of the target parameter; Accordingly, the first operation is used to determine to change the target parameter according to the recommended modification value; The change instruction includes updated data for the target parameter, and the updated data is the recommended modified value.

[0012] In this application, the initial parameters of the device are automatically acquired and structured to obtain target parameter information, enabling the first application to identify the target parameter information and generate parameter descriptions containing functional explanations based on the target parameter information, allowing users to clearly understand the function of the parameters; based on the actual state of the device, a feasibility analysis is performed and recommended modification values ​​are output, replacing blind input by users, and ensuring that the parameter values ​​are safe, compliant, and adapted to the current operating state of the device.

[0013] In one possible implementation of the first aspect, sending the change instruction for the target parameter to the target device in response to the first operation includes: In response to the first operation, the first application sends a parameter modification instruction to the data processing module, wherein the parameter modification instruction includes a recommended modification value for the target parameter; After receiving the parameter modification instruction, the data processing module performs parameter verification on the target parameter and obtains the verification result. The parameter verification includes at least one of the following: verification of the modification permission of the target parameter, verification of the modification range of the recommended modification value, and verification of the format of the recommended modification value. If the verification result is successful, the data processing module sends a change instruction for the target parameters to the target device.

[0014] In this application, the target parameters are validated to reduce issues such as out-of-range assignments and invalid formats, thereby lowering the parameter configuration error rate. Instructions are only issued after validation is passed, avoiding risks such as equipment protection failures, shutdowns, and logical errors due to invalid / non-compliant parameters, thus improving the operational stability of industrial and energy equipment.

[0015] In one possible implementation of the first aspect, if the verification result is a successful verification, the data processing module sends a change instruction for the target parameter to the target device, including: If the verification result is successful and the target parameter is a preset parameter, the data processing module performs normalization processing on the target parameter according to the recommended modification value to obtain the updated data corresponding to the target parameter. The normalization processing includes at least one of parameter combination processing, parameter recalculation processing, and parameter completion processing. The data processing module sends the target parameter change instruction to the target device.

[0016] In this application, the system automatically performs combination, recalculation, completion, and normalization processing for preset complex parameters, eliminating the need for manual calculation and coding by the user and fundamentally avoiding configuration errors caused by manual processing.

[0017] In one possible implementation of the first aspect, the data processing module sends a change instruction for the target parameter to the target device, including: The data processing module encrypts the updated data to obtain encrypted updated data. The data processing module obtains the device type of the target device; The data processing module searches for a data write interface that matches the device type to obtain the target interface; The data processing module sends the target parameter change instruction to the target device through the target interface.

[0018] This application enhances the security and confidentiality of parameter configuration in industrial control and energy IoT scenarios by encrypting updated data to prevent parameters from being stolen, tampered with, or forged during transmission. It also employs a dedicated interface matched to the device type to issue commands, avoiding communication failures and data parsing errors caused by interface incompatibility, significantly improving the success rate of parameter change execution.

[0019] In one possible implementation of the first aspect, the normalization process includes parameter recalculation of the dry contact signal; the user request is a dry contact signal dry node modification request, and the target parameter is the dry contact signal; The data processing module normalizes the target parameter based on the recommended modification value to obtain updated data corresponding to the target parameter, including: Obtain the current data of the dry contact signal; Identify the recommended modification value of the target parameter and determine the state of the digital input sub-port in the channel of the dry contact that needs to be modified; Based on the state of the digital input sub-port that needs to be modified, the digital input mask in the current data is modified to obtain the first data, wherein the digital input mask represents the start / stop state of the digital input sub-port; Based on the state of the digital input sub-port that needs to be modified, the digital input bit table in the current data is modified to obtain the second data, wherein the digital input bit table represents the parameter values ​​of the digital input sub-port in the enabled state; Based on the digital input bit table in the second data, the channel length of the dry contact signal is determined. Based on the channel length of the dry contact signal, the matrix length in the current data is modified to obtain the updated data corresponding to the target parameter.

[0020] Secondly, embodiments of this application provide a device for changing device parameters, including: A request receiving module is used to receive a user request, wherein the user request is a request to change the target parameter in the target device to the first data; The interface display module is used to respond to the user request and display a first interface, the first interface including a first control; An operation receiving module is used to receive a first operation applied to the first control, wherein the first operation is used to determine a change to the target parameter; The instruction sending module is configured to, in response to the first operation, send a change instruction for the target parameter to the target device, the change instruction including updated data for the target parameter.

[0021] Thirdly, embodiments of this application provide a terminal device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method for changing device parameters as described in any of the first aspects above.

[0022] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method for changing device parameters as described in any of the first aspects above.

[0023] Fifthly, embodiments of this application provide a computer program product that, when run on a terminal device, causes the terminal device to execute the device parameter modification method described in any of the first aspects above.

[0024] It is understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0025] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0026] Figure 1 This is a flowchart illustrating a method for changing device parameters according to an embodiment of this application; Figure 2 This is a flowchart illustrating a method for changing device parameters provided in another embodiment of this application; Figure 3This is a flowchart illustrating a method for generating parameter descriptions for modified parameters according to an embodiment of this application. Figure 4 This is a flowchart illustrating a parameter verification method for modifying parameters provided in an embodiment of this application; Figure 5 This is a flowchart illustrating a method for standardizing modified parameters according to an embodiment of this application; Figure 6 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. Detailed Implementation

[0027] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0028] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0029] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized.

[0030] In equipment management scenarios such as the Internet of Things for Energy, industrial control, new energy storage, and photovoltaic power plants, equipment parameter configuration and signal reading / writing are core aspects of equipment commissioning, operation control, and strategy optimization. Field devices such as inverters, energy storage systems, and charging piles typically contain hundreds of control signal points and configuration parameters. These parameters directly determine key performance characteristics such as equipment operating modes, power output, protection thresholds, and linkage logic.

[0031] With the increasing intelligence of equipment and the growing demand for on-site operation and maintenance, users are increasingly modifying equipment parameters remotely or locally through terminal applications and management platforms. Traditional parameter change methods often employ a fixed form configuration, manual value entry, and direct submission via a click-to-submit button. The process typically involves: the user finding the target parameter item on the configuration page → manually entering / selecting the target value → clicking the save button → the client directly sending a write command to the device.

[0032] However, traditional configuration interfaces only display parameter names and input controls, failing to provide users with crucial information such as parameter meanings, value ranges, impacts of modifications, and associated constraints. Ordinary users or non-professional maintenance personnel may struggle to accurately understand the purpose of these parameters, easily leading to misconfiguration due to insufficient knowledge, which can then cause equipment malfunctions, protection failures, or control strategy failures.

[0033] For device parameters that need to follow specific encoding rules, mask calculations, combinational logic, and field completion requirements, the traditional method requires users to manually calculate and fill them in, which is cumbersome and prone to errors, seriously affecting configuration efficiency and device stability.

[0034] To address the aforementioned issues, this application proposes a method for changing device parameters. This method can be applied to a user's terminal device (i.e., the user terminal), such as a mobile phone or computer. Specifically, the user only needs to input a user request, and the terminal device can automatically integrate and send the parameters to be updated, thus automatically changing the device parameters.

[0035] Below, we will first provide an overview of the methods for changing equipment parameters.

[0036] Obtain the user request, which includes the first data of the target parameters of the target device to be changed. The first data is the data that the user wants to update the target parameters to.

[0037] Obtain the initial parameter information of the target device, which includes the signal configuration table and the current signal value.

[0038] The initial parameter information is processed into a structured form to obtain the target parameter information.

[0039] A feasibility analysis is performed on the user request based on the target parameter information to obtain a parameter description of the target parameter. The parameter description includes a functional explanation of the target parameter and a recommended modification value for the target parameter. The parameter description is used to instruct the user to determine whether to change the target parameter according to the recommended modification value.

[0040] The parameter description shows that after receiving the confirmation modification instruction, the target parameter is processed according to the recommended modification value. The processing includes at least one of parameter validation and normalization processing to obtain the updated data corresponding to the target parameter.

[0041] The updated data is encrypted, and a change instruction is generated based on the encrypted updated data. The change instruction is then sent to the target device to instruct the target device to update the stored data of the target parameters according to the changed data.

[0042] Please refer to the following. Figure 1 To further explain the method of this application, the terminal device includes a first application and a data processing module. The first application is an artificial intelligence application.

[0043] S11, the first application receives the user request.

[0044] S12, the first application sends a data acquisition instruction to the data processing module.

[0045] S13, after receiving the data acquisition instruction, the data processing module sends a data query request to the target device.

[0046] S14 After receiving the data query request, the target device sends initial parameter information to the data processing module. The initial parameter information includes the signal configuration table and the current signal value.

[0047] S15, after receiving the initial parameter information, the data processing module performs structured processing on the initial parameter information to obtain the target parameter information.

[0048] S16, the data processing module sends the target parameter information to the first application.

[0049] S17, the first application analyzes the user request based on the target parameter information to obtain the parameter description of the target parameter to be updated. The parameter description includes the functional explanation of the target parameter and the recommended modification value of the target parameter.

[0050] S18, First Application Display Parameter Description.

[0051] S19, after receiving the user's confirmation instruction to modify the parameter, the first application sends the parameter modification instruction to the data processing module.

[0052] S20, after receiving the parameter modification instruction, the data processing module processes the target parameter, including at least one of parameter verification and normalization, to obtain the updated data corresponding to the target parameter.

[0053] S21, the data processing module encrypts the updated data and generates a change instruction for the target parameters based on the encrypted updated data.

[0054] S22, the data processing module sends a change command to the target device.

[0055] S23, after receiving the change instruction, the target device updates the stored data of the target parameters according to the update data.

[0056] S24, The target device sends the execution result of the change instruction to the data processing module.

[0057] S25, the data processing module sends the instruction execution result to the first application.

[0058] S26, the first application displays the instruction execution result. If the instruction execution result includes the parameter change failure, the first application analyzes the reason for the parameter update failure and generates processing suggestions. The instruction execution result also includes the failure reason and processing suggestions.

[0059] In another implementation, after receiving the user's confirmation modification instruction, the first application processes the target parameter, including at least one of parameter validation and normalization, to obtain updated data corresponding to the target parameter. The first application encrypts the updated data and generates a change instruction for the target parameter based on the encrypted updated data. The first application sends the change instruction to the data processing module. The data processing module then sends the change instruction to the target device.

[0060] For example, the user request is to "adjust the backup power SOC value of the target device to 30%". The first application, based on the target parameter information, determines the parameter description as follows: "Backup power SOC is the minimum charge the control battery retains during a power outage. The current value is 20%, with a range of 10%-50%. The recommended value is 2005=30". After user confirmation, the value of 30 is verified, and a change command for the target parameter is sent to the target device.

[0061] The method of this application will now be described in detail. For ease of description, the implementation of this application on the user end will be used as an example.

[0062] Figure 2 A schematic flowchart illustrating the method for changing equipment parameters provided in this application is shown, with reference to... Figure 2 The method is described in detail below: S101, Receive a user request, wherein the user request is a request to change the target parameter in the target device to the first data.

[0063] In this embodiment, the user request can be in text or voice form. A user request refers to an instruction or information issued by the user to the system that expresses their intention. Its core purpose is to instruct the user to change the target parameters in the target device to new data specified by the user.

[0064] The target device refers to the actual physical device on which this method is applied, such as a new energy storage system, a photovoltaic inverter, or a charging pile. The target device has configurable parameters, and its operating status and functions can be adjusted by modifying these parameters.

[0065] Target parameters refer to specific configuration items or signal points in the target device that need to be modified. Target parameters can be the device's operating mode, threshold settings, function switches, etc., and their value range and meaning are usually determined by the device type and model.

[0066] The first data refers to the new value or state of the target parameters after the user expects them to change, representing the user's expected configuration of the target device parameters.

[0067] For example, a user can type "Set device A's operating mode to energy-saving mode" in the text input box, or input "Adjust device B's temperature threshold to 25 degrees Celsius" via voice command. The client parses the user's request, identifying the target device, target parameters, and desired initial data. Alternatively, the client can receive user selections through preset menus or option lists, allowing users to express their intention to make changes by clicking or checking boxes.

[0068] For example, if a user requests to change the device's operating mode from mode A to mode B, then the target parameter is the operating mode parameter, and the first data is the mode B data.

[0069] S102, in response to the user request, a first interface is displayed, the first interface including a first control.

[0070] In this embodiment, the first interface refers to the interactive interface displayed to the user after the user terminal responds to the user's request. This interface is designed to present the user with detailed information about the request, potential impact, or confirmation options so that the user can make further decisions.

[0071] For example, a dialog box might pop up on the user's device, displaying the message, "Do you wish to change the operating mode of device A from the current standard mode to energy-saving mode?". This dialog box contains a primary control, such as an "OK" button.

[0072] S103, receive a first operation applied to the first control, the first operation being used to determine to change the target parameter.

[0073] In this embodiment, the first control refers to a graphical element on the first interface that the user can interact with, such as a button, checkbox, drop-down menu, or text input box. The user interacts with this control to express their intention to confirm, cancel, or modify.

[0074] The first action refers to the interactive behavior performed by the user on the first control, such as clicking a button, selecting an option, or entering text.

[0075] In another implementation, if a second operation is received, which determines that the target parameter should not be changed, a request input interface can be displayed to allow the user to re-enter the user request; or, a modification interface can be displayed, which includes a parameter modification box, through which the user enters the final data to which the target parameter needs to be changed.

[0076] S104, in response to the first operation, a change instruction for the target parameter is sent to the target device, the change instruction including updated data for the target parameter.

[0077] In this embodiment, a change command refers to a command generated by the user terminal after receiving user confirmation and sent to the target device to actually perform parameter modification. The change command typically includes an identifier for the target parameter and update data for updating that parameter. The update data refers to the actual data included in the change command used to modify the target parameter to a new value.

[0078] For example, if the user decides to modify the target parameter according to the first data, then the updated data in the change instruction will be the first data.

[0079] In this embodiment, upon receiving the first operation, the identifier of the target parameter and the first data are directly encapsulated into a simple command string and sent to the target device via a network interface; alternatively, the identifier of the target parameter and the first data are written into a predefined configuration file, and then the configuration file is sent to the target device via a file transfer protocol, whereby the target device parses and executes it. Upon receiving the change instruction, the target device executes the corresponding internal logic to update its target parameters with the updated data specified in the instruction.

[0080] In this application, users do not need to delve into complex device communication protocols or parameter encoding details; they can change device parameters simply through natural language interaction and confirmation. This method effectively lowers the barrier to entry for users by providing a clear interface and confirmation mechanism, while ensuring the accuracy of the changes.

[0081] In one possible implementation, after the user terminal sends a change command to the target device, in order to facilitate the user's understanding of the execution result of the user's request, the user terminal can also display the execution result of the command to the user after sending the change command.

[0082] Specifically, after step S104, the method may further include: The second interface is displayed, which includes the instruction execution result of the target device executing the change instruction. The instruction execution result includes whether the parameter change was successful or failed. If the instruction execution result includes the parameter change failed, the instruction execution result also includes the reason for failure and processing suggestions.

[0083] In this embodiment, the second interface can be a pop-up window, new page, or status bar notification in a graphical user interface, or text output in a command-line interface. The function of the second interface is to present feedback information on the device parameter change operation to the user. The instruction execution result can be a Boolean value (success / failure) or an enumeration type, such as success, failure, in progress, or timeout. Parameter change success or parameter change failure are the two main states of the instruction execution result, clearly indicating the final result of the change operation. This can be represented by predefined success codes (e.g., 0) and failure codes (e.g., non-zero), or by specific strings (e.g., "SUCCESS", "FAILURE").

[0084] The failure reason section provides a specific cause of the failure when a change fails, helping users understand the problem. The failure reason can be a predefined error code or error message, such as "Insufficient permissions," "Parameter out of range," or "Device offline," or it can be key information extracted from the device logs. The handling suggestions provide users with solutions or guidance based on the failure reason. Handling suggestions can be a list of preset solutions, such as "Please check your permission settings," "Please re-enter a value within the valid parameter range," or "Please check the device's network connection," or they can be links to help documentation or technical support pages.

[0085] This application displays the command execution results to the user, ensuring that the user can understand the final status of their operation in real time and clearly. Especially when problems occur, the user can obtain immediate diagnostic information and troubleshooting guidance, thereby effectively solving the problem of information opacity for the user during parameter changes.

[0086] In one possible implementation, to make the user terminal more intelligent and to update parameters more accurately and conveniently, an artificial intelligence application can be set up in the user terminal to trigger the parameter update operation.

[0087] The following section introduces how to update parameters using artificial intelligence applications.

[0088] The implementation process of step S101 may include: receiving a user request through a first application, wherein the first application is an artificial intelligence application, and the first interface is the interface of the first application.

[0089] In this embodiment, the first application refers to a software application that serves as the entry point for users to interact with the device parameter change system.

[0090] Artificial intelligence technologies can include, but are not limited to, natural language processing, machine learning, expert systems, and recommendation systems. For example, artificial intelligence applications can use natural language processing technology to understand a user's spoken or textual instructions, thereby transforming the user's unstructured requests into structured parameter change intentions; or, they can use machine learning models to analyze historical operation data and recommend better parameter settings or operation procedures to the user.

[0091] In one possible implementation, such as Figure 3 As shown, the implementation process of step S102 may include: S1021, in response to the user request, the first application sends a data acquisition instruction to the data processing module.

[0092] In this embodiment, the data acquisition instruction is used to trigger the data processing module to collect device parameter information related to the user request.

[0093] S1022, after receiving the data acquisition instruction, the data processing module acquires the initial parameter information of the target device, wherein the initial parameter information includes a signal configuration table and the current signal value.

[0094] In this embodiment, the data processing module obtains initial parameter information from the target device or related data source (database) based on the target device's device type, model version, product serial number, etc.

[0095] The signal configuration table defines the static configuration information of parameters (including target parameters) in the target device, such as their attributes, ranges, and dependencies.

[0096] Current signal value, i.e., the real-time or latest value of the parameters (including target parameters) on the target device.

[0097] S1023, the data processing module performs structured processing on the initial parameter information to obtain structured target parameter information.

[0098] In this embodiment, the data processing module performs structured processing on the initial parameter information. For example, it converts data of different formats into a standardized data structure to facilitate subsequent analysis and processing, thereby obtaining structured target parameter information.

[0099] Target parameter information may include title (display title), type (control type), maxVal / minVal (value range), validate (regular expression validation rule), hintText (input hint), filter (linked filtering conditions), readOnly (read-only attribute), signalComment (signal comment), signalRange (multi-segment range), etc.

[0100] S1024, the data processing module sends the target parameter information to the first application.

[0101] S1025, the first application performs a feasibility analysis on the user request based on the target parameter information to obtain a parameter description of the target parameter. The parameter description includes a functional explanation of the target parameter and a recommended modification value for the target parameter. The parameter description is used to instruct the user to determine whether to change the target parameter according to the recommended modification value.

[0102] In this embodiment, probability analysis may include parameter meaning explanation, risk analysis, modification analysis, and user intent parsing, aiming to assess the rationality, security, and potential impact of user requests. The analysis results will generate parameter descriptions for the target parameters. These descriptions not only include functional explanations of the target parameters to help users understand their role, but also provide a recommended modification value. The recommended modification value is the parameter value deemed most reasonable or optimal after intelligent analysis, used to guide users in making decisions.

[0103] In this embodiment, the parameter description may also include risk warnings, user intent feedback, and reasons for recommending modified values. The risk warning represents the linkage parameters affected by the change of the target parameter if the target parameter is modified.

[0104] S1026, the first application displays the first interface, and the first interface also includes a parameter description of the target parameter.

[0105] Accordingly, the first operation is used to determine to change the target parameter according to the recommended modification value. The change instruction includes updated data for the target parameter, wherein the updated data is the recommended modification value.

[0106] In this embodiment, when the first application displays the first interface, it also presents this parameter description to the user, enabling the user to decide whether to change the target parameter according to the recommended modification value based on sufficient information when performing the first operation. At this point, the user's first operation is no longer simply confirming their original request, but explicitly determining to change according to the recommended modification value provided by the first application. Therefore, the updated data included in the change instruction ultimately sent to the target device is the recommended modification value. This mechanism ensures the intelligence and security of the parameter change process, avoiding blind operations by the user due to insufficient information, thereby improving the accuracy and reliability of device configuration.

[0107] In another approach, if the user disagrees with modifying the target parameter according to the recommended value, the user can perform a second operation. At this point, a parameter modification box can be displayed, allowing the user to modify the final value of the target parameter. The final value is the updated data for the target parameter. Alternatively, multiple parameter options can be presented to the user, allowing them to select a satisfactory value from these options as the final data for the target parameter. The final data selected by the user is the updated data.

[0108] In this application, when a user requests to change device parameters, the system can proactively acquire and analyze relevant parameter information, and provide the user with parameter descriptions including functional explanations and recommended modification values. This allows users to obtain sufficient background information and professional modification suggestions when making parameter change decisions, thereby avoiding erroneous operations caused by information asymmetry or misunderstandings. This intelligent guidance mechanism significantly improves the accuracy, security, and user experience of parameter changes, effectively reduces device configuration risks, and optimizes device operating efficiency.

[0109] In one possible implementation, if the user-confirmed recommended modification value is sent directly to the target device without any verification after receiving the first operation, there may be potential risks. For example, the recommended modification value may exceed the device's allowed range or be in an incorrect format, which could lead to device parameter change failure or even device malfunction or system instability. Therefore, before sending the change instruction to the target device, the change data of the target parameters confirmed by the user can be verified first. Only after successful verification can the parameters be modified to ensure the accuracy of the target parameter modification.

[0110] Specifically, such as Figure 4 As shown, the implementation process of step S104 may include: S1041, in response to the first operation, the first application sends a parameter modification instruction to the data processing module, wherein the parameter modification instruction includes a recommended modification value for the target parameter.

[0111] S1042, after receiving the parameter modification instruction, the data processing module performs parameter verification on the target parameter and obtains the verification result. The parameter verification includes at least one of the following: verification of the modification permission of the target parameter, verification of the modification range of the recommended modification value, and verification of the format of the recommended modification value.

[0112] In this embodiment, the data processing module has preset verification rules and makes judgments based on the type, attributes, and business logic of the target parameters; alternatively, the data processing module can interact with external configuration management systems, permission management systems, or device specification databases to obtain the basis and rules required for verification.

[0113] Modification permission verification can include read-only verification and linked verification. For read-only verification, if the target parameter is read-only, it cannot be updated, and the verification result is failed. For linked verification, the target parameter is linked to other parameters; that is, whether the target parameter can be displayed, modified, or taken effect depends on whether the current state of one or more other signals on the device meets preset conditions. If the signal linked to the target parameter meets the preset conditions, the target parameter can be modified, and the verification result is passed; if the signal linked to the target parameter does not meet the preset conditions, the target parameter cannot be modified, and the verification result is failed. The permission characteristics of each parameter are stored in the initial parameter information.

[0114] The recommended modification range validation verifies whether the recommended modification value falls within the range of the target parameter. The range of the target parameter can be obtained from the initial parameter information and can be one or more ranges. If the recommended modification value is within the range of the target parameter, the validation passes; if the recommended modification value is not within the range of the target parameter, the validation fails.

[0115] The format validation of the recommended modification value is primarily to check whether the recommended modification value meets the format requirements. If the target parameter has format validation rules, the recommended modification value will be validated according to the format validation rules to obtain the validation result. The initial parameter information contains a description of the parameter format validation rules. For example, if the target parameter expects an integer value, but the recommended modification value is a floating-point number or a string, the format validation will fail. Furthermore, format validation can be performed through regular expression matching, data type conversion attempts, or predefined format templates; no restrictions are placed here.

[0116] For example, parameter verification includes verification of the modification permission of the target parameter, verification of the modification range of the recommended modification value, and verification of the format of the recommended modification value. The specific verification process is as follows.

[0117] Perform read-only verification on the target parameters.

[0118] If the target parameter is a read-only parameter, then no processing is performed on the target parameter, and the generated verification result is "verification failed".

[0119] If the target parameter is not a read-only parameter, perform a linkage check on the target parameter.

[0120] If the target parameter does not meet the rules of the linkage verification, the target parameter will not be processed, and the generated verification result will be "verification failed".

[0121] If the target parameter meets the rules of the linkage verification and the modified recommended value is a numerical data type, the modification range of the modified recommended value of the target parameter is verified.

[0122] If the modified recommended value is outside the modification range, the generated verification result will be "verification failed".

[0123] If the recommended value is within the modification range, or if the recommended value is not a numeric type, the format of the modified recommended value will be validated.

[0124] If the format validation passes, the generated validation result will be "Validation passed".

[0125] If the format validation fails, the generated validation result will be "Validation failed".

[0126] Of course, in actual use, the order of verification of the target parameter modification permission, the modification range of the recommended modification value, and the format of the recommended modification value can be set as needed, and no restrictions are imposed here.

[0127] S1043, if the verification result is successful, the data processing module sends a change instruction for the target parameter to the target device.

[0128] In another approach, if the verification result is that the verification fails, the data processing module sends the verification result to the first application, and the first application displays the verification result; or, the first application generates a new recommended modification value based on the reason for the verification failure, and displays the verification result, the reason for the verification failure, and the new recommended modification value.

[0129] In one possible implementation, complex parameters need to be processed before updating. Specifically, for example... Figure 5 As shown, the implementation process of step S1043 above may further include: S21, if the verification result is that the verification is passed and the target parameter is a preset parameter, the data processing module performs normalization processing on the target parameter according to the recommended modification value to obtain the updated data corresponding to the target parameter, wherein the normalization processing includes at least one of parameter combination processing, parameter recalculation processing and parameter completion processing.

[0130] In this embodiment, preset parameters refer to parameters that have specific functions, predefined behaviors, or are linked with other parameters in a device or system. These parameters are usually not independent, and their modification may trigger a series of related parameter adjustments, calculations, or supplements to ensure the logical consistency and functional integrity of the entire system configuration.

[0131] The preset parameters include dry contact signals, combined signals, and dependency completion signals. Combined signals are those that need to be combined with other signals to form a write group. Dependency completion signals are those that need to be written along with other information, which may include the target device's serial number, the serial number of the site where the target device is located, etc.

[0132] Normalization refers to further processing and transformation of the recommended modified values ​​that have passed verification, so that they conform to the specific configuration requirements and internal logic of the target device.

[0133] Parameter combination processing mainly targets combined signals. Signals that need to be written into a group with the target parameter are combined according to the upper limit of the number of signals in a group. The signals or parameters in the group are numbered and sorted so that the target device knows which parameter to process first and which parameter to process later.

[0134] Parameter completion processing mainly targets dependent completion signals. If a parameter or signal needs to include the device's serial number and other information in the target parameter, then the recommended modification value needs to be completed to add the required information.

[0135] Parameter recalculation primarily targets dry contact signals. It refers to the automatic recalculation and determination of new values ​​for affected parameters based on preset logical relationships or calculation formulas when a modification to one parameter affects other related parameters. For example, modifying the device's "sampling frequency" might require recalculating the "data buffer size" to maintain data flow stability; or, after modifying a primary parameter, its dependent parameters might need to be adjusted proportionally based on the new primary parameter value.

[0136] S22, the data processing module sends a change instruction for the target parameters to the target device.

[0137] In this embodiment, a verification specification table is set in advance, as shown in Table 1 below. The table is consulted to determine what parameter processing is required for the target parameters.

[0138] Table 1, Verification Rules Table:

[0139] In one possible implementation, step S22 may include: S31, the data processing module encrypts the updated data to obtain encrypted updated data.

[0140] In this embodiment, the written data is encrypted using an encryption algorithm. The encryption can employ a symmetric encryption algorithm, such as Advanced Encryption Standard (AES) or Data Encryption Standard (DES), using a pre-shared key to encrypt the written data. Alternatively, an asymmetric encryption algorithm can be used, encrypting the written data using the target device's public key, ensuring that only the target device holding the corresponding private key can decrypt it.

[0141] S32, the data processing module obtains the device type of the target device.

[0142] In this embodiment, the equipment type can include equipment from a conventional power plant and equipment from a PPC (Photovoltaic Power Controller) power plant. Different equipment types correspond to different interfaces.

[0143] Device type can also include identifying information such as specific model, manufacturer, functional category, or supported communication protocols. The data processing module can pre-store a device type database and retrieve the corresponding device type by querying the unique identifier of the target device during system initialization or device registration. Alternatively, the target device can proactively report its device type information to the data processing module when connecting to the system.

[0144] S33, the data processing module searches for a data writing interface that matches the device type and obtains the target interface.

[0145] In this embodiment, the data processing module can maintain an interface mapping table, which records the association between different device types and their corresponding data writing interfaces. When the target device type is obtained, the data processing module queries the mapping table to find the matching target interface.

[0146] S34, the data processing module sends the target parameter change instruction to the target device through the target interface.

[0147] In this application, when the data processing module needs to send a change instruction for target parameters to the target device, to ensure the security and compatibility of data transmission, the module first encrypts the update data to be sent, thereby generating encrypted update data. This effectively prevents the change instruction from being stolen or tampered with by unauthorized entities during data transmission, ensuring the confidentiality and integrity of parameter changes. By obtaining the device type of the target device and finding a matching data write interface, this solution can flexibly adapt to the communication needs of different types of devices, solving the communication compatibility problem caused by the diversity of device types. This enables the change instruction to be delivered to the target device securely, correctly, and efficiently, significantly improving the reliability and success rate of device parameter change operations and reducing the risks caused by communication failures or security vulnerabilities.

[0148] In one possible implementation, when processing specific types of device parameters, such as dry contact signal dry node modification requests, the parameter structure is complex, involving multiple interrelated sub-parameters (such as digital input masks, digital input bit tables, and matrix lengths). Simple normalization processing cannot ensure the synchronous and correct updating of these related parameters, which may lead to parameter configuration errors or abnormal device function. To address this, this application further proposes that the aforementioned normalization processing includes parameter recalculation of the dry contact signal. When the user request is a dry contact signal dry node modification request, and the target parameter is the dry contact signal, parameter recalculation processing is performed.

[0149] Specifically, methods for standardizing dry-connected electrical signals may include: S31, Obtain the current data of the dry contact signal.

[0150] In this embodiment, the current data is the current stored value of the dry contact signal.

[0151] Dry contacts are non-energized mechanical switches that transmit signals by opening and closing the contacts. A single channel contains multiple digital input sub-ports. Each digital input sub-port can be independently enabled or disabled to connect to different physical dry contact inputs. Dry contact signals comprise multiple channels (e.g., Channel 1, Channel 2, etc.). Each channel has an independent mask, bit table, and active / reactive power values.

[0152] The dry contact signal is a matrix structure. The data structure of the dry contact signal includes: an enable switch, matrix length, and channel information for multiple channels. Channel information includes a digital input mask (DI mask), a digital output mask (DI bit table), active power, and reactive power. Each bit of the DI mask represents whether a digital input sub-port is enabled (1 = enabled, 0 = disabled). The DI bit table contains only the specific parameter values ​​of the digital input sub-ports that are 1 in the DI mask, and its number is equal to the number of bits in the mask. The active power is the active power setting value corresponding to that channel. The reactive power is the reactive power setting value corresponding to that channel.

[0153] S32, identify the recommended modification value of the target parameter, and determine the state of the digital input sub-port in the channel where the dry contact signal needs to be modified.

[0154] In this embodiment, by analyzing the target parameters, it is determined whether the target parameters are dry contact signals. By analyzing the recommended modification values, it is determined whether the state of the digital input sub-ports in the channel should be changed.

[0155] For example, a dry node modification request could be: "Enable the digital input sub-port (DI sub-port) 5 of dry contact channel 3, i.e., target channel = 3, operation = enable, target bit = 5." Alternatively, a dry node modification request could be: "Disable DI sub-ports 2 and 7 of dry contact channel 1, i.e., target channel = 1, operation = disable, target bit = [2, 7]." Or, a dry node modification request could be: "Change the active power of dry contact channel 2 to 50%, i.e., target channel = 2, field = active power, value = 50." Or, a dry node modification request could be: "Add a 5th dry contact, DI sub-port 3 triggered, active power limit 80%, i.e., new channel = 5, enable bit = 3, active power = 80."

[0156] S33, based on the state of the digital input sub-port that needs to be modified, modify the digital input mask in the current data to obtain the first data, wherein the digital input mask represents the start / stop state of the digital input sub-port.

[0157] In this embodiment, the DI mask is a 16-bit register. Each bit of the DI mask represents whether a digital input sub-port is enabled or disabled. Therefore, modifying the enable / disable status of a DI sub-port will change the DI mask, thus requiring recalculation. For example, a DI mask of 0b0000_0000_0010_1101 = 0x002D indicates that DI sub-ports 0, 2, 3, and 5 are enabled.

[0158] Replace the numeric input mask in the current data with the newly calculated DI mask to obtain the first data.

[0159] For example, the dry node modification request is "Enable DI sub-port 4 of channel i". If the DI mask in the channel information of channel i in the original current data is 0b0000_0000_0010_1101, indicating that DI sub-ports 0, 2, 3, and 5 are enabled; then the DI mask modified according to the dry node modification request is 0b0000_0000_0011_1101, indicating that DI sub-ports 0, 2, 3, 4, and 5 are enabled.

[0160] S34, based on the state of the digital input sub-port that needs to be modified, modify the digital input bit table in the current data to obtain the second data, wherein the digital input bit table represents the parameter values ​​of the digital input sub-port in the enabled state.

[0161] In this embodiment, since the DI bit table only contains the specific parameter values ​​of the digital input sub-ports that are 1 in the DI mask, the DI bit table needs to be recalculated when the start / stop state of the digital input sub-port changes. After the DI mask changes, the DI bit table must be updated and deleted synchronously to maintain consistency with the DI mask.

[0162] When enabling a new DI subport, if a bit in the DI mask changes from 0 to 1, a new register value (default or user-specified value) needs to be inserted at the corresponding position in the DI bit table. The method for determining the insertion position of the new register value is as follows: for the newly enabled bit k, its index in the DI bit table = the number of bits set from bit 0 to bit (k-1) in the new mask (i.e., the number of all enabled bits below k).

[0163] For example, if the DI mask in the current data is 0b...0010_1101, and the DI bit table is [val_0, val_2, val_3, val_5], after enabling port 4, the DI mask becomes 0b...0011_1101, and the DI bit table becomes [val_0, val_2, val_3, val_4_new, val_5]. The DI bit table contains 5 parameter values.

[0164] To disable a DI subport, changing a bit in the DI mask from 1 to 0 requires shifting a register value (default or user-specified value) out of the corresponding position in the DI bit table.

[0165] S35, determine the channel length of the dry contact signal according to the digital input bit table in the second data, and modify the matrix length in the current data based on the channel length of the dry contact signal to obtain the updated data corresponding to the target parameter.

[0166] In this embodiment, the calculation of the single channel length is as follows: the number of registers for channel i = 1 (representing the DI mask) + popcount(mask_i) + 1 (active power) + 1 (reactive power) = popcount(mask_i) + 3, where popcount(mask_i) is the number of parameter values ​​in the digital input bit table of channel i.

[0167] For example, if the number of parameter values ​​in the DI bit table of a channel is 2, then the channel length is 2+3=5.

[0168] The length of the matrix is ​​the sum of the lengths of each channel. For example, if there are 3 channels, channel 1 has a length of 5, channel 2 has a length of 5, and channel 3 has a length of 6, then the length of the matrix is ​​5 + 5 + 6 = 16.

[0169] When calculating the matrix length, it is determined whether there is a channel with all zeros at the end (mask is 0, active power is 0, and reactive power is 0). If not, the channel lengths of all channels are added together to obtain the matrix length; if they exist, the channel with all zeros at the end is removed, and the channel lengths of the remaining channels are added together to obtain the matrix length.

[0170] In another implementation, if the dry node modification request is to modify the active power and / or reactive power of the channel, then the active power and / or reactive power of the channel in the current data can be modified directly without recalculating the DI mask, DI bit table and matrix length.

[0171] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0172] Corresponding to the device parameter changing method described in the above embodiments, this application embodiment also provides a device for changing device parameters.

[0173] The device may include: a request receiving module, an interface display module, an operation receiving module, and an instruction sending module.

[0174] The request receiving module is used to receive user requests, wherein the user request is a request to change the target parameter in the target device to the first data. The interface display module is used to respond to the user request and display a first interface, the first interface including a first control; An operation receiving module is used to receive a first operation applied to the first control, wherein the first operation is used to determine a change to the target parameter; The instruction sending module is configured to, in response to the first operation, send a change instruction for the target parameter to the target device, the change instruction including updated data for the target parameter.

[0175] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0176] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0177] This application also provides a terminal device, see [link to relevant documentation] Figure 6 The terminal device 400 may include: at least one processor 410, a memory 420, and a computer program stored in the memory 420 and executable on the at least one processor 410. When the processor 410 executes the computer program, it implements the steps in any of the above method embodiments, for example... Figure 2 Steps S101 to S104 in the illustrated embodiment. Alternatively, when the processor 410 executes the computer program, it implements the functions of each module / unit in the above-described device embodiments, such as the function of requesting the receiving module to send the instruction module.

[0178] For example, a computer program may be divided into one or more modules / units, one or more of which are stored in memory 420 and executed by processor 410 to complete this application. The one or more modules / units may be a series of computer program segments capable of performing a specific function, which are used to describe the execution process of the computer program in terminal device 400.

[0179] Those skilled in the art will understand that Figure 6This is merely an example of a terminal device and does not constitute a limitation on the terminal device. It may include more or fewer components than shown, or combine certain components, or different components, such as input / output devices, network access devices, buses, etc.

[0180] The processor 410 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0181] The memory 420 can be an internal storage unit of the terminal device or an external storage device, such as a plug-in hard drive, a smart media card (SMC), a secure digital (SD) card, or a flash card. The memory 420 is used to store the computer program and other programs and data required by the terminal device. The memory 420 can also be used to temporarily store data that has been output or will be output.

[0182] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0183] The method for changing device parameters provided in this application can be applied to terminal devices such as computers, tablets, laptops, netbooks, and personal digital assistants (PDAs). This application does not impose any restrictions on the specific type of terminal device.

[0184] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0185] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0186] In the embodiments provided in this application, it should be understood that the disclosed terminal devices, apparatuses, and methods can be implemented in other ways. For example, the terminal device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, apparatuses, or units, and may be electrical, mechanical, or other forms.

[0187] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0188] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0189] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by one or more processors, it can implement the steps of the various method embodiments described above.

[0190] Similarly, as a computer program product, when the computer program product is run on a terminal device, it enables the terminal device to implement the steps in the above-described method embodiments.

[0191] The computer program includes computer program code, which can be in the form of source code, object code, executable file, or some intermediate form. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium can be appropriately added or removed according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media may not include electrical carrier signals and telecommunication signals.

[0192] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method for changing equipment parameters, characterized in that, include: Receive a user request, wherein the user request is a request to change the target parameter in the target device to the first data; In response to the user request, a first interface is displayed, the first interface including a first control; Receive a first operation applied to the first control, the first operation being used to determine a change to the target parameter; In response to the first operation, a change instruction for the target parameter is sent to the target device, the change instruction including updated data for the target parameter.

2. The method as described in claim 1, characterized in that, After sending a change instruction for the target parameter to the target device in response to the first operation, the method further includes: The second interface is displayed, which includes the instruction execution result of the target device executing the change instruction. The instruction execution result includes whether the parameter change was successful or failed. If the instruction execution result includes the parameter change failed, the instruction execution result also includes the reason for failure and processing suggestions.

3. The method as described in claim 1, characterized in that, The receiving of user requests includes: The user request is received through a first application, which is an artificial intelligence application, and the first interface is the interface of the first application.

4. The method as described in claim 3, characterized in that, The step of displaying a first interface in response to the user request includes: In response to the user request, the first application sends a data acquisition instruction to the data processing module; After receiving the data acquisition instruction, the data processing module acquires the initial parameter information of the target device, wherein the initial parameter information includes a signal configuration table and the current signal value; The data processing module performs structured processing on the initial parameter information to obtain structured target parameter information; The data processing module sends the target parameter information to the first application; The first application performs a feasibility analysis on the user request based on the target parameter information to obtain a parameter description of the target parameter. The parameter description includes a functional explanation of the target parameter and a recommended modification value for the target parameter. The parameter description is used to instruct the user to determine whether to change the target parameter according to the recommended modification value. The first application displays the first interface, and the first interface also includes a parameter description of the target parameter; Accordingly, the first operation is used to determine to change the target parameter according to the recommended modification value; The change instruction includes updated data for the target parameter, and the updated data is the recommended modified value.

5. The method as described in claim 4, characterized in that, The step of sending a change instruction for the target parameter to the target device in response to the first operation includes: In response to the first operation, the first application sends a parameter modification instruction to the data processing module, wherein the parameter modification instruction includes a recommended modification value for the target parameter; After receiving the parameter modification instruction, the data processing module performs parameter verification on the target parameter and obtains the verification result. The parameter verification includes at least one of the following: verification of the modification permission of the target parameter, verification of the modification range of the recommended modification value, and verification of the format of the recommended modification value. If the verification result is successful, the data processing module sends a change instruction for the target parameters to the target device.

6. The method as described in claim 5, characterized in that, If the verification result is successful, the data processing module sends a change instruction for the target parameter to the target device, including: If the verification result is successful and the target parameter is a preset parameter, the data processing module performs normalization processing on the target parameter according to the recommended modification value to obtain the updated data corresponding to the target parameter. The normalization processing includes at least one of parameter combination processing, parameter recalculation processing, and parameter completion processing. The data processing module sends the target parameter change instruction to the target device.

7. The method as described in claim 6, characterized in that, The data processing module sends a change instruction for the target parameters to the target device, including: The data processing module encrypts the updated data to obtain encrypted updated data. The data processing module obtains the device type of the target device; The data processing module searches for a data write interface that matches the device type to obtain the target interface; The data processing module sends the target parameter change instruction to the target device through the target interface.

8. The method as described in claim 6, characterized in that, The normalization process includes recalculating the parameters of the dry contact signal; the user request is a dry contact signal dry node modification request, and the target parameter is the dry contact signal; The data processing module normalizes the target parameter based on the recommended modification value to obtain updated data corresponding to the target parameter, including: Obtain the current data of the dry contact signal; Identify the recommended modification value of the target parameter and determine the state of the digital input sub-port in the channel where the dry contact signal needs to be modified; Based on the state of the digital input sub-port that needs to be modified, the digital input mask in the current data is modified to obtain the first data, wherein the digital input mask represents the start / stop state of the digital input sub-port; Based on the state of the digital input sub-port that needs to be modified, the digital input bit table in the current data is modified to obtain the second data, wherein the digital input bit table represents the parameter values ​​of the digital input sub-port in the enabled state; Based on the digital input bit table in the second data, the channel length of the dry contact signal is determined. Based on the channel length of the dry contact signal, the matrix length in the current data is modified to obtain the updated data corresponding to the target parameter.

9. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method for changing device parameters as described in any one of claims 1 to 8.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the method for changing device parameters as described in any one of claims 1 to 8.

Images