Fault Information Processing Method, Device, Clothing Processing Equipment and Storage Medium

Abstract

The present application provides a fault information processing method, apparatus, clothing processing device and storage medium. The method includes: when it is detected that a clothing processing device has a fault, obtaining a first fault identifier; obtaining a second fault identifier from the storage space of the clothing processing device, where the second fault identifier is the previously stored fault identifier; when it is determined that the first fault identifier is different from the second fault identifier, storing the first fault identifier in the storage space. By setting a storage space for storing fault identifiers to store the fault identifiers corresponding to the faults that occur in the clothing processing device, it is possible to obtain the fault identifiers before power-off again after restart, which can improve the maintenance efficiency; by judging the fault identifiers before storing, not only can the storage times be reduced, but also more effective fault identifiers can be stored in the limited storage space, and it is also convenient for maintenance personnel to quickly locate the fault identifiers during maintenance, further improving the maintenance efficiency.

Description

Technical Field

[0001] The present application relates to the technical field of household appliances, and relates to, but is not limited to, a method and device for processing fault information, a laundry treatment device, and a computer-readable storage medium. Background Art

[0002] With the progress of science and technology, people's living standards are getting higher and higher. Laundry treatment devices, such as washing machines and washer-dryers, have become indispensable household appliances in people's lives. Usually, washing machines are equipped with a fault alarm function, and the fault indicators displayed during fault alarms are quite useful for analyzing the cause of faults during maintenance. Currently, most washing machines do not save the fault indicators. Once the washing machine is powered off, the fault indicators cannot be redisplayed. It is only possible to restart the operation for a period of time and wait for the fault to occur again before analyzing the cause of the fault based on the number of times the indicator light flashes or the fault indicator displayed by the digital tube. Sometimes, the fault may be triggered in a certain specific environment, and the waiting time for the fault to occur again may be relatively long, affecting the maintenance efficiency.

[0003] In the related art, one solution to the above problem is that when a washing machine has a fault, it sends the fault indicator to a terminal through a network, and the terminal stores the fault indicator. This method has relatively high requirements for the washing machine, and the washing machine needs to be connected to the network in real time during the washing process. The problem that the fault indicator cannot be redisplayed still cannot be solved in the case of network disconnection; another solution is to set a memory in the washing machine to store the fault indicators generated during the operation of the washing machine. However, in the related art, the fault indicators of each fault are stored, which not only causes waste of storage space, but also requires multiple operations to locate the fault indicator during maintenance, and the operation is cumbersome, affecting the maintenance efficiency. Summary of the Invention

[0004] In view of this, embodiments of the present application provide a method and device for processing fault information, a laundry treatment device, and a computer-readable storage medium.

[0005] The technical solution of the embodiments of the present application is implemented as follows:

[0006] Embodiments of the present application provide a method for processing fault information, which is applied to a laundry treatment device. The method includes:

[0007] When it is detected that the laundry treatment device has a fault, obtain a first fault indicator;

[0008] Obtain a second fault indicator from the storage space of the laundry treatment device, where the second fault indicator is the previously stored fault indicator;

[0009] When it is determined that the first fault indicator is different from the second fault indicator, store the first fault indicator in the storage space.

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

[0011] When it is determined that the first fault identifier is the same as the second fault identifier, obtaining the time when the laundry treatment device fails and the storage time of the second fault identifier;

[0012] Determining a fault time difference according to the time when the laundry treatment device fails and the storage time of the second fault identifier;

[0013] When it is determined that the fault time difference is greater than a preset duration, storing the first fault identifier in the storage space.

[0014] In some embodiments, storing the first fault identifier in the storage space includes:

[0015] Obtaining a second fault index value corresponding to the second fault identifier in the storage space;

[0016] Determining a first fault index value corresponding to the first fault identifier according to the second fault index value;

[0017] Based on the first fault index value, storing the first fault identifier in the storage space.

[0018] In some embodiments, determining a first fault index value corresponding to the first fault identifier according to the second fault index value includes:

[0019] Determining whether the second fault index value is the last index value in the storage space;

[0020] When it is determined that the second fault index value is the last index value, determining the first index value in the storage space as the first fault index value;

[0021] When it is determined that the second fault index value is not the last index value, determining the next index value of the second fault index value as the first fault index value.

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

[0023] Counting the number of times the first fault identifier appears;

[0024] When the number reaches a preset number threshold, obtaining at least one fault cause corresponding to the first fault identifier from the storage space;

[0025] Outputting the at least one fault cause.

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

[0027] Obtain request information for querying a fault identifier;

[0028] In response to the request information, control the laundry treatment device to enter a fault query mode;

[0029] Obtain a third fault identifier from the storage space of the laundry treatment device, where the third fault identifier is the last stored fault identifier;

[0030] Output the third fault identifier.

[0031] In some embodiments, in response to a query operation for querying a historical fault identifier received, obtain a third fault index value corresponding to the third fault identifier in the storage space;

[0032] When it is determined that the third fault index value is the last index value in the storage space, determine the first index value in the storage space as a fourth fault index value.

[0033] Output a fourth fault identifier corresponding to the fourth fault index value.

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

[0035] When it is determined that the third fault index value is not the last index value in the storage space, determine whether there is a fault identifier corresponding to the next index value of the third fault index value;

[0036] When it is determined that there is a fault identifier corresponding to the next index value of the third fault index value, determine the next index value of the third fault index value as a fourth fault index value;

[0037] When it is determined that there is no fault identifier corresponding to the next index value of the third fault index value, determine the first index value in the storage space as a fourth fault index value.

[0038] An embodiment of the present application provides a fault information processing device, which is applied to a laundry treatment device. The device includes:

[0039] A first obtaining module, configured to obtain a first fault identifier when it is detected that the laundry treatment device has a fault;

[0040] A second obtaining module, configured to obtain a second fault identifier from the storage space of the laundry treatment device, where the second fault identifier is the previously stored fault identifier;

[0041] A storage module, configured to store the first fault identifier into the storage space when it is determined that the first fault identifier is different from the second fault identifier.

[0042] An embodiment of the present application provides a laundry treatment device, which includes:

[0043] A memory, configured to store executable instructions;

[0044] A processor, configured to implement the steps of the above-mentioned fault information processing method when executing the executable instructions stored in the memory.

[0045] An embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and the computer-executable instructions are configured to execute the steps of the above-mentioned fault information processing method.

