Fault data processing method and device, readable medium and equipment

Abstract

The application discloses a fault data processing method and device, readable medium and equipment, the method sends a system state log reading request to the lower computer through the upper computer, receives the system state log sent by the lower computer, wherein the system state log comprises: the fault information of the monitored device, the running cycle of the lower computer when the monitored device fails, and the running cycle of the lower computer at present, the upper computer analyzes the obtained system state log, obtains the fault information of the monitored device and the corresponding time point when the monitored device fails; generate a fault log; because the fault log comprises: the fault information of the monitored device and the corresponding time point when the monitored device fails, compared with the existing alarm information, it is easier to help the user to analyze and locate the fault reason, quickly repair the fault and save the economic cost.

Description

Technical Field

[0001] This application relates to the field of information processing technology, and in particular to a method, apparatus, readable medium, and device for processing fault data. Background Technology

[0002] In existing technologies, most embedded protection systems in the industrial field use board-based devices to monitor the operating environment. When a device malfunction is detected, an alarm message is sent to a host computer. After viewing the alarm message on the host computer, personnel will go to the site to perform hardware analysis on the board-based device and locate the fault causing the alarm.

[0003] However, existing fault location methods only indicate which devices are currently in an alarm state, but the specific fault causing the alarm still requires complex hardware analysis of the circuit boards on-site to pinpoint the problem step by step. This is especially true when some devices experience intermittent faults, as the equipment may have already returned to normal operation by the time personnel arrive on-site for hardware analysis, making it even more difficult to determine the actual cause of the fault. Therefore, the current fault location process is complex, cumbersome, and inefficient. Summary of the Invention

[0004] In view of the shortcomings of the prior art, this application proposes a method, apparatus, readable medium and device for processing fault data, so as to improve the efficiency of fault analysis and location by generating fault logs.

[0005] The first aspect of this application discloses a method for processing fault data, applied to a host computer, the method for processing fault data including:

[0006] Send a system status log read request to the lower-level machine;

[0007] Receive system status logs sent by the lower-level machine; wherein, the system status logs include: fault information that has occurred in the monitored device, the lower-level machine operation cycle at which the monitored device failed, and the current lower-level machine operation cycle;

[0008] The system status log is parsed to obtain the fault information that has occurred in the monitored device and the time point corresponding to when the monitored device failed.

[0009] Generate a fault log; wherein the fault log includes: fault information that has occurred in the monitored device and the time point corresponding to when the monitored device experienced a fault.

[0010] Optionally, in the above-mentioned method for processing fault data, parsing the system status log to obtain the fault information that has occurred in the monitored device and the time point corresponding to when the monitored device experienced a fault includes:

[0011] Using preset fault parsing rules, the fault information in the system status log is parsed to obtain the fault information in plaintext form. Furthermore, time conversion parsing is performed using the lower-level machine's operating cycle at the time the monitored device malfunctioned, the current lower-level machine's operating cycle, and the current time point to calculate the time point corresponding to the time the monitored device malfunctioned. The fault parsing rules are pre-agreed rules between the host computer and the lower-level machine for parsing fault information. The fault log includes: the plaintext fault information and the time point corresponding to the time the monitored device malfunctioned.

[0012] Optionally, in the above-mentioned method for processing fault data, the step of using the lower-level machine's operating cycle at the time the monitored device malfunctioned, the current lower-level machine's operating cycle, and the current time point to perform time conversion and analysis, and calculating the time point corresponding to the time when the monitored device malfunctioned, includes:

[0013] Substitute the lower-level machine operation cycle at the time the monitored device malfunctioned, the current lower-level machine operation cycle, and the current time point into the time conversion analysis formula to obtain the time point corresponding to the time when the monitored device malfunctioned.

[0014] The time conversion formula is: T = T1 - (tick1 - tick2) * Cycle; T is the time point corresponding to the failure of the monitored device; T1 is the current time point; tick1 is the current lower-level machine operation cycle; tick2 is the lower-level machine operation cycle at the time the monitored device failed; and Cycle is the duration of the lower-level machine operation cycle.

[0015] A second aspect of this application discloses a method for processing fault data, applied to a lower-level computer, the method comprising:

[0016] The monitored equipment is monitored, and the fault information of the monitored equipment and the lower-level machine operation cycle at the time of the fault are recorded in the system status log.

[0017] Receive the system status log read request sent by the host computer;

[0018] In response to the system status log read request, the currently recorded system status log is sent to the host computer, which then uses the system status log to parse and obtain the fault log. The system status log includes: fault information of the monitored device, the lower-level machine operating cycle at the time the monitored device failed, and the current lower-level machine operating cycle. The fault log includes: fault information of the monitored device and the time point corresponding to the time the monitored device failed.

[0019] Optionally, in the above-mentioned method for processing fault data, the step of monitoring the monitored equipment and recording the fault information that has occurred on the monitored equipment into the system status log includes:

[0020] The monitored device is monitored to obtain the system status information of the monitored device in each lower-level machine operation cycle; wherein, the system status information of the lower-level machine operation cycle is fault information used to describe the fault that occurs in the monitored device during the lower-level machine operation cycle;

[0021] For each lower-level machine operation cycle, compare the system status information of the lower-level machine operation cycle with the system status information of the previous lower-level machine operation cycle; if the system content data of the lower-level machine operation cycle is inconsistent with the system content data of the previous lower-level machine operation cycle, then record the system content data of the lower-level machine operation cycle and the lower-level machine operation cycle in the system status log.

