Instrument log data processing method and system, electronic equipment and medium

Abstract

The invention provides an instrument log data processing method and system, electronic equipment and a medium, and belongs to the technical field of vehicle instruments. Obtaining an independently packaged MCU log data packet according to the instrument log data; sending the MCU log data packet to instrument middleware through a preset communication protocol, so that the instrument middleware prints the MCU log data packet in an instrument log; and exporting the instrument log, and analyzing the instrument log according to a preset unpacking script to obtain a problem analysis result. According to the method, the MCU log data packet is independently grouped and sent without depending on the instrument interaction data packet, so that the sending time point is more flexibly selected, and the transmission abnormal risk of long-segment data is reduced. And after receiving the MCU log data packet, the instrument middleware only needs to print the data string in the log, so that the code operation burden is reduced. And the MCU log is captured from the log file for unpacking analysis, so that the analyzed MCU log data can be conveniently obtained to analyze problems.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of vehicle instrument, and in particular relates to an instrument log data processing method and system, electronic equipment and medium. BACKGROUND

[0002] With the development of digital large screen of vehicle instrument, the complexity of instrument system is higher and higher, and display abnormalities in use are more and more common. For instrument micro control unit (MCU), a large number of underlying operation logic is processed, and the result is sent to system on chip (SoC) for further processing by instrument middleware, which includes the on-off of indicator light, the pop-up of pop-up window, and the specific value of table head display. In order to quickly locate whether the problem occurs in instrument MCU or instrument middleware, or even locate the problem in which part of the instrument MCU, an effective and detailed instrument MCU log acquisition and processing process is needed. SUMMARY

[0003] The present application aims to solve at least one of the technical problems in the prior art, and provides an instrument log data processing method, system, electronic equipment and medium.

[0004] In a first aspect, an instrument log data processing method is provided, comprising:

[0005] obtaining instrument log data;

[0006] obtaining MCU log data packets separately packaged according to the instrument log data;

[0007] sending the MCU log data packets to instrument middleware through a preset communication protocol, so that the instrument middleware prints the MCU log data packets in the instrument log;

[0008] exporting the instrument log, and analyzing the instrument log according to a preset unpacking script to obtain a problem analysis result.

[0009] In some embodiments, the MCU log data packets obtained separately packaged according to the instrument log data comprise:

[0010] determining intermediate process variables of problem analysis;

[0011] extracting intermediate process data from the instrument log data based on the intermediate process variables;

[0012] packaging the intermediate process data into MCU log data packets according to a preset data packaging method.

[0013] In some embodiments, the step of packaging the intermediate process data into MCU log data packets according to a preset data packet packaging mode comprises:

[0014] establishing an MCU log data packet packaging mode;

[0015] allocating bit positions based on the MCU log data packet packaging mode according to the length of the intermediate process data and integrating the intermediate process data into a structure to obtain MCU log data packets;

[0016] setting the first byte of the MCU log data packets corresponding to different modules to different values.

[0017] In some embodiments, the step of sending the MCU log data packets to the instrument middleware through a preset communication protocol comprises:

[0018] setting a trigger condition and a sending period;

[0019] sending the MCU log data packets to the instrument middleware periodically based on a preset communication protocol and the sending period;

[0020] and / or,

[0021] sending the MCU log data packets to the instrument middleware based on a preset communication protocol and the trigger condition.

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

[0023] determining whether an instrument display abnormality occurs;

[0024] when the instrument display abnormality occurs, performing the steps of exporting the instrument log, analyzing the instrument log according to a preset unpacking script, and obtaining a problem analysis result.

[0025] In some embodiments, the step of exporting the instrument log, analyzing the instrument log according to a preset unpacking script, and obtaining a problem analysis result comprises:

[0026] exporting the instrument log;

[0027] obtaining a preset keyword of the instrument middleware, searching for the keyword in the instrument log, and capturing the corresponding MCU log;

[0028] analyzing the MCU log according to a preset unpacking script to obtain a problem analysis result.

[0029] In some embodiments, the step of analyzing the MCU log according to a preset unpacking script to obtain a problem analysis result comprises:

[0030] writing a preset unpacking script;

[0031] According to the preset unpacking script, the corresponding MCU log is parsed respectively to obtain parsed MCU log data;

[0032] According to the parsed MCU log data, a problem analysis result is obtained.

