msc.software – december 2003 adams/rail 2003.1 training

MSC.Software – December 2003MSC.Software – December 2003

ADAMS/Rail 2003.1 TrainingADAMS/Rail 2003.1 Training

ADAMS/Rail HighlightsADAMS/Rail Highlights Setting configurations Standard Interface

Defining Subsystems Creating Assemblies Accessing the Curve Manager

Performing an analysis Results postprocessing Template Builder

Build Menu Hardpoints / Construction Frames

Definition of communicators

Setting configurations Standard Interface

Defining Subsystems Creating Assemblies Accessing the Curve Manager

Performing an analysis Results postprocessing Template Builder

Build Menu Hardpoints / Construction Frames

Definition of communicators

Database ManagementDatabase Management Every project is associated with a

database (“cdb”) containing different tables (“tbl”) corresponding to the different model files

Default writable database can be set by the user

No limit to the number of databases

Defaults can be changed and saved in configuration file (Tools / Save ADAMS/Rail

Configuration)

Every project is associated with a database (“cdb”) containing different tables (“tbl”) corresponding to the different model files

Default writable database can be set by the user

No limit to the number of databases

Defaults can be changed and saved in configuration file (Tools / Save ADAMS/Rail

Configuration)

Configuration FilesConfiguration Files Settings are defined in the

file .acar.cfg stored in the home directory

Tables are defined in the acar.cfg file in the ADAMS/Rail installation directory

ENVIRONMENT MDI_ACAR_PLUS_AVIEW yes

Settings are defined in the file .acar.cfg stored in the home directory

Tables are defined in the acar.cfg file in the ADAMS/Rail installation directory

ENVIRONMENT MDI_ACAR_PLUS_AVIEW yes

Now it’s your turn... (1)Now it’s your turn... (1) Refer to the “Getting Started

Using ADAMS/Rail” guide - Introductory section Identify the configuration

file .acar.cfg for your specific user Change your user mode to “expert” Start ADAMS/Rail and get familiar

with the graphical interface Create your own database

(“training”) Specify the <training> database as

default writable with priorital search order

Save configuration in .acar.cfg file

Refer to the “Getting Started Using ADAMS/Rail” guide - Introductory section Identify the configuration

file .acar.cfg for your specific user Change your user mode to “expert” Start ADAMS/Rail and get familiar

with the graphical interface Create your own database

(“training”) Specify the <training> database as

default writable with priorital search order

Save configuration in .acar.cfg file

High-SpeedVehicle

Dynamics

ADAMS/Rail

Durability

FEM

ControlsCAD

In-House Solutions

Expanded Integration PlatformExpanded Integration Platform

NVH

“The simulation produced results in agreement with all service conditions and the overall dynamic behavior. Derailment and rollover stability measurements have been matched with a maximum error of 3%.”

-- Massimo Lenti Manager R&D, Alstom IPS

Business: Railway vehicles manufacturer

Challenge: Optimize new streetcar for rollover stability and derailment avoidance

Solution: Evaluated the vehicle behavior virtually to optimize the design

Value: Improved safety; greater confidence

Case Study: AlstomCase Study: Alstom

Components

Subsystems

Systems

FVPD with ADAMS/RailFVPD with ADAMS/Rail

VEHICLEMODEL

Vehicle Data FilesDampers

SuspensionsAirsprings

BumpstopsWheels

TopologyFiles

AccessoriesRunning gear

Car body

Accessories

VehicleModel

Track Data FileIrregularitiesalong track

Trackcenterline

layoutRail profiles

System & AnalysisConfiguration

Contactmodel

Analysis type:stability curvingswitch

Automatic generation of the railway system

ADAMS/Rail Environment StructureADAMS/Rail Environment Structure

Templates Subsystems Assemblies

STANDARD USER

STANDARD USER

EXPERTEXPERT

USERUSER

Standard InterfaceStandard Interface

Accessible by users with every privilege Subsystems are created referencing existing

templates Minor Role of subsystems must be defined

Front, Rear, Middle, Any Same template can be referenced several

times COPY no longer necessary!

Possibility of defining model data Masses - Inertias Suspensions - Dampers - Wheel properties

Accessible by users with every privilege Subsystems are created referencing existing

templates Minor Role of subsystems must be defined

Front, Rear, Middle, Any Same template can be referenced several

times COPY no longer necessary!

Possibility of defining model data Masses - Inertias Suspensions - Dampers - Wheel properties

