Controller debugging methods, apparatus, equipment and computer-readable storage media

Abstract

This application provides a controller debugging method, apparatus, device, and computer-readable storage medium. The method includes: receiving identification information sent by a second terminal, the identification information being determined based on the model information of a first terminal, wherein the first terminal and the second terminal establish a communication connection; determining the control command to be debugged based on the identification information; controlling the controller to debug the control command to be debugged, obtaining a debugging result; and sending the debugging result to the second terminal. This eliminates the need for maintenance personnel to manually perform complex debugging operations or acquire extensive debugging knowledge, greatly simplifying the operation steps for maintenance personnel, reducing debugging difficulty, and improving maintenance efficiency.

Description

Technical Field

[0001] This application relates to the field of automation control technology, and includes, but is not limited to, a controller debugging method, apparatus, device, and computer-readable storage medium. Background Technology

[0002] In traditional technology, different models of garment processing equipment often use different controllers. When a controller malfunctions, most users cannot accurately tell the repair personnel the model of their garment processing equipment, increasing the risk that the repair personnel will bring the wrong spare part. Furthermore, repair stations must keep stock of every type of controller, putting significant pressure on their storage capacity.

[0003] To address the problems inherent in traditional technologies, a solution has been proposed: designing a universal hardware controller that stores software for multiple different models. When repair personnel visit the site, they manually adjust the controller's software on-site according to the required model of the garment processing equipment, ensuring the software model matches the equipment. While this solution resolves the issues of repair personnel bringing the wrong spare parts and the heavy inventory burden on repair stations, the on-site manual adjustment process is complex and requires repair personnel with a high level of knowledge. Summary of the Invention

[0004] In view of this, embodiments of this application provide a controller debugging method, apparatus, device, and computer-readable storage medium.

[0005] The technical solution of this application embodiment is implemented as follows:

[0006] This application provides a controller debugging method, applied to a first terminal, the method comprising:

[0007] The system receives identification information sent by a second terminal, the identification information being determined based on the model information of the first terminal, and the first terminal and the second terminal have established a communication connection.

[0008] The control command to be debugged is determined based on the identification information;

[0009] The controller is controlled to debug the control command to be debugged, and the debugging result is obtained;

[0010] The debugging results are sent to the second terminal.

[0011] In some embodiments, determining the control command to be debugged based on the identification information includes:

[0012] Based on the identification information, the control command corresponding to the identification information is searched in the first storage space of the first terminal to obtain the search result;

[0013] If the search results include control instructions, then the control instructions included in the search results are identified as the control instructions to be debugged.

[0014] In some embodiments, determining the control command to be debugged based on the identification information further includes:

[0015] If the search results do not include control commands, the control commands corresponding to the identification information are obtained from the third terminal based on the identification information.

[0016] The control commands obtained from the third terminal will be identified as the control commands to be debugged.

[0017] In some embodiments, the process of controlling the controller to debug the control command to be debugged and obtaining a debugging result includes:

[0018] Control the controller to start, and control the controller to enter debug mode;

[0019] In debug mode, the controller is controlled to invoke and identify the control command to be debugged, and the identification result is obtained;

[0020] The recognition result is determined to indicate successful recognition, and the debugging result of the controller is determined to be successful debugging;

[0021] If the identification result indicates identification failure, the debugging result of the controller is determined to be debugging failure;

[0022] Control the controller to exit the debug mode.

[0023] In some embodiments, the method further includes:

[0024] The interface display information corresponding to the control command is determined based on the identification information;

[0025] If the debugging result is successful, the display interface of the controller is updated according to the interface display information.

[0026] This application provides a controller debugging method applied to a second terminal, the method comprising:

[0027] Obtain the model information of the first terminal, and establish a communication connection between the first terminal and the second terminal;

[0028] Based on the model information, determine the identification information corresponding to the model information;

[0029] The identification information is sent to the first terminal so that the first terminal can determine the control command to be debugged based on the identification information, and control the controller to debug the control command to be debugged to obtain the debugging result;

[0030] Receive and output the debugging results sent by the first terminal.

[0031] In some embodiments, obtaining the model information of the first terminal includes:

[0032] Determine that a communication connection has been established between the first terminal and the second terminal, and receive the model information of the first terminal from the first terminal; or,

[0033] An input box is displayed in the display area of ​​the second terminal;

[0034] Receive the model information entered by the user in the input box.

[0035] In some embodiments, determining the identification information corresponding to the model information based on the model information includes:

[0036] Based on the model information, search for the corresponding identification information in the second storage space of the second terminal; or...

[0037] A query request carrying the model information is sent to a fourth terminal, so that the fourth terminal can determine the identification information corresponding to the model information based on the model information;

[0038] Receive the identification information sent by the fourth terminal.

[0039] This application provides a controller debugging device applied to a first terminal, the device comprising:

[0040] The first receiving module is used to receive identification information sent by the second terminal. The identification information is determined based on the model information of the first terminal. The first terminal and the second terminal have established a communication connection.