[0033] In a second aspect, an embodiment of the present application provides an instrument log data processing system, comprising:

[0034] a data acquisition module configured to acquire instrument log data;

[0035] an MCU log data packet module configured to obtain individually packaged MCU log data packets according to the instrument log data;

[0036] a sending and printing module configured to send the MCU log data packets to an instrument middleware through a preset communication protocol, so that the instrument middleware prints the MCU log data packets in an instrument log;

[0037] an export and unpacking module configured to export the instrument log, parse the instrument log according to a preset unpacking script, and obtain a problem analysis result.

[0038] In a third aspect, an embodiment of the present application provides an electronic device, comprising:

[0039] one or more processors;

[0040] a memory configured to store one or more programs;

[0041] When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any of the above.

[0042] In a fourth aspect, an embodiment of the present application provides a computer readable medium, wherein the computer readable medium stores a computer program, and the computer program is executed by a processor to implement the steps in the method described in any of the above.

[0043] The instrument log data processing method provided by the application comprises the following steps: obtaining instrument log data; obtaining MCU log data packets by separately packing the instrument log data; sending the MCU log data packets to instrument middleware through a preset communication protocol, so that the instrument middleware prints the MCU log data packets in an instrument log; exporting the instrument log, and analyzing the instrument log according to a preset unpacking script to obtain a problem analysis result. The MCU log data packets are sent by separate packing, and are not dependent on instrument interaction data packets, so that the time point of sending can be more flexibly selected, and the risk of transmission abnormality of long data is reduced. In addition, the instrument middleware does not need to unpack each data after receiving the MCU log data packets, but only needs to print the data string in the log, so that the code running has little burden. Finally, the MCU logs can be captured from the log file, and the MCU log data after analysis can be obtained by separate unpacking script, so that the problem can be analyzed more conveniently. BRIEF DESCRIPTION OF DRAWINGS

[0044] Figure 1 An IPCL frame structure diagram involved in the embodiment of the application;

[0045] Figure 2 A flowchart of an instrument log data processing method provided by the embodiment of the application;

[0046] Figure 3 A main flowchart of log acquisition and log processing in the embodiment of the application;

[0047] Figure 4 A structural block diagram of an instrument log data processing system provided by the embodiment of the application;

[0048] Figure 5 A structural block diagram of an electronic device provided by the embodiment of the application. DETAILED DESCRIPTION

[0049] In order to enable those skilled in the art to better understand the technical solutions of the present application, the exemplary embodiments of the present application will be described in detail below with reference to the accompanying drawings, which include various details of the embodiments of the present application to help understanding. It should be considered that they are only exemplary. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Also, in order to be clear and concise, the description in the following description omits the description of well-known functions and structures.

[0050] In the case of no conflict, the embodiments of the present application and the features in the embodiments can be combined with each other.

[0051] As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed items.

[0052] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. As used herein, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. “Coupled” or “connected” or similar terms are not restricted to physical or mechanical connections or associations, but can also include electrical connections, whether direct or indirect.

[0053] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted in an overly literal or overly formal sense unless expressly so defined herein.

[0054] In the technical solutions of the present application, the collection, storage, use, processing, transmission, provision and disclosure of user personal information comply with relevant laws and regulations and do not violate public order and good customs. The use of user data in the technical solutions complies with relevant national laws and regulations (for example, “Information Security Technology Personal Information Security Specification” and the like). For example, appropriate measures are taken for personal information access control; restrictions are given to the display of personal information; the use purpose of personal information does not exceed the direct or reasonably related range; the use of personal information eliminates explicit identity pointing and avoids precise positioning to a specific individual.

[0055] In the related art, as Figure 1The IPCL frame structure shown, the instrument MCU sends data to the SoC, using IPCL protocol transmission. The IPCL protocol specifies the frame format of the transmission, including the frame header, address code, function code, rolling count, data length, data packet and CRC check bit, wherein the most important is the data packet. The two parties agree on the structure of the packet, and the instrument MCU will form the instrument interaction data packet according to the data to be sent, and the instrument middleware can also unpack the data to obtain the data, and print the received data packet and the unpacked result in the instrument log. When the instrument display is abnormal, for example, a certain indicator light is incorrectly turned on, or the speedometer display is incorrect, the data packet and unpacked result sent by the instrument MCU at the corresponding time point can be found in the log, and after comparison, whether the calculation result of the instrument MCU is incorrect can be found out, thereby improving the problem solving efficiency of the display abnormality. However, the data required by the instrument middleware is only the final result, so the IPCL protocol generally only includes the final result when designing the instrument interaction data packet, such as the display value of the speedometer and the total mileage. Since the calculation of some modules in the instrument MCU is very complex, there are many intermediate processes, such as the calculation of the fuel gauge and the range. When these modules display abnormally, it is difficult to find out the error in which intermediate process only by the final display value, thereby increasing the difficulty of solving the problem.

