Electric vehicle, control method for electric vehicle, and control device for electric vehicle

Abstract

To enable a period to update control program of a plurality of control devices mounted on an electric vehicle to be secured while curbing an increase in power consumption when updating the control program.SOLUTION: When an OTA request is made (Yes in S100), an update ECU executes processes including: a step (S102) to acquire an ECU to be a subject of OTA; a step (S108) to request the ECU to be the subject of OTA to execute an update process when the ECU to be the subject of the OTA is the ECU to be operated while an electric vehicle is traveling (Yes in S104) and the electric vehicle is performing external charging (Yes in S106); and a step (S114) to request the ECU to be the subject of the OTA to execute the update process when the ECU to be the subject of the OTA is the ECU to be operated while the electric vehicle is performing the external charging (No in S104 and Yes in S110) and the electric vehicle is traveling (Yes in S112).SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present disclosure relates to updating of control programs for a plurality of control devices mounted on an electric vehicle. [Background technology]

[0002] An electric vehicle is equipped with a plurality of control devices that control the operation of various on-board electrical devices. When updating one of the control programs of the plurality of control devices, the update can be performed using data transmitted via wires, or using update information received via wireless communication from a server outside the electric vehicle, a so-called OTA (over-the-air) update. Over When updating a control program using this type of OTA technology, it is necessary to ensure that the power supply to the control device being updated is not interrupted.

[0003] For example, JP 2013-151222 A (Patent Document 1) discloses a technology that prohibits the supply of power from the auxiliary battery to devices other than those related to updating the charging control program when it is determined that the power supply voltage of the auxiliary battery of a vehicle is below a predetermined value. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2013-151222 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, when the control programs of multiple control devices need to be updated, the power consumption during the update may increase if the control programs are updated in parallel in the multiple control devices. Furthermore, when the control programs require a long time to be updated, it may not be possible to secure the time required for the update, or the update may be necessary, making it impossible to suppress the decrease in the charge level of the auxiliary battery.

[0006] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to provide an electric vehicle, a control method for an electric vehicle, and a control device for an electric vehicle that make it possible to ensure an update period while suppressing an increase in power consumption when updating the control programs of multiple control devices mounted on the electric vehicle. [Means for solving the problem]

[0007] An electric vehicle according to an aspect of the present disclosure includes a power storage device capable of being charged using a power source external to the vehicle, a drive motor that drives the vehicle using power from the power storage device, a receiving device that receives predetermined information from outside the vehicle, and a control system configured with a plurality of control devices including a first control device and a second control device. The first control device uses a first control program to control devices that operate during charging of the power storage device using the external power source. The second control device uses a second control program to control devices that operate during running of the vehicle using the drive motor. When the control system receives update information for the first control program using the receiving device, the control system updates the first control program using the update information while the vehicle is running. When the control system receives update information for the second control program using the receiving device, the control system updates the second control program using the update information while the vehicle is charging.

[0008] In this way, the first control program of the first control device is updated while the vehicle is traveling, and the second control program of the second control device is updated while the vehicle is charging, thereby ensuring a period for updating. Furthermore, by updating the first control program and the second control program in different periods, an increase in power consumption during updating can be suppressed compared to a case where the first control program and the second control program are updated in parallel.

[0009] In one embodiment, the plurality of control devices further includes a third control device that controls, using a third control program, a controlled device that operates during charging and while the vehicle is running. When the control system receives update information for the third control program using the receiving device, the control system updates the third control program using the update information while the vehicle is stopped.

[0010] In this way, the third control program of the third control device that operates during charging and traveling is updated while the vehicle is stopped, so that a period for updating can be secured. Furthermore, by updating the third control program in a different period from that for updating the first control program and the second control program, an increase in power consumption during updating can be suppressed compared to the case where the first to third control programs are updated in parallel.

[0011] In yet another embodiment, the electric vehicle further includes an auxiliary battery that supplies power to the third control device. When the control system receives update information for the third control program using the receiving device, the control system charges the auxiliary battery at least during charging and while traveling. When the amount of power stored in the auxiliary battery while stopped is equal to or greater than a threshold value that allows updating of the third control program, the control system updates the third control program using the update information.

[0012] In this way, the third control program can be updated without causing a shortage of power in the auxiliary battery while the vehicle is stopped.

[0013] In yet another embodiment, when the control system receives update information for the first control program using a receiving device, if the increase in power consumption associated with updating the first control program would result in a driving distance shorter than the distance to the vehicle's destination, the control system does not update the first control program while the vehicle is traveling.

[0014] In this manner, when power consumption due to updating the first control program would prevent the vehicle from reaching its destination, the first control program is not updated while the vehicle is traveling, so that the vehicle can reach its destination.

[0015] In yet another embodiment, when the control system receives update information for the second control program using a receiving device, if the increase in power consumption associated with updating the second control program prevents charging of the power storage device from being completed by the departure time, the control system does not update the second control program during charging.

[0016] In this way, if power is consumed in conjunction with updating the second control program and charging of the power storage device cannot be completed by the departure time, the second control program is not updated during charging, so that charging of the power storage device can be completed by the departure time.

[0017] A control method for an electric vehicle according to another aspect of the present disclosure is a control method for an electric vehicle including a power storage device that can be charged using a power source external to the vehicle, a drive motor that drives the vehicle using power from the power storage device, a receiving device that receives predetermined information from outside the vehicle, and a control system configured by a plurality of control devices including a first control device and a second control device. The first control device uses a first control program to control devices that operate during charging of the power storage device using the external power source. The second control device uses a second control program to control devices that operate during running of the vehicle using the drive motor. The control method includes, when update information for the first control program is received using the receiving device, a step of updating the first control program using the update information while the vehicle is running, and, when update information for the second control program is received using the receiving device, a step of updating the second control program using the update information while the vehicle is charging.

