Kinematic Exports - MapleSim Help

Online Help

All Products    Maple    MapleSim


Home : Support : Online Help : MapleSim : MapleSim Application Programming Interface : Multibody : MapleSim/Multibody/Kinematic_Exports

Kinematic Exports

Kinematic Variables and Functions

Every system is modeled by a set of generalized coordinates, q, and generalized speeds, p. The time derivatives of q are related to p through a derived set of kinematic transformations. If the coordinates, q, are not independent, they are related to each other through a set of position constraints.  Similarly, if the speeds, p, are dependent, their inter-relationships are defined by the velocity constraints, and their derivatives by the acceleration constraints. The table below summarizes these exported kinematic variables and functions.

 

Expression

Model Export

Description

Variables

 

 

q

vQ

Generalized coordinates selected by user (n x 1 column matrix)

p

vP

Generalized speeds selected by user (n x 1 column matrix)

[pq]

vX

State variables, comprised of generalized speeds

and coordinates (2n x 1 column matrix)

ⅆqⅆt

vQdot

Time derivative of generalized coordinates

ⅆpⅆt

vPdot

Time derivative of generalized speeds

[ⅆpⅆtⅆqⅆt]

vXdot

Time derivative of state variables

Transformations

 

 

ⅆqⅆthp,q,t=0

GetKinTrans()

Transformation between vQdot and vP (n x 1 column matrix)

hp,q,t

vKinTransRHS

Right-hand side of GetKinTrans() function

Position Constraints

 

 

Φq,t=0

GetPosCons()

Position-level kinematic constraint equations in terms of the n coordinates (m x 1 matrix)

Φq

xJacPos

Jacobian matrix of the position constraint equations with respect to the generalized coordinates (m x n matrix)

Velocity Constraints

 

 

Ψp,q,t=0

=Ψppc

GetVelCons()

Velocity-level kinematic constraint equations, which are nonlinear in the coordinates q and linear in the speeds p (m x 1 column matrix)

Ψp

xJacVel

Jacobian matrix of the velocity constraint equations with respect to the generalized speeds (m x n matrix)

c

vVelRHS

Right-hand side of velocity-level kinematic constraint equations

Acceleration Constraints

 

 

χⅆpⅆt,p,q,t=0

=Ψpⅆpⅆte

GetAccCons()

Acceleration-level kinematic constraint equations, which are nonlinear in p and q,  and linear in accelerations (m x 1 column matrix)

χⅆpⅆt=Ψp=Φqhp

xJacVel

Jacobian matrix of the acceleration-level constraints is identical to that for velocity-level constraints, and equal to the product of Φqand hp, where hpis the partial derivative of h with respect to the speeds p

ep,q,t

=ⅆcⅆtⅆΨpⅆtp

vAccRHS

Right-hand side of acceleration-level kinematic constraint equations

 

GetFrameMotion Command

The GetFrameMotion command generates expressions for the translational or rotational motion of any moving frame in the system, in terms of the defined coordinates and speeds.  The general form of this command is:

 

> sModelName:="MB"

 

> MB:-GetFrameMotion(vector_type,end_frame,start_frame,ref_frame,[ListNumSubs]);

 

where the vector describes the motion of the end_frame relative to the start_frame (the default is the inertial frame), resolved in components along the ref_frame (default is the inertial frame).

 

The vector_type string may take one of the following values:

• 

"r" - translational position vector

• 

"v" - translational velocity vector

• 

"vdot" - translational acceleration vector

• 

"R" - rotation transformation matrix (gives orientation of end_frame relative to start_frame; the ref_frame string must be omitted when this 3x3 matrix is requested)

• 

"w" - angular velocity vector

• 

"wdot" - angular acceleration vector

 

Finally, the ListNumSubs list is used to enter numeric values for parameters that appear in the motion expressions in symbolic form. To determine which system parameters have not been assigned numerical values, use the GetParams command. The ListNumSubs list takes the general form [pd_1=value_1, pd_2=value_2, ...], where pd_i is the i_th parameter or driver and value_i is  the numeric parameter value or driving function of time.

 

A few examples will help to clarify these concepts.

 