[0056] In view of the above technical defects, an improved technology is provided: in the scheme, the length of the instrument interaction data packet sent by the IPCL protocol is increased, and some important intermediate process data is added. In this way, when the display abnormality problem occurs, the problem can be located in which step by checking the intermediate process data, thereby quickly solving the problem. However, this way also has defects: first, since the added intermediate process data is much, and is frequently sent after the instrument interaction data packet, the risk of data transmission exception is increased; second, the final result data in the instrument interaction data packet is required by the instrument middleware, and the intermediate process data is not required, and the instrument middleware unpacks all the data, which increases the running burden of the code; finally, the packaging and unpacking of these intermediate data also need to be coordinated, and the increase and decrease of data will cause a great burden.

[0057] To solve at least one of the technical problems in the related art, the present application provides an instrument log data processing method. Figure 2 A flowchart of an instrument log data processing method provided by an embodiment of the present application is shown.

[0058] As an embodiment of the present application, as shown in the figure, the instrument log data processing method comprises the steps of: Figure 2

[0059] Step S1: obtaining instrument log data;

[0060] ​Step S2: obtaining a separately packaged MCU log data packet from the meter log data;

[0061] Step S3: sending the MCU log data packet to the meter middleware through a preset communication protocol, so that the meter middleware prints the MCU log data packet in the meter log;

[0062] Step S4: exporting the meter log, and analyzing the meter log according to a preset unpacking script to obtain a problem analysis result.

[0063] It should be noted that the execution subject in the embodiment can be an electronic device, which can be a computer device with a data processing function, and can also be other devices that can realize the same or similar functions, and the embodiment does not limit this. In the embodiment, the execution subject is taken as a computer device, for example, a meter MCU, for example.

[0064] The meter log data processing method described in the embodiment aims to provide a flow of meter log data acquisition and processing. First, the intermediate process data will also be sent to the meter middleware to facilitate locating the step where the problem occurs. However, unlike the related art described above, the intermediate process data in the embodiment is separately packaged to send an MCU log data packet, and does not depend on the meter interaction data packet. In this way, the time point of sending can be more flexible, and the risk of transmission exception of long data can be reduced. In addition, the meter middleware does not need to unpack each data after receiving these MCU log data packets, but only needs to print the data string in the log, which does not have too much burden on the running of the code. As for the final unpacking process, the MCU logs can be grabbed from the log file, and the unpacked analysis can be performed through a separate script. The analyzed MCU log data can also be obtained to analyze the problem. Moreover, the packaging process and the unpacking script are completed by the meter MCU, so that additional communication and coordination are not required when adding or reducing log data. Only the meter MCU needs to change the code of packaging and unpacking.

[0065] In some embodiments, obtaining a separately packaged MCU log data packet from the meter log data includes: determining an intermediate process variable for problem analysis; extracting intermediate process data from the meter log data based on the intermediate process variable; and separately packaging the intermediate process data into an MCU log data packet according to a preset data packaging method.

[0066] In some embodiments, the intermediate process data is individually packaged into MCU log data packets according to a preset data packet packaging mode, including: formulating an MCU log data packet packaging mode; allocating bit positions based on the MCU log data packet packaging mode according to the length of the intermediate process data and integrating into a structure to obtain an MCU log data packet; setting the first byte of the MCU log data packet corresponding to different modules to different values.

[0067] Specifically, referring to Figure 3 , the main process of the embodiment includes: packaging the intermediate process data into MCU log data packets, transmitting to the instrument middleware through the IPCL protocol, printing in the instrument log, then grabbing the MCU log in the log file, and analyzing the data through the unpacking script.

