Method for detecting failure of range extender system and related device

Abstract

The invention relates to a method for detecting a fault of a range extender system and a related device. The invention discloses a method for detecting a fault of a range extender system. The method comprises the following steps: receiving report information from a subsystem of the range extender system; determining that the reported information is fault multi-packet information; storing a data packet in the fault multi-packet information; and in response to successfully storing all data packets in the fault multi-packet information, executing the following operations: analyzing each data packet in the stored fault multi-packet information to obtain a fault signal value of the fault signal, and performing first coding on the fault signal whose fault signal value indicates that the fault signal has a fault so as to obtain a fault signal coding value of the fault signal, and circularly sending the fault signal coding value.

Description

Technical Field

[0001] The present disclosure relates to the technical field of engineering machinery, and more particularly, to a method for detecting a fault in a range extender system and an associated range extender controller, a range extender system including the range extender controller, a non-transitory storage medium, and a computer program product. Background Art

[0002] Extended-range electric vehicles are popular equipment in the field of construction machinery. Extended-range electric vehicles overcome the shortcoming of traditional electric vehicles' short driving range by adding a range extender. Summary of the invention

[0003] A brief overview of the disclosure is given below in order to provide a basic understanding of some aspects of the disclosure. However, it should be understood that this overview is not an exhaustive overview of the disclosure. It is not intended to identify the key or important parts of the disclosure, nor is it intended to limit the scope of the disclosure. Its purpose is simply to give some concepts of the disclosure in a simplified form as a prelude to a more detailed description given later.

[0004] According to a first aspect of the present disclosure, a method for detecting a fault in a range extender system is provided, the method comprising: receiving reporting information from a subsystem of the range extender system; determining that the reporting information is a fault multi-packet information; storing a data packet in the fault multi-packet information; and in response to successfully storing all data packets in the fault multi-packet information, performing the following operations. The operations include: parsing each data packet in the stored fault multi-packet information to obtain a fault signal value of a fault signal; first encoding a fault signal whose fault signal value indicates a fault to obtain a fault signal code value of the fault signal; and cyclically sending the fault signal code value.

[0005] According to a second aspect of the present disclosure, a range extender controller is provided, comprising: a processor; and a memory storing computer executable instructions, which, when executed by the processor, causes the processor to execute the method for detecting a fault in a range extender system according to the first aspect of the present disclosure.

[0006] According to a third aspect of the present disclosure, a non-volatile storage medium having computer executable instructions stored thereon is provided. When the computer executable instructions are executed by a processor, the processor executes the method for detecting a fault of a range extender system according to the first aspect of the present disclosure.

[0007] According to a fourth aspect of the present disclosure, a computer program product is provided. The computer program product includes instructions. When the instructions are executed by a processor, the method for detecting a fault of a range extender system according to the first aspect of the present disclosure is implemented.

[0008] According to a fifth aspect of the present disclosure, a range extender system is provided, comprising: a range extender controller coupled to a bus; a display coupled to the bus; at least one of an engine controller, a vehicle controller, and a generator controller, which is coupled to the bus and configured to send reporting information to the bus. The range extender controller is configured to: receive reporting information; determine that the reporting information is fault multi-packet information; store data packets in the fault multi-packet information; and perform the following operations in response to successfully storing all data packets in the fault multi-packet information. The operations include: parsing each data packet in the stored fault multi-packet information to obtain a fault signal value of a fault signal; first encoding a fault signal whose fault signal value indicates a fault to obtain a fault signal code value of the fault signal; and cyclically sending the fault signal code value to the bus. The display is configured to receive and display the fault signal code value from the bus. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The foregoing and other features and advantages of the present disclosure will become apparent from the following description of the embodiments of the present disclosure in conjunction with the accompanying drawings. The accompanying drawings are incorporated herein and form a part of the specification, and are further used to explain the principles of the present disclosure and enable those skilled in the art to make and use the present disclosure. Among them:

[0010] Figure 1 A flow chart showing a method for detecting a fault in a range extender system according to some embodiments of the present disclosure is shown;

[0011] Figure 2 A flow chart showing a non-limiting example process in which a method for detecting a fault of a range extender system according to some embodiments of the present disclosure is applied;

[0012] Figure 3 A schematic block diagram of a range extender controller according to some embodiments of the present disclosure is shown;

[0013] Figure 4 A schematic block diagram of a range extender system according to some embodiments of the present disclosure is shown;

[0014] Figure 5 A schematic block diagram of a computer system 500 is shown upon which embodiments of the present disclosure may be implemented.

[0015] Note that in the embodiments described below, sometimes the same reference numerals are used in common between different drawings to represent the same parts or parts with the same functions, and their repeated descriptions are omitted. In some cases, similar numbers and letters are used to represent similar items, so once an item is defined in one drawing, it does not need to be further discussed in subsequent drawings.

[0016] For ease of understanding, the position, size, range, etc. of each structure shown in the drawings and the like may not represent the actual position, size, range, etc. Therefore, the present disclosure is not limited to the position, size, range, etc. disclosed in the drawings and the like. DETAILED DESCRIPTION

[0017] Various exemplary embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. It should be noted that unless otherwise specifically stated, the relative arrangement of components and steps, numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present disclosure.

[0018] The following description of at least one exemplary embodiment is in fact merely illustrative and is in no way intended to limit the present disclosure and its application or use. That is, the structures and methods herein are shown in an exemplary manner to illustrate different embodiments of the structures and methods in the present disclosure. However, those skilled in the art will appreciate that they merely illustrate exemplary ways of the present disclosure that can be implemented, rather than exhaustive ways. In addition, the drawings need not be drawn to scale, and some features may be enlarged to illustrate the details of specific components.

[0019] In addition, technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the technologies, methods, and equipment should be considered as part of the specification.

