Prescan InstallationGuide
Prescan InstallationGuide
Guide 2020.2.0
Simcenter
Simcenter Prescan
W h ile every preca ution h a s been ta ken in th e prepa ra tion of th is docum en t, th e publish er
a n d th e a uth or a ssum e n o respon sibility for errors or om ission s, or for da m a ges resultin g from
th e use of in form a tion con ta in ed in th is docum en t or from th e use of progra m s a n d source
code th a t m a y a ccom pa n y it. In n o even t sh a ll th e publish er a n d th e a uth or be lia ble for a n y
loss of profit or a n y oth er com m ercia l da m a ge ca used or a lleged to h a ve been ca used directly
or in directly by th is docum en t.
Contents
1. Prescan Installation Guide 4
1.1 Installation Procedure 5
1.1.1 MATLAB 5
1.1.2 Prescan 6
1.1.3 Prescan for Linux and Prescan Real-Time 13
1.1.4 Prescan Cluster Solution 17
1.1.5 Graphics Card Configuration 17
1.1.6 3rd Party Products 24
1.2 Licensing 24
1.2.1 Licensing Set Up 25
1.2.2 Managing the License Server 25
1.2.2.1 Installing the License Server 25
1.2.2.2 Administrating the License Server 26
1.2.3 License Troubleshooting Guide 26
Introductionary Remarks
A d m inistr a to r R ig hts
Note: To be able to install the Prescan application and to install licenses, you need to have administrator
rights on the computer where the application is installed.
M ultip le P r e sc a n ve r sio ns
Multiple Prescan versions may exist on your computer starting Prescan R5.2. Please take care you select a new
directory for your experiments such that the experiments created with the older version are not overwritten.
U ninsta ll
Prescan can be uninstalled using the normal uninstall option of your Windows version.
It may happen that some files could not be deleted because they were in use by other programs during uninstall.
They need to be deleted manually.
P r e sc a n Lic e nse M o d e l S um m a r y
The license server keeps track of all Prescan licenses and handles requests from network users who want to run
Prescan, granting authorization to the requesters to allow them to run Prescan, and denying requests when all
licenses are in use. When one of the existing users exits Prescan, his license is freed and made available for the
next user.
It is possible for the Prescan application and the license manager to run on the same system. In this case the
network address of this system needs to be entered when installing the Prescan application in network license
mode.
N o n-W e ste r n I nsta lla tio n
Note: Please do not use non-western characters (e.g. Japanese, Korean, Chinese, etc.) in the installation
path(s).
Manual | Simcenter Prescan
Before following the installation procedure, please read the Introductionary Remarks, and check if your system
fulfills the System Requirements.
Step 5: Install any of the optional components or 3rd party products described in 3rd Party Products.
1.1.1 MATLAB
MATLAB and Simulink must be installed on the system if Prescan is to be used for simulation. If MATLAB/Simulink
has not yet been installed, install the product using the installation procedure as provided with the MATLAB
product.
Note: See System Requirements for the compatibility table between Prescan 2020.2.0 and MATLAB/Simulink.
It is mandatory to have a supported compiler installed.
MATLAB path
If a previous Prescan installation was used on the PC, and the MATLAB path was modified using the 'Set Path'-
option under the File menu in MATLAB, it is possible that some references to old Prescan installation paths exist in
the MATLAB path. They should be manually removed using the 'Set Path'-option under the File menu in MATLAB.
A benefit of making a local copy of MATLAB for all users of the network license is that MATLAB uses in this case the
files on your local drive, therefore reducing network use and increasing speed.
1.1.2 Prescan
Prescan installation will begin with the welcome window as shown below. Please read the information shown
and press next if you are ready to continue with the installation.
Prescan Welcome
Now the installation of your new Prescan version will take place in a number of steps.
Next the destination installation directory needs to be defined. Note that a full Prescan installation requires
approximately 1,6 GB of disk capacity.
Manual | Simcenter Prescan
A choice is offered which components should be installed. The remainder of this guide assumes that a full
installation is chosen.
Library folders need to be defined for User Defined elements, for Generic Vehicles and for Generic Models.
Prescan will look here for libraries added by the user. It is advised to use the proposed directory so all users can use
each others elements. This directory can later be changed in the GUI.
Manual | Simcenter Prescan
Prescan requires an installed MATLAB application for its simulations. If not present the user can skip the MATLAB
step.
If a MATLAB version is to be used the user needs to specify where the version can be found.
A directory must be configured that Prescan will use to store new experiments.
Manual | Simcenter Prescan
The Demo Experiments and Test Scenarios can be extracted to the Experiments Destination Folder.
Note: Do not use space characters (' ') in experiment names or experiment location names.
Prescan 2020.2.0 works with Siemens PLM licensing tools. For set up please refer to Managing the License Server
for more information on how to set up the licensing mechanism. Important during installation is to add the
license server if not yet present. This is done by adding ";28000@<license server name>".
Manual | Simcenter Prescan
Note: By entering the license server, the installer will create the environment variable
SPLM_TASS_LICENSE_SERVER. Prescan will use the variable to identify where the license server is located.
Now indicate what the name is for Prescan in the Start Menu Folder.
Finally, check the installation settings and correct if needed by clicking the <Ba ck> button to the appropriate
dialog. The In sta ll button will start the installation with the given settings.
Installation in progress
Installation finished
Note 1: To be able to use Prescan Real-Time on a Concurrent RedHawk system, the Concurrent SimWB
Control Center with the ML Toolkit need to be properly installed on the Windows host system. Refer to SimWB
installation manual for installation instructions.
Note 2: To be able to use Prescan Real-Time on an ETAS RTPC, the LABCAR-OPERATOR and Experiment
Environment need to be properly installed on the Windows host system. Refer to the ETAS installation manual
for installation instructions.
Prescan for Linux is a solution for running compiled Prescan experiments on a CentOS 7.2 Linux system.
Prescan Real-Time is a solution to run on real-time in the following supported platforms:
National Instruments PXI Controllers;
Manual | Simcenter Prescan
Concurrrent RedHawk;
ETAS RTPC.
Both Prescan for Linux and Prescan Real-Time share a single installer.
The following installation instructions are valid for both Prescan for Linux and Prescan Real-Time.
Note: Prescan for Linux has only been tested on CentOS 7.2. It might also work on other Linux distributions
but we advise to use Docker containers to run Prescan for Linux on other Linux systems.
Log in and run the installer in the temporary directory as root. Use the --target option to specify the target
system Prescan is being installed on. See the next section for a list of targets and other installation options.
Edit or create the file /etc/profile.d/lm.sh and make sure the following line is present:
export SPLM_TASS_LICENSE_SERVER=port@host
Where host and port are the hostname and port number of the license server. See Licensing for more
information.
Manual | Simcenter Prescan
Installation Options
The Prescan linux Installer accepts a number of options to control the installation process:
-h, --help Shows all options with a short description of their use
--target=<target_name> Specify the target Prescan is being installed on. The supported targets are n a tion a l-
in strum en ts, con curren t, eta s and cluster. This option will trigger additional installation
steps necessary for each target.
--skip-config Do not write the current configuration to /etc/xdg. This configuration file is used by
Prescan to locate its components and data. If this configuration step is skipped, manual
verification of the current file is needed to ensure it is configured to use the new
installation.
--skip-service Skip installation of the background service file. The DeploymentService can run as a
background process (started manually, or at system start). In order to facilitate this a
configuration file is installed. Use this option to suppress installation of this file.
--skip-user Skip the creation of a prescan user and group, and corresponding /home/prescan folder.
Use this option if there is already a prescan user, group and home directory present that
is already used for another purpose, and was not created by a Prescan installer.
--prefix=dir Specify the root installation directory for Prescan. By default, Prescan is installed in /
usr/local. Using this option will install Prescan in the specified dir instead.
--postfix=name Specify a custom postfix to the default installation folder name. By default, Prescan is
installed in a folder named Prescan_2020.2.0. To facilitate multiple side by side
installations, a postfix can be added to this name.
For example, using --postfix=-demo would use Prescan_2020.2.0-demo as the
installation folder name.
--force-install Use this option to overwrite an existing Prescan installation. When this option is
specified, the existing installation directory is removed before installing Prescan again.
It is imported to note that this only applies to installations of Prescan with the same
version, and prefix and postfix settings.
--install-minimal Install only Prescan libraries and header files. Use this option to cross compile
experiments in Windows for a Linux target. When this option is used, --skip-config, --skip-
service, and --skip-user are automatically set. The --prefix and --postfix options can be
used in combination with this option.
$ ./Simcenter-Prescan-2020.2.0-Linux-x86_64-installer.sh --install-
minimal --prefix=/mnt/c/build/17.0/x64/sysroots/core2-64-nilrt-linux/usr/local/
The postfix and prefix options used in the installation of Prescan Linux on Windows shall be identical to the options
used when installing Prescan Linux in the PXI Controller. The only difference is that the installation in Windows
shall use the sysroot directory of the cross compile toolchain as the root directory. If the toolchain directory does
not exist, make sure you install the C/C++ Development Tools as specified in the Section System Requirements for
Prescan software.
E r r o r d ur ing b uild ing o f p la tfo r m d e p e nd e nt lib r a r y w he n using --ta r g e t=c o nc ur r e nt w ith sud o
Building of the platform library uses the SIMWB_ROOT environment variable to locate the Prescan installation.
When using sudo to install Prescan, this variable is not properly propagated to the installer. To resolve this use
the -E option with sudo to forward all current environment variables. Also use the --force-install option to
make sure the new installation overwrites the former one: sudo -E Simcenter-Prescan-2020.2.0-Linux-
x86_64-installer.sh --force-install.
error while loading shared libraries: libGLU.so.1: cannot open shared object file:
No such file or directory
This is due to the missing libGLU library, which can be resolved by installing it using the local package manager.
E r r o r d ur ing r unning the D e p lo ym e nt S e r vic e
When running the Deployment Service in Prescan Linux, the following error may occur:
error while loading shared libraries: libgomp.so.1: cannot open shared object file:
No such file or directory
This is due to the missing libgomp library, which can be resolved by installing it using the local package
manager.
$ ./Simcenter-Prescan-2020.2.0-Linux-x86_64-installer.sh --install-
minimal --prefix=/mnt/c/build/17.0/x64/sysroots/core2-64-nilrt-linux/usr/local/
The postfix and prefix options used in the installation of Prescan Linux on Windows shall be identical to the options
used when installing Prescan Linux in the PXI Controller. The only difference is that the installation in Windows
shall use the sysroot directory of the cross compile toolchain as the root directory. If the toolchain directory does
not exist, make sure you install the C/C++ Development Tools as specified in the Section System Requirements for
Prescan software.
Install the latest drivers for your graphics card, which can be found on the website of your graphics card
manufacturer. Make sure you reboot after installing the new drivers. After the reboot, start the Prescan Viewer
and click on the About menu item:
Your graphics card information will now be listed as in the figure below. It will show either an AMD or a NVIDIA
graphics card.
With the latest drivers installed, Prescan will typically use the dedicated graphics card automatically. However,
Windows might still force (parts of) Prescan to use the on-board GPU even when a dedicated graphics card is
present. For NVIDIA graphics cards there is a simple solution. In the N V ID IA con trol pa n el -> M a n a ge 3D Settin gs,
you can configure the system to use the NVIDIA card by default.
Manual | Simcenter Prescan
Anti-aliasing settings
Note: Anti-aliasing is of specific importance for white line detection with a camera system. Without anti-
aliasing, lines further away might 'flicker' (appear and disappear from view) whereas with anti-aliasing turned
on, they will remain in view.
Computer screens that display images use a limited number of pixels. As a result, shapes (e.g. circles, lines) are
displayed with jagged edges. This jagged shape is known as aliasing or ja ggies.
Manual | Simcenter Prescan
We can suppress these ja ggies using a technique called anti-aliasing (AA). In practice, there is not much
improvement when going from an AA factor of 2 to 4 or higher. It is therefore advised to have a default setting of
2 which can be accessed through Settings -> Preferences -> Visualisation Settings. The chapter Visualization
Settings provides more info on anti-aliasing.
Manual | Simcenter Prescan
In order for these settings to have an effect, make sure your graphics card is configured to use the application-
specific AA settings. This is shown in the images below.
Manual | Simcenter Prescan
Threaded optimisation
NVIDIA GPUs have a driver feature called Th rea ded optim isa tion , which can cause problems with the Prescan
Manual | Simcenter Prescan
Viewer and/or the Remote Viewer Federate. For systems with NVIDIA Titan GPUs, this feature needs to be turned
off. You can turn Th rea ded optim isa tion off in the N V ID IA con trol pa n el -> M a n a ge 3D Settin gs.
Note: Make sure you close and then restart the Prescan Viewer in order for the change to take effect.
Typical 3rd party products to be installed with Prescan but which need a special connection to Prescan are:
CarSim
Install the product using the installation procedure as provided with the product. More information about the
connection method can be found in the following section Connection to 3rd Party - CarSim.
LabView
Install the product using the installation procedure as provided with the National Instruments product. More
information about the connection method can be found in the following section Connection to 3rd Party -
LabView.
VeDYNA
Install the product using the installation procedure as provided with the Tesis - DYNAWare product. More
information about the connection method can be found in the following section Connection to 3rd Party -
VeDYNA
1.2 Licensing
This document contains information regarding the license system used to run Siemens products.
The licensing documentation will refer to installdir. This directory is platform specific and refers to the following
default installation paths:
Windows: C:\Program Files\Simcenter Prescan\Prescan_2020.2.0\
Linux: /usr/local/Prescan_2020.2.0/
Licensing Tools
The licensing tools are distributed via the regular installer and can be found at: installdir > Licensing
Licensing tools are also available via the Siemens PLM Download Server at https://
download.industrysoftware.automation.siemens.com/:
Obtaining a license
The license(s) for Siemens products will be delivered after completing the purchase order for Prescan.
If you are an existing customer using previous versions of Prescan (2019.3 and older) please contact your sales
representative.
In the course of requesting a license a 'CID' may be requested. This tool is included in the Prescan installation and
can be found in:
A. installdir > Licensing > utilities > win64 > getcid.exe for Windows
B. installdir > Licensing > utilities > linux-x86_64 > getcid for Linux
C. Using your Webkey see Licensing Tools
Note: The SPLM_TASS_LICENSE_SERVER environment variable will also be automatically set by the Prescan
installation process.
The Siemens PLM License server installation software can be found at installdir > server_installations
The Windows Prescan installer contains both the Windows and Linux Siemens PLM Licensing installers.
In order to control the operation of lmgrd from the LMTOOLS user interface, you must first install the PLM License
Server. Follow the procedure in Installing the License Server before proceeding.
After installation please refer to installdir > Licensing > documentation > SPLMLicensing_user_guide.pdf
3. Considerable delays in start up of the applications have been noticed if the license file contains license strings
of which the end date has expired.
4. Considerable delays in start up of the applications have been noticed if nonexistent servers are assigned to the
SPLM_TASS_LICENSE_SERVER environment variables or even in the registry.
5. The questions below have been taken from the FLEXlm™ user guide and are important when you have
questions for Siemens First Line Support:
6. Set the environment variable FLEXLM_TIMEOUT to 10000000. Its value is in microseconds and corresponds to
10 seconds. As the name suggests it sets a timeout value of 10 seconds to contact the FLEXlm™ server. This
should be considered to be a last resort in case of failing license checkouts.
7. Further FlexNet documentation is included in installdir > Licensing > documentation > fnp_LicAdmin.pdf
Manual | Simcenter Prescan
P r o c e sso r :
Minimum required CPU: Intel Core2Duo E8400, or equivalent.
Note: Due to the memory requirements of the application it is highly recommended to use 64bit systems with
at least 8GB of memory.
V id e o Ca r d s:
All video cards need to support OpenGL 4.2 and GL shading language 4.20. They can be of any brand (NVIDIA,
AMD). Remember to always install the latest driver versions that are available for you system. In house tested are
the following cards:
Note: Integrated chipsets (eg. Intel HD graphics) have in general a very limited specification due to which
the Prescan Prescan Viewer may fail to run or results are incorrect. The use of systems with this type of
graphics hardware is discouraged.
S c r e e n R e so lutio n:
In order to have a correct view of scenarios, menus and 3D view, a minimum screen resolution of 1280x1024
pixels is required.
Note: Remote desktop can not be used in combination with Prescan 3D Visual Viewer. The application may
block or crash in an attempt to do so.
Manual | Simcenter Prescan
Software requirements
S up p o r te d O S :
o Windows 64bit: 7/8.1/10
O the r :
The table below shows the compatibility of Prescan with MATLAB/Simulink versions. General notes unrelated to
MATLAB versions are stated below the table as well.
National Instruments:
o National Instruments PXI Controller with NI Linux Real-Time
o VeriStand 2018 SP1
o VeriStand 2018 SP1 Model Framework f1 patch
o C/C++ Development Tools 2017 (provided by National Instruments)
o A MATLAB version supported by both Prescan 2020.2.0 and VeriStand
o Linux Bash shell for Windows (only supported on Windows 10)
Note: The following link shows the compatibility between VeriStand and MATLAB versions: https://
www.ni.com/en-us/support/documentation/compatibility/17/veristand-version-compatibility.html
Concurrent:
o Concurrent iHawk hardware platform (or a platform compatible with Concurrent RedHawk Linux)
o Concurrent RedHawk Linux 7.2 [on the real-time hardware platform]
o Concurrent Simulation Work Bench (SimWB) version 2017.1.0
o Concurrent MATLAB Toolkit (ML Toolkit) installed as part of the SimWB installation
Note: Matlab versions 2017a and higher are not compatible with SimWB 2017.1.0
ETAS:
o ETAS RTPC v6.2.2
o ETAS LABCAR-OPERATOR 5.4 with ETAS Experiment Environment
Note: Not all versions of Matlab are supported by LABCAR-OPERATOR. Use the ETAS "Matlab Version Selector"
tool to select a Matlab version which is also supported by Prescan. This tool is part of the installation of
LABCAR-OPERATOR.
Compatibility Requirements
Prescan 2020.2.0 is compatible with the following MATLAB/Simulink releases:
Manual | Simcenter Prescan
Note 1: Prescan is compatible with Windows 7, 8.1 & 10 for the user profiles Administrator and User. It is
not compatible with the profile Guest, due to file restrictions.
Note 3: For 64-bit platforms an additional requirement needs to be fulfilled to run Simulink models in general.
A C/C++ compiler does not come standard with the MATLAB for 64-bit platforms. The presence of a compiler
can be verified and updated by executing "mex –setup" or "mex –setup C" and "mex –setup C+
+" in a MATLAB command window. For Matlab 2014b and higher, the Microsoft Windows SDK 7.1 (and the
.NET Framework 4) will suffice. This can be found here:
http://www.microsoft.com/en-us/download/details.aspx?id=8279
With the introduction of MATLAB R2015b, the MinGW-w64 compiler is supported. This compiler is available at
no charge.
Please refer to The MathWorks documentation for supported compilers for your version of MATLAB/Simulink.
In particular, pay attention to the C/C++ compiler versions required by the Simulink Coder, which may have
different compatibility requirements than the other MATLAB components. Incompatible C/C++ compilers may
not give any warnings/errors when working with Prescan Real-Time work flow, but they will result in
undefined behavior when compiling/running the generated code on the real-time target.
Note 4: When different versions of MATLAB are installed on the same machine, it is possible that they require
different versions of MinGW. This is the case for MATLAB R2015b, where MinGW 4.9.2 is used, and MATLAB
2017b which requires MinGW 5.3. In this case, one must pay special attention to the system environment
variable MW_MINGW64_LOC, which holds the path to the installed MinGW compiler. MATLAB reads its value
to select the MinGW version to use. In many versions, MATLAB only updates the value of the environment
variable when installing the MinGW compiler. This means that when switching between MATLAB versions
MW_MINGW64_LOC could hold the path to the wrong MinGW version.
The workaround for this is to manually check the value of the environment variable when starting up
MATLAB. This can be done with getenv('MW_MINGW64_LOC'). The typical installation directories are:
- MinGW 4.9.2 - C:\M ATLAB\SupportP a cka ges\R2015b\M W _ M in G W _ 4_ 9
- MinGW 5.3 - C:\P rogra m D a ta \M ATLAB\SupportP a cka ges\R2017b\3P .in strset\m in gw_ w64.in strset
In recent versions (R2017b and later) this problem does not occur as MATLAB checks its version on start-up
and updates MW_MINGW64_LOC accordingly. Still, we advise the users to do their own verification and from
there learn from experience how MATLAB is selecting MinGW.
When MATLAB is started for Prescan, using the Prescan Process Manager, the Prescan GUI or otherwise, the
whole Prescan environment is passed to MATLAB and with it MW_MINGW64_LOC. This implies that every
time MATLAB is restarted without restarting the process from which it was started (Prescan Process Manager
or other), the original environment will be again passed to MATLAB, and any changes made in the previous
MATLAB session are not taken into account. For this reason, if MinGW has been installed on a MATLAB
session which has been closed and another session is started from the same Prescan Process Manager
instance (or other process from which MATLAB was started), MATLAB will still not know the new value of
MW_MINGW64_LOC. The same applies for when uninstalling MinGW. For this reason, in these cases, the
Prescan Process Manager (or, again, any other process from which MATLAB was started) must be terminated
and restarted too.
Note 5: MATLAB 2015a should work with Prescan. However, only MATLAB 2015a SP1 is officially supported.
Manual | Simcenter Prescan
Index
System Requirements 27
Vedyna 24
-3- Verification of system settings 17
Vertical synchronization 17
3rd Party Products 24
Installation Procedure 5
-A-
-L-
Administrator Rights 4
Labview 24
Anti-aliasing 17
License 24
Floating 4
-C- License Server Manager 24
Management 24
CarSim 24 Models 24
Codec 24 Network 4, 24
Compatibility Node-locked 4
MATLAB 28 Obtaining 24
Stand-alone 4, 24
Type 4
-D- Licensing
dSPACE ControlDesk 24 Tools 24
-F- -M-
FlexLM 24 MATLAB 28
Installation 5
Network License 5
-G- Upgrading version 6
Google SketchUp 24
-S-
-H- Sketchup 24
Software Requirements 28
Hardware Requirements 27
System Requirements 27
Hardware 27
Software 28
-I-
Installation 4
3rd Party Products 24 -U-
Anti-aliasing 17
Uninstall 4
CarSim 24
Codec 24
dSPACE ControlDesk 24
-V-
Google SketchUp 24
Guide 4 Vedyna 24
Improve performance 17 Vertical synchronization 17
Labview 24
Prescan 6
Prescan Real-Time 13
Procedure 5
Manual | Simcenter Prescan
C5 7/19 C