Vehicle management system and battery electric vehicle

Abstract

The invention relates to a vehicle management system and a battery electric vehicle. The vehicle management system includes one or more processors configured to generate a pseudo engine sound based on a driving state of the battery-powered vehicle. The one or more processors are configured to output a dummy engine sound from a speaker mounted on the battery-powered vehicle. The one or more processors are configured to generate a dummy engine sound using a sound source corresponding to a selected vehicle type selected from a plurality of engine vehicle types. The one or more processors are configured to, when a user makes a temporary designation input that temporarily designates the selected vehicle type while the battery electric vehicle is stationary, output a sample sound for an engine vehicle type corresponding to the temporary designation input in a predetermined output form from the speaker.

Description

Technical Field

[0001] The present disclosure relates to a battery electric vehicle including an electric motor as a driving source, and to a vehicle management system to be applied to the battery electric vehicle. Background Art

[0002] Conventionally, a battery electric vehicle has been designed that generates a pseudo engine sound generated when a virtual engine vehicle including an internal combustion engine as a driving source is running. For example, Japanese Unexamined Patent Application Publication No. 2011-215437 discloses a sound control device that controls a pseudo engine sound (virtual engine sound) so as to realistically reflect an engine sound generated when a gear shift is performed in an engine vehicle. Summary of the invention

[0003] The actual engine vehicle generates engine sounds with different characteristics depending on the vehicle type. In a battery electric vehicle that generates a pseudo engine sound, the vehicle type (engine vehicle type) of the virtual engine vehicle can be specified from a plurality of types so that pseudo engine sounds simulating engine sounds of various engine vehicle types can be generated. The user can specify an appropriate engine vehicle type according to his / her taste or mood.

[0004] On the other hand, it is conceivable that the user determines whether the pseudo engine sound matches his / her taste or mood after actually listening to the pseudo engine sound during driving. In this case, the user usually needs to specify the engine vehicle type after actually driving the vehicle and listening to the pseudo engine sound. This gives the user the impression that specifying the engine vehicle type is troublesome. The present disclosure provides a vehicle management system and a battery electric vehicle that reduce such troubles for the user.

[0005] A first aspect of the present disclosure provides a vehicle management system to be applied to a battery electric vehicle, the battery electric vehicle including an electric motor as a driving source. The vehicle management system includes one or more processors. The one or more processors are configured to generate a pseudo engine sound based on the driving state of the battery electric vehicle. The one or more processors are configured to output the pseudo engine sound from a speaker mounted on the battery electric vehicle. The one or more processors are configured to generate the pseudo engine sound using a sound source corresponding to a selected vehicle type selected from a plurality of engine vehicle types. The one or more processors are configured to: when a user makes a temporary designated input that temporarily designates the selected vehicle type while the battery electric vehicle is stationary, a sample sound of the engine vehicle type corresponding to the temporary designated input is output from the speaker in a predetermined output form.

[0006] In the vehicle management system according to the first aspect of the present disclosure, the sample sound may be an engine roar sound within a predetermined engine speed range.

[0007] In the vehicle management system according to the first aspect of the present disclosure, the driving state of the battery electric vehicle may include an operating state of a manual driving element of the battery electric vehicle. One or more processors may be configured to stop outputting the sample sound when the manual driving element is operated while the sample sound is being output from the speaker.

[0008] In the vehicle management system according to the first aspect of the present disclosure, the manual driving element may include an accelerator pedal.

[0009] In a vehicle management system according to the first aspect of the present disclosure, one or more processors may be configured to accept a change input from a user to change the pitch of a sample sound while the sample sound is being output from a speaker. One or more processors may be configured to adjust the pitch of the sample sound according to the change input when the change input is made. One or more processors may be configured to output a pseudo engine sound to reflect the adjustment of the sample sound when the engine vehicle type corresponding to the temporary designated input is determined to be the selected vehicle type.

[0010] In a vehicle management system according to the first aspect of the present disclosure, one or more processors may be configured to switch the state of an engine sound stop mode in which the output of a pseudo engine sound from a speaker is stopped. One or more processors may be configured to output a pseudo engine start sound of a selected vehicle type from the speaker when the engine sound stop mode is switched from on to off.

[0011] In a vehicle management system according to the first aspect of the present disclosure, the user may include multiple users. The battery electric vehicle may include one or more storage devices and a driver identification sensor, the one or more storage devices being configured to store a database, the database managing user identification information and a designated engine vehicle type associated with each other for each user, and the driver identification sensor being configured to identify the driver of the battery electric vehicle. The designated engine vehicle type may be a vehicle type specified by a designated input that specifies the selected vehicle type. One or more processors may be configured to obtain user identification information about the driver using the driver identification sensor when the battery electric vehicle starts. One or more processors may be configured to read the designated engine vehicle type associated with the user identification information about the driver from the database. One or more processors may be configured to determine the read designated engine vehicle type as the selected vehicle type.

[0012] In the vehicle management system according to the first aspect of the present disclosure, the battery electric vehicle may include a manual mode in which driving characteristics of a manual transmission vehicle are simulated.

[0013] In a vehicle management system according to the first aspect of the present disclosure, a battery electric vehicle may include an accelerator pedal and a sequential shifter. The battery electric vehicle may be configured to change an output characteristic of an electric motor for operation of the accelerator pedal according to a shift operation of the sequential shifter in a manual mode.

[0014] In a vehicle management system according to a first aspect of the present disclosure, a battery electric vehicle may include an accelerator pedal, a pseudo clutch pedal, and a pseudo shift device. When the pseudo shift device is operated, the pseudo clutch pedal may be operated. The battery electric vehicle may be configured to change the output of an electric motor used for operation of the accelerator pedal in manual mode according to the operation of the pseudo clutch pedal and the operation of the pseudo shift device.

[0015] A second aspect of the present disclosure provides a battery electric vehicle, comprising: an electric motor used as a drive source; and one or more processors. The one or more processors are configured to generate a pseudo engine sound based on the driving state of the battery electric vehicle. The one or more processors may be configured to: output a pseudo engine sound from a speaker mounted on the battery electric vehicle; and generate a pseudo engine sound using a sound source corresponding to a selected vehicle type selected from a plurality of engine vehicle types. The one or more processors are configured to: when a user makes a temporary designation input that temporarily designates a selected vehicle type while the battery electric vehicle is stationary, output a sample sound of the engine vehicle type corresponding to the temporary designation input from the speaker in a predetermined output form.

[0016] In a battery electric vehicle according to the second aspect of the present disclosure, one or more processors may be configured to accept a change input from a user to change the pitch of the sample sound while the sample sound is being output from a speaker. One or more processors may be configured to adjust the pitch of the sample sound according to the change input when the change input is made. One or more processors may be configured to output a pseudo engine sound when the engine vehicle type corresponding to the temporary designated input is determined to be the selected vehicle type so as to reflect the adjustment of the sample sound.

[0017] In a battery electric vehicle according to a second aspect of the present disclosure, one or more processors may be configured to switch a state of an engine sound stop mode in which the output of a pseudo engine sound from a speaker is stopped. One or more processors may be configured to output a pseudo engine start sound of a selected vehicle type from the speaker when the engine sound stop mode is switched from on to off.

[0018] In a battery electric vehicle according to a second aspect of the present disclosure, the user may include multiple users. The battery electric vehicle may also include one or more storage devices and a driver identification sensor, the one or more storage devices being configured to store a database, the database managing user identification information and a designated engine vehicle type associated with each other for each user, and the driver identification sensor being configured to identify the driver of the battery electric vehicle. The designated engine vehicle type may be a vehicle type specified by a designated input that specifies the selected vehicle type. One or more processors may be configured to obtain user identification information about the driver using the driver identification sensor when the battery electric vehicle starts. One or more processors may be configured to read a designated engine vehicle type associated with the user identification information about the driver from the database. One or more processors may be configured to determine the read designated engine vehicle type as the selected vehicle type.