[0020] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0021] Since the range extender system frequently starts and stops and has a harsh working environment, it is very prone to failures and the number of failures is high.

[0022] In the related technology, the J1939 data transmission protocol based on the Controller Area Network (CAN) is commonly used. The data volume of some fault message information of the range extender system can reach tens of bytes. These messages with a length greater than the preset number of bytes cannot be loaded in a single CAN data frame, so they are usually transmitted using the J1939 multi-packet data transmission protocol based on the CAN bus. This kind of fault message information belongs to multi-packet messages or multi-packet information, which includes multiple data packets.

[0023] At present, the multi-packet message parsing method corresponding to the J1939 multi-packet data transmission protocol can parse the received multi-packet messages. However, when the system actually includes only one fault or no fault, or when the fault multi-packet information is lost, this parsing method can easily parse out wrong fault information, causing the range extender system to report an error but may not be able to eliminate the real fault in time, reducing the safety and reliability of the range extender system. For example, when there is no fault signal in the message information, the parsing method for processing fault multi-packet information continues to be applied to it. If a certain section of the code in the message information happens to be the same as a section of the fault code preset in the multi-packet message parsing method, then it will be mistakenly parsed that the message information includes a fault signal.

[0024] In addition, in the related art, when the subsystems of the range extender system trigger multiple faults, a single CAN communication ID is usually used to send fault signals. However, the range extender system is a small-scale real-time communication system, and high-speed CAN is generally used for communication in the range extender system, which means that the range extender system sends fault signals at a high frequency, resulting in the human eye being unable to observe the fast-refreshing fault signals displayed on the display, which is not conducive to the operator's efficient discovery and handling of faults, and further reduces the safety and reliability of the range extender system.

[0025] In order to solve one or more of the above problems, the present disclosure provides a method for detecting a fault in a range extender system. Below, the method for detecting a fault in a range extender system according to various embodiments of the present disclosure will be described in detail in conjunction with the accompanying drawings. It can be understood that the actual method for detecting a fault in a range extender system may also include other steps, but in order to avoid blurring the main points of the present disclosure, these other steps are not discussed herein and are not shown in the accompanying drawings.

[0026] In addition, the terms "first", "second" and the like may also be used herein for reference purposes only, and thus are not intended to be limiting. For example, the terms "first", "second" and other such numerical terms referring to structures or elements do not imply a sequence or order unless the context clearly indicates otherwise.

[0027] Figure 1 A flow chart of a method 100 for detecting a fault in a range extender system according to some embodiments of the present disclosure is shown. Figure 1 As shown, the method 100 includes steps S102 to S108.

[0028] In step S102, reporting information from a subsystem of the range extender system is received.

[0029] In some embodiments, the subsystem of the range extender system includes at least one of an engine controller (Engine Control Unit, ECU), a range extender controller (Range extender Control Unit, RCU), a vehicle control unit (VCU), and a generator controller (Generator Controller Unit, GCU).

[0030] At step S104, it is determined that the reported information is fault multi-packet information. Here, the fault multi-packet information may refer to message information that may indicate a fault and includes multiple data packets.

[0031] In some examples, whether the reported information is fault multi-packet information may be determined based on the CAN communication address. For example, the CAN communication address may include one or more digits for indicating whether it is a fault.

[0032] In step S106, the data packets in the faulty multi-packet information are stored.

[0033] At step S108, in response to successfully storing all data packets in the faulty multi-packet information, an operation is performed.

[0034] Here, the operation performed in step S108 may include parsing each data packet in the stored fault multi-packet information to obtain the fault signal value of the fault signal. In some embodiments, each data packet may be parsed based on a preset transmission protocol (such as the aforementioned J1939 multi-packet data transmission protocol, etc.) to obtain a diagnostic trouble code (DTC) of the fault signal as the fault signal value of the fault signal.

[0035] The operation performed in step S108 may also include: first encoding the fault signal whose fault signal value indicates a fault to obtain the fault signal code value of the fault signal; and cyclically sending the fault signal code value. In some embodiments, the first encoding may include encoding the fault signal according to the value specified in the communication protocol. For example, the DTC in the aforementioned example may correspond one-to-one to the fault signal specified in the communication protocol. In some examples, the fault signal code value may be between 0 and (10 k -1), k is an integer greater than zero, for example, k>1. Exemplarily, k may be equal to 3.

[0036] In some embodiments, a fault signal whose fault signal value indicates no fault may not be encoded. Therefore, such a fault signal has no fault signal encoding value and does not need to be sent, which can reduce the amount of data transmission and save energy. In other embodiments, a fault signal whose fault signal value indicates no fault may be encoded but the fault encoding value of the fault signal is not sent, so as to reduce the amount of data transmission and save energy. In some examples, it can be set so that when the fault signal value of the fault signal is zero, it indicates no fault, and when the fault signal value of the fault signal is not zero (for example, one), it indicates a fault.

[0037] Therefore, when collecting the reported information of each subsystem, method 100 will determine whether it is a multi-packet fault information, and if it is a multi-packet fault information, it will only be parsed when all its data packets are successfully stored. Through such a storage and parsing strategy, the problem of mis-parsing and missed parsing caused by packet loss of multi-packet fault information can be prevented, and the accuracy of subsequent fault detection can be guaranteed. In addition, by cyclically sending the fault signal coding value, the fault signal coding value can be continuously displayed on the display without changing the display structure, which is convenient for operators to obtain fault-related information, improve fault detection efficiency, and improve the safety and reliability of the range extender system.