[0018] A control device for an electric vehicle according to yet another aspect of the present disclosure is a control device for an electric vehicle including a power storage device that can be charged using a power source external to the vehicle, a drive motor that drives the vehicle using power from the power storage device, and a receiving device that receives predetermined information from outside the vehicle. The control device is configured to be able to communicate with a first control device that uses a first control program to control devices that are subject to control and operate while the power storage device is being charged using the external power source, and a second control device that uses a second control program to control devices that are subject to control and operate while the vehicle is traveling using the drive motor. When the control device receives update information for the first control program using the receiving device, the control device requests the first control device to update the first control program using the update information while the vehicle is traveling. When the control device receives update information for the second control program using the receiving device, the control device requests the second control device to update the second control program using the update information while the vehicle is being charged. Effect of the Invention

[0019] According to the present disclosure, it is possible to provide an electric vehicle, a control method for an electric vehicle, and a control device for an electric vehicle that make it possible to ensure an update period while suppressing an increase in power consumption when updating the control programs of multiple control devices installed in the electric vehicle. [Brief description of the drawings]

[0020] [Figure 1] 2 is a diagram for explaining an example of a configuration of a management server and a plurality of electric vehicles capable of communicating with the management server; FIG. [Diagram 2] 1 is a diagram illustrating an example of a configuration of an electric vehicle according to an embodiment of the present invention. [Diagram 3] 5 is a flowchart illustrating an example of a process executed by an updated ECU. [Figure 4] 4 is a timing chart showing an example of an operation of the update ECU. [Diagram 5] 10 is a flowchart showing an example of a process executed by an updated ECU in a modified example. [Figure 6] 10 is a flowchart showing another example of the process executed by the updated ECU in the modified example. [Figure 7] 10 is a flowchart showing yet another example of the process executed by the updated ECU in the modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are designated by the same reference characters and their description will not be repeated.

[0022] FIG. 1 is a diagram for explaining an example of the configuration of a management server 10 and a plurality of electric vehicles 1, 2, 3, and 4 (hereinafter referred to as “1 to 4”) capable of communicating with the management server 10. As shown in FIG.

[0023] As shown in FIG. 1, the management server 10 is configured to be able to communicate with a plurality of electric vehicles including electric vehicles 1-4 via a base station 7 provided on a communication network 6. Identification information for identifying the electric vehicles 1-4 is stored in advance in the management server 10. The identification information is unique information set for each vehicle. The management server 10 further stores version information, revision information and update history of various control programs in each of the electric vehicles 1-4 in association with the above-mentioned identification information. The management server 10 manages the update status of the various control programs used in the operation of the electric vehicles 1-4, and when a new version of at least one of the plurality of control programs is prepared, it requests the target vehicle among the electric vehicles 1-4 to update the control program.

[0024] The management server 10 is a computer including a control device 11, a storage device 12, and a communication device 13. The control device 11, the storage device 12, and the communication device 13 are connected to each other via a communication bus 14 so as to be able to communicate with each other.

[0025] The storage device 12 stores a management list including the identification information of the electric vehicles 1 to 4 and the above-mentioned update status associated with the identification information. The management list may further include other information associated with the identification information (such as update date and time and update status for each control program). The communication device 13 realizes two-way communication between the control device 11 and the communication network 6.

[0026] The control device 11 is configured to include a CPU (Central Processing Unit), memory (such as ROM (Read Only Memory) and RAM (Random Access Memory)), and input / output ports for inputting and outputting various signals, all of which are not shown. The various controls performed by the control device 11 are performed by software processing, i.e., by the CPU reading out a program stored in the memory. The various controls by the control device 11 can also be realized by a general-purpose server (not shown) executing a program stored in a storage medium. However, the various controls by the control device 11 are not limited to software processing and may be processed by dedicated hardware (electronic circuitry).

[0027] Although the above-mentioned management server 10 has been described as managing four electric vehicles 1 to 4 as an example, the number of electric vehicles to be managed is not particularly limited to four, and may be three or less, or five or more.

[0028] Next, a specific configuration of electric vehicle 1 according to the present embodiment will be described. Note that, since electric vehicles 2 to 4 basically have a common configuration with electric vehicle 1, detailed description of those configurations will not be repeated.

[0029] Fig. 2 is a diagram illustrating an example of a configuration of an electrically powered vehicle 1 according to the present embodiment. With reference to Fig. 2, the electrically powered vehicle 1 includes a power storage device 20, a system main relay (SMR) 21, a power control unit (PCU) 22, a DC (Direct Current) / DC converter 40, an auxiliary battery 50, a motor generator (hereinafter, referred to as MG) 62, a power transmission gear 65, drive wheels 66, and a control system 90.

[0030] The power storage device 20 is a rechargeable DC power source, and is configured to include, for example, a secondary battery such as a nickel metal hydride battery or a lithium ion battery having a liquid or solid electrolyte. A capacitor such as an electric double layer capacitor can also be adopted as the power storage device 20. The power storage device 20 supplies electric power to the PCU 22 for generating a driving force for running the electric vehicle 1. The power storage device 20 is charged with electric power generated by a regenerative operation of the MG 62, discharged by a driving operation of the MG 62, charged with electric power supplied from outside the vehicle, and discharged by a supply of electric power to the outside of the vehicle.

[0031] The SMR 21 is electrically connected between the power storage device 20 and the PCU 22. The closing / opening of the SMR 21 is controlled in accordance with a command from an HV-ECU (Electronic Control Unit) 100 of a control system 90.

[0032] PCU 22 performs power conversion between power storage device 20 and MG 62 in accordance with a command from HV-ECU 100 of control system 90. PCU 22 is configured to include an inverter that receives power from power storage device 20 and drives MG 62, and a converter that adjusts the level of DC voltage supplied to the inverter (neither of which is shown), and the like.

[0033] The MG 62 is a three-phase AC rotating electric machine, for example a permanent magnet type synchronous motor having a rotor with a permanent magnet embedded therein. The MG 62 has both a function as an electric motor (motor) and a function as a generator. The MG 62 is connected to the power storage device 20 via the PCU 22.

[0034] For example, when the electric vehicle 1 is traveling, the MG 62 is driven by an inverter included in the PCU 22. The power of the MG 62 is transmitted to drive wheels 66 via a power transmission gear 65. For example, when the electric vehicle 1 is braking, the MG 62 is driven by the drive wheels 66 and operates as a generator to perform regenerative braking. The electric power generated by the MG 62 is stored in the power storage device 20 via the PCU 22.

