CN114973453A

CN114973453A - Vehicle motor controller fault information storage system

Info

Publication number: CN114973453A
Application number: CN202210527208.3A
Authority: CN
Inventors: 贾成禹; 尚超; 吴威振; 秦显慧
Original assignee: Beijing Sword Electric Industrial Co ltd
Current assignee: Beijing Sword Electric Industrial Co ltd
Priority date: 2022-05-16
Filing date: 2022-05-16
Publication date: 2022-08-30

Abstract

The invention relates to the field of electric vehicle fault analysis, provides a vehicle motor controller fault information storage system, and aims to solve the problem of storage and reading of fault data. The system comprises: the main controller writes fault data into the storage module or reads the fault data from the storage module; the storage module includes a fault logging unit and a plurality of data storage units. The storage of the fault data is performed by the following data storage steps: storing the data to be stored in the selected unit to be stored, and judging whether the fault recording condition is met; when the fault recording condition is met, recording the serial number of the unit to be stored and the address stored by the fault data in the fault recording unit; selecting a new unit to be stored from the plurality of data storage units according to preset logic; and after the unit to be stored is reset, continuing the data storage step. The invention realizes timely and comprehensive storage and reading of fault data.

Description

Vehicle motor controller fault information storage system

Technical Field

The invention relates to the field of electric vehicle control, in particular to a fault information storage system of a vehicle motor controller.

Background

With the development of economy and the popularization of new energy technology, new energy automobiles are rapidly developed. The motor controller is a core component of a motor system of the electric automobile and realizes the conversion of direct current and alternating current. The motor controller is used for adjusting energy conversion to save efficiency and improve pure electric endurance mileage of the electric vehicle. In order to ensure that the motor controller can normally and safely operate, fault diagnosis of the motor controller and relevant components such as a motor and the like is indispensable, and the abnormal state is detected and corresponding safety treatment is carried out before the motor controller is in danger through the fault diagnosis so as to ensure that an automobile is safely stopped. The timely and comprehensive storage of the key state data information before and after the motor controller fails is the guarantee that the failure causes can be found out quickly and the failure can be solved.

At present, the following scheme is provided for storing key state data information before and after a motor controller fault. The first scheme is as follows: a mode of storing a group of fault data at the fault moment is adopted, namely a group of fault-related state data, such as the rotating speed of a motor, bus voltage and the like at the fault moment, is stored at the fault reporting moment, and the group of data can be read later to analyze the fault reason. The data saved by the scheme can help to analyze the fault reason to a certain extent, and the storage space required by the small amount of the stored data is small, so that a storage chip is not required to be additionally added for the function. However, since the amount of stored data is small and many faults have detection time, the fault reporting time is not the initial occurrence time of the fault, and the stored data is not the real data corresponding to the fault occurrence time, which reduces the accuracy of analyzing the fault by using the data. Scheme II: and data of a period of time before and after the fault is stored in an external handheld device mode. In the scheme, the motor controller does not have a storage device for storing continuous fault data, and if the fault data needs to be stored, a manual plug-in handheld device is needed. Therefore, after the fault needs to be fed back on site, the external handheld device is manually removed, and data are monitored when the fault occurs again, so that on one hand, the labor cost is increased, and the fault data can be acquired after the next fault occurs, so that the time for analyzing and solving the problem is greatly prolonged.

The existing data storage mode has the problems that the stored data quantity is too small, and the data may not be the data at the real fault occurrence time, so that the fault reason may not be accurately analyzed by using the data; or a device for storing data is manually added after the fault needs to be fed back on site, so that the problem of fault analysis solution time is greatly prolonged. Therefore, a system capable of directly storing fault data is needed, which can save the relevant data of all fault occurrence moments in real time after the faults occur, and improve the timeliness and comprehensiveness of the fault data storage, thereby ensuring the safe operation of the motor controller.

Disclosure of Invention

