Remote acquisition method and system for fault information of charging equipment

Abstract

The invention belongs to the field of fault detection of charging equipment, and particularly relates to a remote acquisition method and system for fault information of the charging equipment. Comprising the steps that when the charging equipment breaks down, fault information of the charging equipment is recorded in a log file mode through the charging equipment, and the fault information is uploaded to a platform end; after the platform end receives the fault information of the charging equipment, acquiring a charging log list under the condition of determining that the charging equipment has response capability; the charging log list comprises log file records generated by the charging equipment; the single log file record comprises information for representing identity characteristics of the single charging equipment log file; if the log file record is successfully acquired, displaying the log file record in the list through the platform end so as to select a corresponding log file according to the log file record, and driving the charging equipment to upload the log file to the platform end according to a selection result; and if the log file is successfully acquired, generating a log record of equipment fault generation according to the acquired log file for equipment analysis.

Description

Technical Field

[0001] This invention belongs to the field of charging equipment fault detection, specifically relating to a method and system for remotely acquiring charging equipment fault information. Background Technology

[0002] Currently, when charging equipment malfunctions, it is typically necessary to locate, analyze, and diagnose the specific fault based on the charging log. This is because the charging log provides a precise fault timestamp (i.e., the exact time the fault occurred) and complete data records, which include data on the equipment's operating status (including charging power, temperature, and current-voltage curves). Technicians can then analyze the fault in the charging equipment based on the data provided in the charging log, thereby inferring the cause of the malfunction.

[0003] However, the current maintenance method for charging equipment typically involves the following steps: If the charging equipment stores fault messages or logs, maintenance personnel can go to the site to download the charging logs or messages, then provide them to technicians for analysis and develop solutions for on-site maintenance. If the charging equipment does not store the fault messages or logs, maintenance personnel need to reproduce the problem based on the equipment's operational description and then provide the data recorded during the reproduction to technicians for analysis; however, reproducing the problem takes a significant amount of time. Therefore, this method of relying on manual inspection of equipment fault information is clearly inefficient.

[0004] With the development of charging equipment operation and maintenance technology, methods for fault diagnosis through remote access to charging logs have been proposed. For example, the published text of Chinese invention patent application CN107390056A discloses a method and system for detecting charging piles. This method uses a platform server to analyze acquired fault code information (obtained from the charging pile) to generate fault information; then, based on this fault information, a log document is obtained. The required fault information can then be retrieved by querying the log document stored on the platform server. Summary of the Invention

[0005] The purpose of this invention is to provide a method and system for remotely acquiring charging equipment fault information, which solves the problem that the existing method of relying on manual acquisition of charging equipment fault information is inefficient, thus leading to low operation and maintenance efficiency of charging equipment.

[0006] To achieve the above objectives, the present invention provides a method for remotely acquiring charging equipment fault information. The method includes: when the charging equipment malfunctions, recording the charging equipment fault information in the form of a log file through the charging equipment itself, and uploading the fault information to the platform. When the platform receives a charging equipment fault information sent by the charging equipment, and determines that the charging equipment is responsive to the platform's call, it retrieves the charging log list generated by the charging equipment. The charging log list includes each log file record generated by the charging equipment. Each log file record contains information generated by the charging equipment that identifies the individual charging equipment log file. If the charging log list is successfully obtained, the log file records in the list are displayed on the platform so that the corresponding log file can be selected according to the log file records. Based on the selection result, the charging device is driven to send the selected log file to the platform. If the platform successfully retrieves the log file sent by the charging device, it generates a log record of the device failure based on the retrieved log file for device analysis.

[0007] Beneficial Effects: This invention provides a novel method for remotely acquiring charging equipment fault information. This method utilizes a platform within a charging station and the charging equipment in collaboration to remotely acquire charging equipment fault information. However, unlike conventional methods, this method does not directly drive the charging equipment to send its generated log file upon receiving fault information. Instead, it monitors the equipment's status in real time during charging, recording data from the charging process before the fault occurs. After the fault occurs, it aggregates various equipment data (the smallest unit constituting the charging log list, containing information identifying the log file's identity) into a single charging log (i.e., a log file). For multiple log entries generated during equipment use, the charging equipment can aggregate them into a charging log list. After obtaining this list through the platform, the desired log file can be selected from the displayed log file records, allowing targeted acquisition of the corresponding charging equipment's log file. Once the desired log file is obtained, the log record indicating the equipment fault can be obtained from it. The content displayed in this log record (i.e., equipment operation record information) details the specific circumstances of the charging equipment fault. Once the log records are obtained, maintenance personnel can make a preliminary judgment on equipment malfunctions or charging failures based on the equipment operation record information. This avoids the tedious process of reproducing charging failures or equipment malfunctions, thereby improving equipment maintenance efficiency and achieving efficient operation and maintenance of charging equipment. Furthermore, based on this, relevant log files can be selectively sent using the charging log list, thus avoiding the transmission of a large amount of redundant information that is not required, thereby further improving maintenance efficiency.