[0035] The electric vehicle 1 further includes a charging relay 26, a charging device 27, and an inlet 28 as components for charging using an AC power source 15 external to the electric vehicle 1 (hereinafter, sometimes referred to as external charging). A connector 32 is connected to the inlet 28. The connector 32 is connected to a charging stand 53 via a cable 31. In FIG. 2 , the connector 32 is shown attached to the inlet 28, but the connector 32 is configured to be detachable from the inlet 28, and the connector 32 is attached to the inlet 28 when external charging is performed, and the connector 32 is detached from the inlet 28 when the electric vehicle 1 is operated. The charging stand 53 is supplied with AC power from the AC power source 15, and by attaching the connector 32 to the inlet 28, a state in which AC power can be supplied from the charging stand 53 to the electric vehicle 1 is achieved.

[0036] When the power storage device 20 is externally charged, power is supplied from the charging stand 53 via the cable 31, the connector 32 and the inlet 28, and is converted in the charging device 27 into power capable of charging the power storage device 20 (hereinafter referred to as charging power), and the converted charging power is supplied to the power storage device 20.

[0037] The charging relay 26 is electrically connected between the power storage device 20 and the charging device 27. When the charging relay 26 is closed and the SMR 21 is closed, power transmission between the inlet 28 and the power storage device 20 is enabled.

[0038] The charging device 27 is electrically connected between the charging relay 26 and the inlet 28. The charging device 27 converts the power (e.g., AC power of AC 100 V) supplied from the charging stand 53 into charging power (DC power) in accordance with a command from the HV-ECU 100 of the control system 90.

[0039] The DC / DC converter 40 is electrically connected between the SMR 21 and the charging device 27. Therefore, when the SMR 21 is closed, power can be supplied from the power storage device 20 to the DC / DC converter 40. The DC / DC converter 40, in accordance with a command from the battery ECU 130 of the control system 90, steps down the high DC voltage of the power storage device 20 to a low DC voltage, and supplies the stepped-down low DC voltage to an auxiliary load (not shown) and also to the auxiliary battery 50. This charges the auxiliary battery 50.

[0040] The auxiliary battery 50 is a secondary battery such as a lead storage battery, and is capable of charging and discharging a low DC voltage (for example, power of about 12 V) that allows the auxiliary load to operate. A voltage sensor 52 that detects the output voltage of the auxiliary battery 50 is provided on a terminal portion of the auxiliary battery 50 or a power line connecting the auxiliary battery 50 to the DC / DC converter 40. The voltage sensor 52 transmits a signal indicating the detected output voltage of the auxiliary battery 50 to the battery ECU 130.

[0041] In this embodiment, the control system 90 includes a plurality of control devices. Specifically, the control system 90 includes an HV-ECU 100, a charging ECU 110, a battery ECU 130, a meter ECU 140, and an update ECU 150.

[0042] The HV-ECU 100 includes a CPU 102, a memory 104, and an input / output port (not shown) for inputting and outputting various signals. The HV-ECU 100 controls the SMR 21 and the PCU 22 in the electric vehicle 1 so that the electric vehicle 1 is in a desired running state. The various controls executed by the HV-ECU 100 are performed by software processing, that is, by the CPU 102 reading out a control program stored in the memory 104.

[0043] A wheel speed sensor 67 is connected to the HV-ECU 100. The wheel speed sensor 67 detects the rotation speed (wheel speed) V of the drive wheels 66, and transmits a signal indicating the detected wheel speed V to the HV-ECU 100. The HV-ECU 100 uses the detected wheel speed V to calculate the speed of the electric vehicle 1 (hereinafter also referred to as vehicle speed).

[0044] The charging ECU 110 includes a CPU 112, a memory 114, and an input / output port (not shown) for inputting and outputting various signals. The charging ECU 110 controls the charging relay 26 and the charging device 27 in the electric vehicle 1 so that the stopped electric vehicle 1 is in a state where external charging using a charging stand 53 can be performed. The various controls executed by the charging ECU 110 are executed by software processing, that is, by the CPU 112 reading out a control program stored in the memory 114.

[0045] The battery ECU 130 includes a CPU 132, a memory 134, and an input / output port (not shown) for inputting and outputting various signals. The battery ECU 130 acquires information on the state of the power storage device 20, calculates the SOC (State Of Charge) of the power storage device 20 using the acquired information, and controls the DC / DC converter 40 so that the auxiliary battery 50 is charged. The various processes executed by the battery ECU 130 are software processes, that is, executed by the CPU 132 reading out a control program stored in the memory 134.

[0046] The power storage device 20 is provided with, for example, a voltage sensor 136, a current sensor 137, and a temperature sensor 138. The voltage sensor 136, the current sensor 137, and the temperature sensor 138 are connected to the battery ECU .

[0047] The voltage sensor 136 detects the voltage VB of the power storage device 20, and transmits a signal indicating the detected voltage VB to the battery ECU 130. The current sensor 137 detects the current IB of the power storage device 20, and transmits a signal indicating the detected current IB to the battery ECU 130. Furthermore, the temperature sensor 138 detects the temperature TB of the power storage device 20, and transmits a signal indicating the detected temperature TB to the battery ECU 130.

[0048] Battery ECU 130 calculates the SOC, which indicates the remaining capacity of power storage device 20, using, for example, the results of detection by voltage sensor 136, current sensor 137, and temperature sensor 138. SOC is a percentage that represents the ratio of the current amount of stored power to the amount of stored power in a fully charged state of power storage device 20. Note that, as a method for calculating SOC, various known methods can be used, such as a method based on current value integration (coulomb counting) or a method based on open circuit voltage (OCV) estimation.

[0049] Furthermore, a voltage sensor 52 that detects the voltage of the auxiliary battery 50 is connected to the battery ECU 130. The voltage sensor 52 transmits to the battery ECU 130 a signal that indicates the voltage of the auxiliary battery.