The method aims to solve the problems in the prior art that after a fault occurs in the operation of a motor controller and related components, the amount of stored data is too small and the data may not be the data at the time of the true fault occurrence in the existing data storage mode, so that the fault reason may not be accurately analyzed by using the data; or a device for storing data is manually added after the fault needs to be fed back on site, so that the problem of fault analysis solution time is greatly prolonged. The application provides a motor controller fault information storage system for vehicle, preserves the relevant data of all trouble emergence moments in real time after the trouble takes place, and quick analysis location problem reason solves the problem, makes the vehicle resume normal operating in order to improve the security performance of whole car. The following technical scheme is adopted to solve the problems:

the application provides a motor controller fault information storage system for vehicle, this system includes: the main controller is in communication connection with the storage module, and writes fault data into the storage module or reads the fault data from the storage module; the storage module comprises a fault recording unit and a plurality of data storage units; the storage of the fault data is performed through the following data storage steps, wherein the data storage steps comprise:

storing the data to be stored in the selected unit to be stored, and judging whether the fault recording condition is met; when the fault recording condition is satisfied, recording the address of the written data to be stored in the unit to be stored in the fault recording unit when the serial number of the unit to be stored and the fault recording condition are satisfied; selecting the data storage unit to be subjected to data writing operation from a plurality of data storage units as the to-be-stored unit according to preset logic; and resetting the unit to be stored after the first threshold time, and continuing the data storage step.

In some examples, the vehicle motor controller failure information storage system further includes a code that is encoded in advance for each of the data storage units, and a number that corresponds to each of the data storage units is assigned.

In some examples, the "storing data to be stored in the selected unit to be stored" includes: and sequentially storing the data to be stored into the units to be stored from the first address of the units to be stored in a cyclic writing mode.

In some examples, the data storing step further includes: and when the fault recording condition is met, continuing to record the data to be stored in the cell block to be stored within the first threshold time.

In some examples, the motor controller failure information storage system for a vehicle further includes a data reading step, the data reading step including: determining a fault data unit and a fault address according to information recorded in the fault recording unit, wherein the fault data unit is a data storage unit for recording the fault data, and the fault address is a first address for storing the fault data; reading data of a specified length from the defective address of the defective data storage unit.

In some examples, the "determining the failure data unit and the failure address according to the information recorded in the failure recording unit" includes: extracting number information from the information recorded by the fault recording unit, and determining the data storage unit recording the fault data as the fault storage unit according to the corresponding relation between the number and each data storage unit; and extracting the address of the written data to be stored in the unit to be stored when the fault recording condition is met from the information recorded by the fault recording unit, and determining the address as a fault address for recording fault data when the fault is detected.

According to the fault information storage system of the vehicle motor controller, data are stored in the selected data storage unit, and when a fault condition is met, the serial number and the storage address of the data storage unit for storing fault data in a period of time before and after the fault occurs are recorded in the fault recording unit; and, reselecting one data storage unit from the plurality of data storage units according to a preset logic to record the subsequent data. When the fault data needs to be read, the data storage unit corresponding to the read fault data and the position of the read data are determined according to the number and the storage address of the data storage unit in the information recorded by the fault recording unit when the fault recording condition is met. The data storage method and the data storage device have the advantages that the data stored for a period of time before and after the fault occurs automatically are divided into the plurality of data storage units, and a plurality of fault data can be stored on the basis that the storage modules are not added. Meanwhile, the serial number and the address of the data storage unit for storing the fault data are recorded in the fault recording unit, so that the fault data are conveniently positioned, the fault data are read and analyzed, and the fault is quickly solved.

Drawings

FIG. 1 is a schematic diagram of an exemplary system architecture to which embodiments of the present application may be applied;

FIG. 2 is a schematic view of a flow chart of data storage steps in an embodiment of the vehicle motor controller failure information storage system according to the present application;

FIG. 3 is a schematic view of a flow chart of data reading step in an embodiment of the storage system for vehicle motor controller failure information according to the present application;

FIG. 4 is a schematic flow chart illustrating an implementation of a step of storing failure data in an application scenario according to an embodiment of the present application;