[0008] Furthermore, the information used to characterize the identity of a single charging device log file includes: the log file name, file size, and file modification time.

[0009] Furthermore, methods for determining whether a charging device is responsive to a call from the platform include: The platform sends instructions to the charging device to verify whether the charging device is responsive to the platform's calls. Subsequently, if the platform receives a receipt instruction from the charging device within a first set time period, it determines that the charging device is responsive to the platform's call. If the platform receives an erroneous instruction from the charging device within the first set time period, it determines that the instruction verification is incorrect and resends an instruction to the charging device through the platform to verify whether the charging device is responsive to the platform's call. If the platform does not receive any information within the first set time period, it determines that the instruction has timed out and resends an instruction to the charging device through the platform to verify whether the charging device is responsive to the platform's call.

[0010] Furthermore, if it is determined that the charging device has the ability to respond to the call of the platform, the method of obtaining the charging log list generated by the charging device includes: the platform sends an instruction to the charging device to obtain the charging log list, so as to drive the charging device to upload the charging log list. If the platform receives the charging log list within the second set time period, it is determined that the charging log list has been successfully obtained. If the platform receives an error message that is inconsistent with the charging log list or cannot be correctly parsed by the platform within the second set time period, it will be judged as a connection failure. If the platform does not receive the charging log list within the second set time period, it is determined that the connection has timed out.

[0011] Furthermore, the methods by which the driving charging device sends the selected log file to the platform include: The platform sends verification information containing the username and password to the charging device, which then verifies the user's identity based on the information. If the verification is successful, the charging device uploads the selected log file to the platform, along with information about the file's save path and file name. If the verification result indicates an incorrect username or password, or insufficient permissions, the device uploads the corresponding information to the platform.

[0012] Furthermore, the methods for uploading the selected log files to the platform include: using the SSH file transfer protocol to upload the selected log files as files or compressed packages.

[0013] Furthermore, the platform determines the success of retrieval of log files sent by the charging device through the following methods: When the log file is saved in a fixed path, if the platform receives the log file sent by the charging device, it determines that the charging log file sent by the charging device has been successfully obtained. When the log file is saved in a fixed path, if the platform receives a log file with a non-specified name from the charging device, it will determine that the charging log file sent by the charging device has failed to be retrieved. When the log file is saved in a non-fixed path, if the platform receives the log file sent by the charging device and receives the information corresponding to the log file, including the save path and file name, it is determined that the charging log file sent by the charging device has been successfully obtained. When the log file is saved in a non-fixed path, if the platform receives the log file sent by the charging device but does not receive the information containing the save path and file name corresponding to the log file, it will be determined that the log file sent by the charging device has failed to be retrieved. If the platform does not receive the log file sent by the charging device, it determines that the log file retrieval by the charging device has failed.

[0014] Furthermore, when the charging device is not charging, the charging device fault information includes: alarm information of the current device fault, fault time, and faulty pile data; When the charging device is in the charging state, the charging device fault information includes: the interaction process information between the current charging device and the BMS of the electric vehicle, the device action information of the charging device, fault codes, fault phenomena, and current or voltage information during the charging process.

[0015] The present invention also provides a remote acquisition system for charging equipment fault information, the system including a platform and a charging equipment; When a charging device malfunctions, it records the fault information in a log file and uploads the fault information to the platform. After receiving charging equipment fault information from the charging equipment, the platform determines that the charging equipment is responsive to the platform's call and then retrieves the charging log list generated by the charging equipment. The charging log list includes each log file record generated by the charging equipment. Each log file record contains information generated by the charging equipment that identifies the individual charging equipment log file. The platform is also used to display the log file records in the list when the charging log list is successfully obtained, so that the corresponding log file can be selected according to the log file record, and the charging device can be driven to send the selected log file to itself according to the selection result. The platform is also used to generate log records of device failures based on the successfully acquired log files sent by the charging device, for device analysis.

[0016] Furthermore, the information used to characterize the identity of a single charging device log file includes: the log file name, file size, and file modification time.

