Installation Guide
Installation Guide
Installation Guide
Version 7.5.1
All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic,
electronic, or mechanical, including photocopying, recording, taping, or information storage and
retrieval systems - without the written permission of the publisher.
Products that are referred to in this document may be either trademarks and/or registered
trademarks of the respective owners. The publisher and the author make no claim to these
trademarks.
While every precaution has been taken in the preparation of this document, the publisher and the
author assume no responsibility for errors or omissions, or for damages resulting from the use of
information contained in this document or from the use of programs and source code that may
accompany it. In no event shall the publisher and the author be liable for any loss of profit or any
other commercial damage caused or alleged to have been caused directly or indirectly by this
document.
Installation Guide
Table of Contents
1.
1.1
1.1.1
1.1.2
1.1.3
1.1.4
1.2
1.2.1
1.2.2
Installation Procedure
MATLAB
PreScan
4
5
5
6
14
16
Licensing
17
Licensing Set Up
17
18
1.2.2.1
18
1.2.2.2
1.2.2.3
19
20
20
1.2.3
1.3
21
1.4
26
Installation Guide
The installation guide guides you through the installation procedure. The following topics are being dealt with:
Installation Procedure
Licensing
System Requirements
Installation Procedure Flowchart
Introductionary Remarks
Administrator Rights
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.
Multiple PreScan versions
Multiple PreScan versions may exist on your computer starting PreScan R5.2.0. Please take care you select
a new directory for your experiments such that the experiments created with the older version are not
overwritten.
Uninstall
PreScan can be uninstalled using 'Add or Remove Programs' in the Windows Control Panel or via the Start
Menu by selecting Uninstall PreScan.
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.
PreScan License Model Summary
Description
Requires
Stand-alone
(nodelocked)
- License code
- Flexnet license server
Network
(floating)
- License code
- Installation of Flexnet
license server
With an external license manager running on a server in a network, PreScan can run on multiple computers
which are part of this network. PreScan (and MATLAB) still need to be installed locally conform the system
requirements.
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.
Non-Western Installation
Installation Guide
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 1: See System Requirements for the compatibility table between PreScan 7.5.1 and MATLAB/
Simulink.
Note 2: If you want to use dSPACE ControlDesk in combination with PreScan, the name of the MATLAB
installation directory must NOT contain space characters. Hence, do not install MATLAB in the Program
Files directory!
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.
Installation Guide
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 Welcom e
Now the installation of your new PreScan version will take place in a number of steps.
Installation Guide
Next the destination installation directory needs to be defined. Note that a full PreScan installation requires
approximately 1,6 GB of disk capacity.
A choice is offered which components should be installed. The remainder of this guide assumes that a full
installation is chosen.
Installation Guide
Library folders need to be defined for User Defined elements and for Generic Vehicles. 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.
Installation Guide
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.
Installation Guide
A directory must be configured that PreScan will use to store new experiments.
The Demo Experiments and Test Scenarios can be extracted to the Experiments Destination Folder.
Installation Guide
10
PreScan 7.5.1 works with Flexera's FlexNet 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 ";27000@<license server name>" or just ";
@<license server name>".
Note: By entering the license server, the installer will create the environment variable
MADLIC_LICENSE_FILE. 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.
Installation Guide
11
Finally, check the installation settings and correct if needed by clicking the <Back > button to the appropriate
dialog. The Install button will start the installation with the given settings.
Installation Guide
12
Installation in progress
The installation displays the readme file with some pointers to where to get help if the installation fails or the
the application refuses to start.
Installation Guide
13
Installation finished
1.1.3
This section describes how the performance of PreScan can be improved by verifying some System Settings.
Note: Video cards should receive regular updates of their drivers since it has been noted that bugs in the
drivers are the cause of wrong simulation results.
Note: Anti-aliasing is of specific importance for white line detection with a camera system. Without
anti-aliasing, lines further away will 'flicker' (appear and disappear from view) whereas with anti-aliasing on
they will remain in view.
Installation Guide
14
Using a technique called anti-aliasing we can suppress these jaggies. 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.
Note:
Make sure you close and then restart the visualization viewer in order for the change to take effect.
Furthermore, make sure your video card's anti-aliasing mode is application controlled as is shown here
in the NVIDIA Control Panel below.
Installation Guide
15
1.1.4
Installation Guide
16
1.2.1
Licensing Set Up
Obtaining a license
The various licenses for TASS products can be retrieved via your local sales representative. The tools,
applications, and libraries needed for the license server are part of the distribution and packaged in a separate
subdirectory. The directory is named installationdir/platformid/fnp.
Installation Guide
17
1.2.2
This section provides procedural information on how to configure and manage the License Server Manager as a
service.
1.2.2.1
To configure a license server system as a service, you must have Administrator privileges.
To configure a license server system as a service:
1. Run the file lmtools.exe which can be found in the folder C:\Program Files\PreScan\PreScan_7.5.1\bin
2. Click the Configuration using Services button, and then click the Config Services tab.
3. In the Service Name, type the name of the service that you want to define, for example, PreScan license
server.
4. In the Path to the lmgrd.exe file field, enter or browse to lmgrd.exe for this license server system.
5. In the Path to the license file field, enter or browse to the license file for this license server system. A
default license file is prepared when using Consumable token licenses only. The PreScan version is
available in the installationdir\license\default.lic file, where installationdir refers to the location where
PreScan is installed. For example: C:\Program Files\PreScan\PreScan_7.5.1\bin
Note: The licenses are provided via the local sales representative.
6. In the Path to the debug log file, enter or browse to the debug log file that this license server system
writes. Prepending the debug log file name with the + character appends logging entries. The default
location for the debug log file is the c:\Windows\System32 folder. To specify a different location, make sure
you specify a fully qualified path. Note that the log file is not automatically created. It needs to be created by
hand.
7. Please check the boxes Use Services and Start Server at Power Up
8. To save the new PreScan license server service, click Save Service.
Installation Guide
18
A graphical user interface to the license server manager tools is provided called LMTOOLS. Some of the
functions LMTOOLS performs include:
o
o
o
In order to control the operation of lmgrd from the LMTOOLS user interface, you first must configure it as a
license server manager service. Follow the procedure in Configuring the License Server Manager as a Windows
Service before proceeding.
Once the license server manager service is configured, lmgrd is started by starting the service from the
LMTOOLS interface.
To start the service from the LMTOOLS interface:
1. Start LMTOOLS.
2.
3.
Select the service name from the list presented in the selection box. In this example, the service name
is PreScan license server.
4.
5.
The PreScan license server system starts and writes its debug log output to the defined logfile.
Installation Guide
19
In order for lmgrd, and hence the license server system, to start up automatically at system start-up time, you
first must configure it as a license server manager service. Follow the procedure in Configuring the License
Server Manager as a Windows Service before proceeding, and then continue with the steps below.
To configure lmgrd as a license manager service:
1.
With LMTOOLS started and the desired service name selected, click the Config Services tab.
2.
Make this license server manager a Windows service by selecting the Use Services check box
(otherwise, it becomes a FLEXnet Licensing service).
3.
Configure it to start at system startup time by selecting the Start Server at Power Up check box.
From now on, when the machine is rebooted, this license server manager starts automatically as a Windows
service
1.2.3
1. Make sure that your FLEXlm license server is the latest available version
2. The environment variable MADLIC_LICENSE_FILE or ALTAIR_LM_LICENSE_FILE should be set to
<portnumber>@<hostname>; portnumber is the connection port number of the license server, where
hostname is the name of the license server without the domain name. See the first line in the license file for
these details Note that the first hostname should be <portnumber>@localhost. This will enforce to look
locally on your system if the machine is detached from the network.
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 MADLIC_LICENSE_FILE 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 TASS First Line Support:
What kind of machine is your license server running on?
What version of the operating system?
What machine and operating system is the application running on?
What version of FLEXlm does the FLEXlm-licensed application use? Use the lmver script, or, on Linux,
execute the following command on your lmgrd, vendor daemon, and application: strings binary_name |
grep copy. Alternatively, lmgrd -v gives the lmgrd version, and this works with the vendor daemon also.
o What error or warning messages appear in the log file?
o
o
o
o
Installation Guide
20
21
Did the server start correctly? Look for a message such as: server xyz started for: feature1 feature2.
What is the output from running lmutil lmstat -a?
What is the output from running serveractutil view?
Are you running other products which are also licensed by FLEXlm?
Are you using a combined license file or separate license files?
Are you using a three-server redundant license server (multiple SERVER lines in your license file)?
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.
Hardware requirements
Processor:
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.
Series
Driver version
nVidia
189.99 or later
GeForce 310M
189.99 or later
189.99 or later
GeForce GT 650M
189.99 or later
189.99 or later
347.52
Radeon HD 6790
Radeon HD 7670M
Radeon HD 7690M
Radeon HD 7870
Radeon R9 290
14.12
AMD/ATI
Note 1: It is advised to buy equipment of which the Graphics hardware supports OpenGL3.x and the
Installation Guide
22
Screen Resolution:
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.
Software requirements
Supported OS:
o Windows 32bit: XP/Vista/7
o Windows 64bit: XP/Vista/7
Note 1: It is possible to install PreScan 32bit on a 64bit platform. This enables the coupling of PreScan
with 3rd party software only delivered as 32bit installer. It is however highly recommended to use PreScan
64bit on a 64bit platform if there is no direct need to use the 32bit version.
Note 2: Both the 32bit version and the 64bit version of a PreScan release should not be installed on the
same system.
Other:
o Engineers control system modeling tool: 32-Bit and 64-Bit MathWorks Products MATLAB / Simulink
o Optional: engineers experiment run-time control and data acquisition tool: dSPACEs ControlDesk or
National Instruments' LabVIEW
The table below shows the compatibility of PreScan versions with MATLAB/Simulink versions:
Compatibility Requirements
PreScan 7.5.1 is compatible with the following MATLAB/Simulink releases:
Versions
Build-No.
Release 7.4.0
32/64 bit
Windows
MATLAB
32/64 bit
7 / 8.1
2010b Note 4
2011 a/b
2012 a/b Note 5/6
2013 a/b
Installation Guide
23
8564 (88566d0e4b62)
32/64 bit
7 / 8.1
2010b Note 4
2011 a/b
2012 a/b Note 5/6
2013 a/b
2014 a/b
Release 7.2.0
8261 (5bf8faf4fe03)
32/64 bit
7 / 8.1
Release 7.1.4
7785 (aa2497b00195)
32/64 bit
7 / 8.1
Release 7.1.3
7764 (f50b7d24f8d1)
32/64 bit
7 / 8.1
Release 7.1.2
7749 (7c52d2055336)
32/64 bit
7 / 8.1
Release 7.1.1
7751 (42c20f6c76d4)
32/64 bit
7 / 8.1
Release 7.1.0
7742 (f78e6709c7e4)
32/64 bit
7 / 8.1
Release 7.0.1
7279 (61094a278805)
32/64 bit
Vista/7
Release 7.0.0
7192 (5ab02635f321)
32/64 bit
Vista/7
Release 6.9.0
6643 (18cb8ac104c3)
32/64 bit
Vista/7
2009a/b
2010a/b Note 4
2011a/b
2012a/b Note 5/6
Release 6.8.1
Installation Guide
6510 (e170cc99acbf)
32/64 bit
XP/Vista/7
2009a/b
24
6268 (ea760ffd6f39)
32/64 bit
XP/Vista/7
2009a/b
2010a/b Note 4
2011a/b
2012a/b Note 5/6
Release 6.7.0
6002 (48be3d1f9046)
32/64 bit
XP/Vista/7
2009a/b
2010a/b Note 4
2011a/b
2012a/b Note 5/6
Release 6.6.0
5347 (495b31561462)
32/64 bit
XP/Vista/7
2009a/b
2010a/b Note 4
2011a/b
2012a/b Note 5/6
Release 6.5.0
4845 (788d23df80ec)
32/64 bit
XP/Vista/7
2009a/b
2010a/b Note 4
2011a/b
2012a/b Note 5/6
Release 6.4.0
4215 (6243aade0f25)
32/64 bit
XP/Vista/7
2009a/b
2010a/b Note 4
2011a/b
2012a/b Note 5/6
Release 6.3.0
3903 (993b43c7bbfe)
32/64 bit
XP/Vista/7
2009a/b
2010a/b Note 4
2011a/b
2012a/b Note 5
Release 6.2.1
3716 (6dbdd8aba47d)
32/64 bit
XP/Vista/7
2009a/b
2010a/b Note 4
2011a/b
Release 6.2.0
3644 (56bb4c3dccf1)
32/64 bit
XP/Vista/7
2009a/b
2010a/b Note 4
2011a/b
Release 6.1.0
3272 (3eeb53feb6e7)
32/64 bit
XP/Vista/7
2009a/b
2010a/b Note 4
2011a/b
Release 6.0.0
2899 (da1cdf69df3f)
32/64 bit
XP/Vista
2008a/b
2009a/b
2010a/b Note 4
2011a/b
32/64 bit
2009a/b
2010a/b Note 4
2011a/b
Installation Guide
25
2370 (3290cfd6f49a)
32/64 bit
XP/Vista
2008a/b
2009a/b
2010a/b Note 4
2011a/b
32/64 bit
2009a/b
2010a/b Note 4
2011a/b
Release 5.4.0
2196 (a913af061b7c)
32/64 bit
XP/Vista
2008a/b
2009a/b
2010a/b Note 4
2011a/b
32/64 bit
2009a/b
2010a/b Note 4
2011a/b
Note 1: PreScan is compatible with Windows 7 & 8.1 for the user profiles Administrator and User. It is
not compatible with the profile Guest, due to file restrictions.
Note 2: The above mentioned MATLAB versions are the only MATLAB releases tested in combination with
PreScan.
Note 3: For 64-bit platforms an additional requirement needs to be fulfilled to correctly run some of the
demo examples delivered with PreScan. A C compiler does not come standard with Simulink/Stateflow for
64-bit platforms. The presence of a compiler can be verified by executing mex setup in a MATLAB
command window. In general, the appropriate version of the Express Edition of Microsoft Visual Studio with
the accompanying Platform SDK will suffice. Please note that some C compilers will also require the .NET
framework 4.0 to be installed on your PC. This can be found here: http://www.microsoft.com/en-us/
download/details.aspx?id=17851
Please refer to The MathWorks documentation for supported compilers for your version of Simulink:
http://www.mathworks.com/support/compilers/current_release/win64.html
http://www.mathworks.com/support/compilers/previous_releases.html
http://www.mathworks.com/products/matlab/preparing-for-64-bit-windows.html
Note 4: Collision detection is not correctly working for MATLAB 2010b. This is due to incompatibilities
with the Java Runtime Environment as used by MATLAB 2010b.
Note 5: In MATLAB 2012b a new SLX format for Simulink is introduced. PreScan does not support this
format, but supports the MDL format instead.
Note 6: MATLAB 2011a, MATLAB 2012 (a/b) and MATLAB 2013a ship a Java archive file that conflicts
with the PreScan installation. To solve the conflict where Simulink crashes, MATLAB's static java class
path needs to be changed:
- Edit the following file with administrator rights (please do not use Notepad due to wrong line ending
represenation! Wordpad is ok):
<matlabroot>\toolbox\local\classpath.txt
- Look for the following line:
$matlabroot/java/jarext/protobuf.jar
- Change the line into:
# $matlabroot/java/jarext/protobuf.jar
Note 7: When saving a Simulink model from MATLAB 2010a to MATLAB 2012b+, Simulink may report
Installation Guide
Installation Guide
26
Installation Guide
27
28
Index
Vedyna 16
Verification of system settings 14
Vertical synchronization 14
Installation Procedure 5
Installation Procedure Flowchart 26
16
-A-
-L-
Administrator Rights
Anti-aliasing 14
Labview 16
License 17
Floating 4
License Server Manager
Management 17
Models 17
Network 4, 17
Node-locked 4
Obtaining 17
Stand-alone 4, 17
Type 4
-CCarSim 16
Codec 16
Compatibility
MATLAB 22
-DdSPACE ControlDesk
16
-MMATLAB 22
Installation 5
Network License 6
Upgrading version 6
-FFlexLM
17
-GGoogle SketchUp
-S16
-HHardware Requirements
21
-I-
-U-
Installation 4
3rd Party Products 16
Anti-aliasing 14
CarSim 16
Codec 16
dSPACE ControlDesk 16
Google SketchUp 16
Guide 4
Improve performance 14
Labview 16
PreScan 6
Procedure 5
Procedure Flowchart 26
System Requirements 21
Installation Guide
Sketchup 16
Software Requirements 22
System Requirements 21
Hardware 21
Software 22
Uninstall
-VVedyna 16
Vertical synchronization
14
17