fig. 5 is a schematic flowchart of an implementation procedure of a step of reading fault data in an application scenario according to an embodiment of the present application.

Detailed Description

Preferred embodiments of the present invention are described below with reference to the accompanying drawings. It should be understood by those skilled in the art that these embodiments are only for explaining the technical principle of the present invention, and are not intended to limit the scope of the present invention.

It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.

FIG. 1 illustrates an exemplary system block diagram that may be applied to embodiments of the present application.

As shown in fig. 1, the motor controller failure information storage system for a vehicle includes: a main controller 1 and a storage module 2, wherein the main controller 1 is connected to the storage module 2 in a communication manner, and the main controller 1 writes failure data into the storage module 2 or reads failure data from the storage module 2; the memory module 2 includes a failure recording unit and a plurality of data storage units.

The main controller 1 may be a Motor Controller (MCU) for an electric vehicle, or a Vehicle Control Unit (VCU). The main controller 1 is a core control unit of the electric automobile, collects a driver driving signal and a vehicle state, manages, schedules, analyzes and operates network information through a CAN bus, manages energy according to different vehicle configurations, and realizes the driving control of the whole automobile.

The storage module 2 can be a data storage chip with no data loss after power failure, such as an F-RAM, an off-chip Flash, an EEPROM and the like. Ferroelectric random access memory (i.e., F-RAM), which is a type of nonvolatile memory capable of performing read and write operations, is used in the present application. The memory module 2 may be built in the main controller 1.

The communication connection between the main controller 1 and the memory module 2 may be a communication connection using an SPI high-speed synchronous serial input/output port or a multi-channel buffer serial port Mcbsp port. The main controller 1 may store the acquired data or the data after the arithmetic processing in the storage module 2, or may read out the held data from the storage module 2. Specifically, as shown in fig. 1, the main controller 1 and the memory module 2 are provided with a SIMO data connection, a SOMI data connection, a CS chip select connection, and a CLK clock connection. Through the SIMO data connection, the main controller 1 writes data to the memory module 2; through the SOMI data connection, the main controller 1 reads out fault data from the storage module 2; through the CS chip select connection, the main controller 1 can select a location where data is saved/read in the storage module 2; the clock synchronization of the main controller 1 and the memory module 2 is realized through the CLK clock connection. Wherein the data related to the safe operation of the vehicle detected when the vehicle is out of order, or the data related to the safe operation of the vehicle detected when a preset failure condition is satisfied, is taken as the failure data.

In this embodiment, the storage module 2 includes a fault recording unit and a plurality of data storage units. In order to store a plurality of sets of fault data, the storage module 2 is divided into a fault recording unit and a plurality of data storage units. The data storage unit may store data sent by the main controller 1, each data storage unit may record a set of fault data, and the fault recording unit may record information about the time when the fault occurs, the location where the fault data is stored, and the like in each set of fault data. In a specific application, the size of each data storage unit can be adjusted according to the number (or length) of data to be recorded in each group of fault data. For example, less data needs to be recorded for each set of fault data, the number of data storage units can be increased appropriately by reducing the capacity of each data storage unit, so as to store more fault data; for example, more data needs to be recorded in each group of fault data, and the number of data storage units can be appropriately reduced by increasing the capacity of each data storage unit, so as to comprehensively store the associated data before and after the occurrence of the fault.

The storage or reading of data between the main controller 1 and the memory module 2 may be realized by the following data storage step and data reading step.

With continuing reference to fig. 2, fig. 2 is a schematic flow chart illustrating the implementation of data storage steps applied to the embodiment of the vehicle motor controller failure information storage system. As shown in fig. 2, the implementation flow of the data storage step is specifically as follows:

and step11, storing the data to be stored in the selected unit to be stored, and judging whether the fault recording condition is met.