[0046] An embodiment of the present application provides a fault information processing method, apparatus, laundry treatment device and computer-readable storage medium. The method includes: when a fault occurs in the laundry treatment device is detected, obtaining a first fault identifier; obtaining a previously stored second fault identifier from the storage space of the laundry treatment device; when the first fault identifier is different from the second fault identifier, storing the first fault identifier into the storage space. In this way, a storage space for storing fault identifiers is set in the laundry treatment device, and the fault identifiers corresponding to the faults occurring in the laundry treatment device are stored, so that the fault identifiers before power-off can be obtained again after restart, which is convenient for analyzing the cause of the fault and improving the maintenance efficiency. And when storing, the fault identifiers are judged, and when the first fault identifier is different from the previously stored second fault identifier, it is stored. There is no need to continuously store multiple identical fault identifiers, which can not only reduce the number of storage times, but also store more effective fault identifiers in the limited storage space, and can also facilitate the maintenance personnel to quickly locate the fault identifiers during maintenance, further improving the maintenance efficiency. Description of the Drawings

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

[0048] Figure 1 It is a schematic flowchart of an implementation of the fault information processing method provided by an embodiment of the present application;

[0049] Figure 2 It is another schematic flowchart of an implementation of the fault information processing method provided by an embodiment of the present application;

[0050] Figure 3Another schematic implementation flowchart of the fault information processing method provided by the embodiments of this application;

[0051] Figure 4 Schematic flowchart of the background fault memory method provided by the embodiments of this application;

[0052] Figure 5 Schematic flowchart of the background fault query method provided by the embodiments of this application;

[0053] Figure 6 Schematic diagram of the structure of the control panel and the display panel provided by the embodiments of this application;

[0054] Figure 7 Schematic diagram of the composition structure of the washing machine provided by the embodiments of this application;

[0055] Figure 8 Schematic diagram of the composition structure of the fault information processing device provided by the embodiments of this application;

[0056] Figure 9 Schematic diagram of the composition structure of the clothing processing equipment provided by the embodiments of this application. Detailed implementation manners

[0057] In order to make the objectives, technical solutions and advantages of this application clearer, the following will further describe this application in detail with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this application.

[0058] In the following description, "some embodiments" are involved, which describe a subset of all possible embodiments. However, it can be understood that "some embodiments" can be the same subset or different subsets of all possible embodiments, and can be combined with each other without conflict.

[0059] In the following description, the terms "first / second / third" involved are only used to distinguish similar objects, and do not represent a specific order for the objects. It can be understood that "first / second / third" can be interchanged with a specific order or sequence when allowed, so that the embodiments of this application described here can be implemented in an order other than that illustrated or described here.

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

[0061] In related technologies, when a clothing processing device such as a washing machine or a washer-dryer malfunctions, a fault identifier is generated and displayed on the display panel, but the fault identifier is not stored locally. As a result, when the power is cut off and the device is restarted, the fault identifier is no longer displayed, and it is necessary to run the device again to reproduce the fault in order to display the fault identifier again, which is not convenient for maintenance personnel to perform repairs. In view of this problem, an embodiment of the present application provides a fault information processing method applied to a clothing processing device. This fault information processing method can be implemented by a computer program. When the computer program is executed, it completes each step in the fault information processing method provided by the embodiment of the present application. In some embodiments, the computer program can be executed by a fault information processing device in the clothing processing device. Figure 1 FIG. is a schematic flowchart of an implementation process of the fault information processing method provided by an embodiment of the present application. As Figure 1 shown, the fault information processing method includes the following steps:

[0062] Step S101, when it is detected that the clothing processing device malfunctions, obtain a first fault identifier.

[0063] The fault information processing method provided by an embodiment of the present application is applied to clothing processing devices such as washing machines, dryers, and dishwashers. In the embodiment of the present application, a washing machine is taken as an example for illustration.

[0064] When a user uses a washing machine to wash clothes, various faults may occur during the entire washing process of the washing machine: some are faults caused by improper human operation, such as a door lock fault caused by the door not being closed, and a water inlet timeout fault caused by the faucet not being opened; some are faults caused by the washing machine itself, such as a water inlet timeout fault caused by a blocked water inlet valve, and a motor fault caused by the motor being blocked; and some are faults caused by other reasons such as low water pressure, resulting in a water inlet timeout fault, and so on. When the washing machine malfunctions, a corresponding fault identifier is generated according to the fault cause and displayed on the display panel of the washing machine so that the user can know what kind of fault the washing machine has occurred. For example, the fault identifier "E1", and the user can query the user manual to know that this fault identifier represents a door lock fault. Another example is that the fault identifier "E2" represents a drainage timeout fault.

[0065] When the washing machine detects that it has malfunctioned, the controller in the washing machine determines the fault identifier according to the location where the fault occurs, and uses this fault identifier as the first fault identifier.

[0066] Step S102, obtain a second fault identifier from the storage space of the clothing processing device.

[0067] In the related art, most washing machines do not have a storage space for storing fault identifiers. When a fault occurs, the fault identifier is only displayed on the display panel and cannot be reproduced after power-off. For faults caused by washing machine failures, professional maintenance personnel are generally required for repair. When repairing a washing machine, either the user needs to inform the maintenance personnel of the fault identifier they remember, or the washing process needs to be run again, and the maintenance personnel can only know what kind of fault has occurred to the washing machine when the washing machine fails again, which seriously affects the repair efficiency. In view of this problem, in the embodiments of the present application, a dedicated storage space is provided in the washing machine to store historical fault identifiers. The fault identifiers stored in this storage space are not affected by power-off. Even if the washing machine is powered off, the fault identifiers corresponding to the previous faults of the washing machine are still stored in the storage space. In this way, after the washing machine is restarted, the fault identifiers that occurred to the washing machine before can be obtained by querying this storage space, without the need for the user to remember, nor the need to run the washing process again, greatly saving the time of maintenance personnel and improving the repair efficiency.

[0068] In the embodiments of the present application, after the washing machine fails and obtains the first fault identifier, the second fault identifier stored previously is obtained from the storage space, that is, the fault identifier that was most recently stored in the storage space, so as to determine whether the first fault identifier needs to be stored according to the second fault identifier. Specifically, it is determined whether the first fault identifier is the same as the second fault identifier. When the first fault identifier is the same as the second fault identifier, it indicates that the fault identifier corresponding to the currently occurring fault is the same as the fault identifier corresponding to the previous fault. For these two consecutive faults, they may be caused by the same reason. In order to save the occupancy of the storage space, in the embodiments of the present application, when the first fault identifier is the same as the second fault identifier, the first fault identifier is no longer stored. When the first fault identifier is different from the second fault identifier, step S103 is entered.

[0069] Step S103: When it is determined that the first fault identifier is different from the second fault identifier, store the first fault identifier in the storage space.

[0070] In the embodiments of the present application, when it is determined that the first fault identifier is different from the second fault identifier, it is considered that the faults occurring to the washing machine twice in a row are different. At this time, the first fault identifier corresponding to the currently occurring fault is stored, avoiding storing multiple identical fault identifiers continuously. In this way, not only can the number of storage times be reduced, but also more effective fault identifiers can be stored in the limited storage space, and it can also enable the maintenance personnel to quickly locate the fault identifier without having to view multiple consecutive and repeated fault identifiers during maintenance, further improving the repair efficiency.