[0019] According to the present disclosure, when a user makes a temporary designation input when a battery electric vehicle is stationary, a sample sound of the engine vehicle type corresponding to the temporary designation input is output from a speaker. This allows the user as a driver to listen to the sample sound of each engine vehicle type before designating the engine vehicle type. By listening to the sample sound, the user can determine whether the pseudo engine sound matches his / her taste or mood, even without actually driving the battery electric vehicle. Then, when the pseudo engine sound matches the user's taste or mood, he / she can designate the engine vehicle type. In this way, the trouble given to the user can be reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Features, advantages, and technical and industrial significance of exemplary embodiments of the present invention will be described below with reference to the accompanying drawings, in which like symbols represent like elements, and in which:

[0021] Figure 1 is a conceptual diagram showing a battery electric vehicle and a vehicle management system according to an embodiment;

[0022] Figure 2 is a block diagram showing an example of a basic functional configuration of a vehicle management system;

[0023] Figure 3 is a block diagram showing an example of a functional configuration of a vehicle management system associated with a function of outputting a sample sound;

[0024] Figure 4 is a flowchart showing an example of a process flow of a process performed by a vehicle management system related to a function of outputting a sample sound;

[0025] Figure 5is a block diagram showing an example of a functional configuration of a vehicle management system associated with a function of adjusting the pitch of a pseudo engine sound using a sample sound;

[0026] Figure 6 is a block diagram showing an example of a functional configuration of a vehicle management system associated with a function of outputting a false engine starting sound;

[0027] Figure 7 is a block diagram showing an example of a functional configuration of a vehicle type selection unit at the time of starting of a battery electric vehicle;

[0028] Figure 8 is a block diagram showing a first example of the configuration of a power control system of a battery electric vehicle;

[0029] Fig. 9 shows corresponding examples of an engine model, a clutch model, and a transmission model constituting a manual transmission (MT) vehicle model;

[0030] Fig.10 shows the torque characteristics of the electric motor achieved by motor control performed using the MT vehicle model, compared with the torque characteristics of the electric motor achieved by normal motor control of a battery electric vehicle; and

[0031] Fig.11 is a block diagram showing a second example of the configuration of a power control system of a battery electric vehicle. DETAILED DESCRIPTION

[0032] Embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0033] 1. Battery Electric Vehicles and Vehicle Management Systems

[0034] Figure 1 1 is a conceptual diagram showing a battery electric vehicle 10 and a vehicle management system 100 according to the present embodiment. The battery electric vehicle 10 includes an electric motor 44 as a driving source. The electric motor 44 may be, for example, a brushless direct current (DC) motor or a three-phase alternating current (AC) synchronous motor. The battery electric vehicle 10 uses the electric motor 44 as a driving power unit.

[0035] The battery electric vehicle 10 further includes various sensors 11. The various sensors 11 detect the driving state of the battery electric vehicle 10. Examples of the various sensors 11 include an accelerator position sensor, a brake position sensor, a steering angle sensor, a steering torque sensor, a wheel speed sensor, an acceleration sensor, a rotation speed sensor, a position sensor, a surrounding environment recognition sensor, and a driver recognition sensor. The accelerator position sensor detects the amount of operation of the accelerator pedal. The brake position sensor detects the amount of operation of the brake pedal. The steering angle sensor detects the steering angle of the steering wheel. The steering torque sensor detects the steering torque of the steering wheel. The wheel speed sensor detects the rotation speed of the wheels of the battery electric vehicle 10. The acceleration sensor detects the lateral acceleration and the front-rear acceleration of the battery electric vehicle 10. The rotation speed sensor detects the rotation speed of the electric motor 44. The position sensor detects the position of the battery electric vehicle 10. Examples of the position sensor include a global navigation satellite system (GNSS) sensor. The surrounding environment recognition sensor is a sensor that recognizes (detects) the surrounding environment of the battery electric vehicle 10. Examples of the surrounding environment recognition sensor include a camera, a LIDAR (Light Detection and Ranging System), and a radar. The driver recognition sensor is a sensor that recognizes (detects) the driver of the battery electric vehicle 10 .

[0036] In addition, the battery electric vehicle 10 is equipped with one or more speakers 70. The speaker 70 may be, for example, an in-vehicle speaker that outputs sound to the cabin of the battery electric vehicle 10. In another example, the speaker 70 may be an external speaker that outputs sound to the outside of the battery electric vehicle 10. The battery electric vehicle 10 may include both in-vehicle speakers and external speakers.

[0037] The battery electric vehicle 10 also includes a human machine interface (HMI) 12 as an interface with a user. The HMI 12 presents various information to the user through a display or sound, and accepts various inputs from the user. The HMI 12 is composed of a multi-information display, an instrument display, a steering switch, a speaker phone, a touch panel, etc.

[0038] The vehicle management system 100 is applied to such a battery electric vehicle 10, and manages the battery electric vehicle 10. The entire vehicle management system 100 may be installed on the battery electric vehicle 10. In another example, at least a portion of the vehicle management system 100 may be included in a management server outside the battery electric vehicle 10. In this case, the vehicle management system 100 may remotely manage the battery electric vehicle 10. In yet another example, the vehicle management system 100 may be distributed to the battery electric vehicle 10 and the management server.

[0039] Typically, the vehicle management system 100 includes one or more processors 101 (hereinafter referred to as "processors 101") and one or more storage devices 102 (hereinafter referred to as "storage devices 102"). The processor 101 performs various processes. The processor 101 is composed of a general-purpose processor, a special-purpose processor, a central processing unit (CPU), a graphics processing unit (GPU), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), an integrated circuit, a traditional circuit, etc. The processor 101 may also be referred to as a "circuit" or a "processing circuit". A circuit is hardware that is programmed to implement the described function or hardware that performs the function. The storage device 102 stores various types of information. Examples of the storage device 102 include volatile memory, non-volatile memory, a hard disk drive (HDD), and a solid-state drive (SSD). The functions of the vehicle management system 100 are implemented through the collaboration of the processor 101 and the storage device 102.

[0040] For example, the vehicle management system 100 includes a function as a sound management system that manages sounds related to the battery electric vehicle 10. Specifically, the vehicle management system 100 generates and manages sounds to be output from the speaker 70 mounted on the battery electric vehicle 10. In addition, the vehicle management system 100 outputs the generated sounds through the speaker 70 mounted on the battery electric vehicle 10.

[0041] Specifically, the vehicle management system 100 generates a "pseudo engine sound" that simulates the engine sound of an engine vehicle according to the sound management system. Then, the vehicle management system 100 outputs the pseudo engine sound from the speaker 70 mounted on the battery electric vehicle 10. The engine vehicle is a vehicle that is equipped with an engine (internal combustion engine) and uses the engine as a driving power unit.

[0042] Figure 2 1 is a block diagram showing an example of a basic functional configuration of a vehicle management system 100 as a sound management system. As functional blocks, the vehicle management system 100 includes an information acquisition unit 110, a sound source data management unit 120, an engine sound generation unit 130, a sound output control unit 140, an HMI control unit 150, a vehicle type selection unit 160, and an engine sound stop mode determination unit 170. For example, these functional blocks can be realized by cooperation of a processor 101 and a storage device 102 that execute a vehicle management program 105.

[0043] The information acquisition unit 110 acquires information about the battery electric vehicle 10. Specifically, the information acquisition unit 110 acquires driving state information DRV indicating the driving state of the battery electric vehicle 10. The driving state information DRV includes information about the operation state of the manual driving elements (e.g., accelerator pedal, brake pedal, and steering wheel) of the battery electric vehicle 10, information about the running state of the battery electric vehicle 10, information about the situation around the battery electric vehicle 10, information about the driver of the battery electric vehicle 10, and the like. In general, the driving state information DRV includes information detected by the sensor 11 installed on the battery electric vehicle 10. For example, the driving state information DRV may include the operation amount of the accelerator pedal (accelerator operation amount), the operation amount of the brake pedal (brake operation amount), the steering angle, the steering speed, the steering torque, the wheel speed, the vehicle speed, the front and rear acceleration, the lateral acceleration, the rotation speed of the electric motor 44, and the like. The driving state information DRV may include the position of the battery electric vehicle 10. The driving state information DRV may include the surrounding environment of the battery electric vehicle 10 recognized (detected) by the surrounding environment recognition sensor. The driving state information DRV may include a driver recognition result recognized (detected) by a driver recognition sensor.

