TWI774406B - Component of electronic vehicle, data collecting system for electronic vehicle, and data collecting method for electronic vehicle - Google Patents

Abstract

A data collecting system including a component assembled in an electronic vehicle, a data collector connected to the component through a bus of the electronic vehicle, and a detecting server connected to the data collector is disclosed. The component collects different data from the electronic vehicle and performs different sending procedures respectively under different situations including: A normal sending procedure sends normal data to the bus based on normal frequency; A high-speed sending procedure starts collecting high-speed data and sending the same to the bus based on high-speed frequency after a condition is satisfied; and, A high-resolution sending procedure sends high-resolution data collected within a period of time before and after a malfunction occurs to the bus. The data collector collects these data from the bus. The detecting server analyses the data collected by the data collector for an engineer to review.

Description

Electric Vehicle Components, Electric Vehicle Data Collection System and Electric Vehicle Data Collection method

The present invention relates to electric vehicles, in particular to components in the electric vehicles, as well as an electric vehicle data collection system and an electric vehicle data collection method for collecting and analyzing the data of the parts.

Generally speaking, the car factory will collect the relevant data of the operation of the electric vehicle through the bus of the electric vehicle. However, car manufacturers usually only focus on problems related to large components in electric vehicles, so they only collect slow data such as bus fault codes. Due to the insufficient amount of collected data, low resolution and no time parameters, when an electric vehicle fails, there are usually only the customer's oral failure experience and low-resolution bus data. As a result, component manufacturers are often not able to analyze the cause of the failure when notified of the failure, and it is difficult to reproduce the failure directly.

The main purpose of the present invention is to provide an electric vehicle component, an electric vehicle data collection system and an electric vehicle data collection method, which can transmit the low-speed data, high-speed data and high-resolution data with absolute time information of components through a dynamic data transmission mechanism. The degree data are respectively sent to the bus of the electric vehicle, and then sent from the bus to the debug server, so that the engineers can obtain the effective data needed for analysis at the remote end in real time.

In order to achieve the above-mentioned purpose, the electric vehicle component of the present invention is disposed in the electric vehicle and connected to the bus of the electric vehicle, and includes: a communication unit, which continuously collects a component data of the electric vehicle component at a common frequency a general data in and executes a general data sending program to send the general data to the bus based on the general frequency; a condition judging unit records at least one set of trigger conditions, and judges whether the trigger is met based on the component data condition; a high-speed data collection unit, connected to the condition judgment unit and the communication unit, is triggered by the condition judgment unit to continuously collect a high-speed data in the component data at a high-speed frequency after the component data meets the trigger condition, and the component data The communication unit executes a high-speed data sending program to send the high-speed data to the bus based on the high-speed frequency, wherein the high-speed frequency is higher than the normal frequency; a storage unit is connected to the communication unit; a high-resolution data collection unit, Continuously collect and temporarily store a high-resolution data in the component data; an error diagnosis unit, connected to the high-resolution data collection unit, determines whether a fault occurs based on the component data; and a timing unit, connected to the high-resolution a data collection unit, wherein the temporarily stored high-resolution data includes time information provided by the timing unit, and the time information records a standard time; Wherein, the high-resolution data collection unit is connected to the storage unit, and is triggered by the error diagnosis unit when the fault occurs to store the currently temporarily stored and subsequently collected high-resolution data to the storage unit, and the communication unit executes A high-resolution data sending program is used to send the high-resolution data stored in the storage unit to the bus with respect to the time when the fault occurs, before and after a certain period of time.

In order to achieve the above object, the electric vehicle data collection system of the present invention includes: a component, disposed in an electric vehicle and connected to a bus of the electric vehicle, the component executes a general data transmission procedure, a high-speed data transmission program or a high-resolution data sending program, wherein the general data sending program continuously collects a general data in a component data of the electric vehicle, and sends the general data to the bus based on a general frequency, wherein the high speed data The sending program starts to collect a high-speed data in the component data after the component data meets a trigger condition, and sends the high-speed data to the bus based on a high-speed frequency higher than the normal frequency, wherein the high-resolution data sending program Continuously collect and temporarily store a high-resolution data in the component data, store the currently temporarily stored and subsequently collected high-resolution data with a time information in a storage unit when a fault occurs, and store the The high-resolution data stored in the unit relative to the time when the fault occurs, before and after a certain period of time is sent to the bus; a data collector is connected to the bus and performs full sampling of a bus data on the bus , wherein the data collector has a timing unit, a first communication unit and a processing unit, the timing unit is connected to an NTP server through the first communication unit to obtain time information, and the processing unit associates the bus data with the The obtained time information is correlated to generate an upload data, wherein the bus data includes at least one of the general data, the high-speed data and the high-resolution data; and A debug server communicated with the first communication unit of the data collector to receive the uploaded data, the debug server has an error database and a diagnosis unit, and the error database stores a plurality of fault patterns , the diagnosing unit compares the uploaded data with the plurality of fault patterns and displays a comparison result in real time.

In order to achieve the above-mentioned purpose, the data collection method of an electric vehicle of the present invention is applied to an electric vehicle data collection system, wherein the electric vehicle data collection system includes a component disposed in an electric vehicle, and the electric vehicle data collection system A data collector communicatively connected with the component and a debug server communicatively connected with the data collector, the electric vehicle data collection method includes: a) the component continuously collects the general information in the component data data, and execute a general data sending program to send the general data to the bus based on a general frequency; b) the component determines whether a trigger condition is met based on the component data; c) the component meets the trigger condition when the component data meets the trigger condition Then continue to collect a high-speed data in the component data, and execute a high-speed data sending program to send the high-speed data to the bus based on a high-speed frequency, wherein the high-speed frequency is higher than the normal frequency; d) The component continues to collect and Temporarily store a high-resolution data in the component data; e) the component determines whether a fault has occurred based on the component data; f) the component stores the high-resolution data currently temporarily stored and subsequently collected when the fault occurs to a storage unit; g) after the step f, the component executes a high-resolution data sending program to send the high-resolution data stored in the storage unit relative to the time when the fault occurs, before and after a certain period of time onto the bus, wherein the high-resolution data includes a time information that records a standard time; h) the data collector performs full sampling of a bus data on the bus, wherein the bus data includes the general data , at least one of the high-speed data and the high-resolution data; i) the data collector correlates the sampled bus data with the standard time to generate an upload data; j) the debug server receives the upload data from the data collector; and k) the debug server Compare the uploaded data with a plurality of pre-stored fault patterns, and display a comparison result in real time.

Compared with the related art, the present invention enables the components of the electric vehicle to release different data to the bus in different ways according to different situations, thereby respectively transmitting low-speed data, high-speed data and high-resolution data with absolute time information, and can be optimized. The load status of the bus. In addition, the present invention can flexibly set the triggering conditions of the data collection action and the transmission action of the component, thereby facilitating the acquisition of effective information required by the engineer for analysis. In addition, through the synchronous collection, analysis and display of data at the remote end by the debug server, engineers can also analyze the component data and the cause of the failure in real time when the component fails.

In addition, the present invention allows engineers to directly send corresponding control commands to the data collector after analysis at the remote end to adjust the specified components, thereby assisting the engineers to directly control the Parts of the electric vehicle were faulty repaired.

1: Collection system

2: Electric vehicle

20: Memory

21: Components

211: Component communication unit

212: Condition judgment unit

213: High Speed Data Collection Unit

214: High Resolution Data Collection Unit

215: Error diagnostic unit

216: Parts Storage Unit

217: Timing Unit

22: Bus

23: General Information

24: High Speed Data

25: High Resolution Data

3: Data Collector

31: Processing unit

32: The first communication unit

33: School hours unit

34: Second communication unit

35: Collection Unit

36: Collector Memory

37: Collector storage unit

4: Debug server

41: Server communication unit

42: Server storage unit

43: Decoding unit

44: Diagnostic unit

45: Human Machine Interface

46: Error database

5: Engineering staff

6: NTP server

C1: Control command

S10~S17: Time proofreading steps