In this embodiment, the main controller 1 collects the vehicle state information or the information related to the safe operation of the vehicle in real time, and in order to facilitate the failure analysis later, some collected information related to the safe operation of the vehicle needs to be subjected to the failure analysis when the failure occurs. Therefore, when a failure occurs, data or information related to safe operation of the vehicle needs to be saved as failure data. In order to protect the safe operation of the vehicle, the main controller 1 may collect data such as speed (or rotational speed), acceleration, bus voltage, current, and the like of the motor. The data related to the safe operation of the motor, which is acquired or processed by the main controller 1, is used as data to be stored. The unit to be stored is a data storage unit selected from a plurality of data storage units and used for storing fault data. Because each data storage unit is coded in advance and the number corresponding to each data storage unit is allocated, when the unit to be stored is selected, the unit to be stored can be selected circularly according to the size of the number sequence corresponding to the data storage unit. In this embodiment, the data to be stored is stored in the unit to be stored. And writing the data to be stored into the unit to be stored in a data writing mode. When the system is initialized at power-on, all data in each data storage unit is reset to 0.

Specifically, the data to be stored is written in order from the head address of the unit to be stored in a cyclic writing manner. The data written to the selected cell to be stored may be normal data or may be failure data. In the process of writing data into the to-be-stored unit, the main controller 1 determines whether a fault recording condition is satisfied, that is, determines whether the to-be-written data has a fault or is possible to have a fault. When the fault recording condition is not triggered, the main controller 1 writes the data related to the safe operation of the vehicle, which is detected in real time, as the data to be stored into the unit to be stored in real time, and then writes the data into the unit to be stored from the starting end of the unit to be stored in a circulating manner again after the data reaches the tail end of the unit to be stored.

And 12, when the fault recording condition is satisfied, recording the address of the written data to be stored in the unit to be stored in the fault recording unit, wherein the address of the written data to be stored in the unit to be stored is the address of the written data to be stored in the unit to be stored when the fault recording condition is satisfied.

In this embodiment, in step1, the main controller 1 continuously writes the collected real-time data or the processed data into the selected to-be-stored unit in a circulating manner. And when the fault recording condition is met, the data to be stored is the fault data which needs to be recorded in the selected storage unit for subsequent fault reason analysis.

And when the fault recording condition is met, recording the written data to be stored in the address of the unit to be stored in the fault recording unit when the serial number of the unit to be stored and the fault recording condition are met. That is, the failure recording unit records: when the fault condition is satisfied, the position where the data to be stored is stored can be represented by the number information and the address information. The number information is the number of the data storage unit in which the data to be stored is written when the fault occurs; the address information is the address of the data to be stored, which is being written, in the data storage unit when a failure occurs.

Further, in order to facilitate analysis of the cause of the fault, it is necessary to record data before and after the fault for a certain period of time when the fault occurs. And when the fault recording condition is met, continuing to store and record the data to be stored in the unit block to be stored in a second threshold time period.

And step13, selecting the data storage unit to be subjected to data writing operation from the plurality of data storage units as a new unit to be stored according to a preset logic.

In this embodiment, based on the process of recording the number and address of the current to-be-stored unit in the fault recording unit when the fault recording condition is satisfied, which is implemented in step12, the data storage unit needs to be reselected as the to-be-stored unit for storing the next group of fault data based on step 12. The selecting step is to select the data storage unit to be subjected to the data writing operation from the plurality of data storage units according to a set condition as the to-be-stored unit. Specifically, one of the data storage units that has not stored the failure data may be selected as a new unit to be stored. Here, the units to be stored may be selected in order of the data storage unit numbers.

And 14, after the first threshold time, resetting the newly selected unit to be stored, and continuing the data storage step.

In this embodiment, after the fault recording condition is satisfied, a reset operation is performed on the newly selected to-be-stored unit after a first threshold time elapses, where all data of the newly selected to-be-stored unit may be reset to 0. The first purpose is to clear the invalid data of the storage unit, namely to clear the original data; the other is to identify whether there is missing data, that is, if all or most of the stored data is 0 after writing, the data is missing. After the reset operation is completed, the process then proceeds to step11, and the main controller 1 writes the data to be stored into the newly selected unit to be stored, and continues the above-described failure data saving step. In practical applications, the time lengths of the first threshold time and the second threshold time may be set to be the same time, for example, the first threshold time and the second threshold time are both set to be 2 seconds.

