This is machine translation

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

Note: This page has been translated by MathWorks. Please click here
To view all translated materals including this page, select Japan from the country navigator on the bottom of this page.

Model Driveline Actuation Using Torques, Forces, and Motion

From the torques and forces applied to driveline inertias and masses, a Simscape™ Driveline™ simulation determines the resulting motion from the driveline component connections and defining equations. However, a simulation can also accept motions imposed on a driveline and solve for the torques and forces to produce those motions. In general, a driveline simulation is a mixture of these two requirements, solving dynamics both forward (torque and force to motion) and inverse (motion to torque and force). Imposing motions and applying torques and forces to a driveline are together forms of mechanical actuation.

To learn how to actuate drivelines with torques, forces, and motions and how to set motion initial conditions, see: .

All these actuation types (except for initial conditions) require physical signal inputs to define time-varying functions that carry physical units.

Torque-Force Actuation and Motion Actuation Are Complementary and Mutually Exclusive

In all cases, exercise care as you apply a mixture of actuation types to a driveline and its degrees of freedom (DoFs). The complete effect of the actuation types must be such that:

  • Driveline DoFs actuated by torques and forces are not also subject to motion actuation. (They can be subject to motion initial condition settings.)

  • Driveline DoFs actuated by motions are not also subject to torque or force actuation.

For a Simscape Driveline model to simulate nontrivial motion, torque and motion actuation types complement one another exactly to account consistently for the motion of all the DoFs. If this criterion is not satisfied, one of these outcomes results:

  • The motion of the driveline is trivial, staying in its initial motion state for the entire simulation.

  • The actuation types are inconsistent with each other, and the simulation stops with an error.

  • The actuation types leave the driveline motion underdetermined or overdetermined, and the simulation stops with an error.

For more information, see Troubleshoot Driveline Modeling and Simulation Issues.

Was this topic helpful?