Subsystem AdjustSubsystem Adjust

Menu is automatically adjusted for every subsystem

Model data can be assigned and modified

Subsystems can be shifted

Subsystem order can be defined

Menu is automatically adjusted for every subsystem

Model data can be assigned and modified

Subsystems can be shifted

Subsystem order can be defined

Templates & SubsystemsTemplates & Subsystems

One single Template… One single Template…

...Several Subsystems with different model configurations

Working with Property FilesWorking with Property Files Property Files are ASCII

formatted files containing the data of every modeling element

Can be modified with Text editor Curve Manager

Are read into the complete assembly prior to the analysis

Wheel profiles are described in wheel property files

Property Files are ASCII formatted files containing the data of every modeling element

Can be modified with Text editor Curve Manager

Are read into the complete assembly prior to the analysis

Wheel profiles are described in wheel property files

Assembly ProcedureAssembly Procedure

Template: _ERRI_Bogie

Major_Role: Running_Gear

Subsystem: ERRI_Rear_Bogie

Minor_Role: Rear

Template: _ERRI_Bogie

Major_Role: Running_Gear

Subsystem: ERRI_Front_Bogie

Minor_Role: Front

Template: _ERRI_Car_Body

Major_Role: Car_Body

Subsystem: ERRI_Car_Body

Minor_Role: Any

Wagon OrderWagon Order Introduced in order to allow the use of

multiple instances of the same template for more than one wagon

Requested for General Assembly (more than one “Car Body” template)

Introduced in order to allow the use of multiple instances of the same template for more than one wagon

Requested for General Assembly (more than one “Car Body” template)

x

Now it’s your turn... (2)Now it’s your turn... (2)

Go through the “Getting Started Using ADAMS/Rail” guide - Standard Interface section (page 6 to 17) Create subsystems

referencing existing templates

View / modify model data Create an assembly using

your subsystems

Go through the “Getting Started Using ADAMS/Rail” guide - Standard Interface section (page 6 to 17) Create subsystems

referencing existing templates

View / modify model data Create an assembly using

your subsystems

Performing an Analysis (1)Performing an Analysis (1) Several type of analysis can be performed:

Preload analysis (calculation of suspensions preload) : Can be performed only in interactive mode, and it doesn’t need any additional file.

Linear analysis (evaluation of vehicle modes, excluding the effect of wheel/rail contact) : Can be performed in interactive, batch, or files only (external) mode, and it doesn’t need any additional file.

Stability analysis (evaluation of vehicle modes, including effect of wheel/rail contact, evaluation of critical speed, stability map) : Can be performed in interactive, batch, or files only (external) mode, and it needs an additional file: contact configuration file (*.ccf)

Several type of analysis can be performed: Preload analysis (calculation of suspensions preload) : Can

be performed only in interactive mode, and it doesn’t need any additional file.

Linear analysis (evaluation of vehicle modes, excluding the effect of wheel/rail contact) : Can be performed in interactive, batch, or files only (external) mode, and it doesn’t need any additional file.

Stability analysis (evaluation of vehicle modes, including effect of wheel/rail contact, evaluation of critical speed, stability map) : Can be performed in interactive, batch, or files only (external) mode, and it needs an additional file: contact configuration file (*.ccf)

Performing an Analysis (2)Performing an Analysis (2) Several type of analysis can be performed:

Dynamic analysis (fully non-linear vehicle analysis for curving, switch crossing, comfort analysis) : Can be performed in interactive, batch, or files only (external) mode, and it needs several additional files, according to the type of analysis performed:

Contact configuration file (*.ccf) Track property file (*.trk) Flexible track property file (*.frp) [optional] Guiding rail property file (*.grp) [optional]

Several type of analysis can be performed: Dynamic analysis (fully non-linear vehicle analysis for

curving, switch crossing, comfort analysis) : Can be performed in interactive, batch, or files only (external) mode, and it needs several additional files, according to the type of analysis performed:

Contact configuration file (*.ccf) Track property file (*.trk) Flexible track property file (*.frp) [optional] Guiding rail property file (*.grp) [optional]

Performing an Analysis (3)Performing an Analysis (3) The following files are generated when submitting an

analysis: ADM (ADAMS/Solver Deck) ACF (ADAMS/Solver Commands) NAM (Request Configuration) LOG (Analysis information) VEL (for stability analysis, range of velocities used)