[0050] The meter ECU 140 includes a CPU 142, a memory 144, and an input / output port (not shown) for inputting and outputting various signals. The meter ECU 140 executes display control for displaying predetermined information on a display device in the interior of the electric vehicle 1 (for example, a display device for displaying various instruments such as a speedometer and a distance meter and warning lights provided at a position visible to a driver seated in the driver's seat). The various controls executed by the meter ECU 140 are executed by software processing, that is, by the CPU 142 reading out a control program stored in the memory 144.

[0051] The update ECU 150 includes a CPU 152, a memory 154, a communication device 156, and an input / output port (not shown) for inputting and outputting various signals. The update ECU 150 transmits update information for the control program to at least one of the HV-ECU 100, the charging ECU 110, the battery ECU 130, and the meter ECU 140, and executes a process for requesting an update of the control program.

[0052] The communication device 156 is configured to be able to communicate with devices external to the electric vehicle 1. Specifically, the communication device 156 is configured to be able to communicate with the above-mentioned management server 10 via the communication network 6 and the base station 7. The communication network 6 is configured, for example, by the Internet or the like. The base station 7 and the communication device 156 may be connected to each other so as to be able to communicate with each other via a mobile phone line (for example, 4G or 5G), or may be connected by wireless communication such as Wifi.

[0053] The update ECU 150 executes a process requesting the execution of an update process so that the update process is executed in each ECU. The various processes executed by the update ECU 150 are software processes, that is, executed by the CPU 152 reading a program stored in the memory 154. The various processes executed by the update ECU 150 are not limited to software processes, and may be executed using dedicated hardware (electronic circuits).

[0054] For example, when the updating ECU 150 receives the update difference data and information on the ECU to be updated from the management server 10 using the communication device 156, the updating ECU 150 transmits, as update information, information indicating a request to execute an update process and the update difference data to the ECU to be updated. When the updating ECU receives the update information from the updating ECU 150, the updating ECU executes an update process to update a control program stored in memory using the update difference data included in the received update information. During the execution of such an update process, it is required that the power supply to the control system 90 is not interrupted.

[0055] However, when the control programs of multiple control devices need to be updated, the power consumption during the update may increase if the control programs are updated in parallel in the multiple control devices. Furthermore, when the control program update takes a long time, it may not be possible to secure the time for the update, or the update may be necessary and the decrease in the amount of stored power in the auxiliary battery 50 may not be suppressed.

[0056] Therefore, in this embodiment, when control system 90 receives update information for a first control program of an ECU that operates during external charging among the multiple ECUs using communication device 156, it updates the first control program using the update information while traveling. Furthermore, when control system 90 receives update information for a second control program of an ECU that operates while electric vehicle 1 using MG62 is traveling using communication device 156, it updates the second control program using the update information during external charging.

[0057] In this way, the first control program is updated while the vehicle is traveling, and the second control program is updated while the vehicle is externally charged, thereby ensuring a period for updating. Furthermore, by updating the first control program and the second control program in different periods, an increase in power consumption during updating can be suppressed compared to updating the first control program and the second control program in parallel.

[0058] In the present embodiment, it is assumed that the update ECU 150 of the control system 90 takes the lead in executing the process for updating the first control program and the second control program.

[0059] An example of processing executed by the updated ECU 150 will be described below with reference to Fig. 3. Fig. 3 is a flowchart showing an example of processing executed by the updated ECU 150. A series of processing shown in this flowchart is repeatedly executed at every predetermined control period.

[0060] In step (hereinafter, step will be abbreviated as S) 100, the update ECU 150 determines whether or not there is an OTA request. For example, the update ECU 150 determines that there is an OTA request when a flag indicating that there is an OTA request is in an ON state. For example, the update ECU 150 sets the flag indicating that there is an OTA request to an ON state when receiving update information for updating a control program of any of the multiple ECUs mounted on the electric vehicle 1 from the management server 10 using the communication device 156. If it is determined that there is an OTA request (YES in S100), the process proceeds to S102.

[0061] In S102, the update ECU 150 acquires the ECU that is the target of the OTA request (hereinafter, may be referred to as the OTA target ECU). When transmitting update information for a control program, the management server 10 includes identification information for identifying the OTA target ECU in the update information. The update ECU 150 acquires the OTA target ECU by using, for example, the identification information included in the update information received from the management server 10.

[0062] In S104, update ECU 150 determines whether the ECU to be OTA-targeted is an ECU that operates while driving. ECUs that operate while driving include, for example, HV-ECU 100 and meter ECU 140. If it is determined that the ECU to be OTA-targeted is an ECU that operates while driving (YES in S104), the process proceeds to S106.

[0063] In S106, the updated ECU 150 determines whether or not external charging is in progress. The updated ECU 150 determines that external charging is in progress when, for example, the connector 32 is attached to the inlet 28, the charging device 27 is in operation, or charging power is being supplied from the charging device 27 to the power storage device 20. If it is determined that external charging is in progress (YES in S106), the process proceeds to S108.

[0064] In S108, the update ECU 150 requests the target ECU to execute the update process. That is, the update ECU 150 transmits update information to the OTA target ECU among the HV-ECU 100 and the meter ECU 140, and requests the execution of the update process of the control program. When the OTA target ECU receives the update information from the update ECU 150, the OTA target ECU updates the control program stored in the memory of the OTA target ECU using the difference data included in the update information. Note that a well-known method may be used as the method for updating the control program, and a detailed description thereof will not be given here. When the OTA target ECU completes the update process, the update ECU 150 transmits information indicating the completion of the update process. When the update ECU 150 receives the information, the update ECU 150 sets a flag indicating that there is an OTA request to an off state.

[0065] On the other hand, if it is determined that the ECU that is the target of the OTA is not an ECU that operates while the vehicle is running (NO in S104), the process proceeds to S110.

[0066] In S110, update ECU 150 determines whether the ECU that is the target of OTA is an ECU that operates during external charging. ECUs that operate during external charging include, for example, charging ECU 110. If it is determined that the ECU that is the target of OTA is an ECU that operates during external charging (YES in S110), the process proceeds to S112.

[0067] In S112, the update ECU 150 determines whether the electric vehicle 1 is traveling. For example, the update ECU 150 determines that the electric vehicle 1 is traveling when the vehicle speed is higher than a threshold value. The threshold value is a predetermined value for determining whether the electric vehicle 1 is traveling or not, and is adapted through experiments or the like. When it is determined that the electric vehicle 1 is traveling (YES in S112), the process proceeds to S114.

[0068] In S114, the update ECU 150 requests the target ECU to execute update processing. That is, the update ECU 150 transmits update information to the charging ECU 110 to request the execution of update processing of the control program. When the charging ECU 110 receives the update information from the update ECU 150, the charging ECU 110 updates the control program stored in the memory 114 of the charging ECU 110 by using the difference data included in the update information. When the update processing is completed, the charging ECU 110 transmits information indicating the completion of the update processing to the update ECU 150. When the update ECU 150 receives the information, it sets a flag indicating the presence of an OTA request to an OFF state.

[0069] On the other hand, if it is determined that the ECU that is the target of OTA is not an ECU that operates during external charging (NO in S110), the process proceeds to S116.

[0070] In S116, the update ECU 150 determines whether or not the electric vehicle 1 is stopped. For example, the update ECU 150 determines that the electric vehicle 1 is stopped when the vehicle speed is equal to or lower than a threshold value and the connector 32 is not connected to the inlet 28. If it is determined that the electric vehicle 1 is stopped (YES in S116), the process proceeds to S118.

[0071] In S118, the update ECU 150 requests the target ECU to execute update processing. In this case, the OTA target ECU is an ECU that operates both during running and during external charging, and includes, for example, the battery ECU 130. That is, the update ECU 150 transmits update information to the battery ECU 130 to request the execution of update processing of the control program. When the battery ECU 130 receives the update information from the update ECU 150, the battery ECU 130 updates the control program stored in the memory 134 of the battery ECU 130 using the difference data included in the update information. When the update processing is completed, the battery ECU 130 transmits information indicating the completion of the update processing to the update ECU 150. When the update ECU 150 receives the information, it sets a flag indicating that there is an OTA request to an off state.

[0072] It should be noted that this process is terminated if it is determined that there is no OTA request (NO in S100), if it is determined that external charging is not occurring (NO in S106), if it is determined that the vehicle is not running (NO in S112), or if it is determined that the vehicle is not stopped (NO in S116).

[0073] An example of the operation of the update ECU 150 in the present embodiment based on the above-described structure and flowchart will be described with reference to FIG. 4. FIG. 4 is a timing chart showing an example of the operation of the update ECU 150. The vertical axis of FIG. 4 indicates the driving state of the electric vehicle 1, whether or not the update process of the HV-ECU 100 is executed, whether or not the update process of the charging ECU 110 is executed, and whether or not the update process of the battery ECU 130 is executed. The horizontal axis of FIG. 4 indicates time. Furthermore, LN1 of FIG. 4 indicates a change in the driving state of the electric vehicle 1. LN2 of FIG. 4 indicates a change in whether or not the update process of the HV-ECU 100 is executed. LN3 (dashed line) of FIG. 4 indicates whether or not the update process of the charging ECU 110 is executed when the charging ECU 110 is an ECU that is an OTA target. LN4 (dotted line) of FIG. 4 indicates whether or not the update process of the battery ECU 130 is executed when the battery ECU 130 is an ECU that is an OTA target.

[0074] Assume that at time T(0), for example, update information for the control program of HV-ECU 100 is received. In this case, the flag indicating that there is an OTA request is turned on, so it is determined that there is an OTA request (YES in S100).

[0075] When it is acquired using the identification information included in the update information that the ECU to be the target of OTA is HV-ECU100 (S102), since HV-ECU100, which is the ECU to be the target of OTA, is an ECU that operates while driving (YES in S104), it is determined whether or not external charging is being performed (S106).

[0076] Therefore, as shown in LN1 of Fig. 4, the operating state of the electric vehicle 1 is not during external charging until time T(5), and therefore the HV-ECU 100 is not requested to perform the update process. On the other hand, when the operating state of the electric vehicle 1 becomes during external charging at time T(5) (YES in S106), the HV-ECU 100 is requested to perform the update process (S108). Therefore, as shown in LN2 of Fig. 4, the update process is performed in the HV-ECU 100 during the period from time T(5) to time T(6). When the update process is completed at time T(6), a flag indicating that there is an OTA request is set to the OFF state.

[0077] Next, assume that at time T(0), for example, update information for the control program of charging ECU 110 is received. In this case, the flag indicating that there is an OTA request is turned on, and therefore it is determined that there is an OTA request (YES in S100).

[0078] When it is acquired using the identification information included in the update information that the ECU to be the target of OTA is the charging ECU 110 (S102), since the charging ECU 110, which is the ECU to be the target of OTA, is an ECU that operates during external charging (NO in S104 and YES in S110), it is determined whether the electric vehicle 1 is running (S112).

[0079] 4, the operating state of the electric vehicle 1 is not in motion until time T(2), and therefore the charging ECU 110 is not requested to perform the update process. On the other hand, when the operating state of the electric vehicle 1 becomes in motion at time T(2) (YES in S112), the charging ECU 110 is requested to perform the update process (S114).

[0080] 4, the update process is executed in the charging ECU 110 during the period from time T(2) to time T(3). When the update process is completed at time T(3), the flag indicating that there is an OTA request is set to the OFF state.

[0081] Next, assume that at time T(0), for example, update information for the control program of battery ECU 130 is received. In this case, the flag indicating that there is an OTA request is turned on, so it is determined that there is an OTA request (YES in S100).

[0082] Using the identification information included in the update information, it is acquired that the ECU to be the OTA target is the battery ECU 130 (S102).

[0083] The battery ECU 130, which is the ECU to be subjected to OTA, is neither an ECU that operates during external charging nor an ECU that operates while traveling (NO in S104 and NO in S110), so it is determined whether the electric vehicle 1 is stopped (S116).

[0084] Therefore, as shown by LN1 in FIG. 4, if the operating state is stopped at time T(0) (YES in S116), a request is made to the battery ECU 130 to execute the update process (S118).

[0085] 4, the update process is executed in the battery ECU 130 during the period from time T(0) to time T(1). When the update process is completed at time T(1), the flag indicating that an OTA request has been made is set to the OFF state.

[0086] As described above, according to the electric vehicle of the present embodiment, the control program of the charging ECU 110 that operates during external charging is updated while the vehicle is traveling, and the control programs of the HV-ECU 100 and the meter ECU 140 that operate while the vehicle is traveling are updated during external charging, thereby making it possible to secure a period for updating. Furthermore, by updating the control program of the charging ECU 110 and the control programs of the HV-ECU 100 and the meter ECU 140 in different periods, it is possible to suppress an increase in power consumption during updating compared to a case in which these control programs are updated in parallel. Therefore, it is possible to provide an electric vehicle, a control method for an electric vehicle, and a control device for an electric vehicle that make it possible to secure a period for updating while suppressing an increase in power consumption during updating of the control programs of multiple control devices mounted on the electric vehicle.

[0087] Furthermore, a period for updating the control program of the battery ECU 130, which operates during external charging and while traveling, can be secured because the control program is updated while the electric vehicle 1 is stopped. Furthermore, by performing the update of the control program of the battery ECU 130 in a period different from the update of the control program of the charging ECU 110 and the update of the control programs of the HV-ECU 100 and the meter ECU 140, an increase in power consumption during the update can be suppressed compared to the case where these control programs are updated in parallel.

[0088] Modifications will be described below. In the above-described embodiment, when the ECU targeted for OTA is an ECU that operates while charging, the target ECU is requested to execute the update process while the vehicle is traveling. However, for example, in addition to when the vehicle is traveling, the target ECU may be requested to execute the update process when the electric vehicle 1 can reach the destination even if power consumption increases due to the update process.

[0089] Hereinafter, an example of control processing executed by the updated ECU 150 in the modified example will be described with reference to Fig. 5. Fig. 5 is a flowchart showing an example of processing executed by the updated ECU 150 in the modified example. A series of processing shown in this flowchart is repeatedly executed at every predetermined control period.

[0090] The processes of S100, S102, S104, S106, S108, S110, S112, S114, S116 and S118 (hereinafter referred to as "S100 to S118") described in the flowchart shown in Fig. 5 are similar to the processes of S100 to S118 described in the flowchart shown in Fig. 3 except as described below, and therefore detailed description thereof will not be repeated.

[0091] If it is determined that the electric vehicle 1 is traveling (YES in S112), the process proceeds to S200.

[0092] In S200, the update ECU 150 calculates the reduction in the EV travel distance due to the update process. The EV travel distance indicates the travel distance of the electric vehicle 1 using the MG62. The update ECU 150 calculates, for example, the EV travel distance corresponding to the power consumption during the period in which the update process is performed as the reduction in the EV travel distance. The power consumption due to the update process may be, for example, a predetermined value, or may be calculated by estimating the update time from the amount of data to be updated and using the estimated update time and the power consumption per hour. Furthermore, the update ECU 150 calculates, as the reduction in the EV travel distance, the EV travel distance calculated using the power consumption per unit distance during electric travel using the MG62 and the power consumption due to the update process.

[0093] In S202, the update ECU 150 determines whether the electric vehicle 1 can reach the destination. Specifically, when the distance from the current location of the electric vehicle 1 to the destination is shorter than the drivable distance, the update ECU 150 determines that the electric vehicle 1 can reach the destination. The drivable distance is calculated, for example, by subtracting the reduction in the EV drivable distance due to the update process from the drivable distance based on the current SOC. The update ECU 150 acquires location information of the destination and location information of the current location from, for example, a navigation system (not shown). When it is determined that the electric vehicle 1 can reach the destination (YES in S202), the process proceeds to S114. When it is determined that the electric vehicle 1 cannot reach the destination (NO in S202), this process is ended.

[0094] An example of the operation of the updating ECU 150 in this modified example based on the above flowchart will be described.

[0095] For example, it is assumed that update information for the control program of charging ECU 110 is received. In this case, the flag indicating that there is an OTA request is turned on, and therefore it is determined that there is an OTA request (YES in S100).

[0096] When it is acquired using the identification information included in the update information that the ECU to be the target of OTA is the charging ECU 110 (S102), since the charging ECU 110, which is the ECU to be the target of OTA, is an ECU that operates during external charging (NO in S104 and YES in S110), it is determined whether the electric vehicle 1 is running (S112).

[0097] When the driving state of the electric vehicle 1 is in traveling (YES in S112), the reduction in the EV travel distance due to the update process is calculated (S200), and it is determined whether the electric vehicle 1 can reach the destination taking into account the calculated reduction (S202). Then, when it is determined that the electric vehicle 1 can reach the destination (YES in S202), a request is made to the charging ECU 110, which is the target ECU, to perform the update process (S114). Therefore, the update process is performed in the charging ECU 110, and when the update process is completed, a flag indicating that there is an OTA request is set to the OFF state.

[0098] In this manner, when the amount of power consumption increases due to the execution of the update process of the control program of the charging ECU 110 and the electric vehicle 1 cannot reach the destination, the control program of the charging ECU 110 is not updated while traveling, so that the electric vehicle 1 can reach the destination.

[0099] Furthermore, in the above-described embodiment, when the ECU targeted for OTA is an ECU that operates while driving, it has been described that the execution of the update process for the target ECU is requested when charging. However, for example, in addition to when charging, the execution of the update process for the target ECU may be requested when charging of the power storage device 20 can be completed by the departure time even if power consumption increases due to the update process.

[0100] Hereinafter, an example of control processing executed by the updated ECU 150 in the modified example will be described with reference to Fig. 6. Fig. 6 is a flowchart showing another example of processing executed by the updated ECU 150 in the modified example. A series of processing shown in this flowchart is repeatedly executed at every predetermined control period.

[0101] The processes of S100 to S118 in the flowchart shown in Fig. 6 are similar to those of S100 to S118 in the flowchart shown in Fig. 3 except as described below, and therefore detailed description thereof will not be repeated.

[0102] If it is determined that external charging is in progress (YES in S106), the process proceeds to S300.

[0103] At S300, the update ECU 150 calculates the increase in the charging time due to the update process. For example, the update ECU 150 calculates the time to charge the amount of power corresponding to the amount of power consumption during the period in which the update process is performed as the increase in the charging time. The amount of power consumption due to the update process is as described above, so detailed description thereof will not be repeated. The update ECU 150 calculates the charging time calculated using the charging power per unit time and the amount of power consumption due to the update process as the increase in the charging time.

[0104] In S302, the update ECU 150 determines whether or not the charging of the power storage device 20 can be completed by the departure time. Specifically, the update ECU 150 calculates the charging time required to complete charging from the amount of charging power corresponding to the difference between the current SOC and the SOC at the time of charging completion (for example, SOC corresponding to a fully charged state) and the charging power per unit time, and calculates the charging completion time from the current time by adding an increment to the calculated charging time. If the charging completion time is a time before the scheduled departure time, the update ECU 150 determines that the charging of the power storage device 20 can be completed by the departure time. If the charging completion time is a time after the scheduled departure time, the update ECU 150 determines that the charging of the power storage device 20 cannot be completed by the departure time. For example, the update ECU 150 may acquire information about the charging power from the charging stand 53, or may calculate the charging power from the voltage and current of the power storage device 20 during external charging. If it is determined that charging of the power storage device 20 can be completed by the departure time (YES in S302), the process proceeds to S108. If it is determined that charging of the power storage device 20 cannot be completed by the departure time (NO in S302), this process is ended.

[0105] An example of the operation of the updating ECU 150 in this modified example based on the above flowchart will be described.

[0106] For example, it is assumed that update information for the control program of HV-ECU 100 is received. In this case, the flag indicating that there is an OTA request is turned on, so it is determined that there is an OTA request (YES in S100).

[0107] When it is acquired using the identification information included in the update information that the ECU to be the target of OTA is HV-ECU100 (S102), since HV-ECU100, which is the ECU to be the target of OTA, is an ECU that operates while driving (YES in S104), it is determined whether or not external charging is being performed (S106).

[0108] If external charging is in progress (YES in S106), an increase in charging time due to the update process is calculated (S300), and it is determined whether or not charging of the power storage device 20 can be completed by the departure time of the electric vehicle 1, taking into consideration the calculated increase in charging time (S302). If it is determined that charging of the power storage device 20 can be completed by the departure time (YES in S302), a request is made to the HV-ECU 100, which is the target ECU, to perform an update process (S108). Therefore, the update process is performed in the HV-ECU 100, and when the update process is completed, a flag indicating that there is an OTA request is set to the OFF state.

[0109] In this manner, if power consumption increases due to the execution of an update process for the control program of HV-ECU 100 and charging of the power storage device 20 cannot be completed by the departure time, the control program of HV-ECU 100 is not updated during external charging, so that charging of the power storage device 20 can be completed by the departure time.

[0110] Furthermore, in the above-described embodiment, if the ECU that is the target of OTA is an ECU that operates while the electric vehicle 1 is traveling and during external charging, it has been described that the update process of the target ECU is executed when the electric vehicle 1 is stopped. However, for example, the auxiliary battery 50 may be charged while the electric vehicle 1 is traveling or during external charging, and if the auxiliary battery 50 has a stored amount of power required to execute the update process of the target ECU while the electric vehicle 1 is stopped, a request may be made to execute the update process on the ECU that is the target of update.

[0111] An example of the control process executed by the updating ECU 150 in the modified example will be described below with reference to Fig. 7. Fig. 7 is a flowchart showing yet another example of the process executed by the updating ECU 150 in the modified example.

[0112] In S400, the update ECU 150 determines whether or not there is an OTA request to an ECU that operates while the vehicle is traveling and during external charging. As described above, the ECUs that operate while the vehicle is traveling and during external charging include the battery ECU 130. Therefore, when there is an OTA request to the battery ECU 130, the update ECU 150 determines that there is an OTA request to an ECU that operates while the vehicle is traveling and during external charging. When it is determined that there is an OTA request to an ECU that operates while the vehicle is traveling and during external charging (YES in S400), the process proceeds to S402.

[0113] In S402, the update ECU 150 determines whether the electric vehicle 1 is traveling or is being externally charged. The method of determining whether the electric vehicle 1 is traveling and the method of determining whether the electric vehicle 1 is being externally charged are both as described above, and therefore detailed description thereof will not be repeated. If the electric vehicle 1 is traveling or is being externally charged (YES in S402), the process proceeds to S404.

[0114] In S404, the update ECU 150 charges the auxiliary battery 50. The update ECU 150 charges the auxiliary battery 50 using the DCDC converter 40 via the battery ECU 130. When the amount of stored power in the auxiliary battery 50 is lower than a threshold (for example, when the voltage of the auxiliary battery 50 is lower than a threshold), the update ECU 150 controls the DCDC converter 40 so that the auxiliary battery 50 is charged. For example, the update ECU 150 sets the threshold so that the value is higher when there is an OTA request to the battery ECU 130 than when there is no OTA request.

[0115] If the electric vehicle 1 is not traveling and is not being externally charged (for example, if the electric vehicle 1 is stopped) (NO in S402), the process proceeds to S406.

[0116] In S406, the update ECU 150 determines whether the auxiliary battery 50 has a storage amount necessary for the update process. For example, when the voltage of the auxiliary battery 50 is higher than a threshold value, the update ECU 150 determines that the auxiliary battery 50 has a storage amount necessary for the update process. If it is determined that the auxiliary battery 50 has a storage amount necessary for the update process (YES in S406), the process proceeds to S408.

[0117] At S408, the update ECU 150 requests the battery ECU 130, which is an ECU to be subjected to OTA, to execute update processing. When the battery ECU 130 receives update information from the update ECU 150, the battery ECU 130 updates the control program stored in the memory 134 of the battery ECU 130 using the difference data included in the update information. When the update processing is completed, the battery ECU 130 transmits information indicating the completion of the update processing to the update ECU 150. When the update ECU 150 receives the information, it sets a flag indicating that there is an OTA request to the off state.

[0118] In this way, the electric power required to perform the update process can be secured by charging the auxiliary battery 50 during external charging or while the electric vehicle 1 is traveling. Therefore, the control program can be updated in the battery ECU 130 while the vehicle is stopped.

[0119] Furthermore, in the above-described embodiment, it has been described that the update ECU 150 requests the ECUs that are the targets of OTA to perform an update process. However, it is sufficient that the update process is executed in the control system 90, and it is not particularly limited to the update process being executed in the ECUs that are the targets of OTA in response to a request from the update ECU 150. For example, the update ECU 150 may be capable of executing the update process for each ECU, or any of the ECUs that constitute the control system 90 may be capable of executing the update process for each ECU.

[0120] Furthermore, in the above embodiment, the update information received from the management server 10 has been described as including update information for one of the ECUs in the control system 90, but the update information received from the management server 10 may include, for example, update information for a plurality of ECUs. In this case, the control programs may be updated in an order according to a priority previously set for each ECU, or, if the update information includes information defining the update order, the control programs of each ECU may be updated in the defined update order.

[0121] Furthermore, in the above embodiment, the update ECU 150 has been described as requesting the OTA target ECU to execute the update process, but for example, the management server 10 may request the OTA target ECU to execute the update process. For example, the management server 10 may communicate with the electric vehicle 1 to obtain information on whether the electric vehicle 1 is traveling, being externally charged, or stopped, and use the obtained information to request the OTA target ECU to execute the update process.

[0122] The above-described modified examples may be implemented in whole or in part in appropriate combination. The embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The scope of the present invention is defined by the claims, not the above description, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0123] 1,2,3,4 Electric vehicle, 6 Communication network, 7 Base station, 10 Management server, 11 Control device, 12 Storage device, 13,156 Communication device, 14 Communication bus, 15 AC power source, 20 Power storage device, 21 SMR, 22 PCU, 26 Charging relay, 27 Charging device, 28 Inlet, 31 Cable, 32 Connector, 40 DC / DC converter, 50 Auxiliary battery, 52,136 Voltage sensor, 53 Charging stand, 62 MG, 65 Power transmission gear, 66 Drive wheel, 67 Wheel speed sensor, 90 Control system, 100 HV-ECU, 102,112,132,142,152 CPU, 104,114,134,144,154 Memory, 110 Charging ECU, 137 Current sensor, 138 Temperature sensor, 140 Meter ECU.

