JP2021133829A - Vehicle control device - Google Patents

Abstract

To curb generation of erroneous failure detection and communication abnormality in a vehicle control device mounted with a plurality of ECUs.SOLUTION: A vehicle control device comprises a plurality of control units which can communicate with each other. The plurality of control units have a superior unit 21 and subordinate units managed by the superior unit 21. Any one of the subordinate units has a start signal input section into which a signal to start predetermined operation of the vehicle control device is input. The superior unit 21 has: a unit identification section 212 which identifies the subordinate unit to be used for executing the predetermined operation among the subordinate units when the signal is input through the start signal input section; a start-up request instruction section 213 which outputs a start-up request instruction to the identified subordinate unit; and an operation start-up instruction section 215 which outputs an operation start-up instruction for the predetermined operation to the subordinate unit identified by the unit identification section 212 after the lapse of a predetermined period since the start-up request instruction is output.SELECTED DRAWING: Figure 2B

Description

The present invention relates to a vehicle control device that controls a vehicle.

Conventionally, as this type of device, a plurality of ECUs (electronic control units) are provided, and each ECU periodically communicates with another ECU, and the presence or absence of failure of the other ECU is determined from the information obtained by the communication. A device for detecting is known (see, for example, Patent Document 1).

JP-A-2002-314632

In a device including a plurality of ECUs, when a single ECU receives a start request, the other ECUs are started by the single ECU after the single ECU is started. Therefore, in a device including a plurality of ECUs, each ECU may be started at a different timing. Therefore, in a configuration such as the device described in Patent Document 1 that constantly detects a failure, when each ECU is started at a different timing, a communication abnormality may occur with an ECU that has not been started, or a communication abnormality may occur. False detection of failure may occur.

One aspect of the present invention is a vehicle control device including a plurality of control units capable of communicating with each other. One of the lower units of the above has a signal input unit for inputting a signal for starting a predetermined operation of the vehicle control device, and the upper unit has a plurality of lower units when a signal is input by the signal input unit. A unit identification unit that specifies the lower unit used to execute a predetermined operation, a first command unit that outputs an activation request command to the lower unit specified by the unit identification unit, and an activation request by the first command unit. It has a second command unit that outputs an operation start command of a predetermined operation to a lower unit specified by the unit specifying unit after a predetermined time has elapsed from the output of the command.

According to the present invention, it is possible to suppress erroneous detection of failure and occurrence of communication abnormality in a vehicle control device including a plurality of ECUs.

The figure which shows the schematic structure of the vehicle to which the vehicle control device which concerns on embodiment of this invention is applied. The figure which shows the schematic structure of the vehicle control device which concerns on embodiment of this invention. The figure which shows the functional structure of the lower unit provided in the vehicle control device which concerns on embodiment of this invention. The figure which shows the functional structure of the superordinate unit provided in the vehicle control device which concerns on embodiment of this invention. The flowchart which shows an example of the process executed by the lower unit of the vehicle control device which concerns on embodiment of this invention. The flowchart which shows an example of the process executed by the higher-level unit of the vehicle control device which concerns on embodiment of this invention. The figure which shows an example of the unit identification table. It is a time chart which shows an example of the operation of the vehicle control device which concerns on embodiment of this invention. It is a time chart which shows other example of the operation of the vehicle control device which concerns on embodiment of this invention. The figure which shows the example of another schematic structure of the vehicle control device which concerns on embodiment of this invention.

Hereinafter, an embodiment of the present invention will be described with reference to FIGS. 1A to 8. The vehicle control device according to the embodiment of the present invention is applied to a vehicle having a plurality of ECUs.

By the way, in recent years, vehicles having a timer function such as a timer charging function and a timer air conditioner function that start a predetermined operation (charging operation or air conditioner operation) at a preset time have appeared. In order to operate such a function when the power of the vehicle is turned off, it is necessary to activate the ECU required for executing the predetermined operation at a preset time. At that time, when there are a plurality of ECUs required to execute the predetermined operation, first, a single ECU is started by a timer, and then the activated single ECU is required to execute the predetermined operation. A start request command is output to other ECUs to start those ECUs. However, in such an activation method, a deviation occurs in the activation timing between the ECU activated by the timer and the ECU activated by the activation request command from the ECU. In particular, when each ECU is hierarchically connected, a difference occurs in the time when the start request command reaches each ECU, so that the difference in start timing between the ECUs becomes even larger. In such a situation, if each ECU starts the communication process for failure detection immediately after starting, a communication abnormality occurs with an ECU that has not been started yet, or a failure is erroneously detected. May occur.