[0071] For example, if the second fault identifier stored in the washing machine last time is "E1", and the first fault identifier corresponding to the current fault is "E2", and the first fault identifier is different from the second fault identifier, then the first fault identifier "E2" is stored; if the first fault identifier corresponding to the current fault is "E1", and the first fault identifier is the same as the second fault identifier, then the first fault identifier "E1" is not stored repeatedly.

[0072] Here, the first fault identifier is compared with the second fault identifier stored last time, rather than with other fault identifiers stored even earlier. This is because when the fault identifiers corresponding to consecutive multiple faults are the same, the faults that occur may be the same fault. However, when the fault identifiers corresponding to non - consecutive multiple faults are the same, it is impossible to determine whether the faults that occur are the same fault. Therefore, only the fault identifier stored last time is compared to avoid missing the storage of fault identifiers and affecting the maintenance personnel's analysis of the fault cause.

[0073] The fault information processing method applied to a laundry treatment device provided in an embodiment of the present application includes: when a fault of the laundry treatment device is detected, obtaining a first fault identifier; obtaining a second fault identifier from the storage space of the laundry treatment device, where the second fault identifier is the fault identifier stored last time; and when it is determined that the first fault identifier is different from the second fault identifier, storing the first fault identifier in the storage space. In this way, a dedicated storage space for storing fault identifiers is set in the laundry treatment device to store the fault identifiers corresponding to the faults that occur in the laundry treatment device, so that the fault identifiers before power - off can be obtained again after restart, which is convenient for analyzing the fault cause, improving the maintenance efficiency. And when storing, the fault identifier is judged, and it is stored when the first fault identifier is different from the second fault identifier stored last time. There is no need to continuously store multiple identical fault identifiers, which can not only reduce the storage times, but also store more effective fault identifiers in the limited storage space, and can also facilitate the maintenance personnel to quickly locate the fault identifier during maintenance, further improving the maintenance efficiency.

[0074] In some embodiments, when it is determined that the first fault identifier is the same as the second fault identifier, the first fault identifier is no longer stored. In this way, there is no need to continuously store multiple identical fault identifiers, which can reduce the number of storage times. When the time of the current fault is relatively close to the time of the previous fault, if the first fault identifier is the same as the second fault identifier, the causes of these two faults are probably the same; but when the time of the current fault is relatively long after the time of the previous fault and the washing machine can operate normally for a long time during this period, even if the first fault identifier is the same as the second fault identifier, the causes of these two faults may be different. At this time, if the first fault identifier corresponding to the current fault is not stored, it may affect the maintenance personnel's judgment of the fault information, and thus may prolong the maintenance time. Based on this, when it is determined that the first fault identifier is the same as the second fault identifier, the following steps are executed:

[0075] Step S11, obtain the time when the laundry treatment device fails and the storage time of the second fault identifier.

[0076] The time when the laundry treatment device fails is the current time. The storage time of the second fault identifier is close to the time when the laundry treatment device has a fault corresponding to the second fault identifier. Therefore, the storage time of the second fault identifier is equivalent to the time when the laundry treatment device has a fault corresponding to the second fault identifier.

[0077] Step S12, determine the fault time difference according to the time when the laundry treatment device fails and the storage time of the second fault identifier.

[0078] For example, the second fault identifier stored previously in the washing machine is "E1", and the first fault identifier corresponding to the current fault is also "E1". The first fault identifier is the same as the second fault identifier. Obtain the time when the second fault identifier was stored previously, such as June 2, 2021, and the current time corresponding to the current fault is June 27, 2021. Then subtract the storage time of the second fault identifier from the current time, and the obtained fault time difference is equal to 25 days.

[0079] Step S13, determine whether the fault time difference is greater than a preset duration.

[0080] When the fault time difference is greater than the preset duration, it indicates that the time intervals between these two faults are relatively long, and the faults with the same identifier may be caused by different reasons. At this time, enter step S14; when the fault time difference is less than or equal to the preset duration, it indicates that the time intervals between these two faults are relatively close, and it is considered that the faults with the same identifier are caused by the same reason. At this time, the first fault identifier is no longer stored.

[0081] Here, the preset duration can be the initial value set at the factory or the custom value set by the user. For example, the preset duration can take any value from 1 day to 30 days.

[0082] Step S14, store the first fault identifier into the storage space.

[0083] In the embodiments of the present application, when it is determined that the first fault identifier is the same as the second fault identifier, it is further determined whether the time interval between two consecutive faults of the washing machine is greater than a preset duration. When the time interval is less than or equal to the preset duration, it is considered that the two faults are caused by the same reason. At this time, the first fault identifier is not stored anymore. When the time interval is greater than the preset duration, it is considered that the two faults may be caused by different reasons. At this time, the first fault identifier corresponding to the currently occurring fault is stored. In this way, while reducing the storage times, the accuracy of fault analysis can be improved, thereby improving the maintenance efficiency.

[0084] In some embodiments, to store the first fault identifier into the storage space, one implementation method is to store it in order in the storage space according to the storage order. For example, the fault identifier stored for the Nth time is stored in the Nth storage unit of the storage space. When searching, the fault identifiers can be searched in the storage order. The advantage of this storage method is convenient storage, but the disadvantage is that a large storage space is required. During maintenance, multiple repeated query operations are required to locate the fault identifier corresponding to the fault to be repaired, and the operation is cumbersome.

[0085] To store the first fault identifier into the storage space, another implementation method is to store it based on an index method, which can be implemented through the following steps S1031 to S1033.

[0086] Step S1031, obtain the second fault index value corresponding to the second fault identifier in the storage space.

[0087] In the storage space, there is a unique second fault index value corresponding to the second fault identifier. This second fault index value is less than or equal to the maximum index value. According to the second fault index value, the second fault identifier can be quickly found.

[0088] Step S1032, determine the first fault index value corresponding to the first fault identifier according to the second fault index value.

[0089] The second fault index value is the index value corresponding to the previously stored fault identifier. According to the second fault index value, the first fault index value corresponding to the first fault identifier to be stored this time is determined.

[0090] Step S1033, based on the first fault index value, store the first fault identifier into the storage space.

[0091] Based on the determined first fault index value, store the first fault identifier to be stored this time.

[0092] In the embodiments of the present application, the fault identifier is stored based on the index value, which facilitates subsequent querying of the fault identifier based on the index value, can reduce the search time, and thus further improve the maintenance efficiency.

