Home
Multibody Modeling
MotionView is a general pre-processor for Multibody Dynamics.
Vehicle Modeling
Explore the various vehicle modeling tools.
Full Vehicle Events and Altair Driver
Controllers Library
Controllers form the core of the driver. The Controller Library has various basic controllers its arsenal to calculate different driver outputs.
Closed Loop Controllers
Closed-loop controllers use vehicle responses (for example, speed, position, yaw rate, etc.) as feedback to determine the vehicle inputs needed to match a desired vehicle response, such as following a demand lean profile (for two wheelers) or a path.
Throttle and Brake Controllers
Feedback Traction Controller - PID Controller
A Proportional-Integral-Derivative (PID) controller is a feedback controller that computes a vehicle input using the error, the integral of error, and the rate of change of error between a desired vehicle response and the actual vehicle response.

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
  - Tire Modeling
  - Soft Soil Modeling
  - Full Vehicle Events and Altair Driver
    - Full Vehicle Models with Altair Driver and Events
      This section describes how to add a full vehicle model with the Altair Driver and include the events. The events are simulation commands that enable the Altair Driver control to perform the vehicle maneuvers. A model with an event exports an Altair Driver File (.adf) and the MotionSolve (.xml) files to be simulated.
    - Event Types
      This section describes all of the full vehicle events currently supported with Altair Driver. It also describes all of the events and their parameters.
    - Driver Overview
      The Altair Driver is a set of MotionView models and libraries that allows MotionView users to control and script vehicle events.
    - Controllers Library
      Controllers form the core of the driver. The Controller Library has various basic controllers its arsenal to calculate different driver outputs.
      - Open Loop Controllers
        Open-loop controllers define vehicle inputs directly without feedback (for example, steering wheel angle vs. time).
      - Closed Loop Controllers
        Closed-loop controllers use vehicle responses (for example, speed, position, yaw rate, etc.) as feedback to determine the vehicle inputs needed to match a desired vehicle response, such as following a demand lean profile (for two wheelers) or a path.
        Throttle and Brake Controllers
        Feed-forward Traction Controller
        The Feed-forward controller is the predictive controller of the Altair Driver. It predicts some of the states of the vehicle after look ahead time, or look ahead distance, and accordingly drives the throttle and brake signals to match the demand signal (for example, speed).
        Feedback Traction Controller - PID Controller
        A Proportional-Integral-Derivative (PID) controller is a feedback controller that computes a vehicle input using the error, the integral of error, and the rate of change of error between a desired vehicle response and the actual vehicle response.
        Steering Controllers
        Gear and Clutch Controllers
        Additional Controllers
        Demand Signal for Controllers
        Demand Path for Steering Controllers
    - Additional Altair Driver File Blocks
    - Altair Driver Mathematical Methods
    - Troubleshooting Driver Modeling
    - MotionView Interface
      Driver can be loaded using the Model Wizard of MDLLIB when the Full Vehicle with Driver option is chosen. Driver has some special requirements to interface with the vehicle model. These requirements are resolved automatically if the vehicle model is built using the Full vehicle with advanced driver option in the Model Wizard in MDLLIB.
    - Altair Driver File
      Driver uses the Altair Driver File (ADF) to access all the event parameters in the Solver.
  - 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

Feedback Traction Controller - PID Controller

A Proportional-Integral-Derivative (PID) controller is a feedback controller that computes a vehicle input using the error, the integral of error, and the rate of change of error between a desired vehicle response and the actual vehicle response.

To use a PID control you enter proportional (KP), integral (KI), and derivative (KD) gains, the type of desired response (for example, longitudinal speed or acceleration), and reference the desired response (for example, a table of speed vs time). The Altair Driver then applies the Proportional-Integral-Derivative (PID) control law to calculate the throttle and brake signals.

Algorithm


Parameters
Demand Signal	U
Feedback or response signal	X
Error	e
Proportional gain	Proportional gain
Derivative gain	Derivative gain
Integral gain	Integral gain
Integral control flag	Integral control flag
Integral band	Integral band
Driver throttle output	O _throttle
Driver brake output	O _brake
Drive Ratio
Gear Ratio

Types

VELOCITY CONTROL - Demand signal is a velocity profile with time or distance traveled as independent variable.
ACCELERATION CONTROL - Demand signal is an acceleration profile with time or distance traveled as independent variable.
Demand signal can be constant, expression driver, user defined curve, or MotionView Signal (similar to Open Loop controller).

[LONG_PID_CONTROLLER]
TAG = 'PID'
TYPE = 'FOLLOW_VELOCITY'
DEMAND_SIGNAL = 'DEMAND_SPEED'
I_ACTIVE_BAND = 2
KP 	 			= 100
KD 				= 20
KI 				= 10
INITIAL_ERROR 		= -5


[FEEDFORWARD LONGITUDINAL CONTROLLER]
`TAG`	Attr - string	REQUIRED <PID >
	Attr - string	OPTIONAL By default assumes FOLLOW_VELOCITY. Options: FOLLOW_VELOCITY FOLLOW_ACCELERATION
`DEMAND_SIGNAL`	Attr - string	REQUIRED Block name that contains the demand signal. See the Demand Signal Block topic to learn more about all of the available methods.
`I_ACTIVE_BAND`	Attr - real	OPTIONAL Band in which integral control is activate. If absent: Integral gain is always active. May lead to overcompensation.
`KP`	Attr - real	OPTIONAL Proportional gain If absent: `KP` = 0
`KD`	Attr - real	OPTIONAL Differential gain If absent: `KD` = 0
`KI`	Attr - real	OPTIONAL Integral gain If absent: `KI` = 0
`INITIAL_ERROR`	Attr-real	OPTIONAL Integral error If absent: `INITIAL_ERROR` = 0