JP2006327217A - Program for vehicle control and electronic control device for vehicle - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a program for vehicle control and an electronic control device for a vehicle free of the risk of malfunction even when they are started according to other system requisite when a plurality of systems are mounted on one ECU. <P>SOLUTION: The program for vehicle control has a power supply IC 4 to enter the power supply condition and the starting requisite to a CPU 11 on the basis of signals from a timer 16, a battery 2, a push SW, a brake switch (STP), an IG SW, an ACC, a communication IC 15, etc. The communication IC 15 conducts mutual communication with other ECUs via a CAN bus 3, while the timer 16 clocks the time, and emits wake-up signals to the power supply IC 14 at certain intervals, for example every three hours. A motion requisite determining part 34 determines the motion requisites of each of the applications such as a power supply management 21, a push start 22, an eco-run 23, a start charger 24, etc. on the basis of the power supply condition and the starting requisites fed from a power supply condition sensing part 31 and a starting requisite sensing part 32, and actuates only the application which meets the motion requisites. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a vehicle control program including a platform that is a hardware-dependent program, and a plurality of applications that are programs for causing a computer to realize a vehicle control function, and a computer that executes the vehicle control program. The present invention relates to a vehicle electronic control device.

  A vehicle electronic control device (hereinafter referred to as an ECU) performs electronic control of a vehicle by exchanging signals with a vehicle control mechanism. For example, an engine control ECU is provided in a vehicle. Information such as the vehicle speed, the engine speed, and the air inflow amount detected by the sensor group is input, and the engine control ECU performs predetermined arithmetic processing based on the information, and the calculation result (for example, fuel injection amount, A signal for controlling the amount of bypass air, etc.) is sent to a control mechanism such as an electric throttle or a starter injection valve installed in the vehicle to control the fuel injection amount and the inflow air amount.