[0093] In some embodiments, the above step S1032 "determine the first fault index value corresponding to the first fault identifier according to the second fault index value" can be implemented by the following steps:

[0094] Step S10321, determine whether the second fault index value is the last index value in the storage space.

[0095] When it is determined that the second fault index value is the last index value, the storage space after this will no longer store the fault identifier, and at this time, step S10322 is entered; when it is determined that the second fault index value is not the last index value in the storage space, step S10323 is entered.

[0096] Step S10322, determine the first index value in the storage space as the first fault index value.

[0097] When the second fault index value is the last index value, the storage space after the storage space storing the second fault identifier will no longer be used to store the fault identifier, and the first fault identifier is stored again in the storage space corresponding to the first index value. For example, 1 to 20 index values are preset in the storage space, and in the first 20 times of storage, they are stored in the storage space corresponding to the corresponding ordinal index value in sequence. The second fault index value is the last index value, that is, the index value of the second fault identifier is 20, and the index value 20 is already the maximum fault index value. The first index value in the storage space (i.e., index value 1) is used as the first fault index value, and the first fault identifier stored this time is stored in the storage space corresponding to index value 1. That is to say, the historical fault identifier corresponding to index value 1 is overwritten by the first fault identifier stored this time.

[0098] Step S10323, determine the next index value of the second fault index value as the first fault index value.

[0099] When the second fault index value is not the last index value, the storage space after the storage space storing the second fault identifier is still used to store fault identifiers, and the next index value of the second fault index value is determined as the first fault index value. For example, if the second fault index value corresponding to the stored second fault identifier is index value 10, and index value 10 is not the last index value, then the next index value of index value 10 in the storage space (i.e., index value 11) is used as the first fault index value, and the first fault identifier stored this time is stored in the storage space corresponding to index value 11. When there is no corresponding fault identifier for index value 11, it indicates that the corresponding fault identifier has not been stored before, and the first fault identifier is directly stored; when there is a corresponding fault identifier for index value 11, the first fault identifier stored this time overwrites the historically stored fault identifier corresponding to index value 11.

[0100] Based on the index method for storage, only a small amount of storage space is required to store fault identifiers. The maintenance personnel can locate the fault identifier corresponding to the fault to be repaired by repeating the operation at most the maximum index value times, which can reduce the operation times of the maintenance personnel. The disadvantage is that it will overwrite the previously stored fault identifiers and cannot query fault identifiers exceeding the maximum index value.

[0101] In some embodiments, when a fault identifier is recorded multiple times without repetition, it indicates that this component of the washing machine is likely to have problems. At this time, the user can be reminded in time to perform maintenance or replacement to avoid causing greater faults in the washing machine. Specifically, it can be achieved through the following steps:

[0102] Step S104, count the number of times the first fault identifier appears.

[0103] Step S105, when the number of times reaches the preset number threshold, obtain at least one fault cause corresponding to the first fault identifier from the storage space.

[0104] For example, the preset number threshold is 5. When the cumulative number of times the first fault identifier "E2" appears reaches 5 times, obtain the fault cause corresponding to "E2" from the storage space, and at least one fault cause corresponding to each fault identifier has been previously stored in the storage space. The fault causes obtained from the storage space corresponding to the "E2" drainage timeout fault include at least one of: the drain pipe is not put down, the drain pipe is deformed and twisted, foreign objects are blocked, the drain valve fails, the drainage circuit fails, and the drainage controller fails.

[0105] Step S106, output at least one fault cause.

[0106] Here, the at least one fault cause can be displayed on the display panel of the washing machine, or the at least one fault cause can be sent to the user terminal for display, so that the user or the maintenance personnel can repair the fault occurred in the washing machine according to the output fault cause. For example, for the drainage timeout fault, the fault handling methods include: 1) Check whether the drain pipe has been put down; 2) Check whether the drain pipe is deformed or twisted; 3) Check whether the drain pipe is unobstructed and whether there is any foreign object blocking the drain pipe; 4) Check whether the drain valve of the washing machine is blocked and determine whether the tension spring of the drain valve has fallen off or is corroded and broken; 5) Check whether there is a fault in the circuit; 6) Check whether the drain controller has a fault.

[0107] In the embodiment of the present application, by counting the number of occurrences of the fault identifier, when the number of occurrences of the same fault identifier reaches the preset number threshold, the fault cause that may generate the fault identifier is automatically output to remind the user to check and repair in time.

[0108] In the above embodiment, it mainly describes storing the fault information when a fault occurs in the fault information processing method. Next, it continues to describe how to query the fault identifier after storage. Figure 2 Another implementation process schematic diagram of the fault information processing method provided by the embodiment of the present application is as Figure 2 shown, and the method includes the following steps:

[0109] Step S201, obtain the request information for querying the fault identifier.

[0110] The request information can be triggered based on the query operation performed by the user or the maintenance personnel. For example, a button for entering the fault query mode is set on the control panel of the washing machine. When the maintenance personnel press the button, the fault information processing device of the washing machine obtains the request information for querying the fault identifier.

[0111] Here, the request information can be defaulted to query the fault identifier stored most recently, so that the user or the maintenance personnel can obtain the fault identifier corresponding to the most recent fault at the fastest speed to process and repair the most recent fault.

[0112] In some other embodiments, the request information can also be the request information for querying the target fault identifier. At this time, the target fault identifier to be queried is carried in the request information. For example, when querying whether the washing machine has had a drainage timeout fault, the target fault identifier "E2" is carried in the request information.

[0113] Step S202, in response to the request information, control the laundry handling device to enter the fault query mode.

[0114] Step S203, obtain the third fault identifier from the storage space of the laundry handling device.

[0115] The third fault identifier is the last stored fault identifier. In some other embodiments, when the requested information is to find a target fault identifier, if the target fault identifier is stored in the storage space, the third fault identifier is the found target fault identifier; if the target fault identifier is not stored in the storage space, it is considered that the washing machine has not had a fault corresponding to the target fault identifier. At this time, the third fault identifier can be "NULL".

[0116] Step S204, output the third fault identifier.

[0117] When the third fault identifier is the last stored fault identifier, the third fault identifier is displayed on the display panel of the washing machine, or the third fault identifier is output through a user terminal connected to the washing machine via a network, so that the user or the maintenance personnel can view the fault identifier corresponding to the last fault and analyze the cause of the fault based on this fault identifier to eliminate the fault.

[0118] When the third fault identifier is the target fault identifier, outputting the third fault identifier indicates that the washing machine has had a fault corresponding to this fault identifier, which is convenient for the maintenance personnel to perform targeted maintenance; when the target fault identifier does not exist in the storage space, output "NULL" to prompt the maintenance personnel that the washing machine has not had a fault corresponding to the target fault identifier.

