Multibody Solutions Release Notes

3D Contact

3D Contact

Previous topic Next topic Expand/collapse all hidden text  

3D Contact

Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function  

The 3D Contact capabilities in MotionSolve have been completely revamped. Pre-processing, Simulation, Post-Processing and Documentation have been significantly upgraded. The tables below summarize the key benefits you will obtain by using the new contact capabilities and how they have been implemented.

 

Pre-processing


hmtoggle_arrow1CAD Geometry can now be Imported Easily and Reliably to Provide the Geometry for 3D Contact

New meshing options are now available when importing CAD geometry. These enable you to control the mesh density in a very intuitive way.

mbs_14_01

Accurate contact force generation requires uniform meshes. New algorithms, more suited for uniform mesh generation are now used.  This new meshing option is only enabled for input geometries and not for FE models.

 

hmtoggle_arrow1Contact Models are Defined with Minimum of User Iinput

The Properties tab in the Contact panel has been reorganized to have sub-tabs for normal force and friction force.

mbs_14_17

Reasonable contact and friction parameters are provided as defaults. You do not have to change these unless your contacts have special properties.

Parameters are checked for validity as they are entered and the user is alerted to invalid values before the model is run.

Output Requests to measure contact forces are automatically created.

 

hmtoggle_arrow1Extensive Geometry Checks are Performed Automatically to Avoid Potential Failures in the Solver

All contact meshes examined and invalid or “dirty” geometry is clearly identified during modeling.  Contact surfaces for all meshes can be visualized using “Highlight contact side” option in the Connectivity tab.

mbs_14_18

Surface normals can be inverted with just one operation. This is especially useful when contact is happening inside a selected closed geometry.

Red indicates outward normals and blue indicates the inward normals.

mbs_14_02

The normals for a mesh are automatically corrected when inconsistencies are detected. This is especially useful when tria-meshes are imported from STL files or Wavefront OBJ files.

Open edges and T connections, if any, can be highlighted as shown in the figure on the top right. If the mesh is clean (i.e. it forms a closed volume), the panel indicates “No mesh errors” else the “Highlight mesh errors” option becomes available.

mbs_14_19

mbs_14_20

 

hmtoggle_arrow1Mesh Cleaning and Healing Tools

MotionView now includes a new mesh manipulation tool that allows you to clean previously unusable meshes for contact solution. The capability is accessed from the Import CAD or FE utility.

Import CAD or FE utility now provides additional cleaning options that enable you to fill holes, thicken surfaces, eliminate T-junctions and shrink-wrap unusable meshes. All of this is done with a minimum of user input.

 

hmtoggle_arrow1New Contact Models are Supported

A new Volume Model for normal force calculations is now supported. User defined contact models for both normal and friction forces are also supported.

mbs_14_21

In addition, user-defined normal and friction force definitions are supported.

 

hmtoggle_arrow1Updated Contact Properties Editor Macro

This macro tool has been updated to take into account the new contact properties available in the solver and makes setting properties across multiple contacts quick and intuitive.

mbs_14_22

 

hmtoggle_arrow1Contacts are Visualized During Modeling

A new “implicit graphics” contact icon is now visible. You can visually see the geometries that have contact connections.

mbs_14_03

Associated graphics are highlighted when contact entity is selected.

 

hmtoggle_arrow1Precise Contact Detection is Supported

Advanced options are available to detect the precise event when contact occurs. An option is also available to change the maximum step size subsequent to contact detection. This option introduces a Sensor entity with a zero crossing attribute into the MotionSolve XML file. This Sensor will control integration step size so that the onset of contact is accurately detected.

Refer to Rigid to Rigid Contact section in MotionView User Guide to learn more about modeling contacts.

 

 

Solution


hmtoggle_arrow1Improved Robustness of Mesh-to-Mesh Contact

A new collision engine that vastly improves the robustness of mesh-mesh contact has been implemented.

mbs_14_04

 

hmtoggle_arrow1Contact Simulations are Much Faster Now

There are two main reasons for fast contact simulations:

Parallel solution for all contacts
Specialized contact algorithms for simpler shapes

 

Parallel solution for all contacts

The contact kinematics between each pair of geometries is calculated in parallel in different threads. This means whenever there are multiple contacts in your model you can improve simulation time by using multiple cores in a machine. All contact pairs will be dynamically distributed onto the available cores.