[0068] Illustratively, the instrument log data is obtained, and the individually packaged MCU log data is obtained according to the instrument log data: for modules with complex calculation processes, some important data in their calculation processes are selected, bit positions are allocated according to the length of the data, and a large structure is integrated as an MCU log data packet.

[0069] In an example, the functions and calculation processes of the modules are understood, it is determined which data is critical for diagnosing problems, and important data is obtained; the data type (e.g., int, float, char, etc.) is determined according to the nature and range of the important data, and the bit length of the data type on the current system is determined; the bit field is used to define the structure, so that the number of bits occupied by each data field can be accurately controlled.

[0070] Illustratively, the MCU log data packets of different modules are generally independently packaged, and the embodiment can be distinguished by setting the first byte to different values, for example, the MCU log data packet of the oil meter is set to a fixed 0x01, and the MCU log data packet of the driving computer module is set to a fixed 0x02. In this way, the logs of different modules can be conveniently distinguished when the logs are grabbed later.

[0071] In some embodiments, the MCU log data packet is sent to the instrument middleware through a preset communication protocol, so that the instrument middleware prints the MCU log data packet in the instrument log.

[0072] In some embodiments, the MCU log data packet is sent to the instrument middleware through a preset communication protocol, including: setting a trigger condition and a sending period; sending the MCU log data packet to the instrument middleware based on the preset communication protocol and the sending period; and / or, sending the MCU log data packet to the instrument middleware based on the preset communication protocol and the trigger condition.

[0073] Specifically, the frame containing the MCU log data packet is sent to the instrument middleware through the IPCL protocol. The main difference compared with the frame of the instrument interaction data packet is that the function code of the frame is different, facilitating the instrument middleware to receive and make different corresponding processing. The instrument interaction data packet is parsed and processed, and the MCU log data packet is directly printed into the log, saving the MCU log data packet parsing part and reducing the code burden.

[0074] Specifically, the MCU data packet is also packaged separately in the embodiment, which is also conducive to selecting different sending methods. Figure 3 As shown in the figure, some module data needs to be monitored for changes, so a period can be set to periodically run the sending function; some module data only needs to check the state change before and after to find out the problem, so only the trigger condition corresponding to the state change needs to be set, and the sending function is run when the condition is met.

[0075] In the embodiment, a separate MCU log data packet is constructed in the log acquisition process, which breaks away from the dependence on the instrument interaction data packet, reduces the risk of abnormal long data transmission, and lays the foundation for flexible selection of periodic sending and trigger sending methods in the future; in addition, the instrument middleware only needs to print the MCU log data packet, which reduces the code burden and is a one-time solution that does not need to be changed in the future. The above process includes the acquisition of instrument log data, i.e., how log data is written into a log file. When the instrument display problem occurs, the log data needs to be processed to obtain the parsed data for analyzing the problem.

[0076] In some embodiments, the method further includes: determining whether an instrument display abnormal problem occurs; and performing the steps of exporting the instrument log, analyzing the instrument log according to a preset unpacking script, and obtaining a problem analysis result when the instrument display abnormal problem occurs.

[0077] Specifically, as shown in the figure, it is determined whether an instrument display abnormal problem occurs; if no instrument display abnormal problem occurs, the process can be ended; if an instrument display abnormal problem occurs, the log data needs to be processed to obtain the parsed data for analyzing the problem. Figure 3

[0078] In some embodiments, exporting the instrument log, analyzing the instrument log according to a preset unpacking script, and obtaining a problem analysis result include: exporting the instrument log; obtaining a keyword preset by the instrument middleware, searching the keyword in the instrument log to capture the corresponding MCU log; and analyzing the MCU log according to a preset unpacking script to obtain a problem analysis result.

[0079] ​Specifically, a log file (instrument log) is exported, in which a keyword is searched to capture all MCU logs. The keyword is generally set by the instrument middleware and printed before the MCU log data string. For example, after receiving a log data packet each time, the keyword MCUlog is printed first, followed by all log data strings printed in hexadecimal. For problems of a certain module, the byte distinguishing designed when packetizing can be further used to separate the required log data string.

[0080] Exemplarily, log data generated by the MCU during operation is exported to a file, a specific keyword is searched in the log file to quickly locate the relevant log entries, and all log entries matching the keyword are extracted from the log file, which includes the state and event information of the MCU at a specific time point. The keyword is generally set by the instrument middleware (a part of the software responsible for coordinating the interaction between different modules and hardware) and is printed before the log data string to facilitate identification and processing.