S20~S36, S40~S60: Data collection steps

FIG. 1 is a specific embodiment of a block diagram of an electric vehicle data collection system of the present invention.

Figure 2 is a specific embodiment of a block diagram of the components of the present invention.

FIG. 3A is a specific embodiment of a schematic diagram of a first data change rate of the present invention.

FIG. 3B is a specific embodiment of a schematic diagram of the second data change rate of the present invention.

FIG. 4 is a specific embodiment of the block diagram of the data collector of the present invention.

FIG. 5 is a specific embodiment of a time series schematic diagram of the present invention.

FIG. 6 is a specific embodiment of a block diagram of a debug server of the present invention.

FIG. 7A is a schematic diagram of a general data packet.

FIG. 7B is a schematic diagram of a data packet of the present invention.

FIG. 8 is the first part of the specific embodiment of the data collection flow chart of the present invention.

FIG. 9 is the second part of the specific embodiment of the data collection flow chart of the present invention.

Hereinafter, a preferred embodiment of the present invention will be described in detail in conjunction with the drawings.

As mentioned above, in order to solve the problems of insufficient resolution of the collected data, lack of corresponding time information, long processing time for fault analysis and troubleshooting, and difficulty for engineers in the laboratory when testing electric vehicles The problem of directly reproducing the fault and needing to go to the scene to carry out the fault analysis, etc., the invention discloses a novel data collection system of the electric vehicle.

Please refer to FIG. 1 , the collection system 1 of the electric vehicle of the present invention (hereinafter referred to as the collection system 1 in the description) can be mainly applied to various electric vehicles 2 , including livelihood vehicles (such as electric vehicles, electric locomotives) , electric bicycles, etc.) and industrial vehicles (such as stackers). Specifically, the collection system 1 of the present invention can respectively collect and transmit different data of one or more components 21 in the electric vehicle 2 with different frequencies based on different situations. Through the dynamic data collection/transmission mechanism, engineers are assisted to obtain effective information in real time when the electric vehicle 2 fails, so that the failure can be reproduced and analyzed quickly and accurately, thereby speeding up the troubleshooting.

The collection system 1 at least includes at least one component 21 disposed in the electric vehicle 2 , a data collector 3 that is connected in communication with the component 21 in the electric vehicle 2 and collects data sent by the component 21 , and a data collector 3 . The debug server 4 that communicates with and receives the data collected by the data collector 3 . In one embodiment, the data collector 3 and the component 21 can be arranged in the same position (eg, inside the electric vehicle 2 ), so that the detection The error server 4 can be installed at a distance, and the engineer 5 can directly view the data collected by the data collector 3 through the error detection server 4 .

The component 21 is arranged in the electric vehicle 2 and is connected to the bus 22 on the electric vehicle 2 . In one embodiment, the component 21 may be a motor, a driver, a battery, a meter or other electronic components in the electric vehicle 2 that can be modified by firmware to meet the requirements of the collection system 1 of the present invention. The bus 22 can be, for example, a CAN bus using a Controller Area Network (CAN) protocol as a bus communication protocol. Each component 21 of the electric vehicle 2 can send their respective component data to the bus 22, whereby basic communication can be performed between the various components 21 through the bus 22, and the data related to these basic communications is defined as the component data. normal information. The above are only some specific embodiments of the present invention, but are not limited thereto.

The data collector 3 is a component with a processing unit, which is coupled to the bus 22 of the electric vehicle 2, collects the data of the electric vehicle 2 and the component 21 by transmitting electronic signals, and can transmit control Command to electric vehicle 2.

The debug server 4 can communicate with the data collector 3 in a wired or wireless manner. In one embodiment, the debug server 4 is an electronic device that can be directly connected to the data collector 3 through a cable, a data transmission line, a telephone line or a network line, such as a personal computer (PC), an industrial computer (Industrial Computer) PC, IPC), notebook computer (Laptop), tablet computer (Tablet), smart phone (Smart Phone), rack server, etc., but not limited. In another embodiment, the debug server 4 is a remote server or a cloud server that can wirelessly connect to the data collector 3 through the Internet (Internet) or Local Area Network (LAN). Not limited.

In the present invention, the component 21 is modified by the firmware, and can execute the general data transmission procedure, the high-speed data transmission procedure and the high-resolution data transmission procedure respectively in different situations. In the different procedures described above, the component 21 collects different data based on different frequencies, and rate to send different data to the bus 22 of the electric vehicle 2, thereby realizing the technical solution of dynamic data sending.

Generally speaking, after the electric vehicle 2 is powered on, the component 21 can continuously sample the component data from the electric vehicle 2 to obtain various data required by the component 21 . It is worth mentioning that the component data may be the data of the component 21 itself or the data of other components 21 . For example, as a component, the driver can collect relevant data of the driver itself from the electric vehicle 2 , and can also collect relevant data of the battery. In this embodiment, the battery is another component on the electric vehicle 2 .

When the component 21 executes the general data sending procedure, it continuously samples the content of the predefined general data from the component data based on the general frequency, and continuously sends the general data to the bus 22 based on the general frequency. In other words, when executing the general data sending procedure, the sampling frequency of the component 21 for general data is the same as the sending frequency for general data. It is worth mentioning that different components 21 may have different general data to be sampled, such as drivers and batteries, so the general frequencies used by different components 21 may also be different from each other. In one embodiment, the general data refers to data required for basic communication between the various components 21, but not limited thereto.

When the component 21 executes the high-speed data sending program, it continuously judges whether the preset at least one trigger condition is satisfied based on the component data, and when the trigger condition is satisfied, it starts to define as defined in the component data based on the high-speed frequency. The data of the data to be collected (hereinafter referred to as high-speed data) is sampled, and the collected high-speed data is sent to the bus 22 based on the high-speed frequency. In this embodiment, the high-speed frequency is higher than the general frequency, and both the high-speed frequency and the general frequency are lower than the upper limit of the transmission capacity of the bus 22 .

In one embodiment, before executing the high-speed data sending procedure, the component 21 mainly continuously collects specific variables in the component data, and compares the specific variables with the preset thresholds recorded in the trigger conditions, thereby determining whether the trigger conditions are not. satisfied. It is worth mentioning that in this embodiment, the components 21 will not collect the high-speed data before the trigger condition is satisfied, so it can avoid wasting the computing resources of the component 21, and can reduce the transmission load of the bus 22 at the same time.

In the present invention, after the electric vehicle 2 is powered on, the component 21 will continue to collect data of the component data with a high rate of change that is defined as high-resolution data (hereinafter referred to as high-resolution data), and the high-resolution data will be collected. The data is temporarily stored in the temporary register (not shown in the figure) of the component 21, waiting to be sent. The above-mentioned high-resolution data defined in the present invention has a high rate of change. If the above-mentioned temporary storage mechanism is not used and the high-resolution data is directly sent to the bus 22, the amount of data sent per unit time will exceed the processing capacity of the bus 22. In addition, the load of the bus 22 will be greatly increased, so that the bandwidth of the bus 22 is insufficient, thereby causing communication failure between components. In the present invention, when the component 21 executes the high-resolution data sending program, it is mainly based on the component data to continuously judge whether at least one predefined fault occurs, and when judging the occurrence of the fault, it immediately sends the All high-resolution data is written into the storage unit of the component 21 (eg, the component storage unit 216 shown in FIG. 2 ). Moreover, the component 21 continues to collect high-resolution data from the component data after the failure occurs, and continues to write into the storage unit.

In the present invention, when the component 21 writes the high-resolution data into the register and/or the storage unit, it simultaneously records the sampling time of the high-resolution data. After the storage unit is written, the component 21 sends all the high-resolution data with sampling time information stored in the storage unit to the bus 22 together.

As mentioned above, high-resolution data refers to the high rate of change data in the component data, and this data is of great help in the analysis of the cause of failure. However, in order to reduce the load on the bus 22 and avoid data loss, the high-resolution data sending procedure of the present invention pre-collects the high-resolution data and stores it in the register/storage unit. Since the sending time of high-resolution data is later than the collection time, it is necessary to add the correct sampling time information when writing to the register/storage unit, so as to maintain the referenceability of the data and the reproducibility of the fault.

