Fault record storage device, upper computer and fault record query system

Abstract

The invention discloses a fault record storage device, an upper computer and a fault record query system, and the device comprises a plurality of first communication interfaces which have different communication protocols and are used for accessing target monitoring equipment so as to obtain a plurality of fault records of the target monitoring equipment based on the corresponding communication protocols; the data processing unit is connected with the plurality of first communication interfaces and is used for storing a plurality of fault records and circularly covering the plurality of fault records based on a storage sequence of the plurality of fault records under the condition that the residual storage space of the data processing unit is smaller than a preset threshold value; the second communication interface is connected with the data processing unit and used for accessing an upper computer so as to send the data messages corresponding to the multiple fault records to the upper computer for a user to inquire, effective storage of the fault records can be achieved only through a single device, then the cost of the fault records can be reduced, and the user experience is improved. And the applicability of the fault record storage device is improved.

Description

Technical Field

[0001] This invention relates to the field of industrial manufacturing technology, and in particular to a fault record storage device, a host computer, and a fault record query system. Background Technology

[0002] In modern industrial manufacturing, actual testing of intelligent industrial products requires long-term tracking and recording of product faults, as well as monitoring and recording the equipment's operating status to facilitate rapid diagnosis and repair when faults occur. However, traditional fault recording solutions have the following problems: traditional fault recording solutions are generally developed for individual products, resulting in poor applicability. Furthermore, during the development and testing phase of intelligent industrial products, large-capacity external storage is typically used to ensure long-term and comprehensive recording of fault information. After the development and testing phase is completed, replacing the storage with a smaller capacity may introduce new risks due to software stability considerations, making replacement inconvenient and leading to unnecessary increases in hardware costs. If software development is undertaken to implement functions such as overwrite and queryability for fault records, its stability still requires extensive and long-term testing, further increasing time and labor costs.

[0003] In summary, current fault recording solutions suffer from technical problems such as high recording costs and poor applicability, making it inconvenient for users to store and retrieve fault records for different monitoring devices. Summary of the Invention

[0004] The purpose of this invention is to at least solve one of the technical problems existing in the prior art, and to provide a fault record storage device, a host computer, and a fault record query system, which can achieve effective storage of fault records with only a single device, thereby reducing the cost of fault records and improving the applicability of the fault record storage device, so that users can store and query fault records for different monitoring devices.

[0005] In a first aspect, this application provides a fault record storage device, comprising: multiple first communication interfaces having different communication protocols for accessing a target monitoring device to obtain multiple fault records of the target monitoring device based on the corresponding communication protocols; a data processing unit connected to the multiple first communication interfaces for storing the multiple fault records, and, when the remaining storage space of the data processing unit is less than a preset threshold, cyclically overwriting the multiple fault records based on the storage order of the multiple fault records; and a second communication interface connected to the data processing unit for accessing a host computer to send data packets corresponding to the multiple fault records to the host computer for user query.

[0006] The fault record storage device provided by the embodiments of the present invention has at least the following beneficial effects: By setting multiple first communication interfaces with different communication protocols, the device can connect to various types of target monitoring devices, thus expanding its applicability. Supporting multiple communication protocols allows the device to be used flexibly in different application scenarios, exhibiting strong adaptability and eliminating the need to develop a dedicated fault record device for each device. Furthermore, by executing a cyclic overwrite strategy through the data processing unit, when the remaining storage space of the data processing unit is less than a preset threshold, cyclic overwrite is performed based on the storage order of the fault records, ensuring the retention of important fault records and avoiding the loss of important data due to insufficient storage space. This effectively improves the utilization rate of storage space, increases storage efficiency, and reduces unnecessary hardware costs. Furthermore, by connecting to a host computer through a second communication interface, the data packets corresponding to the fault records can be sent to the host computer for user query and analysis. This allows users to conveniently view and manage fault records through host computer software, improving the efficiency of fault diagnosis and repair. In summary, it is understood that the device of this application adopts a modular design, which can achieve effective storage of fault records through a single device, thereby reducing the cost of fault records and improving the applicability of the fault record storage device. This allows users to store and query fault records for different monitoring devices, thereby reducing the workload of developers, shortening the development cycle, and reducing development costs.

[0007] In some embodiments, the data processing unit is further configured to, when a new fault record is obtained through the first communication interface and the remaining storage space after storing the plurality of fault records is less than a preset threshold, obtain the storage order of the plurality of fault records, and select the earliest stored fault record from the plurality of fault records based on the storage order for deletion, so as to store the new fault record.

[0008] In some embodiments, the data processing unit is further configured to store the plurality of fault records into a plurality of record files according to the acquisition time corresponding to each fault record, and when the second communication interface receives an instruction signal sent by the host computer, send a data packet to the host computer through the second communication interface, wherein the data packet carries file information of the plurality of record files.