[0038] In some embodiments, the operation performed in step S108 includes: parsing each data packet in the stored fault multi-packet information to obtain corresponding fault signal values ​​of multiple fault signals, encoding each fault signal whose fault signal value indicates a fault in the multiple fault signals to obtain the fault signal code value of the fault signal, and cyclically sending the fault signal code value. In some such embodiments, when multiple fault signal code values ​​are obtained, multiple fault signal code values ​​can be cyclically sent in the following manner: in response to the current fault signal code value to be sent being different from the last fault signal code value that has been sent, determining whether the continuous sending time of the last fault signal code value reaches the preset continuous sending time, and: in response to the continuous sending time of the last fault signal code value not reaching the preset continuous sending time, continue to send the last fault signal code value; or in response to the continuous sending time of the last fault signal code value reaching the preset continuous sending time, send the current fault signal code value. In some examples, the preset continuous sending time can be 0.5 seconds to 2 seconds, for example, 1 second.

[0039] As a non-limiting example, the ECU of the range extender system may have multiple faults at the same time (for example, the engine temperature is too high, the engine speed is too high, etc.), and the reported fault multi-packet information may include multiple fault signals indicating that a fault has occurred, so that multiple fault signal code values ​​can be obtained after parsing the fault multi-packet information. In the case of high-speed CAN communication, in order to ensure that each fault signal code value is displayed on the display for a long enough time to be visually distinguished by the operator, these fault signal code values ​​can be cyclically sent on the CAN bus while each fault signal is continuously sent for 1 second when it is the turn to be sent as the object, so as to comprehensively display all fault signals of the range extender system, improve the accuracy of fault detection, and improve the safety and reliability of the range extender system.

[0040] In some embodiments, storing data packets in the fault multi-packet information at step S106 includes: in response to receiving a first data packet with a sequence number of one, starting to store and storing the first data packet, and setting the count value to the sum of the sequence number of the first data packet and a preset variable, and: in response to a second data packet received after the first data packet having a sequence number equal to the count value, storing the second data packet and increasing the count value by the preset variable; or in response to the sequence number of the second data packet not being equal to the count value, not storing the second data packet and stopping storage.

[0041] In some other embodiments, storing the data packets in the faulty multi-packet information at step S106 includes: stopping the storage in response to successfully storing all the data packets in the faulty multi-packet information.

[0042] As a non-limiting implementation, in the header of the fault multi-packet information, the number of frames and the number of bytes occupied by the data included in the reporting information are usually broadcast, thereby determining the number of data packets to be received and the sequence number of each data packet. For example, the fault multi-packet information may include three data packets, which are data packet A with sequence number 1, data packet B with sequence number 2, and data packet C with sequence number 3, and the count value M is initialized to 1, and the preset variable is 1. In response to receiving data packet A with sequence number 1, storage of data packet A begins and storage is performed, and the count value M=M+1 is updated, that is, the count value is 2. Specifically, after the storage starts, for example, the data of data packet A can be stored in array a (for example, array a can be an array of 1 column and 70 rows, or an array of other sizes specifically configured according to actual needs) in order from low to high, and the sequence number of the data packet may not be stored. In response to the continued reception of data packet B with sequence number 2, it is determined that the sequence number of data packet B is equal to the count value, data packet B is stored (for example, the data of data packet B is continued to be stored in array a from low to high order), and the count value M=M+1 is updated, that is, the count value is 3. In response to the continued reception of data packet C with sequence number 3, it is determined that the sequence number of data packet C is equal to the count value, and data packet C is stored (for example, the data of data packet C is continued to be stored in array a from low to high order). So far, all data packets A, B, and C of the faulty multi-packet information have been successfully stored.

[0043] In addition, if after storing data packet A and updating the count value M=2, data packet C with sequence number 3 is received instead of data packet B with sequence number 2, data packet C will not be stored and storage will be stopped. Thus, when packet loss is found, storage will be stopped in time and preparation will be made to receive the next report information again.

[0044] In some embodiments, the method 100 may include: in response to failure to successfully store all data packets in the faulty multi-packet information, not performing the operation performed in the aforementioned step S108. Thus, in the case where all data packets in the faulty multi-packet information are not successfully stored, the faulty multi-packet information is not processed, which can improve processing efficiency and reduce the risk of false detection caused by processing the faulty multi-packet information in the case of packet loss.

[0045] It can be understood that when a subsystem in the range extender system sends a fault, if the fault is not eliminated, the subsystem will continue to repeatedly send reporting information indicating the fault at a certain frequency. Therefore, if there is a packet loss problem in the current round of reporting information, the next round of reporting information can continue to be received and processed, thereby ensuring the accuracy and comprehensiveness of the fault analysis without missing the fault detection.

[0046] In some embodiments, the method 100 further includes: in response to determining that the reported information is not fault multi-packet information, determining whether the reported information is multi-packet information. In this embodiment, the method 100 further includes: in response to determining that the reported information is not multi-packet information, processing the reported information; or in response to determining that the reported information is multi-packet information, not processing the reported information.

[0047] For example, when it is determined that the reported information is not fault multi-packet information and is not multi-packet information, it can be determined that the reported information is single-packet information, and then the method for processing single-packet information as described below can be applied to the reported information to parse the fault signal in the reported information, thereby reducing the probability of missed parsing and mis-parsing when the reported information is single-packet information (which may include a single fault, or no fault). In addition, when it is determined that the reported information is not fault multi-packet information but multi-packet information, it can be determined that the reported information is non-fault multi-packet information, and it can be not processed at this time, thereby reducing the probability of mis-parsing when the reported information is non-fault multi-packet information (no fault).

[0048] In some embodiments, in response to determining that the reported information is not fault multi-packet information and is not multi-packet information, processing the reported information may include: in response to determining that the value of the fault signal in the reported information is outside the normal value range for the type of the fault signal and the continuous reporting time of the fault signal exceeds the normal time threshold for the type of the fault signal or is outside the normal time range for the type of the fault signal, determining the fault signal value of the fault signal as a first value, and the first value indicates a fault.