[0081] In some embodiments, the MCU log is parsed according to a preset unpacking script to obtain a problem analysis result, including: writing a preset unpacking script; parsing the corresponding MCU log according to the preset unpacking script to obtain parsed MCU log data; and obtaining a problem analysis result according to the parsed MCU log data.

[0082] Specifically, the log data is parsed using an unpacking script. Unpacking is the reverse operation of packetizing, and it is not difficult to implement a script. Different modules have different packetizing, and the unpacking script is also separate. However, since the log formats are similar, the unpacking scripts are also similar, and are easy to implement. Moreover, since the instrument middleware only needs to print data strings and does not care about the length of the data string or the packetizing method, when the log data needs to be added or reduced, the code of the instrument middleware does not need to be changed. All changes are in the packetizing code of the instrument MCU and the unpacking script, which saves the time of communication and joint debugging.

[0083] In this embodiment, in the log processing flow, the MCU log is separated by distinguishing the first byte of different modules to facilitate quick locking of the log data of a certain module; the MCU log data is processed by a separate unpacking script, and the change is limited in the instrument MCU, which saves the time of communication and joint debugging.

[0084] The core content of the technical solution of this embodiment is: separate packetizing and sending of the MCU log data packet, and parsing the log using an unpacking script outside the project. The two complement each other and are the key points that distinguish the method described in this embodiment from other solutions, which constitutes the greatest advantage of this embodiment: facilitating the parsing of log data and greatly improving the efficiency of processing instrument display abnormal problems.

[0085] The instrument log data processing method provided by the embodiment comprises: acquiring instrument log data; obtaining MCU log data packets separately packaged according to the instrument log data; sending the MCU log data packets to instrument middleware through a preset communication protocol, so that the instrument middleware prints the MCU log data packets in an instrument log; exporting the instrument log, and analyzing the instrument log according to a preset unpacking script to obtain a problem analysis result. In the embodiment, the MCU log data packets are sent separately packaged, and are not dependent on instrument interaction data packets, so that the time point of sending can be selected more flexibly, and the risk of transmission abnormality of long data is reduced. In addition, the instrument middleware does not need to unpack each data after receiving the MCU log data packets, but only needs to print the data string in the log, so that the code running has no great burden. Finally, the unpacking process can grab the MCU logs from the log file, and analyze the MCU logs by a separate preset unpacking script, so that the MCU log data after analysis can be obtained to analyze the problem. The whole process of acquiring and processing the instrument log in the embodiment facilitates the analysis of the log data, and greatly improves the efficiency of processing the instrument display abnormality problem.

[0086] Reference Figure 4 , Figure 4 is a structural block diagram of an embodiment of the instrument log data processing system. As shown in Figure 4 , the instrument log data processing system comprises:

[0087] The data acquisition module 10 is configured to acquire instrument log data.

[0088] The MCU log data packaging module 20 is configured to obtain MCU log data packets separately packaged according to the instrument log data.

[0089] The sending and printing module 30 is configured to send the MCU log data packets to instrument middleware through a preset communication protocol, so that the instrument middleware prints the MCU log data packets in an instrument log.

[0090] The exporting and unpacking module 40 is configured to export the instrument log, and analyze the instrument log according to a preset unpacking script to obtain a problem analysis result.

[0091] The instrument log data processing system provided by the embodiment can send MCU log data packets through separate packetization, without relying on instrument interaction data packets, so that the time point of sending can be selected more flexibly, and the risk of transmission exception of long data is reduced. In addition, the instrument middleware does not need to unpack each data after receiving the MCU log data packets, but only needs to print the data string in the log, so that the code operation has little burden. Finally, the unpacking process can capture the MCU logs from the log file, and analyze the MCU log data after analysis through a separate preset unpacking script, so that the MCU log data after analysis can be obtained more conveniently to analyze the problem. In the log acquisition process, the separate MCU log data packets are constructed, the dependence on the instrument interaction data packets is eliminated, the risk of long data transmission exception is reduced, and the foundation is laid for the sending mode of flexible periodic sending and triggered sending in the future. In the log acquisition process, the instrument middleware only needs to print the MCU log data packets, so that the code burden is reduced, and the subsequent change is not needed. In the log processing process, the MCU logs are separated, and the first byte of different modules is distinguished, so that the log data of a certain module can be locked quickly and conveniently. In the log processing process, the MCU log data is processed by a separate unpacking script, and the change is limited in the instrument MCU, so that the time of communication and joint debugging is saved. The whole instrument log acquisition and processing process in the embodiment facilitates the analysis of log data, and greatly improves the efficiency of instrument display exception problem processing.

