Home
Multibody Modeling
MotionView is a general pre-processor for Multibody Dynamics.
Vehicle Modeling
Explore the various vehicle modeling tools.
Road Modeling
FTire Road Modeling
COSIN FTire Documentation
To specify and evaluate road excitation, COSIN/road uses one central subroutine evrmr (COSIN environmental models: road main routine).
Road Profiles and Obstacles in TeimOrbit Format
If COSIN/road recognizes the road data file is in TeimOrbit format (typically, the file name extension is rdf), it branches into the respective reading and evaluation routines.
TeimOrbit 2D Road Type: hydraulic_test_rig

Welcome
What's New
View new features for Altair HyperWorks 2024.1.
Get Started
Learn the basics and discover the workspace.
Tutorials
Learn more about the Altair HyperWorks suite of products with interactive tutorials.
Startup Procedures and Customizations
Start and configure the applications.
Tool Finder
View a list of deprecated panels and their newer, equivalent workflows.
Manage Files and Data
Create, open, import, and save models.
Sessions and Report Templates
Set up sessions and create report templates.
Interface with External Products
Solver interfaces supported in HyperMesh.
Entities and Solver Interfaces
A solver interface is made up of a template and a FE-input reader.
Browsers
Browsers provide a structured view of model data, which you can use to review, modify, create, and manage the contents of a model. In addition to visualization, browsers offer features like search, filtering, and sorting, which enhance your ability to navigate and interact with the model data.
Sketching
Create and edit 2D parametric sketch geometry.
Topology
Create, edit, and cleanup geometry.
FE Geometry
FE geometry is topology on top of mesh, meaning CAD and mesh exist as a single entity. The purpose of FE geometry is to add vertices, edges, surfaces, and solids on FE models which have no CAD geometry.
Meshing and Elements
Explore the different types of mesh you can create in HyperMesh and create and edit 0D, 1D, 2D, and 3D elements.
Model Build and Assembly
Create, organize and manage parts and subsystems.
Composites
HyperMesh composites modeling.
Connectors
Create connections between parts of your model.
Morph
Rapidly change the shape of the FE mesh without severely sacrificing the mesh quality.
Skeleton Modeling
Create a reduced ordered model to facilitate optimization at the concept phase.
Design Space
Workflow to support topology optimization model build and setup.
Optimization
Setup an Optimization in HyperMesh.
Design Explorer
Multi-disciplinary design exploration and optimization tools.
Validate
Validate the model built before running solver analysis.
Analyze
Models require loads and boundary conditions in order to represent the various physics and/or physical equivalents to bench and in-use testing.
Axisymmetry
Reduce a full 3D model with axisymmetric surfaces while accounting for imperfections.
Concept Modeling
Tools and workflows that are dedicated to rapidly creating new parts for specific use cases, or amending existing parts. The current capabilities are focused on stiffening parts.
Crash and Safety
Tools used for crash and safety analysis.
Airbag
Use airbag folder utilities and export a resulting airbag in a Radioss deck.
Aerospace
Essential utility tools developed using HyperMesh-Tcl.
Aeroelasticity
Import an aeroelastic finite element model with Nastran Bulk Data format.
Certification
Framework to plug certification methods to assess margin of safety from the model and result information.
PhysicsAI
Use PhysicsAI to build fast predictive models from CAE data. PhysicsAI can be trained on data with any physics or remeshing and without design variables.
Results Data
Results data can be post-processed using both HyperMesh and HyperView.
Developer
The Developer ribbon contains tools for automation and customization.
Plot Data
HyperGraph is a data analysis and plotting tool with interfaces to many file formats.
Multibody Modeling
MotionView is a general pre-processor for Multibody Dynamics.
- MotionView Overview
  MotionView is a general pre-processor for Multibody Dynamics.
- Model Browser
  The Model Browser allows you to view the MotionView model structure while providing display and editing control of entities.
- MotionView Ribbons
  The MotionView ribbons allows you to quickly access tools and standard functions, and is located along the top of MotionView.
- MotionView CAD Interfacing
  MotionView supports the importing of several types of CAD and FE formats.
- Flexible Bodies
  MotionView has many pre-processing and post-processing capabilities with regards to flexible bodies, or flexbodies, for multibody dynamics models.
- Functional Mockup Unit (FMU)
  Add an FMU to the model or export a model as an FMU.
