This section describes the Point to Surface (PTSF) Joint entity of MotionView and shows the various usage, creation, and editing methods.
A Point to Surface Joint is a higher pair constraint, which constrains a fixed point on a body to slide along a Surface. The Point to Surface joint provides five degrees of freedom: three rotational at the instantaneous point of contact and two translational DOF.
Common Applications of PTSF Joints are:
• | Cam Follower Mechanisms |
• | Robotic Simulations |
• | Manufacturing Simulations |
The topological information required to define an PTSF Joint is shown in the figure below:
The data members of the PTSF Joint can be classified into the following members:
An PTSF Joint needs the following:
• | One Body – Body 1. |
• | Point on Body 1 that is constrained to the Surface - Point. |
• | The Surface that belongs to Body 2. |
• | Reference Marker with respect to which Surface is created above - Ref Marker. |
If required, the following Initial conditions can be specified for the joint:
• | An Initial Condition Marker can be specified for applying the initial conditions. |
• | An XYZ Initial Position Condition can be specified for the Point. |
If initial conditions are known, it is better to specify them while defining the joint as this will help reduce chances of error in results. If the initial conditions are not specified, MotionView will calculate the point on the surface that is nearest to the Point specified for the Joint.
To learn how to add a Point to Surface Joint to a model, please see the Joints topic.
Important Note - In order to completely specify a Point to Surface Joint, the following entities must be created first:
1. | A 3D Surface entity (created using the Surfaces panel ). |
2. | A Marker that belongs to Body 2 of the joint and is located appropriately so that the Surface entity can be meaningfully described as belonging to the Coordinate System of the Reference Marker. |
Joints Panel (PTSF Joint) – Connectivity Tab
Joints Panel (PTSF Joint) – Initial Conditions Tab
|
The Project Browser will filter the entities and display only the Advanced Joints in the model.
The corresponding panel is automatically displayed.
|
The model containing the PTSF Joint can be saved in MDL format from MotionView and exported in the MotionSolve XML format.
To learn how to create a complete model using MDL Statements please refer to tutorial MV-1060: Introduction to MDL. |
The PTSF Joint when exported to the MotionSolve XML format is defined as a Constraint_PTSF statement. Syntax: <Constraint_PTSF id = "integer" label = "Advanced Joint name" i_marker_id = "integer" j_marker_id = "integer" [ disp_xo = "real" disp_yo = "real" disp_zo = "real" ] surface_id = "integer" > /> In case of the PTSF Joint the model statement will be as shown below: <Constraint_PTSF id = "301001" label = "Point to Surface Joint" i_marker_id = "30102030" j_marker_id = "30103040" disp_x0 = "200." disp_y0 = "150." disp_z0 = "255." surface_id = "301001" /> In the above XML Model statement the i_marker_id and j_marker_id represent the I and J markers of the Joint which belong to Body 1 and Body 2 respectively. To understand the complete syntax of the Constraint_PTSF XML model statement, please refer to the MotionSolve Reference Guide Page for Constraint_PTSF. |
In MotionView, Tcl can be used to add any MDL entities to the model. There are two Tcl commands that can be used to add an entity:
Syntax: mdlmodel_handle InterpretEntity new_handle keyword varname label In case of the PTSF Joint the statement will look as shown below: mdlmodel_handle InterpretEntity aj PointToSurfaceJoint aj_0 "\"Advanced Joint 0\"" b_0 b_0 p_0 sur_0 m_0; |
The initial conditions for the Point to Surface Joint can be specified using the InterpretSet Tcl command. Syntax: mdlmodel_handle InterpretSet keyword tokens In case of the PTSF Joint the statement will look as shown in the example below: mdlmodel_handle InterpretSet SetJointICFlag aj_0 "true"; mdlmodel_handle InterpretSet SetJointIC aj_0 250 150 255; |
The InterpretEntity command is used to add entities to the model and the InterpretSet command is used to set the entity properties. So in the case of the Point to Surface Joint, the properties that can be set are the joints Initial Conditions. Extended definitions for InterpretEntity and InterpretSet can be found in the HyperWorks Desktop Reference Guide.
Note - When using the InterpretEntity and InterpretSet commands, it is important to also use the Evaluate command in order for the changes to take effect immediately.
To learn how to create a complete model using Tcl commands, please refer to tutorial MV-1040: Model Building Using Tcl.
See Also:
*PointToSurfaceJoint (MDL Model Statement)
*SetJointIC (MDL Model Statement)
Constraint_PTSF (XML Command)
InterpretEntity (Tcl Command)
InterpretSet (Tcl Command)