SimDriveline™

Limitations

About SimDriveline and Simulink Limitations

Some Simulink features and tools either do not work with models containing SimDriveline blocks or work only with restrictions. Others work with SimDriveline models but only on the normal Simulink blocks in those models.

Back to Top

Continuous Sample Times Required

The sample times of all SimDriveline blocks are always continuous, and you cannot use them with discrete solvers. You also cannot override the sample time of a nonvirtual subsystem containing SimDriveline blocks.

Back to Top

Changing Block Properties at the Command Line

Changing the block properties of SimDriveline blocks at the command line is not recommended.

Back to Top

Restricted Simulink Tools

Certain Simulink tools are restricted in use with SimDriveline software.

• Enabled subsystems can contain SimDriveline blocks, but the States when enabling parameter on the subsystem's Enable Port is always treated as held, regardless of how you set the States when enabling pull-down menu in the Enable Port dialog.

• Simulink configurable subsystems work with SimDriveline blocks only if all of the block choices have consistent port signatures.

• For Iterator, Function-Call, Triggered, and While Iterator nonvirtual subsystems cannot contain SimDriveline blocks.

• SimDriveline software supports Simulink model referencing, with this restriction:

  • A SimDriveline model can be referenced only once by another model.

Back to Top

Unsupported Simulink Tool

The Simulink Profiler does not work with SimDriveline models.

Back to Top

Simulink Tools Not Compatible with SimDriveline Blocks

Some Simulink tools and features do not work with SimDriveline blocks:

• Execution order tags do not appear on SimDriveline blocks.

• SimDriveline blocks do not invoke user-defined callbacks.

• You cannot set breakpoints on SimDriveline blocks.

• Reusable subsystems cannot contain SimDriveline blocks.

• You cannot place SimDriveline blocks into Atomic Subsystems that are configured to minimize algebraic loops.

• You cannot use the Simulink Fixed-Point Tool with SimDriveline blocks.

• The Report Generator reports SimDriveline block properties incompletely.

Most SimDriveline Parameters Not Tunable

SimDriveline blocks do not support tunable parameters.

Note   Some SimDriveline blocks are masked subsystems that contain a mixture of normal Simulink and fundamental SimDriveline blocks. Normal Simulink blocks in such masked subsystems do support tunable parameters.

Back to Top

Restrictions with Generated Code

Code generated from models containing SimDriveline blocks has certain limitations.

Clutch-Related Mode Iteration Disabled

In the default simulation mode, SimDriveline software uses mode iteration to determine the locking and unlocking of clutches, suspending the simulation time steps and entering an algebraic loop. Through the Driveline Environment block, present in each distinct driveline, you can manually change the simulation mode to turn off mode iteration while running your Simulink model. In that case, clutch modes are determined over multiple time steps while the simulation continues. Turning off mode iteration increases simulation speed somewhat but at the possible cost of accuracy.

In the generated code versions of SimDriveline models, mode iteration is turned off automatically. Clutch locking and unlocking are determined over multiple time steps.

Restriction on S-Functions Generated from SimDriveline

You cannot generate code from a SimDriveline model that itself contains one or more S-functions generated from other SimDriveline models.

Back to Top

Generating Code

Block Reference