[0022] Optionally, in the above-mentioned method for processing fault data, the step of monitoring the monitored equipment and recording the fault information that has occurred on the monitored equipment into the system status log includes:

[0023] The monitored device is monitored to obtain the system status information of the monitored device in each lower-level machine operation cycle; wherein, the system status information of the lower-level machine operation cycle is fault information used to describe the fault that occurs in the monitored device during the lower-level machine operation cycle;

[0024] For each lower-level machine operation cycle, the system status information of the lower-level machine operation cycle and the lower-level machine operation cycle are recorded in the system status log.

[0025] A third aspect of this application discloses a fault data processing device, applied to a host computer, the fault data processing device comprising:

[0026] The first sending unit is used to send a system status log read request to the lower-level machine.

[0027] The first receiving unit is used to receive the system status log sent by the lower-level machine; wherein, the system status log includes: fault information that has occurred in the monitored device, the lower-level machine operation cycle at which the monitored device failed, and the current lower-level machine operation cycle.

[0028] The parsing unit is used to parse the system status log to obtain the fault information that has occurred in the monitored device and the time point corresponding to when the monitored device failed.

[0029] The first generation unit is used to generate a fault log; wherein the fault log includes: fault information that has occurred in the monitored device and the time point corresponding to when the monitored device malfunctioned.

[0030] Optionally, in the above-mentioned fault data processing apparatus, the parsing unit includes:

[0031] The parsing subunit is used to parse the fault information in the system status log using preset fault parsing rules to obtain the fault information in plaintext form; and to perform time conversion parsing using the lower-level machine's operating cycle at the time the monitored device malfunctioned, the current lower-level machine's operating cycle, and the current time point to calculate the time point corresponding to the time the monitored device malfunctioned; wherein, the fault parsing rules are rules for parsing fault information pre-agreed between the upper-level machine and the lower-level machine; the fault log includes: the plaintext fault information and the time point corresponding to the time the monitored device malfunctioned.

[0032] Optionally, in the above-mentioned fault data processing device, when the parsing subunit performs time conversion parsing using the lower-level machine operation cycle at the time the monitored device malfunctioned, the current lower-level machine operation cycle, and the current time point, and calculates the time point corresponding to the time when the monitored device malfunctioned, it is used for:

[0033] Substitute the lower-level machine operation cycle at the time the monitored device malfunctioned, the current lower-level machine operation cycle, and the current time point into the time conversion analysis formula to obtain the time point corresponding to the time when the monitored device malfunctioned.

[0034] The time conversion formula is: T = T1 - (tick1 - tick2) * Cycle; T is the time point corresponding to the failure of the monitored device; T1 is the current time point; tick1 is the current lower-level machine operation cycle; tick2 is the lower-level machine operation cycle at the time the monitored device failed; and Cycle is the duration of the lower-level machine operation cycle.

[0035] A fourth aspect of this application discloses a fault data processing device, applied to a lower-level computer, the fault data processing device comprising:

[0036] The monitoring unit is used to monitor the monitored equipment and record the fault information of the monitored equipment and the lower-level machine operation cycle when the monitored equipment fails into the system status log.

[0037] The second receiving unit is used to receive the system status log reading request sent by the host computer;

[0038] The second sending unit is used to respond to the system status log read request and send the currently recorded system status log to the host computer, which then uses the system status log to parse and obtain the fault log. The system status log includes: fault information that has occurred on the monitored device, the lower-level machine operating cycle at the time the monitored device failed, and the current lower-level machine operating cycle. The fault log includes: fault information that has occurred on the monitored device and the time point corresponding to the time the monitored device failed.

[0039] Optionally, in the above-mentioned fault data processing device, the monitoring unit includes:

[0040] The first acquisition subunit is used to monitor the monitored device and acquire the system status information of the monitored device in each lower-level machine operation cycle; wherein, the system status information of the lower-level machine operation cycle is fault information used to describe the fault that occurred in the monitored device during the lower-level machine operation cycle;

[0041] The first recording subunit is used to compare the system status information of the lower-level machine operation cycle with the system status information of the previous lower-level machine operation cycle for each lower-level machine operation cycle; if the system content data of the lower-level machine operation cycle is inconsistent with the system content data of the previous lower-level machine operation cycle, the system content data of the lower-level machine operation cycle and the lower-level machine operation cycle are recorded in the system status log.

[0042] Optionally, in the above-mentioned fault data processing device, the monitoring unit includes:

[0043] The second acquisition subunit is used to monitor the monitored device and acquire the system status information of the monitored device in each lower-level machine operation cycle; wherein, the system status information of the lower-level machine operation cycle is fault information used to describe the fault that occurred in the monitored device during the lower-level machine operation cycle;

[0044] The second recording subunit is used to record the system status information of the lower-level machine operation cycle and the lower-level machine operation cycle into the system status log for each lower-level machine operation cycle.

[0045] The fifth aspect of this application discloses a computer-readable medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the method as described in any of the first aspects above, or the method as described in any of the second aspects above.

[0046] The sixth aspect of this application discloses a device comprising:

[0047] One or more processors;

[0048] A storage device on which one or more programs are stored;

[0049] When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any of the first aspects above, or the method as described in any of the second aspects above.

