MotionView comes with an improved graphical rendering engine that offers smoother rendering of geometrical objects and a better visual appearance.

MotionView now provides the ability to use geometrical features such as edge and surfaces while creating entities. Through this feature, an edge or a surface of CADGraphics and primitive graphics such as Box and Cylinder can be used to pick origin or alignment axis for entities such as joints, bushings and forces. A point or a vector entity would be automatically created and resolved into the Entity panel.

While picking the point/vector, hover the mouse on the edge/surface to highlight it. While picking a point, a red cr

oss mark + indicates the location of the point being created if clicked. Yellow cross marks + indicate other potential location on the edge.

To use this feature, the option “Use CAD feature recognition for picking” needs to be turned on through Tools > Option > Build Model.

In addition, this option enables:

MotionSolve 14.0 introduced the “NLFE Body” as an experimental feature, which allows you to model non-linearly flexible beams and cables in your multi-body system. The NLFE Body is based on the Absolute Nodal Coordinate Formulation (ANCF). Nonlinearity can occur for two main reasons: (A) Geometric nonlinearity and (B) Material non-linearity. The NLFE body supports both. MotionView also introduced NLFE subsystems to model stabilizer bar and a helical spring system.

This release includes a more robust functionality for the NLFE in MotionSolve. The following improvements have been implemented for this release:

If the maximum von Mises strain in any element of the NLFE component exceeds this value during the simulation, MotionSolve will issue a warning message. MotionSolve monitors the maximum von Mises strain in the NLFE component for BEAM12, BEAMC and CABLE element types for transient and quasi-static analyses.

Specifying the maximum yield strain is helpful for the following scenarios:

A new air spring model is available as an Auto Entity in MotionView.  The air spring force is interpolated from a table of force verses spring height and static inflation pressure, which is typically published by spring manufacturers. You enter the spring trim load and trim height and MotionSolve calculates the static inflation pressure automatically. You may include a bumpstop with the air spring as well. The air spring and bumpstop force properties are read from TeimOrbit format property files.

To add an air spring to your MotionView model:

The Full Vehicle Kinematics and Compliance Event available via the task wizard in MotionView is now documented in the online help under the topic
MotionView > Vehicle Dynamics Modeling > MDL Library User's Guide > Vehicle Modeling Library User's Guide > Events.

The Auto Entities for MF-TYRE/MF-SWIFT, FTIRE/HTIRE, and CDTire now support offsetting the wheel/tire CM along the spin axis. A positive offset moves the CM outboard from the vehicle X-Z-plane.  In addition you can offset the wheel hub graphics as well.

COSIN FTire shipped with MotionSolve 14.0.210 is updated to version 2016-1. However, in the future releases of MotionSolve, FTire binaries will not be included. Altair recommends obtaining FTire from COSIN and installing FTire independently of MotionSolve. When you run FTire with MotionSolve, the COSIN initialization file (e.g. cosin_2016-1.ini) is read to identify the FTire installation, so you can be assured that the latest installed version of FTire is used.

 
Note: Using FTire 2016-1 with MotionSolve 14.0.210 requires a COSIN initialization file in your home directory.

Previously, the powertrain CSE function names were not mapped correctly from the ADM/ACF deck to the MotionSolve XML file. With this release, the following names are mapped automatically:

Note: The function name GSEXX977 was being mapped correctly to GSEXX in version 14.0.

Previously, the RESTART action caused the solver to restart whenever the sensor criteria is true. This can potentially cause an endless restart if the sensor criteria remains true after the solver restarts. This behavior has been modified such that the solver restarts only when the sensor criteria changes from false to true, thus avoiding the possibility of an endless solver restart.

Previously, the strains/stresses reported by MotionSolve for the helical spring created by the MotionView subsystem were discontinuous. This has been fixed starting with the current release.

With this release, support for a number of USERSUBs has been added to a number of Lexicon statements such as ARYSUB (ARRAY), STRING_READ (STRING), GRASUB (GRAPHICS), MATRIX_READ (MATRIX), etc.

This release introduces support for modal displacement, velocity and acceleration as MotionSolve expressions as well within the data access subroutines SYSFNC and SYSARY.

Note: The support for SYSFNC and SYSARY is also available for the Python version of the subroutine. For more details on usage and syntax, please refer to the reference manual.

This release adds support for the PRINT action in the Sensor model statement. When the PRINT action is triggered, MotionSolve writes an additional output to the results files at the time the action is triggered.

The MFOSUB can now be defined as a Python script in addition to being defined as a FORTRAN/C/C++ compiled user subroutine.

MotionSolve will now check if the beam length, Young’s Modulus and/or Shear Modulus are specified as non-positive numbers (which is unrealistic) and will report an error and halt the simulation if these conditions are detected.