Vehicle control device

By introducing state conversion logic of manual driving, automatic driving and standby mode in the vehicle control device, the problem of vehicles stationary vehicles when autonomous driving is started is solved, and stable vehicle state conversion and service continuity is achieved.

CN118928456APending Publication Date: 2024-11-12TOYOTA JIDOSHA KK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410277695.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-09
Filing Date
2024-03-12
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

When the autonomous driving system is started, the vehicle may become a stationary vehicle due to failure to properly switch to the autonomous driving mode, resulting in stagnation in the service of transporting passengers.

Method used

A vehicle control device is designed, with manual driving mode, automatic driving mode and standby mode. The processor receives and converts commands in different states to ensure that the driver's intention is not switched to standby mode before detecting the driver's intention, and is in the gear shift Receive autonomous driving conversion instructions when parking to avoid undesired state transitions.

Benefits of technology

It effectively avoids the situation where the vehicle becomes a stationary vehicle when the autonomous driving is started, ensures that the vehicle can be successfully switched to the autonomous driving mode or manual driving mode, and ensures the continuity and safety of services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118928456A_ABST
    Figure CN118928456A_ABST
Patent Text Reader

Abstract

This vehicle control device is connected between an automatic driving system and a vehicle platform that performs automatic driving in accordance with a command from the automatic driving system, and is provided with: a memory that stores a program; and a processor performing interaction between the autonomous driving system and the vehicle platform by executing a program. The processor is configured to switch to a pure manual state when an activation command based on a manual operation is received in an unknown state, switch to a standby state when an activation command is received from an automatic driving system in the unknown state, and switch to a standby mode when a condition for switching to the standby mode in the standby state is satisfied, and switch to the standby mode when a condition for switching to the standby mode in the standby state is satisfied. And if the driving intention of the driver is detected in the preparation state, switching to the pure manual state.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a vehicle control device, and more particularly to a vehicle control device connected between an autonomous driving system and a vehicle platform that performs autonomous driving according to instructions from the autonomous driving system. Background Art

[0002] In recent years, the autonomous driving technology of vehicles has been continuously developed. For example, in the vehicle control system disclosed in Japanese Patent Application Laid-Open No. 2019-177807, the vehicle cooperates with the information processing device to perform autonomous driving. The information processing device automatically generates control information through the autonomous driving control software and sends it to the vehicle. The vehicle performs autonomous driving based on the received control information.

[0003] It is possible to consider placing the autonomous driving system outside the vehicle body (the vehicle platform described later). The vehicle platform controls the vehicle according to the instructions from the autonomous driving system, thereby realizing autonomous driving. As vehicle modes, the vehicle platform has a manual driving mode under the control of the driver, an autonomous driving mode under the control of the autonomous driving system, and a standby mode in which the driver's control is basically impossible and the control by the autonomous driving system is waiting to start.

[0004] In the case where the vehicle is used for a service of transporting passengers, it is usually considered to be operated through automatic driving. After the vehicle platform based on the automatic driving system is started, if for some reason it does not switch from the manual driving mode to the standby mode, since the automatic driving has not started, the operator of the vehicle thinks that it is in the manual driving mode and considers starting manual driving. When the conditions for switching to the standby mode are met after the start of manual driving and the standby mode is switched to, if the gear is not the parking gear, even if an instruction to switch from the automatic driving system to the automatic driving mode is sent, it will not switch to the automatic driving mode. In this case, if the gear is switched to the parking gear, since it is in the standby mode, the operator's switching operation to other gears is not accepted. In addition, since it has not switched to the automatic driving mode, the instructions from the automatic driving system are not accepted, so the vehicle may become a stationary vehicle. Summary of the invention

[0005] The present disclosure has been made to solve the above-mentioned problems, and an object of the present disclosure is to provide a vehicle control device that can prevent a vehicle from becoming immobile when automatic driving is started.

[0006] The vehicle control device involved in the present disclosure is a vehicle control device connected between an autonomous driving system and a vehicle platform that performs autonomous driving according to instructions from the autonomous driving system, wherein the vehicle control device comprises: a memory storing a program including a prescribed API defined according to each signal; and a processor that performs interaction between the autonomous driving system and the vehicle platform by executing the program.

[0007] The vehicle control device has a manual driving mode, an automatic driving mode, and a standby mode as vehicle modes.

[0008] Manual driving modes include unknown state, pure manual state and preparatory state.

