Internal Combustion Engine Emulation for Electric Vehicle Drivers

Abstract

A computer-implemented method includes: receiving, by an electric vehicle (EV), a user selection of a first vehicle type from among a plurality of vehicle types, each having an internal combustion engine, the user selection being made for an emulation mode of operation of the EV; receiving, by the EV, a first input made by a driver using an accelerator pedal of the EV with the first vehicle type selected for the emulation mode of operation, the first input being associated with a first acceleration of the EV with the emulation mode of operation inactive; and, in response to the first input and while the emulation mode of operation is active, providing to the EV a second acceleration determined based on the first vehicle type and the first input.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 269,740, entitled “EMULATION OF INTERNAL COMBUSTION ENGINE FOR DRIVER OF ELECTRIC VEHICLE,” filed March 22, 2022, the disclosure of which is incorporated herein by reference in its entirety.

[0002] This document concerns driver-facing internal combustion engine emulation for electric vehicles. [Background technology]

[0003] In recent years, global transportation has begun to transition away from powertrains driven primarily by fossil fuels and towards more sustainable energy sources, most notably electric motors powered by on-board energy storage. Electric vehicles (EVs) are typically quieter than internal combustion engine (ICE) vehicles. Some EVs have powertrains that generate much more torque than typical ICE vehicles, especially at low speeds. Summary of the Invention

[0004] In a first aspect, a computer-implemented method includes: receiving, by an electric vehicle (EV), a user selection of a first vehicle type from among a plurality of vehicle types, each having an internal combustion engine, the user selection being made for an emulation mode of operation of the EV; receiving, by the EV, a first input made by a driver using an accelerator pedal of the EV with the first vehicle type selected for the emulation mode of operation, the first input being associated with a first acceleration of the EV with the emulation mode of operation inactive; and, in response to the first input and while the emulation mode of operation is active, providing to the EV a second acceleration determined based on the first vehicle type and the first input.

[0005] Implementations may include any or all of the following features: Providing the second acceleration to the EV includes emulating an acceleration of the first vehicle type. Emulating the acceleration of the first vehicle type includes applying an acceleration reduction to the EV. Emulating the acceleration of the first vehicle type includes considering at least one characteristic of the first vehicle type selected from the group consisting of rotational inertia, transmission gear shift, turbocharger rotation speed, boost control, anti-lag control, launch control, or a blow-off valve. Emulating the acceleration of the first vehicle type includes emulating a gear shift of the first vehicle type. Emulating the acceleration of the first vehicle type includes applying at least the first input to a model corresponding to the first vehicle type. The computer-implemented method further includes emulating an instrument cluster of the first vehicle type on a display device of the EV. The computer-implemented method further comprises emulating a sound of the first vehicle type using a speaker of the EV. The sound of the first vehicle type comprises a motor sound. The sound of the first vehicle type comprises a non-motor sound. The computer-implemented method further comprises receiving a second input at the EV and applying the second input in emulating the first vehicle type. The second input comprises a gear shift request made using a hardware controller of the EV, and applying the second input in emulating the first vehicle type comprises adjusting the second acceleration based on the second input. The first vehicle type is a tracked vehicle. The first vehicle type is a non-road vehicle. The computer-implemented method further comprises limiting the second acceleration at least once by the first acceleration. The second acceleration is limited by the first acceleration in response to a magnitude of the second acceleration exceeding an upper limit. The second acceleration is based on a scaling of an acceleration capability of the first vehicle type.Providing the second acceleration to the EV includes modifying a torque crossover.

[0006] In a second aspect, an electric vehicle (EV) includes: a selection control for receiving a user selection of a first vehicle type from among a plurality of vehicle types each having an internal combustion engine, the user selection being made for an emulation mode of operation of the EV; an accelerator pedal for generating a first input made by a driver of the EV with the first vehicle type selected for the emulation mode of operation, the first input being associated with a first acceleration of the EV with the emulation mode of operation inactive; and a model for providing a second acceleration to the EV using a powertrain of the EV while the emulation mode of operation is active, the second acceleration being determined based on the first vehicle type and the first input.

[0007] Implementations may include any or all of the following features: The EV further comprises a display device, where the model outputs images emulating an instrument cluster of the first vehicle type; The EV further comprises a speaker, where the model outputs sounds emulating sounds of the first vehicle type; The EV further comprises a hardware control for the driver to make a gear shift request, where the model adjusts the second acceleration based on the gear shift request; The model has inputs including an accelerator pedal input, a gear shift request, and a vehicle state, and the model generates outputs including a longitudinal acceleration target, a sound, and a driver metric; The second acceleration is limited at least once by the first acceleration; The second acceleration is limited by the first acceleration in response to a magnitude of the second acceleration exceeding an upper limit.

[0008] In a third aspect, an EV includes: a selection control for receiving a user selection of a first vehicle type from among a plurality of vehicle types each having an internal combustion engine, the user selection being made with respect to an emulation mode of operation of the EV; a powertrain; and means for emulating acceleration of the first vehicle type without exceeding an associated acceleration of the EV using the powertrain and while the emulation mode of operation is active. [Brief description of the drawings]

[0009] [Figure 1] 1 illustrates an example of an emulation controller that may be used with an electric vehicle (EV).

[0010] [Diagram 2] An example of an EV instrument panel is shown.

[0011] [Diagram 3] A diagram of EV acceleration capability that encompasses the acceleration capability of an ICE vehicle is shown.

[0012] [Figure 4] 1 illustrates an exemplary block diagram of an EV.

[0013] [Diagram 5] 1 illustrates generally an example block diagram of a model for emulating at least the acceleration of an ICE vehicle.

[0014] [Figure 6] 1 shows an example of a vehicle sound system that can emulate the sound of an ICE vehicle.

[0015] [Figure 7] An example of the method is given below.

[0016] [Figure 8] 1 shows an example of a system that can perform emulation in an EV.

[0017] [Figure 9] 1 shows an example of an architecture for performing emulation in an EV.

[0018] [Figure 10] 1 illustrates a schematic representation of a torque crossover emulation.

[0019] [Figure 11] 1 shows an example of scaling in emulation.

[0020] [Figure 12] 1 illustrates an exemplary architecture of a computing device that may be used to implement aspects of the present disclosure.

[0021] Like reference numbers in the various drawings indicate like elements. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0022] Described herein are examples of systems and techniques for an EV to emulate one or more aspects of an ICE vehicle, such as its acceleration. This may allow an EV driver to enjoy a convincing experience of a powertrain different from that of the EV. An EV may be characterized by its nearly silent operation and smooth, powerful acceleration, both of which are attributable to its electric powertrain. For example, an EV may provide an "emulation mode of operation" in which the EV selectively and dynamically reduces the torque output by its powertrain to simulate that of an ICE vehicle. This may be referred to as providing a "virtual powertrain." Optionally, the EV may also emulate the visuals and / or sounds of the ICE vehicle's gauges. Thus, the present subject matter can add personality to an EV, making it a more attractive and exciting choice and increasing its appeal to a wide range of automotive enthusiasts.

[0023] If the driver selects the emulation mode of operation, the EV can automatically and seamlessly simulate the powertrain of the selected ICE vehicle based on driver input and EV state input. The EV can dynamically limit the torque output of its powertrain to match the acceleration output of the ICE vehicle according to the model. In some implementations, a convincing auditory experience tailored to the selected ICE vehicle can be provided. In some implementations, the EV can provide relevant metrics to the driver (e.g., by emulating one or more dials or other instrument devices of the ICE vehicle).

[0024] The model used as part of the emulation mode of operation may be designed with the goal of facilitating emulation to the acceleration of the modeled ICE vehicle, with the constraint that torque is dynamically limited. For functional safety, an EV emulating an ICE vehicle should not implement a torque greater than the EV itself would generate in the same situation with the emulation mode of operation deactivated. Thus, the goal of the model may be to reproduce the acceleration of the model ICE vehicle, rather than merely replicating the motor torque or its axle torque of the model ICE vehicle. That is, the emulation mode of operation may aim to emulate the acceleration feel and acceleration force of an ICE vehicle. To do so, the model may be scaled for one or more actual aspects or characteristics of the EV, including, but not limited to, the EV's vehicle mass, or its voltage, or state of energy (SoE). When the EV driver presses the accelerator of the EV, the unfiltered torque demand corresponding to the accelerator press and the emulated vehicle acceleration (e.g., in meters per second (m / s)) calculated by the model may be scaled to the desired torque. 2) may be subject to one or more comparisons. The filtered torque request output to the EV's controller may then be the smaller of the torque request generated by the model or the unfiltered torque request from the EV driver. That is, with the emulation mode of operation active, the EV may filter the torque request through an on-board model and limit the output torque to replicate the longitudinal acceleration of a particular ICE powertrain, and such torque output may be scaled to account for (e.g., to compensate for) weight differences between the EV and ICE vehicles.