[0041] The first determining module is used to determine the control command to be debugged based on the identification information;

[0042] The control module is used to control the controller to debug the control command to be debugged and obtain the debugging result;

[0043] The first sending module is used to send the debugging results to the second terminal.

[0044] This application provides a controller debugging device for use in a second terminal, the device comprising:

[0045] The acquisition module is used to acquire the model information of the first terminal, which has established a communication connection with the second terminal.

[0046] The second determining module is used to determine the identification information corresponding to the model information based on the model information;

[0047] The second sending module is used to send the identification information to the first terminal, so that the first terminal determines the control command to be debugged according to the identification information, controls the controller to debug the control command to be debugged, and obtains the debugging result;

[0048] The second receiving module is used to receive the debugging results sent by the first terminal;

[0049] The output module is used to output the debugging results.

[0050] This application provides an electronic device, including:

[0051] Memory, used to store executable instructions;

[0052] The processor, when executing executable instructions stored in the memory, implements the steps of the controller debugging method described above.

[0053] This application provides a computer-readable storage medium storing computer-executable instructions configured to perform the steps of the controller debugging method described above.

[0054] The controller debugging method provided in this application involves a first terminal receiving identification information sent by a second terminal. This identification information is determined based on the model information of the first terminal, and a communication connection is established between the first and second terminals. The control command to be debugged is determined based on the identification information. The controller is then used to debug the control command to obtain a debugging result, which is then sent to the second terminal. This eliminates the need for maintenance personnel to manually perform complex debugging operations or acquire extensive debugging knowledge, greatly simplifying the operation steps for maintenance personnel, reducing debugging difficulty, and improving maintenance efficiency. Attached Figure Description

[0055] In the accompanying drawings (which are not necessarily drawn to scale), similar reference numerals may describe similar parts in different views. The drawings illustrate, by way of example and not limitation, the various embodiments discussed herein.

[0056] Figure 1 This is a schematic diagram illustrating an implementation flow of the controller debugging method provided in an embodiment of this application;

[0057] Figure 2 A schematic diagram illustrating another implementation flow of the controller debugging method provided in this application embodiment;

[0058] Figure 3 A schematic diagram illustrating another implementation flow of the controller debugging method provided in this application embodiment;

[0059] Figure 4 This is a schematic diagram illustrating an implementation process of the controller debugging system provided in an embodiment of this application;

[0060] Figure 5 A network structure diagram for setting up a control system via a mobile phone, provided in an embodiment of this application;

[0061] Figure 6 This is a schematic diagram of the controller control logic provided in an embodiment of this application;

[0062] Figure 7 This is a schematic diagram of the composition of the controller debugging device provided in the embodiments of this application;

[0063] Figure 8 This is a schematic diagram of the composition structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0064] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0065] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0066] In the following description, the terms "first, second, third" are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first, second, third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0067] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0068] Addressing the challenges of repairing and simplifying the maintenance of controllers in home appliances such as washing machines, dryers, and dishwashers, this application provides a controller debugging method for home appliances. The method provided in this application can be implemented using a computer program, which, upon execution, completes each step of the debugging method provided. In some embodiments, the computer program can be executed by a controller debugging device in an electronic device. Figure 1 This is a schematic diagram illustrating an implementation flow of the controller debugging method provided in an embodiment of this application, such as... Figure 1 As shown, the controller debugging method includes the following steps:

[0069] Step S101: Receive the identification information sent by the second terminal.

[0070] The debugging method provided in this application is applied to a first terminal, which can be a household appliance with a controller, such as a washing machine, a washer-dryer combo, or a dishwasher. The following description uses a washing machine as an example of the first terminal.

[0071] To avoid bringing the wrong spare parts during repairs and storing a large number of different controller models, this application embodiment provides controllers with the same hardware but different software for various different models of washing machines. This way, when repair personnel go to repair, they only need to bring a universal controller, and the repair station only needs to store the universal controller.

[0072] The second terminal here can be a mobile phone, tablet, laptop, or other similar device. This second terminal has an application (App) installed that can debug the controller in the washing machine. During repair, the repairman establishes a communication connection between the washing machine and the second terminal through the washing machine's internal communication module (such as a wireless WiFi module). The second terminal obtains the washing machine's model information and, based on the model, determines the identification information corresponding to that model. This identification information can be the identification information of one of the multiple software programs stored in the controller. The second terminal then sends the determined identification information to the washing machine.

[0073] Step S102: Determine the control command to be debugged based on the identification information.

[0074] Different software programs have different identification information, and each software program corresponds to a set of control instructions. In a washing machine, different sets of control instructions can execute different clothing processing programs, such as different clothing processing flows and processing parameters.

[0075] When a first terminal pre-stores various software programs and their identification information in its own first storage space, it can locate the target software program among the multiple software programs stored in its storage space after receiving the identification information. If the first terminal has not pre-stored any software programs, it can obtain the target software program from other devices that store software programs (such as a server).