Through the high-resolution data sending program, the component 21 can send all the high-resolution data stored at the time of the failure, within a certain period of time before the failure, and within a certain period of time after the failure to the bus 22. The amount of high-resolution data is sufficient, and the correct sampling time information is recorded, so that the engineer 5 can reproduce the fault in a specific time range through the high-resolution data, thereby effectively analyzing the cause of the fault.

The data collector 3 is communicatively connected to the bus 22 of the electric vehicle 2 , and performs full sampling of the bus data, that is, the data collector 3 obtains all the bus data transmitted on the bus 22 . The bus data refers to all data sent by each component 21 to the bus 22, including the general data, high-speed data and high-resolution data, but not limited thereto.

It is worth mentioning that the bus 22 of the electric vehicle 2 of the present invention can be configured with one or more connection ports, and can be connected to one or more data collectors 3 at the same time. In this way, the engineer 5 can perform different analysis procedures through different data provided by different data collectors 3 according to requirements.

In one embodiment, the data collector 3 can obtain correct time information from an external server (such as the NTP server 6 shown in Upload data in packet format. In the present invention, the data collector 3 generates and transmits the uploaded data immediately after collecting the bus data.

In one embodiment, the debug server 4 is wired or wirelessly connected to the data collector 3 , and receives the upload data sent by the data collector 3 . The database of the debug server 4 (eg, the error database 46 shown in FIG. 6 ) can store a variety of predefined failure modes and parameter ranges corresponding to these failure modes. After the error detection server 4 receives the uploaded data, it can decode the uploaded data to obtain the original physical quantity information of the component 21, and after comparing with the various failure modes, the comparison result can be displayed to the engineer 5 in real time. References (eg displayed as faulty, no fault or impending fault, etc.).

Through the collection system 1 of the present invention, the engineer 5 can directly obtain the original physical quantity information of the component 21, the possible failure mode, the failure time, and the high resolution of the component 21 in the period before and after the failure from the debugging server 4 Therefore, the engineer 5 can easily reproduce the fault, analyze the cause of the fault, and then directly repair the fault from the remote end.

As mentioned above, the collection system 1 of the present invention is mainly composed of one or more components 21 in the electric vehicle 2 , the data collector 3 connected to the electric vehicle 2 , and the debug server 4 connected to the data collector 3 . composition. The components of the collection system 1 will be described in detail below with reference to the drawings.

Referring to FIG. 2, the component 21 of the present invention is composed of hardware and firmware, wherein the hardware part is the same as or similar to the components of the general electric vehicle, including the processor (not shown), the memory 20, the component communication The unit 211, the component storage unit 216 and the timing unit 217, the firmware part is recorded in the processor and executed by the processor. One of the technical features of the present invention is that the firmware part of the component 21 is customized and logically divided into a condition judgment unit 212 , a high-speed data collection unit 213 , a high-resolution data collection unit 214 and an error diagnosis unit according to the execution function. 215 and other firmware units.

In the present invention, the component 21 continuously collects the general data 23 in the component data through the component communication unit 211 at a normal frequency, and in the first type of situation (eg, normal operation), the component 21 continuously executes the general data through the component communication unit 211. A sending program to send the general data 23 to the bus 22 of the electric vehicle 2 based on the general frequency. General data 23 are common, for example, the bus communication protocol defined by the customer (such as the KWP2000 protocol), the specific function or mechanism commands (such as light switch or use) issued by the upper control component to the controlled component (such as controlling a motor with a driver), the component itself Physical quantities with a low rate of change or low sampling rate can meet the needs of judgment data (such as battery power percentage, fault code, drive on/off command, peripheral component status such as tripod not received, storage compartment not closed, brake signal, etc. ).

In the second case (for example, a special case), the component 21 can be pre-defined by the manufacturer or the engineer 5 to define one or more data to be collected (that is, the high-speed data 24 that needs to be collected under special conditions), However, the high-speed data is not directly collected and transmitted through the component communication unit 211 for the time being twenty four. In this embodiment, the high-speed data 24 refers to the bus information (such as battery voltage, motor current or voltage, etc.) provided according to the predictive error detection requirement before the error occurs, and the physical quantity of the component itself has a high rate of change or needs to be higher. Only the sampling rate can meet the data required for judgment (such as motor speed changes, encoder angle changes, and protection-related physical parameters such as current, voltage, torque, temperature changes, etc.).

In this embodiment, the component 21 continuously collects component data through the condition judging unit 212 , and judges whether the component data complies with one or more trigger conditions preset in the condition judging unit 212 . Specifically, the condition judging unit 212 may pre-record one or more triggering conditions through the setting of the manufacturer or the engineer 5 . When any triggering condition is satisfied, it means that the component 21 may have a problem, or a problem is about to occur. Therefore, when the condition judging unit 212 judges that at least one trigger condition is satisfied based on the component data, it will issue a start command to the high-speed data collecting unit 213 . In practical applications, the electric vehicle driver and the motor can be set with corresponding temperature thresholds, so that the failure can be pre-determined based on the temperature. Specifically, a threshold value can be set for the negative temperature coefficient (NTC) signal, and when the feedback value of the NTC signal is greater than the set value, the collection of specific physical quantities or parameters is started. Before the electric vehicle will fail due to the influence of temperature, the high-speed data 24 can be collected to make a pre-judgment whether it fails. For example, an intelligent power module (IPM) temperature warning threshold can be set to 95°C, a motor temperature warning threshold to 125°C, and a capacitor temperature warning threshold to 120°C. Although the fault code will not be released immediately when the temperature of these components exceeds these warning thresholds, it also means that the working temperature of the components is too high and may fail. It is necessary to find out the cause of the possible failure and prevent it, so it is necessary to conduct high-speed data 24 is collected to aid judgment.

The high-speed data collection unit 213 is connected to the condition determination unit 212 and the component communication unit 211 . After receiving the activation command, the high-speed data collection unit 213 will first read the content of the activation command, and start to collect the high-speed data 24 specified in the activation command based on the high-speed frequency. In this embodiment, after the high-speed data collection unit 213 starts to collect the designated high-speed data 24, the component communication unit 211 starts to execute the high-speed data sending procedure to send the high-speed data 24 to the bus 22 based on the high-speed frequency. Wherein, the high-speed frequency is higher than the general frequency used in the general data transmission procedure.

In the third type of situation (eg, a failure situation), the component 21 pre-collects predefined specific data (ie, the high-resolution data 25 ) from the component data through the high-resolution data collection unit 214, and temporarily It is stored in a temporary register (not shown in the figure) inside the component 21 . In one embodiment, the high-resolution data collection unit 214 mainly writes the high-resolution data 25 into the register sequentially in a first-in-first-out (FIFO) manner, and when the register is When full, older data are preferentially deleted to maintain the applicability of the data.

In detail, the high-resolution data 25 includes bus data (such as overcurrent, overvoltage) defined according to the debug requirements when the error occurs, the physical quantity of the component itself with a very high rate of change, or a very high sampling rate to satisfy the judgment. Required data (such as quadrature axis current, direct axis current, torque command, etc.).

The error diagnosis unit 215 is connected to the high-resolution data collection unit 214 , the component storage unit 216 is connected to the high-resolution data collection unit 214 and the component communication unit 211 , and the timing unit 217 is connected to the high-resolution data collection unit 214 .

In this embodiment, the component 21 continuously collects component data through the error diagnosis unit 215, and determines whether one or more predefined faults occur based on the component data. When the fault diagnosis unit 215 determines that a fault occurs, it will issue a start command to the high-resolution data collection unit 214 . After receiving the activation command, the high-resolution data collection unit 214 stores all the high-resolution data 25 in the current register to the component storage unit 216 . At the same time, the high-resolution data collection unit 214 continuously collects the high-resolution data 25 and stores the data in the component storage unit 216 synchronously.

In practical applications, for example, the IPM temperature fault threshold can be set to 100°C, the motor temperature fault threshold to 130°C, and the capacitor temperature fault threshold to 125°C. These fault thresholds are higher than the above-mentioned early warning thresholds, so when these components continue to heat up and exceed these fault thresholds, the system will release fault codes such as OH1, OH2, OH3, etc. respectively. Based on these fault codes, the relevant person can know which part the fault occurred in. In addition, according to the high-resolution data 25 collected at the time of the occurrence of the failure, before and after a period of time, the cause of the failure and overheating of the component can be determined.

Take the judgment of the overcurrent fault of the electric vehicle driver as an example. In this embodiment, the fault threshold of the driver current can be set to 212A-rms, where A represents ampere and rms represents the root mean square. Since the factors that cause overcurrent faults are high-frequency changes, the collection of high-resolution data 25 is required to obtain richer information. When the current detection value of the motor exceeds the fault threshold, the system can issue an OCN fault code. According to this fault code, it can be judged as an overcurrent fault. In this way, according to the high-resolution data 25 collected at the time of the occurrence of the fault and a period of time before and after the occurrence of the fault, the cause of the overcurrent fault, such as wrong operation steps or component failure, can be determined.

When the component storage unit 216 reaches a certain threshold (for example, it is full), the component 21 executes the high-resolution data sending procedure through the component communication unit 211 to send all the high-resolution data 25 stored in the component storage unit 216 to the bus 22 on. Through the above-mentioned means of pre-data collection, temporary storage, storage and failure-delayed transmission, the high-resolution data 25 sent by the component communication unit 211 to the bus 22 includes the time when the failure occurred, a specific period of time before the failure occurred, and the occurrence of the failure. Complete data stored for a specified period of time thereafter.

Specifically, the high-resolution data 25 referred to in the present invention refers to data whose rate of change is higher than the upper limit of the transmission capacity of the bus 22 . If the high-resolution data 25 is sent to the bus 22 through a general sending process, the high-resolution data 25 will be lost due to insufficient sampling frequency before the general sending process, and the data resolution will be reduced. In view of this, the present invention completely collects the high-resolution data 25 by means of data pre-collection and data temporary storage, and only sends the high-resolution data 25 stored at the time when the fault occurs, before and after a certain period of time to the bus. 22 on. It can be seen from this that the time information is very important for the high-resolution data 25 because the sending time of the high-resolution data 25 lags the collection time.

The timing unit 217 of the component 21 can obtain correct time information from the electric vehicle 2, the data collector 3 or other means, and the high-resolution data collection unit 214 stores the high-resolution data 25 in the register and/or the component When storing the unit 216, the corresponding time information will be entrained at the same time. As such, always The high-resolution data 25 sent on the line 22 also includes time information, which helps the engineer 5 to know the actual occurrence time of the fault, so as to enhance the accuracy of judgment.

The component 21 also includes a memory 20 connected to the component communication unit 211 , the condition determination unit 212 , the high-speed data collection unit 213 , the high-resolution data collection unit 214 and the error diagnosis unit 215 . In the present invention, the memory 20 fully samples and records the component data in the electric vehicle 2 at an ultra-high-speed frequency that is much higher than the general frequency and the high-speed frequency. It is worth mentioning that the ultra-high-speed frequency is much higher than the upper limit of the transmission capacity of the bus 22. Therefore, no matter whether the component 21 executes the general data transmission procedure, the high-speed data transmission procedure or the high-resolution data transmission procedure, the data recorded in the memory 20 will not be affected. All can meet the collection and delivery requirements of the component 21 .

The memory 20 records all the component data related to the component 21 . In an embodiment, the component communication unit 211 can collect the general data 23 in the component data from the memory 20 , and the condition determination unit 212 can obtain the general data 23 from the memory 20 . The high-speed data collection unit 213 can collect the high-speed data 24 in the component data from the memory 20 , and the high-resolution data collection unit 214 can collect the component data from the memory 20 In the high-resolution data 25 in the memory, the error diagnosis unit 215 can collect component data from the memory 20 to determine whether a fault occurs.

For example, the condition judging unit 212 can collect the first variable in the component data from the memory 20, and when the first variable reaches a preset specific threshold, determine that the component data meets the triggering condition and start the high-speed data sending process. For example, if the aforementioned motor temperature is used as the first variable and exceeds the temperature warning threshold of 125°C, the condition determining unit 212 determines that the temperature meets the triggering condition and starts the high-speed data sending process.

For another example, the error diagnosis unit 215 can collect the component data from the memory 20, compare the second variable in the component data with a plurality of preset fault parameters one by one, and judge the fault based on whether the comparison result is consistent. If it occurs, then start the high-resolution data sending program when it is judged that the fault occurs. For example, when the motor temperature continues to rise and exceeds the temperature fault threshold of 130°C, the fault diagnosis The element 215 releases the OH2 fault code accordingly, and uses the fault code as the second variable and compares it with multiple fault parameters (such as OH1, OH2, OH3...), thereby judging that it corresponds to a fault that the motor temperature is too high. Or, when the driver current exceeds the fault threshold 212A-rms, the error diagnosis unit 215 releases the OCN fault code accordingly, and compares the fault code with a plurality of fault parameters (eg OVN, OCN . This judgment corresponds to the occurrence of an overcurrent fault. However, the above are only some specific embodiments of the present invention, but not limited thereto.

Please refer to FIG. 3A and FIG. 3B at the same time, the schematic diagram (a) of FIG. 3A shows the change trend of the original variables of the component 21 over time, and the schematic diagram (b) of FIG. 3A shows the component 21 through the general data sending procedure. The change trend of the variables sent over time, the schematic diagram (c) of FIG. 3B shows the change trend of the variables sent by the component 21 through the high-speed data transmission program with time, and the schematic diagram (d) of FIG. 3B shows the component 21 Change trends of variables sent by the high-resolution data sending program over time.

As shown in the schematic diagram (b) of FIG. 3A , the sampling period of the general data 23 sent by the general data sending program is about 100 ms, which can only show the trend of the data. As shown in the schematic diagram (c) of FIG. 3B , the sampling period of the high-speed data 24 sent by the high-speed data sending program is about 1 ms, and the curve of the general data can present more details. As shown in the schematic diagram (d) of FIG. 3B , the sampling period of the high-resolution data 25 sent by the high-resolution data sending program is about 200 μs, and the curve relative to the high-speed data can show more subtle changes. According to different requirements, the data of different rate of change is obtained by sampling in different cycles, which can reduce the workload of the bus when sending, and can also meet the needs of engineers to determine the cause of the fault.

As shown in the schematic diagram (a) of FIG. 3A , the sampling rate of the original variables of the component 21 (ie, the frequency at which the memory 20 collects component data from the electric vehicle 2 ) is much larger than that of the general data transmission process, the high-speed data transmission process, and the The frequency used by the high-resolution data sending process. Therefore, no matter what frequency the general data transmission process, the high-speed data transmission process, and the high-resolution data transmission process use to transmit To send data, the memory 20 can meet the requirements of the component 21 . In this way, the present invention can surely achieve the purpose of enabling the component 21 to perform a dynamic data transmission mechanism.

4, the data collector 3 of the present invention may mainly include a processing unit 31, a first communication unit 32, a timing unit 33, a second communication unit 34, a collection unit 35, a collector memory 36, and a collector storage Unit 37.

The processing unit 31 may be, for example, a processor (Processor), a Micro Control Unit (MCU), a System on Chip (SoC), or a Programmable Logic Controller (PLC). The first communication unit 32 and the second communication unit 34 can be integrated together, or can be two independent units, and can be a wired communication unit (such as a bus connector) or a wireless communication unit (such as Wi-Fi, Bluetooth , RF or Zigbee and other communication protocols), but not limited.

In one embodiment, the data collector 3 is connected to the external Network Time Protocol (NTP) server 6 and the debug server 4 through the first communication unit 32 , and is connected to the electric vehicle through the second communication unit 34 2, and the timing unit 33 is connected to the first communication unit 32 and the second communication unit 34. In this embodiment, the time calibration unit 33 can obtain correct time information from the NTP server 6 through the first communication unit 32 after the data collector 3 is activated. In addition, the timing unit 33 sends the time information to one or more components 21 in the electric vehicle 2 through the second communication unit 34, whereby each component 21 can use the internal timing mechanism ( For example, the timing unit 217 shown in FIG. 2 is used to maintain the correctness of the time, and to make the multiple components 21 in the electric vehicle 2 maintain the consistency of the time.

The processing unit 31 is connected to the first communication unit 32 , the second communication unit 34 , the collection unit 35 , the collector memory 36 and the collector storage unit 37 , and the collection unit 35 is connected to the second communication unit 34 . In one embodiment, the collecting unit 35 samples all the bus data on the bus 22 of the electric vehicle 2 through the second communication unit 34 , and temporarily stores the bus data in the collector memory 36 . In this embodiment, the data collector 3 fully samples the data on the bus 22, so the obtained bus data will be complete It includes the general data 23 , the high-speed data 24 and the high-resolution data 25 sent to the bus 22 by the various components 21 in the electric vehicle 2 according to different procedures.

The processing unit 31 associates the bus data in the collector memory 36 with the obtained time information, so as to generate the upload data with a time stamp and conforming to a specific transmission format, and then transmit the upload data to the external through the first communication unit 32. Debug server 4.

It is worth mentioning that, in order to enable the engineer 5 to obtain the relevant information of the electric vehicle 2 on the debug server 4 synchronously, in the general embodiment, the data collector 3 will immediately pass the first communication unit 32 after sampling. The uploaded data is sent to the debug server 4 . However, if there is a problem with the transmission path (eg, poor network communication, damaged connection line, etc.), the processing unit 31 will first store the uploaded data in the collector storage unit 37 . In addition, after the problem is eliminated (for example, the network signal returns to normal, the connection cable is replaced, etc.), the processing unit 31 reads the uploaded data stored in the collector storage unit 37 and transmits it to the debugger through the first communication unit 32 Server 4. It is worth mentioning that the collector memory 36 and the collector storage unit 37 can also be integrated together.

It is worth mentioning that, although the timing unit 217 shown in FIG. 2 may be provided in the component 21 of the present invention, due to the design consideration of the electric vehicle 2 itself, the timing unit 217 may not be able to keep the timing unit 217 even after the power is turned off. Real-time clock (Real-Time Clock, RTC) timer that operates continuously. In this case, the component 21 loses absolute time information every time the electric vehicle 2 is powered off. In view of this, the collection system 1 of the present invention provides the correct time information of the component 21 by the time calibration unit 33 of the data collector 3 .

Please refer to FIG. 5 at the same time. In FIG. 5, the electric vehicle 2 includes two parts 21 (including the first part and the second part) as an example for description, but the collection system 1 of the present invention does not include the two parts 21. The examples are limited.

First, the data collector 3 sends a time information request to the NTP server 6 through the first communication unit 32 (step S10 ). After the NTP server receives the request, it immediately responds with the standard time to the data The collector 3 (step S11 ), and the data collector 3 sets the standard time as the system time of the data collector 3 through the timing unit 33 .

After the system time setting is completed, the data collector 3 performs time setting for the components 21 on the bus 22 one by one. Specifically, the data collector 3 sends the system time to the first component through the second communication unit 34 (step S12). After the first component receives the system time, the timing unit 217 completes the internal time setting, and returns the current time to the data collector 3 for confirmation (step S13 ).

After the setting of the first component is completed, the data collector 3 then sends the system time to the second component through the second communication unit 34 (step S14). If no reply is received from the second component within a certain period of time (for example, one second) after sending, or the second component returns an incorrect time, the data collector 3 resends the system time to the second component (step S15 ). . In one embodiment, when the data collector 3 resends the system time to the second component twice (step S15 and step S16 ), and neither receives a reply or receives the wrong time, it determines that the second component is abnormal.

When it is determined that the second component is abnormal, the data collector 3 sends an abnormality report to the debugging server 4 through the first communication unit 32 to notify the debugging server 4 that the time setting of the second component is abnormal (step S17 ).

However, the above is only one of the specific implementation examples of the present invention, the data collector 3 of the present invention can actually set the time of the components 21 in the electric vehicle 2 through a variety of different setting methods. The setting method is limited.

Please continue to refer to FIG. 6 , the debug server 4 of the present invention is an electronic device composed of hardware and firmware, such as a personal computer, a notebook computer, a tablet computer, a smart phone, an industrial computer or a cabinet-type servo device, etc. Among them, the hardware part of the debug server 4 is the same as or similar to the components of general electronic devices, mainly including a processing unit (not shown in the figure), a server communication unit 41, a server storage unit 42, a man-machine interface 45 and an error The database 46, etc., the firmware part is recorded and executed by the processing unit Row. In the present invention, the firmware components of the debug server 4 are customized and logically divided into the decoding unit 43 and the diagnosis unit 44 according to the required functions, but not limited thereto.

The processing unit may be, for example, a processor, a microcontroller unit, a system-on-a-chip or a programmable logic controller for executing firmware to execute the corresponding functions of the decoding unit 43 and the diagnosis unit 44 . The server communication unit 41 may be a wired communication unit (eg, a connector) or a wireless communication unit (eg, a transmission module using a communication protocol such as Wi-Fi, Bluetooth, RF, or Zigbee). The error database 46 may be a memory inside the electronic device. The human-machine interface 45 can be any combination of interactive devices such as keyboard, mouse, display, touch screen, etc. on the electronic device that can interact with the user. However, the above are only specific embodiments of the present invention, but are not limited to the above.

In the present invention, the debug server 4 communicates with the data collector 3 through the server communication unit 41 to receive the uploaded data sent by the data collector 3 . The server storage unit 42 is connected to the server communication unit 41 for storing the uploaded data received by the server communication unit 41 .

The decoding unit 43 is connected to the server storage unit 42 for decoding the uploaded data, so as to restore the uploaded data to the real physical quantities of each component 21 in the electric vehicle 2, such as output voltage, output current, remaining battery capacity, motor Rotation angle, etc., but not limited to this. Wherein, since the time stamp is entrained in the uploaded data, the real physical quantity generated after decoding by the decoding unit 43 can effectively reflect the real information of each component 21 at each time point.

The diagnosis unit 44 is connected to the decoding unit 43 , the human-machine interface 45 and the error database 46 , wherein the error database 46 records one or more failure modes predefined by the engineer 5 , and the failure mode can be, for example, a specific failure Correspondence between codes and specific physical quantities. For example, the fault state can be, for example, "when the output voltage of the battery is less than the first threshold, the first fault code corresponding to the voltage is abnormal", "when the input current of the driver is greater than the second threshold, corresponding to the The second fault code represents abnormal current", etc., but not limited.

The specific fault codes, specific physical quantities and threshold values can be defined by the developers of each component 21 through experiments, and recorded in the error database 46 . If the researcher thinks that the above information or values need to be modified in order to improve the analysis quality of the diagnosis unit 44 and the accuracy of the analysis results, the error detection server 4 can be operated through the man-machine interface 45 to record the errors in the error database 46 . to add, delete or modify the fault state.

After the diagnosis unit 44 receives the decoded real physical quantity from the decoding unit 43, and compares the real physical quantity with a plurality of fault patterns in the error database 46, a comparison result is generated to present a preliminary analysis result, such as "fault occurs. ", "No fault" or "Failure imminent", etc.

It is worth mentioning that the electric vehicle 2 is equipped with multiple components 21, and the multiple components 21 may affect each other. Sometimes the A component is suspected to be faulty, but it is actually caused by a problem with the B component. In one embodiment, the data collector 3 can simultaneously collect data of a plurality of components 21 from the bus 22 and send the data to the debug server 4 synchronously. In this embodiment, the diagnosing unit 44 can perform synchronous analysis in combination with multiple sets of data of different components 21 , so as to more accurately determine the possible cause of the failure.

In one embodiment, the error detection server 4 can directly display the relevant information (ie, the real physical quantities) of each component 21 in the electric vehicle 2 through the man-machine interface 45 , and simultaneously display the preliminary analysis result of the diagnosis unit 44 . In this way, the engineer 5 can directly obtain all the data needed to reproduce the fault and analyze the cause of the fault from the man-machine interface 45 of the debugging server 4 . In addition, by synchronously displaying the preliminary analysis result of the diagnosis unit 44, the present invention can also assist the engineer 5 in interpreting the cause of the failure more quickly.

In the present invention, the general data 23 , the high-speed data 24 and the high-resolution data 25 are sent from each component 21 to the bus 22 , and the debug server 4 displays the real physical quantity and the comparison result through the man-machine interface 45 . The action can be completed in seconds. In this way, it is possible to effectively avoid the traditional problem that it is difficult for the engineer 5 to reproduce the fault based on the data obtained afterwards, and it is necessary to go to the location of the electric vehicle 2 to perform debugging and maintenance.

It is worth mentioning that, in an embodiment, the human-machine interface 45 can also be directly connected to the server communication unit 41 . Specifically, when the engineer 5 checks the relevant data of each component 21 through the man-machine interface 45 and thinks that the data needs to be modified or added, the man-machine interface 45 can be directly operated to make the error detection server 4 generate The corresponding control command C1 is sent to the data collector 3 through the server communication unit 41 .

In one embodiment, the control instruction C1 can record the ID of the component 21 that the engineer 5 thinks needs to be adjusted, and the content that needs to be adjusted. After receiving the control command C1, the data collector 3 can adjust the corresponding components 21 on the bus 22 according to the content of the control command C1. In this embodiment, the adjustment content recorded by the control command C1 may include, for example, the content of general data 23, high-speed data 24 or high-resolution data sent by the adjustment component 21, data sampling frequency or data transmission frequency of the adjustment component 21, modification of high-speed data The trigger conditions of the sending program, the modification of the fault parameters for judging whether the fault occurs, and the firmware of the updating component 21, etc., are not limited. The foregoing process may be referred to as Over-the-air programming (OTA for short). Through the technical solution of sending the control command C1 to the data collector 3 in reverse, the collecting system 1 of the present invention can allow the engineer 5 to simulate the working mode of visiting the electric vehicle 2 in person at the remote site to debug the electric vehicle 2 .

Referring to FIG. 7A , the current data collection method used by the components in the general electric vehicle is to always send all data to the bus regardless of whether an error occurs or not. Therefore, in addition to the basic communication packets between components (ie, similar to the general data 23 referred to in the present invention), each component also needs to add a large number of debug packets into the data packets. In this way, the bandwidth of the bus will be filled with the data continuously sent by each component, making the load of the bus remain high.

Moreover, because the load of the bus is extremely high, even if the data on the bus is collected by an additional data collector, the data collector cannot fully sample the bus, and must reduce the amount of data by partial sampling or compression. . In this way, the data obtained by the backend engineers through the data collector will be greatly reduced low-resolution data. As a result, when the electric vehicle fails At the time, it is difficult for back-end engineers to directly reproduce the fault from the remote end from these data, and analyze the cause of the fault.

In the collection system 1 of the present invention, each component 21 usually only needs to send basic communication packets (ie, general data 23) required for communication to the bus 22, and only when a preset trigger condition is satisfied (by the condition judging unit 212 ) When a fault occurs (diagnosed by the error diagnosis unit 215), the high-speed data 24 is sent at a high-speed frequency, or the high-resolution data 25 is sent at a specific frequency, accompanied by necessary error detection packets. And when the cut-off condition is met (ie, the trigger condition is no longer met, or the fault is eliminated), the component 21 stops sending the high-speed data 24 or the high-resolution data 25 . Thereby, the collection system 1 of the present invention can greatly reduce the number of debug packets transmitted on the bus 22, thereby reducing the load on the bus 2, and compared with the prior art, the data collector 3 can obtain a higher value from the bus 22. Resolution bus data.

Referring to FIG. 7B , the collection system 1 of the present invention greatly reduces the load on the bus 22 , so even if the data collector 3 performs full sampling on the bus 22 , the load on the data collector 3 will not be increased. In this way, the resolution and validity of the data can be effectively improved, and the debugging server 4 and the engineer 5 can be assisted to analyze the cause of the failure more effectively.

The present invention further discloses a data collection method for electric vehicles (hereinafter referred to as collection method in the specification), the collection method is mainly applied to the collection system 1 shown in FIG. The component 21 shown in FIG. 6 , the data collector 3 and the debug server 4 are realized.

Referring to FIG. 8 , to implement the collection method of the present invention, firstly, at least one component 21 disposed in the electric vehicle 2 continuously collects the general data 23 in the component data generated when the electric vehicle 2 operates. In addition, the component 21 also continuously collects the high-resolution data 25 in the component data and temporarily stores it (step S20 ). Next, the component 21 executes the general data sending procedure through the component communication unit 211 to send the general data 23 to the bus 22 based on the general frequency (step S22).

The general information 23 is common, such as the bus communication protocol defined by the customer (such as the KWP2000 protocol), the command of the specific function or mechanism issued by the upper control component to the controlled component (such as controlling the motor with the driver) (such as light switch or use ), the component itself has a low rate of change of physical quantity or a low sampling rate to meet the needs of judgment (such as battery power percentage, fault code, drive switch command, peripheral components status such as the tripod is not received, the storage compartment is not closed, brake signal...etc).

In one embodiment, the component 21 continuously samples the general data 23 from the memory 20 at a normal frequency through the component communication unit 211 when the electric vehicle 2 is operating in step S20, and in step S22, the component communication unit 211 continuously samples the general data 23 from the memory 20 at a normal frequency. Unit 211 sends general data 23 onto bus 22 at a general frequency. In addition, in step S20 , when the electric vehicle 2 is operating, the component 21 continues at a specific frequency (such as the above-mentioned general frequency, high-speed frequency, or other frequency exceeding the transmission rate of the bus 22 ) through the high-resolution data collection unit 214 . The high-resolution data 25 is sampled from the memory 20, and the high-resolution data 25 is temporarily stored in the temporary register in a first-in-first-out (FIFO) manner, so as to pre-collect the data before the failure occurs. . It should be noted that, since the high-resolution data is pre-collected data, it is only necessary to ensure that the corresponding data when the fault occurs can be obtained, and there is no need to specially set the sending frequency for sending the high-resolution data 25 to the bus 22 .

In the present invention, the component 21 also samples the component data in the memory 20 through the condition determination unit 212, and judges whether the preset trigger condition is met based on the component data (step S24). When the condition determination unit 212 determines that the component data meets the trigger condition, the high-speed data collection unit 213 is activated to start sampling the high-speed data 24 in the sampled component data from the memory 20 (step S26 ). After step S26, the component 21 executes the high-speed data sending procedure through the component communication unit 211 to send the high-speed data 24 to the bus 22 based on the high-speed frequency (step S28).

The high-speed data 24 refers to the bus information (such as battery voltage, motor current or voltage, etc.) provided according to the pre-determined debug requirement before the error occurs, and the physical quantity of the component itself with a high rate of change. Or data that requires a higher sampling rate to meet the judgment requirements (such as motor speed changes, encoder angle changes, protection-related physical parameters such as current, voltage, torque, temperature changes, etc.).

In one embodiment, in step S26, when the trigger condition is satisfied, the condition determination unit 212 triggers the high-speed data collection unit 213 to continuously sample the high-speed data 24 from the memory 20 at a high-speed frequency, And make the component communication unit 211 continue to send the high-speed data 24 to the bus 22 at the high-speed frequency until the trigger condition is not satisfied.

In one embodiment, the manufacturer of the component 21 can preset multiple sets of different trigger conditions in the firmware of the component 21 for different potential problems, and each set of trigger conditions corresponds to different high-speed data 24 respectively. When a trigger condition is satisfied, it indicates that a corresponding potential problem may occur or is about to occur in the component 21 , and the high-speed data 24 refers to the data in the component data that is highly correlated with these potential problems. In step S24, the condition judging unit 212 generates and sends a corresponding start command to the high-speed data collection unit 213 when the currently collected component data meets any set of trigger conditions, so that the high-speed data collection unit 213 starts to collect and this trigger. Condition-related high-speed data 24.

For example, the trigger condition may be "the first variable exceeds the first threshold", and in step S24, the condition determination unit 212 may determine the trigger condition when the first variable in the component data exceeds the first threshold satisfied. For example, if the aforementioned motor temperature is used as the first variable and exceeds the temperature warning threshold of 125°C, the condition determining unit 212 determines that the temperature meets the triggering condition and starts the high-speed data sending process. At this time, the condition judging unit 212 controls the high-speed data collecting unit 213 by starting the command, so that the high-speed data collecting unit 213 starts collecting the first variable and the second variable that is related to the first variable. However, the above is only a specific implementation example, but not limited thereto.

While continuously collecting and temporarily storing the high-resolution data 25 through step S20, the component 21 also samples the component data in the memory 20 through the error diagnosis unit 215, and judges whether the component 21 has a fault based on the component data (step S30). ). When the error diagnosis unit 215 determines that there is a fault condition in the component data, the high-resolution data collection unit 214 is activated to collect all the high-resolution data currently in the register. The data 25 are all written to the component storage unit 216 . In addition, the high-resolution data collection unit 214 continues to sample the high-resolution data 25 from the memory 20 from the time when the fault occurs and for a period of time afterward, and writes the high-resolution data 25 into the component storage unit 216 (step S32 ).

The high-resolution data 25 includes bus data (such as overcurrent, overvoltage) defined according to the debug requirements when the error occurs, the physical quantities of the component itself with a very high rate of change, or a very high sampling rate to meet the judgment requirements. information (such as quadrature axis current, direct axis current, torque command, etc.).

For example, the error diagnosis unit 215 may record various failure parameters, and in step S30, the error diagnosis unit 215 compares the second variable in the component data with the various failure parameters, and when the comparison result shows the second variable When the variable conforms to one of the various fault parameters, it is judged that the fault occurs. For example, when the temperature of the motor continues to rise and exceeds the temperature fault threshold of 130°C, the fault diagnosis unit 215 will release the OH2 fault code accordingly, and use this fault code as the second variable and multiple fault parameters (such as OH1, OH2, OH3). ...) to compare, and then judge that the fault is caused by excessive motor temperature. Alternatively, when the driver current exceeds the fault threshold 212A-rms, the error diagnosis unit 215 releases the OCN fault code accordingly, uses the fault code as the second variable, and determines that an overcurrent fault occurs.

Next, the component 21 determines whether the preset data transmission conditions are met (step S34). When any data sending condition (for example, the storage unit 216 is full) is satisfied, the component 21 executes the high-resolution data sending procedure through the component communication unit 211, and the load of the bus 22 is not exceeded under the condition that the load of the bus 22 is not exceeded. The state determines a transmission frequency (such as the above-mentioned general frequency, high-speed frequency or any other frequency), and then transmits all the high-resolution data 25 stored in the storage unit 216 to the bus 22 based on this transmission frequency (step S36).

In this embodiment, when the high-resolution data collection unit 214 writes the high-resolution data 25 into the register and/or the component storage unit 216 , the timing unit 217 adds a correct time stamp, and thus is sent to the bus 22 The high-resolution data 25 on the device has correct time information and contains all the data at the time when the fault occurred, before and after a specific period of time.

Continuing to refer to FIG. 9 , when the component 21 sends the general data 23 , the high-speed data 24 and the high-resolution data 25 to the bus 22 of the electric vehicle 2 , the data collector 3 continuously performs full sampling of the bus data on the bus 22 (step S40 ), and associate the acquired bus data with the correct time to generate upload data (step S42 ).

Specifically, the present invention enables the component 21 to dynamically collect different data (general data 23, high-speed data 24 and high-resolution data) through different frequencies (general frequency and high-speed frequency) and different data collection methods (continuous collection and pre-collection). The data 25) is sent to the bus 22, the bandwidth is used more flexibly and the load of the bus 22 is greatly reduced. Therefore, the data collector 3 can use the full sampling data collection method to collect all the data on the bus 22 without compressing the data for partial sampling, so as to avoid data loss and improve the data resolution, thereby helping the engineer 5 to effectively Troubleshoot and analyze.