Therefore, in the present embodiment, in a vehicle equipped with the timer charging function and the timer air conditioner function as described above, each ECU is controlled so as not to cause a false detection of a communication abnormality or a failure when those functions are operated. The vehicle control device will be described.

First, the configuration of the vehicle to which the present embodiment is applied will be described. FIG. 1A is a diagram showing a schematic configuration of a vehicle 1 to which the vehicle control device 100 according to the embodiment of the present invention is applied. As shown in FIG. 1A, the vehicle 1 includes an air conditioner 2, a battery 3, a charging device 4, and an operation unit 5 in addition to the vehicle control device 100. The vehicle control device 100 controls the drive of the air conditioner 2 to realize the air conditioner function. Further, the vehicle control device 100 realizes a charging function of controlling the charging device 4 to supply electric power from external electric power to the battery 3 to charge the battery 3. The battery 3 is, for example, a nickel storage battery or a lithium storage battery.

The operation unit 5 includes an operation switch for setting the air conditioner function and the charging function. In the present embodiment, the operation unit 5 has a touch panel (not shown) and displays a touch switch on the touch panel. The operation unit 5 also functions as a display unit for displaying the setting contents of the air conditioner function and the charging function, the status of the air conditioner 2 and the battery 3, and the like on the touch panel.

The vehicle 1 may include a device other than the air conditioner 2 and the charging device 4. Further, the vehicle 1 may have a function other than the air conditioner function and the charging function.

FIG. 1B is a diagram showing a schematic configuration of a vehicle control device 100 according to an embodiment of the present invention.
As shown in FIG. 1B, the vehicle control device 100 includes a plurality of ECUs (Electric Control Units) 21 to 27 connected by an in-vehicle communication network such as CAN (Controller Area Network). Hereinafter, the ECU may be simply referred to as a control unit.

In the present embodiment, as shown in FIG. 1B, the plurality of ECUs 21 to 27 are assigned to and provided in a plurality of domains D1 and D2 (two in FIG. 1B). For example, domains D1 are assigned ECUs 21, 23 to 25, and domain D2 is assigned ECUs 22, 26, 27. Further, in the domains D1 and D2, each ECU is hierarchically connected.

The ECUs 21 and 22 assigned to the upper layers communicate with a device connected to a communication network outside the vehicle via a TCU (telematics control unit) (not shown), and domain control that relays communication between domains. It is a unit. Hereinafter, the ECUs 21 and 22 will be referred to as DCUs (Domain Control Units) 21 and 22. Further, the DCUs 21 and 22 assigned to the upper hierarchy are referred to as upper units, and the ECUs 23 to 25 and the ECUs 26 and 27 assigned to the lower hierarchy are referred to as lower units.

In the present embodiment, the ECU 23 of the domain D1 is an air conditioner ECU that controls the air conditioner 2. The ECU 23 controls the temperature and air volume of the air conditioner 2 based on the information acquired from the ECUs 24 and 25 of the same domain, and controls the transmission of information indicating the state of the air conditioner 2 to those ECUs. Further, the ECU 26 of the domain D2 is a charging ECU that controls the charging device 4. The ECU 26 adjusts the power supply to the charging device 4 based on the information acquired from the ECU 27 of the same domain and the ECU 25 of a different domain (domain D1), and transmits information indicating the state of the charging device 4 to those ECUs. Control to do.

Next, the functional configuration of the vehicle control device 100 according to the embodiment of the present invention will be described. First, the functional configuration of the lower units (ECUs 23 to 27) will be described. FIG. 2A is a diagram showing a functional configuration of a lower unit included in the vehicle control device 100 according to the embodiment of the present invention. Since the functional configuration of each lower unit is the same, the functional configuration of the ECU 23 will be described here.

As shown in FIG. 2A, the ECU 23 includes a calculation unit 230 such as a CPU and a storage unit 235 such as a ROM, RAM, and hard disk. The calculation unit 230 functions as a start signal input unit 231, a start request input unit 232, a timer control unit 233, and an execution unit 234 by executing the program stored in the storage unit 235.