[0050] As can be seen from the above technical solutions, the fault data processing method proposed in this application is applied to a host computer. This method sends a system status log read request to a lower-level computer and receives the system status log sent by the lower-level computer. Since the system status log in this application includes: fault information of the monitored device, the lower-level computer's operating cycle at the time the monitored device malfunctioned, and the current lower-level computer's operating cycle, the fault information of the monitored device and the corresponding time point can be obtained by parsing the system status log. This allows for the generation of a fault log containing both the fault information and the corresponding time point. Compared to existing technologies where alarm information only indicates which devices are in an alarm state, the fault log in this application provides information on the faults of the monitored devices and the corresponding time point. This allows for faster and more convenient analysis of the actual causes of device alarms, improving the efficiency of fault analysis, quickly repairing faults, and saving economic costs. Attached Figure Description

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

[0052] Figure 1This is a flowchart illustrating a fault data processing method proposed in an embodiment of this application;

[0053] Figure 2 This is a flowchart illustrating a method for recording system status information according to an embodiment of this application.

[0054] Figure 3 This is a flowchart illustrating another method for recording system status information proposed in an embodiment of this application;

[0055] Figure 4 This is a schematic diagram of the structure of a fault data processing device proposed in an embodiment of this application;

[0056] Figure 5 This is a schematic diagram of another fault data processing device proposed in an embodiment of this application. Detailed Implementation

[0057] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0058] See Figure 1 This application proposes a method for processing fault data, which specifically includes the following steps:

[0059] S101. The lower-level machine monitors the monitored equipment and records the fault information of the monitored equipment and the lower-level machine's operating cycle when the monitored equipment fails into the system status log.

[0060] A lower-level computer is a computer that directly controls the monitored device and obtains its operational status. Specifically, it can be a board device containing a controller, a microcontroller, a programmable logic controller (PLC), etc. The monitored device refers to the device monitored by the lower-level computer. Fault information generated when the lower-level computer malfunctions can be monitored by the lower-level computer. The lower-level computer can monitor one or more monitored devices. It can perform periodic monitoring or real-time monitoring. Then, it records the fault information of the monitored device and the lower-level computer's operating cycle at the time of the fault in the system status log. The fault information of the monitored device describes the fault that has occurred.

[0061] Since the lower-level machine is a clockless system, it does not know the system time when the fault information was detected (i.e., it does not know the specific day, hour, minute, and second when the fault information was detected). However, the lower-level machine in a clockless system can record time using its runtime cycle. For example, if a monitored device is found to have a fault, and the current state is the nth runtime cycle of the lower-level machine, then the runtime cycle in which the monitored device experienced the fault is the nth runtime cycle. Therefore, when recording system status logs, the lower-level machine can record the time information of the fault by recording the runtime cycle in which the monitored device experienced the fault.

[0062] The fault information in step S101 can take many forms, such as pre-agreed board status data with the lower-level machine. Specifically, the upper-level machine and the lower-level machine pre-agreed on the status code corresponding to each type of fault, and then record the status code corresponding to the fault of the monitored device into the corresponding status bit of the monitored device. Alternatively, the fault information can also be encrypted program code. The specific forms of fault information include, but are not limited to, those proposed in the embodiments of this application.

[0063] The fault information that has occurred in the monitored equipment can be information describing the type of fault that has occurred, or information describing the specific fault condition that has occurred, such as the code program when the monitored equipment malfunctions.

[0064] When executing step S101, the system can record either the fault information of the monitored device and the lower-level machine operation cycle at which the monitored device is running when the fault occurs in real time to the system status log, or it can record the fault information of the monitored device and the lower-level machine operation cycle at which the monitored device is running when the fault occurs periodically.

[0065] For example, if a Class A fault is detected in device A during the third lower-level machine operation cycle, then the third lower-level machine operation cycle and the fault information indicating that device A has experienced a Class A fault will be recorded in the system status log.

[0066] Optionally, if no faults are detected in the monitored devices, the information indicating that the monitored devices are in a normal state, as well as the lower-level machine operating cycle in which the monitored devices are in a normal state, can be recorded in the system status log. That is, in addition to recording fault information indicating that the monitored devices have failed, information indicating that the monitored devices are in a normal state is also recorded. Optionally, no records can be made when no faults are detected in the monitored devices, and records can only be made in the system status log when a fault occurs.

[0067] Optionally, see Figure 2 In one specific embodiment of this application, one implementation of step S101 of the lower-level machine execution includes:

[0068] S201. Monitor the monitored equipment and obtain the system status information of the monitored equipment in each lower-level machine operation cycle.

[0069] The system status information during the lower-level machine's operating cycle describes the fault information that occurs in the monitored device during the lower-level machine's operating cycle. When executing step S201, the lower-level machine periodically monitors and obtains the system status information of the monitored device according to its operating cycle.

[0070] S202. For each lower-level machine operation cycle, compare whether the system status information of the lower-level machine operation cycle is consistent with the system status information of the previous lower-level machine operation cycle.