[0017] Furthermore, methods for determining whether a charging device is responsive to a call from the platform include: The platform sends instructions to the charging device to verify whether the charging device is responsive to the platform's calls. Subsequently, if the platform receives a receipt instruction from the charging device within a first set time period, it determines that the charging device is responsive to the platform's call. If the platform receives an erroneous instruction from the charging device within the first set time period, it determines that the instruction verification is incorrect and resends an instruction to the charging device through the platform to verify whether the charging device is responsive to the platform's call. If the platform does not receive any information within the first set time period, it determines that the instruction has timed out and resends an instruction to the charging device through the platform to verify whether the charging device is responsive to the platform's call.

[0018] Furthermore, if it is determined that the charging device has the ability to respond to the call of the platform, the method of obtaining the charging log list generated by the charging device includes: the platform sends an instruction to the charging device to obtain the charging log list, so as to drive the charging device to upload the charging log list. If the platform receives the charging log list within the second set time period, it is determined that the charging log list has been successfully obtained. If the platform receives an error message that is inconsistent with the charging log list or cannot be correctly parsed by the platform within the second set time period, it will be judged as a connection failure. If the platform does not receive the charging log list within the second set time period, it is determined that the connection has timed out.

[0019] Furthermore, the methods by which the driving charging device sends the selected log file to the platform include: The platform sends verification information containing the username and password to the charging device, which then verifies the user's identity based on the information. If the verification is successful, the charging device uploads the selected log file to the platform, along with information about the file's save path and file name. If the verification result indicates an incorrect username or password, or insufficient permissions, the device uploads the corresponding information to the platform.

[0020] Furthermore, the methods for uploading the selected log files to the platform include: using the SSH file transfer protocol to upload the selected log files as files or compressed packages.

[0021] Furthermore, the platform determines the success of retrieval of log files sent by the charging device through the following methods: When the log file is saved in a fixed path, if the platform receives the log file sent by the charging device, it determines that the charging log file sent by the charging device has been successfully obtained. When the log file is saved in a fixed path, if the platform receives a log file with a non-specified name from the charging device, it will determine that the charging log file sent by the charging device has failed to be retrieved. When the log file is saved in a non-fixed path, if the platform receives the log file sent by the charging device and receives the information corresponding to the log file, including the save path and file name, it is determined that the charging log file sent by the charging device has been successfully obtained. When the log file is saved in a non-fixed path, if the platform receives the log file sent by the charging device but does not receive the information containing the save path and file name corresponding to the log file, it will be determined that the log file sent by the charging device has failed to be retrieved. If the platform does not receive the log file sent by the charging device, it determines that the log file retrieval by the charging device has failed.

[0022] Furthermore, when the charging device is not charging, the charging device fault information includes: alarm information of the current device fault, fault time, and faulty pile data; When the charging device is in the charging state, the charging device fault information includes: the interaction process information between the current charging device and the BMS of the electric vehicle, the device action information of the charging device, fault codes, fault phenomena, and current or voltage information during the charging process.

[0023] The remote acquisition system for charging equipment fault information is based on the aforementioned method for remote acquisition of charging equipment fault information and has the same beneficial effects as the method. Attached Figure Description

[0024] Figure 1 This is a flowchart illustrating the method for remotely acquiring fault information of charging equipment according to the present invention. Figure 2 This is a system architecture diagram of the method for remotely acquiring fault information of charging equipment according to the present invention. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments.

[0026] Implementation Method for Remote Acquisition of Charging Equipment Fault Information This embodiment provides a technical solution for remotely acquiring charging equipment fault information. The main concept of this solution is as follows: After receiving equipment fault information from the charging equipment, the platform first obtains a list of charging logs from the faulty charging equipment (the contents of this list reflect the characteristic information of each log file generated by the charging equipment), and then selects the required log file from the list for acquisition. This file acquisition method is highly targeted, meaning it only drives the faulty charging equipment to send its charging logs, without requiring other normal equipment to send its own logs. Therefore, it satisfies the need for remote acquisition of fault information from faulty charging equipment while avoiding the unnecessary transmission of large amounts of information.

[0027] In this embodiment, the following is included: when the charging device malfunctions, the charging device itself records the charging device malfunction information in the form of a log file and sends the malfunction information to the platform. When the platform receives a charging equipment fault information sent by the charging equipment, and determines that the charging equipment is responsive to the platform's call, it retrieves the charging log list generated by the charging equipment. The charging log list includes each log file record generated by the charging equipment. Each log file record contains information generated by the charging equipment that identifies the individual charging equipment log file. If the charging log list is successfully obtained, the log file records in the list are displayed on the platform so that the corresponding log file can be selected based on the log file records. Based on the selection result, the charging device is driven to send the selected log file to the platform. If the platform successfully retrieves the log file sent by the charging device, it generates a log record of the device failure based on the retrieved log file for device analysis.