[0092] In addition, technical details not described in detail in the instrument log data processing system embodiment can be referred to the instrument log data processing method provided by any embodiment of the application, which will not be described here.

[0093] Based on the same inventive concept, the embodiment of the application also provides an electronic device. Figure 5 The structure block diagram of the electronic device provided by the embodiment of the application is shown in FIG. 1. As shown in FIG. 1, the electronic device provided by the embodiment of the application includes one or more processors 101, a memory 102, and one or more I / O interfaces 103. The memory 102 stores one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors implement the instrument log data processing method in any of the above embodiments. Figure 5

[0094] ​The processor 101 is a device with data processing capability, including but not limited to a central processing unit (CPU) and the like; the memory 102 is a device with data storage capability, including but not limited to a random access memory (RAM, more specifically SDRAM, DDR, etc.), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), and a flash memory (FLASH); the I / O interface (read-write interface) 103 is connected between the processor 101 and the memory 102, and can realize information interaction between the processor 101 and the memory 102, including but not limited to a data bus (Bus) and the like.

[0095] In some embodiments, the processor 101, the memory 102, and the I / O interface 103 are connected to each other through the bus 104, and further connected to other components of the computing device.

[0096] In some embodiments, the one or more processors 101 include a field programmable gate array.

[0097] The embodiments of the present application also provide a computer readable medium. The computer readable medium stores a computer program, wherein the program is executed by a processor to implement the steps in the meter log data processing method in any of the above embodiments. The computer readable storage medium can be a volatile or non-volatile computer readable storage medium.

[0098] The embodiments of the present application also provide a computer program product, including computer readable code or a non-volatile computer readable storage medium carrying computer readable code, when the computer readable code is run in a processor of an electronic device, the processor in the electronic device executes the meter log data processing method.

[0099] Those skilled in the art can understand that all or some of the steps in the above disclosed method, the functions of the modules / units in the system and the device can be implemented as software, firmware, hardware, and appropriate combinations thereof. In the hardware implementation, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component can have multiple functions, or one function or step can be performed by several physical components in cooperation. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software can be distributed on a computer readable storage medium, which can include computer storage media (or non-transitory media) and communication media (or transitory media).

[0100] As those skilled in the art will appreciate, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable program instructions, data structures, program modules or other data. Computer storage media include, but are not limited to, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), static random access memory (SRAM), flash memory or other memory technology, portable compact disc read only memory (CD-ROM), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer. Further, as those skilled in the art will appreciate, communication media typically embodies computer readable program instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term "modulated data signal" means a signal that has one or more of its characteristics changed or set in a manner so as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as wireless networks, cellular telephone networks, code division multiple access (CDMA) networks, and other terrestrial and satellite radio frequency communication networks. Thus the computer readable program instructions and / or other program modules can be embodied in a computer readable storage medium, which can be any device or article that is enab!ed to store and / or carry computer readable program instructions and / or data structures. The computer readable storage medium can also be distributed over networked computer systems so that the computer readable program instructions and / or other program modules are stored and executed in a distributed fashion.

[0101] Computer readable program instructions described herein can be downloaded to respective computing / processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and / or a wireless network. The network can comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and / or edge servers. A network adapter card or network interface in each computing / processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing / processing device.

[0102] Computer readable program instructions for carrying out operations of the present application can be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer readable program instructions can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate array (FPGA), or programmable logic array (PLA) can execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present application.

[0103] The computer program product described herein can be embodied in a specific manner by hardware, software, or a combination thereof. In an optional embodiment, the computer program product is embodied as a computer storage medium. In another optional embodiment, the computer program product is embodied as a software product, such as a software development kit (SDK), and the like.

[0104] The computer program product described herein can be embodied in a specific manner by hardware, software, or a combination thereof. In an optional embodiment, the computer program product is embodied as a computer storage medium. In another optional embodiment, the computer program product is embodied as a software product, such as a software development kit (SDK), and the like.