Claims

1. a power storage device that can be charged using a power source external to the vehicle; a drive motor that drives the vehicle using electric power from the power storage device; a receiving device that receives predetermined information from outside the vehicle; a control system including a plurality of control devices including a first control device and a second control device; The first control device uses a first control program to control a control target device that operates while the power storage device is being charged using the external power source; The second control device uses a second control program to control a device to be controlled that operates while the vehicle is traveling using the drive motor, The control system includes: When update information for the first control program is received using the receiving device, the first control program is updated using the update information during the running of the vehicle; When update information for the second control program is received using the receiving device, the second control program is updated using the update information during the charging; an electric vehicle, when performing a process for updating the first control program and the second control program, determining whether or not there is a request to update the control program before determining whether charging is in progress, and performing the update for the control program for which the conditions are met.

2. the plurality of control devices further includes a third control device that uses a third control program to control devices that operate during charging and during running, The electric vehicle according to claim 1 , wherein when the control system receives update information for the third control program using the receiving device, the control system updates the third control program using the update information while the vehicle is stopped.

3. The electric vehicle further includes an auxiliary battery that supplies power to the third control device. The control system includes: When the update information of the third control program is received using the receiving device, the auxiliary battery is charged at least during the charging and during the running of the vehicle; The electric vehicle according to claim 2 , wherein when an amount of stored power in the auxiliary battery during the stop is equal to or greater than a threshold value at which the third control program can be updated, the third control program is updated using the update information.