[0071] For each lower-level machine operation cycle, the system status information of the current lower-level machine operation cycle is compared with that of the previous lower-level machine operation cycle. If they are consistent, it means that the status of the monitored device has not changed. For example, if the system status information of the current lower-level machine operation cycle indicates that device A has experienced a type A fault, and the system status information of the previous lower-level machine operation cycle also indicates that device A experienced a type A fault in the previous lower-level machine operation cycle, then it means that the type A fault of device A has not been eliminated and the type A fault is still in the occurrence state. Since the fault information has not changed, in order to save storage space, the system status information of the current lower-level machine operation cycle does not need to be recorded in the system status log.

[0072] If the system status information of the current lower-level machine operation cycle is inconsistent with that of the previous lower-level machine operation cycle, it indicates that the status of the monitored device has changed and needs to be recorded in the system status log, i.e., step S203 should be executed. For example, if the system status information of the current lower-level machine operation cycle indicates that device A has not experienced any faults, while the system status information of the previous lower-level machine operation cycle indicates that device A experienced a type A fault, then it means that the type A fault of device A has been repaired and it has returned to normal. Therefore, this change needs to be recorded in the system status log for subsequent fault analysis.

[0073] S203. Record the system content data and lower-level machine operation cycle of the lower-level machine into the system status log.

[0074] If the system status information of the current lower-level machine operation cycle is found to be inconsistent with the system status information of the previous lower-level machine operation cycle, the system content data of the current lower-level machine operation cycle and the current lower-level machine operation cycle are recorded in the system status log for subsequent analysis and fault location. That is, when recording the system content data, the corresponding lower-level machine operation cycle must also be recorded. Recording the lower-level machine operation cycle here can refer to recording the sequence number and identifier of the lower-level machine operation cycle.

[0075] pass Figure 2 The system status log is recorded in the manner shown. From the system status log, you can see which faults occurred in which lower-level machine operation cycles of the monitored device. In other words, you can read the fault information of the monitored device and the lower-level machine operation cycle in which the monitored device failed from the system status log.

[0076] In existing technologies, when a circuit board detects a device malfunction, it sends an alarm message to the host computer. However, this alarm message only indicates which devices are in an alarm state, not the specific fault. Personnel must conduct complex hardware analysis on-site to pinpoint the fault. This is especially problematic when alarms are caused by malfunctions in related devices, requiring further analysis to accurately locate the cause. In some cases, the fault is intermittent, meaning it recovers shortly after the initial malfunction. By the time personnel arrive on-site after receiving the alarm, the device has already recovered, making it even more difficult to determine the cause of the intermittent fault.

[0077] In this embodiment, the lower-level machine records the fault information of the monitored device and the lower-level machine operation cycle at which the monitored device malfunctions into the system status log. The system status log not only describes which specific faults have occurred in the monitored device, but also records time information such as the lower-level machine operation cycle at which the fault occurred. Compared with the prior art, this is more conducive to the upper-level machine to analyze and locate the cause of the fault.

[0078] Optionally, see Figure 3 In one specific embodiment of this application, another implementation of the lower-level machine execution step S101 includes:

[0079] S301. Monitor the monitored equipment and obtain the system status information of the monitored equipment in each lower-level machine operation cycle.

[0080] The principle and execution process of step S301 are as follows: Figure 2 The steps shown in step S201 are the same and can be found elsewhere, so they will not be repeated here.

[0081] S302. For each lower-level machine operation cycle, record the system status information of the lower-level machine operation cycle and the lower-level machine operation cycle in the system status log.

[0082] According to the lower-level machine's operating cycle, the system status information for each lower-level machine operating cycle, as well as the corresponding lower-level machine operating cycle, are periodically recorded in the system status log. The recorded lower-level machine operating cycle can be the sequence number or identifier of the lower-level machine operating cycle.

[0083] pass Figure 3 The system status log is recorded in the manner shown. Since the system status information and the lower-level machine operation cycle are recorded for all lower-level machine operation cycles, it is possible to see from the system status log which faults occurred in which lower-level machine operation cycles of the monitored device. In other words, the fault information of the monitored device and the lower-level machine operation cycle in which the monitored device failed can be read from the system status log.

[0084] S102. The host computer sends a system status log read request to the slave computer.

[0085] The system status log read request is used to request the reading of the system status log currently recorded by the lower-level machine.

[0086] S103. The lower-level machine responds to the system status log read request and sends the currently recorded system status log to the upper-level machine.

[0087] The system status log includes: fault information of the monitored device, the lower-level machine operation cycle at which the monitored device failed, and the current lower-level machine operation cycle. The currently recorded system status log includes all fault information of the monitored device recorded up to and including the current time point, the lower-level machine operation cycle at which the monitored device failed, and the current lower-level machine operation cycle.

[0088] Step S101 mentions that the lower-level machine records fault information of the monitored device and the lower-level machine's operating cycle at the time of the fault in the system status log. Step S103 sends a system status log that includes not only the recorded fault information of the monitored device and the lower-level machine's operating cycle at the time of the fault, but also the current lower-level machine operating cycle. Specifically, if step S101 uses... Figure 2If executed in the manner shown, the latest lower-level machine running cycle recorded in the system status log may not be the current lower-level machine running cycle (for example, if the monitored system status information remains unchanged). Therefore, after responding to the system status log read request, the lower-level machine needs to write its current lower-level machine running cycle into the system status log before sending it to the upper-level machine. Alternatively, it can also be executed using... Figure 2 When recording the system status log in the manner shown, the current lower-level machine's running cycle is also updated and recorded in real time. Therefore, when executing step S103, the system status log sent includes the current lower-level machine running cycle.