[0049] In other embodiments, in response to determining that the reported information is not fault multi-packet information and is not multi-packet information, processing the reported information may also include: in response to determining that the value of the fault signal in the reported information is within the above-mentioned normal value range or the continuous reporting time of the fault signal does not exceed the above-mentioned normal time threshold or is within the above-mentioned normal time range, determining the fault signal value of the fault signal as a second value, the second value indicating that there is no fault. In some embodiments, the first value may not be zero, and the second value may be zero. For example, the first value may be 1, and the second value may be 0.

[0050] Different types of fault signals (e.g., temperature fault signals, speed fault signals, etc.) may have different normal value ranges, which may be set separately according to specific circumstances. In some examples, a first preset value range indicating normality may be determined, and the value of the fault signal in the reported information may be compared with the first preset value range, so that when the value of the fault signal is within the first preset value range, the value of the fault signal is determined to be within the normal value range, and when the value of the fault signal is outside the first preset value range, the value of the fault signal is determined to be outside the normal value range. In other examples, a second preset value range indicating abnormality may be determined, and the value of the fault signal in the reported information may be compared with the second preset value range, so that when the value of the fault signal is outside the second preset value range, the value of the fault signal is determined to be within the normal value range, and when the value of the fault signal is within the second preset value range, the value of the fault signal is determined to be outside the normal value range. The first preset value range may, for example, be complementary to the second preset value range.

[0051] Different types of fault signals (e.g., temperature fault signals, speed fault signals, etc.) may have different normal time thresholds or normal time ranges, which may be set separately according to specific circumstances. In some examples, a first preset time range indicating normality may be determined, and the continuous reporting time of the fault signal in the reporting information may be compared with the first preset time range, so that when the continuous reporting time of the fault signal is within the first preset time range, it is determined that the continuous reporting time of the fault signal is within the normal time range, and when the continuous reporting time of the fault signal is outside the first preset time range, it is determined that the continuous reporting time of the fault signal is outside the normal time range. In other examples, a second preset time range indicating abnormality may be determined, and the continuous reporting time of the fault signal in the reporting information may be compared with the second preset time range, so that when the continuous reporting time of the fault signal is outside the second preset time range, it is determined that the continuous reporting time of the fault signal is within the normal time range, and when the continuous reporting time of the fault signal is within the second preset time range, it is determined that the continuous reporting time of the fault signal is outside the normal time range. The first preset time range may, for example, be complementary to the second preset time range. Generally speaking, the lower limit of the second preset time range is not lower than the upper limit of the first preset time range.

[0052] As a non-limiting implementation, assume that the fault signal in the reported information is an engine speed signal, the value of the engine speed signal is 200 revolutions per minute (r / min) and the continuous reporting time is 1 minute and 50 seconds, the normal value range for the engine speed signal is 700~4000 r / min, and the normal time threshold is 1 minute. At this time, the value of the engine speed signal in the reported information is outside the normal value range, and the continuous reporting time of the engine speed signal exceeds the normal time threshold, therefore, the fault signal value of the engine speed signal can be determined as 1 to indicate an engine speed fault.

[0053] In some embodiments, method 100 may include: performing a second encoding on a fault signal whose fault signal value is determined to be a first value to obtain a fault signal encoding value of the fault signal, and cyclically sending the fault signal encoding value. The second encoding may be the same as the first encoding, that is, they may adopt a unified encoding method. By uniformly encoding the faults of each subsystem (for example, ECU and VCU usually report a single fault package, and GCU usually reports a multi-fault package), the location of the fault can be determined by only sending the system fault, which is conducive to reducing the bus load rate.

[0054] refer to Figure 2 , which shows a flow chart of a non-limiting example process 200 in which a method for detecting a fault in a range extender system according to some embodiments of the present disclosure is applied. Figure 2 As shown, the non-limiting example process 200 includes steps S202 to S230.

[0055] In step S202, the reporting information of the subsystem is received.

[0056] In step S204, it is determined whether the reported information belongs to fault multi-packet information.

[0057] On the one hand, if the reported information belongs to fault multi-packet information (step S204 "Yes"), then at step S206, the data packets in the fault multi-packet information are stored; then at step S208, it is determined whether all the data packets in the fault multi-packet information are successfully stored; if all the data packets in the fault multi-packet information are not successfully stored (step S208 "No"), the reported information is not processed at step S218 and the process returns to step S202; if all the data packets in the fault multi-packet information have been successfully stored (step S208 "Yes"), at step S210, each data packet in the stored fault multi-packet information is parsed to obtain the fault signal value of the fault signal.

[0058] On the other hand, if the reported information does not belong to the fault multi-package information (step S204 "No"), then at step S220, it is determined whether the reported information belongs to the multi-package information; if it belongs to the multi-package information (step S220 "Yes"), then at step S230, the reported information is not processed and the process returns to step S202; if it does not belong to the multi-package information (step S220 "No"), then at step S222, it is determined whether the value of the fault signal is outside the corresponding normal value range; if the value of the fault signal is outside the corresponding normal value range (step S222 "Yes"), then the process continues. Continuing at step S224, determine whether the continuous reporting time of the fault signal exceeds the corresponding normal time threshold; if the continuous reporting time of the fault signal exceeds the corresponding normal time threshold (step S224 "Yes"), then at step S226, the fault signal value of the fault signal is determined to be 1; if the value of the fault signal is within the corresponding normal value range (step S222 "No") or the continuous reporting time of the fault signal does not exceed the corresponding normal time threshold (step S224 "No"), then at step S228, the fault signal value of the fault signal is determined to be 0.