[0025] Models that emulate a particular ICE may be provided by companies that currently or have previously manufactured ICE vehicles. For example, models that are specific to a particular type of ICE vehicle may be offered as licensed versions. In some implementations, generic versions of the emulated ICE vehicle may be provided. For example, such models may replicate the acceleration performance of an ICE vehicle's powertrain in a generic manner.

[0026] The emulation operating mode, which may be implemented using software and / or hardware components of the EV, may be installed in the EV during manufacture, or it may be added to the EV later (e.g., upon request of the driver). For example, an over-the-air software update may be provided via a wireless communication channel to install the emulation operating mode, or one or more new emulation models may be added and selected among them. A particular type of ICE vehicle may be added to the emulation operating mode either as part of a group of emulation vehicle types or individually (e.g., upon request).

[0027] In some implementations, a manufacturer of EV powertrain components may offer the emulation mode of operation as, among other things, a product or service, for example, the emulation mode of operation may be sold (e.g., licensed for conditional use) with an EV drive unit and / or EV battery pack that the manufacturer makes available for purchase.

[0028] For vehicle manufacturers, the present subject matter may facilitate an easier transition to modern and more sustainable products. Some vehicle manufacturers are well known for their traditions in ICE vehicles and have built up a loyal and devoted customer base that remains faithful to their vehicle types and their particular performance, look, and sound. When such traditional manufacturers contemplate adding EVs to their product lineup, they may at times be concerned that these loyal customers may feel uneasy or unfamiliar with the significantly different experience of driving an EV. However, the present subject matter may offer such potential EV manufacturers the option of offering an emulated version of their traditional ICE vehicle as part of a newly introduced EV. Thus, an automobile enthusiast who is committed to the traditional ICE vehicles of company "X" may now be offered the purchase of a newly introduced EV from company "X" that retains the feel, and optionally the look or sound, of the company's traditional ICE vehicles. Many of today's ICE performance vehicles already provide artificial and / or enhanced motor sounds in the passenger cabin, so the use of ICE-emulated sounds in an EV may be readily accepted by such car enthusiasts. In addition to catering to the brand loyalty of their existing customers, the emulation mode of operation may enable traditional ICE vehicle manufacturers to profile their EVs against the EVs of other companies.

[0029] In some implementations, if a particular type of commercially available ICE vehicle is not readily available for testing, the present subject matter may enable a prospective purchaser of an ICE vehicle to "test drive" its performance and get a feel for its driving characteristics. In such a scenario, an EV equipped with an emulation mode of operation may serve to emulate a multitude of ICE vehicles, thereby offering unparalleled flexibility to test and compare an essentially limitless number of possibilities.

[0030] The emulation of an ICE vehicle is not limited to its acceleration or other powertrain characteristics. In some implementations, any of a number of visual and / or auditory aspects of an ICE vehicle may be emulated. Such aspects may include, but are not limited to, the appearance of the instrument cluster, the sounds of the ICE, or any other (non-motor) sounds produced by an ICE vehicle.

[0031] Implementations of the present subject matter may include advantages including, for example, but not limited to: EVs may be provided with unique value for car enthusiasts who may have previously preferred ICE vehicles; EV manufacturers may be provided with a post-sales revenue stream by installing emulation operating modes and / or adding new ICE vehicle types to be emulated; EV manufacturers may secure the opportunity to offer exclusive incentives to certain customers (e.g., as loyalty programs); EV manufacturers may provide their EVs with tactile and exciting features that are easily marketable; EVs may be provided with flexible and tailored "personalities."

[0032] Examples herein refer to vehicles. A vehicle is a machine that transports passengers or cargo, or both. A vehicle may have one or more motors that use at least one type of fuel, or other energy source (e.g., electricity). As used herein, an EV is a vehicle that does not have an ICE used for the propulsion of the EV. Examples of vehicles include, but are not limited to, automobiles, trucks, buses, rail vehicles, or non-road vehicles (e.g., aircraft). The number of wheels may vary among multiple types of vehicles, and one or more (e.g., all) of the wheels may be used for the propulsion of the vehicle. A vehicle may include a passenger compartment that accommodates one or more people. At least one vehicle occupant may be considered a driver; in this case, various tools, implements, or other devices may be provided to the driver. In the examples herein, any person carried by a vehicle may be referred to as a "driver" or "passenger" of the vehicle, regardless of whether the person is driving the vehicle, whether the person has access to the controls to drive the vehicle, or whether the person lacks the controls to drive the vehicle.

[0033] Examples herein refer to display devices. A display device visually outputs a graphical user interface for one or more computing devices. A display device may operate according to any of a number of display technologies used to present computer-based information. A display device may include a liquid crystal display (LCD), a light-emitting diode (LED) display, and / or a plasma display, just to name a few. A display device may be configured to receive input for a computing device. In some implementations, a display device may comprise one or more types of technology for detecting contact with or proximity to a screen by a user's hand or an instrument such as a stylus. A display device may operate according to any of a number of touch detection or gesture recognition technologies. A display device may include a resistive touch screen, a capacitive touch screen, and / or a touch screen based on optical imaging, just to name a few. A display device may have any of a number of shapes. In some implementations, a display device has a quadrilateral shape (e.g., rectangular) or a non-polygonal shape, just to name a few. A display device may have a substantially flat form factor (e.g., the screen is essentially flat) or may have a non-flat form factor (e.g., the screen is curved according to one or more radii).

[0034] 1 illustrates an example of an emulation controller 100 that may be used with an EV. The emulation controller 100 may be used in combination with one or more other examples described elsewhere herein. The emulation controller 100 is a selection control that may generate one or more screens on a display device with which a user (e.g., a driver of the EV) may interact. For example, the display device on which the emulation controller 100 is displayed may be provided by a mobile electronic device (e.g., a smartphone) or by the EV's instrument panel.

[0035] The emulation controller 100 allows a user to select one of a number of vehicle types having an ICE for emulation, where ICE selections 102 are provided for the user to choose from. In some implementations, the ICE selections 102 may include a number of types of ICEs intended for land use (e.g., on-road or off-road), where the ICE vehicle types for land use are represented by ICE vehicle selections 102-1, 102-2, ..., 102-k shown, where k is any integer. For example, each of the ICE vehicle selections 102-1, 102-2, ..., 102-k may be associated with one or more of a model year, manufacturer name (e.g., brand), model name, trim level, or edition identifier.

[0036] In some implementations, ICE selection 102 may include multiple types of ICEs intended for track use (e.g., off-highway vehicles), where the ICE vehicle types for track use are represented by ICE vehicle selection 102-m, where m represents one or more distinct options. For example, ICE vehicle selection 102-m may correspond to having an EV emulate a track vehicle, including, but not limited to, a race car, a rally car, an oval stock car, or an endurance racing car.

[0037] In some implementations, ICE selection 102 may include multiple types of ICEs intended for off-road use (e.g., air or sea vehicles), where the ICE vehicle types for off-road use are represented by ICE vehicle selection 102-n, where n represents one or more distinct options. For example, ICE vehicle selection 102-n may correspond to having an EV emulate a non-road vehicle, including, but not limited to, an aircraft or a watercraft.

[0038] Other approaches may be presented in addition or instead. For example, the emulation controller 100 may provide control 104 to make additional selections available.

[0039] The emulation controller 100 can cause the EV to emulate the acceleration of an ICE vehicle type selected by the user when activating the emulation mode of operation. In doing so, the emulation controller 100 can limit the emulated acceleration by the acceleration the EV would have if the emulation mode of operation was inactive. For example, the limiting can be performed constantly during the emulation, or the limiting can be performed only once or multiple times, such as only if the emulation meets one or more criteria (including but not limited to exceeding an upper limit).