- Vehicle Modeling
  Explore the various vehicle modeling tools.
  - Build and Analyze Models
  - Vehicle Libraries
  - Components Library
  - Leaf Spring Modeling
  - Road Modeling
    - Altair Road Modeling
    - CD-Tire Road Modeling
    - FIALA Road Modeling
    - FTire Road Modeling
      - COSIN FTire Documentation
        To specify and evaluate road excitation, COSIN/road uses one central subroutine evrmr (COSIN environmental models: road main routine).
        Road Profiles and Obstacles in COSIN/io Format
        If COSIN/road detects the road file in COSIN/io format, it first tries to read certain information common to all road types within this format (see Data Common to all COSIN/io Style Road Types).
        Road Profiles and Obstacles in TeimOrbit Format
        If COSIN/road recognizes the road data file is in TeimOrbit format (typically, the file name extension is rdf), it branches into the respective reading and evaluation routines.
        TeimOrbit 2D Road Type: drum
        TeimOrbit 2D Road Type: flatbelt
        TeimOrbit 2D Road Type: hydraulic_test_rig
        TeimOrbit 2D Road Type: plank or cleat
        TeimOrbit 2D Road Type: pot_hole
        TeimOrbit 2D Road Type: ramp
        TeimOrbit 2D Road Type: roof
        TeimOrbit 2D Road Type: sine
        TeimOrbit 2D Road Type: sine_sweep
        TeimOrbit 2D Road Type: stochastic_uneven
        Superposition of TeimOrbit 2D Roads with 3D Roads
        COSIN Road Track Files
        If the road data file is in COSIN/io format, but does not contain the data block $road_type, it is interpreted as a COSIN road track file.
        User-Defined Road Models
    - MF-SWIFT/MF-Tyre Road Modeling
    - Applus IDIADA Proving Ground
    - XenomatiX Scanned Roads
  - Tire Modeling
  - Soft Soil Modeling
  - Full Vehicle Events and Altair Driver
  - Road Tools
  - 1D Vehicle System Models
  - Update Model Tool
  - Aerodynamics
  - Track Builder
- Tcl/Tk Reference Guide
  Reference material for the scripting interface which is a set of Tcl/Tk commands.
- MDL Reference Guide
  Reference materials for the MotionView MDL Language, Tire Modeling, and the MDL Library.
- MotionSolve Reference Guide
  Reference material detailing command statements, model statements, functions and the Subroutine Interface available in MotionSolve.
- Templex and Math Reference Guide
  Reference material for Templex (a general purpose text and numeric processor) and additional mathematical functions and operators.
- MotionView Python Reference Guide
  Reference materials for the MotionView Python Language.
Media Files
MediaView plays video files, displays static images, tracks objects, and measures distances.
Tabulate Results
Use TableView to create an Excel-like spreadsheet.
Text Files
TextView math scripts reference vector data from HyperGraph windows to automate data processing and data summary.
Publishing and Reporting
Create, define, and export reports.

View All Altair HyperWorks Help

TeimOrbit 2D Road Type: hydraulic_test_rig

A general, time history driven servohydraulic test rig excitation (eventually combined with a flatbelt test rig) is implemented as another 2D road type. If the ROAD_TYPE is set to hydraulic_test_rig, COSIN/road searches and reads the following data items in the [PARAMETERS] section:


Name of input variable	Unit	Meaning
`sampling_time`	time	Assumed time increment of wheel support displacement values, if no separate time channel is provided.
`flat_belt_velocity`	length/time	Optional time span at beginning of simulation, during which an optional, additional flatbelt device is accelerated from stand-still to nominal speed. Default value is 0 (no additional flatbelt).
`acceleration_time`	time	Time span at beginning of dynamic simulation, to accelerate the flatbelt device from stand-still to nominal velocity. Default value is 0.

The wheel support displacement (either purely in vertical (z) direction, or fully spatial in x/y/z direction) is defined by one of the following alternatives:

Either:


`data sub-section (Z_DATA)`	Arbitrarily many lines with a single value of type: length	Values defining time-dependent vertical wheel support displacement values. Time values are assumed to be equidistant, with increment defined by `sampling_time`.

Or:


`data sub-section (XYZ_DATA)`	Arbitrarily many lines with 3 values each of type:3 x length	Data triples defining x/y/z data of the time-dependent spatial wheel support displacement. Time values are assumed to be equidistant, with increment defined by sampling_time.

Or


`data sub-section (TZ_DATA)`	Arbitrarily many lines with 2 values each of type: time, length	Data defining t and z data of the time-dependent spatial wheel support displacement. Time values must be in ascending order. x and y displacements are set to zero.

Or:


`data sub-section (TXYZ_DATA)`	Arbitrarily many lines with 4 values each of type:time, 3 x length	Data defining t/x/y/z data of the time-dependent spatial wheel support displacement. Time values must be in ascending order.

Or:


`data sub-section (TXYZV_DATA)`	Arbitrarily many lines with 5 values each of type:time, 3 x length, length/time	Data defining t/x/y/z data of the time-dependent spatial wheel support displacement, and in addition velocity of the flatbelt device. Time values must be in ascending order.