[0119] In some embodiments, after outputting the third fault identifier, other previously stored fault identifiers can continue to be searched in the storage space based on the index value. Based on this, after the above step S204, the above method can further include the following steps:

[0120] Step S205, in response to a query operation for querying historical fault identifiers received, obtain the third fault index value corresponding to the third fault identifier in the storage space.

[0121] This query operation can be that the washing machine presses the "+" button in the fault query mode to query the historical fault identifiers before the last fault identifier, so that the maintenance personnel can troubleshoot and repair earlier faults.

[0122] Step S206, determine whether the third fault index value is the last index value in the storage space.

[0123] The last index value in the storage space is the preset maximum index value. When it is determined that the third fault index value is the last index value in the storage space, return the first index value and enter step S207; when it is determined that the third fault index value is not the last index value in the storage space, enter step S208.

[0124] Step S207, determine the first index value in the storage space as the fourth fault index value.

[0125] After determining the fourth fault index value, proceed to step S210.

[0126] Step S208: Determine whether there is a fault identifier that has a corresponding relationship with the next index value of the third fault index value.

[0127] If the third fault index value is not the maximum index value and there is a corresponding fault identifier for its subsequent index value, it is determined that there is a fault identifier that has a corresponding relationship with the next index value of the third fault index value, and proceed to step S209; if the third fault index value is not the maximum index value but there is no corresponding fault identifier for its subsequent index value, it is determined that there is no fault identifier that has a corresponding relationship with the next index value of the third fault index value, and at this time, proceed to step S207.

[0128] Step S209: Determine the next index value of the third fault index value as the fourth fault index value.

[0129] Step S210: Output the fourth fault identifier corresponding to the fourth fault index value.

[0130] In the embodiment of the present application, querying the fault identifier based on the index value can improve the query speed of the fault identifier, thereby improving the maintenance efficiency.

[0131] In some embodiments, after step S204 "output the third fault identifier", it is also possible to display the fault cause corresponding to the third fault identifier based on the user's operation. The specific implementation is as follows:

[0132] Step S211: In response to a query operation for querying the fault cause triggered for the third fault identifier, obtain at least one fault cause corresponding to the third fault identifier from the storage space.

[0133] Step S212: Output at least one fault cause.

[0134] For example, there is a button for querying the fault cause on the washing machine control panel. After outputting a certain fault identifier, if the user or maintenance personnel wants to obtain the cause of the fault corresponding to this fault identifier, they can press this button, obtain at least one fault cause corresponding to this fault identifier from the storage space according to the fault identifier, and output the at least one fault cause queried on the display panel, which is convenient for users who are not familiar with the washing machine fault identifier to know the fault cause and is convenient for maintenance.

[0135] Based on the above-described embodiments, the embodiment of the present application further provides a fault information processing method applied to a laundry treatment device. Figure 3 This is another schematic diagram of the implementation process of the fault information processing method provided by the embodiment of the present application. As Figure 3 shown, this fault information processing method includes the following steps:

[0136] Step S301, when a failure of the laundry treatment device is detected, obtain a first failure identifier.

[0137] When the washing machine detects its own failure, the controller in the washing machine determines a failure identifier according to the location where the failure occurs, and uses this failure identifier as the first failure identifier.

[0138] Step S302, obtain a second failure identifier from the storage space of the laundry treatment device.

[0139] This second failure identifier is the failure identifier stored previously.

[0140] Step S303, determine whether the first failure identifier is the same as the second failure identifier.

[0141] When the first failure identifier is the same as the second failure identifier, proceed to step S310 to further determine whether the time interval between the two failures is greater than a preset duration. When the first failure identifier is different from the second failure identifier, store the first failure identifier. Here, when storing, it can be stored in sequence in the storage space, or stored based on an index. When storing based on an index, it can be implemented as steps S304 to S308.

[0142] Step S304, obtain the second failure index value corresponding to the second failure identifier in the storage space.

[0143] In the storage space, there is a unique second failure index value corresponding to the second failure identifier, and this second failure index value is less than or equal to the maximum index value. According to the second failure index value, the second failure identifier can be quickly found.

[0144] Step S305, determine whether the second failure index value is the last index value in the storage space.

[0145] When the second failure index value is the preset maximum index value, determine that the second failure index value is the last index value in the storage space, and proceed to step S306; when the second failure index value is less than the preset maximum index value, determine that the second failure index value is not the last index value in the storage space, and proceed to step S307.

[0146] Step S306, determine the first index value in the storage space as the first failure index value.

[0147] When the second failure index value is the last index value, the storage space after the storage space for storing the second failure identifier is no longer used for storing failure identifiers, and the first failure identifier is stored again in the storage space corresponding to the first index value.

[0148] Step S307, determine the next index value of the second fault index value as the first fault index value.

[0149] When the second fault index value is not the last index value, the storage space after the storage space storing the second fault identifier is still used to store the fault identifier, and determine the next index value of the second fault index value as the first fault index value.

[0150] Based on the above steps S305 to S307, implement determining the first fault index value corresponding to the first fault identifier according to the second fault index value.

[0151] Step S308, based on the first fault index value, store the first fault identifier into the storage space.

[0152] Step S309, end the storage.

[0153] After ending the storage, continue to execute step S313 to determine whether a request message for querying the fault identifier is received. Here, after ending the storage, if the washing machine is powered off, it will not affect the stored fault identifiers.

[0154] Step S310, obtain the time when the laundry handling device fails and the storage time of the second fault identifier.

[0155] Here, the time when the laundry handling device fails is the current time.

[0156] Step S311, determine the fault time difference according to the time when the laundry handling device fails and the storage time of the second fault identifier.

[0157] Here, the time when the laundry handling device fails can be subtracted from the storage time of the second fault identifier, and the obtained difference is determined as the fault time difference.

[0158] Step S312, determine whether the fault time difference is greater than a preset duration.

[0159] When the fault time difference is greater than the preset duration, it indicates that the two fault occurrence times are separated by a relatively long time, and it may be the fault of the same identifier caused by different reasons. At this time, enter step S304; when the fault time difference is less than or equal to the preset duration, it indicates that the two fault occurrence times are relatively close, and it is considered to be the fault of the same identifier caused by the same reason. At this time, enter step S313, and no longer store the first fault identifier.

[0160] Step S313, determine whether a request message for querying the fault identifier is obtained.

[0161] When the request information for querying the fault identifier by the user is obtained, it indicates that the user or the maintenance personnel is performing a fault query operation, and step S314 is entered; when the request information is not obtained, step S324 is entered to end the fault information processing process.

[0162] Step S314, in response to the request information, control the laundry treatment device to enter the fault query mode.

[0163] Step S315, obtain the third fault identifier from the storage space of the laundry treatment device.