[0009] The vehicle platform is configured to accept a manual driving operation in a manual driving mode and to accept a shift operation from a manual driving operation to a parking gear in a standby mode.

[0010] In autonomous driving mode, it can accept driving instructions from the autonomous driving system.

[0011] The processor is configured as follows: upon receiving a start command based on manual operation in an unknown state, the processor switches to a pure manual state; upon receiving a start command from the automatic driving system in an unknown state, the processor switches to a preparatory state; upon the condition that a transition condition to a standby mode in the preparatory state is met, the processor switches to the standby mode; and upon detecting the driver's driving intention in the preparatory state, the processor switches to a pure manual state.

[0012] According to such a structure, the vehicle is switched to the preparatory state on condition that a start command from the automatic driving system is received in an unknown state, and is switched to the pure manual state on condition that a driving intention of the driver is detected in the preparatory state. Therefore, if a driving intention is detected before switching to the standby mode, the vehicle will not be switched to the standby mode. As a result, a vehicle control device can be provided that can prevent the vehicle from becoming immobile when the automatic driving starts.

[0013] The processor may also be configured to switch to the automatic driving mode upon receiving an automatic driving switching instruction from the automatic driving system in the standby mode and the gear gear is the parking gear, and to switch to the error state upon receiving an automatic driving switching instruction from the automatic driving system in the standby mode and the gear gear is not the parking gear.

[0014] According to such a configuration, it is possible to avoid an undesirable situation in which automatic driving is started when the gear shift position is not the parking position in the standby mode.

[0015] The processor may also be configured to switch to the automatic driving mode upon receiving an automatic driving switch instruction in a purely manual state.

[0016] According to such a configuration, it is possible to switch from a state in which manual driving is possible to a state in which automatic driving is possible.

[0017] The processor may be configured to switch to a pure manual state upon receiving a standby mode stop command from the automatic driving system in the standby mode.

[0018] According to such a configuration, even when the vehicle is switched to the standby mode, if there is a stop command from the automatic driving system, the vehicle can be switched to a state where manual driving is possible.

[0019] The processor may also be configured to switch to a purely manual state upon receiving an automatic driving stop instruction from the automatic driving system in the automatic driving mode.

[0020] According to such a configuration, even when the vehicle is switched to the automatic driving mode, if there is a stop instruction from the automatic driving system, the vehicle can be switched to a state where manual driving is possible. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Features, advantages, and technical and industrial significance of exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which like reference numerals represent like elements, wherein:

[0022] Figure 1 is a diagram showing an overview of a vehicle according to an embodiment of the present disclosure;

[0023] Figure 2 is a diagram showing the structures of ADK, VCIB, and VP in more detail;

[0024] Figure 3 is a state transition diagram for explaining the vehicle mode in this embodiment;

[0025] Figure 4 is a timing diagram for explaining the transition from the unknown state to the preparatory state in the manual driving mode;

[0026] Figure 5 is a timing chart for explaining the transition from the preparatory state of the manual driving mode to the standby mode;

[0027] Figure 6 This is a timing chart for explaining the transition from the unknown state of the manual mode to the preparatory state and then to the pure manual state. DETAILED DESCRIPTION

[0028] Figure 11 is a diagram showing an overview of a vehicle according to an embodiment of the present disclosure. The vehicle 1 is configured such that the driving subject is a system and is capable of highly automated driving (for example, automated driving classified as so-called automated driving level 4 or 5). In this example, it is assumed that the vehicle 1 is used for a mobility service related to automated driving, such as a service for transporting passengers.

[0029] The vehicle 1 includes an autonomous driving kit (ADK) 10, a vehicle control interface box (VCIB) 20, and a vehicle platform (VP) 30. The ADK 10 can be installed on the VP 30 (such as the ceiling of the VP 30) and removed from the VP 30. The ADK 10 and the VP 30 are connected to each other via the VCIB 20 in a communicative manner according to a communication standard such as a controller area network (CAN).

[0030] ADK 10 includes an autonomous driving system (ADS) 11 for autonomous driving of vehicle 1. ADK 10 (ADS 11) creates a driving plan for vehicle 1. ADK 10 outputs various instructions (control requirements) for driving vehicle 1 according to the driving plan to VP 30 according to an application program interface (API) defined according to each control requirement. In addition, ADK 10 receives various signals indicating vehicle status (status of VP 30) from VP 30 according to the API defined according to each signal. Moreover, ADK 10 reflects the vehicle status on the driving plan.