The start signal input unit 231 inputs a signal from a timer (not shown) (hereinafter, referred to as a start signal or a start request signal). When the start signal input unit 231 inputs the start signal, the start signal input unit 231 outputs a start request command to its own higher-level unit (DCU21 in this case) and starts the ECU 23. Note that "activating the ECU 23" means making the execution unit 234 operable. Further, the timer may be a timer included in the ECU 23 or a timer installed outside the ECU 23.

The start request input unit 232 starts the ECU 23 when a start request command is input from its own higher-level unit (DCU21 in this case).

The timer control unit 233 includes information for operating the timer charging function and the timer air conditioner function at a designated time, that is, information for starting a predetermined operation (charging operation or air conditioner operation) at a designated time (hereinafter, timer setting information). Control the timer based on (call). In the present embodiment, the timer control unit 233 inputs timer setting information from the operation unit 5, sets a count value in the timer based on the input timer setting information, and starts counting the timer. The timer setting information may be input from other than the operation unit 5, and may be input from, for example, a user terminal connected to a communication network outside the vehicle. The execution unit 234 executes a process of controlling the air conditioner 2 and a communication process for detecting a failure. Although the operation of the execution unit differs for each lower unit, communication processing for failure detection is performed in the execution unit of all lower units.

Next, the functional configuration of the upper unit (DCU21,22) will be described. FIG. 2B is a diagram showing a functional configuration of a higher-level unit included in the vehicle control device 100 according to the embodiment of the present invention. Since the functional configuration of each upper unit is the same, the functional configuration of the DCU 21 will be described here.

As shown in FIG. 2B, the DCU 21 includes a calculation unit 210 such as a CPU and a storage unit 216 such as a ROM, RAM, and hard disk. By executing the program stored in the storage unit 216, the calculation unit 210 functions as a start request input unit 211, a unit identification unit 212, a start request command unit 213, a predetermined time derivation unit 214, and an operation start command unit 215. do.

The activation request input unit 211 activates the DCU 21 when an activation request command is input from a lower unit in the domain or when an activation request command is input from a DCU of another domain. It should be noted that "activating the DCU 21" means making each part 212 to 216 in an operable state.

When the start request input unit 211 inputs a start request command from a lower unit in the domain, the unit identification unit 212 identifies the type of the predetermined operation and the lower unit required to execute the predetermined operation from the start request command. do. The method of specifying the lower unit in the unit specifying unit 212 will be described later. In this embodiment, the lower units required to execute the air conditioner operation are ECUs 23, 24, and 25. Further, the lower units required to execute the charging operation are the ECUs 26 and 27 and the ECU 25.

The activation request command unit 213 outputs an activation request command to the lower unit specified by the unit identification unit 212. The predetermined time derivation unit 214 predicts (derives) a predetermined time from the output of the activation request command unit 213 to the activation of all the lower units to which the activation request command is output.

The operation start command unit 215 is a command for causing the lower unit specified by the unit identification unit 212 to execute a predetermined operation after the predetermined time has elapsed since the start request command was output by the start request command unit 213. (Hereinafter referred to as an operation start command) is output.

In addition to the above program, the storage unit 216 stores information necessary for the predetermined time derivation unit 214 to derive the predetermined time. Here, the information stored in the storage unit 216 will be described. In the present embodiment, the activation time (hereinafter, referred to as the first activation time) when the lower unit activates the lower unit belonging to the same domain is 5 seconds. Further, the activation time when the lower unit activates the lower unit belonging to the adjacent domain (hereinafter, referred to as the second activation time) is 7 seconds, which is obtained by adding 2 seconds to the first activation time. Further, the activation time when the lower unit activates the lower unit belonging to the domain further adjacent to the adjacent domain (hereinafter referred to as the third activation time) is 9 seconds, which is obtained by adding 2 seconds to the second activation time. And. That is, in the present embodiment, the activation time when the lower unit activates the lower units belonging to the adjacent domain by n is the time obtained by adding (2 × n) seconds to the first activation time. In this case, the predetermined time can be derived by using the first start-up time and the domain addition time which is the difference (2 seconds) between the first start-up time and the second start-up time. Therefore, information indicating at least the first activation time and the domain addition time may be stored in the storage unit 216.