[0076] After the first terminal identifies the target software program, it determines the control instructions to be debugged based on the target software program. Then, it debugs the control instructions to be debugged and ensures that there are no errors. After that, it updates the control instructions of the controller, thus realizing the update of the software program in the controller and completing the maintenance operation of the controller.

[0077] Step S103: The controller debugs the control command to be debugged and obtains the debugging result.

[0078] The first terminal calls the control command and identifies the control command. If the identification is successful, the controller is considered to be successfully debugged. If the identification fails, the control command debugging is considered to have failed, and a debugging result indicating whether the debugging is successful or failed is obtained.

[0079] Step S104: Send the debugging results to the second terminal.

[0080] After the first terminal completes the debugging of the controller, it sends the debugging results to the second terminal. The second terminal displays the debugging results on the App so that maintenance personnel can check whether the debugging was successful. If the debugging is successful, the controller repair is considered complete; otherwise, the repair operation continues. With the debugging method provided in this application embodiment, maintenance personnel only need to perform simple operations in the App on the second terminal. They do not need to manually perform complex debugging operations or learn extensive debugging knowledge to complete the controller debugging, greatly simplifying the operation steps for maintenance personnel, reducing debugging difficulty, and improving maintenance efficiency.

[0081] The controller debugging method provided in this application involves a first terminal receiving identification information sent by a second terminal. This identification information is determined based on the model information of the first terminal, and a communication connection is established between the first and second terminals. The control command to be debugged is determined based on the identification information. The controller is then used to debug the control command to obtain a debugging result, which is then sent to the second terminal. This eliminates the need for maintenance personnel to manually perform complex debugging operations or acquire extensive debugging knowledge, greatly simplifying the operation steps for maintenance personnel, reducing debugging difficulty, and improving maintenance efficiency.

[0082] In some embodiments, the above Figure 1In the illustrated embodiment, step S102, "determine the control command to be debugged based on the identification information," can be achieved through the following steps:

[0083] Step S1021: Based on the identification information, search for the control command corresponding to the identification information in the first storage space of the first terminal to obtain the search result.

[0084] Step S1022: Determine that the search results include control instructions, and identify the control instructions included in the search results as the control instructions to be debugged.

[0085] The first terminal has various software programs and their identification information pre-stored in the first storage space. After receiving the identification information, the first terminal searches for the target software program among the multiple software programs stored in the storage space. If the search is successful, the corresponding control instructions are determined based on the found target software program, resulting in a search result including that set of control instructions. The found set of control instructions is then identified as the control instructions to be debugged.

[0086] Step S1023: Determine that the search results do not include control commands, and obtain the control commands corresponding to the identification information from the third terminal based on the identification information.

[0087] If the first terminal cannot find the target software program corresponding to the identification information among the software programs pre-stored in the first storage space, there are two possibilities: either the identification information is incorrect, or the first terminal has not stored the control command corresponding to the identification information. In the latter case, the search results in the first storage space do not include the control command. In this case, the first terminal can expand its stored software programs from the server to add any software programs that were not pre-stored and their corresponding control commands.

[0088] Step S1024: The control command obtained from the third terminal is determined as the control command to be debugged.

[0089] The third terminal here can be the server mentioned above, or any other terminal that can establish a communication connection with the first terminal.

[0090] In this embodiment, the first terminal obtains the control command to be debugged from its own first storage space through identification information, and determines the control command to be debugged from the third terminal connected to the first terminal when the first storage space does not store it, thereby enabling the first storage space to be updated.

[0091] In some embodiments, the above Figure 1 In the illustrated embodiment, step S103, "the controller debugs the control command to be debugged and obtains the debugging result," can be achieved through the following steps:

[0092] Step S1031: Start the controller and control the controller to enter the debugging mode.

[0093] After the first terminal determines the control command to be debugged, the controller starts and enters the debugging mode.

[0094] In step S1032, in debug mode, the controller calls and identifies the control command to be debugged and obtains the identification result.

[0095] The first terminal controller invokes the control command to be debugged and identifies whether the control command matches the model information of the first terminal to ensure that the first terminal can control the controller to execute the corresponding software program after debugging. When the control command to be debugged matches the model information of the first terminal, the identification result is determined to be successful; when the control command to be debugged does not match the model information of the first terminal, the identification result is determined to be unsuccessful.

[0096] Step S1033: Determine that the recognition result indicates successful recognition, and determine the debugging result of the controller as successful debugging.

[0097] When the control command to be debugged is successfully recognized, the debugging result of the controller is determined to be successful. When the first terminal is working, the controller can execute the debugged control command normally.

[0098] Step S1034: Determine that the recognition result indicates recognition failure, and determine the controller's debugging result as debugging failure.

[0099] If the control command to be debugged fails to be recognized, the debugging result of the controller will be determined as a debugging failure. At this time, a debugging failure prompt message can be returned so that the maintenance personnel can re-execute the debugging operation.

[0100] Step S1035: Control the controller to exit debug mode.