[0059] Regardless of whether it is fault multi-packet information or single-packet information, after determining the fault signal value of the fault signal, at step S212, it is determined whether the fault signal value is zero; if the fault signal value is zero (step S212 "yes"), then return to step S202; if the fault signal value is not zero (step S212 "no"), then at step S214, the fault signal is encoded to obtain the fault signal encoding value of the fault signal; then, at step S216, the fault signal encoding value is sent cyclically. In other examples, after determining the fault signal value of the fault signal, at step S212, the fault signal is encoded to obtain the fault signal encoding value of the fault signal; then, at step S214, it is determined whether the fault signal encoding value of the fault signal indicates a fault; if the fault signal encoding value of the fault signal indicates a fault (step S214 "yes"), then at step S216, the fault signal encoding value is sent cyclically; if the fault signal encoding value of the fault signal indicates no signal (step S214 "no"), then return to step S202.

[0060] By uniformly encoding the fault signal in step S214, it is possible to determine the location of the fault by only sending the reporting information, thereby reducing the load rate of the bus. In some examples, the encoding of the fault signal in step S214 can be implemented by a fault signal encoding table.

[0061] The present disclosure also provides a range extender controller, which may include: a processor; and a memory storing computer executable instructions, which, when executed by the processor, enables the processor to execute the method for detecting a fault in a range extender system according to any of the aforementioned embodiments.

[0062] refer to Figure 3 , which shows a schematic block diagram of a range extender controller 300 according to some embodiments of the present disclosure. Figure 3 As shown, the range extender controller 300 includes a processor 302, and a memory 304 storing computer executable instructions, which, when executed by the processor 302, causes the processor 302 to perform the method 100 according to any of the aforementioned embodiments. The processor 302 may be, for example, a central processing unit (CPU) of the range extender controller 300. The processor 302 may be any type of general-purpose processor, or may be a processor specifically designed to detect faults in the range extender system, such as an application-specific integrated circuit (“ASIC”). The memory 304 may be coupled to the processor 302 and may include various computer-readable media accessible by the processor 302. In various embodiments, the memory 304 described herein may include volatile and non-volatile media, removable and non-removable media. For example, the memory 304 may include any combination of the following: random access memory (“RAM”), dynamic RAM (“DRAM”), static RAM (“SRAM”), read-only memory (“ROM”), flash memory, cache memory, and / or any other type of non-transitory computer-readable media. The memory 304 may store instructions that, when executed by the processor 302 , enable the processor 302 to perform the method 100 according to any of the aforementioned embodiments of the present disclosure.

[0063] The range extender controller 300 is configured to execute the method 100 described in any of the foregoing embodiments, and therefore reference may be made to the foregoing descriptions of the various embodiments of the method 100 , which will not be repeated herein.

[0064] The present disclosure also provides a non-transitory storage medium having computer executable instructions stored thereon, which, when executed by a computer, causes the computer to execute the method for detecting a fault of a range extender system according to any of the aforementioned embodiments of the present disclosure.

[0065] The present disclosure also provides a computer program product, which may include instructions, and when the instructions are executed by a processor, the method for detecting a fault of a range extender system according to any of the aforementioned embodiments of the present disclosure may be implemented. The instructions may be any set of instructions to be executed directly by one or more processors, such as machine code, or any set of instructions to be executed indirectly, such as a script. The instructions may be stored in an object code format for direct processing by one or more processors, or in any other computer language, including a script or collection of independent source code modules that are interpreted on demand or compiled in advance.

[0066] The present disclosure also provides a range extender system. Figure 4, which shows a schematic block diagram of a range extender system 400 (hereinafter referred to as "system 400") according to some embodiments of the present disclosure. It is understood that the actual range extender system 400 may also include other components, but in order to avoid blurring the key points of the present disclosure, these other components are not discussed herein and are not shown in the drawings.

[0067] like Figure 4 As shown, the system 400 may include a range extender controller 402, a display 404, and at least one of an engine controller 408, a vehicle controller 406, and a generator controller 410 coupled to a bus (indicated by an arrow, which may be, for example, a CAN bus). In some embodiments, the bus includes a first portion and a second portion, wherein the display 404 and the vehicle controller 406 are coupled to the range extender controller 402 (e.g., via a CANB module of the range extender controller 402) through the first portion, and the engine controller 408 and the generator controller 410 (e.g., respectively, through their respective CAN1 modules) are coupled to the range extender controller 402 (e.g., via a CANC module of the range extender controller 402) through the second portion.

[0068] For example, the range extender controller 402 may be configured to control the engine controller 408 and the generator controller 410 to perform corresponding responses according to instructions from the vehicle controller 406. The engine controller 408 may be configured to monitor and control the operation of the engine. The generator controller 410 may be configured to convert the mechanical energy output by the engine into electrical energy.

[0069] At least one of the engine controller 408 , the vehicle controller 406 , and the generator controller 410 may be configured to send reporting information to the bus.

[0070] The range extender controller 402 may be configured to: receive reporting information; determine that the reporting information is fault multi-packet information; store data packets in the fault multi-packet information; and perform the following operations in response to successfully storing all data packets in the fault multi-packet information. The operation includes: parsing each data packet in the stored fault multi-packet information to obtain a fault signal value of a fault signal, first encoding a fault signal whose fault signal value indicates a fault to obtain a fault signal encoding value of the fault signal, and cyclically sending the fault signal encoding value to the bus. In some embodiments, the reporting information received by the range extender controller 402 is reporting information received from at least one of the engine controller 408, the vehicle controller 406, and the generator controller 410 via the bus. Additionally or alternatively, in some embodiments, the reporting information received by the range extender controller 402 is generated internally (e.g., by a fault detection module built into the range extender controller 402).

[0071] The display 404 may be configured to receive and display the fault signal encoding value from the bus.