[0164] The third fault identifier is the last stored fault identifier. If the first fault identifier is different from the second fault identifier, the third fault identifier is the last stored first fault identifier; if the first fault identifier is the same as the second fault identifier, the third fault identifier is the last stored second fault identifier.

[0165] Step S316, output the third fault identifier.

[0166] After outputting the third fault identifier information, continue to execute step S317.

[0167] Step S317, determine whether a query operation for querying the historical fault identifier is received.

[0168] When a query operation for querying the historical fault identifier is received, it indicates that the user needs to query an earlier stored fault identifier, and step S318 is entered; when a query operation for querying the historical fault identifier is not received, it indicates that the user only queries the last stored fault identifier, and at this time, step S324 is entered to end the fault information processing process.

[0169] Step S318, in response to the received query operation for querying the historical fault identifier, obtain the third fault index value corresponding to the third fault identifier in the storage space.

[0170] Step S319, determine whether the third fault index value is the last index value in the storage space.

[0171] When the third fault index value is equal to the preset maximum index value, it is determined that the third fault index value is the last index value in the storage space, and step S320 is entered; when the third fault index value is less than the preset maximum index value, it is determined that the third fault index value is not the last index value in the storage space, and step S321 is entered.

[0172] Step S320, determine the first index value in the storage space as the fourth fault index value.

[0173] After determining the fourth fault index value, step S323 is entered.

[0174] Step S321: Determine whether there is a fault identifier corresponding to the next index value of the third fault index value.

[0175] If the third fault index value is not the maximum index value and there is a corresponding fault identifier for its subsequent index value, it is determined that there is a fault identifier corresponding to the next index value of the third fault index value, and proceed to step S322; if the third fault index value is not the maximum index value but there is no corresponding fault identifier for its subsequent index value, it is determined that there is no fault identifier corresponding to the next index value of the third fault index value, and at this time, proceed to step S320.

[0176] Step S322: Determine the next index value of the third fault index value as the fourth fault index value.

[0177] Step S323: Output the fourth fault identifier corresponding to the fourth fault index value.

[0178] In the embodiment of the present application, querying the fault identifier based on the index value can improve the query speed of the fault identifier, thereby improving the maintenance efficiency.

[0179] Step S324: End.

[0180] The fault information processing method provided by the embodiment of the present application sets a storage space for storing fault identifiers in the clothing processing device, stores the fault identifiers corresponding to the faults that occur in the clothing processing device, so that the fault identifiers before power-off can be obtained again after restart, which is convenient for analyzing the cause of the fault and improving the maintenance efficiency. And when storing, the fault identifiers are judged, and when the first fault identifier is different from the second fault identifier stored last time, it is stored. There is no need to continuously store multiple identical fault identifiers, which can not only reduce the storage times, but also store more effective fault identifiers in the limited storage space, and can also facilitate the maintenance personnel to quickly locate the fault identifiers during maintenance, further improving the maintenance efficiency.

[0181] Next, the exemplary application of the embodiment of the present application in an actual application scenario will be described.

[0182] In the related art, most washing machines do not have a storage space for storing fault identifiers. When a fault occurs, the fault identifier is only displayed on the display panel and cannot be reproduced after power-off. Some washing machines send the fault identifier when a fault occurs to the user terminal through the network. If there is a problem with the network, there is still no need to store it. And when storing based on the network, during maintenance, the fault identifier must be obtained again through the network, which brings inconvenience to the maintenance personnel. The embodiment of the present application proposes a solution for the computer board to remember the fault identifier in the background. This solution does not need to rely on the network to implement background fault memory and fault query. By querying the fault identifier in the background and analyzing the fault phenomenon according to the fault identifier, the problem can be located and the fault can be repaired.

[0183] The fault memory method proposed in the embodiment of the present application can record n fault identifiers, and the adjacent fault identifiers recorded are different, that is, each time a fault occurs, it is compared with the previous fault identifier remembered to see if they are the same. If they are not the same, it is recorded in the storage area (that is, the storage space mentioned above).

[0184] Figure 4 It is a schematic flowchart of the background fault memory method provided by the embodiment of the present application. As Figure 4 shown, this background fault memory method includes the following steps:

[0185] Step S401, after the controller is powered on, it first reads the adjacent fault identifier and fault index value from the fault memory module.

[0186] Step S402, when an error occurs, compare whether the current fault identifier is the same as the adjacent fault identifier. If they are the same, ignore this fault.

[0187] Step S403, if the current fault identifier is not the same as the adjacent fault identifier, then add 1 to the fault index value.

[0188] Step S404, record this fault identifier and fault index value in the fault storage module.

[0189] In fault memory, after the computer board is powered on, first the controller will read the adjacent fault identifier and fault index value from the storage device. If the fault detection module detects that a current fault occurs and compares the current fault identifier with the adjacent fault identifier to see if they are the same. If they are the same, ignore this fault; if they are not the same, then add 1 to this fault identifier and fault index value and record them in the storage device at the same time.

[0190] Figure 5 It is a schematic flowchart of the background fault query method provided by the embodiment of the present application. As Figure 5 shown, this background fault query method includes the following steps:

[0191] Step S501: The washing machine is powered on and enters the service mode in response to a key operation.

[0192] When the washing machine is not powered off, the power-on operation may not be performed. Figure 6 The following is a schematic structural diagram of the computer board provided by the embodiment of the present application. As Figure 6 shown, the computer board includes a digital tube 601 and keys K1 to K8. When performing a fault query, after the user presses the K7 key to power on, the washing machine is powered on. When the user presses the K1 + K6 keys simultaneously within 5 seconds, the washing machine enters the service mode, and the digital tube on the display panel displays "FLN".

[0193] Step S502: In response to the K1 key operation, if the digital tube displays T2, it is determined that the function selection mode is entered.

[0194] After entering the service mode, the user presses the K1 key several times until the digital tube displays "T2", which means entering the function selection mode, and the controller controls the washing machine to enter the function selection mode.

[0195] Step S503: In response to the K8 key operation, the background fault query mode is entered.

[0196] The user selects the K8 key to confirm entering the background fault query function, and the controller responds to this operation and controls the washing machine to enter the background fault query mode.

[0197] Step S504: The digital tube displays the last fault identifier.

[0198] After entering the background fault query mode, the digital tube displays the last stored fault identifier.

[0199] Step S505: In response to the K1 key operation, the digital tube displays the historical fault identifier.

[0200] After the digital tube displays the last stored fault identifier, if the user continues to press the K1 key, the historical fault identifier can be queried. Each time the user presses the K1 key, the index value is incremented by 1, and the digital tube displays a historical fault identifier. When the current index value reaches the preset maximum index value or there is no corresponding fault identifier after the current index value, the index value is reset to 0. In this way, multiple fault identifiers stored in the storage device are cyclically displayed through the K1 key.