[0044] The driving state information DRV also includes a virtual engine speed Ne. Here, it is assumed that the battery electric vehicle 10 uses a virtual engine as a driving power unit. The virtual engine speed Ne is the speed of the virtual engine when it is assumed that the battery electric vehicle 10 is driven by the virtual engine. For example, the information acquisition unit 110 can calculate the virtual engine speed Ne so that it increases as the wheel speed increases. When the battery electric vehicle 10 includes a manual mode (manual transmission (MT) mode) to be discussed later, at the same time, the information acquisition unit 110 can calculate the virtual engine speed Ne in the manual mode based on the wheel speed, the total reduction ratio, and the slip rate of the virtual clutch. The method of calculating the virtual engine speed Ne in the manual mode will be discussed in detail later.

[0045] The sound source data management unit 120 stores engine vehicle sound source data EVS for generating pseudo engine sounds. Specifically, the sound source data management unit 120 stores multiple types of engine vehicle sound source data EVS (EVS-1, ..., EVS-n) corresponding to multiple engine vehicle types (1, ..., n), respectively. That is, the sound source data management unit 120 stores engine vehicle sound source data EVS for each engine vehicle type. Sound source data EVS-i (1≤i≤n) is generated in advance by simulation based on an engine model and a vehicle model corresponding to an engine vehicle model. Sound source data EVS is generally composed of multiple types of sound source data. Examples of the types of sound source data include sound source data (for low speed, medium speed and high speed) on sounds caused by engine combustion, sound source data (for low speed, medium speed and high speed) on sounds caused by a drive system (such as gears), sound source data on noise sounds, and sound source data on event sounds (for example, scratching sounds and engine stall sounds). The sound source data is flexible and adjustable. That is, at least one of the sound pressure and the frequency of the sound represented by the sound source data is flexibly adjustable. The sound source data management unit 120 is mainly implemented by the storage device 102 .

[0046] The HMI control unit 150 controls the HMI 12 to provide various information to the user and accept various inputs from the user in each function associated with the sound management system. Specific contents of the control of the HMI 12 by the HMI control unit 150 will be described appropriately in the description of each function.

[0047] The vehicle type selection unit 160 selects one of the engine vehicle types (1, ..., n). The vehicle type selection unit 160 transmits the selected engine vehicle type (selected vehicle type) k to the engine sound generation unit 130. As discussed later, the vehicle management system 100 generates a pseudo engine sound that reproduces the engine sound of the selected vehicle type k. Specifically, the user can make a designated input via the HMI 12 to designate the selected vehicle type k. This is achieved by the HMI control unit 150 executing the following process.

[0048] The HMI control unit 150 displays a list of multiple engine vehicle types on the HMI 12 in response to a request from the user. The HMI control unit 150 first accepts a temporary designated input for each engine vehicle type displayed on the list. For example, the HMI control unit 150 accepts an operation of selecting each engine vehicle type on the list as a temporary designated input for each engine vehicle type. The user can make a temporary designated input by selecting an engine vehicle type from multiple engine vehicle types on the list. When the user makes a temporary designated input, the HMI control unit 150 displays information of the engine vehicle type corresponding to the temporary designated input on the HMI 12. Examples of the information to be displayed include the type of engine installed on the engine vehicle type, the external image of the engine vehicle type, and the vehicle specifications (e.g., vehicle weight and size) of the engine vehicle type. Then, the HMI control unit 150 accepts a designated input of the engine vehicle type corresponding to the temporary designated input. For example, the HMI control unit 150 displays a designated input operating member (e.g., a button switch) on the HMI 12, which is used to make a designated input to specify the engine vehicle type corresponding to the temporary designated input. The user can make a designated input to specify the engine vehicle type corresponding to the temporary designated input by operating the designated input operating member.

[0049] The vehicle type selection unit 160 acquires the user input information INI from the HMI control unit 150. The vehicle type selection unit 160 determines the state of the designation input designating the selected vehicle type k based on the input information INI. When the user makes the designation input designating the selected vehicle type k, the vehicle type selection unit 160 determines the designated engine vehicle type (hereinafter referred to as "designated engine vehicle type") as the selected vehicle type k.

[0050] The engine sound generation unit 130 (engine sound simulator) is a simulator that generates a pseudo engine sound. The engine sound generation unit 130 acquires at least a portion of the driving state information DRV from the information acquisition unit 110. Specifically, the engine sound generation unit 130 acquires information about the virtual engine speed Ne and the vehicle speed from the information acquisition unit 110. The engine sound generation unit 130 also acquires the selected vehicle type k from the vehicle type selection unit 160. The engine sound generation unit 130 also acquires the sound source data EVS-k corresponding to the selected vehicle type k from the sound source data management unit 120· among multiple types of engine vehicle sound source data EVS (EVS-1, ..., EVS-n). Then, the engine sound generation unit 130 generates a pseudo engine sound that matches the driving state (virtual engine speed Ne and vehicle speed) of the battery electric vehicle 10 by combining one or more sound source data included in the sound source data EVS-k. The engine sound data EGS is data representing the generated pseudo engine sound.

[0051] The generation of pseudo engine sounds is a well-known technique, and the method for generating pseudo engine sounds applicable to the present disclosure is not specifically limited. For example, pseudo engine sounds can be generated by a well-known engine sound simulator used in games, etc. A mapping of a virtual engine speed Ne and frequency and a mapping of a virtual engine torque and sound pressure can be prepared, and the frequency of the pseudo engine sound can be increased and decreased in proportion to the virtual engine speed Ne, and the sound pressure of the pseudo engine sound can be increased and decreased in proportion to the virtual engine torque.

[0052] The vehicle management system 100 includes a mode (engine sound stop mode) for stopping the output of a pseudo engine sound from the speaker 70. The engine sound stop mode determination unit 170 determines whether the engine sound stop mode is turned on or off based on at least one of the driving state information DRV acquired from the information acquisition unit 110 and the input information INI acquired from the HMI control unit 150. For example, the engine sound stop mode determination unit 170 determines the state of the manual mode (MT mode) to be discussed later according to the driving state information DRV. The engine sound stop mode determination unit 170 turns off the engine sound stop mode while applying the manual mode, and turns on the engine sound stop mode while canceling the manual mode. In this case, the vehicle management system 100 outputs a pseudo engine sound from the speaker 70 only while applying the manual mode. In addition, for example, the HMI control unit 150 accepts an input from a user to turn on and off the engine sound stop mode via the HMI 12. Then, the engine sound stop mode determination unit 170 switches to turn on and off the engine sound stop mode according to the input from the user. The engine sound stop mode determination unit 170 transmits a mode state signal MOD indicating an on / off state of the engine sound stop mode to the sound output control unit 140 .

[0053] The sound output control unit 140 receives the engine sound data EGS generated by the engine sound generation unit 130. Then, the sound output control unit 140 outputs the pseudo engine sound from the speaker 70 based on the engine sound data EGS. When outputting the engine sound data EGS, the sound output control unit 140 controls the sound pressure of the pseudo engine sound by controlling the amplifier. In addition, the sound output control unit 140 changes the frequency of the pseudo engine sound by controlling the frequency modulation circuit (FMC).

[0054] The sound output control unit 140 determines whether the engine sound stop mode is on or off from the mode state signal MOD. When the engine sound stop mode is on, the sound output control unit 140 stops outputting the pseudo engine sound from the speaker 70.

[0055] In this way, vehicle management system 100 is configured to output a pseudo engine sound from speaker 70. Therefore, the user who is the driver of battery electric vehicle 10 is provided with an environment that makes him / her feel as if he / she is driving a real engine vehicle.

[0056] 2. Features of this embodiment

[0057] 2.1 Sample sound output