[0028] In one specific embodiment, firstly, storage rules, transmission protocol content, and corresponding storage hardware units related to charging records and charging messages are added to a general charging device communication device, and the charging record and charging message acquisition method of the charging device is set on the platform side (i.e. the platform side of the charging station) to establish an information transmission channel between the platform side and the charging device.

[0029] like Figure 1As shown, when a charging device malfunctions, the device itself (i.e., the charging device) records the fault information in a log file and uploads it to the platform. Upon receiving the fault information, the platform initiates a response to the charging device to test its responsiveness. Once the platform confirms the charging device's responsiveness, it requests a list of charging logs (generated by the charging device) from the charging device. This list contains records of each log file generated by the charging device. These records display the device's unique identifiers, serving as identifiers to differentiate between different log files; however, the log records themselves do not contain the actual information within the log files.

[0030] After requesting a charging log list from the charging device via the platform, if the charging log list is successfully obtained (i.e., the platform has indeed received the charging log list sent by the charging device), the platform displays the log file records in the list. Then, based on the identity feature information displayed in the log file records, the platform selects the corresponding log file and drives the charging device to send the selected log file to the platform. It is important to note that when selecting the corresponding log file based on the identity feature information displayed in the log file records, it is not limited to a single attribute of identity feature information. Instead, the platform operator (i.e., technical personnel) makes a flexible selection based on actual needs. For example, if the identity feature information includes file name and file modification time, then the log file can be selected either by file name or by file modification time, depending on the operator's actual needs.

[0031] If the platform successfully obtains the log file uploaded by the charging device, it generates a log record of the device malfunction based on the obtained log file for device analysis. In one specific embodiment, technicians can parse the log file uploaded by the charging device on the platform using the viewing function and display the obtained fault log record on the platform. This is mainly to convert the log file into information readable by technicians, facilitating device analysis. Device analysis here can be specifically defined as: making a preliminary judgment on device malfunctions or charging failure events based on the device operation record information. In other embodiments, log files can also be processed and analyzed in ways other than file parsing, such as inputting the obtained log file into a model with processing capabilities for machine recognition.

[0032] It should be noted that this solution is designed for information exchange between a single charging device and the platform. When multiple charging devices malfunction simultaneously, the process of this solution can be executed separately for each malfunctioning charging device.

[0033] In this embodiment, the information used to characterize the identity features of a single charging device log file includes: the log file name, file size, and file modification time.

[0034] Specifically, log files are presented in message format, containing information that identifies a single charging device log file, including the filename, file size, and file modification time. Other attributes, such as file identifiers and file sequence numbers, can also be set. When selecting a log file based on its records, the filename is typically the primary selection criterion, but selection based on other attributes is also supported.

[0035] In this embodiment, the methods for determining that the charging device is responsive to a call from the platform include: The platform sends instructions to the charging device to verify whether the charging device is responsive to the platform's calls. Subsequently, if the platform receives a receipt instruction from the charging device within a first set time period, it determines that the charging device is responsive to the platform's call. If the platform receives an erroneous instruction from the charging device within the first set time period, it determines that the instruction verification is incorrect and resends an instruction to the charging device through the platform to verify whether the charging device is responsive to the platform's call. If the platform does not receive any information within the first set time period, it determines that the instruction has timed out and resends an instruction to the charging device through the platform to verify whether the charging device is responsive to the platform's call.

[0036] refer to Figure 1 In one specific embodiment, the platform sends a response command to the charging device (i.e., a command used to verify whether the charging device is responsive to the platform's call). After the command is sent, a 1-minute wait is performed (i.e., the first set time). After this 1-minute wait, the following three response scenarios can be assessed and appropriate actions taken: 1) If the platform receives a "False" response (i.e., an error command) from the charging device within 1 minute, it determines that the command verification is incorrect and resends a response command to the charging device to initiate a call. 2) If the platform does not receive any information within 1 minute, it will determine that the instruction has timed out and resend the response instruction to the charging device to call it; 3) If the platform receives a "received" instruction from the charging device within 1 minute, it is determined that the charging device is responsive to the platform's call, and there is no need to call the device again.

[0037] The above-described process of sending response commands to the charging device from the platform and receiving replies aims to test whether the charging device has the ability to respond to the platform. In reality, scenarios 1) and 2) both indicate that the charging device does not have the ability to respond; only scenario 3) demonstrates that the charging device does have the ability to respond.