[0031] The VCIB 20 receives various control requests from the ADK 10 and outputs the vehicle status to the ADK 10 by executing the prescribed API defined for each signal. When the VCIB 20 receives the control request from the ADK 10, it outputs the control instruction corresponding to the control request to the system corresponding to the control instruction via the unified control manager 41. In addition, the VCIB 20 obtains various information of the VP 30 from various systems via the unified control manager 41, and outputs the various information of the VP 30 to the ADK 10 as the vehicle status.

[0032] When the ADK 10 is installed, the VP 30 can perform the automatic driving control in the automatic driving mode according to the control request from the ADK 10. When the ADK 10 is removed, the VP 30 performs the travel control in the manual driving mode.

[0033] VP 30 includes a base vehicle 40. The base vehicle 40 performs various vehicle controls according to the control request from ADK 10. The base vehicle 40 includes, for example, a unified control manager 41, a brake system 42, a steering system 43, a powertrain system 44, an active safety system 45, and other systems 46 (see Figure 2 ), wheel speed sensors 51, 52, a pinion angle sensor 53, a camera 54, radar sensors 55, 56, and a power switch 60.

[0034] The integrated control manager 41 includes a processor and a memory, and performs integrated control of the above-mentioned systems involved in the operation of the vehicle 1 .

[0035] The brake system 42 controls the brake devices of each wheel provided on the base vehicle 40. Wheel speed sensors 51 and 52 are connected to the brake system 42. The wheel speed sensors 51 and 52 detect the rotation speed of the front wheels and the rear wheels of the base vehicle 40, respectively, and output them to the brake system 42. The brake system 42 outputs the rotation speed of each wheel to the VCIB 20 as one of the information included in the vehicle state. The unified control manager 41 calculates the speed (vehicle speed) of the vehicle 1 based on the rotation speed of each wheel. In addition, the brake system 42 generates a brake command to the brake device according to a prescribed control request output from the ADK 10 via the VCIB 20 and the unified control manager 41. The brake system 42 controls the brake device using the generated brake command.

[0036] The steering system 43 uses a steering device to control the steering angle of the steering wheel of the vehicle 1. A pinion angle sensor 53 is connected to the steering system 43. The pinion angle sensor 53 detects the rotation angle (pinion angle) of the pinion connected to the rotating shaft of the actuator and outputs it to the steering system 43. The steering system 43 outputs the pinion angle to the VCIB 20 as one of the information included in the vehicle state. In addition, the steering system 43 generates a steering control instruction for the steering control device according to the prescribed control requirements output from the ADK 10 via the VCIB 20 and the unified control manager 41. The steering system 43 uses the generated steering control instruction to control the steering control device.

[0037] The powertrain system 44 controls an electric parking brake (EPB) system 441 provided on at least one of the plurality of wheels, a parking lock (P-Lock) system 442 provided on a transmission of the vehicle 1 , and a propulsion system 443 including a shift device configured to select a shift position.

[0038] The active safety system 45 detects obstacles (pedestrians, bicycles, parked vehicles, electric poles, etc.) in front or behind using the camera 54 / radar sensors 55, 56. The active safety system 45 determines whether there is a possibility of collision between the vehicle 1 and the obstacle based on the distance between the vehicle 1 and the obstacle and the moving direction of the vehicle 1. If it is determined that there is a possibility of collision, the active safety system 45 outputs a braking command to the brake system 42 via the unified control manager 41 in a manner that increases the braking force.

[0039] The power switch 60 accepts a user's operation for selecting a power position of the vehicle 1. The power position includes an ignition off (IG-OFF) position, an accessory (ACC) position, an ignition on (IG-ON) position, a start position, and a ready (Ready ON) position.

[0040] The IG-OFF position corresponds to the power-off state of the vehicle 1. In the IG-OFF position, the power supply to each device mounted on the vehicle 1 is cut off. In the ACC position, power is supplied to accessory devices such as air conditioning devices and audio equipment. In the IG-ON position, power is supplied to systems required for the driving of the vehicle 1 in addition to the accessory devices. If the start position is selected, VP 30 is started in such a way that the vehicle 1 becomes capable of driving. After the start of VP 30, an initial check of VP 30 is performed. The initial diagnosis is a diagnosis for confirming that each system in VP 30 is normal. If the result of the initial diagnosis is that VP 30 is confirmed to be normal, the start position is switched to the ready position.