[0058] The user can specify the engine vehicle type as the selected vehicle type k via HMI12. This allows the user as a driver to enjoy a pseudo engine sound that simulates the engine sounds of various engine vehicle types according to his / her taste or mood. On the other hand, it is conceivable that the user determines whether the pseudo engine sound matches his / her taste or mood after actually listening to the pseudo engine sound during driving. Therefore, if it is not known what pseudo engine sound is to be output before the battery electric vehicle 10 actually drives, the user may be given the impression that it is troublesome to specify the engine vehicle type. This may be a factor that reduces the usability of the function.

[0059] Therefore, the vehicle management system 100 according to the present embodiment also has the following function: when the user makes a temporary designation input to temporarily designate the selected vehicle type k while the battery electric vehicle 10 is stationary, a sample sound of the engine vehicle type (hereinafter referred to as the "temporarily designated engine vehicle type") corresponding to the temporary designation input is output from the speaker 70.

[0060] Figure 3 is a block diagram showing an example of a functional configuration of the vehicle management system 100 associated with a function of outputting a sample sound. Figure 3 In the example shown, except Figure 2 In addition to the functional blocks shown, the vehicle management system 100 further includes a sample sound data management unit 180 and a sample sound output determination unit 190. These functional blocks are implemented, for example, by the cooperation of the processor 101 and the storage device 102. Figure 3 In the illustrated example, the functional blocks of the engine sound stop mode determination unit 170 are omitted. Figure 3 In the description, it is assumed that the engine sound stop mode is turned off.

[0061] The sample sound data management unit 180 stores the sample sound data SMS as data about the sample sound. Specifically, the sample sound data management unit 180 stores the sample sound data SMS (SMS-1, ..., SMS-n) corresponding to the engine vehicle types (1, ..., n), respectively. That is, the sample sound data management unit 180 stores the sample sound data SMS for each engine vehicle type. The sample sound data management unit 180 is mainly implemented by the storage device 102.

[0062] The sample sound reproduced based on the sample sound data SMS indicates the characteristics of the pseudo engine sound generated for each engine vehicle type. For example, the sample sound may be an engine roar within a predetermined engine speed range. In another example, the sample sound may be a pseudo engine sound generated during acceleration or deceleration within a predetermined vehicle speed range. In yet another example, the sample sound may be a pseudo engine sound generated for a predetermined pattern of the operating state of the accelerator pedal (accelerator operation amount). The sample sound data SMS may be configured to achieve the reproduction of such multiple types of sample sounds.

[0063] The sample sound data SMS-i (1≤i≤n) is pre-generated based on the simulation of the engine model and the vehicle model of the corresponding engine vehicle type. Optionally, the sample sound data SMS-i (1≤i≤n) is pre-generated based on the sound source data EVS-i of the corresponding engine vehicle type. Optionally, the sample sound data SMS-i (1≤i≤n) is pre-generated by recording the actual engine sound of the corresponding engine vehicle type.

[0064] The sample sound output determination unit 190 determines whether to output a sample sound from the speaker 70. The sample sound output determination unit 190 determines whether the battery electric vehicle 10 is stationary based on the driving state information DRV acquired from the information acquisition unit 110. Whether the battery electric vehicle 10 is stationary may be determined based on the vehicle speed of the battery electric vehicle 10. In addition, the sample sound output determination unit 190 determines the state of the temporary designation input based on the input information INI acquired from the HMI control unit 150. Then, when the user makes a temporary designation input while the battery electric vehicle is stationary, the sample sound output determination unit 190 determines to output the sample sound.

[0065] When determining to output the sample sound, the sample sound output determination unit 190 sets the output specification SP of the sample sound. The output specification SP includes information about the engine vehicle type and output form of the sample sound to be output. The engine vehicle type to which the sample sound is to be output is a temporarily designated engine vehicle type. The output form may include the duration of the reproduction of the sample sound, the number of repetitions, etc. When the sample sound data SMS is configured to achieve the reproduction of multiple types of sample sounds, the output specification SP may include information about the type of the sample sound. The sample sound output determination unit 190 transmits the output specification SP to the sound output control unit 140.

[0066] After determining to output the sample sound, the sample sound output determination unit 190 further determines whether to stop outputting the sample sound. The sample sound output determination unit 190 determines the operating state of the manual driving element of the battery electric vehicle 10 based on the driving state information DRV acquired from the information acquisition unit 110. When the operation of the manual driving element of the battery electric vehicle 10 is detected, the sample sound output determination unit 190 determines to stop outputting the sample sound. For example, when the accelerator pedal is operated, the sample sound output determination unit 190 determines to stop outputting the sample sound. The sample sound output determination unit 190 also determines the state of the designated input based on the input information INI acquired from the HMI control unit 150. When the user makes a designated input to specify the temporarily designated engine vehicle type, the sample sound output determination unit 190 determines to stop outputting the sample sound. When it is determined to stop outputting the sample sound, the sample sound output determination unit 190 transmits a stop request SRQ to the sound output control unit 140.

[0067] When receiving the output specification SP from the sample sound output determination unit 190, the sound output control unit 140 outputs the sample sound from the speaker 70 according to the output specification SP. Specifically, the sound output control unit 140 acquires the sample sound data SMS-j corresponding to the engine vehicle type (temporarily specified engine vehicle type) specified by the output specification SP from the sample sound data management unit 180. Then, the sound output control unit 140 outputs the sample sound from the speaker 70 in a predetermined output form specified by the output specification SP based on the sample sound data SMS-j. Meanwhile, when receiving the stop request SRQ from the sample sound output determination unit 190 while outputting the sample sound, the sound output control unit 140 stops outputting the sample sound.

[0068] The sound output control unit 140 may be configured to stop outputting the pseudo engine sound while outputting the sample sound. The sound output control unit 140 may be configured to resume outputting the pseudo engine sound after reproduction of the sample sound is completed or after output of the sample sound is stopped.

[0069] By providing the vehicle management system 100 with functional components in this manner, the function of outputting a sample sound can be realized. Figure 4 : is a flowchart showing an example of a process flow of a process executed by the vehicle management system 100 related to the function of outputting a sample sound based on the above-described functional components. Figure 4 The process flow shown may be repeatedly executed in a predetermined processing cycle.

[0070] First, in step S110 , the vehicle management system 100 acquires various information including driving state information DRV and input information INI.

[0071] Next, in step S120, the vehicle management system 100 determines whether the battery electric vehicle 10 is stationary based on the driving state information DRV. For example, it can be determined whether the battery electric vehicle 10 is stationary based on the detection value from the wheel speed sensor. When the battery electric vehicle is not stationary (step S120: No), the vehicle management system 100 ends the current process without outputting the sample sound. When the battery electric vehicle is stationary (step S120: Yes), the process proceeds to step S130.

[0072] In step S130, the vehicle management system 100 determines whether a temporary designation input for temporarily designating the selected vehicle type k is made by the user based on the input information INI. When the temporary designation input is not made (step S130: No), the vehicle management system 100 ends the current process without outputting the sample sound. When the temporary designation input is made (step S130: Yes), the process proceeds to step S140.

[0073] In step S140, the vehicle management system 100 stops outputting the pseudo engine sound, and outputs the sample sound for the temporarily designated engine vehicle type from the speaker 70. When the reproduction of the sample sound in the predetermined output form is completed (step S150: Yes), the vehicle management system 100 resumes outputting the pseudo engine sound (step S160), and ends the current process. In this case, the pseudo engine sound to be output is the pseudo engine sound of the initially selected vehicle type k.

[0074] When the sample sound is output from the speaker 70 (step S150: No), the vehicle management system 100 determines whether the manual driving element of the battery electric vehicle 10 is operated or whether a designated input designating the temporarily designated engine vehicle type is made (step S170). When the results of the determination are all negative (step S170: No), the vehicle management system 100 continues to output the sample sound.

[0075] When the manual driving element is operated (step S170: Yes), the vehicle management system 100 stops outputting the sample sound (step S180). Then, the vehicle management system 100 resumes outputting the pseudo engine sound (step S160), and ends the current process. In this case, the pseudo engine sound to be output is the pseudo engine sound of the vehicle type k initially selected.