[0038] In this embodiment, when it is determined that the charging device has the ability to respond to the call of the platform, the method of obtaining the charging log list generated by the charging device includes: the platform sends an instruction to the charging device to obtain the charging log list, so as to drive the charging device to upload the charging log list. If the platform receives the charging log list within the second set time period, it is determined that the charging log list has been successfully obtained. If the platform receives a charging log list that is inconsistent with the agreed format and content of the charging device or cannot be correctly parsed by the platform within the second set time period, the connection is deemed to have failed. If the platform does not receive the charging log list within the second set time period, it is determined that the connection has timed out.

[0039] Specifically, based on the determination that the charging device is responsive to the platform's call, a charging log list (generated by the charging device itself) is further obtained. In a specific embodiment, this list is obtained by sending a log list retrieval command (i.e., a command for retrieving the charging log list) from the platform to the charging device. After the command is sent, a 30-second wait (i.e., the second set time) is performed, and the following three response scenarios are considered: a) If the platform receives the charging log list from the charging device within these 30 seconds, it is determined that the charging log list has been successfully obtained. b) If the platform receives an error message from the charging device within these 30 seconds, it will be considered a connection failure. It should be noted that the error message is defined as follows: The charging log list information is transmitted in the charging device's reply information in a pre-defined format. Information that is inconsistent with the pre-defined format or that the platform cannot parse correctly will be defined as an error message. c) If the platform does not receive the charging log list from the charging device within 30 seconds, it is determined that the connection has timed out.

[0040] In this embodiment, to ensure the security of log file upload, user identity verification is required before the driving charging device uploads the selected log file to the platform. Based on this, the methods by which the driving charging device uploads the selected log file to the platform include: The platform sends verification information containing the username and password to the charging device, which then verifies the user's identity based on the information. If the verification is successful, the charging device uploads the selected log file to the platform, along with information about the file's save path and file name. If the verification result indicates an incorrect username or password, or insufficient permissions, the device uploads the corresponding information to the platform.

[0041] Specifically, the user identity verification process is as follows: First, the platform sends verification information (including username and password) to the charging device, which then verifies the user's identity based on this information. The verification results and their corresponding processing operations include the following three types: I) The verification result is correct; The verification result indicates that the username and password provided by the device are correct, proving that the charging device is qualified to upload files. The corresponding processing operation for this verification result is: to upload the selected log file to the platform through the charging device, and at the same time, to upload information including the file save path and file name of the log file to the platform.

[0042] II) The verification result indicates that the username or password is incorrect; This verification result indicates that at least one of the username and password provided by the device is incorrect, proving that the charging device is not qualified to upload files. The corresponding processing operation for this verification result is to send the username or password error information to the platform through the charging device, so that the platform's technical personnel are aware of the current problem. For example, when the charging device sends "Incorrect Name!" to the platform, it means that the username verification has failed; when the charging device sends "Incorrect Password!" to the platform, it means that the password verification has failed.

[0043] III) The verification result is "No permission"; This verification result is unrelated to the correctness of the username and password verification; rather, it indicates that the platform does not have permission to access the log file. The corresponding action for this verification result is to send a message indicating that the charging device lacks permission to the platform, so that the platform's technical personnel are aware of the current problem.

[0044] In this embodiment, the platform determines the success of acquiring the log file sent by the charging device by means of: When the log file is saved in a fixed path, if the platform receives the log file sent by the charging device, it is determined that the charging log file sent by the charging device has been successfully obtained; when the log file is saved in a fixed path, if the platform receives the log file sent by the charging device with a name other than the specified name, it is determined that the charging log file sent by the charging device has failed to be obtained. When the log file is saved in a non-fixed path, if the platform receives the log file sent by the charging device and receives the information corresponding to the log file, including the save path and file name, it is determined that the charging log file sent by the charging device has been successfully obtained. When the log file is saved in a non-fixed path, if the platform receives the log file sent by the charging device but does not receive the information containing the save path and file name corresponding to the log file, it will be determined that the log file sent by the charging device has failed to be retrieved. If the platform does not receive the log file sent by the charging device, it determines that the log file retrieval by the charging device has failed.

[0045] Specifically, when determining whether the platform successfully retrieves the log file sent by the charging device, this solution first needs to consider whether the log file's save path is a fixed path (a fixed save path means the save path is known, i.e., a preset fixed path), and then substitute the judgment condition into this case for judgment. This judgment condition actually includes the following two conditions: Condition 1: The platform receives the log file sent by the charging device; Condition 2: The platform receives information corresponding to the log file, including the file save path and file name.