[0009] In some embodiments, the data processing unit is further configured to, upon receiving a first instruction signal sent by the host computer, send a first data message to the host computer via the second communication interface. The first data message carries file feature information of the plurality of record files for user preview. The file feature information includes file date, file size, and file name.

[0010] In some embodiments, the data processing unit is further configured to, upon receiving a second instruction signal sent by the host computer, determine the corresponding target record file based on the file feature information carried in the second instruction signal, and send a second data packet to the host computer through the second communication interface, wherein the second data packet carries the file content information of the target record file for user viewing.

[0011] In some embodiments, the fault record storage device further includes an extended data interface connected to the data processing unit. The data processing unit is further configured to store the plurality of fault records to the external storage device based on a preset file storage format when it detects that an external storage device is connected to the extended data interface.

[0012] Secondly, this application provides a host computer for connecting to the second communication interface in the fault record storage device as described in any one of the first aspects, so as to obtain data packets corresponding to the plurality of fault records for user query.

[0013] The host computer provided by the embodiments of the present invention has at least the following beneficial effects: The host computer in this embodiment is connected to a fault record storage device. Through multiple first communication interfaces with different communication protocols provided in the fault record storage device, this embodiment can access various types of target monitoring devices to expand its applicability. By supporting multiple communication protocols, the device can be used flexibly in different application scenarios, exhibiting strong adaptability, without the need to develop a dedicated fault record device for each device. Furthermore, by executing a cyclic overwrite strategy through the data processing unit, when the remaining storage space of the data processing unit is less than a preset threshold, cyclic overwrite is performed based on the storage order of the fault records, ensuring the retention of important fault records and avoiding the loss of important data due to insufficient storage space. This effectively improves the utilization rate of storage space, increases storage efficiency, and reduces unnecessary hardware costs. Furthermore, by connecting to the host computer through a second communication interface, the data packets corresponding to the fault records can be sent to the host computer for user query and analysis. This allows users to conveniently view and manage fault records through the host computer software, improving the efficiency of fault diagnosis and repair. In summary, it is understood that the fault record storage device in this application adopts a modular design, which can achieve effective storage of fault records through a single device, thereby reducing the cost of fault records and improving the applicability of the fault record storage device. This allows users to store and query fault records for different monitoring devices, thereby reducing the workload of developers, shortening the development cycle, and reducing development costs.

[0014] In some embodiments, the host computer includes a communication module, which is used to send a first instruction signal to the fault record storage device to obtain a first data message sent by the fault record storage device. The first data message carries file feature information of the plurality of record files, including file date, file size, and file name.

[0015] In some embodiments, the host computer further includes a human-computer interaction module, which is connected to the communication module. The human-computer interaction module is used to generate a visual interface based on the file feature information for the user to preview.

[0016] In some embodiments, the communication module is further configured to send a second instruction signal to the fault record storage device in response to a user input signal obtained by the human-computer interaction module, so as to obtain a second data message sent by the fault record storage device, wherein the second instruction signal carries file feature information of the target record file corresponding to the user input signal, and the second data message carries file content information of the target record file.

[0017] In some embodiments, the host computer further includes a parsing module, which is connected to the communication module and the human-computer interaction module. The parsing module is used to parse the second data packet based on a preset message format to display the file content information on the visualization interface for user viewing.

[0018] Thirdly, this application provides a fault record query system, including a fault record storage device as described in any one of the first aspects, and a host computer as described in any one of the second aspects.

[0019] According to embodiments of the present invention, a fault record query system is provided, which has at least the following beneficial effects: Since the fault record query system includes the aforementioned fault record storage device and the aforementioned host computer, multiple first communication interfaces with different communication protocols provided in the fault record storage device allow the present invention to access various types of target monitoring devices, thereby expanding its applicability. By supporting multiple communication protocols, the device can be used flexibly in different application scenarios, exhibiting strong adaptability, without the need to develop a dedicated fault record device for each device. Furthermore, by executing a cyclic overlay strategy through the data processing unit, when the remaining storage space of the data processing unit is less than a preset threshold, cyclic overlay is performed based on the storage order of the fault records, ensuring the retention of important fault records and avoiding the loss of important data due to insufficient storage space. This effectively improves the utilization rate of storage space, increases storage efficiency, and reduces unnecessary hardware costs. Furthermore, by connecting to the host computer through a second communication interface, the data packets corresponding to the fault records can be sent to the host computer for user query and analysis, allowing users to conveniently view and manage fault records through the host computer software, thus improving the efficiency of fault diagnosis and repair. In summary, it is understood that the fault record storage device in this application adopts a modular design, which can achieve effective storage of fault records through a single device, thereby reducing the cost of fault records and improving the applicability of the fault record storage device. This allows users to store and query fault records for different monitoring devices, thereby reducing the workload of developers, shortening the development cycle, and reducing development costs.

[0020] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention may be realized and obtained by means of the structures particularly pointed out in the description, claims, and drawings. Attached Figure Description