FIG. 3 is a flowchart showing an example of processing executed by a lower unit of the vehicle control device 100. The process shown in FIG. 3 is repeatedly executed at a predetermined cycle while power is being supplied to the lower unit. It is assumed that the lower unit is supplied with electric power from the battery 3 or the like even when the electric power of the vehicle 1 is off. Since the processes executed in each lower unit are the same, the processes executed by the air conditioner ECU (ECU 23) will be described below.

First, in step S301, the start signal input unit 231 of the ECU 23 determines whether or not the start signal from the timer has been received. If affirmed in step S301, the ECU 23 is activated in step S302. As a result, the execution unit 234 becomes operable. Next, in step S303, the execution unit 234 outputs a start request command to its own higher-level unit, that is, DCU21, and proceeds to step S306.

On the other hand, if it is denied in step S301, in step S304, the activation request input unit 232 confirms whether or not the activation request command has been received from the DCU21 of the higher-level unit. If denied in step S304, the process returns to step S301. If affirmed in step S304, the ECU 23 is activated in step S305. As a result, the execution unit 234 becomes operable.

In step S306, the execution unit 234 determines whether or not the operation start command has been received from the DCU 21. Step S306 is repeated until affirmed. If affirmed in step S304, the execution unit 234 starts the operation in step S307.

FIG. 4 is a flowchart showing an example of processing executed by the higher-level unit of the vehicle control device 100. The process shown in FIG. 4 is repeatedly executed at a predetermined cycle while power is being supplied to the upper unit. It is assumed that the upper unit is supplied with electric power from the battery 3 or the like even when the electric power of the vehicle 1 is off. Further, since the processes executed in each higher-level unit are the same, the processes executed by the DCU 21 will be described below.

First, in step S401, the activation request input unit 211 of the DCU 21 determines whether or not the activation request command has been input from a lower unit in the domain or from another domain. Step S401 is repeated until affirmed. If affirmed in step S401, the activation request input unit 211 activates the DCU 21 in step S402. As a result, each part 212 to 215 becomes operable. Next, in step S403, the activation request input unit 211 determines whether or not the activation request command input in step S401 is input from a lower unit in the domain. If denied in step S403, the process proceeds to step S409. If affirmed in step S403, the process proceeds to step S404.

In step S404, the unit identification unit 212 outputs a standby instruction to a lower unit of the output source of the activation request command. The standby instruction is an instruction for not executing at least the communication process for failure detection. Next, in step S405, the unit specifying unit 212 identifies a predetermined operation specified by the activation request command input from the lower unit in the domain and a lower unit necessary for executing the predetermined operation.

Here, a method of specifying a lower unit in the unit specifying unit 212 will be described. It is assumed that the DCU 21 stores in advance a table (hereinafter referred to as a unit identification table) for storing each predetermined operation and a lower unit required for executing each predetermined operation in association with each other. FIG. 5 is a diagram showing an example of a unit identification table. As shown in FIG. 5, the unit identification table stores the identification information (operation ID) of each predetermined operation and the identification information (unit ID) of the lower unit required for executing each predetermined operation in association with each other. In addition, ECU_A to ECU_E in the figure are unit IDs of ECUs 23 to 27, respectively. The unit identification unit 212 refers to the unit identification table stored in the storage unit 216 to specify lower-level units necessary for executing each predetermined operation.

For example, when the start signal input unit 231 of the air conditioner ECU (ECU 23) inputs the start signal of the air conditioner operation, the start signal input unit 231 outputs the operation ID of the air conditioner operation to the DCU 21 of the upper unit together with the start request command. Then, the unit specifying unit 212 of the DCU 21 specifies the type of predetermined operation (here, air conditioner operation) from the operation ID input from the lower unit. Further, the unit identification unit 212 reads the unit ID corresponding to the operation ID from the unit identification table, and identifies lower units (here, ECUs 23, 24, 25) necessary for executing the air conditioner operation.

Next, in step S406, the predetermined time out-licensing unit 214 derives a predetermined time from the output of the activation request command to the lower-level units specified in step S405 to the activation of all of the lower-level units. For example, when all the lower units specified in step S405 belong to the same domain, the predetermined time derivation unit 214 derives the first predetermined time (5 seconds) as the predetermined time.