[0076] When the designated input is made (step S170: Yes), similarly, the vehicle management system 100 stops outputting the sample sound (step S180). Then, the vehicle management system 100 resumes outputting the pseudo engine sound (step S160), and ends the current process. In this case, the temporarily designated engine vehicle type is determined as the designated engine vehicle type, and is selected as the selected vehicle type k. Therefore, the pseudo engine sound to be output is the pseudo engine sound of the newly selected vehicle type k.

[0077] In the vehicle management system 100 according to the present embodiment, as described above, when the user makes a temporary designation input to temporarily designate the selected vehicle type k while the battery electric vehicle 10 is stationary, a sample sound of the engine vehicle type (temporarily designated engine vehicle type) corresponding to the temporary designation input is output from the speaker 70. This allows the user as a driver to listen to the sample sound of each engine vehicle type by making a temporary designation input before the designation input. By listening to the sample sound, the user can determine whether the pseudo engine sound matches his / her taste or mood, even without actually driving the battery electric vehicle 10. Then, when the pseudo engine sound matches his / her taste or mood, the user can make a designation input to determine the temporarily designated engine vehicle type as the designated engine vehicle type. In this way, the trouble given to the user when designating the engine vehicle type can be reduced. In particular, safety can be ensured because the user can determine and designate the engine vehicle type that matches his / her taste or mood while the battery electric vehicle 10 is stationary.

[0078] In the vehicle management system 100 according to the present embodiment, in addition, the output of the sample sound is stopped when the manual driving element of the battery electric vehicle 10 is operated while the sample sound is output from the speaker 70. That is, the output of the sample sound is stopped when the driving of the battery electric vehicle 10 is resumed. This makes it possible to suppress the output of the sample sound from continuing and naturally resume the output of the false engine sound when the driver resumes driving the battery electric vehicle 10.

[0079] 2.2 Pitch adjustment of pseudo engine sound using sample sound

[0080] With the vehicle management system 100 according to the present embodiment, as described above, the user can check the pseudo engine sound of each engine vehicle type and specify the engine vehicle type by listening to the sample sound. Here, it is conceivable that when he / she listens to the sample sound, the user feels that the tone of the sample sound is slightly different from his / her taste. "Tone" may also be referred to as "pitch" or "tone".

[0081] Therefore, the vehicle management system 100 according to the present embodiment may be configured to further include a pitch adjustment function that enables a user to adjust the pitch of a pseudo engine sound using a sample sound.

[0082] Figure 5 1 is a block diagram showing an example of a functional configuration of the vehicle management system 100 associated with a function of adjusting the pitch of a pseudo engine sound using a sample sound. Figure 5 In the example shown, except Figure 3 In addition to the functional blocks shown, the vehicle management system 100 further includes a tone adjustment unit 191. This functional block is implemented by the cooperation of the processor 101 and the storage device 102, for example.

[0083] When the sample sound is being output from the speaker 70, the HMI control unit 150 accepts a change input from the user to change the pitch of the sample sound. For example, the HMI control unit 150 displays a change input member on the HMI 12, which is used to change the input to change the pitch of the sample sound of the engine vehicle type temporarily specified when accepting the temporary specified input. For example, the change input member can be composed of a button, which is used to input to gradually increase or decrease the pitch of the sound. Alternatively, the change input member can be composed of a slide switch, which is used to input to continuously change the pitch of the sound, for example. Or, the change input member can be composed of a selection switch, for example, for selecting one of a plurality of preset tones. The user can change the input to change the pitch of the sample sound by operating such a change input member.

[0084] The tone adjustment unit 191 acquires input information INI from the HMI control unit 150. The tone adjustment unit 191 determines the state of the change input for changing the tone of the sample sound based on the input information INI. When the user makes a change input, the tone adjustment unit 191 sets the tone specification TP. The tone specification TP is set according to the content of the change input. For example, when the user makes a change input to increase the pitch of the sound by two scales, the tone specification TP indicates that the pitch of the sound is increased by two scales from the default value. The tone adjustment unit 191 transmits the tone specification TP to the sound output control unit 140.

[0085] When receiving the tone specification TP from the tone adjustment unit 191 while the sample sound is output from the speaker 70, the sound output control unit 140 adjusts the tone of the sample sound based on the information about the tone specification TP. In addition, when the temporarily designated engine vehicle type associated with the sample sound is a selected vehicle type k based on a designated input from a user, the sound output control unit 140 outputs a pseudo engine sound from the speaker 70, the tone of which has been adjusted based on the information about the tone specification TP. That is, in this case, the sound output control unit 140 outputs a pseudo engine sound reflecting the adjustment of the sample sound. The sound output control unit 140 can store the tone specification TP for each engine vehicle type.

[0086] By providing the vehicle management system 100 with functional components in this way, a function of adjusting the pitch of a pseudo engine sound based on a sample sound can be implemented. This allows the user as a driver to adjust the pitch while listening to the sample sound. Then, by the driver making a specified input to specify a specified engine vehicle type after adjusting the pitch so as to match his / her taste or mood, a pseudo engine sound reflecting the adjustment can be output. In this way, a pseudo engine sound close to the taste or mood of the driver can be output. Therefore, user satisfaction can be improved.

[0087] 2.3 Output of pseudo engine starting sound

[0088] The vehicle management system 100 includes an engine sound stop mode in which the output of a false engine sound is stopped. When the engine sound stop mode is switched from on to off, the vehicle management system 100 resumes outputting the false engine sound. At this time, if a false engine sound of a selected vehicle type k based on the driving state of the battery electric vehicle 10 is suddenly output, the user as a driver may feel a sense of discomfort.

[0089] Therefore, the vehicle management system 100 according to the present embodiment may be configured to further include a function of outputting a pseudo engine start sound of the selected vehicle type k when the engine sound stop mode is switched from on to off.

[0090] Figure 6 1 is a block diagram showing an example of a functional configuration of the vehicle management system 100 associated with a function of outputting a false engine start sound. Figure 6 In the illustrated example, the engine sound stop mode determination unit 170 is shown.

[0091] The sample sound data management unit 180 stores pseudo engine start sound data ESS (ESS-1, ..., ESS-n) corresponding to the engine vehicle types (1, ..., n), in addition to the sample sound data SMS (SMS-1, ..., SMS-n). Figure 3 In comparison, Figure 6 In the example shown, the sample sound data management unit 180 stores pseudo engine starting sound data ESS for each engine vehicle type. The pseudo engine starting sound data ESS-i (1≤i≤n) is pre-generated by simulation based on an engine model and a vehicle model of the corresponding engine vehicle type. Alternatively, the pseudo engine starting sound data ESS-i (1≤i≤n) is pre-generated based on sound source data EVS-i of the corresponding engine vehicle type. Alternatively, the pseudo engine starting sound data ESS-i (1≤i≤n) is pre-generated by recording an actual engine starting sound of the corresponding engine vehicle type.

[0092] The sound output control unit 140 acquires the selected vehicle type k from the vehicle type selection unit 160. The sound output control unit 140 reads the pseudo engine start sound data OSS-k according to the selected vehicle type k. Then, when the engine sound stop mode is turned from on to off, the sound output control unit 140 outputs the pseudo engine start sound from the speaker 70 based on the pseudo engine start sound data OSS-k.

[0093] By providing the vehicle management system 100 with functional components in this way, a function of outputting a pseudo engine start sound can be realized. This makes it possible to reduce the discomfort felt by the user when the engine sound stop mode is switched from on to off. Therefore, user satisfaction can be improved.

[0094] 2.4 Selected vehicle type when starting a battery electric vehicle

[0095] When there are multiple users of the battery electric vehicle 10, it is assumed that each time the battery electric vehicle 10 is driven, a different user drives the battery electric vehicle 10. It is conceivable that each user has a pseudo engine sound that he / she likes, which may be different from pseudo engine sounds that other users like. In this case, the user as a driver may have the impression that it is troublesome to repeatedly specify the engine vehicle type according to his / her taste every time he / she starts driving the battery electric vehicle 10.

