JP2019133518A - Electronic control device for vehicle - Google Patents

Abstract

To provide an electronic control device for a vehicle that can maintain storage information to output correct vehicle information to an external tool even when reprogramming is performed.SOLUTION: An electronic control device 30 stores first identification information that is common among a plurality of first control programs and that does not depend on the first control programs corresponding to vehicle information being generated in an operation of a vehicle 10. And, after at least one of a plurality of first control programs is rewritten as a second control program, second identification information depending on a second control program is referred from the stored first identification information, and the vehicle information is output on the basis of the second identification information. Even after rewriting of a program is performed, storage information is maintained by storing the first identification information not depending on the first control program, and compatibility between before rewriting of the program and the vehicle information is maintained by outputting the second identification information depending on the second control program to an external tool.SELECTED DRAWING: Figure 1

Description

  The present invention relates to an electronic control device for a vehicle, for example, maintenance of failure information during reprogramming in an ECM (Engine Control Module).

  In a vehicle electronic control device such as an ECM, when a failure is detected, failure information generated in the vehicle is stored and held in a nonvolatile memory. When maintenance or inspection is performed, an operator connects an external tool for diagnosis to the ECM, reads out failure information from the nonvolatile memory, and displays the failure status on the monitor of the external tool for confirmation. (For example, refer to Patent Document 1 and Patent Document 2).

JP 2009-059334 A JP 2009-067298 A

By the way, in the vehicle electronic control device, when the program or data needs to be updated or corrected, rewriting, that is, so-called reprogramming is performed. At this time, if reprogramming is performed after the ECM detects a failure, the failure information stored in the nonvolatile memory may not be displayed by an external tool. This is because failure information cannot be taken over if the information form changes before and after reprogramming. For this reason, the failure information stored in the nonvolatile memory is generally erased during reprogramming.
However, due to changes in laws and regulations, it has become necessary to maintain failure information even after reprogramming.

  The present invention has been made in view of the above circumstances, and an object of the present invention is to provide an electronic control device for a vehicle that can maintain stored information and output correct vehicle information to an external tool even if reprogramming is performed. Is to provide.

  An electronic control device for a vehicle according to an aspect of the present invention is an electronic control device configured such that a program can be rewritten from the outside, and is common among a plurality of first control programs and depends on the first control program. The first identification information that is not stored is stored in association with the vehicle information generated during operation of the vehicle, and the first identification information stored after rewriting at least one of the plurality of first control programs to the second control program is stored. The second identification information depending on the second control program is referred to from the information, and the vehicle information is output based on the second identification information.

  According to the present invention, by storing the first identification information that is common among the plurality of first control programs and does not depend on the first control program, the stored information is maintained even after the first control program is rewritten. Then, by outputting the second identification information depending on the second control program after rewriting, compatibility of vehicle information can be maintained even if at least one of the plurality of first control programs is rewritten to the second control program. it can. Therefore, even if reprogramming is performed, the stored vehicle information can be maintained and correct vehicle information can be output to the external tool.

It is a block diagram which shows schematic structure of the electronic controller for vehicles which concerns on embodiment of this invention. It is a system schematic diagram in the case of performing reprogramming of the vehicle electronic control device shown in FIG. FIG. 3 is a block diagram illustrating a configuration example of a reprogramming tool illustrated in FIG. 2. It is a figure which compares and shows the diagnostic information of the past and this invention. It is a flowchart which shows the reprogramming operation | movement in the vehicle electronic control apparatus shown in FIG. It is a figure for demonstrating the state before and after reprogramming in the electronic controller for vehicles shown in FIG. It is a figure for demonstrating the detail of the identification method of an old and new program, and an external display process. It is a figure for demonstrating the 1st example of the identification method and reprogramming method of an old and new program. It is a figure for demonstrating the 2nd example of the identification method and reprogramming method of an old and new program. It is a figure for demonstrating the 3rd example of the identification method and reprogramming method of an old and new program. It is a figure for demonstrating the 4th example of the identification method and reprogramming method of an old and new program.