[0101] The first terminal controller exited the debugging mode, completing this round of debugging.

[0102] In some embodiments, the first terminal may output the debugging results on its display panel for maintenance personnel to view.

[0103] Based on the above embodiments, this application further provides a method for debugging a controller. Figure 2 This is a schematic diagram illustrating another implementation flow of the controller debugging method provided in the embodiments of this application, as follows: Figure 2 As shown, the method includes the following steps:

[0104] Step S201: Receive the identification information sent by the second terminal.

[0105] During controller debugging, the maintenance personnel establish a communication connection between the first terminal and the second terminal through the communication module within the first terminal. The second terminal obtains the model information of the first terminal and determines the identification information based on this model information. This identification information is determined based on the model information of the first terminal. Then, the second terminal sends the determined identification information to the first terminal.

[0106] Step S202: Determine the control command to be debugged based on the identification information.

[0107] In one implementation, this step can be implemented as follows: based on the identification information, search for the control instruction corresponding to the identification information in the first storage space of the first terminal to obtain the search result; determine whether the search result includes the control instruction; when the search result includes the control instruction, determine the control instruction included in the search result as the control instruction to be debugged; when the search result does not include the control instruction, obtain the control instruction corresponding to the identification information from the third terminal based on the identification information; determine the control instruction obtained from the third terminal as the control instruction to be debugged.

[0108] Step S203: The controller debugs the control command to be debugged and obtains the debugging result.

[0109] In one implementation, this step can be implemented as follows: the controller is started and enters debug mode; in debug mode, the controller calls and identifies the control command to be debugged and obtains the identification result; it is determined whether the identification result indicates successful identification; when it is determined that the identification result indicates successful identification, the controller's debugging result is determined as successful debugging; when it is determined that the identification result indicates failure, the controller's debugging result is determined as failed debugging; finally, the controller exits debug mode.

[0110] Step S204: Send the debugging results to the second terminal.

[0111] The first terminal sends the debugging results to the second terminal, which then outputs the results in its display area, allowing maintenance personnel to view them on the second terminal.

[0112] Step S205: Determine the interface display information corresponding to the control command based on the identification information.

[0113] Step S206: If the debugging result is successful, update the controller's display interface according to the interface display information.

[0114] In practical applications, different software programs may display different interfaces. After successful debugging, the display interface is updated. Specifically, the target software program, i.e., the interface display information corresponding to the debugged control commands, is first determined based on the identification information. Then, the controller's display interface is updated according to the interface display information, so that the interface display information of the control panel matches the current control commands of the controller, facilitating user operation.

[0115] Figure 3 This is a schematic diagram illustrating another implementation flow of the controller debugging method provided in this application embodiment. The method is applied to a second terminal that has established a communication connection with the first terminal, such as... Figure 3 As shown, the method includes the following steps:

[0116] Step S301: Obtain the model information of the first terminal.

[0117] The second terminal here can be a mobile phone, tablet, laptop, or other similar device. This second terminal has an application (App) installed that can debug the controller of the first terminal. During repair, the technician establishes a communication connection between the first terminal and the second terminal through the communication module within the first terminal (such as a wireless WiFi module) to obtain the model information of the first terminal.

[0118] The model information here can be obtained by the second terminal from the first terminal. In this case, step S301 can be implemented as follows: confirming that a communication connection has been established between the first terminal and the second terminal, and receiving the model information from the first terminal. This model information can also be set by the maintenance personnel. In this case, step S301 can be implemented as follows: displaying an input box in the display area of ​​the second terminal; receiving information entered by the user in the input box; and determining the model information based on the information entered by the user. When the maintenance personnel enter complete model information, the information entered by the user is the model information. When the maintenance personnel enter partial information or keywords, the model information that is closest to the first terminal's model information is matched based on that partial information or keywords among all model information.

[0119] Step S302: Determine the identification information corresponding to the model information based on the model information.

[0120] When the second terminal stores a data table containing the correspondence between model information and identification information in its second storage space, it searches for the corresponding identification information in the second storage space based on the model information. When the second terminal does not store a data table containing the correspondence between model information and identification information, it sends a query request carrying model information to the fourth terminal, so that the fourth terminal can determine the corresponding identification information based on the model information. The second terminal then receives the identification information sent by the fourth terminal. This fourth terminal can be the same device as the first terminal or the third terminal, or it can be a different device; this embodiment does not limit the specific device.

[0121] In step S303, the identification information is sent to the first terminal so that the first terminal can determine the control command to be debugged based on the identification information, and the controller debugs the control command to be debugged to obtain the debugging result.

[0122] The first terminal controller debugs the control commands to be debugged and obtains the debugging results, which include debugging success and debugging failure.

[0123] Step S304: Receive and output the debugging results sent by the first terminal.