There are many such electronic control devices in the vehicle, such as an engine control ECU as described above, an eco-run ECU that performs engine automatic stop / restart control when a predetermined condition is satisfied, a body ECU that controls lamps, doors, etc. A transmission (AT) control ECU, an airbag ECU, a security ECU, and the like are mounted, and each of these ECUs independently controls a control object in charge, but information is exchanged with other ECUs. It may be necessary.
For this reason, in order to perform various controls by associating a plurality of ECUs mounted on a vehicle, the plurality of ECUs are connected to a common bus line, and a typical standard network protocol, a controller area network (Controller Area Network, Intercommunication control is performed using a protocol (hereinafter referred to as CAN).

On the other hand, an electronic control device for a vehicle includes an embedded microcomputer (hereinafter referred to as a microcomputer), and software that operates on the microcomputer generally includes a platform program that is a hardware-dependent program, and a vehicle. And an application program that is a program that depends on the control for use (see, for example, Patent Document 1).
JP 2000-97102 A

The platform program inputs data from a hardware device and provides data based on the input data to processing by an application program via an interface such as an API (Application Program Interface), It is a program for causing a computer to execute processing for outputting data obtained by processing by a program to a hardware device.
The application program is a program for causing a computer to execute processing using data input from the platform program and processing to generate data output via the platform program.

  As described above, the platform program includes a program for accessing the hardware device, while the application program does not include a program for directly accessing the hardware device, and is hard to process by the platform program via the platform interface. I / O with wear devices. By doing so, the developer of the application program can create the application program without being aware of the detailed configuration of hardware and the control method.

  The above-described applications of the vehicle electronic control device are roughly classified into a power train application and a body application. The power train application is a group of applications that operate when the ignition is turned on, and includes, for example, engine control and transmission control, and is hereinafter referred to as an IG system. The body application is a group of applications that operate at all times or at the time of communication wakeup, and includes, for example, push start and door courtesy.

At present, the power train application and the body application are operated by separate ECUs, but it is expected that the power train application and the body application will be mounted on one ECU in the future.
In this way, if a powertrain application and a body application are mounted on the same ECU or microcomputer, or if a plurality of body applications are mounted on a single ECU, the application may be started with requirements other than the operation requirements of the own application. Therefore, the following problems may occur.
(1) Since the ECU and microcomputer are activated by the activation requirements of other applications, the occurrence of malfunctions that cause the actuators, etc., driven by the application to operate at a timing that should not be operated originally (2) False detection of diagnostics / failures

  The present invention has been made in view of the above-described problems. When a plurality of systems (applications) are mounted on a single ECU, a vehicle control program and a vehicle that do not malfunction even when activated by other system requirements An object is to provide an electronic control device.

In order to achieve the above object, a vehicle control program (1) according to the present invention includes:
A vehicle control program including a platform that is a hardware-dependent program and a plurality of applications that are programs for causing a computer to realize a vehicle control function,
The platform includes a program for realizing the function of notifying the power state and / or activation requirement of the control device to each application,
Each of the applications includes a program for realizing a function of determining whether or not to start based on a power supply state and / or a start requirement notified from the platform.

Moreover, the vehicle control program (2) according to the present invention includes:
A vehicle control program including a platform that is a hardware-dependent program and a plurality of applications that are programs for causing a computer to realize a vehicle control function,
The platform includes a program for realizing the function of notifying the power state and / or activation requirement of the control device to each application,
When each of the applications starts when the power status and / or activation requirements are notified from the platform, and the power status and / or activation requirements notified from the platform do not correspond to the operation requirements of the application, predetermined control is performed. A program for realizing a function for prohibiting the operation is included.

Furthermore, the vehicle control program (3) according to the present invention includes:
A vehicle control program including a platform that is a hardware-dependent program and a plurality of applications that are programs for causing a computer to realize a vehicle control function,
The platform includes a program for determining an operation requirement of each application based on a power supply state and / or activation requirement of the control device and realizing a function of starting only a necessary application.

Moreover, the vehicle control program (4) according to the present invention includes:
A vehicle control program including a platform that is a hardware-dependent program and a plurality of applications that are programs for causing a computer to realize a vehicle control function,
The above platform starts all applications based on the power supply status and / or startup requirements of the control device, and determines the operation requirements of each application based on the power supply status and / or startup requirements of the control device. It includes a program for realizing a function of prohibiting a predetermined control operation for an application that does not meet the requirements.

Furthermore, the vehicle control program (5) according to the present invention is a vehicle control program (1) or a vehicle control program (3).
The application or the platform includes a program for realizing a function of setting a variable that an application not corresponding to the operation requirement is disclosed to another application to a predetermined fixed value,
The vehicle control program (6) according to the present invention is a vehicle control program (1) or a vehicle control program (3).
When the operation of the application that does not correspond to the operation requirements of the application or the platform is stopped, the fact is notified to the other vehicle electronic control device, and the other vehicle electronic control device does not correspond to the operation requirement. It includes a program for realizing a function of masking a process of detecting an abnormality with reference to application data.

Further, the vehicle control program (7) according to the present invention is any one of the vehicle control program (1) to the vehicle control program (4).
The application or the platform includes a program for realizing a function of prohibiting connector terminal abnormality detection processing output by an application not corresponding to the operation requirement.

Furthermore, the vehicle control program (8) according to the present invention is any one of the vehicle control program (1) to the vehicle control program (6).
The power state is a state of power off, accessory power on, ignition on, etc. set by operating an ignition switch or a power control device,
The vehicle control program (9) according to the present invention is any one of the vehicle control program (1) to the vehicle control program (6).
The activation requirement is a condition such as a wake-up by communication from another vehicle electronic control device, a predetermined switch operation, or a wake-up every fixed time by an internal timer.

Moreover, the vehicle electronic control device (1) according to the present invention includes:
A computer that realizes the function based on any one of the vehicle control program (1) to the vehicle control program (9) is provided.

According to the vehicle control program (1) according to the present invention, the platform notifies each application of the power state and / or activation requirement of the control device, and each application receives the power state and / or notified from the platform. It is determined whether or not to perform an operation based on the activation requirement. If the operation does not meet the operation requirement of the own application, the operation is not performed, so that malfunction can be prevented.
In addition, according to the vehicle control program (2) of the present invention, each application is activated when the power supply state and / or activation requirement is notified from the platform, and the power state and / or activation requirement notified from the platform. Is not applicable to the operation requirements of the own application, the predetermined control operation is prohibited, so that the malfunction can be similarly prevented.

Furthermore, according to the vehicle control program (3) according to the present invention, the platform determines the operation requirement of each application based on the power supply state and / or the activation requirement of the control device, and operates only the necessary application. , Malfunction can be prevented.
Further, according to the vehicle control program (4) according to the present invention, the platform starts all applications based on the power supply state and / or start-up requirement of the control device, and the power supply state and / or start-up of the control device. Since the operation requirements of each application are determined based on the requirements, and a predetermined control operation is prohibited for the application not corresponding to the operation requirements, similarly, malfunction can be prevented.

Furthermore, according to the vehicle control program (5) according to the present invention, a variable that an application that does not meet the operation requirements is set to a predetermined fixed value, and the vehicle control program (6) according to the present invention is set. According to the above, when the operation of an application not corresponding to the operation requirement is stopped, the fact is notified to the other vehicle electronic control device, and the application data not corresponding to the operation requirement on the other vehicle electronic control device side Referring to FIG. 5, the process for detecting an abnormality is masked, so that a malfunction can be prevented.
Moreover, according to the vehicle control program (7) according to the present invention, the connector terminal abnormality detection process output by the application not corresponding to the operation requirement is prohibited, so that erroneous diagnosis can be prevented.

  Embodiments of a vehicle control program according to the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing an embodiment of an ECU in which the vehicle control program of the present invention is implemented. As shown in the figure, the ECU 1 includes a CPU 11, a ROM 12, a RAM 13, a power supply IC 14, a communication IC 15, a timer 16 and these. It is comprised from the bus line etc. which connect. The CPU 11 controls each part of the hardware of the ECU 1 and executes various programs based on the programs stored in the ROM 12. The RAM 13 is composed of an SRAM or the like and stores temporary data generated when the program is executed.

  Signals from the timer 16, the battery 2, the push switch (SW), the brake switch (STP), the ignition switch (IGSW), the accessory switch (ACC), the communication IC 15 and the like are input to the power supply IC 14, and the power supply state and activation requirements Is input to the CPU 11. Further, the communication IC 15 performs mutual communication with other ECUs via the CAN bus 3, and the timer 16 measures time, for example, outputs a wakeup signal to the power supply IC 14 every 3 hours.

  The IGSW and ACC are turned on when the key switch (ignition key) is in the ignition (IGN) position and the accessory (ACC) position, and the push SW starts the engine by the switch operation regardless of the operation of the ignition key. For example, when the switch button is pressed once, the ACC switch is turned on, when the switch button is pressed twice, the IGSW is turned on, and when the switch button is pressed three times, the engine start function is executed.

  On the other hand, a program stored in the ROM 12 for causing the CPU 11 to execute various applications is configured by linking an application program and a platform program as shown in FIG. 2, and the application program is a + B system. It consists of a power management 21, a push start 22, an eco-run 23 which is an IG system, and a start / charge 24.

The power management 21 controls the power supply of the in-vehicle electronic device or the like with the power connection as an activation requirement, and the push start 22 pushes the push SW to activate the push switch such as an ACC switch on, an ignition switch on, and an engine start. The engine start function is executed.
The eco-run 23 performs an eco-run (idling stop) function for driving the vehicle while driving and stopping the engine, and the start / charge 24 performs engine start-up and battery charge control by the electric power generated by the alternator. It is something to execute.

FIG. 3 is a table showing the activation conditions of these applications. The power management 21 is activated by any one of the wake-up signal from the timer 16 every three hours, CAN wake-up, battery connection, and ACC on. The push start 22 is activated when the push SW is operated, the brake is depressed, and the CAN wakes up. The eco-run 23 and the start / charge 24 are activated when the ignition SW is turned on.
The CAN wakeup is a wakeup signal from another ECU. As shown in FIG. 4, when the ECU-A sends a wakeup signal on the CAN communication bus, the ECU-B sleeps. Transition from state to wake-up state.

  The platform program includes a power supply state detection unit 31, an activation requirement detection unit 32, and an operation requirement notification unit 33. Each of the power supply state detection unit 31 and the activation requirement detection unit 32 is a power source input from the power supply IC 14. The state and activation requirements are detected and input to the operation requirement notification unit 33. The operation requirement notification unit 33 notifies the application programs 21 to 24 of the power supply state and the activation requirement when the power supply state and the activation requirement are input from the power supply state detection unit 31 and the activation requirement detection unit 32.

Next, the operation of the CPU 11 when the power requirement and the activation requirement are notified from the operation requirement notification unit 33 will be described with reference to the flowchart of FIG.
When the power requirement and the activation requirement are notified from the operation requirement notifying unit 33, the CPU 11 starts the activation program for each application shown in the flowchart of FIG. 5, and the activation condition of the application corresponding to the notified power status and activation requirement is started. Is determined (step 101), and if it is determined that the activation condition for the corresponding application is satisfied, the application is activated (step 102), and the activation condition for the corresponding application is not satisfied. If determined, the application startup program is terminated.

  As described above, the platform notifies each application of the power status and activation requirements of the control device, and each application determines whether to perform an operation based on the power status and activation requirements notified from the platform. Since it does not start when it does not correspond to the operation requirements of its own application, it can prevent malfunction.

In the above embodiment, when it is determined that each application does not correspond to the operation requirement, the malfunction of the other application can be prevented by setting the variable that the own application discloses to the other application to a predetermined fixed value. Can do.
For example, as shown in FIG. 6, when the eco-run application 23 meets the operation requirements and is activated, a start request signal is transmitted from the eco-run application 23 to the start / charge application 24. When the operation is not performed and the operation is stopped, the start / charge application 24 is prevented from malfunctioning by transmitting the always-off signal to the start / charge application 24 as a start request signal from the eco-run application 23. can do.

  Further, when the operation of an application that does not correspond to the operation requirement is stopped, the fact is notified to the other ECU via the communication IC 15 and the CAN bus 3, and the data of the application that does not correspond to the operation requirement on the other ECU side. By referring to the above and masking the process for detecting the abnormality, it is possible to prevent erroneous diagnosis by other ECUs.

In the above embodiment, each application is started only when it meets the operation requirements of its own application. However, all the applications are started when the power state and the start requirement are notified from the platform, and the power state notified from the platform and It is also possible to prevent malfunctions by prohibiting prescribed control operations for applications whose start requirements do not correspond to the operation requirements. Hereinafter, when all applications are started when the power status and start requirements are notified from the platform The embodiment will be described with reference to the flowchart of FIG.
The hardware configuration and software structure of the ECU are the same as those shown in FIGS.

  When the power supply state and the activation requirement are notified from the operation requirement notification unit 33, the CPU 11 starts the activation program for each application shown in the flowchart of FIG. 7, and the operation requirement of the corresponding application is determined from the notified power supply state and activation requirement. It is determined whether or not it is established (step 201). If it is determined that the operation requirement of the corresponding application is satisfied, the CPU 11 starts the application (step 202), and then ends the start program.

On the other hand, if it is determined in step 201 that the operation requirements of the application itself are not satisfied, the CPU 11 activates the application (step 203), and then sets the lamp and actuator output / driven by the corresponding application to the non-driving side. The control operation is prohibited (step 204). Next, the CPU 11 prohibits the detection (diagnosis process) of the connector terminal output by the corresponding application to another application or another ECU (step 205), and then ends the activation program.
Note that the CPU 11 executes the activation programs for the respective applications sequentially or simultaneously.

  As described above, even if all applications are started when the power status and startup requirements are notified from the platform, if the power status and startup requirements notified from the platform do not correspond to the operation requirements of the local application, the predetermined control operation is performed. By prohibiting the above, malfunction can be similarly prevented.

  In the above embodiment, whether or not each application meets the operation requirements is determined based on the power supply status and the start requirement notified from the platform, but the operation of each application is determined based on the power supply status and the start requirement by the platform program. The requirements can be determined and only necessary applications can be activated. Hereinafter, an embodiment in which the operation requirements of each application are determined by the platform program will be described.

FIG. 8 is a block diagram showing a configuration of the ECU including a software structure stored in the ROM 12 for causing the CPU 11 to execute various applications. The operation requirement notifying unit 33 of the platform program in FIG. However, since the hardware configuration and software structure of other ECUs are the same as those in FIGS. 1 and 2, detailed description thereof will be omitted.
The operation requirement determination unit 34 determines the operation requirement of each application based on the power supply state and the activation requirement input from the power supply state detection unit 31 and the activation requirement detection unit 32. This operation requirement determination unit The operation of the CPU 11 when executing the program 34 will be described with reference to the flowchart of FIG.

  The CPU 11 always executes the application operation requirement determination program shown in the flowchart of FIG. 9. When this program is started, the CPU 11 first determines whether or not a wake-up signal is received from the timer 16 every three hours ( Step 301) When it is determined that the wake-up signal is received from the timer 16, the power management application 21 is started (Step 302). When it is determined that the wake-up signal is not received from the timer 16, the battery 2 is connected. It is determined whether or not (step 303).

  If it is determined that the battery 2 is connected, the CPU 11 activates the power management application 21 (step 302). If it is determined that the battery 2 is not connected, the CPU 11 determines whether the ACC is turned on (step). 304). If it is determined that ACC is turned on, the CPU 11 activates the power management application 21 (step 302). If it is determined that ACC is not turned on, the CPU 11 determines whether a CAN wakeup signal has been received. If it is determined (step 305) and it is determined that the CAN wakeup signal has been received, the power management application 21 and the push start application 22 are activated (step 306).

  On the other hand, if it is determined in step 305 that the CAN wakeup signal has not been received, or after starting the power management application 21 in step 302, the CPU 11 determines whether or not a push switch operation has been performed (step 307) If it is determined that the push switch has been operated, the push start application 22 is activated (step 308). If it is determined that the push switch has not been operated, the CPU 11 determines whether or not the brake has been depressed based on the input of the STP (step 309). If it is determined that the brake has been depressed, the push start application 22 Is activated (step 308).

  If the power management application 21 and the push start application 22 are activated in step 306, if the push start application 22 is activated in step 308, or if it is determined in step 309 that the brake has not been depressed, the CPU 11 Whether or not the ignition switch is turned on (step 310). If it is determined that the ignition switch is turned on, the eco-run application 23 is started (step 311), and then the start / charge application 24 Start up. On the other hand, if it is determined in step 310 that the ignition switch is not turned on, the CPU 11 ends the program.

  As described above, since the platform program determines the operation requirements of each application based on the power supply state and activation requirements of the control device and operates only the necessary applications, it is possible to prevent malfunctions as described above.

  In this embodiment, only applications that satisfy the operation requirements are activated. However, as in the above-described embodiment 2, the platform program activates all applications based on the power supply state and activation requirements of the control device, and performs control. It is also possible to determine the operation requirement of each application based on the power supply state and activation requirement of the device, and prohibit a predetermined control operation for an application not corresponding to the operation requirement.

