Project 2
ANSWER:
Forward Model Approach:
- the forward modeling approach is also called a cause-effect, engine-to-wheel method.
- the direction of calculation is the same as the direction of positive power flow from the engine to the wheel.
- this approach is based on the vehicle dynamics equation and the behavior of each powertrain component and their dynamics interaction.
- in this we start with modeled using a ‘Driver' block, which is a basic PI controller that generates accelerator and brake pedal outputs to match the desired and actual vehicle speeds.
- The ‘Controller’ block is the brains of the vehicle, representing the electronic control units. Based on the driver inputs, it generates desired engine torque, desired transmission gear, and desired brake torque.
- These inputs are fed to the ‘Powertrain’ block which represents the drivetrain of the vehicle. It consists of an ‘Engine’ and 'Electric Motor through a battery' connected to the ‘Automatic Transmission’ through a ‘Torque Converter’. The output of the transmission is connected to the ’Differential’, which powers the ‘Wheels’, which provides the tractive force for vehicle acceleration. The longitudinal dynamics of the vehicle along with the road load are represented in the ‘Vehicle Dynamics’ block.
P1 Hybrid Vehicle Model:

Honda Insight motor and battery are considered for this project. Data is taken from the ADVISOR database developed by NREL, USA. Data is provided in the project files.

Vehicle Model:
Pre-Processing:
A MATLAB script has been created to load all the variables needed for running the Simulink model and for post-processing. The drive cycle selection is also done here. Before running the Simulink vehicle model, run this initialization script.
drive cycle can be selected from this MATLAB script by changing the variable Drive_cycle select to,
1
UDDS
2
HWFET
3
FTP
4
US06
5
NEDC
6
WLTP
SIMULINK MODELLING:

- Here we start with modeled using a ‘Driver model' block, which is a basic PI controller that generates accelerator and brake pedal outputs to match the desired and actual vehicle speeds.
- The ‘Controller model’ block is the brains of the vehicle, representing the electronic control units. Based on the driver inputs, it generates desired engine torque, desired transmission gear, and desired brake torque.
- These inputs are fed to the ‘Powertrain model’ block which represents the drivetrain of the vehicle. It consists of an ‘Engine model with Electric Motor’ connected to the ‘Automatic Transmission model’ through a ‘Torque Converter’. The output of the transmission is connected to the ’Differential’, which powers the ‘Wheels’, which provides the tractive force for vehicle acceleration. The longitudinal dynamics of the vehicle along with the road load are represented in the ‘Vehicle Dynamics model’ block.
Driver Model:
- ‘Driver model' block, which is a basic PI controller that generates accelerator and brake pedal outputs to match the desired and actual vehicle speeds.
- the PI controller controls the error between the required drive cycle and actual vehicle speed by providing acceleration and brake pedal output to the controller.
Controller Model:
- The ‘Controller’ block is the brains of the vehicle, representing the electronic control units. Based on the driver inputs, it generates desired engine torque, desired transmission gear, and desired brake torque. These inputs are fed to the ‘Powertrain’ block which represents the drivetrain of the vehicle.
- a state flow machine is used to represent the supervisory control unit which decided the operating mode whether it is the start /stop mode or cruising mode or regen braking mode for each mode the engine drive and the motor drive are controlled.

FLOWCHART:
- the input to the state flow charts is accel. and brake pedal input from the driver unit engine actual speed actual vehicle speed soc status and the clutch lockup state and the output to the controller is the mode engine on /off request engine input throttle and electric motor input throttle.
- all control signals passed to the transmission model which represents the drive train.
Engine control unit:
- engine control unit compares engine speed with the maximum torque and minimum torque curve of the lookup table and gives the required torque command to the engine block. the throttle input is combined with the idle speed throttle and gains with torque output from the lookup table to estimate the torque input required for the engine.
- throttle input idle throttle and their sum can be scoped from this block.

Idle speed controller:

Transmission control block:
- the transmission control block controls the gear shifting using the study flow variable chart.
- the gear shifting is controlled according to the vehicle speed and throttle input.

SHIFT LOGIC:

Electric motor control unit:
- motor control unit compares EM speed with the max torque curve and max torque generation curve of the lookup table and gives the required torque command to the electric motor the EM throttle input is used to compare the lookup table and to estimate the torque input required for the e-motor.

Brake control unit:
- brake control unit produces the required brake torque according to the brake pedal input and passes the brake torque into the wheel block in the transmission model.

Powertrain model:
- the power train model includes all the components that convert the power of the engine into the vehicle motion.
- this includes the engine,e-motor, battery pack, transmission, differential, wheels, and vehicle body dynamics subsystem.

Battery model:
- a battery pack subsystem is created with electric power input and battery soc as output
- 2 diffs. subblock has been created to determine the soc and terminal voltage separately soc is used to determine the terminal voltage.

SOC Estimation model:

- pack current in ampere is converted to amphr and divides with max capacity and adds with the initial soc to determine the soc of the battery at each instance the soc value is limited between 0 to 1.
Terminal voltage model:

- ideal voltage and internal resistance are determined by a 1D lookup table and battery voltage is determined using the model.
- the specified values are sent back to the workspace using the to-workspace block and can be used for post-processing.
Engine model:
- based on the engine speed the required torque from the controller is saturated between the max torque curve and min torque curve and passes the engine torque to the transmission block
- the 2D lookup table is used to calculate the fuel flow rate based on engine speed and engine torque.
- the new engine also has an on/off feature to eliminate the fuel flow rate when the engine is off also the engine torque cannot be negative torque as min. torque curve mode saturated.
- the fuel rate is then integrated to find the fuel consumption.
- estimated fuel flow rate fuel consumption engine torque and engine speed are passed to the MATLAB workspace using the to-workspace block
- engine fuel flow rate and fuel consumption are scoped.

Electric motor model:
- based on the engine speed the required EM torque from the controller is saturated between the max EM torque curve and max EM torque generation curve and passes the EM torque to the crank hub
- the 2D lookup table is used to calculate the input electric power to the motor based on the EM speed and EM torque.

crank hub:
- crank hub adds up the EM torque and the engine torque and passes it to the transmission block as the crank torque.

Transmission model:
- the engine block is connected to the automatic transmission via a torque converter the output of the transmission is connected to the differential.

Torque converter:

- the gear selection from the transmission control unit is multiplied by the engine torque in this block and the efficiency and engine dynamics of the torque converter are applied in this model.
Differential Model:

- the transmission output torque is multiplied by the differential ratio and differential efficiency in this block and the torque is transmitted to the wheel as the axle torque.
Wheel Model:
- the brake torque from the control model is subtracted from the axle torque and divided from the rolling radius to determine the tractive force
- the wheel speed is calculated from the vehicle velocity and saved in the workspace.

Vehicle dynamics:
- the longitudinal dynamics of the vehicle along with the road load is represented in the vehicle dynamics block
- tractive force and road loads are used to calculate the vehicle velocity.

1] tractive force = ηt*λt*Te/Rw = M*(dVveh/dt) + 0.5 *ρa *Af*Cd*(Vveh+Vwd)^2 + Cr*M*g*cosθ +M*g*sinθ
2] road load = 0.5 *ρa *Af*Cd*(Vveh+Vwd)^2 + Cr*M*g*cosθ +M*g*sinθ
where,
ρa = air density
Af = frontal area
Cd = drag coefficients
Cr = rolling coefficients
M = vehicle mass
g = acceleration due to gravity
θ = slope
- the variable is loaded on the workspace using MATLAB scripts.
- the acceleration velocity and distance traveled are calculated and stored in the workspace.
Simulation Result:
1] UDDS Drive Cycle:
a] Drive Cycle and Actual Velocity:

Engine Fuel Rate and Fuel Consumption:

VELOCITY, ROAD LOAD, ACCELERATION:

DIFFERENT ROAD LOADS:


electric motor torque require and motor speed:

engine torque requires and gear cmd:

Post-processing:
Matlab script was used to analyze this data and to generate plots. This script needs to be executed after the Simulink model data has been loaded into the workspace. the variables loaded from the model (if desired), do some basic post-process calculations, and generate results and plots.
Post-Processing Results:
1] drive cycle:
a] UDDS:

HWFET:

2] fuel economy numbers(KMPL):
a] UDDS:
average speed[kmph] maximum speed[kmph] fuel economy[kmpl]
___________________ ___________________ __________________
31.528 91.742 28.979
HWFET:
average speed[kmph] maximum speed[kmph] fuel economy[kmpl]
___________________ ___________________ __________________
77.679 96.451 37.059
3] the time trace for engine, transmission input, transmission output, and wheel speed:
a] UDDS:

HWFET:

- much of the fluctuating input speed is facilitated by the torque converter and the transmission input speed fluctuates according to the engine torque required to achieve the drive cycle.
- wheel speed and transmission output speed vary according to gear and differential ratio.
4] engine torque, engine power, fuel rate, fuel consumption:
a] UDDS:

HWFET:
5] accelerator and brake pedal, gear command, vehicle desired and actual speed, vehicle distance:
a] UDDS:

HWFET:

- acceleration and brake pedals are used more bcoz the drive cycle is not very smooth and the gear has to be shifted frequently.
- brake requirements are lower more accelerator pedals are applied on the highway drive cycle and gear shift often occurs bcoz the drive cycle is smoother.
- acceleration and brake pedal the gear command of the transmission control unit the required speed of the vehicle the actual speed and the actual vehicle distance are plotted.
6] the engine operating points on the engine fuel map:
a] UDDS:

HWFET:

- the engine operating points are plotted on the fuel map and the operating points are under the maximum torque curve.
7] the motor speed, motor torque, and motor input power:
a] UDDS:

HWFET:

8] the pack voltage, current, SOC, VOC, and internal resistance:
a] UDDS:

HWFET:

9] The motor operating points on the motor inputs power map, with the motor max motoring and generating torque curves:
UDDS:

HWFET:

CONCLUSION :
- therefore the forward energy-based fuel consumption model of a P1 Hybrid vehicle has been successfully simulated using MATLAB and SIMULINK.
- Analysis and understanding of vehicle operating points based on engine speed, torque, transmission speed, pedal position, gear, distance, velocity, acceleration, battery, voltage, current, SOC, and pedal position.
- Post-process calculations were performed and the required graphs were successfully plotted.
- Successfully calculated vehicle fuel efficiency number[kmpl] for the given city cycle [UDDS] and highway cycle[HWFET].and also compared to the conventional vehicle.