[0124] The controller debugging method provided in this application involves a second terminal acquiring the model information of a first terminal; determining identification information corresponding to the model information based on the model information; sending the identification information to the first terminal, so that the first terminal can determine the control command to be debugged based on the identification information, control the controller to debug the control command to be debugged, and obtain the debugging result; and receiving and outputting the debugging result sent by the first terminal. This eliminates the need for maintenance personnel to manually perform complex debugging operations or acquire extensive debugging knowledge to complete the controller debugging, greatly simplifying the operation steps for maintenance personnel, reducing debugging difficulty, and improving maintenance efficiency.

[0125] Based on the above embodiments, this application provides a debugging system. Figure 4 This is a schematic diagram illustrating an implementation flow of the controller debugging system provided in an embodiment of this application, such as... Figure 4 As shown, the system includes the following steps:

[0126] Step S401: The second terminal obtains the model information of the first terminal.

[0127] When debugging the controller, the maintenance personnel establish a communication connection between the first terminal and the second terminal through the communication module (such as a wireless WiFi module) in the first terminal, and then obtain the model information of the first terminal.

[0128] In step S402, the second terminal determines the identification information corresponding to the model information based on the model information.

[0129] When the second terminal has a data table containing the correspondence between model information and identification information stored in its second storage space, it searches for the identification information corresponding to the model information in the second storage space of the second terminal based on the model information; when the second terminal does not have a data table containing the correspondence between model information and identification information stored in its second storage space, the second terminal sends a query request carrying model information to the fourth terminal so that the fourth terminal can determine the identification information corresponding to the model information based on the model information; and receives the identification information sent by the fourth terminal.

[0130] In step S403, the second terminal sends the identification information to the first terminal.

[0131] In step S404, the first terminal determines the control command to be debugged based on the identification information.

[0132] In one implementation, this step can be implemented as follows: based on the identification information, search for the control instruction corresponding to the identification information in the first storage space of the first terminal to obtain the search result; determine whether the search result includes the control instruction; when the search result includes the control instruction, determine the control instruction included in the search result as the control instruction to be debugged; when the search result does not include the control instruction, obtain the control instruction corresponding to the identification information from the third terminal based on the identification information; determine the control instruction obtained from the third terminal as the control instruction to be debugged.

[0133] In step S405, the first terminal controller is started and the controller is put into debugging mode.

[0134] In step S406, the first terminal, in debug mode, controls the controller to call and identify the control command to be debugged, and obtains the identification result.

[0135] The first terminal controller invokes the control command to be debugged and identifies whether the control command matches the model information of the first terminal to ensure that the first terminal can control the controller to execute the corresponding software program after debugging. When the control command to be debugged matches the model information of the first terminal, the identification result is determined to be successful; when the control command to be debugged does not match the model information of the first terminal, the identification result is determined to be unsuccessful.

[0136] Step S407: The first terminal determines whether the recognition result indicates successful recognition.

[0137] When the identification result indicates successful identification, the controller debugging is confirmed to be successful, and the process proceeds to step S408; when the identification result indicates failed identification, the controller debugging is confirmed to be failed, and the process proceeds to step S411.

[0138] In step S408, the first terminal confirms the debugging result of the controller as successful.

[0139] When the control command to be debugged is successfully recognized, the debugging result of the controller is determined to be successful. When the first terminal is working, the controller can execute the debugged control command normally.

[0140] In step S409, the first terminal determines the interface display information corresponding to the control command based on the identification information.

[0141] In step S410, the first terminal updates the controller's display interface based on the information displayed on the interface.

[0142] In practical applications, different software programs may display different interfaces. After successful debugging, the display interface is updated. Specifically, first, the target software program, i.e., the interface display information corresponding to the debugged control command, is determined based on the identification information. Then, the controller's display interface is updated according to the interface display information, so that the interface display information of the control panel matches the current control command of the controller, facilitating user operation. After step S410 is completed, proceed to step S412.

[0143] In step S411, the first terminal determines the debugging result of the controller as a debugging failure.

[0144] If the control command to be debugged fails to be recognized, the debugging result of the controller will be determined as a debugging failure. At this time, a debugging failure prompt message can be returned so that the maintenance personnel can re-execute the debugging operation.

[0145] Step S412: The first terminal controller exits the debugging mode.

[0146] The first terminal controller exited the debugging mode, completing this round of debugging.

[0147] In step S413, the first terminal sends the debugging results to the second terminal.

[0148] Step S414: The second terminal outputs the debugging results.

[0149] The controller debugging system provided in this application embodiment debugs the controller of the first terminal through a first terminal and a second terminal with a communication connection. It eliminates the need for maintenance personnel to manually perform complex debugging operations or learn and accumulate a lot of debugging knowledge to complete the debugging of the controller, greatly simplifying the operation steps of maintenance personnel, reducing the debugging difficulty, and improving maintenance efficiency.

[0150] The following will describe an exemplary application of the embodiments of this application in a real-world application scenario.