4. The electric vehicle according to any one of claims 1 to 3, wherein when the control system receives update information for the first control program using the receiving device, if an increase in power consumption accompanying the update of the first control program causes a travelable distance to be shorter than a distance to a destination of the vehicle, the control system does not update the first control program while the vehicle is traveling.

5. 5. The electric vehicle according to claim 1, wherein when the control system receives update information for the second control program using the receiving device, if charging of the power storage device cannot be completed by the departure time due to an increase in power consumption accompanying the update of the second control program, the control system does not update the second control program during the charging.

6. A control method for an electric vehicle including an electricity storage device that can be charged using a power source external to the vehicle, a drive motor that drives the vehicle using power from the electricity storage device, a receiving device that receives predetermined information from outside the vehicle, and a control system constituted by a plurality of control devices including a first control device and a second control device, wherein the first control device uses a first control program to control devices that operate during charging of the electricity storage device using the external power source, and the second control device uses a second control program to control devices that operate during running of the vehicle using the drive motor, The control method includes: when update information for the first control program is received using the receiving device, updating the first control program using the update information during the running of the vehicle; When update information of the second control program is received using the receiving device, updating the second control program using the update information during the charging; a step of determining, when performing processing to update the first control program and the second control program, whether or not there is a request to update the control program before determining whether charging is in progress, and executing the update for which a condition is met.

7. A control device for an electric vehicle including a power storage device that can be charged using a power source external to the vehicle, a drive motor that drives the vehicle using electric power from the power storage device, and a receiving device that receives predetermined information from outside the vehicle, The control device includes: a first control device that uses a first control program to control a control target device that operates while the power storage device is being charged using the external power source; a second control device that uses a second control program to control a device to be controlled that operates while the vehicle is traveling using the drive motor; The control device includes: When update information of the first control program is received using the receiving device, a request is made to the first control device to update the first control program using the update information during the traveling; When update information of the second control program is received using the receiving device, a request is made to the second control device to update the second control program using the update information during the charging; a control device for an electric vehicle that, when performing processing to update the first control program and the second control program, first determines whether there is a request to update the control program before determining whether charging is in progress, and performs the update for the control program for which the conditions are met.

Images