[0021] The accompanying drawings are provided to further understand the technical solutions of the present invention and constitute a part of the specification. They are used together with the embodiments of the present invention to explain the technical solutions of the present invention, and do not constitute a limitation on the technical solutions of the present invention.

[0022] The present invention will be further described below with reference to the accompanying drawings and embodiments;

[0023] Figure 1 This is a schematic diagram of an optional structure of a fault record storage device provided in an embodiment of the present invention;

[0024] Figure 2 This is a schematic diagram of the structure of a fault record storage device provided in an embodiment of the present invention, which includes an extended data interface;

[0025] Figure 3 This is a schematic diagram of the structure of a battery unit in a fault record storage device provided in an embodiment of the present invention;

[0026] Figure 4 This is a schematic diagram of the structure of a fault record storage device provided in an embodiment of the present invention, showing the specific communication interface.

[0027] Figure 5 This is a schematic diagram of a fault record storage device connected to a host computer according to an embodiment of the present invention;

[0028] Figure 6 This is a schematic diagram of an optional host computer structure provided in an embodiment of the present invention;

[0029] Figure 7 This is a schematic diagram of an optional structure of a fault record query system provided in an embodiment of the present invention.

[0030] Figure label:

[0031] 100. Fault record storage device; 110. First communication interface; 120. Data processing unit; 130. Second communication interface; 131. USB communication interface; 140. Expansion data interface; 141. External SD card interface; 150. Battery unit; 160. Power supply interface; 200. Host computer; 210. Communication module; 220. Human-computer interaction module; 230. Analysis module; 300. Fault record query system. Detailed Implementation

[0032] This section will describe in detail specific embodiments of the present invention. Preferred embodiments of the present invention are shown in the accompanying drawings. The purpose of the drawings is to supplement the textual description with graphics, so that people can intuitively and vividly understand each technical feature and overall technical solution of the present invention, but they should not be construed as limiting the scope of protection of the present invention.

[0033] In the description of this invention, "several" means one or more, "multiple" means two or more, "greater than," "less than," "exceeding," etc. are understood to exclude the number itself, while "above," "below," "within," etc. are understood to include the number itself. "Any one" refers to one or more, and "at least one of the following" and similar expressions refer to any combination of these items, including any combination of single or multiple items. If "first" or "second" is used in the description, it is only for the purpose of distinguishing technical features and should not be construed as indicating or implying relative importance or implicitly indicating the number of indicated technical features or the order of the indicated technical features.

[0034] It should be noted that the terms "setting," "installing," and "connecting" in the embodiments of this invention should be interpreted broadly. Those skilled in the art can reasonably determine the specific meaning of the above terms in the embodiments of this invention in conjunction with the specific content of the technical solution. For example, the term "connection" can be a mechanical connection, an electrical connection, or a connection that allows for mutual communication; it can be a direct connection or an indirect connection through an intermediate medium.

[0035] It should be noted that the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0036] In modern industrial manufacturing, actual testing of intelligent industrial products requires long-term tracking and recording of product faults, monitoring and recording equipment operating status for rapid diagnosis and repair in case of malfunctions. However, traditional fault recording solutions suffer from the following problems: Traditional solutions are generally developed for individual products, resulting in poor applicability. Furthermore, during the development and testing phase of intelligent industrial products, large-capacity external storage is typically used to ensure long-term and comprehensive fault information recording. After development and testing, replacing the storage with smaller capacity devices may introduce new risks due to software stability considerations, making replacement inconvenient and leading to unnecessary hardware cost increases. If software development is undertaken to implement functions such as overwrite and query capabilities for fault records, its stability still requires extensive and long-term testing, further increasing time and labor costs. In summary, current fault recording solutions suffer from high recording costs and poor applicability, making it inconvenient for users to store and query fault records for different monitoring devices.

[0037] Based on this, the purpose of the present invention is to at least solve one of the technical problems existing in the prior art, and to provide a fault record storage device, a host computer and a fault record query system, which can achieve effective storage of fault records with only a single device, thereby reducing the cost of fault records and improving the applicability of the fault record storage device, so that users can store and query fault records for different monitoring devices.

[0038] The embodiments of this application will be further described below with reference to the accompanying drawings.

[0039] refer to Figure 1 , Figure 1This is an optional structural schematic diagram of a fault record storage device 100 provided in an embodiment of the present invention. In a first aspect, this application provides a fault record storage device 100, comprising: multiple first communication interfaces 110 having different communication protocols, used to access a target monitoring device to obtain multiple fault records of the target monitoring device based on the corresponding communication protocols; a data processing unit 120, connected to the multiple first communication interfaces 110, used to store multiple fault records, and, when the remaining storage space of the data processing unit 120 is less than a preset threshold, to cyclically overwrite the multiple fault records based on their storage order; and a second communication interface 130, connected to the data processing unit 120, used to access a host computer to send data packets corresponding to the multiple fault records to the host computer for user query.