[0046] Based on conditions one and two, the following judgment logic is determined: A) When the log file is saved in a fixed path, as long as the platform receives the log file with the specified name sent by the charging device, it can directly determine that the charging log file sent by the charging device has been successfully obtained. Since the fixed path is a known path, it does not affect the judgment regardless of whether the platform receives the save path. Subsequent saving can be done according to the known fixed path.

[0047] B) When the log file is saved in a fixed path, if the platform receives a log file with a non-specified name from the charging device, and the selected file in the log list does not match the actual file name, the platform will determine that the log file sent by the charging device has failed to be retrieved.

[0048] C) When the log file is saved in a non-fixed path, if the platform receives the log file sent by the charging device and receives the information corresponding to the log file, including the save path and file name, it is determined that the charging log file sent by the charging device has been successfully obtained; subsequently, the file is saved and processed according to the received save path and file name.

[0049] D) When the log file is saved in a non-fixed path, if the platform receives the log file sent by the charging device but does not receive the information containing the save path and file name corresponding to the log file, it is determined that the log file sent by the charging device has failed to be retrieved.

[0050] E) If the platform does not receive the log file sent by the charging device, it determines that the log file sent by the charging device has failed to be obtained.

[0051] Since non-fixed paths are essentially unknown paths, if the platform only receives the log file but not the corresponding save path and filename information, problems may arise in the subsequent saving and processing of the log file due to the missing save path and filename. Therefore, for non-fixed paths, both conditions one and two must be met to ensure the integrity of the log file information and avoid problems in subsequent saving and processing.

[0052] In this embodiment, the method of uploading the selected log file to the platform includes: using the SSH file transfer protocol to upload the selected log file in the form of a file or a compressed package.

[0053] Specifically, when uploading log files to the platform using the SSH file transfer protocol, the upload can be in either file or compressed format, depending on the actual upload requirements. For example, if the log file contains too much information or has a large data volume, it can be uploaded as a compressed file and then unpacked on the platform.

[0054] The fault conditions of charging equipment in non-charging and charging states are completely different. Faults in the non-charging state typically indicate a problem with the charging equipment itself, while faults in the charging state typically indicate potential problems that may occur during the charging interaction between the charging equipment and the electric vehicle. Therefore, in this embodiment, the fault information of the charging equipment in the non-charging and charging states contains different content and represents different meanings.

[0055] When the charging device is not charging, the charging device fault information includes: the current device fault alarm information, the fault time, and the faulty charging pile data; When the charging equipment is charging, the charging equipment fault information includes: the interaction process information between the current charging equipment and the BMS of the electric vehicle, the action information of the charging equipment components, fault codes and fault phenomena (such as charging module failure, charging voltage overvoltage and BMS communication failure), and may also include current or voltage information during the charging process.

[0056] Implementation of a Remote Acquisition System for Charging Equipment Fault Information This embodiment provides a technical solution for a remote acquisition system for charging equipment fault information, which includes a platform and a charging equipment. When a charging device malfunctions, it records the fault information in a log file and sends the fault information to the platform. After receiving charging equipment fault information from the charging equipment, the platform determines that the charging equipment is responsive to the platform's call and then retrieves the charging log list generated by the charging equipment. The charging log list includes each log file record generated by the charging equipment. Each log file record contains information generated by the charging equipment that identifies the individual charging equipment log file. The platform is also used to display the log file records in the list when the charging log list is successfully obtained, so that the corresponding log file can be selected according to the log file record, and the charging device can be driven to send the selected log file to itself according to the selection result. The platform is also used to generate log records of device failures based on the successfully acquired log files sent by the charging device, for device analysis.

[0057] In a specific embodiment, the architecture of a remote acquisition system for charging device fault information is as follows: Figure 2 As shown. The platform includes a display unit, a storage unit 1, and a processor; the processor is equipped with a remote acquisition method for charging device fault information, as described in this embodiment, and the processor can interact with the storage unit 1. The storage unit 1 also establishes communication (including wireless and wired communication) with the charging pile (i.e., the charging device, or the device end), and is used to receive and store information sent from the charging pile. In this embodiment, the device end includes a processing unit, a communication unit, and a storage unit 2; the processing unit and communication unit can interact with the storage unit 2. The processing unit and communication unit are used to receive the original fault information, process it, and then send it to the storage unit 1 on the platform for storage. The processing unit and communication unit are also used to receive the original fault information, process it, and then send it to the storage unit 2 on the device end for storage.

[0058] When a charging station malfunctions, the original fault information is received by the charging station's processing and communication units, processed, and then sent to the platform's storage unit 1 for storage. The processing method involves converting the original fault information into charging equipment fault information (which is recorded in a log file).