[0151] Currently, machine controllers on the market are often only compatible with one model, or compatible with multiple models with identical hardware but different software. The software adapts to different models, requiring manual settings to update the controller's software. The first approach has many drawbacks: service centers need to maintain large quantities of various controllers, placing significant pressure on their storage capacity. Furthermore, multiple controllers with seemingly identical hardware but different software increase the risk of technicians bringing the wrong spare parts. The second approach, while alleviating storage pressure at service centers, requires technicians to perform complex manual controller operation procedures. In practice, lengthy instructions pose a significant challenge for technicians with lower levels of education, leading to resistance. After these evolutionary processes, a simplified method for updating controller control commands via a mobile app was finally developed.

[0152] The updated controller control instructions consist of three parts: The first part, S1, is a mobile app application. The app features a user interface (UI) where users can input the desired device model. A background database continuously maintains the list of configurable device models, with software versions ranging from tens of thousands. Based on the input device name, the background searches for matching software identifiers and sends the matched identifiers in a specific data format to the second part, S2, using existing Socket communication. The second part, S2, is a WiFi module firmware. This module can communicate with the first part, S1, via Socket communication, receiving commands and data from the mobile app. It can also connect to the controller via a Universal Asynchronous Receiver / Transmitter (UART) port, promptly sending the received data to the third part, S3. The third part, S3, is a controller that communicates with the WiFi module, analyzes and filters the received data, and stores the filtered identifiers in an Electrically Erasable Programmable Read-Only Memory (EEPROM). In the memory (EEPROM), after the machine is powered on, it calls and recognizes the control commands to realize the software update matching the model.

[0153] Figure 5 A network structure diagram for a control system via a mobile phone, provided in this application embodiment, includes the following components:

[0154] Part S1: Mobile App application software. The program interface is simple, displaying only key information, providing repair personnel with an easy-to-use and easy-to-understand interactive interface. Users only need to enter the model name to be set (e.g., ...). Figure 5 The MD100-1431DG shown will display the corresponding identification information, which is easy to verify against the instructions. After pressing the "Send" button in the app, it will directly return "Success" or "Failure," with a simple and clear result that is easy to understand. Maintaining the background program for newly added models is also relatively simple; it only requires continuously expanding the corresponding model name, software, and software identification information, making it easy for future maintainers. Users need to connect the WiFi module to the controller. The WiFi will automatically generate a hotspot. The phone unlocks to the hotspot, connects, and communication is established. After a successful handshake, the phone can set control commands for the controller, enabling rapid updates to the controller software.

[0155] Part S2: WiFi module. It uses existing mature technology, is small in size, easy to carry, and is a widely used component in washing machines, making it readily available. It supports Socket communication, facilitating command interaction with mobile apps, and its unique communication features effectively facilitate data transfer.

[0156] Part S3: Controller, a main control board used to control the normal operation of the machine and support user input of required parameters. It stores the identification information received from Part S2 into EEPROM and reads it to change the current software state of the controller and change the UI display of the controller.

[0157] The UI buttons also support manual update settings, but this is a traditional setting method, which is more cumbersome. However, this method can serve as a backup for phone-controlled updates, and can be used as an alternative when the phone runs out of power or other abnormal situations prevent phone settings from being used.

[0158] Figure 6 This is a schematic diagram of the controller control logic provided in the embodiments of this application, such as... Figure 6 As shown, it includes the following steps:

[0159] Step S601: The WiFi module is powered on and generates a hotspot.

[0160] Step S602: Connect to mobile hotspot.

[0161] Step S603: Determine if the connection is successful.

[0162] If the connection is successful, proceed to step S604; if the connection fails, return to step S602 to reconnect.

[0163] Step S604: The App searches for the correct device model.

[0164] Step S605: Send.

[0165] Step S606: Determine whether the reception was successful.

[0166] If the reception is successful, proceed to step S607; if the reception fails, return to step S605 and try to send again.

[0167] In step S607, the WiFi module sends data to the controller.

[0168] Step S608: The controller EEPROM stores the identification information.

[0169] Step S609: Power on the machine and determine whether the control command corresponding to the identification information in the EEPROM has been successfully read.

[0170] If the control instruction in the EEPROM is successfully read, proceed to step S610; if the reading fails, proceed to step S611.

[0171] Step S610: The machine software is configured with identification information that matches the machine model.

[0172] Step S611: The machine software is configured with the default model identification information.

[0173] Finish.

[0174] The control method provided in this application allows maintenance personnel to easily set up and update the software in the controller using a mobile app, greatly simplifying the operation steps, reducing debugging difficulty, and improving maintenance efficiency.

[0175] Based on the foregoing embodiments, this application provides a controller debugging device. The modules and units included in the device can be implemented by a processor in a computer device; of course, they can also be implemented by specific logic circuits. In the implementation process, the processor can be a central processing unit (CPU), a microprocessor unit (MPU), a digital signal processor (DSP), or a field programmable gate array (FPGA), etc.

[0176] Figure 7 This is a schematic diagram of the composition of the controller debugging device provided in the embodiment of this application. The controller debugging device 700 is applied to a first terminal, such as... Figure 7 As shown, the controller debugging device 700 includes:

[0177] The first receiving module 701 is used to receive identification information sent by the second terminal. The identification information is determined based on the model information of the first terminal. The first terminal and the second terminal have established a communication connection.

[0178] The first determining module 702 is used to determine the control command to be debugged based on the identification information;

[0179] Control module 703 is used to control the controller to debug the control command to be debugged and obtain the debugging result;

[0180] The first sending module 704 is used to send the debugging results to the second terminal.

[0181] In some embodiments, the first determining module 702 is further configured to:

[0182] Based on the identification information, the control command corresponding to the identification information is searched in the first storage space of the first terminal to obtain the search result;

[0183] If the search results include control instructions, then the control instructions included in the search results are identified as the control instructions to be debugged.

[0184] In some embodiments, the first determining module 702 is further configured to:

[0185] If the search results do not include control commands, the control commands corresponding to the identification information are obtained from the third terminal based on the identification information.

[0186] The control commands obtained from the third terminal will be identified as the control commands to be debugged.

[0187] In some embodiments, the control module 703 is further configured to:

[0188] Control the controller to start, and control the controller to enter debug mode;

[0189] In debug mode, the controller is controlled to invoke and identify the control command to be debugged, and the identification result is obtained;

[0190] The recognition result is determined to indicate successful recognition, and the debugging result of the controller is determined to be successful debugging;

[0191] If the identification result indicates identification failure, the debugging result of the controller is determined to be debugging failure;

[0192] Control the controller to exit the debug mode.

[0193] In some embodiments, the controller debugging device 700 may further include:

[0194] The third determining module is used to determine the interface display information corresponding to the control command based on the identification information;

[0195] The update module is used to update the display interface of the controller according to the interface display information when the debugging result is successful.

[0196] This application embodiment further provides a controller debugging device, which is applied to a second terminal, and the controller debugging device includes:

[0197] The acquisition module is used to acquire the model information of the first terminal, which has established a communication connection with the second terminal.

[0198] The second determining module is used to determine the identification information corresponding to the model information based on the model information;

[0199] The second sending module is used to send the identification information to the first terminal, so that the first terminal determines the control command to be debugged according to the identification information, controls the controller to debug the control command to be debugged, and obtains the debugging result;

[0200] The second receiving module is used to receive the debugging results sent by the first terminal;

[0201] The output module is used to output the debugging results.

[0202] In some embodiments, the acquisition module is further configured to:

[0203] Determine that a communication connection has been established between the first terminal and the second terminal, and receive the model information of the first terminal from the first terminal; or,

[0204] An input box is displayed in the display area of ​​the second terminal;

[0205] The model information is determined based on the information entered by the user in the input box.

[0206] In some embodiments, the second determining module is further configured to:

[0207] Based on the model information, search for the corresponding identification information in the second storage space of the second terminal; or...

[0208] A query request carrying the model information is sent to a fourth terminal, so that the fourth terminal can determine the identification information corresponding to the model information based on the model information;

[0209] Receive the identification information sent by the fourth terminal.

[0210] It should be noted that the descriptions of the controller debugging device embodiments above are similar to the method descriptions above, and have the same beneficial effects as the method embodiments. For technical details not disclosed in the controller debugging device embodiments of this application, those skilled in the art should refer to the descriptions of the method embodiments of this application for understanding.

[0211] It should be noted that, in the embodiments of this application, if the above-described controller debugging method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0212] Accordingly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps in the controller debugging method provided in the above embodiments.

[0213] This application provides an electronic device. Figure 8 This is a schematic diagram of the composition structure of the electronic device provided in the embodiments of this application. Figure 8 The exemplary structure of the electronic device 800 shown can be used to deduce other exemplary structures of the electronic device 800. Therefore, the structure described herein should not be regarded as a limitation. For example, some components described below may be omitted, or components not described below may be added to suit the specific needs of certain applications.

[0214] Figure 8 The illustrated electronic device 800 includes: a processor 801, at least one communication bus 802, a user interface 803, at least one external communication interface 804, and a memory 805. The communication bus 802 is configured to enable communication between these components. The user interface 803 may include a display panel, and the external communication interface 804 may include standard wired and wireless interfaces. The processor 801 is configured to execute a program of a controller debugging method stored in the memory to implement the steps of the controller debugging method provided in the above embodiments.

[0215] The descriptions of the above embodiments of the electronic devices and storage media are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the embodiments of the electronic devices and storage media of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0216] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above-described processes do not imply a sequential 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. The sequence numbers of the above-described embodiments are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0217] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

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

[0219] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units. They may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0220] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0221] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0222] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a product to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0223] The above description is merely an embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A controller debugging method, applied to household appliances with controllers, characterized in that, The method includes: The system receives identification information sent by a debugging terminal. The identification information is determined based on the model information of the home appliance, and the home appliance has established a communication connection with the debugging terminal. The debugging terminal has an application program (App) installed to debug the controller of the home appliance. The identification information is the identification information of one of the multiple software programs stored in the controller. The control command to be debugged is determined based on the identification information; The controller is controlled to debug the control command to be debugged, and the debugging result is obtained; The debugging results are sent to the debugging terminal; The step of determining the control command to be debugged based on the identification information includes: Based on the identification information, the target software program is determined from multiple software programs; Based on the target software program, the control instructions to be debugged are determined.