[0040] In this embodiment, by setting multiple first communication interfaces 110 with different communication protocols, the device can be connected to various types of target monitoring equipment to expand its applicability. By supporting multiple communication protocols, the device can be used flexibly in different application scenarios, with strong adaptability, without the need to develop a dedicated fault recording device for each type of equipment. Furthermore, by executing a cyclic overwrite strategy through the data processing unit 120, when the remaining storage space of the data processing unit 120 is less than a preset threshold, cyclic overwrite is performed based on the storage order of the fault records to ensure the retention of important fault records and avoid the loss of important data due to insufficient storage space. This can effectively improve the utilization rate of storage space, improve storage efficiency, and reduce unnecessary hardware costs. Furthermore, by connecting to the host computer through the second communication interface 130, the data packets corresponding to the fault records can be sent to the host computer for users to query and analyze. This allows users to conveniently view and manage fault records through the host computer software, improving the efficiency of fault diagnosis and repair.

[0041] In some embodiments, it is understood that the device of this application adopts a modular design, which can realize effective storage of fault records through a single device, thereby reducing the cost of fault records and improving the applicability of the fault record storage device 100, so that users can store and query fault records for different monitoring devices, thereby reducing the workload of developers, shortening the development cycle, and reducing development costs.

[0042] It is worth noting that current technologies lack universal storage devices for storing fault records. Generally, multiple storage devices are required, or time is spent developing corresponding software, which is time-consuming, labor-intensive, and costly. The main technical concept of this application is to design a fault record storage device 100 with multiple communication protocol interfaces. By supporting multiple communication protocols, the applicability is improved. By optimizing storage resources and reducing hardware costs through an efficient cyclic overlay mechanism, data packets are sent through the second communication interface 130 to realize the fault record query function, thereby improving the efficiency of user query and management. It is simple and effective.

[0043] In some embodiments, the data processing unit 120 is further configured to, when a new fault record is obtained through the first communication interface 110 and the remaining storage space after storing multiple fault records is less than a preset threshold, obtain the storage order of multiple fault records, and delete the fault record stored first from the multiple fault records based on the storage order, so as to store a new fault record.

[0044] It is understood that when the data processing unit 120 receives a new fault record through the first communication interface 110, and after multiple fault records have been stored, if the remaining storage space is detected to be lower than a preset threshold, the data processing unit 120 will check the storage order of all stored fault records and select the earliest stored fault record to delete according to this order, so as to make room for the newly received fault record. This mechanism can ensure that even when storage resources are limited, the system can continuously receive and store the latest fault information, thereby ensuring the system's operating efficiency and fault diagnosis capabilities. In addition, the preset threshold can be adjusted in advance according to the preset fault record storage requirements to avoid the problem of insufficient storage space caused by a sudden large number of fault records.

[0045] In some embodiments, the data processing unit 120 may also obtain the record length of each fault record and the fault frequency corresponding to multiple fault records, and then perform cyclic overwriting based on the storage order, record length and fault frequency of the fault records. For example, for longer records, it may be necessary to overwrite them earlier to ensure sufficient storage space, and when the fault frequency is high, earlier records may be overwritten more frequently to ensure that there is enough space to store new records.

[0046] It is understood that the data processing unit 120 may consider not only the storage order, but also the size (i.e., record length) of each fault record and the associated frequency of fault occurrence to improve the accuracy of fault diagnosis and reduce unnecessary data storage costs. For example, firstly, the system can determine which records are stored first based on the storage order. These records will be the first to be overwritten. Furthermore, when the storage order is the same, the system will prioritize overwriting records with longer record lengths, as longer records occupy more storage space, and overwriting these records can free up more space. Further still, when the storage order and record length are the same, the system will prioritize overwriting records with lower fault frequencies, as frequently occurring fault records are usually more important and should therefore be retained.

[0047] In some embodiments, the data processing unit 120 is further configured to store multiple fault records into multiple record files according to the acquisition time corresponding to each fault record, and when the second communication interface 130 receives an instruction signal sent by the host computer, send a data message to the host computer through the second communication interface 130. The data message carries file information of multiple record files. Specifically, when the data processing unit 120 detects communication data acquired by the first communication interface 110, it will create a corresponding file according to the current time, parse the message sent by the monitored device, and store it according to the time order. Each time it stores, the device will detect the remaining space of the internal FLASH in the data processing unit 120. When the remaining space is lower than a preset threshold, it will clean up the earliest data according to the time order to achieve the purpose of cyclic overwrite storage.

[0048] It is understood that the data processing unit 120 can store all received fault records into multiple independent files according to the time sequence in which they were acquired. When the second communication interface 130 receives an instruction request from the host computer, the data processing unit 120 can send a data message containing information from multiple record files to the requester through this interface. Whenever the first communication interface 110 captures new communication data, the data processing unit 120 will create a new file based on the current time point to parse and store the messages from the monitored device in chronological order. In this way, storing data in chronological order facilitates subsequent data analysis and fault tracing. The cyclic overwrite storage strategy ensures that the system can continue to operate efficiently and record the latest fault conditions in a timely manner with limited storage capacity.