Embodiments of the present invention will be described below with reference to the drawings.
FIG. 1 shows a schematic configuration of a vehicle electronic control apparatus according to an embodiment of the present invention. The engine 20 (internal combustion engine) mounted on the vehicle 10 is provided with various sensors 31, and signals detected by these sensors 31 are input to the ECM 30. The sensor 31 is, for example, an intake air amount sensor, a crank angle sensor, an accelerator opening sensor, a water temperature sensor, a cam angle sensor, an air-fuel ratio sensor, and an oil temperature sensor. Further, the ECM 30 receives a signal from an ignition switch (not shown) that is a main switch for operating and stopping the engine 20.

  The ECM 30 performs arithmetic processing according to a control program stored in advance based on the signals from these various sensors 31 and the ignition switch, and manipulates or controls the various devices such as the fuel injection valve, the VTC mechanism, and the ignition module. Is calculated, and a control signal is output to the device 32 and the actuator 32 that drives the device.

  The ECM 30 includes a processor 33 such as a CPU (Central Processing Unit), a RAM (Random Access Memory) 34 as an example of a volatile memory, and a ROM (Read as an example of a nonvolatile memory for storing a control program and various data. Only Memory (35), EEPROM (Electrically Erasable and Programmable Read Only Memory) 36 as an example of a non-volatile memory for storing vehicle information (failure and abnormality information), learning values, and the like, and an interface between input and output Input / output interface (input / output I / F) 37, an external communication interface (external communication I / F) 38 for communicating with an external device, and a bus 39.

  The processor 33, RAM 34, ROM 35, EEPROM 36, input / output I / F 37, and external communication I / F 38 are connected to each other by a bus 39. The external communication I / F 38 has a connector 38a for detachably connecting the network cable 40. The connector 38a includes a reprogramming tool 50 for rewriting a program from the outside, or an external tool 60 for performing maintenance and inspection when a failure occurs, CAN (Controller Area Network), serial communication, FlexRay (registered trademark), and Ethernet. It is connected via a network cable 40 such as (registered trademark).

FIG. 2 shows a system configuration when reprogramming the vehicle electronic control device. The ECM 30 to be reprogrammed is detachably connected to the reprogramming tool 50 via the network cable 40. In this state, the operator operates the reprogramming tool 50 to perform reprogramming work for the ECM 30.
The ECM 30 and the reprogramming tool 50 are not limited to a wired connection using the network cable 40 and the connectors 38a and 52a, but may be configured to be connected to each other by wireless communication using a wireless transceiver.

  The reprogramming tool 50 is an electronic device in which an operator rewrites data in the ECM 30, and includes, for example, a personal computer. Specifically, as shown in FIG. 3, the reprogramming tool 50 includes a processor 51 such as a CPU, a communication device 52 for connection to a network, a storage 53 such as a hard disk device or an SSD (Solid State Drive), , An input / output device 54 serving as an interface to the worker and a bus 55 are provided. The processor 51, the communication device 52, the storage 53, and the input / output device 54 are connected to each other by a bus 55. Here, the communication device 52 includes a connector 52a for detachably connecting the network cable 40. The input / output device 54 includes a display such as an LCD (Liquid Crystal Display), a keyboard, and a pointing device such as a mouse.

The storage 53 may be, for example, a NAS (Network Attached Storage) connected to a network (not shown) or a server storage.
The storage 53 stores data for rewriting the EEPROM 36 of the ECM 30. This data includes, for example, a control program for controlling various devices mounted on or installed in the engine 20, control parameters such as constants and maps used in the control program, and the like.

  The reprogramming process (data rewriting process) is executed when a predetermined operation is performed in the reprogramming tool 50 after the operator connects the ECM 30 and the reprogramming tool 50 via the network cable 40. Here, it is assumed that the ECM 30 is activated by being supplied with power when connected to the reprogramming tool 50 via the network cable 40. However, the ECM 30 may be activated by connecting another power cable. .

  On the other hand, the external tool 60 receives the failure code output from the ECM 30 and displays the failure state corresponding to the failure code on the monitor. The external tool 60 may be a dedicated diagnostic tool or similar to the reprogramming tool 50. In addition, for example, a personal computer may be used. Further, the external tool 60 and the ECM 30 are not limited to a wired connection using the network cable 40, and may be configured to be connected to each other by wireless communication using a wireless transceiver. Here, as the external tool 60, a detailed description is omitted on the assumption that a known diagnostic tool is used.

  FIG. 4 shows a comparison between the conventional and diagnostic information of the present invention. That is, conventionally, as shown in FIG. 4A, a fault code (DTC: Diagnostic Trouble Code) and an index (Index) are used. When the ECM 30 detects a fault, an index corresponding to the fault code is assigned to the EEPROM 36. I remembered. For maintenance and inspection, when the external tool 60 is connected to the connector 38a of the ECM 30 and a fault code output request is made, the fault code is determined based on the index stored in the EEPROM 36, and the external tool 60 is connected to the vehicle. A failure code was sent as information. The external tool 60 displays a failure state corresponding to the received failure code on the monitor.

For example, if the detected failure code is “2000”, the EEPROM 36 stores an index “3” corresponding to the failure code “2000”. When the external tool 60 is connected and there is a fault code output request, the fault code “2000” corresponding to the index “3” is referred to from the index “3” stored in the EEPROM 36, and the vehicle information is obtained. The failure code “2000” is transmitted to the external tool 60. The external tool 60 displays a failure state corresponding to the failure code “2000” on the monitor.
Here, the definition of what kind of failure the failure code corresponds to does not change, but the index depends on the number of control programs and is distributed according to the number of diagnoses. If it increases or decreases, the index number changes.

  On the other hand, in the present invention, as shown in FIG. 4B, a management number (management No.) is used in addition to the failure code and the index. The management number does not depend on the number of control programs (does not depend on the number of diagnoses), and is common between a plurality of control programs before rewriting (first control program) and a control program after rewriting (second control program). It is what is used. Therefore, the indexes are sequentially assigned to the failure codes “1000”, “1001”, “1002”, “2000”, “2001” as “1”, “2”, “3”, “4”, “5”. On the other hand, the management number is assigned according to diagnosis as “00”, “01”, “02”, “05”, “06” corresponding to each failure code. When a failure is detected, an index corresponding to the failure code is not stored in the EEPROM 36, but a management number is stored in the EEPROM 36.

  That is, as shown in the flowchart of FIG. 5, for example, when the ECM 30 detects a failure with the failure code “2000” (step S1), the failure code “2000” refers to the index “3”, and the index “3” begins with the management number. Refer to “05”. Then, the management number “05” corresponding to the failure code “2000” is stored in the EEPROM 36 (step S2). This state is schematically shown in FIG.

Thereafter, the control program is rewritten (reprogramming) (step S3), and as shown in FIG. 6B, the failure code “1003” is added between the failure codes “1002” and “2000”. Assuming that the index depends on the number of diagnoses, the fault code “1003” is index “3”, the fault code “2000” is index “4”, and the fault code “2001” is index “5”. At this time, the indexes “0”, “1”, and “2” corresponding to the failure codes “1000”, “1001”, and “1002” do not change.
Also, the management number corresponds to the failure code and is used in common among multiple control programs, so a new management number “03” is added, but other management numbers remain in the state before reprogramming. To do.

  Next, when the external tool 60 is connected (step S4) and a fault code output request is made (step S5), the management number "05" stored in the EEPROM 36 is referred to as shown in FIG. 6C. (Step S6). Subsequently, the index “4” is referenced from the management number “05” (step S7), the failure code “2000” is referenced from the index “4” (step S8), and the index “4” is stored as vehicle information in the external tool 60. The failure code “2000” corresponding to is transmitted. The external tool 60 receives the vehicle information and displays a failure state corresponding to the failure code “2000” on the monitor.

  In this way, the index (second identification information) is referred to from the failure code (vehicle information), and the management number (first identification information) is referred to from the index and stored in the EEPROM 36. The index is referred to from the management number stored in the EEPROM 36, and the failure code is transmitted to the external tool 60. By storing the management number in the EEPROM 36 in this way, even if the index changes due to rewriting of the control program, the stored information (failure information) can be maintained, and the failure code can be output by referring to the index from the management number. Thus, since the compatibility with the failure code before rewriting the program is not lost, the correct failure code can be output to the external tool 60.

FIG. 7 shows details of the new and old program identification method and external display processing. In this example, information of “DGNSWbyte” and “DGNSWbit” is used in combination with the management number. That is, when the number of diagnoses is expressed by the same number of bits as in the conventional case, the maximum value (Max) of the number of diagnoses is “256 × 8 = 2048”. In hexadecimal, it is represented by “07FF” and the most significant bit (MSB15) is “0”. Therefore, “MSB15 = 0” is defined as an old program, “1” is written in the most significant bit, and “MSB15 = 1 ”is defined as a new program. As a result, old and new programs can be identified based on whether the most significant bit is “1” or “0”.
In order to make it possible to identify such new and old programs, it is preferable to store them in the order of “bit / byte” instead of storing them in the order of “byte / bit” in the EEPROM 36.

FIG. 8 shows a first example of a new and old program identification method and reprogramming method. This example relates to handling of fault codes when writing old and new programs. If the program written in the ECM 30 is an old program and the program to be rewritten is also an old program, the fault code is erased (as before). When the program written in the ECM 30 is an old program and the program to be rewritten is a new program, the fault code is erased. Even when the program written in the ECM 30 is a new program and the program to be rewritten is an old program, the fault code is erased. If the program written in the ECM 30 is a new program and the program to be rewritten is a new program, a fault code is held.
As described above, the present invention is applied to a case where a new program written in the ECM 30 is rewritten to a new program.

  FIG. 9 shows a second example of a new and old program identification method and reprogramming method. In this example, it is confirmed whether or not the control program before rewriting has a management number, and if not, the data stored in the EEPROM 36 is erased. When the management number is not possessed, before rewriting, an index (here, “3”) is stored in the EEPROM 36 as shown in FIG. That is, since the data stored in the EEPROM 36 is an index, it is an old program. Therefore, the data is erased and initialized.

As a result, in the rewritten program, as shown in FIG. 9B, the failure code “1003” is increased, the index “3” corresponds to the failure code “1003”, and the index “4” is the failure code “2000”. ”And the index“ 5 ”changes so as to correspond to the failure code“ 2001 ”. Also, the management numbers “00”, “01”, “02”, “03” correspond to the failure codes “1000”, “1001”, “1002”, “1003”, “2000”, “2001”, respectively. , “05”, “06” are added.
On the other hand, when the management number is stored in the EEPROM 36, the data is not erased because it is a new program.
Thus, by determining whether the index or management number is stored in the EEPROM 36, it is possible to determine whether it is an old program or a new program.

FIG. 10 shows a third example of a new and old program identification method and reprogramming method. Assume that the management number “05” is stored in the EEPROM 36 with the control program before rewriting in the state of FIG. In this state, if the failure code “2000” is deleted by reprogramming, the state shown in FIG. That is, the index “0” corresponds to the failure code “1000”, the index “1” corresponds to the failure code “1001”, the index “2” corresponds to the failure code “1002”, and the index “3” corresponds to the failure. Corresponding to the code “1003”, the index “4” changes so as to correspond to the failure code “2001”. At this time, the management numbers “00”, “01”, “02”, “03”, and “06” are assigned to the failure codes “1000”, “1001”, “1002”, “1003”, and “2001”, respectively. Correspond.
In this case, no fault code is output to the external tool 60, but there is no problem because it is the same as the current situation.

FIG. 11 shows a fourth example of a new and old program identification method and reprogramming method. When the control program before rewriting is in the state of FIG. 11A, the reprogramming has been rewritten to the control programs (failure codes “4000” and “4001”) in which the fault codes “2000” and “2001” are changed. The state shown in FIG. Thus, even if the failure code is changed, there is no problem because the failure contents of the failure codes “2000” and “4000” do not change.
However, the correspondence between the failure code in the external tool 60 and the vehicle failure state must also be corrected.

As described above, in the present invention, a management number (first control program) that is common between a plurality of control programs (first control program) before rewriting and a control program (second control program) after rewriting and does not depend on the control program. The control program (second control program) was rewritten by storing (1 identification information) in a nonvolatile memory (EEPROM) in association with a failure code (vehicle information) generated during operation of the vehicle. The stored information can be maintained later. In addition, after rewriting at least one of the plurality of control programs, an index (second identification information) depending on the control program is referred to from the stored management number, and a fault code is output based on this index to display an external tool. By using it, compatibility of the fault code with that before rewriting the control program can be maintained.
Therefore, according to the present invention, even if reprogramming is performed, failure information stored in the nonvolatile memory can be maintained, and a correct failure code can be output to an external tool.

In the above-described embodiment, the ECM has been described as an example. However, it is needless to say that the present invention can be applied to general electronic control devices in which programs and data are reprogrammed.
Further, the case where the stored information is a failure code (failure information) has been described as an example, but the present invention can be similarly applied to a case where a learning value is held.

Furthermore, although expressed as “rewrite at least one of a plurality of control programs”, this includes the case of rewriting part of a specific control program or data such as setting values and initial values used in this control program. Shall be. Here, the plurality of control programs are control programs whose control targets are the same series, in other words, control programs whose control targets are the same or related to each other.
Furthermore, the example in which the ECM controls the fuel injection valve, the VTC mechanism, the ignition module, and the like has been described, but various devices mounted on the vehicle, such as a transmission, an electric brake system, an ABS (Antilock Brake System), and a brushless The present invention can be similarly applied to an electronic control device that controls a motor or the like.

  DESCRIPTION OF SYMBOLS 10 ... Vehicle, 20 ... Engine, 30 ... ECM (electronic control unit for vehicles), 31 ... Sensor, 32 ... Actuator, 33 ... Processor, 34 ... RAM, 35 ... ROM, 36 ... EEPROM (non-volatile memory), 37 ... Input / output interface, 38 ... external communication interface, 39 ... bus, 40 ... network cable, 50 ... reprogramming tool, 60 ... external tool

Claims (4)

An electronic control device configured to be rewritable from the outside,
Storing first identification information that is common among a plurality of first control programs and that does not depend on the first control program, corresponding to vehicle information generated during operation of the vehicle,
After rewriting at least one of the plurality of first control programs to the second control program, the second identification information that depends on the second control program is referred to from the stored first identification information, and the second identification information The vehicle information is output based on the vehicle electronic control device.   The vehicle electronic control device according to claim 1, wherein the vehicle information is input to an external tool, and the state of the vehicle corresponding to the vehicle information is displayed with the external tool.   The first identification information to be stored is stored by referring to the second identification information from the vehicle information generated during operation of the vehicle and by referring to the first identification information from the second identification information. The vehicle electronic control device according to claim 1 or 2, characterized in that The plurality of first control programs have the same control target or are related to each other,
4. The vehicle electronic control according to claim 1, wherein the first identification information is common to the second control program in addition to the plurality of first control programs. 5. apparatus.