[0089] If step S101 is adopted Figure 3 As shown, since the system status information of each lower-level machine operation cycle and the corresponding lower-level machine operation cycle are recorded in the system status log, the current lower-level machine operation cycle is the latest recorded lower-level machine operation cycle. Therefore, when executing step S103, the currently recorded system status log can be sent directly.

[0090] S104. The host computer parses the system status log to obtain the fault information that has occurred in the monitored equipment and the time point corresponding to the fault of the monitored equipment.

[0091] The system status log in step S103 includes: fault information of the monitored device, the lower-level machine operation cycle at which the monitored device failed, and the current lower-level machine operation cycle. Therefore, by parsing the system status log, the fault information of the monitored device that has failed can be obtained. The parsed fault information can be read by the host computer and viewed by the user. The lower-level machine operation cycle at which the monitored device failed and the current lower-level machine operation cycle included in the system status log can be parsed and converted into the time point corresponding to the failure of the monitored device. Specifically, since the host computer is different from the lower-level machine using a clockless system, the host computer has a system time. Therefore, the time point corresponding to the failure of the monitored device can be parsed from the current time point indicated by the system time, the lower-level machine operation cycle at which the monitored device failed, and the current lower-level machine operation cycle.

[0092] Optionally, in one specific embodiment of this application, one implementation of step S104 performed by the host computer includes:

[0093] Using preset fault parsing rules, the fault information in the system status log is parsed to obtain the fault information in plaintext. Then, the time conversion is performed using the lower-level machine operation cycle when the monitored device failed, the current lower-level machine operation cycle, and the current time point to obtain the time point corresponding to when the monitored device failed.

[0094] The fault parsing rules are pre-agreed rules between the host computer and the slave computer for parsing fault information. To improve the security of fault information recorded in the system status log, the fault information recorded by the slave computer in the system status log is recorded using the fault parsing rules. Only the host computer, which knows the fault parsing rules, can successfully parse the fault information recorded by the slave computer. The successfully parsed fault information is in plaintext form, which can be read by the host computer user to indicate that the monitored device has failed. If other devices that do not know the fault parsing rules obtain the system status log, they will not be able to parse the fault information to indicate that the monitored device has failed.

[0095] For example, the fault analysis rules specify the correspondence between fault types and status codes, as well as the correspondence between monitored devices and status bits. The fault information of monitored devices in the system status log is recorded in the corresponding status bit of the monitored device using the status code corresponding to the fault type. That is, the system status log records all fault status codes of the monitored devices up to the current time point. When the host computer parses the system status log, because it knows in advance the correspondence between fault types and status codes, and the correspondence between monitored devices and status bits specified in the fault analysis rules, it can parse out all the faults that have occurred on the monitored devices in the system status log.

[0096] When performing time conversion analysis using the lower-level machine's operating cycle at the time the monitored device malfunctioned, the current lower-level machine's operating cycle, and the current time point, the current time point corresponds to the current lower-level machine's operating cycle, and the time point at which the monitored device malfunctioned corresponds to the lower-level machine's operating cycle at the time the monitored device malfunctioned. Therefore, the time point at which the monitored device malfunctioned can be calculated analytically.

[0097] Optionally, in a specific embodiment of this application, a time conversion analysis is performed using the lower-level machine's operating cycle at the time the monitored device malfunctioned, the current lower-level machine's operating cycle, and the current time point. The analysis calculates the time point corresponding to the time when the monitored device malfunctioned, including:

[0098] Substitute the lower-level machine's operating cycle at the time the monitored device malfunctioned, the current lower-level machine's operating cycle, and the current time point into the time conversion and analysis formula to obtain the time point corresponding to the time the monitored device malfunctioned.

[0099] The time conversion formula is: T = T1 - (tick1 - tick2) * Cycle. T represents the time point corresponding to the time when the monitored device malfunctioned, T1 is the current time point, tick1 is the current lower-level machine operation cycle, tick2 is the lower-level machine operation cycle at the time the monitored device malfunctioned, and Cycle is the duration of the lower-level machine operation cycle. For example, if the system status log records that device A experienced a fault A in the 3rd lower-level machine operation cycle, and the current lower-level machine operation cycle is the 5th cycle, with the current time being 9:00 AM and the lower-level machine operation cycle duration being 1 second, then using the time conversion formula, T can be calculated as 8:59:58, meaning device A experienced a fault A at 8:59:58.

[0100] S105, The host computer generates a fault log.

[0101] The fault log includes: fault information that has occurred on the monitored equipment and the time point corresponding to the occurrence of the fault. The fault information that has occurred on the monitored equipment and the time point corresponding to the occurrence of the fault are obtained by parsing in step S104.

[0102] All faults that occurred at or before the current time, as well as the specific time of the fault, can be retrieved from the fault log. Even if the monitored device experiences a flash fault, the fault information and the time of the flash fault can be read from the fault log. By using the time of the fault recorded in the fault log, along with the fault information describing the specific fault that occurred, the cause of the fault in the monitored device can be quickly analyzed and located.

[0103] In the prior art, since the lower-level machine operates without a clock, even if fault information can be monitored and obtained, the time point when the fault occurred cannot be known. However, in the embodiments of this application, the lower-level machine sends the system status log, which includes the fault information of the monitored device, the lower-level machine operation cycle in which the monitored device failed, and the current lower-level machine operation cycle, to the upper-level machine. The upper-level machine can then parse out the time point when the monitored device failed, providing important time information for analyzing and locating the cause of the fault.