[0049] In some embodiments, the data processing unit 120 can also periodically, for example, check the remaining space of the internal FLASH every minute or hour. When the remaining space is lower than a preset threshold, the earliest data is cleaned up first according to the time sequence to achieve the purpose of cyclic overwrite storage. In this embodiment, the storage state of the internal FLASH can be initialized when the device is started, and the fault records and their timestamps are recorded. Then, a timed task is set, for example, to check the remaining storage space of the internal FLASH once every minute or hour, using a preset threshold (e.g., 10%) as the trigger condition. During each check, the total capacity and the used capacity of the internal FLASH are read, the remaining space is calculated, and if the remaining space is lower than the preset threshold, the overwrite mechanism is started.

[0050] In some embodiments, the circular overwrite in this application can be implemented in the following way: obtain a list of all records from the stored metadata, including timestamps and record lengths, sort the records in ascending order according to the timestamps, with the earliest record at the front, and select the first record from the sorted list for deletion until enough storage space is freed up.

[0051] In some embodiments, the data processing unit 120 is further configured to, upon receiving a first instruction signal sent by the host computer, send a first data message to the host computer via the second communication interface 130. The first data message carries file feature information of multiple record files for user preview. The file feature information includes file date, file size, and file name. It is understood that when the data processing unit 120 receives the first instruction signal sent by the host computer, it prepares the file feature information, extracts the file date, file size, and file name of all record files from the stored metadata, generates the file feature information, and then sends the first data message to the host computer via the second communication interface 130. The first data message contains the file feature information.

[0052] In some embodiments, the data processing unit 120 is further configured to, upon receiving a second instruction signal sent by a host computer, determine the corresponding target record file based on the file feature information carried in the second instruction signal, and send a second data message to the host computer through the second communication interface 130. The second data message carries the file content information of the target record file for the user to view.

[0053] In this context, it is understood that sending the first data message enables the host computer to communicate with the fault recording device via the USB interface, traverse the records to obtain information such as the date, size, and name of each record file, and form a visual interface for the user to preview the general content of each fault record file. Correspondingly, sending the second data message enables the specific file information to be obtained from the fault record storage device 100 and stored when the user clicks, and its content to be parsed for the user to view the specific content of the selected fault record file.

[0054] refer to Figure 2 , Figure 2 This is a schematic diagram of a fault record storage device 100 provided in an embodiment of the present invention, which includes an extended data interface. In some embodiments, the fault record storage device 100 further includes an extended data interface 140, which is connected to a data processing unit 120. The data processing unit 120 is also used to store multiple fault records to the external storage device based on a preset file storage format when it detects that an external storage device is connected to the extended data interface 140. The extended data interface 140 is used to connect to an external storage device (such as an SD card, USB flash drive, etc.), and its main purpose is to expand the storage capacity of the fault record storage device 100. When the internal storage space is insufficient, an external storage device can be used to store more fault records. The extended data interface 140 can be an SD card slot, a USB interface, or other types of storage device interfaces. It is understood that the data processing unit 120 will periodically detect the extended data interface 140 to determine whether an external storage device is connected. If an external storage device is detected, the data processing unit 120 will automatically identify and enable the external storage device, and the data processing unit 120 will store the fault records in the external storage device according to the preset file storage format (such as CSV file format) to ensure data consistency and readability. The external storage device can be an SD card, USB flash drive, or other similar device.

[0055] In some embodiments, the data processing unit 120, while storing data, also has data filtering capabilities. The data processing unit 120 can use a 16Mb capacity storage chip to record faults in the monitored equipment. It can flexibly overwrite and store records based on their length and frequency, ensuring that fault records are available for at least half a month. Furthermore, the required records can be queried and exported via host computer software, offering strong compatibility and eliminating the need for users to develop separate fault recording systems. When the internal FLASH storage space of the user's data processing unit 120 is insufficient, the data processing unit 120 can notify the user via indicator lights or a visual interface on the host computer, allowing the user to choose to connect an SD card (up to 32GB) to the expansion data interface 140 for storage expansion.

[0056] refer to Figure 3 , Figure 3 This is a schematic diagram of the structure of a fault record storage device 100 provided in an embodiment of the present invention, in which a battery unit 150 is provided. In some embodiments, when the fault record storage device 100 is used for the first time in this application, the fault record storage device 100 can be connected to a host computer such as a PC through a second communication interface 130. The fault record storage device 100 is initialized using an initialization program pre-deployed on the host computer, including functions such as the length of a single fault log entry, clock synchronization, and self-test for the fault record storage device 100. The host computer can be a computer device used to initialize and manage the fault record storage device 100. It runs a pre-deployed initialization program and communicates with the fault record storage device 100 through the second communication interface 130. The second communication interface 130 can be a USB interface, a serial interface (such as RS-232), or other standard communication interface. Through the second communication interface 130, the initialization program on the host computer can perform a series of configurations and tests on the fault record storage device 100 to ensure its normal operation.