The following files are generated when the analysis is executed: REQ (Request file, with user defined output) GRA (Graphics file, with data for animation) OUT (Ouptut file, with additional results) MSG (Message file, the analysis execution log) RES (Results file, all state outputs, optional)

The following command is used to run the analysis externally: adams03 arail ru-solver file.acf

The following files are generated when submitting an analysis: ADM (ADAMS/Solver Deck) ACF (ADAMS/Solver Commands) NAM (Request Configuration) LOG (Analysis information) VEL (for stability analysis, range of velocities used)

The following files are generated when the analysis is executed: REQ (Request file, with user defined output) GRA (Graphics file, with data for animation) OUT (Ouptut file, with additional results) MSG (Message file, the analysis execution log) RES (Results file, all state outputs, optional)

The following command is used to run the analysis externally: adams03 arail ru-solver file.acf

Preload AnalysisPreload Analysis

Calculates the preload for the suspensions of the vehicle: Suspension elements Shear Springs Airsprings (Nishimura, Krettek,

Krettek Coupled Bushings

Preloads automatically applied Allows to choose only a subset

of the vehicle suspension

Calculates the preload for the suspensions of the vehicle: Suspension elements Shear Springs Airsprings (Nishimura, Krettek,

Krettek Coupled Bushings

Preloads automatically applied Allows to choose only a subset

of the vehicle suspension

Preload Analysis – Cont.Preload Analysis – Cont.

Should be run before other analysis Apply a preload at suspension system Will update subsystem file automatically No need to run again using a saved model Will result in transient effect if no preload

is applied first

Should be run before other analysis Apply a preload at suspension system Will update subsystem file automatically No need to run again using a saved model Will result in transient effect if no preload

is applied first

Linear AnalysisLinear Analysis

Linear analysis allows to investigate the behaviour of the vehicle suspension looking at the modal behaviour (damped or undamped Example 1 (Bounce mode) Example 2 (Roll mode) Example 3 (Pitch mode)

Linear analysis allows to investigate the behaviour of the vehicle suspension looking at the modal behaviour (damped or undamped Example 1 (Bounce mode) Example 2 (Roll mode) Example 3 (Pitch mode)

Stability Analysis (1)Stability Analysis (1)

Open Loop Multiple analysis at

different vehicle velocity No check is done on the

stability of the vehicle

Open Loop Multiple analysis at

different vehicle velocity No check is done on the

stability of the vehicle

Critical Speed?Critical Speed?

Real part become positive (should be negative in order to delay over time…)

Real part become positive (should be negative in order to delay over time…)

Critical Speed?Critical Speed?

Critical damping smaller than 0 Critical damping smaller than 0


Closed loop The critical speed of the

vehicle is identified for different value of conicity.

Stability map is automatically generated if more than one conicity value is specified

A frequency range can be specified to avoid instability due to undesired modes

Specification of critical damping to determine stability (0%, 5%,...)

Closed loop The critical speed of the

vehicle is identified for different value of conicity.

Stability map is automatically generated if more than one conicity value is specified

A frequency range can be specified to avoid instability due to undesired modes

Specification of critical damping to determine stability (0%, 5%,...)

Dynamic Analysis (1)Dynamic Analysis (1)

Allows to run a wide range of simulation, according to the parameters and property files specified. Track configuration file Contact configuration file Track flexibility property file

(only when using flexible track) Guiding rail property file (only

when using track with guiding rail)

Allows to run a wide range of simulation, according to the parameters and property files specified. Track configuration file Contact configuration file Track flexibility property file

(only when using flexible track) Guiding rail property file (only

when using track with guiding rail)


Wheel Flat Description This feature is available only when using wheel property

files of format WPF_2. It allows to model wheels with variable radius and variable profiles.

Wheel Flat Description This feature is available only when using wheel property

files of format WPF_2. It allows to model wheels with variable radius and variable profiles.

Cruise Control This feature allows to specify

a constant speed or a velocity profile ( *.vpf file) to be followed during the simulation using a PD controller. The Cruise Control Setup Panel is available in the Simulate menu in the main toolbar.

Cruise Control This feature allows to specify

a constant speed or a velocity profile ( *.vpf file) to be followed during the simulation using a PD controller. The Cruise Control Setup Panel is available in the Simulate menu in the main toolbar.

More...


Switch crossing simulations Available only when using track files in format TRK_4. Detailed description of track profile variation. Possibility to introduce effect of guiding rail (with

flexible connection to the ground). Possibility to define rail and guiding rail at different

sections (see TRK_4). Profiles used for the switch description are stored in the

database table “wheel_rail_profiles.tbl”, and are in TeimOrbit (property file) format. (Example *.rpr file).

Switch crossing simulations Available only when using track files in format TRK_4. Detailed description of track profile variation. Possibility to introduce effect of guiding rail (with

flexible connection to the ground). Possibility to define rail and guiding rail at different

sections (see TRK_4). Profiles used for the switch description are stored in the

database table “wheel_rail_profiles.tbl”, and are in TeimOrbit (property file) format. (Example *.rpr file).

Running simulation with switch: Example Results...

Specifying W/R ContactSpecifying W/R Contact Wheel/rail contact elements implemented with exclusive

rights from ArgeCare: Quasi-linear Element – Basic Features

Described through conicity parameter etc. Suitable for stability analysis in modal space

Tabular Element - Basic Features Pre-computed contact geometry Two-dimensional contact Suitable for standard dynamic analysis (comfort, curving on wide

curves) General Element - Basic Features

On-line computation of contact geometry Three-dimensional contact Flexible, non-elliptical multi-point contact Suitable for severe contact condition analysis (switch crossing,

narrow curving, wear…)

Wheel/rail contact elements implemented with exclusive rights from ArgeCare: Quasi-linear Element – Basic Features

Described through conicity parameter etc. Suitable for stability analysis in modal space

Tabular Element - Basic Features Pre-computed contact geometry Two-dimensional contact Suitable for standard dynamic analysis (comfort, curving on wide

curves) General Element - Basic Features

On-line computation of contact geometry Three-dimensional contact Flexible, non-elliptical multi-point contact Suitable for severe contact condition analysis (switch crossing,

narrow curving, wear…)

Contact MechanicsContact Mechanics

Wheel/rail interconnection represented with Hertzian theory applied to elastic surfaces with variable curvature

Wheel/rail interconnection represented with Hertzian theory applied to elastic surfaces with variable curvature

Contact MechanicsContact Mechanics

Independently represented with a GFORCE on left/right wheel/rail pairs

Contact geometry is precomputed and stored in tables (TAB) or calculated on-line (GEN)

Table is calculated for different values of wheel lateral displ.

Independently represented with a GFORCE on left/right wheel/rail pairs

Contact geometry is precomputed and stored in tables (TAB) or calculated on-line (GEN)

Table is calculated for different values of wheel lateral displ.

Contact MechanicsContact Mechanics The QLT element is based on equivalent

conical profiles (linear approximation of wheel/rail contact)

Suitable for stability analysis in frequency domain

Equivalent conical profiles are calculated corresponding to the “conicity” value inputed by the user

The QLT element is based on equivalent conical profiles (linear approximation of wheel/rail contact)

Suitable for stability analysis in frequency domain

Equivalent conical profiles are calculated corresponding to the “conicity” value inputed by the user

Contact parameters can be visualized in plots

Real wheel/rail profiles used for the model graphics

Contact parameters can be visualized in plots

Real wheel/rail profiles used for the model graphics

Contact mechanicsContact mechanics

Possible to specify in the CCF file the variability of the friction coefficient as spline in function of:

Track distance Creepage With lateral

coordinate on rail / wheel

Possible to specify in the CCF file the variability of the friction coefficient as spline in function of:

Track distance Creepage With lateral

coordinate on rail / wheelF

rictio

n C

oeffi

cien

t

Dista

nceCreepage

Friction variabilityFriction variability

Examples: Wheel/Rail ContactExamples: Wheel/Rail Contact

Lift-Off Simulation

Wheel Profile variability

Lift-Off Simulation

Wheel Profile variability

PostprocessingPostprocessing Stability and comfort toolkit

accessible through separate menus

Time-dependent requests accessible through Curve Toolbar

Request names defined through NAM file

CFG file allows to customize request names

Stability and comfort toolkit accessible through separate menus

Time-dependent requests accessible through Curve Toolbar

Request names defined through NAM file

CFG file allows to customize request names

Using Comfort ToolkitUsing Comfort Toolkit

PostProcessing->Comfort Toolkit PostProcessing->Comfort Toolkit

How to create RequestHow to create Request

Only in Template Builder Only in Template Builder

Section Length?Section Length?

In UIC Comfort Toolkit, Section Length表示的是每隔多遠的距離輸出一次結果點 . 以下圖為例 , 速度為30m/sec, 分析時間 10秒 , section length為 6m, 所以輸出的時候一共有 50 個 section.(30*10/6=50)

In UIC Comfort Toolkit, Section Length表示的是每隔多遠的距離輸出一次結果點 . 以下圖為例 , 速度為30m/sec, 分析時間 10秒 , section length為 6m, 所以輸出的時候一共有 50 個 section.(30*10/6=50)

How to check total load?How to check total load?

Tool->Aggregate Mass Tool->Aggregate Mass

How to check contact table?How to check contact table?

Tool->RSGEO Interface Tool->RSGEO Interface

Plot Configuration FilePlot Configuration File Allow to store in an ASCII file the plot

formatting executed once according to own standards

PLT file can be modified with text editor PLT file can be used for different analysis

referred to the same model

Allow to store in an ASCII file the plot formatting executed once according to own standards

PLT file can be modified with text editor PLT file can be used for different analysis

referred to the same model


Complete the “Getting Started Using ADAMS/Rail” guide - Standard Interface section (pages 18 to 24) Perform a preload analysis to check

the nominal force values of the suspension elements

Perform a stability analysis to investigate the stability of the system

Perform a dynamic analysis over a straight track with lateral ramp to investigate dynamic stability

Perform a dynamic analysis over a curve track to investigate curving behavior

Complete the “Getting Started Using ADAMS/Rail” guide - Standard Interface section (pages 18 to 24) Perform a preload analysis to check

the nominal force values of the suspension elements

Perform a stability analysis to investigate the stability of the system

Perform a dynamic analysis over a straight track with lateral ramp to investigate dynamic stability

Perform a dynamic analysis over a curve track to investigate curving behavior

Template BuilderTemplate Builder

Accessible by users with expert privileges Major Role of template must be defined

Running Gear Car Body Accessory

Possibility of defining model topology Parts Attachments Forces

Possibility of defining model structure Communication between different templates

Accessible by users with expert privileges Major Role of template must be defined

Running Gear Car Body Accessory

Possibility of defining model topology Parts Attachments Forces

Possibility of defining model structure Communication between different templates

The Build MenuThe Build Menu

Build Menu organized in sequential order

Standard modeling elements General parts Attachments

Kinematic (joints) Compliant (bushings)

Railway modeling elements Railway vehicle parts Railway vehicle

interconnections

Build Menu organized in sequential order

Standard modeling elements General parts Attachments

Kinematic (joints) Compliant (bushings)

Railway modeling elements Railway vehicle parts Railway vehicle

interconnections

Symmetrical ApproachSymmetrical Approach

Every modeling element can be created as “left”, “right” or “single”

Symmetrical elements can be automatically connected to symmetrical parts

Left-Right symmetry can be broken in Standard Interface

Every modeling element can be created as “left”, “right” or “single”

Symmetrical elements can be automatically connected to symmetrical parts

Left-Right symmetry can be broken in Standard Interface

Hardpoints and Construction Frames

Hardpoints and Construction Frames

Hardpoints Define location in global reference

frame Can be created/modified in TB Can be modified in SI Are used to define parameterization of

the models Construction frames

Define location and orientation with respect to a local reference frame

Belong to the GROUND part Can be created/modified in TB Cannot be modified in SI

Hardpoints Define location in global reference

frame Can be created/modified in TB Can be modified in SI Are used to define parameterization of

the models Construction frames

Define location and orientation with respect to a local reference frame

Belong to the GROUND part Can be created/modified in TB Cannot be modified in SI

Accessing Hardpoints TableAccessing Hardpoints Table

Mount PartsMount Parts

Used to generate connection elements between parts belonging to different templates

Symmetry is implied from coordinate reference

Mount parts are assigned to the parts they replace during the assembly, if not assigned to GROUND

Connectivity can be tested with an automatic procedure

Used to generate connection elements between parts belonging to different templates

Symmetry is implied from coordinate reference

Mount parts are assigned to the parts they replace during the assembly, if not assigned to GROUND

Connectivity can be tested with an automatic procedure

Switch PartsSwitch Parts Used to define

adjustable topology in templates

Are defined in Template Builder but can be accessed in Standard Interface

“Parts list” contains the different part the Switch Part can represent

Switch to Part is defines as default in TB

Used to define adjustable topology in templates

Are defined in Template Builder but can be accessed in Standard Interface

“Parts list” contains the different part the Switch Part can represent

Switch to Part is defines as default in TB

Template Generation ChecklistTemplate Generation Checklist

Create new template (Major Role: Running_Gear) Define hardpoints (will be parametric) Define construction frames Create parts (i.e. wheelsets, bogie frames…) Create connection elements (i.e. joints…) Define Mount Parts (when necessary) Define Communicator Outputs (when necessary) Define elastic connections (i.e. suspensions,

dampers...) Model data defined in TB can be default values as

they can all be accessed in SI

Create new template (Major Role: Running_Gear) Define hardpoints (will be parametric) Define construction frames Create parts (i.e. wheelsets, bogie frames…) Create connection elements (i.e. joints…) Define Mount Parts (when necessary) Define Communicator Outputs (when necessary) Define elastic connections (i.e. suspensions,

dampers...) Model data defined in TB can be default values as

they can all be accessed in SI

TroubleshootingTroubleshooting “Graphical topology”, accessible through

Database Navigator “Highlight Connectivity”, accessible

through Tools menu

“Graphical topology”, accessible through Database Navigator

“Highlight Connectivity”, accessible through Tools menu


Go through the “Getting Started Using ADAMS/Rail” guide - Template Builder section (page 25 to 60) Create a Running Gear

template Investigate the correctness of

the model Perform linear analysis on a

General Assembly containing the bogie model only to check the plausibility of the system

Go through the “Getting Started Using ADAMS/Rail” guide - Template Builder section (page 25 to 60) Create a Running Gear

template Investigate the correctness of

the model Perform linear analysis on a

General Assembly containing the bogie model only to check the plausibility of the system

CommunicatorsCommunicators

Provide transfer of data in two directions between different subsystems

Two types of communicators: Input Communicators

Request information from other subsystems (name prefix: ci[lrs]_)

Output Communicators Provide information to other subsystems (name prefix:

co[lrs]_)

Data are correctly exchanged when I and O have same “matching names”

Different classes available to provide exchange of different type of information

Provide transfer of data in two directions between different subsystems

Two types of communicators: Input Communicators

Request information from other subsystems (name prefix: ci[lrs]_)

Output Communicators Provide information to other subsystems (name prefix:

co[lrs]_)

Data are correctly exchanged when I and O have same “matching names”

Different classes available to provide exchange of different type of information

Communicator type: MountCommunicator type: Mount

Enable to connect parts belonging to different templates

Exchange a part name (“Car Body”) between the different subsystems

An input communicator is automatically created with a mount part using the name of the mount part: mts_car_body ==> cis_car_body

Enable to connect parts belonging to different templates

Exchange a part name (“Car Body”) between the different subsystems

An input communicator is automatically created with a mount part using the name of the mount part: mts_car_body ==> cis_car_body

Mo

un

t P

art O

utp

ut

Co

mm

un

ica

tor

Output communicatorsOutput communicators To create an output communicator the following

must be specified: Matching Name Entity and Type To Minor Role (inherit =

defined by subsystem minor role) Parameter to be exchanged

(i.e. for mount CO: part name) For “double Attachment Type”

templates: Attached to model with

Same Next

Wagon Order

To create an output communicator the following must be specified: Matching Name Entity and Type To Minor Role (inherit =

defined by subsystem minor role) Parameter to be exchanged

(i.e. for mount CO: part name) For “double Attachment Type”

templates: Attached to model with

Same Next

Wagon Order

Matching CommunicatorsMatching Communicators

Communicators will exchange information during assembly when: Having matching names Being of opposite types (one I, one O) Being of same symmetry type Being of same class Having same minor role or be assigned a role of “any” Belonging to subsystems with same wagon order

Correct definition of communicators can be tested with the help of an automatic procedure

Communicators will exchange information during assembly when: Having matching names Being of opposite types (one I, one O) Being of same symmetry type Being of same class Having same minor role or be assigned a role of “any” Belonging to subsystems with same wagon order

Correct definition of communicators can be tested with the help of an automatic procedure

Communicator TestCommunicator Test

Now it’s your turn... (5)Now it’s your turn... (5) Complete the “Getting

Started Using ADAMS/Rail” guide - Template Builder section (page 61 - 64) Create a Car Body template Define communication of this

template with the Running Gear template

Test validity of communicators Create a new wagon assembly

using the user templates Reproduce one simulation

performed on the example assembly to check the validity of the user model

Complete the “Getting Started Using ADAMS/Rail” guide - Template Builder section (page 61 - 64) Create a Car Body template Define communication of this

template with the Running Gear template

Test validity of communicators Create a new wagon assembly

using the user templates Reproduce one simulation

performed on the example assembly to check the validity of the user model

Assembly Example 1Assembly Example 1

Now it’s your turn... (6)Now it’s your turn... (6) Starting from the ERRI_Car_Body assembly:

Create a template called “buffer” with: major role = “accessory” attachment type = “double wagon attachment”

Create in the template two hardpoints (“front” and “rear”) with distance one from the other = 1m, height from ground = 1.3 m

Create two mount parts: mts_cb_front, over “hps_front”, attached to model with same

wagon order mts_cb_rear, over “hps_rear”, attached to model with next

wagon order Create a longitudinal spring between the two mount parts

(use as property file a modified version of <shared>\springs.tbl\manch_trail_rod.spr to take into account the new free length)

Starting from the ERRI_Car_Body assembly: Create a template called “buffer” with:

major role = “accessory” attachment type = “double wagon attachment”

Create in the template two hardpoints (“front” and “rear”) with distance one from the other = 1m, height from ground = 1.3 m

Create two mount parts: mts_cb_front, over “hps_front”, attached to model with same

wagon order mts_cb_rear, over “hps_rear”, attached to model with next

wagon order Create a longitudinal spring between the two mount parts

(use as property file a modified version of <shared>\springs.tbl\manch_trail_rod.spr to take into account the new free length)

Now it’s your turn... (7)Now it’s your turn... (7) Modify the ERRI_Car_Body template introducing two

additional output communicators: “cb_to_buffer_front”, matching name “cb_front”, attached

to model with same wagon order “cb_to_buffer_rear”, matching name “cb_rear”, attached

to model with same wagon order Create a subsystem referred to the buffer template,

minor role = any, wagon order = 1, shifting it of 24 m forwards

Shift the subsystems of the original ERRI_Car_Body assembly of 25 m forwards

Create new subsystems for the second wagon using the same templates, but with wagon order = 2 (refer to the Getting Started Guide), calling them ERRI_Front_Bogie_2 etc.

Modify the ERRI_Car_Body template introducing two additional output communicators:

“cb_to_buffer_front”, matching name “cb_front”, attached to model with same wagon order

“cb_to_buffer_rear”, matching name “cb_rear”, attached to model with same wagon order

Create a subsystem referred to the buffer template, minor role = any, wagon order = 1, shifting it of 24 m forwards

Shift the subsystems of the original ERRI_Car_Body assembly of 25 m forwards

Create new subsystems for the second wagon using the same templates, but with wagon order = 2 (refer to the Getting Started Guide), calling them ERRI_Front_Bogie_2 etc.


Create a new General Assembly including the following subsystems:

ERRI_Car_Body ERRI_Front_Bogie ERRI_Rear_Bogie ERRI_Car_Body_2 ERRI_Front_Bogie_2 ERRI_Rear_Bogie_2 Buffer

Execute a linear analysis to investigate the influence of a coupling element between the car bodies

Create a new General Assembly including the following subsystems:

ERRI_Car_Body ERRI_Front_Bogie ERRI_Rear_Bogie ERRI_Car_Body_2 ERRI_Front_Bogie_2 ERRI_Rear_Bogie_2 Buffer

Execute a linear analysis to investigate the influence of a coupling element between the car bodies

CustomizationCustomization

Customization features available from the Build Menu in TB/SI

Custom menus and dboxes are: Automatically built over

the standard menus Saved with the template

and automatically built when importing the template

Customization features available from the Build Menu in TB/SI

Custom menus and dboxes are: Automatically built over

the standard menus Saved with the template

and automatically built when importing the template

Linear Modes Control 1Linear Modes Control 1

Back


Back

Cruise ControlCruise Control

In order to use Cruise Control it is necessary to create a construction frame in the car body, in the position where the traction force have to be applied. The construction frame have to be oriented with itz Z axis in the longitudinal positive direction of the car body. An output communicator of type Marker with matching name “traction” it’s needed to transfer the construction frames infromation to the TESTRIG when the vehicle is assembled.

In order to use Cruise Control it is necessary to create a construction frame in the car body, in the position where the traction force have to be applied. The construction frame have to be oriented with itz Z axis in the longitudinal positive direction of the car body. An output communicator of type Marker with matching name “traction” it’s needed to transfer the construction frames infromation to the TESTRIG when the vehicle is assembled.

Back

Track Property File (1)Track Property File (1)

Describe the properties of an ADAMS/Rail track. Different format exist, but only TRK_2 format is supported from the GUI. New format TRK_4 has been developed to allow the modeling of switch crossing and the introduction of guiding rails.

Information in the trk file consist of different blocks: Global track info (Total length, format…). Centerline layout (Curvature, cant, height…). Irregularity data (Measured, analytic, … ). Rail profiles.

Describe the properties of an ADAMS/Rail track. Different format exist, but only TRK_2 format is supported from the GUI. New format TRK_4 has been developed to allow the modeling of switch crossing and the introduction of guiding rails.

Information in the trk file consist of different blocks: Global track info (Total length, format…). Centerline layout (Curvature, cant, height…). Irregularity data (Measured, analytic, … ). Rail profiles.

Contact Configuration FileContact Configuration File

Defines the type and parameters of the contact model to be used LIN (model check) TAB (fast dynamics) GEN (accurate dynamics) QLT (linear analysis)

Can be different for every wheel/wheelset

Can be modified in ADM file

Defines the type and parameters of the contact model to be used LIN (model check) TAB (fast dynamics) GEN (accurate dynamics) QLT (linear analysis)

Can be different for every wheel/wheelset

Can be modified in ADM file

Switch Crossing (1)Switch Crossing (1)

Back

Switch Crossing (2)Switch Crossing (2)

Back

Switch Crossing (3)Switch Crossing (3) Switch Description Enhancements

Separate description of "rail" and "guiding rail" IDs in the rail configuration matrix of the TRK file (to allow profiles for rail and guiding rail to be defined at different sections)

Increase maximum number of points allowed for profile description; eventually, allow an automatic resampling of profiles to a number of points as specified by the user

Add the possibility of specifying, instead of a gauge value+vertical distance (1435 + 14), directly the distance between rail profiles reference systems (i.e. 1500)

Track gauge is now calculated only for the first profile pair Add a parameter in the TRK file to specify the reference

position of the switch along the track Implement contemporary flexibility between track-ground and

rail-guiding rail Implement Unit independency in RPR files

Switch Description Enhancements Separate description of "rail" and "guiding rail" IDs in the rail

configuration matrix of the TRK file (to allow profiles for rail and guiding rail to be defined at different sections)

Increase maximum number of points allowed for profile description; eventually, allow an automatic resampling of profiles to a number of points as specified by the user

Add the possibility of specifying, instead of a gauge value+vertical distance (1435 + 14), directly the distance between rail profiles reference systems (i.e. 1500)

Track gauge is now calculated only for the first profile pair Add a parameter in the TRK file to specify the reference

position of the switch along the track Implement contemporary flexibility between track-ground and

rail-guiding rail Implement Unit independency in RPR files

Next

Switch Crossing (3)Switch Crossing (3) Example: Track with Guiding Rail, speed = 10 m/s Flexibility between rail and guiding rail

Example: Track with Guiding Rail, speed = 10 m/s Flexibility between rail and guiding rail

25 m 40 m

45 m 54 m

Next

Switch Crossing (3)Switch Crossing (3) Example: Track with Guiding Rail, speed = 10 m/s Flexibility between rail and guiding rail

Example: Track with Guiding Rail, speed = 10 m/s Flexibility between rail and guiding rail

Next

Switch Crossing (3)Switch Crossing (3) Contact point number Contact point number

Next

Switch Crossing (3)Switch Crossing (3) Example: Curve Track with Switch, speed = 20 m/s Flexibility between rail and guiding rail <training>\tracks.tbl\mdi_curved_switch_TRK4.trk Use track graphic setting = “high”

Example: Curve Track with Switch, speed = 20 m/s Flexibility between rail and guiding rail <training>\tracks.tbl\mdi_curved_switch_TRK4.trk Use track graphic setting = “high”

85 m

125 m

Next

Switch Crossing (3)Switch Crossing (3) Example: Curve Track with Switch, speed = 20 m/s Flexibility between rail and guiding rail

Example: Curve Track with Switch, speed = 20 m/s Flexibility between rail and guiding rail

Back

msc.software – december 2003 adams/rail 2003.1 training

Documents