[0104] The fault data processing method proposed in this application involves a lower-level computer monitoring the monitored device and recording the fault information that has occurred on the monitored device, as well as the lower-level computer's operating cycle at the time of the fault, into a system status log. Then, the upper-level computer sends a system status log read request to the lower-level computer, thereby receiving the system status log sent by the lower-level computer. Since the system status log in this application includes: fault information that has occurred on the monitored device, the lower-level computer's operating cycle at the time of the fault, and the current lower-level computer operating cycle, the upper-level computer can parse the system status log to obtain the fault information that has occurred on the monitored device and the corresponding time point when the fault occurred, thereby generating a fault log that includes both the fault information and the corresponding time point. Compared to existing technologies where alarm information only indicates which devices are in an alarm state, the fault log in this application provides both the fault information that has occurred on the monitored device and the corresponding time point when the fault occurred. This allows for faster and more convenient analysis of the actual causes of device alarms, improving the efficiency of fault analysis.

[0105] See Figure 4 Based on the fault data processing method proposed in the above embodiments of this application, this application also discloses a fault data processing device, which is applied to a host computer. The fault data processing device includes: a first sending unit 401, a first receiving unit 402, a parsing unit 403, and a first generating unit 404.

[0106] The first sending unit 401 is used to send a system status log read request to the lower-level machine.

[0107] The first receiving unit 402 is used to receive the system status log sent by the lower-level machine. The system status log includes: fault information that has occurred in the monitored device, the lower-level machine operation cycle at which the monitored device failed, and the current lower-level machine operation cycle.

[0108] The parsing unit 403 is used to parse the system status log to obtain the fault information that has occurred in the monitored device and the time point corresponding to the fault of the monitored device.

[0109] Optionally, in a specific embodiment of this application, the parsing unit 403 includes:

[0110] The parsing subunit is used to parse fault information in the system status log using preset fault parsing rules, obtaining fault information in plaintext form. It then performs time conversion parsing using the lower-level machine's operating cycle at the time the monitored device failed, the current lower-level machine's operating cycle, and the current time point, calculating the time point corresponding to the time the monitored device failed. The fault parsing rules are pre-agreed rules between the host computer and the lower-level machine for parsing fault information. The fault log includes: plaintext fault information and the time point corresponding to the time the monitored device failed.

[0111] Optionally, in a specific embodiment of this application, the parsing subunit performs time conversion parsing using the lower-level machine's operating cycle at the time the monitored device malfunctioned, the current lower-level machine's operating cycle, and the current time point. When the time point corresponding to the time when the monitored device malfunctioned is obtained through parsing and calculation, it is used for:

[0112] Substitute the lower-level machine's operating cycle at the time the monitored device malfunctioned, the current lower-level machine's operating cycle, and the current time point into the time conversion and analysis formula to obtain the time point corresponding to the time the monitored device malfunctioned.

[0113] The time conversion formula is: T = T1 - (tick1 - tick2) * Cycle, where T is the time point corresponding to the failure of the monitored device, T1 is the current time point, tick1 is the current lower-level machine operation cycle, tick2 is the lower-level machine operation cycle at the time the monitored device failed, and Cycle is the duration of the lower-level machine operation cycle.

[0114] The first generation unit 404 is used to generate a fault log. The fault log includes: fault information that has occurred on the monitored device and the time point corresponding to the occurrence of the fault.

[0115] The specific principles and execution processes of each unit in the fault data processing device disclosed in the above-described embodiments of this application are the same as those of the fault data processing method disclosed in the above-described embodiments of this application. Please refer to the corresponding parts of the fault data processing method disclosed in the above-described embodiments of this application, and they will not be repeated here.

[0116] The fault data processing device proposed in this application embodiment is applied to a host computer. This device sends a system status log read request to a lower-level computer via a first sending unit 401, and a first receiving unit 402 receives the system status log sent by the lower-level computer. Since the system status log in this application embodiment includes: fault information of the monitored device, the lower-level computer's operating cycle at the time the monitored device malfunctioned, and the current lower-level computer's operating cycle, the parsing unit 403 can parse the system status log to obtain the fault information of the monitored device and the corresponding time point when the monitored device malfunctioned. Then, the first generating unit 404 generates a fault log including the fault information of the monitored device and the corresponding time point when the monitored device malfunctioned. Compared to existing technologies where alarm information only indicates which devices are in an alarm state, the fault log in this application can indicate the fault information of the monitored device and the corresponding time point when the monitored device malfunctioned. Through the fault log, the actual cause of the device alarm can be analyzed more quickly and conveniently, improving the efficiency of fault analysis.

[0117] See Figure 5 Based on the fault data processing method proposed in the above embodiments of this application, this application also discloses another fault data processing device, which is applied to a lower-level machine. The fault data processing device includes: a monitoring unit 501, a second receiving unit 502, and a second sending unit 503.

[0118] The monitoring unit 501 is used to monitor the monitored equipment and record the fault information of the monitored equipment and the lower-level machine operation cycle when the monitored equipment fails into the system status log.

[0119] Optionally, in a specific embodiment of this application, the monitoring unit 501 includes: a second acquisition subunit and a second recording subunit.