[0057] In some embodiments, the fault recording storage device 100 has a built-in battery unit 150, which is connected to a power supply interface 160. The power supply interface 160 can be a 5V power supply interface 160. By connecting the battery unit 150 and the power supply interface 160, this application can use an external power supply. When the external power supply is connected, the battery unit 150 is charged and supplies power to the entire system. In addition, when the fault recording storage device 100 starts running, the 5V power supply interface 160 can be used to detect whether the fault recording storage device 100 has a 5V output capability. If the fault recording storage device 100 does not have a 5V output capability, the battery unit 150 can be fully charged using a matching charging cable. After that, the user selects a communication method supported by the device and connects the corresponding hardware lines to the first communication interface 110 of the corresponding communication protocol.

[0058] Understandably, battery unit 150 is the built-in power supply of fault recording storage device 100, used to ensure that the device can continue to operate and prevent data loss when external power is interrupted. When an external power supply is connected, battery unit 150 automatically charges and simultaneously powers the entire system. When the external power supply is disconnected, battery unit 150 continues to power the system, ensuring the continuous operation of fault recording storage device 100. Power supply interface 160 is used to connect to an external power source to provide power to fault recording storage device 100. Power supply interface 160 is typically a 5V power supply interface 160 to ensure compatibility with common power adapters. When fault recording storage device 100 starts running, it detects whether the device has a 5V output capability through the 5V power supply interface 160. If a 5V output capability is detected, battery unit 150 can be fully charged using the matching charging cable.

[0059] refer to Figure 4 , Figure 4 This is a schematic diagram of the structure of a fault record storage device 100 provided in an embodiment of the present invention, showing the specific communication interfaces. In some embodiments, the multiple first communication interfaces 110 with different communication protocols in this application may include communication interfaces such as CAN, RS485, RS232, and TTL, so that this application can support CAN, RS485, RS232, and TTL communication, thereby realizing a fault record storage device 100 with overlay storage and fault record retrieval. In addition, the second communication interface 130 is a USB communication interface 131, and the extended data interface 140 can be an external SD card interface 141. In actual use, the user only needs to input their fault record into the corresponding first communication interface 110, and the fault record storage device 100 in this application can record it, and can realize time-series storage and iteration. Furthermore, by using the fault record storage device 100 with a host computer, the original data message of the fault record can be exported through the host computer. The user can pre-set the message format of the data message model, thereby realizing the automatic parsing of the data message by the host computer.

[0060] In some embodiments, the process of exporting and viewing fault records may include the following: when the fault record storage device 100 is not connected to an external SD card, the fault record storage device 100 can be connected to a host computer via the USB communication interface 131, and the software module in the host computer can be used to query and read the data packets corresponding to the fault records; when the fault record storage device 100 is connected to an external SD card, the SD card can be removed, and the contents of the SD card can be exported using a card reader for analysis and viewing, or the data in the SD card can be transferred to the host computer, and the message parsing program can be configured through the software module in the host computer to achieve automatic parsing, thereby querying and reading the fault records.

[0061] refer to Figure 5 , Figure 5 This is a schematic diagram of a fault record storage device 100 connected to a host computer 200 according to an embodiment of the present invention; in a second aspect, this application provides a host computer 200 for connecting to the second communication interface 130 in the fault record storage device 100 as described in any of the first aspects, so as to obtain data packets corresponding to multiple fault records for user query.

[0062] In this embodiment, the host computer 200 is connected to the fault record storage device 100. Through multiple first communication interfaces 110 with different communication protocols provided in the fault record storage device 100, this embodiment can access various types of target monitoring devices to expand its applicability. By supporting multiple communication protocols, the device can be used flexibly in different application scenarios, exhibiting strong adaptability without requiring the development of a dedicated fault record device for each type of device. Furthermore, the data processing unit 120 executes a cyclic overwrite strategy. When the remaining storage space of the data processing unit 120 is less than a preset threshold, cyclic overwrite is performed based on the storage order of the fault records to ensure the retention of important fault records and avoid errors caused by faults. Insufficient storage space leading to the loss of important data can be effectively mitigated by improving storage space utilization, increasing storage efficiency, and reducing unnecessary hardware costs. Furthermore, by connecting to the host computer 200 via the second communication interface 130, the data packets corresponding to the fault records can be sent to the host computer 200 for user query and analysis. This allows users to conveniently view and manage fault records through the host computer 200 software, improving the efficiency of fault diagnosis and repair, thereby reducing the cost of fault records and enhancing the applicability of the fault record storage device 100. This facilitates the storage and retrieval of fault records for different monitoring devices, thereby reducing the workload of developers, shortening the development cycle, and lowering development costs.

