complete vehicle model -凯发k8网页登录

using an engine block from vehicle components

the engines library contains blocks that you control using an input physical signal for the throttle. you can parameterize the generic engine block using vectors to specify speed and torque. the block calculates the maximum possible torque as a function of the engine speed at any instant. the throttle signal controls how much of the maximum torque the engine can deliver. the piston engine block accounts for the instantaneous torque transmitted to the engine drive shaft. the instantaneous torque enables you to model vibrations in the drivetrain due to piston revolution. to model just the piston mechanism of a combustion engine, use the piston block.

the vehiclewithfourspeedtransmissionexample example uses a generic engine block, configured as spark-ignition type. the block properties specified in the property inspector include the maximum power, speed at maximum power, and maximum possible speed of the engine. to view engine settings, click the engine block. the engine torque and motion are modeled relative to the rotational ground, which is taken as the base reference of the engine and the starting point of the driveline, or mechanical rotational, connections in this model.

alternative and advanced methods for modeling engines

simscape driveline allows you to create complex, custom engine models. several important engine features to consider in a complex model are:

modeling the tires and brakes

the right and left tire blocks accept the driveline torque and rotation from the transmission at their wheel axle rotational ports (a). given a normal or vertical load (n), this torque and rotation are converted to a thrust force and translation at the wheel hub translational ports (h).

the tires rotate nonideally, slipping before they fully generate traction and react against the road surface. the tire slip of the left tire is reported as a physical signal and converted to simulink^® for use with the tire slip scope.

the double-shoe brake block represents a brake arranged as two pivoted rigid shoes that are symmetrically installed inside or outside of a drum and operated by one actuator. the brake block converts the braking signal from the driver inputs block to an actuator force that exerts a friction torque on the shaft that connects the brake drum to the tire blocks.

modeling the vehicle body and load

the driveline connection line sequence of the model ends with the block, which specifies the vehicle geometry, mass, aerodynamic drag, and initial velocity (zero). this block generates the normal forces that the tire blocks accept as vertical loads. vehicle body accepts the developed thrust force and motion at its horizontal motion translational port (h). the vehicle body model also accepts a wind velocity (w) and a road incline (beta), both provided by physical constants.

the rear wheel vertical load force (nr) is reported back to the tire blocks. the forward wheel vertical load (nf) is not used.

the forward velocity (v) of the vehicle is converted and reported, through the subsystem outport, to the vehicle velocity scope.

alternative differential, wheel, road, and braking models

the vehiclewithfourspeedtransmissionexample example models only the rear wheels, the rear tires, and the vehicle body, without the more realistic drivetrain components of differential gears and brakes. the vehiclewithfourwheeldriveexample example illustrates how to model a vehicle that has four wheels and front and rear differential gears.

for information on modelling brake systems using clutches, see and .

state-controlled gear selection

the stateflow block, which is labeled shift logic, implements gear selection for the transmission. the block determines whether to shift up or down based on input from two other components in the model. driver inputs block supplies throttle and braking information. the vehicle body subsystem supplies the velocity of the vehicle body via a feedback loop.

to open the stateflow diagram, double-click the shift logic block. the model explorer is utilized to define the inputs as throttle and vehicle speed and the output as the desired gear number. two dashed and states keep track of the gear state and the state of the gear selection process. the overall chart is executed as a discrete-time system. the stateflow diagram shown in the figure illustrates the functionality of the block.

the model computes the upshifting and downshifting speed thresholds as a function of the instantaneous values of gear and throttle. while in steady_state, the model compares these values to the present vehicle speed to determine if a shift is required. if so, it enters one of the confirm states (upshifting or downshifting), which records the time of entry.

if the vehicle speed no longer satisfies the shift condition, while in the confirm state, the model ignores the shift and it transitions back to steady_state. the steady-state condition prevents extraneous shifts due to noise conditions. if the shift condition remains valid for a duration of twait ticks, the model transitions through the lower junction and, depending on the current gear, it broadcasts one of the shift events. the model again activates steady_state after a transition through one of the central junctions. the shift event, which is broadcast to the gear_selection state, activates a transition to the appropriate new gear. the stateflow block outputs the gear information to a clutch schedule subsystem that is in the transmission subsystem.

clutch schedule subsystem

the signal from the stateflow block to the clutch schedule controls the five clutches of the cr-cr 4-speed transmission. to see the clutch schedule, open the transmission subsystem, and then the clutch schedule subsystem.