[0120] The second acquisition subunit is used to monitor the monitored device and acquire the system status information of the monitored device in each lower-level machine operation cycle. The system status information in each lower-level machine operation cycle describes the fault information that occurs in the monitored device during that cycle.

[0121] The second recording subunit is used to record the system status information of the lower-level machine operation cycle and the lower-level machine operation cycle to the system status log for each lower-level machine operation cycle.

[0122] Optionally, in a specific embodiment of this application, the monitoring unit 501 includes: a first acquisition subunit and a first recording subunit.

[0123] The first acquisition subunit is used to monitor the monitored device and acquire the system status information of the monitored device in each lower-level machine operation cycle. The system status information in each lower-level machine operation cycle describes the fault information that occurs in the monitored device during that cycle.

[0124] The first recording subunit is used to compare the system status information of each lower-level machine operation cycle with the system status information of the previous lower-level machine operation cycle. If the system content data of the lower-level machine operation cycle is inconsistent with the system content data of the previous lower-level machine operation cycle, the system content data of the lower-level machine operation cycle and the lower-level machine operation cycle are recorded in the system status log.

[0125] The second receiving unit 502 is used to receive system status log reading requests sent by the host computer.

[0126] The second sending unit 503 is used to respond to a system status log read request and send the currently recorded system status log to the host computer, which then uses the system status log to parse and obtain the fault log. The system status log includes: fault information that has occurred on the monitored device, the lower-level machine's operating cycle at the time the monitored device failed, and the current lower-level machine's operating cycle. The fault log includes: fault information that has occurred on the monitored device and the time point corresponding to the failure of the monitored device.

[0127] The specific principles and execution processes of each unit in the fault data processing device disclosed in the above-described embodiments of this application are the same as those of the fault data processing method disclosed in the above-described embodiments of this application. Please refer to the corresponding parts of the fault data processing method disclosed in the above-described embodiments of this application, and they will not be repeated here.

[0128] The fault data processing device proposed in this application embodiment is applied to a lower-level machine. A monitoring unit 501 monitors the monitored device and records the fault information that has occurred on the monitored device, as well as the lower-level machine's operating cycle at the time of the fault, into a system status log. A second receiving unit 502 receives a system status log read request from a higher-level machine, and then a second sending unit 503 responds to the request by sending the currently recorded system status log to the higher-level machine. Since the system status log includes: the fault information that has occurred on the monitored device, the lower-level machine's operating cycle at the time of the fault, and the current lower-level machine operating cycle, the higher-level machine can use the system status log to parse and obtain the fault log. Compared to existing technologies where alarm information only indicates which devices are in an alarm state, the fault log in this application shows the fault information that has occurred on the monitored device and the corresponding time point when the fault occurred. The fault log allows for faster and more convenient analysis of the actual cause of the device alarm, improving the efficiency of fault analysis.

[0129] This application discloses a computer-readable medium storing a computer program thereon, wherein when the program is executed by a processor, it implements a fault data processing method as described in any of the above embodiments.

[0130] This application discloses an apparatus including: one or more processors and a storage device storing one or more programs thereon. When the one or more programs are executed by the one or more processors, the one or more processors implement the fault data processing method as described in any of the above embodiments.

[0131] Those skilled in the art will be able to implement or use this invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0132] It should also be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, 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. Without further limitations, 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 said element.

Claims

1. A method for processing fault data, characterized in that, When applied to a host computer, the method for processing the fault data includes: Send a system status log read request to the lower-level machine; Receive system status logs sent by the lower-level machine; wherein, the system status logs include: fault information that has occurred in the monitored device, the lower-level machine operation cycle at which the monitored device failed, and the current lower-level machine operation cycle; The system status log is parsed to obtain the fault information that has occurred in the monitored device and the time point corresponding to when the monitored device failed. Generate a fault log; wherein the fault log includes: fault information that has occurred in the monitored device and the time point corresponding to when the monitored device experienced a fault; The step of parsing the system status log to obtain the fault information of the monitored device and the time point corresponding to the fault of the monitored device includes: Using preset fault parsing rules, the fault information in the system status log is parsed to obtain the fault information in plaintext form. Furthermore, time conversion parsing is performed using the lower-level machine's operating cycle at the time the monitored device malfunctioned, the current lower-level machine's operating cycle, and the current time point to calculate the time point corresponding to the time the monitored device malfunctioned. The fault parsing rules are pre-agreed rules between the host computer and the lower-level machine for parsing fault information. The fault log includes: the plaintext fault information and the time point corresponding to the time the monitored device malfunctioned.

2. The method according to claim 1, characterized in that, The process involves using the lower-level machine's operating cycle at the time the monitored device malfunctioned, the current lower-level machine's operating cycle, and the current time point to perform time conversion and analysis. The resulting time point corresponding to the time when the monitored device malfunctioned is calculated, including: Substitute the lower-level machine operation cycle at the time the monitored device malfunctioned, the current lower-level machine operation cycle, and the current time point into the time conversion analysis formula to obtain the time point corresponding to the time when the monitored device malfunctioned. The time conversion formula is as follows: T represents the time point when the monitored device malfunctions; T1 represents the current time point; tick1 represents the current lower-level machine operation cycle; tick2 represents the lower-level machine operation cycle when the monitored device malfunctions; and Cycle represents the duration of the lower-level machine operation cycle.