[0041] Figure 2 FIG. 2 is a diagram showing the structures of ADK10, VCIB20 and VP30 in more detail. Figure 2 As shown, the ADK 10 (ADS 11 ) includes a computer 111 , a human machine interface (HMI) 112 , a recognition sensor 113 , a posture sensor 114 , and a sensor cleaner 115 .

[0042] The computer 111 uses various sensors to obtain the environment of the vehicle 1, the posture, behavior, and position of the vehicle 1 during the automatic driving of the vehicle 1, and obtains the vehicle state from the VP 30 via the VCIB 20 to set the next action (acceleration, deceleration, turning, etc.) of the vehicle 1. In addition, the computer 111 sends various instructions for implementing the next action to the VCIB 20. The computer 111 includes communication modules 111A and 111B.

[0043] The HMI 112 presents information to the user and accepts user operations during automatic driving, driving that requires user operations, and switching between automatic driving and manual driving.

[0044] The recognition sensor 113 is a sensor for recognizing the environment of the vehicle 1. The recognition sensor 113 includes, for example, at least one of a laser radar (LIDAR, Laser Imaging Detection and Ranging), a millimeter wave radar, and a camera.

[0045] The posture sensor 114 is a sensor for detecting the posture, behavior, and position of the vehicle 1. The posture sensor 114 includes, for example, an inertial measurement unit (IMU) and a global positioning system (GPS). The sensor washer 115 is configured to remove dirt attached to the above-mentioned various sensors (camera lens, laser irradiation part, etc.) while the vehicle 1 is running using a cleaning fluid, a wiper, etc.

[0046] VCIB 20 includes a main VCIB 21 and a sub VCIB 22. VCIB 21 includes a processor 211 and a memory 212. VCIB 22 includes a processor 221 and a memory 222. Memories 212 and 222 include a read-only memory (ROM) and a random access memory (RAM), etc., respectively, and store programs including the prescribed API defined according to each signal. Processors 221 and 221 include a central processing unit (CPU), etc., respectively, and interact between ADK 10 and VP 30 by executing the above-mentioned programs.

[0047] VCIB 21 and communication module 111A are connected to each other so as to be communicable. VCIB 22 and communication module 111B are connected to each other so as to be communicable. Furthermore, VCIB 21 and VCIB 22 are connected to each other so as to be communicable. VCIB 21 and 22 respectively transfer control requirements and vehicle information between ADK 10 and VP 30. Specifically, VCIB 21 uses API to generate control instructions according to control requirements from ADK 10. Furthermore, VCIB 21 outputs the generated control instructions to corresponding systems among the multiple systems included in VP 30. In addition, VCIB 21 uses API to generate information indicating the vehicle status according to the vehicle information from each system of VP 30. VCIB 21 outputs the generated information indicating the vehicle status to ADK 10. The same is true for VCIB 22.

[0048] The EPB system 441 controls the EPB according to the control request output from the ADK 10 via the VCIB 21. The EPB is provided separately from the brake device (disc brake system, etc.), and the wheels are fixed by the action of the actuator. The P-Lock system 442 controls the P-Lock device according to the control request output from the ADK 10 via the VCIB 21. When the control request includes a control request to change the shift position to the parking position (P gear), the P-Lock system 442 operates the P-Lock device, and when the control request includes a control request to change the shift position to a position other than the parking position, the P-Lock device is released. The P-Lock device fixes the rotation of the output shaft of the transmission and fixes the wheels.

[0049] The propulsion system 443 switches the shift position of the shift device (not shown) and controls the driving force from the driving source (motor generator, engine, etc.) according to the control request output from the ADK 10 via the VCIB 21. The shift position includes, for example, a neutral position (N range), a forward driving position (D range), a reverse driving position (R range), and a brake position (B range) in addition to the parking position.

[0050] The active safety system 45 is communicatively connected to the brake system 421. As described above, the active safety system 45 uses the camera 54 and / or the radar sensor 55 to detect obstacles ahead, and when it is determined that there is a possibility of a collision, it outputs a brake command to the brake system 421 in a manner of increasing the braking force. Other systems 46 include a body system, an air conditioning device, and audio systems. The body system controls components such as the direction controller, the horn, and the wipers according to the control requirements from the ADK10.