> GetFrameMotion("v","CoM");

gives the three global X, Y, Z components of the translational velocity of the CoM frame relative to the inertial frame.

 

> GetFrameMotion("vdot","CoM","Base");

gives the three global X, Y, Z components of the translational acceleration of the CoM frame relative to the Base frame.

 

> Params:= [L1=1, L2=0.5]:

> GetFrameMotion("w","CoM","Base","Ref",Params);

gives the angular velocity of the CoM frame relative to the Base frame, resolved into x, y, and z components along the Ref frame.  Numerical values for L1 and L2 are stored in the Params list, and substituted into the symbolic expressions.

 

> GetFrameMotion("R","CoM","Base");

gives the 3x3 rotation matrix transformation from the Base frame to the CoM frame.  A complete description of rotation matrices is given in the section Building System Models / Bodies and Frames.

 

 

GetNodeName Command

 

The GetNodeName command collects the generated names for the system nodes.  In multibody modeling when connecting two distinctly named nodes, MapleSim arbitrarily picks one of the node names and uses that name for the connected node. The general form of this command is:

 

> MB:-GetNodeNames()

 

where

 

> sModelName:="MB"

 

 

GetParams Command

 

The GetParams command collects all of the system parameters the have not been assigned numerical values (symbols) in the system.  The general form of this command is:

 

> MB:-GetParams()

 

where

 

> sModelName:="MB"

 

 

Examples

The example below shows an embedded MapleSim model of a planar slider-crank mechanism.  In this example, the embedded component name is Simulation0, and the model name is SliderCrank.

leArguments:='InputString'=MapleSim:-Multibody:-GetMultibodyInputSimulation0,'ModelName'=SliderCrank,'KinSimpType'=Simplify,'DynSimpType'=Simplify,'AugType'=Lagrange,'MaxSmallQOrder'=1,'SaveToLib'=false,'SilentMode'=false:MapleSim:-Multibody:-BuildEQsopleArguments:

Analyzing system...

Performing constraint analysis...

The system has 1 degree(s) of freedom. It is modeled using 3 generalized coordinate(s) coupled by 2 algebraic constraint(s).

Peforming a dynamic analysis using an augmented Lagrange formulation - system variables shown below:

vQ,s_P2ttheta_R1ttheta_R5t,vP,ⅆⅆts_P2tⅆⅆttheta_R1tⅆⅆttheta_R5t,vPdot,ⅆ2ⅆt2s_P2tⅆ2ⅆt2theta_R1tⅆ2ⅆt2theta_R5t,vLambda,λ1tλ2t

Dynamic analysis complete.

(1.5.1)

SliderCrank:-vX

ⅆⅆts_P2tⅆⅆttheta_R1tⅆⅆttheta_R5ts_P2ttheta_R1ttheta_R5t

(1.5.2)

SliderCrank:-GetPosCons

1.costheta_R5ts_P2t+0.5000000000costheta_R5tcostheta_R1t+0.5000000000sintheta_R5tsintheta_R1t+1.sintheta_R5ts_P2t0.5000000000sintheta_R5tcostheta_R1t+0.5000000000costheta_R5tsintheta_R1t

(1.5.3)

SliderCrank:-GetFrameMotionv,R6_frame_b,GROUND,GROUND

0.5000000000ⅆⅆttheta_R1tsintheta_R1t0.5000000000ⅆⅆttheta_R1tcostheta_R1t0.

(1.5.4)

SliderCrank:-GetFrameMotionR,R6_frame_b,GROUND,GROUND

costheta_R5tsintheta_R5t0sintheta_R5tcostheta_R5t0001

(1.5.5)

See Also

Dynamic Exports, MapleSim, MapleSim[Multibody][BuildEQs], MapleSim[Multibody][BuildExpression](deprecated), MapleSim[Multibody][BuildSimCode](deprecated), MapleSim[Multibody][BuildSimulation](deprecated), MapleSim[Multibody][GetModel](deprecated), MapleSim[Multibody][GetMultibodyInput]


Download Help Document

Was this information helpful?



Please add your Comment (Optional)
E-mail Address (Optional)
What is ? This question helps us to combat spam