[0201] Figure 7 The following is a schematic structural diagram of the washing machine provided by the embodiment of the present application. As Figure 7As shown, the washing machine 700 mainly includes components: a controller 701, a key processing module 702, a fault detection module 703, a display module 704, and a storage module 705. The fault detection module 703 detects whether a fault occurs currently. If a fault occurs and it is determined whether the current fault needs to be memorized, the processing result is transmitted to the controller 701. If the controller 701 receives a memorization instruction, the controller 701 sends a storage requirement to the storage module 705. The storage module 705 records the corresponding data in the storage device.

[0202] The key processing module 702 reads the current input keys, determines whether to enter the background service mode, and transmits the determination result to the controller 701. The controller 701 sends a fault reading request to the storage module 705. The storage module 705 feeds back the fault to the controller 701. The controller 701 transmits the fault display content to the display module 704 for display.

[0203] In the embodiment of the present application, by querying the fault identifier of the problem locally on the washing machine, analyzing the operating state of the washing machine, and locating the maintenance problem, the maintenance efficiency can be improved.

[0204] Based on the foregoing embodiments, the embodiment of the present application provides a fault information processing device. Each module included in the device and each unit included in each module can be implemented by a processor in a computer device. Of course, it can also be implemented by specific logic circuits. During the implementation process, the processor can be a central processing unit (CPU, Central Processing Unit), a microprocessor (MPU, Microprocessor Unit), a digital signal processor (DSP, Digital Signal Processing), or a field programmable gate array (FPGA, Field Programmable Gate Array), etc.

[0205] Figure 8 It is a schematic structural diagram of the composition of the fault information processing device provided by the embodiment of the present application. The fault information processing device 800 is applied to a clothing processing device, such as Figure 8 As shown, the fault information processing device 800 includes:

[0206] A first acquisition module 801, configured to acquire a first fault identifier when it is detected that a fault occurs in the clothing processing device;

[0207] A second acquisition module 802, configured to acquire a second fault identifier from the storage space of the clothing processing device, where the second fault identifier is a previously stored fault identifier;

[0208] A storage module 803, configured to store the first fault identifier into the storage space when it is determined that the first fault identifier is different from the second fault identifier.

[0209] In some embodiments, the fault information processing device 800 further includes: a third acquisition module and a first determination module;

[0210] The third acquisition module is configured to acquire the time when the clothing processing device fails and the storage time of the second fault identifier when it is determined that the first fault identifier is the same as the second fault identifier;

[0211] The first determination module is configured to determine a fault time difference according to the time when the clothing processing device fails and the storage time of the second fault identifier;

[0212] The storage module 803 is further configured to store the first fault identifier into the storage space when it is determined that the fault time difference is greater than a preset duration.

[0213] In some embodiments, the storage module 803 is further configured to:

[0214] Acquire a second fault index value corresponding to the second fault identifier in the storage space;

[0215] Determine a first fault index value corresponding to the first fault identifier according to the second fault index value;

[0216] Based on the first fault index value, store the first fault identifier into the storage space.

[0217] In some embodiments, the storage module 803 is further configured to:

[0218] Determine whether the second fault index value is the last index value in the storage space;

[0219] When it is determined that the second fault index value is the last index value, determine the first index value in the storage space as the first fault index value;

[0220] When it is determined that the second fault index value is not the last index value, determine the next index value of the second fault index value as the first fault index value.

[0221] In some embodiments, the fault information processing device 800 may further include: a statistics module and a first output module;

[0222] The statistics module is configured to count the number of times the first fault identifier appears;

[0223] The second acquisition module 802 is further configured to, when the number of times reaches a preset number threshold, acquire at least one cause of the failure corresponding to the first failure identifier from the storage space;

[0224] The first output module is configured to output the at least one cause of the failure.

[0225] In some embodiments, the failure information processing device 800 may further include: a fourth acquisition module, a control module, and a second output module;

[0226] The fourth acquisition module is configured to acquire request information for querying a failure identifier;

[0227] The control module is configured to control the laundry processing device to enter a failure query mode in response to the request information;

[0228] The second acquisition module 802 is further configured to acquire a third failure identifier from the storage space of the laundry processing device, where the third failure identifier is the last stored failure identifier;

[0229] The second output module is further configured to output the third failure identifier.

[0230] In some embodiments, the failure information processing device 800 may further include: a fifth acquisition module and a second determination module;

[0231] The fifth acquisition module is configured to acquire a third failure index value corresponding to the third failure identifier in the storage space in response to a query operation for querying a historical failure identifier received;

[0232] The second determination module is configured to, when determining that the third failure index value is the last index value in the storage space, determine the first index value in the storage space as a fourth failure index value.

[0233] The second output module is further configured to output a fourth failure identifier corresponding to the fourth failure index value.

[0234] In some embodiments, the failure information processing device 800 may further include:

[0235] A third determination module, configured to, when determining that the third failure index value is not the last index value in the storage space, determine whether there is a failure identifier having a corresponding relationship with the next index value of the third failure index value;

[0236] A fourth determination module, configured to determine that when there is a fault identifier corresponding to the next index value of the third fault index value, determine the next index value of the third fault index value as the fourth fault index value;

[0237] A fifth determination module, configured to determine that when there is no fault identifier corresponding to the next index value of the third fault index value, determine the first index value in the storage space as the fourth fault index value.

[0238] It should be noted here that the description of the above embodiments of the fault information processing device is similar to the above method description and has the same beneficial effects as the method embodiments. For the technical details not disclosed in the embodiments of the fault information processing device of the present application, those skilled in the art may refer to the description of the method embodiments of the present application for understanding.

[0239] It should be noted that in the embodiments of the present application, if the above-mentioned fault information processing method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the embodiments of the present application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in the various embodiments of the present application. The foregoing storage medium includes: various media such as a USB flash drive, a mobile hard disk, a read-only memory (ROM, Read Only Memory), a magnetic disk, or an optical disc that can store program codes. In this way, the embodiments of the present application are not limited to any specific combination of hardware and software.

[0240] Correspondingly, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps in the fault information processing method provided in the above embodiments are implemented.

[0241] An embodiment of the present application provides a laundry treatment device, Figure 9 which is a schematic diagram of the composition structure of the laundry treatment device provided in the embodiment of the present application. According to Figure 9 the exemplary structure of the laundry treatment device 900 shown, other exemplary structures of the laundry treatment device 900 can be foreseen. Therefore, the structure described here should not be regarded as a limitation. For example, some components described below can be omitted, or components not described below can be added to meet the special needs of certain applications.