[0051] In the vehicle 1, for example, when the automatic driving mode is selected by the user's operation on the HMI 112, the automatic driving is performed. As described above, the ADK 10 first creates a driving plan in the automatic driving. As examples of driving plans, for example, a plan to continue moving forward, a plan to turn left / right at a predetermined intersection in the middle of a predetermined driving path, a plan to change driving lanes, etc. can be cited. The ADK 10 calculates the controllable physical quantities (acceleration, deceleration, tire steering angle, etc.) required for the vehicle 1 to perform actions based on the created driving plan. The ADK 10 divides the physical quantities of each execution cycle of the API. The ADK 10 uses the API to output control requirements representing the divided physical quantities to the VCIB 20. In addition, the ADK 10 obtains the vehicle state (the actual moving direction of the vehicle 1, the fixed state of the vehicle, etc.) from the VP 30, and again creates a driving plan reflecting the obtained vehicle state. In this way, the ADK 10 enables automatic driving of the vehicle 1.

[0052] Figure 3 VCIB 20 has a standby mode in addition to a manual driving mode and an automatic driving mode. The manual driving mode includes an unknown state, a pure manual state, and a pre-standby state.

[0053] The VCIB 20 transitions to the pure manual state (see E1 ) on the condition that a ready command based on a manual operation by a user is received in the unknown state. In the pure manual state, the unified control manager 41 (or other ECU) performs an initial diagnosis.

[0054] After the implementation of the initial diagnosis, the VCIB 20 receives an automatic driving switching command from the ADK 10 in the pure manual state, and then switches to the automatic driving mode (autonomous state) (see E3). In the automatic driving mode, the unified control manager 41 controls the VP 30 according to the request from the ADK 10, thereby realizing automatic driving.

[0055] The VCIB 20 transitions to the pure manual state on condition that an automatic driving stop instruction is received from the ADK 10 in the automatic driving mode (see E6 ).

[0056] On the other hand, VCIB 20 is switched to the standby state on condition that a ready instruction is received from ADK 10 in the unknown state (see E2). In the standby state, the unified control manager 41 (or other ECU) also performs initial diagnosis. VCIB 20 is further switched from the manual driving mode (standby state) to the standby mode (standby state) on condition that a switching condition to the standby mode (e.g., a condition including completion / implementation of initial diagnosis) is satisfied (see E4). VCIB 20 is switched to the pure manual state on condition that a manual operation other than the manual operation of changing the shift position to the P gear (e.g., a prescribed operation for moving the vehicle 1, specifically, an operation of changing to the D, R, or B gear) is received in the standby state (see E10).

[0057] In addition, in the present embodiment, the driver's driving intention is detected by accepting a manual operation other than the manual operation of changing the shift position to the P gear. However, the present invention is not limited thereto, and the driver's driving intention may be detected by accepting an operation of an operating unit for manual driving (e.g., an accelerator pedal, a brake pedal, a steering wheel, a parking brake), or by detecting a vehicle speed other than zero.

[0058] In addition, in the present embodiment, the switch to the pure manual state is made on the condition that the driving intention is detected. However, the condition for switching to the pure manual state may be, for example, the condition that the switch to the standby mode is not made after a predetermined period (e.g., 8 seconds) has passed since the switch to the preparatory state, or the condition of the AND of the condition that the driving intention is detected.

[0059] In the standby mode, the manual operation accepted by the VP 30 is suppressed. More specifically, the integrated control manager 41 (which may be the ECU in the propulsion system 443) does not accept the shift operation of the shift device (the switching operation to a shift position other than the P range) by the propulsion system 443. In addition, the integrated control manager 41 does not accept the accelerator operation (the stepping operation of the accelerator pedal). Furthermore, the integrated control manager 41 (which may be the ECU in the EPB system 441) does not accept the EPB release operation of the EPB system 441.

[0060] The VCIB 20 switches to the automatic driving mode (autonomous state) (see E5) when the automatic driving switching command is received from the ADK 10 in the standby mode and the gear shift gear is the P gear. The VCIB 20 switches to the error state when the automatic driving switching command is received from the ADK 10 in the standby mode and the gear shift gear is not the P gear.

[0061] In the automatic driving mode, the VCIB 20 switches to the manual driving mode (Pure Manual state) on condition that the standby mode stop command is received from the ADK 10 (see E8).

[0062] Under the condition that the IG-OFF operation (typically, the power switch 60 is turned off) is performed in the pure manual state, the VCIB 20 is switched to the unknown state (see E7).