Similarly to the first embodiment, when each application determines that it does not meet the operation requirements, a variable that each application discloses to the other application is set to a predetermined fixed value, thereby causing a malfunction of the other application. Can be prevented.
For example, as shown in FIG. 10, in the platform program, when the eco-run application 23 meets the operation requirements and is operating, the start-up request signal from the eco-run application 23 is transmitted to the start / charge application 24, and the eco-run application 23 When the application 23 does not correspond to the operation requirement and the operation is stopped, the start / charge application 24 is notified by transmitting an always-off signal to the start / charge application 24 as a start request signal from the eco-run application 23. Malfunctions can be prevented.

  Further, when the operation of the application not corresponding to the operation requirement is stopped, the platform program notifies the other ECU via the communication IC 15 and the CAN bus 3 in the same manner as described above. By referring to the data of the application that does not correspond to the operation requirements in FIG. 5 and masking the process for detecting the abnormality, it is possible to prevent erroneous diagnosis by other ECUs.

  In the above embodiments, power management, push start, eco-run, and start / charge are described as examples of ECU applications. However, the present invention can also be applied to a vehicle electronic control device having other applications. Is possible.

It is a block diagram which shows the Example of ECU which mounted the control program for vehicles of this invention. It is a figure which shows the structure of the program memorize | stored in ROM in order to perform various applications. It is a table | surface which shows an example of the starting conditions of each application. It is a figure for demonstrating CAN wakeup. It is a flowchart which shows the effect | action of the starting program when a power supply state and a starting requirement are notified. It is a figure which shows the program structure in the case of determining with a predetermined | prescribed fixed value the variable which an own application discloses to other applications, when it determines with not satisfy | filling operation requirements. It is a flowchart which shows the effect | action of the other Example of the starting program when a power supply state and a starting requirement are notified. It is a figure which shows the structure of the other Example of ECU containing the structure of the software memorize | stored in ROM in order to perform various applications. It is a flowchart which shows an effect | action in the case of determining the operation requirement of each application based on a power supply state and a starting requirement. It is a figure which shows the program structure of a platform in case it determines with not satisfy | filling operation requirements, and the variable which each application exposes to another application is set to a predetermined fixed value.