[0242] Figure 9The clothes processing device 900 shown includes: a processor 901, at least one communication bus 902, a user interface 903, at least one external communication interface 904, and a memory 905. Among them, the communication bus 902 is configured to enable connection communication between these components. Among them, the user interface 903 may include a display panel 9031, and the external communication interface 904 may include a standard wired interface and a wireless interface. Among them, the processor 901 is configured to execute a program of a fault storage method stored in the memory to implement the steps in the fault storage method provided in the above embodiments.

[0243] The descriptions of the above embodiments of the clothes processing device and the storage medium are similar to those of the above method embodiments, and have beneficial effects similar to those of the method embodiments. For the technical details not disclosed in the embodiments of the clothes processing device and the storage medium of the present application, please refer to the descriptions of the method embodiments of the present application for understanding.

[0244] It should be understood that the term "one embodiment" or "an embodiment" mentioned throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the present application. Therefore, the appearances of "in one embodiment" or "in an embodiment" throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that in various embodiments of the present application, the magnitudes of the serial numbers of the above processes do not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. The serial numbers of the embodiments of the present application above are only for description and do not represent the advantages or disadvantages of the embodiments.

[0245] It should be noted that in this article, the term "comprising", "including" or any other variant thereof is intended to cover a non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the phrase "including a..." does not exclude the existence of additional identical elements in the process, method, article or device including the element.

[0246] In several embodiments provided in the present 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 the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined, or can be integrated into another system, or some features can be ignored, or not executed. In addition, the coupling, direct coupling, or communication connection between the displayed or discussed components can be through some interfaces. The indirect coupling or communication connection of devices or units can be electrical, mechanical, or other forms.

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

[0248] In addition, each functional unit in the embodiments of the present application can be all integrated in a processing unit, or each unit can be separately used as a unit, or two or more units can be integrated in one unit. The above-mentioned integrated units can be implemented in the form of hardware, or in the form of a combination of hardware and software functional units.

[0249] Those of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiments can be completed by hardware related to program instructions. The foregoing program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps including the above method embodiments. The foregoing storage medium includes various media that can store program codes, such as removable storage devices, ROMs, magnetic disks, or optical discs.

[0250] Alternatively, if the above-mentioned integrated units of the present application are implemented in the form of 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 solution of the embodiments of the present application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions to enable a product to execute all or part of the methods described in the embodiments of the present application. The foregoing storage medium includes various media that can store program codes, such as removable storage devices, ROMs, magnetic disks, or optical discs.

[0251] As described above, it is only the implementation mode of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed by this application can easily think of changes or substitutions, which should all be covered within the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the said claims.

Claims

1. A fault information processing method, applied to a laundry treatment device, characterized in that The method includes: When a failure of the clothing processing device is detected, obtaining a first failure identifier; Obtaining a second failure identifier from the storage space of the clothing processing device, where the second failure identifier is the previously stored failure identifier; When it is determined that the first failure identifier is different from the second failure identifier, storing the first failure identifier in the storage space; The method further includes: In response to a query operation for querying historical failure identifiers, obtaining a third failure index value corresponding to a third failure identifier in the storage space; the third failure identifier is the last stored failure identifier; When it is determined that the third failure index value is not the last index value in the storage space, determining whether there is a failure identifier corresponding to the next index value of the third failure index value; When it is determined that there is a failure identifier corresponding to the next index value of the third failure index value, determining the next index value of the third failure index value as a fourth failure index value; Outputting the fourth failure identifier corresponding to the fourth failure index value.

2. The method according to claim 1, characterized in that The method further includes: When it is determined that the first failure identifier is the same as the second failure identifier, obtaining the time when the clothing processing device fails and the storage time of the second failure identifier; Determining a failure time difference according to the time when the clothing processing device fails and the storage time of the second failure identifier; When it is determined that the failure time difference is greater than a preset duration, storing the first failure identifier in the storage space.

3. The method according to claim 1, characterized in that, The storing the first failure identifier in the storage space includes: Obtaining a second failure index value corresponding to the second failure identifier in the storage space; Determining a first failure index value corresponding to the first failure identifier according to the second failure index value; Based on the first failure index value, storing the first failure identifier in the storage space.

4. The method according to claim 3, characterized in that The determining a first failure index value corresponding to the first failure identifier according to the second failure index value includes: Determining whether the second failure index value is the last index value in the storage space; When it is determined that the second failure index value is the last index value, determining the first index value in the storage space as the first failure index value; When it is determined that the second failure index value is not the last index value, determining the next index value of the second failure index value as the first failure index value.

5. The method according to claim 1, wherein The method further includes: Counting the number of times the first failure identifier appears; When the number reaches a preset number threshold, obtaining at least one failure cause corresponding to the first failure identifier from the storage space; Outputting the at least one failure cause.

6. The method according to any one of claims 1 to 5, characterized in that The method further includes: Obtaining request information for querying a failure identifier; In response to the request information, controlling the clothing processing device to enter a failure query mode; Obtaining the third failure identifier from the storage space of the clothing processing device; Outputting the third failure identifier.

7. The method according to claim 6, characterized in that, The method further includes: In the case where the third fault index value is determined to be the last index value in the storage space, the first index value in the storage space is determined as the fourth fault index value.

8. The method according to claim 7, characterized in that, The method further includes: In the case where it is determined that there is no fault identifier corresponding to the next index value of the third fault index value, the first index value in the storage space is determined as the fourth fault index value.

9. A fault information processing device is applied to a clothing processing device, and is characterized in that, The apparatus includes: A first acquisition module, configured to acquire a first fault identifier when it is detected that the laundry treatment device has a fault; A second acquisition module, configured to acquire a second fault identifier from the storage space of the laundry treatment device, where the second fault identifier is the previously stored fault identifier; A storage module, configured to store the first fault identifier into the storage space when it is determined that the first fault identifier is different from the second fault identifier; The fault information processing apparatus further includes: a fifth acquisition module, a third determination module, a fourth determination module, and a second output module; The fifth acquisition module is configured to, in response to a query operation for querying a historical fault identifier, acquire a third fault index value corresponding to a third fault identifier in the storage space; the third fault identifier is the last stored fault identifier; The third determination module is configured to, in the case where it is determined that the third fault index value is not the last index value in the storage space, determine whether there is a fault identifier corresponding to the next index value of the third fault index value; The fourth determination module is configured to, in the case where it is determined that there is a fault identifier corresponding to the next index value of the third fault index value, determine the next index value of the third fault index value as the fourth fault index value; The second output module is configured to output a fourth fault identifier corresponding to the fourth fault index value.

10. A laundry treatment device, characterized in that, The laundry treatment device includes: A memory, configured to store executable instructions; A processor, configured to implement the steps of the fault information processing method according to any one of claims 1 to 8 when executing the executable instructions stored in the memory.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are configured to execute the steps of the fault information processing method according to any one of claims 1 to 8 above.

Images