[0063] refer to Figure 6 , Figure 6This is a schematic diagram of an optional structure of a host computer 200 provided in an embodiment of the present invention. In some embodiments, the host computer 200 includes a communication module 210, which is used to send a first instruction signal to the fault record storage device 100 to obtain a first data message sent by the fault record storage device 100. The first data message carries file feature information of multiple record files, including file date, file size, and file name. The communication module 210 communicates with the fault record storage device 100 through a second communication interface 130. Specifically, the communication is USB communication, which can include two forms: one is that the communication module 210 receives the message information transmitted from the fault record storage device 100 in real time and saves the message in the host computer 200 in real time through a MySQL database, so as to facilitate real-time monitoring and analysis by users in certain scenarios, such as on-the-go testing and analysis of new energy vehicles; the other is that the host computer 200 interacts with the fault record storage device 100 and can make corresponding export settings for the fault record storage device 100, thereby realizing functions such as time-based calibration and historical data export.

[0064] In some embodiments, the host computer 200 further includes a human-computer interaction module 220, which is connected to the communication module 210. The human-computer interaction module 220 is used to form a visual interface based on file feature information for users to preview. It can be understood that in the visual interface, users can view and delete historical data corresponding to fault records. In order to achieve this function, after the host computer 200 establishes communication with the fault record storage device 100 through the communication module 210, it will first send a first instruction signal to traverse the information stored in the fault record storage device 100, including the date, size, name, etc. of the files currently stored in the fault record storage device 100, and draw the obtained information in the form of a classic Windows interface on the user interface of the host computer 200.

[0065] In some embodiments, the communication module 210 is further configured to send a second instruction signal to the fault record storage device 100 in response to the user input signal obtained by the human-computer interaction module 220, so as to obtain the second data message sent by the fault record storage device 100. The second instruction signal carries the file feature information of the target record file corresponding to the user input signal, and the second data message carries the file content information of the target record file. It can be understood that after the visualization interface is formed for the user to preview, furthermore, when the user double-clicks a file and the human-computer interaction module 220 detects the user input signal obtained by the visualization interface, the host computer 200 can send the second instruction signal carrying the relevant information of this file to the fault record storage device 100 through the communication module 210. The fault record storage device 100 sends this file information back to the host computer 200. The host computer 200 summarizes the received information and saves it in a temporary file. The user can view the original message content in this file, view the time of each message, or the host computer 200 software can automatically parse the message into content information after setting the parsing format.

[0066] In some embodiments, the host computer 200 further includes a parsing module 230, which is connected to the communication module 210 and the human-computer interaction module 220. The parsing module 230 is used to parse the second data message based on a preset message format to display the file content information on a visual interface for user viewing. It can be understood that, since in this embodiment, the data messages can be saved in the form of "time + message + carriage return and line feed", and the content of the data messages conforms to the "Modbus-RTU-like (header, register address, content length, content, CRC check value)" communication format, the user only needs to preset the corresponding register and length and the content mapping data they represent in the parsing module 230 to realize the parsing module 230 to parse any content. In addition, the parsing module 230 can also realize the parsing of non-messages. For example, if the user exports a log file (such as if the user uses an SD card), the parsing module 230 can obtain the file data directly from the lower device to perform the same parsing process as the above message data.

[0067] In some embodiments, the software modules in the host computer 200 include a communication module 210, a human-computer interaction module 220, and a parsing module 230 that are interconnected. The communication module 210 is responsible for communicating with the fault record storage device 100, sending a first instruction signal to the fault record storage device 100 to request the acquisition of file feature information of the fault record, and receiving a first data packet and a second data packet sent by the fault record storage device 100, thereby ensuring reliable data transmission and processing communication protocols and data formats. The human-computer interaction module 220 is used to visualize the data and to receive user input signals. The parsing module 230 is responsible for parsing the data packets received from the fault record storage device 100, parsing the file feature information in the first data packet, extracting the file date, file size, and file name, parsing the file content information in the second data packet, and extracting the specific content of the fault record, so as to achieve the effect of parsing according to the preset message format, thereby ensuring the correctness and integrity of the data.

[0068] refer to Figure 7 , Figure 7 This is a schematic diagram of an optional structure of a fault record query system 300 provided in an embodiment of the present invention; in a third aspect, this application provides a fault record query system 300, including a fault record storage device 100 as described in any of the first aspects, and a host computer 200 as described in any of the second aspects. The host computer 200 can communicate with the fault record storage device 100 via a USB interface, and obtain information such as the date, size, and name of each record in the fault record storage device 100 by sending a first instruction signal to form a visual interface. Then, when the user clicks, the system obtains specific file information from the fault record device by sending a second instruction signal for storage, and parses its content for the user to preview.