After step S42, the data collector 3 sends the upload data to the outside world (step S44), and the error detection server 4 receives the upload data sent by the data collector 3 (step S46). After receiving the uploaded data, the debug server 4 can compare the uploaded data with pre-stored various failure modes, so as to generate and display the comparison result in real time. Through the comparison results, the engineer 5 can easily and quickly determine the current status of each component 21 in the electric vehicle 2 , whether there is a failure, how to reproduce the failure, the cause of the failure, and how to repair the failure.

Specifically, after step S46, the error detection server 4 first decodes the uploaded data through the decoding unit 43 to generate the original physical quantity information of each component 21 (step S48). Next, the diagnostic unit 44 of the debug server 4 compares and analyzes the physical quantity information with various failure modes recorded in the error database 46, and generates a preliminary analysis result (step S50). Thereby, the debug server 4 can synchronously display the physical quantity information of each component 21 through the man-machine interface 45, and the preliminary analysis result made by the debug server 4 based on the physical quantity information (step S52). Through the above-mentioned data displayed on the man-machine interface 45 , the engineer 5 can analyze the current status of the electric vehicle 2 effectively and quickly.

In the collection method of the present invention, in addition to synchronizing the data of the display part 21 and the preliminary analysis results for the engineering personnel 5 to check through the debug server 4, if the engineering personnel 5 thinks that it is necessary to modify or increase the currently collected data after checking, Then, the engineer 5 can also refer to the pre-defined failure modes in the error database 46 to directly perform remote adjustment of each component 21 through the error detection server 4 . For example, the engineer 5 can directly adjust the data sampling frequency of each component 21 through the debug server 4, define a new trigger condition for the condition determination unit 212, set a new failure mode for the error diagnosis unit 215, etc., but Not limited to this.