With continuing reference to fig. 3, fig. 3 is a schematic flow chart illustrating an implementation of the data reading step of the vehicle motor controller failure information storage system in the embodiment of the present application. As shown in fig. 3, the implementation flow of the data reading step includes:

and step21, determining a fault data unit and a fault address according to the information recorded in the fault recording unit.

In this embodiment, in order to analyze the cause of the fault, analysis and judgment need to be performed according to data recorded when the fault occurs. Based on the information recorded in the failure recording unit, failure data corresponding to the information is read from the data storage unit. In this step, a failure data unit and a failure address, which store failure data when a failure occurs, are determined based on information recorded in the failure recording unit. The failure data unit is a data storage unit for recording the failure data, and the failure address is a first address for storing the failure data. In combination with the data storage step in this embodiment, when a fault occurs, that is, when the fault recording condition is satisfied, the main controller 1 writes fault data in a period of time before and after the fault occurs into the data storage unit, and completely stores the fault data; the number of the data storage unit storing the failure data and the address position of the failure data in the data storage unit, that is, the address information of the failure data is stored in the failure recording unit.

In this embodiment, when using the failure data, the main controller 1 reads the information of the failure recording unit, and determines the failure data unit and the failure address according to the information recorded by the failure recording unit. The method specifically comprises the following steps: extracting number information from the information recorded by the fault recording unit, determining a data storage unit for recording the fault data according to the corresponding relation between the number and each data storage unit, and determining the data storage unit as a fault storage unit; and extracting the address of the written data to be stored in the unit to be stored when the fault recording condition is met from the information recorded by the fault recording unit, and determining the address as a fault address for recording fault data when a fault occurs.

And step22, reading data with a specified length from the fault address of the fault data unit.

In this embodiment, when reading failure data, data of a specified length is read from the failure address of the failure data unit. When the main controller reads data, firstly, a data storage unit for storing fault data is determined, and secondly, the position of the fault data in the unit is determined. The failure data unit is a data storage unit for storing the failure data, and the failure address is a first address for storing the failure data. Data of a specified length, i.e. data within a certain time after the occurrence of the failure, may be read starting from the failed address of the failed data unit.

It is understood that a plurality of pieces of failure information may be recorded in the failure recording unit, and failure data corresponding to each piece of failure information is recorded in a different data storage unit. The fault information recorded by the recording unit corresponds to the data storage unit recording the fault data and the position of the data storage unit, and the corresponding mode is determined by the number and the address in the fault information, for example, if the number of the record in the first piece of fault information of the fault recording unit is 3, and the address is 0100H, the fault data corresponding to the first piece of fault information is stored in the data storage unit with the number of 3; in reading, reading is performed from the 0100H address of the data storage cell numbered 3, and data of a specified length is read as failure data of the first piece of failure information. It should be noted that, when storing, the failure data are sequentially stored in each data storage unit in a circular storage manner; therefore, when the data is read, the data does not reach the specified length when the tail address of the data storage unit is reached, and the data needs to be transferred to the first address of the data storage unit to start reading continuously. Each piece of fault information may include time for recording the piece of fault information, and the time for the fault data to occur may be determined by the time, so that the time, the sequence, the time interval, and other information for the fault data to occur may be determined.

To explain the technical solution of the present application in detail, the following description is provided for a specific application scenario of an embodiment of a vehicle motor controller fault information storage system:

the storage module 2 is a data storage with a large space, and the data storage is divided into a plurality of data storage units and a fault recording unit. The data storage unit stores fault data, and the fault recording unit records state information such as position and time of storing the fault data. In the application scenario, in order to completely store relevant data when a fault occurs, factors such as the length of each piece of fault data, the number of pieces of stored fault data, the size of a storage module and the like are comprehensively considered, the size of each data storage unit can be 16000 × 16 bits, and the size of a fault recording unit can be 2944 × 16 bits. The storage module is divided into 1 fault recording unit and 8 data storage units, and the serial number of the data storage units is 1-8. The main controller 1 writes status information of failure data to the data storage unit and failure data to the failure recording unit. Referring to fig. 4, fig. 4 is a step of storing and recording failure data in an application scenario of the present embodiment, as shown in fig. 4:

step11 begins. Writing data to the data storage unit after system power-on initialization or data storage switching, wherein in the first step, all data of the data storage unit are reset to 0. It should be noted that each data storage unit stores a set of failure data, and when the failure data is stored in the data storage unit, data storage needs to be switched, that is, data storage needs to be switched to another data storage unit to continue data storage.

Step12 data is cyclically written to the selected data storage unit. The main controller 1 cyclically writes the detected data as data to be stored in the selected data storage unit (i.e. the unit to be stored), i.e. the data is written from the head end of the data storage unit, and when written to the tail end of the data storage unit, it immediately switches back to the head end of the data storage unit to continue.

Step13 satisfies the fault condition. In writing data to the data storage unit, the main controller 1 determines whether a failure condition is satisfied, that is, whether a failure occurs. If the failure condition is not met, Step12 continues with the loop writing data in the data storage unit.

Step14 continues to store the data. After the failure condition is satisfied, data needs to be recorded in the data storage unit for a while, for example, data is continuously written for 1 second, so that data after the failure occurs is completely recorded.

Step15 records status information in the fault recording unit. After the fault condition is met, some state information of the fault data needs to be recorded, so that the data stored before and after the fault occurs can be found according to the state information. The information of the state information record may be a location where data is saved (information such as the number of data storage units, the first address and the last address of failure data), a failure time, and the like.

Step16 reselects the data storage cell storing the failed data and switches. And the fault occurs and after fault data storage and fault data state information recording are completed. And reselecting a new data storage unit, and then switching to the reselected data storage unit to continue recording and saving the data. Resetting the reselected data storage location and jumping to Step11 to continue the Step of sequentially completing the failed data storage recording.

With continuing reference to fig. 5, fig. 5 illustrates a step of reading failure data in an application scenario of the present embodiment, as shown in fig. 5:

step21 begins. And entering a data reading step, the main controller 1 communicates with a data center or handheld equipment through a CAN bus, a serial communication interface and the like to read data, and the read fault data is sent to the data center or the handheld equipment to realize fault analysis.

Step22 obtains a data read indication. And judging whether an instruction for reading fault data is received, wherein the data reading instruction can be information sent by a data center or handheld equipment, each data storage unit can store one piece of fault data, and the data reading instruction needs to indicate that the fault data at the time of reading is required. If no indication to read the fault data is received, the fault data storage step continues.

Step23 reads the counter as 0. And judging whether the reading counter is 0, if so, determining the storage position of the read fault data. If not 0, then the location of the fault data has been determined, STEP27 is taken for data read.

Step24 determines the data storage unit number. And determining the data storage unit where the read fault data is located. And determining the data storage unit where the current fault data is located according to the serial number of the current fault data in the state information of the fault recording unit. In the fault recording unit, the fault indicated by the state information of the latest fault record is the first fault; and the fault indicated by the state information recorded in the near-second fault is the second fault, and so on. If data is stored in the order of the number sizes of the data storage units when data is stored, accordingly, when reading defective data, the reading order of the data storage units may be determined in the reverse order of the number sizes.

Step25 determines the failure data head address. And determining the position of the current fault data in the data storage unit according to the initial address indicated by the state information of the current fault record in the fault recording unit.

Step26 reads the counter set to 1. The specific position of the fault data read at this time is determined by Step24 and Step25, and the reading counter is set to 1, so that the fault data can be read.

Step27 reads the data. The master controller reads the fault data from the address location determined by Step24 and Step 25. When data is read, data in a period of time before and after a fault can be read according to preset reading logic, and reading of a group of fault data is completed. For example, the data stored 2 seconds from the first address of the current failure is the failure data of the current failure.

