This is machine translation

Translated by Microsoft
Mouseover text to see original. Click the button below to return to the English version of the page.

Note: This page has been translated by MathWorks. Click here to see
To view all translated materials including this page, select Country from the country navigator on the bottom of this page.

Explore the Hybrid Electric Vehicle Input Power-Split Reference Application

The hybrid electric vehicle (HEV) input power-split reference application represents a full HEV model with an internal combustion engine, transmission, battery, motor, generator, and associated powertrain control algorithms. Use the HEV input power-split reference application for HIL testing, tradeoff analysis, and control parameter optimization of a power-split hybrid like the Toyota® Prius®. To create and open a working copy of the HEV input power-split reference application project, enter

By default, the HEV input power-split reference application is configured with:

  • Nickel-metal hydride (NiMH) battery pack

  • Mapped electric motors

  • Mapped spark-ignition (SI) engine

This table summarizes the blocks and subsystems in the reference application. Also indicated are subsystems that contain variants. To implement the model variants, the reference application uses variant subsystems.

Reference Application ElementDescriptionVariants
Drive Cycle Source block

Generates a standard or user-specified drive cycle velocity versus time profile. Block output is the selected or specified vehicle longitudinal speed.

Environment subsystem

Creates environment variables, including road grade, wind velocity, and atmospheric temperature and pressure.

Longitudinal Driver subsystem

Uses the Longitudinal Driver block to generate normalized acceleration and braking commands based on vehicle target and feedback velocities.

Controllers subsystem

Implements a powertrain control module (PCM) containing an input power-split hybrid control module (HCM) and an engine control module (ECM).

Passenger Car subsystem

Implements a hybrid passenger car that contains drivetrain, electric plant, and engine subsystems.

Visualization subsystem

Displays vehicle-level performance, battery state of charge (SOC), fuel economy, and emission results that are useful for powertrain matching and component selection analysis.


Drive Cycle Source

The Drive Cycle Source block generates a target vehicle velocity for a selected or specified drive cycle. The reference application has these options.

Output sample timeDiscrete

Discrete operator commands

Continuous (default)

Continuous operator commands

Longitudinal Driver

The Longitudinal Driver subsystem generates normalized acceleration and braking commands based on the target vehicle velocity. The reference application has these options.

Low-pass filter (LPF)pass (default)

Do not use a filter on velocity error.


Use an LPF on target velocity error for smoother driving.


The Controller subsystem has a PCM containing an input power-split HCM and an ECM. The controller has these variants.

ECMSiEngineController (default)

SI engine controller


CI engine controller

Input power split HCMSeries Regen Brake (default)

Friction braking provides the torque not supplied by regenerative motor braking.

Parallel Regen Braking

Friction braking and regenerative motor braking independently provide the torque.

The input-power split HCM implements a dynamic supervisory controller that determines the engine torque, generator torque, motor torque, and brake pressure commands. Specifically, the input power-split HCM:

  • Converts the driver accelerator pedal signal to a wheel torque request. The algorithm uses the optimal engine torque and maximum motor torque curves to calculate the total powertrain torque at the wheels.

  • Converts the driver brake pedal signal to a brake pressure request. The algorithm multiplies the brake pedal signal by a maximum brake pressure.

  • Implements a regenerative braking algorithm for the traction motor to recover the maximum amount of kinetic energy from the vehicle.

  • Implements a virtual battery management system. The algorithm outputs the dynamic discharge and charge power limits as functions of battery SOC.

  • Determines the vehicle operating mode through a set of rules and decision logic implemented in Stateflow®. The operating modes are functions of wheel speed and requested wheel torque. The algorithm uses the wheel power request, accelerator pedal, battery SOC, and vehicle speed rules to transition between electric vehicle (EV) and HEV modes.



    Traction motor provides the wheel torque request.

    HEV – Charge Sustaining (Low Power)

    • Engine provides the wheel torque request.

    • Torque blending algorithm transitions the torque production from the EV motor to the HEV engine. The algorithm allows the motor to ramp down the torque while the engine torque ramps up. Once the blending is complete, the motor can start sustaining the charge (negative torque), if needed.

    • Based on the target battery SOC and available kinetic energy, the HEV mode determines a charge sustain power level. The mode includes the additional charge power in the engine power command. To provide the desired charge power, the traction motor acts as a generator.

    • Depending on the instantaneous speeds of the engine and motor, the generator may consume energy while regulating the engine speed. In this case, the motor provides the additional charge sustaining power.

    HEV – Charge Depleting (High Power)

    • Engine provides the wheel power request up to its maximum output.

    • If the wheel torque request is greater than the engine torque output at the wheels, the traction motor provides the remainder of the wheel torque request.


    While the vehicle is at rest, the engine and generator can provide optional charging if battery SOC is below a minimum SOC value.

  • Controls the motor, generator, and engine through a set of rules and decision logic implemented in Stateflow.



    • Decision logic determines the engine operation modes (off, start, run).

    • In engine run mode, lookup tables determine the engine torque and engine speed that optimizes the break specific fuel consumption (BSFC) for a given engine power request. The ECM uses the optimal engine torque command. The generator control uses the optimal engine speed command.


    • As determined by the HCM, the generator either starts the engine or regulates the engine speed. To regulate the engine speed, the generator uses a PI controller.

    • A rule-based power management algorithm calculates a generator torque that does not exceed the dynamic power limits.


    A rule-based power management algorithm calculates a motor torque that does not exceed the dynamic power limits.

Passenger Car

To implement a passenger car, the Passenger Car subsystem contains drivertrain, electric plant, and engine subsystems. To create your own engine variants for the reference application, use the CI and SI engine project templates. The reference application has these variants.

Drivetrain SubsystemVariantDescription


Vehicle Body 3 DOF Longitudinal

Configured for 3 degrees of freedom

Wheels and Brakes

Longitudinal Wheel - Front

For the wheels, you can configure the type of:

  • Brake

  • Force calculation

  • Resistance calculation

  • Vertical motion

Longitudinal Wheel - Rear

Electric Plant SubsystemVariantDescription
Battery and DC-DC ConverterBattHevIps

Configured with NiMH battery

GeneratorGenMapped (default)

Mapped generator with implicit controller


Interior permanent magnet synchronous motor (PMSM) with controller

MotorMotMapped (default)

Mapped motor with implicit controller


Interior permanent magnet synchronous motor (PMSM) with controller

Engine SubsystemVariantDescription

Dynamic SI engine

SiMappedEngine (default)

Mapped SI engine


Dynamic CI engine with turbocharger


Mapped CI engine with implicit turbocharger


[1] Balazs, A., Morra, E., and Pischinger, S., Optimization of Electrified Powertrains for City Cars. SAE Technical Paper 2011-01-2451. Warrendale, PA: SAE International Journal of Alternative Powertrains, 2012.

[2] Burress, T. A. et al, Evaluation of the 2010 Toyota Prius Hybrid Synergy Drive System. Technical Report ORNL/TM-2010/253. U.S. Department of Energy, Oak Ridge National Laboratory, March 2011.

[3] Rask, E., Duoba, M., Loshse-Busch, H., and Bocci, D., Model Year 2010 (Gen 3) Toyota Prius Level-1 Testing Report. Technical Report ANL/ES/RP-67317. U.S. Department of Energy, Argonne National Laboratory, September 2010.

See Also

| | | | | | | | | |

Related Examples

More About

Was this topic helpful?