[0072] In some embodiments, the range extender controller 402 is configured to: in response to determining that the reported information is not a fault multi-packet information, determine whether the reported information is a multi-packet information. In some such embodiments, the range extender controller 402 may also be configured to not process the reported information in response to determining that the reported information is a multi-packet information. In some such embodiments, the range extender controller 402 may also be configured to process the reported information in response to determining that the reported information is not a multi-packet information. For example, processing the reported information may include: in response to determining that the magnitude of the fault signal in the reported information is outside the normal magnitude range for the type of the fault signal and the continuous reporting time of the fault signal exceeds the normal time threshold for the type of the fault signal or is outside the normal time range for the type of the fault signal, determining the fault signal value of the fault signal as a first value, the first value indicating a fault; or in response to determining that the magnitude of the fault signal in the reported information is within the normal magnitude range or the continuous reporting time of the fault signal does not exceed the normal time threshold or is within the normal time range, determining the fault signal value of the fault signal as a second value, the second value indicating no fault.

[0073] In some embodiments, the range extender controller 402 is configured to: perform a second encoding on a fault signal whose fault signal value is determined to be a first value to obtain a fault signal encoding value of the fault signal, and cyclically send the fault signal encoding value to the bus. The second encoding may be the same as the first encoding.

[0074] In some embodiments, the range extender controller 402 is configured to: in response to receiving a first data packet with a sequence number of one, start storing and storing the first data packet, and set the count value to the sum of the sequence number of the first data packet and a preset variable, and: in response to the sequence number of a second data packet received after the first data packet being equal to the count value, store the second data packet and increase the count value by a preset variable; or in response to the sequence number of the second data packet not being equal to the count value, not store the second data packet and stop storing. In some such embodiments, the range extender controller 402 is further configured to not perform an operation (specifically, not perform the described parsing, encoding, sending, etc.) in response to not successfully storing all data packets in the faulty multi-packet information.

[0075] In some embodiments, the range extender controller 402 is further configured to: parse each data packet in the stored fault multi-packet information to obtain corresponding fault signal values ​​of multiple fault signals, encode each fault signal among the multiple fault signals whose fault signal value indicates a fault to obtain a fault signal encoding value of the fault signal, and send the fault signal encoding value to the bus in a loop.

[0076] In some such embodiments, the range extender controller 402 is configured to, when acquiring multiple fault signal code values, cyclically send the multiple fault signal code values ​​to the bus in the following manner: in response to the current fault signal code value to be sent being different from the last fault signal code value that has been sent, determine whether the continuous sending time of the last fault signal code value reaches the preset continuous sending time, and: in response to the continuous sending time of the last fault signal code value not reaching the preset continuous sending time, continue to send the last fault signal code value to the bus; or in response to the continuous sending time of the last fault signal code value reaching the preset continuous sending time, send the current fault signal code value to the bus. In this way, different fault signal code values ​​can be continuously displayed on the display for a period of time, thereby helping the operator to see and discover the fault in the first place and prevent missing the fault, improve the efficiency of fault troubleshooting, and improve the safety and reliability of the range extender system.

[0077] System 400 receives, analyzes, encodes and cyclically transmits fault signals of each subsystem of the range extender system through the range extender controller, and displays each fault signal encoding value on the display for at least a period of time, thereby solving the problem of the human eye observing the high-frequency data displayed on the display without upgrading the display or adding other display devices, thereby accurately and quickly discovering and locating faults, improving work efficiency, enhancing the safety and reliability of the range extender system, and reducing costs.

[0078] The range extender controller in the system 400 may be configured to execute the method 100 described in any of the foregoing embodiments, and thus various embodiments of the system 400 may refer to the foregoing descriptions of various embodiments of the method 100 and will not be repeated herein.

[0079] Figure 5A schematic block diagram of a computer system 500 on which embodiments of the present disclosure may be implemented is shown. The computer system 500 includes a bus 502 or other communication mechanism for transmitting information, and a processing device 504 coupled to the bus 502 for processing information. The computer system 500 also includes a memory 506 coupled to the bus 502 for storing instructions to be executed by the processing device 504, which may be a random access memory (RAM) or other dynamic storage device. The memory 506 may also be used to store temporary variables or other intermediate information during the execution of instructions to be executed by the processing device 504. The computer system 500 also includes a read-only memory (ROM) 508 or other static storage device coupled to the bus 502 for storing static information and instructions for the processing device 504. A storage device 510 such as a magnetic disk or optical disk is provided and coupled to the bus 502 for storing information and instructions. The computer system 500 may be coupled to an output device 512 via the bus 502 for providing output to a user, such as, but not limited to, a display (such as a cathode ray tube (CRT) or a liquid crystal display (LCD)), a speaker, etc. An input device 514 such as a keyboard, a mouse, a microphone, etc. is coupled to the bus 502 for transmitting information and command selections to the processing device 504. The computer system 500 may perform embodiments of the present disclosure. Consistent with certain implementations of the present disclosure, the results are provided by the computer system 500 in response to the processing device 504 executing one or more sequences of one or more instructions contained in the memory 506. Such instructions may be read into the memory 506 from another computer-readable medium such as the storage device 510. The execution of the sequence of instructions contained in the memory 506 causes the processing device 504 to perform the methods described herein. Alternatively, hard-wired circuitry may be used instead of software instructions or in combination with software instructions to implement the present teachings. Therefore, implementations of the present disclosure are not limited to any specific combination of hardware circuitry and software. In various embodiments, computer system 500 can be connected to one or more other computer systems like computer system 500 across a network via network interface 516 to form a networked system. The network can include a private network or a public network such as the Internet. In a networked system, one or more computer systems can store data and supply data to other computer systems. The term "computer-readable medium" as used herein refers to any medium that participates in providing instructions to processing device 504 for execution. Such media can take many forms, including but not limited to non-volatile media, volatile media, and transmission media. Non-volatile media include, for example, optical disks or disks such as storage device 510. Volatile media include dynamic memories such as memory 506. Transmission media include coaxial cables, copper wires, and optical fibers, including wiring that includes bus 502.Common forms of computer-readable media or computer program products include, for example, floppy disks, flexible disks, hard disks, tapes, or any other magnetic media, CD-ROMs, digital video disks (DVDs), Blu-ray disks, any other optical media, thumb drives, memory cards, RAMs, PROMs and EPROMs, flash EPROMs, any other memory chips or boxes, or any other tangible media from which a computer can read. Various forms of computer-readable media may be involved when carrying one or more sequences of one or more instructions to processing device 504 for execution. For example, instructions may initially be carried on a disk of a remote computer. The remote computer may load instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 500 may receive data over a telephone line and convert the data into an infrared signal using an infrared transmitter. An infrared detector coupled to bus 502 may receive the data carried in the infrared signal and place the data on bus 502. Bus 502 carries the data to memory 506, and processing device 504 retrieves instructions from memory 506 and executes the instructions. Optionally, the instructions received by memory 506 may be stored on storage device 510 either before or after execution by processing device 504 .