[0059] The charging equipment fault information is sent to the processor through the storage unit 1. The computer software program running on the processor (i.e., the program written according to the remote acquisition method of charging equipment fault information) processes the charging equipment fault information to obtain the log record of the equipment fault for equipment analysis.

[0060] It should be understood that the above-described specific embodiments of the present invention are merely illustrative or explanatory of the principles of the present invention, and do not constitute a limitation thereof.

Claims

1. A method for remotely acquiring fault information of charging equipment, characterized in that, include: When a charging device malfunctions, the charging device itself records the malfunction information in the form of a log file and sends the malfunction information to the platform. When the platform receives a charging equipment fault information sent by the charging equipment, and determines that the charging equipment is responsive to the platform's call, it retrieves the charging log list generated by the charging equipment. The charging log list includes each log file record generated by the charging equipment. Each log file record contains information generated by the charging equipment that identifies the individual charging equipment log file. If the charging log list is successfully obtained, the log file records in the list are displayed on the platform so that the corresponding log file can be selected according to the log file records. Based on the selection result, the charging device is driven to send the selected log file to the platform. If the platform successfully retrieves the log file sent by the charging device, it generates a log record of the device failure based on the retrieved log file for device analysis.

2. The method for remotely acquiring charging equipment fault information according to claim 1, characterized in that, Information used to identify the identity of a single charging device log file includes: the log file name, file size, and file modification time.

3. The method for remotely acquiring charging equipment fault information according to claim 1, characterized in that, Methods to determine whether a charging device is responsive to a call from the platform include: The platform sends instructions to the charging device to verify whether the charging device is responsive to the platform's calls. Subsequently, if the platform receives a receipt instruction from the charging device within a first set time period, it determines that the charging device is responsive to the platform's call. If the platform receives an erroneous instruction from the charging device within the first set time period, it determines that the instruction verification is incorrect and resends an instruction to the charging device through the platform to verify whether the charging device is responsive to the platform's call. If the platform does not receive any information within the first set time period, it determines that the instruction has timed out and resends an instruction to the charging device through the platform to verify whether the charging device is responsive to the platform's call.

4. The method for remotely acquiring charging equipment fault information according to claim 1, characterized in that, If it is determined that the charging device is responsive to the platform's call, the methods for obtaining the charging log list generated by the charging device include: the platform sends an instruction to the charging device to obtain the charging log list, thereby driving the charging device to upload the charging log list. If the platform receives the charging log list within the second set time period, it is determined that the charging log list has been successfully obtained. If the platform receives an error message that is inconsistent with the charging log list or cannot be correctly parsed by the platform within the second set time period, it will be judged as a connection failure. If the platform does not receive the charging log list within the second set time period, it is determined that the connection has timed out.

5. The method for remotely acquiring charging equipment fault information according to any one of claims 1-3, characterized in that, The methods by which the driving charging device sends the selected log file to the platform include: The platform sends verification information containing the username and password to the charging device, which then verifies the user's identity based on the information. If the verification is successful, the charging device uploads the selected log file to the platform, along with information about the file's save path and file name. If the verification result indicates an incorrect username or password, or insufficient permissions, the device uploads the corresponding information to the platform.

6. The method for remotely acquiring charging equipment fault information according to claim 5, characterized in that, The methods for uploading the selected log file to the platform include: using the SSH file transfer protocol to upload the selected log file as a file or compressed package.

7. The method for remotely acquiring charging equipment fault information according to claim 5, characterized in that, The platform determines the success of receiving log files sent by the charging device through the following methods: When the log file is saved in a fixed path, if the platform receives a log file with a specified name sent by the charging device, it determines that the charging log file sent by the charging device has been successfully obtained. When the log file is saved in a fixed path, if the platform receives a log file with a non-specified name from the charging device, it will determine that the charging log file sent by the charging device has failed to be retrieved. When the log file is saved in a non-fixed path, if the platform receives the log file sent by the charging device and receives the information corresponding to the log file, including the save path and file name, it is determined that the charging log file sent by the charging device has been successfully obtained. When the log file is saved in a non-fixed path, if the platform receives the log file sent by the charging device but does not receive the information containing the save path and file name corresponding to the log file, it will be determined that the log file sent by the charging device has failed to be retrieved. If the platform does not receive the log file sent by the charging device, it determines that the log file retrieval by the charging device has failed.