Explanation of symbols

1 ECU
11 CPU
12 ROM
13 RAM
14 Power IC
15 Communication IC
16 timer
2 battery 3 CAN bus 21 power management application 22 push start application 23 eco-run application 24 start / charge application 31 power supply state detection unit 32 activation requirement detection unit 33 operation requirement notification unit 34 operation requirement determination unit

Claims (10)

A vehicle control program including a platform that is a hardware-dependent program and a plurality of applications that are programs for causing a computer to realize a vehicle control function,
The platform includes a program for realizing the function of notifying the power state and / or activation requirement of the control device to each application,
A vehicle control program comprising: a program for realizing a function for determining whether or not each application is activated based on a power state and / or activation requirement notified from the platform. A vehicle control program including a platform that is a hardware-dependent program and a plurality of applications that are programs for causing a computer to realize a vehicle control function,
The platform includes a program for realizing the function of notifying the power state and / or activation requirement of the control device to each application,
When each of the applications starts when the power status and / or activation requirements are notified from the platform, and the power status and / or activation requirements notified from the platform do not correspond to the operation requirements of the application, predetermined control is performed. A vehicle control program comprising a program for realizing a function for prohibiting operation. A vehicle control program including a platform that is a hardware-dependent program and a plurality of applications that are programs for causing a computer to realize a vehicle control function,
Vehicle control characterized in that the platform includes a program for determining an operation requirement of each application based on a power supply state and / or activation requirement of a control device, and realizing a function of starting only a necessary application Program. A vehicle control program including a platform that is a hardware-dependent program and a plurality of applications that are programs for causing a computer to realize a vehicle control function,
The above platform starts all applications based on the power supply status and / or startup requirements of the control device, and determines the operation requirements of each application based on the power supply status and / or startup requirements of the control device. A vehicle control program comprising a program for realizing a function for prohibiting a predetermined control operation for an application not corresponding to the requirement. In the vehicle control program according to claim 1 or 3,
A vehicle control program, characterized in that the application or the platform includes a program for realizing a function of setting a variable that an application that does not correspond to the operation requirement is disclosed to another application to a predetermined fixed value. In the vehicle control program according to claim 1 or 3,
When the operation of the application that does not correspond to the operation requirements of the application or the platform is stopped, the fact is notified to the other vehicle electronic control device, and the other vehicle electronic control device does not correspond to the operation requirement. A vehicle control program comprising a program for realizing a function of masking a process of detecting an abnormality with reference to application data. In the vehicle control program according to any one of claims 1 to 4,
A vehicle control program comprising: a program for causing the application or the platform to realize a function of prohibiting connector terminal abnormality detection processing output by an application not corresponding to the operation requirement. In the vehicle control program according to any one of claims 1 to 6,
A vehicle control program, wherein the power state is a state of power off, accessory power on, ignition on, or the like set by operating an ignition switch or operating a power control device. In the vehicle control program according to any one of claims 1 to 6,
The vehicle control program characterized in that the activation requirement is a condition such as a wake-up by communication from another vehicle electronic control device, a predetermined switch operation, or a wake-up at regular intervals by an internal timer .   An electronic control device for a vehicle, comprising: a computer that realizes the function according to the claim based on the vehicle control program according to any one of claims 1 to 9.

Images