Professional Documents
Culture Documents
Lab Amesim
LMS Imagine.Lab Amesim 14
www.siemens.com/plm/lms
How to contact LMS Imagine.Lab
+33 4 77 23 60 30 Phone
+33 4 77 23 60 31 Fax
2.1. 3D Mechanical
New submodels
Submodels updated
Documentation updated
Update Aircraft Electrics manual with best practices for electrical network modeling
[0168442].
Submodels updated
ACFWOR003: hole in tank wall allowing liquid and gas flow. Improvement:
Orifice orientation varies with the aircraft attitude [0158641].
CFROL00, CFROL00A and CFROL10: full compatibility with data files produced by
Cam Designer [169656].
Utilities updated
CF_loadprofND: this function can read cam profiles including velocity and acceleration produced
by Cam Designer [169656].
New documentation
CFD1DGLBP000: definition for mesh size, solver type and gas properties
used in CFD 1D components [ref 0169290]. Possibility to run multi-thread
simulations, specifying the number of threads [ref 0158760]. Relaxation of
mesh size locally in the sketch [ref 0096086]. This submodel replaces
obsolete submodels CFD1DGLBP01 and CFD1DGLBP00.
Documentation updated
The CFD1D library user manual has been updated. In particular there is a new section
dedicated to the CPU time optimization, giving insights on available solver types and
the multithread option for simulations [ref 0164127].
Update equations in the Cooling System documentation thanks to LateX [ref 154992].
EBPS11, EBPS12 and EBPS13: power source or sink. In these submodels, there is
no state variable. In some cases, it reduces the computation time [0154893].
Submodels updated
Utilities updated
CreateBHSpline: vacuum permittivity is used to extrapolate B(H) characteristics with a constant
slope in cubic interpolation mode. Magnetic material models are now more accurate for high
magnetic intensity in cubic interpolation mode [0157833].
Utilities updated
ESSInitOCV is now obsolete. It is replaced by ESSInitOCV2 that features a specific discontinuity
handling for the entropic coefficient. It only applies to linear interpolation mode when the entropic
coefficient is computed from the OCV derivative [0148576].
IFP_ESSdUdT is now obsolete. It is replaced by IFP_ESSdUdT2 that features a specific
discontinuity handling for entropic coefficient. It only applies to linear interpolation mode when the
entropic coefficient is computed from the OCV derivative [0148576].
2.16. Hydraulic
New submodels
PEG02, PEG03: .new gear pumps models with uneven numbersof teeth [0154822]
Submodels updated
FP04: new fluids for aeronautic applications. [0120914], and correction of the
viscosity for several fluids [0165790]
BAP27, BAP28, BRP027, BRP028: correction of the mean pressure value for
negative lift values [0168457].
BAP27RT, BAP28RT: correction of the mean pressure value for negative lift values
[0168457].
Submodels updated
HRBEA0010, HRBEA0011, HRBEA0012, HRBEA0013, HRBEA0040,
HRBEA0041: corrected min/max values of some parameters in bearing
submodels [0154848]
2.20. IFP-Drive
New submodels
DRVDRV02A, DRVDRV02B and DRVDRVRMT02: update pull-away [ref
168068]. These submodels replace DRVDRV01A, DRVDRV01B and
DRVDRVRMT01 that are now considered as obsolete.
DRVICE Table Creator: this tool is dedicated to the creation of the IFP-
Drive engine maps from very simple parameters:
2.21. IFP-Engine
New submodels
Submodels updated
ENGVDEF03: a tool has been created to help users setting up the cylinder head
definition parameters with clear and visual representations [ref 0161640]:
EXHCC3WCTRL05: 3 Way Catalytic Converter submodel adapted for FTS and HIL
applications [0168499].
EXHDOCCTRL05: Diesel Oxidation Catalyst submodel adapted for FTS and HIL
applications [0168499].
EXHLNTRCTRL05: Lean NOx Trap submodel adapted for FTS and HIL
applications [0168499].
EXHGPF05: Gasoline Particulate Filter submodel adapted for Gasoline engine with
a particulate filter [0167127].
Documentation updated
New methodology guides to explain the parameters setting for the submodels 3WCC,
DOC, LNT and SCR [0169490].
2.23. Mechanical
New submodels
Submodels updated
RN010, RN011, RN010A and RN011A: added power, energy and activity
calculations [124590].
RACK02 and RACK02A: added power, energy and activity calculations [124590].
Submodels updated
PLMROPE0: specify initial tension [151630].
2.26. Pneumatic
New submodels
2.28. Powertrain
New submodels
TRBLCSH0: balance shaft is an eccentric weighted shaft that cancels out vibrations
in unbalanced engine designs [0135659].
TRTLEXPORT01: export LMS Amesim simulation results into .unv file that can be
read by LMS Test.Lab Desktop [0161530].
New submodels
FXYA001: stairs interpolation [112186] and corrected display of slopes for out
of range mode [167706].
FXYA02: corrected display of slopes for out of range mode [167706].
NDFXA0: stairs interpolation [112186] and corrected display of slopes for out
of range mode [167706].
2.30. Simulation
Submodels updated
SIMP00: new variables for min and max time step reset at each call [156934] and
possibility to set the fixed solver step [153838 + 168294].
Utilities updated
rtable1d, rtable2d, rtable3d, rtablend, rtablemd, rtablem3d and rtablexy: improved robustness
with respect to incorrect table formats [168014 + 160593].
splinitnd: reduce memory size required for cubic spline interpolation [135187].
THMAS00: define the moist air boundary conditions thanks to the wet bulb
temperature [ref 159864]
Submodels updated
TPFCVINT00/01/02/03: TPF pipe with heat exchange and two thermal ports
[0132152].
Submodels updated
TPF_FP01: Add R407c fluid and model the glide effect below the saturation curve
[0166274, 0168379 and 162032].
TPFMAS00: define the moist air boundary conditions thanks to the wet bulb
temperature [ref 159864].
VDSRTIREFORKIN0: replace the belt, tire and road as seen from the kinematic
[0121265].
Submodels updated
VDTIRE02A, VDTIRE03A: default values for Pacejka 97 and 2002 result in
reversed camber forces [0170937].
VDTIRE03A: fix error in lateral stiffness computation [0170959].
3.1. Automotive
3.1.1. Engine
New demos
LMS Amesim demo help > Solutions > Automotive > Engine > Control
units for Mean Value Engine Model (ECU) > Gasoline engine (MVEM)
with an electric supercharger (Engine_SI_electricSuperCharger.ame):
the demo purpose is to simulate an in–line four cylinders gasoline
engine connected to an electric supercharger.
LMS Amesim demo help > Solutions > Automotive > Engine > Exhaust
system > Management of Additional Species in IFP-Exhaust
(ManagementAdditionalSpecies1.ame): the demo purpose is to explain
the workflow to manage additional species in the IFP-Exhaust Library.
LMS Amesim demo help > Solutions > Automotive > Engine >
Valvetrain system > Electro-hydraulic variable valve actuation and air
content (VVA_LMS_THH.ame): the demo purpose is to demonstrate the
impact of air content on the behavior of a VVA system.
Demo updated
LMS Amesim demo help > Solutions > Automotive > Engine > Stop &
Start application > Diesel engine with starter and battery
(Engine_DID_Start_Stop.ame): the electrical starter has been updated in
order to improve CPU time.
LMS Amesim demo help > Solutions > Automotive > Engine > Complete
vehicle modeling with controls for MIL / SIL / HIL applications > Detailed
powertrain plant models ( PWT_ENG4T_AT6_MIL/SIL/HIL.ame): a
predictive model for combustion chamber has been implemented.
Migration to up to date softwares (64 bits, Matlab 2013, dSpace Next
Generation).
New demos
LMS Amesim demo help > > Solutions > Automotive > Drivetrain >
Transmission / Gearbox> Automatic gearbox > Park lock mechanism for
automatic transmission (ParkLockMechanism.ame): the demo purpose is
to model and simulate the park lock mechanism of a standard automatic
transmission.
LMS Amesim demo help > > Solutions > Automotive > Drivetrain >
Transmission / Gearbox> Manual gearbox > Losses analysis of a
manual transmission (MT6_losses_analysis.ame): the demo purpose is
to introduce the app for gear parameters setting and to analyze and
optimize the losses of a gearbox.
LMS Amesim demo help > > Solutions > Automotive > Drivetrain >
Driveline / Differentials > Reaction torque Front Wheel Drive
(reactionTorque_FWD.ame): the demo purpose is to deal correctly with
the reaction torque acting on the engine block and coming from the
engine moving parts and the gearbox.
LMS Amesim demo help > > Solutions > Automotive > Drivetrain >
Clutch / Torque Converter / Dual Mass Flywheel > Centrifugal Pendulum
Vibration Absorber (CPVA_filtration.ame): the demo purpose is to show
how to use of a Centrifugal Pendulum Vibration Absorber (CPVA) in
order to improve the filtration efficiency of a Dual-Mass Flywheel (DMF).
LMS Amesim demo help > Libraries > Powertrain > Engine crankshaft
with twin balance shafts (L4_engine_balance_shafts.ame): the demo
purpose is to highlight the role of twin balance shafts in a L4 cylinders
engine that is to say to balance the vertical force generated by the
crankshaft resulting in a smooth running engine with minimal vibration.
LMS Amesim demo help > Libraries > Powertrain > Engine >
Torsional Vibration Analysis of LMS Amesim simulations
using LMS Test.Lab post-processing: new tutorial based on
the demo L4_engine_step2 to export LMS Amesim simulation
results into a universal file format and how to apply the post-
processing features of LMS Test.Lab to these results for
Torsinal Vibration analysis.
New apps
Configuration tool for simple gears: help parameters setting of
the simple gear submodels. The geometry tab offers a 2D
view of the gear set that dynamically changes accordingly to
the parameters [0152979].
Apps updated
Shape Editor: fix modulo display in case of simple dog
geometry option [0169111].
New demos
LMS Amesim demo help > Solutions > Automotive > Vehicle
Integration> Electric vehicle > Battery aging and charging strategy :
Assess battery aging in the context of a vehicle usage for 5 different
charging strategies.
LMS Amesim demo help > Solutions > Automotive > Vehicle
Integration > Hybrid vehicle > Multi-criteria analysis > Maneuvers and
control made with Statechart (ManeuversSequence_Statechart.ame):
the demo purpose is to model a sequence of maneuvers and the
vehicle subsystems controllers thanks to the Statechart feature.
New demos
LMS Amesim demo help > Solutions > Automotive > Chassis > Axle system
> Kinematics and Compliance (K&C) test bench template > Multibody
McPherson Axle System (Multibody_Axle_KandC_Bench_McPherson.ame):
the demo purpose is to generate the K&C functional characteristics of a
given axle system, knowing the hard-point location and bushing stiffness.
LMS Amesim demo help > Solutions > Automotive > Chassis > Integration
of vehicle dynamics systems > 4 wheels drive tractor with oscillating front
axle pulling a trailer (tractor_soft_soil.ame): the demo purpose is to model
and simulate the interactions of driveline and chassis (weight transfer) in a
realistic environment (soft soil + slopes + bumps + turn). The tractor has a
front oscillating axle and is pulling a trailer, this results in complex weight
transfers that affect available traction. In that context the limited slip
differentials must balance mobility, manoeuvrability, tire wear…
App updated
Trajectory designer app enhancement to handle long
trajectories [0159791].
3.2.1. Drivetrain
New demos
LMS Amesim demo help > Solutions > OffHighway > Drivetrain >
Transmission / Gearbox > Hydrostatic transmission > Hydrostatic
transmission of tractor (HydrostaticTransmission_Tractor.ame): the
demo purpose is to analyze the power losses and monitor the global
efficiency of an hydrostatic transmission in function of the vehicle speed.
3.2.2. Chassis
New demos
LMS Amesim demo help > Solutions > Off-Highway > Chassis > Tractor
with trailer on uneven soft soil (tractor_soft_soil.ame): the demo purpose
is to model and simulate the interactions of driveline and chassis (weight
transfer) in a realistic environment (soft soil + slopes + bumps + turn).
The tractor has a front oscillating axle and is pulling a trailer, this results
in complex weight transfers that affect available traction. In that context
the limited slip differentials must balance mobility, manoeuvrability, tire
wear…
3.3.1. Aircraft
New demos
LMS Amesim demo help > Solutions > Aerospace and Defense >
Aircraft & Space > Hydraulic Systems > Hydraulic and AC Emergency
Power Generation (RATHyd.ame): the demo purpose is to show the
power flow and power transformation from the relative wind power
extracted by the RAT to hydraulic and electrical power.
LMS Amesim demo help > Solutions > Aerospace and Defense >
Aircraft & Space > Hydraulic Systems > Aircraft Hydraulic Network
(HydraulicAircraft.ame): the demo purpose is to perform a high level
power analysis, in order to assess the flow balance between the
hydraulic power generators and consumers.
LMS Amesim demo help > Solutions > Aerospace and Defense >
Aircraft & Space > Environmental Control Systems > Global thermal
management > Thermal cabin modeling: series of demos to assess the
thermal behavior: ECS requirements validation (simple cabin model),
detailed thermal model of the cabin and integration with the ECS (air
conditioning pack).
LMS Amesim demo help > Solutions > Aerospace and Defense >
Aircraft & Space > Electrical Systems > Network > Power Budget:
Twinjet Electrical Network interactive simulation
(ACE_ELECNetworkInteractive.ame): dashboard interactive simulation
to reconfigure and simulate an electrical network in a "pseudo" real-
time way.
LMS Amesim demo help > Solutions > Aerospace and Defense >
Aircraft & Space > Electrical Systems> Network > Power Systems
multiphysics integration (MultiPhysicsNetwork.ame): this demo
interfaces the electrical network with other aircraft subsystems (flight
controls, fuel pumps, ECS) to gather/validate nominal and dynamic
requirements on generators and converters.
LMS Amesim demo help > Solutions > Aerospace and Defense >
Aircraft & Space > Engine Equipment > Burst duct event
(Burst_duct_event.ame): bleed pipe burst: study pressure wave in a
confined space, the nacelle compartment for example, where
equipment must be protected from overpressure.
New demos
LMS Amesim demo help > Solutions > Mechanical Industries > Fluids
Systems and Components > Hydraulic components> Hydraulic vane
pump (VanePump_THH.ame): the demo purpose is to demonstrate the
effect of air dissolution dynamics on a vane pump’s behavior.
New demos
LMS Amesim demo help > Solutions > Mechanical Industries > Two
Phase Flow Systems > Refrigerator freezer with on/off control
(RefrigeratorFreezerWithOnoffControl.ame): the demo purpose is to
show the way to model a refrigerator freezer using an on/off control
command.
LMS Amesim demo help > Solutions > Mechanical Industries > Two
Phase Flow Systems > Refrigerator freezer with inverter control
(RefrigeratorFreezerWithInverterControl.ame): the demo purpose is to
show the way to model a refrigerator freezer with an inverter control
command.
ID Description
8143498 Files and folders with spaces were not supported as text global parameters
Using a real global parameter in the expression of an integer parameter was allowed
8150139
but did not work at simulation time
8170780 The '-axWP' Intel compiler option could generate different results
Performance analyzer was not correctly updated when a simulation was run from
8172210
Amepilot
8174796 The Adams manual specified an unsupported compiler
In the Excel scripting API, the ‘ameputgpar’ script failed if two global parameters had
8178364
very similar names
8187302 The RLM statistics could be wrong for token based licenses
8189058 If a parameter value was empty after a ‘Check submodels’ or a submodel assignment, it
8189210 was not replaced by its default value
8189297 With the Statechart, it was difficult to create transitions between states
8189762 The variable print interval submodel did not work correctly with the standard simulator
The HEAT assistant displayed an error message, in velocity mode, on radiator
8189876
parameter change
8190151 The C API was not working under Red Hat Enterprise 5
8191210 Legend position was not restored correctly when loading saved plot styles
8191580 The open simulator could fail at discontinuity restart with DASSL
A poor message was generated for unknown global paramters with the standard
8191921
simulator
8193879 In the Python scripting API, the ‘amebode’ function always created a plot
8195570 Supercomponent exposed variables could be used in an optimization
8195571 Exposed global parameters were not updated after renaming supercomponents
8195986 Issues could appear in column size of batch dialog boxes when importing batch files
8196442 Wrong unit conversions occurred on FFT plots
8196862 The plot ‘batch’ status was wrongly stored in plot configurations
8197675 A Confusing message could be displayed when compiling encrypted supercomponents
Values displayed in batch run selection dialog boxes did not take unit conversions into
8197892
account
Editing some LMS Ameset source code with an external editor could fail if a submodel
8197948
path contained spaces
8197949 The RLM installation from the LMS Amesim DVD could fail
8198237 The ‘Save next’ option did not work for common parameters
8198482 The contextual help of some submodels was not displayed
8198802 A license error could occur when opening ICAR models using LMS Amerun
8199575 Writing auxiliary files was sometimes not taken into account before saving a model
8199611 Memory limitations existed in the ‘ameloadvarst’ Python script
ID Description
The ‘Check submodels’ blocks when updating dynamic blocks in a local
7282321
supercomponent
Selected states info message is no longer displayed in the Modelica import assistant
7288010
messages window
729105 It is not possible to convert unsaved models to a Native LMS Amesim submodel
7291111 CAD position is wrong in the case of several assembly levels
When putting a Simulink interface block in a supercomponent, the resulting S-function
8140075
makes Matlab crash
8145952 Points after the simulation final time can be printed during simulation
8148193 The solver sometimes fails because of a bad discontinuity handling in some submodels
When using the Simulink Co-Simulation interface, the option to create files for blackbox
8156347
in the ‘File’ menu is still available
8160979 The ‘Discontinuity Printout’ option is always activated with co-simulation using DASSL
There can be a drift of print points when co-simulation interval and LMS Amesim print
8165894
interval are the same
8183393 Discrete Partitioning is not compatible with continuation run
There is no check between the unit of a global parameter and the unit required where
8183987
the global parameter is used
The print interval is not taken into account when a co-simulation model has an implicit
8184038
loop
LMS Motion Co-simulation interface in LMS Amesim: interface blocks cannot handle
8186982
backslashes
8189933 Numerical noise produced when changing equations due to supercomponent creation
8190229 A buffer overflow with 'amefprintf' in Simulink can occur and crash the Matlab GUI
8192267 The ‘ameputp’ Matlab script wrongly considers requests ending with wildcards
Removing submodels in sketch mode does not work for line submodels in the Hydraulic
8193957
Library
It is not possible to run coupled simulation between LMS Amesim and LMS Motion
8196062 when external files are referenced in relative folders of the LMS Amesim working
directory
The Simulink interface manual claims that short names are needed for Matlab, which is
8199274
no longer true
8199963 When a comma is used in a parameter value, it cannot be replaced by a dot character
GUI issues when pasting multiline text into the ‘Add Class’ dialog box of the Modelica
8201041
Editor
8201043 Modelica models can be seen as packages in the Library Tree
8201056 Crashes occur when loading batch files then removing batch sets out of the range set
8256276 The ‘AMEGetCompilers’ API function does not work as expected
ID Library Description
All units for American System of Unit are not appropriate with respect to
8178060 all
SAE standard.
Stability problems when considering pressure losses in multi-port
8190447 CFD1D
junctions
8170666 CF Bad cam profile can generate NaNs
All the variables of CSDATA000 should be visible whatever the output
8189428 CS
chosen.
8190377 DRV DRVDRV1C does not correctly manage gear ratio.
8156735 ENG There are turbine preprocessing robustness issues.
The display of GM partial pressure and fractions are not consistent when
8198775 GM
fog is considered.
8200350 GM Compilation issue with half heat exchanger depending on user path list.
Interference between the Regulation Tool Apps linked to THPHIREG1
8201295 GM
and all its connected components
Turbine pre processing issues: accuracy may be low and efficiency
8156735 ICE
extrapolation may be improved.
The display of partial pressure and fractions are not consistent when fog
8198775 MA
is considered.
Mass conservation issue in the moist air condensation chamber
8170375 MA
MACND010.
8140956 MEC Under some circumstances, CAM00 can miss some discontinuities.
8171882 PLM PLM assembly can miss some over-constrained configurations.
Pneumatic line PNL00R: add explanations in the documentation about
8157612 PN
the velocity calculation when pressure ratio is close to 1.
PN mixture domain of validity is not given for all the gas properties
8189198 PN
submodels.
8200350 PN Compilation issue with half heat exchanger depending on user path list.
Interference between the Regulation Tool Apps linked to THPHIREG1
8201295 PN
and all its connected components.
7282406 SIG SIGHULL0 not compatible with 64 bit platforms.
In THGCV2 convective exchange, wrong temperature is used in the
8200286 TH computation of the absolute humidity of moist air leading to inconsistent
warning.
8200350 TH Compilation issue with half heat exchanger depending on user path list.
Interference between the Regulation Tool Apps linked to THPHIREG1
8201295 TH
and all its connected components.
In TFPHE** submodels, some numerical noise could appear when
7269049 THH
pressure changes.
8200350 THH Compilation issue with half heat exchanger depending on user path list.
Interference between the Regulation Tool Apps linked to THPHIREG1
8201295 THH
and all its connected components.
8193954 TR Planar contact sometimes ignores some contact events
It is important to remember that LMS Amesim 14 models cannot be read by versions of LMS
Amesim earlier than LMS Amesim 14.
Once LMS Amesim is installed, you must set up its license manager (Reprise License
Manager) in order to be able to start it. For more information, please refer to the section The
License manager installation.
Basic knowledge of the Operating System of your machine is required for the installation but also
and above all for the setup of the license manager. Please ask for the assistance of your local
system administrator if needed.
In addition to this license file, you must have an activation key to start the setup application. This
activation key is composed of 25 characters.
Both your license file and your activation key are usually supplied by e-mail. If you already have
them, you can proceed with the installation. If you do not have them, please contact your local
Siemens representative (see the Contact section at the beginning of this document).
For any request, please have ready, or include in your e-mail or fax, the following three items:
• Your License Contract Number if you have already used a previous version of LMS
Amesim.
• The hostname and hostid of the server (or servers) on which you will execute the RLM
license manager. For a node-locked license and/or a stand-alone workstation, this is the
hostname and hostid of your workstation. For a floating license, this is your server
hostid(s) and hostname(s), not your client workstation information.
A utility is provided on your DVD (in the LicensingTools folder) to get the required hostname and
hostid information:
Just run this utility on your server(s) and copy the output information into your e-mail message or
fax. Please refer to the section License servers and hostids for more details. Send this data to
your local Siemens office with the signed license agreement.
You will not be able to go through the installation procedure of LMS Amesim
without your activation key.
8.2. Requirements
The LMS Amesim software is ordinarily installed on a single file system. This can be an
individual user's computer in case of a stand-alone workstation, or a central file server for
networked installations.
Multiple different versions of LMS Amesim can be installed on the same server, possibly for
heterogeneous platforms. All of these versions can access the same license file using a common
license server.
All machines that are to use LMS Amesim must be able to access the installation folder (also
known as %AME% or $AME, under Windows or Linux respectively).
If you have an older version of LMS Amesim on your PC and you still want to be
able to use this version, you should install LMS Amesim 14 in a different folder
and use the batch files supplied in the misc subfolder of the installation folder to
run the old version.
8.2.2.1. Windows
To run LMS Amesim on Windows Vista /7/8, you need:
Windows 2003 Server has the same compatibility constraints as Windows XP.
Windows 2008 Server has the same compatibility constraints as Windows
Vista.
Windows 2012 Server has the same compatibility constraints as Windows 7
The Microsoft Visual C++ compiler is not supplied on the CD. If you do not want
to use GCC, you have to buy the Microsoft Visual C++ compiler and install it
independently. Express editions of the Microsoft Visual C++ compiler are free.
The license file is not on the DVD, it is specific to each computer. Please refer to the section
Before you start for more details.
8.2.2.2. Linux
The following requirements apply to Linux systems running LMS Amesim:
LMS Amesim is compatible with other Linux versions: SUSE 10.0, Fedora, RedHat Enterprise
5.0, Ubuntu 8.04, etc. (always require at least a GLIBC 2.5)
In case of compatibility questions with your platforms and/or operating system versions, please
contact your local Siemens Technical Support (see the Contact section at the beginning of this
document).
To use the API in C under Linux, you need a GCC compiler version 4.4.7 or higher.
You can use either a local or remote DVD drive to access the LMS Amesim installation file sets.
The instructions given below are for mounting a local DVD drive; for a remote DVD drive please
ask
for the assistance of your local system administrator. The LMS Amesim DVD is in ISO 9660
format.
1. Log in with the root account and make a DVD drive mount point. For example:
mkdir /dvdrom
2. Then execute the command below to mount the DVD drive on your system where
DVDROMDIR refers to the DVD drive mount point:
There is also another way for advanced user to install LMS Amesim in silent mode using scripts.
For more details, refer to section The Installation procedure using script.
1. Log in as Administrator.
2. Place the LMS Amesim DVD into the drive.
3. The auto-run configuration should start the setup automatically and the Welcome page should
appear. If not, start the setup.bat file located in the root folder of the DVD.
Under Linux:
1. Login as root.
2. Place the LMS Amesim DVD into the drive.
3. If necessary, mount the DVD drive on your system as described in section 8.2.3
4. Move to the DVDROMDIR:
cd DVDROMDIR
5. Run the DVD installation script. Use either the upper-case or lower-case version as
appropriate for your platform (do an ls to see the file name on your system):
./INSTALL.SH AMEHOME
The AMEHOME argument is the chosen installation directory (also known as $AME). The
installation script is self-explanatory and will ask for which optional libraries you want to install.
6. If you want to add extra libraries after the initial installation, just re-run the installation
command.
7. Unmount the DVD drive if required:
umount DVDROMDIR
9. Log out.
Make sure that there is no anti-virus program running during the installation
process since this, for LMS Amesim (and other software), has proven to result
in a faulty installation. After the installation is complete you should of course turn
on the virus protection again.
8.3.1.1. Welcome
During the LMS Amesim installation, there will be a sequence of dialog boxes displayed; we will
show some of them in this document with some comments on what to choose in each of them.
The default options have been selected so that they suit the majority of installations.
To navigate forwards or backwards in this sequence of dialog boxes, you need to press
respectively the Next or Back buttons (or Cancel if you wish to quit the installation).The first
Welcome dialog box is simply to introduce the LMS Amesim installation.
LMS Amesim and its components are protected by a license manager application named RLM,
the installation process will install all the files needed for this tool. However, the license file and
the activation key are provided by Siemens separately.
If you already have the license file, the dialog box asks you to enter the folder where it is stored.
At the end of the installation process, this file will be copied from this folder to the licensing
subfolder of the installation folder.
If you do not have the license file and/or the activation key, please ask your local Siemens
representative to provide you with what you need (see section Before you start).
Regarding the new license daemon, please refer to section New license daemon for more
information.
If you selected the Custom installation you get an extra dialog with which you can select which
parts of the product you want to install. There are some dependencies between some features,
not all parts can be installed independently.
Under Windows only, this folder can contain blank characters (such as
C:\Program Files). This is not permitted under Linux.
For compilers, we recommend you to use the GNU GCC which is supplied with LMS Amesim. If
the Microsoft Visual C++ compiler is not installed, GNU GCC will be the only one used by LMS
Amesim and LMS Ameset.
If you want to use the LMS Amesim /Simulink interface, you must use Microsoft Visual C++
since GNU GCC is not compatible with Simulink. To use the Microsoft Visual C++ compiler, it
is necessary to buy it and install it independently.
By using LMS Ameset, it is possible to compile submodel code written in Fortran. To compile this
code, you can either use g77 which is supplied with GNU GCC or the Microsoft Visual Fortran
compiler. In this last case, it is necessary to buy it and install it independently.
If you have chosen to install both LMS Amesim and LMS Amerun you must specify
which software must be started by default when double-clicking on a model file from the
Windows Explorer. If you plan to use both applications we recommend that you set
LMS Amesim as the default program to launch.
• Adding shortcuts
In this dialog box you are asked for a default working folder for LMS Amesim, this will
determine where it will start.
Under Windows only, folder names can contain blank characters (such as
C:\My Work). This is not permitted under Linux.
In order to run any applications of the LMS Amesim suite under Linux, you
need to define an environment variable named AME and set it to the LMS
Amesim installation directory.
You also need to add the $AME environment variable to your command search
path. The following instructions explain how to get this done automatically each
time you log in to your machine.
You may put the following two lines in your .cshrc file which is in your home directory:
Replace AMEHOME by the name of the LMS Amesim installation directory and check these two
lines are placed after any other set path command lines in the file.
You may put the following lines in your .profile file which is in your home directory:
AME=AMEHOME
export AME
Replace AMEHOME by the name of the LMS Amesim installation directory and check these four
lines are placed after any other set path command lines in the file.
Once you have modified your .cshrc or .profile file, you have to log out and log in again so that
the changes take effect. If you use the C shell, you can run the following command from a
terminal window to avoid the login/logout process:
source ~/.cshrc
When these environment variables are set properly, the LMS Amesim applications can be
started by typing LMS Amesim, LMS Ameset, LMS Amecustom… as appropriate.
Once you have installed LMS Amesim we recommend that you do not modify
your installation manually (adding or removing files), otherwise we cannot
guarantee that the application will function correctly. Moreover, any hotfix
installations will be rendered impossible by such modifications.
LMS Sysdm is a model management tool supplied with LMS Amesim. If you
have the necessary license, you can install its Client version.
Once the setup wizard finishes installing LMS Amesim, the following message appears:
You can click the Get more info button to learn more about the capabilities LMS
Sysdm.
You can click the Help button to launch the LMS Sysdm Client Installation guide
(which can be found in the third_party/sysdm folder of the installation media).
On the LMS Amesim DVD, there is an example of this file called install_config.dat
USER_NAME=user_name_of_the_owner
COMPANY_NAME=Siemens Industry Software
CD_KEY=replace_this_label_with_your_activation_key
SETUP_TYPE=Full
DESTINATION_DIRECTORY=E:\AMESim
WORKING_DIRECTORY=E:\AMETest
PLATFORM=windows
FILE_ASSOCIATION_TO_AMESIM=yes
SHORTCUT_ON_DESKTOP=yes
SHORTCUT_IN_START_MENU=yes
SETUP_TYPE: setup type like Full, Run and others special setup types. Custom type is not
configurable for scriptable installation
DESTINATION_DIRECTORY: full path for the location of the LMS Amesim installation
folder
Under Windows:
setup –s name_of_config_file
Under Linux:
INSTALL.sh –s name_of_config_file
Under Windows:
• Select the Uninstall shortcut in the LMS Amesim entry of the Start menu.
• Use the uninstall.bat file located in %AME%.
• Start the setup.bat file on the installation DVD.
Under Linux:
When you launch the uninstallation facility from the DVD under Windows, you obtain the dialog
box shown below. Select the Uninstall option and click the Next button.
If you want to uninstall a different version of LMS Amesim, you can click the Change location
button, and then browse to select the version you want to uninstall.
In order to use LMS Amesim 14, you must ask for a new license file since
license files in older formats are not compatible (Rev 11 SL1 and below).
To use LMS Amesim 14, you must have a valid license file named
LMS_HOSTNAME_HOSTID.lic from Siemens, see section Before you start for more details. This
license file includes all the features you are allowed to use.
This new daemon is installed by default with LMS Amesim 14 and it is the only one required if
you do not need to use previous versions of LMS Amesim at the same time (only the 14 version
will be used). In this case, just run the default installation: the new daemon (LMS) and license file
(LMS.lic) will be used.
If you plan to continue using previous versions of LMS Amesim (Rev 11 SL1 and below) along
side LMS Amesim Rev11 SL2, then two license servers with two different license files will be
required:
• The new daemon (LMS) and license file (LMS.lic) will be used by LMS Amesim 14.
• The old daemons (AMED or LMS_INTL) and license files (license.dat or LMS_INTL.lic)
will be used by previous versions.
• On the server specified in the license file: RLM must be installed and configured (see
instructions below).
• On every client machine accessing the server: no installation or configuration of RLM is
required, only a copy of the license file (renamed as LMS.lic) is required in the licensing
subfolder of the LMS Amesim installation. Alternatively the LMS_LICENSE environment
variable can be used in this case, please refer to the section LMS_LICENSE
environment variable for more information.
Under Windows:
To install the license manager, you must run the RLMLicenseServer.exe utility which is located in
the %AME%\licensing\install folder. The Welcome screen for installing RLM
appears.
You just need to click Next and the Destination Folder Location screen opens.
A default destination path is filled in. If there is a need to, it can be changed. The path in the
picture might be different depending on the operating system you are working on.
With the upper part of this dialog box, you have the ability to select the license file that will be
used by the license server. The installer will copy the license file to the location specified in the
lower field of the dialog box.
The destination folder of the license file can be set with two possible options:
• The default place to store the license file is the folder {Common application
data}/LMS/Licensing. The folder {Common application data} can be different depending
on the OS. On Windows 7, the license file will be stored in the folder
C:\ProgramData\LMS\Licensing. On Windows XP this will be C:\Documents and
Settings\All Users\Application Data\LMS\Licensing.
• Alternatively, you can override the default place, and browse to any other existing
folders.
If you have no license file yet, you can leave the input field for the license file
blank. The installer will point to the selected destination folder and once you
retrieve the license file, you can copy it into this folder manually. To easily
retrieve this folder, the installer creates a shortcut to access it from the Start >
LMS RLM 9.3.0 License Server >Tools >LMS license folder menu.
From the RLM web-interface or from command lines (see License management for more details),
it is possible to shut down the license server. The check box can be selected to disable this
possibility.
You can also define the places where the log files of both the server (rlm.exe) and the daemon
(LMS.exe) are stored.
Selecting the check box will launch the FLEXNet installation package for dongles. With this, you
will have support for recent dongles. Although the installation is based on RLM, we keep
supporting FLEXNet dongles.
Selecting the check box will alter the firewall settings on your computer. The daemon will be
allowed to pass the firewall for domain, home/work and public.
Click Install to start the installation. A status screen shows progress of the installation process. At
the end of the process, you will see a screen indicating that the installation is complete. Click
Finish to complete the license server installation. You do not need to reboot your machine.
Under Linux:
Before you can start any LMS Amesim application, you must place a copy of the license file
(renamed as LMS.lic) in the licensing subfolder of the LMS Amesim installation, and the license
manager daemon must be started by the command:
lmstart
The lmstart script is in the $AME/licensing directory. You can check the
$AME/licensing/lmslm_hostname.log file to check that the license server is running correctly.
To ensure that the license manager daemon starts at boot time, add the following startup
command to a boot script on your system as described hereafter (as one line):
where username is a non-privileged user and AMEHOME the LMS Amesim installation directory.
This includes:
This section is intended to give the system administrator a general overview of RLM and how
licenses are managed.
• Under Windows: On the LMS Amesim DVD there is a folder named LicensingTools
that contains a command file named hostids.bat and two executables called
rlmhostid.exe and lmshostid.exe. Copy these files to a temporary folder and execute
the command hostids.bat. This command will create a file named hostids.txt which will
contain the data used for establishing the license file.
• Under Linux: On the LMS Amesim DVD there is a directory named LicensingTools/lnx
that contains an executable named rlmhostid. Copy this file to a temporary directory
and execute it: this command will display the data used for establishing the license file.
Any time you make changes to the license file, you must reread the license file
or restart the license daemons by running lmstop and then lmstart. These utilities
are available in the licensing folder of LMS Amesim. Alternatively, the web-
server application can be used. For more information, please refer to the section
License administration tools.
For a complete description of the license file, please refer to the License File section of the RLM
End-User Manual (RLM_Enduser.htm) which lives in the EndUser subfolder of the LMS Amesim
licensing folder.
• A list of full paths to license files (including the name of the license files), these are separated
by a colon ( : ) on Linux or a semicolon ( ; ) on Windows.
• A list of port@host where port and host are the TCP/IP port number and the host name from
the HOST line in the license file. Alternatively, use the shortcut specification, @host, if the
license file HOST line uses the default TCP/IP port (5053). A list of several port@host can be
used for a server redundant configuration. For example:
port1@host1: port2@host2
or
port1@host1; port2@host2
You can create a list containing both port@host and full license path files.
When several license files or hostnames are set, LMS Amesim licenses are first taken from the
first license or hostname of the list.
The licensing folder contains a template (named lms.opt) which contains the
following command:
TIMEOUTALL 900
To use these options, you or your users can create local options files. For a complete description
of the options files, please refer to the RLM Options File and ISV Options File sections of the
RLM End-User Manual (RLM_Enduser.htm) which lives in the EndUser subfolder of the LMS
Amesim licensing folder.
LMS Amesim is only able to generate C code and consequently only needs a C compiler.
LMS Ameset can, in addition, manage also Fortran code for submodels.
While using LMS Amesim and LMS Ameset, you can choose the compiler you want to use from
the Preferences dialog box.
• GNU GCC,
• Microsoft Visual C ++,
• Intel C.
If you plan to use only the GNU GCC compiler, no other configuration is needed since it is
provided in the LMS Amesim distribution.
For the other compilers, if the compiler is installed after the installation of LMS
Amesim, additional setup is needed as described below.
This will take care of the environment variables required by the Microsoft Visual C++ compiler.
In order to use the Simulink interface, you must install Microsoft Visual C++
since the GNU GCC compiler is not compatible with Simulink.
A similar procedure must be applied with the iclvars.bat command file located by default in the
C:\Program Files (x86)\Intel\Compiler\C++\10.0.027\IA32\Bin\ folder.
which cc
or
which gcc
you should see the full path name of the executable cc (or gcc). Otherwise, you need to include
the path for the C compiler in your .cshrc or.profile file. The same applies to the Fortran compiler
with f77 or g77.
LMS Amesim product releases are available and supported on this platform. You can get
technical support for this platform through the standard support mechanisms.
LMS Amesim product releases are available on this platform but no technical support is
officially available.
New LMS Amesim product releases are no longer available on this platform. Technical
support will be provided as defined in the maintenance contract, depending on version used
and current version.
LMS Amesim is not a native 64-bit application, but can be run with 32-bit
compatibility packages.
Models generated with LMS Amesim can be compiled using a Linux 64-bit compiler.
www.siemens.com/plm/lms