[0080] According to various embodiments, instructions configured to be executed by a processing device to perform a method are stored on a computer-readable medium. A computer-readable medium may be a device that stores digital information. For example, a computer-readable medium includes a compact disk read-only memory (CD-ROM) as known in the art for storing software. The computer-readable medium is accessed by a processor adapted to execute the instructions configured to be executed.

[0081] One or more exemplary embodiments of the present disclosure are described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0082] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a server system. Of course, the present disclosure does not exclude that with the development of computer technology in the future, the computer that implements the functions of the above embodiments may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0083] Although one or more embodiments of the present disclosure provide method operation steps as described in the embodiments or flowcharts, more or fewer operation steps may be included based on conventional or non-creative means. The order of steps listed in the embodiments is only one way of executing the order of many steps and does not represent the only execution order. When the device or terminal product in practice is executed, it can be executed in sequence or in parallel according to the method shown in the embodiments or the drawings (for example, in a parallel processor or multi-threaded processing environment, or even a distributed data processing environment).

[0084] The terms "comprises", "includes" or any other variation thereof are intended to cover non-exclusive inclusion, so that a process, method, product or apparatus comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, product or apparatus. In the absence of further restrictions, it is not excluded that there are other identical or equivalent elements in the process, method, product or apparatus comprising the elements. For example, if the words "first", "second" and the like are used to indicate names, they do not indicate any particular order.

[0085] For the convenience of description, the above devices are described in various modules according to their functions. Of course, when implementing one or more embodiments of the present disclosure, the functions of each module can be implemented in the same or more software and / or hardware, or the module implementing the same function can be implemented by a combination of multiple sub-modules or sub-units, etc. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0086] The present disclosure is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present disclosure. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate a device for implementing the functions specified in one process or multiple processes in the flowchart and / or one box or multiple boxes in the block diagram.

[0087] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0088] These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0089] Those skilled in the art should understand that one or more embodiments of the present disclosure may be in the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, one or more embodiments of the present disclosure may be in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0090] One or more embodiments of the present disclosure may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more embodiments of the present disclosure may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0091] The same or similar parts between the various embodiments of the present disclosure can refer to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts refer to the partial description of the method embodiment. In the description of the present disclosure, the description of the reference terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present disclosure. In the present disclosure, the schematic representation of the above terms does not necessarily target the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner. In addition, in the absence of mutual contradiction, those skilled in the art can combine and combine the different embodiments or examples described in the present disclosure and the features of the different embodiments or examples.

[0092] In addition, when used in the present disclosure, the words "herein," "above," "below," "hereunder," "above," and words of similar meaning shall refer to the present disclosure as a whole rather than to any particular portion of the present disclosure. Furthermore, unless expressly stated otherwise or understood otherwise in the context of use, conditional language used herein, such as "may," "might," "for example," "such as," and the like, is generally intended to express that certain embodiments include, while other embodiments do not include, certain features, elements, and / or states. Thus, such conditional language is generally not intended to imply that one or more embodiments require features, elements, and / or states in any way, or whether such features, elements, and / or states are included or performed in any particular embodiment.

[0093] The above description is only an example of one or more embodiments of the present disclosure, and is not intended to limit one or more embodiments of the present disclosure. For those skilled in the art, one or more embodiments of the present disclosure may have various changes and variations. Any modification, equivalent substitution, improvement, etc. made within the spirit and principle of the present disclosure shall be included in the scope of the claims.

Claims

1. A method for detecting a fault in a range extender system, the method comprising: Receiving reporting information from a subsystem of the range extender system; Determining that the reported information is fault multi-packet information; Storing data packets in the fault multi-packet information; as well as In response to successfully storing all data packets in the faulty multi-packet information, performing the following operations: Parsing each data packet in the stored fault multi-packet information to obtain a fault signal value of the fault signal, performing a first encoding on a fault signal whose fault signal value indicates a fault to obtain a fault signal encoding value of the fault signal, and The fault signal encoding value is sent cyclically.

2. The method according to claim 1, comprising: In response to determining that the reported information is not fault multi-packet information, determining whether the reported information is multi-packet information, Wherein, the method further comprises: In response to determining that the reported information is not multi-packet information, processing the reported information; or In response to determining that the reported information is multi-packet information, the reported information is not processed.

3. The method according to claim 2, wherein: In response to determining that the reported information is not multi-packet information, processing the reported information includes: In response to determining that the magnitude of the fault signal in the reporting information is outside the normal magnitude range for the type of the fault signal and the continuous reporting time of the fault signal exceeds the normal time threshold for the type of the fault signal or is outside the normal time range for the type of the fault signal, determining the fault signal value of the fault signal as a first value, wherein the first value indicates a fault; or In response to determining that the value of the fault signal in the reporting information is within the normal value range or the continuous reporting time of the fault signal does not exceed the normal time threshold or is within the normal time range, the fault signal value of the fault signal is determined as a second value, and the second value indicates that there is no fault.

4. The method according to claim 3, comprising: Performing a second encoding on a fault signal whose fault signal value is determined to be a first value to obtain a fault signal code value of the fault signal, wherein the second encoding is the same as the first encoding; as well as The fault signal code value is sent cyclically.

