Sie sind auf Seite 1von 300

dSPACE Release

Software Installation
and Management
Guide
Release 7.3 May 2012
How to Contact dSPACE
How to Contact dSPACE Support
There are different ways to contact dSPACE Support:
Visit our Web site at http://www.dspace.com/goto?support
Send an e-mail or phone:
General Technical Support:
support@dspace.de
+49 5251 1638-941
TargetLink Support:
support.tl@dspace.de
+49 5251 1638-700
Use the dSPACE Installation Manager:
On your dSPACE DVD at \Tools\InstallationManager
Via Start Programs dSPACE Installation Manager (after installation of the dSPACE
software)
At http://www.dspace.com/goto?im
You can always find the latest version of the dSPACE Installation Manager here.
dSPACE recommends that you use the dSPACE Installation Manager to contact dSPACE
Support.
Mail: dSPACE GmbH
Rathenaustrae 26
33102 Paderborn
Germany
Tel.: +49 5251 1638-0
Fax: +49 5251 16198-0
E-mail: info@dspace.de
Web: http://www.dspace.com
Important Notice
This document contains proprietary information that is protected by copyright. All rights
are reserved. Neither the documentation nor software may be copied, photocopied,
reproduced, translated, or reduced to any electronic medium or machine-readable form, in
whole or in part, without the prior written consent of dSPACE GmbH.
Copyright 2004 - 2012 by:
dSPACE GmbH
Rathenaustrae 26
33102 Paderborn
Germany
This publication and the contents hereof are subject to change without notice.
AutomationDesk, CalDesk, ConfigurationDesk, ControlDesk, SCALEXIO, SystemDesk and
TargetLink are registered trademarks of dSPACE GmbH in the United States or other
countries, or both. Other brand names or product names are trademarks or registered
trademarks of their respective companies or organizations.
I
3

Software Installation and Management Guide May 2012


Contents
About This Document 9
Document Symbols and Conventions ..................................... 10
Accessing Online Help and PDF Files....................................... 11
Related Documents ................................................................ 13
Safety Precautions 15
General Warning.................................................................... 15
Basics on dSPACE Software Installation 17
Introduction to dSPACE Setup Programs ................................. 18
Important Changes and Improvements to dSPACE Setup ........ 20
Basics on dSPACE License Mechanisms ................................... 23
Features of the dSPACE Installation Manager.......................... 23
Introduction to dSPACE Software Products on
DVD 29
RCP and HIL Software ..................................................................... 31
Product Overview................................................................... 32
Protected Products and Required Licenses .............................. 36
TargetLink Software......................................................................... 40
Software Modules.................................................................. 40
Protected Modules and Required Licenses .............................. 42
ControlDesk Next Generation.......................................................... 45
Software Modules.................................................................. 45
Protected Modules and Required Licenses .............................. 47
Model Compare Software ............................................................... 49
Protected Modules and Required Licenses .............................. 49
SystemDesk Software...................................................................... 50
Setup Components ................................................................ 50
Protected Modules and Required Licenses .............................. 51
AutomationDesk Software .............................................................. 52
Software Versions and Packages............................................. 52
Protected Modules and Required Licenses .............................. 53
Common Software Tools with Own Setup Programs........................ 55
Contents
Software Installation and Management Guide May 2012
I
4

Common dSPACE Software Tools ........................................... 55
Before You Start 59
Installation Workflow............................................................. 60
What Do You Want to Install?................................................ 63
Notes and Tips for Using Multiple Installations on Your Host
PC ......................................................................................... 64
Preconditions for Installing dSPACE Software ......................... 65
How to Check Administrator Rights ....................................... 68
MATLAB Compatibility Information 69
Required MATLAB Releases.................................................... 69
Modifying the MATLAB Installation by dSPACE Software........ 71
Installing Third-Party Software 73
Information About Required Third-Party Software ........................... 74
MATLAB, Simulink, Simulink Coder (formerly Real-Time
Workshop), and Stateflow ..................................................... 75
Microtec PowerPC C Compiler................................................ 76
dSPACE DS1006 Compiler...................................................... 78
SCALEXIO GNU C/C++ Compiler (QNX) .................................. 79
Texas Instruments ANSI C Compiler ........................................ 79
FLEXnet Publisher................................................................... 81
Installing Texas Instruments ANSI C Compilers................................. 82
Installing Texas Instruments ANSI C Compilers Before dSPACE
Software (Recommended)...................................................... 83
Installing Texas Instruments ANSI C Compilers After dSPACE
Software................................................................................ 84
How to Set a dSPACE Environment Variable ........................... 85
How to Prepare the Parallel Runtime Support Library ............. 86
How to Upgrade Texas Instruments ANSI C Compiler Version 4.70
to Version 5.11...................................................................... 87
How to Upgrade Texas Instruments ANSI C Compiler Version 5.10
to Version 5.11...................................................................... 88
How to Upgrade Texas Instruments ANSI C Compiler Version 4.70
or Version 5.11 to Code Composer Tools................................ 89
Installing dSPACE Software 91
Installing dSPACE Software Products ............................................... 92
Information Requested By the Setup Programs....................... 92
How to Install dSPACE Software............................................. 94
How to Install Components of Software Products
Subsequently ......................................................................... 99
Contents
Software Installation and Management Guide May 2012 5
I

How to Install Software Patches ........................................... 101
How to Install Common Software Tools ................................ 102
How to Enable Dongle Licenses............................................ 104
How to Test the Dongle........................................................ 105
Advanced Installation Tasks ........................................................... 106
How to Customize a ControlDesk Next Generation
Installation ........................................................................... 106
How to Install the Client Software for Automating ControlDesk
Next Generation................................................................... 108
Preconfigured Automatic Installations............................................ 110
Basics on Preconfigured Automatic Installations ................... 110
How to Install dSPACE Software Automatically in Unattended
Mode................................................................................... 114
Managing Installations with the dSPACE
Installation Manager 121
Preconditions and Restrictions for Working with the dSPACE
Installation Manager ............................................................ 122
How to View Installation Details ........................................... 123
How to Activate a dSPACE Installation.................................. 126
How to Deactivate the Active Installation ............................. 130
Integrating MATLAB into dSPACE Software 133
Basics on Integrating a MATLAB Installation ......................... 134
How to Change the MATLAB Integration.............................. 139
Managing dSPACE Licenses 143
Basics on dSPACE License Types..................................................... 144
Dongle License Mechanism.................................................. 144
Floating Network License Mechanism................................... 146
Managing Licenses in a Local License.dsp File (= Run-Time
Licenses)........................................................................................ 149
How to Show Available Licenses........................................... 149
How to Add New Licenses to a Specific Local License File ..... 152
How to Activate, Deactivate or Remove Licenses .................. 156
How to Restore a Specific License Configuration .................. 159
Merging License Files..................................................................... 162
Basics on Merging License Information................................. 162
How to Merge License Files .................................................. 166
How to Modify the dSPACE Installation with Merged Files .... 172
Specifics on Using Floating Network Licenses................................. 173
Setting Up the dSPACE License Server ....................................... 174
Cont ent s
Software Installation and Management Guide May 2012
I
6

FLEXnet Publisher Software.................................................. 174
Requirements and License Server Settings ............................ 176
How to Install and Configure the dSPACE License Server ...... 178
How to Update the License.dat File on the dSPACE License
Server .................................................................................. 180
Setting Up a Connection to the dSPACE License Server............. 182
How to Set Up a Connection Between Client and Server ...... 182
License Behavior of Specific Products ........................................ 188
RTI and RTI Blocksets............................................................ 188
FlexRay Configuration Tool ................................................... 189
ControlDesk......................................................................... 190
AutomationDesk.................................................................. 190
ConfigurationDesk - Configuration Version .......................... 191
ConfigurationDesk - Implementation Version ....................... 192
ModelDesk and ASM........................................................... 193
MotionDesk......................................................................... 193
MotionDesk Blockset ........................................................... 194
MLIB/MTRACE...................................................................... 194
Microtec PowerPC C Compiler.............................................. 195
TargetLink............................................................................ 195
Model Compare................................................................... 195
ControlDesk Next Generation............................................... 196
SystemDesk ......................................................................... 196
Obtaining Permanent Floating Network Licenses ...................... 197
How to Obtain Permanent Floating Network Licenses .......... 197
Migrating to Floating Network Licenses .................................... 201
How to Add Floating Network License Support on Clients .... 202
Removing dSPACE Software 203
What Do You Want to Remove? .......................................... 204
How to Remove dSPACE Software ....................................... 208
How to Remove Components From a dSPACE Installation .... 209
How to Remove Software Automatically in Unattended
Mode .................................................................................. 211
Contacting Support via the dSPACE Installation
Manager 213
How to Prepare Information Required for dSPACE Support... 214
How to Send Information to dSPACE Support ...................... 218
Overview on Information to be Collected Manually .............. 221
Collecting Information Concerning ConfigurationDesk
(Configuration Version) and RapidPro Hardware................... 223
Collecting Information Concerning TargetLink ...................... 224
Collecting Information Concerning Model Compare............. 224
Contents
Software Installation and Management Guide May 2012 7
I

Collecting Information Concerning the Hardware ................. 225
Collecting Information Concerning RTI.................................. 226
Handling Installations of Earlier dSPACE
Releases with dSPACE Installation Manager 229
How to Restore the Default Settings for the Active
Installation ........................................................................... 230
How to Connect TargetLink and Model Compare To Other
dSPACE Installations ............................................................. 232
Integrating MATLAB Into dSPACE Installations From dSPACE
Release 7.1 And Earlier......................................................... 234
How to Remove a dSPACE Installation via dSPACE Installation
Manager .............................................................................. 235
Troubleshooting 239
Installation Problems ..................................................................... 241
Non-Administrator Logon After Installation .......................... 241
Installation With a Different User Account............................ 242
Installation on NTFS Partition................................................ 243
Only RCP and HIL Software: How to Install a dSPACE Release
Older than the Active Installation ......................................... 244
Problems When Installing TargetLink .................................... 245
Problem with Incompatibility Between RTT 1.9 and 1.6 ........ 246
How to Repair a dSPACE Installation..................................... 247
License Problems ........................................................................... 248
Basics on Error Messages...................................................... 248
Dongle License Problems...................................................... 249
Debugging Dongle Problems................................................ 251
Dongle and Floating Network License Problems.................... 253
Floating Network License Problems ...................................... 256
How to Check dSPACE Floating Network Licenses................. 261
Appendix: System Requirements 267
Basic System Requirements............................................................ 268
Host PC Hardware................................................................ 269
Operating System................................................................. 273
Run-Time-Compatibility of dSPACE Software ........................ 276
Limitations for Windows Vista/Windows 7............................ 277
Limitations for 64-Bit Windows Operating Systems in
Combination with dSPACE 32-Bit Software........................... 278
Limitations for TargetLink 64-Bit Version............................... 278
Third-Party Software ............................................................ 279
Expansion Box Hardware...................................................... 286
Additional Requirements for Specific Products and Tasks ............... 289
Contents
Software Installation and Management Guide May 2012
I
8

Using RTI FPGA Programming Blockset................................. 289
Remote Control of Measurement and Calibration Systems
According to ASAM-MCD 3MC (ASAP3) via
AutomationDesk.................................................................. 290
3-D Online Animation via MotionDesk ................................. 290
Using Automotive Simulation Models (Vehicle Dynamics, Trailer,
Truck, Traffic Scenarios) ........................................................ 292
Using AutoBoot Option........................................................ 292
Resource Requirements of dSPACE Boards .................................... 293
Installation in the Host PC.................................................... 293
Installation in the Expansion Box .......................................... 294
Index 297
I
9

Software Installation and Management Guide May 2012


About This Document
Contents This document will show you the installation and handling of the
dSPACE software.
It describes the software installation procedure and gives detailed
information on handling dSPACE software and dSPACE licenses.
Required knowledge Knowledge in handling the host PC and the Microsoft operating
system is assumed.
Where to go from here Information in this section
Document Symbols and Conventions 10
Accessing Online Help and PDF Files 11
Related Documents 13
About This Document
Software Installation and Management Guide May 2012
I
10

Document Symbols and Conventions
Symbols The following symbols may be used in this document.
Naming conventions The following abbreviations and formats are used in this document:
%name% Names enclosed in percent signs refer to environment
variables for file and path names, for example, %DSPACE_PYTHON25% is
the folder containing the Python installation.
< > Angle brackets contain wildcard characters or placeholders for
variable file and path names, etc.
Precedes the document title in a link that refers to another
document.
Indicates that a link refers to another document, which is available
in dSPACE HelpDesk.
Indicates a general hazard that may cause personal injury
of any kind if you do not avoid it by following the
instructions given.
Indicates the danger of electric shock which may cause
death or serious injury if you do not avoid it by following
the instructions given.
Indicates a hazard that may cause material damage if
you do not avoid it by following the instructions given.
Indicates important information that should be kept in
mind, for example, to avoid malfunctions.
Indicates tips containing useful information to make your
work easier.
ST M
About This Document
Software Installation and Management Guide May 2012 11
I

Accessing Online Help and PDF Files
Objective After you install your dSPACE software, the documentation for the
installed products is available as online help and Adobe

PDF files.
Online help You can access the online help, dSPACE HelpDesk, as follows:
Windows Start menu Click Start Programs <ProductName>
dSPACE HelpDesk (<ProductName>) to open dSPACE HelpDesk with
the start page of the selected product displayed. However, the user
documentation of any installed software product and its supported
hardware is available for navigating and searching.
Context-sensitive Press the F1 key or click the Help button in the
dSPACE software to get help on the currently active context.
Help menu in the dSPACE software From the menu bar, choose
Help Contents or Help Search (not available in all software products)
to open dSPACE HelpDesk. It opens at the start page of the currently
active product, but the user documentation of any installed software
product and its supported hardware is available for navigating or
searching.
About This Document
Software Installation and Management Guide May 2012
I
12

PDF files You can access the PDF files as follows:
dSPACE HelpDesk Click the PDF link at the beginning of a
document:
About This Document
Software Installation and Management Guide May 2012 13
I

Related Documents
Recommended reading Information in other documents
Hardware Installation and Configuration
DS1005 Hardware Installation and Configuration
Guide
DS1006 Hardware Installation and Configuration
Guide
DS1103 Hardware Installation and Configuration
DS1104 Hardware Installation and Configuration
MicroAutoBox Hardware Installation and
Configuration
MicroAutoBox II Hardware Installation and
Configuration
dSPACE Simulator Compact Hardware Installation
and Configuration
dSPACE Simulator Mid-Size Hardware Installation
and Configuration
dSPACE Simulator Mid-Size Based on DS2211
Hardware Installation and Configuration
SCALEXIO Hardware Installation and
Configuration
Provides feature-oriented access to the information you need
to install and configure your SCALEXIO system.
RapidPro System Hardware Installation Guide
Provides instructions on installing, assembling and
connecting the RapidPro hardware. It also contains
information on building the cable harness.
ECU Interfaces Hardware Installation and
Configuration
Provides detailed instructions on connecting ECUs to the
host PC using dSPACE ECU interfaces. It also provides the
data sheets of these interfaces and of the relevant
connection cables. This document is intended for users who
have detailed knowledge about their specific ECU and the
effects of connecting devices to it.
About This Document
Software Installation and Management Guide May 2012
I
14

First work steps
First Work Steps with MicroAutoBox, DS1103,
DS1104, DS1005, and DS1006
Provides information on configuring dSPACE systems after
you installed the dSPACE hardware. It shows you how to get
started with your dSPACE system after installation. This
document is aimed at users who have no experience with
dSPACE systems.
I
15

Software Installation and Management Guide May 2012


Safety Precautions
General Warning
Danger potential Using dSPACE software can be dangerous. You must observe the
following safety instructions and the relevant instructions in the user
documentation.
Safety Precautions
Software Installation and Management Guide May 2012
I
16

Liability dSPACE GmbH and its subsidiaries accept no liability for property
damage or personal injury resulting from improper or noncontractual
use of this product, or from incorrect operation by insufficiently
qualified staff.
If you do not accept the above restrictions, you can return this product
at the expense of dSPACE GmbH within one (1) month of receiving it.
The purchase price will then be refunded to you immediately.
Data loss during operating
system shutdown
The shutdown procedure of Microsoft Windows operating systems
causes some required processes to be aborted although they are still
being used by dSPACE software. To avoid data loss, the dSPACE
software must be terminated manually before a PC shutdown is
performed.
WARNI NG
Improper or negligent use can result in serious
personal injury and/or property damage.
Using the dSPACE software can have a direct effect on
technical systems (electrical, hydraulic, mechanical)
connected to it.
The risk of property damage or personal injury also exists
when the dSPACE software is controlled via an
automation interface. The dSPACE software is then part
of an overall system and may not be visible to the end
user. It nevertheless produces a direct effect on the
technical system via the controlling application that uses
the automation interface.
n Only persons who are qualified to use dSPACE
software, and who have been informed of the above
dangers and possible consequences, are permitted to
use this software.
n All applications where malfunctions or misoperation
involve the danger of injury or death must be
examined for potential hazards by the user, who must
if necessary take additional measures for protection
(for example, an emergency off switch).
I
17

Software Installation and Management Guide May 2012


Basics on dSPACE Software
Installation
Where to go from here Information in this section
Introduction to dSPACE Setup Programs 18
Important Changes and Improvements to dSPACE
Setup
20
Basics on dSPACE License Mechanisms 23
Features of the dSPACE Installation Manager
The dSPACE Installation Manager lets you handle all the
dSPACE installations available on your host PC and provides
detailed information on properties and installed products.
23
Basics on dSPACE Software Installation
Software Installation and Management Guide May 2012
I
18

Introduction to dSPACE Setup Programs
Objective dSPACE Release 7.3 features various setup programs, to install the
different software products available on the DVD.
Installation types The setup programs will guide you through the installation of the
software. To handle the installation scenarios, the dSPACE DVD
contains different types of setup programs:
n A global setup program (dSPACE Master Setup) to install dSPACE
software from dSPACE Release 7.3. With it you can install a single
software product (or software package) in a new folder. In addition
you also can install two or more software products in different new
folders in one run.
The dSPACE_MasterSetup.exe setup program is located in the root
folder of the DVD.
n Single setup programs to install a specific dSPACE software product
(or software package). The following are available:
o Install_RCP_HIL.exe to install the RCP and HIL software
o Install_AutomationDesk.exe to install AutomationDesk
o Install_ControlDesk.exe to install ControlDesk Next
Generation
o Install_TargetLink.exe, Install_TargetLink_x64.exe to install
TargetLink (32-bit or 64-bit version)
o Install_TargetLinkBlockset.exe,
Install_TargetLinkBlockset_x64.exe to install the license-free
(stand-alone) TargetLink Blockset (32-bit or 64-bit version)
o Install_MdlCmp.exe, Install_MdlCmp_x64.exe to install Model
Compare (32-bit or 64-bit version)
o Install_SystemDesk.exe to install SystemDesk
"RCP and HIL software" is a generic term for a
software package containing several dSPACE
software products, for example RTI, ControlDesk,
ConfigurationDesk, MotionDesk, ModelDesk. These
software products are installed in a common folder.
Use single setup programs only for specific installation
tasks, for example, for preconfigured automatic
installations.
Basics on dSPACE Software Installation
Software Installation and Management Guide May 2012 19
I

The single setup programs are located in the /Products folder of
the DVD for Release 7.3.
n dSPACE Maintenance Setup helps you modify (add components or
remove them) and repair the corresponding installation. In addition
you can remove the installation completely.
The dSPACE Maintenance Setup is available in product-specific
versions for the following products: RCP and HIL software,
TargetLink, TargetLink Blockset, Model Compare, ControlDesk Next
Generation, SystemDesk, AutomationDesk.
You can access the product-specific versions of the dSPACE
Maintenance Setup after installation of the dSPACE software via
Start Programs dSPACE <Product x.y> dSPACE Maintenance
Setup (<Product x.y>) and via the Windows Control Panel.
The term dSPACE Maintenance Setup is used in this documentation
for all software product-specific versions of this setup.
n Setup programs for common software tools
Common software tools, for example, the DCI Configuration Tool,
are used by several dSPACE products. For maximum independence,
these tools have their own setup programs.
The setup programs are located in /Tools/<SoftwareTool>/ on the
dSPACE DVD.
Installation methods The dSPACE setup programs provide two installation methods:
n Interactive installation (= standard installation)
n Preconfigured automatic installation
You can record an initial interactive installation and then use it to
install dSPACE software on several host PCs automatically. For
basics and instructions on initializing and running a preconfigured
automatic installation, refer to Preconfigured Automatic
Installations on page 110.
Various common software tools are also installed with
other dSPACE software via the dSPACE Master Setup,
if the required license information is available during
installation.
Basics on dSPACE Software Installation
Software Installation and Management Guide May 2012
I
20

Important Changes and Improvements to dSPACE Setup
Improving dSPACE
software installation
As of dSPACE Release 7.0, improvements are being made to the
installation programs for dSPACE software. The software architecture
has been redesigned to reduce dependencies between products.
The aim is to ensure that software installations have maximal flexibility
in installation and maximal run-time compatibility. This means that
dSPACE products can be used in parallel after software installation,
even if they are installed in different folders.
dSPACE Release 7.3 is an intermediate step towards this aim. Some
products do not yet support all new features. For further information,
refer to this documentation.
Installation in separate
folders
dSPACE software products (or software packages) with their own
setup programs must be installed in separate new folders. Afterwards
you can run the products without restrictions in usage. For example,
you can work with several installations simultaneously and quickly
change from one installation to another.
You can work with several software products from different releases
and installations on your host PC in parallel, if they are run-time-
compatible. For details, refer to Run-Time-Compatibility of dSPACE
Software on page 276.
With some products such as TargetLink, it is possible to use multiple
parallel installations of the same software version on your host PC. For
details, refer to Notes and Tips for Using Multiple Installations on Your
Host PC on page 64.
Improved MATLAB
integration
If you want to work with dSPACE software which requires MATLAB, a
MATLAB installation must be integrated into the dSPACE software.
Only an integrated (= connected) MATLAB installation is prepared for
use with dSPACE software.
Thus, you can perform MATLAB integration either during the initial
installation of dSPACE software or at a later date.
dSPACE software is now installed with all the components
required for MATLAB integration, even if MATLAB is not
installed on your host PC. Thus, it is no longer necessary
to install MATLAB before you install dSPACE software.
You can install MATLAB after the dSPACE software
without restrictions in usage.
Basics on dSPACE Software Installation
Software Installation and Management Guide May 2012 21
I

To support this feature, the dSPACE setup programs and the dSPACE
Installation Manager let you connect to MATLAB installations simply by
selecting checkboxes. The illustration below serves as an example and
shows the possible combinations of MATLAB software and dSPACE
installations:
n It is possible to connect a single dSPACE installation to several
MATLAB installations.
n Several dSPACE installations can be connected to one MATLAB
installation. It is no longer a requirement that each dSPACE
installation (to be used with MATLAB) needs a separate MATLAB
installation. This reduces installation time and disk space.
Offline Simulator
MATLAB installation
... connected to ...
RCP and HIL
Preferred connection
Preferred connection
AutomationDesk
TargetLink
(32-bit)
Model Compare
(32-bit)
TargetLink
(64-bit)
Model Compare
(64-bit)
R2011b (64-bit)
R2011a (64-bit)
R2011b (32-bit)
R2011a (32-bit)
R2010b SP1
(32-bit)
dSPACE installation
as of dSPACE Release 7.2
Basics on dSPACE Software Installation
Software Installation and Management Guide May 2012
I
22

n You can install a new MATLAB installation on your host PC without
reinstalling dSPACE software. To use the new installation, you just
have to connect it to the dSPACE software.
n You can connect only compatible MATLAB installations to a dSPACE
installation. For an overview of compatible products on dSPACE
Release 7.3, refer to Required MATLAB Releases on page 69.
n Only products with the same bit version can be connected and used
together. For example, TargetLink's 64-bit version can be connected
to a 64-bit version but not to a 32-bit version of MATLAB.
If you have connected several MATLAB installations to your dSPACE
installation, you must choose (mark) one of them as the preferred
connection. If you connect only one MATLAB installation, this
automatically is the preferred MATLAB installation.
A preferred connection is the default MATLAB installation which is
used by the dSPACE products, for example, when dSPACE software
products generate specific MATLAB files or automatically start
MATLAB. You can change the preferred MATLAB installation via the
dSPACE Installation Manager anytime after initial installation of
dSPACE software.
Improved license handling As of dSPACE Release 7.2 license handling also has been improved. A
separate license file is now available for each installation. The dSPACE
Installation Manager makes it easy to display and manage license
information. Note that handling dSPACE licenses is necessary only in
specific use scenarios.
Preconfigured automatic
installations
The dSPACE setup programs are based on the MSI technology from
Microsoft. They have their own configuration program, dSPACE Setup,
which installs the MSI setups and enables automatic preconfigured
software installation. It is therefore not possible to use third-party MSI
deployment tools which use MSI transformations for automatic
installation on several PCs.
Using the record mode of the setup porgrams you can record the
installation configuration of dSPACE software and use the generated
configuration file to install the software on other PCs automatically in
setup's unattended mode (manual inputs are unnecessary). You can
also automatically install several setups successively via batch file.
For more detailed instructions, refer to Preconfigured Automatic
Installations on page 110.
Basics on dSPACE Software Installation
Software Installation and Management Guide May 2012 23
I

Basics on dSPACE License Mechanisms
Licensing Various dSPACE products on the dSPACE DVD are license-protected.
The license type covers both the installation and the use of the
installed software as follows:
n For installation, you need two license files (Keys.dsp and
License.dsp file). The Keys.dsp file contains information on the
software products which can be installed during the installation
procedure. The License.dsp file contains information on the
products you can run after installation on your host PC.
n To execute applications protected by license, the license protection
must be enabled. Two different license types (dongle license,
floating network license) are available for working with the dSPACE
software after installation, depending on your order.
For basics on the different license types, refer to:
o Dongle License Mechanism on page 144
o Floating Network License Mechanism on page 146
Features of the dSPACE Installation Manager
Objective The dSPACE Installation Manager lets you handle all the dSPACE
installations available on your PC and provides, for example, detailed
information on properties and installed products.
Restriction
Enhanced functionality As of dSPACE Release 7.0, the dSPACE Installation Manager has
enhanced functionality. In addition to its basic functionality (managing
dSPACE installations), the tool now supports the integration of a
dSPACE installation into MATLAB software, provides license
management, and has a diagnostics feature that collects information
on your installation for you to send to dSPACE Support if necessary.
You cannot use the dSPACE Installation Manager to install
dSPACE software on your PC.
Basics on dSPACE Software Installation
Software Installation and Management Guide May 2012
I
24

Support of installations
from earlier dSPACE
Releases
dSPACE Installation Manager supports all dSPACE Releases. The latest
version is always compatible to installations of earlier dSPACE Releases.
However, some features which are necessary to manage earlier
dSPACE Releases are only available for those installations which require
the specific feature.
Basics on dSPACE Software Installation
Software Installation and Management Guide May 2012 25
I

Feature overview The illustration below gives an overview of the features available for
installations as of dSPACE Release 7.2. For further features which are
necessary to manage installations from earlier dSPACE releases, refer
to Handling Installations of Earlier dSPACE Releases with dSPACE
Installation Manager on page 229.
Get diagnostics information for
dSPACE support
- Collect diagnostics information
- Prepare e-mail to contact support
Manage dSPACE
installations
Current
installation
Connect dSPACE installation to
MATLAB installation
Available MATLAB installation can
be integrated into dSPACE installations
which require to work with MATLAB.
Activate/Deactivate installation
Switching between installations
is possible.
PC with your
dSPACE installations
View details
Details of selected installation and
installed products are displayed.
Manage licenses
- Available licenses are displayed
- Merging license files
- Floating network license support:
- Setting up connection between
client and server
- Obtaining permanent floating
network licenses
Basics on dSPACE Software Installation
Software Installation and Management Guide May 2012
I
26

Below are some explanations and basics on several features of the
dSPACE Installation Manager.
Managing installations Activating a dSPACE installation One of each installation of a
dSPACE software product is known as the active installation.
n The last installation of a software product that you install on your
host PC automatically becomes the active installation.
n If your system contains more than one installation (from different
releases or multiple instances of the same release), you can activate
another installation manually. The previous active installation than is
deactivated automatically.
The effects of activating a dSPACE installation depend on the software
product you use. For details, refer to How to Activate a dSPACE
Installation on page 126.
Deactivating the active installation You can deactivate the
active installation without activating another one.
This can be useful if you want to install a dSPACE Release which is
older than the currently active installation. Deactivating the active
installation automatically during installation of an older release might
be incomplete, and reactivating it might be impossible. Deactivating
the active installation manually before installing older releases ensures
that it is deactivated completely.
Connecting MATLAB to dSPACE software The dSPACE
Installation Manager provides an easy way to integrate (connect) your
MATLAB installation into dSPACE software installations which require
to work with MATLAB. All the available MATLAB installations on your
host PC and their integration statuses are listed.
Managing licenses The dSPACE Installation Manager helps you to manage the licenses
required for installation and usage of dSPACE products. The main
features are:
n Display of the available licenses on your host PC with details such as
their license types.
n Managing license codes in the license files (License.dsp and
Keys.dsp)
Not every dSPACE software product needs to be activated
before usage. So this function is, for example, not
available for the installations of TargetLink and Model
Compare.
Basics on dSPACE Software Installation
Software Installation and Management Guide May 2012 27
I

n Merging several dSPACE license files to common files
n Handling dSPACE license mechanism for floating network licenses,
for example, to set up a connection to the dSPACE License Server
n Providing information (for example, the MAC address) to obtain
permanent floating network licenses
Getting diagnostic
information for contacting
dSPACE Support
When contacting dSPACE Support, you need to provide the Support
team with information about your dSPACE installation and the
problems you may have. Some information required by dSPACE
Support is extracted automatically by the dSPACE Installation
Manager's diagnostic feature. Other information must be collected
manually.
After collecting all the information, the diagnostic feature creates an
e-mail with an automatically generated ZIP file to send to the
resonsible Support team in your country.
Related topics
Basics
Contacting Support via the dSPACE Installation Manager on page 213
Integrating MATLAB into dSPACE Software on page 133
Managing Installations with the dSPACE Installation Manager on page 121
Basics on dSPACE Software Installation
Software Installation and Management Guide May 2012
I
28

I
29

Software Installation and Management Guide May 2012


Introduction to dSPACE Software
Products on DVD
Contents of DVD The DVD for Release 7.3 contains the following dSPACE software
packages and main products:
n RCP and HIL software
"RCP and HIL software" is a generic term for a software package
containing several dSPACE software products, for example RTI,
ControlDesk, AutomationDesk, ConfigurationDesk, MotionDesk,
ModelDesk.
n AutomationDesk 3.5
n ControlDesk Next Generation (ControlDesk 4.2.1)
ControlDesk Next Generation (= ControlDesk versions as of
ControlDesk 4.0) is the successor to CalDesk and ControlDesk.
However, ControlDesk versions lower than ControlDesk 4.0 are still
included in the RCP and HIL software package.
n TargetLink 3.3
n Model Compare 2.2
n SystemDesk 3.1
Product use prohibited in United States
You are not licensed to use Model Compare in the
United States. You are not allowed to use or permit
others to use this product in the United States or in any
way that violates the laws of the United States.
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012
I
30

Where to go from here Information in this section
RCP and HIL Software 31
TargetLink Software 40
ControlDesk Next Generation 45
Model Compare Software 49
SystemDesk Software 50
AutomationDesk Software 52
Common Software Tools with Own Setup Programs 55
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012 31
I

RCP and HIL Software
Definition "RCP and HIL software" (Rapid Control Prototyping and Hardware-in-
the-Loop software) is a generic term for a software package
containing several dSPACE software products, for example RTI,
ControlDesk, ConfigurationDesk, MotionDesk, ModelDesk.
Where to go from here Information in this section
Product Overview
Here you find an overview of the dSPACE software products
contained in the RCP and HIL software package.
32
Protected Products and Required Licenses
The various dSPACE products of RCP and HIL software on the
dSPACE DVD are license-protected.
36
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012
I
32

Product Overview
Overview The illustration below gives an overview of the dSPACE products
contained in the RCP and HIL software package:
Licensed software License-free software
Real-Time Library (RTLib)
ControlDesk
Standard
ConfigurationDesk Configuration Version
ConfigurationDesk Implementation Version
MotionDesk MotionDesk Blockset
CLIB
MLIB/MTRACE
Microtec PowerPC C Compiler
RTI for Multiprocessor
Systems (RTI-MP)
Real-Time
Interface (RTI)
RTI Blocksets
ECU Interface Manager
ConfigurationDesks
Loader versions
ControlDesk Basic Features
dSPACE DS1006 Compiler
Failure
Simulation
Automotive Simulation Models (ASM) ModelDesk
FlexRay Configuration Package
SCALEXIO
Real-Time Library (RTLib)
SCALEXIO
GNU C/C++ Compiler (QNX)
Multiprocessor
Extension
ControlDesk Next Generation is a stand-alone software
product and not part of the RCP and HIL software
package. For information on its software modules, refer
to ControlDesk Next Generation on page 45.
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012 33
I

License-free RCP and HIL
software package
The dSPACE DVD includes the following license-free RCP and HIL
software:
Real-Time Library (RTLib) The real-time core software running on
the real-time platform (RTP) with a C programming interface.
ControlDesks Basic Features A graphical user interface for
managing the dSPACE hardware. In addition to the functions for
registering the hardware and managing applications via the Platform
Manager, Basic Features provides the functions for managing
experiments via the Experiment Manager. The Source Code Editor with
syntax highlighting for C or Python is also included.
ConfigurationDesk's Loader versions ConfigurationDesk
Implementation Version and Configuration Version have their own
Loader versions, which provide a reduced, license-free subset of the
full-featured versions.
ConfigurationDesk's Configuration Version, for example, is for use by
vehicle test drivers during fleet tests. Only a few features are then
supported, that is, downloading configuration settings to RapidPro
hardware and diagnostics handling.
dSPACE DS1006 Compiler A special version of the GNU C
Compiler allowing you to compile applications for the DS1006.
Licensed RCP and HIL
software package
dSPACE optionally offers all the tools needed for implementing,
experimenting and testing control systems. These tools are protected
by license.
Real-Time Interface (RTI and RTI-MP) The interface between
Simulink and the dSPACE hardware. Real-Time Interface can be used
to build real-time code, and to download and execute it on dSPACE
hardware. As a further option, you can get additional blocksets, like
the RTI CAN MultiMessage Blockset.
ControlDesk Standard Offering a variety of instruments to build
and configure instrument panels via Instrumentation, and providing
functions to perform parameter studies via the Parameter Editor and
functions to automate ControlDesks features via Automation.
ConfigurationDesk Configuration Version ConfigurationDesk's
Configuration Version is the configuration software for the dSPACE
RapidPro hardware. It allows intuitive and efficient configuration of
this hardware.
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012
I
34

ConfigurationDesk Implementation Version
ConfigurationDesk's Implementation Version supports the
implementation of real-time applications via a signal chain using
graphical elements.
FlexRay Configuration Package Containing the FlexRay
Configuration Tool, the RTI FlexRay Configuration Blockset, and the
FlexRay Configuration Blockset for the SCALEXIO system. You can use
the package for hardware-in-the-loop and restbus simulations of
FlexRay networks.
RTI AUTOSAR Package Containing the RTI AUTOSAR Interface
Generator and the RTI AUTOSAR Interface Blockset. You can use the
package to implement atomic software components and compositions
into a Simulink environment and execute them on the dSPACE real-
time hardware.
ModelDesk A graphical user interface that allows you to perform
intuitive model parameterization, and parameter set and project
management. You can parameterize the dSPACE Automotive
Simulation Models and create roads and maneuvers.
dSPACE Automotive Simulation Models (ASM) Simulink
models for the real-time simulation of automotive engines (gasoline
and diesel) and vehicle dynamics.
MotionDesk Giving you realistic visual feedback on your
simulation. MotionDesk has been developed as an addition to the
dSPACE tool chain to visualize the movement of mechanical objects in
the 3-D world. If your PC is fast enough, even "man-in-the-loop"
simulation is possible.
MotionDesk Blockset If you work with Simulink, you need the
MotionDesk Blockset to get an interface to MotionDesk. The
MotionDesk Blockset provides blocks for calculating the motion data
necessary for MotionDesk and blocks for setting up the
communication from the simulation platform to the MotionDesk PC.
ECU Interface Manager A graphical user interface that allows
control engineers to quickly integrate dSPACE bypass services in the
ECU Image and A2L file without having to change the ECU source
code itself.
CLIB The interface between host and real-time hardware. It
simplifies the control of dSPACE processor boards and access to the
on-board memory. When CLIB is used, applications can access dSPACE
processor boards concurrently. Moreover, the CLIB interface covers
differences in the host interfaces of the different board types and
allows you to uniformly access all kinds of processor boards.
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012 35
I

MLIB/MTRACE The MATLABdSPACE Interface Libraries. The
functions of these libraries allow direct access to dSPACE real-time
hardware from the MATLAB workspace.
Microtec PowerPC C Compiler Allowing you to:
n Compile applications for the DS1103, the DS1104, the DS1005,
and MicroAutoBox
n Work with the RapidPro System used as a prototyping ECU
SCALEXIO Real-Time Library (RTLib) A specific real-time core
software running on SCALEXIO real-time systems.
SCALEXIO GNU C/C++ Compiler (QNX) A special version of the
GNU C Compiler allowing you to compile applications for the
SCALEXIO system.
Related topics
Basics
Protected Products and Required Licenses on page 36
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012
I
36

Protected Products and Required Licenses
Objective The various dSPACE products of RCP and HIL software on the dSPACE
DVD are license-protected.
Products and licenses The table below lists the available dSPACE products of RCP and HIL
software which are protected by dSPACE licenses and the names of
the required licenses.
Protected Products/Modules Required License
RTI and RTI Blocksets Real-Time Interface to Simulink
(RTI1005, RTI1006, RTI1103, RTI1104,
RTI1401)
RTI
1)
RTI for Multiprocessor Systems RTIMP
RTI Bypass Blockset RTIBYPASS
RTI Bypass Blockset: XCP on UDP/IP
Option
RTIBYPASS_XCPETH
RTI Bypass Blockset: Internal Bypass
Plug-In
RTIBYPASS_INTBYP
RTI CAN Blockset RTICAN
RTI CAN MultiMessage Blockset RTICANMM
RTI CAN MM J1939 (add-on to RTI
CAN MultiMessage Blockset)
RTICANMM_J1939
RTI Ethernet (UDP) Blockset RTIETHERNETUDP
RTI DS1552 I/O Extension Blockset RTIDS1552IOEXT
RTI FPGA Programming Blockset RTIFPGA
RTI LIN MultiMessage Blockset RTILINMM
RTI RapidPro Control Unit Blockset RTIRPCU
RTI USB Flight Recorder Blockset RTIUSBFLIGHTREC
FlexRay Configuration Package FlexRay Configuration Tool FLEXRAYCONFIGTOOL
FlexRay Replay Script Generator
2)
FlexRay Configuration Blockset FLEXRAYCONFIG
RTI FlexRay Configuration Blockset RTIFLEXRAYCONFIG
RTI AUTOSAR Package RTI AUTOSAR Interface Generator RTIAUTOSAR_GEN
RTI AUTOSAR Interface Blockset RTIAUTOSAR_BS
ControlDesk ControlDesk Standard Developer
Version
CDD_STANDARD
CDO_STANDARD
ControlDesk Standard Operator
Version
CDO_STANDARD
Failure Simulation Extension FIU_AUTOMATION
FIU_INTERACTIVE
Multiprocessor Extension MP_EXTENSION
ControlDesk Test Automation CD_TA_PYTHON
ConfigurationDesk
Configuration Version
Configuration license CFD_CONFIGURATION
3)
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012 37
I

ConfigurationDesk
Implementation Version
Implementation license CFD_Implementation
3)
Implementation license required for
multimodel applications
CFD_Implementation_MC
Function block licenses CFD_Implementation_100
CFD_Implementation_200
CFD_Implementation_300
CFD_Implementation_1000
CFD_Implementation_FULL
SCALEXIO Failure Simulation SCALEXIO_FIU_100
SCALEXIO_FIU_200
SCALEXIO_FIU_300
SCALEXIO_FIU_1000
SCALEXIO_FIU_FULL
RTLIB for downloading and handling
real-time applications for SCALEXIO
systems
SCALEXIO_RTLIB
4)
RTLIB for downloading and handling
multicore real-time applications for
SCALEXIO systems
SCALEXIO_RTLIB_MC
4)
SCALEXIO GNU C/C++ Compiler
(QNX)
QNX_COMPILER
Protected Products/Modules Required License
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012
I
38

ModelDesk/Automotive
Simulation Models (ASM)
ModelDesk Offline MOD_OFFLINE
ModelDesk HW-Access MOD_HWACCESS
ModelDesk Road MOD_ROAD
ModelDesk Maneuver MOD_MANEUVER
ModelDesk Engine MOD_ENGINE
ModelDesk Traffic MOD_TRAFFIC
ASM Base License ASM_UTILS
ASM Base InCylinder Library ASM_INCYLINDERBASE
ASM BrakeHydraulics Library
Developer Version
ASM_BRAKEHYDRAULICS
ASM BrakeHydraulics Library
Operator Version
ASM_BRAKEHYDRAULICS_OP
ASM Diesel Engine InCylinder Library ASM_INCYLINDERDIESEL
ASM DrivetrainBasic Library ASM_DRIVETRAINBASIC
ASM ElectricComponents Library ASM_ELECTRIC
ASM EngineDiesel Library ASM_ENGINEDIESEL
ASM EngineGasoline Library ASM_ENGINEGASOLINE
ASM EngineGasolineBasic Library ASM_ENGINEGASOLINEBASIC
ASM Environment Library Developer
Version
ASM_ENVIRONMENT
ASM Environment Library Operator
Version
ASM_ENVIRONMENT_OP
ASM Gasoline Engine InCylinder
Library
ASM_INCYLINDERGASOLINE
ASM Optimizer ASM_OPTIMIZER
ASM Parameterization Tool ASM_PARA
ASM Traffic ASM_TRAFFIC
ASM TurboCharger Library ASM_TURBOCHARGER
ASM Truck Library ASM_TRUCK
ASM VehicleDynamics Library
Developer Version
ASM_VEHICLEDYNAMICS
ASM VehicleDynamics Library
Operator Version
ASM_VEHICLEDYNAMICS_OP
MotionDesk MotionDesk Hardware Access MDD_HWACCESS
MotionDesk Offline MDD_SL_OFFLINE
MotionDesk Blockset MOTIONDESK_BS
ECU Interface Manager ECU Interface Manager (basic) EIFMGR
Option for external bypassing on
Infineon TriCore Cs
EIFMGR_SWM_TRICORE_EXT
Option for internal bypassing on
Infineon TriCore Cs
EIFMGR_SWM_TRICORE_INT
Protected Products/Modules Required License
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012 39
I

Related topics
MLIB/MTRACE Standard option MLIB
Multiprocessor (MP) Extension option MLIB_MPOPTION
Microtec PowerPC C Compiler MCCPPC
1)
All RTI platform supports (RTI1xxx) require the same license. If you use floating network licenses and
RTI1005, for example, is used on a dSPACE License Client, this license is blocked for other clients even if they
use other RTI platform supports (as RTI1104, for example).
2)
FlexRay Replay Script Generator requires Real-Time Testing.
3)
If you start ConfigurationDesk without a valid license available, a specific runtime license-free Loader
Version opens.
4)
Available only as a dongle license.
Protected Products/Modules Required License
n A dSPACE license is not bound to a particular dSPACE
hardware. You can use one software installation for
different MicroAutoBoxes, for example.
As long as the required compiler is the same, for
example, the PowerPC C Compiler, one can even use
completely different platforms like DS1103, DS1005-
based modular systems, or MicroAutoBox with the
same software installation.
n If you purchase a separate license and want to add it
to an already existing dSPACE system, you must merge
the license information first. Refer to Merging License
Files on page 162.
Basics
Product Overview on page 32
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012
I
40

TargetLink Software
Objective TargetLink, dSPACE's production code generation software, lets you
generate highly efficient C code for microcontrollers in electronic
control units (ECUs). It also helps you implement control systems that
have been modeled graphically in a Simulink/Stateflow diagram on a
production ECU.
Where to go from here Information in this section
Software Modules
Tailoring TargetLink TargetLink is a software application consisting of several modules. This
means you can install and configure exactly the specific modules you
intend to use. The following TargetLink modules are currently
available:
TargetLink Base Suite Including the standard ANSI C Code
Generator
To work with TargetLink, the Data Dictionary Manager is required. It is
automatically installed with the TargetLink Base Suite during setup. It
can also be installed separately as a stand-alone tool without
TargetLink.
The Data Dictionary Manager is the user interface of the dSPACE Data
Dictionary (DD). The DD is a central data container that holds all the
relevant information about an ECU application, for example, for code
generation.
TargetLink Target Simulation Module For executing the
generated code on evaluation boards: for example, HCS12EVB,
CMD565, TriBoard TC1796, etc.
The list of available evaluation boards is subject to change without
notice.
Software Modules 40
Protected Modules and Required Licenses 42
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012 41
I

TargetLink Target Optimization Modules For generating code
which is optimized for specific compiler/processor combinations: for
example, Infineon c166 with Altium Tasking C compiler, Freescale
MPC500 with Wind River Diab C Compiler, Renesas SH-2 with Renesas
C compiler, etc.
TargetLink TMOS-OSEK Module For code generation for the
OSEK real-time operating system
TargetLink AUTOSAR Module For generating AUTOSAR software
components (SWCs) containing function code for ECUs and for
modeling and simulating them.
Overview The illustration below gives you an overview of the available TargetLink
modules and their structure.
Target Optimization
Modules
TargetLink
Base Suite
ANSI C
coder
TargetLink
Blockset
Data
Dictionary
Documentation
Generator
Autoscaling
Automotive-
Specific
Modules
OSEK/VDX Module AUTOSAR Module
TargetLink Module Overview
Target Simulation
Module
ASAM-MCD 2MC
file generation
Freescale
S12X
Freescale
MPC5xx
Infineon
XC2000
Infineon
C16x
Renesas
SH-2
Freescale
MC56F83xx
Renesas
V850
Freescale
HCS12
Freescale
HCS12
Infineon
C16x
Freescale
MPC5xx
Freescale
MPC55xx
Infineon
TriCore
Renesas
SH-2
Renesas
M32R
Freescale
MPC560xB
Infineon
TriCore
Renesas
M32R
Freescale
MPC55xx
Each software module has a separate license code. During
the installation procedure you can select only modules for
which you have purchased a license. If you have the
TargetLink Target Simulation Module, you can use any of
the displayed target/compiler combinations.
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012
I
42

TargetLink Preferences
Editor
The TargetLink Preferences Editor is a license-free tool that lets you
view and modify a subset of user, project and post-installation
preference settings. It can be accessed during and also after
installation.
It comes with the TargetLink Base Suite and is installed automatically
during setup.
Protected Modules and Required Licenses
Order information The table below lists the available TargetLink products which are
protected by dSPACE licenses and the names of the required licenses
and order numbers.
Classification Type Required License Order Number
TargetLink Base Suite TL_BASE TBS
TargetLink Target Optimization
Modules
Freescale HCS12/Cosmic TL_HC12_COSMIC TOM_HCS12/Cosmic
Freescale HCS12/Metrowerks TL_HCS12_METROWERKS TOM_HCS12/Metrowerks
Freescale MPC5xx/Wind River Diab TL_MPC5XX_DIAB TOM_MPC5xx/Diab
Freescale MPC5xx/Green Hills TL_MPC5XX_GHS TOM_MPC5xx/GREEN
Freescale MPC55xx/Wind River Diab TL_MPC55XX_DIAB TOM_MPC55xx/Diab
Infineon C16x/Altium Tasking TL_C16X_TASK TOM_C16x/Tasking
Infineon TriCore/Altium Tasking TL_TRICORE_TASK TOM_TriCore/Tasking
Renesas M32R/Gaio TL_M32R_GAIO TOM_M32R/GAIO
Renesas SH-2/Renesas TL_SH2_HIT TOM_SH2/SHC
TargetLink Target Simulation Module (for all supported processors) TL_TGTSIM TSM
TargetLink Module for
Operating Systems - OSEK
Metrowerks OSEKturbo TL_TMOS_OSEK TMOS_OSEK
Vector Informatik osCAN
Vector Informatik osCANopen
3Soft ProOSEK
WindRiver OSEKWorks
LiveDevices RTA/OSEK
TargetLink AUTOSAR Module TL_AUTOSAR_SWC TAS
dSPACE Data Dictionary Manager (also included in TargetLink Base Suite) DSDD_MANAGER DSDD_MANAGER
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012 43
I

TargetLink features and
required licenses
The table below shows the different TargetLink features and the
required dSPACE licenses:
TargetLink
Features
TL_BASE TL_<TOM> TL_TGTSIM TL_TMOS_OSEK TL_AUTOSAR_SWC DSDD_MANAGER
Setting
properties for
production
code
generation

Simulating in
MIL simulation
mode including
data logging
and overflow
checking
1)

Simulating in
SIL simulation
mode
1)

Simulating in
PIL simulation
mode
1)

Generating
standard ANSI
C compliant C
code

Generating
target-specific
C code

Generating
ASAM MCD-2
MC files

Generating
code for the
OSEK operating
system

Generating
code for
AUTOSAR
software
components
(SWCs)

Modeling and
simulating
AUTOSAR
SWCs

Importing and
exporting
AUTOSAR SWC
descriptions

Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012
I
44

There is no license required for
n Loading and displaying a TargetLink model
n Editing parameter values
n Working with the TargetLink Blockset (stand-alone)
n Clearing models from TargetLink data
Related topics
Managing the
dSPACE Data
Dictionary and
editing its
contents

Preparing
Simulink
models for
TargetLink

1)
For more information, refer to Simulation Mode Basics and Preconditions ( TargetLink Production Code Generation Guide).
TargetLink
Features
TL_BASE TL_<TOM> TL_TGTSIM TL_TMOS_OSEK TL_AUTOSAR_SWC DSDD_MANAGER
ST M
Basics
Installing dSPACE Software on page 91
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012 45
I

ControlDesk Next Generation
Objective ControlDesk Next Generation is the dSPACE experiment software for
seamless ECU development. It performs all the necessary tasks and
gives you a single working environment, from the start of
experimentation to the end.
Where to go from here Information in this section
Software Modules
Objective There is a basic version of ControlDesk Next Generation that can be
extended by optional software modules.
Loader version ControlDesk Next Generation Loader Version A license-free
version of ControlDesk Next Generation for registering dSPACE real-
time hardware and handling real-time applications.
Basic and Operator version ControlDesk Next Generation Basic Version A version of
ControlDesk Next Generation for creating and running experiments.
The functionality can be extended by optional software modules.
ControlDesk Next Generation - Operator Version A version of
ControlDesk Next Generation that provides only a subset of
functionality for running existing experiments. The functionality can be
extended by optional software modules.
Optional modules The installation of the software modules is controlled via license
information. In addition, with some modules, you have to specify
whether you want to install them or not during setup.
The following optional software modules are currently available.
Standard Platforms Module An optional software module for
ControlDesk Next Generation which provides access to the dSPACE
real-time platforms DS1103, DS1104, DS1005, DS1006 and
MicroAutoBox.
Software Modules 45
Protected Modules and Required Licenses 47
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012
I
46

Multiprocessor Module An optional software module for
ControlDesk Next Generation which provides access to the
multiprocessor features of dSPACE real-time platforms (not yet
available with SCALEXIO systems).
Using the Multiprocessor Module requires that you also have a valid
license for the Standard Platforms Module.
SCALEXIO Platform Module An optional software module for
ControlDesk Next Generation that provides access to the dSPACE real-
time platform SCALEXIO.
SCALEXIO Multicore Module An optional software module for
ControlDesk Next Generation that provides access to real-time
applications that are computed on multiple cores of a single-processor
SCALEXIO system.
Using the SCALEXIO Multicore Module requires that you also have a
valid license for the SCALEXIO Platform Module.
ECU Interface Module An optional software module for
ControlDesk Next Generation for calibration and measurement access
to electronic control units.
ECU Diagnostics Module An optional software module for
ControlDesk Next Generation that facilitates the calibration and
validation of ECU diagnostic functions.
Signal Editor Module An optional software module for
ControlDesk Next Generation for the graphical definition and
execution of signal generators for stimulating model variables of real-
time applications.
Bus Navigator Module An optional software module for
ControlDesk Next Generation for handling bus messages, such as CAN
messages, LIN frames, and FlexRay frames and PDUs.
Failure Simulation Module An optional software module for
ControlDesk Next Generation for simulating failures in the wiring of an
electronic control unit via a Failure Insertion Unit.
MCD3 Automation Module An optional software module for
ControlDesk Next Generation that enables users to automate
ControlDesk Next Generation according to the ASAM MCD3 standard.
Variable Editor With the Variable Editor you can view and edit/modify the content of
variable descriptions. It can be used as a standalone tool or as a
completely integrated component of ControlDesk Next Generation.
The functionality of the Variable Editor is adapted to the scenario it is
used in.
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012 47
I

Protected Modules and Required Licenses
Objective The various ControlDesk Next Generation modules on the DVD are
license-protected.
Modules and licenses The table below lists the software modules of ControlDesk Next
Generation which are protected by licenses, and the names of the
required licenses.
Product Versions/Modules Required License
Versions Loader Version (none)
Operator Version CDNG_OPERATOR
Basic Version CDNG_BASIC, CDNG_OPERATOR
(both are required)
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012
I
48

Modules Standard Platforms Module CDNG_PLATFORM_STD
Multiprocessor Module CDNG_PLATFORM_MP
1)
SCALEXIO Platform Module CDNG_SCALEXIO, SCALEXIO_RTLIB
2)
(both are required)
CDNG_SCALEXIO_MC,
SCALEXIO_RTLIB_MC
2)
(both
additionally required for multicore
real-time applications)
ECU Interface Module CDNG_ECU
ECU Diagnostics Module CDNG_DIAGNOSTIC,
CDNG_DIAGRUNTIME (both are
required)
Signal Editor Module CDNG_SIGNALEDITOR
Bus Navigator Module CDNG_BUSNAVIGATOR
Failure Simulation Module CDNG_FS
SCALEXIO Failure Simulation
2)
The licenses for the SCALEXIO
failure simulation units are available
in different sizes for different
numbers of instantiated function
blocks in your ConfigurationDesk
application:
o SCALEXIO_FIU_100
o SCALEXIO_FIU_200
o SCALEXIO_FIU_300
o SCALEXIO_FIU_1000
o SCALEXIO_FIU_FULL
For details, refer to Licenses
Required for Failure Simulation
( SCALEXIO System Overview).
MCD3 Automation Module CDNG_MCD3_AUTOMATION
Variable Editor CDNG_VARIABLEEDITOR
1)
Requires that you also have a valid license for the Standard Platforms Module.
2)
Availalble only as a dongle license.
Product Versions/Modules Required License
ST M
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012 49
I

Model Compare Software
Objective Model Compare is dSPACE's tool for identifying and visualizing the
differences between two Simulink or TargetLink models (including
Stateflow).
Protected Modules and Required Licenses
Objective The Model Compare product on the dSPACE DVD is license-protected.
Modules and licenses The table below lists the software module of Model Compare which is
protected by license, and the name of the required license.
Product use prohibited in United States
You are not licensed to use Model Compare in the United
States. You are not allowed to use or permit others to use
this product in the United States or in any way that
violates the laws of the United States.
Product/Module Required License
Model Compare MODEL_COMPARE
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012
I
50

SystemDesk Software
Objective SystemDesk is a dSPACE tool supporting the development of
distributed automotive electric/electronic systems and subsystems.
Where to go from here Information in this section
Setup Components
Objective SystemDesk consists of several components, which can be installed
separately. This allows you to install and configure the specific
components you intend to use.
Components dSPACE SystemDesk Setup component that contains all of
SystemDesk's features.
GCC Compiler The GNU C compiler is required for code generation
for the simulation target (host PC).
Setup Components 50
Protected Modules and Required Licenses 51
SystemDesk allows you to build VPUs for virtual ECUs
(V-ECUs), and experiment with them. For running a
simulation system, you also have to install the
dSPACE Offline Simulator. Refer to Common dSPACE
Software Tools on page 55.
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012 51
I

Protected Modules and Required Licenses
Versions and modules SystemDesk versions are product variants for designing AUTOSAR
ECUs. Versions can be extended by additional modules.
The table below describes the versions and modules of SystemDesk
which are protected by licenses, and the names of the required
licenses.
Legend These are the meanings of the symbols:
n "" The feature is available with that version/module.
n "" The feature is unavailable with that version/module.
Version /
Module
Modeling
Software
Architectures
Modeling
Hardware
Topologies,
Network
Communications
and Systems
Generating RTE
Code and A2L
Files
Building
Simulation
Systems
Required
License(s)
Single-ECU Design
Version

1)
SD_SINGLE_ECU_D
ESIGNER
Multi-ECU Design
Version
SD_MULTI_ECU_DE
SIGNER
RTE Generation
Module
2)
SD_RTE_BASE
3)
SD_RTE_FULL
4)
V-ECU Generation
Module
2)

3)

5)
SD_RTE_BASE
3)
SD_GEN_SIM
1)
Only for systems with one ECU.
2)
Also requires a license for the Single-ECU Design Version or for the Multi-ECU Design Version.
3)
Generation of non-optimized RTE code for simulation purposes. The RTE code is not intended for use in production ECUs.
4)
Generation of optimized RTE code of production code quality.
5)
To run a simulation system, you also have to install the dSPACE Offline Simulator. Refer to Common dSPACE Software Tools
on page 55.
You cannot open or import a SystemDesk project if it
contains elements whose licenses are unavailable. For
example, if you have a license for the Single-ECU Design
Version, opening or importing a project with a hardware
topology with more than one ECU will fail.
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012
I
52

AutomationDesk Software
Objective AutomationDesk offers a test automation environment with a highly
efficient graphical sequence editor for describing tests. In addition, it
provides a Project Manager for organizing the handling of large test
projects and an easy-to-extend library with a wide range of
automation functions.
Where to go from here Information in this section
Software Versions and Packages
Objective AutomationDesk comes in two versions, which can be installed
separately. Near a standard software package (comes with the version
and is installed automatically), additional software packages and tools
are required for executing AutomationDesk.
Versions AutomationDesk AutomationDesk version that contains all
AutomationDesk's features with graphical user interface for test
automation.
AutomationDesk Automation Server AutomationDesk version
for test automation without graphical user interface. It can be
accessed via the AutomationDesk API.
Additional software
packages and tools
The installation and activation of the additional software packages and
tools is controlled via license information. Note that not every package
has its own setup program, so in this case the elements of a package
are installed with several different setup programs. For details, refer to
Protected Modules and Required Licenses on page 53.
The following software packages are available:
n Platform API Package
The Platform API Package is required for executing blocks of the
following AutomationDesk libraries: Platform Access, HIL API, HIL
API Convenience.
Software Versions and Packages 52
Protected Modules and Required Licenses 53
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012 53
I

n Failure Simulation API Package
The Failure Simulation API Package is required for executing blocks
of the Failure Simulation Access library.
n Real-Time Testing
Real-Time Testing is required for executing blocks of the
AutomationDesk's Real-Time Testing library.
For more details, refer to Packaging of AutomationDesk
( AutomationDesk Guide).
Protected Modules and Required Licenses
Products and licenses The table below lists the available dSPACE products and additional
software packages of AutomationDesk which are protected by
dSPACE licenses and the names of the required licenses.
The table also shows the setup programs which are used to install a
product or module. Note that they are executed automatically if you
use the dSPACE Master Setup for installation and if the required
licenses are available.
ST M
Protected
Products/Modules
Involved Setups Required License
AutomationDesk o Install_AutomationDesk.exe
o Install_PythonExtensions.exe
o ADD_STANDARD
o ADD_AUTOMATION
o PYEXT_MATLABLIB2
o PYEXT_RS232LIB2
AutomationDesk
Automation Server
o Install_AutomationDesk.exe
o Install_PythonExtensions.exe
o ADD_AUTOMATION
o PYEXT_MATLABLIB2
o PYEXT_RS232LIB2
Platform API Package o Install_HILAPI.NET.exe
o Install_PythonExtensions.exe
o Install_RCP_HIL.exe
o HILAPI_DOTNET_MAPORT
o HILAPI_DOTNET
o PYEXT_HILAPI_MAPORT
o PYEXT_RTPLIB2
o CD_TA_PYTHON
o CLIB
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012
I
54

Failure Simulation API
Package
o Install_HILAPI.NET.exe
o Install_RCP_HIL.exe
o FS_CORE
o HILAPI_DOTNET_EESPORT
o HILAPI_DOTNET
o FIU_AUTOMATION
Real-Time Testing o Install_AutomationDesk.exe o RTT_DEVELOPER
o RTT_OPERATOR
Protected
Products/Modules
Involved Setups Required License
If you install the Platform API Package with the dSPACE
Master Setup, during the installation process the setup
program for the RCP and HIL software package is also
started. It is only required if you want to use the dSPACE
Test Automation Python modules in combination with
ControlDesk 3.x. In other cases click Cancel in the setup
dialog to reject the RCP and HIL installation. The dSPACE
Master Setup then continues with the installation of the
next product.
If you do not cancel the RCP and HIL installation, note
that this installation becomes the active RCP and HIL
installation. To use another RCP and HIL installation, you
first have to activate it via the dSPACE Installation
Manager.
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012 55
I

Common Software Tools with Own Setup
Programs
Objective Common software tools, for example the DCI Configuration Tool, are
used by several dSPACE products. For maximum independence, these
tools have their own setup programs.
Common dSPACE Software Tools
Objective The dSPACE DVD contains the following common dSPACE software
tools. Some of them are license-protected.
Information in this topic
DCI Configuration Tool on page 56
Required Licenses on page 56
dSPACE CAN API on page 56
Required Licenses on page 56
dSPACE ECU Flash Programming Tool on page 56
Required Licenses on page 56
dSPACE Offline Simulator on page 56
DsOffSim on page 56
GCC Compiler on page 56
Modules on page 57
Offline Simulator Core on page 57
dSPACE Python Extensions on page 57
Required Licenses on page 57
Real-Time Testing on page 58
Required Licenses on page 58
dSPACE Profiler on page 58
Required Licenses on page 58
HIL API .NET on page 58
EESPort on page 58
MAPort on page 58
Required Licenses on page 58
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012
I
56

DCI Configuration Tool The DCI Configuration Tool provides wizards that guide you through
the configuration and firmware update of a DCI-GME1 or DCI-GSI1.
Required Licenses
dSPACE CAN API To work with CAN, you must connect your host PC to the CAN bus via
one or more CAN interfaces. The dSPACE CAN API lets you use the
same API commands for all supported CAN interface types, so you do
not need to adapt your application to your CAN interface.
Required Licenses
dSPACE ECU Flash
Programming Tool
Via the dSPACE ECU Flash Programming Tool, you can program the
flash memory of ECUs equipped with a DCI-GME1, DCI-GSI1 or DCI-
GSI2 calibration interface, ECUs with XCP on CAN, or ECUs with XCP
on USB. The principle of ECU flash programming via the dSPACE ECU
Flash Programming Tool varies according to the ECU interface type
used.
Required Licenses
dSPACE Offline Simulator The setup of the dSPACE Offline Simulator provides the following
setup components:
DsOffSim You need the dSPACE Target for Offline Simulation
(DsOffSim) to build VPUs from Simulink

models, and to prepare


Simulink

models for integration into SystemDesk. You can run VPUs


as part of a simulation system.
GCC Compiler The GNU C compiler is required for building VPUs.
Tool Required Licenses
DCI Configuration Tool None
Tool Required Licenses
dSPACE CAN API None
Tool Required Licenses
dSPACE ECU Flash Programming
Tool
ECUFLASHPROGRAMMING
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012 57
I

Offline Simulator Core Installing this component is mandatory for
running simulation systems with SystemDesk or ControlDesk
Next Generation.
This component contains the following applications:
n The Offline Simulation Player, which is an application for
configuring and running an offline simulation.
n The Simulation System Editor, which is an application for
connecting VPUs in a simulation system.
Modules
dSPACE Python Extensions The dSPACE Python Extensions are a collection of Python modules for
different dSPACE products. You require them if you want to use the
new generation of dSPACE Python modules rtplib2, rs232lib2 or the
dSPACE Python implementation of the HIL API MAPort in a Python
interpreter.
Required Licenses
Module Description Required License(s)
DS_OFFSIM_BASE Capability for running Simulink

models
in an offline simulation
o DSOFFSIM
o OFFSIM_SL
DS_OFFSIM_ECU
1)
Capability for running V-ECUs in an
offline simulation
OFFSIM_ECU
DS_OFFSIM_PIL
2)
Capability for running V-ECUs in a
PIL simulation
OFFSIM_PIL
DS_OFFSIM_CAN
2)
Capability for additional CAN bus
simulation
OFFSIM_BUS
1)
Requires the DS_OFFSIM_BASE module.
2)
Requires the DS_OFFSIM_BASE and DS_OFFSIM_ECU modules.
Module Required Licenses
rtplib2 PYEXT_RTPLIB2
rs232lib2 PYEXT_RS232LIB2
HIL API MAPort (Python) PYEXT_HILAPI_MAPORT
Introduction to dSPACE Software Products on DVD
Software Installation and Management Guide May 2012
I
58

Real-Time Testing dSPACE software, which offers a test automation environment for
executing Python scripts synchronously with the simulation model.
Model variables can be observed and changed in every simulation step
without modifying the model.
Required Licenses
dSPACE Profiler The dSPACE Profiler is a graphical front end for displaying arbitrary
events, logged by applications running on the real-time hardware. The
basis for this profiling mechanism is supplied by the dSPACE Event
Logging module (DSELOG) in combination with the dSPACE Time
Stamping module (DSTS), which are part of the real-time libraries
(RTLibs) of the supported platforms and are implicitly initialized by the
general initialization function init().
Required Licenses
HIL API .NET The HIL API .NET provides elements that are based on the HIL API
specified by the ASAM association. The ASAM HIL API .NET provides
two modules which can be installed separately.
EESPort The EESPort controls electrical error simulation hardware.
It allows to set different error types.
MAPort The Model Access port provides access to the simulation
model. It is possible to read and write parameters, and to capture and
generate signals.
Required Licenses
Module Required Licenses
Real-Time Testing Developer Version RTT_DEVELOPER
Real-Time Testing Operator Version RTT_OPERATOR
Tool Required Licenses
dSPACE Profiler None
Module Required Licenses
EESport o FS_CORE
o HILAPI_DOTNET_EEPORT
MAPort HILAPI_DOTNET_MAPORT
I
59

Software Installation and Management Guide May 2012


Before You Start
Where to go from here Information in this section
Installation Workflow
A graphical overview of the installation sequence gives a quick
orientation and a workflow shows you the steps in which you
must install the dSPACE software.
60
What Do You Want to Install? 63
Notes and Tips for Using Multiple Installations on
Your Host PC
64
Preconditions for Installing dSPACE Software 65
How to Check Administrator Rights
Make sure you have the required administrator rights to install
dSPACE software.
68
Before You Start
Software Installation and Management Guide May 2012
I
60

Installation Workflow
Objective A flow chart and a description of work steps describe the workflow for
installing the dSPACE software.
Installation graphical
overview
The flow chart below shows the installation sequence required to
install the dSPACE software:
No
Yes
Does your host PC
meet the system
requirements?
Update your host PC to meet
the system requirements.
Installing dSPACE software
Do you have the
required administrator
rights?
No
Yes
Get the required
administrator rights.
Install required third-party software.
*
Install the dSPACE software.
dSPACE software is installed.
Install the dSPACE hardware.
dSPACE system is installed. * You can also install third-party software after the dSPACE software.
Before You Start
Software Installation and Management Guide May 2012 61
I

Installation workflow
Installing a dSPACE system requires that you first install the software
and then the hardware in the specified order according to the
following steps.
1. Check whether the host PC meets the requirements of the dSPACE
software. Refer to Appendix: System Requirements on page 267.
2. Determine the installation location and method. Refer to Before
You Start on page 59.
3. Check whether you have the required administrator rights. Refer to
How to Check Administrator Rights on page 68.
4. Before installing dSPACE software, you have to install third-party
software. Refer to Installing Third-Party Software on page 73.
5. Install the dSPACE software. Refer to Installing dSPACE Software
on page 91.
6. If you use the dongle license mechanism, you should check the
dongle installation. Refer to How to Test the Dongle on page 105.
NOTI CE
Changing the installation sequence may lead to
unpredictable results or even damage the system.
n Read the instructions carefully before starting
installation. Install the components of your system in
exactly the order specified.
n Note all warnings that are given.
n Do not install dSPACE hardware in your host PC (e.g.
DS81x link boards, DS1103, DS1104) before software
installation is completed. Failing to do so will cause
problems with assigning dSPACE device drivers
correctly.
It is recommended to install MATLAB before you install
dSPACE software which require MATLAB. However, it
is possible to install MATLAB after installing dSPACE
software.
After you install the software, you can use dSPACEs
online Help provided by dSPACE HelpDesk.
Before You Start
Software Installation and Management Guide May 2012
I
62

7. Afterwards, you can install and configure the hardware
components. Refer to the board-specific Installation and
Configuration document of your dSPACE hardware.
Related topics
If you encounter any problems during installation:
n Check the description again and verify that you
have not missed a step.
n Contact dSPACE Support using the dSPACE
Installation Manager. It is available:
o Via Start Programs dSPACE Installation
Manager (after installation of the dSPACE
software)
o At http://www.dspace.com/goto?im
Basics
Removing dSPACE Software on page 203
Before You Start
Software Installation and Management Guide May 2012 63
I

What Do You Want to Install?
Installation cases The installation procedure depends on the dSPACE product you want
to install on your host PC. The table lists installation cases with links to
necessary information.
What do You Want to
Install?
Installation
Location
Installation Program Preconditions Installation
Instructions
RCP and HIL software
1)
New folder dSPACE_MasterSetup.exe Preconditions for
Installing dSPACE
Software
on page 65
How to Install
dSPACE Software
on page 94
ControlDesk Next
Generation
AutomationDesk
TargetLink (32-bit and 64-
bit version)
Model Compare (32-bit and
64-bit version)
SystemDesk
2)
TargetLink Blockset (32-bit
version)
New folder Install_TargetLinkBlockset.exe
TargetLink Blockset (64-bit
version)
New folder Install_TargetLinkBlockset_x64.exe
A new product/software
module (for example,
ConfigurationDesk to the
"RCP and HIL software"
installation)
Folder with
existing dSPACE
software
dSPACE Maintenance Setup How to Install
Components of
Software
Products
Subsequently
on page 99
A software patch Folder with
existing dSPACE
software
How to Install
Software Patches
on page 101
dSPACE ECU Flash
Programming Tool
New folder
specified by
dSPACE
ECUFlashProgrammingTool_<x.y>.exe How to Install
Common
Software Tools
on page 102
dSPACE CAN API DSCanApi.exe
DCI Configuration Tool DCI_ConfigurationTool_<x.y>.exe
Real-Time Testing New folder RealTimeTesting <x.y> Setup.exe
dSPACE Offline Simulator Install_OfflineSimulator.exe
dSPACE Python Extensions Install_PythonExtensions.exe
dSPACE Profiler New folder
specified by
dSPACE
dSPACE_Profiler.exe
HIL API .NET Install_HILAPI.NET.exe
1)
"RCP and HIL software" is a generic term for a software package containing several dSPACE software products, for example RTI,
ControlDesk, ConfigurationDesk, MotionDesk, ModelDesk. These software products are installed in a common folder.
2)
SystemDesk 3.1 requires the installation of a patch (DS_SD31p3_p3_213589.exe), which is availlable in the \Updates\ folder of the
dSPACE DVD.
dSPACE software products can only be installed in
separate new folders. Products of the RCP and HIL
software package are installed in a common new folder.
Before You Start
Software Installation and Management Guide May 2012
I
64

Notes and Tips for Using Multiple Installations on Your Host
PC
Objective You should note the following guidelines when you want to install
multiple versions of dSPACE software on your host PC.
Multiple installation of
different releases
If you want to install different releases of the same software product,
you have to install them in different folders on your host PC, for
example:
n RCP and HIL software of dSPACE Release 7.3 in
D:\dSPACERCPHIL7.3, and RCP and HIL software of dSPACE Release
7.2 in D:\dSPACERCPHIL7.2
n TargetLink 3.3 in D:\TargetLink3.3, and TargetLink 3.2 in
D:\TargetLink3.2
Multiple installation of
same releases
The guidelines for installing multiple instances of the same release,
depend on the software product you use.
RCP and HIL software You have to install each instance of the
same release in a different folder, for example, one instance of the RCP
and HIL software from dSPACE Release 7.3 in D:\dSPACERCPHIL7.3_1 ,
and another instance of the RCP and HIL software from dSPACE
Release 7.3 in D:\dSPACERCPHIL7.3_2.
Up to 15 instances of the same RCP and HIL software release can be
installed on your host PC.
One of your RCP and HIL software installations is known as the active
installation. If you want to work with a specific deactivated
installation, you have to activate it first and then reboot your host PC
before you can use a product of the desired installation.
You cannot install products and product modules (which
are part of a specific software product or software
package) in an installation of a different release, for
example:
n ConfigurationDesk 4.2 (part of dSPACE Release 7.3) in
a Release 7.2 software installation.
n Data Dictionary Manager 3.3 (part of TargetLink 3.3) in
a TargetLink 3.2 software installation.
Before You Start
Software Installation and Management Guide May 2012 65
I

TargetLink You have to install each instance of the same release in
a different folder, for example, one instance of TargetLink 3.3 in
D:\TargetLink3.3_1, and and another instance of TargetLink 3.3 in
D:\TargetLink3.3_2
Up to 15 instances of the 32-bit version and up to 15 instances of the
64-bit version of the same TargetLink release can be installed on your
host PC.
You can run multiple instances of MATLAB independently, so multiple
instances of TargetLink can also run in parallel, but only one TargetLink
instance per instance of MATLAB. This lets you, for example, compare
the generated production code of different MATLAB/TargetLink
installations simultaneously.
Unlike TargetLink, the same release of the TargetLink Blockset (stand-
alone) can only be installed once on your host PC.
Model Compare You can install only one instance of the 32-bit
version and one instance of the 64-bit version of Model Compare on
your host PC. Multiple installation of one version of the same release is
not supported. However, you can install different releases of Model
Compare on your host PC.
All other products with own setup program You can install
only one instance of these software products (for example,
ControlDesk Next Generation, AutomationDesk, SystemDesk,
common software tools) on your host PC. Multiple installation of the
same release is not supported. However, you can install different
releases of them on your host PC.
Preconditions for Installing dSPACE Software
Installation folder The folder in which you want to install the software must not contain
any other software. You cannot install the software in a new subfolder
of an existing dSPACE installation.
Limitation Since parentheses in the path name can cause problems
in conjunction with third-party software, make sure to choose
installation paths for the dSPACE software, MATLAB, and third-party
compilers without parentheses.
System requirements Your system must meet specific system requirements. Refer to Host PC
Hardware on page 269 and Operating System on page 273.
Before You Start
Software Installation and Management Guide May 2012
I
66

Administrator rights You need administrator rights to install dSPACE software.
If you are not sure whether you have administrator rights, check them.
For instructions, refer to How to Check Administrator Rights
on page 68.
System protection
software
Make sure that the installation is not blocked by system protection
software like Windows Defender, firewalls or anti-virus software. It is
recommended to disable this software during installation.
Power-saving states The installation process must not be interrupted by your host PC
activating a power-saving state triggered by a user action or by
Microsoft Windows. An interrupted dSPACE installation cannot be
continued after you have woken up your PC. It is recommended to
disable all power-saving states (for example, the sleep or the
hibernation state) during installation.
Valid only for Windows 7:
User Account Control
It is recommended to disable Windows User Account Control (UAC)
during the installation of dSPACE software. If you cannot disable it,
you should note the following Windows behavior: If UAC is enabled,
the setup programs run with the administrator account instead of the
user account. Therefore it is important that the administrator account
has access to the required drives, particularly to the required network
drives.
Valid only for RCP and HIL
software: Required user
rights
To work with the RCP and HIL software, you need modify permissions
(write and read access) for the <InstallationFolder> folder (and all
subfolders).
If you install software on the system partition (that is, the partition
where Windows is installed) and this partition is formatted as an NTFS
partition, nonadministrators usually have only read-only access to it.
To ensure that every user can work with the RCP and HIL software
without restrictions:
n Install the RCP and HIL software on a partition where the operating
system is not installed, or
Before You Start
Software Installation and Management Guide May 2012 67
I

n After installation, give the software users modify permissions for
the <InstallationFolder> folder (and all subfolders)
3-D object library of MotionDesk and ModelDesk To change
objects in the 3-D object library as a user with restricted rights, you
need write access to the library root folder (e.g.,
C:\3DLibrary\md3dlib).
Write access is necessary because objects in the library are also
changed if you work with the ModelDesk Road Generator or
ModelDesk Traffic Editor.
Required licenses The Keys.dsp and License.dsp license files provide all the license
information which you need for the dSPACE software you want to
install.
If you order dSPACE software as a package, you receive the merged
license information with the software. If not, you must merge the
license information yourself. Refer to Basics on Merging License
Information on page 162.
Unpacking received license files Before sending the license files
via e-mail, dSPACE creates a ZIP archive which contains the license files
and changes the file name extension of the ZIP archive to avoid
firewall problems. When you receive the license files, you have to
change the file name extension from .piz to .zip. Each ZIP archive
contains two or three files which have to be unpacked before installing
the software. Save all these files to one folder which you specify
during installation.
Third-party software The required third-party software must be installed.
Some dSPACE products require specific third-party products to be
installed. You must install some of these first, before installing the
dSPACE products, to ensure correct operation and full functionality.
Refer to Third-Party Software on page 279.
It is important to give modify permissions for the
<InstallationFolder> folder (and all subfolders) after
the software is installed. Otherwise, software users get
modify permissions for the <InstallationFolder>
folder, but not for all the subfolders that are created
during the installation of the RCP and HIL software.
Before You Start
Software Installation and Management Guide May 2012
I
68

How to Check Administrator Rights
Objective You need administrator rights to install dSPACE software and manage
dSPACE installations.
Possible methods There are two ways in which you can check your administrator rights:
n Via the Control Panel of your host PC. Refer to Method 1.
n Via the dSPACE Installation Manager. Refer to Method 2.
Method 1 To check administrator rights via Control Panel
1 From the Start Control Panel menu, select the Users and Passwords
dialog.
If the entry at your User Name is Administrator, you have
administrator rights.
Method 2 To check administrator rights via dSPACE Installation Manager
1 Via Start Programs dSPACE Installation Manager open the
dSPACE Installation Manager.
2 If the status bar of dSPACE Installation Manager displays The
current account <user name> has administrative privileges., you
have administrator rights.
I
69

Software Installation and Management Guide May 2012


MATLAB Compatibility Information
Where to go from here Information in this section
Required MATLAB Releases
MATLAB

Working with various dSPACE products requires that you have installed
MATLAB.
Required MATLAB Releases 69
Modifying the MATLAB Installation by dSPACE
Software
71
For system requirements of MathWorks

software, refer
to
http://www.mathworks.com/support/sysreq/current_relea
se.
MATLAB Compatibility Information
Software Installation and Management Guide May 2012
I
70

For up-to-date information on additional MATLAB releases which can
be used in combination with dSPACE software, refer to
http://www.dspace.com/goto?sw3rdparty.
64-bit versions of MATLAB As of dSPACE Release 7.2, TargetLink
and Model Compare are distributed as 32-bit and 64-bit versions.
MATLAB Release... Is Supported by Release 7.3
R
C
P

a
n
d

H
I
L

S
o
f
t
w
a
r
e
1
)
A
u
t
o
m
a
t
i
o
n
D
e
s
k

3
.
5
1
)
2
)
T
a
r
g
e
t
L
i
n
k

3
.
3
M
o
d
e
l

C
o
m
p
a
r
e

2
.
2
d
S
P
A
C
E

O
f
f
l
i
n
e

S
i
m
u
l
a
t
o
r

2
.
2
1
)
R2012a
3)4)

R2011b
R2011a
R2010bSP1
5)

R2010b
R2010a
5)

R2009bSP1
5)

R2009b
R2009a
1)
64-bit MATLAB versions are not supported.
2)
AutomationDesk's MATLAB Access library requires MATLAB.
3)
Not supported by the RTI FPGA Programming Blockset - FPGA Interface
4)
Not supported by dSPACE Automotive Simulation Models (ASM)
5)
Tested with RTI FPGA Programming Blockset but not officially supported by Xilinx.
Only the 64-bit versions of TargetLink and Model
Compare support the 64-bit versions of MATLAB. The 32-
bit versions of TargetLink and Model Compare and all
other dSPACE software products support only 32-bit
versions of MATLAB.
MATLAB Compatibility Information
Software Installation and Management Guide May 2012 71
I

Modifying the MATLAB Installation by dSPACE Software
Objective dSPACE software modifies some files of the MATLAB installation
during installation procedure or by changing the MATLAB integration
(via dSPACE Installation Manager) , to improve the handling between
MATLAB and the dSPACE software.
Modifiying MATLAB's
startup file
At startup time, MATLAB automatically executes the matlabrc.m file.
dSPACE Setup (and the dSPACE Installation Manager) modifies this file
by adding the dspacerc function call to the script, depending on the
location where MATLAB is installed.
dSPACE software does not check whether MATLAB is installed in a
network or locally on your host PC. If MATLAB is installed in a
network, you must have modify rights for the matlabrc.m file and the
MATLAB folder that contains it:
n If you do not have modify rights, dSPACE Setup (and the dSPACE
Installation Manager) cannot integrate the MATLAB installation and
issue an error message.
n If you have modify rights, dSPACE Setup (and the dSPACE
Installation Manager) modify matlabrc.m automatically.
Modifying MATLAB
warnings for P-coded files
Because MATLAB will not support P-coded files generated prior to
MATLAB version 7.5 (R2007b) in the future, MATLAB R2010b displays
warning messages when older P-coded files are opened. These files
should be regenerated.
Warning: The P-code file abc.p was generated prior to MATLAB
version 7.5 (R2007b) and will not be supported in a future
release. Use pcode to regenerate abc.p using MATLAB R2007b or
later.
Because dSPACE supports a wide range of MATLAB versions, there are
a lot of P-coded files that will be detected by this MATLAB check. To
reduce warning messages to the most relevant, dSPACE software
disables the above mentioned oldPfileVersion warning.
You can reactivate the warning by entering
warning on MATLAB:oldPfileVersion
in the MATLAB Command Window.
To deactivate the warning, enter:
warning off MATLAB:oldPfileVersion
MATLAB Compatibility Information
Software Installation and Management Guide May 2012
I
72

As of MATLAB R2011a, dSPACE software does not
disable the above mentioned oldPfileVersion warning.
I
73

Software Installation and Management Guide May 2012


Installing Third-Party Software
Objective Depending on the dSPACE products you want to use, you must install
third-party software on your host PC before you can install the dSPACE
software.
Where to go from here Information in this section
Information in other sections
Information About Required Third-Party Software 74
Installing Texas Instruments ANSI C Compilers 82
Installing dSPACE Software 91
Troubleshooting 239
Installing Third-Party Software
Software Installation and Management Guide May 2012
I
74

Information About Required Third-Party
Software
Where to go from here Information in this section
MATLAB, Simulink, Simulink Coder (formerly Real-
Time Workshop), and Stateflow
To work with various dSPACE products.
75
Microtec PowerPC C Compiler
To compile applications for the DS1103, the DS1104, the
DS1005, and MicroAutoBox, and to work with the RapidPro
System used as prototyping ECU.
76
dSPACE DS1006 Compiler
To compile applications for the DS1006.
78
SCALEXIO GNU C/C++ Compiler (QNX)
To compile applications for the SCALEXIO system.
79
Texas Instruments ANSI C Compiler
To compile slave applications for the DS1103, DS2210,
DS2211, and DS2302.
79
FLEXnet Publisher
To work with floating network licenses, you need software to
install and configure a dSPACE License Server providing the
available dSPACE licenses for the connected dSPACE License
Clients.
81
Installing Third-Party Software
Software Installation and Management Guide May 2012 75
I

MATLAB, Simulink, Simulink Coder (formerly Real-Time
Workshop), and Stateflow
Objective You have to install software from The MathWorks

if you want to
work with:
n RTI, RTI-MP, or RTI Blocksets
n MLIB/MTRACE
n AutomationDesk to automate MATLAB via AutomationDesks
MATLAB Access library
n Automotive Simulation Models (ASM)
n TargetLink
n Model Compare
Compatibility information As of MATLAB Release R2011a, the products formerly called Real-Time
Workshop

and Stateflow Coder have been reorganized by


MathWorks as the MATLAB Coder
TM
and Simulink

Coder
TM
. The
Simulink Coder requires the MATLAB Coder.
Make sure that the MATLAB, MATLAB Coder, Simulink, Simulink
Coder, and Stateflow versions are supported by the dSPACE software
version you intend to install. Refer to MATLAB Compatibility
Information on page 69.
Installation procedure Install MATLAB, MATLAB Coder, Simulink, Simulink Coder , and
Stateflow as described in the respective manuals.
Related topics
For detailed version and compatibility information, refer
to the compatibility list (CompList.txt), available:
n In the RCP_HIL folder of the dSPACE DVD
n At <InstallationFolder>\ReadMe\CompList.txt (after
installation of the dSPACE software)
n At http://www.dspace.com/goto?sw3rdparty
Basics
dSPACE DS1006 Compiler on page 78
Microtec PowerPC C Compiler on page 76
Texas Instruments ANSI C Compiler on page 79
Installing Third-Party Software
Software Installation and Management Guide May 2012
I
76

Microtec PowerPC C Compiler
Objective Microtec PowerPC C Compiler Ver. 3.7 is required for compiling
applications for the DS1103, the DS1104, the DS1005 and
MicroAutoBox and working with the RapidPro System used as a
prototyping ECU.
Compatibility information Make sure that the Microtec PowerPC C Compiler is supported by the
dSPACE software version you intend to install.
C compiler ordered from
dSPACE
If you ordered the compiler together with your dSPACE system, it is
installed automatically from the dSPACE DVD as part of the RCP and
HIL software.
The compiler required for dSPACE Release 6.0 or later is
not compatible with earlier dSPACE releases (for example,
dSPACE Release 5.4). Therefore the installation does not
allow an earlier compiler version to be overwritten, as
that version might still be used by earlier dSPACE
Releases.
For detailed version and compatibility information, refer
to the compatibility list (CompList.txt), available:
n In the RCP_HIL folder of the dSPACE DVD
n At <InstallationFolder>\ReadMe\CompList.txt (after
installation of the dSPACE software)
n At http://www.dspace.com/goto?sw3rdparty
Installing Third-Party Software
Software Installation and Management Guide May 2012 77
I

C compiler not ordered
from dSPACE
If you did not order the Microtec PowerPC C Compiler from dSPACE,
install the required compiler version before installing the dSPACE
software. Afterwards you have to set the environment variable
PPC_ROOT to adapt the search path accordingly.
Related topics
n The folder where the compiler is installed should be
located in the root folder of the drive.
n You can adapt your dSPACE installation to the new
compiler search path by modifying your installation via
dSPACE Maintenance Setup. This tool will ask you for
the location of your PowerPC C Compiler. To access
the setup, select Start Programs dSPACE RCP & HIL
<x.y> dSPACE Maintenance Setup (RCP & HIL <x.y>).
<x.y> is a placeholder for the release version.
Basics
dSPACE DS1006 Compiler on page 78
MATLAB, Simulink, Simulink Coder (formerly Real-Time Workshop), and Stateflow
on page 75
Texas Instruments ANSI C Compiler on page 79
Installing Third-Party Software
Software Installation and Management Guide May 2012
I
78

dSPACE DS1006 Compiler
Objective For compiling applications for the DS1006, you need a special version
of the GNU C Compiler. This version is named dSPACE DS1006
Compiler Version 2.2 and based on GNU C Compiler Ver. 3.3.5.
Installation procedure The compiler is installed automatically when the dSPACE software is
installed. The environment variable X86_ROOT is set, and the search
path is adapted accordingly.
Related topics
The DS1006 Compiler is free of charge. The original GNU
C Compiler Ver. 3.3.5 is available from dSPACE on
demand. Contact dSPACE Support to get the original ZIP
archive, which is also available at http://gcc.gnu.org.
For detailed information on the GNU C Compiler, its
features, incompatibilities, how to use it and how to
report bugs, refer to the GCC 3.3.5 Manual. It is available:
n At %X86_ROOT%\doc\index.html (after installation of
the dSPACE software)
n At http://gcc.gnu.org/onlinedocs/gcc-3.3.5/gcc
Basics
MATLAB, Simulink, Simulink Coder (formerly Real-Time Workshop), and Stateflow
on page 75
Microtec PowerPC C Compiler on page 76
Texas Instruments ANSI C Compiler on page 79
Installing Third-Party Software
Software Installation and Management Guide May 2012 79
I

SCALEXIO GNU C/C++ Compiler (QNX)
Objective For compiling applications for the SCALEXIO system, you need a
special version of the GNU C Compiler. This version is named
SCALEXIO GNU C/C++ Compiler (QNX 6.5.0) and based on GNU C
Compiler Ver. 4.4.2 as provided by QNX Software Systems.
Installation procedure The installation also includes libraries and header files for QNX 6.5.0.
The compiler and libraries are installed automatically when the dSPACE
software is installed.
Texas Instruments ANSI C Compiler
Basics If you want to compile slave applications for the boards mentioned
below, you need an ANSI-C Compiler from Texas Instruments.
The Texas Instruments ANSI C Compilers are not part of the dSPACE
installation. They have to be installed separately. If you need these
compilers, it is recommended to install them before you install the
dSPACE software.
n For detailed information on the GNU C Compiler, its
features, incompatibilities, how to use it and how to
report bugs, refer to the GCC 4.4.2 Manual. It is
available at http://gcc.gnu.org/onlinedocs/gcc-
4.4.2/gcc.
n Information on the QNX libraries are available at
http://www.qnx.com/developers/docs/6.5.0/topic/com.
qnx.doc.neutrino_lib_ref/about.html.
Board Required Compiler
DS2210 One of the following Texas Instruments tools (including an ANSI-C
Compiler):
o TMS 320C3x/C4x Code Generation Tools Ver. 4.70
o TMS 320C3x/C4x Code Generation Tools Ver. 5.11
o TMS 320C3x/C4x Code Composer Tools Release 4.10 (including
TI Compiler Ver. 5.11)
DS2211
DS2302
DS1103 C2000 Code Composer Tools (including TMS320C2x/C2xx/C5x
Compiler Vs 7.0)
Installing Third-Party Software
Software Installation and Management Guide May 2012
I
80

For compiling slave applications, it does not matter which of the above
mentioned versions of TMS 320C3x/C4x Code Generation Tools you
use.
Compatibility information For detailed version and compatibility information on the TMS
320C3x/C4x Code Generation or Code Composer Tool, refer to the
compatibility list (CompList.txt), available:
n In the RCP_HIL root folder of the dSPACE DVD concerned
n At <InstallationFolder>\ReadMe\CompList.txt (after installation
of the dSPACE software)
n At http://www.dspace.com/goto?sw3rdparty
Installing the TI Compiler You can install the TI Compiler before or after installation of the
dSPACE software. For more information on the installation procedures,
refer to Installing Texas Instruments ANSI C Compilers on page 82.
Upgrading to a newer
version
If you already installed TI Compiler Version 4.70 or Version 5.10, you
can upgrade to Version 5.11 or to Code Composer Tools Release 4.10.
For instructions, refer to:
n How to Upgrade Texas Instruments ANSI C Compiler Version 4.70
to Version 5.11 on page 87
n How to Upgrade Texas Instruments ANSI C Compiler Version 5.10
to Version 5.11 on page 88
n How to Upgrade Texas Instruments ANSI C Compiler Version 4.70
or Version 5.11 to Code Composer Tools on page 89
Related topics
Basics
dSPACE DS1006 Compiler on page 78
MATLAB, Simulink, Simulink Coder (formerly Real-Time Workshop), and Stateflow
on page 75
Microtec PowerPC C Compiler on page 76
Installing Third-Party Software
Software Installation and Management Guide May 2012 81
I

FLEXnet Publisher
FLEXnet Publisher
software
To provide suitable license management for floating network licenses,
dSPACE uses FLEXnet Publisher a product of Flexera Software Inc.
This makes it easy to install and configure the dSPACE License Server
providing the available dSPACE licenses for the connected dSPACE
License Clients. The dSPACE DVD provides the entire FLEXnet Publisher
software required by the dSPACE License Client(s) and the dSPACE
License Server. Refer to FLEXnet Publisher Software on page 174.
Installing Third-Party Software
Software Installation and Management Guide May 2012
I
82

Installing Texas Instruments ANSI C Compilers
Objective This applies only for RCP and HIL software installations: If you want to
compile slave applications for specific boards (for example, the
DS2211), you need an ANSI C Compiler from Texas Instruments. The
Texas Instruments ANSI C Compilers are not part of the dSPACE
installation. They have to be installed separately. If you need these
compilers, it is recommended to install them before you install the
dSPACE software.
Where to go from here Information in this section
Installing Texas Instruments ANSI C Compilers
Before dSPACE Software (Recommended)
83
Installing Texas Instruments ANSI C Compilers After
dSPACE Software
84
How to Set a dSPACE Environment Variable 85
How to Prepare the Parallel Runtime Support
Library
86
How to Upgrade Texas Instruments ANSI C Compiler
Version 4.70 to Version 5.11
87
How to Upgrade Texas Instruments ANSI C Compiler
Version 5.10 to Version 5.11
88
How to Upgrade Texas Instruments ANSI C Compiler
Version 4.70 or Version 5.11 to Code Composer Tools
89
Installing Third-Party Software
Software Installation and Management Guide May 2012 83
I

Installing Texas Instruments ANSI C Compilers Before
dSPACE Software (Recommended)
Objective For instructions on installing the required TI Compiler, refer exclusively
to the instructions in the respective manual from Texas Instruments.
Specifying compiler path
during dSPACE installation
After you install the Texas Instrument ANSI-C Compiler, you must
specify its path during installation of the dSPACE software. The
compiler path depends on the compiler version you want to install:
For more information on the required compiler version, refer to the
table in Texas Instruments ANSI C Compiler on page 79.
Preparing Parallel Runtime
Support Library
After installation of the dSPACE software, you must prepare the TI
compiler's Parallel Runtime Support Library, which is required by the
dSPACE software environment. Refer to How to Prepare the Parallel
Runtime Support Library on page 86.
The folder where the compiler is installed should be
located in the root folder of the drive.
Compiler Compiler Path Example
C3x/C4x TI Compiler Version 4.70 <drive>:\<name_of_the_compiler_folder>\ C:\C3xtools
C3x/C4x TI Compiler Version 5.11
C3x/C4x Code Composer Tools <drive>:\<code_composer_name>\c3x4x\cgtools C:\tic3x4x\c3x4x\cgtools
C2000 Code Composer Tools <drive>:\<code_composer_name>\c2000\cgtools c:\tic2xx\c2000\cgtools
Installing Third-Party Software
Software Installation and Management Guide May 2012
I
84

Installing Texas Instruments ANSI C Compilers After dSPACE
Software
Basics For instructions on installing the required TI Compiler, refer exclusively
to the instructions in the respective manual from Texas Instruments.
If you already specified a compiler folder during installation of the
dSPACE software, install the compiler in that folder. You can check the
compiler folder settings by reading the respective dSPACE environment
variable (see the tables in How to Set a dSPACE Environment Variable
on page 85). To show the contents of a variable, for example, TI_ROOT,
use the following command in a Command Prompt window (= DOS
window):
SET TI_ROOT
If you want to use another compiler folder, or did not specify it during
installation of the dSPACE software, you must set the respective
dSPACE environment variable to the compiler folder after installation
of the compiler.
The dSPACE software uses this environment variable to find the
installed TI compiler. Refer to How to Set a dSPACE Environment
Variable on page 85.
Preparing Parallel Runtime
Support Library
After installation of the compiler software, you must prepare the TI
compiler's Parallel Runtime Support Library, which is required by the
dSPACE software environment. Refer to How to Prepare the Parallel
Runtime Support Library on page 86.
The folder where the compiler is installed should be
located in the root folder of the drive.
You can open a Command Prompt window, for example,
as follows: From the Start menu, choose Run ..., enter
cmd and click OK.
Installing Third-Party Software
Software Installation and Management Guide May 2012 85
I

How to Set a dSPACE Environment Variable
Objective If you specify the compiler paths during installation of the dSPACE
software, the environment variables are set by the installation
software. You therefore do not have to set the variables afterwards.
If you did not specify a compiler path or specified a different path, you
must set the environment variables after installation of the dSPACE
software.
Required environment
variables
DS2210, DS2211 and DS2302 I/O boards require the following
environment variable and variable value:
DS1103 requires the following environment variable and variable
value:
Method To set a dSPACE environment variable
1 Depending on the operating system:
n Windows XP: From Start Control Panel, select System.
n Windows 7/Windows Vista: From Start Control Panel System
and Security, select System. In the link list on the left side, select
Advanced system settings.
The System Properties dialog opens.
2 On the Advanced page, click Environment Variables.
3 In the System Variables frame, click
n New to set a new environment variable.
n Edit to change an existing environment variable.
4 In the New System Variable dialog, enter the variable name and
value.
5 Reboot your system.
Compiler Variable Name Variable Value Example
C3x/C4x TI Compiler
Version 4.70
TI_ROOT <drive>:\<name_of_the_compiler_folder>\ C:\C3xtools
C3x/C4x TI Compiler
Version 5.11
C3x/C4x Code Composer
Tools
<drive>:\<code_composer_name>\c3x4x\cgtools C:\tic3x4x\c3x4x\cgtools
Compiler Variable Name Variable Value Example
C2000 Code Composer Tools C2X_ROOT <drive>:\<code_composer_name>\c2000\cgtools c:\tic2xx\c2000\cgtools
Installing Third-Party Software
Software Installation and Management Guide May 2012
I
86

Result The dSPACE environment variable is set.
How to Prepare the Parallel Runtime Support Library
Objective After installation of the dSPACE software, you must prepare the TI
compiler's Parallel Runtime Support Library, which is required by the
dSPACE software environment of DS2210, DS2211 and DS2302 I/O
boards.
Method To prepare the Parallel Runtime Support Library
1 Open a Command Prompt window (DOS window): For example,
from the Start menu, choose Run ..., enter cmd and click OK.
2 Type the following at the prompt:
bldtirts.bat
The command is available only after installation of the dSPACE RCP
and HIL software.
Result The bldtirts.bat batch file builds the Parallel Runtime Support Library
of the compiler.
The Parallel Runtime Support Library is not required for
the DS1103.
Installing Third-Party Software
Software Installation and Management Guide May 2012 87
I

How to Upgrade Texas Instruments ANSI C Compiler Version
4.70 to Version 5.11
Objective The following instructions show how to upgrade the installed TI
Compiler Version 4.70 to Version 5.11.
Method To upgrade TI Compiler Version 4.70 to Version 5.11
1 Delete all files in the root folder of the %TI_ROOT% compiler. Do not
delete the %TI_ROOT% folder itself.
2 Install TI Compiler Version 5.10. For installation instructions, refer
exclusively to the instructions in the respective manual from Texas
Instruments.
3 Install the patch available under ftp://ftp.ti.com/pub/cs/c4x/5.11.
4 Open the corresponding ReadMe file available under
ftp://ftp.ti.com/pub/cs/c4x/5.11/readme/ and follow the
instructions.
Result The TI Compiler Version 4.70 is upgraded to Version 5.11.
Next steps After installation of the compiler software, you must prepare the TI
compiler's Parallel Runtime Support Library, which is required by the
dSPACE software environment. Refer to How to Prepare the Parallel
Runtime Support Library on page 86.
Related topics
The root folder of the compiler is referred to as %TI_ROOT%
below.
Basics
Installing Texas Instruments ANSI C Compilers on page 82
Installing Third-Party Software
Software Installation and Management Guide May 2012
I
88

How to Upgrade Texas Instruments ANSI C Compiler Version
5.10 to Version 5.11
Objective The following instructions show how to upgrade the installed TI
Compiler Version 5.10 to Version 5.11.
Method To upgrade TI Compiler Version 5.10 to Version 5.11
1 Install the patch available under ftp://ftp.ti.com/pub/cs/c4x/5.11.
2 Open the corresponding ReadMe file available under
ftp://ftp.ti.com/pub/cs/c4x/5.11/readme/ and follow the
instructions.
Result The TI Compiler Version 5.10 is upgraded to Version 5.11.
Next steps After installation of the compiler software, you must prepare the TI
compiler's Parallel Runtime Support Library, which is required by the
dSPACE software environment. Refer to How to Prepare the Parallel
Runtime Support Library on page 86.
The root folder of the compiler is referred to as %TI_ROOT%
below.
Installing Third-Party Software
Software Installation and Management Guide May 2012 89
I

How to Upgrade Texas Instruments ANSI C Compiler Version
4.70 or Version 5.11 to Code Composer Tools
Objective The following instructions show how to upgrade the installed TI
Compiler Version 4.70 or Version 5.11 to Code Composer Tools.
Method To upgrade TI Compiler Version 4.70 or Version 5.11 to Code
Composer Tools
1 Delete all files in the root folder of the %TI_ROOT% compiler. Also
delete the %TI_ROOT% folder itself.
2 Follow the instructions to install the TI Code Composer Tools. For
details, see Installing Texas Instruments ANSI C Compilers After
dSPACE Software on page 84.
3 Set the dSPACE variable %TI_ROOT% to the new compiler folder as
described in How to Set a dSPACE Environment Variable
on page 85.
Result The TI Compiler Version 4.70 or Version 5.11 is upgraded to Code
Composer Tools.
Next steps After installation of the compiler software, you must prepare the TI
compiler's Parallel Runtime Support Library, which is required by the
dSPACE software environment. Refer to How to Prepare the Parallel
Runtime Support Library on page 86.
The root folder of the compiler is referred to as %TI_ROOT%
below.
Installing Third-Party Software
Software Installation and Management Guide May 2012
I
90

I
91

Software Installation and Management Guide May 2012


Installing dSPACE Software
Where to go from here Information in this section
Information in other sections
Installing dSPACE Software Products 92
Advanced Installation Tasks 106
Preconfigured Automatic Installations 110
Installing Third-Party Software
Depending on the dSPACE products you want to use, you
must install third-party software on your host PC before you
can install the dSPACE software.
73
Removing dSPACE Software 203
Troubleshooting 239
Installing dSPACE Software
Software Installation and Management Guide May 2012
I
92

Installing dSPACE Software Products
Where to go from here Information in this section
Information Requested By the Setup Programs
Naming of installation
folder
When installing your dSPACE software, the setup program asks you for
the name of the installation folder. This guide and other documents
refer to this folder as <InstallationFolder>. The path name of the
installation folder can contain spaces.
As of dSPACE Release 6.1, all dSPACE products on the DVD allow
spaces in the path name of the installation folder.
Limitation Since parentheses in the path name in conjunction with
3third party software can cause problems, make sure to choose
installation paths for the dSPACE software, MATLAB and third-party
compilers without parentheses.
Licenses For license-protected products you have to provide valid license
information. The setup program asks you for the location of the
license files (*.keys and *.dsp ).
Floating network licenses If you have purchased floating
network licenses, specify the following when prompted during
installation:
n The name or IP address of the dSPACE License Server
Information Requested By the Setup Programs 92
How to Install dSPACE Software 94
How to Install Components of Software Products
Subsequently
99
How to Install Software Patches
Software patches contain bugfixes for your dSPACE software.
101
How to Install Common Software Tools 102
How to Enable Dongle Licenses 104
How to Test the Dongle 105
Installing dSPACE Software
Software Installation and Management Guide May 2012 93
I

n The TCP/IP port used for the management of dSPACE licenses
If you leave the TCP/IP port edit field empty, the software
automatically determines a free port in the default port range 27
000 27 009. In this case, the edit field must also be left empty
during installation of the dSPACE License Server.
Compiler installation Some dSPACE products require a compiler to compile applications. The
accompanying setup program asks for the installation path of this
compiler. You can:
n Specify the path of already installed compilers
n Specify the path of compilers that are to be installed by the setup
program
n Skip specifying the path for compilers you do not want to use
MATLAB integration MATLAB is required for work with various dSPACE products. The setup
program asks for the MATLAB installations on your host PC to be
linked to the dSPACE software.
You can also perform MATLAB integration at a later date after
installing dSPACE software.
Parts of a software
package/software product
to be installed
During installation you have to specify the parts (products and
modules) of a software package or of a software product which you
want to install and which you do not want to install. The installation of
some software modules is controlled only via license information. The
Select Components dialog does not list these modules (for you to select
or deselect them) during setup.
Note that you can install only products and modules which are license-
free or for which license information is available.
MotionDesk: Path of the
3-D object library
When selecting the path of the 3-D object library, note the following
points:
n Specify a path outside <InstallationFolder> to ensure the path is
independent for later dSPACE Releases.
n If you want to use your scenes on different computers, ensure that
the 3-D object library is installed in a folder with identical pathname
on all computers.
As of dSPACE Release 7.0, you have to specify the
compilers required for TargetLink in the TargetLink
Preferences Editor after installing TargetLink.
Installing dSPACE Software
Software Installation and Management Guide May 2012
I
94

How to Install dSPACE Software
Objective The dSPACE Master Setup is the global setup program to install
dSPACE software. You can install a single software product or you can
install two or more software products in new folders in one run.
Information requested by
the setup program
During installation of dSPACE software, the setup program requests
several information. Refer to Information Requested By the Setup
Programs on page 92.
Preconditions Before installing the dSPACE software, check if the preconditions are
met. Refer to Preconditions for Installing dSPACE Software
on page 65.
Automatic installation of
third-party software
Third-party software is automatically installed during setup, if the
software is not available on your PC, for example:
n Microsoft .NET Framework 3.5 SP1
n Microsoft .NET Framework 4.0
n Microsoft Visual C++ 2008 SP1 Redistributables
n Microsoft Windows Installer 4.5
n Python 2.5.1 is installed during the setup of ControlDesk Next
Generation, SystemDesk, AutomationDesk and RCP and HIL
software (for products that require Python).
n Microsoft SQL Express is installed during setup of SystemDesk.
Method To install dSPACE software
1 Insert the dSPACE DVD into the DVD drive.
2 Close all running programs including Windows Explorer before
continuing the installation.
The installation process must not be interrupted by your
host PC activating a power-saving state triggered by a
user action or by Microsoft Windows. An interrupted
dSPACE installation cannot be continued after you have
woken up your PC. It is recommended to disable all
power-saving states (for example, the sleep or the
hibernation state) during installation.
Installing dSPACE Software
Software Installation and Management Guide May 2012 95
I

3 Choose the DVD drive and run dSPACE_MasterSetup.exe.
4 Follow the instructions given by the setup program.
When you have entered all license information requested (the
license information's path), the dSPACE Master Setup displays the
current settings in the Start Copying Files dialog.
The following screenshot serves as an example.
5 Check whether all the dSPACE software you want to install is listed.
A software product can be missing in the list if:
n You did not provide its license information.
n The license information is wrong or incomplete.
If not everything is listed, click Cancel to quit the setup. Add the
correct license information to the existing files by merging it. Refer
to How to Merge License Files on page 166. Restart
dSPACE_MasterSetup.exe.
Make sure the installation is not blocked by system
protection software like Windows Defender, firewall or
anti-virus software. It is recommended to disable such
software during installation.
For installing the TargetLink Blockset, you have to run
Install_TargetLinkBlockset.exe or
Install_TargetLinkBlockset_x64.exe.
Installing dSPACE Software
Software Installation and Management Guide May 2012
I
96

6 Click Next to continue the installation.
7 Valid only for TargetLink and RCP and HIL software: If this software
already is installed on your host PC, the setup program detects this
installation. You can install a further instance on your host PC.
Therefore you have to set the Install a new instance checkbox (see
below).
8 In the Select Components dialog, select the products and modules
you want to install and deselect the products and modules you do
not want to install.
9 When you have entered the installation path(s), the dSPACE Setup
displays the edited settings in the Start Copying Files dialog.
The following screenshot serves as an example.
If there is a software product on the list which you do
not want to install, continue the dSPACE Master Setup
anyway. In the installation process, each software
product starts with its own setup dialog. You can click
Cancel in this dialog to reject installation. Then dSPACE
Master Setup continues with the installation of the
next product.
n Expand the nodes to view all products and
modules.
n Grayed checkboxes indicate mandatory modules
which cannot be deselected.
n You can resize the Select Components dialog for a
better overview.
Installing dSPACE Software
Software Installation and Management Guide May 2012 97
I

10Check if the path entries are correct.
If not, click Back to edit the correct settings.
11Windows Vista/Windows 7 only: When the system generates
messages for the device drivers asking if you want to install the
software, select Always trust software from... and click Install.
No more messages are generated for the device drivers.
12When prompted, reboot your PC.
13Log on as the same user with administrator rights directly after
reboot. This allows the system to complete the installation correctly.
The last step is mandatory because some DLLs installed
by dSPACE are registered only after reboot. This
registration and thus the entire installation will fail
if you first log on without administrator rights.
This is the standard behavior for most software
installations that add or update system DLLs.
Installing dSPACE Software
Software Installation and Management Guide May 2012
I
98

If Windows' autologon process is enabled on your PC, press the
Shift key directly after restarting your PC, and hold the key until
the log-on dialog opens. This allows you to log on as the same user
with administrator rights.
14Visit http://www.dspace.com/goto?support and check our Web site
for patches for your current dSPACE installation.
15Download and install the available patches.
Result The dSPACE software is installed according to the license information
in the Keys.dsp file and your selection during setup. This file holds
information on the products and modules you can install from the
related dSPACE DVD.
Components which are not specified in the Keys.dsp file or have been
deselected are either not installed, or installed in a basic version or
demo mode. To install these products and modules later, you have to
modify your installation when you receive the license information.
Refer to How to Install Components of Software Products
Subsequently on page 99.
Next steps n You can check the software installation. Refer to Verifying the
Installation ( Software Installation and Management Guide).
n Valid only for RCP and HIL software: Ensure that the software users
have modify permissions (write and read access) for the
<InstallationFolder> and all subfolders.
n Valid only for SystemDesk: If you have installed
SystemDesk 3.1 during the installation procedure,
you must then install a patch which is availlable on
the dSPACE DVD. Run DS_SD31p3_p3_213589.exe in
the \Updates\ folder of the dSPACE DVD.
n Valid only for dSPACE Offline Simulator: If you have
installed dSPACE Offline Simulator 2.2 during the
installation procedure, you must then install a patch
which is available on the dSPACE DVD. Run
DS_OSIM22p2_p2_216755.exe in the \Updates\ folder
of the dSPACE DVD.
ST M
Installing dSPACE Software
Software Installation and Management Guide May 2012 99
I

n Before you can work with software protected by licenses, make
sure the licenses are available and enabled.
o Dongle licenses: Enable the dongle licenses by connecting the
execution key (dongle) to the USB port of the host PC. Refer to
How to Enable Dongle Licenses on page 104.
Test the dongle afterwards. For instructions, refer to How to Test
the Dongle on page 105.
o Floating network licenses: Normally, the floating network
licenses are automatically enabled on installation of the
software. If you skipped specifying the IP address and TCP/IP
port of the dSPACE License Server during installation, you must
direct your host PC as a client to use the server. Refer to How to
Set Up a Connection Between Client and Server on page 182.
n AutomationDesk only:
n SystemDesk only: Automating more than one version
When you install SystemDesk, by default the automation feature
gives you access to the last SystemDesk version that was installed.
For information on how to automate a previously installed version
of SystemDesk, refer to Automating Different SystemDesk Versions
( SystemDesk Guide).
How to Install Components of Software Products
Subsequently
Objective Instead of installing a complete dSPACE software product (or software
package), you can install components (products or modules) of it after
it has been installed initially.
Installing components of
software products during
initial installation
Installing components of dSPACE software products during initial
installation is the standard way to install dSPACE software for most
users. For preconditions and instructions, refer to How to Install
dSPACE Software on page 94.
Preconditions n You have administrator rights.
When starting AutomationDesk for the first time,
make sure to start it with administrator rights.
ST M
Installing dSPACE Software
Software Installation and Management Guide May 2012
I
100

n Valid only for the RCP and HIL software: If you want to install
products and modules for an existing installation, the dSPACE
installation for which you want to install the product and module
has to be the active installation. For details, refer to How to Activate
a dSPACE Installation on page 126.
Method To install components of a software product subsequently
1 Use the dSPACE Maintenance Setup for the software product for
which you want to install modules: From the Start Programs
dSPACE <product> <x.y> menu, select dSPACE Maintenance Setup
<product> <x.y> .
<product> <x.y> is a placeholder for the software and its version,
since your host PC can have multiple installations and multiple
products in Start Programs. The term dSPACE Maintenance Setup
is used for all product-specific versions, for example, dSPACE
Maintenance Setup (TargetLink 3.3) .
2 Select Modify Installation.
3 Specify the location of the license information files (*.dsp).
4 In the Select Components dialog, select the products and modules
you want to install and deselect the products and modules you do
not want to install.
5 Follow the instructions of the setup program.
6 When prompted, reboot your PC.
Result The selected modules of the software product are installed.
Related topics
n Expand the nodes to view all modules.
n Grayed checkboxes indicate mandatory modules
which cannot be deselected.
n You can resize the Select Components dialog for a
better overview.
Basics
How to Install dSPACE Software on page 94
Integrating MATLAB into dSPACE Software on page 133
HowTos
How to Remove Components From a dSPACE Installation on page 209
How to Repair a dSPACE Installation on page 247
Installing dSPACE Software
Software Installation and Management Guide May 2012 101
I

How to Install Software Patches
Objective Software patches usually contain bugfixes for your dSPACE software.
Keeping your dSPACE
installation up-to-date
To keep your dSPACE installations up-to-date, dSPACE strongly
recommends that you visit our Web site at
http://www.dspace.com/goto?support periodically and download and
install the most recent software patches.
Reinstalling custom
solutions after installing
software patches
After the dSPACE installation has been updated with a software patch,
it might be necessary to reinstall previously installed custom solutions.
If you are not sure, contact dSPACE Support at support@dspace.de.
Preconditions n The dSPACE product for which you want to install the software
patch is installed on your host PC.
n Only valid for RCP and HIL software: The dSPACE installation which
contains the dSPACE product that should be updated, must be the
active installation. For details on how to activate an installation,
refer to How to Activate a dSPACE Installation on page 126.
Method To install dSPACE software patches
1 Visit http://www.dspace.com/goto?support and check for patches
for your current dSPACE installation.
2 Download and install the available patches.
3 When prompted, reboot your PC.
Result The dSPACE installation is updated with the software patch.
Next steps Reinstall custom solutions if necessary. If you are not sure, contact
dSPACE Support at support@dspace.de.
Related topics
Basics
How to Install dSPACE Software on page 94
Removing dSPACE Software on page 203
Installing dSPACE Software
Software Installation and Management Guide May 2012
I
102

How to Install Common Software Tools
Objective Common software tools, for example, the DCI Configuration Tool, are
used by several dSPACE products. To get maximal independency, these
tools have there own setup programs.
Tools and their installation
characteristics
The following table lists common software tools with some installation
characteristics:
n Various common software tools can also be installed with other
dSPACE software via the dSPACE Master Setup, if the required
license information is available during installation.
n Various common software tools are installed in folders defined by
dSPACE (\Program Files\Common Files\dSPACE\<SoftwareTool>/).
n For a short description of the available tools and the required
licenses, refer to Common dSPACE Software Tools on page 55.
Valid only for dSPACE Offline Simulator 2.2 (on dSPACE Release
7.3) After installation of dSPACE Offline Simulator 2.2, you must
install the DS_OSIM22p2_p2_216755.exe patch from the \Updates\
folder on the dSPACE DVD.
Tool Installation
Location
License-
Protected Tool
Installation is
Possible via dSPACE
Master Setup
DCI Configuration Tool Fixed folder defined
by dSPACE

dSPACE CAN API
dSPACE ECU Flash
Programming Tool

Real-Time Testing
dSPACE Offline Simulator Folder defined by
user during
installation

dSPACE Python Extensions
Python Folder defined by
user during
installation
1)

MCD3 Client Fixed folder defined
by dSPACE

dSPACE Profiler
HIL API .NET
dSPACE Installation Manager
1)
Folder defined by user if Python is not already installed on the host PC during another product installation.
Installing dSPACE Software
Software Installation and Management Guide May 2012 103
I

Location of setup
programs
The setup programs are located in \Tools\<SoftwareTool>\ on the
dSPACE DVD.
Preconditions n You have administrator rights.
n The Keys.dsp file contains the keys for license-protected common
software tools.
Method To install common software tools
1 Insert the dSPACE DVD into the DVD drive.
2 Choose the DVD drive and run the corresponding setup in the
\Tools\<SoftwareTool>\ folder.
3 Follow the instructions given by the setup program.
4 When prompted, reboot your PC.
5 Only valid for dSPACE Offline Simulator 2.2: Run
DS_OSIM22p2_p2_216755.exe in the \Updates\ folder of the dSPACE
DVD.
Result The software tool is installed in the fixed folder defined by dSPACE or
in a user-defined folder (depending on the tool).
Installing dSPACE Software
Software Installation and Management Guide May 2012
I
104

How to Enable Dongle Licenses
Objective To execute applications protected by dongle license, the license must
be enabled by a dongle.
Preconditions The dSPACE software with the WIBU-KEY driver must be installed.
Method To enable dongle licenses
1 Connect the dongle to an USB port of the host PC.
2 Check the functionality of the dongle by using a diagnostics tool
from WIBU. For instructions, refer to How to Test the Dongle
on page 105.
Related topics
When you connect a dongle to a host PC for the first
time, the hardware wizard opens. You must install the
WIBU-KEY driver via the wizard, even if the driver was
installed with the dSPACE software. You need
administrator rights for this.
A special version of the dongle for connection to a
parallel port is available on request.
Basics
Dongle License Mechanism on page 144
Managing Licenses in a Local License.dsp File (= Run-Time Licenses) on page 149
Merging License Files on page 162
HowTos
How to Show Available Licenses on page 149
Installing dSPACE Software
Software Installation and Management Guide May 2012 105
I

How to Test the Dongle
Objektive If you use the dongle license mechanism, you should first check the
dongle installation. Afterwards you can test the functionality by using
a diagnostics tool from WIBU.
Method To test the dongle
1 Check that the dongle is connected to an USB port or LPT1: port.
2 Check that the dongle number matches the license installed on
your host PC. For instructions, refer to How to Show Available
Licenses on page 149.
3 If using a dongle for a parallel port, check that the LPT1: port is
enabled in the BIOS setup of the host PC.
4 Select Start Control Panel.
5 In the Control Panel, double-click the WIBU-KEY icon.
Result The main page of the WIBU-KEY diagnostics tool opens.
n If the dongle software recognizes the dongle, the table on the right
side of the Contents page shows code 470 and your dongle
number.
n If the dongle software does not recognize the dongle or any errors
are displayed, proceed with Debugging Dongle Problems
on page 251.
Installing dSPACE Software
Software Installation and Management Guide May 2012
I
106

Advanced Installation Tasks
Where to go from here Information in this section
How to Customize a ControlDesk Next Generation
Installation
Objective If you want the ControlDesk Next Generation installation to run
customer-specific tasks such as replacing a configuration file by
another one, install ControlDesk Next Generation together with a
customer-specific batch file. For details on writing batch files, refer to
the online documentation of your operating system.
Batch file example The batch file in the following example renames the
XmlDataSetComp2HTML10.xsl file to XmlDataSetComp2HTML10.xsl_org
and copies the customer-specific XmlDataSetComp2HTML10.xsl file from
c:\ to the %Inst_ROOT%\Main\bin\XMLResources folder. The script
maps %Inst_ROOT% to the installation folder of ControlDesk Next
Generation.
How to Customize a ControlDesk Next Generation
Installation
If you want the ControlDesk Next Generationk installation to
run customer-specific tasks such as replacing a configuration
file by another, install ControlDesk Next Generation together
with a customer-specific batch file.
106
How to Install the Client Software for Automating
ControlDesk Next Generation
You can automate or remote-control ControlDesk Next
Generation via a client PC using the ControlDesk Next
Generation MCD3 Automation Module with the ASAM MCD-
3 (DCOM) interface. In this case you must install specific client
software on the client PC.
108
Installing dSPACE Software
Software Installation and Management Guide May 2012 107
I

@echo off
set INST_ROOT=C:\Program Files\dSPACE ControlDesk 4.0\
if not exist "%INST_ROOT%" (
color 0C
echo Error: InstallationSetRoot folder not found !!!
goto :end_app
)
@echo on
rename
"%INST_ROOT%\Main\bin\XMLResources\XmlDataSetComp2HTML10.xsl"
^
XmlDataSetComp2HTML10.xsl_org
copy "c:\XmlDataSetComp2HTML10.xsl" ^
"%INST_ROOT%\Main\bin\XMLResources\XmlDataSetComp2HTML10.xsl"
:end_app
pause
Restrictions If you install the dSPACE software with the dSPACE Master Setup, the
batch file is run only if ControlDesk Next Generation is part of the
installation. The file cannot be used for other dSPACE software
products.
Method To customize a ControlDesk Next Generation installation
1 Write a batch file for your customer-specific tasks and name it
CustomInstall.bat.
2 Copy the entire structure of the DVD to an empty folder on your PC
or network.
The copied folder structure must be identical to the one on the
DVD.
3 In the copied DVD structure, put CustomInstall.bat parallel to
ControlDeskNG.msi, which is located in \Products\ControlDesk.
4 In the copied folder on your host PC, run the setup program for the
way you want to install ControlDesk Next Generation:
n Install_ControlDesk.exe to install ControlDesk Next
Generation as a single installation
n dSPACE_MasterSetup.exe to install ControlDesk Next Generation
as part of an installation of several software products in one run
Make sure to use the copied dSPACE Master Setup.
The dSPACE Master Setup on the DVD would start
the ControlDesk Next Generation setup program on
the DVD, which does not install the batch file.
Installing dSPACE Software
Software Installation and Management Guide May 2012
I
108

5 Follow the instructions given by the setup program as described in
How to Install dSPACE Software on page 94.
Result n ControlDesk Next Generation is installed and the setup program
copies CustomInstall.bat to
<InstallationFolder>\Setup\ControlDeskNG.
n After rebooting your PC and logging on again, CustomInstall.bat
runs.
How to Install the Client Software for Automating
ControlDesk Next Generation
Objective You can automate or remote-control ControlDesk Next Generation via
a client PC using the ControlDesk Next Generation MCD3 Automation
Module with the ASAM MCD-3 (DCOM) interface. In this case you
must install specific client software on the client PC.
Client PC and server PC Client PC The client PC is the PC to be used for automating
ControlDesk Next Generation. An automation system is installed on
the client PC. One or more PCs can be used as client PCs. You must
install the client software on all client PCs.
Server PC The server PC is the PC on which ControlDesk Next
Generation is installed with the ControlDesk Next Generation MCD3
Automation Module.
Restrictions You need administrator rights to install the software package. To check
whether you have the required rights, refer to How to Check
Administrator Rights on page 68.
Method To install the client software for automating ControlDesk Next
Generation
1 Insert the dSPACE DVD into the DVD drive of the client PC.
2 Select the DVD drive and run
dSPACE_MCD3Client_Setup_<version>.exe, which is located in
\Tools\MCD3Client\ on the dSPACE DVD.
Installing dSPACE Software
Software Installation and Management Guide May 2012 109
I

The Setup wizard opens.
3 Follow the instructions given by the Setup wizard.
Result You have installed the specific client software on the client PC that is
required to automate or remote control ControlDesk Next Generation.
Next steps To run ControlDesk Next Generation and the automation system on
different PCs, you have to configure the DCOM settings on the
server PC.
For instructions, refer to:
n How to Configure DCOM Settings on the Server PC (Windows XP)
( ControlDesk Next Generation MCD-3 Automation Guide)
n How to Configure DCOM Settings on the Server PC (Windows 7)
( ControlDesk Next Generation MCD-3 Automation Guide)
Then, you can connect to ControlDesk Next Generation remotely.
For further details on automating ControlDesk Next Generation, refer
to the ControlDesk Next Generation MCD-3 Automation Guide.
Removing client software You can remove the client software from the client PCs via the
Windows Add or Remove Programs function. For instructions, refer to
How to Remove dSPACE Software on page 208.
After you install ControlDesk Next Generation on the
server PC, you will also find the
dSPACE_MCD3Client_Setup_<version>.exe file in
<InstallationFolder>\ControlDesk\MCD3ClientSetup
on the server PC. You can copy the file to the client PC
and then run it.
ST M
ST M
Installing dSPACE Software
Software Installation and Management Guide May 2012
I
110

Preconfigured Automatic Installations
Objective In addition to interactive installation (= standard installation), the setup
programs provide an automatic installation feature. You can record an
initial interactive installation and then use it to install dSPACE software
on several host PCs automatically.
This makes installation on several PCs quicker and easier.
Where to go from here Information in this section
Basics on Preconfigured Automatic Installations
Objective If you want to install a dSPACE software product (RCP and HIL
software, AutomationDesk, ControlDesk Next Generation, TargetLink,
Model Compare, or SystemDesk) on several host PCs, you can use the
setup's automatic installation feature to make installation quicker and
easier.
Basics on preconfigured
automatic installations
The dSPACE setup programs are based on the MSI technology from
Microsoft. They have their own configuration program, dSPACE Setup,
which installs the MSI setups and enables automatic preconfigured
software installation. It is therefore not possible to use third-party MSI
deployment tools which use MSI transformations for automatic
installation on several PCs.
The setup programs provide a record mode and an unattended mode.
Using the record mode you can record the installation configuration of
dSPACE software. Afterwards you can use the recorded configuration
file to install the software on other PCs automatically in setup's
unattended mode. The recording contains all the entries you made
during installation. Manual entries are therefore unnecessary. A log file
tells you whether the installation finished successfully or errors
occured.
You can also automatically install several setups successively via batch
file.
Basics on Preconfigured Automatic Installations 110
How to Install dSPACE Software Automatically in
Unattended Mode
114
Installing dSPACE Software
Software Installation and Management Guide May 2012 111
I

Accessing record and
unattended mode
You can access the two modes via command line tool, for example,
cmd.exe from Windows.
When you use long path and file names with spaces on the command
line, enclose the names in double quotation marks. This indicates that
spaces within the quotation marks are not command line delimiters.
Overview of commands and parameters To open a help list,
which shows all the commands and optional parameters available for
the modes, open a Command Prompt window and type:
<Drive>\Products\Install_<SoftwareProduct>.exe -help
Example: D:\Products\Install_TargetLink.exe -help
Suppressing security
warnings under Windows
7 and Windows Vista
When Windows attempts to validate the dSPACE device driver
packages and discovers that a package is signed by a certificate that is
not yet in the Trusted Publishers certificate store, Windows outputs a
security warning. Select the Always trust ... option to continue the
software installation.
To install dSPACE software in unattended mode, you have to suppress
these security warnings. This is done by installing trusted dSPACE
certificates on the PC that the dSPACE software is to be installed on.
Getting dSPACE certificates The dSPACE certificates are
generated when you install the dSPACE software interactively in the
usual way. The generated certificates are valid only for a specific
dSPACE Release, but can be used for unattended software installation
on multiple PCs.
You can access the generated dSPACE certificates (*.cer) and export
them via the Microsoft Management Console. For detailed
instructions, refer to the documentation from Microsoft.
Importing trusted dSPACE certificates The dSPACE certificates
can be imported (= installed) by a local user (with administrator rights)
as well as by a network or domain administrator. Use the Microsoft
Management Console for this. For detailed instructions, refer to the
documentation from Microsoft.
You can open cmd.exe, for example, as follows: From the
Start menu, choose Run ..., enter cmd and click OK.
Commands and parameters (such as --configonly) must
be written as shown below. They are case-sensitive.
Installing dSPACE Software
Software Installation and Management Guide May 2012
I
112

Unattended installation of
several dSPACE products in
a queue
To install several dSPACE products automatically in one run, you can
use a batch file. The recommended order of the setups included in the
batch file is shown in the example below.
Example of batch file
<Drive>\Products\Install_RCP_HIL.exe --install --load "c:\_myRCPHILinstallation.ini" --nogui --noreboot --
ignorependingreboot
<Drive>\Products\Install_AutomationDesk.exe --install --load "c:\_myAutomationDeskinstallation.ini" --nogui --noreboot
--ignorependingreboot
<Drive>\Products\Install_ControlDesk.exe --install --load "c:\_myControlDeskinstallation.ini" --nogui --noreboot --
ignorependingreboot
<Drive>\Products\Install_SystemDesk.exe --install --load "c:\_mySystemDeskinstallation.ini" --nogui --noreboot --
ignorependingreboot
<Drive>\Products\Install_MdlCmp.exe --install --load "c:\_myModelCompareinstallation.ini" --nogui --noreboot --
ignorependingreboot
<Drive>\Products\Install_TargetLink.exe --install --load "c:\_myTargetLinkinstallation.ini" --nogui --noreboot --
ignorependingreboot
You can open the Microsoft Managment Console as
follows: From the Start menu, choose Run..., enter mmc
and click OK.
To install several products without reboots interrupting
the installation procedure, you must add the --noreboot
and the --ignorependingreboot parameter to the
command.
When the actions defined in the batch file are finished,
you have to reboot your host PC manually.
Installing dSPACE Software
Software Installation and Management Guide May 2012 113
I

Getting information of required setups Especially when the
installation of software is controlled only via license information, you
may not know which product is available in which setup. To get the
information, use the dSPACE Master Setup beforehand und execute it
until the Start Copying Files dialog appears. The dialog lists the
necessary setups (in a recommended order) which you need for
installing software according to your license information.
The example below shows the Start Copying Files dialog for a
complete installation of AutomationDesk with its available software
packages.
Use the information (displayed setups and their order) to create your
batch file.
Unattended installation of
patches
You also can install a patch in unattended mode. To open a help list,
which shows all the commands and optional parameters available for
the patch, open a Command Prompt window in the path where the
patch is available and type: <Patchname>.exe -help .
To install the patch with the corresponding product automatically in
one run, use a batch file as shown in the example below.
<Drive>\Products\Install_RCP_HIL.exe --install --load "c:\_myRCPHILinstallation.ini" --nogui --noreboot --
ignorependingreboot
<Drive>\Updates\<Patchname>.exe --install "c:\dSPACE\RCP_HIL_7.3" --nogui --ignorependingreboot
Installing dSPACE Software
Software Installation and Management Guide May 2012
I
114

How to Install dSPACE Software Automatically in
Unattended Mode
Basic information Before starting the installation worksteps, you should familiarize
yourself with the basics in Basics on Preconfigured Automatic
Installations on page 110.
Restrictions n You cannot use the unattended mode with the dSPACE Master
Setup.
n You need a separate recording for each version of the dSPACE
software. For example, you cannot use a recording of TargetLink
from Release 7.3 with the next version of TargetLink.
Preconditions n You need administrator rights to install dSPACE software.
n The host PCs on which you want to install software in unattended
mode and the host PC on which you record the installation must
have the same configuration. This includes the operating system,
the third-party software (for example, MATLAB), the referenced
license files, and all installation folders (including the drive letter). If
the configuration of the host PCs on which you want to install
differs from the configuration of the host PC on which you record,
this can cause errors because the installation waits for answers from
dialogs which were not recorded.
n Microsoft .NET Framework 4.0 should be installed on the host PCs
beforehand to shorten installation time and to avoid reboot
requests when installed in unattended mode.
n Valid only for Windows 7 and Windows Vista: To suppress security
warnings when the setup installs the dSPACE device drivers a
dSPACE certificate (*.cer) must be installed on the PC that the
dSPACE software is to be installed on.
Method To install dSPACE software automatically via unattended mode
1 Record the dSPACE software installation by running the setup in
record mode. Open a Command Prompt window and type the
following command according to the software product you want to
install. The command must state your INI file name and the path to
save the file to.
n <Drive>\Products\Install_RCP_HIL.exe --install --save
"c:\_myRCPHILinstallation.ini" --configonly
Installing dSPACE Software
Software Installation and Management Guide May 2012 115
I

n <Drive>\Products\Install_AutomationDesk.exe --install
--save "c:\_myAutomationDeskinstallation.ini" --
configonly
n <Drive>\Products\Install_ControlDesk.exe --install --save
"c:\_myControlDeskinstallation.ini" --configonly
n <Drive>\Products\Install_TargetLink.exe --install --save
"c:\_myTargetLinkinstallation.ini" --configonly
n <Drive>\Products\Install_TargetLink_x64.exe --install --
save "c:\_myTargetLinkx64installation.ini" --configonly
n <Drive>\Products\Install_MdlCmp.exe --install --save
"c:\_myMdlCompareinstallation.ini" --configonly
n <Drive>\Products\Install_MdlCmp._x64exe --install --save
"c:\_myMdlComparex64installation.ini" --configonly
n <Drive>\Products\Install_SystemDesk.exe --install --save
"c:\_mySystemDeskinstallation.ini" --configonly
All entries you make during installation are written to the specified
INI file.
2 Copy your INI file to the host PCs on which you want to install the
software.
3 Run the setup on the host PCs on which you want to install the
software. Open a Command Prompt window and enter the
following command according to the software product you want to
install. The command must state the INI file to be executed and its
path.
n <Drive>\Products\Install_RCP_HIL.exe --install --load
"c:\_myRCPHILinstallation.ini" --nogui
n Use the --configonly parameter if you want to
record only the configuration of the setup program,
without starting the software installation.
n The parameter --configonly can only be used in
conjunction with the parameter --save.
n To modify an existing record file (*.ini), use the
following command:
<Drive>\Procucts\Install_<SoftwareProduct>.ex
e --install --load "c:\_myinstallation.ini"
--save "c:\_myinstallation_modified.ini"
--configonly
n An existing file with the same name will be
overwritten.
Installing dSPACE Software
Software Installation and Management Guide May 2012
I
116

n <Drive>\Products\Install_AutomationDesk.exe --install
--load "c:\_myAutomationDeskinstallation.ini" --nogui
n <Drive>\Products\Install_ControlDesk.exe --install --load
"c:\_myControlDeskinstallation.ini" --nogui
n <Drive>\Products\Install_TargetLink.exe --install --load
"c:\_myTargetLinkinstallation.ini" --nogui
n <Drive>\Products\Install_TargetLink_x64.exe --install
--load "c:\_myTargetLinkx64installation.ini" --nogui
n <Drive>\Products\Install_MdlCmp.exe --install --load
"c:\_myMdlCompareinstallation.ini" --nogui
n <Drive>\Products\Install_MdlCmp.exe --install --load
"c:\_myMdlComparex64installation.ini" --nogui
n <Drive>\Products\Install_SystemDesk.exe --install --load
"c:\_mySystemDeskinstallation.ini" --nogui
Installing dSPACE Software
Software Installation and Management Guide May 2012 117
I

4 Reboot your host PC.
The following parameters can be added to the
command to perform specific tasks:
n --nogui: Use this optional parameter if you want to
install the software without user interaction. If you
do not use this parameter, the dialogs of the setup
program appear including the recorded user
settings. To continue the installation, you must
confirm each dialog.
n --noreboot: Use this optional parameter only in
combination with the --nogui parameter. If you use
this parameter, the reboot dialog at the end of the
setup is not displayed and the installation finishes
without rebooting. If you do not use this parameter,
the reboot dialog opens and waits for user
interaction. This parameter should be used if
multiple unattended installations are executed in a
queue.
n --logfile "<drive>\_mylogs": Use this optional
parameter if you want to save the log files to a
specific folder. After software installation, the log
files will be in the specified folder. You have to
provide the full path for the folder of the log files.
n --ignorependingreboot: Use this optional
parameter if you want to skip the detection for a
pending reboot when the setup starts. It is helpful
in the following use scenarios:
o Multiple dSPACE software products have to be
installed in a queue.
o The dSPACE setup program displays a reboot
request even if a reboot was just performed. This
can happen if third-party software sets specific
registry entries to trigger dSPACE software to
reboot.
Installing dSPACE Software
Software Installation and Management Guide May 2012
I
118

Next steps Check the setup log files for errors.
To get the location of the setup log files, run
<Drive>\Products\Install_<SoftwareProduct>.exe -help via
command line tool. The full path to the folder with the setup logs is
displayed in the dSPACE Setup Commands dialog as shown in the
example below:
The dSPACEInstaller.log file contains the result code indicating
whether or not the unattended installation succeeded. An integer
value is assigned to the BOOTSTRAPPER_GLOBALRETURN key name at
the end of the log file. A successful unattended installation has result
code 0 as shown in the example below:
564 2010-10-11 08:03:03.2948 INFO
dSPACE.SetupGen.Bootstrapper.Bootstrapper.Main:;
BOOTSTRAPPER_GLOBALRETURN: 0
Contact dSPACE Support for further instructions if either of these
situations arises:
n The result code (BOOTSTRAPPER_GLOBALRETURN) is not 0.
n The log file is not located in the folder described above.
Installing dSPACE Software
Software Installation and Management Guide May 2012 119
I

Advanced commands The automatic installation feature provides commands for advanced
tasks.
Repairing an installation
<CommonProgramFiles(x86)>\dSPACE\Setup\{<MainProductCode>}\Boo
tstrapper.exe --repair {<MainProductCode>} --nogui: Repairs the
dSPACE installation that has the specified main product code.
Example: "C:\Program Files (x86)\Common
Files\dSPACE\Setup\{AB28949A-7642-4BCE-AB77-
172A8DD1C430}\Bootstrapper\Bootstrapper.exe" --repair
{AB28949A-7642-4BCE-AB77-172A8DD1C430} --nogui
Removing an installation
<CommonProgramFiles(x86)>\dSPACE\Setup\{<MainProductCode>}\Boo
tstrapper\Bootstrapper.exe --uninstall {<MainProductCode>} --
nogui: Removes the dSPACE installation that has the specified main
product code.
Example: "C:\Program Files (x86)\Common
Files\dSPACE\Setup\{D7AA2FFD-E7C6-4823-9FE6-
8A485CFF3110}\Bootstrapper\Bootstrapper.exe" --uninstall
{D7AA2FFD-E7C6-4823-9FE6-8A485CFF3110} --nogui
Installing dSPACE Software
Software Installation and Management Guide May 2012
I
120

I
121

Software Installation and Management Guide May 2012


Managing Installations with the
dSPACE Installation Manager
Objective The dSPACE Installation Manager handles all the dSPACE installations
available on your PC and provides detailed information, for example,
on properties and installed products.
Where to go from here Information in this section
Information in other sections
Preconditions and Restrictions for Working with the
dSPACE Installation Manager
122
How to View Installation Details 123
How to Activate a dSPACE Installation 126
How to Deactivate the Active Installation 130
How to Remove a dSPACE Installation via dSPACE
Installation Manager
235
Managing Installations with the dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
122

Preconditions and Restrictions for Working with the dSPACE
Installation Manager
Preconditions n To manage dSPACE installations (for example, to activate or to
deactivate an installation and to perform MATLAB integration) you
need administrator rights.
n The required version of the dSPACE Installation Manager depends
on the latest version of dSPACE software installed on your system.
o As of dSPACE Release 7.3, you have to use at least dSPACE
Installation Manager 3.3. This is provided by dSPACE Release
7.3.
o Since the dSPACE Installation Manager is downward compatible,
you can always use its latest version to manage your
installations.
o You can download the most recent version of the dSPACE
Installation Manager from http://www.dspace.com/goto?IM.
Restrictions
n You cannot use the dSPACE Installation Manager to
install dSPACE software on your PC.
n As of dSPACE Release 7.2, you cannot remove dSPACE
software via the dSPACE Installation Manager
Managing Installations with the dSPACE Installation Manager
Software Installation and Management Guide May 2012 123
I

How to View Installation Details
Objective The dSPACE Installation Manager handles all the dSPACE installations
available on your PC and provides detailed information, for example,
on properties and installed products.
Method To view installation details
1 Quit all dSPACE programs and MATLAB (if used).
2 From Start Programs dSPACE Installation Manager, select dSPACE
Installation Manager.
The dSPACE Installation Manager displays a list of all the available
dSPACE installations in the dSPACE Installations window on the
Installation Sets page.
The available installations are displayed with their version numbers,
installation paths and states (active or inactive).
3 Select an installation from the list.
Managing Installations with the dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
124

Further details of the selected installation are displayed on separate
pages at the right side in the dSPACE Installations window.
Page Description
Products Lists of all the dSPACE products included in the selected
installation together with the respective version numbers.
Managing Installations with the dSPACE Installation Manager
Software Installation and Management Guide May 2012 125
I

4 Optional: In the Annotation edit field, edit an identifier. All
characters are allowed.
Connect to MATLAB Release Performs MATLAB integration for the selected dSPACE software
installation, i.e., you can connect the dSPACE installation to one
or more MATLAB installations and select the preferred MATLAB
connection (if this feature is available for the selected
installation).
MATLAB integration for RCP and HIL software installations from
dSPACE Release 7.0 and 7.1 (and installations of dSPACE
Release 6.6 or earlier) is also shown, but you cannot change the
integration via the dSPACE Installation Manager.
This page is only displayed for dSPACE installations which
require MATLAB for working.
Connect to dSPACE Release Performs the combination of several dSPACE installations to an
installation set.
This page is only displayed for TargetLink and Model Compare
installations from dSPACE Release 7.0 and 7.1.
Page Description
Managing Installations with the dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
126

Your input in the Annotation edit field is saved automatically during
editing.
Related topics
How to Activate a dSPACE Installation
Active Installation One of each installation of various dSPACE software products is known
as the active installation.
n The last installation of a software product that you install on your
host PC automatically becomes the active installation.
n If your system contains more than one installation (from different
releases or multiple instances of the same release), you can activate
another installation manually. The previous active installation then is
deactivated automatically.
Effects of Activating The effects of activating a dSPACE installation depend on the software
product you use.
RCP and HIL software Activating a specific RCP and HIL software
installation means modifying environment variables. In addition the
shortcut keys in the Start Programs menu and the uninstall entries of
the operating system are altered according to the selected installation.
The uninstall entries are accessible, via Start Control Panel Add or
Remove Programs (valid for Windows XP).
Before you can use a product from a deactivated RCP and HIL
installation, you have to activate this installation and then reboot your
host PC. You can work with only one RCP and HIL installation at a
time.
Basics
Features of the dSPACE Installation Manager on page 23
How to Activate a dSPACE Installation on page 126
HowTos
How to Deactivate the Active Installation on page 130
How to Remove a dSPACE Installation via dSPACE Installation Manager on page 235
How to Restore the Default Settings for the Active Installation on page 230
Not every dSPACE software product needs to be activated
before usage. So this function is, for example, not
available for the installations of TargetLink and Model
Compare as of dSPACE Release 7.0.
Managing Installations with the dSPACE Installation Manager
Software Installation and Management Guide May 2012 127
I

SystemDesk Activating a specific SystemDesk installation means
registering SystemDesks Automation feature and linking SystemDesk's
project (SDP) files to the active installation. To access an inactive
SystemDesk installation via automation, however, you have to supply
version information of the inactive SystemDesk installation. For details,
refer to Automating Different SystemDesk Versions ( SystemDesk
Guide).
You can activate a SystemDesk installation without rebooting your
host PC.
ControlDesk Next Generation Activating a specific ControlDesk
Next Generation installation means registering ControlDesk Next
Generations Automation feature. You can also work with an inactive
ControlDesk Next Generation installation. To access an inactive
ControlDesk Next Generation installation via automation, however,
you have to supply version information of the inactive ControlDesk
Next Generation installation. For details, refer to Automating Different
ControlDesk Versions ( ControlDesk Next Generation Basic
Practices Guide).
You can activate a ControlDesk Next Generation installation without
rebooting your host PC.
AutomationDesk Activating a specific AutomationDesk
installation means registering default settings and file assignments for
automatic tasks, for example, to open ADP files from other software
products. You can also work with an inactive AutomationDesk
installation, but then these automatic tasks are not provided.
You can activate an AutomationDesk installation without rebooting
your host PC.
Real-Time Testing (RTT) Activating a specific RTT version means
that all products that can work with RTT (ControlDesk, ControlDesk
Next Generation, AutomationDesk, Python, customer software)
automatically use the activated installation. You cannot work with an
inactive RTT installation.
You can activate a Real-Time Testing installation without rebooting
your host PC.
Precondition You have administrator rights.
ST M
ST M
Managing Installations with the dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
128

Method To activate an installation
1 Exit all dSPACE programs and MATLAB (if used).
2 From Start Programs dSPACE Installation Manager, select dSPACE
Installation Manager.
The Installation Manager opens.
3 In the dSPACE Installations window, select the installation you want
to activate.
4 To activate the selected installation, click Activate.
5 Valid only for the RCP and HIL software installation: When
prompted, reboot your system.
Managing Installations with the dSPACE Installation Manager
Software Installation and Management Guide May 2012 129
I

Result The selected installation becomes the active installation.
The current settings of the installation that you deactivated are saved
automatically. The previously saved settings of the installation that you
are activating are restored. If the dSPACE Installation Manager cannot
find previously saved settings for the installation that you are
activating, the factory default settings are applied.
The selected installation becomes the active installation.
Valid only for the RCP and HIL software installations:
n The shortcut keys in the Start Programs menu and the uninstall
entries (Start Settings Control Panel Add/Remove Programs) are
adapted according to the selected installation.
n When you restart the dSPACE Installation Manager after reboot, the
newly activated dSPACE installation is displayed in the dSPACE
Installations window.
Related topics
This procedure may take some time.
Basics
Features of the dSPACE Installation Manager on page 23
HowTos
How to Remove a dSPACE Installation via dSPACE Installation Manager on page 235
How to Restore the Default Settings for the Active Installation on page 230
How to View Installation Details on page 123
Managing Installations with the dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
130

How to Deactivate the Active Installation
Objective You can deactivate the active installation of the corresponding
software product without activating another one.
This can be useful if you want to install a software product from a
dSPACE Release which is older than the currently active installation.
Deactivating the active installation automatically during installation of
an older release might be incomplete, and reactivating it might be
impossible. Deactivating the active installation manually before
installing older releases ensures that it is deactivated completely.
Active installation One of each installation of a dSPACE software product is known as the
active installation.
n The last installation of a software product that you install on your
host PC automatically becomes the active installation.
n If your system contains more than one installation (from different
releases or multiple instances of the same release), you can activate
a specific installation manually. The previous active installation then
is deactivated automatically.
Precondition You have administrator rights.
Method To deactivate the active installation
1 Quit all dSPACE programs and MATLAB (if used).
2 From Start Programs dSPACE Installation Manager, select dSPACE
Installation Manager.
The Installation Manager opens.
3 In the dSPACE Installations window, select the active installation.
Managing Installations with the dSPACE Installation Manager
Software Installation and Management Guide May 2012 131
I

4 Click Deactivate.
5 Valid only for the RCP and HIL software installation: When
prompted, reboot your system.
Result The dSPACE Installation Manager deactivates the installation and saves
its settings.
Valid only for the RCP and HIL software installation: When you restart
the dSPACE Installation Manager after reboot, no installation of the
corresponding dSPACE product is active.
Next steps Install the older dSPACE Release. It becomes the active installation.
Refer to Installing dSPACE Software Products on page 92.
This procedure may take some time.
Managing Installations with the dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
132

Related topics
Basics
How to Activate a dSPACE Installation on page 126
I
133

Software Installation and Management Guide May 2012


Integrating MATLAB into dSPACE
Software
Objective If you want to work with dSPACE software which requires MATLAB, a
MATLAB installation must be integrated into the dSPACE software.
Only an integrated (= connected) MATLAB installation is prepared for
use with dSPACE software.
Where to go from here Information in this section
Basics on Integrating a MATLAB Installation 134
How to Change the MATLAB Integration 139
Integrating MATLAB into dSPACE Software
Software Installation and Management Guide May 2012
I
134

Basics on Integrating a MATLAB Installation
Objective Only an integrated (= connected) MATLAB installation is prepared for
use with dSPACE software.
Possible combinations of
installations
The dSPACE setup programs and the dSPACE Installation Manager lets
you connect to MATLAB installations simply by selecting checkboxes.
The illustration below serves as an example and shows possible
combinations of MATLAB and dSPACE installations:
n It is possible to connect a single dSPACE installation to several
MATLAB installations.
Offline Simulator
MATLAB installation
... connected to ...
RCP and HIL
Preferred connection
Preferred connection
AutomationDesk
TargetLink
(32-bit)
Model Compare
(32-bit)
TargetLink
(64-bit)
Model Compare
(64-bit)
R2011b (64-bit)
R2011a (64-bit)
R2011b (32-bit)
R2011a (32-bit)
R2010b SP1
(32-bit)
dSPACE installation
as of dSPACE Release 7.2
Integrating MATLAB into dSPACE Software
Software Installation and Management Guide May 2012 135
I

n Several dSPACE installations can be connected to one MATLAB
installation. It is no longer a requirement that each dSPACE
installation (to be used with MATLAB) needs a separate MATLAB
installation. This reduces installation time and disk space.
n You can install a new MATLAB installation on your host PC without
reinstalling dSPACE software. To use the new installation, you just
have to connect it to the dSPACE software.
n You can connect only compatible MATLAB installations to a dSPACE
installation. For an overview of compatible products on dSPACE
Release 7.3, refer to Required MATLAB Releases on page 69.
n Only products with the same bit version can be connected and used
together. For example, TargetLink's 64-bit version can be connected
to a 64-bit version but not to a 32-bit version of MATLAB.
Preferred connection If you have connected several MATLAB installations to your dSPACE
installation, some dSPACE software products require that you select
one of them as the preferred connection. If you connect only one
MATLAB installation, this automatically is the preferred MATLAB
installation.
A preferred connection is the default MATLAB installation which is
used by the dSPACE products, for example, when dSPACE software
products generate specific MATLAB files or automatically start
MATLAB. You can change the preferred MATLAB installation via the
dSPACE Installation Manager anytime after initial installation of
dSPACE software.
Integrating MATLAB into dSPACE Software
Software Installation and Management Guide May 2012
I
136

Options for performing
MATLAB integration
You can perform MATLAB integration either during the initial
installation of dSPACE software or at a later date.
Integration during initial installation of the dSPACE software
The setup program asks which MATLAB installation on your host PC
you want to connect to (integrate into) the dSPACE software.
The setup programs provide the Select MATLAB Support dialog shown
below. This dialog shows all the compatible and locally installed
MATLAB installations as of MATLAB Release R2007b. You can link the
dSPACE software to a specific MATLAB installation via the Connect To
checkbox.
Integration at a later date After installing dSPACE software on
your host PC, you have to use the dSPACE Installation Manager to
change the MATLAB integration. There are two scenarios for this:
n The dSPACE software was installed without selecting a MATLAB
installation during the initial setup, for example, because you want
to install MATLAB after installing the dSPACE software.
n You install an additional MATLAB installation and you want the
dSPACE software to use it.
MATLAB installations which are installed on a network
drive are not listed automatically and must be added
manually via the Add MATLAB Installation to View button.
This also applies if a MATLAB installation was
reinstalled without reinstalling the dSPACE software.
Integrating MATLAB into dSPACE Software
Software Installation and Management Guide May 2012 137
I

The following screenshot shows the Connect to MATLAB Release page,
where you can connect the dSPACE software by selecting the
Connected checkbox.
For instructions, refer to How to Change the MATLAB Integration
on page 139.
Integrating MATLAB into dSPACE Software
Software Installation and Management Guide May 2012
I
138

Overview of available
MATLAB installations
The dSPACE Installation Manager provides an overview of all the
available MATLAB installations.
The MATLAB Integration page (shown above) provides the following
features:
n All MATLAB installations (on your host PC) are listed automatically
with their installation details and their current integration statuses.
n You can manually add a MATLAB installation which is installed in a
network (and not on your host PC) to connect it to dSPACE
software. For this, use the Add ... button (see above).
n You can remove all connections between a specific MATLAB
installation and several dSPACE installations with one click via the
Remove button (see above).
n Error messages showing a failed MATLAB integration are displayed,
for example, when you try to connect to a MATLAB installation
which is not compatible with the dSPACE installation.
Integrating MATLAB into dSPACE Software
Software Installation and Management Guide May 2012 139
I

How to Change the MATLAB Integration
Objective If you want to change the MATLAB integration, for example, because
you have installed MATLAB after the initial installation of the dSPACE
software, you have to use the dSPACE Installation Manager.
Preconditions n You have administrator rights.
n A compatible MATLAB installation is available.
Method To change the MATLAB integration
1 From Start Programs dSPACE Installation Manager, select dSPACE
Installation Manager.
The Installation Manager opens.
2 Click the MATLAB Integration tab.
The MATLAB Integration window opens. All the MATLAB
installations which are installed on your host PC are listed
automatically.
Integrating MATLAB into dSPACE Software
Software Installation and Management Guide May 2012
I
140

3 Check if your desired MATLAB installation is listed on the page. If it
is not listed, but it is installed on a network drive, you can add this
installation via the Add ... button.
4 Click the Installation Sets tab.
5 In the dSPACE Installations window, select the installation that you
want to connect to a MATLAB installation.
6 On the Connect to MATLAB Release page select the desired
MATLAB installation, by selecting the Connected checkbox.
MATLAB installations which are installed on a network
drive are not listed automatically and must be added
manually.
Integrating MATLAB into dSPACE Software
Software Installation and Management Guide May 2012 141
I

7 Only valid for dSPACE software products which require a preferred
connection:
If you have connected several MATLAB installations to your dSPACE
installation: Choose one of them as the preferred connection.
dSPACE products use the preferred installation as the default, for
example, to start MATLAB automatically.
Result The dSPACE installation is connected to the new MATLAB installation.
MATLAB integration for RCP and HIL software
installations of dSPACE Release 7.1 or earlier is also
shown, but you cannot change this integration via the
dSPACE Installation Manager.
If you connect only one MATLAB installation this
automatically is the preferred MATLAB installation.
Integrating MATLAB into dSPACE Software
Software Installation and Management Guide May 2012
I
142

I
143

Software Installation and Management Guide May 2012


Managing dSPACE Licenses
Objective Various dSPACE products on the dSPACE DVD are license-protected.
The dSPACE Installation Manager makes it easy to display and manage
license information. Note that handling dSPACE licenses is necessary
only in specific use scenarios.
Where to go from here Information in this section
Basics on dSPACE License Types 144
Managing Licenses in a Local License.dsp File (=
Run-Time Licenses)
149
Merging License Files 162
Specifics on Using Floating Network Licenses 173
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
144

Basics on dSPACE License Types
Objective Two different license types (dongle license, floating network license)
are available for working with the dSPACE software after installation,
depending on your order.
Where to go from here Information in this section
Dongle License Mechanism
Basics on the mechanism With dongle licenses, the dSPACE software is protected by a license
mechanism based on an execution key (dongle) and a license file. The
local license files (one for each software installation to be installed on
your host PC) are created automatically from the supplied license
information during installation. To execute applications protected by
license, the license must be enabled with a dongle.
Elements dSPACE dongle licensing is based on three elements:
n Execution key (dongle)
n Keys.dsp file
n License.dsp file
You receive the Keys.dsp and License.dsp files via e-mail in a ZIP
archive.
Dongle License Mechanism 144
Floating Network License Mechanism 146
keys.dsp license.dsp
dSPACE license ID
# 8899
8899_R71.zip
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 145
I

Dongle The dongle has to be connected to an USB port of your PC.
A special version of the dongle for the connection to a parallel port is
available on request.
Keys.dsp file The Keys.dsp file contains information on the software products you
can install from the related dSPACE Release. The Keys.dsp file is
associated with a specific software release, but not with a specific
license ID. It is used only during software installation.
License.dsp file The License.dsp file contains information on the products you can run
with a specific dongle. Only software components that need a license
code are listed here. The license-free components, for example,
various Real-Time Libraries (RTLibs) are not listed. The License.dsp file
is associated with a specific software release and the license ID.
If a dSPACE DVD contains different versions of a product, multiple
license entries can be present in the supplied License.dsp file.
Before sending the license files via e-mail, dSPACE creates
a ZIP archive which contains the license files and changes
the file name extension of the ZIP archive to .piz to
prevent them being filtered by your e-mail server.
It is strongly recommended to make a backup copy of the
license files.
Install the dSPACE software including the WIBU-KEY
driver before connecting the dongle to the USB port.
You can use several dongles of identical or different types
at the same time on your PC. The dongles for the parallel
port can even be connected in series.
The dSPACE license ID is indicated on the dongle shell.
The number is also registered in the License.dsp file.
dSPACE Support can identify your dSPACE software
components by it.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
146

The local license file is created on your hard disk from the supplied
license information automatically during the installation of the dSPACE
software. This file can contain entries for different dongles, however
the entries for dongles not connected to the PC are ignored. Each
software installation has it's own local license file.
Related topics
Floating Network License Mechanism
Basics of the mechanism If you purchased floating network licenses, one Windows PC in the
network has to be configured as the dSPACE License Server. The PCs
on which you want to run the dSPACE software (dSPACE License
Clients) need to be connected to the dSPACE License Server networked
via TCP/IP.
With floating network licenses, the dSPACE License Client
automatically requests the license required by a particular action from
the connected dSPACE License Server (automatic activation). If there is
at least one license available, you can go on working with the dSPACE
software as usual. At the same time, the license is blocked for other
clients.
Elements The license mechanism is based on three files, which are supplied via
e-mail in a ZIP archive:
n Keys.dsp file
n License.dsp file
n License.dat file
Basics
Managing Licenses in a Local License.dsp File (= Run-Time Licenses) on page 149
Merging License Files on page 162
Migrating to Floating Network Licenses on page 201
HowTos
How to Enable Dongle Licenses on page 104
How to Show Available Licenses on page 149
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 147
I

The following illustration serves as an example.
Keys.dsp file The Keys.dsp file contains information on the software products you
can install from the related dSPACE Release. The Keys.dsp file is
associated with a specific software release. It is used only during
software installation and only for the dSPACE License Clients.
License.dsp file The License.dsp file contains information on the products you can run
with a floating network license. Only software components that need
a license code are listed here. The unlicensed components, for
example, various Real-Time Libraries (RTLibs) are not listed. The
License.dsp file is associated with a specific software release. This file
is needed only for the dSPACE License Clients.
If a dSPACE DVD contains different versions of a product, multiple
license entries can be present in the supplied License.dsp file.
A local license file is created on the dSPACE License Clients hard disk
from the supplied license information. This is an automatic action
during the installation of the dSPACE software.
Before sending the license files via e-mail, dSPACE creates
a ZIP archive which contains the license files and changes
the file name extension of the ZIP archive to .piz to
prevent them being filtered by your e-mail server.
It is strongly recommended to make a backup copy of the
license files.
keys.dsp license.dsp license.dat
8899_R71.zip
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
148

License.dat file The License.dat file contains the floating network license codes for
the available dSPACE products and information on the validity of the
licenses.
A local License.dat file is created from the supplied license
information on the hard disk of the dSPACE License Server and on the
hard disks of the dSPACE License Clients. This is an automatic action
during the installation of the dSPACE software.
Basics of timeout
mechanism
There is a timeout mechanism for several dSPACE licenses. If you do
not perform an action triggering an automatic license check for more
than 30 minutes (default linger time), the license is released and can
be used by other dSPACE License Clients.
After a process has finished, for example, by closing an RTI block
dialog or a TargetLink model on the dSPACE License Client, the license
remains reserved for that client until the timeout occurs.If a dSPACE
License Client crashes, the corresponding licenses remain reserved for
that client until the timeout occurs.
Extending the linger time The linger time of products protected by floating network licenses is
set to a default value. Using the FLEXnet Publisher software, the
default linger time can be extended on the dSPACE License Server. This
ensures that you can use a protected product or module for a longer
period without losing the license.
However, you cannot specify timeout values less than 30 minutes. For
details, for example, on how to extend the linger time, refer to the
FLEXnet License Administration Guide. To access it, select:
n On the dSPACE License Server: Start Programs dSPACE License
Server FLEXnet Licensing End User Guide
n Or open the Tools\LicenseServer\fnp_LicAdmin.pdf file on the
dSPACE DVD.
License behavior of specific
products
For details on the license protected dSPACE software products and
with explanations on how they work with floating network licenses,
refer to License Behavior of Specific Products on page 188.
As of dSPACE Release 7.2, the License.dat file is
required only for installing the dSPACE License Server but
not for installing the dSPACE software on the dSPACE
License Clients.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 149
I

Managing Licenses in a Local License.dsp File
(= Run-Time Licenses)
Use cases for managing
licenses
It is necessary to manage the licenses entries in a local License.dsp file
(= run-time licenses) in special use cases:
n Replacing existing licenses (for example, expired demo licenses)
with new ones
n Managing licenses on several dSPACE systems. This means that you
can install the dSPACE software on as many PCs as you like.
However, to run the software, the License.dsp file and the
matching dongle must be present.
n Installing a new license-protected dSPACE product on an existing
dSPACE system
The dSPACE Installation Manager provides several functions for this
purpose.
Where to go from here Information in this section
How to Show Available Licenses
Objective The available licenses are registered in the local License.dsp files. You
can view them with the dSPACE Installation Manager.
Method To show licenses available on your host PC
1 From Start Programs dSPACE Installation Manager, select dSPACE
Installation Manager.
2 Click the Licenses tab.
3 In the dSPACE Licensing window, click the Manage Runtime Licenses
tab.
How to Show Available Licenses 149
How to Add New Licenses to a Specific Local License
File
152
How to Activate, Deactivate or Remove Licenses 156
How to Restore a Specific License Configuration 159
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
150

The tabbed page lists all the dSPACE installations on your host PC
as shown below.
4 Click the Refresh available licenses button to update the
information.
5 Select an installation from the list and expand it to see the license
entries.
The entries in the local License.dsp file that is associated to the
selected installation on your PC are displayed. The table entries
(from left to right) have the following meanings:
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 151
I

Related topics
Entry Description
License name Name of the license.
Version Version of the license.
License ID Identification number of the license. The number also is indicated on the dongle
shell.
Available Yes means:
o Dongle licenses: The dongle which is needed to execute the software
protected by the license is connected to the host PC.
o Floating network license: At least one license is available on the dSPACE
License Server. The dSPACE License Client automatically requests the license
required by a particular action from the connected dSPACE License Server.
Active Yes means that the license is activated and the software protected by the license
can be used, when the corresponding dongle is connected to the host PC
(dongle license mechanism), or when a free license is available on the dSPACE
License Server (floating network license mechanism).
Expired Yes means that the license has expired.
Time-limited licenses are supplied, for example, if you purchased floating
network licenses, or if you received a demo license.
Expiration Date The date on which a time-limited license expires.
Kind Kind of license mechanism. The possible entries are:
o Full: Full unrestricted license
o Demo: Restricted, for example, time-limited license
Type Type of license mechanism. The possible entries are:
o WIBU: Dongle license
o FlexNet: Floating network license
Note Specific information on the license, for example, information on restrictions
when using the license.
Basics
Dongle License Mechanism on page 144
Managing Licenses in a Local License.dsp File (= Run-Time Licenses) on page 149
Merging License Files on page 162
HowTos
How to Enable Dongle Licenses on page 104
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
152

How to Add New Licenses to a Specific Local License File
Use scenarios for adding
licenses
In special cases it is necessary to add new licenses to a local
License.dsp file:
n If your dongle has been damaged and you need a replacement,
dSPACE provides you with a new dongle with a different license ID
and a new license information.
This license information is supplied via e-mail in a ZIP archive and
contains the same Keys.dsp and License.dsp files as the license
information of your old (damaged) dongle but with new key codes
for the new dongle. The License.dsp file from the new license
information has to be added to the License.dsp file on your PC.
The license codes for the damaged dongle can be deleted
afterwards.
n If your demo license expired and you need a replacement.
n If you have mistakenly deleted the licenses from a local license file.
Note that every dSPACE installation on your host PC contains its own
local license file.
Restrictions
Method To add new licenses to a specific local license file
1 From Start Programs dSPACE Installation Manager, select dSPACE
Installation Manager.
The dSPACE Installation Manager opens.
2 Click the Licenses tab.
3 In the dSPACE Licensing window, click the Manage Runtime Licenses
tab.
The dSPACE Installation Manager does not check for the
compatibility of the Keys.dsp and License.dsp files. It
adds every license that is not contained in the local
License.dsp file which belongs to a specific installation
on the hard disk.
If licenses of different versions of a dSPACE software
product are contained in the License.dsp file, the dSPACE
software might generate error messages that the licenses
are invalid. Make sure to use the correct license
information and add only licenses of one version of a
dSPACE product.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 153
I

The tabbed page lists all the dSPACE installations on your host PC
as shown below.
4 Click the Refresh available licenses button to update the
information.
5 Select the desired installation from the list and expand it to see the
license entries.
The entries in the local License.dsp file that is associated to the
selected installation on your PC are displayed.
6 Right-click a license entry.
7 From the context menu, select Renew - Renew and add licenses for
installation set by file.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
154

A Windows standard Open dialog opens.
8 In the Open dialog, specify the path of the new License.dsp file.
9 Click Open.
The licenses are copied from the new License.dsp file to the local
License.dsp file which is associated to the selected installation.
The following dialog appears when the process has finished:
If the new license.dsp is available in a ZIP or PIZ
archive, it is sufficient to specify the path to this file.
Unpacking the archive before adding the new licenses
is not necessary.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 155
I

10Click OK.
11If the new License.dsp file contains also license information for
dSPACE products in other dSPACE installations: Repeat the steps 5
to 10 for all relevant dSPACE installations on your host PC.
Result New licenses are added to the local license file which belongs to the
selected installation.
Next steps If you add new licenses, dSPACE Installation Manager automatically
creates a license backup before adding the licenses. A backup contains
a specific license configuration, which you can use for later
restoration.
Related topics
You can undo changes by restoring the license
configuration of a previous backup. For instructions, refer
to How to Restore a Specific License Configuration
on page 159.
Basics
Dongle License Mechanism on page 144
Merging License Files on page 162
HowTos
How to Activate, Deactivate or Remove Licenses on page 156
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
156

How to Activate, Deactivate or Remove Licenses
Objective With the dSPACE Installation Manager you can deactivate the licenses
that belong to a specific dongle, or remove these permanently from a
local License.dsp file.
Deactivated licenses must be reactivated before you can work with the
corresponding dSPACE products again.
Purpose of deactivating
licenses
If you have used the license information merge function to install
several dSPACE products on your PC, the local License.dsp file
contains entries for different dongles.
Each time you start a license-protected action, the running dSPACE
application checks the local License.dsp file for a valid license. This
procedure takes some time, according to the number of licenses
included in the local License.dsp file. You can shorten this procedure,
if you deactivate the licenses for dongles that are not connected to the
PC.
Precondition Two or more dongles must be available in your license file.
Method To activate, deactivate or remove licenses in a specific local
license file
1 From Start Programs dSPACE Installation Manager, select dSPACE
Installation Manager.
The dSPACE Installation Manager opens.
2 Click the Licenses tab.
3 In the dSPACE Licensing window, click the Manage Runtime Licenses
tab.
The tabbed page lists all the dSPACE installations on your host PC
as shown below.
If you have only one activated dongle in your license file,
the dSPACE Installation Manager does not let you
deactivate or remove it.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 157
I

4 Click the Refresh available licenses button to update the
information.
5 Select the desired installation from the list and expand it to see the
license entries.
The entries in the local License.dsp file that is associated to the
selected installation on your PC are displayed.
6 Select the license(s) which you want to deactivate, activate or
remove.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
158

7 Right-click a license entry.
8 From the context menu, select the desired action:
n Selected licenses - Activate to activate the selected license(s).
n Selected licenses - Deactivate to deactivate the selected
license(s).
n Remove - Remove selected licenses to remove the selected
license(s).
n Remove - Remove expired licenses to remove all expired licenses
available in your local license file.
Result The dSPACE Installation Manager carries out the changes.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 159
I

Next steps You can create a license backup via the License configuration backup
Create backup context menu command. A backup contains a specific
license configuration, which you can use for later restoration. If you
remove a license, dSPACE Installation Manager automatically creates a
backup before you remove it.
Related topics
How to Restore a Specific License Configuration
Objective You can restore a previous configuration of run-time licenses to undo
changes easily.
Basics on license backups A license backup allows you to restore a specific state of the license
configuration. The Installation Manager automatically creates backups
before you add/remove a license to/from the local license files. In
addition, you can create your own backup whenever required. The
License configuration backup Create backup context menu command
is available on the Manage Runtime Licenses tab. In this case other
actions such as activating and deactivating licenses are stored with the
backup.
The backup label contains the date and the time when it was created.
You cannot change this label, for example, mark it with a user-specific
name.
You can undo changes by restoring the license
configuration of a previous backup. For instructions, refer
to How to Restore a Specific License Configuration
on page 159.
Basics
Dongle License Mechanism on page 144
Merging License Files on page 162
HowTos
How to Add New Licenses to a Specific Local License File on page 152
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
160

Method To restore a specific license configuration
1 From Start Programs dSPACE Installation Manager, select dSPACE
Installation Manager.
The dSPACE Installation Manager opens.
2 Click the Licenses tab.
3 In the dSPACE Licensing window, click the Manage Runtime Licenses
tab.
The tabbed page lists all the dSPACE installations on your host PC.
4 Right-click anywhere on the list.
5 From the context menu, select License configuration backup
Restore backup.
The following dialog opens:
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 161
I

6 From the list, select a backup and click OK.
A dialog is displayed with the backup data for the restored license
configuration as shown below:
7 Click OK to finish the restoration.
Result You have restored the license configuration to a specific backup.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
162

Merging License Files
Where to go from here Information in this section
Basics on Merging License Information
Use scenarios There are three possible cases, where the license files merge feature of
the dSPACE Installation Manager is useful:
n Simplifying the dongle license handling for different dSPACE
products on several dSPACE systems
n Installing two or more software products of the same dSPACE
release in one run via dSPACE Master Setup. The software products
must be installed in different folders. They can be protected with
different license mechanisms.
n Before you can install a new license-protected dSPACE product
(that comes with separate license files) to an existing dSPACE
system, you must merge the license files of the new product and
the license files of the existing system.
Restriction
Basics on Merging License Information 162
How to Merge License Files 166
How to Modify the dSPACE Installation with
Merged Files
172
Merging license files for this use scenario is useful only
for installations from dSPACE Releases 7.1 and earlier.
As of dSPACE Release 7.2, the setup programs do not
require license information on the existing software
products to avoid uninstalling them automatically.
The dSPACE Installation Manager used for merging
license files generally does not check for the version
compatibility of License.dsp or Keys.dsp files. Make sure
that only license codes for the same software version are
merged or added to an existing License.dsp file on the
hard disk.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 163
I

Simplifying dongle license
handling
You can merge license files for different dongles that belong to the
same DVD (dSPACE Release) in master license files by using the merge
function. With these master license files you can install the dSPACE
software on several PCs, without having to care about the number of
the dongle that is actually connected to a particular PC.
Installing several software
products via dSPACE
Master Setup in one run
To install two or more dSPACE software products with the dSPACE
Master Setup in one run, the setup requires license information
containing all the Keys.dsp and License.dsp files of the software you
want to install in merged files. The dSPACE Master Setup then knows
which dSPACE software is available for installation and can set the
correct installation order.
If the license information for a dSPACE software product is missing,
the dSPACE Master Setup will not install the product. It is then not
listed in the Start Copying Files dialog of the dSPACE Master Setup
during installation. If a dSPACE software you want to install is missing
from this list, exit the dSPACE Master Setup and check the license
information for completeness.
If you place an order for all the dSPACE software you want to install in
one run, you receive a software package with the merged license files
as merged Keys.dsp and License.dsp files with the software.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
164

The illustration below shows the principle of merging license files for
an installation via dSPACE Master Setup:
If you place an order for all the dSPACE software you want to install in
one run, you will receive a software package with the merged license
files as merged Keys.dsp and License.dsp files with the software.
Adding a new product
Suppose you have several dSPACE systems (A, B, C) each with an
installed, licensed version of AutomationDesk. You also have one
additional software license for development tools like RTI and
compilers, maybe for a completely different dongle number (D). Let us
assume that you want to use the development tools on any one of the
AutomationDesk systems, but only on one system at a time. To do so,
Host PC
RCP and
HIL software
TargetLink
ControlDesk
Next Generation
Keys.dsp
License.dsp
RCP and HIL software
TargetLink
Model Compare
ControlDesk Next Generation
SystemDesk
License
information
Merged license information
Model Compare
SystemDesk
License
information
License
information
License
information
License
information
Merging license files for this use scenario is useful only for
installations from dSPACE Releases 7.1 and earlier. As of
dSPACE Release 7.2, the setup programs do not require
license information on the existing software products to
avoid uninstalling them automatically.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 165
I

you must merge license files (A, D), (B, D), (C, D) before adding
software products licensed on (D). With the merged license files,
components from (D) can be installed to each of the three systems.
But they will run only on the system where dongle (D) is presently
connected.
The illustration below describes this situation.
Use the dSPACE Maintenance Setup to install additional
products. Refer to How to Install Components of
Software Products Subsequently on page 99.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
166

Background If you install software using specific license files to the
same folder where software of the same release has already been
installed using different license files, all the software components that
are not also permitted for installation by the second license files are
uninstalled automatically.
Suppose you have installed software with license files allowing you to
install products a, b, c. Now you install software with other license files
allowing the installation of products a, d, e. After the second
installation only products a, d, e are left on the hard disk. Products b, c
are uninstalled. Repeating the installation with the first license files
reinstalls products a, b, c on the hard disk, but d, e are removed. This
problem occurs regardless of whether you have license files for the
same or different dongle numbers.
Instructions For detailed instructions, refer to How to Merge License Files
on page 166.
How to Merge License Files
Objective You can merge license files for different dSPACE software products to
make merged Keys.dsp and License.dsp files by using the merge
function of the dSPACE Installation Manager.
ZIP files You receive the Keys.dsp and License.dsp files via e-mail in a ZIP
archive.
Restrictions The restriction is valid for:
n As of dSPACE Release 7.1: Only valid for software products of the
RCP and HIL software package
n dSPACE Release 6.6 and earlier: For all software products
n Before sending the license files via e-mail, dSPACE
creates a ZIP archive which contains the license files
and changes the file name extension of the ZIP archive
to .piz to prevent them being filtered by your e-mail
server.
n The merge function of the dSPACE Installation
Manager can handle ZIP files and PIZ files without
unpacking them first.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 167
I

The dSPACE Master Setup does not accept merged Keys.dsp and
License.dsp files containing different versions of the same dSPACE
software product.
Method To merge license files
1 From Start Programs dSPACE Installation Manager, select dSPACE
Installation Manager.
The dSPACE Installation Manager opens.
2 Click the Licenses tab.
3 In the dSPACE Licensing window, click the Merge Installation Key
Files tab.
If the dSPACE Installation Manager is not available (= is
not installed) on your host PC, install the dSPACE
Installation Manager from
http://www.dspace.com/goto?IMUpdate.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
168

4 Click Add file and specify the path of the first ZIP file in the
Windows Open dialog.
5 Click Open.
The added ZIP file is displayed as shown below. If selected, you can
enter your own comments in the Annotations column, for example,
for easier identification of the files.
6 Repeat the last two steps for all the ZIP files you want to add and
display in the Installation Manager, and to merge.
The settings on the Merge Installation Key Files page are stored in
the dSPACE Installation Manager and are available after you close
and restart the Manager.
You also can select and add several files at once if they
are available on the same path.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 169
I

7 Select the checkboxes of the ZIP and/or PIZ files which you want to
merge.
The entries of the files contained in the selected ZIP archives are
displayed as follows:
n The entries of all the Keys.dsp files on the Installation Keys
page.
n The entries of all the License.dsp files on the Runtime Licenses
page.
8 Click Merge.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
170

The Save As dialog opens:
9 Specify the name and the path of the ZIP archive with the merged
Keys.dsp and License.dsp file, and click Save.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 171
I

10Only valid for dSPACE Release 7.1 and earlier: If you received a
License.dat file from dSPACE, you must copy it manually to the
folder where you saved the merged Keys.dsp and License.dsp files.
Result The Keys.dsp and License.dsp files of the selected ZIP files are
merged in one Keys.dsp file and one License.dsp file (available in a
new ZIP archive).
Next steps After you have merged the Keys.dsp and License.dsp files, you can
n Modify the installation on your PC or other PCs with the merged
Keys.dsp file. Refer to How to Modify the dSPACE Installation with
Merged Files on page 172.
n Start a new dSPACE installation on several PCs without having to
care about the number of the dongle that is connected to a
particular PC.
n Install two or more software products in different free folders in one
run. Refer to How to Install dSPACE Software on page 94.
Related topics
Do not change the file names of the merged files
(Keys.dsp and License.dsp) in the ZIP archive.
As of dSPACE Release 7.2, the License.dat file is
required only for installing the dSPACE License Server
but not for installing the dSPACE software on the
dSPACE License Clients.
The files added on the Keystore page are stored in the
dSPACE Installation Manager and are available after you
close and restart the Installation Manager.
In addition you can export the contents of the Keystore
page to a file (DSK file), for example, to use it on other
PCs.
Basics
Dongle License Mechanism on page 144
Floating Network License Mechanism on page 146
Managing Licenses in a Local License.dsp File (= Run-Time Licenses) on page 149
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
172

How to Modify the dSPACE Installation with Merged Files
Objective After you have merged the license files you can modify your
installation with the merged Keys.dsp file. You have to use dSPACE
Maintenance Setup for this.
Preconditions n You have administrator rights.
n The merged license files must be available as unpacked files. The
dSPACE setups cannot handle ZIP files and PIZ files.
Method To modify the dSPACE installation with merged files
1 From the Start Programs dSPACE <product> <x.y> menu, select
dSPACE Maintenance Setup (<product> <x.y>).
<product> <x.y> is a placeholder for the software and its version,
since your host PC can have multiple installations and multiple
entries in Start Programs. The term dSPACE Maintenance Setup is
used for all product-specific versions, for example, dSPACE
Maintenance Setup (TargetLink 3.3) .
2 Select the Modify Installation option, and click Next.
3 In the License Files Location dialog, specify the folder which
contains the merged license files, and click Next.
Now you can specify the dSPACE products that you want to install.
You can install all the products specified in the merged Keys.dsp
file.
4 Follow the instructions of the setup program.
5 When prompted, reboot your PC.
Result The dSPACE installation is modified according to your selections.
Related topics
Basics
Dongle License Mechanism on page 144
Managing Licenses in a Local License.dsp File (= Run-Time Licenses) on page 149
HowTos
How to Merge License Files on page 166
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 173
I

Specifics on Using Floating Network Licenses
Objective If you purchased floating network licenses, one PC in the network has
to be configured as the dSPACE License Server.
The PCs on which you want to run the dSPACE software (dSPACE
License Clients) need to be connected to the dSPACE License Server
networked via TCP/IP.
Where to go from here Information in this section
Setting Up the dSPACE License Server
If you purchased floating network licenses for dSPACE
software, you have to install and configure one of the
networked PCs as the dSPACE License Server.
174
Setting Up a Connection to the dSPACE License
Server
You have to adapt the settings of your dSPACE License Client
to the address of the dSPACE License Server to direct the client
to use the server.
182
License Behavior of Specific Products 188
Obtaining Permanent Floating Network Licenses
When you purchase floating network licenses and dSPACE
does not know the MAC address of the PC on which you want
to run the dSPACE License Server, you first receive licenses that
are valid for only 4 weeks. To obtain permanent licenses, you
need to provide dSPACE information about your system.
197
Migrating to Floating Network Licenses
You can migrate from dongle licenses to floating network
licenses.
201
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
174

Setting Up the dSPACE License Server
Objective If you purchased floating network licenses for dSPACE software, you
have to install and configure one of the networked PCs as the dSPACE
License Server.
Required knowledge Preparing the dSPACE License Server requires knowledge about the
network configuration, e.g., TCP/IP addresses, available TCP/IP ports
on the dSPACE License Server, and configuration of firewalls and
routers. Thus this is recommended for experienced network
administrators only.
Where to go from here Information in this section
FLEXnet Publisher Software
Objective To provide suitable license management for floating network licenses,
dSPACE uses FLEXnet Publisher a product of Flexera Software Inc.
This allows you to easily install and configure the dSPACE License
Server providing the available dSPACE licenses for the connected
dSPACE License Clients.
The dSPACE DVD provides the entire FLEXnet Publisher software
required by the dSPACE License Client(s) and the dSPACE License
Server.
FLEXnet Publisher Software
dSPACE uses FLEXnet Publisher software to provide suitable
license management for floating network licenses.
174
Requirements and License Server Settings
The dSPACE License Server must meet some requirements and
you must specify how it is started.
176
How to Install and Configure the dSPACE License
Server
178
How to Update the License.dat File on the dSPACE
License Server
You must modify floating network licenses to update the
License Server.
180
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 175
I

Installation of the FLEXnet
Publisher software
The FLEXnet Publisher software required by the dSPACE License
Client(s) is installed automatically during installation of the dSPACE
software.
The FLEXnet Publisher software required by the dSPACE License Server
has to be installed separately: for instructions, see How to Install and
Configure the dSPACE License Server on page 178.
Viewing and changing the
license status
The FLEXnet Publisher software LMTOOLS can be used to start, stop
and configure the dSPACE License Server, and to get system
information including host IDs, the server status and the number of
currently used licenses.
Related topics
For information and instructions on using FLEXnet
Publisher, refer to the FLEXnet License Administration
Guide. To access it, select
n On the dSPACE License Server: Start Programs
dSPACE License Server FLEXnet Licensing End User
Guide
n On a dSPACE License Client: Start Programs dSPACE
Installation Manager dSPACE Installation Manager:
On the Licenses tab, click Help (below the FlexNet
Utility button) to open the FlexNet License
Administration Guide.
n Or open the
Tools\LicenseServer\fnp_LicAdmin.pdf.pdf file on
the dSPACE DVD.
Basics
Floating Network License Mechanism on page 146
Requirements and License Server Settings on page 176
Setting Up the dSPACE License Server on page 174
HowTos
How to Install and Configure the dSPACE License Server on page 178
How to Set Up a Connection Between Client and Server on page 182
How to Update the License.dat File on the dSPACE License Server on page 180
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
176

Requirements and License Server Settings
Objective The dSPACE License Server must meet some requirements and you
must specify how it is started in the license server settings.
Requirements n The operating system of the dSPACE License Server must be one of
the following:
o Windows XP Professional (32-bit version) with Service Pack 3
o Windows Vista Business, Ultimate, or Enterprise (32-bit or 64-bit
version) with the latest Service Pack
o Windows 7 Professional, Ultimate, or Enterprise (32-bit or 64-bit
version)
o Windows Server 2003 (32-bit or 64-bit version)
o Windows Server 2008 (32-bit or 64-bit version)
o Windows Server 2008 RC (32-bit or 64-bit version)
n The version of the FLEXnet Publisher software installed on the
dSPACE License Server must be compatible with the version
installed on the dSPACE License Clients. As the FLEXnet Publisher
software on the dSPACE License Server is backward compatible,
you should always run the License Server that comes with the latest
dSPACE Release.
For Release 7.3, at least the dSPACE License Server 2.1 is required.
You can download the most recent version of the dSPACE License
Server from http://www.dspace.com/goto?FNLServer.
The dSPACE License Server does not support
non-Windows operating systems.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 177
I

dSPACE License Server
settings
You have to specify how the dSPACE License Server is started. For this
purpose, you can install the dSPACE License Server either as a service
or as an application.
dSPACE License Server installed as a service In this case, the
server can provide licenses for the connected dSPACE License Clients
even if the dSPACE license administrator is currently not logged on.
The server PC simply needs to be running for this purpose. The license
server installation configures the PC to automatically start the dSPACE
License Server upon reboot.
In this configuration each dSPACE License Client can deactivate or
delete all licenses available in the network using the FLEXnet Publisher
software LMTOOLS.
dSPACE License Server installed as an application In this case,
the server can provide licenses only if the dSPACE license administrator
is currently logged on, and if the dSPACE License Server application is
running. The license server installation configures the PC to
automatically start the dSPACE License Server application upon logon
of the license administrator.
When specifying the installation as an application, you can disable the
remote shutdown and the manual removal of license functions.
Disabling these functions prevents dSPACE License Clients being able
to deactivate or delete licenses available in the network.
Related topics
Basics
FLEXnet Publisher Software on page 174
Floating Network License Mechanism on page 146
Setting Up the dSPACE License Server on page 174
HowTos
How to Install and Configure the dSPACE License Server on page 178
How to Set Up a Connection Between Client and Server on page 182
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
178

How to Install and Configure the dSPACE License Server
Objective If you purchased floating network licenses for dSPACE software, you
have to install and configure one of the networked PCs as the dSPACE
License Server.
Precondition Unpacking received license files Before sending the license files
via e-mail, dSPACE creates a ZIP archive which contains the license files
and changes the file name extension of the ZIP archive to avoid
firewall problems. When you receive the license files, you have to
change the file name extension from .piz to .zip. Each ZIP archive
contains two or three files which have to be unpacked before installing
the software. Save all these files to one folder which you specify
during installation.
Method To install and configure the dSPACE License Server
1 Insert the dSPACE DVD into the DVD drive.
2 Choose the DVD drive, and run
Tools\LicenseServer\LicServer_Setup.exe
3 Follow the instructions given by the installation program.
4 When prompted, specify the path where the software for the
dSPACE License Server should be installed. Ensure that the specified
folder does not already contain an installation of other FLEXnet
Publisher software.
5 Specify the dSPACE License Server installation: it can be installed
either as a service or as an application. By default, the server is
installed as a service.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 179
I

If you install the dSPACE License Server as an application you can
disable/enable:
n The remote shutdown function: This is the ability of every
dSPACE License Client to deactivate all licenses available in the
network using FLEXnet Publishersoftware LMTOOLS.
n The manual removal of license function: This is the ability of
every dSPACE License Client to remove all licenses available in
the network using FLEXnet Publishersoftware LMTOOLS.
6 Specify the TCP/IP port to be used for communication with the
connected dSPACE License Clients.
7 When prompted, remove the dSPACE DVD.
8 Only if you install the dSPACE License Server as an application:
n Reboot your operating system.
n Log on as the same user with administrator rights directly after
reboot. This allows the system to complete the installation
correctly.
Related topics
If you leave the TCP/IP port edit field empty, FLEXnet
Publisher automatically determines a free port in the
range 27 000 27 009. In this case, this edit field
must also be left empty during installation of the
dSPACE License Clients.
If there is a firewall between the server PC and the
client PCs, make sure that the corresponding TCP/IP
port is not blocked.
Basics
FLEXnet Publisher Software on page 174
Floating Network License Mechanism on page 146
Migrating to Floating Network Licenses on page 201
Requirements and License Server Settings on page 176
HowTos
How to Install and Configure the dSPACE License Server on page 178
How to Set Up a Connection Between Client and Server on page 182
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
180

How to Update the License.dat File on the dSPACE License
Server
Objective Every time you receive a new License.dat file with floating network
licenses from dSPACE, you need to update the License.dat file on the
dSPACE License Server.
Use scenario You get a new License.dat file, for example:
n With new products
n With a changed number of licenses
n When the servers MAC address changed
n When you obtain permanent floating network licenses
Method To update the License.dat file
1 On the dSPACE License Server, open Windows Explorer and change
to the folder where you installed the dSPACE License Server
software.
2 Replace the old License.dat file by the new one provided by
dSPACE.
3 From the Start menu, select Programs dSPACE Tools dSPACE
License Administration FLEXlm LMTOOLS. The LMTOOLS dialog
opens.
NOTI CE
Do not update the License.dat files on the dSPACE
License Clients with the new License.dat file.
You should also update the License.dat file in the
license files folder.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 181
I

4 On the Service/License File page, choose the
n Configuration using License File option if the dSPACE License
Server was started as an application, and click Browse to specify
the location of the License.dat file.
Or choose the
n Configuration using Services option if the dSPACE License Server
was started as a service, and mark dSPACE License Server in the
list below the option.
5 On the Start/Stop/Reread page, click Reread License File.
Result The new License.dat file is reread and the corresponding licenses can
be used immediately.
Related topics
Basics
FLEXnet Publisher Software on page 174
Floating Network License Mechanism on page 146
Migrating to Floating Network Licenses on page 201
Obtaining Permanent Floating Network Licenses on page 197
Setting Up the dSPACE License Server on page 174
HowTos
How to Set Up a Connection Between Client and Server on page 182
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
182

Setting Up a Connection to the dSPACE License
Server
How to Set Up a Connection Between Client and Server
Objective You have to adapt the settings of your dSPACE License Client to the
address of the dSPACE License Server to direct the client to use the
server.
If not already done during initial installation of the dSPACE software,
you have to use the dSPACE Installation Manager for this.
Scenarios for setting up a
connection
The following cases require adaptation of the dSPACE License Client
settings to direct the clients to use the server:
n Subsequent installation of the dSPACE License Server
n Changes of the servers name or IP address
n Migrating from dongle lisenses to floating network licenses
Tasks for adaption of client
settings
The adaptation of the client settings involves the following tasks:
n Hosting the server when it was installed after installation of the
clients.
n Rehosting the server when it was moved to another PC or when the
name or IP address of the server PC changed.
n Redirecting the clients to use the new server when it was moved to
another PC or when the name or IP address of the server PC
changed.
Preconditions n The dSPACE License Server must be installed. Refer to Setting Up
the dSPACE License Server on page 174.
n Floating network licenses are available and the floating network
license support for the corresponding installation on the dSPACE
License Client is installed. For instructions, refer to How to Add
Floating Network License Support on Clients on page 202.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 183
I

Method To set up a connection between client and server
1 On a dSPACE License Client:
From Start Programs dSPACE Installation Manager, select dSPACE
Installation Manager.
The dSPACE Installation Manager opens.
2 Click the Licenses tab.
3 In the dSPACE Licensing window, click the Network Licenses
Configuration tab.
On the Client tab, all dSPACE installations available on your host PC
are listed as shown below.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
184

4 In the Select column, select the installation(s) which you should
connect to a specific dSPACE License Server.
The License server name and License server port edit fields appear:
5 In the License server name edit field, enter the host name or the IP
address of the dSPACE License Server.
You can select only installations that support floating
network licenses. Installations marked with a filled
blue checkbox do not support floating network
licenses, so you cannot select them. If you want to
change their license mechanism to floating network
licenses, refer to Migrating to Floating Network
Licenses on page 201.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 185
I

6 In the License server port edit field, enter the servers TCP/IP port
number.
The entries in the screenshots serve as an example.
7 Click Apply to Selected.
The entries in the screenshots serve as an example.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
186

Result The selected installation(s) on the client is (are) connected to the
specified server. The dSPACE License Client saves the information
about the dSPACE License Server to the local License.dat file (creates
a new file or updates the existing file).
After deselecting the previous installation(s), you can set up a further
connection between selected installations and another dSPACE License
Server.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 187
I

Related topics
Basics
Floating Network License Mechanism on page 146
Migrating to Floating Network Licenses on page 201
Obtaining Permanent Floating Network Licenses on page 197
Setting Up the dSPACE License Server on page 174
HowTos
How to Update the License.dat File on the dSPACE License Server on page 180
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
188

License Behavior of Specific Products
Where to go from here Information in this section
RTI and RTI Blocksets
Mechanism The license is checked and the license linger time is triggered when:
n RTI block dialogs and RTI Task Configuration dialogs are opened.
n The RTI or RTI-MP build process is started.
The license is released when the license linger time has elapsed.
For RTI block dialogs based on Simulink masks, no license check is
performed.
Default linger time 30 minutes
Reaction to no (free)
license available
n The protected block dialog does not open.
n The RTI or RTI-MP build process cannot be started.
n An error message appears.
RTI and RTI Blocksets 188
FlexRay Configuration Tool 189
ControlDesk 190
AutomationDesk 190
ConfigurationDesk - Configuration Version 191
ConfigurationDesk - Implementation Version 192
ModelDesk and ASM 193
MotionDesk 193
MotionDesk Blockset 194
MLIB/MTRACE 194
Microtec PowerPC C Compiler 195
TargetLink 195
Model Compare 195
ControlDesk Next Generation 196
SystemDesk 196
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 189
I

FlexRay Configuration Tool
Mechanism The license is checked and the license linger time is triggered
whenever:
n The FlexRay Configuration Tool is started.
n A FIBEX file is imported.
n A new project is created.
n A project is loaded.
n A project is saved.
n The About window is opened.
n The CRC configuration window is opened.
n The Controller window is opened.
n The Code Generator window is opened.
n The Hardware window is opened.
The license is released when the license linger time has elapsed.
Default linger time 30 minutes
Reaction to no (free)
license available
n An error message appears.
n The wanted action, for example, opening the Hardware window, is
not executed except for:
o Opening the About window. You can always open the About
window and no error message appears. The window contains
information on the license.
o Starting the FlexRay Configuration Tool. You can start the tool
but an error message appears.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
190

ControlDesk
Mechanism Licenses are checked and blocked when ControlDesk is started.
ControlDesk module licenses are blocked on first use.
All licenses without a linger time are released immediately when
ControlDesk is closed. If a module has linger time, the license is
released after the linger time has elapsed.
Default linger time n MP_EXTENSION, CD_TA_PYTHON: 30 minutes
n Other modules: no linger time
Reaction to no (free)
license available
n Licensed parts of ControlDesk (for example ControlDesk Standard -
Developer Version) are not available.
n An error message appears.
AutomationDesk
Mechanism Licenses are checked and blocked when AutomationDesk is started.
AutomationDesk module licenses are blocked on first use.
The ADD_STANDARD license is released immediately when
AutomationDesk is closed. If a module has linger time, the license is
released after the linger time has elapsed.
Default linger time n ADD_STANDARD, ADD_AUTOMATION: no linger time
n CD_TA_PYTHON, RTT_DEVELOPER, RTT_OPERATOR: 30 minutes
Reaction to no (free)
license available
n AutomationDesk cannot be used.
n An error message appears.
Python Libraries Most of the Python libraries (PYD files) are protected by license. The
CD_TA_PYTHON license is blocked when a PYD file is imported. The
license is released when the linger time has elapsed. In addition to
AutomationDesk, Python scripts running in ControlDesk or PythonWin
can also request PYD files.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 191
I

Real-Time Testing RTT sequences can only be transformed into byte code generator files
(BCG files) on the PC with an RTT_DEVELOPER license. The
RTT_DEVELOPER or RTT_OPERATOR license is necessary for
downloading BCG files to the processor board via the Create function
of the Real-Time Test Manager or the rttmanagerlib module.
ConfigurationDesk - Configuration Version
Mechanism The license is checked and blocked when ConfigurationDesk is started.
The license is released immediately when ConfigurationDesk is closed.
Default linger time No linger time
Reaction to no (free)
license available
ConfigurationDesks Loader Version opens.
BCG files generated by the Signal Editor of ControlDesk
Next Generation can be downloaded to the processor
board without any license.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
192

ConfigurationDesk - Implementation Version
Mechanism Implementation license The CFD_Implementation license is
checked and blocked when ConfigurationDesk is started.
The license is released immediately when ConfigurationDesk is closed.
Function block license The function block licenses are available in
different sizes for different numbers of instantiated function blocks in
your active ConfigurationDesk application. There are licenses that
allow you to implement 100, 200, 300, 1000 or an unlimited number
of function blocks.
One minimum function block license is blocked when a
ConfigurationDesk application is loaded that contains at least one
instantiated function block. The license is released immediately when
the project or ConfigurationDesk is closed again. The required
function block license is calculated at run time from the number of
instantiated function blocks in the signal chain of your active
ConfigurationDesk application.
As ConfigurationDesk also requires the smaller function block licenses,
it is blocked for other users connected to the dSPACE License Server.
This means that if the active application requires an unlimited function
block license, the function block licenses for 100, 200, 300 and 1000
function blocks are blocked as well. If function blocks are deleted from
the active application, so that the unlimited license is released and only
the license for 1000 function blocks is used, the unlimited license is
not necessarily available for other users. It can be used only if
additional licenses for 100, 200, 300 and 1000 function blocks are
available on the dSPACE License Server.
For more details on the ConfigurationDesk license concept, refer to
Required Licenses ( ConfigurationDesk Real-Time Implementation
Guide).
Default linger time No linger time
Reaction to no (free)
license available
n Most operations are blocked with an error message.
n However, you can save the ConfigurationDesk application.
ST M
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 193
I

ModelDesk and ASM
Mechanism Licenses are checked and blocked when:
n ModelDesk is started.
n An ASM model is opened.
The MOD_HWACCESS license is released immediately when
ModelDesk is closed. If a module has linger time, the license is released
after the linger time has elapsed.
Default linger time n MOD_HWACCESS: no linger time
n All ASM licenses: 30 minutes
Reaction to no (free)
license available
n ModelDesk: ModelDesk cannot be used.
n ASM: The protected model cannot be used.
n An error message appears.
MotionDesk
Mechanism The license is checked and blocked when MotionDesk is started.
The license is released immediately when MotionDesk is closed.
Default linger time No linger time
Reaction to no (free)
license available
n MotionDesk cannot be used.
n An error message appears.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
194

MotionDesk Blockset
Mechanism The license is checked and the license linger time is triggered when:
n MotionDesk block dialogs (MD_Communication, MD_Object) are
opened.
n A build process is executed for a model containing blocks from the
MotionDesk Blockset.
n When a simulation of the model is started in Simulink.
The license is released when the license linger time has elapsed.
Default linger time 30 minutes
Reaction to no (free)
license available
n The protected block dialog does not open.
n The build process cannot be started.
n The Simulink simulation cannot be started.
n An error message appears.
MLIB/MTRACE
Mechanism The licenses are checked and blocked:
n when MLIB is initialized with the command
mlib('SelectBoard', ...); (standard license)
n when the MP option is used with the command
mlib('Multiprocessing', ...); (standard license and MP
extension license)
All licenses are released immediately when a clear mex, clear
functions, clear mlib, or clear all command is invoked, or when
MATLAB is closed.
Default linger time No linger time
Reaction to no (free)
license available
n MLIB/MTRACE cannot be used.
n An error message appears.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 195
I

Microtec PowerPC C Compiler
Mechanism The license is checked and blocked when an executable of the
compiler is started. The license is released when the executable exits
and the linger time has elapsed.
The linger time guarantees the availability of the license throughout
the whole build process.
Default linger time 30 minutes
Reaction to no (free)
license available
n The executables of the compiler cannot be started.
n An error message appears.
TargetLink
Mechanism The timeout mechanism of licensed TargetLink products is as follows:
The licenses are checked and blocked when the corresponding action
is carried out. For example, the TL_BASE license is checked and
blocked when a TargetLink block dialog is opened and the
TOM/TGTSIM license is checked and blocked when code is generated
or loaded to an EVB.
The licenses are released after the linger time has elapsed.
Default linger time 30 minutes
Reaction to no (free)
license available
n The corresponding action cannot be carried out.
n An error message appears.
Model Compare
Mechanism The license is checked and blocked when Model Compare is started.
The license is released immediately when Model Compare is closed.
Default linger time No linger time
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
196

Reaction to no (free)
license available
n Model Compare cannot be used.
n An error message appears.
ControlDesk Next Generation
Mechanism Licenses are checked and blocked when ControlDesk Next Generation
is started. ControlDesk Next Generation module licenses are blocked
on first use.
All licenses are released immediately when ControlDesk Next
Generation is closed.
Default linger time No linger time
Reaction to no (free)
license available
ControlDesk Next Generation can only be used in the Loader Version.
SystemDesk
Mechanism The license is checked and blocked when SystemDesk is started.
The license is released immediately when SystemDesk is closed.
Default linger time No linger time
Reaction to no (free)
license available
n SystemDesk cannot be used.
n An error message appears.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 197
I

Obtaining Permanent Floating Network Licenses
How to Obtain Permanent Floating Network Licenses
Objective When you purchase floating network licenses and dSPACE does not
know the MAC address of the PC on which you want to run the
dSPACE License Server, you first receive licenses that are valid for only
4 weeks.
To obtain permanent licenses, you need to provide dSPACE (via e-mail
to fnl@dspace.de) with
n the dSPACE license ID
n the MAC address of the network adapter installed in the dSPACE
License Server.
You can use the dSPACE Installation Manager to get the required
information and to prepare an e-mail which you can complement and
then sent to dSPACE.
Getting the dSPACE license
ID
You can get the dSPACE license ID from the name of the ZIP archive
sent via e-mail (like xyz_R64.zip). Otherwise, if you do not have the ZIP
archive available, you can use the dSPACE Installation Manager to get
the dSPACE license ID as desribed below.
Getting the MAC address The MAC address matches the hardware ID of your dSPACE License
Server. Contact your system administrator to get ther required MAC
address of the host PC, on which the dSPACE License Server is
installed.
If the dSPACE License Server is installed on the same host PC as one of
the networked clients, you can get the MAC address from this host PC
via dSPACE Installation Manager.
Precondition You have an e-mail client installed on your dSPACE License Client.
Both the MAC address and the dSPACE license ID are
required by dSPACE to provide permanent floating
network licenses. Otherwise dSPACE cannot handle your
request.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
198

Method To obtain permanent floating network licenses
1 On a dSPACE License Client with dSPACE software installed:
From Start Programs dSPACE Installation Manager, select dSPACE
Installation Manager.
The dSPACE Installation Manager opens.
2 Click the Licenses tab.
3 In the dSPACE Licensing window, click the Configure Network
Licenses page.
On the Client tab, all dSPACE installations available on your host PC
are listed as shown below.
4 In the list, search for installations that support floating network
licenses and select their checkboxes.
Installations not marked with a filled blue checkbox do support
floating network licenses and therefore can be selected.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 199
I

When you select one or more installations, the dSPACE Installation
Manager gets the corresponding license ID(s) and adds it (them)
later to a prepared e-mail.
5 On the Network License Configuration tab, select the Server page.
It displays a list of MAC addresses for the available network
adapters on your host PC.
6 Depending on the installation location of the dSPACE License
Server:
n If the dSPACE License Server is running on another PC and not
on this host PC: Do not select a networt adapter.
n If the dSPACE License Server is running on this host PC: From the
list, select a network adapter that resides permanently in the
dSPACE License Server.
With the permanent licenses, the dSPACE License Server will run
only if this network adapter is present.
7 On the Server page, click the Prepare e-mail button.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
200

The installed e-mail program opens, and a prepared e-mail opens
with the dSPACE license ID and (if a network adapter is selected
beforehand) the MAC address.
8 If the dSPACE License Server is not running on this host PC: Add the
MAC address which you receive from your system administrator to
the e-mail.
9 Send the e-mail to fnl@dspace.de.
If you do not have an e-mail client installed on your
dSPACE License Client, the Prepare e-mail button is
disabled. You then have to save the MAC address to a
text file with the Save as file button, and send the file
to dSPACE via e-mail from another PC.
Alternatively you can copy only the MAC address with
the Copy to clipboard button. You can then paste it
into a text for use as e-mail or fax.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012 201
I

Next step For instructions on how to replace the License.dat file with a new one
(with the requested permanent licenses) and activate it, refer to How
to Update the License.dat File on the dSPACE License Server
on page 180.
Migrating to Floating Network Licenses
Working steps You can migrate from dongle licenses to floating network licenses by
executing the following steps:
1. The dSPACE License Server must be installed and set up first. For
instructions, refer to Setting Up the dSPACE License Server
on page 174.
2. You have to install floating network license support for the
corresponding installation on each dSPACE License Client. For
instructions, refer to How to Add Floating Network License Support
on Clients on page 202.
3. Only if you have not specified the settings for the dSPACE License
Server during Modify Installation (step 2 above): You have to set up
a connection between dSPACE License Client and dSPACE License
Server. For instructions, refer to How to Set Up a Connection
Between Client and Server on page 182.
Managing dSPACE Licenses
Software Installation and Management Guide May 2012
I
202

How to Add Floating Network License Support on Clients
Objective If you want to migrate to floating network licenses, the floating
network license support must be installed for the corresponding
installation on each dSPACE License Client. You have to use dSPACE
Maintenance Setup for this.
Preparing license
information
The new floating network licenses are supplied via e-mail in a ZIP
archive.
Unpacking received license files Before sending the license files
via e-mail, dSPACE creates a ZIP archive which contains the license files
and changes the file name extension of the ZIP archive to avoid
firewall problems. When you receive the license files, you have to
change the file name extension from .piz to .zip. Each ZIP archive
contains two or three files which have to be unpacked before installing
the software. Save all these files to one folder which you specify
during installation.
Precondition You have administrator rights.
Method To add floating network license support on clients
1 From the Start Programs dSPACE <product> <x.y> menu, select
dSPACE Maintenance Setup (<product> <x.y>) .
<product> <x.y> is a placeholder for the software and its version,
since your host PC can have multiple installations and multiple
entries in Start Programs. The term dSPACE Maintenance Setup is
used for all product-specific versions, for example, dSPACE
Maintenance Setup (TargetLink 3.3) .
2 Select Modify Installation.
3 Follow the instructions of the setup program.
4 When prompted, reboot your PC.
Next step Only if you have not specified the settings for the dSPACE License
Server during Modify Installation: Proceed with How to Set Up a
Connection Between Client and Server on page 182.
Related topics
Basics
Floating Network License Mechanism on page 146
I
203

Software Installation and Management Guide May 2012


Removing dSPACE Software
Removing/disconnecting
hardware
Before you remove the dSPACE software, disconnect all dSPACE USB
devices from your system.
Where to go from here Information in this section
Information in other sections
What Do You Want to Remove? 204
How to Remove dSPACE Software 208
How to Remove Components From a dSPACE
Installation
209
How to Remove Software Automatically in
Unattended Mode
211
How to Remove a dSPACE Installation via dSPACE
Installation Manager
235
Removing dSPACE Software
Software Installation and Management Guide May 2012
I
204

What Do You Want to Remove?
Objective dSPACE software offers various methods for removing the software
from your hard disk. The available methods depend on the software
and its version.
Effects on removing General effects Removing an installation means that the whole
<InstallationFolder> folder (as shown in the dSPACE Installation
Manager's Path field) is deleted, including all files and subfolders.
Files in folders outside the <InstallationFolder> folder are not
removed.
Additional effects of removing a SystemDesk installation If
you have installed more than one version of SystemDesk and remove
one of these versions, you cannot automate SystemDesk before
re-registering SystemDesk's automation feature. For information on
automating SystemDesk if you have removed another version of
SystemDesk, refer to Automating Different SystemDesk Versions
( SystemDesk Guide).
Overview for dSPACE
Release 7.2
The table below shows possible scenarios and the methods available
for a specific scenario. Note that the methods have the same effect.
Limitation when removing SystemDesk 2.1 or earlier: If
you remove SystemDesk 2.1 or earlier after installing
SystemDesk 3.0, Microsoft SQL Express 2005 cannot be
removed from your host PC. This limitation is caused by
the Microsoft setup program.
ST M
Each dSPACE software product has its own dSPACE
Maintenance Setup, for example the dSPACE RCP & HIL
Maintenance Setup. The term dSPACE Maintenance
Setup is used for all software product-specific versions of
the setup.
Removing dSPACE Software
Software Installation and Management Guide May 2012 205
I

What Do You Want to Remove? Via
Wndow's
Add or
Remove
Programs
1)
Via Start -
Programs -
<Product> -
dSPACE
Maintenance
Setup
Via dSPACE
Installation
Manager
Complete
installation of ...
RCP and HIL
software
Active
installation

Inactive
installation

ControlDesk Next Generation
AutomationDesk
TargetLink
Model Compare
SystemDesk
Specific modules/
products from ...
RCP and HIL
software
Active
installation

Inactive
installation

ControlDesk Next Generation
AutomationDesk
TargetLink
SystemDesk
Common software
tools
DCI Configuration Tool
dSPACE CAN API
dSPACE ECU Flash
Programming Tool

Real-Time Testing
dSPACE Offline Simulator
dSPACE Python Extensions
dSPACE Profiler
HIL API. NET
Stand-alone tools such as the dSPACE Installation
Manager
2)

1)
The Window's Add or Remove Programs function opens the product-specific dSPACE Maintenance Setup and uses its entire
functionality
2)
These stand-alone tools might not have their own setup programs, possibly because they are installed during the setup of a
software product such as TargetLink, but can be removed separately.
Removing dSPACE Software
Software Installation and Management Guide May 2012
I
206

Note the following important facts shown in the table above:
n As of dSPACE Release 7.2, you cannot remove dSPACE software via
the dSPACE Installation Manager
n As of dSPACE Release 7.2, you cannot remove an inactive RCP and
HIL software installation from your host PC. You first have to
activate the installation, then you can remove it via Microsoft
Wndows Add or Remove Programs function or via Start - Programs
- <Product> <x.y.> - dSPACE Maintenance Setup.
Overview for dSPACE
Release 7.1 and earlier
The table below shows possible scenarios and the methods available
for a specific scenario. Note that the methods have the same effect.
Each dSPACE software product has its own dSPACE
Maintenance Setup, for example the dSPACE RCP & HIL
Maintenance Setup. The term dSPACE Maintenance
Setup is used for all software product-specific versions of
the setup.
What Do You Want to Remove? Via
Wndow's
Add or
Remove
Programs
Function
Via Start -
Programs -
<Product x.y>
- dSPACE
Maintenance
Setup
Via dSPACE
Installation
Manager
Installation From Release 6.6 or Earlier
Complete
Installation of
...
RCP and HIL
Software,
TargetLink,
Model Compare,
or CalDesk in
separate folders
or in a common
folder
Active
installation

Inactive
installation

SystemDesk
Removing dSPACE Software
Software Installation and Management Guide May 2012 207
I

Installation From dSPACE Release 7.0 and dSPACE Release 7.1
Complete
installation of
...
RCP and HIL
software
Active
installation

Inactive
installation

TargetLink
Model Compare
ControlDesk Next Generation
SystemDesk
Specific
modules/
products from
...
RCP and HIL Active
installation

Inactive
installation

TargetLink
ControlDesk Next Generation
SystemDesk
Stand-alone tools such as the dSPACE Installation
Manager
1)

Common software tools (DCI Configuration Tool,
dSPACE CAN API, dSPACE ECU Flash Programming
Tool)
2)

1)
These stand-alone tools might not have their own setup programs, possibly because they are installed during the setup of a
software product such as TargetLink, but can be removed separately.
2)
To prevent removal of these common software tools, they are not listed in the Control Panel's Add or Remove Programs dialog.
It is not possible to remove these tools via a deinstallation program. This is planned for future dSPACE releases.
What Do You Want to Remove? Via
Wndow's
Add or
Remove
Programs
Function
Via Start -
Programs -
<Product x.y>
- dSPACE
Maintenance
Setup
Via dSPACE
Installation
Manager
Removing dSPACE Software
Software Installation and Management Guide May 2012
I
208

How to Remove dSPACE Software
Objective You can remove a complete installation of dSPACE software (RCP and
HIL software package, TargetLink, Model Compare, ControlDesk Next
Generation, SystemDesk, AutomationDesk). Various common stand-
alone tools from dSPACE (for example, the dSPACE Installation
Manager), which are installed during the setup of a software product,
can also be removed separately.
Preconditions n You have administrator rights.
n All dSPACE products and MATLAB are closed.
n Only valid for RCP and HIL software: The installation you want to
remove via dSPACE Maintenance Setup must be the active
installation.
Possible methods You can remove dSPACE software as follows:
n Via Window's Add/Remove Programs function
You can remove a complete installation of a software product (or
software package) and various dSPACE stand-alone tools which are
installed during the setup of dSPACE software. Refer to Method 1.
n Via dSPACE Maintenance Setup
You can remove a complete software product (or software package)
but not common stand-alone dSPACE software tools. Refer to
Method 2.
Method 1 To remove dSPACE software via Window's Add/Remove
Programs function
1 From the Start menu, select Control Panel and double-click Add or
Remove Programs.
2 In the Add or Remove Programs dialog, select the dSPACE
installation you want to remove and click Remove.
3 Follow the instructions given by the setup program.
4 When removal has finished, reboot your system when prompted.
Removing dSPACE Software
Software Installation and Management Guide May 2012 209
I

Method 2 To remove a dSPACE software via dSPACE Maintenance Setup
1 Select the dSPACE Maintenance Setup for the software product you
want to remove: From the Start Programs dSPACE <product>
<x.y> menu, select dSPACE Maintenance Setup (<product> <x.y>) .
<product> <x.y> is a placeholder for the software and its version,
since your host PC can have multiple installations and multiple
products in Start Programs. The term dSPACE Maintenance Setup
is used for all product-specific versions, for example, dSPACE
Maintenance Setup (TargetLink 3.3) .
2 Select Remove and click Next.
3 Follow the instructions given by the setup program.
4 When removal has finished, reboot your system when prompted.
Result You have removed the dSPACE software.
How to Remove Components From a dSPACE Installation
Objective You can remove components (separate software products or software
modules) from a dSPACE installation (RCP and HIL software package,
TargetLink, ControlDesk Next Generation, SystemDesk,
AutomationDesk).
Preconditions n You have administrator rights.
n The dSPACE products you want to modify or remove are closed.
n Only valid for RCP and HIL software: The installation you want to
remove via dSPACE Maintenance Setup must be the active
installation.
Possible methods You can remove components (products or modules) from a dSPACE
installation as follows:
n Via Window's Add/Remove Programs function. Refer to Method 1.
Only valid for RCP and HIL software: Via Start
Programs you can access only the active installation. If
you want to remove an inactive installation, use
method 1 (... via Window's Add or Remove Programs
function).
Removing dSPACE Software
Software Installation and Management Guide May 2012
I
210

n Via dSPACE Maintenance Setup. Refer to Method 2.
Method 1 To remove components from a dSPACE Installation via
Window's Add/Remove function
1 From the Start menu, select Control Panel and double-click Add or
Remove Programs.
2 In the Add or Remove Programs dialog, select the dSPACE
installation you want to modify and click Change.
The dSPACE Maintenance Setup opens.
3 Select Modify installation and click Next.
4 In the License Files Location dialog, specify the path of the license
files containing the licenses for the installed software
products/modules.
5 Follow the instructions given by the setup program.
Deselect the modules/products that you want to remove.
6 Click OK.
7 When removal has finished, reboot your system when prompted.
Method 2 To remove components from a dSPACE Installation via dSPACE
Maintenance Setup
1 Select the dSPACE Maintenance Setup for the software product you
want modify: From the Start Programs dSPACE <product> <x.y>
menu, select dSPACE Maintenance Setup <product> <x.y> .
<product> <x.y> is a placeholder for the software and its version,
since your host PC can have multiple installations and multiple
products in Start Programs. The term dSPACE Maintenance Setup
is used for all product-specific versions, for example, dSPACE
Maintenance Setup (TargetLink 3.3) .
2 Select Modify installation and click Next.
3 In the License Files Location dialog, specify the path of the license
files containing the licenses for the installed software
products/modules.
4 Follow the instructions given by the setup program.
Deselect the modules/products that you want to remove.
5 When removal has finished, reboot your system when prompted.
Result You have removed the selected products or modules from the current
installation.
Removing dSPACE Software
Software Installation and Management Guide May 2012 211
I

Related topics
How to Remove Software Automatically in Unattended
Mode
Objective If you want to remove dSPACE software (RCP and HIL software
package, AutomationDesk, ControlDesk Next Generation, TargetLink,
Model Compare, or SystemDesk) on several host PCs, you can use the
setup's unattended mode to make removing quicker and easier.
Accessing unattended
mode
You can access the unattended mode via command line tool, for
example, cmd.exe from Windows.
When you use long path and file names with spaces on the command
line, enclose the names in double quotation marks. This indicates that
spaces within the quotation marks are not command line delimiters.
Preconditions You need administrator rights to remove dSPACE software.
Basics
How to Activate a dSPACE Installation on page 126
You can open cmd.exe, for example, as follows: From the
Start menu, choose Run ..., enter cmd and click OK.
Commands and parameters (such as --nogui) must be
written as shown below. They are case-sensitive.
Removing dSPACE Software
Software Installation and Management Guide May 2012
I
212

Method To remove dSPACE software automatically via unattended
mode
1 Open a Command Prompt window and type the following
command:
<CommonProgramFiles(x86)>\dSPACE\Setup\{<MainProductCode>}\
Bootstrapper\Bootstrapper.exe --uninstall
{<MainProductCode>} --nogui
Example: "C:\Program Files (x86)\Common
Files\dSPACE\Setup\{D7AA2FFD-E7C6-4823-9FE6-
8A485CFF3110}\Bootstrapper\Bootstrapper.exe" --uninstall
{D7AA2FFD-E7C6-4823-9FE6-8A485CFF3110} --nogui
Result The dSPACE installation that has the specified main product code is
removed.
Next steps Remove the remainig files and folders manually, for example, via
Windows Explorer.
Use the optional --nogui parameter if you want to
remove the software without user interaction. If you
do not use this parameter, the dialogs of the setup
program appear. To continue the deinstallation, you
must confirm each dialog.
The installation folder may still contain files or folders.
These are not automatically removed when you uninstall
the software in unattended mode.
I
213

Software Installation and Management Guide May 2012


Contacting Support via the dSPACE
Installation Manager
Objective When contacting dSPACE Support, you need to provide the Support
team with some information about your dSPACE environment and the
problems you may have.
It is recommended to use the dSPACE Installation Manager to contact
dSPACE Support.
Information required by
dSPACE Support
n Automatic extraction of information: The diagnostics feature of the
dSPACE Installation Manager automatically extracts system
information, configuration files, and dSPACE product information,
and attaches them to your e-mail as a ZIP file.
n Manually collected information: The dSPACE Installation Manager
cannot extract all the required information automatically. You must
collect some information manually.
Where to go from here Information in this section
How to Prepare Information Required for dSPACE
Support
214
How to Send Information to dSPACE Support 218
Overview on Information to be Collected Manually 221
Collecting Information Concerning
ConfigurationDesk (Configuration Version) and
RapidPro Hardware
223
Collecting Information Concerning TargetLink 224
Collecting Information Concerning Model Compare 224
Contacting Support via the dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
214

How to Prepare Information Required for dSPACE Support
Objective To prepare automatically extracted information, your personal details,
and a problem description for sending to dSPACE Support.
Creating support
information file in
ControlDesk 3.x
When working with ControlDesk 3.x or RTI If you work with
ControlDesk 3.x or RTI (from the RCP and HIL software package) and
have hardware problems, create a support information file in
ControlDesk via Tools Create Support Information File beforehand.
This file is contained in the Config folder, which is read by the
diagnostics feature of the Installation Manager.
Method To prepare information required for dSPACE Support
1 From Start Programs dSPACE Installation Manager, select dSPACE
Installation Manager.
The Installation Manager opens.
2 Click the Diagnostics tab.
The Diagnostics page opens.
3 On the User Information tab, enter your personal details and give a
short description of the problem that occurred (as shown in the
example below).
Collecting Information Concerning the Hardware 225
Collecting Information Concerning RTI 226
In the operator mode of ControlDesk 3.x, you must use
the command line parameter -admin to be able to create
a support information file.
Start the dSPACE Installation Manager on the PC
where the software you have problems with is
installed.
Contacting Support via the dSPACE Installation Manager
Software Installation and Management Guide May 2012 215
I

4 Choose your country.
The software then determines the correct e-mail address of your
regional support team.
5 Click the Product Information tab to select or deselect the product
information you want to send to dSPACE Support.
Contacting Support via the dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
216

6 Click the Preview button if you want to display the collected
information that will be sent to dSPACE Support.
The collected information is displayed in the Preview information
window.
7 Click the Attachments tab, to add manually collected information
to the automatically generated ZIP file.
The Preview button is only available if it takes longer to
collect the information. If the information can be
collected quickly, it is immediately displayed in the
Preview information window.
Contacting Support via the dSPACE Installation Manager
Software Installation and Management Guide May 2012 217
I

8 Click the Add button and select the files which you want to include
in the ZIP file.
9 Choose one of the following possibilities:
n If you want to save the automatically extracted information and
the manually added information to a ZIP file (without creating an
e-mail), click the Save Information button.
n If you want to send the information to dSPACE Support via
automatically created e-mail, refer to How to Send Information
to dSPACE Support on page 218.
Result The prepared information is ready for sending.
If your e-mail client does not generate an e-mail
form automatically, save the information via Save
Information and send them manually.
Contacting Support via the dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
218

How to Send Information to dSPACE Support
Objective After preparing the information, you are now ready to send it via
e-mail.
E-mail client The diagnostics feature of the dSPACE Installation Manager works
with the default e-mail client that is registered on your system. For
further details on how to register your favorite e-mail client as the
default e-mail client on your system, refer to the respective
documentation.
Preconditions You have all the manually collected information ready. Refer to
Overview on Information to be Collected Manually on page 221.
Method To send the information to dSPACE Support
1 Click the User Information tab to check the country selection.
The diagnostic feature of the dSPACE Installation Manager
automatically chooses one of the following e-mail addresses
according to the country selected:
If your e-mail client does not generate an e-mail form
automatically, save the information via Save Information
and send it manually.
If the file size for the generated support information
might exceed the allowed limit of our e-mail client,
contact support@dspace.de for a link to upload the
information via FTP.
Country Company Contact
Australia Ceanet Pty Ltd. support@dspace.de
Canada dSPACE Inc. support@dspaceinc.com
China dSPACE Mechatronic Control
Technology (Shanghai) Co., Ltd.
support.china@dspace.de
Czech Republic HUMUSOFT s.r.o. support@dspace.de
France dSPACE SARL support@dspace.fr
Germany dSPACE GmbH support@dspace.de
India DynaFusion Technologies Pvt Ltd. support@dspace.de
Japan dSPACE Japan K.K. support@dspace.jp
Contacting Support via the dSPACE Installation Manager
Software Installation and Management Guide May 2012 219
I

2 On the Diagnostics page, click Prepare Email.
Korea MDS Technology Co. Ltd. support@dspace.de
Netherlands TSS Consultancy support@dspace.de
Poland Technika Obliczeniowa support@dspace.de
Slovakia HUMUSOFT s.r.o. support@dspace.de
Sweden Fengco Real Time Control AB support@dspace.de
Taiwan Scientific Formosa Incorporation support@dspace.de
United Kingdom dSPACE Ltd. support@dspace.ltd.uk
USA dSPACE Inc. support@dspaceinc.com
Other dSPACE GmbH support@dspace.de
Country Company Contact
Contacting Support via the dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
220

If the file size for the generated support information might exceed
the allowed limit of our e-mail client, the following message box
appears:
3 Click Continue to prepare the email if the size displayed is below
the allowed limit of your e-mail-client.
Your default e-mail client opens a pre-configured form for sending
an e-mail to dSPACE Support. Your personal details are displayed,
and the system and configuration information which you selected is
attached as a ZIP file.
If the file size is over the allowed limit, click Save
information to file and contact support@dspace.de for
a link to upload the information via FTP.
Contacting Support via the dSPACE Installation Manager
Software Installation and Management Guide May 2012 221
I

The illustration above serves as an example.
4 If you have more information files for dSPACE Support, for
example, pictures or screenshots, attach them to the e-mail.
5 When the e-mail is complete, click Send.
Result The e-mail is sent to the selected dSPACE Support address.
Overview on Information to be Collected Manually
Objective The dSPACE Installation Manager cannot extract all the information
automatically. You have to collect some general information, and
depending on the product, some additional information, manually.
Restrictions on file and
image formats
Do not send screenshots of text messages.
For images, use only JPEG, GIF, or ZIP formats. Do not send
uncompressed images of BMP or TIFF format.
Overview on required
information
The dSPACE Installation Manager cannot extract all the information
automatically. You have to collect some general information, and
depending on the product, some additional information, manually.
Zip all attachments, especially screenshots.
Product Required Information to be Collected Manually
All Give a detailed description of the problem and how it can be
reproduced:
o Can the problem be reproduced at will?
o Can the problem be reproduced after rebooting?
o Does the problem also occur when you use the supplied standard
demo files described in the documentation?
All Did you ever get the dSPACE system installed properly? If so, which
changes led to the problems:
o Changes in the PC configuration (hardware and/or software)
o Changes in the dSPACE system
o Changes in your Simulink model or C code
AutomationDesk
Contacting Support via the dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
222

ConfigurationDesk
(Configuration
Version)/RapidPro
Refer to Collecting Information Concerning ConfigurationDesk
(Configuration Version) and RapidPro Hardware on page 223.
ControlDesk
ControlDesk Next
Generation
Which calibration interface do you use?
o DCI-CAN1
o Calibration Hub
o CANCardX
o DCI-GSI1
o DCI-KLine1
ModelDesk
MotionDesk How do you work with MotionDesk?
o One PC with MotionDesk and ControlDesk
o One PC with ControlDesk and one PC with MotionDesk
o One PC with ControlDesk and one or more PC(s) with MotionDesk
(multi-PC solution) connected to a real-time system via MotionDesk
Multi-PC Interface Kit
o Single-processor system
o Multiprocessor system
TargetLink Refer to Collecting Information Concerning TargetLink on page 224.
Model Compare Refer to Collecting Information Concerning Model Compare
on page 224.
Hardware How is the hardware set up? For detailed questions, refer to Collecting
Information Concerning the Hardware on page 225.
RTI Refer to Collecting Information Concerning RTI on page 226.
Third-party
software
o Which MATLAB components, patches, and other software from
MathWorks

do you use? To find out which MATLAB component


versions you are using, type ver in the MATLAB Command Window
and copy the information to a text file.
o Which compiler versions do you use?
Product Required Information to be Collected Manually
Contacting Support via the dSPACE Installation Manager
Software Installation and Management Guide May 2012 223
I

Collecting Information Concerning ConfigurationDesk
(Configuration Version) and RapidPro Hardware
Information to be collected
manually
Provide the following information:
n The RapidPro serial number RP-Number xxxxxx, printed on the
housing of the RapidPro unit
n The backup of a ConfigurationDesk project. For instructions, refer
to How to Back up and Transfer a Project ( ConfigurationDesk
RapidPro Configuration Guide).
n The content of the imview analyzing tool (DOS tool).
To collect Method
the content of imview 1. Connect the RapidPro
system to the host PC and
the power supply.
2. In the Command Prompt
window
1)
, type imview >
im.txt.
3. Save the content as a ZIP
file.
The collected information is
available as ZIP file.
1)
You can open a Command Prompt window, for example, as follows: From the
Start menu, choose Run ..., enter cmd and click OK.
ST M
Contacting Support via the dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
224

Collecting Information Concerning TargetLink
Information to be collected
manually
n TargetLink version
n Version of MATLAB components
n Error description
n Model in which the problem occurs
Model settings The problem can also be related to the model settings. Send us the
model (including the dSPACE Data Dictionary) for analysis. A reduced
model in which the problem can be reproduced is sufficient.
Collecting Information Concerning Model Compare
Information to be collected
manually
n Model Compare version
n MATLAB version
n Error description
n Model in which the problem occurs or dump file
n User and comparison settings different to default settings
n Log file
The log file is located in
%LOCALAPPDATA%\dSPACE\ModelCompare\<x.y>\Log\Log.txt if you
use Windows 7 or %USERPROFILE%\Local Settings\Application
Data\dSPACE\ModelCompare\<x.y>\Log\Log.txt if you use
Windows XP where <x.y> is the current version of Model Compare.
If you send us a model that needs additional libraries
and/or workspace variables, for example, stimuli, provide
these additional files, too.
Send us the model for analysis. A reduced model in
which the problem can be reproduced is sufficient. If
you send us a model, it is recommended to provide
additional libraries and/or workspace variables if they
are needed to dump the models.
Contacting Support via the dSPACE Installation Manager
Software Installation and Management Guide May 2012 225
I

Collecting Information Concerning the Hardware
Objective Describe the setup of your system on the basis of the questions below.
Try to fill out as much information as possible to help us solve your
problem.
Type of dSPACE boards Which dSPACE boards are you using?
If all the boards originally belonged to the same system, it is sufficient
to tell us the number of the execution key. Otherwise, specify the
boards and list their serial numbers, too.
Location of the boards n Where are your dSPACE boards installed?
o Host PC
o Expansion box via Link Boards
o Expansion box via an Ethernet connection
o MicroAutoBox or MicroAutoBox II
n If the boards are installed in an expansion box via Link Boards: What
types of Link Boards are installed (host PC/expansion box)?
o DS813/DS814
o DS815/DS814
o DS817/DS814
o DS819/DS814
o DS821/DS814
o DS811/DS812
n If you use a MicroAutoBox: What type of Link Board is installed in
the host PC?
o DS813
o DS815
o DS817
o DS819
o DS821
n Do you use MicroAutoBox II?
In this case, host PC connection is established via Ethernet.
Status LEDs What is the status of the board?
The status LEDs can indicate the boards status as well as bad power
supply or damage to the board.
Contacting Support via the dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
226

The Link Boards status LEDs on the brackets indicate the status of the
connection.
Expansion box via
Ethernet
If you are using an expansion box via an Ethernet connection:
n Is there more than one Ethernet adapter in your host PC?
n How is your expansion box connected to your host PC?
o Peer-to-peer connection (network consists only of expansion box
and host PC)
o Expansion box is connected to a LAN.
Collecting Information Concerning RTI
Information to be collected
manually
n Version of MATLAB components
To find out which MATLAB component versions you are using, type
ver in the MATLAB Command Window and copy the information
to a text file.
n Build process output (for details, see below)
n Simulink model (for details, see below)
Build process output If the error occurs during the build process, you have to get the
information manually as follows:
n For single-processor systems, type
[errorFlag, errorMsg] = rti_build('<modelname without MDL-
Extension>','LogOutput','on') at the MATLAB Command
Window (for example, [errorFlag, errorMsg] =
rti_build('smd_1005_sl','LogOutput','on')).
A text file <modelname>_rti1<XXX>_log.txt is generated in the
working folder.
n For multiprocessor systems, type
[errorFlag, errorMsg] = rtimp_build('<modelname without MDL-
Extension>','LogOutput','on') at the MATLAB Command
Window (for example, [errorFlag, errorMsg] =
rtimp_build('pipt1_dual1005_sl','LogOutput,'on')).
A text file <modelname>_rtimp_log.txt is generated in the working
folder.
Contacting Support via the dSPACE Installation Manager
Software Installation and Management Guide May 2012 227
I

Simulink model If possible, also save the Simulink model itself.
If you send us a program for analysis (such as your model
or C code), try to reduce it to a minimum so that the
problem still occurs. Include all files belonging to the
application (including linked object files and S-function
files). It is best to zip the complete working folder and the
build folder <modelname_rti1<XXX> and send them
together with the model.
If you send us a model which contains Simulink blocks
that you implemented yourself, also provide the Simulink
libraries which are linked with these blocks.
Contacting Support via the dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
228

I
229

Software Installation and Management Guide May 2012


Handling Installations of Earlier
dSPACE Releases with dSPACE
Installation Manager
Objective dSPACE Installation Manager supports all dSPACE Releases. The latest
version always is compatibe to installations of older dSPACE Releases.
However, some features which are necessary to manage ealier dSPACE
Releases are not available for the latest dSPACE installations.
Where to go from here Information in this section
How to Restore the Default Settings for the Active
Installation
230
How to Connect TargetLink and Model Compare To
Other dSPACE Installations
232
Integrating MATLAB Into dSPACE Installations From
dSPACE Release 7.1 And Earlier
234
How to Remove a dSPACE Installation via dSPACE
Installation Manager
235
Handling Installations of Earlier dSPACE Releases with dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
230

How to Restore the Default Settings for the Active
Installation
Valid for This feature of the dSPACE Installation Manager is available:
n For all software installations of dSPACE Release 6.6 and earlier
n For RCP and HIL software installations of dSPACE Release 7.1 and
earlier
Basics on restoring default
settings
The dSPACE Installation Manager lets you restore the factory default
settings of the active installation. This allows you to undo
unintentional changes in your dSPACE applications, such as changes to
the toolbar settings in ControlDesk 3.x.
Method To restore the default settings for the active installation
1 Quit all dSPACE programs and MATLAB (if used).
2 From Start Programs dSPACE Installation Manager, select dSPACE
Installation Manager.
The Installation Manager opens.
3 In the dSPACE Installations window, select the installation you want
to restore.
Handling Installations of Earlier dSPACE Releases with dSPACE Installation Manager
Software Installation and Management Guide May 2012 231
I

4 Click Reset to Defaults.
The dSPACE Installation Manager restores the factory default
settings. This may take some time.
5 Reboot your system.
Related topics
Basics
Features of the dSPACE Installation Manager on page 23
How to Activate a dSPACE Installation on page 126
HowTos
How to Deactivate the Active Installation on page 130
How to Remove a dSPACE Installation via dSPACE Installation Manager on page 235
How to View Installation Details on page 123
Handling Installations of Earlier dSPACE Releases with dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
232

How to Connect TargetLink and Model Compare To Other
dSPACE Installations
Valid for This feature of the dSPACE Installation Manager is available:
n For TargetLink 3.2 installations (on dSPACE Release 7.0 and dSPACE
Release 7.1)
n For Model Compare 2.1 installations (on dSPACE Release 7.0 and
dSPACE Release 7.1)
Installation set You have to connect a TargetLink or a Model Compare installation to
other compatible installations to build an installation set. You can then
work with several software products from different releases and
installations in parallel on your host PC. All the products in an
installation set are initialized for full, unrestricted interaction between
products.
Compatibility The following table shows the software products with their versions
that are compatible. Installations from compatible products and
versions can be combined to an installation set.
Method To connect TargetLink and Model Compare to other dSPACE
installations
1 Exit all dSPACE programs and MATLAB (if used).
2 From Start Programs dSPACE Installation Manager, select dSPACE
Installation Manager.
The Installation Manager opens.
Software
Product
Can be Connected To ...
RCP and
HIL
Software
1)
TargetLink ControlDesk
2)
CalDesk Model Compare SystemDesk
<
6.1
as of
6.1
<
2.3.1
as of
2.3.1
4.0 4.1 <
2.0
as of
2.0
< 2.0.2 2.0.2 2.1 as of 1.0
TargetLink
3.2

n.a.

Model
Compare
2.1

n.a.
1)
"RCP and HIL software" is a generic term for a software package containing several dSPACE software products, for example
RTI, ControlDesk, AutomationDesk, ConfigurationDesk, MotionDesk, ModelDesk.
2)
ControlDesk Next Generation (= ControlDesk 4.0 and later) is the successor to CalDesk and ControlDesk. However,
ControlDesk versions lower than ControlDesk 4.0 are still included in the RCP and HIL software package.
Handling Installations of Earlier dSPACE Releases with dSPACE Installation Manager
Software Installation and Management Guide May 2012 233
I

3 In the dSPACE Installations window, select the installation you want
to connect to another one.
4 On the Connect to dSPACE Release page, select the Connected
checkbox of each dSPACE installation, to which you want to
connect the selected installation.
Result The selected installations are initialized and combined in an installation
set.
Handling Installations of Earlier dSPACE Releases with dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
234

Integrating MATLAB Into dSPACE Installations From dSPACE
Release 7.1 And Earlier
Objective If you want to work with dSPACE software which requires MATLAB, a
MATLAB installation must be integrated into the dSPACE software.
Methods for integration For dSPACE Releases earlier than dSPACE Release 6.6, MATLAB
integration must be performed via dSPACE Maintenance Setup. Since
dSPACE Release 7.0, MATLAB integration is being improved step-by-
step for all dSPACE products which require MATLAB. The improved
versions let you integrate dSPACE software in MATLAB installations
simply by selecting checkboxes in the dSPACE Installation Manager.
The table below shows which tool is required for which dSPACE
product and release version.
Instructions for integrating
MATLAB
Using dSPACE Maintenance Setup If you have to integrate
MATLAB via the product-specific dSPACE Maintenance Setup, use the
Modify option. For details and instructions, refer to the Software
Installation and Management Guide for the dSPACE Release
concerned.
Tool for MATLAB
Integration
RCP and HIL
software
TargetLink Model
Compare
SystemDesk
<

7
.
1
7
.
1
<

3
.
2
3
.
2

1
)
<

2
.
1

2
.
1

<
1
)
<

3
.
0
3
.
0

1
)
dSPACE Maintenance
Setup
2)

dSPACE Installation
Manager

1)
Available on dSPACE Release 7.0 and dSPACE Release 7.1
2)
The dSPACE Maintenance Setup has product-specific versions, for example, the dSPACE RCP&HIL Maintenance Setup.
MATLAB integration for RCP and HIL software
installations (from dSPACE Release 7.1 and earlier) and
installations of other products (from dSPACE Release 6.6
or earlier) is also displayed in the dSPACE Installation
Manager, but you can change this integration only via the
product-specific dSPACE Maintenance Setup.
Handling Installations of Earlier dSPACE Releases with dSPACE Installation Manager
Software Installation and Management Guide May 2012 235
I

Using dSPACE Installation Manager For details and instructions,
refer to How to Change the MATLAB Integration on page 139.
Related topics
How to Remove a dSPACE Installation via dSPACE
Installation Manager
Objective If you want to remove a dSPACE installation of earlier dSPACE Releases
you can use the dSPACE Installation Manager to remove the software.
Valid for This feature of the dSPACE Installation Manager is available:
n For all software installations of dSPACE Release 6.6 and earlier
(except for SystemDesk)
n For RCP and HIL software installations of dSPACE Release 7.1 and
earlier
Other possible methods To remove the dSPACE software products from dSPACE Release 6.6 or
earlier, you can use:
n Windows Add/Remove Programs function.
n The dSPACE Maintenance Setup
For instructions, refer to How to Remove dSPACE Software
on page 208.
Basics
How to Change the MATLAB Integration on page 139
As of dSPACE Release 7.2, you cannot remove dSPACE
software via the dSPACE Installation Manager
If you want to remove an inactive installation, you can
only use the dSPACE Installation Manager to remove
the software.
Handling Installations of Earlier dSPACE Releases with dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
236

Removing a combined
dSPACE Installation
A combined installation is an installation of several software products
(for example, RCP and HIL software and TargetLink) in a common
folder.
With the dSPACE Installation Manager, you can remove a combined
installation regardless of the installation order. You can use the
dSPACE Installation Manager for active and inactive installations.
Active installations are deactivated automatically during removal.
Preconditions n You have administrator rights.
n All dSPACE tools and MATLAB are closed.
Removing a combined installation with the dSPACE
Installation Manager means that the whole
%DSPACE_ROOT% folder (as shown in the dSPACE
Installation Manager's Path field) will be deleted,
including all files and subfolders.
Before deleting an installation, back up the user-defined
data you want to keep, for example:
n Own projects, experiments, or model files in the work
folder
n An extended custom instrument library for
ControlDesk in the folders below ControlDesk\Users
n An extended custom library for AutomationDesk in the
folder AutomationDesk\Users\AllUsers
Files in folders outside the %DSPACE_ROOT% folder, such as
the PowerPC C Compiler in %PPC_ROOT%, will not be
removed.
To remove a combined installation and install new
dSPACE software, it is recommended to first install the
new software in a new path. The old installation becomes
inactive after reboot and the folders outside the
%DSPACE_ROOT% folder, which remained unchanged, can
be used by the new installation.
Handling Installations of Earlier dSPACE Releases with dSPACE Installation Manager
Software Installation and Management Guide May 2012 237
I

Method To remove a dSPACE installation via dSPACE Installation
Manager
1 From Start Programs dSPACE Installation Manager, select dSPACE
Installation Manager.
The Installation Manager opens.
2 In the dSPACE Installations window, select the installation you want
to remove.
3 Click Remove.
If you remove the active installation, the dSPACE Installation
Manager deactivates the installation and deletes the installation's
root folder and all corresponding files and subfolders. A reboot is
required after this.
If you remove an inactive installation, the dSPACE Installation
Manager deletes the installation's root folder and all corresponding
files and subfolders.
Handling Installations of Earlier dSPACE Releases with dSPACE Installation Manager
Software Installation and Management Guide May 2012
I
238

Related topics
Basics
Features of the dSPACE Installation Manager on page 23
How to Activate a dSPACE Installation on page 126
HowTos
How to Deactivate the Active Installation on page 130
How to Restore the Default Settings for the Active Installation on page 230
I
239

Software Installation and Management Guide May 2012


Troubleshooting
Objective If any problem related to the installation of your system comes up,
refer to the information given in this section.
Getting further support If the information in this section does not help you solve the problem,
you should check the support section of our Web site
http://www.dspace.com/goto?support. This might help you solve the
problem on your own. The FAQ section especially might be of help.
If you cannot solve the problem, contact dSPACE Support.
There are different ways to contact dSPACE Support:
n Visit our Web site at http://www.dspace.com/goto?support
n Send an e-mail or phone:
o General Technical Support:
support@dspace.de
+49 5251 1638-941
o TargetLink Support:
support.tl@dspace.de
+49 5251 1638-700
n Use the dSPACE Installation Manager:
o On your dSPACE DVD at \Tools\InstallationManager
o Via Start Programs dSPACE Installation Manager (after
installation of the dSPACE software)
o At http://www.dspace.com/goto?im
You can always find the latest version of the dSPACE Installation
Manager here.
Troubleshooting
Software Installation and Management Guide May 2012
I
240

dSPACE recommends that you use the dSPACE Installation Manager
to contact dSPACE Support.
Checking known problem
reports and limitations
To stay up-to-date with information on possible problems, you should
periodically check the known problem reports sections on our Web
site.
You can find the known problem reports at
http://www.dspace.com/goto?ProblemReports.
Where to go from here Information in this section
Installation Problems 241
License Problems 248
Troubleshooting
Software Installation and Management Guide May 2012 241
I

Installation Problems
Objective If you have problems with your dSPACE software and suspect they are
related to the installation, check the following topics.
Where to go from here Information in this section
Non-Administrator Logon After Installation
Applies to Applies only to RCP and HIL software and ControlDesk Next
Generation
Problem If you did not log on with administrator rights directly after installation,
you might be unable to start the dSPACE software or receive error
messages regarding missing DLLs, for example. The system could not
finish the setup properly and you have to repair the installation.
Preconditions You have administrator rights.
Non-Administrator Logon After Installation 241
Installation With a Different User Account 242
Installation on NTFS Partition 243
Only RCP and HIL Software: How to Install a dSPACE
Release Older than the Active Installation
244
Problems When Installing TargetLink 245
Problem with Incompatibility Between RTT 1.9 and
1.6
246
How to Repair a dSPACE Installation
Problems that are related to the software installation can be
solved by repairing the installation with dSPACE Maintenance
Setup.
247
Troubleshooting
Software Installation and Management Guide May 2012
I
242

Method To repair an installation with the dSPACE Maintenance Setup
1 From the Start Programs dSPACE <product> <x.y> menu, select
dSPACE Maintenance Setup (<product> <x.y>) .
<product> <x.y> is a placeholder for the software and its version,
since your host PC can have multiple installations and multiple
products in Start Programs. The term dSPACE Maintenance Setup
is used for all product-specific versions, for example, dSPACE
Maintenance Setup (TargetLink 3.3) .
2 Select Repair Installation.
3 Follow the instructions of the setup program.
4 When prompted, reboot your system.
Result The dSPACE software is installed properly.
Related topics
Installation With a Different User Account
Applies to Applies only to RCP and HIL software and ControlDesk Next
Generation
Problem If you encounter problems, for example, missing instruments in
ControlDesk, check the account that the new dSPACE software was
installed with. It has to be the same as the users and that of the
formerly installed dSPACE software. Otherwise the registry settings are
invalid for the new installation and you have to repair it.
Method To set the right user account
1 Log on as the user concerned.
2 Ensure that all dSPACE software and MATLAB is closed.
3 Start regedit.exe of your operating system.
Windows Registry Editor opens.
4 Delete HKEY_CURRENT_USER\Software\dSPACE.
5 Close the Registry Editor.
Basics
Installing dSPACE Software on page 91
Troubleshooting
Software Installation and Management Guide May 2012 243
I

Result The new installation is set to the right user account.
Related topics
Installation on NTFS Partition
Problem If you are a non-administrator and cannot access the installation,
check if it is installed on the same partition as the operating system
and if this partition is formatted as an NTFS partition. You have to get
modify permissions to be able to work with the installation.
Log file access for
non-administrators in an
RCP and HIL installation
Since dSPACE Release 5.2, data is written to the log file with
administrator settings when the installation is rebooted. A non-
administrator does not have modify permission and cannot access the
log file. A new log file is saved to <Systempartition>:\Documents and
Settings\<Username>\Local Settings\Temp\dspace.log instead of
<InstallationFolder>\Config\dSPACE.log.
Preconditions You have administrator rights.
Method To get modify permissions for a non-administrator
1 Log on with administrator rights and start Windows Explorer.
2 Select the installation folder and open Properties via the context
menu.
Basics
Features of the dSPACE Installation Manager on page 23
Installation on NTFS Partition on page 243
Non-Administrator Logon After Installation on page 241
If RCP and HIL software and also ControlDesk Next
Generation are installed on your host PC, the log file
handling is the same as described above. However, if
ControlDesk Next Generation is installed but there is no
RCP and HIL software installation on your host PC, the log
file is initially saved to a folder where non-administrators
have modify permissions.
Use context-sensitive help on the Security page if you are
not sure about the security settings.
Troubleshooting
Software Installation and Management Guide May 2012
I
244

3 On the Security page, add the user or group concerned with at least
modify permissions.
4 Click Advanced.
5 On the Advanced Security Settings page, select:
n Inherit from parent the permission entries that apply to child
objects. Include these ... (Windows XP) or
n Include inheritable permissions from this object's parent
(Windows Vista/Windows 7).
6 Click OK in both dialogs.
Result You have at least modify permissions to work with the installation.
Related topics
Only RCP and HIL Software: How to Install a dSPACE Release
Older than the Active Installation
Problem If you install a dSPACE Release older than the active installation, the
new installation might not function correctly. Use the method
described below for error-free installation.
Method To install a dSPACE Release older than the active installation
1 Start the dSPACE Installation Manager 3.3 or later.
You can download the most recent version from
http://www.dspace.com/goto?IM.
2 Select the active installation and click Deactivate.
3 Reboot your PC.
4 Install the older dSPACE Release.
5 Reboot your PC.
6 Log on as the same user with administrator rights directly after
reboot. This allows the system to complete the installation correctly.
Basics
Installation With a Different User Account on page 242
Non-Administrator Logon After Installation on page 241
This procedure may take some time.
Troubleshooting
Software Installation and Management Guide May 2012 245
I

If Windows' autologon process is enabled on your PC, press the
Shift key directly after restarting your PC, and hold the key until
the log-on dialog opens. This allows you to log on as the same user
with administrator rights.
Result The older dSPACE Release is installed and is the active installation.
Related topics
Problems When Installing TargetLink
Objective The TargetLink environment relies on the proper installation of several
hardware and software products. If you encounter any problems
during the installation, follow the instructions below to correct the
problem.
Method 1 To check the functionality of the MATLAB MEX command
1 Run MATLAB and compile one of Simulinks sample S-functions by
typing the following commands in the MATLAB Command
Window:
cd <MATLAB_ROOT>\simulink\src
dir limintc.dll
If limintc.dll is listed and you want to keep it, rename the file
with !ren limintc.dll *.sav Otherwise delete the file with !del
limintc.dll.
2 Type mex('limintc.c') to create a new limintc.dll file.
3 Type dir limintc.dll to check if the file has been build:
If limintc.dll is listed, the MATLAB MEX command works
correctly. Refer to the MATLAB manual Application Program
Interface Reference if you encounter any problems.
The last step is mandatory because some DLLs installed
by dSPACE are registered only after reboot. This
registration and thus the entire installation will fail
if you first log on without administrator rights.
This is the standard behavior for most software
installations that add or update system DLLs.
HowTos
How to Deactivate the Active Installation on page 130
Troubleshooting
Software Installation and Management Guide May 2012
I
246

4 To restore the previous saved version, delete the newly created one
with !del limintc.dll and rename the previous one with !ren
limintc.sav *.dll.
Method 2 To check the installation of TargetLink
1 Enter ver at the MATLAB command prompt to display the version
numbers of the installed toolboxes.
2 If TargetLink is not listed, make sure that the MATLAB intallation
used, is linked to a TargetLink installation. For instructions on
linking, refer to How to Change the MATLAB Integration
on page 139.
Problem with Incompatibility Between RTT 1.9 and 1.6
When you install ControlDesk 4.2.1 with the Signal Editor Module or
Bus Navigator Module, the following problem occurs with real-time
applications that were built with dSPACE Release 6.6 or earlier and
with real-time testing support (RTT 1.6 or earlier) enabled.
Problem description During installation of ControlDesk Next
Generation (ControlDesk 4.2.1) with the Signal Editor Module or Bus
Navigator Module, Real-Time Testing (RTT) 1.9 is installed. This also
applies to the installation of AutomationDesk from dSPACE Release
7.3).
RTT 1.9 is then also used by AutomationDesk from dSPACE Release
6.6 or earlier, but it is not compatible with RTT 1.6 or earlier. Thus, if a
real-time application was built with dSPACE Release 6.6 or earlier, and
RTT support was enabled during the build, it is not possible to use
AutomationDesk and RTT.
Solution Rebuild the real-time application with dSPACE Release 7.1
or later.
Result You can use AutomationDesk from dSPACE Release 7.3 or
earlier.
Troubleshooting
Software Installation and Management Guide May 2012 247
I

How to Repair a dSPACE Installation
Objective If you unintentionally modified your installation or the software
outputs syntax errors or error messages concerning missing files, you
can repair the installation with dSPACE Maintenance Setup.
The term dSPACE Maintenance Setup is used for all software product-
specific versions.
Preconditions n You have administrator rights.
n Only valid for RCP and HIL software: The dSPACE installation which
you want to repair is the active installation. For details, refer to How
to Activate a dSPACE Installation on page 126.
Method To repair a dSPACE installation
1 From the Start Programs dSPACE <product> <x.y> menu, select
dSPACE Maintenance Setup (<product> <x.y>) .
<product> <x.y> is a placeholder for the software and its version,
since your host PC can have multiple installations and multiple
products in Start Programs. The term dSPACE Maintenance Setup
is used for all product-specific versions, for example, dSPACE
Maintenance Setup (TargetLink 3.3).
2 Select Repair Installation.
3 Follow the instructions of the setup program.
4 When prompted, reboot your system.
Result dSPACE Maintenance Setup automatically repairs the installation
according to your entries.
Related topics
Basics
Installation Problems on page 241
Integrating MATLAB into dSPACE Software on page 133
HowTos
How to Install Components of Software Products Subsequently on page 99
Troubleshooting
Software Installation and Management Guide May 2012
I
248

License Problems
Objective The dSPACE licenses are checked on various occasions. If the software
does not find a valid license, it will stop and issue an error message.
Where to go from here Information in this section
Information in other sections
Basics on Error Messages
RTI error messages
Example for an RTI error message RTI License Check
Checking RTI product license failed with message:
Product license for RTI not found.
Please check your license file for a valid product entry.
Refer to the dSPACE documentation for troubleshooting.
TargetLink error messages In the error messages, <product> can be any of the following products:
n TargetLink Base Suite
n TargetLink Target Optimization Module <module name>
n TargetLink Target Simulation Module
Basics on Error Messages 248
Dongle License Problems 249
Debugging Dongle Problems 251
Dongle and Floating Network License Problems 253
Floating Network License Problems 256
How to Check dSPACE Floating Network Licenses 261
Installation Problems 241
When RTI and RTI Blocksets are used the error messages
mentioned in this section do not appear in the described
form. In addition the RTI error messages provide more
text with instructions for the user. An example is given
below.
Troubleshooting
Software Installation and Management Guide May 2012 249
I

n TargetLink Module for Operating Systems
n TargetLink AUTOSAR Module
n Data Dictionary Manager
Error messages The error messages may occur due to:
n Dongle license problems. Refer to Dongle License Problems
on page 249.
n Floating network license problems. Refer to Floating Network
License Problems on page 256.
n Or both. Refer to Dongle and Floating Network License Problems
on page 253.
The FLEXnet License Administration Guide also provides a
troubleshooting section. The guide is available:
n On your dSPACE DVD in the
Tools\LicenseServer\fnp_LicAdmin.pdf file
n On the dSPACE License Server (after installation of the dSPACE
software)
Dongle License Problems
Objective For general information on handling the dongle and activating the
license, refer to Dongle License Mechanism on page 144.
Error message Execution key not found!
or
Execution key invalid!
dSPACE software cannot access the dongle because it is not plugged
in, or the dongle software is not properly installed. Try the following:
1. If the dongle is missing, plug it in. If the problem persists, carry out
the following steps.
2. Select Start Control Panel and check whether there is a
WIBU-KEY icon. If this icon does not exist, you have to reinstall the
dongle software in the \Tools\WibuKey folder on your dSPACE
DVD.
3. If the WIBU-KEY icon exists, double-click it to open the WIBU-KEY
Control Panel. Check whether the dongle software can recognize
the key. Refer to Testing the dongle on page 251.
Troubleshooting
Software Installation and Management Guide May 2012
I
250

4. If not, contact dSPACE Support at support@dspace.de.
Error message WIBU license handler not installed!
The WIBU license handler is not installed or the files have been moved
or damaged.
n Start the WIBU-KEY software setup located on your dSPACE DVD in
the \Tools\WibuKey folder.
Error message Found new hardware WIBU-Box/U
If you connected the dongle to the USB port of your host PC before
installing the dSPACE software, Windows cannot identify the key
because its driver is not installed. Windows opens the Found New
Hardware Wizard to let you search for the driver. Since the driver is not
installed, the execution key is blocked in the Device Manager.
Use the following troubleshooting to reset the Plug & Play settings of
the dongle and install its driver:
1. Remove the dongle from the USB port.
2. In the Found New Hardware Wizard, click Cancel.
3. From Start Control Panel System, select the Hardware page and
click Device Manager.
4. The Device Manager opens.
5. Under the Universal Bus Controllers node, select the WIBU-Box/U
entry highlighted in yellow and press the Del key.
6. Install the dSPACE software.
7. Reboot your system.
The Plug & Play settings for the USB dongle are reset and the dongle
driver is installed with the dSPACE software.
The next time you connect the USB dongle, the Plug & Play mechanism
will recognize the hardware and the dongle license will be enabled.
Error message WIBU-KEY driver cannot be found If the driver for the WIBU-
KEY cannot be found automatically, try the following:
1. Select Start Control Panel.
2. In the Control Panel dialog, double-click the WIBU-KEY icon.
The WIBU-KEY Software Protection: Test and Settings dialog opens.
3. On the Install page, click Plug & Play.
4. Remove the dongle from the USB port.
5. Reboot your system.
Troubleshooting
Software Installation and Management Guide May 2012 251
I

6. Plug in the dongle.
The dongle software finds the driver automatically.
Error message USB dongle cannot be read
n Visit http://www.dspace.com/goto?wibudrv and follow the
instructions for updating the dongle driver. Refer to Updating the
dongle driver on page 252.
Related topics
Debugging Dongle Problems
Objective For general information on handling the dongle and activating the
license, refer to Dongle License Mechanism on page 144.
Use the following troubleshooting if you have problems with your
dongle.
Checking the dongle
installation
1. Check if the dongle is installed at the LPT1: or USB port.
2. Check if the dongle number matches the license installed on your
host PC.
3. If using a dongle for a parallel port, check if the LPT1: port is
enabled in the BIOS setup of the host PC.
4. Proceed with the following paragraph.
Testing the dongle 1. Select Start Control Panel.
References
Dongle and Floating Network License Problems on page 253
Floating Network License Problems on page 256
Troubleshooting
Software Installation and Management Guide May 2012
I
252

2. In the Control Panel dialog, double-click the WIBU-KEY icon.
The WIBU-KEY diagnostics tool opens.
If the dongle software recognizes the dongle, the table on the right
side of the Contents page shows the code 470 and your dongle
number.
3. Right-click the dialog's titlebar to open its context menu and select
Advanced Mode.
4. If the dongle software recognizes the dongle, select the Test page,
click Start, and let the test run until the counter displays 200.
5. If the dongle software does not recognize the dongle or any errors
are displayed, proceed with the following paragraph.
Specifying the dongle
settings
1. On the Setup page, specify the settings of the USB or LPT1: port:
o In the Port setting frame, select Enabled (port accessed by WIBU-
KEY driver).
o If using the LPT1: port:
o In the Location frame, select System default if Port address
displays 0378.
o If Port address is empty, deselectSystem default and enter
0378 manually.
2. If this does not help, proceed with the following paragraph.
Updating the dongle driver When you use an older dSPACE Release, it can be necessary to update
the dongle driver:
1. Visit http://www.dspace.com/goto?wibudrv and follow the
instructions given there.
Troubleshooting
Software Installation and Management Guide May 2012 253
I

2. If this does not help, proceed with the following paragraph.
Specifying a delay factor
1. On the Setup page, enter a value in Delay factor to specify the delay
factor of the WIBU dongle driver.
It is recommended that you start with a delay factor of 8. If this
helps, you can try to reduce it to 4. If it does not, you can try a
higher factor, for example, 16.
2. If this does not help, proceed with the following paragraph.
Checking the dongle on
other PCs
To check if the dongle itself or your host PC causes the problems, try
the following:
1. Install the WIBU-KEY driver on another PC.
2. Check if the dongle software recognizes the dongle on this PC.
3. If this does not help, contact dSPACE Support at
support@dspace.de.
Dongle and Floating Network License Problems
Error messages generated
by FLEXnet Publisher
Sometimes the FLEXnet Publisher software provided as of dSPACE
Release 3.4 generates misleading error messages, for example, when
no more licenses are available. If an error message appears, confirm it
and try the desired action again. If the error message appears again,
you should:
n Perform the step-by-step test described in How to Check dSPACE
Floating Network Licenses on page 261.
n Carry out the measures described below.
You need administrator rights for this.
Troubleshooting
Software Installation and Management Guide May 2012
I
254

Error message License file not found!
A local licence file was not found. This file contains the license codes
for a specific dSPACE product.
n Check if the file has been moved, deleted or renamed. Use the
dSPACE Installation Manager to add the missing file. For details,
refer to How to Add New Licenses to a Specific Local License File
on page 152. If you cannot fix the error, reinstall the dSPACE
software.
Error message License for product <product> not found!
The license entry for the specified product in the corresponding
license dsp file is missing.
This error message appears when you try to:
n Use software products or modules which you have not purchased
n Load a multiprocessor experiment on a single-processor platform
n Use PYD files without installing AutomationDesk
Carry out the measure described below.
n Check the points above. Check if the file has been moved, deleted
or renamed. Use the dSPACE Installation Manager to add the
missing license. For details, refer to How to Add New Licenses to a
Specific Local License File on page 152. If you cannot fix the error,
reinstall the dSPACE software.
Error message License for product <product> not valid!
There is a number of possible reasons why the license might not be
valid. Perhaps the license string of the product license is incorrect. In
addition, the license entry might belong to an earlier version of the
dSPACE software .
n If the license string is incorrect or the license entry belongs to an
earlier product version, use the dSPACE Installation Manager to add
the valid license. For details, refer to How to Add New Licenses to a
Specific Local License File on page 152. If you cannot fix the error,
reinstall the dSPACE software.
Error message Execution key invalid or not found!
n If the license entry does not match the number of the dongle, you
just have to connect the correct dongle to the PC.
Troubleshooting
Software Installation and Management Guide May 2012 255
I

Error message License for product <product> has expired!
The license has expired.
n Your license is time-limited and the expiration date has passed. To
continue working with the software, you have to renew your
license. Contact the dSPACE sales department for further
information.
Error message Cannot find environment variable DSPACE_CONFIG!
This environment variable points to the dSPACE configuration folder
where the license files reside.
n Repair the RCP and HIL software installation with the dSPACE
Maintenance Setup. Select Start Programs dSPACE RCP & HIL
<x.y> dSPACE Maintenance Setup RCP & HIL (RCP & HIL <x.y>)
Error message in
SystemDesk
License missing. Creation failed. This action requires license type <xyz>
or higher. Please check your license file for a valid product entry. Or
check your license key or license server connection. Or contact dSPACE
GmbH to upgrade your licenses.
The license entry is missing. This error message appears when you try
to use an element type which you do not have a license for.
n Check if the license file contains the necessary license entry.
n If you use dongle licenses, check if the license entry matches the
number of the dongle. You just have to connect the correct dongle
to the PC.
n If you use floating network licenses, check the connection to the
license server and if a free license is available.
n If your license type does not fulfill the element type's requirements,
contact dSPACE to upgrade your licenses.
Related topics
References
Dongle License Problems on page 249
Floating Network License Problems on page 256
Troubleshooting
Software Installation and Management Guide May 2012
I
256

Floating Network License Problems
Error messages generated
by FLEXnet Publisher
Sometimes the FLEXnet Publisher software provided as of dSPACE
Release 3.4 generates misleading error messages, for example, when
no more licenses are available. If an error message appears, confirm it
and try the desired action again. If the error message appears again,
you should:
n Perform the step-by-step test described in How to Check dSPACE
Floating Network Licenses on page 261.
n Carry out the measures described below.
Error message Floating network license file not found!
The file containing information about the dSPACE License Server to be
used was not found on the dSPACE License Client.
1. On the dSPACE License Client: From Start Programs dSPACE
Installation Manager, select dSPACE Installation Manager.
2. Click the Licenses tab.
3. In the dSPACE Licensing window, click the Network Licenses
Configuration tab.
On the Client tab, all dSPACE installations available on your host PC
are listed.
4. Select the installation(s) which you should connect to a specific
dSPACE License Server.
The License server name and License server port edit fields appear.
5. Specify the IP address and the TCP/IP port of the dSPACE License
Server.
Error message Floating network license server not found!
The server specified in the file containing information about the
dSPACE License Server to be used was not found on the network.
There are two possible reasons:
n The dSPACE License Server is not available, because, for example
the dSPACE License Server is currently down : Contact your IT
department to check, if the dSPACE License Server is running.
n If the license server is up and running, do the following:
1. On the dSPACE License Client: From Start Programs dSPACE
Installation Manager, select dSPACE Installation Manager.
The dSPACE Installation Manager opens.
Troubleshooting
Software Installation and Management Guide May 2012 257
I

2. Click the Licenses tab.
3. In the dSPACE Licensing window, click the Network Licenses
Configuration tab.
On the Client tab, all dSPACE installations available on your host
PC are listed.
4. Select the installation(s) which you should connect to a specific
dSPACE License Server.
The License server name and License server port edit fields
appear.
5. Specify the IP address and the TCP/IP port of the dSPACE License
Server.
Error message Syntax error in floating network license file!
The local configuration file containing information about the dSPACE
License Server to be used has a syntax error. This can happen if you
change the entries in the local configuration file without using the
dSPACE Installation Manager.
1. On the dSPACE License Client: From Start Programs dSPACE
Installation Manager, select dSPACE Installation Manager.
The dSPACE Installation Manager opens.
2. Click the Licenses tab.
3. In the dSPACE Licensing window, click the Network Licenses
Configuration tab.
On the Client tab, all dSPACE installations available on your host PC
are listed.
4. Select the installation(s) which you should connect to a specific
dSPACE License Server.
The License server name and License server port edit fields appear.
5. Check the IP address and the TCP/IP port of the dSPACE License
Server and correct it if necessary.
The dSPACE License Server version is too old and cannot read the
License.dat file.
n On the dSPACE License Server, install the latest dSPACE License
Server version. Refer to How to Install and Configure the dSPACE
License Server on page 178.
You can also find the latest version of the dSPACE License Server at
http://www.dspace.com/goto?FNLServer.
Troubleshooting
Software Installation and Management Guide May 2012
I
258

Error message All licenses for product <product> are currently being used!
You have tried to obtain a license from the dSPACE License Server, but
all available licenses are currently in use.
n A license becomes available after the session using it has finished
and/or the linger time (if applicable) has elapsed. If this problem
occurs frequently, you should consider purchasing additional
licenses for the specified product.
Error message License for product <product> not found!
There is no license for the specified product available on the dSPACE
License Server.
n Purchase a license for the specified product and add it to to the
dSPACE system. You must merge the license information first. Refer
to Merging License Files on page 162.
Error message Could not connect to license server!
There are several reasons why the dSPACE License Client could not
connect to the dSPACE License Server. If this message occurs, do the
following:
n Check if the IP address and the TCP/IP port of the dSPACE License
Server are specified correctly.
1. On the dSPACE License Client: From Start Programs dSPACE
Installation Manager, select dSPACE Installation Manager.
The dSPACE Installation Manager opens.
2. Click the Licenses tab.
3. In the dSPACE Licensing window, click the Network Licenses
Configuration tab.
On the Client tab, all dSPACE installations available on your host
PC are listed.
4. Select the installation(s) which you should connect to a specific
dSPACE License Server.
The License server name and License server port edit fields
appear.
5. Check the IP address and the TCP/IP port of the dSPACE License
Server and correct it if necessary.
Troubleshooting
Software Installation and Management Guide May 2012 259
I

n Check if the PC which runs the dSPACE License Server appears in
your Network Neighborhood. However, the dSPACE License Server
could be down even if it is actually displayed due to the limitations
of Microsoft's networking design. On the other hand, if it is not
displayed, this does not necessarily mean that the TCP/IP
connection is faulty. It could be a setting made by your network
administrator.
n To check if a connection to the license server PC is possible at all,
you could ping it in a Command Prompt window, for example, ping
licserver
The Command Prompt window should show the following:
Pinging licserver.mydomain.com [10.0.0.1] with 32 bytes
of data:
Reply from 10.0.0.1: bytes=32 time<10ms TTL=128
Reply from 10.0.0.1: bytes=32 time<10ms TTL=128
Reply from 10.0.0.1: bytes=32 time<10ms TTL=128
Reply from 10.0.0.1: bytes=32 time<10ms TTL=128
If the ping command results in a timeout, there is no network
connection, or the dSPACE License Server is down.
n If the dSPACE License Server can be reached, but the dSPACE
software nevertheless fails to connect, make sure there is no
firewall which rejects packets destined to the given port (27000 by
default). If the network problems persist, consult your network
administrator.
Error message Bad system date on license server!
The system date of the dSPACE License Client is not compliant with
the system date of the dSPACE License Server.
n Set the system date of the dSPACE License Client to the date of the
dSPACE License Server.
You can open a Command Prompt window, for
example, as follows: From the Start menu, choose Run
..., enter cmd and click OK.
Troubleshooting
Software Installation and Management Guide May 2012
I
260

Error message FLEXnet Publisher Module missing
You tried to install the dSPACE software with license files that did not
contain a floating network license. The software was not installed.
1. From the Start Programs dSPACE <product> <x.y> menu, select
dSPACE Maintenance Setup (<product> <x.y>) .
<product> <x.y> is a placeholder for the software and its version,
since your host PC can have multiple installations and multiple
products in Start Programs. The term dSPACE Maintenance Setup
is used for all product-specific versions, for example, dSPACE
Maintenance Setup (TargetLink 3.3) .
2. Select Modify.
3. Follow the instructions of the setup program.
4. When prompted, specify the path of the license files folder
containing the floating network license file.
Related topics
Make sure that the license files contain the Keys.dsp and
License.dsp files for all products installed with the first
installation. Products whose license information is not
contained in the license files will be uninstalled.
References
Dongle and Floating Network License Problems on page 253
Dongle License Problems on page 249
Troubleshooting
Software Installation and Management Guide May 2012 261
I

How to Check dSPACE Floating Network Licenses
Objective Perform the following checks if you have problems with floating
network licenses.
Since you can work with a dongle license, which is based on a dongle,
and a floating network license on the same PC, you should first check
your specific license type.
Method To find out the license type
1 From Start Programs dSPACE Installation Manager, select dSPACE
Installation Manager.
2 Click the Licenses tab.
3 In the dSPACE Licensing window, click the Manage Runtime Licenses
tab.
The tabbed page lists all the dSPACE installations on your host PC.
4 Select the installation from the list and expand it to see the license
entries.
The entries in the local License.dsp file that is associated to the
selected installation on your PC are displayed.
Floating Network licenses are labeled as FlexNet in the Type
column.
Troubleshooting
Software Installation and Management Guide May 2012
I
262

Step-by-step license check You should perform the following step-by-step license check before
you proceed to the troubleshooting instructions in License Problems
on page 248:
Step Point to check Method
1 Check if a floating
network license has
expired.
1. On the dSPACE License Server, open the
<InstallDir>\Exe\License.dat file with a text editor.
<InstallDir> is the folder where the dSPACE License
Server software is installed. The file contains the floating
network license codes for the available dSPACE products.
The general license code pattern reads like this:
INCREMENT <feat> <vend> <ver> <expir_date> <num> DUP_GROUP =
<[H][U][D][V]> SIGN = 123456789AB
If the expiration date is not yet reached or if the code
contains the string permanent instead of an expiration date,
the license has not expired.
If the license has expired, contact the dSPACE sales
department.
2 Check if the dSPACE
License Server is running.
1. Right-click on the taskbar of the dSPACE License Server.
2. From the context menu, select Task Manager.
3. In the Task Manager, change to the Processes page.
4. In the Image Name list, check if the processes dspace.exe
and lmgrd.exe are running.
5. If both processes are running, check if the dSPACE License
Clients can access the server. Refer to step 3.
If one of the processes is not yet running, open a
Command Prompt window, change to <InstallDir>\Exe\
and enter
lmutil lmreread -vendor DSPACE
If there is still one process not running after running
lmutil, read the entries in the
<InstallDir>\Exe\dSPACElm.log file for further
information.
Running lmutil requires administrator rights.
Troubleshooting
Software Installation and Management Guide May 2012 263
I

3 Check the TCP/IP
connection between
license server and license
client.
1. On the dSPACE License Client, open a Command Prompt
window and enter the following command:
ping <myserver>
If a message similar to the following one appears, the
TCP/IP connection is ok.
Pinging <myserver>.<mycompany.com> [10.1.2.3] with
32 bytes of data:
Reply from 10.1.2.3: bytes=32 time<10ms TTL=128
Reply from 10.1.2.3: bytes=32 time<10ms TTL=128
Reply from 10.1.2.3: bytes=32 time<10ms TTL=128
Reply from 10.1.2.3: bytes=32 time<10ms TTL=128
If the following message appears, the client cannot access
the license server.
Request timed out.
In this case, ask your network administrator to establish a
TCP/IP connection between client and server.
Step Point to check Method
Troubleshooting
Software Installation and Management Guide May 2012
I
264

4 Check the configuration
of the dSPACE License
Servers TCP/IP ports.
1. Make sure that:
o The IP address of the license server is constant.
o The selected TCP/IP ports are not blocked by a firewall
between the dSPACE License Server and the dSPACE
License Client.
o The selected TCP/IP ports are also enabled in a Virtual
Private Network.
2. Define the TCP/IP port used for communication with the
connected dSPACE License Clients: You can find it in the
<InstallDir>\Exe\dSPACElm.log file in the line
<hh>:<mm>:<ss> (lmgrd) lmgrd tcp-port <TCP_Port>
3. On the dSPACE License Client and the dSPACE License
Server, start Telnet: From the Start menu, select Programs
Accessories Telnet.
4. Open a Command Prompt window and enter the
following command:
telnet <myserver> <TCP_Port>
If the message Connection failed is displayed, ask your
system administrator to configure the TCP/IP port of the
dSPACE License Server.
Perhaps a firewall or router between the dSPACE License
Server and the dSPACE License Client in question is not
configured correctly to handle the specified TCP/IP port.
If no error message appears, the configuration is OK.
5 Check the license servers
registry entries.
1. Check the registry entries of the dSPACE License Server.
The server uses the following entry depending on the
operating system used:
o 32-bit operating system:
HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager
o 64-bit operating system:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\FLEXlm License Manager
o If the registry entry does not point to the correct
License.dat file path, create a new registry key under
HKEY_LOCAL_MACHINE\SOFTWARE or
(HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node) and
(re-)name it FLEXlm License Manager. Add the string
value DSPACE_LICENSE_FILE containing the full path of
the License.dat file.
o If the registry entry points to the correct license file path,
the server uses the correct License.dat file.
Step Point to check Method
Troubleshooting
Software Installation and Management Guide May 2012 265
I

More troubleshooting If your problems are not yet resolved, refer to the troubleshooting
instructions in License Problems on page 248.
Related topics
You can open a Command Prompt window, for example,
as follows: From the Start menu, choose Run ..., enter
cmd and click OK.
The FLEXnet License Administration Guide provides a
troubleshooting section. The guide is available:
n On your dSPACE DVD in the
\Tools\LicenseServer\fnp_LicAdmin.pdf file
n On the dSPACE License Server (after installation of the
dSPACE software)
Basics
Protected Modules and Required Licenses on page 42
Protected Products and Required Licenses on page 36
Specifics on Using Floating Network Licenses on page 173
Troubleshooting
Software Installation and Management Guide May 2012
I
266

I
267

Software Installation and Management Guide May 2012


Appendix: System Requirements
Objective Before installing dSPACEs software, you have to check whether your
system meets the system requirements.
Where to go from here Information in this section
Basic System Requirements 268
For some complex tasks your system has to meet additional
requirements.
Remote Control of Measurement and Calibration
Systems According to ASAM-MCD 3MC (ASAP3) via
AutomationDesk
290
3-D Online Animation via MotionDesk 290
Using Automotive Simulation Models (Vehicle
Dynamics, Trailer, Truck, Traffic Scenarios)
292
Using AutoBoot Option 292
Resource Requirements of dSPACE Boards
Depending on the installation, dSPACE boards require
resources in the host PC and the expansion box.
293
Appendix: System Requirements
Software Installation and Management Guide May 2012
I
268

Basic System Requirements
Objective Check whether your system meets the basic requirements. The
requirements for third-party software, for example, software from
MathWorks

, may be higher. For details, refer to the corresponding


software documentation.
Where to go from here Information in this section
Host PC Hardware 269
Operating System 273
Run-Time-Compatibility of dSPACE Software 276
Limitations for Windows Vista/Windows 7 277
Limitations for 64-Bit Windows Operating Systems
in Combination with dSPACE 32-Bit Software
278
Limitations for TargetLink 64-Bit Version 278
Third-Party Software 279
Expansion Box Hardware 286
Appendix: System Requirements
Software Installation and Management Guide May 2012 269
I

Host PC Hardware
Host PC requirements You can use an x86-compatible personal computer as a host PC for
your dSPACE applications. If you install the 64-bit versions of
TargetLink or Model Compare you need a 64-bit (x64) processor.
Hardware dSPACE Software Required
Host processor RCP and HIL software
1)
Pentium 4 at 2 GHz (or equivalent)
AutomationDesk
TargetLink
Model Compare
ControlDesk Next
Generation
SystemDesk o Pentium 4 at 2 GHz (or equivalent)
o Pentium 4 at 3 GHz or higher (recommended)
Main memory RCP and HIL software
1)
o 1 GB RAM
o 2 GB RAM or more (recommended)
AutomationDesk
ControlDesk Next
Generation
TargetLink (32-bit version)
Model Compare (32-bit
version)
TargetLink (64-bit version) o 4 GB RAM
o 8 GB RAM or more (recommended)
Model Compare (64-bit
version)
4 GB RAM
SystemDesk o 2 GB RAM
o 3 GB RAM or more (recommended)
Disk space
2)
Complete installation of
the DVD
o 5.5 GB on the program partition
o In addition up tp 6.0 GB on the system
partition, for example, for runtime software
like the Microsoft .NET Framework
Disk drives All DVD drive for software installation
Appendix: System Requirements
Software Installation and Management Guide May 2012
I
270

Ports for
connecting
hardware
RCP and HIL software o For communication with RapidPro hardware,
you need a USB port.
o For using the SteeringController Instrument in
ControlDesk, you need a game port or USB
port to connect a game controller device.
o For using ControlDesk Failure Simulation, you
need a serial port (COM1, COM2, COM3 or
COM4) that can be run at 9,600 bps to
connect dSPACE Simulator's failure insertion
unit (FIU).
TargetLink For processor-in-the-loop (PIL) simulation, you
need:
o A serial port (COM1, COM2, COM3, or
COM4) that can be run at 19,200, 38,400,
57,600, or 115,200 bps
o A free USB port when using the NEC CanIt
F3377, MCT S12X T-Board USB, Freescale
MPC5561EVB USB or Infineon SK-EB XC2287
evaluation board
ControlDesk Next
Generation
o For connecting hardware (DCI-CAN1, CalHub,
DCI-GSI1), you need a USB port version 1.1
(USB 2.0 recommended).
o For using the SteeringController Instrument,
you need a USB port to connect a game
controller device.
o For using ControlDesk Failure Simulation, you
need a serial port that can be run at 9,600 bps
to connect dSPACE Simulator's failure insertion
unit (FIU).
Hardware dSPACE Software Required
Appendix: System Requirements
Software Installation and Management Guide May 2012 271
I

Using MicroAutobox
Embedded PC as host PC
ControlDesk Next Generation can also be installed on the
MicroAutoBox Embedded PC, running under Microsoft Windows 7
Ultimate (32-bit version).
Additional requirements
for license handling
Required slots for dSPACE
boards
The dSPACE boards have different slot requirements for the installation
in the host PC.
DS1104 To install a DS1104, you need one free 33 MHz/32-bit 5 V
PCI slot.
DS1103, modular system based on DS1005 or DS1006 You
cannot install a DS1103, DS1005, or DS1006 in your host PC. You can
install these systems only in an expansion box.
Display RCP and HIL software
1)
o OpenGL-compliant graphics adapter (16, 24,
or 32-bit)
3)
o Windows' display properties must be set to at
least 16-bit
3)
TargetLink o Standard graphics adapter with 1024 x 768
resolution (min.)
o Windows' display property "Custom Text Size
(DPI)" must be set to 100 % (default setting)
or to 125 %. Other settings are not supported.
Model Compare Windows' display property "Custom text size
(DPI)" must be set to 100 % (default setting) or
to 125 %. Other settings are not supported.
1)
For some complex tasks your host PC has to meet additional requirements. Refer to Additional Requirements for Specific
Products and Tasks on page 289
2)
Keep in mind that additional disk space is required for non-dSPACE software, for example, from MathWorks

.
3)
Required by MATLAB.
Hardware dSPACE Software Required
License Type Host PC Requirements
Dongle licenses o A USB port: To install the execution key (dongle)
A special version of the execution key for connection to a parallel
port is available on request.
Floating network licenses o All the PCs on which you want to run dSPACE software (dSPACE
License Clients) need to be able to establish a TCP/IP connection to
the dSPACE License Server.
Appendix: System Requirements
Software Installation and Management Guide May 2012
I
272

Link boards A link board is required in your host PC:
n To connect your modular system installed in an expansion box to
the host PC via a bus interface.
n To connect MicroAutoBox, dSPACE Simulator Compact, or dSPACE
Simulator Mid-Size to the host PC.
The possible link boards require the following slots in your host PC:
dSPACE system with Ethernet connection To connect your
dSPACE system to the host PC via an Ethernet connection, your host
PC must have a 10baseT (twisted pair, 10 Mbit/s or faster) network
adapter.
MicroAutoBox II and the SCALEXIO system require no
link board. Host PC communication is established via
Ethernet.
Link Board Required slots
DS815 One free PC card slot (type 2)
DS817 One free 5 V PCI slot
DS819 One free PCI Express slot (x1 ... x32)
DS821-34 mm One free ExpressCard/34 slot or one free
ExpressCard/54 slot
DS821-54 mm One free ExpressCard/54 slot
Appendix: System Requirements
Software Installation and Management Guide May 2012 273
I

Operating System
Operating system on host
PC
The following table shows which software products in Release 7.3
support which operating system:
Operating System Is Supported By
R
C
P

&

H
I
L

S
o
f
t
w
a
r
e
A
u
t
o
m
a
t
i
o
n
D
e
s
k

3
.
5
C
o
n
t
r
o
l
D
e
s
k

4
.
2
.
1
1
)
T
a
r
g
e
t
L
i
n
k

3
.
3
T
a
r
g
e
t
L
i
n
k

3
.
3

(
6
4
-
b
i
t

v
e
r
s
i
o
n
)
M
o
d
e
l

C
o
m
p
a
r
e

2
.
2
M
o
d
e
l

C
o
m
p
a
r
e

2
.
2

(
6
4
-
b
i
t

v
e
r
s
i
o
n
)
S
y
s
t
e
m
D
e
s
k

3
.
1
C
o
m
m
o
n

d
S
P
A
C
E

S
o
f
t
w
a
r
e

T
o
o
l
s
Windows XP Professional (32-bit
version) with Service Pack 3

Windows Vista Business, Ultimate,
and Enterprise (32-bit version) with
Service Pack 2
2)

Windows Vista Business, Ultimate,
and Enterprise (64-bit version) with
Service Pack 2
2)

3)

3)

3)

3)
Windows 7 Professional, Ultimate,
and Enterprise (32-bit version) with
Service Pack 1
4)

5)

Windows 7 Professional, Ultimate,
and Enterprise (64-bit version) with
Service Pack 1
4)

3)

3)

3)5)

3)

3)

3)

3)
1)
ControlDesk Next Generation (= ControlDesk 4.x) is the successor to CalDesk and ControlDesk 3.x. However, ControlDesk
versions earlier than ControlDesk 4.0 are still included in the RCP and HIL software package.
2)
Only the Windows Vista Business, Ultimate, and Enterprise editions are supported. The Windows Vista Home and Starter
editions are not supported.
3)
The 64-bit operating systems are supported by 32-bit software running in WoW64 (Windows-On-Windows64).
4)
Only the Windows 7 Professional, Ultimate, and Enterprise editions are supported. The Windows 7 Home and Starter editions
are not supported.
5)
ControlDesk Next Generation's ECU Diagnostics v2.0.1 device (supporting ASAM MCD-3 D V2.0.1) does not support this
operating system. As an alternative, you can use the ECU Diagnostics v2.0.2 device (supporting ASAM MCD-3 D V2.0.2), which
supports this operating system.
Appendix: System Requirements
Software Installation and Management Guide May 2012
I
274

Limitations for Windows Vista/Windows 7 Some limitations
apply when you use Windows Vista or Windows 7 in combination
with dSPACE software. Refer to Limitations for Windows
Vista/Windows 7 on page 277.
32-bit dSPACE software running on 64-bit Windows operating
systems dSPACE software runs as a 32-bit application under 64-bit
Windows operating systems in a WoW64 (Windows-on-Windows 64-
bit) subsystem. WoW64 is the x86 emulator that allows 32-bit
Windows-based applications to run seamlessly on 64-bit versions of
Windows. This allows you to use up to 4 GB virtual memory for each
32-bit process. 32-bit versions of Windows can address only up to 3.2
GB of memory in total for all running processes including the
operating system itself.
Some additional limitations apply when you use a 64-bit Windows
operating system with dSPACE software. Refer to Limitations for 64-Bit
Windows Operating Systems in Combination with dSPACE 32-Bit
Software on page 278.
Allowing communication
via additional firewall
rules
During installation of the dSPACE software, two additional Windows
firewall rules are installed. The first rule allows communication with a
dSPACE expansion box, for example, AutoBox. The second rule allows
MotionDesk to receive motion data from a network channel.
The rules are created by the following commands:
n advfirewall firewall add rule name="dSPACE Net Service"
service=any dir=in action=allow profile=any
protocol=icmpv4:0, any description="Allow the dSPACE Net
Service to connect to a dSPACE expansion box via network."
n advfirewall firewall add rule name="dSPACE MotionDesk"
program="%dspace_root%\MotionDesk\Bin\MotionDesk.exe"
n Windows XP Professional x64 Edition is not supported
in general.
n The 64-bit versions of TargetLink and Model Compare
require Windows 7 Professional, Ultimate, or
Enterprise (64-bit version) with Service Pack 1.
Other 64-bit operating systems (Windows XP and
Windows Vista) are not supported.
n ControlDesk Next Generation can also be installed on
the MicroAutoBox Embedded PC, running under
Microsoft Windows 7 Ultimate (32-bit version).
Appendix: System Requirements
Software Installation and Management Guide May 2012 275
I

dir=in action=allow profile=any description="Allow dSPACE
MotionDesk to receive motion data via network."
Operating system on
dSPACE License Server
If you purchased floating network licenses, you have to install and
configure one of the networked PCs as the dSPACE License Server.
The operating system of the dSPACE License Server must be one of the
following:
n Windows XP Professional (32-bit version) with Service Pack 3
n Windows Vista Business, Ultimate, or Enterprise (32-bit or 64-bit
version) with the latest Service Pack
n Windows 7 Professional, Ultimate, or Enterprise (32-bit or 64-bit
version)
n Windows Server 2003 (32-bit or 64-bit version)
n Windows Server 2008 (32-bit or 64-bit version)
n Windows Server 2008 RC (32-bit or 64-bit version)
The dSPACE License Server does not support
non-Windows operating systems.
Appendix: System Requirements
Software Installation and Management Guide May 2012
I
276

Run-Time-Compatibility of dSPACE Software
Definition Run-time compatibility means:
n dSPACE products can be used in parallel after software installation,
even if they are installed in different folders.
n dSPACE products without interaction can run independently of
each other.
General notes on
limitations
If dSPACE products interact directly (for example, through automation
interfaces) or indirectly (for example, through common file types like
.a2l) limitations may apply. For major limitations, see below. For minor
limitations, refer to the appropriate product documentation.
In rare cases, an additional patch must be installed for a product to
achieve run-time compatibility. For information on, whether a patch is
necessary and for the patch itself, refer to
http://www.dspace.com/go/CompPatch.
Compatibility of products
in dSPACE Release 7.3
Each software product in dSPACE Release 7.3 is run-time-compatible
with the other software products in dSPACE Release 6.6 up to dSPACE
Release 7.3. Note that RCP and HIL software products (on Release 7.3)
cannot be used in combination with RCP and HIL software products
from earlier dSPACE Releases.
Limitations for TargetLink and ModelCompare
n With Model Compare 2.1 (on dSPACE Release 7.1) and earlier, you
can not dump TargetLink 3.3 models. If you need to dump
TargetLink 3.3 models with Model Compare 2.1, contact dSPACE
support for a compatibility patch.
n The 64-bit version of TargetLink cannot be used in combination
with the 32-bit version of Model Compare and vice versa because
you can work only with a bit-compatible MATLAB version (32-bit or
64-bit).
Limitation for ControlDesk Next Generation (= ControlDesk as
of ControlDesk 4.0) When ControlDesk 4.2.1 is used with dSPACE
Release 7.0 or earlier, limitations regarding Real-Time Testing (RTT)
apply. Simulink models compiled with these releases are not supported
by the Signal Editor (for signal generation) and for CAN Data Replay of
the Bus Navigator. For details, refer to Problem with Incompatibility
Between RTT 1.9 and 1.6 on page 246.
Appendix: System Requirements
Software Installation and Management Guide May 2012 277
I

Limitations for Windows Vista/Windows 7
Objective Some limitations apply when you use Windows Vista/Windows 7 in
combination with dSPACE software.
MATLAB support For system requirements of MathWorks

software, refer to
http://www.mathworks.com/support/sysreq/current_release.
Fast user switching not
supported
The dSPACE software does not support the fast user switching feature
of Windows.
Closing dSPACE software
before PC shutdown
The shutdown procedure of Windows operating systems might cause
some required processes to be aborted although they are still being
used by dSPACE software. To avoid data loss, it is recommended to
terminate the dSPACE software manually before a PC shutdown is
performed.
User Account Control It is recommended to disable Windows User Account Control (UAC)
during the installation of dSPACE software. If you cannot disable it,
you should note the following Windows behavior: If UAC is enabled,
the setup programs run with the administrator account instead of the
user account. Therefore it is important that the administrator account
has access to the required drives, particularly to the required network
drives.
USB devices under
Windows 7
The first time dSPACE USB devices using cables with opto-isolation are
connected to the PC, there might be a message that the device driver
software was not successfully installed. The dSPACE device will
nevertheless work properly later on.
Using boards with ISA
interface installed in the
host PC
When installed directly in the host PC, ISA boards such as the DS1103
or DS813 cannot be used with Windows Vista/Windows 7 with the
standard installation routines. If necessary, contact dSPACE Support.
Appendix: System Requirements
Software Installation and Management Guide May 2012
I
278

Limitations for 64-Bit Windows Operating Systems in
Combination with dSPACE 32-Bit Software
Objective Some additional limitations apply when you use Windows
Vista/Windows 7 (64-bit versions) in combination with dSPACE 32-bit
software.
Limitations of device
drivers
Third-party bus interfaces (CAN, LIN, or FlexRay) are supported only if
they have 64-bit drivers from the manufacturers.
Limitations of target
compilers
For information on support for a specific target compiler, contact the
respective compiler manufacturer.
MATLAB If you install a 32-bit version of MATLAB under Windows
Vista/Windows 7 (64-bit versions), the MATLAB installation program
generates a message that a 64-bit version of MATLAB is available.
Click OK and continue installing the 32-bit version of MATLAB.
Limitations for TargetLink 64-Bit Version
Objective Some additional limitations apply when you use the 64-bit version of
TargetLink.
Parallel installation of a 32-
bit and a 64-bit version of
MATLAB
On a 64-bit operating system, you can install both a 32-bit and a 64-
bit version of a particular MATLAB release, for example, R2009a.
However, MATLAB release versions share the same preference settings
folder, which means that you have to set all architecture-dependent
settings such as the MEX compiler settings each time you switch
between different versions of one MATLAB release.
Importing an A2L file It is not possible to import an A2L file into a 64-bit version of
TargetLink. However, you can use a workaround desribed in Basics of
Importing ASAM MCD-2 MC Files ( dSPACE Data Dictionary Basic
Concepts Guide).
ST M
Appendix: System Requirements
Software Installation and Management Guide May 2012 279
I

Third-Party Software
Overview You may need to install third-party products to work with dSPACE
products. The following table shows which dSPACE product requires
which third-party software.
Third-Party
Software
R
C
P

a
n
d

H
I
L

s
o
f
t
w
a
r
e
A
u
t
o
m
a
t
i
o
n
D
e
s
k
T
a
r
g
e
t
L
i
n
k
M
o
d
e
l

C
o
m
p
a
r
e
C
o
n
t
r
o
l
D
e
s
k

N
e
x
t

G
e
n
e
r
a
t
i
o
n
MATLAB

/Simulink

To work with:
RTI
Various RTI Blocksets
RTI-MP
ConfigurationDesk -
Implementation Version
MLIB/MTRACE
Automotive Simulation Models
(ASM)
To automate
MATLAB via
AutomationD
esk's MATLAB
Access library.
To work with
TargetLink
To work
with Model
Compare

Simulink

Coder
TM
and
MATLAB Coder
TM

(formerly
Real-Time Workshop

)
For C code generation with RTI
and RTI-MP
For C code generation with
ConfigurationDesk -
Implementation Version
For C code generation of
Automotive Simulation Models
(ASM)

C compiler For compiling real- time
applications for the DS1103,
DS1104, DS1005, DS1006,
MicroAutoBox, the RapidPro
Control Unit with MPC5554,
and the SCALEXIO system
For compiling slave applications
for the DS1103, DS2210,
DS2211, and DS2302
For
production
code
generation
and
processor-
in-the-loop
(PIL)
simulation
For
building
MATLAB
MEX files

Required for using the RTI CAN
MultiMessage Blockset and RTI
LIN MultiMessage Blockset to
build MATLAB MEX files.
You can use the LCC compiler as
shipped with MATLAB as the C
Compiler.

DAQ modules
configuration software
To configure DAQ
modules
Appendix: System Requirements
Software Installation and Management Guide May 2012
I
280

Make sure that the versions of the third-party software you intend to
install are supported by the dSPACE software. For compatibility
information:
n Refer to MATLAB Compatibility Information on page 69
n See below for other third-party software (for example C compilers)
CAN hardware driver To use CAN interfaces from Vector
Informatik GmbH
To use CAN
interfaces from
Kvaser or Vector
Informatik GmbH
Driver for FlexRay
interfaces
To use FlexRay
interfaces from
Eberspcher
Electronics (formerly
TZM), Elektrobit or
Vector Informatik
GmbH
Ethernet driver To communicate
with an ECU with
XCP on Ethernet
Microsoft Internet
Explorer
To work with dSPACE software and use dSPACE's online help dSPACE HelpDesk.
Microsoft Office To automate Microsoft Office applications such as writing data to an Excel sheet with Python.
PDF Acrobat Reader To read PDF files, for example of the dSPACE documentation, and to create PDF files with some dSPACE
software products (for example, TargetLink and Model Compare).
Third-Party
Software
R
C
P

a
n
d

H
I
L

s
o
f
t
w
a
r
e
A
u
t
o
m
a
t
i
o
n
D
e
s
k
T
a
r
g
e
t
L
i
n
k
M
o
d
e
l

C
o
m
p
a
r
e
C
o
n
t
r
o
l
D
e
s
k

N
e
x
t

G
e
n
e
r
a
t
i
o
n
Appendix: System Requirements
Software Installation and Management Guide May 2012 281
I

C compiler for RCP and HIL
software
The C compiler you need depends on the dSPACE hardware you use.
Microtec PowerPC C Compiler You can order the required
Microtec PowerPC C Compiler together with your dSPACE system. The
compiler is then installed automatically with the dSPACE software.
Refer to Microtec PowerPC C Compiler on page 76.
DS1006 Compiler The dSPACE DS1006 Compiler Version 2.2
based on GNU C Compiler Ver. 3.3.5 is free of charge and is installed
automatically with the dSPACE software. Refer to dSPACE DS1006
Compiler on page 78.
SCALEXIO GNU C/C++ Compiler (QNX) The SCALEXIO GNU
C/C++ compiler 6.5.0 is based on GNU C Compiler Ver. 4.4.2 as
provided by QNX Software Systems and is installed with the dSPACE
software products which require the compiler. Refer to SCALEXIO GNU
C/C++ Compiler (QNX) on page 79.
Texas Instruments ANSI C Compiler The Texas Instruments tools
are not part of the dSPACE Releases and have to be purchased
separately. Refer to Texas Instruments ANSI C Compiler on page 79.
Hardware Required C Compiler
DS1005 Microtec PowerPC C Compiler Ver. 3.7
1)
DS1006 dSPACE DS1006 Compiler Version 2.2 based on GNU C Compiler Ver.
3.3.5
1)
DS1103 o Microtec PowerPC C Compiler Ver. 3.7
1)
o Texas Instruments C2000 Code Composer Tools (including
TMS320C2x/C2xx/C5x Compiler Vs 7.0)
2)
DS1104 Microtec PowerPC C Compiler Ver. 3.7
1)
MicroAutoBox Microtec PowerPC C Compiler Ver. 3.7
1)
DS2210 One of the following Texas Instruments tools
2)
(including an ANSI C
Compiler):
o TMS 320C3x/C4x Code Generation Tools Ver. 4.70
o TMS 320C3x/C4x Code Generation Tools Ver. 5.11
o TMS 320C3x/C4x Code Composer Tools Release 4.10 (including TI
Compiler Ver. 5.11)
DS2211
DS2302
RapidPro Control Unit
with MPC5554
Microtec PowerPC C Compiler Ver. 3.7
1)
SCALEXIO system SCALEXIO GNU C/C++ Compiler (QNX)
1)
1)
For compiling real-time applications.
2)
For compiling slave applications.
Appendix: System Requirements
Software Installation and Management Guide May 2012
I
282

Driver for CAN interfaces
from Vector Informatik
GmbH for ControlDesk
Failure Simulation
To use CAN interfaces from Vector Informatik GmbH with ControlDesk
Failure Simulation, you need the XL Driver Library 7.5 or later.
Download it from http://www.vector-informatik.de.
C Compiler for TargetLink For compatibility reasons, TargetLink requires that specific C compilers
for building MATLAB MEX files and processor-in-the-loop (PIL)
simulation applications are installed:
n One of the following C compilers to build MATLAB MEX files:
o Microsoft Visual C/C++ Ver. 7.1, Ver. 2005, Ver. 2008, or Ver.
2010 (recommended, see the MATLAB documentation)
o LCC Compiler as shipped with the supported MATLAB versions
If you use the 64-bit version of TargetLink, the LCC Compiler is
not available, because it is not shipped with 64-bit MATLAB
versions.
n A target-specific compiler for PIL simulation:
If you use the 64-bit version of TargetLink, Microsoft
Visual C/C++ Ver. 2008 or higher is required.
Compatible Evaluation
Boards for PIL Simulation in
TargetLink
Compatible TargetLink Compilers
Freescale HCS12EVB
1)
Cosmic 4.7
Cosmic 4.8
Metrowerks CodeWarrior 3.1
Metrowerks CodeWarrior 5.1
MCT HCS12 T-Board (DP256)
1)
Cosmic 4.7
Cosmic 4.8
Metrowerks CodeWarrior 3.1
Metrowerks CodeWarrior 5.1
MCT HCS12 T-Board (DP512) Cosmic 4.7
Cosmic 4.8
Metrowerks CodeWarrior 3.1
Metrowerks CodeWarrior 5.1
Freescale 56F8367 Evaluation
Module
Metrowerks CodeWarrior 8.3
Axiom CMD-0565 Wind River Diab 5.7
Appendix: System Requirements
Software Installation and Management Guide May 2012 283
I

Axiom CME-0555 Green Hills 5.1
Wind River Diab 5.7
Axiom MPC5554DEMO GNU 4.1
Green Hills 5.2
Metrowerks CodeWarrior 2.8
Wind River Diab 5.7
Wind River Diab 5.9
Freescale MPC5561EVB Green Hills 5.2
Metrowerks CodeWarrior 2.8
Wind River Diab 5.9
Freescale MPC5561EVB USB Green Hills 5.2
Metrowerks CodeWarrior 2.8
Wind River Diab 5.9
Freescale MPC5604BEVB Green Hills 5.2
Wind River Diab 5.9
MCT S12X T-Board Cosmic 4.8
Metrowerks CodeWarrior 5.1
MCT S12X T-Board USB Cosmic 4.8
Metrowerks CodeWarrior 5.1
I+ME Promotion Package 166 TASKING TASKING C166/ST10 Toolchain
8.6
TASKING TASKING C166/ST10 Toolchain
8.7
Infineon TriBoard TriCore 1766 TASKING TASKING TriCore VX-Toolset 3.2
TASKING TASKING TriCore VX-Toolset 3.5
Infineon TriBoard TriCore 1766 20
MHz
TASKING TASKING TriCore VX-Toolset 3.2
TASKING TASKING TriCore VX-Toolset 3.5
Infineon TriBoard TriCore 1767 TASKING TASKING TriCore VX-Toolset 3.2
TASKING TASKING TriCore VX-Toolset 3.5
Infineon TriBoard TriCore 1796 HighTec GNU 3.4
TASKING TASKING TriCore VX-Toolset 3.2
TASKING TASKING TriCore VX-Toolset 3.5
Infineon EasyKit XC2287 TASKING TASKING VX-toolset for C166 3.0
Renesas M3A-2154 Gaio 11
Gaio 9
Renesas 5.1
Compatible Evaluation
Boards for PIL Simulation in
TargetLink
Compatible TargetLink Compilers
Appendix: System Requirements
Software Installation and Management Guide May 2012
I
284

For detailed information on the evaluation boards, microcontrollers,
and compilers, refer to TargetLink Evaluation Board Hardware
Reference.
Third-Party software for
ControlDesk Next
Generation
Driver software for CAN interfaces To use CAN interfaces with
ControlDesk Next Generation, you need the appropriate driver
software versions:
Renesas EVB7058 Renesas 9.3
Renesas 9.4
Renesas SH72513 System
Development Kit
Renesas 9.4
NEC Fx3-CAN it! Green Hills 5.3
NEC 3.40
1)
The board is no longer distributed by dSPACE but is still supported for
downward compatibility
Compatible Evaluation
Boards for PIL Simulation in
TargetLink
Compatible TargetLink Compilers
CAN Interface
1)
Required Third-Party Software
Interfaces from Vector
Informatik GmbH
To use CAN interfaces from Vector Informatik GmbH with
ControlDesk Next Generation, you need the appropriate API and
driver:
o API: XL Driver Library 7.5 (or later) is required. The ControlDesk
Next Generation installation provides the Vector XL Driver
Library 7.5.
o Driver: You need a driver version that is compatible with the
API you use.
Download the driver from http://www.vector-informatik.de.
Interfaces from Kvaser To use Kvaser CAN interfaces with ControlDesk Next Generation,
you need the appropriate Kvaser driver Vers. 4.0 or later.
Download it from http://www.kvaser.com.
1)
Refer to Supported CAN Interfaces ( ControlDesk Next Generation Basic Practices Guide).
ST M
Appendix: System Requirements
Software Installation and Management Guide May 2012 285
I

Driver software for FlexRay interfaces To use FlexRay interfaces
with ControlDesk Next Generation, you need the appropriate driver
software versions:
Microsoft Internet Explorer Release 7.3 supports all versions of the Microsoft Internet Explorer
from version 6 SP1 up to the current version 9. However, limitations
can occur when you use the Microsoft Internet Explorer with dSPACE
software, for example, AutomationDesk. Refer to the limitations
chapter in the relevant documentation.
To use the dSPACE HelpDesk of Release 7.3, you need Microsoft
Internet Explorer 6 SP1 or later.
FlexRay
1)
Required Third-Party Software
Interfaces from Vector
Informatik GmbH
To use FlexRay interfaces from Vector Informatik GmbH with
ControlDesk Next Generation, you need the appropriate API and
driver:
o API: XL Driver Library 7.5 (or later) is required. The ControlDesk
Next Generation installation provides the Vector XL Driver
Library 7.5.
o Driver: You need a driver version that is compatible with the
API you use.
Download the driver from http://www.vector-informatik.de.
Interfaces from Eberspcher
Electronics (formerly TZM)
To use these FlexRay interfaces with ControlDesk Next
Generation, you need the appropriate driver Ver. 3.0 (or later).
Download it from http://www.eberspaecher.com/.
Interfaces from Elektrobit To use the Elektrobit EB 61x0 (formerly BUSDOCTOR) interfaces
with ControlDesk Next Generation, you need the appropriate
BDDriver Version 2.21.8. The driver and DLL file are shipped by
Elektrobit. To let ControlDesk Next Generation access the driver,
the bdDriver.dll file must be located in a folder specified in the
'Path' environment variable.
1)
Refer to Supported FlexRay Interfaces ( ControlDesk Next Generation Basic Practices Guide).
ST M
Appendix: System Requirements
Software Installation and Management Guide May 2012
I
286

Microsoft Office You can automate Microsoft Office applications such as writing data
to an Excel sheet with Python. The following table shows the Microsoft
Office versions supported by Release 7.3 and which operating systems
support which Office version:
Expansion Box Hardware
DS1104 It is not possible to install the DS1104 in an expansion box since this
board has a PCI connector.
DS1006 The DS1006-based modular system must be installed in a PX10 or
PX20 Expansion Box.
n The PX10 Expansion Box supports one DS1006.
n The PX20 Expansion Box supports up to two DS1006.
Microsoft Office
Version...
Supported by Operating System...
Windows XP
Professional
(32-bit version)
with Service
Pack 3
Windows Vista
1)

(32-bit version)
with the latest
Service Pack
Windows Vista
1)

(64-bit version)
2)

with the latest
Service Pack
Windows 7
3)

(32-bit version)
with the latest
Service Pack
Windows 7
3)

(64-bit version)
2)
with the
lastest Service
Pack
2000
XP
2003
4)

4)
2007
4)

4)
2010
4)

4)
1)
Only the versions Windows Vista Business, Ultimate, and Enterprise are supported. The versions Windows Vista Home and
Starter are not supported.
2)
The 64-bit operating systems are supported by 32-bit software running in WoW (Windows-On-Windows64). 64-bit MATLAB
versions are not supported.
3)
Only the versions Windows 7 Professional, Ultimate, and Enterprise are supported. The versions Windows 7 Home and Starter
are not supported.
4)
Some limitations apply when using Microsoft Office versions with 64-bit Windows operating systems. Refer to
http://office.microsoft.com.
Appendix: System Requirements
Software Installation and Management Guide May 2012 287
I

Required slots The dSPACE boards have different slot requirements for the installation
in an expansion box.
DS1103 You need one free full-size ISA slot and three adjacent
brackets. One free full-size ISA slot is required either by the DS814 (bus
connection) or the slot CPU (Ethernet connection).
Modular system based on DS1005 or DS1006 If you want to
install a modular system, you need as many free slots in the box as the
number of boards you want to install. Note that the DS2210 requires
two adjacent brackets altogether. The DS5203 requires two adjacent
brackets, if the DS5203M1 I/O modules are installed. The DS2202,
DS2211, DS4003 and the DS4004 each require a total of three
adjacent brackets. One free full-size ISA slot is required either by the
DS814 (bus connection) or the slot CPU (Ethernet connection). Note
that the slot CPU (supplied as of March 2008) requires two slots if you
use it in an AutoBox with a DS1005 with Gigalink modules.
The DS1006 has special slot requirements to ensure proper cooling of
the AMD Opteron
TM
processor:
n In a PX20 Expansion Box, the slot requirement depends on the
board revision:
o Up to board revision DS1006-03 each DS1006 requires four
slots. One of them can be used for the DS814 Link Board or the
slot CPU.
o As of board revision DS1006-06 each DS1006 requires three
slots. However, none of them can be used for the DS814 Link
Board or the slot CPU.
n In a PX10 Expansion Box, the DS1006 can be installed next to the
boxs power supply (recommended). It then requires:
o Two slots, if a DS911 Gigalink module is mounted
n The PX10/PX20 Expansion Boxes need power supplies
and connectors which fulfill the DS1006 requirements
to support a DS1006-based modular system. For
information on whether your existing expansion box
fulfills the requirements, refer to
http://www.dspace.com/goto?pxboxvers.
n The system must not exceed the max. amperage of 75
A (PX20) or 40 A (PX10) at 5 V. Note that the DS1006
needs 22 A at 5 V.
n You cannot insert a DS1006 in a PX4 Expansion Box or
in an AutoBox/TandemAutoBox.
Appendix: System Requirements
Software Installation and Management Guide May 2012
I
288

o One slot without the DS911 Gigalink module
Connecting an expansion
box and host PC via bus
connection
n The DS814 Link Board has to be installed in the expansion box.
n The DS815, DS817, DS819, or DS821 Link Board has to be installed
in the host PC.
The DS819 and DS821 Link Boards are supported by the dSPACE
software since dSPACE Release 5.2.
n You cannot connect the currently available dSPACE boards to the
host PC via DS811 and DS812 Link Board.
Connecting an expansion
box and host PC via
Ethernet
n To install your dSPACE system in an expansion box connected to the
host PC via Ethernet, a slot CPU with an integrated network
adapter has to be installed in the expansion box.
n The host PC must have a 10baseT (twisted pair, 10 Mbit/s or faster)
network adapter.
n Only if you use Autoboot Option: To install the PC Card reader, one
free bracket is required in the expansion box.
Appendix: System Requirements
Software Installation and Management Guide May 2012 289
I

Additional Requirements for Specific Products
and Tasks
Objective For some complex tasks your system has to meet additional
requirements.
Where to go from here Information in this section
Using RTI FPGA Programming Blockset
Objective Limited availability outside Europe and Asia, please inquire.
If you use the RTI FPGA Programming Blockset, your host PC has to
meet the following requirements.
Host PC requirements
Using RTI FPGA Programming Blockset 289
Remote Control of Measurement and Calibration
Systems According to ASAM-MCD 3MC (ASAP3) via
AutomationDesk
290
3-D Online Animation via MotionDesk 290
Using Automotive Simulation Models (Vehicle
Dynamics, Trailer, Truck, Traffic Scenarios)
292
Using AutoBoot Option 292
Hardware Required Recommended
Host processor Pentium 4 at 2 GHz Intel Core 2 6600 at 2.4 GHz or
higher
Main memory 1 GB RAM 2 GB RAM or more
Appendix: System Requirements
Software Installation and Management Guide May 2012
I
290

Remote Control of Measurement and Calibration Systems
According to ASAM-MCD 3MC (ASAP3) via AutomationDesk
Software requirements n A description file for your ECU
n A binary data (HEX) file containing the basic configuration of the
ECU
n A properly installed ASAM MCD-3 MC-compatible measurement
and calibration (MC) system
Hardware requirements n An ECU that can be connected to a measurement and calibration
(MC) system
n If your host PC provides two free serial interface connectors, both
AutomationDesk and the MC system can run on it. Otherwise,
AutomationDesk and the MC system require one PC each.
3-D Online Animation via MotionDesk
Objective You can use MotionDesk with the DS1103, DS1005, DS1006,
MicroAutoBox, dSPACE Simulator Compact, dSPACE Simulator Mid-
Size, dSPACE Simulator Full-Size, SCALEXIO systems, or dSPACE
Offline Simulator. In these cases, your system must meet the following
requirements.
Software requirements The latest driver for the graphics adapter must be installed.
Host PC requirements
Hardware Required Recommended
Host processor Pentium 4 at 2 GHz Intel Core i5 or i7 processor
Main memory 1 GB RAM 4 GB RAM or more
Disk space At least 3 GB
Graphics card NVIDIA Quadro graphics
accelerator (OpenGL-
compliant) with at least 512
MB RAM
Graphics memory at least 1 GB
RAM and two output channels
(one output channel to display
MotionDesk, the other to
display ModelDesk,
ControlDesk or MATLAB).
Appendix: System Requirements
Software Installation and Management Guide May 2012 291
I

Additional hardware
requirements
n For a multi-PC solution, you need:
o MotionDesk Multi-PC Interface Kit for the simulator
o 10 Mbit/s Ethernet card (or faster) for each connected
MotionDesk PC
n For a Simulink simulation, the Simulation PC and each connected
MotionDesk PC must have at least one 10 Mbit/s Ethernet card. If
simulation and visualization run on the same PC, one 10 Mbit/s
Ethernet card is sufficient for that PC.
Additional requirements
for notebooks
n MotionDesk has high requirements with regard to graphic
performance and driver quality. In some cases MotionDesk will not
operate properly.
n If the notebook is equipped with an NVIDIA graphics processing
unit, it should be the NVIDIA Quadro

FX Mobile. There must be


only one graphics processing unit on the computer.
n MotionDesk does not support notebooks with NVIDIA Optimus
technology.
Onboard graphic adapters dSPACE does not guarantee that MotionDesk will run on computers
with onboard graphic adapters for the following reasons:
n The specialized on-board graphics processing units often behave
differently from high-end graphics cards.
n Even if the technical specifications of these processing units match
the formal requirements, drivers are often not stable enough to
satisfy the requirements of CAD-like applications.
n A multi-PC solution is not possible with DS1103 or
MicroAutoBox.
n For a multi-PC solution in combination with
SCALEXIO systems, additional hardware is not
required.
Appendix: System Requirements
Software Installation and Management Guide May 2012
I
292

Using Automotive Simulation Models (Vehicle Dynamics,
Trailer, Truck, Traffic Scenarios)
Objective If you use the models for vehicle dynamics, trailer, truck and traffic
scenario simulations, your host PC has to meet the following
requirements.
Host PC requirements
Using AutoBoot Option
Objective AutoBoot Option is only available for the DS1005 and the DS1103. In
this case, your system must meet the following requirements.
Hardware requirements n AutoBoot Option requires an expansion box (for example, an
AutoBox) with:
o A slot CPU connected to the host PC via Ethernet
o One free bracket for the Compact Flash card reader
n Your host PC must support the reading and writing of
CompactFlash cards.
Hardware Required Recommended
Host processor Pentium 4 at 2 GHz Intel Core i5 or i7 processor
Main memory 1 GB RAM 4 GB RAM or more
Appendix: System Requirements
Software Installation and Management Guide May 2012 293
I

Resource Requirements of dSPACE Boards
Objective Depending on the installation, dSPACE boards require resources in the
host PC and the expansion box.
Where to go from here Information in this section
Installation in the Host PC
Resources in the host PC The following table lists the required I/O address range together with
the default address and the required memory of dSPACE boards when
installed in the host PC. Some dSPACE boards support Plug & Play in
which case they require an interrupt request line (IRQ). However the
boards operate correctly even if no free IRQ is available.
Installation in the Host PC 293
Installation in the Expansion Box 294
The resource requirements listed in this table apply to the
host PC.
Board Required I/O
Address Range
Default I/O
Base Address
Required
Memory Range
Required
IRQ
DS1104 2 x 4 KB 1 (PCI)
DS815 10H Plug & Play None 1 (ISA)
DS817 10H Plug & Play None 1 (PCI)
DS819
1)
10H Plug & Play None 1 (PCI Express)
DS821
1)
10H Plug & Play None 1 (PCI Express)
1)
Supported by the dSPACE software as of dSPACE Release 5.2.
Appendix: System Requirements
Software Installation and Management Guide May 2012
I
294

Installation in the Expansion Box
Resources in the expansion
box
When installed in an expansion box, dSPACE boards require the
following resources in the expansion box:
Resources in the host PC The resource requirements for the host PC depend on the connection
between the host PC and the expansion box:
Connection via DS815, DS817, DS819 or DS821 Link Board
The Link Boards require the following resources in the host PC:
The DS819 and DS821 Link Boards are supported by the dSPACE
software since dSPACE Release 5.2.
The resource requirements listed in this table apply to the
expansion box, not to the host PC.
Board Required Address
Bytes
Default I/O
Base Address
Required Memory Required
IRQ
DS1005 10H 300H None None
DS1006 up to board
revision DS1006-03
10H 300H None None
DS1006 as of board
revision DS1006-06
(multicore processor
board)
40H 300H None None
DS1103 10H 300H None None
DS2302 10H 380H None None
Required
Address Bytes
Default I/O
Base Address
Required
Memory
IRQ
10H Plug & Play None 1 o ISA for DS815
o PCI for DS817
o PCI Express for
DS819/DS821
Appendix: System Requirements
Software Installation and Management Guide May 2012 295
I

Connection via Ethernet The boards installed in the expansion
box require no resources in the host PC.
The slot CPUs installed in the expansion box as provided
by dSPACE do not conflict with the default I/O base
addresses of dSPACE boards.
Appendix: System Requirements
Software Installation and Management Guide May 2012
I
296

Index
Software Installation and Management Guide May 2012 297
I

Index
A
activating licenses 156
adding licenses 152
administrator rights
checking 68
ASM
using floating network licenses 193
AutomationDesk
using floating network licenses 190
available license types 23
B
before you start 59
bus interfaces
driver software 284, 285
C
CAN interfaces
driver software 284
CANcardX/CANcardXL driver 282
checking
administrator rights 68
floating network licenses 261
system requirements 267
common software tools 55
compiler
DS1006 78
GNU C 78
GNU C/C++ 79
Microtec PowerPC C 76
SCALEXIO 79
components of dSPACE software 32
ConfigurationDesk - Configuration version
using floating network licenses 191
ConfigurationDesk - Implementation
version
using floating network licenses 192
ControlDesk
using floating network licenses 190
ControlDesk Next Generation software 91
customizing installation 106
customizing ControlDesk Next
Generation 106
D
deactivating licenses 156
debugging dongle problems 251
deleting licenses 156
dongle 145
dSPACE system number 145
installing 104
dongle licenses
debugging problems 251
dongle licenses
enabling 104
files supplied 144
keys.dsp file 145
license.dsp file 145
mechanism 144
migrating to floating network
licenses 201
driver software
bus interfaces 284, 285
DS1006 Compiler
installation 78
requirements 281
dSPACE boards
resource requirements 293
dSPACE license ID 197
DVD contents 29
E
environment variable
C2X_ROOT 85
PPC_ROOT 77
TI_ROOT 84
X86_ROOT 78
expansion box
connecting via bus connection 288
connecting via Ethernet 288
required slots 287
requirements 286
F
features
Installation Manager 23
files supplied
dongle licenses 144
floating network licenses 146
FLEXnet Publisher software 174
FlexRay Configuration Tool
using floating network licenses 189
FlexRay interfaces
driver software 284, 285
floating network licenses 173
automatic license activation 146
checking 261
files supplied 146
FLEXnet Publisher software 174
keys.dsp file 147
License Client 146
License Server 146
requirements 176
settings 177
license.dat file 148
license.dsp file 147
linger time 148
floating network licenses
migrating 202
migrating from dongle licenses 201
migrating to 202
modify 180
obtaining permanent licenses 197
setting up client/server-connection 182
setting up License Server 174
step-by-step license check 262
timeout mechanism 148
updating license.dat file 180
G
GNU C Compiler
installation 78
GNU C/C++ Compiler
installation 79
H
handling dSPACE installations 121
hard disk 269
host PC hardware
free hard disk 269
host processor 269
main memory 269
required ports 269
required slots 271
requirements for license handling 271
host PC software
C compiler for RCP and HIL
software 281
C compiler for TargetLink 282
driver software for bus interfaces 284,
285
MATLAB 69
Microsoft Internet Explorer 286
Microsoft Office 286
operating system 273
I
information
requested by setup program 92
installation cases 63
installation instructions
customizing ControlDesk
NextGeneration 106
Installation Manager 121
activating a dSPACE installation 26
connecting MATLAB to dSPACE
software 26
deactivating a dSPACE installation 26
deactivating the active installation 130
features 23
Index
Software Installation and Management Guide May 2012
I
298

Installation Manager
getting diagnostic information 27
managing licenses 26
removing a dSPACE installation 235
switching to another dSPACE
installation 26
viewing installation details 123
installation problems 241
installation types 18
installing
components 63
ControlDesk Next Generation 63
dongle 104
in new folder
preconditions 65
instructions for customizing
ControlDesk Next Generation 106
License Server 178
MATLAB 133
modules 99
packages for automating CalDesk 108
RCP and HIL software 63
RCP and HIL software, TargetLink,
ControlDesk Next Generation,
SystemDesk, Model Compare 91
software patches 63, 101
TargetLink 63
third-party software 73
K
keys.dsp file
dongle licenses 145
floating network licenses 147
L
License Client 146
license files
files supplied
dongle licenses 144
floating network licenses 146
merging 162
license information
merging 162
License Manager
activating licenses 156
adding licenses 152
deactivating licenses 156
deleting licenses 156
merging license files 162
simplifying license handling 163
license mechanism
dongle licenses 144
license mechanisms 23
license problems 248
dongle and floating network
licenses 253
license problems
dongle licenses 249
floating network licenses 256
License Server 146
installation 178
requirements 176
setting up 174
settings 177
updating 180
license types 23
license.dat file
floating network licenses 148
updating 180
license.dsp file
dongle licenses 145
floating network licenses 147
licensed RCP and HIL software
package 33
license-free RCP and HIL software 33
licenses
SystemDesk 51
licensing 23
limitations for TargetLink 64-Bit
version 278
limitations for Windows 64-Bit and
dSPACE 64-Bit software 278
limitations for Windows 7 277
limitations for Windows Vista 277
linger time 148
M
main memory of host PC 269
MATLAB
compatibility information 69
installation 75
modifiying the installation by dSPACE
software 71
requirements 69
MATLAB connection, preferred 20
mechanism of
dongle licenses 144
merging license files 162
merging license information 162
Microsoft Internet Explorer 286
Microsoft Office 286
Microtec PowerPC C Compiler
installation 76
requirements 281
using floating network licenses 195
migrating 201
floating network licenses 202
MLIB/MTRACE
using floating network licenses 194
Model Compare 49
using floating network licenses 195
Model Compare software 91
ModelDesk
using floating network licenses 193
modifying the dSPACE installation 172
MotionDesk
system requirements 290
using floating network licenses 193
MotionDesk Blockset
using floating network licenses 194
N
NTFS partition 66
O
obtaining permanent floating network
licenses 197
P
patches 101
PowerPC C Compiler
installation 76
requirements 281
preconditions
for installing 65
preferred MATLAB connection 20
problems
installation 241
protected modules
AutomationDesk 53
ControlDesk Next Generation 47
Model Compare 49
SystemDesk 51
TargetLink 42
protected products 36
protected versions
AutomationDesk 53
SystemDesk 51
R
RCP and HIL 36
RCP and HIL software 91
definition 29
removing software 208
repairing a dSPACE installation 247
required licenses
ControlDesk Next Generation 47
Model Compare 49
RCP and HIL 36
SystemDesk 51, 53
TargetLink 42
required ports 269
required user rights 66
requirements
dSPACE boards
resources 293
Index
Software Installation and Management Guide May 2012 299
I

requirements
expansion box 286
connecting via bus connection 288
connecting via Ethernet 288
required slots 287
host PC hardware
for license handling 271
free hard disk 269
main memory 269
ports for connecting hardware 269
processor 269
required slots 271
host PC software
C compiler for RCP and HIL
software 281
C compiler for TargetLink 282
CANcardX/CANcardXL driver 282
driver software for bus
interfaces 284
driver software for FlexRay
interfaces 285
MATLAB 69
Microsoft Internet Explorer 286
Microsoft Office 286
operating system 273
License Server 176
resource requirements of dSPACE
boards 293
resources
for installation in expansion box 294
for installation in host PC 293
RTI and RTI blocksets
using floating network licenses 188
S
SCALEXIO Compiler
installation 79
setting up
client/server-connection 182
License Server 174
settings of dSPACE License Server 177
setup program
introduction 18
requested information 92
simplifying license handling 163
software
dSPACE
components 32
installation
patches 101
third-party 73
Model Compare
protected modules 49
required licenses 49
RCP and HIL
licensed 33
license-free 33
software
RCP and HIL
protected products 36
required licenses 36
supplied license files
dongle licenses 144
floating network licenses 146
system requirements 267
asap3lib 290
AutoBoot Option 292
host PC hardware 269
MotionDesk 290
operating system 273
third-party software 279
SystemDesk
licenses 51
using floating network licenses 196
SystemDesk software 91
T
TargetLink 64-Bit
limitations 278
TargetLink software 91
TCP/IP
floating network licenses 173
setting up connection between client
and server 183
Texas Instruments ANSI C Compiler
requirements 281
Texas Instruments ANSI-C Compiler
installing 82
root folder 83, 84
Texas Instruments Compiler
basics 79
installing after dSPACE software 84
installing before dSPACE software 83
preparing Parallel Runtime Support
Library 86
setting environment variable 85
upgrading to Code Composer Tools 89
upgrading Version 4.7 to 5.11 87
upgrading Version 5.10 to 5.11 88
third-party software 73, 279
timeout mechanism 148
troubleshooting 239
U
using dSPACE Installation Manager 121
using floating network licenses
ASM 193
AutomationDesk 190
ConfigurationDesk - Configuration
version 191
ConfigurationDesk - Implementation
version 192
ControlDesk 190
using floating network licenses
FlexRay Configuration Tool 189
Microtec PowerPC C Compiler 195
MLIB/MTRACE 194
Model Compare 195
ModelDesk 193
MotionDesk 193
MotionDesk Blockset 194
RTI and RTI blocksets 188
SystemDesk 196
W
Windows 64-Bit
limitations 278
Windows 7
limitations 277
Windows Vista
limitations 277
Index
Software Installation and Management Guide May 2012
I
300