3. A method for processing fault data, characterized in that, When applied to a lower-level machine, the method for processing the fault data includes: The monitored equipment is monitored, and the fault information of the monitored equipment and the lower-level machine operation cycle at the time of the fault are recorded in the system status log. Receive system status log read requests sent by the host computer; In response to the system status log read request, the currently recorded system status log is sent to the host computer, which then uses the system status log to parse and obtain the fault log. The system status log includes: fault information of the monitored device, the lower-level machine operating cycle at the time the monitored device failed, and the current lower-level machine operating cycle. The fault log includes: fault information of the monitored device and the time point corresponding to the time the monitored device failed. The host computer uses the system status log to parse and obtain the fault log, including: The host computer uses preset fault parsing rules to parse the fault information in the system status log to obtain the fault information in plaintext form. It then uses the lower-level machine's operating cycle at the time the monitored device malfunctioned, the current lower-level machine's operating cycle, and the current time point to perform time conversion parsing, calculating the time point corresponding to the time the monitored device malfunctioned. The fault parsing rules are pre-agreed rules between the host computer and the lower-level machine for parsing fault information. The fault log includes the plaintext fault information and the time point corresponding to the time the monitored device malfunctioned.

4. The method according to claim 3, characterized in that, The monitoring of the monitored equipment, including recording the fault information of the monitored equipment to the system status log, includes: The monitored device is monitored to obtain the system status information of the monitored device in each lower-level machine operation cycle; wherein, the system status information of the lower-level machine operation cycle is fault information used to describe the fault that occurs in the monitored device during the lower-level machine operation cycle; For each lower-level machine operation cycle, compare the system status information of the lower-level machine operation cycle with the system status information of the previous lower-level machine operation cycle; if the system content data of the lower-level machine operation cycle is inconsistent with the system content data of the previous lower-level machine operation cycle, then record the system content data of the lower-level machine operation cycle and the lower-level machine operation cycle in the system status log.

5. The method according to claim 3, characterized in that, The monitoring of the monitored equipment, including recording the fault information of the monitored equipment to the system status log, includes: The monitored device is monitored to obtain the system status information of the monitored device in each lower-level machine operation cycle; wherein, the system status information of the lower-level machine operation cycle is fault information used to describe the fault that occurs in the monitored device during the lower-level machine operation cycle; For each lower-level machine operation cycle, the system status information of the lower-level machine operation cycle and the lower-level machine operation cycle are recorded in the system status log.

6. A fault data processing device, characterized in that, The fault data processing device, applied to a host computer, includes: The first sending unit is used to send a system status log read request to the lower-level machine. The first receiving unit is used to receive the system status log sent by the lower-level machine; wherein, the system status log includes: fault information that has occurred in the monitored device, the lower-level machine operation cycle at which the monitored device failed, and the current lower-level machine operation cycle. The parsing unit is used to parse the system status log to obtain the fault information that has occurred in the monitored device and the time point corresponding to when the monitored device failed. The first generation unit is used to generate a fault log; wherein the fault log includes: fault information that has occurred in the monitored device and the time point corresponding to when the monitored device malfunctioned; The parsing unit includes: The parsing subunit is used to parse the fault information in the system status log using preset fault parsing rules to obtain the fault information in plaintext form; and to perform time conversion parsing using the lower-level machine's operating cycle at the time the monitored device malfunctioned, the current lower-level machine's operating cycle, and the current time point to calculate the time point corresponding to the time the monitored device malfunctioned; wherein, the fault parsing rules are rules for parsing fault information pre-agreed between the upper-level machine and the lower-level machine; the fault log includes: the plaintext fault information and the time point corresponding to the time the monitored device malfunctioned.

7. A fault data processing device, characterized in that, The fault data processing device, applied to a lower-level machine, includes: The monitoring unit is used to monitor the monitored equipment and record the fault information of the monitored equipment and the lower-level machine operation cycle when the monitored equipment fails into the system status log. The second receiving unit is used to receive system status log reading requests sent by the host computer. The second sending unit is used to respond to the system status log read request and send the currently recorded system status log to the host computer, which then uses the system status log to parse and obtain the fault log. The system status log includes: fault information that has occurred on the monitored device, the lower-level machine's operating cycle at the time the monitored device failed, and the current lower-level machine's operating cycle. The fault log includes: fault information that has occurred on the monitored device and the time point corresponding to the time the monitored device failed. The host computer uses the system status log to parse and obtain the fault log, including: The host computer uses preset fault parsing rules to parse the fault information in the system status log to obtain the fault information in plaintext form. It then uses the lower-level machine's operating cycle at the time the monitored device malfunctioned, the current lower-level machine's operating cycle, and the current time point to perform time conversion parsing, calculating the time point corresponding to the time the monitored device malfunctioned. The fault parsing rules are pre-agreed rules between the host computer and the lower-level machine for parsing fault information. The fault log includes the plaintext fault information and the time point corresponding to the time the monitored device malfunctioned.

8. A computer-readable medium, characterized in that, It stores a computer program thereon, wherein the program, when executed by a processor, implements the method as described in any one of claims 1 to 2, or the method as described in any one of claims 3 to 5.

9. A device, characterized in that, include: One or more processors; A storage device on which one or more programs are stored; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1 to 2, or the method as described in any one of claims 3 to 5.

Images