[0040] The emulation controller 100 may emulate one or more aspects of an instrument cluster of a selected ICE vehicle type. In some implementations, the EV may have a display 106 (e.g., mounted on the EV's instrument panel). The display 106 may include one or more separate display devices. In some implementations, one or more of the content 108A-108C may be displayed on the display 106 during an emulation mode of operation. One or more of the content 108A, content 108B, or content 108C may visually resemble a dial, gauge, meter, or other instrument on an ICE vehicle type dashboard. For example, the appearance of a particular needle, faceplate, and / or bezel of a conventional instrument may be emulated in an operational manner. For example, the content 108A may display a speedometer, the content 108B may display a pressure gauge, and the content 108C may display a tachometer. Other approaches may be explored.

[0041] 2 shows an example of an instrument panel 200 for an EV 202. The EV 202 is largely omitted in this illustration for simplicity. The EV 202 includes a steering wheel 204 (shown here in phantom for clarity), which may be used in conjunction with or independent of one or more controls or functions available in the instrument panel 200. The instrument panel 200 may be used in combination with one or more other examples described elsewhere herein.

[0042] The instrument panel 200 may be used to emulate one or more aspects of an ICE vehicle. In some implementations, the instrument panel 200 may emulate an instrument cluster of a selected vehicle type having an ICE. The emulation may be performed by displaying an image of the instrument cluster on a display device of the instrument panel 200. For example, this may enable the display of one or more relevant metrics to the driver of the EV.

[0043] The instrument panel 200 includes a display device 206, which is here positioned somewhat to the left of the steering wheel 204. The instrument panel 200 includes a display device 208, which is here positioned essentially behind the steering wheel 204. The instrument panel 200 includes a display device 210, which is here positioned somewhat to the right of the steering wheel 204. The display device 210 may be horizontally aligned with an instrument cluster of the vehicle 202. For example, the instrument cluster may include at least the display device 208. The instrument panel 200 includes a display device 212, which is here positioned lower (e.g., essentially vertically below) than the display device 210. The display device 212 is considered to be positioned within the instrument panel 200. For example, the display device 212 may be positioned lower within the same physical housing in which the display devices 206, 208, and 210 are mounted. Display of the emulations (eg, visual representations) shown or referred to herein may occur on one or more of display devices 206 , 208 , 210 , or 212 .

[0044] The emulation mode of operation may be managed using one or more hardware controls within EV 202. First, an EV driver may use an accelerator pedal (not shown) to generate an input that controls the acceleration (e.g., emulated acceleration) of the EV. Second, one or more other aspects of the emulation mode of operation may be controlled by applying an input generated using a hardware control. For example, a gear shift request may be made using a hardware control. Based on such input, the acceleration of the emulation mode of operation may be adjusted.

[0045] In some implementations, the instrument panel 200 may include one or more buttons, paddles, toggles, scroll wheels, or other physical control devices by which the driver may make at least one input. Here, a hardware control 214 on the instrument panel 200 is represented generally. The hardware control 214 may be located at any of a number of locations on the instrument panel 200 reachable by the driver of the EV 202. In some implementations, the steering wheel 204 may include one or more buttons, paddles, toggles, scroll wheels, or other physical control devices by which the driver may make at least one input. Here, hardware controls (HWC) 216 and 218 on the steering wheel 204 are represented generally. In some implementations, one or more of the hardware controls 214, 216, or 218 may be used to make an input (e.g., a gear shift request or a selection of an emulation vehicle type), and the emulation operating mode may be controlled based on the input. One or more of hardware controls 214, 216, or 218 may be standard equipment of EV 202 that is reused to generate emulation inputs while the emulation mode of operation is active. One or more of hardware controls 214, 216, or 218 may be optional equipment (e.g., retrofit devices) installed in EV 202 to generate emulation inputs while the emulation mode of operation is active.

[0046] FIG. 3 shows a diagram 300 of EV acceleration capabilities, which encompasses the acceleration capabilities of ICE vehicles. The example diagram 300 may be used in combination with one or more other examples described elsewhere herein. In diagram 300, the acceleration capabilities of different vehicle types may be represented by visualizing the high performance envelope of each vehicle type. In diagram 300, the vertical axis shows the longitudinal acceleration of the vehicle (measured in any applicable units, e.g., in terms of the number of g's, which is a common value of the acceleration of gravity). On the vertical axis, a point of zero acceleration is marked. The horizontal axis shows the speed of the vehicle (measured in any applicable units). Thus, diagram 300 may show the available longitudinal acceleration as a function of speed.

[0047] Diagram 300 includes a graph 302 corresponding to a high-performance EV, a graph 304 corresponding to a mid-size ICE vehicle, sometimes classified as a "pony car," and a graph 306 corresponding to a light-duty ICE vehicle, which may be referred to as a roadster sports car. For example, the high-performance EV (graph 302) may have multiple electric motors (e.g., permanent magnet motors) and may weigh more than 5,000 pounds (2,268 kilograms); the pony car (graph 304) may have a V8 engine and may weigh approximately 3,700 pounds (1,678 kilograms); and the roadster (graph 306) may have a four-cylinder engine and may weigh approximately 2,300 pounds (1,043 kilograms).

[0048] The portions of graphs 302-306 above zero acceleration represent the ability of each powertrain to accelerate the corresponding vehicle. The performance EV (graph 302) significantly exceeds the acceleration capabilities of the roadster (graph 306) at any speed, and similarly exceeds the acceleration capabilities of the pony car (graph 304) at all speeds except for the top speed (e.g., the performance EV may have an electronically limited maximum speed).

[0049] The portions of graphs 302-306 below zero acceleration represent the ability of each powertrain to decelerate the corresponding vehicle. For a performance EV, negative acceleration may occur when the accelerator pedal is released due to regenerative braking, where kinetic energy from the electric motor is converted to electricity, which charges the on-board battery. For a pony car and roadster, negative acceleration may occur when the gas pedal is released due to engine braking, where a vacuum is created inside the ICE that robs kinetic energy from the moving cylinders. The performance EV (graph 302) exceeds the deceleration capabilities of the roadster (graph 306) at all speeds, and similarly exceeds the deceleration capabilities of the pony car (graph 304), except at top speed.

[0050] In some implementations, the emulation algorithm may correspond to a scaled replay of acceleration versus speed. For example, such a scaled replay may operate based on one or more of graphs 302-306 to provide the EV with a corresponding acceleration. For each of graphs 302-306, diagram 300 may show one or more points 308 where the slope of the acceleration curve changes significantly. For a vehicle with a multi-speed transmission, points 308 may correspond to gear shifts. If the high-performance EV in this example had a single-speed transmission, points 308 in graph 302 may instead correspond to boundaries between different operating intervals of its powertrain (e.g., coordinated by a power electronics controller).

[0051] The emulation may be of a transient nature. In some implementations, the target acceleration of the EV may be a transient function. For example, a particular input from the driver may trigger the EV to provide an acceleration that is a transient response to the input, including but not limited to, which may be followed after a certain amount of time by a steady state response. An example is now described with reference to Scenario A and Scenario B according to the respective tables below. [Table 1]

[0052] In Scenario A above, the driver applies a relatively small accelerator input at T-1 seconds, and values ​​for some of the characteristics are shown.

[0053] At time T, the driver exerts maximum pedal input (accelerator to the floor). At time T, the EV maintains a speed of 100 km / h, the emulated automatic transmission begins to downshift into third gear, and the emulated turbocharger accelerates. At time T, the axle torque output can be highly variable to emulate the feeling of a downshift.

[0054] At time T+1 seconds, the driver maintains full throttle, the turbocharger accelerates, and the EV travels at 5 m / s 2 During the definition of the emulated acceleration target, some of the characteristics are numerically increased.

[0055] At time T+2 seconds, the driver maintains full throttle and some of the characteristics increase numerically while the turbocharger reaches full speed. [Table 2]

[0056] In Scenario B above, the driver launches from a standstill at full throttle at time T, and values ​​for several of the characteristics are given.

[0057] At time T+5 seconds, the driver maintains full throttle and due to recent history, some of the characteristics increase numerically, including the fact that the emulated turbocharger is already at full speed.

[0058] In both Scenario A and Scenario B above, the EV reaches 102 km / h with full throttle applied. Due to the modeled turbo lag that affects Scenario A, the resulting torque differs from each other. Transient emulation, of which Scenario A and Scenario B are examples, can have an impact on the reproduction of the driver experience, including but not limited to emulating a turbocharged car. An algorithm that provides emulation of a transient nature can allow an EV driver to feel the emulated turbo lag as boost builds, for example, when the driver is increasing the throttle amount as the driver exits a corner. This example shows a significantly deeper level of immersion than emulating full throttle straight line acceleration.

[0059] That is, diagram 300 shows that the acceleration performance of an EV generally encompasses that of these ICE vehicles (pony cars and roadsters). As such, a high performance EV may emulate the acceleration of either of them by applying acceleration reduction to its native acceleration capabilities. For example, the acceleration reduction may correspond to the difference between graph 302 and either graph 304 or graph 306 at essentially any speed.

[0060] FIG. 4 illustrates generally an example block diagram of an EV 400. Some aspects of the EV 400 are omitted for brevity. The EV 400 may be used in combination with one or more other examples described elsewhere herein. The EV 400 includes an accelerator pedal 402 that the driver can depress or release to place it in any of a range of positions (e.g., positions expressed as a percentage of a fully depressed position) indicated generally by an arrow 404. In some implementations, the EV 400 emulates the acceleration of one or more ICE vehicle types based at least in part on the current position of the accelerator pedal 402.

[0061] The EV 400 includes an emulation component 406 that allows the EV driver to choose and select among any of a plurality of vehicle types having an ICE, and causes the EV 400 to emulate at least the acceleration of the selected vehicle type. The emulation component 406 may receive an input 408 generated by a user to make a selection (e.g., using the emulation controller 100 of FIG. 1). An input 410 to the emulation component 406 may be generated based on a current position of the accelerator pedal 402. The emulation component 406 may apply the input 410 to a model 412 that corresponds to the vehicle type selected by the input 408. The emulation component 406 may output an acceleration value 414 based on the model 412 and the input 410. The acceleration value 414 represents the acceleration that the model 412 specifies for the EV 400 in the current situation. For example, the acceleration value 414 may be essentially any value of the graph 304 (pony car) or the graph 306 (roadster) in FIG. 3.

[0062] Model 412 may calculate the emulation of an ICE vehicle in any of a number of different ways. Model 412 may take inputs such as accelerator pedal position, gear selection, and reactive load, and output calculated torque and resulting acceleration values. In some implementations, model 412 scales pedal inputs (e.g., accelerator pedal position) as a function of speed (e.g., based on graph 304 or graph 306 in FIG. 3). If the EV driver depresses accelerator pedal 402 by x%, model 412 may output an acceleration value corresponding to the acceleration that the emulated ICE vehicle would experience if it were in the applicable gear of its transmission and had its accelerator pedal depressed by x%. For example, if the accelerator pedal is at 50%, this may correspond to an acceleration of 0.7g in the EV 400 with the emulation operating mode inactive, and 0.4g in the emulated ICE vehicle at 50% throttle.

[0063] In some implementations, model 412 may take into account the physical characteristics of the ICE powertrain. Such aspects may include, but are not limited to, rotational inertia (e.g., the effect of the individual moments of inertia of the wheels, tires, drive shafts, or other rotating components), transmission gear shifting, turbocharger rotational speed, boost control devices (e.g., controlling air pressure affecting a turbocharger or supercharger), anti-lag systems (e.g., controlling ignition timing to reduce turbo lag), launch control devices (e.g., using computer-controlled electronic accelerators to provide optimized acceleration), or blow-off valves (e.g., compressor bypass valves that vent to atmosphere).

[0064] The EV 400 may also provide input 410 to a torque controller 416. The torque controller may be a standard component of an EV powertrain that is not specific to the emulation mode of operation. For example, if the emulation mode of operation is not active in the EV 400, the input 410 provided to the torque controller 416 may cause the EV 400 to operate its powertrain in a particular manner in response to the current position of the accelerator pedal 402. The torque controller 416 generates an output that includes an acceleration value 418. That is, the acceleration value 418 represents the acceleration that the EV 400 may have if the emulation mode of operation is inactive.

[0065] EV 400 includes an emulation controller 420 that can limit the emulated acceleration at an acceleration specified by torque controller 416. In some implementations, emulation controller 420 receives acceleration value 414 from emulation component 406 and acceleration value 418 from torque controller 416. For example, emulation controller 420 generates an output 422 that corresponds to the smaller of acceleration value 414 or acceleration value 418.

[0066] EV 400 may provide output 422 to powertrain 424. In some implementations, powertrain 424 includes one or more electric motors (e.g., induction or permanent magnet based) and associated power electronics and control circuitry. Powertrain 424 generates acceleration for EV 400 based on output 422, as represented diagrammatically by arrow 425. This example illustrates emulating the acceleration of an ICE vehicle type without exceeding the associated acceleration of EV 400 (i.e., by limiting acceleration value 414 by acceleration value 418).

[0067] The emulation component 406 may generate an output 426 using the model 412. The output 426 may correspond to one or more aspects of the emulation other than the acceleration of the EV 400. In some implementations, the output 426 includes at least one image emulating an instrument cluster of an ICE vehicle. For example, a video or another animation may be generated showing one or more gauges or dials of the ICE vehicle. In some implementations, the output 426 includes an audio emulating a characteristic of an ICE vehicle. For example, a motor sound or a non-motor sound may be generated. The EV 400 includes vehicle electronics 428 that receives the output 426 and generates an output 430 perceptible by at least a driver of the EV 400. For example, if the output 426 includes an image, the vehicle electronics 428 may include a display device and the output 430 may include the visual appearance of the emulated instrument cluster. As another example, if output 426 includes audio, vehicle electronics 428 may include a speaker and output 430 may include an audible reproduction of one or more sounds.

[0068] The examples described above illustrate that an EV (e.g., EV 400 in FIG. 4 ) may include a selection control (e.g., emulation controller 100 in FIG. 1 ) for receiving a user selection of a first vehicle type from among a plurality of vehicle types each having an ICE. The user selection is made for an emulation mode of operation of the EV (e.g., activated by input 408 in FIG. 4 ). The EV may include an accelerator pedal (e.g., accelerator pedal 402 in FIG. 4 ) for generating a first input (e.g., input 410 in FIG. 4 ) made by a driver of the EV with the first vehicle type selected for the emulation mode of operation. The first input is associated with a first acceleration (e.g., acceleration value 418 determined by torque controller 416 in FIG. 4 ) of the EV with the emulation mode of operation inactive. The EV may include a model (e.g., model 412 in FIG. 4 ) for providing the EV with a second acceleration (e.g., corresponding to output 422 in FIG. 4 ) determined based on the first vehicle type and input while the emulation mode of operation is active and using the EV's powertrain (e.g., powertrain 424 in FIG. 4 ). The second acceleration is limited by the first acceleration (e.g., with emulation controller 420 in FIG. 4 ).

[0069] 5 illustrates generally an example block diagram of a model 500 for emulating at least the acceleration of an ICE vehicle. The model 500 may be employed to emulate the acceleration of a selected ICE vehicle type without exceeding the associated acceleration of an EV with an EV powertrain having an activated emulation mode of operation. The model 500 may be used in combination with one or more other examples described elsewhere herein. The model 500 is configured to receive one or more inputs 502. For example, the inputs 502 may include pedal inputs, gear shift requests, or vehicle state information.

[0070] Model 500 may include one or more state variables 504. State variables 504 may be assigned values ​​(e.g., numeric or Boolean) depending on inputs 502. The values ​​of state variables 504 represent dynamic or static characteristics of the ICE vehicle being emulated. Such characteristics may include, but are not limited to, engine speed (e.g., measured in RPM), turbo speed (e.g., measured in RPM), boost pressure, intake air temperature (e.g., temperature of air entering the ICE), barometric pressure (e.g., modeled based on the altitude of the EV's current location), transmission gear selection (e.g., affecting available acceleration according to graph 304 or graph 306 in FIG. 3 ).

[0071] Model 500 may be configured to represent one or more modeled characteristics of the ICE vehicle with which model 500 is associated. The modeled characteristics may be used to ensure that the EV emulates the feel of a selected ICE vehicle. Such characteristics may include, but are not limited to, component inertia, vehicle mass, volumetric efficiency (e.g., the ratio of mass density of the air-fuel mixture in a cylinder to the mass density of the same volume of air in the intake), plenum volume (e.g., of an intake manifold), sound (e.g., sound of the ICE, transmission, or any other audibly perceptible vehicle component), drive-related metrics or other signals (e.g., vehicle speed, ICE RPM, ICE temperature, ICE gear selection, ICE air pressure, ICE oil pressure, ICE coolant temperature, turn signals, or ICE fuel level).

[0072] Model 500 is configured to generate one or more outputs 506. Outputs 506 may control one or more aspects of the EV to emulate the acceleration and optionally other aspects of a selected ICE vehicle type. Such outputs 506 may include, but are not limited to, an ICE vehicle-based longitudinal acceleration target, an ICE vehicle sound, or an ICE vehicle instrument cluster display.

[0073] 6 shows an example of a vehicle audio system 600 that may emulate the sound of an ICE vehicle. The vehicle audio system 600 may be used with one or more other examples described elsewhere herein. The vehicle audio system 600 may be implemented within an EV 602 using some or all of the examples described below with reference to FIG.

[0074] The vehicle sound system 600 includes a model 604 that may represent at least the sounds of one or more ICE vehicles. If multiple ICE vehicles are represented, the user may select any of them for emulation. The model 604 may include at least one motor sound 606. In some implementations, the motor sound 606 represents the sound of the ICE powertrain (e.g., as perceived inside the passenger cabin of the ICE) at any of a number of different speeds or idle, ICE RPM, gear selection, etc. The motor sound 606 may include combustion noises (e.g., exhaust sounds or engine backfire), mechanical sounds (e.g., intake noises, transmission noises, or piston smacking), or combinations thereof.

[0075] The model 604 may include at least one non-motor sound 608. In some implementations, the non-motor sound 608 may relate to any aurally perceptible aspect of the modeled ICE vehicle other than its powertrain. Such aurally perceptible aspects may include, but are not limited to, any of the following: a vehicle horn or other signaling mechanism such as a bell, a turn signal, a fan sound, the sound of pulling or releasing a parking brake lever, the sound of a windshield wiper, the sound of a manually turning window handle, the sound of a door lock, brake-related sounds (e.g., the squeal of a disc or drum brake, or the release of air from a hydraulic brake system), wheel sounds (e.g., of a particular tire type, or of the metal wheels of a locomotive or another vehicle against a rail), or scraping sounds (e.g., from a vehicle moving through air or from a vessel moving through water).

[0076] To create the model 604, either motor sounds 606 or non-motor sounds 608 may be recorded, either by sampling actual instances of the ICE vehicle being modeled, or by synthesizing actual sounds. For example, data may be collected using binaural microphones and head models within the ICE vehicle to create the motor sounds 606 in a spatially accurate manner. The motor sounds 606 and / or non-motor sounds 608 may be rendered in a three-dimensional (3D) space around the driver to realistically emulate the direction from which sounds would naturally arrive to the driver. For example, exhaust noise may be modeled to arrive approximately from the direction that the exhaust pipe terminates on the modeled ICE vehicle. As another example, the sound of a turbocharger or supercharger may arrive from its general location on the ICE.

[0077] The sound of the model 604 may be rendered in one or more channels in EV 602 (e.g., as 3D or "surround" sound, optionally with a height dimension). Any number of channels may be used.

[0078] The vehicle audio system 600 may include an audio processor 610 that may receive or obtain any or all of the motor sounds 606 or non-motor sounds 608 from the model 604. The audio processor 610 may include a renderer that may be used when playing audio content that has not yet been rendered. In some implementations, the renderer may mix sounds into one or more of the available channels. For example, the renderer may pan sounds between different channels.

[0079] The audio processor 610 includes an emulator 612 that can provide audio content of the motor sounds 606 or non-motor sounds 608 to one or more speakers for playback. The emulator 612 may be engaged when an emulation mode of operation is active and may not be engaged otherwise. The EV 602 includes speakers for playing audio including, but not limited to, the motor sounds 606 or non-motor sounds 608. One or more types of speaker types may be used including, but not limited to, tweeter speakers, mid-range speakers, full-range speakers, and / or woofers. Each speaker (type) may include one or more transducers (e.g., voice coils) for converting electrical input into sound waves. The EV 602 may include n number of tweeter speakers 614 that may have any of several arrangements within the EV 602. The EV 602 may include m number of mid-range speakers 616 that may have any of several arrangements within the EV 602. The EV 602 may include a number p of full-range speakers 618 (sometimes referred to as twiddler speakers) that may have any of a number of arrangements within the EV 602. The EV 602 may include a number q of woofers 620 (e.g., subwoofers) that may have any of a number of arrangements within the EV 602. Other approaches may be used.

[0080] 7 illustrates an example of a method 700. Method 700 may be used with one or more other examples described elsewhere herein. More or fewer operations may be performed. Two or more operations may be performed in different orders unless otherwise indicated.

[0081] At operation 702, method 700 may include an EV (e.g., EV 400 in FIG. 4) receiving a user selection of a first vehicle type from among a plurality of vehicle types (e.g., emulation controller 100 in FIG. 1), each having an ICE. The user selection is made with respect to an emulation mode of operation of the EV (e.g., activated by input 408 in FIG. 4).

[0082] At operation 704, method 700 may include the EV receiving a first input (e.g., input 410 in FIG. 4 ) made by a driver using an accelerator pedal of the EV with the first vehicle type selected for the emulation mode of operation. The first input is associated with a first acceleration of the EV with the emulation mode of operation inactive (e.g., acceleration value 418 determined by torque controller 416 in FIG. 4 ).

[0083] At operation 706, in response to the input and while the emulation mode of operation is active, the method may include providing a second acceleration rate (e.g., corresponding to output 422 in FIG. 4) to the EV determined based on the first vehicle type and the input. The second acceleration rate is limited by the first acceleration rate (e.g., with emulation controller 420 in FIG. 4). For example, the sound of an ICE may also be emulated.

[0084] At operation 708, method 700 may include receiving another input. In some implementations, the other input may be generated using a hardware controller of the EV. For example, the other input may represent a gear shift request, a configuration of the ICE powertrain (e.g., engagement or disengagement of components), or the use of any other component within the EV that may be associated with a visual output or sound.

[0085] At operation 710, method 700 may include emulating another aspect of the ICE vehicle. In some implementations, the emulation may be performed in response to the input at operation 708. For example, if the EV driver switches to a different modeled ICE powertrain or reconfigures the modeled ICE powertrain, the emulation at operation 710 may take into account the change.

[0086] 8 illustrates an example of a system 800 that may perform emulation in an EV. System 800 may be used with one or more other examples described elsewhere herein. System 800 includes a driver input 802. In some implementations, driver input 802 is generated by a driver using one or more hardware controls of the EV. For example, driver input 802 may be generated using one or more of an accelerator pedal, brake pedal, clutch pedal, gear shifter / selector, knob, wheel, button, lever, crank, pull, control stalk, paddle, toggle, scroll wheel, or other physical control device.

[0087] System 800 includes vehicle state 804. In some implementations, vehicle state 804 includes information (e.g., digital information represented in electronic form as one or more signals) representative of one or more aspects of a current state of the EV. For example, vehicle state 804 may include or be based on outputs of one or more components (e.g., a motor, a gearbox, an electronic control unit, or a sensor) that correspond to one or more aspects of a current characteristic of the EV.

[0088] Driver inputs 802 and vehicle conditions 804 may be input to a model 806. In some implementations, model 806 may include hardware and / or software, or may be designed or configured to emulate one or more aspects of another vehicle within the EV in which system 800 is currently being used.

[0089] The model 806 may generate one or more outputs based on the driver inputs 802 and the vehicle states 804. In some implementations, the model 806 may generate a torque demand 808 that corresponds to an emulation of the acceleration of another vehicle. The torque demand 808 may be subject to a safety check 810. The safety check 810 may ensure that the emulated acceleration of the EV is limited by the acceleration that the EV would experience in this situation if the emulation mode of operation was inactive. For example, the EV may have an inactive emulation mode of operation and, in a current situation where the driver inputs 802 and vehicle states 804 are otherwise the same, may require a maximum acceleration of at most 10 ... 2 The emulated acceleration is then currently calculated as am / s to avoid exposing the driver to greater acceleration than the EV would otherwise provide. 2 may be limited to.

[0090] In some implementations, model 806 may generate output 812 for one or more gauges or other output devices. Output 812 may include information that affects the operation of one or more components of the EV whose function may be perceptible as an emulation by the driver. For example, output 812 may affect the display on one or more display devices of the EV.

[0091] In some implementations, model 806 may generate sound 814. Sound 814 may include digital and / or analog audio signals for at least one speaker in the EV whose output may be perceptible by the driver as an emulation. For example, the sound of a combustion engine powertrain may be emulated.

[0092] FIG. 9 illustrates an example architecture 900 for performing emulation in an EV. The architecture 900 may be used with one or more other examples described elsewhere herein. The architecture 900 may include an accelerator pedal input 902 generated by a driver using an accelerator pedal of the EV. The architecture 900 may include a motor speed input 904 reflecting a speed of one or more electric motors of the EV. The architecture 900 may include a driver input 906. In some implementations, the driver input 906 may reflect whether an emulation operating mode is currently active or inactive. In some implementations, the driver input 906 may reflect an operating mode of the EV, including, but not limited to, an operating mode of the EV powertrain. In some implementations, the driver input 906 may reflect a gear selection by the driver. Other driver inputs, selections, selections, settings, activations, or deactivations may additionally or alternatively be reflected by the driver input 906.

[0093] An accelerator pedal input 902, a motor speed input 904, and / or a driver input 906 may be received at a processing component 908 (e.g., implemented with a processor and at least one memory or other computer-readable storage) of the EV. The processing component 908 may use one or more of the accelerator pedal input 902, the motor speed input 904, and / or the driver input 906 to provide an emulation of another vehicle. For example, the processing component 908 may include a vehicle control unit 910 implemented in the form of one or more processors and capable of controlling one or more aspects of the functionality of the EV. In some implementations, the processing component 908 includes a physics simulator 912. The physics simulator 912 may include hardware and / or software and may be designed or configured to simulate one or more physical characteristics or conditions based on some or all parameters currently known by the processing component 908. The physics simulator 912 may model the performance characteristics of the emulated vehicle for the purpose of controlling the EV to emulate its behavior. For example, acceleration and / or other dynamics may be modeled. The physics simulator 912 may utilize one or more parameters of the model parameters 914 in performing its simulation.

[0094] The physical simulator 912 may generate model outputs 916 based on the simulation. The model outputs 916 may include one or more values, states, characteristics, symbols, or other information that reflect aspects or characteristics of the emulated vehicle. The model outputs 916 may reflect, but are not limited to, one or more of motor RPM (e.g., for each of the multiple drive units), instantaneous air pressure, gear selection, turbine pressure / speed, vehicle acceleration, or motor torque.

[0095] The processing component 908 may generate one or more outputs based on the physics simulator 912. In some implementations, the output may include a sound emulation 918a provided to one or more speakers of the EV. For example, the sound emulation 918a may emulate the sound of an ICE powertrain under current operating conditions (e.g., speed, acceleration, gear selection). The sound emulation 918a may be provided to an audio system 918b (e.g., a multi-channel surround sound system capable of reproducing three-dimensionally localized sound). The audio system 918b may output sound based on the sound emulation 918a on one or more individual units of speakers 918c within the EV.

[0096] In some implementations, the output may include an instrument display emulation 920. For example, the instrument display emulation 920 may include at least one image (e.g., a video stream) that emulates one or more aspects of an instrument panel of the vehicle being emulated.

[0097] In some implementations, the output may include a motor control signal 922 for a motor of the EV. For example, the motor control signal 922 may include respective signals configured for two or more electric motors of the EV (e.g., a front drive unit (FDU) and / or a rear drive unit (RDU)).

[0098] 10 illustrates a schematic of a torque crossover emulation. Axis 1000 represents the position of an EV accelerator pedal (e.g., controlled by the driver's foot). The features of axis 1000 may be used with one or more other examples described elsewhere herein. Axis 1000 may represent accelerator pedal input using a suitable metric, such as current pedal position relative to maximum pedal input. For example, no pedal input (i.e., 0% of maximum pedal input) may correspond to a position at the top end of axis 1000, and full pedal input (i.e., 100% of maximum pedal input) may correspond to a position at the bottom end of axis 1000.

[0099] The availability of regenerative braking in an EV may be reflected by axis 1000. In an EV traveling at high speed, an accelerator pedal position greater than a certain value may correspond to positive torque, and an accelerator pedal position less than a certain value may correspond to regenerative braking. An EV torque crossover 1002 is shown here diagrammatically, associated with a pedal input greater than 0% and less than 100% of a maximum value. A portion 1000A of axis 1000 corresponding to a pedal input greater than EV torque crossover 1002 is shown, and a portion 1000B of axis 1000 corresponding to a pedal input less than EV torque crossover 1002 is also shown. When the EV accelerator pedal position is within portion 1000A, positive acceleration (i.e., positive torque) may occur. When the EV accelerator pedal position is within portion 1000B, regenerative braking (i.e., negative torque) may occur. That is, the torque crosses over between negative and positive at EV torque crossover 1002. When the emulation mode of operation is not active, the position of the EV torque crossover 1002 may vary as a function of the speed of the EV.

[0100] On the other hand, the vehicle being emulated may not have regenerative braking or may have a different torque crossover than an EV. Axis 1004 represents the position of the accelerator pedal of the emulated vehicle. As in the above example, torque crossover 1006 is shown here diagrammatically. Torque crossover 1006 is associated with a pedal input greater than 0% and less than 100% of maximum, but is different from EV torque crossover 1002. A portion 1004A of axis 1004 corresponding to a pedal input greater than torque crossover 1006 is shown, and a portion 1004B of axis 1004 corresponding to a pedal input less than torque crossover 1006 is also shown.

[0101] In an EV with the emulation mode of operation inactive, the pedal position 1008 in the portion 1000B, for example about 5%, is, so to speak, 1 m / s at a particular speed. 2On the emulated powertrain axis 1004, in contrast, pedal position 1008 may correspond to a deceleration of 100 ms. On the emulated powertrain axis 1004, pedal position 1008, in contrast, may correspond to a very small positive acceleration. Thus, whether the acceleration is positive or negative may differ between the emulated powertrain and the EV powertrain, as the case may be. If the EV is configured to limit the emulated acceleration, such a limit may be deactivated or modified under certain circumstances (e.g., based on the magnitude of the emulated acceleration). For example, the limit may be set to 0 if the emulated acceleration exceeds an upper limit value (e.g., 2 m / s 2 ), and / or the restriction may be enforced only if the emulated deceleration is greater than a lower limit (e.g., −3 m / s 2 ) can be executed.

[0102] 11 shows an example of scaling in emulation. This example is illustrated by EV acceleration diagram 1100, in which the vertical axis shows the longitudinal acceleration of the vehicle (measured in any applicable units, e.g., in terms of the number of g's, which is a common value for the acceleration of gravity) and the horizontal axis shows the vehicle's speed (measured in any applicable units). The diagram 300 example may be used in combination with one or more other examples described elsewhere herein.

[0103] Graph 1102 in diagram 1100 here represents the acceleration capability of the emulated vehicle. This acceleration may be greater (or less) than the acceleration capability of the EV that will perform the emulation at each speed in diagram 1100. In some implementations, the EV may perform emulation in one or more of its regions based on the scaling of graph 1102 (e.g., as a calibration performed by a scaling algorithm that is part of the model for the emulated vehicle). For example, here graph 1102A represents a scaled down of graph 1102. Since humans may not be adept at detecting absolute acceleration, scaling down the acceleration of the emulated vehicle can provide the essence of the emulation experience. As another example, here graph 1102B represents a scaled up of graph 1102. Thus, the emulation implementation may include a scaling algorithm that is used to appropriately scale the torque output of the powertrain to match the capabilities of the EV.

[0104] FIG. 12 illustrates an example architecture of a computing device 1200 that may be used to implement aspects of the disclosure, including any of the systems, devices, and / or techniques described herein, or any other systems, devices, and / or techniques that may be utilized in various possible embodiments.

[0105] The computing device illustrated in FIG. 12 may be used to execute the operating system, application programs, and / or software modules (including software engines) described herein.

[0106] In some embodiments, the computing device 1200 includes at least one processing device 1202 (e.g., processor), such as a central processing unit (CPU). A variety of processing devices are available from a variety of manufacturers, e.g., Intel or Advanced Micro Devices. In this example, the computing device 1200 also includes a system memory 1204 and a system bus 1206 that couples various system components including the system memory 1204 to the processing device 1202. The system bus 1206 is one of any number of types of bus structures that may be used, including, but not limited to, a memory bus or memory controller; a peripheral bus; and a local bus using any of a variety of bus architectures.

[0107] Examples of computing devices that may be implemented using computing device 1200 include a desktop computer, a laptop computer, a tablet computer, a mobile computing device (such as a smartphone, touchpad mobile digital device or other mobile device), or other device configured to process digital instructions.

[0108] The system memory 1204 includes a read-only memory 1208 and a random access memory 1210. A basic input / output system 1212, containing the basic routines that act to transfer information within the computing device 1200, such as during start-up, may be stored in the read-only memory 1208.

[0109] In some embodiments, computing device 1200 also includes a secondary storage device 1214, such as a hard disk drive for storing digital data. The secondary storage device 1214 is connected to the system bus 1206 by a secondary storage interface 1216. The secondary storage device 1214 and its associated computer-readable media provide non-volatile and non-transitory storage of computer-readable instructions (including application programs and program modules), data structures, and other data for computing device 1200.

[0110] Although the exemplary environment described herein employs a hard disk drive as a secondary storage device, other embodiments use other types of computer-readable storage media. Examples of these other types of computer-readable storage media include magnetic cassettes, flash memory cards, solid-state drives (SSDs), digital video disks, Bernoulli cartridges, compact disk read-only memories, digital versatile disk read-only memories, random access memories, or read-only memories. Some embodiments include non-transitory media. For example, a computer program product may be tangibly embodied in a non-transitory storage medium. Additionally, such computer-readable storage media may include local storage or cloud-based storage.

[0111] A number of program modules may be stored in secondary storage device 1214 and / or system memory 1204, including an operating system 1218, one or more application programs 1220, other program modules 1222 (such as a software engine described herein), and program data 1224. Computing device 1200 may utilize any suitable operating system.

[0112] In some embodiments, a user provides input to the computing device 1200 through one or more input devices 1226. Examples of input devices 1226 include a keyboard 1228, a mouse 1230, a microphone 1232 (e.g., for voice and / or other audio input), a touch sensor 1234 (such as a touchpad or touch-sensitive display), and a gesture sensor 1235 (e.g., for gesture input). In some implementations, the input devices 1226 provide presence, proximity, and / or motion-based detection. Other embodiments include other input devices 1226. The input devices may be connected to the processing device 1202 through an input / output interface 1236 coupled to the system bus 1206. These input devices 1226 may be connected by any number of input / output interfaces, such as a parallel port, a serial port, a game port, or a universal serial bus. In some contemplated embodiments, wireless communication between the input device(s) 1226 and the input / output interface 1236 may also be possible, including infrared, BLUETOOTH® wireless technology, 802.11a / b / g / n, cellular, ultra-wideband (UWB), ZIGBEE®, or other radio frequency communication systems, to name just a few.

[0113] In this exemplary embodiment, a display device 1238, such as a monitor, liquid crystal display device, light emitting diode display device, projector, or touch-sensitive display device, is also connected to the system bus 1206 via an interface, such as a video adapter 1240. In addition to the display device 1238, computing device 1200 may also include various other peripheral devices (not shown), such as speakers or printers.

[0114] Computing device 1200 may be connected to one or more networks through network interface 1242. Network interface 1242 may provide wired and / or wireless communication. In some implementations, network interface 1242 may include one or more antennas for transmitting and / or receiving wireless signals. When used in a local area networking environment or a wide area networking environment (such as the Internet), network interface 1242 may include an Ethernet interface. Other possible embodiments use other communication devices. For example, some embodiments of computing device 1200 include a modem for communicating across a network.

[0115] Computing device 1200 may include at least some form of computer-readable media. Computer-readable media includes any available media that can be accessed by computing device 1200. By way of example, computer-readable media include computer-readable storage media and computer-readable communication media.

[0116] Computer-readable storage media include volatile and nonvolatile, removable and non-removable media implemented in any device configured to store information, such as computer-readable instructions, data structures, program modules, or other data. Computer-readable storage media include, but are not limited to, random access memory, read-only memory, electrically erasable programmable read-only memory, flash memory, or other memory technology, compact disc read-only memory, digital versatile disk or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and that can be accessed by the computing device 1200.

[0117] Computer-readable communication media typically embodied computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and include any information delivery media. The term "modulated data signal" refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, computer-readable communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency, infrared and other wireless media. Combinations of any of the above are also included within the scope of computer-readable media.

[0118] The computing device illustrated in FIG. 12 is also an example of a programmable electronic apparatus that may include one or more such computing devices, where multiple computing devices are included, such computing devices may be coupled together with a suitable data communications network to collectively perform various functions, methods, or operations disclosed herein.

[0119] In some implementations, the computing device 1200 may be characterized as an ADAS computer. For example, the computing device 1200 may include one or more components that are possibly used to process tasks that arise in the field of artificial intelligence (AI). The computing device 1200 then includes sufficient processing power and necessary support architecture for the demands of ADAS or AI in general. For example, the processing device 1202 may include a multi-core architecture. As another example, the computing device 1200 may include one or more co-processors in addition to or as part of the processing device 1202. In some implementations, at least one hardware accelerator may be coupled to the system bus 1206. For example, a graphics processing unit may be used. In some implementations, the computing device 1200 may implement neural network specific hardware to address one or more ADAS tasks.

[0120] The terms "substantially" and "about" used throughout this specification are used to describe and take into account small variations, such as those due to processing variations. For example, they can refer to less than or equal to ±5%, such as less than or equal to ±2%, such as less than or equal to ±1%, such as less than or equal to ±0.5%, such as less than or equal to ±0.2%, such as less than or equal to ±0.1%, such as less than or equal to ±0.05%. Also, as used herein, indefinite articles such as "a" or "an" mean "at least one".

[0121] It should be understood that all combinations of the above-mentioned concepts, and additional concepts discussed in more detail below (provided that such concepts are not mutually inconsistent), are contemplated as being part of the inventive subject matter disclosed herein. In particular, all combinations of claimed subject matter appearing at the end of this disclosure are contemplated as being part of the inventive subject matter disclosed herein.

[0122] Although several implementations have been described, it will nevertheless be understood that various modifications may be made without departing from the spirit and scope of the specification.

[0123] Additionally, the logic flows depicted in the figures do not require the particular order shown, or sequential order, to achieve desirable results. Additionally, other processes may be provided or processes may be eliminated from the described flows, and other components may be added to or removed from the described systems. Accordingly, other implementations are within the scope of the following claims.

[0124] While certain features of the described implementations have been shown as described herein, many modifications, substitutions, changes, and equivalents will now occur to those skilled in the art. It should therefore be understood that the appended claims are intended to cover all such modifications and changes that fall within the scope of these implementations. It should be understood that they have been presented by way of example only and not by way of limitation, and that various changes in form and details may be made. Any part of the apparatus and / or method described herein may be combined in any combination, except in mutually exclusive combinations. The implementations described herein may include various combinations and / or subcombinations of the functions, components, and / or features of the different implementations described. (Other possible items) (Item 1) receiving, by an electric vehicle (EV), a user selection of a first vehicle type from among a plurality of vehicle types each having an internal combustion engine, the user selection being made with respect to an emulation mode of operation of the EV; receiving, by the EV, a first input made by a driver using an accelerator pedal of the EV with the first vehicle type selected for the emulation mode of operation, the first input being associated with a first acceleration of the EV with the emulation mode of operation inactive; and In response to the first input and while the emulation mode of operation is active, providing the EV with a second acceleration determined based on the first vehicle type and the first input. A computer-implemented method comprising: (Item 2) 2. The computer-implemented method of claim 1, wherein providing the second acceleration to the EV comprises emulating an acceleration of the first vehicle type. (Item 3) 3. The computer-implemented method of claim 2, wherein emulating the acceleration of the first vehicle type comprises applying an acceleration reduction to the EV. (Item 4) 4. The computer-implemented method of any one of claims 2 or 3, wherein emulating the acceleration of the first vehicle type includes taking into account at least one characteristic of the first vehicle type selected from the group consisting of rotational inertia, transmission gear shifting, turbocharger rotational speed, boost control, anti-lag control, launch control, or a blow-off valve. (Item 5) 5. The computer-implemented method of any one of claims 2 to 4, wherein emulating the acceleration of the first vehicle type comprises emulating a gear shift of the first vehicle type. (Item 6) 6. The computer-implemented method of any one of items 2 to 5, wherein emulating the acceleration of the first vehicle type comprises applying at least the first input to a model corresponding to the first vehicle type. (Item 7) 7. The computer-implemented method of any one of items 1 to 6, further comprising emulating an instrument cluster of the first vehicle type on a display device of the EV. (Item 8) 8. The computer-implemented method of any one of items 1 to 7, further comprising emulating a sound of the first vehicle type using a speaker of the EV. (Item 9) 9. The computer-implemented method of claim 8, wherein the sound of the first vehicle type includes a motor sound. (Item 10) 9. The computer-implemented method of claim 8, wherein the sounds of the first vehicle type include non-motor sounds. (Item 11) 11. The computer-implemented method of any one of items 1 to 10, further comprising: receiving a second input at the EV; and applying the second input in emulating the first vehicle type. (Item 12) Item 12. The computer-implemented method of item 11, wherein the second input includes a gear shift request made using a hardware control of the EV, and applying the second input in emulating the first vehicle type includes adjusting the second acceleration based on the second input. (Item 13) Item 13. The computer-implemented method of any one of items 1 to 12, wherein the first vehicle type is a rail vehicle. (Item 14) Item 14. The computer-implemented method of any one of items 1 to 13, wherein the first vehicle type is a non-road vehicle. (Item 15) 15. The computer-implemented method according to any one of claims 1 to 14, further comprising limiting the second acceleration by the first acceleration at least once. (Item 16) Item 16. The computer-implemented method of item 15, wherein the second acceleration is limited by the first acceleration in response to a magnitude of the second acceleration exceeding an upper limit. (Item 17) 17. The computer-implemented method of any one of items 1 to 16, wherein the second acceleration is based on a scaling of an acceleration capability of the first vehicle type. (Item 18) Item 18. The computer-implemented method of any one of items 1 to 17, wherein providing the second acceleration to the EV comprises modifying a torque crossover. (Item 19) An electric vehicle (EV) comprising: a selection control for receiving a user selection of a first vehicle type from among a plurality of vehicle types each having an internal combustion engine, the user selection being made with respect to an emulation mode of operation of the EV; an accelerator pedal for generating a first input made by a driver of the EV with the first vehicle type selected for the emulation mode of operation, the first input being associated with a first acceleration of the EV with the emulation mode of operation inactive; and a model for providing a second acceleration to the EV using a powertrain of the EV while the emulation mode of operation is active, the second acceleration being determined based on the first vehicle type and the first input; An electric vehicle (EV) equipped with: (Item 20) 20. The EV of claim 19, further comprising a display device, wherein the model outputs an image emulating an instrument cluster of the first vehicle type. (Item 21) 21. The EV of any one of items 19 or 20, further comprising a speaker, wherein the model outputs a sound that emulates a sound of the first vehicle type. (Item 22) 22. The EV of any one of items 19 to 21, further comprising a hardware control unit for the driver to make a gear shift request, wherein the model adjusts the second acceleration based on the gear shift request. (Item 23) 23. The EV of any one of items 19 to 22, wherein the model has inputs including accelerator pedal input, gear shift requests, and vehicle states, and the model generates outputs including longitudinal acceleration targets, sounds, and driver metrics. (Item 24) 24. The EV according to any one of items 19 to 23, wherein the second acceleration is limited at least once by the first acceleration. (Item 25) 25. The EV of item 24, wherein the second acceleration is limited by the first acceleration in response to a magnitude of the second acceleration exceeding an upper limit. (Item 26) An electric vehicle (EV) comprising: a selection control for receiving a user selection of a first vehicle type from among a plurality of vehicle types each having an internal combustion engine, the user selection being made with respect to an emulation mode of operation of the EV; Powertrain; and means for emulating an acceleration of the first vehicle type without exceeding an associated acceleration of the EV using the powertrain and while the emulation mode of operation is active; An electric vehicle (EV) equipped with:

Claims

1. receiving, by an electric vehicle (EV), a user selection of a first vehicle type from among a plurality of vehicle types each having an internal combustion engine, the user selection being made with respect to an emulation mode of operation of the EV; receiving, by the EV, a first input made by a driver using an accelerator pedal of the EV with the first vehicle type selected for the emulation mode of operation, the first input being associated with a first acceleration of the EV with the emulation mode of operation inactive; and in response to the first input and while the emulation mode of operation is active, providing the EV with a second acceleration determined based on the first vehicle type and the first input. A computer-implemented method comprising:

2. The computer-implemented method of claim 1 , wherein providing the second acceleration to the EV comprises emulating an acceleration of the first vehicle type.

3. The computer-implemented method of claim 2 , wherein emulating the acceleration of the first vehicle type comprises applying an acceleration reduction to the EV.

4. 3. The computer-implemented method of claim 2, wherein emulating the acceleration of the first vehicle type comprises taking into account at least one characteristic of the first vehicle type selected from the group consisting of rotational inertia, transmission gear shifting, turbocharger rotational speed, boost control, anti-lag control, launch control, or a blow-off valve.

5. The computer-implemented method of claim 2 , wherein emulating the acceleration of the first vehicle type comprises emulating a gear shift of the first vehicle type.

6. The computer-implemented method of claim 2 , wherein emulating the acceleration of the first vehicle type comprises applying at least the first input to a model corresponding to the first vehicle type.

7. The computer-implemented method of claim 1 , further comprising emulating an instrument cluster of the first vehicle type on a display device of the EV.

8. The computer-implemented method of claim 1 , further comprising emulating sounds of the first vehicle type using speakers of the EV.

9. The computer-implemented method of claim 8 , wherein the sounds of the first vehicle type include motor sounds.

10. The computer-implemented method of claim 8 , wherein the sounds of the first vehicle type include non-motor sounds.

11. 2. The computer-implemented method of claim 1, further comprising: receiving a second input at the EV; and applying the second input in emulating the first vehicle type.

12. 12. The computer-implemented method of claim 11, wherein the second input comprises a gear shift request made using a hardware controller of the EV, and applying the second input in emulating the first vehicle type comprises adjusting the second acceleration based on the second input.

13. The computer-implemented method of claim 1 , wherein the first vehicle type is a rail vehicle.

14. The computer-implemented method of claim 1 , wherein the first vehicle type is a non-road vehicle.

15. The computer-implemented method of claim 1 , further comprising limiting the second acceleration at least once by the first acceleration.

16. 16. The computer-implemented method of claim 15, wherein the second acceleration is limited by the first acceleration in response to a magnitude of the second acceleration exceeding an upper limit.

17. The computer-implemented method of any one of claims 1 to 16, wherein the second acceleration is based on a scaling of an acceleration capability of the first vehicle type.

18. The computer-implemented method of any one of claims 1 to 16, wherein providing the second acceleration to the EV comprises modifying a torque crossover.

19. An electric vehicle (EV) comprising: a selection control for receiving a user selection of a first vehicle type from among a plurality of vehicle types each having an internal combustion engine, the user selection being made with respect to an emulation mode of operation of the EV; an accelerator pedal for generating a first input made by a driver of the EV with the first vehicle type selected for the emulation mode of operation, the first input being associated with a first acceleration of the EV with the emulation mode of operation inactive; and a model for providing the EV with a powertrain of the EV while the emulation mode of operation is active, the second acceleration determined based on the first vehicle type and the first input; An electric vehicle (EV) equipped with:

20. 20. The EV of claim 19, further comprising a display device, where the model outputs an image that emulates an instrument cluster of the first vehicle type.

21. 20. The EV of claim 19, further comprising a speaker, wherein the model outputs a sound that emulates a sound of the first vehicle type.

22. 20. The EV of claim 19, further comprising a hardware control for the driver to make a gear shift request, wherein the model adjusts the second acceleration based on the gear shift request.

23. 20. The EV of claim 19, wherein the model has inputs including accelerator pedal input, gear shift requests, and vehicle states, and the model generates outputs including longitudinal acceleration targets, sounds, and driver metrics.

24. The EV according to any one of claims 19 to 23, wherein the second acceleration is limited at least once by the first acceleration.

25. 25. The EV of claim 24, wherein the second acceleration is limited by the first acceleration in response to a magnitude of the second acceleration exceeding an upper limit.

26. An electric vehicle (EV) comprising: a selection control for receiving a user selection of a first vehicle type from among a plurality of vehicle types each having an internal combustion engine, the user selection being made with respect to an emulation mode of operation of the EV; Powertrain; and means for emulating an acceleration of the first vehicle type without exceeding an associated acceleration of the EV using the powertrain and while the emulation mode of operation is active; An electric vehicle (EV) equipped with:

Images