Next, in step S407, the activation request command unit 213 outputs an activation request command to the lower unit specified by the unit identification unit 212 to activate the lower unit. At that time, the activation request command unit 213 may output a standby instruction to a lower unit to which the activation request command is output. When the lower unit specified by the unit identification unit 212 includes a lower unit belonging to another domain, the activation request command unit 213 sends the identification information of the lower unit together with the activation request command of the other domain. Output to the upper unit (DCU).

When a predetermined time (predetermined time derived in step S406) has elapsed since the start request command unit 213 outputs the start request command, in step S408, the operation start command unit 215 is the lower unit to which the start request command is output. The operation start command is output to. As a result, the predetermined operation is started by the lower unit specified by the unit specifying unit 212. When the lower unit specified by the unit identification unit 212 includes a lower unit belonging to another domain, the operation start command unit 215 sends the identification information of the lower unit together with the operation start command of the other domain. Output to the upper unit (DCU).

On the other hand, when the activation request input unit 211 of the DCU 21 inputs an activation request command from another domain in step S401, it is denied in step S403, and the processes of steps S409 to S410 are executed. For example, when the charging ECU (ECU 26) of the domain D2 inputs the start signal of the charging operation, the ECU 25 of the domain D1 is included in the lower unit required to execute the charging operation. A start request command is output.

In step S409, the unit specifying unit 212 identifies the lower unit to which the activation request command should be output from the identification information of the lower unit associated with the activation request command input in step S401. Next, in step S410, the activation request command unit 213 outputs an activation request command to the lower unit specified by the unit identification unit 212 to activate the lower unit. At that time, the activation request command unit 213 may output a standby instruction to a lower unit to which the activation request command is output.

Here, with reference to FIGS. 6 and 7, the operation of the vehicle control device 100 when the lower unit inputs a start signal of a predetermined operation when the power supply of the vehicle 1 is off will be described.

FIG. 6 is a time chart showing the operation of the vehicle control device 100 when the air conditioner ECU (ECU 23) inputs the start signal of the air conditioner operation. As shown in FIG. 6, at the time point t1, the ECU 23 inputs the start signal of the air conditioner operation (step S301). As a result, the ECU 23 is activated (step S302). At the time point t2, the ECU 23 outputs a start request command to its higher-level unit DCU21 (step S303). As a result, DCU21 is activated (steps S401 and S402). At the time point t3, the DCU 21 outputs a standby command to the ECU 23 (steps S403 and S404). The ECU 23 that has input the standby command stands by without starting the operation.

At time point t4, the DCU 21 identifies the lower unit required to perform the air conditioner operation (step S405). Here, ECUs 23, 24, and 25 are specified. Further, the DCU 21 derives a predetermined time until all the specified lower units are activated (step S406). Since the ECUs 23, 24, and 25 all belong to the same domain, the first predetermined time (5 seconds) is derived as the predetermined time. Then, when the predetermined time is derived, the DCU 21 outputs a start request command to all the specified lower units (step S407). At this time, the DCU 21 does not output a start request command to the ECU 23 that has already been started. At the time point t5 when a predetermined time elapses from the time point t4, the DCU 21 outputs an operation start command to the ECUs 23, 24, 25 (step S408). As a result, the air conditioner operation by the ECUs 23, 24, and 25 is started (steps S306 and S307).

FIG. 7 is a time chart showing the operation of the vehicle control device 100 when the charging ECU (ECU 26) inputs a start signal for starting the charging operation at a designated time. In the timer charging function, when the ECU 26 inputs a start signal, it is necessary to activate the ECU 25 belonging to the domain next to the ECU 26. Therefore, in that respect, the operation of the vehicle control device 100 shown in FIG. 7 is different from the operation shown in FIG.

As shown in FIG. 7, at the time point t11, the ECU 26 inputs the start signal of the charging operation (step S301). As a result, the ECU 26 is activated (step S302). At the time point t12, the ECU 26 outputs a start request command to its higher-level unit DCU22 (step S303). As a result, DCU22 is activated (steps S401 and S402). At the time point t13, the DCU 22 outputs a standby command to the ECU 26 (steps S403 and S404). The ECU 26 that has input the standby command stands by without starting the operation.