Step28 completes the data read. Whether the current fault data is completely read is judged, for example, whether the reading time is up can be judged in a timing mode, and whether the data reading is finished is determined.

The application scenario of the embodiment of the application explains the storage and reading processes of the fault data, and the data related to the required fault before and after the occurrence moment can be stored in real time within the full life range of the main controller, so that the timeliness and comprehensiveness of storing the fault data are greatly improved.

Compared with the prior art, the method has the following beneficial effects:

under the condition of not increasing the capacity of the storage modules, the number of fault data storage is increased through reasonable distribution of the storage modules.

Through the built-in storage module of main control unit, can all preserve the relevant data around its emergence moment of required trouble in real time in main control unit life-span, greatly improve the timeliness and the comprehensiveness of trouble data preservation.

Due to the fact that the storage module is arranged in the main controller, data can be automatically stored in the operation process of the main controller, and labor cost of fault analysis is reduced.

When the fault feedback is received and the fault needs to be analyzed, the historical saved data can be read, the reading time is shortened, and the fault analysis efficiency is improved.

Because the storage positions of all groups of fault data are stored in the fault recording unit, the fault data can be directly hit according to the information recorded by the fault recording unit during reading, and the interference of invalid data is reduced.

When the main controller is initialized, working modes such as all fault continuous storage data and specific fault storage data can be set, and the application is flexible.

So far, the technical solutions of the present invention have been described in connection with the preferred embodiments shown in the drawings, but it is easily understood by those skilled in the art that the scope of the present invention is obviously not limited to these specific embodiments. Equivalent changes or substitutions of related technical features can be made by those skilled in the art without departing from the principle of the invention, and the technical scheme after the changes or substitutions can fall into the protection scope of the invention.

Claims

1. A motor controller failure information storage system for a vehicle, characterized by comprising: the main controller is in communication connection with the storage module, and writes fault data into the storage module or reads the fault data out of the storage module; the storage module comprises a fault recording unit and a plurality of data storage units; wherein the storage of the fault data is performed by a data storage step comprising:

storing the data to be stored in the selected unit to be stored, and judging whether the fault recording condition is met;

when the fault recording condition is met, recording the serial number of the unit to be stored and the address of the written data to be stored in the unit to be stored in the fault recording unit when the fault recording condition is met;

selecting the data storage unit to be subjected to data writing operation from the plurality of data storage units as the to-be-stored unit according to preset logic;

and after the first threshold time, resetting the newly selected unit to be stored, and continuing the data storage step.

2. The motor controller failure information storage system for a vehicle according to claim 1, further comprising a code that encodes each of the data storage units in advance and assigns a number corresponding to each of the data storage units.

3. The motor controller failure information storage system for vehicles according to claim 2, wherein said "storing data to be stored in a selected unit to be stored" includes:

and sequentially storing the data to be stored into the units to be stored from the first addresses of the units to be stored in a cyclic writing mode.

4. The motor controller failure information storage system for vehicles according to claim 3, wherein the data storage step further comprises:

when the fault recording condition is met, continuing to record the data to be stored in the unit block to be stored within the first threshold time.

5. The motor controller failure information storage system for a vehicle according to claim 1, further comprising a data reading step including:

determining a fault data unit and a fault address according to the information recorded in the fault recording unit, wherein the fault data unit is a data storage unit for recording the fault data, and the fault address is a first address for storing the fault data;

reading data of a specified length from the fail address of the fail data storage unit.

6. The motor controller failure information storage system for vehicles according to claim 5, wherein said "determining a failure data unit and a failure address from information recorded in the failure recording unit" includes:

extracting number information from the information recorded by the fault recording unit, and determining a data storage unit recording the fault data as the fault storage unit according to the corresponding relation between the number and each data storage unit;

and extracting the address of the written data to be stored in the unit to be stored when the fault recording condition is met from the information recorded by the fault recording unit, and determining the address as a fault address for recording fault data when the fault is detected.