8. The method for remotely acquiring charging equipment fault information according to any one of claims 1-3, characterized in that, When the charging device is not charging, the charging device fault information includes: alarm information of the current device fault, fault time, and fault pile data; When the charging device is in the charging state, the charging device fault information includes: the interaction process information between the current charging device and the BMS of the electric vehicle, the device action information of the charging device, fault codes, fault phenomena, and current or voltage information during the charging process.

9. A remote acquisition system for charging equipment fault information, characterized in that, This includes the platform and charging equipment; When a charging device malfunctions, it records the fault information in a log file and uploads the fault information to the platform. After receiving charging equipment fault information from the charging equipment, the platform determines that the charging equipment is responsive to the platform's call and then retrieves the charging log list generated by the charging equipment. The charging log list includes each log file record generated by the charging equipment. Each log file record contains information generated by the charging equipment that identifies the individual charging equipment log file. The platform is also used to display the log file records in the list when the charging log list is successfully obtained, so that the corresponding log file can be selected according to the log file record, and the charging device can be driven to send the selected log file to itself according to the selection result. The platform is also used to generate log records of device failures based on the successfully acquired log files sent by the charging device, for device analysis.

10. The remote acquisition system for charging equipment fault information according to claim 9, characterized in that, Information used to identify the identity of a single charging device log file includes: the log file name, file size, and file modification time.

11. The remote acquisition system for charging equipment fault information according to claim 9, characterized in that, Methods to determine whether a charging device is responsive to a call from the platform include: The platform sends instructions to the charging device to verify whether the charging device is responsive to the platform's calls. Subsequently, if the platform receives a receipt instruction from the charging device within a first set time period, it determines that the charging device is responsive to the platform's call. If the platform receives an erroneous instruction from the charging device within the first set time period, it determines that the instruction verification is incorrect and resends an instruction to the charging device through the platform to verify whether the charging device is responsive to the platform's call. If the platform does not receive any information within the first set time period, it determines that the instruction has timed out and resends an instruction to the charging device through the platform to verify whether the charging device is responsive to the platform's call.

12. The remote acquisition system for charging equipment fault information according to claim 9, characterized in that, If it is determined that the charging device is responsive to the platform's call, the methods for obtaining the charging log list generated by the charging device include: the platform sends an instruction to the charging device to obtain the charging log list, thereby driving the charging device to upload the charging log list. If the platform receives the charging log list within the second set time period, it is determined that the charging log list has been successfully obtained. If the platform receives an error message that is inconsistent with the charging log list or cannot be correctly parsed by the platform within the second set time period, it will be judged as a connection failure. If the platform does not receive the charging log list within the second set time period, it is determined that the connection has timed out.

13. The remote acquisition system for charging equipment fault information according to any one of claims 9-11, characterized in that, The methods by which the driving charging device sends the selected log file to the platform include: The platform sends verification information containing the username and password to the charging device, which then verifies the user's identity based on the information. If the verification is successful, the charging device uploads the selected log file to the platform, along with information about the file's save path and file name. If the verification result indicates an incorrect username or password, or insufficient permissions, the device uploads the corresponding information to the platform.

14. The remote acquisition system for charging equipment fault information according to claim 13, characterized in that, The methods for uploading the selected log files to the platform include: using the SSH file transfer protocol to upload the selected log files as files or compressed packages.

15. The remote acquisition system for charging equipment fault information according to claim 13, characterized in that, The platform determines the success of receiving log files sent by the charging device through the following methods: When the log file is saved in a fixed path, if the platform receives the log file sent by the charging device and receives the file name information, it determines that the charging log file sent by the charging device has been successfully obtained. When the log file is saved in a fixed path, if the platform receives a log file with a non-specified name from the charging device, it will determine that the charging log file sent by the charging device has failed to be retrieved. When the log file is saved in a non-fixed path, if the platform receives the log file sent by the charging device and receives the information corresponding to the log file, including the save path and file name, it is determined that the charging log file sent by the charging device has been successfully obtained. When the log file is saved in a non-fixed path, if the platform receives the log file sent by the charging device but does not receive the corresponding information including the save path and file name, it is determined that the log file sent by the charging device has failed to be retrieved; if the platform does not receive the log file sent by the charging device, it is determined that the log file sent by the charging device has failed to be retrieved.

16. The remote acquisition system for charging equipment fault information according to any one of claims 9-11, characterized in that, When the charging device is not charging, the charging device fault information includes: alarm information of the current device fault, fault time, and fault pile data; When the charging device is in the charging state, the charging device fault information includes: the interaction process information between the current charging device and the BMS of the electric vehicle, the device action information of the charging device, fault codes, fault phenomena, and current or voltage information during the charging process.

Images