At time point t14, the DCU 22 identifies the lower unit required to perform the air conditioner operation (step S405). Here, ECUs 26 and 27 of the same domain and ECU 25 of different domains are specified. Further, the DCU 22 derives a predetermined time until all the specified lower units are activated (step S406). Since the ECU 25 belongs to a domain (adjacent domain) different from that of the ECU 26, the time (7 seconds) obtained by adding the domain addition time (2 seconds) to the first predetermined time (5 seconds) is derived as the predetermined time. Will be done. Then, when the predetermined time is derived, the DCU 22 outputs a start request command to all the specified lower units (step S407). At this time, the DCU 22 does not output a start request command to the ECU 26 that has already been started. Further, a start request command for the ECU 25 belonging to a domain different from the DCU 22 is output to the ECU 25 via the DCU 21. At this time, first, the DCU 21 is activated in response to the activation request command from the DCU 22 (steps S401 and S402). Then, the activated DCU21 outputs a start request command to the ECU 25 at the time point t15 (steps S403, S409, S410). As a result, the ECU 25 is activated (steps S304 and S305). At the time point t16 when a predetermined time elapses from the time point t14, the DCU 22 outputs an operation start command to the ECUs 26 and 27 and the ECU 25. As a result, the charging operation by the ECUs 26 and 27 and the ECU 25 is started (steps S306 and S307). The operation start command for the ECU 25 is output to the ECU 25 via the DCU 21.

As described above, in the present embodiment, the predetermined operation is not started until all the lower units that have received the start request command have been started. Therefore, even when the predetermined operation includes communication for failure detection, it is possible to suppress the occurrence of the above-mentioned communication abnormality or false detection of failure.

According to the embodiment of the present invention, the following effects can be obtained.
(1) The vehicle control device 100 includes a plurality of control units 21 to 27 capable of communicating with each other. The plurality of control units 21 to 27 have an upper unit (DCU 21 and 22) and a lower unit (ECU 23 to 27) managed by the upper unit. Any of the lower units has a start signal input unit (signal input unit) 231 for inputting a signal (start signal) for starting a predetermined operation of the vehicle control device 100. When the start signal is input by the signal input unit 231, the upper unit has a unit identification unit 212 that specifies the lower unit used to execute a predetermined operation from the lower units and a lower unit specified by the unit identification unit 212. It is specified by the unit identification unit 212 after a predetermined time has elapsed since the activation request command was output by the activation request command unit (first command unit) 213 and the first command unit 213 that output the activation request command. It has an operation start command unit (second command unit) 215 that outputs an operation start command of a predetermined operation to the lower unit.

As a result, when a plurality of lower units are activated, the operation start timing of each lower unit can be aligned. Therefore, it is possible to prevent communication processing (communication processing for failure detection, etc.) from being performed with a lower unit that has not been activated. Therefore, it is possible to suppress erroneous detection of communication abnormality or failure that may occur when each lower unit is started at a different timing.

(2) The predetermined operation includes a failure detection operation of the DCUs 21 and 22 and the ECUs 23 to 27 via communication. As a result, when the timer function such as the charging function or the timer air conditioner function is operated, each lower unit can start the failure detection operation without causing a communication abnormality or a false detection of the failure.

(3) When a plurality of lower units are specified by the unit identification unit 212, the first command unit 213 outputs an activation request command to each lower unit specified by the unit identification unit 212. Further, the second command unit 215 starts the operation of the predetermined operation for each lower unit specified by the unit identification unit 212 after a predetermined time has elapsed after the activation request command is output by the first command unit 213. Output the command. As a result, even when a predetermined operation started by a timer function such as a timer charging function or a timer air conditioner function is executed by a plurality of lower units, it is possible to suppress false detection of a communication abnormality or failure.

(4) The upper unit includes a storage unit 216 that stores in advance the start-up time from when the start request command is output by the first command unit 213 until all of the plurality of lower units are in a communicable state. Then, the predetermined time derivation unit 214 derives the start-up time stored in the storage unit 216 as a predetermined time. As a result, when all the lower units used to execute the predetermined operation become communicable, the operations of those lower units can be started, so that false detection of communication abnormality or failure can be suppressed more reliably. can do.

(5) The vehicle control device 100 has a first upper unit (DCU21) and a second upper unit (DCU22) that belong to different domains. When the lower unit (ECU 26 or ECU 27 of the domain D2) of a different domain is specified by the unit identification unit 212 of the first upper unit, the predetermined time out-licensing unit 214 of the first upper unit is stored in the storage unit 216 of the first upper unit. A predetermined addition time (domain addition time) is added to the stored startup time to derive a predetermined time. As a result, even if the subordinate units used to execute a predetermined operation include subordinate units belonging to different domains, when all of the subordinate units become communicable, the operation of those subordinate units is performed. You can get started.