5. The method according to claim 1, wherein: The data packets storing the fault multi-packet information include: In response to receiving a first data packet with a sequence number of one, starting to store and storing the first data packet, and setting the count value to the sum of the sequence number of the first data packet and a preset variable, and: In response to a sequence number of a second data packet received after the first data packet being equal to the count value, storing the second data packet and increasing the count value by the preset variable; or In response to the sequence number of the second data packet not being equal to the count value, the second data packet is not stored and the storing is stopped.

6. The method according to claim 1, comprising: In response to failure to successfully store all data packets in the failed multi-packet information, not performing the operation.

7. The method according to claim 1, wherein: The subsystem of the range extender system includes at least one of an engine controller, a range extender controller, a vehicle controller, and a generator controller.

8. The method according to claim 1, wherein: The operations include: Parsing each data packet in the stored fault multi-packet information to obtain corresponding fault signal values ​​of multiple fault signals, encoding each fault signal of the plurality of fault signals whose fault signal value indicates a fault to obtain a fault signal encoding value of the fault signal, and The fault signal encoding value is sent cyclically.

9. The method according to claim 8, wherein: When multiple fault signal code values ​​are obtained, the multiple fault signal code values ​​are cyclically sent in the following manner: In response to the current fault signal code value to be sent being different from the last fault signal code value that has been sent, determining whether the continuous sending time of the last fault signal code value reaches a preset continuous sending time, and: In response to the continuous sending time of the previous fault signal code value not reaching the preset continuous sending time, continue to send the previous fault signal code value; or In response to the continuous sending time of the previous fault signal code value reaching the preset continuous sending time, the current fault signal code value is sent.

10. A range extender controller, comprising: processor; as well as A memory storing computer executable instructions, which, when executed by the processor, cause the processor to perform the method for detecting a fault of a range extender system according to any one of claims 1 to 9.

11. A non-transitory storage medium having computer executable instructions stored thereon, the computer executable instructions, when executed by a processor, causing the processor to perform the method for detecting a fault of a range extender system according to any one of claims 1 to 9. 12 . A computer program product comprising instructions, which when executed by a processor implement the method for detecting a fault in a range extender system according to claim 1 .

13. A range extender system, comprising: a range extender controller coupled to the bus; a display coupled to the bus; At least one of an engine controller, a vehicle controller, and a generator controller, which is coupled to the bus and configured to send reporting information to the bus, Wherein, the range extender controller is configured as follows: Receive reported information; Determining that the reported information is fault multi-packet information; storing the data packets in the fault multi-packet information; and In response to successfully storing all data packets in the faulty multi-packet information, performing the following operations: Parsing each data packet in the stored fault multi-packet information to obtain a fault signal value of the fault signal, performing a first encoding on a fault signal whose fault signal value indicates a fault to obtain a fault signal encoding value of the fault signal, and The fault signal encoding value is sent cyclically to the bus, And wherein the display is configured to receive and display the fault signal encoding value from the bus.

14. The range extender system according to claim 13, wherein: The range extender controller is configured as follows: In response to determining that the reported information is not fault multi-packet information, determining whether the reported information is multi-packet information, Wherein, the range extender controller is configured as follows: In response to determining that the reported information is multi-packet information, not processing the reported information; or In response to determining that the reported information is not multi-packet information, the reported information is processed, wherein the processing of the reported information includes: In response to determining that the magnitude of the fault signal in the reporting information is outside the normal magnitude range for the type of the fault signal and the continuous reporting time of the fault signal exceeds the normal time threshold for the type of the fault signal or is outside the normal time range for the type of the fault signal, determining the fault signal value of the fault signal as a first value, the first value indicating a fault; or In response to determining that the value of the fault signal in the reporting information is within the normal value range or the continuous reporting time of the fault signal does not exceed the normal time threshold or is within the normal time range, the fault signal value of the fault signal is determined as a second value, and the second value indicates that there is no fault.

15. The range extender system according to claim 14, wherein: The range extender controller is configured as follows: Performing a second encoding on a fault signal whose fault signal value is determined to be a first value to obtain a fault signal code value of the fault signal, the second encoding being the same as the first encoding; and The fault signal encoding value is cyclically sent to the bus.

16. The range extender system according to claim 13, wherein: The range extender controller is configured as follows: In response to receiving a first data packet with a sequence number of one, starting to store and storing the first data packet, and setting the count value to the sum of the sequence number of the first data packet and a preset variable, and: In response to a sequence number of a second data packet received after the first data packet being equal to the count value, storing the second data packet and increasing the count value by the preset variable; or In response to the sequence number of the second data packet not being equal to the count value, not storing the second data packet and stopping storing, The range extender controller is further configured to not perform the operation in response to failure to successfully store all data packets in the fault multi-packet information.

17. The range extender system according to claim 13, wherein: The range extender controller is further configured to: Parsing each data packet in the stored fault multi-packet information to obtain corresponding fault signal values ​​of multiple fault signals, encoding each fault signal of the plurality of fault signals whose fault signal value indicates a fault to obtain a fault signal encoding value of the fault signal, and The fault signal encoding value is cyclically sent to the bus.

18. The range extender system according to claim 17, wherein: The range extender controller is configured to, when acquiring a plurality of fault signal code values, cyclically send the plurality of fault signal code values ​​to the bus in the following manner: In response to the current fault signal code value to be sent being different from the last fault signal code value that has been sent, determining whether the continuous sending time of the last fault signal code value reaches a preset continuous sending time, and: In response to the continuous sending time of the last fault signal code value not reaching the preset continuous sending time, continue to send the last fault signal code value to the bus; or In response to the continuous sending time of the previous fault signal code value reaching the preset continuous sending time, the current fault signal code value is sent to the bus.

Images