[0096] Therefore, in the vehicle management system 100 according to the present embodiment, the vehicle type selection unit 160 may be configured to determine the selected vehicle type k according to the user who is the driver when the battery electric vehicle 10 starts.

[0097] Figure 7An example of the functional configuration of the vehicle type selection unit 160 is shown when the battery electric vehicle 10 is started. The vehicle type selection unit 160 includes a user identification unit 161 and a designated engine vehicle type acquisition unit 162.

[0098] The user identification unit 161 acquires user identification information about the driver using the driver identification sensor 11a. Examples of the driver identification sensor 11a include a driver monitor, a fingerprint authentication sensor, and an integrated circuit (IC) tag authentication sensor. The user identification information is information that can identify each user of the battery electric vehicle 10. Typically, the user identification information is a user identifier (ID). For example, the user identification unit 161 acquires user identification information by identifying the user as the driver based on the feature amount of the driver image acquired by the driver monitor. Alternatively, the user identification unit 161 acquires user identification information about the driver, for example, directly from authentication information from a fingerprint authentication sensor or an IC tag authentication sensor. The user identification unit 161 sends the acquired user identification information to the designated engine vehicle type acquisition unit 162.

[0099] The designated engine vehicle type acquisition unit 162 is connected to the user database D10. The user database D10 manages information about each user of the battery electric vehicle 10. Specifically, the user database D10 manages the user identification information and the designated engine vehicle type (see Figure 7 ). The designated engine vehicle type managed by the user database D10 is generally the engine vehicle type designated by the most recent designated input from the user.

[0100] The designated engine vehicle type acquisition unit 162 acquires the user identification information about the user from the user identification unit 161. Then, the designated engine vehicle type acquisition unit 162 refers to the user database D10 and reads the designated engine vehicle type associated with the user identification information about the driver. For example, when the user identification information about the driver is "B10", the designated engine vehicle type acquisition unit 162 reads "vehicle type 5" from the user database D10.

[0101] The vehicle type selection unit 160 determines the selected vehicle type k at the time of start-up of the battery electric vehicle 10 as the designated engine vehicle type read by the designated engine vehicle type acquisition unit 162 .

[0102] In this way, the selected vehicle type k can be determined according to the user as the driver at the start of the battery electric vehicle 10. This makes it possible to reduce the trouble given to the driver at the start of driving the battery electric vehicle 10.

[0103] 3. Application to battery electric vehicles with manual mode (MT mode)

[0104] The electric motor used as a driving power unit in a general battery electric vehicle is significantly different in torque characteristics from the internal combustion engine used as a driving power unit in a conventional vehicle (CV). Due to the difference in torque characteristics of the power unit, a battery electric vehicle generally does not include a transmission, while a CV inevitably includes a transmission. Of course, a general battery electric vehicle does not include a manual transmission (MT), in which the gear ratio is switched by manual operation of the driver. Therefore, there is a significant difference in driving feel between driving a conventional vehicle with an MT (hereinafter referred to as an "MT vehicle") and driving a battery electric vehicle.

[0105] On the other hand, the torque of the electric motor can be relatively easily controlled by controlling the applied voltage or magnetic field. Therefore, the desired torque characteristics within the operating range of the electric motor can be obtained by appropriately controlling the electric motor. By utilizing this feature, the torque characteristics unique to MT vehicles can be simulated by controlling the torque of the battery electric vehicle. In addition, the battery electric vehicle can be provided with a pseudo shifter so that the driver can obtain a driving feel similar to that of an MT vehicle. This enables the battery electric vehicle to simulate an MT vehicle.

[0106] That is, in a battery electric vehicle, the output of the electric motor is controlled so as to simulate the driving characteristics (torque characteristics) peculiar to an MT vehicle. The driver performs a pseudo-manual shifting operation by operating a pseudo-shifter. In response to the driver's pseudo-manual shifting operation, the battery electric vehicle changes the driving characteristics (torque characteristics) by simulating an MT vehicle. This allows the driver of the battery electric vehicle to feel as if he / she is driving an MT vehicle. The control mode of the electric motor for simulating the driving characteristics and manual shifting operation of an MT vehicle will be referred to as a "manual mode" or "MT mode."

[0107] The battery electric vehicle 10 according to the present disclosure may include such a manual mode (MT mode). In the MT mode, the battery electric vehicle 10 generates a pseudo engine sound that matches the driving operation of the driver and outputs the pseudo engine sound via the speaker 70. Since not only the driving operation of the MT vehicle but also the engine sound of the MT vehicle is reproduced, the satisfaction of the driver who seeks realism is improved.

[0108] An example of a configuration of the battery electric vehicle 10 having a manual mode (MT mode) will be described below.

[0109] 3.1 First Configuration Example (Sequential Shifter)

[0110] Figure 81 is a block diagram showing a first example of the configuration of a power control system of a battery electric vehicle 10 according to the present embodiment. The battery electric vehicle 10 includes an electric motor 44, a battery 46, and an inverter 42. The electric motor 44 is a driving power unit. The battery 46 stores electric energy to drive the electric motor 44. That is, the battery electric vehicle 10 is a pure electric vehicle (BEV) that travels based on the electric energy stored in the battery 46. During acceleration, the inverter 42 converts the DC power input from the battery 46 into driving power for the electric motor 44. At the same time, during deceleration, the inverter 42 converts the regenerative power input from the electric motor 44 into DC power to charge the battery 46.

[0111] The battery electric vehicle 10 includes an accelerator pedal 22, which is used by a driver to input an acceleration request to the battery electric vehicle 10. The accelerator pedal 22 is provided with an accelerator position sensor 32 that detects an accelerator operation amount.

[0112] The battery electric vehicle 10 includes a sequential shifter 24. The sequential shifter 24 may be a fork type shifter, or may be a lever type pseudo shifter.

[0113] The fork type shifter is a dummy thing different from a real fork type shifter. The fork type shifter is constructed similarly to a fork type shifter provided in an MT vehicle without a clutch pedal. The fork type shifter is attached to a steering wheel. The fork type shifter includes an upshift switch and a downshift switch for determining an operation position. An upshift signal 34u is generated when the upshift switch is pulled forward, and a downshift signal 34d is generated when the downshift switch is pulled forward.

[0114] Meanwhile, the lever-type pseudo shifter is a dummy thing different from a real shifter, like a fork-type shifter. The lever-type pseudo shifter is constructed similarly to a lever-type shifter provided in an MT vehicle without a clutch pedal. The lever-type pseudo shifter is configured to output an upshift signal 34u when the shift lever is tilted forward, and to output a downshift signal 34d when the shift lever is tilted backward.

[0115] The wheel 26 of the battery electric vehicle 10 is provided with a wheel speed sensor 36. The wheel speed sensor 36 serves as a vehicle speed sensor that detects the vehicle speed of the battery electric vehicle 10. Furthermore, the electric motor 44 is provided with a rotation speed sensor 38 that detects the rotation speed of the electric motor 44.

[0116] The battery electric vehicle 10 includes a control device 50. The control device 50 is typically an electronic control unit (ECU) mounted on the battery electric vehicle 10. The control device 50 may be a combination of a plurality of ECUs. The control device 50 includes an interface, a memory, and a processor. The on-board network is connected to the interface. The memory includes a random access memory (RAM) for temporarily storing data and a read-only memory (ROM) for storing programs executable by the processor and various data associated with the programs. The program consists of a plurality of instructions. The processor reads the program and data from the memory, executes the program, and generates a control signal based on a signal acquired from a sensor.

[0117] For example, the control device 50 controls the electric motor 44 by pulse width modulation (PWM) control of the inverter 42. Signals from the accelerator position sensor 32, the sequential shifter 24 (upshift switch and downshift switch when the sequential shifter 24 is a fork type shifter), the wheel speed sensor 36, and the rotation speed sensor 38 are input to the control device 50. The control device 50 processes these signals and calculates a motor torque command value for PWM control of the inverter 42.