The configuration of the vehicle control device 100 is not limited to the configuration shown in FIG. 1B. For example, as shown in FIG. 8, a plurality of ECUs included in the vehicle control device 100 may be assigned to and provided in the domain D3 and the domain D4 connected via the gateway (relay device) 7. However, when the lower unit starts the lower unit belonging to the adjacent domain connected via the gateway 7, the start time is longer than the start time (the second start time) when the lower unit does not go through the gateway 7. .. Therefore, for the startup time when the lower unit starts the lower unit belonging to the adjacent domain connected via the gateway 7, the gateway addition time (3 seconds) is added to the second startup time (7 seconds) 10. Let it be seconds. That is, when the lower unit activates the lower unit belonging to the domain next to n, the activation time when m gateways are installed between the domain next to n is the first activation time (2). It is the time obtained by adding × n) seconds and (3 × m) seconds. Therefore, information indicating the gateway addition time may be stored in the storage unit 216.

The above embodiment can be transformed into various forms. Hereinafter, a modified example will be described. In the above embodiment, a plurality of control units of the vehicle control device are assigned to two domains, but the plurality of control units may be assigned to three or more domains, or may be assigned to one domain. May be assigned.

In the above embodiment, the activation time (first activation time) when the lower unit activates the lower unit belonging to the same domain is set to 5 seconds, but the activation time of each lower unit may be different. Therefore, information indicating the start-up time for each lower unit may be stored in advance in a storage unit or the like of the DCU, and the DCU may determine the first start-up time based on the information. For example, the longest start-up time among the start-up times of each lower unit required to execute a predetermined operation may be set as the first start-up time. If they are the longest but different from each other, the longest start-up time among those start-up times may be set as the first start-up time.

The above description is merely an example, and the present invention is not limited to the above-described embodiments and modifications as long as the features of the present invention are not impaired. It is also possible to arbitrarily combine one or a plurality of the above-described embodiments and the modified examples, and it is also possible to combine the modified examples.

100 Vehicle control device, 21,22 DCU, 23-27 ECU, 212 Unit identification unit, 213 Start request command unit, 215 Operation start command unit, 231 Start signal input unit

Claims (5)

A vehicle control device having a plurality of control units capable of communicating with each other.
The plurality of control units include a higher-level unit and a plurality of lower-level units managed by the higher-level unit.
One of the plurality of lower units has a signal input unit for inputting a signal for starting a predetermined operation of the vehicle control device.
The upper unit is
When the signal is input by the signal input unit, a unit specifying unit that specifies a lower unit used to execute the predetermined operation from the plurality of lower units, and a unit specifying unit.
A first command unit that outputs a start request command to a lower unit specified by the unit identification unit, and a first command unit.
After a predetermined time has elapsed from the output of the activation request command by the first command unit, the second command unit outputs the operation start command of the predetermined operation to the lower unit specified by the unit identification unit. And, a vehicle control device characterized by having. In the vehicle control device according to claim 1,
The vehicle control device, wherein the predetermined operation includes a failure detection operation of the upper unit and the plurality of lower units via communication. In the vehicle control device according to claim 1 or 2.
When a plurality of lower units are specified by the unit identification unit, the first command unit outputs the activation request command to each lower unit specified by the unit identification unit.
The second command unit performs the predetermined operation with respect to each of the lower units specified by the unit identification unit after the predetermined time has elapsed after the activation request command is output by the first command unit. A vehicle control device that outputs the operation start command. In the vehicle control device according to any one of claims 1 to 3.
The upper unit is
The first command unit includes a storage unit that stores in advance the start-up time from when the start request command is output until all of the plurality of lower units are in a communicable state.
A vehicle control device further comprising a predetermined time out-licensing unit that derives the start-up time stored in the storage unit as the predetermined time. In the vehicle control device according to claim 4.
It has a first upper unit and a second upper unit that belong to different domains.
The predetermined time derivation unit of the first upper unit is
When a lower unit of a different domain is specified by the unit specifying unit of the first upper unit, a predetermined addition time is added to the activation time stored in the storage unit of the first upper unit, and the predetermined addition time is added. A vehicle control device characterized by deriving time.

Images