Specifically, the debug server 4 can accept the external operation of the engineer 5 through the man-machine interface 45 to generate the corresponding control command C1 (step S54 ). Next, the debug server 4 sends the control command C1 to the outside (step S56 ), and the data collector 3 receives the control command C1 sent by the debug server 4 (step S58 ).

After receiving the control command C1, the data collector 3 connects the components 21 indicated in the control command C1 through the bus 22 of the electric vehicle 2, and adjusts the components 21 correspondingly based on the content of the control command C1 (step S60). In an embodiment, the content of the control command C1 can be, for example, but not limited to, the content of the general data 23 sent by the adjustment component 21, the content of high-speed data or high-resolution data, the data sampling frequency or data sending frequency of the adjustment component 21, modification The trigger conditions of the high-speed data transmission program, the modification of the fault parameters for judging whether the fault occurs, and the firmware of the update component 21, etc., are not limited.

The above description is only a preferred specific example of the present invention, and therefore does not limit the scope of the patent of the present invention. Therefore, all equivalent changes made by using the content of the present invention are all included in the scope of the present invention. Bright.

1: Data collection system

2: Electric vehicle

21: Components

22: Bus

3: Data Collector

4: Debug server

5: Engineering staff

Claims (11)

An electric vehicle component, the electric vehicle component is arranged in an electric vehicle and connected to a bus of the electric vehicle, including: a communication unit, which continuously collects a component data of the electric vehicle component at a normal frequency a general data, and execute a general data sending program to send the general data to the bus based on the general frequency; a condition judging unit, recording at least one set of trigger conditions, and based on the component data to determine whether the trigger condition is met ; a high-speed data collection unit, connected to the condition judgment unit and the communication unit, after the component data meets the trigger condition, is triggered by the condition judgment unit to continuously collect a high-speed data in the component data at a high-speed frequency, and the communication The unit executes a high-speed data sending program to send the high-speed data to the bus based on the high-speed frequency, wherein the high-speed frequency is higher than the normal frequency; a storage unit, connected to the communication unit; a high-resolution data collection unit, continuously Collecting and temporarily storing a high-resolution data in the component data; an error diagnosis unit, connected to the high-resolution data collection unit, and judging whether a fault occurs based on the component data; and a timing unit, connected to the high-resolution data A collection unit, wherein the temporarily stored high-resolution data includes time information provided by the timing unit, and the time information records a standard time; wherein, the high-resolution data collection unit is connected to the storage unit, and is subject to the failure when the fault occurs. The error diagnosis unit is triggered to store the currently temporarily stored and subsequently collected high-resolution data to the storage unit, and the communication unit executes a high-resolution data sending procedure to match the data in the storage unit. The high-resolution data stored at the time when the fault occurs, before and after a certain period of time is sent to the bus. The electric vehicle component as claimed in claim 1, wherein the bus is a Controller Area Network (CAN) bus, and the electric vehicle component further includes the communication unit, the condition judging unit, the high-speed A memory of the data collection unit, the high-resolution data collection unit and the error diagnosis unit, the electric vehicle component is connected to the component in the electric vehicle at an ultra-high-speed frequency higher than the normal frequency and the high-speed frequency The data is fully sampled, and the results of the full sampling are recorded in the memory, and the memory provides the results of the full sampling to the component communication unit, the condition judging unit, the high-speed data collection unit, and the high-resolution data collection. unit and the error diagnosis unit. The electric vehicle component of claim 2, wherein the condition judging unit collects the component data from the memory, and judges whether the trigger condition is met according to whether a first variable in the component data exceeds a specific threshold. ; and the fault diagnosis unit collects the component data from the memory, and judges whether the fault occurs according to whether a second variable in the component data corresponds to a fault parameter. An electric vehicle data collection system, comprising: a component disposed in an electric vehicle and connected to a bus of the electric vehicle, the component executes a general data transmission program, a high-speed data transmission program or a high-resolution data A sending program, wherein the general data sending program continuously collects a general data in a component data of the electric vehicle, and sends the general data to the bus based on a general frequency, wherein the high-speed data sending program is in accordance with the component data. After a trigger condition starts to collect a high-speed data in the component data, and sends the high-speed data to the bus based on a high-speed frequency higher than the normal frequency, wherein the high-resolution data sending program continues to collect and temporarily store the component A high-resolution data in the data, when judging that a fault occurs, the current temporary storage and subsequent collection of the data with a time information The high-resolution data is stored in a storage unit, and the high-resolution data stored in the storage unit relative to the time when the fault occurs, before and after a certain period of time is sent to the bus; a data collector, a communication connection The bus also performs full sampling of a bus data on the bus, wherein the data collector has a time calibration unit, a first communication unit and a processing unit, and the time calibration unit is connected to an NTP server through the first communication unit To obtain a time information, the processing unit associates the bus data with the obtained time information to generate an upload data, wherein the bus data includes at least one of the general data, the high-speed data and the high-resolution data 1; and a debug server, communicating with the first communication unit of the data collector to receive the uploaded data, the debug server has an error database and a diagnosis unit, the error database stores a plurality of For the failure state, the diagnostic unit compares the uploaded data with the plurality of failure states and displays a comparison result in real time. The electric vehicle data collection system as claimed in claim 4, wherein the component has a memory, and the component collects the component data of the electric vehicle at an ultra-high-speed frequency higher than the normal frequency and the high-speed frequency. Sampling and recording the results of all sampling in the memory, and the component collects the component data from the memory; the component judges whether it conforms to the component according to whether a first variable in the component data exceeds a specific threshold triggering conditions; and the component determines whether the fault occurs according to whether a second variable in the component data corresponds to a fault parameter. The electric vehicle data collection system according to claim 4, wherein the bus is a Controller Area Network (CAN) bus, and the data collector further comprises: A second communication unit is connected to the timing unit and the processing unit, the data collector communicates with the bus through the second communication unit, sends the time information to the component on the bus, and processes the bus data. Sampling; a collector memory connected to the processing unit; a collection unit connected to the second communication unit and the processing unit to collect the bus data sampled by the second communication unit and temporarily store in the collection through the processing unit and a collector storage unit, connected to the processing unit, and storing the uploaded data when the processing unit cannot send the uploaded data to the debug server through the first communication unit. The electric vehicle data collection system according to claim 6, wherein the debug server further comprises: a server communication unit, connected to the data collector, and receiving the uploaded data; a server storage unit, connected to The server communication unit stores the uploaded data; a decoding unit is connected to the server storage unit and the diagnosis unit, and decodes the uploaded data to generate a real physical quantity, wherein the diagnosis unit and the plurality of fault states compare the sample to generate the comparison result; a human-machine interface, connect the error database and the diagnosis unit to display the comparison result, and receive an external operation to edit the plurality of fault states recorded in the error database Sample. The electric wearable data collection system as claimed in claim 7, wherein the human-machine interface is connected to the server communication unit, receives the external operation to send a control command to the data collector through the server communication unit, and the data The collector adjusts the component on the bus according to the control command, wherein the control command includes adjusting the content of the general data, the high-speed data or the high-resolution data, adjusting the data sampling frequency or data sending frequency of the component, At least one of modifying the trigger condition of the high-speed data transmission program, modifying a failure parameter for judging whether the failure occurs, and updating the firmware of the component. An electric vehicle data collection method, applied to an electric vehicle data collection system, wherein the electric vehicle data collection system includes a component disposed in an electric vehicle, and communicates with the component through a bus of the electric vehicle A connected data collector and a debug server connected in communication with the data collector, the electric vehicle data collection method includes: a) the component continuously collects general data in a component data, and executes a general data transmission The program sends the general data to the bus based on a general frequency; b) the component determines whether a trigger condition is met based on the component data; c) the component continues to collect the component data after the component data meets the trigger condition. a high-speed data, and execute a high-speed data sending program to send the high-speed data to the bus based on a high-speed frequency, wherein the high-speed frequency is higher than the normal frequency; d) the component continuously collects and temporarily stores a part of the component data high-resolution data; e) the component determines whether a fault occurs based on the component data; f) the component stores the high-resolution data currently temporarily stored and subsequently collected in a storage unit when the fault occurs; g) the After step f, the component executes a high-resolution data sending program to send the high-resolution data stored in the storage unit to the bus for a specific period of time when the fault occurs, before and after the failure, wherein the high-resolution data is stored on the bus. The resolution data includes a time information, and the time information records a standard time; h) The data collector performs full sampling of a bus data on the bus, wherein the bus data includes the general data, the high-speed data and the high-resolution data at least one of the data; i) the data collector associates the sampled bus data with the standard time to generate an upload data; j) the debug server receives the upload data from the data collector; and k) The debugging server compares the uploaded data with a plurality of pre-stored fault patterns, and displays a comparison result in real time. The method for collecting data of an electric vehicle as claimed in claim 9, wherein the component has a memory, and the component records the data of the component in the electric vehicle at an ultra-high-speed frequency higher than the normal frequency and the high-speed frequency. All sampling is performed and the result of all sampling is recorded in the memory; the step b) is to collect the component data from the memory, and determine whether a first variable in the component data exceeds a specific threshold value. The trigger condition is met; the step e) is to collect the component data from the memory, and determine whether the fault occurs according to whether a second variable in the component data corresponds to a fault parameter. The data collection method for an electric vehicle as claimed in claim 10, further comprising: l) the debug server receives an external operation to generate a control command; m) the data collector receives the control command; and n) the The data collector adjusts the component on the bus according to the control command, wherein the control command includes adjusting the content of the general data, the high-speed data or the high-resolution data, and adjusting the data sampling frequency or data sending frequency of the component , at least one of modifying the triggering condition of the high-speed data transmission program, modifying the fault parameter, and updating the firmware of the component.

Images