[0118] The control device 50 includes an automatic mode (EV mode) and a manual mode (MT mode) as control modes. The automatic mode is a general control mode for driving the battery electric vehicle 10 as a general battery electric vehicle. The automatic mode is programmed to continuously change the output of the electric motor 44 according to the operation of the accelerator pedal 22. On the other hand, the manual mode is a control mode for driving the battery electric vehicle 10 like an MT vehicle. The manual mode is programmed to change the output characteristics of the electric motor 44 for the operation of the accelerator pedal 22 according to the upshift operation and downshift operation of the sequential shifter 24. That is, the manual mode is a control mode in which the output of the electric motor 44 can be changed in response to the driving operation of the vehicle components other than the accelerator pedal 22 or the brake pedal. The automatic mode (EV mode) and the manual mode (MT mode) are switchable.

[0119] The control device 50 includes an automatic mode torque calculation unit 54 and a manual mode torque calculation unit 56. Each of the units 54, 56 may be an independent ECU, or may be a function of the ECU obtained by a processor executing a program stored in a memory.

[0120] The automatic mode torque calculation unit 54 includes a function of calculating the motor torque when the electric motor 44 is controlled in the automatic mode. The automatic mode torque calculation unit 54 stores a motor torque command map. The motor torque command map is a map for determining the motor torque according to the accelerator operation amount and the rotation speed of the electric motor 44. A signal from the accelerator position sensor 32 and a signal from the rotation speed sensor 38 are input as parameters for the motor torque command map. The motor torque command map outputs a motor torque corresponding to these signals. For this reason, even if the driver operates the sequential shifter 24 in the automatic mode, such an operation will not be reflected in the motor torque.

[0121] The manual mode torque calculation unit 56 includes an MT vehicle model. The MT vehicle model is a model for calculating the drive wheel torque that should be obtained by the operation of the accelerator pedal 22 and the sequential shifter 24 under the assumption that the battery electric vehicle 10 is an MT vehicle.

[0122] Will refer to Fig. 9 The MT vehicle model of the manual mode torque calculation unit 56 is described as follows. Fig. 9 As shown, the MT vehicle model includes an engine model 561, a clutch model 562, and a transmission model 563. The engine, clutch, and transmission virtually implemented by the MT vehicle model will be referred to as a "virtual engine," a "virtual clutch," and a "virtual transmission," respectively. The engine model 561 models the virtual engine. The clutch model 562 models the virtual clutch. The transmission model 563 models the virtual transmission.

[0123] The engine model 561 is used to calculate the virtual engine speed Ne and the virtual engine output torque Teout. The virtual engine speed Ne is calculated based on the wheel speed Nw, the total reduction ratio R and the virtual clutch slip ratio Rslip. For example, the virtual engine speed Ne is expressed by the following equation (1).

[0124] Equation (1): Ne = Nw × R / (1-Rslip)

[0125] The virtual engine output torque Teout is calculated based on the virtual engine speed Ne and the accelerator operation amount Pap. The virtual engine output torque Teout is calculated using a map that specifies the relationship between the accelerator operation amount Pap, the virtual engine speed Ne, and the virtual engine output torque Teout, such as Fig. 9 In this map, for each accelerator operation amount Pap, the virtual engine output torque Teout is given for the virtual engine speed Ne. Fig. 9The torque characteristic indicated in can be set to the characteristic assumed for the gasoline engine, or can be set to the characteristic assumed for the diesel engine. In addition, the torque characteristic can be set to the characteristic assumed for the naturally aspirated engine, or can be set to the characteristic assumed for the supercharged engine.

[0126] The clutch model 562 is used to calculate the torque transfer gain K. The torque transfer gain K is a gain for calculating the torque transfer degree of the virtual clutch according to the virtual clutch operation amount Pc. The virtual clutch operation amount Pc is usually 0%, and is temporarily increased to 100% in conjunction with the switching of the virtual gear of the virtual transmission. The clutch model 562 has the following characteristics: Fig. 9 In this map, the torque transfer gain K is given relative to the virtual clutch operation amount Pc. Fig. 9 , Pc0 corresponds to the position where the virtual clutch operation amount Pc is 0%, and Pc3 corresponds to the position where the virtual clutch operation amount Pc is 100%. The range from Pc0 to Pc1 and the range from Pc2 to Pc3 are dead zones, in which the torque transfer gain K does not change according to the virtual clutch operation amount Pc. The clutch model 562 is used to calculate the clutch output torque Tcout using the torque transfer gain K. The clutch output torque Tcout is the torque output from the virtual clutch. For example, the clutch output torque Tcout is given as the product of the virtual engine output torque Teout and the torque transfer gain K (Tcout=Teout×K).

[0127] The clutch model 562 is also used to calculate the slip ratio Rslip. The engine model 561 uses the slip ratio Rslip to calculate the virtual engine speed Ne. The slip ratio Rslip can be calculated using a map that gives the slip ratio Rslip relative to the virtual clutch operation amount Pc, just like the torque transfer gain K.

[0128] The transmission model 563 is used to calculate the transmission ratio r. The transmission ratio r is a transmission ratio determined by the virtual gear position GP in the virtual transmission. When an upshift operation of the sequential shifter 24 is received, the virtual gear position GP is upshifted by one gear. On the other hand, when a downshift operation of the sequential shifter 24 is received, the virtual gear position GP is downshifted by one gear. The transmission model 563 has the following features: Fig. 9The mapping shown. In the mapping, the gear ratio r is given relative to the virtual gear GP so that the gear ratio r is lower as the virtual gear GP becomes higher. The transmission model 563 is used to calculate the transmission output torque Tgout using the gear ratio r and the clutch output torque Tcout obtained from the mapping. For example, the transmission output torque Tgout is given as the product of the clutch output torque Tcout and the gear ratio r (Tgout=Tcout×r). The transmission output torque Tgout changes non-continuously according to the switching of the gear ratio r. These discontinuous changes in the transmission output torque Tgout cause gear shift shocks, thereby allowing the vehicle to act like a vehicle with a stepped transmission.

[0129] The MT vehicle model is used to calculate the drive wheel torque Tw using a predetermined reduction ratio rr. The reduction ratio rr is a fixed value determined by the mechanical structure from the virtual transmission to the drive wheels. The value obtained by multiplying the reduction ratio rr by the transmission ratio r is the total reduction ratio R discussed above. The MT vehicle model is used to calculate the drive wheel torque Tw based on the transmission output torque Tgout and the reduction ratio rr. For example, the drive wheel torque Tw is given as the product of the transmission output torque Tgout and the reduction ratio rr (Tw = Tgout × rr).

[0130] The control device 50 converts the drive wheel torque Tw calculated using the MT vehicle model into the required motor torque Tm. The required motor torque Tm is the motor torque required to achieve the drive wheel torque Tw calculated using the MT vehicle model. The drive wheel torque Tw is converted into the required motor torque Tm using the reduction ratio from the output shaft of the electric motor 44 to the drive wheel. Then, the control device 50 controls the electric motor 44 by controlling the inverter 42 according to the required motor torque Tm.

[0131] Fig.10 1 shows the torque characteristics of the electric motor 44 achieved by the motor control performed using the MT vehicle model, compared with the torque characteristics of the electric motor 44 achieved by the usual motor control for a pure electric vehicle (BEV) (dashed line in the figure). In the case where the motor control is performed using the MT vehicle model, as shown in FIG. Fig.10 As shown, a torque characteristic (solid line in the figure) simulating the torque characteristic of an MT vehicle can be realized according to the virtual gear set by the sequential shifter 24. Fig.10 In the , the number of gears is six.

[0132] 3.2 Second Configuration Example

[0133] Fig.111 is a block diagram showing a second example of the configuration of the power control system of the battery electric vehicle 10 according to the present embodiment. Here, only the components different from those according to the first configuration example discussed above will be described. Specifically, in the second configuration example, the battery electric vehicle 10 includes a pseudo shift lever (pseudo shift device) 27 and a pseudo clutch pedal 28 instead of the sequential shifter 24 provided in the first configuration example. The pseudo shift lever 27 and the pseudo clutch pedal 28 are virtual objects different from the actual shift lever and clutch pedal.