2. The method according to claim 1, characterized in that, The step of determining the control command to be debugged based on the identification information includes: Based on the identification information, the control command corresponding to the identification information is searched from the first storage space of the household appliance to obtain the search result; If the search results include control instructions, then the control instructions included in the search results are identified as the control instructions to be debugged.

3. The method according to claim 2, characterized in that, The step of determining the control command to be debugged based on the identification information further includes: If the search results do not include control commands, the control commands corresponding to the identification information are obtained from the third terminal based on the identification information. The control commands obtained from the third terminal will be identified as the control commands to be debugged.

4. The method according to claim 1, characterized in that, The controller adjusts the control command to be adjusted to obtain the adjustment result, including: Control the controller to start, and control the controller to enter debug mode; In debug mode, the controller is controlled to invoke and identify the control command to be debugged, and the identification result is obtained; The recognition result is determined to indicate successful recognition, and the debugging result of the controller is determined to be successful debugging; If the identification result indicates identification failure, the debugging result of the controller is determined to be a debugging failure. Control the controller to exit the debug mode.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: The interface display information corresponding to the control command is determined based on the identification information; If the debugging result is successful, the display interface of the controller is updated according to the interface display information.

6. A controller debugging method, applied to a debugging terminal, characterized in that, The method includes: The model information of the home appliance is obtained, and the home appliance establishes a communication connection with the debugging terminal; wherein, the debugging terminal is equipped with an application program (App) for debugging the controller of the home appliance; Based on the model information, identify information corresponding to the model information is determined; the identification information is the identification information of one of the multiple software programs stored in the controller; The identification information is sent to the home appliance so that the home appliance can determine the control command to be debugged based on the identification information, and control the controller to debug the control command to be debugged to obtain the debugging result; Receive and output the debugging results sent by the home appliance; The step of enabling the home appliance to determine the control command to be debugged based on the identification information includes: enabling the home appliance to determine a target software program from multiple software programs based on the identification information; and determining the control command to be debugged based on the target software program.

7. The method according to claim 6, characterized in that, The acquisition of the model information of the household appliances includes: It is confirmed that a communication connection has been established between the home appliance and the debugging terminal, and the model information of the home appliance is received from the home appliance; or, An input box is displayed in the display area of ​​the debugging terminal; The model information is determined based on the information entered by the user in the input box.

8. The method according to claim 6 or 7, characterized in that, The step of determining the identification information corresponding to the model information based on the model information includes: Based on the model information, search for the corresponding identification information in the second storage space of the debugging terminal; or... A query request carrying the model information is sent to a fourth terminal, so that the fourth terminal can determine the identification information corresponding to the model information based on the model information; Receive the identification information sent by the fourth terminal.

9. A controller debugging device, applied to household appliances with a controller, characterized in that, The device includes: The first receiving module is used to receive identification information sent by the debugging terminal. The identification information is determined based on the model information of the home appliance, and the home appliance has established a communication connection with the debugging terminal. The debugging terminal has an application program (App) installed to debug the controller of the home appliance. The identification information is the identification information of one of the multiple software programs stored in the controller. The first determining module is used to determine the control command to be debugged based on the identification information; The control module is used to control the controller to debug the control command to be debugged and obtain the debugging result; The first sending module is used to send the debugging results to the debugging terminal; The first determining module is further configured to determine a target software program from multiple software programs based on the identification information; and to determine the control instructions to be debugged based on the target software program.

10. A controller debugging device, applied to a debugging terminal, characterized in that, The device includes: The acquisition module is used to acquire the model information of the home appliance, which has a communication connection with the debugging terminal; the debugging terminal has an application program (App) installed to debug the controller in the home appliance; wherein, the home appliance has a controller; The second determining module is used to determine the identification information corresponding to the model information based on the model information; the identification information is the identification information of one of the multiple software programs stored in the controller; The second sending module is used to send the identification information to the home appliance, so that the home appliance can determine the control command to be debugged according to the identification information, control the controller to debug the control command to be debugged, and obtain the debugging result; The second receiving module is used to receive the debugging results sent by the household appliance; The output module is used to output the debugging results; The second sending module is further configured to send the identification information to the home appliance, so that the home appliance can determine the target software program from multiple software programs based on the identification information; and determine the control command to be debugged based on the target software program.

11. An electronic device, characterized in that, include: Memory, used to store executable instructions; A processor, when executing executable instructions stored in the memory, implements the steps of the controller debugging method according to any one of claims 1 to 5 or any one of claims 6 to 8.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions configured to perform the steps of the controller debugging method according to any one of claims 1 to 5 or any one of claims 6 to 8.

Images