The graph below shows how contact simulations speed up as a function of the number of threads used to solve for contact.

mbs_14_05

 

Specialized contact algorithms for simpler shapes

mbs_14_23

A much faster, specialized sphere-to-mesh contact algorithm is now available.

A much faster, specialized sphere-to-sphere contact algorithm is now available.

Both of these are automatically invoked when needed.

 

hmtoggle_arrow1Large Initial Penetration Leading to Unrealistic System Behavior is Avoided

A zero crossing sensor that monitors the distance between contacting geometries is now available. The zero crossing sensor controls integrator step-size to precisely capture the contact event.

mbs_14_06

Note: This sensor is only meaningful for impulsive contacts. If a contact is persistent, then a zero crossing sensor is not needed.

 

hmtoggle_arrow1Contact Parameters have a Physical Basis and can be Easily Defined

A new “Volume” force model that relies on understandable physical parameters such as bulk modulus and shear modulus is now available.

mbs_14_07

The normal force is based on an Elastic foundation model. The rigid bodies in contact are assumed to be covered by thin elastic layers. If the tangential shear stress in the layer is ignored, a direct relationship can be found between the normal pressure and normal displacement. This relationship can be used to generate the force between two contacting layers. This model is well known in the literature for contacts.

 

hmtoggle_arrow1Contact Outputs are Provided Even Though They Might Happen at “Irregular” Times

An option to output the system state at the maximum penetration depth in-between two regular output steps is now available. When you run a simulation from MotionView, this is done automatically. You can filter out these “extra” outputs in HyperView.

 

hmtoggle_arrow1Detailed Contact Behavior can be Exported from the Solver as Requests

The CONTACT () function has been enhanced to provide many more details about the contact such as maximum penetration depth, number of contact patches, total number of contacts, area of contact, etc.

 

hmtoggle_arrow1Key Contact Metrics are now Available. You no Longer have to Compute Them!

Contact metrics tables are now printed in the MotionSolve log file. You can examine the metrics table to determine what the maximum penetration(s) and normal force(s) is/are in your model and when it occurred. Two tables are printed – one ordered by maximum penetration depth and another ordered by maximum contact force:

mbs_14_24

 

A contact report containing this table is also available in MotionView.

 

 

Post-processing


 

hmtoggle_arrow1Contact Behavior can be Examined in Detail in HyperView. You can Understand how the Contacts are Behaving During the Simulation.

New vector plots are now available for visualizing normal force, friction force, penetration depth, and penetration velocity.

mbs_14_08

The coefficient of friction in the contact patches can now be visualized as a contour plot.

Contact forces by region can now be visualized.

 

hmtoggle_arrow1The Range of Contact Occurrence on Geometry Across an Entire Simulation can now be Visualized

A new contact summary frame is now available in HyperView. This summary frame will show you where contact has occurred during a simulation with a contour of the maximum penetration depth for all contact occurrences through the entire length of the simulation.

mbs_14_25

hmtoggle_arrow1Contact Report for Easy Post Processing

MotionView now has capability to generate a Contact Report automatically to simplify the post processing of contacts.

For every model that involves contacts, the auto-generated report contains the necessary plots and animations that enable you to easily understand contact behavior in your model.

A ‘Contact Overview’ is first generated so you can see where the contact has occurred in the model.
Two animations of the model, one showing penetration depth and the second showing normal contact force are available for review
Finally, the report also contains ‘Overall Contact Force vs. Time’ plot for every contact in the model.

mbs_14_10

 

hmtoggle_arrow1Detailed Contact Information can now be Plotted

New options have been added to the contact function. This enables you to create requests containing contact details that can be easily plotted.

 

 

Change in Behavior


The new mesh-to-mesh contact algorithm requires Graphics that have a well-defined volume. Open meshes, i.e., meshes that do not have a volume, are not allowed. MotionView will detect open meshes and flag these as errors. You must fix such Graphics before using these for contact. For more information, refer to the Best practices for running 3D contact models in MotionSolve.

The new mesh-to-mesh contact algorithm is capable of handling very large meshes quite efficiently. In the past you had to take care to mesh only the regions in contact with a fine mesh. This is no longer required. A fine mesh that is not in contact, does not add much overhead to the calculations.