[0134] The pseudo shift lever 27 is configured to simulate a shift lever provided in an MT vehicle. The arrangement and operating feel of the pseudo shift lever 27 are equivalent to those in an actual MT vehicle. The pseudo shift lever 27 is provided with positions corresponding to the gear positions, such as the first gear, the second gear, the third gear, the fourth gear, the fifth gear, the sixth gear, the reverse gear, and the neutral gear. The pseudo shift lever 27 is provided with a shift position sensor 27a, which detects the gear position by determining in which position the pseudo shift lever 27 is located.

[0135] The pseudo clutch pedal 28 is configured to simulate a clutch pedal provided in an MT vehicle. The arrangement and operating feel of the pseudo clutch pedal 28 are equivalent to those in an actual MT vehicle. When the pseudo shift lever 27 is operated, the pseudo clutch pedal 28 is operated. That is, when it is desired to change the gear setting using the pseudo shift lever 27, the driver depresses the pseudo clutch pedal 28, and when the change of the gear setting is completed, the depressing of the pseudo clutch pedal 28 is stopped and the pseudo clutch pedal 28 is returned to the original position. The pseudo clutch pedal 28 is provided with a clutch position sensor 28a, and the clutch position sensor 28a detects the depression amount of the pseudo clutch pedal 28.

[0136] Signals from the accelerator position sensor 32, the shift position sensor 27a, the clutch position sensor 28a, the wheel speed sensor 36, and the rotation speed sensor 38 are input to the control device 50. The control device 50 processes these signals and calculates a motor torque command value for PWM control of the inverter 42.

[0137] The control device 50 includes an automatic mode and a manual mode as control modes, as in the first configuration example discussed above. The automatic mode is programmed to continuously change the output of the electric motor 44 according to the operation of the accelerator pedal 22. On the other hand, the manual mode is a control mode for driving the battery electric vehicle 10 like an MT vehicle. The manual mode is programmed to change the output and output characteristics of the electric motor 44 for the operation of the accelerator pedal 22 according to the operation of the pseudo clutch pedal 28 and the pseudo shift lever (pseudo shift device) 27. That is, the manual mode is a control mode in which the output of the electric motor 44 can be changed in response to the driving operation of the vehicle constituent elements other than the accelerator pedal 22 or the brake pedal.

[0138] The vehicle model of the manual mode torque calculation unit 56 is Fig. 9 However, the virtual clutch operation amount Pc is replaced by the depression amount of the pseudo clutch pedal 28 detected by the clutch position sensor 28a. In addition, the virtual gear position GP is determined according to the position of the pseudo shift lever 27 detected by the shift position sensor 27a.

Claims

1. A vehicle management system to be applied to a battery electric vehicle, the battery electric vehicle including an electric motor as a driving source, the vehicle management system being characterized by including one or more processors, the one or more processors being configured to: generating a pseudo engine sound based on a driving state of the battery electric vehicle; outputting the pseudo engine sound from a speaker mounted on the battery electric vehicle; generating the pseudo engine sound using a sound source corresponding to a selected vehicle type selected from a plurality of engine vehicle types; and When a user makes a temporary designation input that temporarily designates the selected vehicle type while the battery electric vehicle is stationary, a sample sound for an engine vehicle type corresponding to the temporary designation input is output from the speaker in a predetermined output form.

2. The vehicle management system according to claim 1, characterized in that: The sample sound is an engine roar sound within a predetermined engine speed range.

3. The vehicle management system according to claim 1, characterized in that: The driving state of the battery electric vehicle includes an operating state of a manual driving element of the battery electric vehicle; and The one or more processors are configured to stop outputting the sample sound when the manual steering element is operated while the sample sound is being output from the speaker.

4. The vehicle management system according to claim 3, characterized in that: The manual driving element includes an accelerator pedal.

5. The vehicle management system according to claim 1, characterized in that: The one or more processors are configured to: accepting a change input from the user to change the pitch of the sample sound while the sample sound is being output from the speaker; When the change input is made, adjusting the pitch of the sample sound according to the change input; and When the engine vehicle type corresponding to the temporary specified input is determined to be the selected vehicle type, the pseudo engine sound is output so as to reflect the adjustment of the sample sound.

6. The vehicle management system according to claim 1, characterized in that: The one or more processors are configured to: switching a state of an engine sound stop mode in which output of the false engine sound from the speaker is stopped; and When the engine sound stop mode is changed from on to off, a pseudo engine start sound of the selected vehicle type is output from the speaker.

7. The vehicle management system according to claim 1, characterized in that: The user includes a plurality of users; The battery electric vehicle includes one or more storage devices and a driver identification sensor, wherein the one or more storage devices are configured to store a database that manages user identification information and a designated engine vehicle type in association with each other for each user, and the driver identification sensor is configured to identify a driver of the battery electric vehicle; The designated engine vehicle type is a vehicle type designated by a designated input designating the selected vehicle type; and The one or more processors are configured to: when the battery electric vehicle is started, acquiring user identification information about the driver using the driver identification sensor, reading the designated engine vehicle type associated with the user identification information about the driver from the database, and The read designated engine vehicle type is determined as the selected vehicle type.

8. The vehicle management system according to any one of claims 1 to 7, characterized in that: The battery electric vehicle includes a manual mode in which driving characteristics of a manual transmission vehicle are simulated.

9. The vehicle management system according to claim 8, characterized in that: The battery electric vehicle includes an accelerator pedal and a sequential shifter; and The battery electric vehicle is configured to change an output characteristic of the electric motor for operation of the accelerator pedal according to a shift operation of the sequential shifter in the manual mode.

10. The vehicle management system according to claim 8, characterized in that: The battery electric vehicle includes an accelerator pedal, a pseudo clutch pedal, and a pseudo shift device; When the pseudo shift device is operated, the pseudo clutch pedal is operated; and The battery electric vehicle is configured to change the output of the electric motor for operation of the accelerator pedal according to operation of the pseudo clutch pedal and operation of the pseudo shift device in the manual mode.

11. A battery electric vehicle, characterized in that include: an electric motor serving as a driving source; as well as One or more processors configured to: generating a pseudo engine sound based on a driving state of the battery electric vehicle, outputting the pseudo engine sound from a speaker mounted on the battery electric vehicle, generating the pseudo engine sound using a sound source corresponding to a selected vehicle type selected from a plurality of engine vehicle types, and When a user makes a temporary designation input that temporarily designates the selected vehicle type while the battery electric vehicle is stationary, a sample sound for an engine vehicle type corresponding to the temporary designation input is output from the speaker in a predetermined output form.

12. The battery electric vehicle according to claim 11, characterized in that The one or more processors are configured to: accepting a change input from the user to change the pitch of the sample sound while the sample sound is being output from the speaker; When the change input is made, adjusting the pitch of the sample sound according to the change input; and When the engine vehicle type corresponding to the temporary specified input is determined to be the selected vehicle type, the pseudo engine sound is output so as to reflect the adjustment of the sample sound.

13. The battery electric vehicle according to claim 11, characterized in that The one or more processors are configured to: switching a state of an engine sound stop mode in which output of the false engine sound from the speaker is stopped; and When the engine sound stop mode is changed from on to off, a pseudo engine start sound of the selected vehicle type is output from the speaker.

14. The battery electric vehicle according to claim 11, characterized in that: The user includes a plurality of users; The battery electric vehicle includes one or more storage devices and a driver identification sensor, wherein the one or more storage devices are configured to store a database and the driver identification sensor is configured to identify a driver of the battery electric vehicle; The database is configured to manage user identification information and a designated engine vehicle type in association with each other for each of the plurality of users; The designated engine vehicle type is a vehicle type designated by a designated input designating the selected vehicle type; and The one or more processors are configured to: when the battery electric vehicle is started, acquiring user identification information about the driver using the driver identification sensor, reading the designated engine vehicle type associated with the user identification information about the driver from the database, and The read designated engine vehicle type is determined as the selected vehicle type.

Images