[0105] These computer readable program instructions can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. These computer readable program instructions can also be stored in a computer readable storage medium that can include a non-transitory computer readable storage medium that can be a computer- readable storage medium having no data storage cycles that change state. The instructions can be executed by one or more processors of a computer, other programmable data processing apparatus, or other devices to produce a computer-implemented process such that the instructions which execute via the one or more processors of the computer or other programmable data processing devices create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. The computer program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0106] The computer readable program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0107] The flow diagrams and the block diagrams in the drawings are presented to illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to the present application. In this regard, each block in the flow diagrams and the block diagrams can represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical functions ("instructions"). In some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks can sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and / or flow diagrams, and combinations thereof, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and

[0108] Example embodiments have been disclosed herein and, although specific terms are employed, they are used in a generic and descriptive sense only and not for purposes of limitation. In some instances, it will be apparent to those skilled in the art that features, characteristics or aspects described in relation to one embodiment can be applied to other embodiments, unless otherwise clearly stated. It will also be apparent to one skilled in the art that various modifications, changes, additions and omissions can be made without departing from the scope of the present application as set forth in the claims.

Claims

1. An instrument log data processing method, characterized by, The method comprises: acquiring instrument log data; obtaining MCU log data packets separately packaged according to the instrument log data; sending the MCU log data packets to instrument middleware through a preset communication protocol, so that the instrument middleware prints the MCU log data packets in an instrument log; exporting the instrument log, and analyzing the instrument log according to a preset unpacking script to obtain a problem analysis result.

2. The method of claim 1, wherein, The obtaining MCU log data packets separately packaged according to the instrument log data comprises: determining intermediate process variables of problem analysis; extracting intermediate process data from the instrument log data based on the intermediate process variables; packaging the intermediate process data into MCU log data packets separately according to a preset data packaging mode.

3. The method of claim 2, wherein, The packaging the intermediate process data into MCU log data packets separately according to a preset data packaging mode comprises: formulating an MCU log data packet packaging mode; allocating bit positions according to lengths of the intermediate process data and integrating the intermediate process data into a structure to obtain MCU log data packets based on the MCU log data packet packaging mode; setting the first byte of the MCU log data packets corresponding to different modules to different values.

4. The method of claim 1, wherein, The sending the MCU log data packets to instrument middleware through a preset communication protocol comprises: setting a trigger condition and a sending period; periodically sending the MCU log data packets to instrument middleware based on the preset communication protocol and the sending period; and / or, triggering the MCU log data packets to be sent to instrument middleware based on the preset communication protocol and the trigger condition.

5. The method of claim 1, wherein, The method further comprises: judging whether an instrument display abnormality problem occurs; when the instrument display abnormality problem occurs, performing the exporting the instrument log, and analyzing the instrument log according to a preset unpacking script to obtain a problem analysis result.

6. The method of claim 5, wherein, The exporting the instrument log, and analyzing the instrument log according to a preset unpacking script to obtain a problem analysis result comprises: exporting the instrument log; acquiring a keyword preset by the instrument middleware, searching the keyword in the instrument log to capture corresponding MCU logs; analyzing the MCU logs according to a preset unpacking script to obtain a problem analysis result.

7. The method of claim 6, wherein, The analyzing the MCU logs according to a preset unpacking script to obtain a problem analysis result comprises: writing a preset unpacking script; analyzing corresponding MCU logs according to the preset unpacking script to obtain MCU log data after analysis; obtaining a problem analysis result according to the MCU log data after analysis.

8. An instrument log data processing system characterized by, The method comprises: a data acquisition module configured to acquire instrument log data; an MCU log data packaging module configured to obtain MCU log data packets separately packaged according to the instrument log data; a sending and printing module configured to send the MCU log data packets to instrument middleware through a preset communication protocol, so that the instrument middleware prints the MCU log data packets in an instrument log; an exporting and unpacking module configured to export the instrument log, and analyze the instrument log according to a preset unpacking script to obtain a problem analysis result.

9. An electronic device, comprising: The method comprises: one or more processors; a memory storing one or more programs; when the one or more programs are executed by the one or more processors, cause the one or more processors to carry out the method according to any one of claims 1 to 7.

10. A computer readable medium having stored thereon a computer program, characterized in that the computer program which, when executed by the processor, carries out the steps of the method according to any one of claims 1 to 7.

Images