[0063] Figure 4 2 is a timing chart for explaining the transition from the unknown state to the preparatory state in the manual driving mode (see E2). Figure 4 , the power position of VP 30, the power mode of VCIB 20, the internal state, the power startup request from ADK 10, the power mode instruction from ADK 10, the vehicle power processing in VCIB 20, the ready processing in VP30 (vehicle 1), and the vehicle mode are shown from top to bottom. The power mode includes a wake-up mode and a driving mode. The wake-up mode is a mode in which VCIB 20 is started by powering the auxiliary battery of VP 30. The driving mode is a mode equivalent to the ready state, in which VCIB 20 and all ECUs are started, and power is supplied from the high-voltage battery to each system.

[0064] In the unknown state, a switching command to the driving mode of the power mode is output from the ADK 10. In this way, the power startup request from the ADK 10 is changed to the startup state in the VCIB 20, the vehicle power processing is executed, and the ready processing is executed in the VP 30. As a result, the power position of the VP 30 is switched to the ready position. In addition, the power mode of the VCIB 20 is switched from the wake-up mode to the driving mode, the internal state is switched from the unknown state to the standby state, and the power startup request from the ADK 10 is changed to the off state.

[0065] Figure 5 This is a time chart for explaining the transition from the preparatory state of the manual driving mode to the standby mode (see E4). Figure 5 In addition to Figure 4 In addition to the items described in , the vehicle mode command from the ADK 10, the standby mode preparation, the automatic driving mode preparation, the vehicle speed, and the shift position are also shown.

[0066] In the preparatory state of the manual driving mode, if the initial diagnosis is completed, the standby mode preparation is completed (for example, vehicle speed = 0), and the internal state is switched from the preparatory state to the standby state. Accordingly, the vehicle mode is also switched from the manual driving mode to the standby mode.

[0067] Figure 6 This is a time chart for explaining the transition from the unknown state of the manual mode to the preparatory state and then to the pure manual state (see E10). Figure 4 After the transition to the preparatory state described in , before the transition to the standby mode, if the shift position is switched to a gear other than the P gear, for example, the R, D, or B gear, the internal state is transitioned from the preparatory state to the pure manual state.

[0068] In addition, the conditions for the conversion of the above-mentioned modes and states may also include other conditions other than the above-mentioned conditions. All points of the embodiments disclosed this time should be considered as illustrative and not limiting the present invention. The scope of the present invention is not limited by the description of the above-mentioned embodiments, but is indicated by the claims, and is intended to include the meaning equivalent to the claims and all changes within the scope thereof.

Claims

1. A vehicle control device connected between an autonomous driving system and a vehicle platform that performs autonomous driving according to instructions from the autonomous driving system, wherein: The vehicle control device comprises: a memory storing a program including a prescribed API defined according to each signal; and a processor, for performing interaction between the autonomous driving system and the vehicle platform by executing the program, The vehicle control device has a manual driving mode, an automatic driving mode, and a standby mode as vehicle modes, The manual driving mode includes an unknown state, a pure manual state and a preparatory state. The vehicle platform is composed of: In the manual driving mode, manual driving operation can be accepted. In the standby mode, an operation of shifting the gear to the parking gear during manual driving operation can be accepted. In the automatic driving mode, the driving instructions from the automatic driving system can be accepted. The processor is composed of: The state is switched to the pure manual state on the condition that a start instruction based on manual operation is received in the unknown state. The system switches to the preparatory state on condition that a start instruction is received from the automatic driving system in the unknown state. The switching to the standby mode is performed on the condition that a switching condition to the standby mode is satisfied in the standby state. The state is switched to the pure manual state on the condition that the driver's driving intention is detected in the preparatory state.

2. The vehicle control device according to claim 1, wherein: The processor is composed of: The automatic driving mode is switched to the automatic driving mode on the condition that an automatic driving switching instruction is received from the automatic driving system in the standby mode and the gear shift gear is the parking gear, The vehicle switches to the error state on the condition that the automatic driving switching instruction is received from the automatic driving system in the standby mode and the gear shift gear is not the parking gear.

3. The vehicle control device according to claim 1, wherein: The processor switches to the automatic driving mode on the condition that an automatic driving switching instruction is received in the pure manual state.

4. The vehicle control device according to claim 1, wherein: The processor switches to the pure manual state on the condition that a standby mode stop instruction is received from the automatic driving system in the standby mode.

5. The vehicle control device according to any one of claims 1 to 4, wherein: The processor switches to the pure manual state on the condition that an automatic driving stop instruction is received from the automatic driving system in the automatic driving mode.