[0069] Since the fault record query system 300 includes the aforementioned fault record storage device 100 and the aforementioned host computer 200, it can access various types of target monitoring devices through the multiple first communication interfaces 110 with different communication protocols provided in the fault record storage device 100, thereby expanding its applicability. By supporting multiple communication protocols, the device can be used flexibly in different application scenarios, exhibiting strong adaptability, without the need to develop a dedicated fault record device for each type of device. Furthermore, the data processing unit 120 executes a cyclic overwrite strategy. When the remaining storage space of the data processing unit 120 is less than a preset threshold, cyclic overwrite is performed based on the storage order of the fault records to ensure that important fault records are properly overwritten. The retention of fault records prevents the loss of important data due to insufficient storage space, effectively improving storage space utilization and efficiency while reducing unnecessary hardware costs. Furthermore, by connecting to the host computer 200 via the second communication interface 130, the data packets corresponding to the fault records can be sent to the host computer 200 for user query and analysis. This allows users to conveniently view and manage fault records through the host computer 200 software, improving the efficiency of fault diagnosis and repair, thereby reducing the cost of fault records and enhancing the applicability of the fault record storage device 100. This facilitates the storage and retrieval of fault records for different monitoring devices, reducing the workload of developers, shortening the development cycle, and lowering development costs.

[0070] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the present invention is not limited to the above embodiments. Within the scope of knowledge possessed by those skilled in the art, various changes can be made without departing from the spirit of the present invention.

Claims

1. A fault record storage device, characterized in that, include: It has multiple first communication interfaces with different communication protocols for accessing the target monitoring device, so as to obtain multiple fault records of the target monitoring device based on the corresponding communication protocol; A data processing unit, connected to the plurality of first communication interfaces, is used to store the plurality of fault records, and when the remaining storage space of the data processing unit is less than a preset threshold, it performs cyclic overwriting of the plurality of fault records based on the storage order of the plurality of fault records; The second communication interface is connected to the data processing unit and is used to access the host computer to send the data messages corresponding to the multiple fault records to the host computer for user query.

2. The fault record storage device according to claim 1, characterized in that, The data processing unit is further configured to, when a new fault record is obtained through the first communication interface and the remaining storage space after storing the multiple fault records is less than a preset threshold, obtain the storage order of the multiple fault records, and select the earliest stored fault record from the multiple fault records based on the storage order for deletion, so as to store the new fault record.

3. The fault record storage device according to claim 1, characterized in that, The data processing unit is further configured to store the multiple fault records into multiple record files according to the acquisition time corresponding to each fault record, and when the second communication interface receives the instruction signal sent by the host computer, send a data packet to the host computer through the second communication interface, wherein the data packet carries the file information of the multiple record files.

4. The fault record storage device according to claim 3, characterized in that, The data processing unit is also used for, Upon receiving the first instruction signal sent by the host computer, a first data message is sent to the host computer through the second communication interface. The first data message carries file feature information of the plurality of record files for user preview. The file feature information includes file date, file size, and file name.

5. The fault record storage device according to claim 4, characterized in that, The data processing unit is also used for, Upon receiving the second instruction signal sent by the host computer, the corresponding target record file is determined based on the file feature information carried in the second instruction signal. The second data message is then sent to the host computer through the second communication interface. The second data message carries the file content information of the target record file for the user to view.

6. The fault record storage device according to claim 1, characterized in that, The fault record storage device further includes an extended data interface, which is connected to the data processing unit. The data processing unit is also used to store the multiple fault records to the external storage device based on a preset file storage format when it detects that an external storage device is connected to the extended data interface.

7. A host computer, characterized in that, Used to connect to the second communication interface in the fault record storage device as described in any one of claims 1 to 6, so as to obtain data packets corresponding to the plurality of fault records for user query.

8. The host computer according to claim 7, characterized in that, The host computer includes a communication module, which is used to send a first instruction signal to the fault record storage device to obtain a first data message sent by the fault record storage device. The first data message carries file feature information of the plurality of record files, including file date, file size and file name.

9. The host computer according to claim 8, characterized in that, The host computer also includes a human-computer interaction module, which is connected to the communication module. The human-computer interaction module is used to generate a visual interface based on the file feature information for users to preview.

10. The host computer according to claim 9, characterized in that, The communication module is further configured to respond to the user input signal obtained by the human-computer interaction module and send a second instruction signal to the fault record storage device to obtain a second data message sent by the fault record storage device. The second instruction signal carries file feature information of the target record file corresponding to the user input signal, and the second data message carries file content information of the target record file.

11. The host computer according to claim 10, characterized in that, The host computer also includes a parsing module, which is connected to the communication module and the human-computer interaction module. The parsing module is used to parse the second data message based on a preset message format to display the file content information on the visualization interface for user viewing.

12. A fault record query system, characterized in that, It includes the fault record storage device as described in any one of claims 1 to 6, and the host computer as described in any one of claims 7 to 11.

Images